From: "Koch, Alexander" <akoch@initse.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] rootfs: /dev/null creation fails with 'Operation not permitted'
Date: Thu, 30 Sep 2021 07:59:45 +0000 [thread overview]
Message-ID: <46ed7a4d-89b9-480a-1d57-bd37d54769b4@initse.com> (raw)
Hi #PTXdist,
I'm currently facing the issue that all my PTXdist builds fail in
'rootfs.make' during the creation of the /dev/null device node:
--------------------------------------( ... )--
install directory:
dir=/dev
owner=0
group=0
permissions=0755
install device node:
owner=0
group=0
permissions=0666
type=c
major=1
minor=3
name=/dev/null
mknod: /mnt/work/ptxdist/platform-pm3/packages/rootfs.tmp/dev/null:
Operation not permitted
Error: install_node failed!
xpkg_finish: failed.
make: *** [/usr/lib/ptxdist-2020.01.0/rules/rootfs.make:93:
/mnt/work/ptxdist/platform-pm3/state/rootfs.targetinstall] Error 1
------------------------------------------------
As you can see I'm using ptxdist-2020.01.0 for this but I've taken a
look at the current release code base and can't see any substantial
changes to the device node creation part in `install_node()`. So I doubt
it's an issue of that particular version.
I've also checked I'm not using any fancy mount options for the
filesystem I'm building on (btrfs) and I do not use SELinux/AppArmor or
any other restriction framework.
Builds used to work fine for years, so I'm running out of clues what
could be causing this issue.
Does anybody have an idea what I could check?
Thanks in advance,
Alex
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2021-09-30 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 7:59 Koch, Alexander [this message]
2021-09-30 10:44 ` Michael Olbrich
2021-09-30 12:00 ` Koch, Alexander
2021-09-30 13:10 ` Koch, Alexander
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=46ed7a4d-89b9-480a-1d57-bd37d54769b4@initse.com \
--to=akoch@initse.com \
--cc=ptxdist@pengutronix.de \
/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