From: Pierre Neidhardt <ambrevar@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Nitrokey and udev rules
Date: Fri, 25 May 2018 15:37:40 +0200 [thread overview]
Message-ID: <87vabbhn4r.fsf@gmail.com> (raw)
In-Reply-To: <87h8mwb972.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Mike Gerwitz <mtg@gnu.org> writes:
>
>> Looking through my notes, it looks like I symlinked
>> `/run/current-system/profile/pcsc/drivers/' to `/var/lib/pcsc/drivers'.
>> See Marius Bakke's message on ccid here:
>>
>> <87vawczpb2.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me>:
>> https://lists.gnu.org/archive/html/guix-devel/2016-10/msg01433.html
>>
>> Can you see if that solves your problem?
>
> This sounds like you’ve installed the package into the system profile.
> If this works we should probably add a system service that takes care of
> setting up this directory.
I tried without installing in the system profile
> sudo ln -s ~/.guix-profile/pcsc /var/lib/pcsc
and it worked!
So what do you reckon? Do we need a service?
What would it do? How do we populate /var/lib/pcsc/drivers?
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-05-25 13:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 10:53 Nitrokey and udev rules Pierre Neidhardt
2018-05-22 12:41 ` Ricardo Wurmus
2018-05-22 14:30 ` Pierre Neidhardt
2018-05-22 15:42 ` Marius Bakke
2018-05-23 8:47 ` Pierre Neidhardt
2018-05-23 9:09 ` Pierre Neidhardt
2018-05-23 9:51 ` Pierre Neidhardt
2018-05-24 4:30 ` Mike Gerwitz
2018-05-24 14:04 ` Pierre Neidhardt
2018-05-25 1:44 ` Mike Gerwitz
2018-05-25 5:22 ` Ricardo Wurmus
2018-05-25 13:37 ` Pierre Neidhardt [this message]
2018-05-25 14:46 ` Pierre Neidhardt
2018-05-26 1:22 ` Mike Gerwitz
2018-05-26 1:16 ` Mike Gerwitz
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=87vabbhn4r.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).