Mailinglist Archive: opensuse-bugs (10021 mails)
| < Previous | Next > |
[Bug 235059] /etc/resmgr.conf.d/99-avrdude_parport.conf is out of date
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Mon, 15 Jan 2007 12:56:28 -0700 (MST)
- Message-id: <20070115195628.9F35F25C889@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=235059
------- Comment #7 from rschiele@xxxxxxxxx 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.
------- Comment #7 from rschiele@xxxxxxxxx 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.
| < Previous | Next > |