Hello, On Mar 10 13:52 Jiri Srain wrote (shortened):
Dne Monday 10 of March 2008 13:31:35 Stefan Hundhammer napsal(a):
Setting up a printer comes to mind ...
Printer can be detected and configured automatically without user's interaction
Since openSUSE 10.3 we have the new RPM "cups-autoconfig" which contains a utility for auto-configuring USB printers which is triggered by udev/HAL device events. On the one hand this tool is limited to USB printers, on the other hand it works independent of YaST e.g. even after the installation: E.g. when the USB printer was disconnected or switched off during installation, cups-autoconfig could automatiocally configure it once it is connected or switched on at any time later. Note that this tool neither comes from the CUPS authors nor is the RPM a sub-package of the cups RPM.
From CUPS's point of view it is a "third-party" tool.
Since cups-autoconfig exists, there is actually no longer any need to let the YaST printer module do the autoconfiguration. Since cups-autoconfig the YaST printer setup module can focus on manual printer setup (i.e. all those cases where cups-autoconfig cannot/doesn't work). By the way: Have a look at http://en.opensuse.org/YaST/Development/Printer_Enhancement in particular regarding "cups-autoconfig" see http://en.opensuse.org/Image:Printer_mschmidkunz_rc2_overview_autoconfig.png By default cups-autoconfig disables/enables print queues when udev/HAL events appear that a USB printer is disconnected/connected. Its /etc/cups-autoconfig.conf contains by default: -------------------------------------------------------------- [CUPS] ConfigureNewPrinters=yes DisablePrintersOnRemoval=yes DefaultCUPSPolicy=relaxed Debug=yes -------------------------------------------------------------- It is triggered via /usr/share/hal/fdi/policy/10osvendor/10-cups-autoconfig.fdi which runs /usr/lib/cups-autoconfig/cups-autoconfig which does the actual stuff, see /usr/lib/cups-autoconfig/cups-autoconfig --help (you must run even '--help' as root, otherwise you get errors) Debugging output is in /var/log/cups-autoconfig.log For some background information, see http://code.google.com/p/cups-autoconfig/ Regarding automated scanner configuration, see https://bugzilla.novell.com/show_bug.cgi?id=347943 If automated printer or scanner configuration doesn't work and the user has problems to find the YaST printer or scanner module for a manual setup, it is a usability problem of the YaST control centre which is also already worked on as far as I know. Summary: I appreciate "Getting Rid of 2nd Stage Installation" very much. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org