Re: configuration files created by Anaconda exclusively

2012-08-09 Thread Scott Schmit
On Thu, Aug 09, 2012 at 12:48:02PM -0700, Adam Williamson wrote: > The reason anaconda writes /etc/default/grub is that it can actually > contain different things depending on the install config. Most notably, > the default timeout can change depending on whether you're installing a > single-boot o

Re: configuration files created by Anaconda exclusively

2012-08-09 Thread Adam Williamson
On Thu, 2012-08-09 at 15:34 -0400, Jan Vcelak wrote: > > I offer my help to "improve" the situation by testing or providing > > patches if involved parties would like to. > > This is great! I can try to identify other "base" packages with the > same problem. There should not be many. > > The ques

Re: configuration files created by Anaconda exclusively

2012-08-09 Thread Jan Vcelak
> I offer my help to "improve" the situation by testing or providing > patches if involved parties would like to. This is great! I can try to identify other "base" packages with the same problem. There should not be many. The question is, what is the best solution. If the configuration file shoul

Re: configuration files created by Anaconda exclusively

2012-08-09 Thread Jan Vcelak
> > I recently switched my BIOS from legacy to EFI mode and therefore > > needed to > > replace grub by grub2-efi. As I do not like garbage in /etc, I > > removed all > > grub configuration files (rpm -qca grub\*) before uninstalling the > > old > > package. Unfortunately /etc/default/grub is just

Re: configuration files created by Anaconda exclusively

2012-08-09 Thread Jan Vcelak
> On my BIOS-based F17 that was upgraded from earlier Fedora install, > /etc/default/grub is owned by the package grub2-tools, so your > problem > appears to be solved moving forward, because grub2 is taking over. The file is owned by grub2-tools but marked as %ghost (not %shadow, sorry). Which me

Re: configuration files created by Anaconda exclusively

2012-08-09 Thread Ian Pilcher
+1 to Jan's point. It should be possible to recover a critical file (or at least a skeleton thereof) by reinstalling the owning RPM. -- Ian Pilcher arequip...@gmail.com "If you're goi

Re: configuration files created by Anaconda exclusively

2012-08-09 Thread Simone Caronni
Hello, On 9 August 2012 16:39, Przemek Klosowski wrote: > On my BIOS-based F17 that was upgraded from earlier Fedora install, > /etc/default/grub is owned by the package grub2-tools, so your problem > appears to be solved moving forward, because grub2 is taking over. I think > you are saying that

Re: configuration files created by Anaconda exclusively

2012-08-09 Thread Reindl Harald
Am 09.08.2012 10:28, schrieb Jan Včelák: > I recently switched my BIOS from legacy to EFI mode and therefore needed to > replace grub by grub2-efi. As I do not like garbage in /etc, I removed all > grub configuration files (rpm -qca grub\*) before uninstalling the old > package. Unfortunately

Re: configuration files created by Anaconda exclusively

2012-08-09 Thread Przemek Klosowski
On 08/09/2012 04:28 AM, Jan Včelák wrote: I recently switched my BIOS from legacy to EFI mode and therefore needed to replace grub by grub2-efi. As I do not like garbage in /etc, I removed all grub configuration files (rpm -qca grub\*) before uninstalling the old package. Unfortunately /etc/defa