On Mon, Nov 17, 2003 at 09:51:29PM +0100, Olivier Blin wrote:
By the way, what should we do about devfs ?
It is deprecated, but is there any working alternative yet ?
udev needs userspace tools IIRC.

uhm, good question, we still ship it enabled by default in 9.2, but there is nothing (i belive) that depends on having it enabled i would keep things as they are, supported but not compulsory, even if that becomes an hassle to maintain.

I will try to add cramfs/tmpfs support if someone kindly notices the
fact i am doing it, if this stuff is not scheduled to be merged
sometimes then i will not bother.

Okay, I let you do it :)
ok :)

It would be a good start to have a look at Debian's linuxrc and
mkinitrd, since they use exactly what you want to do.
http://http.us.debian.org/debian/pool/main/i/initrd-tools/initrd-tools_0.1.55.tar.gz
It is a much cleaner implementation that the rh based mkinitrd we are
using, but i don't know how much space does it waste wrt ours.
Their mkinitrd is completely written in shell and the guy knows about
shell programming. It will be complex to master.

I would really like to rewrite initrd since the current implementation sucks a lot, 
but:
1) there are a some things our mkinitrd does that i do not understand
or have no means to test (i.e. root on a loopback file)
2) before embarking in such a project i would like some consensus on
whether it is needed or not
3) i do not have that much spare time, so i'would need some help

at the moment i was thinking on going on hacking the current mkinitrd.

It was about to patch our linuxrc, but if you wanna do it, you're
welcome :)
I do not particularly like it, but i do not want my previous work for
integrating lvm2 to get lost.

Can you have a look at the mkinitrd/make-initrd patches I've begun ?
i have already integrated them in my tree,
i am now working on mounting tmpfs on /dev (see my other mail)

--
Luca Berra -- [EMAIL PROTECTED]
       Communication Media & Services S.r.l.
/"\
\ /     ASCII RIBBON CAMPAIGN
 X        AGAINST HTML MAIL
/ \



Reply via email to