From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: willy@thepuffingroup.com
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] MAKE initrds FAST
Date: Sun, 13 Feb 2000 16:43:00 +0100 [thread overview]
Message-ID: <20000213164300.A2008@alpha.franken.de> (raw)
In-Reply-To: <20000212225102.D9944@thepuffingroup.com>; from willy@thepuffingroup.com on Sat, Feb 12, 2000 at 10:51:02PM -0500
On Sat, Feb 12, 2000 at 10:51:02PM -0500, willy@thepuffingroup.com wrote:
>
> An interesting project someone might want to take on:
it's sure an interesting project, but there already is a solution for your
problem in the current cvs. It's called NFS root:-)
Right now sash is running on my A180 started from a NFS mounted root.
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
prev parent reply other threads:[~2000-02-13 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-13 3:51 [parisc-linux] MAKE initrds FAST willy
2000-02-13 15:43 ` Thomas Bogendoerfer [this message]
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=20000213164300.A2008@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=parisc-linux@thepuffingroup.com \
--cc=willy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox