Add the ability to install GuixSD offline + Add the ability to add static IP

  • Open
  • quality assurance status badge
Details
3 participants
  • bo0od
  • Josselin Poiret
  • Giovanni Biscuolo
Owner
unassigned
Submitted by
bo0od
Severity
normal
B
B
bo0od wrote on 25 Aug 2020 20:59
(address . bug-guix@gnu.org)
97bbfb6d-e712-cbc7-a809-9285cd504faf@riseup.net
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!
G
G
Giovanni Biscuolo wrote on 5 Feb 18:33 +0100
Re: guix installation why internet connection required?
(address . guix-devel@gnu.org)
875xz2byuo.fsf@xelera.eu
Hi Maxim and vvt@mail-on.us,

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

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

Toggle quote (12 lines)
> vvt@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.

Toggle quote (2 lines)
> That seems like a tricky problem to solve.

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

Thanks! Gio'

--
Giovanni Biscuolo

Xelera IT Infrastructures
-----BEGIN PGP SIGNATURE-----

iQJABAEBCgAqFiEERcxjuFJYydVfNLI5030Op87MORIFAmXBG88MHGdAeGVsZXJh
LmV1AAoJENN9DqfOzDkSxm8P/R/L+5IRblReY3ccnNegqgCE00N98xs4V5u48T4F
TPhi9sTjA219PoUNrCFge+NfDD32P2Gu7sXVbds208L7TCYU9bcPY3ZqhBVqqgoc
DGmTRBU0LvdxP1YhrWK8qPv09H0FC/0CNnNLZwo0VXMlI5UaF0jQSWbm1XPMARE7
r+4hfUdtE2CyUVfiSEaa7Ju6qhCjVZHbQK1Bi++aiWXm4B7GOJ9hbLBo8EEhXWs5
xnqKtExrUHvCpEkazFMk5HT7Qo/VmkTwoyoURqS0gmFitPGOMZSJ0PL08ohi0KJe
r9G2hFY5NLEjN/eHwvzchrkjWxTXWHvX/PC7GFvLz4vPYlei0F5yeaiufk5MDsrr
xvkhJonINKqN/jbHxUXez/3BgqI4WbleO9Xlphm4srBp/jPzR5VP1bajFAkGVKm4
P20R8KX2clIWdP6MKowre5xGPOAiIfh+bcrttg37nsKNRT66AEPGRsa7btvd0RPa
8vW3K8nJ0CfddGlZTZs/7zSk6ty9kZBEgAv6Cyv/SqR0RQrizjo7pqtn01rO9ArR
/gCAQ1voTALCuxTlyhRFxHwbGzoOmuNK/V3RP1Uqh4j2q9P45YYBATjROpPnSCrL
R5yCzsZlh14mUyGDqkjMjZNI5jRV/zr6zvnZDJrGpXX6Ikzin3j/K2OP4XKkZGBE
yLqv
=h7AU
-----END PGP SIGNATURE-----

J
J
Josselin Poiret wrote on 6 Feb 11:58 +0100
(address . guix-devel@gnu.org)
878r3xn9k4.fsf@jpoiret.xyz
Hi Giovanni,

Giovanni Biscuolo <g@xelera.eu> writes:

Toggle quote (6 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iQHEBAEBCAAuFiEEOSSM2EHGPMM23K8vUF5AuRYXGooFAmXCENsQHGRldkBqcG9p
cmV0Lnh5egAKCRBQXkC5FhcaiqUkC/0Y55n9bgmgKeIY6KrJq2hgSe9YKPfJe5xq
QG/sKi5XHMYBxaVSzBDjjbtTLS6NIHKTgh1cviLzJlO7AO8GxmhaZDmh0wSHiuER
rXbvzb5bJvaAI27Tlnqx0vFE9nyc+AjTHHs1BLzAVl9Y22+50YYiHCjHNFSj/9CF
4gpiuB3Pz92GSQzmgBVlJUBYGWB9k5f1K152WvwubDeFMQrYaxhYBW441arfPIaO
NLC1d90Yqt6lpyZqhOIt+JbzC+qZtContvRI4yNZovRXl47vzKlEMiRZ4+hC2Crf
g/6uDCPvfM+tis/A9kvikAeMUigFIH33HHX+LivmHmOmetxR2zTuONjgitNvXqLf
C68Z019yksIG21zLA70OnXyvJxCpOZbKPk0t/0aW9nRBPtQXHYNG/CfyYfZMe19G
4c4wyop9t3b8eiupQnleX8jJN7/yHDc68kuUvgHnA3oaJbyMOdM4hBjD1imuDwG3
/LXO1si2BSqnazCopBGTNn3C7ZPcl+Y=
=Cvt7
-----END PGP SIGNATURE-----

G
G
Giovanni Biscuolo wrote on 7 Feb 10:47 +0100
bug#43049: Add the ability to install Guix System offline
87wmrga9mw.fsf@xelera.eu
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@jpoiret.xyz> writes:

Toggle quote (12 lines)
> Giovanni Biscuolo <g@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).

Toggle quote (4 lines)
> 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?

Toggle quote (3 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iQJABAEBCgAqFiEERcxjuFJYydVfNLI5030Op87MORIFAmXDUbcMHGdAeGVsZXJh
LmV1AAoJENN9DqfOzDkSBjcQAIWXDRkmjV7Ek0Asu2Bh/yOxh4Yzeoj+y2Vwfs4C
hUJXXY83PuAXiLOIpyNLLzZuM/XF3z27WzPS3O8IrSZ+QsrqT3V8/uRxfLmSVsb7
YwGZoMUTia2BpL+S787NNZUm4nOE1QllCEwM0AETJ3H/aTJil+r/J2vso7+xuIKF
VIc0XTeFuG6sp3Y07tsBA+vr9QR1QEMYGiedHtyhcF9IuABs3AvFnyg7Y61DbUom
fHCrG3R2aSaMnyvcQjNz6kafP8gsbBIkZ+Lq16EWvlIzjhzaJVTu79QuTFjkfLQf
jOmFU3yikENkKy/EgoP7+fy65mkYq8/e4CLypN+hhhNYImERIDBxrsIh/vU1vPwm
6FbGpijKx6bDOImJkzBL0O5zbKsI7wzOvT4Jy3NjER28mI+yg9GTI+BTCkxYMmAm
YWBFHOey8NuTbkEswdzWzopg3IPyjPWc7bCyMlvzGWBXQFbhj/R4ThklYLoaErc4
P62uypUE7TUVOvKhkaEEmoGEI24i0PcFHAgvSzEZ5+Ms55XGx3RMXWYh1nh3yUfE
/7PMGcQtnUblqky0VkD/G/Aw9PWmbixM6jsPiOft7uPXORse27ZqS7dBKugMtLRQ
2AReRIm8omAylSjlfxIbef/F/DdLzPfEF5GEfb9u/MEKIlWb0BMnjS+GDhFxT8ig
pYuH
=oGm5
-----END PGP SIGNATURE-----

J
J
Josselin Poiret wrote on 10 Feb 11:13 +0100
87eddk630t.fsf@jpoiret.xyz
Hi Giovanni,

Giovanni Biscuolo <g@xelera.eu> writes:

Toggle quote (8 lines)
>> 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.

Toggle quote (7 lines)
>> 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
-----BEGIN PGP SIGNATURE-----

iQHEBAEBCAAuFiEEOSSM2EHGPMM23K8vUF5AuRYXGooFAmXHTDIQHGRldkBqcG9p
cmV0Lnh5egAKCRBQXkC5Fhcair2CDACLz7pngrsybqCgK/lhfXEHaiGgv4TiPjql
N6kd1Baqe6/Nj6As/oWdz6NoznJldZbilNifkdyFFNYDa2STetg78F2ArOlYe2EA
NJL1ftFuA1LumrsuAbOFp3fACyXRgpuJfWja96KTItXkszNqQ79/CLwjIPXw4mt7
FpY5PsWSbo0mTyCsRlPrifSw7lh3cotrVMguZRRG9YKABMvxNAebUDxXVJHUS/2V
T84dJeA1niCyX1hRox0TBhgszoYHso8+1AW77frm+GG3i+qGSV3XGU35ejouypK1
Pd736NBT3Uczqb+T7bBx11ggIVnWnEn6/scyz+a2ehQCh/6CObUzfNuYajf1N1/C
az9KAvXjyDvebqooeTy9s1VuGEqONUP9sxYmycCGyj4zgk1fsPm7bpX4plMh+8kc
W9xVTnPRr2yqhhHyqHoteKXeRJMZTuyc1bPiWA+3n9rovrdnkluZvbR4VleviTvu
OWk/nWf9VZ1voOOCEmsNX0Iw2kgL/xE=
=chMS
-----END PGP SIGNATURE-----

?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 43049@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 43049
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch