hal-0.5.11-i486-2 in current shows no volume devices
 

Upgrading to the latest version of HAL causes hal to not create/recognise any volume devices. Instead I only get the generic scsi_interface one level above.

Note that I also upgraded udev to 128 and dbus to 1.2.3, and neither of which is the culprit-> downgrading to hal from slackware 12.1 caused all volume devices to come back (and automounting etc).

So far ive only noticed that its only volumes that are affected, all other devices seem to work fine. Very interest. Maybe a warning for you all.

Do you have parted installed? It's a new-ish dependency.

Ahh it all comes to me now. I didnt know that parted is used as a detect volume details method, since it is not linked directly into hal (and shows no broken links). Well thanks for that, I guess im forced to use parted (and perhaps even so far as device-mapper (oh cruel world)).

You must accept my apologies for keeping this thread going. I had initially thought that my issue was closed when parted (and its dependencies) were installed. This is partially true, however I have just been bearer of news that hal fs.type on ntfs partitions is blank (infact the entire fs.xxxx property on a ntfs partition).

Would someone be so kind as to enlighten me once again as how to overcome such problems? Any help is greatly appreciate.

Yes, I'm having the same problem, too now.

A consequence is that Amarok, which is watching an NTFS partition for new additions to my music collection, is repeatedly under the impression that new files have been detected (and running ~90% CPU "adding" new music).

If you are cherry-picking packages from Slackware-current you will bring Doom over your box.

Either stay with Slackware-12.1 (the stable release) and watch out for patches that are released regularly, or stay with the bleeding edge Slackware-current all the way - meaning you have to install all new packages that appear in the tree as well as upgrade the existing ones to their latest version.

Eric

A solution to the NTFS file system not recognized has been found! It turns out, udev 128 has some serious issues with ntfs (http://thread.gmane.org/gmane.linux.hotplug.devel/13087). Therefore, go download the source slackbuild, replace udev 128 with 130 and problem will want to disappear very fast.

One must also thank Alien Bob for some very wise advice. From experience, however, picking only the packages one needs in a minimalist sort of way can be achieved in Slackware much better than any other distro. This is one of the good points of Slackware and while I know you are a person of good intentions, perhaps not be so quick to deny other's need to embrace these good points will make your posts more helpful.

Ah, darn. I'd seen this report, and even worked with a guy a bit about it on the udev mailing list, but since I don't have any ntfs stuff available, I couldn't test it, so I figured that it would either work for us or we'd get bug reports - such is the beauty of -current :-)

Edit: yeah, I'm in that thread... :/

Robby & all,

Any chance my problem is caused by this as well?

I compared udev-118 from Slackware-stable with udev-128 from -current and noticed that the rules in the package moved from /etc/udev/rules.d/ to /lib/udev/rules.d/
And (that's probably the origin of my problem) 'ppp' is missing from /lib/udev/devices/

udev is still like a "black box" to me, so I don't want to experiment too much and risk breaking my working system... :)

Sorry, I didn't get an email notification on this thread for some reason, so I didn't see your question until just now when I was browsing the threads. Anyway, I replied in your separate thread on the issue :)

udev-130 is available in -current now