Re: [Linux-mips-kernel] ramdisks

[Paul M. <pm...@mv...>]

On Fri, Jul 06, 2001 at 09:16:13AM -0700, James Simmons wrote:
> > I often use ramdisk when I bring up a board; I see a ramdisk in=20
> > phillips/nino as well. Any reason why we can't generalize this and put=
=20
> > the ramdisk directory and Makefile in arch/mips?  Also, I can create a=
=20
> > few little and big endian ramdisk of different size, with different=20
> > number of utilities and upload them to sourceforge. No reason for havin=
g=20
> > everything build their own ramdisk from scratch...
>=20
> Please place it in CVS. It only makes sense that we have a gerneal
> ramdisk. As for ramdisk we should import a new module into the rtree then.
> Ramdisk seems a logical module name.
>=20
Well, ramdisks should be properly linked into the kernel during compile tim=
e.
Which requires tossing the ramdisk.gz image through a quick and dirty ld sc=
ript
to dump a ramdisk.o that can then be linked straight into the kernel.

It'd be more beneficial to have a stock ramdisk as just the filesystem image
itself so it can be mounted and people can read/write to it, before passing
it through the ld script to generate the ramdisk.o.

It might also be beneficial to maybe write a script that'd automate the
process of building a ramdisk.. ie, fetching source, building, and installi=
ng
necessary components, then setting it all up in a small compressed image.
This would have the benefit of us not having to worry about things like mip=
s32
and mips64 differences, as you could just build for your target.

Though providing a few ready-to-use images is a good idea as well.

> P.S
>=20
>   Is anyone having trouble getting to CVS on SF. I can't sync my tree up.
> I get a=20
>=20
> ssh_exchange_identification: Connection closed by remote host
> cvs [update aborted]: end of file from server (consult above messages if =
any)
>=20
> Any idea was this is about.
>=20
Yeah, SourceForge is sucking as usual. It was working just fine up till abo=
ut
3 this morning which was the last I used it. Upon trying to do anything rig=
ht
now it dies with the same error. Maybe they'll get around to fixing it some=
time
today.

I'll hop on IRC and see if I can find out what's going on with it.

Regards,

--=20
Paul Mundt <pm...@mv...>
MontaVista Software, Inc.