unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Antwane Mason <ad.mason1413@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: help-guix@gnu.org
Subject: Re: Udev Rule Not Triggered
Date: Sun, 29 Aug 2021 14:54:59 -0400	[thread overview]
Message-ID: <CAAztfgLEcotH7BjmDctAMhuqbsCtkTDr1T5bUymZjJ_+d34kTQ@mail.gmail.com> (raw)
In-Reply-To: <20210829172309.hidcy4pyqmzhksf6@pelzflorian.localdomain>

On Sun, Aug 29, 2021 at 1:23 PM pelzflorian (Florian Pelz) <
pelzflorian@pelzflorian.de> wrote:

> On Sun, Aug 29, 2021 at 11:44:50AM -0400, Antwane Mason wrote:
> > I was able to at least confirm that the rule exists on the system despite
> > not being run. I used "sudo herd rules udev" to find the store path where
> > udev rules were and confirmed that 49-onlykey.rules is in
> lib/udev/rules.d.
> > Still can't figure out why it's not running though.
>
> Does
>
> less $(sudo herd rules udev)/lib/udev/rules.d/49-onlykey.rules
>

> show the same rules as what is described in your documentation (maybe
> https://docs.crp.to/linux.html)?
>
> It appears so but to be completely safe, I pulled in the original rules
file directly.

*--8<---------------cut
here---------------start------------->8---
(define %onlykey-udev-rule
  (file->udev-rule
    "49-onlykey.rules"
    (let ((version "v1.2.5"))
      (origin
       (method url-fetch)
       (uri
"https://raw.githubusercontent.com/M0Rf30/https://raw.githubusercontent.com/trustcrypto/trustcrypto.github.io/master/49-onlykey.rules")
       (sha256
        (base32 "1pj9i4hp0d74073x1qqwigd0cyriamg65zmx2j98mi0k66qrhcxa"))))))
--8<---------------cut
here---------------end--------------->8---*

 I also tried the following to see if setting the environment variable
helps but onlykey-cli still not working without using sudo.

UDEV_CONF_FILE=/gnu/store/7yncwxmnpcg5p4273xzmsc6axydfwm1v-udev-rules/lib/udev/rules.d
sudo udevadm test $(udevadm info -q path -n /dev/bus/usb/001/005)

  reply	other threads:[~2021-08-29 18:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 13:39 Udev Rule Not Triggered Antwane Mason
2021-08-29 13:53 ` pelzflorian (Florian Pelz)
2021-08-29 14:01   ` Antwane Mason
2021-08-29 14:28     ` pelzflorian (Florian Pelz)
2021-08-29 14:42       ` pelzflorian (Florian Pelz)
2021-08-29 15:22         ` Antwane Mason
2021-08-29 15:44           ` Antwane Mason
2021-08-29 17:23             ` pelzflorian (Florian Pelz)
2021-08-29 18:54               ` Antwane Mason [this message]
2021-08-29 21:39                 ` Antwane Mason
2021-08-29 22:12                   ` pelzflorian (Florian Pelz)
2021-08-29 22:17     ` Tobias Geerinckx-Rice
2021-08-31 21:59       ` Antwane Mason

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=CAAztfgLEcotH7BjmDctAMhuqbsCtkTDr1T5bUymZjJ_+d34kTQ@mail.gmail.com \
    --to=ad.mason1413@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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).