On Tue, Nov 8, 2011 at 19:35, Neil Bothwick <n...@digimed.co.uk> wrote: > On Tue, 8 Nov 2011 18:15:06 +0700, Pandu Poluan wrote: > >> > Me, I have always put ext2 on /boot. I just don't see much need in >> > anything fancy for something that is used so seldom plus everything is >> > likely stored somewhere else anyway. The kernel should be in the >> > kernel source directory and a emerge of grub would restore everything >> > else except the config. Not much to lose there. > > One of the benefits of GRUB2 is that the information used to create the > config file is in /etc. If /boot is toasted, you can recreate all you > need with > > grub2-install > grub2-mkconfig > cd /usr/src/linux > make install > >> Not to mention that /boot usually has a noauto option, so it's very >> unlikely that a wayward prog can somehow bollix up the filesystem. > > Leaving /boot unmounted invites the inevitable error of forgetting to > mount it before installing a new kernel. I prefer to mount it ro, that > way its contents are available, protected from accidental overwriting and > it shouts at you if you forget to remount it before installing a kernel > or updating GRUB. >
I have a script that does the menuconfig + diff .config + make + install (including kernel copying to /boot, automagically mounting /boot if needed), so I can get away with noauto ;-) Oh, and it also auto-modifies grub.cfg for me :-D Rgds, -- FdS Pandu E Poluan ~ IT Optimizer ~ • LOPSA Member #15248 • Blog : http://pepoluan.tumblr.com • Linked-In : http://id.linkedin.com/in/pepoluan
