From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12586] avahi failure
Date: Mon, 18 May 2020 07:34:22 +0000 [thread overview]
Message-ID: <bug-12586-163-c2lixdnBaq@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12586-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12586
Thomas Petazzoni <thomas.petazzoni@bootlin.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
Hello Sam. You can write your own filesystem image logic in Buildroot, so that
you can re-use everything Buildroot does under "fakeroot", such as creating
users, adjusting permissions and ownerships, etc. I believe you can even add
your own filesystem format in your separate BR2_EXTERNAL tree, if you're using
that.
In any case, there's nothing to fix in Buildroot here: we explicitly state that
the contents of output/target is not the final root filesystem, and this cannot
be changed as Buildroot does not run as root.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2020-05-18 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 5:08 [Buildroot] [Bug 12586] New: avahi failure bugzilla at busybox.net
2020-02-28 5:09 ` [Buildroot] [Bug 12586] " bugzilla at busybox.net
2020-02-28 12:36 ` bugzilla at busybox.net
2020-03-02 4:37 ` bugzilla at busybox.net
2020-05-18 7:34 ` bugzilla at busybox.net [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=bug-12586-163-c2lixdnBaq@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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