From: Bryan Ferris <saffsnail@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 33999@debbugs.gnu.org
Subject: bug#33999: CP437: Invalid Argument on init
Date: Thu, 10 Jan 2019 07:15:10 -0800 [thread overview]
Message-ID: <CABkR=SUnpHJ+-brA5k40t3gvcOf2DuU8+UKEseTiee25Vuy1rg@mail.gmail.com> (raw)
In-Reply-To: <CABkR=SUyCV7d6sR1Zyy4Aj4Cp5raS_Tn-Akji3k0fQPeneErFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]
I've linked to two videos here, one of the boot (the screen with the GNU
logo and "100% freedom" on it) and one of the init (where Shepherd reports
errors, I think it's dmesg?).
Boot:
https://drive.google.com/file/d/1YMbCI3BvznhMI_eYYTxMvxJC2SKlNqSJ/view?usp=sharing
Init:
https://drive.google.com/file/d/1CZov16Xrpy9D8DMN9eHeANjR7UHh2WpL/view?usp=sharing
On Thu, Jan 10, 2019 at 6:31 AM Bryan Ferris <saffsnail@gmail.com> wrote:
> I've attached two videos here, one of the boot (the screen with the GNU
> logo and "100% freedom" on it) and one of the init (where Shepherd reports
> errors, I think it's dmesg?).
>
> On Wed, Jan 9, 2019, 13:18 Bryan Ferris <saffsnail@gmail.com wrote:
>
>> I assume that it is related because the error is printed once for each
>> failed service but I have no better reason than that. I can send a video of
>> my boot tonight... It might be a little blurry though, all I have is my
>> phone camera. If there's a way for me to start a screen recorder during
>> init or capture the logs that it prints as a text file I'd be happy to do
>> that, I just don't know of a way to.
>>
>>
>>
>> On Jan 9, 2019 11:08, "Danny Milosavljevic" <dannym@scratchpost.org>
>> wrote:
>>
>> Hi,
>>
>> apparently the message is printed by fsck.fat and is harmless (although
>> we should
>> still fix it). Are you sure that the services fail because of it?
>>
>> > (file-systems (cons*
>> > (file-system
>> > (device (file-system-label "ESP"))
>> > (mount-point "/boot/efi")
>> > (type "fat")
>>
>> Try adding (check? #f) here for testing purposes.
>>
>> > )
>>
>>
>>
[-- Attachment #2: Type: text/html, Size: 3071 bytes --]
next prev parent reply other threads:[~2019-01-10 15:16 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 [this message]
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
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=SUnpHJ+-brA5k40t3gvcOf2DuU8+UKEseTiee25Vuy1rg@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).