From: Divan Santana <divan@santanas.co.za>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Installing GuixSD on an external USB hard drive
Date: Thu, 19 Apr 2018 11:26:37 +0200 [thread overview]
Message-ID: <87muxzh7hu.fsf@santanas.co.za> (raw)
In-Reply-To: <CAEKzfHmD6S-ggzK5k2dp_Kjk-HLekjDYnVPDS2RC+fzHMFRczQ@mail.gmail.com>
Chris Marusich <cmmarusich@gmail.com> writes:
> Hi Divan!
>
> Thank you for taking the time to write to us about the problem. These
> kinds of but reports are very helpful!
Your welcome. Thanks for the great reply.
> On Tue, Apr 17, 2018, 06:43 Divan Santana <divan@santanas.co.za> wrote:
>
>> OK, I think this is a bug.
>
>
> It could be. Please report it to bug-guix@gnu.org. If you have an
> operating system configuration file that reproduces the problem
> consistently, please share it in your report. In particular, if you can
> reproduce the problem using "guix system vm", it will make things much
> easier for us to debug. The manual describes how to use that command:
>
> https://www.gnu.org/software/guix/manual/html_node/Invoking-guix-system.html
I need to spend time on this and try reproduce it and report it
properly. For the moment I've worked around it.
>
> The way I worked around it was to:
>
>
>> 1) remount /gnu/store rw
>>
>> 2)
>>
>> cd
>>
>> /gnu/store/n9ym4yl7s55pm57rnc5whjlzjgvxas32-linux-libre-4.16.2/lib/modules/4.16.2-gnu/kernel/drivers/usb/storage/
>> cp usb_storage.ko usb-storage.ko
>>
>
> That's good to know, but you should not modify files in the store or mount
> it rw.
Absolutely. I just did it to try test the theory. I've undone the hack
and will see if things break later. But this is a test system.
> It can lead to unpredictable behavior because doing so may violate
> certain invariants. When hacking around on a throw-away system to
> investigate an issue like this, don't this might be useful, but on systems
> you care about, essentially the only way you should interact with the store
> is via the public Guix scheme APIs and the Guix command line tools, since
> they will ensure that the store's invariants are never violated.
> Again, thank you for the report! I hope everything is smooth sailing from
> this point on.
Thanks again.
Doubt it will be smooth sailing lol. But I'm learning and guix is
awesome and hope to continue learning and cotribute more in time.
--
Divan
next prev parent reply other threads:[~2018-04-19 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 18:04 Installing GuixSD on an external USB hard drive Divan Santana
2018-04-16 19:09 ` Pierre Neidhardt
2018-04-17 7:54 ` Divan Santana
2018-04-17 11:34 ` Pierre Neidhardt
2018-04-17 13:04 ` Divan Santana
2018-04-17 16:26 ` Chris Marusich
2018-04-19 9:26 ` Divan Santana [this message]
2018-04-17 13:32 ` myglc2
2018-04-19 9:23 ` Divan Santana
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=87muxzh7hu.fsf@santanas.co.za \
--to=divan@santanas.co.za \
--cc=cmmarusich@gmail.com \
--cc=help-guix@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.
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).