From: Peter Korsgaard <peter@korsgaard.com>
To: Zvi Vered <veredz72@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] 2023.02 : pty_allocate: openpty: No such file or directory
Date: Sat, 25 Mar 2023 11:37:53 +0100 [thread overview]
Message-ID: <87355tp14u.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CABRndgwHc_rpSxXqMdMmGb+3yDy5FSAjk=UDqeA0CvRS13=oiQ@mail.gmail.com> (Zvi Vered's message of "Sat, 25 Mar 2023 05:02:26 +0300")
>>>>> "Zvi" == Zvi Vered <veredz72@gmail.com> writes:
> Hi Peter,
> Did not try rootfs.cpio.uboot created by buildroot yet.
> But I tried to extract rootfs.cpio (created by buildroot)
> /dev contains the following:
> -------------------------------------------------------------------------------------------------
> drwxr-xr-x 4 zvivered zvivered 4096 Mar 12 22:20 .
> drwxr-xr-x 17 zvivered zvivered 4096 Mar 14 20:31 ..
> lrwxrwxrwx 1 zvivered zvivered 15 Mar 12 22:20 fd -> ../proc/self/fd
> lrwxrwxrwx 1 zvivered zvivered 10 Mar 12 22:20 log -> ../tmp/log
> drwxr-xr-x 2 zvivered zvivered 4096 Mar 12 22:20 pts
> drwxr-xr-x 2 zvivered zvivered 4096 Mar 12 22:20 shm
> lrwxrwxrwx 1 zvivered zvivered 17 Mar 12 22:20 stderr ->
> ../proc/self/fd/2
> lrwxrwxrwx 1 zvivered zvivered 17 Mar 12 22:20 stdin -> ../proc/self/fd/0
> lrwxrwxrwx 1 zvivered zvivered 17 Mar 12 22:20 stdout ->
> ../proc/self/fd/1
> ------------------------------------------------------------------------------------------------------
> Can you please explain how rest of /dev files are created during boot
> sequence ?
The default for Buildroot is to use the devtmpfs filesystem in the
kernel to manage /dev, which will automatically create the needed device
nodes (see system configuration -> /dev management). This requires that
the kernel is built with CONFIG_DEVTMPFS=y and CONFIG_DEVTMPFS_MOUNT=y.
> None of the scripts contains mdev.
> I'm using the option:
> BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y
> Is this the best option for automatic creation of /dev files ?
mdev is only needed if you need custom actions for device nodes,
E.G. special symlinks or module loading. Mdev also relies on devtmpfs as
explained above.
If you have enabled BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV, then you
should end up with a /etc/init.d/S10mdev init script to start up mdev.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-03-25 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABRndgw1EVFyDNDcRJ10gOPFfw-gH+7Gqx7P537EiSVr5Wq6Kw@mail.gmail.com>
2023-03-20 8:51 ` [Buildroot] 2023.02 : pty_allocate: openpty: No such file or directory Peter Korsgaard
[not found] ` <CABRndgyqeJXm6XqwYQ_QUaQAGB9EENSq4dc3qLaq6Y3RUhxFUg@mail.gmail.com>
2023-03-21 18:49 ` Peter Korsgaard
[not found] ` <CABRndgwMRVDXzSAoGb5fU9PqM2b6z6we5rH40_NCs7w12LHiDA@mail.gmail.com>
2023-03-21 19:28 ` Peter Korsgaard
[not found] ` <CABRndgz8n37jikSwt3uBkGTM-UBObYcny6xEqhnFkDod9dae1Q@mail.gmail.com>
2023-03-22 21:59 ` Peter Korsgaard
[not found] ` <CABRndgycL0_hvf5dizJDby8VeW_z4xSnTZkXUOsVsXwy==yheA@mail.gmail.com>
2023-03-23 6:56 ` Peter Korsgaard
[not found] ` <CABRndgzV8hKy1pyRCNm+sgi_ePoHgYrS5h_4ca2bZd3E006nPQ@mail.gmail.com>
2023-03-24 6:36 ` Peter Korsgaard
[not found] ` <CABRndgz5EeQhEkqHG0R=T0AvQnzOLHbabO+MjkYH9UHK53pL8g@mail.gmail.com>
[not found] ` <CABRndgwHc_rpSxXqMdMmGb+3yDy5FSAjk=UDqeA0CvRS13=oiQ@mail.gmail.com>
2023-03-25 10:37 ` Peter Korsgaard [this message]
[not found] ` <CABRndgyK0f71HMi15+r8k0nu51sHQrRDx=OA7e5BWR6Oudhnbg@mail.gmail.com>
2023-03-27 19:12 ` 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=87355tp14u.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=veredz72@gmail.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