Update Pack 4 contains all the new features from Update Pack 1, Update Pack 2, and Update Pack 3,as well as the additional new features listed in this section. See the UnixWare 7.1.4 Feature List for a complete list of new features since UnixWare 7.1.3.
Also see the sections Problems Fixed for a complete list of maintenance fixes, and Known Problems for limitations and workarounds.
The features listed in this section are installed with the Update Pack Set. See the Installation Procedures section for how to install the Update Pack Set.
Support for booting UnixWare systems using the Advanced Configuration and Power Interface (ACPI) BIOS tables is provided. This allows UnixWare to run on multiprocessor (MP) systems that do not have Intel Multi-Processor Specification (MPS) BIOS tables. Previously, UnixWare would not boot on a system that did not have MPS tables. Booting from ACPI tables is disabled by default. To enable booting from ACPI:
Make sure the osmp (multi-processing support) package is installed (even if you have a UP system). Enter:
pkginfo osmp
To see if osmp is installed. If not, install it from the UnixWare 7 Installation CD#1, by inserting the CD into the primary CD drive and entering:
pkgadd -d cdrom1 osmp
Add the following line to the file /stand/boot:
ACPI=Y
Note: Booting from ACPI and hyperthreading may be used together by
adding both ACPI=Y and ENABLE_JT=Y entries to the /stand/boot
file and rebooting the system.
See the boot(4) manual page.
Reboot the system to rebuild the kernel:
shutdown -i6 -g0 -y
If your hardware supports hyperthreading, enter the system BIOS utility as the system reboots to enable hyperthreading in your system BIOS. (See the hardware manufacturer's documentation for details.)
Note: on systems that support hyperthreading, the hyperthreading feature should be enabled in the system BIOS when booting from the ACPI tables, even if hyperthreading is not enabled under UnixWare. Otherwise, if you boot from the ACPI tables on a system that supports hyperthreading but does not have hyperthreading enabled in the BIOS, UnixWare utilities like psrinfo may report fewer processors available than the actual number of processors installed.
Save the BIOS configuration and boot UnixWare.
After the system boots, use the psrinfo(1M) command to check processor status.
Hyperthreading (Jackson Technology) support for UnixWare on Intel processors has been enhanced to work on uniprocessor (UP) systems. Previously, this technology worked only on multiprocessor (MP) systems. By default, hyperthreading is disabled. To enable hyperthreading:
Make sure the osmp (Multiprocessing Support) package is installed (even if you have a UP system). Enter:
pkginfo osmp
To see if osmp is installed. If not, install it from UnixWare 7 Installation CD#1, by inserting the CD into the primary CD drive and entering:
pkgadd -d cdrom1 osmp
Add the following line to the file /stand/boot:
ENABLE_JT=Y
Note: Hyperthreading and ACPI may be used together by
adding both ENABLE_JT=Y and ACPI=Y entries to the /stand/boot
file and rebooting the system.
See the boot(4) manual page.
Reboot the system to rebuild the kernel:
shutdown -i6 -g0 -y
As the system reboots, enter the system BIOS utility to enable hyperthreading in your system BIOS. (See the hardware manufacturer's documentation for details.) Save the BIOS configuration and boot UnixWare.
After the system boots, use the psrinfo(1M) command to check processor status.
The Network Time Protocol (NTP) has been updated to Version 4.1.1 from http://www.ntp.org. NTP is used to synchronize the time of a computer client or server to another server or reference time source. This release maintains compatibility with NTP 2.x and 3.x, while support for NTP 1.x has been removed. See the NTP documentation provided with version 4, under Networking > Administering TCP/IP and Internet Services, in the online documentation. In particular, see the NTP Version 4 Release Notes and the Quick Start.
The IPsec (secure IP) protocol suite and associated tools provides the ability to encrypt and authenticate IP packets transmitted between cooperating hosts or subnets.
When IPsec is configured for a given communication path between hosts or subnets, most of the IP header and the entire data portion of each packet sent over the network is encrypted by the sending host, and decrypted by the receiving host. This is in contrast to non-IPsec packets, which are not encrypted.
In addition to encrypting IP packets, IPsec can authenticate each packet using the information in the expanded header supported by this protocol. Authentication can also be provided using private keys and signed certificates.
In this way, each host can not only be assured that each packet has been encrypted for delivery, but also validate that the packet received has originated with the expected host and that no third party has tampered with or had access to the data in the packets during transmission.
One of the uses of IPsec is to implement a Virtual Private Network (VPN). In a VPN, a non-secure communication path (such as an internet connection) is used for the transmission of encrypted and authenticated packets between hosts that have been set up to use that path and only provide IPsec packets over the path.
A VPN is really a set of security associations established on each host that requires secure IP communications, along with a security policy established for each "subnet" in the VPN. Thus, a corporate VPN might be defined by a gateway router that allows a number of remote systems (or other gateways) to connect over public transmission facilities (phone lines, cable modem, wireless), and access the corporate network. A properly configured IPsec facility on the gateways and the various remote systems prevents the kind of security threats inherent in public transmission systems, such as spoofing, masquerading, denial of service, and others.
IPsec is disabled by default; this is because running IPsec without first configuring it properly for your site reduces overall network performance with no benefit. To configure and enable IPsec, see Networking > Administering TCP/IP and Internet services > Secure IP (IPsec) in the online documentation. The documentation includes procedures and configuration examples.
The Name Service Switch (NSS) provides a single point of control for lookup operations on system databases (such as /etc/passwd, /etc/group, etc.). This gives a system administrator the ability to configure these operations while the system is running, including the ability to extend the implementation through plug-in runtime modules.
For more information see the NSS Overview in the online documentation.
The version identifier returned by the uname(1) command, the uname(2) system call, and associated utilities after installation is updated from 7.1.3 to 7.1.4. For example:
# uname -v
Returns the following:
7.1.4
The features listed in this section are contained in separate packages from the Update Pack Set. To install them, either select them from the Upgrade Wizard when you install the Update Pack Set, or follow the instructions in the section Installing Additional Packages after the Update Pack Set.
A new sound driver (ich) that supports on-board PCI sound cards on Intel 845 chipsets has been added to the audio package. The chipsets supported are ICH1, ICH2, ICH3, and ICH4. The driver also provides support for the AC97 mixer.
The AC97 codec on the soundcard must support VRA (variable rate) for any application to play audio files at variable rates. If the codec doesn't support VRA, then most applications will fail to play any audio files. For example, using mpg123 with a soundcard that does not support VRA returns the following message:
No supported rate found !!
If your hardware supports the relevant chipsets, the ich driver is loaded and configured automatically when the audio package is added. You can also manually load the driver using:
modadmin -l ich
To test whether the driver is working properly, mpg123 player for native UnixWare can be intalled and be used for playing audio files. You can find mpg123 on the web at http://www.sco.com/skunkware. If you have installed the Linux Kernel Personality (LKP) on your system, you can also download the Linux version of Realplayer from the web (http://www.realplayer.com to play audio files. Both mpg123 and Realplayer running on LKP have been tested with the new driver.
Note that the ich driver does not provide audio support for the SCO Merge product at this time.
The db package contains version 4.1.25 of the Berkeley DB software, an embedded programmatic database toolkit. This package is provided primarily for, and is required by, the OpenLDAP software. It can be used in any application where a programmable embedded database is required. See the DB Documentation installed under /usr/docs by the db package.
PostgreSQL (pgsql) is a widely-used open source database system that offers the features and reliability usually associated with more costly proprietary database systems. PostgreSQL documentation is installed with the pgsql package and is available under Software Development in the online documentation. For a review of the advantages of deploying PostgreSQL, please see http://advocacy.postgresql.org/advantages/. General information and news about PostgreSQL is available from the PostgreSQL Web Site at http://www.postgresql.org.
The QLogic PCI FibreChannel (qlc2300) and the Adaptec Ultra320 Family PCI SCSI HBA (adpu320) Host Bus Adapter (HBA) drivers have been updated, as follows:
Fixes problems with board ID return value on some IBM systems with PCI-X slots.
Fixes problems experienced when disks are connected to both channels.
The qlc2300 and adpu320 drivers are available as separate package images in the Update Pack, as well as a floppy disk image suitable for use during a fresh install of UnixWare. The floppy image is available at: ftp://ftp.sco.com/pub/unixware7/drivers/storage.
The Network Drivers (nd) package has been updated with new versions of the following existing Network Interface Card (NIC) drivers:
Fixed problems seen in development environment only.
Fixed some incorrect function return values and a system panic in bcopy(3C) caused by the driver.
Fixed minor problems and added new card support. The complete list of network adapters supported by the new version of eeE8 follows:
645477-xxx PRO/10+ PCI PILA8500
649439-xxx PRO/10+ PCI PILA8520
701738-xxx Pro/100+ PCI Management Adapter PILA8461
668081-xxx Pro/100+ PCI PILA8460
689661-xxx
722762-xxx
721383-xxx Pro/100+ PCI Management Adapter PILA8460B
741462-xxx Pro/100+ PCI PILA8460BN
748566-xxx PRO/100 S Management PILA8460BUS
748564-xxx PRO/100 S Management PILA8464B
742252-xxx InBusiness(tm) 10/100 adapter SA101TX
351361-xxx PRO/100 PCI PILA8465
352509-xxx EtherExpress(tm) PRO/100B PCI adapter PILA8465B
661949-xxx
667280-xxx
678400-xxx
352433-xxx PRO/100B PCI T4 PILA8475B
691334-xxx PRO/100+ PCI Management Adapter PILA8900
A80897-xxx PRO/100 M Desktop PILA8460M
751767-xxx PRO/100 S Desktop PILA8460C3
================== Server Adapters ============
714303-xxx PRO/100+ Dual Port Server Adapter PILA8472
711269-xxx
748565-xxx PRO/100 S Server PILA8474B
748568-xxx Intel(c)PRO/100 S Server PILA8474BUS
710550-xxx PRO/100+ PCI Server Adapter PILA8470
729757-xxx PRO/100+ Server Adapter PILA8470B
A56831-xxx PRO/100 S Dual Port Server Adapter PILA8472C3
752438-xxx PRO/100 S Server PILA8470C3
New NIC support in eeE8 2.6.8:
------------------------------
82559 Fast Ethernet LOM with Alert on LAN
PRO/100 S Mobile LAN on Motherboard
PRO/100 VM Network Connection
PRO/100 VE Network Connection
HP NC3133 Fast Ethernet NIC
HP NC3163 Fast Ethernet NIC
HP NC3162 Fast Ethernet NIC
HP NC3123 Fast Ethernet NIC
HP NC3134 Fast Ethernet NIC
HP NC3135 Fast Ethernet Upgrade Module
HP NC3120 Fast Ethernet NIC
HP NC3122 Fast Ethernet NIC
HP NC1120 Ethernet NIC
HP 10/100 TX PCI Intel WOL UTP Controller
HP NC3160 Fast Ethernet NIC
HP NC3121 Fast Ethernet NIC
HP NC3131 Fast Ethernet NIC
HP NC3132 Fast Ethernet NIC
Fixed minor problems and added new NIC support. The complete list of network adapters supported by the new version of bcme follows:
3Com 3C996/3C1000/3C94X Gigabit Ethernet 3Com 3C996-SX Gigabit Ethernet Broadcom BCM5700 NetXtreme Gigabit Ethernet Broadcom BCM5700S NetXtreme Gigabit Ethernet Broadcom BCM5701 NetXtreme Gigabit Ethernet Broadcom BCM5701S NetXtreme Gigabit Ethernet Broadcom BCM5702 NetXtreme Gigabit Ethernet Broadcom BCM5703 NetXtreme Gigabit Ethernet Broadcom BCM5703S NetXtreme Gigabit Ethernet Broadcom BCM5704 NetXtreme Gigabit Ethernet Broadcom BCM5704S NetXtreme Gigabit Ethernet Broadcom BCM5705 NetXtreme Gigabit Ethernet Broadcom BCM5782 NetXtreme Gigabit Ethernet for hp HP NC6770 Gigabit Ethernet HP NC7722 Gigabit Server Adapter HP NC7760 Gigabit Ethernet HP NC7761 Gigabit Server Ethernet HP NC7770 Gigabit Ethernet HP NC7771 Gigabit Ethernet HP NC7772 Gigabit Server Ethernet HP NC7780 Gigabit Ethernet HP NC7781 Gigabit Ethernet HP NC7782 Gigabit Ethernet HP NC7783 Gigabit Ethernet
The xdrivers package has been updated to include a new ATI Radeon Graphics Adapter Driver. This driver supports the following video cards:
ATI RADEON 7000 Graphics Adapter
ATI RADEON 7200 Graphics Adapter
ATI RADEON 7500 Graphics Adapter
The javaxcomm package contains version 2.0 of the Java Communications API for Java Serial I/O. This package enables Java applications to communicate over serial ports. See the Release Notes for javax.comm, and the RXTX open source web site at http://www.rxtx.org, for more information. Please note that this release of javax.comm does not support communication over parallel I/O ports.
The following Java 2 SE 1.3.1 packages have been updated to the indicated versions in response to Sun Microsystems, Inc., security alerts:
| j2jre131 | Java 2 SE 1.3.1_10 Runtime Environment 1.3.1 |
| j2sdk131 | Java 2 SE 1.3.1_10 Software Development Kit |
| j2plg131 | Java 2 SE 1.3.1_10 Java Plug-in (Netscape and Mozilla) |
| j2pls131 | Java 2 SE 1.3.1_10 Demos and Debug |
The alerts are:
| Sun Alert ID | Description |
| 57436 | Verisign Class 3 and Class 2 PCA Root Certificate Expiration |
| 57221 | A Vulnerability in JRE May Allow an Untrusted Applet to Escalate Privileges |
The Java 2 Standard Edition 1.4.2 consists of the following packages:
| j2jre142 | Java 2 SE 1.4.2_03 Runtime Environment 1.4.2 |
| j2sdk142 | Java 2 SE 1.4.2_03 Software Development Kit |
This is the first Java release for UnixWare to incorporate the Sun HotSpot Java virtual machine. It has greatly improved performance and scalability over the previous Java 1.3.1 release.
The j2jre142 package requires the urwfonts package, and must be installed before installing j2sdk142.
On upgrade, Release 1.4.2 is installed by default and /usr/java is updated to point to the 1.4.2 version (/opt/java2-1.4.2). See the section Checking Update Pack Installation for how to check and change the active Java version.
Note that there is currently no Release 1.4.2 Mozilla Java plugin support; this is provided by the j2plg131 package.
A JDK 1.4.2 debugging package (formerly j2pls131) is not being released. The debugging information for the Sun "hotspot" VM's (now mostly in C++) is too large to be of any practical use (debugging size exceeds 400MB for each VM-client server). The Java demos formerly in j2pls131 have been moved into the j2sdk142 package.
This release of the Java 2SE corresponds to Sun's J2SE 1.4.2_03 patch level and includes the following Sun security fixes:
| Sun Alert ID | Description |
| 57436 | Verisign Class 3 and Class 2 PCA Root Certificate Expiration |
| unknown | Potential Denial of Service - SXun API for XML 1.0 Processing |
Additional information on the Java 2SE can be found at the following links:
The Mozilla web browser has been updated to version 1.2.1a to fix the following known security vulnerabilities in previous versions:
| Mozilla Bug ID | Description |
| 221526 | Script.prototype.freeze/thaw could allow an attacker to run arbitrary code on your computer. |
| 213012 | By requesting a cookie with a path containing the escape sequence "%2E%2E", a malicious web site would be able to read cookies from different paths. |
| 158049 | Detecting variables in another domain is possible. |
| 220122 | A malicious website could gain access to a user's authentication credentials to a proxy server. |
| 92773 | It is possible to get and set variables in another domain. |
For more information please go to http://www.mozilla.org/projects/security/known-vulnerabilities.html.
The Lightweight Directory Access Protocol (LDAP) provides a set of commands and routines to create and manage a Directory Services database. This version of OpenLDAP (2.2.4) implements LDAPv3 as defined in RFC2251. The openldap package depends on the db package (Berkeley DB) for the database back-end. See the LDAP 2.2 Administrator's Guide and LDAP Manual Pages under Networking in the online documentation.
The ppp package has been updated to improve the reliability and scalability of the PPP server, pppd(1M).
The openssl package has been updated to 0.9.7c. OpenSSL is an Open Source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a general purpose cryptography library. A user level command, openssl(1), is provided that performs a variety of cryptographic functions.
Documentation for OpenSSL is packaged separately in openssld. The following manual pages are installed under /usr/man, and can be viewed via man(1) or the DocView Man Pages button (http://hostname:8458):
asn1parse.1 ca.1 CA.pl.1 ciphers.1 crl.1 crl2pkcs7.1 dgst.1 dhparam.1 dsa.1 dsaparam.1 enc.1 gendsa.1 genrsa.1 nseq.1 openssl.1 passwd.1 | pkcs12.1 pkcs7.1 pkcs8.1 rand.1 req.1 rsa.1 rsautl.1 s_client.1 s_server.1 sess_id.1 smime.1 speed.1 spkac.1 verify.1 version.1 x509.1 | bio.3 blowfish.3 bn.3 bn_internal.3 buffer.3 crypto.3 d2i_DHparams.3 d2i_RSAPublicKey.3 des.3 dh.3 dsa.3 err.3 evp.3 hmac.3 lh_stats.3 lhash.3 | md5.3 mdc2.3 OPENSSL_VERSION_NUMBER.3 OpenSSL_add_all_algorithms.3 rand.3 rc4.3 ripemd.3 rsa.3 sha.3 ssl.3 threads.3 config.5 des_modes.7 |
For more information on OpenSSL see the OpenSSL Web Site.
The openssh package has been updated to version 3.7.1.p2 of OpenSSH. OpenSSH is a suite of network connectivity tools that encrypts all traffic to effectively eliminate eavesdropping, connection hijacking, and other network-level attacks. OpenSSH provides a variety of secure tunneling capabilities and authentication methods. SSH protocol versions 1.3, 1.5, and 2.0 are supported.
The OpenSSH suite includes:
Manual pages are provided for all of the above commands, as well as pages for the ssh_config(5) and sshd_config(5) SSH client and server configuration files. To display them, use the man(1) command or DocView on http://hostname:8458. For more information on OpenSSH, please go to the OpenSSH Web Site http://www.openssh.org/manual.html.
NOTE: You should install OpenSSL from the Update Pack before installing OpenSSH, even if you have a previous version of OpenSSL already installed.
Updated manual pages and online guides are provided by the uw7upman and uw7updoc packages, as well as some of the other packages included with the Update Pack. Both guides and manual pages can be viewed using any browser via the DocView Documentation Server. By default, DocView can be reached at http://hostname:8458, where hostname is the network node name of the UnixWare system, or localhost when using a browser on your UnixWare 7 system. The browser can be running on native UnixWare, on the Linux Kernel Personality (LKP), or on the OpenServer Kernel Personality (OKP). The manual pages can also be viewed using the man(1) command; this must be done from a UnixWare shell. (The man commands under LKP and OKP display the manual pages installed in those environments, not the UnixWare 7 pages.)
Newly added documentation will not be searchable using DocView's Search button until indexing is run. This is done, by default, at 3:10AM local time by a root crontab(1) entry. If this time is not appropriate for your site, you can edit the crontab entry to change the time indexing is run. In general, it is a good idea to run indexing when the system load is low, since indexing can consume considerable time and system resources, depending on the amount of text being indexed. You can also run indexing manually using the /usr/lib/docview/conf/rundig command after you finish installing documentation from the Update Pack.
Current UnixWare Documentation can also be viewed on the Internet at http://www.sco.com/support/docs/unixware.
CUPS has been updated to version 1.1.19_01 to correct problems displaying the names of USB printers in the graphical administrative interface. See CUPS and the Printing topic in the online documentation.
The foomatic package contains a generic filter and PPD files for various printer models. The filter and PPD files are integrated with the cups package (see CUPS), and cannot be used with the System V LP print system. Note that the CUPS package also provides its own PPD files.
This updated version of foomatic (3.0.0-01) includes the following:
For more information, see the Printing topic in the online documentation after you install cups and foomatic.
The gimpprint package contains a suite of high-quality printer drivers for use with the cups and foomatic packages; see the notes for CUPS. The gimpprint package includes:
The core driver (libgimpprint.so).
A CUPS driver primarily for Canon and Epson printers (along with some Lexmark and Hewlett-Packard models), and the corresponding PostScript Printer Definition (PPD) files. These PPD files appear as follows in the CUPS administrative web interface:
EPSON model CUPS+Gimp-print v4.2.5
Try these PPD files before trying the IJS-based drivers (below).
An IJS-based GhostScript driver (for use with foomatic) and corresponding PPD files. These PPD files appear as follows in the CUPS administrative web interface:
Epson model Foomatic/gimp-print-ijs
A utility to administer Epson printers, escputil.
Documentation for this driver is installed with the gimpprint package under Printing in the online documentation.
The Hewlett-Packard InkJet Driver (hpijs) is a printer driver for for more than 200 printer models, including, DeskJet, OfficeJet, Photosmart, Business InkJet and some LaserJet models. The hpijs package also contains PostScript Printer Definition (PPD) files for these printers, for use with the cups and foomatic packages. (See the notes for CUPS.) These PPDs appears as follows in the CUPS administrative web interface.
HP model Foomatic/hpijs (recommended) (en)
It is recommended that you use these PPD files even if there are other Foomatic PPDs for your printer model, for example:
HP model Foomatic/pcl3 (en)
The hpijs driver also provides PPD files for some non-HP printers. The list of these printers can be found at: http://www.linuxprinting.org/show_driver.cgi?driver=hpijs. Documentation for this driver is installed with the hpijs package under Printing in the online documentation.
Prior to this release, only one Universal Serial Bus (USB) printer connected to the system at one time was supported. In addition to supporting multiple USB printers, this release also provides fixes to some known problems. See Printing: USB Support for an overview of USB printer support. These updates are in the udienv and usb packages.
SCO Web Services is a set of application programming interfaces that use standard web technologies such as WSDL, SOAP, XML, and XML Schemas to enable your applications to interface with Web Services. The web services supported by SCOx enable applications to exchange data directly over the internet, without human intervention. Such applications can be anything from simple requests to complex business processes.
The web services and libraries are available on a separate CD image. Release notes and installation instructions can be found at the top level of the CD image, and on the UnixWare Supplements Web Page. Also see the SCO Web Services Web Site.
Please Note: You must install the Update Pack Set before you install the Web Services CD. Please read the Release Notes from the CD or Supplements Page before installing the Web Services CD.
Also note that there are some known issues with using the web services support for Java when Java 1.4.2 has been installed. Please see the SCO Java 2 Standard Edition v. 1.4.2_03 Release Notes for more details. Also note that when using web services support for C or C++, you should compile with the UDK C or C++ compiler, and not with the Open Source Tools gcc or g++ compilers.
The zlib package contains version 1.2.1 of the data compression library (/usr/lib/libz.so). The zlib Manual from http://www.zlib.net is available as a manual page; enter man zlib or use the Man Pages button in the online documentation. Note that the version 1.1.4 manual is still the current manual for zlib.
Samba provides filesharing capabilities using native Microsoft SMB and CIFS protocols for interoperability with Microsoft operating systems. Samba 3.0 is provided in a single-byte version for Western locales (samba); a multibyte version suitable for Asian locales will be made available in a future release.
Note the following when installing Samba:
If you are upgrading from a previous release of Samba on UnixWare, save a copy of your existing /usr/lib/samba/lib/smb.conf file before you begin installation, so you can restore any settings that might be affected by the upgrade.
By default, /tmp is automatically shared. This can be a security concern, since various system utilities keep temporary data in /tmp. To remove the /tmp share, log into SWAT (see above) and select the Shares icon. On the next screen, highlight the tmp share in the list box and select the Delete Share button.
Samba cannot run together with Advanced File and Print Sharing (AFPS; found on the Optional Services CD #3), nor with the NetBIOS protocol running. If Samba will not start, do the following to determine if AFPS or NetBIOS are running, and disable them if necessary:
Enter:
# cd /etc/rc2.d
S74netbios S99ms_srv
If these one or both of these files exist, enter the appropriate command or commands shown below:
# mv S74netbios s74netbios # mv S99ms_srv s99ms_srv
# shutdown -i6 -g0 -y
Start Samba:
# /etc/init.d/samba start
Samba documentation and manual pages are available under the DOS and Windows topic in the online documentation.
Samba is configured with the SWAT (Samba Web Administration Tool) utility using a web browser on http://hostname:901. To start SWAT:
As root, enter:
# /usr/lib/samba/sbin/swat
Point a web browser at http://localhost:901.
Log in to SWAT as root.
The main SWAT screen provides links to all the Samba documentation. Select the Status icon to start the Samba daemons.
To start, stop, and restart Samba from the command line, use the /etc/init.d/samba command, as in this example:
# /etc/init.d/samba start
To enable Samba at system startup, enter the following:
# /etc/init.d/samba enable
Samba will now start up automatically whenever the system boots. The disable parameter returns Samba to manual startup.
Localization settings are accessed from the SWAT Home Page by clicking on the Globals tab, and then selecting Advanced View. Set appropriate values for your locale for the client code page, the character encoding system, and the other options (each option has context-sensitive help). Please refer to the documentation for smb.conf for further details.
More Samba documentation and other resources are provided on the Samba Home Page.
© Copyright 2004 The SCO Group, Inc. All rights reserved.