From: "Mark Chambers" <markc@mail.com>
To: <bhawley@luminex.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Next steps
Date: Thu, 6 May 2004 07:48:50 -0400 [thread overview]
Message-ID: <003501c43360$1b3e20f0$0301a8c0@chuck2> (raw)
Bob,
I would definitely recommend NFS. As Bob White pointed out, you can get a
directory structure all set up from eldk. The thing about NFS is you have a
PC with visual tools and all to mess with the same files that your embedded
system is accessing. Plus of course you have much more file space. And if
you're new to Linux it's a whole lot easier to get up to speed on the PC.
dhcp & bootp are really different things from NFS, although I think you have
to enable them in the [embedded] kernel for nfsboot to work. But you
probably want to set your board up with a fixed IP and compressed kernel (or
tftp it in) from u-boot, just feeding a command line to the kernel that
tells it the root is nfs something. No sense adding more complexity than
you need!
When it comes to stand-alone booting of an embedded system you can also
consider jffs2 or cramfs instead of initrd. (I can tell you more if you're
interested).
Mark Chambers
WV Computronics
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-05-06 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 11:48 Mark Chambers [this message]
[not found] <Your message of "Tue, 04 May 2004 23:15:08 +0200." <20040504211508.GA2510@mars.ravnborg.org>
2004-05-04 21:46 ` Simple module, but won't build Wolfgang Denk
2004-05-04 23:50 ` Next steps Brian Hawley
2004-05-05 12:19 ` Bob White
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='003501c43360$1b3e20f0$0301a8c0@chuck2' \
--to=markc@mail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).