From: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Failing NFS root mount
Date: Wed, 23 Apr 2008 10:06:00 +0200 [thread overview]
Message-ID: <06f001c8a518$e16c04d0$ad289e86@LPSC0173W> (raw)
In-Reply-To: 20080422133843.GA5733@real.realitydiluted.com
I'm going to test the others' suggestions right now, but I have a little
issue with this:
> /dev/log
It's the only device that was missing from my list.
I found several examples where the following line is added to
device_table.txt:
/dev/log s 666 0 0 - - - - -
But upon making the filesystem, I get the following error on that line:
$ make
[...]
table='target/generic/device_table.txt'
makedevs: line 59: Unsupported file type s
And indeed I don't see 's' (socket) listed among f/d/c/b/p
IIRC, /dev/log should be created by syslogd (but not other loggers) upon its
start.
I am indeed using syslog and I get a proper log in /tmp/messages. From the
busybox config:
CONFIG_FEATURE_SYSLOG=y
CONFIG_LOGNAME=y
CONFIG_SETLOGCONS=y
CONFIG_FEATURE_INIT_SYSLOG=y
CONFIG_FEATURE_SU_SYSLOG=y
CONFIG_SYSLOGD=y
CONFIG_FEATURE_ROTATE_LOGFILE=y
CONFIG_FEATURE_REMOTE_LOG=y
CONFIG_FEATURE_SYSLOGD_DUP=y
# CONFIG_FEATURE_IPC_SYSLOG is not set
CONFIG_FEATURE_IPC_SYSLOG_BUFFER_SIZE=
# CONFIG_LOGREAD is not set
# CONFIG_FEATURE_LOGREAD_REDUCED_LOCKING is not set
CONFIG_KLOGD=y
CONFIG_LOGGER=y
# CONFIG_SVLOGD is not set
So is /dev/log important or not ?
--
Guillaume Dargaud
http://www.gdargaud.net/Antarctica/
next prev parent reply other threads:[~2008-04-23 8:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 12:34 [Buildroot] Failing NFS root mount Guillaume Dargaud
2008-04-22 13:38 ` sjhill at realitydiluted.com
2008-04-23 8:06 ` Guillaume Dargaud [this message]
2008-04-22 13:40 ` Peter Korsgaard
2008-04-22 14:07 ` Hamish Moffatt
2008-04-23 8:56 ` Guillaume Dargaud
2008-04-23 9:18 ` Peter Korsgaard
2008-04-23 9:47 ` [Buildroot] Failing NFS root mount (SOLVED) Guillaume Dargaud
2008-04-23 10:10 ` 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='06f001c8a518$e16c04d0$ad289e86@LPSC0173W' \
--to=dargaud@lpsc.in2p3.fr \
--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