Originally posted by Feathers McGraw
View Post
Not really sure what you mean.
/boot is a linux directory that holds the kernel and other necessary files for booting linux - along with grub files in most distros. It can be separate from root (/) or not. Separating it is is usually a function of using a file system not supported by grub. Like btrfs in the past or software RAID or encrypted file systems.
You may have a separate grub partition, as I have done in the past with the old version of grub - now known as grub-legacy. It was quite a bit of work to maintain. However, with grub2 a.k.a. grub-pc it's easier to chain grub installs together. Basically, I boot to a grub install and have stanzas in my 40_custom grub.d file that point to the grub.cfg file of other grub installs. I can switch back and forth until I have selected the install and kernel that I want from any number of installs this way.
In my case (which I have documented elsewhere on this forum), I simply created a vanilla install using Ubuntu server with no desktop or any software at all except the bare minimum and installed grub from this install to /dev/sda. In total, less than 800mb and it could probably be smaller if I pushed it. I boot into it every few months and run updates.
All subsequent installs' grub's are pointed at /dev/sdb and therefore never actually booted to. This does create the necessary /boot/grub/cfg files for each distro that are updated along with that install, but without re-booting into the main grub install. I manually create an entry in the main grub install that reads the secondary install grub.cfg - which I can select from or ESC back to the "main menu" as it were. This way if I decide to wipe one install or another, my system is always bootable and all other installs are reachable. Neat huh?
In either case: separate /boot or stand-alone grub install, Windows isn't aware of either so it has no effect on a Windows install.
Comment