/boot filesystem

[Goh Lip]

On Monday 22,November,2010 11:50 PM, Rashkae wrote:
> I can't do this myself, since I haven't used a separate boot partition
> since the Slackware 7 days.  update-grub, I would immagine, has the
> potential to be dangerous to run in this scenario, if it doesn't error
> out gracefully.

Okay then, no problem; /in the final analysis/at the end of the day/when 
it comes to the crunch/when the s*** hits the fan/(heh heh - engrish is 
really funny) what we are doing is splitting hairs (heh) over things 
that do not really matter.

So we've dissected this matter/flogged a dead horse/ to eternity/kingdom 
come. It's time to call it a day/quits/throw in the towel/ and get on 
with our lifes.

But thanks for the input.

>
> If you don't have separate boot partitions for your OS /boot, then what,
> exactly, do you consider your primary boot partition?  (Other than the /
> of one of your Linux installs?).  I think we are talking about
> completely different concepts here.  (Unless you're referring to the
> boot partition to embed grub in a gpt drive, but I think that's a level
> of discussion way beyond the topic that spawned this thread.)

Rashkae, I have a separate boot partition, henceforth called 'primary 
boot',  independent of any OS, in grub2, that's set to mbr and boots all 
my OS directly (except for windows, which chainloads) - no kernels. And 
I do not need to update or maintain.

Yes, there's the usual OS /boot's, set to /dev/sdaX, in /,  which I do 
not worry or look at at all. Any kernel updates, etc will be updated as 
normal and the primary boot will automatically pick/boot these up.

So this is not anything unusual, just a simplified grub2 partition (I 
started this with grub-l).

Take care and regards - Goh Lip