On 5/4/19 12:10 AM, Marius Bakke wrote:
> rendaw <7e9wc56emja...@s.rendaw.me> writes:
>
>> On 5/3/19 7:17 AM, Marius Bakke wrote:
>>> It would be great to have UEFI support in the record,
>>> mainly for system tests, but I doubt that is what rendaw is after
On 5/3/19 7:17 AM, Marius Bakke wrote:
> It would be great to have UEFI support in the record,
> mainly for system tests, but I doubt that is what rendaw is after :-)
Yeah, ideally I'd like secure boot from the flashed media but failing
that I'd at least like to be moving cl
On 4/29/19 7:14 PM, Ludovic Courtès wrote:
> Hello,
>
> rendaw <7e9wc56emja...@s.rendaw.me> skribis:
>
>> From e7dcba4a76d624470d05172390dde8151fdb4750 Mon Sep 17 00:00:00 2001
>> From: rendaw <>
>> Date: Mon, 29 Apr 2019 01:00:17 +0900
>> Subject:
arate reference with
more flags listed somewhere).
>From e7dcba4a76d624470d05172390dde8151fdb4750 Mon Sep 17 00:00:00 2001
From: rendaw <>
Date: Mon, 29 Apr 2019 01:00:17 +0900
Subject: [PATCH] [bug #35475] [PATCH] Add filesystem flag NOATIME
Add a no-atime flag to the file-system flags paramet
Package: guix
Version: 0.16.0
Severity: wishlist
This is useful for mounting drives with limited write lifetime such as
cheap ssds, and there have been some historical reports of noatime
causing COW-linked files on btrfs to split.
Package: guix
Version: 0.16.0
The documentation states that dependencies between filesystems will
determine the mount order, but actually needed-at-boot filesystems are
mounted in the order they appear in the config file.
Currently this is something that can trip people up and has an
inspecific e
Package: guix
Version: 0.16.0
I specified a needed-at-boot bind mount from "/x/y" to "/y" but this
failed with the error:
ERROR: In procedure stat:
In procedure stat: No such file or directory: "/x/y"
At boot "/x" is actually mounted at "/root/x" so the bind mount path
should be "/root/x/y" -- m
Package: guix
Version: 0.16.0
Severity: wishlist
In a disk-image the ssh host keys are generated anew every time the
system boots. This is a significant security issue - the unknown host
warnings will cause notification blindness and users won't recognize if
the host is legitimately compromised.
Package: guix
Version: 0.16.0
Severity: wishlist
Currently nginx, ddclient, and perhaps other packages need private files
(ssl private keys, etc). These files would be only root readable on the
target system.
With disk-image it's not possible to use them because the only way to
get files or othe
Package: guix
Version: 0.16.0
Severity: wishlist
As per 35359 I'd like to use produce a uefi bootloader capable disk-image.
On 4/25/19 5:44 PM, Ludovic Courtès wrote:
> Hi rendaw,
>
> rendaw <7e9wc56emja...@s.rendaw.me> skribis:
>
>> Bug 2: So is it appears disk-image won't build with an EFI bootloader.
>> I'm guessing that qemu is run with a bios boot image here, which i
On 4/23/19 10:13 PM, Ludovic Courtès wrote:
> Hi rendaw,
>
> rendaw <7e9wc56emja...@s.rendaw.me> skribis:
>
>> I get logs like:
>>
>> /gnu/store/6zkimxsfyn0gdc7p4ikxlrhilpnpblsi-grub-efi-2.02/sbin/grub-install:
>> error:
>> /gnu/store/6zkimxsfyn0gdc7
On 4/23/19 1:07 AM, GNU bug Tracking System wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested par
On 4/23/19 1:10 AM, Ricardo Wurmus wrote:
> rendaw <7e9wc56emja...@s.rendaw.me> writes:
>
>> Thanks! I just did `guix pull` and forced an image rebuild (by changing
>> host-name)
> Changing the host name is not needed. After getting the new Guix most
> of the pack
Package: guix
Version: 0.16.0
This might be 2 bugs.
I ran `guix pull` a few hours ago.
I have a minimal system configuration:
```
(use-modules (gnu))
(operating-system
(host-name "min1")
(timezone "UTC")
(locale "en_US.utf8")
(bootloader (bootloader-configuration
(bootloa
On 4/22/19 9:06 PM, Ricardo Wurmus wrote:
> rendaw <7e9wc56emja...@s.rendaw.me> writes:
>
>> $ guix --version
>> guix (GNU Guix) 0.16.0
>> Copyright (C) 2018 the Guix authors
>> License GPLv3+: GNU GPL version 3 or later
>> <http://gnu.org/license
On 4/22/19 5:35 AM, Ludovic Courtès wrote:
> Hi,
>
> rendaw <7e9wc56emja...@s.rendaw.me> skribis:
>
>> $ guix system docker-image testsystem2.scm --on-error=backtrace
>> successfully built
>> /gnu/store/l3psqh73xjb5h11y1hwrlfvl1yr920x4-guixsd-d
Package: guix
Version: 0.16.0
I took the sample system configuration at the top of
https://www.gnu.org/software/guix/manual/en/html_node/Using-the-Configuration-System.html#Using-the-Configuration-System
and ran:
```
$ guix system docker-image testsystem2.scm --on-error=backtrace
successfully bui
On 4/16/19 1:07 AM, Ludovic Courtès wrote:
> Hello,
>
> rendaw <7e9wc56emja...@s.rendaw.me> skribis:
>
>> CWD is `.../server`
>>
>> The directory `.../server/temp` exists
>>
>> The specified -r is: `temp/image-2019-4-14`
>>
>> I would ex
On 4/15/19 9:57 PM, Ludovic Courtès wrote:
> Hi,
>
> rendaw <7e9wc56emja...@s.rendaw.me> skribis:
>
>> guix system disk-image .../server/tmpudkxw7og.scm -r
>> temp/image-2019-4-14 --on-error=backtrace
>>
>> in the `server` directory which has a su
On 4/15/19 9:57 PM, Ludovic Courtès wrote:
> Hi,
>
> rendaw <7e9wc56emja...@s.rendaw.me> skribis:
>
>> guix system disk-image .../server/tmpudkxw7og.scm -r
>> temp/image-2019-4-14 --on-error=backtrace
>>
>> in the `server` directory which has a su
Package: guix
Version: 0.16.0
Running:
guix system disk-image .../server/tmpudkxw7og.scm -r
temp/image-2019-4-14 --on-error=backtrace
in the `server` directory which has a subdirectory `temp` fails with
this error:
successfully built
/gnu/store/xqcy47al19dn2bfbnmz7vmjm812ikgqx-disk-image.drv
gu
Package: guix
Version: 0.16.0
As a workaround for the "guix system init -e" issue I'm creating a
temporary file with the -e expression and passing it to guix like:
```
$ guix system init /tmp/tmpmf8u61uc.scm temp/mount
...
guix system: error: failed to load '/tmp/tmpmf8u61uc.scm': No such file
or
ific in this regard - will the
filesystem created by "guix system init" be a bootable system? Like
disk-image but on a mounted empty filesystem? The other way I could
interpret the docs for that command are that "init" copies all the files
required to build the system (source f
24 matches
Mail list logo
