Olaf Hering wrote:
[]
> To create the initrd you needed a loop file, at least for ext2, minix etc.
It's just damn trivial to pack your files into cpio archive and gzip it.
No need for any filesystem code in kernel, be it ext2, minix or other.
initrd => initramfs conversion (what you said I "force" on users) is
to switch from loop+whatever-fs-du-jur to plain dirrectory and cpio,
and to add the final mount+run_init into the initrd script. And after
that's done, everything becomes good... ;)
> But so far, the arguments are not convincing that kinit has to be in the
> kernel tree.
Here, I agree.
/mjt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
