From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] debugging inittab
Date: Thu, 29 Aug 2013 07:17:57 +0200 [thread overview]
Message-ID: <521ED985.9050705@mind.be> (raw)
In-Reply-To: <2DD0B9C711CDFC45A3A266C78966CE7F451F8F81@G4W3291.americas.hpqcorp.net>
On 08/28/13 00:38, Jenkins, Lee (ISS Houston) wrote:
> -----Original Message-----
> From: Arnout Vandecappelle [mailto:arnout at mind.be]
> Sent: Thursday, August 22, 2013 6:36 PM
> To: Jenkins, Lee (ISS Houston)
> Cc: buildroot at busybox.net
> Subject: Re: [Buildroot] debugging inittab
> Importance: Low
>
>> On 22/08/13 22:11, Jenkins, Lee (ISS Houston) wrote:
>>> Hello. I am debugging a boot problem for a few hours. I'm clearly in
>>> over my head and I could use some insight.
>>>
>>> For debugging purposes, I am booting from a kernel and rootfs on an
>>> nfs share of my dev machine. The console is ttyS0.
>>
>> The nfs-share is an extracted output/images/rootfs.tar, right? You're not using the target directory?
>>
>
> That was the problem. Thanks!
Right. Maybe we should just rename target/ to
THIS_IS_NOT_YOUR_ROOT_FILESYSTEM instead of just creating the file. The
latter is obviously not enough.
What was the reason we didn't do that in the first place?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-08-29 5:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 20:11 [Buildroot] debugging inittab Jenkins, Lee
2013-08-22 23:36 ` Arnout Vandecappelle
2013-08-27 22:38 ` Jenkins, Lee
2013-08-29 5:17 ` Arnout Vandecappelle [this message]
2013-08-29 7:29 ` Peter Korsgaard
2013-08-29 7:39 ` Arnout Vandecappelle
2013-08-29 8:45 ` Peter Korsgaard
2013-08-29 8:31 ` Thomas Petazzoni
2013-08-29 10:14 ` Peter Korsgaard
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=521ED985.9050705@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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