[Bug 235059] New: /etc/resmgr.conf.d/99-avrdude_parport.conf is out of date
https://bugzilla.novell.com/show_bug.cgi?id=235059 Summary: /etc/resmgr.conf.d/99-avrdude_parport.conf is out of date Product: openSUSE 10.3 Version: unspecified Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: sndirsch@novell.com ReportedBy: rschiele@gmail.com QAContact: qa@suse.de /etc/resmgr.conf.d/99-avrdude_parport.conf is out of date and only produces log messages like: Jan 14 20:28:55 sighup resmgr[13786]: /etc/resmgr.conf.d/99-avrdude_parport.conf:1: command 'add' no longer supported Jan 14 20:28:55 sighup resmgr[13786]: /etc/resmgr.conf.d/99-avrdude_parport.conf:2: command 'add' no longer supported Jan 14 20:28:55 sighup resmgr[13786]: /etc/resmgr.conf.d/99-avrdude_parport.conf:3: command 'add' no longer supported Jan 14 20:28:55 sighup resmgr[13786]: /etc/resmgr.conf.d/99-avrdude_parport.conf:4: command 'add' no longer supported Jan 14 20:28:55 sighup resmgr[13786]: /etc/resmgr.conf.d/99-avrdude_parport.conf:5: command 'add' no longer supported Jan 14 20:28:55 sighup resmgr[13786]: /etc/resmgr.conf.d/99-avrdude_parport.conf:6: command 'add' no longer supported Jan 14 20:28:55 sighup resmgr[13786]: /etc/resmgr.conf.d/99-avrdude_parport.conf:7: command 'add' no longer supported Jan 14 20:28:55 sighup resmgr[13786]: /etc/resmgr.conf.d/99-avrdude_parport.conf:8: command 'add' no longer supported -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jw@novell.com, lnussel@novell.com Status|NEW |NEEDINFO Info Provider| |lnussel@novell.com ------- Comment #1 from sndirsch@novell.com 2007-01-14 20:41 MST ------- /etc/resmgr.conf.d/99-avrdude_parport.conf: add /dev/parport0 desktop add /dev/parport1 desktop add /dev/parport2 desktop add /dev/parport3 desktop add /dev/parport4 desktop add /dev/parport5 desktop add /dev/parport6 desktop add /dev/parport7 desktop Ludwig, "add" has been replaced with what? BTW, /etc/resmgr.conf.d/99-uisp_parport.conf is identical. Actually 99-avrdude_parport.conf has been a copy of 99-uisp_parport.conf from the beginning. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 lnussel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|lnussel@novell.com | ------- Comment #2 from lnussel@novell.com 2007-01-15 02:27 MST ------- There is no replacement. resmgr no longer knows about devices, hal has them instead. Granting access to all parallelports just because some random package is installed is broken anyways, please remove the resmgr config file. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|jw@novell.com |sndirsch@novell.com AssignedTo|sndirsch@novell.com |jw@novell.com ------- Comment #3 from sndirsch@novell.com 2007-01-15 02:45 MST -------
[...], please remove the resmgr config file. done. Jürgen, your turn (uisp package).
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 jw@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |lnussel@novell.com ------- Comment #4 from jw@novell.com 2007-01-15 08:41 MST ------- this degrades us to manually chmodding the /dev/parport? Done. Ludwig, are there any examples how to use hal instead? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 lnussel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|lnussel@novell.com | ------- Comment #5 from lnussel@novell.com 2007-01-15 08:53 MST ------- /usr/share/doc/packages/hal-resmgr/README - hal needs to know about /dev/parport* first - I would advise against using some generic 'parport' class where anyone gets access to all parallel ports. Introduce a separate one for the specific purpose of granting access to the controller instead. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 jw@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwalle@novell.com ------- Comment #6 from jw@novell.com 2007-01-15 12:33 MST ------- CCed Bernhard, tfla-01 has the same problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 ------- Comment #7 from rschiele@gmail.com 2007-01-15 12:56 MST ------- Ludwig, I agree with you that allowing access to all parport devices by default is not a very good idea but 1. there should be a documented way (example config file) how a sysadmin can setup this _in an easy way_ if he likes to have it that way, 2. I can't see how you want to give access to the controller device directly --- contrary to USB devices from your example file these devices cannot be easily identified by probing for them, and 3. the documentation situation of all that hal/resmgr/udev is extremely bad, the way to "do things the right way" changes quite frequently in recent times without having appropriate migration documentation available --- for instance documentation for simple questions like "how can one grant access to a specific device in a persistent way" is just not available to the average sysadmin. --- Note that I don't claim it does not exist at all but it is (a) not in a place where the average user will expect to find it and (b) it's complexity level is not appropriate to answer these simple questions in an appropriate way. Actually I know a huge number of sysadmins that work around this hal/resmgr/udev stuff instead of making use of it and thus this is a regression for them compared to the old static device files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 ------- Comment #8 from lnussel@novell.com 2007-01-16 01:58 MST ------- Well, I don't like some changes either but I can't do much about it. The scanner example is an example for example. Instead of vendor and product id you in theory could match any device via info.udi which is supposed to be persistent. In practice it doesn't seem to work as I just found via trial&error. If you have any *specific* docu enhancements just tell me. I usually know where to look at so I have a hard time figuring out what's missing and where. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 ------- Comment #9 from rschiele@gmail.com 2007-01-16 02:25 MST ------- It's not that I am against the changes. --- Not at all. The problem with the documentation in the hal/resmgr/udev packages are mainly that (if existent) they describe and give examples for the shiny new features but basically don't explain how to do the things that were possible before in an easy way. The _specific_ and most annoying problem for most people I actually see in exactly the question Stefan had initially here in this thread: How does one change permissions for a specific device (named just by the device name and no additional magic) in a persistent way. A short simple step-by-step instruction would do as long as this is maintained over future changes. The current situation is more like giving a fancy modern VCR set to some old people not used to technology. When they ask how to record the current TV show on channel 2 you answer that it is not required to just record the current TV show because they could do programming their VCR over the internet instead of just telling them how to record the current TV show. In this thread you did exactly this: Instead of just answering Stefan's and Juergen's questions on how to change permissions for /dev/parportX you gave the advice not to do so. While giving this advice is fine it would be even better if you could just answer the question as well. The file you mentioned (/usr/share/doc/packages/hal-resmgr/README) does not really provide this information. Maybe actually the problem exactly _is_ that the people maintaining these packages typically know where to find all the information and thus don't see the problem any more. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 ------- Comment #10 from bwalle@novell.com 2007-01-16 02:41 MST ------- As far as I understand, there's no way to do this without modifying HAL. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 ------- Comment #11 from lnussel@novell.com 2007-01-16 02:53 MST ------- Yes, for parport* hal needs to be patched so resmgr can do anything in the first place. Robert is right however. His request for matching a device name is probably so simple I didn't even think about it. Here's an example for a fictional device that is known to hal: # mkdir /etc/hal/fdi/policy/20user # cat <<EOF > /etc/hal/fdi/policy/20user/50-missilelauncher.fdi <?xml version="1.0" encoding="ISO-8859-1"?> <deviceinfo version="0.2"> <device> <match key="linux.device_file" string="/dev/missilelauncher"> <merge key="resmgr.class" type="string">wmd</merge> </match> </device> </deviceinfo> EOF # cat <<EOF > /etc/resmgr.conf.d/50-wmd.conf ## define a new class 'wmd' class wmd ## grant access to class 'wmd' when access to 'desktop' is granted ## (ie everyone on a local console) class desktop includes wmd ## maybe you want to restrict access to 'wmd' to members of a group instead #allow wmd group=generals EOF # rcresmgr restart # rchal restart -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 ------- Comment #12 from rschiele@gmail.com 2007-01-16 03:34 MST ------- Yes! Exactly this is the information that people would expect to find in a README file in either hal, hal-resmgr, or resmgr. And maybe packages like avrdude should reference this file in their documentation because these are the packages where this information is actually needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 ------- Comment #13 from sndirsch@novell.com 2007-01-16 07:53 MST ------- It is known to hal after doing this one? # mkdir /etc/hal/fdi/policy/20user # cat <<EOF > /etc/hal/fdi/policy/20user/50-missilelauncher.fdi <?xml version="1.0" encoding="ISO-8859-1"?> <deviceinfo version="0.2"> <device> <match key="linux.device_file" string="/dev/missilelauncher"> <merge key="resmgr.class" type="string">wmd</merge> </match> </device> </deviceinfo> EOF Or is ther more required to make it known to hal? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 ------- Comment #14 from jw@novell.com 2007-01-16 08:10 MST ------- Created an attachment (id=113138) --> (https://bugzilla.novell.com/attachment.cgi?id=113138&action=view) hal patch to make parport devices knwon. Ludwig answered that on research. Thanks! I'll copy here: Attached PoC patch makes all available devices known to hal with at least basic information. For 10.2 you could document a workaround like this: # hal-device -a /org/freedesktop/Hal/devices/computer_ppdev << EOF linux.device_file = '/dev/parport0' (string) linux.subsystem = 'ppdev' (string) info.product = 'ppdev device /dev/parport0' (string) linux.hotplug_type = 2 (0x2) (int) linux.sysfs_path = '/sys/devices/virtual/ppdev/parport0' (string) info.parent = '/org/freedesktop/Hal/devices/computer' (string) EOF -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 jw@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asvetter@cip.physik.uni-wuerzburg.de ------- Comment #15 from jw@novell.com 2007-01-19 09:48 MST ------- *** Bug 129340 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dkukawka@novell.com ------- Comment #16 from sndirsch@novell.com 2007-02-13 10:43 MST ------- So how should we proceed here? In case we'll need to patch hal. Who will take care of this? Jürgen, Ludwig, Danny? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eich@novell.com ------- Comment #17 from sndirsch@novell.com 2007-05-12 04:28 MST ------- Egbert, JFYI. Since Matthias or me is in Cc of this bugreport or the reported itself, it might be interesting for you as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhopf@novell.com ------- Comment #18 from sndirsch@novell.com 2007-05-12 04:42 MST ------- JFYI, Matthias. This is a bugreport, which is assigned to Egbert/me or with Egbert/me in CC or reported by Egbert/me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235059#c19
--- Comment #19 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=235059#c20
--- Comment #20 from Bernhard Walle
https://bugzilla.novell.com/show_bug.cgi?id=235059#c21
--- Comment #21 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=235059#c22
--- Comment #22 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=235059#c23
Danny Kukawka
Can't we work on this for 10.3?
Yes, we can work on this, but not by adding simply every device in sysfs to HAL. We should add only what make sense and is usefull, and not every sysfs entry which in the most cases provide abosultely no info. about the ppdev device: I have no machine with such a device. Please provide more info about the device (grep . /sys/devices/virtual/ppdev/* -R, HAL log (start hal with additional parameter --verbose=yes --use-syslog in the rc file)) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=235059#c24
--- Comment #24 from Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=235059
User jw@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c25
--- Comment #25 from Juergen Weigert
https://bugzilla.novell.com/show_bug.cgi?id=235059
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=235059
User lnussel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c26
Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=235059
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c27
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=235059
User jw@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c28
--- Comment #28 from Juergen Weigert
https://bugzilla.novell.com/show_bug.cgi?id=235059
User lnussel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c29
--- Comment #29 from Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=235059
User jw@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c30
--- Comment #30 from Juergen Weigert
https://bugzilla.novell.com/show_bug.cgi?id=235059
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=235059
User lnussel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c31
Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=235059
User jw@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c32
--- Comment #32 from Juergen Weigert
https://bugzilla.novell.com/show_bug.cgi?id=235059
User jw@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c33
--- Comment #33 from Juergen Weigert
https://bugzilla.novell.com/show_bug.cgi?id=235059
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=235059
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c34
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=235059
User jw@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c35
--- Comment #35 from Juergen Weigert
https://bugzilla.novell.com/show_bug.cgi?id=235059
User jw@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c36
Juergen Weigert
https://bugzilla.novell.com/show_bug.cgi?id=235059
Robert Vojcik
https://bugzilla.novell.com/show_bug.cgi?id=235059
User lnussel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c37
Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=235059
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=235059
User dkukawka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c38
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=235059
User lnussel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c39
Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=235059
User dkukawka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c43
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=235059
User dkukawka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c44
--- Comment #44 from Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=235059
User lnussel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c45
Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=235059
User dkukawka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c46
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=235059
User lnussel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c47
Ludwig Nussel
https://bugzilla.novell.com/show_bug.cgi?id=235059
User bwalle@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c48
--- Comment #48 from Bernhard Walle
https://bugzilla.novell.com/show_bug.cgi?id=235059
User dkukawka@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c49
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=235059
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=235059
User jw@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235059#c50
--- Comment #50 from Juergen Weigert
participants (1)
-
bugzilla_noreply@novell.com