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: Mon, 27 Mar 2023 21:12:18 +0200 [thread overview]
Message-ID: <87o7oenh4d.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CABRndgyK0f71HMi15+r8k0nu51sHQrRDx=OA7e5BWR6Oudhnbg@mail.gmail.com> (Zvi Vered's message of "Mon, 27 Mar 2023 20:19:17 +0300")
>>>>> "Zvi" == Zvi Vered <veredz72@gmail.com> writes:
> Hi Peter,
> I tried the file *rootfs.cpio.uboot* created by buildroot.
> *It works ! *
> dropbear is not killed and there are not /dev/null messages.
Ok, good!
> I want to add a few files to this rootfs and then pack it again to
> *rootfs.cpio.uboot*
> So I extracted rootfs.cpio with:
> cpio -idv < /tmp/rootfs.cpio
> *** Added few files to /root ****
> ls | cpio -ov > /tmp/rootfs.cpio
> gzip -f /tmp/rootfs.cpio
> ./u-boot/u-boot-xlnx/tools/mkimage -A arm64 -T ramdisk -C gzip -n 'zynqmp'
> -d /tmp/rootfs.cpio.gz /tmp/rootfs.cpio.gz.uboot
> Is this the right sequence ?
> I tried the new rootfs.cpio.gz.uboot. Boot hangs.
You need to do such things as root (or run under fakeroot) to ensure
correct permissions and device nodes, but the real way to make
modifications of the rootfs is explained in the Buildroot manual:
https://buildroot.org/downloads/manual/manual.html#rootfs-custom
> Thank you very much for your help,
You are welcome.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-03-27 19:12 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
[not found] ` <CABRndgyK0f71HMi15+r8k0nu51sHQrRDx=OA7e5BWR6Oudhnbg@mail.gmail.com>
2023-03-27 19:12 ` Peter Korsgaard [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=87o7oenh4d.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