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 8831] image generation fails on host ZFS due to "no free space"
Date: Tue, 29 Mar 2016 21:23:34 +0000	[thread overview]
Message-ID: <bug-8831-163-R2X2dCj914@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8831-163@https.bugs.busybox.net/>

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

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at buildroot.uclibc |yann.morin.1998 at free.fr
                   |.org                        |
                 CC|                            |yann.morin.1998 at free.fr

--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Maybe it's time we switch to use e2fsprogs from their 'next' branch,
rather than our canned script?

The upstream e2fsprogs now has the ability to fill-in the generated
filesystem from the content of an existing directory (with the new -d
option).

FWIW, Debian is now using a snapshot of 2016-03-15 in Stretch (testing)
and they have a single patch on top of that. I'd rather trust Debian.

Regards,
Yann E. MORIN.

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

  reply	other threads:[~2016-03-29 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 21:01 [Buildroot] [Bug 8831] New: image generation fails on host ZFS due to "no free space" bugzilla at busybox.net
2016-03-29 21:23 ` bugzilla at busybox.net [this message]
2016-10-24 21:56 ` [Buildroot] [Bug 8831] " bugzilla at busybox.net
2017-03-25 13:44 ` 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-8831-163-R2X2dCj914@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