From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] ramdisk.bin?
Date: Mon, 6 Sep 1999 11:24:46 +0200 [thread overview]
Message-ID: <19990906112446.A25362@mencheca.ch.genedata.com> (raw)
In-Reply-To: <37D35413.6E032AE1@uswest.net>; from Ryan Bradetich on Sun, Sep 05, 1999 at 11:41:39PM -0600
On Sun, Sep 05, 1999 at 11:41:39PM -0600, Ryan Bradetich wrote:
> Hmm...
>
> Ok, I got a stupid question :)
>
> Where do I generate/find the ramdisk.bin that is a dependency for
> ramdisk.c?
You can either generate one yourself using the loop device under Linux
or just take the one we all use from
ftp://puffin.external.hp.com/pub/parisc/binaries/ramdisks/
--
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
prev parent reply other threads:[~1999-09-06 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-06 5:41 [parisc-linux] ramdisk.bin? Ryan Bradetich
1999-09-06 9:24 ` Matthew Wilcox [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=19990906112446.A25362@mencheca.ch.genedata.com \
--to=matthew.wilcox@genedata.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=rbradetich@uswest.net \
/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