all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: znavko@disroot.org
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Cannot install Guix 1.0.1 on Asus K50C
Date: Sun, 16 Jun 2019 13:16:57 +0200	[thread overview]
Message-ID: <20190616111657.nlla3tehksv5w2jl@pelzflorian.localdomain> (raw)
In-Reply-To: <f7470a028368abf5cf44773575e7ee0d@disroot.org>

On Sun, Jun 16, 2019 at 10:29:44AM +0000, znavko@disroot.org wrote:
> I've used in config the name of device as /dev/sda everywhere, and Guix runs ok. Think, manual should have notices about it for those not want to use label of device. 

Using /dev/sda is perhaps not reliable when you have plugged in other
hard drives or storage media.  The manual should not recommend
/dev/sda in my opinion.



> Also if I do not use separate partition for bios grub, guix says that it is not allowed (but on my other laptop i have only one partition for root and grub).

Please file bugs with information what was needed to make Guix work,
if you have the time. :)  It is helpful and important work.  I believe
not all developers have time to read help-guix (and am not
knowledgeable enough and do not see myself as a Guix developer).  In
particular, it is a bug if the graphical installer does not work for
you.

I wish you a good time with Guix.

Regards,
Florian

      reply	other threads:[~2019-06-16 11:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-15 16:45 Cannot install Guix 1.0.1 on Asus K50C znavko
2019-06-15 18:22 ` znavko
2019-06-15 18:54   ` pelzflorian (Florian Pelz)
2019-06-16  8:17   ` znavko
2019-06-16  8:39     ` pelzflorian (Florian Pelz)
2019-06-16 10:29     ` znavko
2019-06-16 11:16       ` pelzflorian (Florian Pelz) [this message]

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

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

  git send-email \
    --in-reply-to=20190616111657.nlla3tehksv5w2jl@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=help-guix@gnu.org \
    --cc=znavko@disroot.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.