8 thoughts on - CentOS 7, Not Systemd Questions

• It doesn’t seem to have default packages. But you can always compile your own. Of course when kernel updates you need to update config by hand.

  Or you could do sensible thing and learn to change grub2 configs. It wasn’t that hard when I had to change some kernel boot parameter.

  -vpk

• GRUB < 2 isn't supported, but it can be made to work. I still use it on most of my Fedora and EL7 systems. Assuming that you already have GRUB installed, the steps are basically: * Tell anaconda not to install a bootloader * After installation, boot from a different OS or live CD and manually create a GRUB stanza for your new OS * Boot your new OS * Create /etc/sysconfig/kernel * ln -s /boot/grub/grub.conf /etc/ The last two steps enable grubby to update grub.conf when you install a new kernel.

• No. I do *not* want to compile my own. We have a very few packages like that, and we do *not* want to be responsible for worrying and tracking security and bugfixes and rebuilding the packages, not when we have 170+
  servers and workstations to worry ’bout.

  I’ve looked at them some, on the one or two fedora boxes here, and on my netbook’s ubuntu netbook remix, and I *LOATHE* having to wade through dozens and dozens of lines of code to fix something.

  Hey, I thought “declarative” configuration files were the way to go, at least according to this eternal thread… and if old grub.conf isn’t that, then your definition is a lot different than mine.

  mark

• This is what I put in my notes about GRUB2

  I have RHEL 7 Beta installed in dual boot with CentOS 6.x. Since RHEL 7
  installed GRUB2, I had problem that RHEL 7 is default boot.

  My personal solution was to go to /etc/grub.d and run command:
  mv 10_linux 31_linux

  grub2-mkconfig -o /boot/grub2/grub.cfg

  Explanation:

  – /etc/grub.d is where grub2 writes down config files used to create boot menu.
  – OS-prober creates 30_os-prober file in /etc/grub.d
  – 10_linux is created for RHEL/CentOS 7.x system installed.

  If you change order of files in /etc/grub.d (numbers at the start of the files) the list generated with grub2-mkconfig will change order in the GRUB2 menu :)

  Fedora/RHEL 7.x have a changed GRUB2 so for further reading read:

  5.3 Multi-boot manual config:
  http://www.gnu.org/software/grub/manual/grub.html#Multi_002dboot-manual-config

  and

  Fedora GRUB Wiki:
  http://fedoraproject.org/wiki/GRUB_2

• Ian Pilcher wrote:
  Interesting… can I do that with the preupgrade from 6.5? And I *rarely*
  see grub updated….

  mark

• That I thought, that’s why I suggested sensible thing. I didn’t say the new config is better. I am pragmatist and just learn the stuff thrown at me and continue chugging on. I think there might be also somekind of tool to make the config editing more sane. Everyone can make their own conclusions on that. I think main thing is that old times aren’t coming back and usually there is some reason for it. (Although some of the old things I am really not wanting back either like irq jumpers on isa motherboards and whatnot)

  -vpk

• I’m not familiar with preupgrade, but I would guess that this method wouldn’t work. (Actually I’d be somewhat surprised if it were possible to do an in-place upgrade from CentOS 6 to CentOS 7 and get a properly functioning system; the differences between the two are so large.)

  I pretty much always do side-by-side installs and then move data and configurations over.

• Configs from GRUB and GRUB2 can coexist in same /boot tree, I managed to install GRUB2 over GRUB and configs of GRUB were NOT affected. Reinstalling GRUB from 6.x should do the trick and no GRUB2 update should mess with functioning GRUB1.