KDE Volume Manager not receiving mount points from HAL - it can't cope!

[David Zeuthen]

On Tue, 2004-09-21 at 12:46 +0100, Luke Kenneth Casson Leighton wrote:
> On Tue, Sep 21, 2004 at 08:46:16AM +0200, David Zeuthen wrote:
> 
> > > >  so has_removable_media will get set to TRUE.
> > > > 
> > > >  ... only to have it set to FALSE because there's no entry
> > > >  /sys/block/sdb/removable in order to be read
> > 
> > You need a more recent kernel to get the removable file in sysfs. Before
> 
>  urk - 2.6.7 doesn't cut it??  urk.
> 

Afraid not, sorry.

> > >  the only bit that's weird - and probably my own fault - is that
> > >  uhm... KVM shows an entry for "floppy" _and_ an entry for "USB-FDU".
> > > 
> > >  is _this_ what you were referring to about "volumes"?
> > >
> > >  namely that even a floppy can contain volumes and should not be
> > >  treated differently from other storage devices (which at present
> > >  it looks like it is: in KVM there is no link from the
> > >  usb floppy device block_8_0 to the volume).
> > > 
> > 
> > Yeah, exactly. Possibly KVM is treating this as two devices?
>  
>  yes.  yuk.
> 
>  how would it be told to stop doing that?
> 
>  the only link between the "floppy" entry and its volume "USB-FDU"
>  is the parent udi - "info.parent" or something.
> 

That explains the parent-child relationship. According to the hal spec
(which is in the hal tarball and should be installed with the hal
development packages - otherwise please bug your distro :-) there is
also the block.storage_device property. That one is the right one to
use.

David


_______________________________________________
hal mailing list
hal at freedesktop.org
http://freedesktop.org/mailman/listinfo/hal