Upgrading to the Power of OpenServer 6

1. Upgrading to the Power of OpenServer 6

2. Agenda • Migrating from OSR5 • Changes to be aware of • Configuring the new features • SCO Global Services

3. Migrating from OSR5 • Hardware configuration • User accounts • Mail • User and application data • Network configuration

4. Migrating Hardware Configuration • The new SVR5 kernel should recognize and automatically configure all your hardware devices – you no longer need to manually configure hardware devices • Sound Cards: • only Intel ICH4 and prior chipsets that comply with the AC’97 standard are supported at this time – they will be detected and automatically configured at boot • Printers: • use the Printer Manager to re-create your printer setup

5. Migrating Hardware Configuration • Serial Cards: • All supported serial cards are now auto-detected at boot, you no longer need to add or configure them in the Serial Manager • However, you must run the Serial Manager at least once to create the devices nodes and configure the ports controlled by the serial cards before you can start using them • Serial cards with 3rd party drivers will need a new SVR5 driver • Modems: • Configured as usual through the Modem Configuration Manager • PC Card (PCMCIA) modems must be configured using the DCU

6. Migrating Hardware Configuration • Mass Storage Devices: • should be auto-detected and configured at boot time – use the DCU to configure HBAs that were not auto-detected • use mkdev hd to view detected hard disks and configure filesystems on them (or run fdisk and divvy manually) • use mkdev cdrom to view detected CD-ROM drives • use mkdev tape to view detected tape drives. Most tape drives supported on OSR5 are also supported on OSR6 except some floppy-tape (QIC-80) devices

7. Migrating Hardware Configuration – Device Nodes • In general OSR6 supports both OSR5-style and SVR5-style (UnixWare) device nodes • For hard disk nodes, a combination is used: • Partitions are OSR5-style: • /dev/[r]hdXYX is the physical disk number • /dev/dsk/XsYY is the partition number • Divisions (slices) are SVR5-style: • /dev/[r]dsk/cXbXtXdXsZ • /dev/[r]dsk/cXbXtXdXpYsZ • X is the SCSI address as output by /etc/scsi/sdiconfig –l • Y is the partition number • Z is the division (slice) number

8. Migrating User Accounts • Archive accounts and group membership on the OSR5 system: • ap –d -g –v > profile.acct • Restore the accounts on the OSR6 system. OSR5 and OSR6 treat long passwords differently, so there are two methods for restoring your account details: • truncate the long passwords to 8 characters: • ap –r –f profile.acct • specify a new default password for all accounts with long passwords only: • ap –r –f profile.acct –p password

9. Migrating Mail • User inboxes: • copy /usr/spool/mail from OSR5 to /var/mail on the OSR6 system • MMDF configuration: • copy only the following files from OSR5 to the OSR6 system: • /usr/mmdf/mmdtailor • /usr/mmdf/table/*.chn • /usr/mmdf/table/*.dom • /usr/mmdf/table/alias.* • /usr/spool/mmdf/lock/home/q.* • on the OSR6 system, enter the following commands: • su mmdf • cd /usr/mmdf/table • ./dbmbuild • exit

10. Migrating Mail • SendMail configuration: • merge the contents of the OSR5 configuration files with the new OSR6 files, do not simply copy them:

11. Migrating Mail • To preserve vacation notifications and custom forwarding, copy the following files from each user’s home directory • MMDF: • ~/.maildelivery • ~/.alter_egos • ~/tripnote • ~/triplog • SendMail: • ~/.forward • ~/.vacation.msg

12. Migrating User Data • You can migrate your user data either via a backup tape or mounting the existing OSR5 disk on OSR6 • Creating a backup tape is the recommended method because it allows you to restore to a VxFS filesystem and take advantage of large file support • Either use a 3rd party backup solution that is supported on both platforms (eg. BackupEdge or LoneTar) or use the cpio command • To restore an OSR5 cpio archive on OSR6: • cpio –iAmudB –I<backup_device>

13. Migrating User Data – Mount OSR5 disk • To mount an existing OSR5 disk (5.0.6 or 5.0.7 only), you must first install the wd Supplement on the OSR5 system • Connect the drive to the OSR6 system • After booting, login as root and run the command getlclfsdevto determine the /dev/dsk device nodes for the filesystems on the disk • Use the Filesystem Manager to mount the filesystems

14. Migrating Networking • The loopback interface is no longer presented in the Network Configuration Manager • The “Add New WAN Connection” menu item has been removed from the Network Configuration Manager • SCO PPP is no longer supported, PPP is provided by Morning Star PPP • SLIP is no longer supported • Netware and IPX/SPX are no longer supported

15. Migrating Networking: TCP/IP • On the OSR5 system, use the netstat –rn command and note the hostname, domain name, IP address, netmask, broadcast address and frame type of the existing network interfaces • On the OSR6 system, enter these values at ISL or via the Network Configuration Manager after ISL • Migrate the following configuration files (merge with existing files, do not simply copy):

16. Migrating Networking: DHCP • To migrate your DHCP Server configuration, copy /etc/inet/dhcpd.conf to the OSR6 system • To migrate your Address Allocation Server (AAS) configuration, copy /etc/inet/aasd.conf to the OSR6 system

17. Migrating Networking: Routing • gated and routed have been updated in OSR6. The new routed adds RIPv2 support and both can do router discovery • The new command rtquery allows you to query the routing daemons and provides additional control over routed • Migrate the following configuration files:

18. Migrating Networking: DNS • DNS has been updated to BIND 8.4.4 in OSR6, which includes security fixes and new features • Copy the following configuration files: • Then use the ndc restart command to restart named

19. Migrating NIS • NIS is unchanged in OSR6 • There are no configuration files to migrate over (assuming you already migrated over the user accounts using ap). • Run the ypinit command to configure NIS: • -m configure as a master server • -s master configure as a slave server • -c master configure as a copy-only server • -C configure as a client

20. Migrating UUCP • UUCP is unchanged in OSR6 • Copy the following configuration files: • /usr/lib/uucp/Devices • /usr/lib/uucp/Permissions • /usr/lib/uucp/Poll • /usr/lib/uucp/Systems

21. Migrating an FTP Server • ftpd has been updated to version 2.4 in OSR6, it includes security fixes and additional features • New FTP Server Manager can be used to configure ftpd • Migrate the following configuration files:

22. Migrating NFS • NFS has been updated to NFSv3 in OSR6, its substantially different from the NFSv2 in OSR5 • automount no longer looks at the NIS auto.master map file unless the following line is added to /etc/auto.master • +auto.master • Use the information in the OSR5 configurations files to edit the OSR6 files, you cannot simply copy the configuration files from OSR5 to OSR6:

23. Migrating NTP • NTP is basically the same on OSR5 and OSR6 • The default configuration file (ntp.conf) is the same on both platforms, but is now located in /etc/inet/ntp.conf instead of /etc/ntp.conf • You will also need to copy over any files containing authentication keys and create any log files defined in ntp.conf

24. Migrating PPP • SCO PPP has been replaced by SCO Morning Star PPP • There is no graphical administration tool for Morning Star PPP • If you were already using Morning Star PPP on OSR5, you can simply copy the following files: • /usr/lib/mstppp/Autostart • /usr/lib/mstppp/Accounts • /usr/lib/mstppp/Auth • /usr/lib/mstppp/Systems • /usr/lib/mstppp/Devices • /usr/lib/mstppp/Dialers.local • /usr/lib/mstppp/exec.in/* • /usr/lib/mstppp/exec.out/*

25. Migrating PPP • To migrate from SCO PPP to Morning Star PPP, save the following files from the OSR5 system for reference: • /etc/ppphosts • /etc/pppauth • For outbound connections: • use the host entries in the OSR5 /etc/ppphosts file when editing the /usr/lib/mstppp/Systems OSR6 file • use the PAP/CHAP information in the OSR5 /etc/pppauth file for the /usr/lib/mstppp/Auth OSR6 file • For inbound connections: • use the host entries in the OSR5 /etc/ppphosts file when editing the /usr/lib/mstppp/Accounts OSR6 file • use the PAP/CHAP information in the OSR5 /etc/pppauth file for the /usr/lib/mstppp/Auth OSR6 file

26. Changes from OSr5 • ISL and system startup • Kernel • Console • X Server and desktops • Filesystems • System administration • Commands • Documentation

27. Changes – ISL • OSR6 uses the “no-emulation” boot cd method instead of “floppy-emulation” – may not work with very old systems that only support floppy-emulation • Supports installing above 1024 cylinders/8GB boundary • Prompts for installing additional HBAs during ISL • Supports HBAs on CDs in addition to floppies • Can defer licensing to get an eval license (press <F8> on the license screen) • A mouse can be configured and tested during ISL • The date and time can be set during ISL • Video cards are no longer configured during ISL, they are autodetected and configured on first reboot

28. Changes – System Startup • OSR6 autoboots by default with a [boot] prompt with a twenty-second countdown instead of the Boot: prompt in OSR5 • A graphical SCO OpenServer Release 6 logo replaces the hwconfig-style hardware listing • /etc/inittab is built from /etc/conf/init.d/kernel instead of /etc/conf/cf.d/init.base • OSR6 is SMP-ready out of the box • Auto-detects multiple CPUs at boot • Licensing controls how many can be utilized • Hyper-threaded and multi-core CPUs need just one license • Enter PSM=atup at the boot prompt to force uni-processor only • NOTE: the /etc/default/boot parameters have changed considerably, see boot(HW) for details

29. Changes – Kernel • Dynamically loadable drivers: • Allows loading of drivers without a kernel relink and reboot • modadmin -s lists the loaded drivers • modadmin -l mod_name loads a driver • Drivers are located in /etc/conf/mod.d • Kernel linking is deferred by default until reboot, use /etc/conf/bin/idbuild -B to build the kernel immediately • Kernel is autotuned based on the amount of memory detected at boot • OSR5 drivers will not work with the new kernel, must use SVR5 drivers • /dev/table and /dev/strings no longer present, use hw(ADM) and sdiconfig(ADM) to view hardware configuration

30. Changes – Kernel • scodb has been replaced with the kdb kernel debugger • Managing multi-processors has changed: • psradm(ADM) for processor configuration • psrinfo(ADM) for displaying processor information • rtpm(ADM) for performance monitoring • pbind(ADM) for locking a process to a specific CPU • processors are numbered from 0 instead of 1

31. Changes – Console • Console termtype has changed from scoansi to at386-ie • Applications with “hard wired” scoansi escape sequences will not work directly on the OSR6 console (but will work in a scoterm or remote login from an OSR5 system) • Applications that use terminfo/termcap will work just fine

32. Changes – X Server • OSR6 has a brand new X Server: X.org X11R6 • It is configured via /etc/xorg.conf • Most video cards are automatically detected and the X Server attempts to use the highest possible resolution for your video card and monitor • If you are having trouble getting the X server to run at a good resolution, try editing /etc/xorg.conf to enter the exact horizontal and vertical refresh rates for your monitor: • Section “Monitor” • HorizSync 31.5 – 60 • VertRefresh 40 - 60

33. Changes – Desktops • In addition to the OSR5 xdt3 desktop, OSR6 has the new KDE desktop • xdt3 desktop is the default • Switch to the KDE desktop for all users by changing XDESKTOP in /etc/default/X11: • XDESKTOP=kde3 • Individual users can specify their desktop preference by setting XDESKTOP in their shell startup scripts • Valid values are “xdt3” or “kde3” – they are defined in /etc/default/xdesktops, so you can add additional desktop options to this file

34. Changes – Filesystems • OSR6 updates support for the following filesystems: • VxFS (new – supports large files, the default root filesystem) • HTFS (updated – journaling and versioning no longer supported) • CDFS (replaces HS filesystem, updated to support Joliet) • DOSFS (updated to support FAT32 and VFAT) • MEMFS (new – memory/RAM filesystem) • NFS (updated to v3) • All the filesystems now support up to 16 divisions per partition and can be encrypted via the new -c option to the marry(ADM) command • The DTFS and XENIX filesystems are no longer supported

35. Changes – Filesystems • The Virtual Disk Manager is no longer supported • AFPS is no longer supported, it has been replaced by Samba • divvy now supports up to 15 user-defined divisions on each partition • badblk & badtrk commands removed, their operations are now handled transparently by the system • dparam & dkinit commands removed, you can no longer change or override the hard disk parameters, they will always be as set by the system BIOS

36. Changes – Large File Support • Only supported on the VxFS filesystem • Enabled by default • Commands that are Large File Aware: • cat(1), du(1), pathchk(1), chgrp(1), ff(1M) • pax(1), chmod(1), find(1), pwd(1), chown(1) • fsck(1M), cksum(1), fsdb(1M), rm(1) • cmp(1), ln(1), rmdir(1), compress(1), ls(C), sum(1) • cp(1), mkdir(1), rcp(1), touch(1), cpio(1), mkfs(1M), ulimit(1) • dd(1M), mv(1), uncompress(1), df(1M), ncheck(1M), zcat(1) • cpio(C) • All except cpio(C) and ls(C) are found in /u95/bin • Note: no shell support for LFS

37. Changes – System Administration • The following SCOadmin Managers have been removed: • Audit Manager • Backup Manager • Internet Manager • Virtual Domain User Manager • Audio Manager • ISA PnP Configuration Manager • PPP Manager • PPP Connection Wizard • sysadmsh • all IPX/SPX-related managers • all NetWare-related managers

38. Changes – System Administration • New FTP Server Manager for configuring ftpd, including one-click setup of anonymous FTP • New Hot Plug Manager for managing Hot Plug devices (memory, CPUs. etc) • New Video Configuration Manager based on xorgcfg(1) • The License Manager “Add Users/CPUs/Products” menu items replaced by a single “Add License” option. Plus it only shows licenses installed on the system, it no longer shows unlicensed products. • most mkdev scripts are no longer needed and display information only • See also the “OSR6 Diagnostics and Troubleshooting” presentation (Room 103, 3pm Tues)

39. Changes – Web • Netscape FastTrack Server no longer supported, replaced by Apache 1.3 • Netscape Communicator no longer supported, replaced by Mozilla

40. Changes – Commands • OSR6 distributes basic system commands into three main directories: • For different behaviors, set your PATH as follows:

41. Changes – Documentation • Online documentation no longer organized by books, but by topics, which allows for tighter integration of third-party documentation • DocView can now print an entire topic instead of just a single section • select which sections you want and DocView will display all the selected sections as one page for printing from the browser • can also elect to generate a PDF or postscript file

42. Configuring new features • CUPS • Samba • mySQL • PostgreSQL • Multi-path I/O

43. Configuring CUPS Printers • To use just CUPS: • edit /etc/default/lpd • PRINTER_SYSTEM=CUPS • the Printer Manager will automatically launch the CUPS web-based administration tool • login as root and use root’s password • To use both CUPS and SYSV lp (default) : • edit /etc/default/lpd • PRINTER_SYSTEM=SYSV • the Printer Manager will manage the SYSV lp printers and to configure CUPS printers, enter the following URL in a browser: • http://localhost:631 • login as root and use root’s password • NOTE: the CUPS administration tool only allows alpha-numeric characters in the password, so you will have to change root’s password if it contains non-alphanumeric characters

44. Configuring Samba • Initial configuration is done via mkdev samba: • workgroup name • WINS configuration • Security Domain or Active Directory configuration • Enable and activate Samba daemon • The Samba configuration file can be found in /etc/samba/smb.conf • For much more info, go to the “Installing and Configuring Samba 3” presentation(Room 104, 10:15am Tues)

45. Configuring mySQL • Initial configuration is done via mkdev mysql: • define the mysql database owner and password • enable/disable the server • stop/start the server processes • define the database location and initialize the database • The mysql(1) command provides a curses-based client for connecting to a mySQL database • The mysqladmin(1) command provides some administration options • The mySQL configuration file can be found in /etc/my.cnf

46. Configuring PostgreSQL • Initial configuration is done via mkdev pgsql: • define the postmaster owner and password • enable/disable the server • stop/start the server processes • define the database location and initialize the database

47. Multi-Path I/O • MPIO allows multiple HBAs to be connected to the same hard disk • Usually requires either a dual-ported device or some form of networked storage • Provides redundancy, availability and load balancing • A path is associated with a disk stamp and SCSI address • OSR6 recognizes if a target has multiple access paths by enumerating different disk SCSI addresses with the same disk stamp • Disabled by default, turn on with mkdev mpio • Administered using sdipath(ADM)

48. SCO Global Services • SCO Services Capabilities • Professional Services and Consulting for OpenServer 6 • Bundled Support • Education • Why SCO Services

49. SCO Services Capabilities • Global reach • 24x7 Follow the Sun • Award winning capability • High level expertise • “One stop shop” for professional services, consulting and support

50. OpenServer 6 Implementation Services MAINTENANCE AND SUPPORT TRAINING DEPLOYMENT PORTING ASSESSMENT