Hunter Jozwiak writes:
> Howdy,
>
> Here is a project I am interested in getting into Guix in some fashion,
> copied from my email I sent to help-guix a while back. Any mentorship
> and/or help pointers would be appreciated, and I appologize for the double
> posting.
>
> -- Forwarded
Hi,
The locations for disk-related packages evolved inconsistently over
time and now seem to be in need of adjustment. Here are some examples:
sdparm (SCSI): disk.scm
hdparm (ATA): linux.scm --> disk.scm
sg3-utils (SCSI): scsi.scm
lsscsi (SCSI): linux.scm --> scsi.scm
I'd be hap
Hi Ludo and Chris,
Ludovic Courtès writes:
> Hello!
>
> Probably the main issue is that childhurds now fail to boot:
>
> https://issues.guix.gnu.org/62307#23
>
> We can still build “new” i586-gnu binaries on an “old” childhurd, of
> course, but to me that’s doing that is less of a priority.
[
On Sun, May 14, 2023 at 05:55:20PM +0200, Josselin Poiret wrote:
> Hi Ludo and Chris,
>
> Ludovic Courtès writes:
>
> > Hello!
> >
> > Probably the main issue is that childhurds now fail to boot:
> >
> > https://issues.guix.gnu.org/62307#23
> >
> > We can still build “new” i586-gnu binaries on
Hi everyone,
Upon personal reflection, a declarative operating system like Guix probably
ought to use only predictable interface names.
More details about this proposal, including the text below, are
available in Bug#63508.
While shorter names like 'eno1' offer an indisputable convenience and be
