From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] bash: /dev/fd/62: No such file or directory
Date: Wed, 04 Apr 2018 20:58:41 +0200 [thread overview]
Message-ID: <87d0zeol26.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <3dd2f190fef3d71e1b2f1f5ec6f4323e8ee8c745.camel@embedded.rocks> ("Jörg Krause"'s message of "Wed, 04 Apr 2018 20:12:08 +0200")
>>>>> "J?rg" == J?rg Krause <joerg.krause@embedded.rocks> writes:
Hi,
>> > 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.
> It turned out that nothing needs to be done for static /dev as the
> symlinks are created now by the init system.
But how can that work? static /dev normally means readonly /dev.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-04-04 18:58 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
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 [this message]
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=87d0zeol26.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