From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Nathan Dehnel <ncdehnel@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: /dev/bcache/by-uuid directory empty
Date: Fri, 18 Dec 2020 15:13:37 +0100 [thread overview]
Message-ID: <87mtyburqm.fsf@nckx> (raw)
In-Reply-To: <CAEEhgEte1dp08p6bzGGCmQCvKjx91jYp_CMLSqpEM5Gqk3m6sg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
Nathan,
You may well be the first to (try to) use bcache on Guix System.
Nathan Dehnel 写道:
> The manual https://www.kernel.org/doc/Documentation/bcache.txt
> states
> that udev is necessary, and it is enabled:
It says:
--8<---------------cut here---------------start------------->8---
bcache-tools now ships udev rules, and bcache devices are known to
the kernel immediately.
--8<---------------cut here---------------end--------------->8---
which is a bit more than that. Guix doesn't ship bcache-tools
(yet); are you using your own package? If so, please consider
sharing :-)
You'd have to add it to the RULES field of your system's
UDEV-CONFIGURATION to make the system's udev ‘see’ the rules.
Simply installing it or adding it to your system packages isn't
enough.
The kernel docs continue:
--8<---------------cut here---------------start------------->8---
Without udev, you can manually register devices like this::
echo /dev/sdb > /sys/fs/bcache/register
echo /dev/sdc > /sys/fs/bcache/register
Registering the backing device makes the bcache device show up in
/dev; you can now format it and use it as normal.
--8<---------------cut here---------------end--------------->8---
Have you tried this?
Good luck,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-12-18 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 23:30 /dev/bcache/by-uuid directory empty Nathan Dehnel
2020-12-18 14:13 ` Tobias Geerinckx-Rice [this message]
2020-12-18 16:31 ` Nathan Dehnel
2020-12-23 3:51 ` Nathan Dehnel
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=87mtyburqm.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=ncdehnel@gmail.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.
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.