making menu.lst readonly will prevent anything..
EchoLynx wrote:/boot/grub/menu.1st doesn't exist, but /boot/grub/menu.lst does. Is that what you're talking about?
Are you saying that making menu.lst readonly will prevent anything from overwriting it?
YES, but the OS may not install correctly since it will not be able to write its grub boot text
but /boot/grub/menu.lst does. Is that what you're talking about?
YES, it is just a fonts selection issue, depends on where I paste from or if I simply type it in the text..
- terminal cut and paste.. menu.lst
As altair4 indicated there are two ways of installing an OS
- Method a) let the install proceed automatically
--it will use the MBR (Master boot record) to enable a boot: unless you uncheck Write to MBR
- Method b) Uncheck the Write to MBR, this prevents booting the boot menus for that new OS
--you are then responsible for adding the changes made, which will appear in /boot/grub directory, not in the MBR
--again there is a backed up file made by grub menu.lst~
that file is now the original file before that OS was installed..
So that new OS will not boot, until you edit grub to include its entry text (boot stanza)
I sometimes use the method b), if I only want to see what the OS will install as a boot entry
I can use chainload +1 to pick up other boot loaders, for example if I used Grub, I could add chainload +1 to pick up the windows OS boot manager (loader: NTLDR) to then boot with its own boot loader sequence..
EchoLynx wrote:I thought mint's pretty graphics were stored in /boot/gfxmenu. Shouldn't I protect that? In fact, shouldn't I protect the whole /boot/grub folder?
If you wanted to, but it isn't necessary, Mint's Grub will not be completely destroyed by another OS install, only the MBR record is being changed to enable that other OS to boot, that does change the grub text entries to locate the default boot entry, which will either be Mint or the other OS; Mint only adds them (other OS text entries in Grub after the last Mint OS stanzas (text entries), so nothing is really lost
Grub boot order, multi-booting Linux + Windows OS..
If you want another explanation about multi-booting (dual boot) with Linux + windows (Linux first or Windows + Linux (windows first), either these forums, forum user:Fred data on Grub
or apcmac for the multiboot OS help
http://forums.linuxmint.com/search.php? ... boot+order
http://apcmag.com/the_definitive_dualbo ... bystep.htm
EchoLynx wrote:If I was to point an installer to /boot/grub, wouldn't it overwrite /boot/grub and replace everything with only what is required to boot the OS I am installing?
Depends on the installer application being used, I guess
- but in this version of Grub, NO