public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ext4/ext3 for /boot?
Date: Tue, 08 Nov 2011 03:49:03 -0600	[thread overview]
Message-ID: <4EB8FB0F.7040602@gmail.com> (raw)
In-Reply-To: <20111108083724.GA3497@acm.acm>

Alan Mackenzie wrote:
> On Mon, Nov 07, 2011 at 09:26:50PM +0200, Alan McKinnon wrote:
>
>> ext2/3/4 are all backwards compatible. ext4 does have a certain feature
>> (I forget what) that once used breaks this compatibility but you are
>> highly, highly unlikely to ever do that on /boot.
>> The benefits of ext3/4 are irrelevant for /boot anyway - that
>> filesystem is write-seldom, read ever so slightly more often.
> Really?  I put my PC into power saving mode before going to bed each
> evening.  The PC needs to read /boot to return to normal operation.
>
>> -- 
>> Alan McKinnnon
>> alan.mckinnon@gmail.com

Really.  It takes maybe 1/4 of a second for it to load the kernel from 
/boot.  After that, it may not read /boot again until you boot back up 
the next day.  So, 1/4 of a second per boot is very little.  The only 
other time /boot is used is when you update grub or your kernel.  That 
is maybe a 1 or 2 second write, if that much.  Even if you 
hibernate/sleep/reboot a few times a day, it is still read very little.  
That is pretty much irrelevant.

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.

< shrugs >

Dale

:-)  :-)



  reply	other threads:[~2011-11-08  9:50 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 [this message]
2011-11-08 11:15       ` Pandu Poluan
2011-11-08 12:35         ` Neil Bothwick
2011-11-08 13:11           ` Pandu Poluan
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=4EB8FB0F.7040602@gmail.com \
    --to=rdalek1967@gmail.com \
    --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