Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12586] avahi failure
Date: Mon, 02 Mar 2020 04:37:10 +0000	[thread overview]
Message-ID: <bug-12586-163-u1N6CqAq5x@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12586-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=12586

--- Comment #3 from Sam Petrocelli <sam.petrocelli@gmail.com> ---
Thanks for the reply. Yeah, I guess that's where the problem is. Unfortunately,
developers that came before have configured the system such that we have custom
python scripts that copy the files out of target and staging and we create a
file system outside of buildroot ourselves. (We also have a similar thing going
on for the kernel as well). I am in the process of getting everything undated
and standardized. What we want right now is a way that we can essentially copy
all of these files for the rootfs out. I see that if we make a tar fs, all the
passwd systemd, avahi, etc is all in there, but we want these files without
having to deal with untar. Do you have any suggestions for this? Thank you.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-03-02  4:37 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 [this message]
2020-05-18  7:34 ` bugzilla at busybox.net

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-u1N6CqAq5x@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