Bug#671546: udev: loop device: add backing file in udev database
Hi, Le 2012-06-28 01:02, Marco d'Itri a écrit : Then I recommend that you propose this change to the upstream maintainer. Done. Thanks, quidame -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671546: udev: loop device: add backing file in udev database
On Jun 28, quid...@poivron.org wrote: > >What uses this variable? > as it does not exist, nothing uses this variable, of course. But if > it exists, maybe it can interest other people. Then I recommend that you propose this change to the upstream maintainer. -- ciao, Marco signature.asc Description: Digital signature
Bug#671546: udev: loop device: add backing file in udev database
Le 2012-06-27 14:40, m...@linux.it a écrit :
On May 05, bilibop wrote:
ENV{BACKING_FILE}="%c"
What uses this variable?
I have built a source package "bilibop" (RFS #675532). One of the
binary packages is called "bilibop-rules" and is mainly a workaround of
the bug #645466 (When running from removable media, udev allows direct
access by "floppy" group):
some bilibop rules override 91-permissions.rules and fix the removable
media hosting the running system, and all its partitions, as owned by
the 'disk' group instead of 'floppy'. Because it supports multi-layered
block devices (dm-crypt, LVM and loop devices), I have introduced this
variable to ease the work.
But thinking that BACKING_FILE can be managed by the udev package
instead of bilibop, the bilibop udev rules file has been splitted:
- 60-loopback.rules (the sample given in this bug report)
- 66-bilibop.rules
If the BACKING_FILE variable is introduced in udev, I will remove
60-loopback.rules from bilibop; otherwise I keep it. That's all.
Additionally,
What uses this variable?
as it does not exist, nothing uses this variable, of course. But if it
exists, maybe it can interest other people.
Cheers,
quidame
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671546: udev: loop device: add backing file in udev database
On May 05, bilibop wrote:
> ENV{BACKING_FILE}="%c"
What uses this variable?
--
ciao,
Marco
signature.asc
Description: Digital signature
Bug#671546: udev: loop device: add backing file in udev database
Package: udev
Version: 175-3.1
Severity: wishlist
Dear Maintainer,
Since kernel 2.6.37, some infos are available in /sys for associated loop
devices, especially the backing file.
I have written a rules file:
== /etc/udev/rules.d/60-loopback.rules =
SUBSYSTEM!="block", GOTO="loopback_end"
KERNEL=="loop?*", OPTIONS+="watch"
ACTION=="add|change", \
KERNEL=="loop?*", \
TEST=="%S/block/%k/loop/backing_file", \
PROGRAM=="/bin/cat %S/block/%k/loop/backing_file", \
ENV{BACKING_FILE}="%c"
LABEL="loopback_end"
Works fine
Is it possible to add a similar file in the udev package (but maybe this is a
task for 'util-linux') or to modify an
existing file (maybe 60-persistent-storage.rules) ?
Thanks
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-proposed-updates')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-486
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages udev depends on:
ii debconf [debconf-2.0] 1.5.42
ii libc6 2.13-30
ii libselinux12.1.9-2
ii libudev0 175-3.1
ii lsb-base 4.1+Debian0
ii util-linux 2.20.1-4
Versions of packages udev recommends:
ii pciutils 1:3.1.9-2
ii usbutils 1:005-3
udev suggests no packages.
-- debconf information:
udev/new_kernel_needed: false
udev/title/upgrade:
udev/reboot_needed:
udev/sysfs_deprecated_incompatibility:
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
