From: Bryan Ferris <saffsnail@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>, 33999@debbugs.gnu.org
Subject: bug#33999: CP437: Invalid Argument on init
Date: Sun, 20 Jan 2019 06:34:46 -0800 [thread overview]
Message-ID: <CABkR=SX3YZ5WSFFf+t5YCWdixo-yK=iUvT7ytAZcx3bV5aH+jw@mail.gmail.com> (raw)
In-Reply-To: <20190120031949.2bb81997@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
Root files:
https://drive.google.com/open?id=1XL_iQCze4SkOSd_GnOzNTfkNMiRJHDLG
ESP: https://drive.google.com/open?id=1o7sQD9rhzRwTKsyvqrZpScMQrgi5XCDT
I tried reconfiguring from chroot but ran into some issues. I bind-mounted
/dev, /sys, /proc, and /var from the installer to the target, which got
past some errors. The one I couldn't get past was being unable to find the
glibc derivation in the store, though the file was present. Not sure what
went wrong there.
On Sat, Jan 19, 2019 at 6:19 PM Danny Milosavljevic <dannym@scratchpost.org>
wrote:
> Hi Bryan,
>
> On Sat, 19 Jan 2019 07:15:43 -0800
> Bryan Ferris <saffsnail@gmail.com> wrote:
>
> > Well, the partition is > 400GiB which makes it difficult to `dd`. I'm not
> > sure if I have a drive big enough to store it, even if I pipe it directly
> > into a compression algorithm. Would compressing the files themselves be
> > sufficient? I'm going to hold off on reconfiguring until I hear back from
> > you on this because if that fixes it then it might also destroy evidence
> of
> > the bug.
>
> Yes, I would suggest you do (in a chroot, probably):
>
> * compress all the files from the root partition (i.e. something like tar
> zcvf)
> * dd only the uefi partition
>
> ... and then send those two files to us.
>
[-- Attachment #2: Type: text/html, Size: 2009 bytes --]
next prev parent reply other threads:[~2019-01-20 14:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 19:34 bug#33999: CP437: Invalid Argument on init Bryan Ferris
2019-01-09 19:08 ` Danny Milosavljevic
2019-01-09 21:18 ` Bryan Ferris
[not found] ` <CABkR=SUyCV7d6sR1Zyy4Aj4Cp5raS_Tn-Akji3k0fQPeneErFg@mail.gmail.com>
2019-01-10 15:15 ` Bryan Ferris
2019-01-10 17:59 ` Danny Milosavljevic
2019-01-10 20:37 ` Bryan Ferris
2019-01-16 11:00 ` Ludovic Courtès
2019-01-18 22:59 ` Danny Milosavljevic
2019-01-19 10:19 ` Ludovic Courtès
2019-01-21 0:40 ` Danny Milosavljevic
2019-01-21 8:41 ` Danny Milosavljevic
2019-01-21 9:50 ` Ludovic Courtès
2019-01-21 10:16 ` Danny Milosavljevic
2019-01-21 10:51 ` Ludovic Courtès
2019-01-23 15:42 ` Bryan Ferris
2019-01-26 17:32 ` Bryan Ferris
2019-01-10 18:21 ` Danny Milosavljevic
2019-01-16 15:43 ` Bryan Ferris
2019-01-18 19:00 ` Bryan Ferris
2019-01-18 22:48 ` Danny Milosavljevic
[not found] ` <CABkR=SWtHUA+G50fR_QiU-tGU6TatQ7wnKWW+n6LdFexSYJZRA@mail.gmail.com>
[not found] ` <20190120031949.2bb81997@scratchpost.org>
2019-01-20 14:34 ` Bryan Ferris [this message]
2019-01-20 22:48 ` Danny Milosavljevic
2019-01-20 22:49 ` Danny Milosavljevic
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABkR=SX3YZ5WSFFf+t5YCWdixo-yK=iUvT7ytAZcx3bV5aH+jw@mail.gmail.com' \
--to=saffsnail@gmail.com \
--cc=33999@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).