Public SourceMage Discussion List

["Jeremy Blosser (emrys)" <jblosser-smgl AT firinn.org>]

I didn't see answers to the below, and given that we just got a bug report
about hal not casting on a system that didn't have the cdrom group, I
wanted to put them forward again.

On Oct 09, Jeremy Blosser (emrys) [jblosser-smgl AT firinn.org] wrote:
> On Oct 09, Flavien Bridault [f.bridault AT fra.net] wrote:
> > At last, I got gnome-volume-manager 1.5.3 working ! :)
> > 
> > I will so make the needed changes, especially in udev. So before doing
> > that, I want to be sure that everybody agrees.
> > 
> > All block devices will belong to disk group, cdrom to cdrom group.
> 
> The latest iso doesn't have a cdrom group by default.
> 
> > Haldaemon user will belong to these groups. We already have these
> > groups, but afaik we don't use them by default. Sandalle suggested to do
> > that in a separated rules file, i.e. 70-hal.rules, but I don't see the
> > interest of not doing that by default. I don't find any reason to not
> > use disk and cdroms groups for the peripherals, but if you have one,
> > please let me know, that's why I opened this thread. ;-)
> 
> Will this affect only new systems or updating existing ones as well?
> Modifying the ownership of existing devices doesn't sound wise.
> 
> > I will make udev the default hotplug multiplexer by
> > modifiying /etc/init.d/runlevels/%DEV/devices. That would not mean
> > however that hotplug scripts are no more launched thanks to the use
> > of /sbin/udev_run_hotplugd.
> 
> Does this only affect people using udev?  Will it do anything to people
> using eg static dev?

Attachment: pgpTYTv6BGk3b.pgp
Description: PGP signature