yancek |
03-18-2016 08:03 PM |
I downloaded and installed CentOS 7 to check it out. The grub.cfg file was in the /boot/grub2 directory. The reason you previously saw the grub.cfg file as empty is because you tried to open it as a normal user. Did this to test and got the same message you posted earlier and an empty file showing. No problem with it as root.
I moved the black lab iso to the / of the CentOS partition and used the loopback entry pointing to it and it failed with the message:
Quote:
no server is found, you need to load the kernel first
|
I extracted the black lab directories/files from the iso and copied them to the / of CentOS and then changed the menuentry path to the kernel (vmlinuz) and initrd in the CentOS grub.cfg file and once again it failed with the message:
Quote:
file /casper/vmlinuz not found, you need to load the kernel first.
|
I've booted extracted Linux iso files dozens of times with various Linux distributions using Grub Legacy and Grub2 and this is the first time I can recall not being able to boot an extracted iso from /. Booting an iso usually fails unless you are using one of the Ubuntus so that was no surprise.
Quote:
loopback loop (hd0,msdos1)/black-lab-702-x86_64.iso
|
If you try to boot it from the boot or Downloads directory, you need to change the above, for example from boot:
Quote:
loopback loop (hd0,msdos1)/boot/black-lab-702-x86_64.iso
|
Quote:
Running update-grub as root returned
|
Yes, that is expected behavior because only the Ubuntus and maybe Debian use update-grub. It's just a stub pointing to the grub-mkconfig command. Look at the link in my last post for the exact command. If you put the entry in grub.cfg, do NOT run grub-mkconfig as it will remove that entry. Just save and reboot. If you had put the entry in the /etc/grub.d/40_custom, then you would run grub-mkconfig.
|