From: "Grant Likely" <grant.likely@secretlab.ca>
To: Behan Webster <behanw@websterwood.com>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
linux-embedded@vger.kernel.org
Subject: Re: embedded rootfs utility
Date: Thu, 14 Aug 2008 00:29:42 -0600 [thread overview]
Message-ID: <fa686aa40808132329k49dee24br1d5c83c0d90ea113@mail.gmail.com> (raw)
In-Reply-To: <489C7C69.5060209@websterwood.com>
Hey Behan, a few more comments...
On Fri, Aug 8, 2008 at 11:03 AM, Behan Webster <behanw@websterwood.com> wrote:
> Geert Uytterhoeven wrote:
>> Thanks for this useful tool!
>> I'm used to plain debootstrap, but decided to give your elbs-rootfs a try for
>> creating up a mipsel and a powerpc NFS root file system. It worked fine,
>> except for one minor nit. As an NFS root file system is mounted read-only by
>> default, I had to manually do
>>
>> | mount -n proc /proc -t proc
>> | mount -n -o remount -w /
>>
>> before running finish.sh. Perhaps this can be added to the top of finish.sh?
>>
> Odd. I never had this issue. It has always just worked for me.
I had to do this also, and I had to explicitly "export PATH" to get
the finish script to work. Otherwise I dpkg complains.
What I probably did differently is that I booted the system with
"init=/bin/bash" on the command line instead of letting it just run
init. I needed to do this because if I let it run init, I got
complaints about PAM failures when trying to log in as root. How are
you booting the system on first run?
Also, when booting on something like a 5200 with an uncommon serial
ports name (ttyPSC0), I had to manually add the /dev/ttyPSC0 device
file before it would boot.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-08-14 6:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 2:18 embedded rootfs utility Behan Webster
2008-07-30 14:09 ` Grant Likely
2008-07-30 15:12 ` Marco Stornelli
2008-07-30 15:40 ` Behan Webster
2008-08-06 11:50 ` Geert Uytterhoeven
2008-08-08 17:03 ` Behan Webster
2008-08-14 6:29 ` Grant Likely [this message]
2008-08-14 14:35 ` Behan Webster
2008-08-14 16:35 ` Grant Likely
2008-08-14 19:20 ` Behan Webster
2008-08-14 19:25 ` Grant Likely
2008-08-14 19:32 ` Behan Webster
2008-08-18 11:30 ` Geert Uytterhoeven
2008-08-18 16:00 ` Grant Likely
2008-08-19 1:44 ` Module init for compiled in vs loaded modules Fundu
2008-08-19 4:29 ` Amol Lad
2008-08-19 16:11 ` T Ziomek
2008-08-10 15:14 ` embedded rootfs utility Michelle Konzack
2008-08-24 16:14 ` Behan Webster
2008-09-17 18:13 ` ELBS mindshare Grant Likely
2008-09-17 18:23 ` Robert Schwebel
2008-09-17 19:48 ` Bill Traynor
2008-09-17 20:27 ` Robert Schwebel
2008-09-17 22:09 ` Grant Likely
2008-09-20 19:20 ` Michelle Konzack
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=fa686aa40808132329k49dee24br1d5c83c0d90ea113@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=behanw@websterwood.com \
--cc=linux-embedded@vger.kernel.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).