hal, ntfs, and 10.0-RC3

[Kevin Oberman]

Since I updated to 10.0-RC3 (from 9), hald no longer works with my ntfs
partitions. I can mount them manually with ntfs-3g, but when not mounted,
hal does not see them at all.
> ls /dev/ntfs
Lenovo_Recovery        SYSTEM_DRV        Windows7_OS

> gpart show ada0
=>        63  1465149105  ada0  MBR  (699G)
          63        1985        - free -  (993K)
        2048     2457600     1  ntfs  (1.2G)
     2459648   958765056     2  ntfs  (457G)
   961224704   471040000     3  ebr  (225G)
  1432264704    32878592     4  ntfs  (16G)
  1465143296        5872        - free -  (2.9M)
> lshal | grep ada0
  block.device = '/dev/ada0'  (string)
  freebsd.device_file = '/dev/ada0'  (string)
> lshal | grep Windows7
Exit 1

I mount on NTFS partition and:
> lshal | grep ada0
  block.device = '/dev/ada0'  (string)
  freebsd.device_file = '/dev/ada0'  (string)
  block.device = '/dev/ada0s1'  (string)
  block.device = '/dev/ada0s2'  (string)
  block.device = '/dev/ada0s3'  (string)
  block.device = '/dev/ada0s5'  (string)
  block.device = '/dev/ada0s4'  (string)
> lshal | grep Windows7
  block.device = '/dev/ntfs/Windows7_OS'  (string)
  info.product = 'Windows7_OS'  (string)
  volume.label = 'Windows7_OS'  (string)
After a umount, all slices vanish again.

Might this be fall-out of the removal of ntfs (read-only) support? I have
not looked through the hald sources to see how it detects these slices. I
do find it interesting that mounting one NTFS file system causes all of the
other ones appear to hald.

Any suggestions?
-- 
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman at gmail.com