From: Timo Wilken <timo@twilken.net>
To: "mhrunnels@yahoo.com" <mhrunnels@yahoo.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Guix Pull - Device or Resource Busy
Date: Sun, 8 Jan 2023 23:18:05 +0100 [thread overview]
Message-ID: <20230108221805.4pwl3zw5smhcdzng@lap.twilken.net> (raw)
In-Reply-To: <1827448990.5046781.1673202056151@mail.yahoo.com>
Hi MH,
I don't have the solution to your problem unfortunately, but here are
a few hopefully-useful pointers:
On Sun, Jan 08, 2023 at 06:20:56PM +0000, mhrunnels@yahoo.com via wrote:
> I have also run the "guix pull" command with the following options
> to ascertain the error.
>
> # guix pull --verbosity=3 --debug=5
>
> However, I have been unable to capture the standard screen output
> for analysis. All attempts to direct the output using pipes "|" or
> redirection ">" have failed.
Guix logs to stderr, not stdout. Use one of the following two
incantations to capture it:
$ guix pull ... 2>guix.log # redirect stderr to guix.log
$ guix pull ... 2>&1 | cmd # pipe stdout and stderr to "cmd"
> PS - My "config.scm" file used to install and run the system is
> reproduced below.
In your config.scm, you seem to have a file-system record with an
empty mountpoint:
(file-system
(mount-point "")
(device (uuid "BDAA-FF93" 'fat16))
(type "vfat"))
Maybe that's causing problems?
Hope that helps,
Timo
prev parent reply other threads:[~2023-01-08 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1827448990.5046781.1673202056151.ref@mail.yahoo.com>
2023-01-08 18:20 ` Guix Pull - Device or Resource Busy mhrunnels@yahoo.com via
2023-01-08 22:09 ` (
2023-01-08 22:18 ` Timo Wilken [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
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=20230108221805.4pwl3zw5smhcdzng@lap.twilken.net \
--to=timo@twilken.net \
--cc=help-guix@gnu.org \
--cc=mhrunnels@yahoo.com \
/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).