hi stefan...
mkinitrd ...
or take an existing initrd.gz file...decompress it
into /dev/ram or /dev/loop
than change the kernel to your version, add your libs/commands
and other stuff you want in the initrd to make your system
bootable
and compress that /dev/loop image into your_initrd.gz and add that
as your initrd image in lilo
or so goes the simplified 3-line howto...
either way...you need to make sure you have minixfs and /dev/ram enabled
in your kernel to be able to create initrd files
i created a full system in about 2.5Mb that expands into 8-16Mb of
linux hierachy that runs in memory ( /dev/ramxx )
( put that on a 4Mb flash and you've got a nice firewall ?? )
you can try tomsrtbt too but, its bash is too small as is its libraries
have fun
alvin
On Tue, 8 May 2001, Sean 'Shaleh' Perry wrote:
>
> On 08-May-2001 Stefan Srdic wrote:
> > I've compiled the 2.4.3 kernel on my patato box. I'm interrested in
> > creating my own initial RAM disk (initrd) to speed up my boot process.
> >
> > Does anybody know of any good HOW-TO's on initrd's?
> >
> > Does anybody have some insight to share?
> >
>
> Fairly easy to make, biggest snag is you really have to be root to make them
> properly.
>
> You need a /dev populated with enough entries for the hardware you care
> about.
> Other than that the file system can contain whatever you want/need.
>
> I think I started seeing issues around 5 - 8 mb sized initrd files.
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
