1 |
On Nov 8, 2011 5:03 PM, "Dale" <rdalek1967@×××××.com> wrote: |
2 |
> |
3 |
> Alan Mackenzie wrote: |
4 |
>> |
5 |
>> On Mon, Nov 07, 2011 at 09:26:50PM +0200, Alan McKinnon wrote: |
6 |
>> |
7 |
>>> ext2/3/4 are all backwards compatible. ext4 does have a certain feature |
8 |
>>> (I forget what) that once used breaks this compatibility but you are |
9 |
>>> highly, highly unlikely to ever do that on /boot. |
10 |
>>> The benefits of ext3/4 are irrelevant for /boot anyway - that |
11 |
>>> filesystem is write-seldom, read ever so slightly more often. |
12 |
>> |
13 |
>> Really? I put my PC into power saving mode before going to bed each |
14 |
>> evening. The PC needs to read /boot to return to normal operation. |
15 |
>> |
16 |
>>> -- |
17 |
>>> Alan McKinnnon |
18 |
>>> alan.mckinnon@×××××.com |
19 |
> |
20 |
> |
21 |
> Really. It takes maybe 1/4 of a second for it to load the kernel from |
22 |
/boot. After that, it may not read /boot again until you boot back up the |
23 |
next day. So, 1/4 of a second per boot is very little. The only other |
24 |
time /boot is used is when you update grub or your kernel. That is maybe a |
25 |
1 or 2 second write, if that much. Even if you hibernate/sleep/reboot a |
26 |
few times a day, it is still read very little. That is pretty much |
27 |
irrelevant. |
28 |
> |
29 |
> Me, I have always put ext2 on /boot. I just don't see much need in |
30 |
anything fancy for something that is used so seldom plus everything is |
31 |
likely stored somewhere else anyway. The kernel should be in the kernel |
32 |
source directory and a emerge of grub would restore everything else except |
33 |
the config. Not much to lose there. |
34 |
> |
35 |
|
36 |
Not to mention that /boot usually has a noauto option, so it's very |
37 |
unlikely that a wayward prog can somehow bollix up the filesystem. |
38 |
|
39 |
In addition, if one's using ext4, the in-kernel ext4 fs driver performs |
40 |
perfectly well as an ext2/3 driver. |
41 |
|
42 |
Rgds, |