Public SourceMage Discussion List

[Flavien Bridault <f.bridault AT fra.net>]

Le lundi 12 septembre 2005 à 10:22 -0700, Eric Sandall a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sun, 11 Sep 2005, Flavien Bridault wrote:
> > 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 ?
> 
> Does it break anything adding them? If they make hal work as people
> would expect (e.g. for gnome-volume-manager) and they don't break any
> other packages that use hal, then I say add them by default.
> 
It does not break anything afaik, other distros like Gentoo enable it by
default, so I believe it is safe. Let's try. ;-)

> > 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 ?
> 
> We already have groups for disk, cdrom, and floppy, plus the cdrtools
> package optionally adds a cdrecord group (IIRC). I'd be fine with
> adding haldaemon to those groups if it makes it functional.
Ok, but I guess I was not clear enough. The groups indeed exist but
there is currently no udev rule that use them afaik. What I meant is
that it so also implies to create udev rules to specify for example,
that ide disk drives belong to disk group, cdrom drives to cdrom group,
floppy drives and usb disk to floppy. Everybody agree on making that by
default ?
> 
> > 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 ?
> 
> It's currently setup by the ISOs, but we're still on FHS 2.2 (IIRC)
> which does not have /media nor /srv (since we as a distro voted not to
> use them when FHS was asking).
Mmmm... I didn't well understand ?? What do you mean ? Don't
use /media ? Or do it ? Or maybe try to patch pmount to use /mnt ? (I
would prefer the last if it is possible, I'm not a great fan
of /media ;-) )
> 
> > 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...
> 
> Until we know what it does, I say leave it as the default. Volunteers
> are, of course, welcome to work on it. ;)
Right. So I will try to continue my investigations. :-)
 
> 
> > 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 ?
> 
> Might depend on the camera? I believe some cameras need drivers (e.g.
> from libgphoto2), but I haven't played with cameras much.
> 
> > 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... ;-)
> 
> We just use the default setups, but it would be nice to have them
> setup 'properly' if we're not already doing so.
> 
> > [0] http://bugs.sourcemage.org/show_bug.cgi?id=9754
> 
> Thanks for looking into this Flavien!
> 
> - -sandalle
> 
> - --
> Eric Sandall                     |  Source Mage GNU/Linux Developer
> eric AT sandall.us                  |  http://www.sourcemage.org/
> http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
> http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> 
> iD8DBQFDJblyHXt9dKjv3WERAoqsAJsFjKiRN1X9hFkkqWnPEqO0OcHEzgCgoFe+
> JsLWs1EHiCjkFEvheTzKgjQ=
> =bkAL
> -----END PGP SIGNATURE-----
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> 
-- 
-- -- -- -- -- -- --
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