Tech Insider					     Technology and Trends


			      USENET Archives

From: swine@iinet.net.au (Peter Swain)
Newsgroups: comp.os.linux.announce
Subject: SCO filesystem patches for 1.3.xx kernel
Date: Wed, 02 May 1996 20:58:46 GMT
Organization: iiNet Technologies
Approved: linux-announce@news.ornl.gov (Lars Wirzenius)
Message-ID: < cola-liw-831070726-10015-0@liw.clinet.fi>
Summary: sysv filesystem now groks SCO
Keywords: SCO filesystem sysv module


i've patched Bruno Haible's sysv filesystem to handle SCO

sco_fs.lsm entry follows .....

Begin3
Title:          sco_fs: patches to allow read/write of SCO filesystems
Version:        0.1
Entered-date:   960501
Description:	
    Here's few patches to the sysv_fs and genhd.c to allow use on SCO filesystems.

    SCO differs from the basic sysv4 filesystem in several areas:
    -	'divvy' partitons
		SCO has its own unique brand of extended fdisk partition,
    -	AFS filesystem
		like sysv4, but using bitmaps instead of the chained free-list
		of blocks (though the inode freelist is unchanged).
    -	Extended File Names
		The sysv (SCO calls it S51K) and AFS filesystems may be
		'extended' to handle names up to 255 chars (rather than 14).
		These filesystem types are called ES51K and EAFS.

    SCO3's default filesystem type is EAFS, but if you convert filesystems
    to ES51K, it runs fine (just saying 'Extended File System' instead of
    'Extended Fast Filesystem' when it does an fsck).
    Don't know about SCO5, i've never met one.

    I've addressed these differences as follows:
    -    CONFIG_SCO_DISKLABEL adds 'divvy' support,
	    recognising divvy partitions on a sco-formatted drive,
    -    EAFS & AFS filesystems can be mounted read-only,
    -    Extended names are handled throughout, so the 14-char limit
	    disappears, and any long names which appeared fragmented under 
	    the old filesys now join up again.
    -	EAFS (SCO3 default) filesystems can be converted to ES51K,
	    and mounted read-write, allowing them to be used by both
	    SCO and linux.
	    Using the initrd package, you can even boot both systems
	    off the one root-filesystem (no, i haven't included an example)
Keywords:       SCO filesystem divvy sysv
Author:         swine@iinet.net.au (peter swain)
Maintained-by:  swine@iinet.net.au (peter swain)
Primary-site:   ftp.iinet.net.au:/incoming/linux/sco_fs/* (20K)
		ftp.iinet.net.au:~swine/sco_fs ??
		maybe moving, but i'll keep you informed
Alternate-site: 
Copying-policy: GPL
End



-- 
This article has been digitally signed by the moderator, using PGP.
Finger wirzeniu@kruuna.helsinki.fi for PGP key needed for validating signature.
Send submissions for comp.os.linux.announce to: linux-announce@news.ornl.gov
PLEASE remember a short description of the software and the LOCATION.

			        About USENET

USENET (Users’ Network) was a bulletin board shared among many computer
systems around the world. USENET was a logical network, sitting on top
of several physical networks, among them UUCP, BLICN, BERKNET, X.25, and
the ARPANET. Sites on USENET included many universities, private companies
and research organizations. See USENET Archives.

		       SCO Files Lawsuit Against IBM

March 7, 2003 - The SCO Group filed legal action against IBM in the State 
Court of Utah for trade secrets misappropriation, tortious interference, 
unfair competition and breach of contract. The complaint alleges that IBM 
made concentrated efforts to improperly destroy the economic value of 
UNIX, particularly UNIX on Intel, to benefit IBM's Linux services 
business. See SCO vs IBM.

The materials and information included in this website may only be used
for purposes such as criticism, review, private study, scholarship, or
research.

Electronic mail:			       WorldWideWeb:
   tech-insider@outlook.com			  http://tech-insider.org/