From: ludo@gnu.org (Ludovic Courtès)
To: Adam Pribyl <pribyl@lowlevel.cz>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: System installation from a USB stick
Date: Mon, 21 Jul 2014 18:09:20 +0200 [thread overview]
Message-ID: <878unm4rtb.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1407210937100.8605@sandbox.cz> (Adam Pribyl's message of "Mon, 21 Jul 2014 09:44:29 +0200 (CEST)")
Adam Pribyl <pribyl@lowlevel.cz> skribis:
> Kernel in dmesg identifies the device like /dev/sdf, doing
> mknod /dev/sdf b 8 80; mknod /dev/sdf1 b 8 81; mount /dev/sdf1 /mnt
> solves the problem. So definitely the drive is at sdf. It looks to me
> like there is some built in limit in udev for number of "scsi" devices
> in this case or something.
Hmm, I have no idea. We’re using a relatively old version of udev,
maybe that will be solved when upgrading.
>>> as there is only 1GB of RAM and it seems the install fetches too much
>>> packages into ramdisk. Why is it not using the target file system
>>> already?
>>
>> Hmm, it’s actually initially populating the local store, on the RAM
>> disk, right. I agree that’s a problem we should address.
>>
>> However, most stuff are already in the store, unless the configuration
>> being built uses many more packages, or use Xorg and related stuff. Is
>> it what’s happening?
>
> The config.scm is as sugessted (just hostname and device modified):
Hmm, OK. I’m surprised that this requires downloading more than 1GiB of
stuff.
I’m looking at a fix, but that’s not as simple as I would have liked.
> Nothing special. I tried to bind mount the /gnu to a target drive, the
> download went OK (cca 1.4G) but then led to different kind of failure.
I’d be interested in knowing about that one as well. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-07-21 16:09 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 20:39 System installation from a USB stick Ludovic Courtès
2014-06-29 22:22 ` Ludovic Courtès
2014-07-01 12:06 ` David Thompson
2014-07-01 21:50 ` David Thompson
2014-07-02 10:22 ` Ludovic Courtès
2014-07-02 11:40 ` David Thompson
2014-07-02 12:23 ` Ludovic Courtès
2014-07-02 10:45 ` Ludovic Courtès
2014-07-03 0:18 ` David Thompson
2014-07-15 14:27 ` Alex Sassmannshausen
2014-07-16 7:14 ` Adam Pribyl
2014-07-16 14:00 ` Ludovic Courtès
2014-07-16 10:02 ` John Darrington
2014-07-16 14:00 ` Ludovic Courtès
2014-07-18 7:04 ` Ludovic Courtès
2014-07-18 11:27 ` Adam Pribyl
2014-07-18 11:28 ` Adam Pribyl
2014-07-18 11:51 ` David Thompson
2014-07-18 18:12 ` Adam Pribyl
2014-07-19 10:52 ` Ludovic Courtès
2014-07-19 12:02 ` Adam Pribyl
2014-07-19 13:15 ` Ludovic Courtès
2014-07-19 13:39 ` Adam Pribyl
2014-07-19 13:47 ` Adam Pribyl
2014-07-19 16:21 ` Ludovic Courtès
2014-07-19 17:14 ` Adam Pribyl
2014-07-20 8:58 ` Ludovic Courtès
2014-07-20 13:48 ` Ludovic Courtès
2014-07-23 15:58 ` Ludovic Courtès
2014-07-24 10:09 ` Adam Pribyl
2014-07-24 11:17 ` Ludovic Courtès
2014-07-24 11:57 ` David Thompson
2014-07-24 14:10 ` Adam Pribyl
2014-07-24 14:26 ` David Thompson
2014-07-24 21:03 ` Ludovic Courtès
2014-07-21 7:44 ` Adam Pribyl
2014-07-21 16:09 ` Ludovic Courtès [this message]
2014-07-21 18:16 ` Adam Pribyl
2014-07-21 18:43 ` Adam Pribyl
2014-07-21 21:30 ` Ludovic Courtès
2014-07-21 19:02 ` Adam Pribyl
2014-07-21 21:40 ` Ludovic Courtès
2014-07-21 21:59 ` Ludovic Courtès
2014-07-22 16:21 ` Ludovic Courtès
2014-07-22 20:26 ` Andreas Enge
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=878unm4rtb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pribyl@lowlevel.cz \
/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.