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 10141] Squashfs extended attribute failures
Date: Mon, 05 Feb 2018 17:35:15 +0000	[thread overview]
Message-ID: <bug-10141-163-P4OJAJCSUe@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10141-163@https.bugs.busybox.net/>

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

--- Comment #11 from Bob <cmg427@hotmail.com> ---
(In reply to Yann E. MORIN from comment #10)

I'm using fakeroot version 1.20.2 on Ubuntu 16.04.

I'm not sure if this helps, but this is what the code looks like.

    squashfuse first.sqsh first_mount
    squashfuse second.sqsh second_mount

    # overlay multiple mounts
    unionfs-fuse -o cow,hide_meta_files first_mount=RW:second_mount=RO
final_mount

    # set capabilities
    fakeroot setcap cap_linux_immutable final_mount/usr/blah.txt

    # create final squash
    fakeroot mksquashfs final_mount final.sqsh -no-progress -noappend -comp xz

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

  parent reply	other threads:[~2018-02-05 17:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 15:01 [Buildroot] [Bug 10141] New: Squashfs extended attribute failures bugzilla at busybox.net
2017-08-02 15:06 ` [Buildroot] [Bug 10141] " bugzilla at busybox.net
2017-08-02 20:56 ` bugzilla at busybox.net
2017-08-02 21:26 ` bugzilla at busybox.net
2017-08-03 13:54 ` bugzilla at busybox.net
2017-08-08 20:33 ` bugzilla at busybox.net
2017-08-13 21:35 ` bugzilla at busybox.net
2017-08-13 21:50 ` bugzilla at busybox.net
2017-08-15 16:19 ` bugzilla at busybox.net
2018-02-02 21:39 ` bugzilla at busybox.net
2018-02-03 13:56 ` bugzilla at busybox.net
2018-02-05 17:35 ` bugzilla at busybox.net [this message]
2018-02-05 18:10 ` 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-10141-163-P4OJAJCSUe@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