All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bob White" <bwhite@perigee.com>
To: Brian Hawley <bhawley@luminex.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Next steps
Date: Wed, 05 May 2004 08:19:06 -0400	[thread overview]
Message-ID: <4098A37A.9745.238D8273@localhost> (raw)
In-Reply-To: <5.0.2.1.2.20040504164521.05116c10@bhawley.mailhost.luminex.com>


> I'm curious as to the direction people think we should take at this
> point.  Should we be trying to set up
> a root NFS filesystem [ presumably because it is easier to change -- and
> then moving it to an initrd ? ]?
>
> What do we need on the NFS filesystem...
>

Are you using the ELDK?  Have you seen:

http://www.denx.de/twiki/bin/view/DULG/ELDKMountingTargetComponentsViaNF
S

Bob
--
Robert B. White        Perigee, A Division of Sensis Corp
Software Design Engr   316 Commerce Blvd.
TEL: 315.453.7842x29   Liverpool, NY  13088
FAX: 315.453.7917      www.Perigee.com


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-05-05 12:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04 18:03 Simple module, but won't build Richard Danter
2004-05-04 19:10 ` Wolfgang Denk
2004-05-04 19:46   ` Richard Danter
2004-05-04 20:19     ` Wolfgang Denk
2004-05-04 21:15     ` Sam Ravnborg
2004-05-04 21:46       ` Wolfgang Denk
2004-05-04 23:50         ` Next steps Brian Hawley
2004-05-05 12:19           ` Bob White [this message]
2004-05-04 19:38 ` Simple module, but won't build Joshua Lamorie
  -- strict thread matches above, loose matches on Subject: below --
2004-05-06 11:48 Next steps Mark Chambers
2007-05-29 14:55 chris
2007-05-29 16:43 ` Takashi Iwai
2007-05-29 16:52   ` chris
2007-05-29 17:06     ` Takashi Iwai
2007-06-03  3:47       ` Chris Schumann
2007-06-03  6:05         ` Tobin Davis

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=4098A37A.9745.238D8273@localhost \
    --to=bwhite@perigee.com \
    --cc=bhawley@luminex.com \
    --cc=linuxppc-embedded@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.