GNU bug report logs - #43049
Add the ability to install GuixSD offline + Add the ability to add static IP

Previous Next

To reply to this bug, email your comments to 43049 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: bo0od <bo0od <at> riseup.net>
To: bug-guix <at> gnu.org
Subject: Add the ability to install GuixSD offline + Add the ability to add
 static IP
Date: Tue, 25 Aug 2020 18:59:12 +0000

Add the ability to install GuixSD offline + Add the ability to add 
static IP in the installation process.

This is important as users with static IP or using VMs or Offline usage 
cant use this distro.

These features are very common and its almost in every OS available, 
Hope to see it here as well.

ThX!

Message #8 received at 43049 <at> debbugs.gnu.org (full text, mbox):

From: Giovanni Biscuolo <g <at> xelera.eu>
To: 43049 <at> debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 vvt <at> mail-on.us
Cc: guix-devel <at> gnu.org
Subject: Re: guix installation why internet connection required?
Date: Mon, 05 Feb 2024 18:33:03 +0100

[Message part 1 (text/plain, inline)]

Hi Maxim and vvt <at> mail-on.us,

I'm including 43049 <at> debbugs.gnu.org to keep track of the discussion on
this feature request (Add the ability to install GuixSD offline)

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> vvt <at> mail-on.us writes:
>
>> x86 x64 gnu guix system 1.4.0 iso requires internet connection in order to get
>> installed. Same goes for i686 iso.
>>
>> Why is that so? Why is there no
>> iso option for installing off line? Thanks.
>
> There's this ticket about the same: #43049.  If I remember correctly it
> may be related by the Guix binary inside the ISO image being from the
> Guix package of the Guix used to generate it, perhaps.

Sorry I don't understand the problem, could you expand please?

The guix (and daemon) versione are those of the channel used when
creating the install .iso image; booting the 1.40 installer we get a
"guix version" and "guix describe" value of 989a391...

Also, the /gnu/store (755MB on 1.4.0 installer image) have all the
software needed to run the installer; when installing the (same) linux
kernel on the target disk, for example, why the daemon would download
the same substitute when it's already in the store?

Obviously the connection to a substitute server is needed if the user
choose to install some software not already in the store, so the point
should "just" be to have all the software the installer allows the user
to be installed.

> That seems like a tricky problem to solve.

...I feel like I'm missing something important here :-)

Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 43049 <at> debbugs.gnu.org (full text, mbox):

From: Josselin Poiret <dev <at> jpoiret.xyz>
To: Giovanni Biscuolo <g <at> xelera.eu>, 43049 <at> debbugs.gnu.org, Maxim Cournoyer
 <maxim.cournoyer <at> gmail.com>, vvt <at> mail-on.us
Cc: guix-devel <at> gnu.org
Subject: Re: guix installation why internet connection required?
Date: Tue, 06 Feb 2024 11:58:35 +0100

[Message part 1 (text/plain, inline)]

Hi Giovanni,

Giovanni Biscuolo <g <at> xelera.eu> writes:

> Sorry I don't understand the problem, could you expand please?
>
> The guix (and daemon) versione are those of the channel used when
> creating the install .iso image; booting the 1.40 installer we get a
> "guix version" and "guix describe" value of 989a391...

Not exactly, to include Guix inside the installer image, it somehow
needs to refer to itself.  The way it used to be done was by using the
`guix` package, which necessarily is older than the current commit.
However, we also implemented the `current-guix` hack that basically uses
a guix checkout at the current guix version as the source for the guix
package.  In both cases though, we shouldn't see any differences in
other package's derivations…

Best,
-- 
Josselin Poiret

[signature.asc (application/pgp-signature, inline)]

Message #14 received at 43049 <at> debbugs.gnu.org (full text, mbox):

From: Giovanni Biscuolo <g <at> xelera.eu>
To: Josselin Poiret <dev <at> jpoiret.xyz>, 43049 <at> debbugs.gnu.org
Subject: bug#43049: Add the ability to install Guix System offline
Date: Wed, 07 Feb 2024 10:47:35 +0100

[Message part 1 (text/plain, inline)]

Hi Josselin,

first of all, sorry for the confusion: I'm still learning... and I'm
probably still using bad terminilogy from a Guix/Guile developer POV.

Josselin Poiret <dev <at> jpoiret.xyz> writes:

> Giovanni Biscuolo <g <at> xelera.eu> writes:
>
>> Sorry I don't understand the problem, could you expand please?
>>
>> The guix (and daemon) versione are those of the channel used when
>> creating the install .iso image; booting the 1.40 installer we get a
>> "guix version" and "guix describe" value of 989a391...
>
> Not exactly, to include Guix inside the installer image, it somehow
> needs to refer to itself.  The way it used to be done was by using the
> `guix` package, which necessarily is older than the current commit.

OK, in fact I checked starting the guix-1.4 install image in a VM and I
got an older guix in the install system (forgive me for the missing the
details, but this is not important in this context), but the verion
installed on the target was 1.4.0 (so I guess its subsitute was
downloaded from one of the build farms).

> However, we also implemented the `current-guix` hack that basically uses
> a guix checkout at the current guix version as the source for the guix
> package.

So, since some commit, now the guix version used to build the target
system image is the one checked-out by the person/agent running the
install image build script: did I understand it correctly?

> In both cases though, we shouldn't see any differences in other
> package's derivations…

Does this mean you consider possible to pre-populate the /gnu/store
install system (the one started using the install image) with a substet
of substitutes possibly needed in the target system?

I'm wondering if it's possible to create a custom build image (info
"(guix) Building the Installation Image") to do something like this.

Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[signature.asc (application/pgp-signature, inline)]

Message #17 received at 43049 <at> debbugs.gnu.org (full text, mbox):

From: Josselin Poiret <dev <at> jpoiret.xyz>
To: Giovanni Biscuolo <g <at> xelera.eu>, 43049 <at> debbugs.gnu.org
Subject: Re: bug#43049: Add the ability to install Guix System offline
Date: Sat, 10 Feb 2024 11:13:06 +0100

[Message part 1 (text/plain, inline)]

Hi Giovanni,

Giovanni Biscuolo <g <at> xelera.eu> writes:

>> However, we also implemented the `current-guix` hack that basically uses
>> a guix checkout at the current guix version as the source for the guix
>> package.
>
> So, since some commit, now the guix version used to build the target
> system image is the one checked-out by the person/agent running the
> install image build script: did I understand it correctly?

Yes.

>> In both cases though, we shouldn't see any differences in other
>> package's derivations…
>
> Does this mean you consider possible to pre-populate the /gnu/store
> install system (the one started using the install image) with a substet
> of substitutes possibly needed in the target system?

I think it's already meant to be the case, see the comment in
gnu/system/install.scm about keeping a reference to the bare bones os's
closure.  It wouldn't contain all graphical stuff either, but I think
there's also some trouble with grafts that forces users to still
download substitutes.

Best,
-- 
Josselin Poiret

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.