My guix installation appears to be working now. Thanks for all your help!
I'm not sure if the underlying issue causing the encoding error has been
identified; if there's anything else you need from me let me know. It
appears that this error is not causing any bad behavior, however.
On Wed, Jan
I am indeed using flash storage, specifically a Samsung Evo 850 (it's a few
years old and has had many distress installed and reinstalled on it; now
that I'm thinking about it, it wouldn't surprise me at all if this was the
underlying issue). I'm trying your recommendation of reinstalling and
Hello,
Danny Milosavljevic skribis:
> On Mon, 21 Jan 2019 10:50:41 +0100
> Ludovic Courtès wrote:
[...]
>> But where are those
>> files you’re talking about? Surely there’s no /gnu/store on the VFAT
>> EFI partition, right?
>
> Oh, these empty files are on the root partition Bryan provided
Hi Ludo,
Hi Bryan,
On Mon, 21 Jan 2019 10:50:41 +0100
Ludovic Courtès wrote:
> It’s not surprising to .lock files to be empty.
I agree. But I didn't filter them out because it would be confusing.
> But where are those
> files you’re talking about? Surely there’s no /gnu/store on the VFAT
>
Hi,
Danny Milosavljevic skribis:
> /etc/pam.d/login is a symlink to
> /gnu/store/7pbmghp19xml75pv9ss5dik6mcc8n5xy-login,
> which has 0 Byte.
>
> There are lots and lots of files with 0 Byte--these:
>
>
I've created a qemu disk image with Bryan's original files:
https://drive.google.com/open?id=1_HcBJ3_qimbY6C4_gppOG57-UeGzuyJO
To use it invoke:
$ qemu-system-x86_64 -hda a.img -kernel
mnt/gnu/store/b27wjlld5105cq56vvxfywk88x5hxsba-system/kernel/bzImage -initrd
../initrd -serial stdio -m 900
On Sun, 20 Jan 2019 23:48:40 +0100
Danny Milosavljevic wrote:
> On Sun, 20 Jan 2019 06:34:46 -0800
> Bryan Ferris wrote:
>
> > Root files:
> > https://drive.google.com/open?id=1XL_iQCze4SkOSd_GnOzNTfkNMiRJHDLG
> > ESP: https://drive.google.com/open?id=1o7sQD9rhzRwTKsyvqrZpScMQrgi5XCDT
> >
> >
On Sun, 20 Jan 2019 06:34:46 -0800
Bryan Ferris wrote:
> 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
>
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
Hi,
Danny Milosavljevic skribis:
> On Wed, 16 Jan 2019 12:00:15 +0100
> Ludovic Courtès wrote:
>
>> Glibc has the ability to bring in statically-linked gconv modules, so we
>> could in theory build a custom glibc for the statically-linked
>> ‘fsck.fat’, but that doesn’t sound great.
>>
>>
Hi Ludo,
On Wed, 16 Jan 2019 12:00:15 +0100
Ludovic Courtès wrote:
> Glibc has the ability to bring in statically-linked gconv modules, so we
> could in theory build a custom glibc for the statically-linked
> ‘fsck.fat’, but that doesn’t sound great.
>
> Thoughts?
Reading the dosfstools
Hi Bryan,
On Fri, 18 Jan 2019 11:00:14 -0800
Bryan Ferris wrote:
> I think I know why d-bus is failing to start. The error when it tries to is
> as follows:
>
> "Failed to start message bus: Error in file /etc/dbus-1/system-local.conf,
> line 1, column 0: no element found"
>
> The first
I think I know why d-bus is failing to start. The error when it tries to is
as follows:
"Failed to start message bus: Error in file /etc/dbus-1/system-local.conf,
line 1, column 0: no element found"
The first possibility came up when I searched /gnu/store for
system-local.conf. There is only one
Hey Danny,
Sorry for the delay in response. I saw no behavior change until I added the
(mount? #f) line. This fixed a number of services, but d-bus fails to
start. I encounter further issues including X Server failing to start and
the inability to log in (when I type in a valid username it
Hi Danny,
Danny Milosavljevic skribis:
> apparently the message is printed by fsck.fat and is harmless (although we
> should
> still fix it).
The statically-linked ‘fsck.fat’ doesn’t have access to gconv module,
which is why ‘iconv_open’ would fail.
Glibc has the ability to bring in
Oh right, forgot about the check line. I'll try that tonight. However, I
don't think I can run your test program unless that fixes the issue as I
never get a shell.
Also, I don't think this matters, but I'll be running `guix system init`
from the installer rather than reconfigure due to the lack
Also, if you want, please try the following program on the booted guix system:
#include
#include
#include
#include
static iconv_t iconv_init_codepage(int codepage)
{
iconv_t result;
char codepage_name[16];
snprintf(codepage_name, sizeof(codepage_name), "CP%d", codepage);
Hi,
On Thu, 10 Jan 2019 07:15:10 -0800
Bryan Ferris wrote:
> 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,
Thanks! I've viewed those.
>I think it's dmesg?).
It depends. On
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:
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
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"))
>
Hello,
I've installed guix to my desktop. `guix system install` ran successfully
and the system is able to boot. However, a large number of services fail to
start with the error "CP437: Invalid argument". There are 3 groups of
information listed below: a partial list of services which fail
22 matches
Mail list logo
