From: "Grant Likely" <grant.likely@secretlab.ca>
To: mojtaba <kernelppc@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: File system problem
Date: Thu, 3 Jan 2008 10:27:24 -0700 [thread overview]
Message-ID: <fa686aa40801030927l4dc95a63s9670d6f6deb3a8c5@mail.gmail.com> (raw)
In-Reply-To: <004801c84e21$59312760$0b937620$@com>
On 1/3/08, mojtaba <kernelppc@gmail.com> wrote:
> Hi,
> Thank you very much for your answers.
>
> But I have both console and null in /dev.
>
> -rw-rw-rw- 1 mojtaba mojtaba 0 2007-12-26 15:50 console
> -rw-rw-rw- 1 mojtaba mojtaba 0 2007-12-26 15:50 null
>
> They have been created by buildroot. Do I need to create them manually?
> Actually the size of both of them is 0 and both are empty files. Is that a
> problem?
They should look like this:
crw------- 1 root root 5, 1 2008-01-03 07:43 /dev/console
crw-rw-rw- 1 root root 1, 3 2007-10-08 18:39 /dev/null
They are not regular files. They are device files created with the
'mknod' command.
Instead of a size, these files have 2 number; the device major and
minor numbers. /dev/console uses major 5, minor 1. /dev/null is
major 1 minor 3.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2008-01-03 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 3:32 File system problem Jean-Samuel Chenard
2008-01-03 15:57 ` mojtaba
2008-01-03 17:27 ` Grant Likely [this message]
2008-01-03 17:00 ` mojtaba
2008-01-03 17:33 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2008-01-03 23:57 Jean-Samuel Chenard
2008-01-04 11:57 ` mojtaba
2008-01-02 18:50 mojtaba
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=fa686aa40801030927l4dc95a63s9670d6f6deb3a8c5@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=kernelppc@gmail.com \
--cc=linuxppc-embedded@ozlabs.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).