unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: My experiences with GuixSD
Date: Mon, 11 Sep 2017 00:04:09 +0200	[thread overview]
Message-ID: <871sne43dy.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=RwfZLipRasVFGGX7oRgxCUhLY4W8Fmznh-PGfxeJjcp3sxw@mail.gmail.com> (David Thompson's message of "Sat, 9 Sep 2017 09:26:06 -0400")

Hello!

"Thompson, David" <dthompson2@worcester.edu> skribis:

> On Fri, Sep 8, 2017 at 6:58 PM, Jonathan Brielmaier
> <jonathan.brielmaier@web.de> wrote:

[...]

>> 1. I had a hard time during installation on the "live-system" to figure
>> out how to do the GRUB setup the right way. The error was quite simple:
>> I only have to write "target /dev/sda" instead of "target /dev/sda1".
>>
>> => Beside I'm not very experienced with setting up GRUB, something like
>> "guix lint" for the system config would be nice :)
>
> I agree. Something that would detect that you are trying to install
> GRUB to a partition instead of the disk itself would be nice.

Right, I agree.

At the GHM there were also discussions about detecting other issues at
‘init’ time, such as the use of wrong UUIDs or file system labels.  We
actually already have everything we need to check whether there really
is a file system with the given UUID/label, so it wouldn’t be hard to
add.  Yet, it would make a big difference since that’s apparently a
common mistake.

> Thanks for the feedback.  Sorry that GuixSD doesn't work for you.  I
> would say that the GPU and IceCat things are "won't fix" (these aren't
> GuixSD problems, nor really problems at all, they are facts of life
> for running a system that fully respects your freedom), and the GRUB
> and font thing could definitely be improved with some effort.

Agreed.

I wonder what happened with the font issue.  Jonathan, if you could
reproduce the issue in ‘guix system vm’ (you can do that on your foreign
distro), that would allow us to investigate.

Thanks for your feedback!

Ludo’.

  reply	other threads:[~2017-09-10 22:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08 22:58 My experiences with GuixSD Jonathan Brielmaier
2017-09-09 13:26 ` Thompson, David
2017-09-10 22:04   ` Ludovic Courtès [this message]
2017-09-10 23:33 ` Mark H Weaver
2017-09-11  8:05   ` Jonathan Brielmaier
2017-09-13 18:32     ` Adonay Felipe Nogueira
2017-09-11 16:39 ` Maxim Cournoyer
2017-09-11 19:13   ` Jonathan Brielmaier
2017-09-13  2:13     ` Maxim Cournoyer

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=871sne43dy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dthompson2@worcester.edu \
    --cc=guix-devel@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).