diff options
author | Gerald Carter <jerry@samba.org> | 2000-08-17 20:05:05 +0000 |
---|---|---|
committer | Gerald Carter <jerry@samba.org> | 2000-08-17 20:05:05 +0000 |
commit | 150d8c6a87a2af724b22ebcc1fd58248ce99a2f3 (patch) | |
tree | cc52bbe54b00a910737d332ad3a33f8cc43d8d62 /source3/lib/util_file.c | |
parent | 82149af29f401f0ebc422359ddc4f6fc21a424ea (diff) | |
download | samba-150d8c6a87a2af724b22ebcc1fd58248ce99a2f3.tar.gz samba-150d8c6a87a2af724b22ebcc1fd58248ce99a2f3.tar.bz2 samba-150d8c6a87a2af724b22ebcc1fd58248ce99a2f3.zip |
Fix for Win9x driver downloads when information is
stored in the TDB. See the message I posted about
this on samba-technical
* If the admin does not desire the new NT print driver
support, nothing needs to be done. All existing
parameters work the same.
* If the admin wants to take advantage of NT printer
driver support but does not want to migrate the 9x drivers
to the new setup, the leave the existing printers.def
file. When smbd attempts to locate a 9x driver for the
printer in the TDB and fails it will drop down to
using the printers.def (and all associated parameters).
The make_printerdef tool will also remain for backwards
compatibility but will be moved to the "this tool is the
old way of doing it" pile.
* If the admin installs a 9x driver for a printer on
a Samba host (in the printing TDB), this information will
take precedence and the three old printing parameters
will be ignored (including print driver location).
* If an admin wants to migrate the printers.def file into
the new setup, I can write a script to do this using
rpcclient. The main problem is the driver namespace
(we need the NT driver name first in order to
be consistent).
jerry
(This used to be commit ac049f8bf348810dc068382fdbc6635a2015d36a)
Diffstat (limited to 'source3/lib/util_file.c')
0 files changed, 0 insertions, 0 deletions