unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: "\"Ludovic Courtès\"" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Testing the installer
Date: Mon, 20 Jan 2020 12:49:21 -0500	[thread overview]
Message-ID: <16fc412c13d.cc4aee5930534.5104860751595817425@zoho.com> (raw)
In-Reply-To: <16f9c1c4117.d406b2d220796.277966992299583807@zoho.com>

 ---- On Sun, 12 Jan 2020 18:34:54 -0500 sirgazil <sirgazil@zoho.com> wrote ----
 >  ---- On Sun, 12 Jan 2020 17:13:54 -0500 Ludovic Courtès <ludo@gnu.org> wrote ----
 >  > Hello Guix!
 >  > 
 >  > One of the lessons from the 1.0.0 screw-up was that we should test the
 >  > graphical installer itself:
 > 
 > And, if possible, not test only using virtual machines, but real ones, because I remember my installation in a virtual machine went smoothly, but installing in my real machine was rough (network devices not detected, installer generated config.scm with truncated UUID, unknown error when trying to restart installation).
 > 

By the way, in my old notes about my installation of the Guix System 1.0.0, I have something about a problem related to the order in which the installer checks for network availability. 

My computer had another OS installed at that time. If I recall correctly, I started the Guix System installation process, told the installer to use the whole disk for installation, and only after formatting the disk, the installer told me there was a connection problem, and I couldn't install the system. So I couldn't boot to the old OS at that point. Fortunately, people on #guix helped me solve the network problem (related to bug) and I could install the Guix System.

So, if this is still the case, I think the installer should check for network connection before attempting to do any destructive operation.

---
https://sirgazil.bitbucket.io/

  reply	other threads:[~2020-01-20 17:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-12 22:13 Testing the installer Ludovic Courtès
2020-01-12 23:34 ` sirgazil
2020-01-20 17:49   ` sirgazil [this message]
2020-01-14  8:02 ` Mathieu Othacehe
2020-01-22 22:27   ` Ludovic Courtès
2020-01-23  9:41     ` Mathieu Othacehe
2020-01-23 11:21       ` Gábor Boskovits
2020-01-23 23:07         ` Bengt Richter
2020-01-24  7:48           ` Gábor Boskovits
2020-01-24  9:23         ` Ludovic Courtès
2020-01-23 14:54       ` Ludovic Courtès
2020-01-20 11:47 ` Jonathan Brielmaier
  -- strict thread matches above, loose matches on Subject: below --
2018-06-13  3:57 swedebugia
2018-06-13 19:47 ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16fc412c13d.cc4aee5930534.5104860751595817425@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).