From: "Emil Kruper" <e.krueper@solcon-systemtechnik.de>
To: buildroot@busybox.net
Subject: [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP
Date: Tue, 2 Sep 2008 08:24:32 +0200 [thread overview]
Message-ID: <MJEBLBOLLBKOACLOGNPBEEIHCBAA.e.krueper@solcon-systemtechnik.de> (raw)
In-Reply-To: <ed4892840809011839w2b021ec5v26159eefa8389e41@mail.gmail.com>
>But I still like to know what you mentioned 'device table'. I want to
>ask, what is and where is the 'device table'? I dont find the
>concepts in buildroot on-line doucments. Thanks.
Have a look at target/generic/device_table.txt and
target/generic/mini_device_table.txt.
You define by the buildroot config which file is used to generate the
targets device table.
Best regards
Emil Kruper
Von: buildroot-bounces at uclibc.org
[mailto:buildroot-bounces at uclibc.org]Im Auftrag von Steven Woody
Gesendet: Dienstag, 2. September 2008 03:40
An: buildroot at uclibc.org
Betreff: Re: [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP
On Tue, Sep 2, 2008 at 8:58 AM, Hamish Moffatt <hamish@cloud.net.au> wrote:
> I couldn't work out where your target_skeleton and device table are
> coming from based on your config. Do you have a device table, and does
> it have those /dev/tty1,2,3,4 devices?
The problem had gone away after I add udev to the packages. I am not
sure whether the absence of udev is really the reason that cause the
previous "can't open /dev/tty?" problems.
But I still like to know what you mentioned 'device table'. I want to
ask, what is and where is the 'device table'? I dont find the
concepts in buildroot on-line doucments. Thanks.
>
> Maybe you could post the output of the build process.
>
>> VFS: Mounted root (cramfs filesystem) readonly.
>> Freeing init memory: 84K
>> mkdir: cannot create directory '/dev/pts': Read-only file system
>> mount: mounting devpts on /dev/pts failed: No such file or directory
>
> Your inittab is obviously trying to make directories in a read-only file
> system which isn't going to work. Not that it's related.
>
Yes, you are right. I did not notice it at first time. But it was
corrected.
You may see in my another post, I now can get the login prompt, and my
problem switchs to "Why I can not login". I hope I can get your help
in that thread.
Best Regards,
narke
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2008-09-02 6:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 1:57 [Buildroot] Still "Can't open /dev/tty1[2,3]", Please HELP Steven Woody
2008-09-02 0:58 ` Hamish Moffatt
2008-09-02 1:39 ` Steven Woody
2008-09-02 6:24 ` Emil Kruper [this message]
2008-09-02 10:27 ` Steven Woody
2008-09-02 11:29 ` Steven Woody
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=MJEBLBOLLBKOACLOGNPBEEIHCBAA.e.krueper@solcon-systemtechnik.de \
--to=e.krueper@solcon-systemtechnik.de \
--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