Hello Erich,

>> That's what I meant ;-)
>> If that option is removed, the initrd can also made smaller, because
>> the code needed to backup (mkfs.minix) can be removed.
>
> I believe this would be the best solution. I have no problem custom
> tailoring my initrd, but for the average user it might be handy to have a
> tool to configure initrd like modules.lrp.
>
I also think this is the best solution.
I don't think the average user would custom tailoring its initrd, why
would that be necessary? There isn't anything that I know of in the initrd
which could or should be changed in the initrd by an average user.
If anyone wants to change the initrd it can easely be done on a linux
machine with loopmounting it.

> Who would be the one to decide on this?
>
If no one objects :)

>
> Another question....
>
>
> How does one to go about building the buildenv for a specific release,
> e.g. does CVS have release tags? For example, if I wanted to have a
> buildenv which matches _exactly_ the one for 2.4.1 how to proceed?
>
There currently aren't any release tags unfortuanatly. But everything in
CVS is exactly 2.4.1, so if you build buildenv you would have version
2.4.1.
The Bering-uClibc team will make a snapshot of the current tree and put
the sources in a tarball in the File release area.

> thanks
>
> Erich
>
Eric




-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to