http://bugzilla.novell.com/show_bug.cgi?id=526657
User jsmeix@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=526657#c4
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |vuntz@novell.com
AssignedTo|bnc-team-screening@forge.pr |jsmeix@novell.com
|ovo.novell.com |
Summary|Printer tool: be ready for |yast2-printer: be ready for
|cups-autoconfig replacement |udev-configure-printer
--- Comment #4 from Johannes Meixner 2009-08-04 06:37:49 MDT ---
Regarding cups-autoconfig:
yast2-printer is already safe if cups-autoconfig is not installed.
I will remove in yast2-printer the possibility to install it.
But if it is already installed (e.g. after an update or when
a user installed it manually because he likes it so much ;-)
the old functionality is still available in yast2-printer.
Regarding udev-configure-printer:
Do not rename it.
I do not care how its name is.
But I will use the name hardcoded in yast2-printer.
Therefore I care that the name is stable.
Add/remove the udev-configure-printer package is perfectly
simple and easy for me and for the end-user too.
(Just like "sane-backends-autoconfig".)
Another question:
When in the running system udev-configure-printer gets installed
or removed, how is udev notified about its changed rules
so that udev will start to configure printers automatically
versus will stop to configure printers automatically?
Or is a restart of the whole udev system needed
which means - as far as I understand - a complete reboot
because udev is part of /etc/init.d/boot...)?
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.