unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: Richard <r_j_humphreys@yahoo.co.uk>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: New Install
Date: Thu, 17 Sep 2015 17:08:23 +0200	[thread overview]
Message-ID: <87a8slrsm0.fsf@igalia.com> (raw)
In-Reply-To: <2018551345.1298753.1442491565410.JavaMail.yahoo@mail.yahoo.com> (Richard's message of "Thu, 17 Sep 2015 12:06:05 +0000 (UTC)")

Hi!

On Thu 17 Sep 2015 14:06, Richard <r_j_humphreys@yahoo.co.uk> writes:

> - It is feasible/straightforward to install guixsd to a spare partition
> without affecting the existing OS (slackware) on my machine? (My other
> machine is burdened with Windows and dual-booting that is a challenge
> which might follow later...)?

It is, if you want to share /home but not not /etc, /var, and so on.
So if your slackware install is on sda1, your home is sda2, and you
install GuixSD to sda3 -- that can work.  Don't install over sda1
though.

> - If so, is it feasible to install guixsd while keeping my existing
> extlinux-based boot system or am I obliged to move to grub?

In practice you'd be obliged to move to grub.

Are you running Guix already?  If not, I would suggest trying Guix as a
user first.  As a user you get most of what GuixSD offers, without
perturbing your system.  The only downside is when you expect to
e.g. see package foo from Guix but you had it installed via slackware
and there's something wrong with your Guix setup so you aren't picking
up the Guix copy but you don't know why -- this sort of thing is only
possible to ultimately clear up if you have nothing in /usr.  But it can
be worked around and when everything is set up right you won't have this
problem.

Andy

  reply	other threads:[~2015-09-17 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 12:06 New Install Richard
2015-09-17 15:08 ` Andy Wingo [this message]
2015-09-18  9:24   ` Richard
2015-09-18 19:25     ` Ludovic Courtès
2015-09-19 10:26       ` Alex Kost

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=87a8slrsm0.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=guix-devel@gnu.org \
    --cc=r_j_humphreys@yahoo.co.uk \
    /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).