public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ext4/ext3 for /boot?
Date: Tue, 8 Nov 2011 20:11:27 +0700	[thread overview]
Message-ID: <CAA2qdGXNhc=0qA8u1E84h+-KuZhJfOVH69WcENaSAX2pi1RE+Q@mail.gmail.com> (raw)
In-Reply-To: <20111108123523.42bd460f@zaphod.digimed.co.uk>

On Tue, Nov 8, 2011 at 19:35, Neil Bothwick <neil@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



  reply	other threads:[~2011-11-08 13:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 18:29 [gentoo-user] ext4/ext3 for /boot? Jarry
2011-11-07 18:37 ` Stéphane Guedon
2011-11-07 19:26 ` Alan McKinnon
2011-11-07 19:32   ` Michael Mol
2011-11-07 20:41     ` [gentoo-user] " Nikos Chantziaras
2011-11-07 20:42     ` [gentoo-user] " Stroller
2011-11-07 21:14       ` Michael Mol
2011-11-08  8:37   ` Alan Mackenzie
2011-11-08  9:49     ` Dale
2011-11-08 11:15       ` Pandu Poluan
2011-11-08 12:35         ` Neil Bothwick
2011-11-08 13:11           ` Pandu Poluan [this message]
2011-11-08 14:14             ` Dale
2011-11-08 21:59             ` Sebastian Beßler
2011-11-08 22:07               ` Paul Hartman
2011-11-09  2:44                 ` Pandu Poluan
2011-11-09  9:39                   ` Neil Bothwick
2011-11-09 11:39                     ` Pandu Poluan
2011-11-09  3:03             ` bill.longman
2011-11-09  4:16               ` Pandu Poluan
2011-11-09  4:18                 ` Pandu Poluan
2011-11-09  5:22                   ` bill.longman
2011-11-09  6:42                     ` Pandu Poluan
2011-11-09  1:36           ` J.Marcos Sitorus
2011-11-08 15:52     ` Stroller
2011-11-08 16:00       ` Neil Bothwick
2011-11-08 18:59         ` David Guillermo
2011-11-09 18:18     ` Alan McKinnon
2011-11-07 19:38 ` Alex Schuster
2011-11-08  0:41 ` pk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA2qdGXNhc=0qA8u1E84h+-KuZhJfOVH69WcENaSAX2pi1RE+Q@mail.gmail.com' \
    --to=pandu@poluan.info \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox