1. 1 Reseller Webinar Jay Petersen April 8, 2003

2. Slide 2 Announcing the creation of… A new organization in SCO with the charter to create new licensing programs for our UNIX intellectual property

3. Slide 3 SCO’s History The invention of UNIX at Bell Labs SCO establishes UNIX on Intel Unix Systems Laboratories source code and UnixWare acquired by SCO in 1995 Merges with SCO in 2001 Develops UNIX derivatives Xenix, OpenServer, bringing UNIX to the Intel volume market and setting the stage for Linux 1994 Caldera established to develop commercial Linux distribution 1979 1969 2003SCO establishes SCOsource

4. Slide 4 Why license SCO’s Intellectual Property?  Customers are requesting it  Increase shareholder value through existing IP  Strengthen Linux by licensing value-add IP  Increase UNIX application use on Linux

5. Slide 5 First Deliverable  SCO’s UNIX Shared Libraries from for use with Linux  Already in use among many enterprise customers  Already encouraged by many Linux vendors  Increases the number of UNIX applications available to Linux Upcoming Plans for SCOsource SCO System V for Linux

6. Slide 6 Example: OpenServer Application Environment OpenServer System Calls OpenServer Kernel OpenServer Application OpenServer Shared Libraries

7. Slide 7 Native Linux Application Environment Linux System Calls Linux Kernel Linux Application Linux Shared Libraries

8. Slide 8 Linux for Native and OpenServer Applications Linux System Calls Linux Kernel OpenServer System Calls Linux ABI OpenServer Application OpenServer Shared Libraries Linux Application Linux Shared Libraries

9. Slide 9 UNIX application details: Object File Formats  There are two object file formats that have been used in UNIX  COFF: original format (SVR2, SVR3, SVR4)  ELF: improved format introduced around 1990  Early versions of SCO UNIX (3.2v4.2, OpenDesktop, etc) used COFF only  OpenServer supports both COFF and ELF  UnixWare supports only ELF  Linux native mode is also ELF

10. Slide 10 UNIX application details: Library Usage  Libraries must match object file format of application (COFF or ELF)  ELF libraries are dynamically linked  COFF libraries may be statically linked  UNIX applications can be created to use shared system libraries or to incorporate the libraries they need (self-contained)  Standard practice is to use shared libraries  Reduces application size on disk  Reduces overall system memory usage  Allows library maintenance to be de-coupled from app

11. Slide 11 SCO System V for Linux Release 1 SCO UNIX Runtime Libraries  First release includes COFF static shared libraries from OpenServer  Compatible with SCO UNIX, OpenDesktop, all versions of OpenServer  Packaged as an rpm installable on Linux  License required and enforced (at install time) on non-SCO Linux systems

12. Slide 12 Customer benefits  Preserves investment in legacy applications  Application licenses  End user training  Applications integration  Same application runs on UNIX and Linux  Allows migration of applications to Linux even if source is not available  Permits movement to Linux without requiring simultaneous upgrade or conversion of apps  Cost effective evaluation of Linux in production environment

13. Slide 13 Why start with OpenServer COFF static libraries?  Most customer interest (some large accounts)  Linux ABI Project interest/development focussed on SCO COFF applications  Largest base of applications for SCO platforms  Oldest legacy applications  Probably not the ISV’s latest release  Upgrade to Linux versions would be painful  Source code may not be available  Nonetheless, apps may be firmly entrenched in customers business practice

14. Slide 14 What about UnixWare Libraries?  Next step is to investigate value and feasibility  Customer demand?  UnixWare apps are newer, more likely to get ported?  More compatible with Linux versions?  Confirm Linux ABI functionality  Not much discussion in Linux ABI project  UnixWare libraries are a much larger set than the COFF static libraries  Need to test some applications

15. Slide 15 Availability & Delivery Customer Pricing: $149 per processor Volume pricing available at standard SCO discounts SCO Linux Server 4.0 includes a SCO System V for Linux license at no charge via SCO Update Delivery is via Download Only SCO Supports the SSVL Support for the Linux ABI is same as any other Linux feature

16. Slide 16 Obtaining SCO System V for Linux  SCO Linux Customers  Registered SCO Linux customer will be notified of availability of ssvl via email  Available via SCO Linux Update service  Two step process (run from shell as root):  run “apt-get update” (updates the apt database)  run “apt-get install ssvl” (downloads and installs ssvl)  ssvl rpm will silently install (it verifies that it is being installed on a SCO Linux system)

17. Slide 17 Summary: SCO System V for Linux  License for SCO OpenServer Libraries on Linux  Aimed at current users of SCO UNIX applications  Key message is investment preservation  Free value add for SCO Linux users  Available for non-SCO Linux distributions  Enables solution migration opportunities