The article preview can be found here
I reviewed the article, and have some ideas about it I would like to share.
First it has been some time since I have had any reason to modify grub
configuration files, and my initial thought was why not use grubby to
copy the default menuentry and modify it to suit. None the less I used
the provided instructions until I had to try alternative methods for the
installation to work. So my first point would be why not use grubby
since it makes the user experience better for adding a menu entry by the
virtue of being able to copy a working menuentry to make a new one with
your own specified kernel and initrd? The drawback being having to
modify /boot/grub2/grub.cfg which is only slightly more hazardous than
The second thing of note is what behavior grub2-mkconfig has on making
the grub.cfg file based upon the contents of /etc/grub.d/, and what the
original OS expects to be in the cfg file. So reviewing the
/boot/grub2/grub.cfg file is necessary to determine the various files to
include in /etc/grub.d/ prior to calling grub2-mkconfig. At the least a
link to here should be provided
Third is the networking, I used a VM of CentOS 7 to test with, and my
networking was by default dhcp, which basically allowed me to drop all
networking references in favour of the default behavior. I'm not certain
bare metal will be the same, but I think it should.
Fourth, the link provided was not working for the install.img, and I
tried it repeatedly finally searching for and finding this one
which worked and I was able to install from the files retrieved, by
using the curl instructions provided by the author for getting the
vmlinuz and initrd.img, so those links worked.
Finally, this article idea may be better served by splitting it into
smaller bits. It is a pretty advanced topic for the normal average user.
The steps I followed were -
1. Create new CentOS 7 VM with Boxes.
2. Follow instructions given in article to use curl to get vimlinuz and
3. Modify grub 40_custom file in /etc/grub.d/ as per directions in
article, excepting networking
4. Use grub2-mkconfig to create grub.cfg.
5. Attempt install, fails repeatedly on part 2 of Anaconda installer,
something regarding missing dependencies.
6. Use grubby to make menu entry then modify /boot/grub2/grub.cfg to
exclude default menuentry kernel commands and options to suit
7. Find alternative download link to use. (for Anaconda part 2 of
install) Modify grub.cfg to suit new link location.
8. Install F29 Server and login
I will document the process I went through and share it with the author.
I found using vi was tedious so installed vim-enhanced which provided a