From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] bash: /dev/fd/62: No such file or directory
Date: Fri, 30 Mar 2018 13:11:47 +0200 [thread overview]
Message-ID: <877ept7r7w.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <d624af0cde7298851332a2fc009f173562d99d98.camel@embedded.rocks> ("Jörg Krause"'s message of "Thu, 29 Mar 2018 21:46:27 +0200")
>>>>> "J?rg" == J?rg Krause <joerg.krause@embedded.rocks> writes:
Hi,
>> Keep in mind that we still support a static /dev, so we should also add
>> them to system/device_table_dev.txt and redirect errors to /dev/null so
>> you don't get a bunch of warnings about these symlinks when booting with
>> a static /dev.
> I am trying to get this working. I managed to add the entries to
> inittab for busybox and sysvinit
Great!
> but I am unsure how to add those symlinks to the static
> /dev. makedevs does not support symbolic links.
Heh, you are right. We can either:
- Add a BASH_ROOTFS_PRE_CMD_HOOKS hook in bash.mk if static /dev is used
to create these symlinks
- Extend the makedevs code to also support symlinks
- Completely ignore this issue for static /dev
The first option is probably the easiest/nicest.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-03-30 11:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 22:55 [Buildroot] bash: /dev/fd/62: No such file or directory Jörg Krause
2018-03-16 14:19 ` Peter Korsgaard
2018-03-21 15:25 ` Jörg Krause
2018-03-29 19:46 ` Jörg Krause
2018-03-30 11:11 ` Peter Korsgaard [this message]
2018-03-30 11:51 ` Jörg Krause
2018-03-30 12:41 ` Peter Korsgaard
2018-04-01 9:45 ` Jörg Krause
2018-04-01 10:27 ` Peter Korsgaard
2018-04-04 18:12 ` Jörg Krause
2018-04-04 18:58 ` Peter Korsgaard
2018-04-04 20:22 ` Jörg Krause
2018-04-04 20:23 ` Peter Korsgaard
2018-04-04 20:39 ` Jörg Krause
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=877ept7r7w.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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