Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hebbar <gururajakr@sanyo.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] Improper device nodes created inside project_build_arm/uclibc/root/dev/
Date: Sun, 20 Apr 2008 23:14:31 -0700 (PDT)	[thread overview]
Message-ID: <16803332.post@talk.nabble.com> (raw)


Hi,

I am trying to build arm9 toolchain using recent buildroot toolchain.
everything works fine except the device nodes inside my
project_build_arm/uclibc/root/dev/ directory.

oot at guru_vlinux:/opt/buildroot_plain# ls -la
project_build_arm/uclibc/root/dev/
total 0
drwxr-xr-x  3 root root 192 Apr 17 23:23 .
drwxr-xr-x 16 root root 408 Apr 17 22:44 ..
-rw-rw-rw-  1 root root   0 Apr 18 00:36 console
lrwxrwxrwx  1 root root  10 Apr 17 22:14 log -> ../tmp/log
-rw-rw-rw-  1 root root   0 Apr 18 00:36 null
drwxr-xr-x  2 root root  48 Apr 17 22:14 pts
-rw-rw-rw-  1 root root   0 Apr 18 00:36 ttyAMA0
-rw-rw-rw-  1 root root   0 Apr 18 00:36 zero

While it should be 

root at guru_vlinux:/opt/buildroot_plain# ls -la /dev/console /dev/null
/dev/zero
crw------- 1 root root 5, 1 Apr 18 12:10 /dev/console
crw-rw-rw- 1 root root 1, 3 Apr 18 08:08 /dev/null
crw-rw-rw- 1 root root 1, 5 Apr 18 08:08 /dev/zero

I have to manualy delete them and cp the basic one from my system root/dev.
Once i copy from root device nodes, i am able to load the root using nfs
mount or by compressing the root directory.

Why are the device nodes not properly cretaed. I have logged into console
with root privileges.

Thanks in advance

Regards
Gururaja
-- 
View this message in context: http://www.nabble.com/Improper-device-nodes-created-inside-project_build_arm-uclibc-root-dev--tp16803332p16803332.html
Sent from the BuildRoot mailing list archive at Nabble.com.

             reply	other threads:[~2008-04-21  6:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21  6:14 Hebbar [this message]
2008-04-21 14:07 ` [Buildroot] Improper device nodes created inside project_build_arm/uclibc/root/dev/ Hamish Moffatt
2008-04-22  0:12   ` Hebbar
2008-04-22  0:50     ` Hamish Moffatt
2008-04-22  1:58       ` [Buildroot] Improper device nodes created insideproject_build_arm/uclibc/root/dev/ Gururaja Hebbar K R
2008-04-22  1:56         ` Hamish Moffatt
2008-04-22  7:54           ` Peter Korsgaard
2008-04-22  7:14       ` [Buildroot] Improper device nodes created inside project_build_arm/uclibc/root/dev/ Peter Korsgaard
2008-04-22  9:59         ` Hamish Moffatt
2008-04-22 16:40           ` [Buildroot] Improper device nodes createdinside project_build_arm/uclibc/root/dev/ Ulf Samuelsson
2008-04-22 18:24             ` Peter Korsgaard
2008-04-22 18:47               ` Ulf Samuelsson
2008-04-22 20:52                 ` Peter Korsgaard
2008-04-23  0:45                   ` Thiago A. Corrêa
2008-04-23 17:03                     ` [Buildroot] Improper device nodes createdinsideproject_build_arm/uclibc/root/dev/ Ulf Samuelsson
2008-04-23 18:09                       ` Peter Korsgaard
2008-04-23 18:33                         ` Ulf Samuelsson
2008-04-24  9:31                           ` Peter Korsgaard
2008-04-25 15:00                             ` Thiago A. Corrêa
2008-04-22  7:12     ` [Buildroot] Improper device nodes created inside project_build_arm/uclibc/root/dev/ Peter Korsgaard
2008-04-23  5:45       ` Hebbar

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=16803332.post@talk.nabble.com \
    --to=gururajakr@sanyo.co.in \
    --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