Skip to contentSkip to conversation

udev remove ATTR(S) not working

DISCUSSION Farkas Levente 3 participants 15 messages Jun 6, 2007 – Jun 10, 2007

lore
Share & tools
lore
#0 lore raw

hi,
how can i write a RUN udev rules for remove event? i want to recognize my usd pendrive's add and remove. the add is simple since i can use rather specific rules like:
---------------------------------------
ACTION="add", SUBSYSTEM="block", ATTR{size}="2880", ATTRS{serial}="07530736300A", ATTRS{product}="USB DISK Pro", RUN+="/xxx"
---------------------------------------
but the remove rule is much complicated, since (at least it seems for me) udev don't send ATTR(S) in this case and don't know about anymore the removed device parameters.

anyway how can i how what kind of ATTR(S) was send by udev? a simple RUN script like this is not too useful since it's only shows environment variable but not ATTR(S)
-----------------------
#!/bin/bash
OUT=/tmp/udev.$$
echo " ------ $ACTION ------------" > $OUT
set >> $OUT
-----------------------
is there any way to debug udev?

another question what is the ID_* env variables? these are the same as ATTR(S) or ..?

thank you for you help in advance.

Signature · 11 lines
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#1 lore raw
Quoted 11 lines · Farkas Levente

hi,
how can i write a RUN udev rules for remove event? i want to recognize my usd pendrive's add and remove. the add is simple since i can use rather specific rules like:
---------------------------------------
ACTION="add", SUBSYSTEM="block", ATTR{size}="2880", ATTRS{serial}="07530736300A", ATTRS{product}="USB DISK Pro", RUN+="/xxx"
---------------------------------------
but the remove rule is much complicated, since (at least it seems for me) udev don't send ATTR(S) in this case and don't know about anymore the removed device parameters.

You can't. Sysfs attributes are already gone when you see the remove event.

Quoted 10 lines

anyway how can i how what kind of ATTR(S) was send by udev? a simple RUN script like this is not too useful since it's only shows environment variable but not ATTR(S)
-----------------------
#!/bin/bash
OUT=/tmp/udev.$$
echo " ------ $ACTION ------------" > $OUT
set >> $OUT
-----------------------
is there any way to debug udev?

ATTR matches files in sysfs, they are not part of the event.

Quoted 2 lines

another question what is the ID_* env variables? these are the same as ATTR(S) or ..?

No, ATTR are files in /sys/*, ID_* variable are added to the event environment by udev tools.

Play around with:
udevmonitor
and:
udevmonitor --env
while connecting a device.

And try:
udevtest <devpath>
and it will probably become more clear.

Kay

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

#2 lore raw
In reply to Farkas Levente
Quoted 13 lines · Farkas Levente
Quoted 11 lines

hi,
how can i write a RUN udev rules for remove event? i want to recognize my usd pendrive's add and remove. the add is simple since i can use rather specific rules like:
---------------------------------------
ACTION=="add", SUBSYSTEM=="block", ATTR{size}=="2880", ATTRS{serial}=="07530736300A", ATTRS{product}=="USB DISK Pro", RUN+="/xxx" ---------------------------------------
but the remove rule is much complicated, since (at least it seems for me) udev don't send ATTR(S) in this case and don't know about anymore the removed device parameters.

If you absolutely need them on remove (could you explain why? What exactly are you trying to do?), set environment vars on add and use (match) them on remove.

-andrey

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

#3 lore raw
In reply to Farkas Levente
Quoted 13 lines · Andrey Borzenkov
Quoted 12 lines · Farkas Levente
Quoted 11 lines

hi,
how can i write a RUN udev rules for remove event? i want to recognize my usd pendrive's add and remove. the add is simple since i can use rather specific rules like:
---------------------------------------
ACTION="add", SUBSYSTEM="block", ATTR{size}="2880", ATTRS{serial}="07530736300A", ATTRS{product}="USB DISK Pro", RUN+="/xxx" ---------------------------------------
but the remove rule is much complicated, since (at least it seems for me) udev don't send ATTR(S) in this case and don't know about anymore the removed device parameters.

Quoted 3 lines

If you absolutely need them on remove (could you explain why? What exactly are you trying to do?), set environment vars on add and use (match) them on remove.

ok so what i really need to somehow properly identify my pen drive. my home partition is luks encrypted and the key on on my pen drive. when i pug in the pen, udev recognize it and mount (after luksopen) the encrypted volue as /home/lfarkas. when i finish my work, simple logout and remove the pen. udev recognize the remove and umount (and luksclose) the volume. what i want to avoid to confuse my pen with other usb device eg. camera, pda and other pen device.

ps. anyway this has been working for years, but now as i upgrade to fedora 7 and have to rewrite the rules (because of the SYSFS<->ATTR changes) i'd also like to polish my scripts.

Signature · 11 lines
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#4 lore raw
In reply to Farkas Levente
Quoted 3 lines · Farkas Levente

ok so what i really need to somehow properly identify my pen drive. my home partition is luks encrypted and the key on on my pen drive. when i pug in the pen, udev recognize it and mount

Any reason you are not using HAL for this? udev is simply the wrong place to do such things. And HAL supports LUKS natively AFAIR.

-andrey

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

#5 lore raw
In reply to Farkas Levente
Quoted 8 lines · Andrey Borzenkov
Quoted 3 lines · Farkas Levente

ok so what i really need to somehow properly identify my pen drive. my home partition is luks encrypted and the key on on my pen drive. when i pug in the pen, udev recognize it and mount

Any reason you are not using HAL for this? udev is simply the wrong place to do such things. And HAL supports LUKS natively AFAIR.

i don't see how can i use hal here? would you explain it to me?!

anyway luks supported by the kernel natively hal has nothing to do with it.

Signature · 11 lines
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#6 lore raw
In reply to Farkas Levente
Quoted 13 lines · Andrey Borzenkov
Quoted 12 lines · Farkas Levente
Quoted 11 lines

hi,
how can i write a RUN udev rules for remove event? i want to recognize my usd pendrive's add and remove. the add is simple since i can use rather specific rules like:
---------------------------------------
ACTION="add", SUBSYSTEM="block", ATTR{size}="2880", ATTRS{serial}="07530736300A", ATTRS{product}="USB DISK Pro", RUN+="/xxx" ---------------------------------------
but the remove rule is much complicated, since (at least it seems for me) udev don't send ATTR(S) in this case and don't know about anymore the removed device parameters.

Quoted 3 lines

If you absolutely need them on remove (could you explain why? What exactly are you trying to do?), set environment vars on add and use (match) them on remove.

how can i do so?
eg i create a new link SYMLINK+="lfarkas" in the add action and in this case in remove actions env contains DEVLINKS='/dev/lfarkas /dev/...'
BUT a rule like this:
ACTION="remove", SUBSYSTEM="block", ENV{DEVLINKS}="/dev/lfarkas*" never match, while a rule like this
ACTION="remove", SUBSYSTEM="block", DEVLINKS="/dev/lfarkas*", match for all block device.
so how can i match for DEVLINKS?
or what other methods exists for properly identify a removed device? thanks in advance.

Signature · 11 lines
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#7 lore raw
In reply to Farkas Levente
Quoted 14 lines · Farkas Levente
Quoted 13 lines · Andrey Borzenkov
Quoted 12 lines · Farkas Levente
Quoted 11 lines

hi,
how can i write a RUN udev rules for remove event? i want to recognize my usd pendrive's add and remove. the add is simple since i can use rather specific rules like:
---------------------------------------
ACTION=="add", SUBSYSTEM=="block", ATTR{size}=="2880", ATTRS{serial}=="07530736300A", ATTRS{product}=="USB DISK Pro", RUN+="/xxx" ---------------------------------------
but the remove rule is much complicated, since (at least it seems for me) udev don't send ATTR(S) in this case and don't know about anymore the removed device parameters.

Quoted 5 lines
Quoted 3 lines

If you absolutely need them on remove (could you explain why? What exactly are you trying to do?), set environment vars on add and use (match) them on remove.

how can i do so?

just like you did. ENV{foo}="bar" on add.

Quoted 6 lines

eg i create a new link SYMLINK+="lfarkas" in the add action and in this case in remove actions env contains DEVLINKS='/dev/lfarkas /dev/...'
BUT a rule like this:
ACTION=="remove", SUBSYSTEM=="block", ENV{DEVLINKS}=="/dev/lfarkas*" never match,

Because DEVLINKS does not come from persistent environment. Check with udevinfo --query=env.

Quoted 1 line

so how can i match for DEVLINKS?

well, again, are you sure you really need it? What do you try to do?

Quoted 1 line

or what other methods exists for properly identify a removed device?

Device is identified by DEVPATH. If you mean - you need to fetch special device attributes that you had set during device add event - you can either store them as environment variable or implement your own on-disk persistent store.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

#8 lore raw
In reply to Farkas Levente
Quoted 11 lines · Farkas Levente
Quoted 7 lines · Andrey Borzenkov
Quoted 3 lines · Farkas Levente

ok so what i really need to somehow properly identify my pen drive. my home partition is luks encrypted and the key on on my pen drive. when i pug in the pen, udev recognize it and mount

Any reason you are not using HAL for this? udev is simply the wrong place to do such things. And HAL supports LUKS natively AFAIR.

i don't see how can i use hal here? would you explain it to me?!

you never mentioned before that you want to mount encrypted partition when you are ot logged on. I am not sure how it works (you need to enter you key at some point, do not you?) but you can use something like ivman or write trivial handler in python that listens to device insert events and mounts them via HAL API.

Quoted 1 line

anyway luks supported by the kernel natively hal has nothing to do with it.

as well as udev :)

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

#9 lore raw
In reply to Farkas Levente
Quoted 10 lines · Andrey Borzenkov
Quoted 9 lines · Farkas Levente
Quoted 7 lines · Andrey Borzenkov
Quoted 3 lines · Farkas Levente

ok so what i really need to somehow properly identify my pen drive. my home partition is luks encrypted and the key on on my pen drive. when i pug in the pen, udev recognize it and mount

Any reason you are not using HAL for this? udev is simply the wrong place to do such things. And HAL supports LUKS natively AFAIR.

Quoted 8 lines
Quoted 2 lines

i don't see how can i use hal here? would you explain it to me?!

you never mentioned before that you want to mount encrypted partition when you are ot logged on. I am not sure how it works (you need to enter you key at some point, do not you?) but you can use something like ivman or write trivial handler in python that listens to device insert events and mounts them via HAL API.

Right, HAL already handles teardown of LUKS volumes when they are removed.

Quoted 3 lines
Quoted 1 line

anyway luks supported by the kernel natively hal has nothing to do with it.

as well as udev :)

That's true. :)

Thanks,
Kay

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

#10 lore raw
In reply to Farkas Levente
Quoted 11 lines · Kay Sievers
Quoted 10 lines · Andrey Borzenkov
Quoted 9 lines · Farkas Levente
Quoted 6 lines · Andrey Borzenkov
Quoted 3 lines · Farkas Levente

ok so what i really need to somehow properly identify my pen drive. my home partition is luks encrypted and the key on on my pen drive. when i pug in the pen, udev recognize it and mount

Any reason you are not using HAL for this? udev is simply the wrong place to do such things. And HAL supports LUKS natively AFAIR.

i don't see how can i use hal here? would you explain it to me?!

Quoted 7 lines
Quoted 5 lines

you never mentioned before that you want to mount encrypted partition when you are ot logged on. I am not sure how it works (you need to enter you key at some point, do not you?) but you can use something like ivman or write trivial handler in python that listens to device insert events and mounts them via HAL API.

Right, HAL already handles teardown of LUKS volumes when they are removed.

my luks partition is on the hard drive it's a 40GB lvm partition. the encryption key to the partition is on the pen drive. and i'd like to automatically luksopen and mount the encrypted partition when i plug in my pendrive and umount and luksclose when i unplug the pendrive.

Signature · 11 lines
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#11 lore raw
In reply to Farkas Levente
Quoted 8 lines · Andrey Borzenkov
Quoted 7 lines · Farkas Levente
Quoted 6 lines · Andrey Borzenkov
Quoted 3 lines · Farkas Levente

ok so what i really need to somehow properly identify my pen drive. my home partition is luks encrypted and the key on on my pen drive. when i pug in the pen, udev recognize it and mount

Any reason you are not using HAL for this? udev is simply the wrong place to do such things. And HAL supports LUKS natively AFAIR.

Quoted 8 lines
Quoted 2 lines

i don't see how can i use hal here? would you explain it to me?!

you never mentioned before that you want to mount encrypted partition when you are ot logged on. I am not sure how it works (you need to enter you key at some point, do not you?) but you can use something like ivman or write trivial handler in python that listens to device insert events and mounts them via HAL API.

my home directory is a luks encrypted volume:
----------------------------------------

# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      34692928   5613204  27288956  18% /
/dev/sda1               101086     12297     83570  13% /boot
tmpfs                   517532         0    517532   0% /dev/shm
/dev/mapper/home-lfarkas
                      39509616  27716680  11391540  71% /home/lfarkas
# cryptsetup status home-lfarkas
/dev/mapper/home-lfarkas is active:
  cipher:  twofish-cbc-essiv:sha256
  keysize: 256 bits
  device:  /dev/mapper/VolGroup00-LogVol02
  offset:  2056 sectors
  size:    80279544 sectors
  mode:    read/write
----------------------------------------
the keyfile (ie. the password to the encrypted partition) is on the
pendrive hidden partition. _before_ i login i just plug in the pendrive
and udev recognize it and mount the pendrive and use the file which
contains the encryption key and mount my volume. this's my udev rules:
----------------------------------------
# cat /etc/udev/rules.d/10-local.rules
ACTION="add", KERNEL="sd[a-z]", SUBSYSTEM="block",
ATTR{size}="2880", ATTRS{serial}="07530736300A", ATTRS{product}="USB
DISK Pro", SYMLINK+="lfarkas", RUN+="/root/bin/home-up
/dev/VolGroup00/LogVol02 lfarkas"

ACTION="remove", KERNEL="sd[a-z]", SUBSYSTEM="block", RUN+="/root/bin/home-down lfarkas"
----------------------------------------
and the used scripts:
----------------------------------------

# cat /root/bin/home-up
#!/bin/bash
if [ -z "`grep /home/$2 /proc/mounts`" ]; then
        TMPDEV="/mnt/tmp"
        mount -t vfat $DEVNAME $TMPDEV
        KEY="$TMPDEV/.$2.key"
        if [ ! -f $KEY ]; then
                exit 1
        fi
        /root/bin/luks-up $1 /home/$2 < $KEY
        RES=$?
        umount $TMPDEV
        exit $RES
fi
# cat /root/bin/home-down
#!/bin/bash
if [ -z "`ps -u $1|grep .Xclients|egrep -v grep`" ]; then
        killall -u $1
        umount /media/*
        sleep 5
        /root/bin/luks-down /home/$1
fi
----------------------------------------
this's working. the only problem i'd like to do it better ie somehow
recognize only _my_ pendrive. in case of add i can use ATTR{size},
ATTRS{serial}, ATTRS{product}, but in remove i can't do any better then
KERNEL="sd[a-z]", SUBSYSTEM="block" which is a satisfied by all kind
of removable device:-( so that's my problem. ie if i plug and remove my
camera it also try to remove my home partition:-(
i hope it's clear now.
Signature · 11 lines
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#12 lore raw
In reply to Farkas Levente
Quoted 13 lines · Farkas Levente
Quoted 12 lines · Andrey Borzenkov
Quoted 10 lines · Farkas Levente
Quoted 7 lines · Andrey Borzenkov
Quoted 3 lines · Farkas Levente

ok so what i really need to somehow properly identify my pen drive. my home partition is luks encrypted and the key on on my pen drive. when i pug in the pen, udev recognize it and mount

Any reason you are not using HAL for this? udev is simply the wrong place to do such things. And HAL supports LUKS natively AFAIR.

i don't see how can i use hal here? would you explain it to me?!

Quoted 7 lines
Quoted 5 lines

you never mentioned before that you want to mount encrypted partition when you are ot logged on. I am not sure how it works (you need to enter you key at some point, do not you?) but you can use something like ivman or write trivial handler in python that listens to device insert events and mounts them via HAL API.

my home directory is a luks encrypted volume:

OK

Quoted 14 lines

----------------------------------------

# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      34692928   5613204  27288956  18% /
/dev/sda1               101086     12297     83570  13% /boot
tmpfs                   517532         0    517532   0% /dev/shm
/dev/mapper/home-lfarkas
                      39509616  27716680  11391540  71% /home/lfarkas
# cryptsetup status home-lfarkas
/dev/mapper/home-lfarkas is active:
  cipher:  twofish-cbc-essiv:sha256
  keysize: 256 bits
  device:  /dev/mapper/VolGroup00-LogVol02
Quoted 8 lines
  offset:  2056 sectors
  size:    80279544 sectors
  mode:    read/write
----------------------------------------
the keyfile (ie. the password to the encrypted partition) is on the
pendrive hidden partition. _before_ i login i just plug in the pendrive
and udev recognize it and mount the pendrive and use the file which
contains the encryption key and mount my volume.

Yes, I guess as it stands now, HAL is not capable of doing it (even when user is logged on). I guess it makes sense to forward this full description to HAL list for discussion.

Quoted 10 lines

this's my udev rules:
----------------------------------------

# cat /etc/udev/rules.d/10-local.rules
ACTION=="add", KERNEL=="sd[a-z]", SUBSYSTEM=="block",
ATTR{size}=="2880", ATTRS{serial}=="07530736300A", ATTRS{product}=="USB
DISK Pro", SYMLINK+="lfarkas", RUN+="/root/bin/home-up
/dev/VolGroup00/LogVol02 lfarkas"

ACTION=="remove", KERNEL=="sd[a-z]", SUBSYSTEM=="block", RUN+="/root/bin/home-down lfarkas"

[...]

Quoted 6 lines

this's working. the only problem i'd like to do it better ie somehow recognize only _my_ pendrive. in case of add i can use ATTR{size}, ATTRS{serial}, ATTRS{product}, but in remove i can't do any better then KERNEL=="sd[a-z]", SUBSYSTEM=="block" which is a satisfied by all kind of removable device:-( so that's my problem. ie if i plug and remove my camera it also try to remove my home partition:-(

Have you ever tried udevinfo?

{pts/0}% udevinfo -q env --name sda
ID_VENDOR=ATA
ID_MODEL=IC25N020ATDA04-0
ID_REVISION=DA3O
ID_SERIAL=SATA_IC25N020ATDA04-_63A63GY1081
ID_SERIAL_SHORT=63A63GY1081
ID_TYPE=disk
ID_BUS=scsi
ID_ATA_COMPAT=IC25N020ATDA04-0_63A63GY1081
ID_PATH=pci-0000:00:04.0-scsi-0:0:0:0
ID_EDD=int13_dev80

notice ID_SERIAL or ID_SERIAL_SHORT?

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

#13 lore raw
In reply to Farkas Levente
Quoted 32 lines · Andrey Borzenkov
Quoted 10 lines

this's my udev rules:
----------------------------------------

# cat /etc/udev/rules.d/10-local.rules
ACTION="add", KERNEL="sd[a-z]", SUBSYSTEM="block",
ATTR{size}="2880", ATTRS{serial}="07530736300A", ATTRS{product}="USB
DISK Pro", SYMLINK+="lfarkas", RUN+="/root/bin/home-up
/dev/VolGroup00/LogVol02 lfarkas"

ACTION="remove", KERNEL="sd[a-z]", SUBSYSTEM="block", RUN+="/root/bin/home-down lfarkas"

[...]

Quoted 6 lines

this's working. the only problem i'd like to do it better ie somehow recognize only _my_ pendrive. in case of add i can use ATTR{size}, ATTRS{serial}, ATTRS{product}, but in remove i can't do any better then KERNEL="sd[a-z]", SUBSYSTEM="block" which is a satisfied by all kind of removable device:-( so that's my problem. ie if i plug and remove my camera it also try to remove my home partition:-(

Have you ever tried udevinfo?

{pts/0}% udevinfo -q env --name sda
ID_VENDOR=ATA
ID_MODEL=IC25N020ATDA04-0
ID_REVISIONÚ3O
ID_SERIAL=SATA_IC25N020ATDA04-_63A63GY1081
ID_SERIAL_SHORTcA63GY1081
ID_TYPE=disk
ID_BUS=scsi
ID_ATA_COMPAT=IC25N020ATDA04-0_63A63GY1081
ID_PATH=pci-0000:00:04.0-scsi-0:0:0:0
ID_EDD=int13_dev80

Quoted 1 line

notice ID_SERIAL or ID_SERIAL_SHORT?

yes but as i wrote earlier if i write ENV{ID_SERIAL}="_USB_DISK_Pro_07530736300A" it's not working in case of removal! that's my problem!

Signature · 11 lines
  Levente                               "Si vis pacem para bellum!"

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
#14 lore raw
In reply to Farkas Levente
Quoted 35 lines · Farkas Levente
Quoted 34 lines · Andrey Borzenkov
Quoted 10 lines

this's my udev rules:
----------------------------------------

# cat /etc/udev/rules.d/10-local.rules
ACTION=="add", KERNEL=="sd[a-z]", SUBSYSTEM=="block",
ATTR{size}=="2880", ATTRS{serial}=="07530736300A", ATTRS{product}=="USB
DISK Pro", SYMLINK+="lfarkas", RUN+="/root/bin/home-up
/dev/VolGroup00/LogVol02 lfarkas"

ACTION=="remove", KERNEL=="sd[a-z]", SUBSYSTEM=="block", RUN+="/root/bin/home-down lfarkas"

[...]

Quoted 6 lines

this's working. the only problem i'd like to do it better ie somehow recognize only _my_ pendrive. in case of add i can use ATTR{size}, ATTRS{serial}, ATTRS{product}, but in remove i can't do any better then KERNEL=="sd[a-z]", SUBSYSTEM=="block" which is a satisfied by all kind of removable device:-( so that's my problem. ie if i plug and remove my camera it also try to remove my home partition:-(

Have you ever tried udevinfo?

{pts/0}% udevinfo -q env --name sda
ID_VENDOR=ATA
ID_MODEL=IC25N020ATDA04-0
ID_REVISION=DA3O
ID_SERIAL=SATA_IC25N020ATDA04-_63A63GY1081
ID_SERIAL_SHORT=63A63GY1081
ID_TYPE=disk
ID_BUS=scsi
ID_ATA_COMPAT=IC25N020ATDA04-0_63A63GY1081
ID_PATH=pci-0000:00:04.0-scsi-0:0:0:0
ID_EDD=int13_dev80

Quoted 5 lines
Quoted 1 line

notice ID_SERIAL or ID_SERIAL_SHORT?

yes but as i wrote earlier if i write ENV{ID_SERIAL}="_USB_DISK_Pro_07530736300A" it's not working in case of removal! that's my problem!

no, earlier you wrote you tried ENV{DEVLINKS} which is not going to work. And if you really use the above, it won't work either - you have to use == not =

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel