Previous Entry Share Next Entry
kde and why we still need hal
I seem to be asked this question a lot lately. So, I asked my friend Lukáš, who's known to pack a reasonable amount of solid-fu, to help document the barriers to kde migrating from hal to other things shiny and new, like DeviceKit. Here's what we came up with so far:
Tags: ,

  • 1
Someone pointed me at this blog entry; here's a couple of thoughts

Re "no smart polling (eg. no detection of the Eject button, no Floppy detection)"

This was was already explained by Kay at here. If you really want to listen for the Eject button you are free to poll yourself (the session has write access to the device node). But as Kay says, it's much better to unlock the tray which is what udisks is already doing _anyway_. Also, if you had bothered to look at the upstream bugzilla, you'd find this bug report

Re "no notion of content types of optical disks (Video/VCD/SVCD/...)"

It would be a layering violation to do this at the system level. Actually, the way you want to do this is via the x-content types that recently landed in the MIME spec. See here for the GLib API and here for when it was proposed to XDG list.

Re "no read/write speed properties for CD/DVD burners, no "rewritability" flag"

udisks does provides the DriveMedia property and the value of this indicates whether the media is rewritable. We don't provide read/write speed properties because it depends on the media. You can easily collect this yourself because you have read/write access to the device node already.

Re "no support for tape (backup) units"

Honestly, I have no idea what that means but we do present any block device the kernel knows about.

Re "no support for xD cards"

I don't know what that means. Again, udisks should present any block device the kernel knows about.

Final thoughts

As a closing remark, you really should report this at the upstream mailing lists / bug trackers - it's not really helpful to use wiki/blogging for this kind of thing. Anyway, hope this helps.

Thanks, I'll add your comments to the wiki tracking this.

Re: Answers

I'd say "do it yourself" for collecting read/write speeds is not really an answer since HAL supports the feature.

  • 1

Log in