Re: loading a compressed ramdisk image

2001-07-24 Thread Andrew Dixon
Michael Schmitz wrote: > > Read the source, then. Ethan explained it - rdev patches the bootloader > piggybacked on the compressed kernel image. I would assume this strategy > is way too primitive to do what you want (the existing piggybacks, not the > 'patch the hell out of the bootloader'). > >

Re: loading a compressed ramdisk image

2001-07-24 Thread Michael Schmitz
> > Your call. You can hardcode the command line and ramdisk path in the > > loader as well. The loader needs to know where to find the ramdisk anyway, > > right? (The kernel cannot load the ramdisk from some other storage BTW.) > > > > Do you mean that the kernel and root image need to live on the

Re: loading a compressed ramdisk image

2001-07-23 Thread Ethan Benson
On Mon, Jul 23, 2001 at 05:35:00PM +0200, Michael Schmitz wrote: > > That's the bootloader's job on PPC. With a sane OF implementation, your > boot loader would be yaboot and something like initrd= ramdisk> and append="root=/dev/ram" should do. you don't need append="root=/dev/ram" yaboot does th

Re: loading a compressed ramdisk image

2001-07-23 Thread Ethan Benson
On Mon, Jul 23, 2001 at 01:07:48PM -0400, Andrew Dixon wrote: > > Is this functionality missing from the PPC or is it just convention to > let the bootloader handle this? the bootloader handles this on i386 too, your just missing the fact that zImage and bzImage kernels are really a 16 bit i386

Re: loading a compressed ramdisk image

2001-07-23 Thread Ethan Benson
On Mon, Jul 23, 2001 at 03:21:03PM -0400, Andrew Dixon wrote: > I've only read the man pages for rdev and I'm still not clear on how it > works. Does it mask a word in the kernel that has all of the > information on where to locate the root image? If that's all it does I > don't see why it would

Re: loading a compressed ramdisk image

2001-07-23 Thread Andrew Dixon
Michael Schmitz wrote: > > > > That's the bootloader's job on PPC. With a sane OF implementation, your > > > boot loader would be yaboot and something like initrd= > > ramdisk> and append="root=/dev/ram" should do. > > > > > Is this functionality missing from the PPC or is it just convention to >

Re: loading a compressed ramdisk image

2001-07-23 Thread Michael Schmitz
> > That's the bootloader's job on PPC. With a sane OF implementation, your > > boot loader would be yaboot and something like initrd= > ramdisk> and append="root=/dev/ram" should do. > > > Is this functionality missing from the PPC or is it just convention to > let the bootloader handle this? Con

Re: loading a compressed ramdisk image

2001-07-23 Thread Andrew Dixon
Michael Schmitz wrote: > > > I'm trying to set up a system that will load a compressed root image > > from the disk (eventually flash) into a ramdisk and run the root > > filesystem from ram. I was wondering if there is an "rdev" type utility > > for the PPC that lets the kernel know that it want

Re: loading a compressed ramdisk image

2001-07-23 Thread Michael Schmitz
> I'm trying to set up a system that will load a compressed root image > from the disk (eventually flash) into a ramdisk and run the root > filesystem from ram. I was wondering if there is an "rdev" type utility > for the PPC that lets the kernel know that it wants to load a compressed > image int