From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
Henning Schild <henning.schild@siemens.com>,
Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] Install /dev/null in rootfs
Date: Fri, 2 Feb 2018 13:35:29 +0100 [thread overview]
Message-ID: <ccd71a1f-f5b2-56c6-876b-6c2edbfc2430@siemens.com> (raw)
In-Reply-To: <e6c174a1-bc4e-53a0-f512-1764aca1201e@ilbers.de>
On 2018-02-02 13:19, Alexander Smirnov wrote:
> On 01/30/2018 02:44 PM, Henning Schild wrote:
>> Good catch,
>>
>> but that and the other mknods makes we wonder why wo do not just
>> bind-mount /dev. And while we are at it also /sys.
>>
>> /dev /proc and /sys are known to be usually required for a working
>> system. Is there a reason to not just mount all three of them?
>> Otherwise it seems like this patch is just another one in a long series
>> of mknod patches.
>>
>
> I'm also thinking in this way, especially because now we have robust
> mechanism how to unmount everything after build finished/stopped via
> events. So I propose the following plan:
>
> - Update bitbake
> - Merge isar-apt with events
> - Rework /proc,/dev mounting to fix this issue
Sounds like a plan. Let me know where I may help.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-02-02 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 9:31 Jan Kiszka
2018-01-30 11:44 ` Henning Schild
2018-02-02 10:41 ` Jan Kiszka
2018-02-02 12:19 ` Alexander Smirnov
2018-02-02 12:35 ` Jan Kiszka [this message]
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=ccd71a1f-f5b2-56c6-876b-6c2edbfc2430@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/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