| 1 |
On 10/18/2013 12:15:35 PM, Francisco Ares wrote: |
| 2 |
> Thanks, Gareth. |
| 3 |
> |
| 4 |
> But it is very interesting that with no special customizations, I am |
| 5 |
> almost |
| 6 |
> able to have a fully functional system. |
| 7 |
> |
| 8 |
> That new thing about having to use a initramfs when the root |
| 9 |
> filesystem and |
| 10 |
> the /usr directory are not present in the same physical partition, it |
| 11 |
> turns |
| 12 |
> out that it helps on having the "genkernel" generated initramfs do |
| 13 |
> the job |
| 14 |
> of mounting different arrangements for partitions, directories and |
| 15 |
> unionfs |
| 16 |
> mounts. That is because of the file "/etc/initramfs.mounts" where the |
| 17 |
> specified mount entries, are extracted from the "/etc/fstab" and |
| 18 |
> mounted |
| 19 |
> before the initram gives way to the real root environment. |
| 20 |
|
| 21 |
You can have initramfs be tmpfs instead of ramfs now. New in the 3.12 |
| 22 |
kernel. (Basically if CONFIG_TMPFS=y you get it for free unless you say |
| 23 |
rootfstype=ramfs or specify a root= to switch to, those enable the old |
| 24 |
legacy rootfs=ramfs behavior.) |
| 25 |
|
| 26 |
If you're keeping initramfs around, it's generally a good thing. Means |
| 27 |
that df tells you how much space you have (and things like rpm that |
| 28 |
care actually get a nonzero size), and if you cat /dev/zero > /blah.txt |
| 29 |
as root the filesystem fills up and _stops_ rather than panicing the |
| 30 |
kernel. |
| 31 |
|
| 32 |
Rob |
Archives