From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Export udev-configuration functions.
Date: Wed, 18 Nov 2015 18:57:03 +0100 [thread overview]
Message-ID: <87610zp4wg.fsf@gnu.org> (raw)
In-Reply-To: <874mgjk0ip.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 18 Nov 2015 12:30:38 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> In my system configuration I first created the new udev rule (that’s all
> a bit verbose, unfortunately), which is almost identical to the
> ‘kvm-udev-rule’:
>
> ~~~~~~~~~~~~~~~~
> (define (avrispmkii-udev-rule)
> "Return a directory with a udev rule that sets the group owner and
> group write permissions on the node matching the AVRISPmkII
> microcontroller programming device."
> (computed-file "avrispmkii-rules"
> #~(begin
> (use-modules (guix build utils))
>
> (define rules.d
> (string-append #$output "/lib/udev/rules.d"))
>
> (mkdir-p rules.d)
> (call-with-output-file
> (string-append rules.d "/90-avrispmkii.rules")
> (lambda (port)
> (display "\
> SUBSYSTEM!=\"usb\", ACTION!=\"add\", GOTO=\"avrisp_end\"
>
> # Atmel Corp. JTAG ICE mkII
> ATTR{idVendor}==\"03eb\", ATTR{idProduct}==\"2103\", MODE=\"660\", GROUP=\"dialout\"
> # Atmel Corp. AVRISP mkII
> ATTR{idVendor}==\"03eb\", ATTR{idProduct}==\"2104\", MODE=\"660\", GROUP=\"dialout\"
> # Atmel Corp. Dragon
> ATTR{idVendor}==\"03eb\", ATTR{idProduct}==\"2107\", MODE=\"660\", GROUP=\"dialout\"
>
> LABEL=\"avrisp_end\"\n" port))))
> #:modules '((guix build utils))))
> ~~~~~~~~~~~~~~~~
We should factorize this so one can write:
(udev-rule "90-avrispmkii.rules"
"SUBSYSTEM != …")
Because here it’s arguably sufficiently verbose to discourage newcomers.
:-)
> Then I replaced %desktop-services to amend the service of
> ‘udev-service-type’:
>
> ~~~~~~~~~~~~~~~~
> (modify-services %desktop-services
> (udev-service-type config =>
> (udev-configuration
> (inherit config)
> (rules (append (udev-configuration-rules config)
> (list (avrispmkii-udev-rule)))))))
> ~~~~~~~~~~~~~~~~
That’s one way do do it.
Another one would be to write an avrispmkii service that would extend
‘udev-service-type’ by passing it its rule (and maybe it could do other
useful things as well?)
> From 46091d6045443a1bedbd1ca37e8ac31c1399d551 Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rekado@elephly.net>
> Date: Wed, 18 Nov 2015 12:17:42 +0100
> Subject: [PATCH] services: Export udev-configuration procedures.
>
> * gnu/services/base.scm (udev-configuration, udev-configuration?,
> udev-configuration-rules): Export.
Good idea indeed. OK!
Ludo’.
next prev parent reply other threads:[~2015-11-18 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 11:30 [PATCH] Export udev-configuration functions Ricardo Wurmus
2015-11-18 17:57 ` Ludovic Courtès [this message]
2015-11-18 21:03 ` Ricardo Wurmus
2015-11-18 21:28 ` Ludovic Courtès
2015-11-19 16:08 ` Ricardo Wurmus
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=87610zp4wg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).