Following up:
Upgrading worked fine when i did this on my other computer just today.
I don't know what happened or what was different on my other computer that it
didn't work previously.
The first instance was from the util-linux problem and that I hadn't updated
but as that's all fine. As
A follow-up on this:
After deleting entries from /etc/udev/rules.d that are in /lib/udev/rules.d
this issue is completely solved.
One version of the debian packages installs files /etc/udev/rules.d/* but in
later versions these files are no longer used and only the /lib/udev/rules.d
entries
On Oct 16, Chris Donoghue cdono...@gmail.com wrote:
One version of the debian packages installs files /etc/udev/rules.d/* but in
later versions these files are no longer used and only the /lib/udev/rules.d
entries are installed and contained within the package.
This is why I requested the
This is hard to believe since preinst deletes the files if they are
unmodified (and you are the only one who is experiencing this).
Though, according to the preinst script, shouldn't the file be renamed if it
was modified? This also didn't occur on my system. True that, so far, I'm the
only
Please also report the output of:
ls -l /lib/udev/rules.d/ /etc/udev/rules.d/ /dev/disk/*/
After being able to see a root filesystem and boot with 146 my system does map
correctly my dmraid entries. But this works fine with 141 udev. When my
/dev/mapper entry can't be mounted with 146 udev
Upon reading from the source of udev and finding the information in the NEWS
file about uuids I thought perhaps that the problem lay from changes in udev
being now included in util-linux as was sort of indicated. I hadn't looked
into it further myself so what I gave was purely informational
On Oct 13, Chris Donoghue cdono...@gmail.com wrote:
gives me no entry at all of /dev/disk/by-uuid when using version 146 udev but
for version 141 these entries exists as does the the uuid of my root drive
within this directory. So, I suspect that is why my system is unable to boot
as this
vol_id has been replaced by blkid, and you still have not explained what
exactly is wrong with your initramfs.
If you mean here that blkid is in the initramfs then this isn't so. I think it
should be from the file /usr/share/initramfs-tools/hooks/util-linux which has
line copy_exec
On Oct 13, Chris Donoghue cdono...@gmail.com wrote:
If you mean here that blkid is in the initramfs then this isn't so. I think
it should be from the file /usr/share/initramfs-tools/hooks/util-linux which
has line copy_exec /sbin/blkid.
This should not matter because
On Tue, Oct 13, 2009 at 22:58:52 +1100, Chris Donoghue wrote:
I get the following:
Available versions: 2.6.30-2-amd64
Keeping /boot/initrd.img-2.6.30-2-amd64.dpkg-bak
update-initramfs: Generating /boot/initrd.img-2.6.30-2-amd64
/usr/share/initramfs-tools/hooks/util-linux ignored: not
On Tue, Oct 13, 2009 at 02:18:08PM +0200, Julien Cristau wrote:
That's #544669, fixed days ago.
Great. I hadn't got around to starting a bugreport at all on that yet. I'd
stopped upgrading due to being unable to boot into the system with the udev
problem so still had that issue in util-linux.
Package: udev
Version: 146-5
Severity: critical
Justification: breaks the whole system
This is in all versions of 146 udev debian packages.
The initramfs hook file extra/initramfs.hook included in debian udev packages
needs fixing.
0.141 versions contains at the bottom:
for program in
On Oct 13, Chris Donoghue cdono...@gmail.com wrote:
This list needs to at least include vol_id (or revert to the 0.141 version of
this hook) as this obtains uuid entries for present disks in which udev
then creates /dev/disk/by-uuid links.
You are obviously confused, since vol_id does not
Hi Marco,
udev is always one of those system killers
From the 146 udev sources in the NEWS file:
udev 142
Bugfixes.
The program vol_id and the library libvolume_id are removed from the
repository. Libvolume_id is merged with libblkid from the util-linux-ng
package. Persistent
On Oct 13, Chris Donoghue cdono...@gmail.com wrote:
So that means that vol_id does exist but now it's not in udev but in
util-linux instead. It's easy to be confused by all that.
Since you appear to be so easily confused then I suggest you stop
jumping to conclusions and answer my questions
15 matches
Mail list logo
