Skip to Content.
Sympa Menu

sm-discuss - [SM-Discuss] Working on GVM...

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Flavien Bridault <f.bridault AT fra.net>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: [SM-Discuss] Working on GVM...
  • Date: Sun, 11 Sep 2005 17:47:22 +0200

Hello !

Well, trying to get gnome-volume-manager 1.5.1 working, I think I
highlighted several interesting problems concerning udev, hotplug, dbus
and hal. I got the stuff working, but some changes need to be done, and
as I'm not an expert, I would like to hear some others opinions.

1) First of all, hal needs to have to more options enabled :
--enable-sysfs-carrier --enable-hotplug-map

Should we put this optional, or default ?

2) Hal is launched with haldaemon user, but with current default udev
rules on block devices, it will have no access to them (that worked with
0.4 but no longer with 0.5), and causing automounting impossible. The
devices does even not appear with lshal. So the first idea would be to
add haldaemon in root group, but I guess it is not very secure. So we
may, as a lot of distros, add disk, cdrom, cdrw, floppy, or scsi groups
for each category of devices and then add haldaemon in this group. Your
thoughts ?

Those two points are sufficient to make gvm working using /etc/fstab.
Pmount can be used then (optionally I think), but a sorcery bug
currently prevents it to be used by gvm [0]. pmount uses /media to mount
devices that do not appear in /etc/fstab. That will re-launch the
debates about using /media or not. Well in fact, I'm not sure /media is
not yet in the default SMGL root layout, can someone clarify this
point ?

The two last points are not useful for gvm, but as I investigated
through them, I would be interested in having more informations about
them, or maybe if someone already tried these stuff.

3) I read things about making udevsend the hotplug multiplexer ( using :
sysctl -w kernel.hotplug="/sbin/udevsend" ) instead of /sbin/hotplug for
kernels >= 2.6.10. I don't really understand what is the real difference
with that, and anyway I didn't see a lot of difference using it. I don't
know a lot of things about hotplug, but I saw that a lot of distros use
it. In the same way, these distros used to create a
symlink /etc/hotplug.d/default/10-udev.hotplug which points
to /sbin/udevsend, in order to call udevsend first when a hotplug event
comes. I wonder is this is not redundant...

4) dbus-launch with gnome-session question. I thought it was needed to
get gvm working, but in fact, digital camera detection no more works
when I launch gnome-session with dbus-launch... Maybe there is something
that I didn't well setup ?

I have the general feeling we are not really up-to-date with
udev/hotplug setup, so that might be the time to do that. I will really
appreciate any clarifications, because, as I already said it, I'm not
very familiar with all these stuffs... ;-)


[0] http://bugs.sourcemage.org/show_bug.cgi?id=9754
--
-- -- -- -- -- -- --
Flavien Bridault
Source Mage GNU/Linux - Disk Section Guru

irc: vlaaad
jabber: vlaaad AT amessage.be

Attachment: signature.asc
Description: Ceci est une partie de message numériquement signée




Archive powered by MHonArc 2.6.24.

Top of Page