Www.sco.com 1 SCO OpenServer 6 Tech Overview SCO OpenServer 6 - City to City Tour 2005 Roberto Zini - Strhold Evolution Division

1www.sco.comwww.strhold.it

SCO OpenServer 6 Tech Overview

SCO OpenServer 6 - City to City Tour 2005

Roberto Zini - Strhold Evolution Division

2

SCO OpenServer Release 6 Overview

• Code-named “Legend”

• A multi-year, multi-million dollar development effort to produce one of the most significant upgrades to OpenServer in the past decade

• Integrated UNIX System V kernel technology

• Application binary compatibility for OpenServer 5.x – OpenServer 6 and UnixWare 7.1.4

3

SCO OpenServer 6 Overview

• Contains the hardenedUNIX System V kernel

• Single certification for both OpenServer 6.x and UnixWare 7.1.x

• New platform, storage, and new driver certifications

• Runs thousands of applications written for UNIX, Java, PostgreSQL, mySQL, KDE and Web Services

4

Customer Benefits of OpenServer 6

New SVR5 Kernel• SCO OpenServer Release 6 brings to users a powerful, new and

modern operating system with large file support, filesystem improvements and kernel-level threading for greater application support

Get work done faster• Significantly faster and increased performance• Multi processor support increased from 4 to 16 processors• Increased Memory Support – up to 64 GB• Dynamic loadable drivers

Work with thousands of UNIX applications, as well as…• Thousands of applications written for MySQL, PostgreSQL,

Apache, Tomcat, and the latest version of Java• SCO’s Web Services Substrate technologies integrated to make

“green screen” apps available in a Web environment Work in a secure environment

• Includes latest security enhancements, including SSH, OpenSSL, IP Filter, IPsec, Encrypted File System

5

What can you expect

The rock-solid stability, excellent reliability you're used to with previous OpenServer5 releases

OpenServer 5.0.7 applications as well as UnixWare applications will run on OpenServer 6 without specific portings

OpenServer 6 will provide much broader hardware support

OpenServer 6 continues our focus on Security, Reliability and Value

6

SCO OpenServer 6 System Requirements

Hardware Minimum

Recommended

Maximum

CPU Pentium Pentium P4 32 CPUs

Memory 128Mb 256Mb 16Gb/64Gb

Disk Space

1Gb 4Gb HBA Dependen

t

HBA IDE SCSI or SATA 32


SCO OpenServer 6 Features

8

SCO OpenServer 6 – new Features

Features new to OpenServer 6 [1]:• New SVR5 Kernel that delivers [1]:

• Advanced fine grained locking• excellent scaling to 16 CPUs – supports 32 (OSR507=4)

• Support for up to 16Gb General Purpose Memory (OSR5=4Gb)

• Support via PSE for up to 64Gb using shm/dshm • Large File Support up to 1Tb (OSR507 = 2Gb)• Improved Disk I/O Performance• Improved Network Stack Performance• Improved SMP and Load Balancing• Kernel Threads • Dynamically Loadable Modules• Hyperthreading

9



• Dynamic Add Memory Support • Hot Plug CPU • Hot Plug PCIx • Veritas Journalling Filesystem• IPsec and VPN• MPIO• NIC Failover• Automatic Tuning at boot time• SAN Support (MSA1000)

10



• Fiberchannel HBA Support (Qlogic qlc2300 HBA)• Prism II Wireless Nic Support (pcpms driver)• Centrino Wireless NIC Support• Improved AIO (not compatible with OpenServer 5 AIO)• AC97 support for i845 chipset for applications that do

not expect opensound driver.

• USB Printing support• automatic disk/tapes recognition (no need for “mkdev

hd”)

11


Features new to OpenServer 6 [4]:• SCOAdmin FTP Manager• SCOAdmin Hot Plug Manager • SCOAdmin Printer Manager can invoke CUPS

Admin• Network Install/Media Less Install (Not in

Beta)• KDE Desktop Release 3• X.org X11R6 X Server

• Greater device support• Improved performance

12


Features new to OpenServer 6 [5]:• Emergency Recovery CD/DVD

• no floppies but who uses them nowadays ?

• Boot Splash Screen replaces Hardware Listing• DocView support the Print Book Option in

Postscript and PDF format• DocView content changed from Book to Topic

format• Extended Shells (bash, zsh and tcsh)• foomatic, ghostscript and hpijs• lsof, vim and xpdf

13

SCO OpenServer 6 – updated Features

Updated Features in OpenServer 6 [1]:• Updated Web Services Components

• Perl 5.8.5• Apache 1.3.33 (docview) with

• mod_perl 1.29 • mod_ssl 2.8.22

• Mozilla 1.7.8 • Tomcat 4.1.31• Squid 2.5Stable7

14


Updated Features in OpenServer 6 [2]:• Updated Networking Components

• Samba 3.0.13• NFS v3• Sendmail 8.13.x (but use whatever you want !)• OpenSSH & OpenSSL

• Updated Database Components• Postgresql 7.4 (Version 8 available soon after FCS)• MySQL 4.1.10

• CDRecord DVD Pro v 2.01.01a01

15


Major Kernel Difference [1]:• Dynamically loadable modules:

• Allows loading of drivers without a kernel relink and reboot

• modadmin –s to list loaded modules• modadmin –l <mod_name> to load a module• Modules held in:

/etc/conf/mod.d• To make a module static:

Add “$static” to /etc/conf/sdevice.d/<mod_name> Relink the kernel

• Modules can be removed from the loaded set by the kernel to save resources (eg, RAM)

16


Major Kernel Difference [2]:

• Kernel Relink• Linking is deferred by default until reboot

• Kernel Autotuning• Kernel tunables are set based on amount of memory

detected at boot• See Autotune(4) for more details

• All UW and OSR5 Device Names provided• OSR5 takes precedence if there is a clash

17


Major Filesystem Differences [1]:• Support for following filesystems:

• VXFS• HTFS (no journalling)• EAFS (boot filesystem)• AFS and S51k• dosfs supporting DOS, VFAT, FAT 12, FAT16, FAT32(New)• cdfs supporting JOILET(New), Rockridge, ISO9660 and High

Sierra• Raw Slice/Division• Memfs (Improved)• NFS

• Xenix and DTFS filesystem types not supported

18


Major Filesystem Differences [2]:• VXFS Filesystem Supports:

• > 64k inodes• File size up to 1Tb

• Encrypted filesystems supported using marry(ADM)

• Support for up to 15 divisions/slices per partition

• /stand is mounted read/write• fdisk(ADM) now supports writing of

Masterboot

19


Major Filesystem Differences [3]:• both SCSI & IDE follows the very same naming

scheme• /dev/[r]dsk/c#b#t#d#s# • /dev/[r]dsk/c#b#t#d#p#

• where:• # is a hex number (0-F)• c# is the SCSI/IDE controller number of the device (starting from

0)• b# is the HBA bus number (SCSI) - always 0 for IDE devices• t# is the SCSI ID number - for IDE, 0 = master, 1 = slave• d# is the SCSI LUN - always 0 for IDE• s# is the slice number• p# is the partition number, where p0 means the whole disk

20


Steps to create an Encrypted filesystem [1]: • Create a regular file with appropriate

permissions• touch <regfile>

• Create a mount point with the correct permissions

• mkdir <mount_point>

• Create the block special device using marry(ADM)

• cryptfs=`marry –a –b blksz –c “passphrase” regfile`• Note 5 of the blksz blocks (512 bytes) are used for

encryption information

21


Steps to create an Encrypted filesystem [2]:

• Make a filesystem on the marry device using:• mkfs -f vxfs $cryptfs blksz-5

• Mount the filesystem on the mountpoint using:

• mount $cryptfs <mount_point>

22


Examples of accelerated networking: NFS v3 [1]

• Version 2 clients can access only the lowest 2GB of a file (signed 32 bit offset).

• Version 3 clients support larger files (up to 64 bit offsets). Maximum file size depends on the NFS server's local file systems.

• NFS Version 2 limits the maximum size of an on-the-wire NFS read or write operation to 8KB (8192 bytes).

• NFS Version 3 over UDP theoretically supports up to 56KB (not to mention you can have NFS over TCP with version 3)

23



• NFS Version 2 requires that a server must save all the data in a write operation to disk before it replies to a client that the write operation has completed.

• This can be expensive because it breaks write requests into small chunks (8KB or less) that must each be written to disk before the next chunk can be written.

• Disks work best when they can write large amounts of data all at once.

24



• NFS Version 3 introduces the concept of "safe asynchronous writes."

• A Version 3 client can specify that the server is allowed to reply before it has saved the requested data to disk, permitting the server to gather small NFS write operations into a single efficient disk write operation.

• A Version 3 client can also specify that the data must be written to disk before the server replies, just like Version 2 does

25



• "Seeing is believing" test 1:

• NFS writing from a client box to a shared folder on SCO OS 5.0.7 and 6.0.0 of a 100MB archive on a PIII-700Mhz, 128MB, Intel Pro 10/100 network card using a crossed network cableSCO OS 5.0.7 SCO OS 6.0.0NFS 20.52 seconds (1) 8.78 seconds (3)

23.94 seconds (2)

(1) NFS writes completely Asynch'd (2) NFS writes mostly Asynch'd (kernel hack)

(3) NFS v3 over TCP/IP (default configuration)

26


Examples of accelerated I/O: VxFS filesystem [1]

• VxFS uses the intent logging feature:

• before committing an I/O request to disk, the filesystem writes it to a “circular log” (journal)

• if there’s a crash, on startup the system examines the log searching for pending operations and committing them if necessary

• result: a much faster filesystem check which has only to check the log file instead of the whole filesystem (which gives a faster boot especially for very large filesystem – fsck’s –ofull option still applies if needed)

27




• glimpseindex compiled under SCO OS 5.0.4 and ported "as-is" onto OpenServer 6.0.0

• mission: the reindexing of a 96MB (2700 files) and 400MB (9000 files) archive under the same HW box (old PIII-700, 128MB of RAM, 20GB EIDE HD) with 2 partitions (SCO OS 5.0.7 HTFS and 6.0.0 VxFS)

SCO OS 5.0.7 SCO OS 6.0.096MB 166 seconds 92 seconds

400MB 865 seconds 305 seconds

28




• given the above 400MB folder, create a tar file on the local (root) filesystem

• under SCO OS 5.0.7, the filesystem is HTFS• under SCO OS 6.0.0, the filesystem is the new VxFS

SCO OS 5.0.7 SCO OS 6.0.0TAR 647 seconds 213 seconds

29


Examples of enhanced I/O: large fs (LFS) [1]

• LFS enabled by default of Root filesystem is vxfs

• Check that LFS its enabled using:• fsadm / (should report unlimited)

• To allow for the creation of large files run:• ulimit unlimited

• Applications from OSR5 must be ported to take advantage of LFS

• Use open64(S) instead of open(S)• Use stat64(S) instead of stat(S) etc

30


Examples of enhanced I/O: large fs (LFS) [2]

• Test Large Filesystem Support using:• dd if=/dev/zero of=big bs=1024k count=2100 • ls -l big

• Utilities 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(1), 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) are found in /u95/bin

31

SCO OpenServer 6 Commands & utils

Command and Utility Differences [1]:• OpenServer 6 contains:

• Many OpenServer 5 commands and utilities Some are redundant (e.g. badblk(ADM) )

Some updated OpenServer 5 commands and utilities e.g. cpio(C) now handles large files

Some new commands and utilities e.g. sdiadd(ADM) supports a new features of OSR6

Some SVR5 commands for compatibility with UnixWare

These are found in /udk/bin Some LFS commands that are not OSR5 compatible

These are found in /u95/bin

32


Command and Utility Differences [2]:

• pstat(C) has been removed, use crash(ADM) instead

• kprf(ADM) and kprpt(ADM) replaced by prfstat(ADM), prfsnap(ADM) and prfpr(ADM)

• The following commands are obsolete:• eisa(ADM), pipe(ADM), pipestat(ADM) and tickadj(ADM)• badblk(ADM) and badtrk(ADM) dkinit(ADM)

33


Command and Utility Differences [3]:

• Large Filesystem Aware commands will all be based on UnixWare commands with exception of cpio(C)

• SCO OpenServer 6 PATH recommendation:• /bin - traditional OSR5 user• /u95/bin:/bin - traditional OSR5 user who wants

LFS• /udk/bin:/u95/bin:/bin- users running a UW7 app

34

SCO OpenServer 6 post FCS

Features being considered post FCS:

• In-place Upgrade• Network Install• Merge 5 with VNET, Audio, Winsock2 & WinXP support• Java 1.5• OpenServer 6 Replication Kit • Online Data Manager (ODM)• Reliant HA• SCOadmin DNS Manager


Sample screenshots

36

OpenServer Boot splash screen

37

OpenServer graphical Login Screen

38

OpenServer Online Help

You can access the online help either local or from any remote webclient

http://machine:8457

39

Printbook – create your PDFs from Help

The Printbook feature in the SCO Online help allows to create PDF Files for certain chapters or topics of the SCO Openserver documentation

40

KDE3.3 is provided as alternative Desktop

/etc/default/X11 allows to switch between old XDT3 and KDE3

41

Webbrowser and Email Client - Mozilla 1.7.8

42

Scoadmin – Software Manager

The admin tools you are familiar with

43

OpenServer 5.0.7 apps are available

old scomail runs on OpenServer 6

44

System Certification Suite

45


46



SCO OpenServer 6 - City to City Tour 2005

Roberto Zini - Strhold Evolution Division

Documents

Www.sco.com 1 SCO OpenServer 6 Tech Overview SCO OpenServer 6 - City to City Tour 2005 Roberto Zini - Strhold Evolution Division