* up2date-3.0.7-1 up2date should really have a non-interactive mode. With 8.0, the first time you run up2date -u it pops up an interactive dialog, which makes it a pain to have a machine automatically up2date itself after an automated install.
The first time you run up2date you have to register with RHN, since rhn_register was merged with up2date. After that I am able to run up2date without any interaction. up2date --nox -u works just fine.
I'm thinking that those doing automagical installs should probably be registered w/ RHN ahead-of-time and ~perhaps~ the Activation Keys feature of RHN will help: https://rhn.redhat.com/news.pxt https://rhn.redhat.com/network/user/activation_keys.pxt "This command can be easily added to the post-installation process." looks pretty promising. *shrug* I should try it one day. Cheers, -Ali
This system was registered (via rhnreg_ks). Activations keys are really handy.
sounds like rhnreg_ks needs to set "networkSetup"=1. added in 3.1.5 or so
Fix confirmed with up2date-3.1.15-7.
Not quite there yet.. I just ran 'up2date -f -i --nox --nosrc up2date >some_log_file' At the time I ran this RHN was temporarily offline. up2date merrily spewed an ncurses "Fatal Error" dialog to my log file file stating that RHN capabilities were being upgraded and that full service would be restored within 1 hour. The real problem was that up2date sat waiting for a user to click the ncurses "Ok" button indefinitely. We really need a clear line drawn between up2date's interactive and non-interactive modes if it is going to be a useful command line tool.
I think I'm deferring this. First one cases are geared to make most users life easier. The use cases described are pretty unnusual.