From: Wolfgang Denk <wd@denx.de>
To: Marius Groeger <mag@sysgo.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Password on ELDK nfs booting
Date: Tue, 27 Aug 2002 16:04:38 +0200 [thread overview]
Message-ID: <20020827140443.4679E1182F@denx.denx.de> (raw)
In-Reply-To: Your message of "Tue, 27 Aug 2002 15:45:11 +0200." <Pine.LNX.4.40.0208271536520.3441-100000@mag.devdep.sysgo.de>
In message <Pine.LNX.4.40.0208271536520.3441-100000@mag.devdep.sysgo.de> you wrote:
>
> > It seems you are using devfs; try running without it. I don't see
> > much advantages of devfs for embedded systems where such a
> > flexibility is usually not needed, on contrary.
>
> Well, I see at least two advantages: a) you don't need to have root
> privileges to assemble your root-filesystem, b) it's the way /dev
> should have been implemented in the first place.
>
> I admid both arguments cover rather aesthetical aspects, so your
> mileage may vary.
The main disadvantage is the increased memory footprint which you
have to pay for a flexibility on the target which is usually not
necessary.
Your (a) is not really an argument; there are several solutions for
this "problem", for example:
genext2fs - ext2 filesystem generator for embedded systems
see http://packages.debian.org/unstable/admin/genext2fs.html
gBootRoot - distribution creation program which may be used by a normal user
see http://gbootroot.sourceforge.net/
(b) is a matter of taste; for embedded systems, I tend to prefer a
fixed, static configuration which does not cost too much of the
resources which may be somewhat limited (espacially ROM and RAM).
Yes, MMV ;-)
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
By the way, ALL software projects are done by iterative prototyping.
Some companies call their prototypes "releases", that's all.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2002-08-27 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.40.0208271536520.3441-100000@mag.devdep.sysgo.de>
2002-08-27 14:04 ` Wolfgang Denk [this message]
2002-08-27 17:38 ` Password on ELDK nfs booting Magnus Damm
2002-08-27 8:17 Sangmoon Kim
2002-08-27 13:24 ` Wolfgang Denk
[not found] ` <009e01c24e61$9bbfd5b0$1a11efcb@industrialDiv.hanasys.co.kr>
[not found] ` <000701c24e73$3227a620$cc00a8c0@ycigrnd.ycig.com>
2002-08-28 10:01 ` Sangmoon Kim
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=20020827140443.4679E1182F@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mag@sysgo.de \
/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).