From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kdm & french keyboard
Date: Wed, 14 Jul 2010 22:29:43 +0200 [thread overview]
Message-ID: <201007142229.44129.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4C3E1A30.6050309@gmail.com>
On Wednesday 14 July 2010 22:12:32 Dale wrote:
> Alan McKinnon wrote:
> > On Wednesday 14 July 2010 09:58:02 Stéphane Guedon wrote:
> >> I agree with you, but I like to make things in order with the rules
> >> (without relation to udev).
> >>
> >> But I don't like udev, its syntax is really hard to understand for user
> >> !
> >
> > Dale, here's your chance to jump in and comment.
> >
> > This user *obviously* never had to deal with hal.
>
> Oh crap. You mean udev uses xml config files too? Well, at least udev
> hasn't broke my keyboard and mouse. lol I don't have to much trouble
> with udev. Heck, the one time I did, I deleted all the config files and
> re-emerged the thing. Worked great then. I think one got messed up
> somehow.
>
> Dale
>
> :-) :-)
No, not XML. It uses something MUCH better. It uses this:
$ cat rules.d/70-persistent-cd.rules
# This file was automatically generated by the /lib64/udev/write_cd_rules
# program, probably run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line
# and set the $GENERATED variable.
# DVD+-RW_AD-7640A (pci-0000:00:1f.1-scsi-0:0:0:0)
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.1-scsi-0:0:0:0",
SYMLINK+="cdrom", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.1-scsi-0:0:0:0",
SYMLINK+="cdrw", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.1-scsi-0:0:0:0",
SYMLINK+="dvd", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.1-scsi-0:0:0:0",
SYMLINK+="dvdrw", ENV{GENERATED}="1"
# Mass_Storage (pci-0000:00:1d.0-usb-0:2:1.2-scsi-0:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*",
ENV{ID_SERIAL}=="HUAWEI_Mass_Storage-0:0", SYMLINK+="cdrom1",
ENV{GENERATED}="1"
See how fantastic this is? See how this conforms to The One True (Unix) Way?
See how it looks nothing like XML (invented by a Windows user, obviously), and
actually looks a lot like perl with regexes?
On second thoughts, it looks nothing like perl. There aren't enough $, @ and %
symbols in it. But the regex bit stands.
:-)
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2010-07-14 20:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 14:56 [gentoo-user] kdm & french keyboard alain.didierjean
2010-07-07 15:03 ` Neil Bothwick
2010-07-07 15:23 ` alain.didierjean
2010-07-07 15:58 ` Neil Bothwick
2010-07-07 17:19 ` Stéphane Guedon
2010-07-07 23:13 ` Neil Bothwick
2010-07-11 17:19 ` Stéphane Guedon
2010-07-12 8:31 ` Neil Bothwick
2010-07-14 7:58 ` Stéphane Guedon
2010-07-14 14:44 ` Alan McKinnon
2010-07-14 20:12 ` Dale
2010-07-14 20:29 ` Alan McKinnon [this message]
2010-07-14 20:46 ` Dale
2010-07-17 20:17 ` Stéphane Guedon
2010-07-17 22:38 ` Alan McKinnon
2010-07-17 23:08 ` Dale
2010-07-18 6:59 ` Stéphane Guedon
2010-07-18 22:34 ` Neil Bothwick
2010-07-18 23:14 ` Dale
2010-07-17 20:18 ` Stéphane Guedon
2010-07-17 20:16 ` Stéphane Guedon
2010-07-08 6:50 ` alain.didierjean
2010-07-11 8:06 ` Ronan Mainbourg
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=201007142229.44129.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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