diff options
| author | Jordan K. Hubbard <jkh@FreeBSD.org> | 1999-09-04 08:46:32 +0000 |
|---|---|---|
| committer | Jordan K. Hubbard <jkh@FreeBSD.org> | 1999-09-04 08:46:32 +0000 |
| commit | 13a407b04466555f96b3285ae5aa1d887e517ccc (patch) | |
| tree | 7caf0a61e260ec09e5c79eabe9d44aac0f7a7b6d /release | |
| parent | 15f39ed3be2e66228bd84c5e644bf8b34f49befc (diff) | |
Notes
Diffstat (limited to 'release')
| -rw-r--r-- | release/Makefile | 33 | ||||
| -rw-r--r-- | release/boot_crunch.conf.generic | 4 | ||||
| -rw-r--r-- | release/boot_crunch.conf.pccard | 4 | ||||
| -rw-r--r-- | release/fixit_crunch.conf | 4 | ||||
| -rwxr-xr-x | release/scripts/dokern.sh | 3 | ||||
| -rwxr-xr-x | release/scripts/proflibs-install.sh | 5 | ||||
| -rw-r--r-- | release/texts/ABOUT.TXT | 8 | ||||
| -rw-r--r-- | release/texts/HARDWARE.TXT | 147 | ||||
| -rw-r--r-- | release/texts/INSTALL.TXT | 529 | ||||
| -rw-r--r-- | release/texts/RELNOTES.TXT | 8 | ||||
| -rw-r--r-- | release/texts/UPGRADE.TXT | 14 | ||||
| -rw-r--r-- | release/texts/XFREE86.TXT | 1584 |
12 files changed, 203 insertions, 2140 deletions
diff --git a/release/Makefile b/release/Makefile index 4907392139ab..e80b0932dc2b 100644 --- a/release/Makefile +++ b/release/Makefile @@ -232,6 +232,8 @@ rerelease release: .endif .if defined(ALLLANG) echo "export ALLLANG=${ALLLANG}" >> ${CHROOTDIR}/mk +.else + echo "export DOC_LANG=en_US.ISO_8859-1" >> ${CHROOTDIR}/mk .endif .if defined(NOSRC) echo "export NOSRC=${NOSRC}" >> ${CHROOTDIR}/mk @@ -259,7 +261,6 @@ rerelease release: echo "cd /usr/src/release/sysinstall" >> ${CHROOTDIR}/mk echo "make obj" >> ${CHROOTDIR}/mk echo "cd /usr/src/release" >> ${CHROOTDIR}/mk - echo "make obj" >> ${CHROOTDIR}/mk echo "make \$${_RELTARGET}" >> ${CHROOTDIR}/mk echo "echo make ${.TARGET} Finished" >> ${CHROOTDIR}/mk chmod 755 ${CHROOTDIR}/mk @@ -299,7 +300,7 @@ release.1: release.2: cd ${.CURDIR}/../etc && make distrib-dirs DESTDIR=${RD}/trees/bin cd ${.CURDIR}/.. && make distribute DISTDIR=${RD}/trees -.if exists(${.CURDIR}/../kerberosIV) && !defined(NOKERBEROS) +.if exists(${.CURDIR}/../kerberosIV) && exists(${.CURDIR}/../crypto) && !defined(NOKERBEROS) cd ${.CURDIR}/../kerberosIV && ( \ make bootstrap &&\ make obj all help-distribute DISTDIR=${RD}/trees &&\ @@ -428,10 +429,12 @@ release.7: fi && shift && shift ; \ done .endif +.if exists(${RD}/dists/des) ( cd ${RD}/dists/src && \ if [ -f ssecure.aa ] ; then mv ssecure.* ../des ; fi && \ if [ -f scrypto.aa ] ; then mv scrypto.* ../des ; fi && \ if [ -f skerbero.aa ] ; then mv skerbero.* ../des ; fi ; ) +.endif @echo "src distribution is finished." .endif touch release.7 @@ -459,9 +462,11 @@ release.8: write_mfs_in_kernel @cd ${.CURDIR} && $(MAKE) installCRUNCH CRUNCH=boot \ DIR=${RD}/mfsfd/stand ZIP=false ( cd ${RD}/trees/bin/dev && \ - ls console tty ttyv0 ttyv1 ttyv2 ttyv3 null zero ${CARDDEV} | \ + ls console tty bpf0 ttyv0 ttyv1 ttyv2 ttyv3 null zero ${CARDDEV} | \ cpio -dump ${RD}/mfsfd/dev ) ( cd ${RD}/mfsfd/dev && rm -f *[swo]d*[bdefgh] ) + ( cd ${RD}/mfsfd && mkdir -p bin sbin && ln -s /stand/sh bin/sh ) + cp /sbin/dhclient-script ${RD}/mfsfd/sbin .if ${PCCARD} == "YES" cp ${.CURDIR}/../etc/pccard.conf.sample ${RD}/mfsfd/etc/pccard.conf .endif @@ -536,7 +541,13 @@ ftp.1: @mkdir -p ${FD} @cd ${RD} && find floppies -print | cpio -dumpl ${FD} @cd ${RD}/dists && find . -print | cpio -dumpl ${FD} - @for i in ${DIST_DOCS}; do if [ -f ${.CURDIR}/texts/${MACHINE_ARCH}/$$i ]; then cp ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ${FD}; else cp ${.CURDIR}/texts/$${i} ${FD}; fi; done + @for i in ${DIST_DOCS}; do \ + if [ -f ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ]; then \ + cp ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ${FD}; \ + else \ + cp ${.CURDIR}/texts/$${i} ${FD}; \ + fi; \ + done @echo "CD_VERSION = ${BUILDNAME}" > ${FD}/cdrom.inf .if !defined(NOPORTS) @tar --exclude CVS -cBf - -C ${CD_DISC1} ports | tar -xBf - -C ${FD} @@ -563,7 +574,13 @@ cdrom.1: @cp ${.CURDIR}/fixit.profile ${CD_DISC2}/.profile @echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC1}/cdrom.inf @echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC2}/cdrom.inf - @for i in ${DIST_DOCS}; do cp ${.CURDIR}/texts/$${i} ${CD_DISC1}; done + @for i in ${DIST_DOCS}; do \ + if [ -f ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ]; then \ + cp ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ${CD_DISC1}; \ + else \ + cp ${.CURDIR}/texts/$${i} ${CD_DISC1}; \ + fi; \ + done .if !defined(NOPORTS) @-rm -rf /usr/ports/distfiles/* @mkdir -p ${CD_DISC1}/ports && \ @@ -577,7 +594,7 @@ doc.1: @for i in ${DOCPORTS}; do \ cd /usr/ports/$$i && make all install clean JADETEX=no FORCE_PKG_REGISTER=yes; \ done - @cd /usr/doc && make all distribute DISTDIR=${RD}/trees + @cd /usr/doc && make all install 'FORMATS=html html-split txt' INSTALL_COMPRESSED='' DOCDIR=${RD}/trees/bin/usr/share/doc touch doc.1 # Various "subroutine" and other supporting targets. @@ -679,8 +696,8 @@ doKERNEL: @cd ${.CURDIR}/../sys/${MACHINE_ARCH}/conf && config ${KERNEL} @cd ${.CURDIR}/../sys/compile/${KERNEL} && \ make depend && \ - make kernel && \ - cp kernel ${RD}/kernels/${KERNEL} + make ${KERNEL} && \ + cp ${KERNEL} ${RD}/kernels/${KERNEL} # # --==## Put a filesystem into a BOOTMFS kernel ##==-- diff --git a/release/boot_crunch.conf.generic b/release/boot_crunch.conf.generic index 2a80d5ed5a3f..5500f4c890a0 100644 --- a/release/boot_crunch.conf.generic +++ b/release/boot_crunch.conf.generic @@ -3,14 +3,16 @@ srcdirs /usr/src/bin /usr/src/sbin /usr/src/release /usr/src/usr.bin srcdirs /usr/src/gnu/usr.bin /usr/src/usr.sbin /usr/src/sbin/i386 -progs sh find +progs sh find sed test progs pwd ppp progs sysinstall newfs minigzip cpio bad144 fsck ifconfig route slattach progs mount_nfs +progs dhclient arp ln minigzip gzip ln minigzip gunzip ln minigzip zcat ln sh -sh +ln test [ libs -ll -ledit -lutil -lkvm -lmd -lcrypt -lftpio -lz libs -ldialog -lncurses -lmytinfo -L/usr/src/release/libdisk/obj -ldisk -lipx diff --git a/release/boot_crunch.conf.pccard b/release/boot_crunch.conf.pccard index 795836bdf4fe..4c773ffee3dc 100644 --- a/release/boot_crunch.conf.pccard +++ b/release/boot_crunch.conf.pccard @@ -4,16 +4,18 @@ srcdirs /usr/src/bin /usr/src/sbin /usr/src/release /usr/src/usr.bin srcdirs /usr/src/gnu/usr.bin /usr/src/usr.sbin /usr/src/sbin/i386 srcdirs /usr/src/usr.sbin/pccard -progs sh find rm +progs sh find sed test rm progs pwd ppp progs sysinstall newfs minigzip cpio bad144 fsck ifconfig route slattach progs mount_nfs +progs dhclient arp progs pccardc pccardd progs wicontrol ln minigzip gzip ln minigzip gunzip ln minigzip zcat ln sh -sh +ln test [ libs -ll -ledit -lutil -lkvm -lmd -lcrypt -lftpio -lz libs -ldialog -lncurses -lmytinfo -L/usr/src/release/libdisk/obj -ldisk -lipx diff --git a/release/fixit_crunch.conf b/release/fixit_crunch.conf index 7c467bf45307..c6a1ee9e7875 100644 --- a/release/fixit_crunch.conf +++ b/release/fixit_crunch.conf @@ -14,7 +14,7 @@ srcdirs /usr/src/sbin/i386 # /bin stuff progs cat chmod chroot cp date dd df echo ed expr hostname kill ln ls mkdir -progs mt mv pwd rcp rm rmdir sleep stty sync test +progs mt mv pwd rm rmdir sleep stty sync test ln test [ @@ -32,7 +32,7 @@ ln chown chgrp # /usr/bin stuff -progs ftp more rsh sed telnet rlogin vi find grep +progs ftp more sed telnet vi find grep ln vi view ln vi ex diff --git a/release/scripts/dokern.sh b/release/scripts/dokern.sh index 3564cbdae0e7..5d6b7eb0aa68 100755 --- a/release/scripts/dokern.sh +++ b/release/scripts/dokern.sh @@ -11,6 +11,9 @@ sed -e '/pty/d' \ -e '/SYSVMSG/d' \ -e 's/GENERIC/BOOTMFS/g' +# So dhclient will work (just on boot floppy). +echo "pseudo-device bpfilter 4" + echo "options NFS_NOSERVER" echo "options SCSI_NO_OP_STRINGS" echo "options SCSI_NO_SENSE_STRINGS" diff --git a/release/scripts/proflibs-install.sh b/release/scripts/proflibs-install.sh index ce410e388805..fa67ec78c626 100755 --- a/release/scripts/proflibs-install.sh +++ b/release/scripts/proflibs-install.sh @@ -5,4 +5,9 @@ if [ "`id -u`" != "0" ]; then exit 1 fi cat proflibs.?? | tar --unlink -xpzf - -C ${DESTDIR:-/} +cd ${DESTDIR:-/}usr/lib +if [ -f libdescrypt_p.a ] +then + ln -f -s libdescrypt_p.a libcrypt_p.a +fi exit 0 diff --git a/release/texts/ABOUT.TXT b/release/texts/ABOUT.TXT index 3be70e08059f..b42f23ffc335 100644 --- a/release/texts/ABOUT.TXT +++ b/release/texts/ABOUT.TXT @@ -21,9 +21,11 @@ environment that extends far beyond what's provided by many commercial versions of UNIX. For more documentation on this system it is recommended that you -purchase the 4.4BSD Document Set from O'Reilly Associates and the -USENIX Association, ISBN 1-56592-082-1. We have no connection with -O'Reilly, we're just satisfied customers! +purchase The Complete FreeBSD, available from local bookstores +and from the FreeBSD Mall (http://www.freebsdmall.com), as well +as the 4.4BSD Document Set from O'Reilly Associates and the USENIX +Association, ISBN 1-56592-082-1. We have no connection with O'Reilly, +we're just satisfied customers! If you're new to FreeBSD then you should also read EVERYTHING listed in the Documentation menu on the boot floppy. It may seem like a lot diff --git a/release/texts/HARDWARE.TXT b/release/texts/HARDWARE.TXT index 39d77e872431..a0f00b285ced 100644 --- a/release/texts/HARDWARE.TXT +++ b/release/texts/HARDWARE.TXT @@ -94,11 +94,11 @@ ed0 280 10 dyn d8000 WD & SMC 80xx; Novell NE1000 & eg0 310 5 dyn dyn 3Com 3C505 ep0 300 10 dyn dyn 3Com 3C509 ex0 dyn dyn dyn n/a Intel EtherExpress Pro/10 cards -fe0 300 dyn n/a n/a Allied-Telesis AT1700, RE2000 and +fe0 300 dyn n/a n/a Allied-Telesyn AT1700, RE2000 and Fujitsu FMV-180 series cards. fxp0 dyn dyn n/a dyn Intel EtherExpress Pro/100B ie0 300 10 dyn d0000 AT&T StarLAN 10 and EN100; - 3Com 3C507; NI5210; + 3Com 3C507; NI5210; Intel EtherExpress (8/16,16[TP]) cards le0 300 5 dyn d0000 Digital Equipment EtherWorks 2 and EtherWorks 3 @@ -329,7 +329,7 @@ ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. -Adaptec 274X/284X/2920C/2930U2/294x/2950/3940/3950 (Narrow/Wide/Twin) series +Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. @@ -367,6 +367,7 @@ SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, Tekram DC390W, 390U and 390F Tyan S1365 + QLogic 1020, 1040, 1040B and 2100 SCSI and Fibre Channel Adapters DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -428,7 +429,7 @@ AIC-6915 fast ethernet controller chip, including the following: ANA-69011 32-bit single port 10/100baseTX adapter ANA-62020 64-bit single port 100baseFX adapter -Allied-Telesis AT1700 and RE2000 cards +Allied-Telesyn AT1700 and RE2000 cards Alteon Networks PCI gigabit ethernet NICs based on the Tigon 1 and Tigon 2 chipsets, including the following: @@ -462,7 +463,7 @@ Lite-On 82c168/82c169 PNIC fast ethernet NICs including the following: NetGear FA310-TX Rev. D1 Matrox FastNIC 10/100 Kingston KNE110TX - + Macronix 98713, 98713A, 98715, 98715A and 98725 fast ethernet NICs NDC Communications SFA100A (98713A) CNet Pro120A (98713 or 98713A) @@ -478,7 +479,11 @@ Winbond W89C840F fast ethernet NICs including the following: VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast ethernet NICs including the following: Hawking Technologies PN102TX - D-Link DFE530TX + D-Link DFE-530TX + +Sundance Technologies ST201 PCI fast ethernet NICs including +the following: + D-Link DFE-550TX SysKonnect SK-984x PCI gigabit ethernet cards including the following: SK-9841 1000baseLX single mode fiber, single port @@ -549,7 +554,135 @@ still waiting for someone to donate a driver for one of them. Any takers? -4.3. Misc +4.3. USB +---- --- + +A range of USB peripherals are supported. Owing to the generic nature +of most USB devices, with some exceptions any device of a given class +will be supported even if not explicitly listed here. + +USB keyboards. + +USB mice. + +USB printers and USB to parallel printer conversion cables. + +USB hubs. + + +Motherboards chipsets: + +ALi Aladdin-V. + +Intel 82371SB (PIIX3). +Intel 82371AB and EB chipsets (PIIX4). + +NEC uPD 9210 Host Controller. + +VIA 83C572 USB Host Controller + +and any other UHCI or OHCI compliant motherboard chipset (no exceptions +known). + + +PCI plug-in USB host controllers: + +ADS Electronics PCI plug-in card (2 ports). + +Entrega PCI plug-in card (4 ports). + + +Specific devices reported to be working: + +Agiler Mouse 29UO. + +Andromeda hub. + +Apple iMac mouse. +Apple iMac keyboard. + +ATen parallel printer adapter. + +Belkin F5U002 parallel printer adapter. +Belkin Mouse. + +BTC BTC7935 keyboard with mouse port. + +Cherry G81-3504 keyboard. + +Chic mouse. + +Cypress mouse. + +Entrega USB-to-parallel printer adapter. + +Genius Niche mouse. + +Iomega USB Zip 100Mb. + +Kensington Mouse-in-a-Box. + +Logitech M2452 keyboard. +Logitech wheel mouse (3 buttons). +Logitech PS/2 / USB mouse (3 buttons). + +MacAlly mouse (3 buttons). +MacAlly self powered hub (4 ports). + +Microsoft IntelliMouse (3 buttons). +Microsoft keyboard. + +NEC hub. + +Trust Ami Mouse (3 buttons). + + +4.4. ISDN (European DSS1 [Q.921/Q.931] protocol) +---- ------------------------------------------- + +Asuscom I-IN100-ST-DV (experimental, may work) +Asuscom ISDNlink 128K PnP + +AVM A1 +AVM Fritz!Card classic +AVM Fritz!Card PnP +AVM Fritz!Card PCI +AVM Fritz!Card PCMCIA + +Creatix ISDN-S0/8 +Creatix ISDN-S0/16 +Creatix ISDN-S0 PnP + +Dr.Neuhaus Niccy 1008 +Dr.Neuhaus Niccy 1016 +Dr.Neuhaus Niccy GO@ (ISA PnP) + +Dynalink IS64PH (no longer maintained) + +ELSA 1000pro ISA +ELSA 1000pro PCI +ELSA PCC-16 + +ITK ix1 micro +ITK ix1 micro PnP + +Sagem Cybermod (ISA PnP, may work) + +Sedlbauer Win Speed + +Siemens I-Surf 2.0 + +Stollmann Tina-pp (under development) + +Teles S0/8 +Teles S0/16 +Teles S0/16.3 (the "c" Versions - like 16.3c - are unsupported !) +Teles S0 PnP (experimental, may work) + +3Com/USRobotics Sportster ISDN TA intern (non-PnP version) + + +4.5. Misc ---- ---- AST 4 port serial card using shared IRQ. diff --git a/release/texts/INSTALL.TXT b/release/texts/INSTALL.TXT deleted file mode 100644 index 304ed0105dc3..000000000000 --- a/release/texts/INSTALL.TXT +++ /dev/null @@ -1,529 +0,0 @@ -+===================== Installing FreeBSD ==========================+ -| | -| Table of Contents: | -| | -| 0.0 Quick Start: | -| 0.1 Installing FreeBSD from CDROM or the Internet. | -| | -| 1.0 Detail on various installation types: | -| 1.1 Installing from a network CDROM | -| 1.2 Installing from Floppies | -| 1.3 Installing from a DOS partition | -| 1.4 Installing from QIC/SCSI tape | -| 1.5 Installing over a network using NFS or FTP | -| 1.5.1 NFS Installation tips | -| 1.5.2 FTP Installation tips | -| 1.6 Tips for Serial COnsole Users | -| | -| 2.0 DOS User's Q&A section. | -| 2.1 How do I make space for FreeBSD? | -| 2.2 Can I use compressed DOS filesystems from FreeBSD? | -| 2.3 Can I use DOS extended partitions? | -| 2.4 Can I run DOS executables under FreeBSD? | -| | -+=====================================================================+ - -Author: Jordan K. Hubbard -Last updated: Tue May 4 16:05:41 PST 1999 - -0.0 Quick Start ---- ----------- - -This manual documents the process of making a new installation of -FreeBSD on your machine. If you are upgrading from a previous -release of FreeBSD, please see the file UPGRADE.TXT for important -information on upgrading. If you are not familiar with configuring -PC hardware for FreeBSD, you should also read the HARDWARE.TXT file - -it contains important information which may save you a lot of grief. - -If you're new to FreeBSD then you should also read EVERYTHING listed -in the Documentation menu of the installer. It may seem like a lot -to read, but the time you spend now reading the documents will be made -up many times over because you were adequately prepared. Also, you will -know the types of information available should you get stuck later. -Once the system is installed, you can also revisit this menu and use a -WEB browser to read the installed FAQ (Frequently Asked Questions) and -Handbook HTML documentation sets for FreeBSD. You can also use the -browser to visit other WEB sites on the net (like http://www.freebsd.org) -if you have an Internet connection. See ABOUT.TXT for more information -on the resources available to you. - -The best laid plans sometimes go awry, so if you run into trouble take a -look at TROUBLE.TXT which contains valuable troubleshooting information. -You should also read ERRATA.TXT before installing and follow the pointers -there carefully since this will stop you from falling over any problems -which have reported in the interim for your particular release. - -DISCLAIMER: While FreeBSD does its best to safeguard against -accidental loss of data, it's still more than possible to WIPE OUT -YOUR ENTIRE DISK with this installation if you make a mistake! Please -do not proceed to the final FreeBSD installation menu unless you've -adequately backed up any important data first! We really mean it! - -FreeBSD requires a 386 or better processor to run (sorry, there is no -support for '286 processors) and at least 5 megs of RAM to install -and 4 megs of RAM to run. You will need at least 100MB of free hard -drive space for the most minimal installation. See below for ways of -shrinking existing DOS partitions in order to install FreeBSD. - - -0.1 Installing FreeBSD from CDROM or the Internet ---- --------------------------------------------- - -The easiest type of installation is from CD. If you have a supported -CDROM drive and a FreeBSD installation CD from Walnut Creek CDROM, -there are 2 ways of starting the installation from it: - - 1. If your system supports bootable CDROM media (usually an option - which can be selectively enabled in the controller's setup menu - or in the PC BIOS for some systems) and you have it enabled, - FreeBSD supports the "El Torrito" bootable CD standard. Simply - put the installation CD in your CDROM drive and boot the system - to begin installation. - - 2. Build a set of FreeBSD boot floppies from the floppies/ - directory in every FreeBSD distribution. Either simply use the - ``makeflp.bat'' script from DOS or read floppies/README.TXT - for more information on creating the bootable floppies under - different operating systems. Then you simply boot from the - first floppy and you should soon be in the FreeBSD installation. - -If you don't have a CDROM and would like to simply install over the -net using PPP, slip or a dedicated connection, simply fetch the -<FreeBSD-release>/floppies/boot.flp file from: - - ftp://ftp.freebsd.org/pub/FreeBSD - -or one of its many mirrors (http://www.freebsd.org/handbook/mirrors.html) -and follow step 3 above. You should also read the floppies/README.TXT -file as it contains important information for downloaders. - -Once you have your boot floppies made, please go to section 1.5 of this -document for additional tips on installing via FTP or NFS. - - -1.0 Detail on various installation types ---- ------------------------------------ - -Once you've gotten yourself to the initial installation screen somehow, -you should be able to follow the various menu prompts and go from there. -If you've never used the FreeBSD installation before, you are also -encouraged to read some of the documentation in the the Documentation -submenu as well as the general "Usage" instructions on the first menu. - - NOTE: If you get stuck at a screen, hit the F1 key for online - documentation relevant to that specific section. - -If you've never installed FreeBSD before, or even if you have, the -"Novice" installation mode is the most recommended since it makes sure -that you'll visit all the various important checklist items along the -way. If you're much more comfortable with the FreeBSD installation -process and know _exactly_ what you want to do, use the Express or -Custom installation options. If you're upgrading an existing system, -use the Upgrade option. - -The FreeBSD installer supports the direct use of floppy, DOS, tape, -CDROM, FTP, NFS and UFS partitions as installation media, further tips -on installing from each type of media listed below. - - -1.1 Installing from a network CDROM ---- ------------------------------- - -If you simply wish to install from a local CDROM drive then see the -Quick Start section. If you don't have a CDROM drive on your system -and wish to use a FreeBSD distribution CD in the CDROM drive of -another system to which you have network connectivity, there are also -several ways of going about it: - -1. If you would be able to FTP install FreeBSD directly from the CDROM - drive in some FreeBSD machine, it's quite easy: You simply add the - following line to the password file (using the vipw command): - - ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin - - And anyone else on your network will now be able to choose a Media - type of FTP and type in: ``ftp://<machine with CDROM drive>'' after - picking "URL" in the ftp sites menu. - -2. If you would rather use NFS to export the CDROM directly to the - machine(s) you'll be installing from, you need to first add an - entry to the /etc/exports file (on the machine with the CDROM drive) - which looks something like this: - - /cdrom -ro ziggy.foo.com - - To allow the machine "ziggy.foo.com" to mount the CDROM directly - via NFS during installation. The machine with the CDROM must also - be configured as an NFS server, of course, and if you're not sure how - to do that then an NFS installation is probably not the best choice - for you unless you're willing to read up on rc.conf(5) and configure - things appropriately. Assuming that this part goes smoothly, you - should be able to enter: cdrom-host:/cdrom as the path for an NFS - installation when the target machine is installed, e.g. wiggy:/cdrom - - -1.2 Installing from Floppies ---- ------------------------ - -If you must install from floppy disks, either due to unsupported -hardware or just because you enjoy doing things the hard way, you must -first prepare some floppies for the install. - -First, make your boot floppies as described in floppies/README.TXT - -Second, read the file LAYOUT.TXT and pay special attention to the -"Distribution format" section since it describes which files you're -going to need to put onto floppy and which you can safely skip. - -Next you will need, at minimum, as many 1.44MB floppies as it takes to -hold all files in the bin (binary distribution) directory. If you're -preparing these floppies under DOS, then THESE floppies *must* be -formatted using the MS-DOS FORMAT command. If you're using Windows, -use the Windows File Manager format command. - -Don't trust Factory Preformatted floppies! Format them again -yourself, just to make sure. Many problems reported by our users in -the past have resulted from the use of improperly formatted media, -which is why I'm taking such special care to mention it here! - -If you're creating the floppies from another FreeBSD machine, a format -is still not a bad idea though you don't need to put a DOS filesystem -on each floppy. You can use the `disklabel' and `newfs' commands to -put a UFS filesystem on a floppy, as the following sequence of -commands illustrates: - - fdformat -f 1440 fd0.1440 - disklabel -w -r fd0.1440 floppy3 - newfs -t 2 -u 18 -l 1 -i 65536 /dev/rfd0 - -After you've formatted the floppies for DOS or UFS, you'll need to -copy the files onto them. The distribution files are split into -chunks conveniently sized so that 5 of them will fit on a conventional -1.44MB floppy. Go through all your floppies, packing as many files as -will fit on each one, until you've got all the distributions you want -packed up in this fashion. Each distribution should go into its own -subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, -a:\bin\bin.ab, ... - -IMPORTANT NOTE: The bin.inf file also needs to go on the first floppy -of the bin set since it is read by the installation program in order -to figure out how many additional pieces to look for when fetching and -concatenating the distribution. When putting distributions onto -floppies, the <distname>.inf file MUST occupy the first floppy of each -distribution set! This is also covered in ABOUT.TXT - -Once you come to the Media screen of the install, select "Floppy" and -you'll be prompted for the rest. - - -1.3 Installing from a DOS partition ---- ------------------------------- - -To prepare for installation from an MS-DOS partition you should simply -copy the files from the distribution into a directory called -"FREEBSD" on the Primary DOS partition ("Drive C:"). For example, to do -a minimal installation of FreeBSD from DOS using files copied from the -CDROM, you might do something like this: - - C:\> MD C:\FREEBSD - C:\> XCOPY /S E:\BIN C:\FREEBSD\BIN - -Assuming that `E:' was where your CD was mounted. - -For as many `DISTS' as you wish to install from DOS (and you have free -space for), install each one in a directory under `C:\FREEBSD' - the -BIN dist is only the minimal requirement. - -Once you've copied the directories, you can simply launch the installation -from floppies as normal and select "DOS" as your media type when the time -comes. - - -1.4 Installing from QIC/SCSI Tape ---- ----------------------------- - -When installing from tape, the installation program expects the files -to be simply tar'ed onto it, so after fetching all of the files for -the distributions you're interested in, simply tar them onto the tape -with a command something like this: - - cd /where/you/have/your/dists - tar cvf /dev/rwt0 (or /dev/rsa0) dist1 .. dist2 - -When you go to do the installation, you should also make sure that you -leave enough room in some temporary directory (which you'll be allowed -to choose) to accommodate the FULL contents of the tape you've -created. Due to the non-random access nature of tapes, this method of -installation requires quite a bit of temporary storage! You should -expect to require as much temporary storage as you have stuff written -on tape. - -SPECIAL NOTE: When going to do the installation, the tape must be in -the drive *before* booting from the boot floppies. The installation -"probe" may otherwise fail to find it. - -Now create a boot floppy as described in section 0.1 and proceed with -the installation. - - -1.5 Installing over a network using FTP or NFS ---- ------------------------------------------ - -After making the boot floppies as described in the first section, you can -load the rest of the installation over a network using one of 3 types -of connections: - - Serial port: SLIP / PPP - Parallel port: PLIP (using ``laplink'' style cable) - Ethernet: A standard Ethernet controller (including - certain PCCARD devices). - -Serial Port ------------ - -SLIP support is rather primitive, and is limited primarily to -hard-wired links, such as a serial cable running between two -computers. The link must be hard-wired because the SLIP installation -doesn't currently offer a dialing capability. If you need to dial out -with a modem or otherwise dialog with the link before connecting to -it, then I recommend that the PPP utility be used instead. - -If you're using PPP, make sure that you have your Internet Service -Provider's IP address and DNS information handy as you'll need to know -it fairly early in the installation process. You may also need to -know your own IP address, though PPP supports dynamic address -negotiation and may be able to pick up this information directly from -your ISP if they support it. - -You will also need to know how to use the various "AT commands" for -dialing out with your particular brand of modem as the PPP dialer -provides only a very simple terminal emulator. - - -Parallel Port -------------- - -If a hard-wired connection to another FreeBSD or Linux machine is -available, you might also consider installing over a "laplink" style -parallel port cable. The data rate over the parallel port is much -higher than what is typically possible over a serial line (up to -50k/sec), thus resulting in a quicker installation. It's not -typically necessary to use "real" IP addresses when using a -point-to-point parallel cable in this way and you can generally just -use RFC 1918 style addresses for the ends of the link (e.g. 10.0.0.1, -10.0.0.2, etc). - -IMPORTANT NOTE: If you use a Linux machine rather than a FreeBSD -machine as your PLIP peer, you will also have to specify "link0" in -the TCP/IP setup screen's ``extra options for ifconfig'' field in -order to be compatible with Linux's slightly different PLIP protocol. - - -Ethernet --------- - -FreeBSD supports most common PC Ethernet cards, a table of supported -cards (and their required settings) being provided as part of the -FreeBSD Hardware Guide (see the Documentation menu on the boot floppy -or the top level directory of the CDROM). If you are using one of the -supported PCMCIA Ethernet cards, also be sure that it's plugged in -_before_ the laptop is powered on! FreeBSD does not, unfortunately, -currently support "hot insertion" of PCMCIA cards during installation. - -You will also need to know your IP address on the network, the -"netmask" value for your address class and the name of your machine. -Your system administrator can tell you which values are appropriate to -your particular network setup. If you will be referring to other -hosts by name rather than IP address, you'll also need a name server -and possibly the address of a gateway (if you're using PPP, it's your -provider's IP address) to use in talking to it. - -If you do not know the answers to these questions then you should -really probably talk to your system administrator _first_ before -trying this type of installation! Using a randomly chosen IP address -or netmask on a live network will almost certainly get you shot at -dawn. - -Once you have a network connection of some sort working, the -installation can continue over NFS or FTP. - - -1.5.1 NFS installation tips ------ --------------------- - - NFS installation is fairly straight-forward: Simply copy the - FreeBSD distribution files you want onto a server somewhere - and then point the NFS media selection at it. - - If this server supports only "privileged port" access (as is - generally the default for Sun and Linux workstations), you - will need to set this option in the Options menu before - installation can proceed. - - If you have a poor quality Ethernet card which suffers from very - slow transfer rates, you may also wish to toggle the appropriate - Options flag. - - In order for NFS installation to work, the server must also support - "subdir mounts", e.g. if your FreeBSD distribution directory lives - on: wiggy:/usr/archive/stuff/FreeBSD - Then wiggy will have to allow the direct mounting of - /usr/archive/stuff/FreeBSD, not just /usr or /usr/archive/stuff. - - In FreeBSD's /etc/exports file this is controlled by the - ``-alldirs'' option. Other NFS servers may have different - conventions. If you are getting `Permission Denied' messages - from the server then it's likely that you don't have this - properly enabled! - - -1.5.2 FTP Installation tips ------ --------------------- - - FTP installation may be done from any mirror site containing a - reasonably up-to-date version of FreeBSD. A full menu of - reasonable choices for almost any location in the world is - provided in the FTP site menu during installation. - - If you are installing from some other FTP site not listed in - this menu, or you are having troubles getting your name server - configured properly, you can also specify your own URL by - selecting the ``URL'' choice in that menu. A URL can - contain a hostname or an IP address, so the following would - work in the absence of a name server: - - ftp://192.216.191.11/pub/FreeBSD - - There are two FTP installation modes you can use: - - o FTP: - - For all FTP transfers, use the standard "Active" mode for - transfers. This will not work through most firewalls but - will often work best with older ftp servers that do not - support passive mode. If your connection hangs with - passive mode, try this one! - - o FTP Passive: - - For all FTP transfers, use "Passive" mode. This allows - the user to pass through firewalls that do not allow - incoming connections on random port addresses. - - NOTE: ACTIVE AND PASSIVE MODES ARE NOT THE SAME AS A `PROXY' - CONNECTIONS, WHERE A PROXY FTP SERVER IS LISTENING ON A - DIFFERENT PORT! - - In such instances, you should specify the URL as something like: - - ftp://foo.bar.com:1234/pub/FreeBSD - - Where "1234" is the port number of the proxy ftp server. - - -1.6 Tips for Serial Console Users ---- ----------------------------- - -If you'd like to install FreeBSD on a machine using just a serial -port (e.g. you don't have or wish to use a VGA card), please follow -these steps. - - 1. Connect some sort of ANSI (vt100) compatible terminal or terminal - emulation program to the COM1 port of the PC you are installing - FreeBSD onto. - - 2. Unplug the keyboard (yes, that's correct!) and then try to boot - from floppy or the installation CDROM, depending on the type of - installation media you have, with the keyboard unplugged. - - 3. If you don't get any output on your serial console, plug - the keyboard in again and wait for some beeps. If you are - booting from the CDROM, proceed to Step 5 as soon as you hear - the beep. - - 4. For a floppy boot, the first beep means to remove the - kern.flp floppy and insert the mfsroot.flp floppy, after - which you should press enter and wait for another beep. - - 5. Hit the space bar, then enter - - boot -h - - and you should now definitely be seeing everything on the - serial port. If that still doesn't work, check your serial - cabling as well as the settings on your terminal emulation - program or actual terminal device. It should be set for - 9600 baud, 8 bits, no parity. - - -2.0 DOS user's Question and Answer section ---- -------------------------------------- - -2.1 Help! I have no space! Do I need to delete everything first? ---- -------------------------------------------------------------- - -If your machine is already running DOS and has little or no free space -available for FreeBSD's installation, all is not lost! You may find -the "FIPS" utility, provided in the tools/ subdirectory on the FreeBSD -CDROM or on the various FreeBSD ftp sites, to be quite useful. - -FIPS allows you to split an existing DOS partition into two pieces, -preserving the original partition and allowing you to install onto the -second free piece. You first "defrag" your DOS partition, using the -DOS 6.xx "DEFRAG" utility or the Norton Disk tools, then run FIPS. It -will prompt you for the rest of the information it needs. Afterwards, -you can reboot and install FreeBSD on the new partition. Also note -that FIPS will create the second partition as a "clone" of the first, -so you'll actually see that you now have two DOS Primary partitions -where you formerly had one. Don't be alarmed! You can simply delete -the extra DOS Primary partition (making sure it's the right one by -examining its size! :) - -NOTE: FIPS does NOT currently work with FAT32 or VFAT style partitions -as used by newer versions of Windows 95. To split up such a partition, -you will need a commercial product such as Partition Magic 3.0. Sorry, -but this is just the breaks if you've got a Windows partition hogging -your whole disk and you don't want to reinstall from scratch. - -2.2 Can I use compressed DOS filesystems from FreeBSD? ---- -------------------------------------------------- - -No. If you are using a utility such as Stacker(tm) or -DoubleSpace(tm), FreeBSD will only be able to use whatever portion of -the filesystem you leave uncompressed. The rest of the filesystem -will show up as one large file (the stacked/dblspaced file!). DO NOT -REMOVE THAT FILE as you will probably regret it greatly! - -It is probably better to create another uncompressed DOS extended -partition and use this for communications between DOS and FreeBSD if -such is your desire. - - -2.3 Can I mount my DOS extended partitions? ---- --------------------------------------- - -Yes. DOS extended partitions are mapped in at the end of the other -``slices'' in FreeBSD, e.g. your D: drive might be /dev/sd0s5, your E: -drive /dev/sd0s6, and so on. This example assumes, of course, that -your extended partition is on SCSI drive 0. For IDE drives, substitute -``wd'' for ``sd'' appropriately. You otherwise mount extended -partitions exactly like you would mount any other DOS drive, e.g.: - -mount -t msdos /dev/sd0s5 /dos_d - - -2.4 Can I run DOS binaries under FreeBSD? ---- ------------------------------------- - -Ongoing work with BSDI's doscmd utility is bringing this much closer to -being a reality in FreeBSD 3.0, though it still has some rough edges. -If you're interested in working on this, please send mail to -emulation@FreeBSD.org and indicate that you're interested in joining -this ongoing effort! - -There is also a neat utility called "pcemu" in the ports collection -which emulates an 8088 and enough BIOS services to run DOS text mode -applications. It requires the X Window System (XFree86) to operate. - ----- End of Installation Guide --- diff --git a/release/texts/RELNOTES.TXT b/release/texts/RELNOTES.TXT index 6ae1908f141a..b90ce95fdaf7 100644 --- a/release/texts/RELNOTES.TXT +++ b/release/texts/RELNOTES.TXT @@ -146,7 +146,7 @@ ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. -Adaptec 274X/284X/2920C/2930U2/294x/2950/3940/3950 (Narrow/Wide/Twin) series +Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. @@ -184,6 +184,7 @@ SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, Tekram DC390W, 390U and 390F Tyan S1365 + QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters. QLogic 2100 Fibre Channel Adapters (private loop only). @@ -335,6 +336,7 @@ Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 ethernet interface. + PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, Winbond W89C940, Surecom NE-34, VIA VT86C926. @@ -431,7 +433,7 @@ Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III -Various Frame grabbers based on Brooktree Bt848 and Bt878 chip. +Various Frame grabbers based on Brooktree Bt848 / Bt878 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. @@ -452,7 +454,7 @@ Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes -(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS). Note: the +(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS). Note: the ISA versions of these adapters are actually PCMCIA cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. diff --git a/release/texts/UPGRADE.TXT b/release/texts/UPGRADE.TXT index 1e90782563f7..8b7b893e2316 100644 --- a/release/texts/UPGRADE.TXT +++ b/release/texts/UPGRADE.TXT @@ -52,8 +52,18 @@ the component over the top of the previous version. Files belonging to the old distribution are not deleted. System configuration is preserved by retaining and restoring the -previous version of a number of files in /etc, some of which -are simply copied back and others of which are merged. +previous version of the following files: + + Xaccel.ini, adduser.conf, aliases, aliases.db, amd.map, crontab, + csh.cshrc, csh.login, csh.logout, daily, disktab, dm.conf, exports, + fbtab, fstab, ftpusers, gettytab, gnats, group, host.conf, hosts, + hosts.equiv, hosts.lpd, inetd.conf, kerberosIV, localtime, login.access, + mail.rc, make.conf, manpath.config, master.passwd, mib.txt, modems, + monthly, motd, namedb, networks, passwd, phones, ppp, printcap, + profile, protocols, pwd.db, rc, rc.firewall, rc.i386, rc.local, + rc.network, rc.conf, remote, resolv.conf, rmt, security, sendmail.cf, + services, shells, skeykeys, spwd.db, supfile, syslog.conf, termcap, + ttys, uucp, weekly The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new diff --git a/release/texts/XFREE86.TXT b/release/texts/XFREE86.TXT deleted file mode 100644 index 9f262384a4e7..000000000000 --- a/release/texts/XFREE86.TXT +++ /dev/null @@ -1,1584 +0,0 @@ - - - - - - - - - - README for XFree86[tm] 3.3.3.1 - - The XFree86 Project, Inc - - 20 December 1998 - - - - Abstract - - XFree86 is a port of X11R6.3 that supports several Unix and Unix-like - operating systems on Intel and other platforms. This release is a - quick update to XFree86 3.3.3, fixing a number of bugs that were - found after releasing it. The release is available as source patches - against the X Consortium X11R6.3 code and the XFree86 3.3.3 release. - Binary distributions for many architectures are also available, - including a binary upgrade for XFree86 3.3.3. - - - -1. What's new in XFree86 3.3.3.1 - -For a summary of new features in this release, please refer to the RELNOTES -file. For a detailed list of changes, refer to the CHANGELOG file in the -source distribution. - - -2. Systems XFree86 has been tested on - -Note: Not all systems listed here have been tested with the current release. - - SVR4.0: - - o Esix: 4.0.3A, 4.0.4, 4.0.4.1 - - o Microport: 2.2, 3.1, 4.1, 4.2 - - o Dell: 2.1, 2.2, 2.2.1 - - o UHC: 2.0, 3.6 - - o Consensys: 1.2 - - o MST: 4.0.3 (Load 2.07 and Load 3.02) - - o ISC: 4.0.3 - - o AT&T: 2.1, 4.0 - - o NCR: MP-RAS - - - - -README for XFree86[tm] 3.3.3.1 1 - - - - - -README for XFree86[tm] 3.3.3.1 2 - - - - o SunSoft: Solaris x86 2.1, 2.4, 2.5, 2.5.1, 2.6 - - o PANIX 5.0 for AT - - - SVR4.2: - - o Consensys - - o Novell/SCO UnixWare - - - SVR3: - - o ISC: 3.0, 4.0, 4.1 - - - Others: - - o NetBSD 1.0, 1.1, 1.2, 1.2.1, 1.3, 1.3.1, 1.3.2, 1.3.3 - - o OpenBSD 2.0, 2.1, 2.2, 2.3, 2.4 - - o FreeBSD 2.0.5, 2.1, 2.1.5, 2.1.6, 2.1.7, 2.1.7.1, 2.2, 2.2.1, - 2.2.2, 2.2.5, 2.2.6, 2,2,7, 2.2.8, 3.0 - - o Linux (Intel x86, DEC Alpha/AXP and m68k) - - o LynxOS AT 2.3.0, 2.4.0, 2.5.0 - - o LynxOS microSPARC 2.4.0, 2.5.0 - - o LynxOS PowerPC 2.4.0, 2.5.0 - - o OS/2 Warp 3 FP5/17/22, Warp 4 -/FP1 - - - PC98: - - o FreeBSD(98) 2.0.5, 2.1, 2.1.5, 2.1.7.1, 2.2, 2.2.1, 2.2.2, - 2.2.5, 2.2.6, 2,2,7, 2.2.8, 3.0 - - o NetBSD/pc98 (based on NetBSD 1.2, 1.2.1, 1.3, 1.3.1, 1.3.2) - - o PANIX 5.0 for 98 - - o Linux/98 - - -3. Supported video-card chip-sets - -At this time, XFree86 3.3.3.1 supports the following chipsets: - - - - - - - - - - -README for XFree86[tm] 3.3.3.1 3 - - - - Ark Logic - ARK1000PV, ARK1000VL, ARK2000PV, ARK2000MT - - Alliance - AP6422, AT24 - - ATI - 18800, 18800-1, 28800-2, 28800-4, 28800-5, 28800-6, 68800-3, - 68800-6, 68800AX, 68800LX, 88800GX-C, 88800GX-D, 88800GX-E, - 88800GX-F, 88800CX, 264CT, 264ET, 264VT, 264GT, 264VT-B, 264VT3, - 264GT-B, 264GT3 (this list includes the Mach8, Mach32, Mach64, 3D - Rage, 3D Rage II and 3D Rage Pro) - - Avance Logic - ALG2101, ALG2228, ALG2301, ALG2302, ALG2308, ALG2401 - - Chips & Technologies - 65520, 65525, 65530, 65535, 65540, 65545, 65546, 65548, 65550, - 65554, 65555, 68554, 69000, 64200, 64300 - - Cirrus Logic - CLGD5420, CLGD5422, CLGD5424, CLGD5426, CLGD5428, CLGD5429, - CLGD5430, CLGD5434, CLGD5436, CLGD5440, CLGD5446, CLGD5462, - CLGD5464, CLGD5465, CLGD5480, CLGD6205, CLGD6215, CLGD6225, - CLGD6235, CLGD6410, CLGD6412, CLGD6420, CLGD6440, CLGD7541(*), - CLGD7543(*), CLGD7548(*), CLGD7555(*) - - Cyrix - MediaGX, MediaGXm - - Compaq - AVGA - - Digital Equipment Corporation - TGA - - Epson - SPC8110 - - Genoa - GVGA - - IBM - 8514/A (and true clones), XGA-2 - - IIT - AGX-014, AGX-015, AGX-016 - - Matrox - MGA2064W (Millennium), MGA1064SG (Mystique and Mystique 220), - MGA2164W (Millennium II PCI and AGP), G100, G200 - - MX - MX68000(*), MX680010(*) - - - - - - - - -README for XFree86[tm] 3.3.3.1 4 - - - - NCR - 77C22(*), 77C22E(*), 77C22E+(*) - - NeoMagic - 2200, 2160, 2097, 2093, 2090, 2070 - - Number Nine - I128 (series I, II and IV), Revolution 3D (T2R) - - NVidia/SGS Thomson - NV1, STG2000, RIVA128, Riva TNT - - OAK - OTI067, OTI077, OTI087 - - RealTek - RTG3106(*) - - Rendition - V1000, V2x00 - - S3 - 86C911, 86C924, 86C801, 86C805, 86C805i, 86C928, 86C864, 86C964, - 86C732, 86C764, 86C765, 86C767, 86C775, 86C785, 86C868, 86C968, - 86C325, 86C357, 86C375, 86C375, 86C385, 86C988, 86CM65, 86C260 - - SiS - 86C201, 86C202, 86C205, 86C215, 86C225, 5597, 5598, 6326 - - 3DLabs - GLINT 500TX, GLINT MX, Permedia, Permedia 2, Permedia 2v - - Tseng - ET3000, ET4000AX, ET4000/W32, ET4000/W32i, ET4000/W32p, ET6000, - ET6100 - - Trident - TVGA8800CS, TVGA8900B, TVGA8900C, TVGA8900CL, TVGA9000, TVGA9000i, - TVGA9100B, TVGA9200CXR, Cyber9320(*), TVGA9400CXi, TVGA9420, - TGUI9420DGi, TGUI9430DGi, TGUI9440AGi, TGUI9660XGi, TGUI9680, Pro- - Vidia 9682, ProVidia 9685(*), Cyber 9382, Cyber 9385, Cyber 9388, - 3DImage975, 3DImage985, Cyber 9397, Cyber 9520 - - Video 7/Headland Technologies - HT216-32(*) - - Weitek - P9000, P9100 - - Western Digital/Paradise - PVGA1 - - Western Digital - WD90C00, WD90C10, WD90C11, WD90C24, WD90C24A, WD90C30, WD90C31, - - - - - - - - -README for XFree86[tm] 3.3.3.1 5 - - - - WD90C33 - -(*) Note, chips marked in this way have either limited support or the drivers -for them are not actively maintained. - -All of the above are supported in both 256 color, and some are supported in -mono and 16 color modes, and some are supported an higher color depths. - -Refer to the chipset-specific README files (currently for TGA, Matrox, Mach32, -Mach64, NVidia, Oak, P9000, S3 (except ViRGE), S3 ViRGE, SiS, Video7, Western -Digital, Tseng (W32), Tseng (all), AGX/XGA, ARK, ATI (SVGA server), Chips and -Technologies, Cirrus, Trident, NeoMagic, Rendition, Epson, 3DLabs) for more -information about using those chipsets. - -The monochrome server also supports generic VGA cards, using 64k of video mem- -ory in a single bank, the Hercules monochrome card, the Hyundai HGC1280, Sigma -LaserView, Visa and Apollo monochrome cards. - -The VGA16 server supports memory banking with the ET4000, Trident, ATI, NCR, -OAK and Cirrus 6420 chipsets allowing virtual display sizes up to about -1600x1200 (with 1MB of video memory). For other chipsets the display size is -limited to approximately 800x600. - - -4. Where to get more information - -Additional documentation is available in the XFree86(1), XF86Config(4/5), -XF86_SVGA(1), XF86_Mono(1), XF86_VGA16(1), XF86_Accel(1), XF86Setup(1) and -xvidtune(1) manual pages. In addition, several README files and tutorial docu- -ments are provided. These are available in /usr/X11R6/lib/X11/doc in the -binary distributions, and in xc/programs/Xserver/hw/xfree86/doc in the source -distribution. - -The files QuickStart.doc and README.Config should be consulted for information -on how to set up the XFree86 servers. All supplied documents, manual pages, -and the XFree86 FAQ <URL:http://www.XFree86.org/FAQ> should be read before con- -tacting the XFree86 team for assistance. - -Documentation on SVGA driver development can be found in the directory -/usr/X11R6/lib/Server/VGADriverDoc in the binary distribution, and in the -directory xc/programs/Xserver/hw/xfree86/VGADriverDoc in the source distribu- -tion. - -If you are totally at a loss, you can contact the XFree86 Support Team at -<XFree86@XFree86.Org>. Before doing so, please make sure that you are using -the latest release of XFree86. Check the versions listed on -ftp://ftp.xfree86.org/pub/XFree86. - -There is a Usenet news group comp.windows.x.i386unix that contains mostly dis- -cussions about XFree86 and related topics. Many questions can be answered -there. - - - - - - - - - - - -README for XFree86[tm] 3.3.3.1 6 - - - -5. Credits - -XFree86 was originally put together by: - - o David Dawes <dawes@XFree86.org> - - o Glenn Lai <glenn@cs.utexas.edu> - - o Jim Tsillas <jtsilla@ccs.neu.edu> - - o David Wexelblat <dwex@XFree86.org> - -XFree86 support was integrated into the base X11R6 distribution by: - - o Stuart Anderson <anderson@metrolink.com> - - o Doug Anson <danson@lgc.com> - - o Gertjan Akkerman <akkerman@dutiba.twi.tudelft.nl> - - o Mike Bernson <mike@mbsun.mlb.org> - - o Robin Cutshaw <robin@XFree86.org> - - o David Dawes <dawes@XFree86.org> - - o Marc Evans <marc@XFree86.org> - - o Pascal Haible <haible@izfm.uni-stuttgart.de> - - o Matthieu Herrb <Matthieu.Herrb@laas.fr> - - o Dirk Hohndel <hohndel@XFree86.org> - - o David Holland <davidh@use.com> - - o Alan Hourihane <alanh@fairlite.demon.co.uk> - - o Jeffrey Hsu <hsu@soda.berkeley.edu> - - o Glenn Lai <glenn@cs.utexas.edu> - - o Ted Lemon <mellon@ncd.com> - - o Rich Murphey <rich@XFree86.org> - - o Hans Nasten <nasten@everyware.se> - - o Mark Snitily <mark@sgcs.com> - - o Randy Terbush <randyt@cse.unl.edu> - - o Jon Tombs <tombs@XFree86.org> - - - - - - - - - -README for XFree86[tm] 3.3.3.1 7 - - - - o Kees Verstoep <versto@cs.vu.nl> - - o Paul Vixie <paul@vix.com> - - o Mark Weaver <Mark_Weaver@brown.edu> - - o David Wexelblat <dwex@XFree86.org> - - o Philip Wheatley <Philip.Wheatley@ColumbiaSC.NCR.COM> - - o Thomas Wolfram <wolf@prz.tu-berlin.de> - - o Orest Zborowski <orestz@eskimo.com> - - 386BSD, FreeBSD, NetBSD support by: - - o Rich Murphey <Rich@XFree86.org> - - NetBSD, OpenBSD support by: - - o Matthieu Herrb <Matthieu.Herrb.@laas.fr> - - Original 386BSD port by: - - o Pace Willison, - - o Amancio Hasty Jr <hasty@netcom.com> - - Mach 386 support by: - - o Robert Baron <Robert.Baron@ernst.mach.cs.cmu.edu> - - Linux support by: - - o Orest Zborowski <orestz@eskimo.com> - - SCO Unix support by: - - o David McCullough <davidm@stallion.oz.au> - - Amoeba support by: - - o Kees Verstoep <versto@cs.vu.nl> - - Minix-386 support by: - - o Philip Homburg <philip@cs.vu.nl> - - OSF/1 support by: - - o Marc Evans <Marc@XFree86.org> - - BSD/OS support by: - - - - - - - - - -README for XFree86[tm] 3.3.3.1 8 - - - - o Hans Nasten <nasten@everyware.se>, - - o Paul Vixie <paul@vix.com> - - Solaris support by: - - o Doug Anson <danson@lgc.com>, - - o David Holland <davidh@use.com> - - ISC SVR3 support by: - - o Michael Rohleder <michael.rohleder@stadt-frankfurt.de> - - LynxOS support by: - - o Thomas Mueller <tmueller@sysgo.de> - - OS/2 support by: - - o Holger Veit <Holger.Veit@gmd.de> - - o Sebastien Marineau <s521936@aix1.uottawa.ca> - - Linux shared libraries by: - - o Orest Zborowski <orestz@eskimo.com>, - - o Dirk Hohndel <hohndel@XFree86.org> - - PC98 support by: - - o Toyonori Fujiura <toyo@ibbsal.or.jp>, - - o Hiroyuki Aizu <aizu@jaist.ac.jp>, - - o Tetsuya Kakefuda <kakefuda@tag.iijnet.or.jp>, - - o Takefumi Tsukada <tsuka@linkt.imasy.or.jp>, - - o H.Komatsuzaki, - - o Naoki Katsurakawa <katsura@prc.tsukuba.ac.jp>, - - o Shuichiro Urata <s-urata@nmit.tmg.nec.co.jp>, - - o Yasuyuki Kato <yasuyuki@acaets0.anritsu.co.jp>, - - o Michio Jinbo <karl@spnet.ne.jp>, - - o Tatsuya Koike <koiket@focus.rim.or.jp>, - - o Koichiro Suzuki <s-koichi@nims.nec.co.jp>, - - - - - - - - - -README for XFree86[tm] 3.3.3.1 9 - - - - o Tsuyoshi Tamaki <tamaki@sail.t.u-tokyo.ac.jp>, - - o Isao Ohishi <ohishi@hf.rim.or.jp>, - - o Kohji Ohishi <atena@njk.co.jp>, - - o Shin'ichi Yairo <QZR00522@niftyserve.or.jp>, - - o Kazuo Ito <ft4k-itu@asahi-net.or.jp>, - - o Jun Sakuma <i931361@jks.is.tsukuba.ac.jp>, - - o Shuichi Ueno <uenos@ppp.bekkoame.or.jp>, - - o Ishida Kazuo <ishidakz@obp.cl.nec.co.jp>, - - o Takaaki Nomura <amadeus@yk.rim.or.jp>, - - o Tadaaki Nagao <nagao@cs.titech.ac.jp>, - - o Minoru Noda <mnoda@cv.tottori-u.ac.jp>, - - o Naofumi Honda <honda@Kururu.math.hokudai.ac.jp>, - - o Akio Morita <amorita@bird.scphys.kyoto-u.ac.jp>, - - o Takashi Sakamoto <sakamoto@yajima.kuis.kyoto-u.ac.jp>, - - o Yasuhiro Ichikawa <cs94006@mbox.sist.ac.jp>, - - o Kazunori Ueno <jagarl@creator.club.or.jp>, - - o Yasushi Suzuki <suz@d2.bs1.fc.nec.co.jp>, - - o Satoshi Kimura <KFB03633@niftyserve.or.jp>, - - o Kazuhiko Uno <Kazuhiko.Uno@softvision.co.jp>, - - o Tomiharu Takigami <takigami@elsd.mt.nec.co.jp>, - - o Tomomi Suzuki <suzuki@grelot.elec.ryukoku.ac.jp>, - - o Toshihiko Yagi <j2297222@ed.kagu.sut.ac.jp>, - - o Masato Yoshida (Contributor of PW805i support) - - Original accelerated code by: - - o Kevin E. Martin <martin@cs.unc.edu>, - - o Rik Faith <faith@cs.unc.edu>, - - o Jon Tombs <tombs@XFree86.org> - - - - - - - - - -README for XFree86[tm] 3.3.3.1 10 - - - - XFree86 Acceleration Architecture (XAA) by: - - o Harm Hanemaayer <H.Hanemaayer@inter.nl.net>, - - S3 accelerated code by: - - o Jon Tombs <tombs@XFree86.org>, - - o Harald Koenig <koenig@tat.physik.uni-tuebingen.de>, - - o David Wexelblat <dwex@XFree86.org>, - - o David Dawes <dawes@XFree86.org>, - - o Robin Cutshaw <robin@XFree86.org>, - - o Amancio Hasty <hasty@netcom.com>, - - o Norbert Distler <Norbert.Distler@physik.tu-muenchen.de>, - - o Leonard N. Zubkoff <lnz@dandelion.com>, - - o Bernhard Bender <br@elsa.mhs.compuserve.com>, - - o Dirk Hohndel <hohndel@XFree86.org>, - - o Joe Moss <joe@XFree86.org> - - S3V accelerated code by: - - o Harald Koenig <koenig@tat.physik.uni-tuebingen.de>, - - o Kevin Brosius <Cobra@compuserve.com> - - o Berry Dijk <berry_dijk@tasking.nl> - - o Dirk Hohndel <hohndel@XFree86.org> - - o Huver Hu <huver@amgraf.com> - - o Dirk Vangestel <gesteld@sh.bel.alcatel.be> - - Mach32 accelerated code by: - - o Kevin E. Martin <martin@cs.unc.edu>, - - o Rik Faith <faith@cs.unc.edu>, - - o Mike Bernson <mike@mbsun.mlb.org>, - - o Mark Weaver <Mark_Weaver@brown.edu>, - - o Craig Groeschel <craig@metrolink.com> - - - - - - - - - -README for XFree86[tm] 3.3.3.1 11 - - - - o Bryan Feir <jenora@istar.ca> - - Mach64 accelerated code by: - - o Kevin E. Martin <martin@cs.unc.edu>, - - Mach8, 8514 accelerated code by: - - o Kevin E. Martin <martin@cs.unc.edu>, - - o Rik Faith <faith@cs.unc.edu>, - - o Tiago Gons <tiago@comosjn.hobby.nl>, - - o Hans Nasten <nasten@everyware.se>, - - o Scott Laird <scott@laird.com> - - Cirrus accelerated code by: - - o Simon Cooper <scooper@vizlab.rutgers.edu>, - - o Harm Hanemaayer <H.Hanemaayer@inter.nl.net>, - - o Bill Reynolds <bill@goshawk.lanl.gov>, - - o Corin Anderson <corina@the4cs.com> - - Western Digital accelerated code by: - - o Mike Tierney <floyd@pepsi.eng.umd.edu>, - - o Bill Conn <conn@bnr.ca> - - P9000 accelerated code by: - - o Erik Nygren <nygren@mit.edu>, - - o Harry Langenbacher <harry@brain.jpl.nasa.gov> - - o Chris Mason <mason@mail.csh.rit.edu> - - o Henrik Harmsen <harmsen@eritel.se> - - AGX accelerated code by: - - o Henry Worth <haworth@wco.com>, - - Number Nine I128 driver by: - - o Robin Cutshaw <robin@XFree86.org>, - - ET4000/W32 accelerated code by: - - - - - - - - - -README for XFree86[tm] 3.3.3.1 12 - - - - o Glenn Lai <glenn@cs.utexas.edu>, - - ET6000 SVGA and accelerated support (both based on the existing W32 code) by: - - o Koen Gadeyne <koen.gadeyne@barco.com>, - - Oak Technologies Inc. accelerated code by: - - o Jorge Delgado <ernar@dit.upm.es>, - - 16 color VGA server by: - - o Gertjan Akkerman <akkerman@dutiba.twi.tudelft.nl> - - 2 color VGA and non-VGA mono servers by: - - o Pascal Haible <haible@izfm.uni-stuttgart.de> - - ATI SVGA driver by: - - o Per Lindqvist <pgd@compuram.bbt.se> and Doug Evans - <dje@cygnus.com>. - - o Ported to X11R5 by Rik Faith <faith@cs.unc.edu>. - - o Rewritten by Marc Aurele La France <tsi@ualberta.ca> - - WD90C24 support by: - - o Brad Bosch <brad@lachman.com> - - Trident SVGA driver by: - - o Alan Hourihane <alanh@fairlite.demon.co.uk> - - SiS SVGA driver by: - - o Alan Hourihane <alanh@fairlite.demon.co.uk> - - o Xavier Ducoin <xavier@rd.lectra.fr> - - DEC 21030 (TGA) server by: - - o Alan Hourihane <alanh@fairlite.demon.co.uk> - - o Harald Koenig <koenig@tat.physik.uni-tuebingen.de> - - NCR SVGA driver by: - - o Stuart Anderson <anderson@metrolink.com> with the permission - of NCR Corporation - - Cirrus SVGA driver by: - - - - - - - - - -README for XFree86[tm] 3.3.3.1 13 - - - - o Bill Reynolds <bill@goshawk.lanl.gov>, - - o Hank Dietz <hankd@ecn.purdue.edu>, - - o Simon Cooper <scooper@vizlab.rutgers.edu>, - - o Harm Hanemaayer <H.Hanemaayer@inter.nl.net>, - - o Corin Anderson <corina@the4cs.com> - - Cirrus CL64xx driver by: - - o Manfred Brands <mb@oceonics.nl> - - o Randy Hendry <randy@sgi.com> - - o Jeff Kirk <jeff@bambam.dsd.ES.COM> - - Compaq SVGA driver by: - - o Hans Oey <hans@mo.hobby.nl> - - o Ming Yu <yum@itp.ac.cn> - - o Gerry Toll <gtoll@tc.cornell.edu> - - Oak SVGA driver by: - - o Steve Goldman <sgoldman@encore.com> - - o Jorge Delgado <ernar@dit.upm.es> - - ARK Logic SVGA driver by: - - o Harm Hanemaayer <H.Hanemaayer@inter.nl.net> - - o Leon Bottou <bottou@laforia.ibp.fr> - - AL2101 SVGA driver by: - - o Paolo Severini <lendl@dist.dist.unige.it> - - Avance Logic ``ali'' SVGA driver by: - - o Ching-Tai Chiu <cchiu@netcom.com> - - Chips & Technologies SVGA driver by: - - o Regis Cridlig <cridlig@dmi.ens.fr> - - o Jon Block <block@frc.com> - - o Mike Hollick <hollick@graphics.cis.upenn.edu> - - - - - - - - - -README for XFree86[tm] 3.3.3.1 14 - - - - o Nozomi Ytow - - o Egbert Eich <Egbert.Eich@Physik.TH-Darmstadt.DE> - - o David Bateman <dbateman@ee.uts.edu.au> - - o Xavier Ducoin <xavier@rd.lectra.fr> - - MX SVGA driver by: - - o Frank Dikker <dikker@cs.utwente.nl> - - Video7 SVGA driver by: - - o Craig Struble <cstruble@acm.vt.edu> - - RealTek SVGA driver by: - - o Peter Trattler <peter@sbox.tu-graz.ac.at> - - Apollo Mono driver by: - - o Hamish Coleman <hamish@zot.apana.org.au> - - Matrox SVGA driver by: - - o Guy Desbief <g.desbief@aix.pacwan.net> - - o Radoslaw Kapitan <kapitan@student.uci.agh.edu.pl> - - o Andrew Vanderstock <vanderaj@mail2.svhm.org.au> - - o Angsar Hockmann <Ansgar.Hockmann@hrz.uni-dortmund.de> - - o Michael Will <Michael.Will@student.uni-tuebingen.de> - - o Andrew Mileski <aem@ott.hookup.net> - - o Stephen Pitts <pitts2@memphisonline.com> - - o Dirk Hohndel <hohndel@XFree86.Org> - - o Leonard N. Zubkoff <lnz@dandelion.com> - - ViRGE SVGA driver by: - - o Sebastien Marineau <marineau@genie.uottawa.ca>, - - o Harald Koenig <koenig@tat.physik.uni-tuebingen.de> - - Linux/m68k Frame Buffer Device driver by: - - o Martin Schaller - - - - - - - - - -README for XFree86[tm] 3.3.3.1 15 - - - - o Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be> - - o Andreas Schwab <schwab@issan.informatik.uni-dortmund.de> - - o Guenther Kelleter <guenther@Pool.Informatik.RWTH-Aachen.de> - - Tseng ET4000 and ET6000 SVGA driver by: - - o [Unknown authors] - - o Dirk Hohndel <hohndel@XFree86.Org> - - o Koen Gadeyne <koen.gadeyne@barco.com> - - o ... and others - - P9100 accelerated code by: - - o Joerg Knura <knura@imst.de> - - Rendition code by: - - o Tim Rowley <tor@cs.brown.edu> - - o Marc Langenbach <mlangen@studcs.uni-sb.de> - - Cyrix accelerated code by: - - o Annius Groenink <Annius.Groenink@cwi.nl> - - o Dirk Hohndel <hohndel@XFree86.Org> - - Epson code by: - - o Thomas Mueller <tmueller@sysgo.de> - - 3DLabs accelerated code by: - - o Alan Hourihane <alanh@fairlite.demon.co.uk> - - o Dirk Hohndel <hohndel@XFree86.Org> - - o Stefan Dirsch <sndirsch@suse.de> - - o Helmut Fahrion <hf@suse.de> - - XFree86-VidModeExtension and xvidtune client by: - - o Kaleb S. Keithley <kaleb@x.org> - - o David Dawes <dawes@XFree86.org> - - o Jon Tombs <tombs@XFree86.org> - - - - - - - - - -README for XFree86[tm] 3.3.3.1 16 - - - - o Joe Moss <joe@XFree86.org> - - XFree86-Misc extension by: - - o Joe Moss <joe@XFree86.org> - - o David Dawes <dawes@XFree86.org> - - XFree86-DGA extension by: - - o Jon Tombs <tombs@XFree86.org> - - o Mark Vojkovich <mvojkovi@ucsd.edu> - - o Harm Hanemaayer <H.Hanemaayer@inter.nl.net>, - - o David Dawes <dawes@XFree86.org> - - XInput integration, devices and clients by: - - o Frederic Lepied <lepied@XFree86.Org> (XInput integration, - Wacom tablet, Joystick and extended mouse devices, xsetpointer - and xsetmode clients) - - o Patrick Lecoanet <lecoanet@cena.dgac.fr> (Elographics touch- - screen device) - - o Steven Lang <tiger@tyger.org> (Summagraphics tablet device) - - Other contributors: - - o Joerg Wunsch <joerg_wunsch@uriah.sax.de> (ET3000 banked mono), - - o Thomas Dickey <dickey@clark.net> (xterm "new" model ANSI col- - ors and VT220, VT52 emulation). - - o Eric Raymond <esr@snark.thyrsus.com> (new video mode documen- - tation), - - o and an entire horde of beta-testers around the world! - - -6. Contact information - -Ongoing development planning and support is coordinated by the XFree86 Core -Team. At this time the Core Team consists of (in alphabetical order): - - o Robin Cutshaw <robin@XFree86.org> - - o David Dawes <dawes@XFree86.org> - - o Marc Evans <marc@XFree86.org> - - - - - - - - - - -README for XFree86[tm] 3.3.3.1 17 - - - - o Harm Hanemaayer <H.Hanemaayer@inter.nl.net> - - o Dirk Hohndel <hohndel@XFree86.org> - - o Harald Koenig <koenig@XFree86.org> - - o Rich Murphey <rich@XFree86.org> - - o Takaaki Nomura <nomura@XFree86.org> - - o Jon Tombs <tombs@XFree86.org> - - o David Wexelblat <dwex@XFree86.org> - -Mail sent to <Core@XFree86.org> will reach the core team. Please note that -support questions should be sent to <XFree86@XFree86.org>. - - -7. The XFree86 Project, Inc. - -The XFree86 Project, Inc, was founded to accomplish two major goals: - - 1. To provide a vehicle by which XFree86 can be represented in X Consortium, - Inc, the organization responsible for the design, development, and - release of The X Window System. - - 2. To provide some basic funding for acquisition of facilities for ongoing - XFree86 development, largely to consist of new video hardware and basic - computing facilities. - -The first of these was the primary motivation. We have held discussions with -the X Consortium on and off for many months, attempting to find an avenue by -which our loosely-organized free software project could be given a voice within -the X Consortium. The bylaws of the Consortium would not recognize such an -organization. After an initial investigation about funding, we decided to form -our own corporation to provide the avenue we needed to meet the requirements of -the X Consortium bylaws. - -By doing this, we were able to be involved in the beta-test interval for X11R6, -and have contributed the majority of XFree86 to the X11R6 and X11R6.1 core -release. The version of XFree86 in the initial X11R6 core is 3.0. The version -of XFree86 in the current X11R6.3 release is 3.2. - -An additional benefit of this incorporation is that The XFree86 Project, Inc -has obtained outside financial support for our work. This will hopefully give -us the freedom to be more pro-active in obtaining new video hardware, and -enable us to release better products more quickly, as we will be able to go and -get what we need, and get it into the hands of the people who can do the work. - -The current Board of Directors and Officers of the The XFree86 Project, Inc, -are: - - o David Dawes, President and Secretary - - - - - - - - - -README for XFree86[tm] 3.3.3.1 18 - - - - o Dirk Hohndel, Vice-President - - o Glenn Lai, Director - - o Rich Murphey, Treasurer - - o Jim Tsillas, Director - - o Jon Tombs, Director - - o David Wexelblat, Director - -Email to <BOD@XFree86.org> reaches the board of directors. - -Our bylaws have been crafted in such a way to ensure that XFree86 is and always -will be a free software project. There is no personal financial benefit to any -member of the Core Team or any other XFree86 participant. All assets of the -corporation remain with the corporation, and, in the event of the dissolution -of the corporation, all assets will be turned over to the X Consortium, Inc. -It is hoped that by doing this, our corporation will be merely a formalization -of what we have been doing in the past, rather than something entirely new. - -As of March 1997, The XFree86 Project has revised its source/binary access and -release policy. The main points of the new policy are: - - o There will be no more time-limited public binary-only beta releases. - Instead we plan to increase the frequency of full public releases to about - four releases per year. - - o The source access/use is divided into three categories: - - o End users. End users have access to only the source of full public - releases. The main reason for this restriction is that our develop- - ment code often contains code from other sources which cannot be - released to the public immediately. - - o Active developers (members of the XFree86 ``developer team''). - Active developers must formally become non-voting members of the - XFree86 Project, and have full access to our internal development - source. They are permitted to make time-limited binaries (in coordi- - nation with the Core Team) of the servers they are actively working - on available to external testers for specific testing. - - o Commercial members. Commercial members are non-voting members of The - XFree86 Project who donate US$5000/year to the Project. Addition- - ally, companies who contribute significantly to the development - effort of XFree86 can be awarded commercial membership by the Core - Team on a yearly bases. Commercial members can use the internal - XFree86 development source for derived binary-only products providing - that they take full responsibility for supporting the product, and - don't call it ``XFree86'' (although the derivation of the product - must be acknowledged in any accompanying documentation). Binary - packages for the OSs we support which are simply compiled from our - internal source without significant added value are explicitly NOT - - - - - - - - -README for XFree86[tm] 3.3.3.1 19 - - - - allowed. - -Here is a list of the organizations and individuals who have provided sponsor- -ship to The XFree86 Project, Inc, either by financial contribution or by the -donation of equipment and resources. The XFree86 Project, Inc gratefully -acknowledges these contributions, and hopes that we can do justice to them by -continuing to release high-quality free software for the betterment of the -Internet community as a whole. - - o UUNET Communications Services, Inc. <URL:http://www.uu.net/> - -UUNET Communications Services, Inc, deserves special mention. This organiza- -tion stepped forward and contributed the entire 1994 X Consortium membership -fee on a moment's notice. This single act ensured XFree86's involvement in -X11R6. - - o GUUG -- 1st German Linux Congress - -Also deserving of special mention are the organizers and attendees of the 1st -German Linux Congress in Heidelberg. Significant funding to The XFree86 Pro- -ject has been provided from its proceeds. - - o AIB Software Corporation <URL:http://www.aib.com/>, Herndon, VA - - o Roland Alder, Armin Fessler, Patrick Seemann, Martin Wunderli - - o American Micro Group - - o ATI Technologies Inc <URL:http://www.atitech.ca/> - - o Andrew Burgess - - o Berkeley Software Design, Inc <URL:http://www.bsdi.com/>, Colorado - Springs, CO - - o Caldera, Inc. <URL:http://www.caldera.com/> - - o Delix Computer GmbH <URL:http://www.delix.de/>, Stuttgart, Germany - - o The Destek Group, Inc. <URL:http://www.destek.net/Destek/>, Nashua, NH - (formerly Synergytics) - - o Diamond Multimedia Systems, Inc. <URL:http://www.diamondmm.com/> - - o Digital Equipment Corporation <URL:http://www.digital.com/> - - o Elsa GmbH <URL:http://www.elsa.de/>, Aachen, Germany - - o Genoa Systems Corporation - - o Helius, Inc. <URL:http://www.helius.com/> - - o Hercules Computer Technology, Inc. <URL:http://www.hercules.com/> - - - - - - - - - -README for XFree86[tm] 3.3.3.1 20 - - - - o Ralf Hockens - - o Dirk Hohndel - - o InfoMagic <URL:http://www.infomagic.com/>, Flagstaff, AZ - - o Daniel Kraemer - - o Epoch Networks, Inc. <URL:http://www.eni.net/>, Irvine, CA - - o Frank & Paige McCormick - - o Internet Labs, Inc. - - o Linux International - - o Linux Support Team, Erlangen, Germany - - o LunetIX Softfair <URL:http://www.lunetix.de>, Berlin, Germany - - o Morse Telecommunications <URL:http://www.morse.net>, Long Beach, NY - - o MELCO, Inc <URL:http://www.melcoinc.co.jp> - - o MIRO Computer Products AG, Braunschweig, Germany - - o Rich & Amy Murphey - - o NCR Corp <URL:http://www.ncr.com/> - - o Brett Neumeier - - o Number Nine, Lexington, MA - - o Kazuyuki Okamoto, Japan - - o Prime Time Freeware <URL:http://www.ptf.com/>, San Bruno, CA - - o Red Hat Software <URL:http://www.redhat.com/>, Chapel Hill, NC - - o Norbert Reithinger - - o SPEA Software AG, Starnberg, Germany - - o STB Systems - - o Clifford M Stein - - o Joel Storm - - o S.u.S.E. GmbH <URL:http://www.suse.de>, Fuerth, Germany - - o Tekelec Airtronic GmbH <URL:http://www.tekelec.com>, Muenchen, Germany - - - - - - - - - -README for XFree86[tm] 3.3.3.1 21 - - - - o Jim Tsillas - - o Trans-Ameritech Enterprises, Inc., Santa Clara, CA - - o Unifix Software GmbH, Braunschweig, Germany - - o Vixie Enterprises <URL:http://www.vix.com/>, La Honda, CA - - o Walnut Creek CDROM <URL:http://www.cdrom.com/>, Concord, CA - - o Xtreme s.a.s. <URL:http://www.xfree86.org/xtreme>, Livorno, Italy - -The XFree86 Project, Inc, welcomes the additional contribution of funding -and/or equipment. Such contributions should be tax-deductible; we will know -for certain when the lawyers get finished with the papers. For more informa- -tion, contact The XFree86 Project, Inc, at <BOD@XFree86.org> - - -8. Source and binary archive sites - -Source patches are available to upgrade X11R6.3 PL2 from the X Consortium (now -The Open Group) to XFree86 3.3.3.1. Binaries for many OSs are also available. -The distribution is available from: - - o ftp://ftp.XFree86.org/pub/XFree86 - -and the following mirror sites: - - o North America: - - o ftp://ftp2.XFree86.org/pub/XFree86 (source and binaries) - - o ftp://ftp.infomagic.com/pub/mirrors/XFree86-current (source and bina- - ries) - - o ftp://ftp.rge.com/pub/X/XFree86 and http://www.rge.com/pub/X/XFree86 - (source and binaries) - - o ftp://ftp.varesearch.com/pub/mirrors/xfree86 (source and binaries) - - o ftp://ftp.cs.umn.edu/pub/XFree86 (source and binaries) - - o ftp://ftp.kernel.org/pub/mirrors/xfree86 (source and binaries) - - - o Europe: - - o ftp://fvkma.tu-graz.ac.at/pub/XFree86 (source and binaries) - - o ftp://gd.tuwien.ac.at/hci/X11/XFree86 and - http://gd.tuwien.ac.at/hci/X11/XFree86 (source and binaries) - - o ftp://ftp.fee.vutbr.cz/pub/XFree86 (source patches and binaries) - - - - - - - - - -README for XFree86[tm] 3.3.3.1 22 - - - - o ftp://ftp.gwdg.de/pub/xfree86/XFree86 (source and binaries) - - o ftp://ftp.mpi-sb.mpg.de/pub/X/mirror/ftp.xfree86.org (source and - binaries) - - o ftp://ftp.cs.tu-berlin.de/pub/X/XFree86 (source and binaries) - - o ftp://ftp.uni-erlangen.de/pub/Linux/MIRROR.xfree86 (source and Linux - binaries) - - o ftp://ftp.uni-stuttgart.de/pub/X11/Xfree86 (source and binaries) - - o ftp://ftp.funet.fi/pub/X11/XFree86 (source and binaries) - - o ftp://ftp.ibp.fr/pub/X11/XFree86 (source and binaries) - - o ftp://ftp.unina.it/pub/XFree86 (source and binaries) - - o ftp://ftp.pvv.unit.no/pub/XFree86 (source and binaries) - - o ftp://sunsite.doc.ic.ac.uk/packages/XFree86 (source and binaries) - - - - - o Asia/Australia: - - o ftp://x.physics.usyd.edu.au/pub/XFree86 (source and binaries) - - o ftp://ftp.netlab.is.tsukuba.ac.jp/pub/XFree86 (source and binaries) - - o ftp://ftp.iij.ad.jp/pub/X/XFree86/XFree86 (source and binaries) - - o ftp://ftp.kreonet.re.kr/pub/Linux/xfree86 (source and binaries) - - -Ensure that you are getting XFree86 3.3.3.1 - some of these sites may archive -older releases as well. Check the RELNOTES to find which files you need to -take from the archive. - - Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml,v 3.75.2.46 1999/01/05 07:15:48 hohndel Exp $ - - - - - - $XConsortium: README.sgml /main/31 1996/10/28 05:43:24 kaleb $ - - - - - - - - - - - - - - - -README for XFree86[tm] 3.3.3.1 23 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - CONTENTS - - - -1. What's new in XFree86 3.3.3.1 ............................................ 1 - -2. Systems XFree86 has been tested on ....................................... 1 - -3. Supported video-card chip-sets ........................................... 2 - -4. Where to get more information ............................................ 5 - -5. Credits .................................................................. 6 - -6. Contact information ..................................................... 16 - -7. The XFree86 Project, Inc. ............................................... 17 - -8. Source and binary archive sites ......................................... 21 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - i - - |