Linux PARISC architecture development
 help / color / mirror / Atom feed
From: willy@thepuffingroup.com
To: Mike Brancato <funnyguy@digitalsmackdown.net>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] build errors, recipe still not up to date?
Date: Mon, 27 Mar 2000 18:40:25 -0500	[thread overview]
Message-ID: <20000327184025.C31396@thepuffingroup.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10003271704100.18835-100000@morph.net>; from Mike Brancato on Mon, Mar 27, 2000 at 05:07:03PM -0500

On Mon, Mar 27, 2000 at 05:07:03PM -0500, Mike Brancato wrote:
> ok, I guess I forgot to ask my real question, how would I create the
> ramdisk image?

Easy: Download one from puffin.external.hp.com/pub/parisc/ramdisks/
Hard: create a non-sparse file, using dd.  create an ext2 filesystem on it.
Mount it via loopback.  copy whatever you want onto it.

> also, say I want nfs, I have two hpux 11.0 machines I could mount from.
> machine A has a raid array (/users/) attached to it, and machine B mounts
> that same array in /users/ via nfs.  can i have the root for the parisc
> linux in /opt/linuxroot/ or something, and have the parisc machine mount
> that thru nfs?  i'm new to nfs.

Linux NFS Root looks for /tftpboot/<ip-address> by default.  I think
there's a way to change it, but I forget how.

  reply	other threads:[~2000-03-27 22:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-27 21:31 [parisc-linux] build errors, recipe still not up to date? Mike Brancato
2000-03-27 22:07 ` Mike Brancato
2000-03-27 23:40   ` willy [this message]
2000-03-28 15:13     ` dkennedy

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=20000327184025.C31396@thepuffingroup.com \
    --to=willy@thepuffingroup.com \
    --cc=funnyguy@digitalsmackdown.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox