On 4/17/05, Sylvain Rouillard <RouillardSy@xxxxxxxx> wrote: > Fair enough, no bug here and I found the culprit. Though this raises some > questions... what's the point of this change? are we supposed to login in in > text mode to test something? aren't we supposed to bring these rpmnew files > that yum creates into action? Too many questions for a Sunday waking up! First, the rpmnew files are a feature of the rpm not yum. You would see them created similarly if using up2date or other high level packaging tool layered over rpm. So let's not confuse the issue by implying to other people this is a yum specific issue. Second, I haven't seen anyone suggest to me that its a good idea to blindly replace your working config files with the rpmnew files. rpmnew files are created when the rpm system sees that a config file is no longer stock and has been customized. rpmnew files only exist because your configs have been changed from what rpm understands to be a default file. rpm -V packagename is handy for manually finding these sorts of files for yourself. Until you do a visual inspection of the rpmnew file against the old config... you have no idea what changes are going to be made. Since the anaconda installer gives you a choice of graphical or text login as part of the install process, it stands to reason that the installer could very well customize inittab. The inittab.rpmnew file encodes the default settings, so whether the default is 3 or 5, if everyone blindly replaced their config with the rpmnew file some users are going to be upset at the result simply because some users use runlevel 3 and some use 5. -jef