All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <Helge.Deller@ruhr-uni-bochum.de>
To: parisc-linux@thepuffingroup.com
Subject: Fwd: Re: [parisc-linux] initrd/ramdisk-Status...
Date: Wed, 25 Aug 1999 00:50:34 +0200	[thread overview]
Message-ID: <99082500505601.00280@P100> (raw)



----------  Weitergeleitete Nachricht  ----------
Subject: Re: [parisc-linux] initrd/ramdisk-Status...
Date: Wed, 25 Aug 1999 00:37:55 +0200
From: Helge Deller <Helge.Deller@ruhr-uni-bochum.de>


Hi Matthew,

Am Tue, 24 Aug 1999 schrieben Sie:
> On Tue, Aug 24, 1999 at 09:11:58PM +0200, Helge Deller wrote:
> > I programmed it in such a way, that the bootable image in arch/parisc/boot/
> > holds a directory-structure for up to 63 possible ramdisks, which can be
> > selected during boot via initrd=<number> or initrd=<name>.  
> > The reason for adding support for multiple ramdisks is, that distributions
> > later can add easier support for multiple/different machines in one bootfile.
> 

> Hang on, this doesn't make sense.  There should be no difference between
> the binaries, the only difference should be the kernels.  

Yes, maybe I could change it to select the kernel..... What do you think ?
On the other side, there also could be different binaries for PA1.x / PA2.

> I believe the
> plan is to put UFS-reading code into the bootloader in any case (mkp?)
> which makes all this a temporary hack; as it should be.

Yes of course is UFS-reading the most important part, but how would you do
UFS-reading over Network or from a DAT on a new system without preinstalled fs
or unformatted fs ?

Helge.

> 
> -- 
> Matthew Wilcox <willy@bofh.ai>
> "Windows and MacOS are products, contrived by engineers in the service of
> specific companies. Unix, by contrast, is not so much a product as it is a
> painstakingly compiled oral history of the hacker subculture." - N Stephenson

                 reply	other threads:[~1999-08-24 22:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=99082500505601.00280@P100 \
    --to=helge.deller@ruhr-uni-bochum.de \
    --cc=parisc-linux@thepuffingroup.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.