~ubuntu-branches/ubuntu/wily/devmapper/wily : changes

~ubuntu-branches/ubuntu/wily/devmapper/wily » Changes from revision 44

From Revision 35 to 16

Rev	Summary	Authors	Tags	Date
35	* Merge from Debian unstable. Remaining Ubuntu changes (LP: ... * Merge from Debian unstable. Remaining Ubuntu changes (LP: #244584): - Support udev-controlled devmapper in initramfs, for consistent device discovery/naming during boot and hotplug: + Add debian/dmsetup.initramfs: Hook for copying dmsetup and udev rules to the initramfs. + debian/rules: Copy hook to build directory. + debian/dmsetup.install: Install above file from build directory. + debian/dmsetup.postinst: Call update-initramfs. - debian/rules: Copy po/device-mapper.po to device-mapper.pot so Rosetta has a POT file to import. - Empty DH_OPTIONS while running dh_makeshlibs so that the -p option works properly, so that we get proper udeb shlibs again. - Create two new packages, libdevmapper-event1.02.1 and dmeventd. These packages will be used to help monitor dmraid events and log them to syslog. - debian/libdevmapper-dev.install: Add libdevmapper-event.h and libdevmapper-event.a to the dev package. - debian/dmsetup.udev: Set link priority to 100 for devmapper devices that have an UUID starting with DMRAID- for dmraid devmapper devices, to prevent UUIDs being used to mount hard disk partitions rather than the array itself.	James Westby	2:1.02.27-3ubuntu1	15 years ago
34	Empty DH_OPTIONS while running dh_makeshlibs so that the -p ... Empty DH_OPTIONS while running dh_makeshlibs so that the -p option works properly, so that we get proper udeb shlibs again.	Colin Watson	2:1.02.25-1ubuntu5	15 years ago
33	* Create two new packages, libdevmapper-event1.02.1 and dmev... * Create two new packages, libdevmapper-event1.02.1 and dmeventd. These packages will be used to help monitor dmraid events and log them to syslog. * debian/libdevmapper-dev.install: Add libdevmapper-event.h and libdevmapper-event.a to the dev package.	Luke Yelavich	2:1.02.25-1ubuntu4	15 years ago
32	debian/dmsetup.udev: Set link priority to 100 for devmapper ... debian/dmsetup.udev: Set link priority to 100 for devmapper devices that have an UUID starting with DMRAIDfor dmraid devmapper devices, to prevent UUIDs being used to mount hard disk partitions rather than the array itself.	Luke Yelavich	2:1.02.25-1ubuntu3	15 years ago
31	debian/patches/dmsetup-export.patch: re-add DM_TARGET_TYPE e... debian/patches/dmsetup-export.patch: re-add DM_TARGET_TYPE exports, required for detecting state of dm devices during udev rule execution and sane creation of by-uuid symlinks (forwarded to Debian #486780).	Kees Cook	2:1.02.25-1ubuntu2	16 years ago
30	* Merge from Debian unstable. Remaining Ubuntu changes: * Merge from Debian unstable. Remaining Ubuntu changes: - Call dmsetup from udev rules to name the device, so udev creates them if they do not already exist, and fill in information about the filesystem on the device afterwards. (forwarded to Debian #455746): + Add debian/dmsetup.udev: Naming udev rules. + debian/rules: Call dh_installudev to install above file. + debian/control: Add Recommends: dmsetup to the library and the udeb. - Support udev-controlled devmapper in initramfs, for consistent device discovery/naming during boot and hotplug: + Add debian/dmsetup.initramfs: Hook for copying dmsetup and udev rules to the initramfs. + debian/rules: Copy hook to build directory. + debian/dmsetup.install: Install above file from build directory. + debian/dmsetup.postinst: Call update-initramfs. - debian/rules: Copy po/device-mapper.po to device-mapper.pot so Rosetta has a POT file to import.	Martin Pitt	2:1.02.25-1ubuntu1	16 years ago
29	Upload simply to add a Debian bug number to the previous cha... Upload simply to add a Debian bug number to the previous changelog entry.	Scott James Remnant	2:1.02.20-2ubuntu2	16 years ago
28	* Merge from debian unstable, remaining changes: * Merge from debian unstable, remaining changes: - Apply patch from SuSE that adds an "export" option that will give udev the full device status of each dm device, including whether it's actually active or not. (exists as Debian #434241). - Apply patch to create devices more atomically to avoid races with udev (forwarded upstream and to Debian #455745). - Call dmsetup from udev rules to name the device, so udev creates them if they do not already exist, and fill in information about the filesystem on the device afterwards. (forwarded to Debian #nnnnnn) - Copy po/device-mapper.po to device-mapper.pot so Rosetta has a POT file to import. - Update file locations from previous Ubuntu versions.	Scott James Remnant	2:1.02.20-2ubuntu1	16 years ago
27	* Make the device take the /dev/mapper name in all cases. * Make the device take the /dev/mapper name in all cases. LP: #126379, #144049. * Drop udeb patch since it's not needed.	Scott James Remnant	2:1.02.20-1ubuntu4	16 years ago
26	* Disable the /dev/mapper/* -> /dev/dm-* symlink business in... * Disable the /dev/mapper/* -> /dev/dm-* symlink business in the udeb, as much of partman depends on the /dev/mapper/* names being canonical and gets confused by /dev/dm-. For the time being, I've done this with a patch applied to the udeb's /etc/udev/rules.d/65-dmsetup.rules at build time rather than by maintaining two versions of the file, to avoid the rules getting out of sync. Fix syntax error in dmsetup(8) that broke the description of 'dmsetup info -c' under COMMANDS.	Colin Watson	2:1.02.20-1ubuntu3	16 years ago
25	* Tweak udev rules to match discussion with SuSE. Note that... * Tweak udev rules to match discussion with SuSE. Note that having /dev/mapper/* as a symlink to /dev/dm-* is a temporary measure to make it easier to debug what's happening and will go away before release. * Ignore devmapper devices with no name (often freshly created ones before a following change event). * Change no_replace option to string_escape=none to match udev changes, adjust dependencies to match. * Adjust devmapper node creation patch to avoid the loop; instead always rename over the top; also set the permissions and the selinux context on the temporary node so that we don't end up with half of udev's settings.	Scott James Remnant	2:1.02.20-1ubuntu2	16 years ago
24	* Merge from debian unstable, remaining changes: * Merge from debian unstable, remaining changes: - Ubuntu maintainer foobar - copy po/device-mapper.po to device-mapper.pot so Rosetta has a POT file to import - Demote dmsetup (and dmsetup-udeb) from Depends to a Recommends. - Apply patch from SuSE that adds an "export" option that will give udev the full device status of each dm device, including whether it's actually active or not. - Modify the udev rules we include. - Since both udev and devmapper might be creating the /dev/mapper device node, it's possible it can appear between our stat() and mknod() calls. So if mknod() returns EEXIST, do the stat again; also check lstat in case there's a hanging symlink there. - Install the udev rules in the udeb. - Add dmsetup postinst/preinst scripts.	Fabio M. Di Nitto	2:1.02.20-1ubuntu1	16 years ago
23	* Don't run vol_id on devices with empty tables. * Don't run vol_id on devices with empty tables. * But do run vol_id on devices with tables containing snapshot or snapshot-origin entries, since these are the final result, not the transient pieces. * Also run vol_id on read-only devices. LP: #117089. * Give devices with snapshot-origin in their tables a slightly higher link priority, so they win out of all the LVM devices (UUID will point to the base device, not any snapshots) but still not higher than the underlying devices so real hardware wins.	Scott James Remnant	2:1.02.18-1ubuntu6	17 years ago
22	Further tweaks; always create the the /dev/mapper symlink an... Further tweaks; always create the the /dev/mapper symlink and those in /dev/disk/by-id; use the state and tables to only decide whether or not to run vol_id, since that's the "problematic" bit.	Scott James Remnant	2:1.02.18-1ubuntu5	17 years ago
21	* Fix a regression introduced by Kees's otherwise largely co... * Fix a regression introduced by Kees's otherwise largely correct patch. We still need to not run vol_id on snapshot target devices, otherwise we'll end up using a changing device, and arguing over UUID/LABEL symlinks. (This might not be a complete fix, LVM may need to be patched to make inactive devices). * Correct a school-boy error with the stat()/mknod() loop; we can't unlink then mknod() since that means there's a period without a device node, which could upset callers. Instead rename() the new device node over the top.	Scott James Remnant	2:1.02.18-1ubuntu4	17 years ago
20	* Adjust debian/dmsetup.udev rule to not ignore "snapshot" d... * Adjust debian/dmsetup.udev rule to not ignore "snapshot" devices. This will be needed even after "udev-lvm-mdadm-evms-gutsy" is solved (LP: #117225). * Update Maintainer fields for Ubuntu.	Kees Cook	2:1.02.18-1ubuntu3	17 years ago
19	Install the udev rules in the udeb, since these only arrange... Install the udev rules in the udeb, since these only arrange for symlinks to point at the kernel name (replacing the /dev/mapper device with a symlink), this isn't unsafe to do in the installer. LP: #105623.	Scott James Remnant	2:1.02.18-1ubuntu2	17 years ago
18	* Merge from debian unstable, remaining changes: * Merge from debian unstable, remaining changes: - copy po/device-mapper.po to device-mapper.pot so Rosetta has a POT file to import * udev-lvm-mdadm-evms-gutsy: - Revert changes made during the feisty development cycle; while a valiant effort, we introduced just as many problems as we fixed. - Demote dmsetup (and dmsetup-udeb) from Depends to a Recommends, since we do tend to install those by default and there's no ordering problem anymore. - Apply patch from SuSE that adds an "export" option that will give udev the full device status of each dm device, including whether it's actually active or not. - Modify the udev rules we include; these now check the device state, set the /dev/mapper target as symlink to the kernel name (which HAL expects), and create the by-id, by-uuid and by-label devices itself. - Since both udev and devmapper might be creating the /dev/mapper device node, it's possible it can appear between our stat() and mknod() calls. So if mknod() returns EEXIST, do the stat again; also check lstat in case there's a hanging symlink there.	Scott James Remnant	2:1.02.18-1ubuntu1	17 years ago
17	Make sure /dev/mapper doesn't exist before making it. Make sure /dev/mapper doesn't exist before making it.	Scott James Remnant	2:1.02.08-1ubuntu10	17 years ago
16	Update rules to avoid replacing "untrusted" characters. LP:... Update rules to avoid replacing "untrusted" characters. LP: #92162.	Scott James Remnant	2:1.02.08-1ubuntu9	17 years ago

Older »