| 1 |
On Sun, Sep 1, 2013 at 11:55 AM, Walter Dnes <waltdnes@××××××××.org> wrote: |
| 2 |
>> I usally use ext4 as filesystem. |
| 3 |
>> |
| 4 |
>> # lsmod|grep ext |
| 5 |
>> ext3 100768 0 |
| 6 |
>> jbd 39586 1 ext3 |
| 7 |
>> ext2 49572 0 |
| 8 |
>> ext4 263621 1 |
| 9 |
>> crc16 1255 2 ext4,bluetooth |
| 10 |
>> mbcache 4450 3 ext2,ext3,ext4 |
| 11 |
>> jbd2 48679 1 ext4 |
| 12 |
>> |
| 13 |
>> Isn't great what an initramfs can do? |
| 14 |
> |
| 15 |
> In this case, initramfs is your root filesystem, from which you load |
| 16 |
> another fs and then transfer (pivot root?) to it. You have to build |
| 17 |
> initramfs support into the kernel, to boot an initramfs. So my argument |
| 18 |
> still stands, regardless of whether your *INITIAL* filesystem is ext4fs, |
| 19 |
> or ZFS, or initramfs, that *INITIAL* filesystem has to be built into the |
| 20 |
> kernel. Also, I really wonder what the point is in having to use |
| 21 |
> initramfs on a system where /usr is part of /. |
| 22 |
|
| 23 |
It allows you to keep some kernel bits in modules. If ever you change your mind |
| 24 |
on whether to include / exclude / reconfigure those kernel bits in the |
| 25 |
future, your |
| 26 |
kernel recompile will take a lot, lot, shorter. |
| 27 |
|
| 28 |
Case in point - do you enable all the ext4 options, like acls and |
| 29 |
whatnot? Let's say no. |
| 30 |
|
| 31 |
What if you suddenly have to mount an external hard disk to recover some system |
| 32 |
on your server and the hard disk uses those ext4 options? If ext4 is |
| 33 |
hard built into your |
| 34 |
kernel, your recompile will have to basically redo the whole thing, |
| 35 |
whereas if ext4 |
| 36 |
was a module you would only recompile ext4 itself. |
| 37 |
-- |
| 38 |
This email is: [ ] actionable [x] fyi [ ] social |
| 39 |
Response needed: [ ] yes [ ] up to you [x] no |
| 40 |
Time-sensitive: [ ] immediate [ ] soon [x] none |
Archives