All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hoover <david.hoover@epfl.ch>
To: linuxppc-dev@lists.linuxppc.org
Subject: dhcp, linuxppc and remote /usr
Date: Mon, 21 Jun 1999 17:42:23 +0200	[thread overview]
Message-ID: <376E5D5F.EBEC6CD3@epfl.ch> (raw)


Hi,

It is generally desirable for a machine to be able to do it's basic
startup sequence even if /usr is not mounted yet (if for example it's
on a remote NFS server).  This is not the case with LinuxPPC when using
DHCP to get network parameters.

Briefly, DHCP booting does not work if /usr is mounted on a remote
server.  This is simply because /etc/rc.d/rc3.d/S10network uses the
'xargs' command (which is in /usr/bin instead of /bin).

(if you are wondering why somebody would do this, the idea is to
create a generic ZIP disk that can be used on any machine to start
up a full LinuxPPC session.  DHCP is used so that it's not
necessary to hardwire net addresses onto the boot disk).

I believe that either xargs should not be used in startup scripts, or
xargs should be in /bin by default.  After making this change, bootup
proceeds perfectly).

Just thought somebody might like to know this.

I'm not on this list--so please reply to me personally if you have
a comment.

Dave.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

             reply	other threads:[~1999-06-21 15:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-21 15:42 David Hoover [this message]
1999-06-21 17:08 ` dhcp, linuxppc and remote /usr David De Ridder

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=376E5D5F.EBEC6CD3@epfl.ch \
    --to=david.hoover@epfl.ch \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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.