diff options
Diffstat (limited to 'distrib')
| -rw-r--r-- | distrib/notes/amd64/contents | 60 | ||||
| -rw-r--r-- | distrib/notes/amd64/hardware | 902 | ||||
| -rw-r--r-- | distrib/notes/amd64/install | 89 | ||||
| -rw-r--r-- | distrib/notes/amd64/prep | 68 | ||||
| -rw-r--r-- | distrib/notes/amd64/upgrade | 103 | ||||
| -rw-r--r-- | distrib/notes/amd64/whatis | 5 | ||||
| -rw-r--r-- | distrib/notes/amd64/xfer | 28 |
7 files changed, 1255 insertions, 0 deletions
diff --git a/distrib/notes/amd64/contents b/distrib/notes/amd64/contents new file mode 100644 index 00000000000..0981de0389e --- /dev/null +++ b/distrib/notes/amd64/contents @@ -0,0 +1,60 @@ +dnl $OpenBSD: contents,v 1.1 2004/02/07 21:29:10 deraadt Exp $ +TopPart + +OpenBSDfloppy + + floppyB{:--:}OSrev.fs Another MACHINE boot and installation floppy; + this one features all the drivers not available + in floppy{:--:}OSrev.fs, such as SCSI, RAID, gigabit + ethernet, and such; see below. + + floppyC{:--:}OSrev.fs Another MACHINE boot and installation floppy; + this one features most of the cardbus and + pcmcia drivers; see below. + + cdrom{:--:}OSrev.fs The MACHINE boot and installation + 2.88MB floppy image that contains almost all + OpenBSD drivers; see below. + +OpenBSDdistsets + +OpenBSDbsd + +OpenBSDrd + +OpenBSDcd + +As well you may be interested in + +.../OSREV/tools/ + miscellaneous MACHINE installation utilities like + rawrite.exe, ntrw.exe, gzip.exe, and pfdisk.exe; + see installation section, below. + + +OpenBSDfloppydesc(three,Each,s) + +In addition, the "tools/" directory contains some utilities that might be +useful for the installation. + +DistributionDescription(ten) + +OpenBSDbase(31.0,90.9,shared) + +OpenBSDcomp(17.4,57.6,shared) + +OpenBSDetc(1.6,6.0) + +OpenBSDgame(2.6,6.0) + +OpenBSDman(6.3,22.4) + +OpenBSDmisc(2.0,6.5) + +OpenBSDxbase(11.1,32.8) + +OpenBSDxfont(32.0,35.2) + +OpenBSDxserv(15.6,40.5) + +OpenBSDxshare(1.7,8.6) diff --git a/distrib/notes/amd64/hardware b/distrib/notes/amd64/hardware new file mode 100644 index 00000000000..926fafedbb8 --- /dev/null +++ b/distrib/notes/amd64/hardware @@ -0,0 +1,902 @@ +dnl $OpenBSD: hardware,v 1.1 2004/02/07 21:29:10 deraadt Exp $ +OpenBSD/MACHINE OSREV works across a broad range of standard PC's and +clones, with a wide variety of processors and I/O bus architectures. It +can be expected to install and run with minimal difficulties on most +current products. The cases where problems may be encountered are +typically older proprietary PC's, laptops or specialized server boxes +that rely on a custom BIOS to paper over implementation differences. + +OpenBSD does not currently support multiple processors (SMP), but will +run using one processor on a multi-processor system board. + +The minimal configuration to install the system is 12M or 16M of RAM and +perhaps 100M of disk space. A custom kernel might be able to run with only +8MB. To install the entire system requires much more disk space, and to run +X or compile the system, more RAM is recommended. (16M of RAM will actually +allow you to run X and/or compile but it won't be speedy. Note that until +you have around 32M of RAM, getting more RAM is more important than getting +a faster CPU.) + +Supported hardware {:-include-:}: + Processors + All versions of the AMD Athlon 64 processors + Buses + All standard ISA, EISA, VLB, and PCI bus based machines, + including: + Intel 450GX/KX based machines + Intel 450NX based machines + ServerWorks chipset-based machines + (We just had to mention those last three, since + they are the hardest to support) + Both 16-bit PCMCIA Cards and newer 32-bit CardBus + support + Universal Serial Bus (USB) + The MCA bus found in various IBM PS/2 machines is not + supported. + Bus Interfaces + Standard PCI-PCI bridges, including PCI expansion + backplanes + YENTA-compatible PCI-CardBus bridges + Entropy Sources + Interrupt latency collection from many devices + Disk Controllers + Floppy controllers. + ISA MFM, ESDI, IDE, and RLL hard disk controllers. + PCI IDE Controllers + Acard ATP850, ATP860 + Acer Labs M5229 + Advanced Micro Devices 756, 766 + CMD Tech PCI0640, PCI0643, PCI0646, PCI0648, PCI0649 and PCI0680 + Contaq Microsytems/Cypress CY82C693 + HighPoint HPT366, HPT370, HPT372, HPT302, HPT371, HPT374 + (RAID mode is not supported) + Intel PIIX, PIIX3, and PIIX4 + Intel 82801 (ICH/ICH0/ICH2/ICH3/ICH4/ICH4-M/ICH5/ICH5R) + National Semiconductor PC87415 + NVIDIA nForce/nForce2 + Promise PDC20246, PDC20262, PDC20265, PDC20267, PDC20268, + PDC20268R, PDC20269, PDC20271, PDC20275, PDC20276, PDC20277 + (RAID mode is not supported) + ServerWorks OSB4, CSB5, CSB6 + Silicon Integrated Systems 5513 (5597/5598) + VIA Technologies VT82C586A/B, VT82C596A/B, VT82C686A/B, + VT8231, VT8366, VT8233, VT8235 + (Other PCI IDE-compliant controllers should work, but + those not listed above may not be capable of DMA modes) + SATA Controllers + Promise PDC20376 (only parallel ATA mode tested) + Silicon Image SiI3112 + SCSI Host Adapters + Adaptec AHA-1540, AHA-154xA, AHA-154xB, AHA-1542C, + AHA-1542CF, AHA-1542CP, AHA-1640 [B] [C] + Adaptec AHA-174x [B] [C] + Adaptec AIC-6260 and AIC-6360 based boards, including: [B] + the Adaptec AHA-152x and the SoundBlaster SCSI host adapter. + (Note that you cannot boot from these boards if they do not + have a boot ROM; only the AHA-152x and motherboards using + this chip are likely to be bootable, consequently.) + Adaptec AIC-7770-based boards, including the Adaptec + AHA-274x and AHA-284x families) [C] + Adaptec AHA-[23]94x[W] cards and some on-board PCI designs + using the AIC7870 and AIC7880 chips. [C] + Adaptec AHA-[23]94xU[2W] cards and some on-board PCI designs + using the AIC789[01], AIC7895, AIC789[67] chips [C] + Adaptec AIC-789[29] chips and products like the + AHA-29160 based upon it which do 160MB/sec SCSI. [C] + (However, the 7899G card is currently not supported with + more than one device attached) + AdvanSys 'U', 'UW', 'U2W' and 'U160' PCI SCSI + controllers including the ABP940U[AW], + ASB3940U[AW]-00, ASB3940U2W-00 and ASB3950U160 [A] [B] [C] + AMD Am53c974 PCscsi-PCI SCSI controllers, including: [A] [B] [C] + Tekram DC-390 + Buslogic BT-54x (Adaptec AHA-154x clones) [B] [C] + BusLogic 445, 74x, 9xx (but not the new "FlashPoint" series + of BusLogic SCSI adapters) [B] [C] + Initio INIC-940 and INIC-950 based PCI SCSI host + adapters, including: [A] [C] + Initio INI-9090U + Initio INI-9100U/UW + Iwill 2935UW + DTC Domex 3194U Plus + QLogic PCI SCSI controllers [A] [C] + Seagate/Future Domain ISA SCSI adapter cards, including: [B] [C] + ST01/02 + Future Domain TMC-885 + Future Domain TMC-950 + Symbios Logic (NCR) 53C8xx, 53C1010, and 53C1510D-based + PCI SCSI host adapters (including generic/no name cards, old + ASUS cards, the DTC-3130 series, Diamond Fireport series, + etc.) [B] [C] + Tekram DC-300B and DC-320E (Adaptec AHA-154x clones) [B] [C] + Tekram DC-3x5U (DC-315U, DC-395U/UW/F) TRM-S1040 based + PCI SCSI host adapters [A] [C] + Ultrastor 14f, 24f, and 34f [A] [C] + WD-7000 SCSI host adapters [A] [B] [C] + RAID and Cache Controllers + 3ware Escalade 3W-5x00, 3W-6x00 [A] [C] + Adaptec FSA-based RAID controllers, including: [A] [C] + Adaptec AAC-2622, AAC-364, AAC-3642 + Dell PERC 2/Si, PERC 2/QC, PERC 3/Si, PERC 3/Di, + PERC 3/QC + HP NetRAID-4M + American Megatrends Inc. MegaRAID controllers in "Mass + Storage" mode [A] [C] + Compaq Smart ARRAY PCI/EISA adapters, including: [A] [C] + Compaq Integrated Array + Compaq IAES + Compaq IDA, IDA-2 + Compaq RAID LC2 + Compaq Smart Array 221, 3100ES, 3200, 4200, + 4250ES, 431 + Compaq SMART, SMART-2/E, SMART-2/P, SMART-2DH, + SMART-2SL + DPT SmartCache and SmartRaid III/IV PCI/EISA adapters [A] [C] + Intel (and formerly ICP-Vortex) GDT series [A] [C] + I2O (intelligent I/O) RAID controllers, including: [A] [C] + Adaptec SCSI RAID (ASR-2100S, ASR-2110S, ASR-3200S, + etc) + American Megatrends Inc. MegaRAID controllers + (in I2O mode) + and probably other vendors' controllers supporting + I2O, including Intel and Mylex (untested) + CD-ROM and DVD-ROM Drives + Mitsumi CD-ROM drives [*] + [Note: The Mitsumi driver device probe is known + to cause trouble with several devices!] + Most SCSI CD-ROM, CD-R, CD-RW, and DVD drives + Most ATAPI CD-ROM, CD-R, CD-RW, and DVD drives + Tape Drives + Most SCSI tape drives + Most SCSI tape changers [G] + QIC-02 and QIC-36 format (Archive- and Wangtek- + compatible) tape drives [*] + MDA, CGA, VGA, SVGA, and HGC Display Adapters. (Note that not + all of the display adapters OpenBSD/MACHINE + are supported by X. See the XFree86 FAQ for more + information.) + Serial Ports + 8250/16450-based ports + 16550-based ports + ST16660-base ports + XR16850-based ports (only in the pccom driver) + AST-style 4-port serial boards [G] + BOCA 8-port serial cards [*] + Cyclades Cyclom-{4, 8, 16}Y serial boards [G] + Cyclades-Z series multiport serial boards [G] + IBM PC-RT 4-port serial boards [*] + Addonics FlexPort 8S [*] + Parallel Ports + Any standard parallel port [G] + Communication Controllers + Universal Serial Bus host controllers, including: + USB Universal Host Controller [A] [B] [C] + USB Open Host Controller [A] [B] [C] + PCI `universal' communication cards, providing serial + and parallel ports, including: [G] + Dolphin Peripherals 4014 (dual parallel) and + 4035 (dual serial) + SIIG Cyber 2P1S (dual parallel, single serial) + and 2S1P (dual serial, single parallel) + SIIG Cyber 4S (quad serial) + SIIG Cyber I/O (single parallel, single serial) + SIIG Cyber Parallel, Parallel Dual, Serial, + Serial Dual + VScom PCI 800 (8 port serial) + VScom PCI 011H (1 port parallel) + VScom PCI 100H (1 port serial) + VScom PCI 110H (1 port serial and 1 port parallel) + VScom PCI 200H (2 port serial) + VScom PCI 210H (2 port serial and 1 port parallel) + VScom PCI 400H (4 port serial) + VScom PCI 410H (4 port serial and 1 port parallel) + VScom PCI 800H (8 port serial) + VScom PCI 100L (1 port serial) + VScom PCI 200L (2 port serial) + VScom PCI 210L (2 port serial and 1 port parallel) + VScom PCI 400L (4 port serial) + VScom PCI 800L (8 port serial) + AT&T/Lucent Venus Modem (found on IBM 33L4618 + card, Actiontec 56K, and others) + US Robotics 3CP5609 PCI (modem) + Lava Computers 2SP-PCI (parallel port) + Lava Computers 2SP-PCI and Quattro-PCI (dual + serial) + NEC PK-UG-X008 (serial) + NEC PK-UG-X001 K56flex PCI (modem) + Koutech IOFLEX-2S (dual serial) + Syba Tech Ltd. PCI-4S2P-550-ECP (4 port serial, 2 + port parallel) + Moxa Technologies Co., Ltd. PCI I/O Card 4S (4 port + serial) + Moxa Technologies Co., Ltd. C104H/PCI (4 port serial) + NetMos 2S1P (2 port serial and 1 port parallel) + Boca Research Turbo Serial 654 PCI (4 port serial) + Boca Research Turbo Serial 658 PCI (8 port serial) + SUNIX 400x (1 port parallel) + SUNIX 401x (2 port parallel) + SUNIX 402x (1 port serial) + SUNIX 403x (2 port serial) + SUNIX 405x (4 port serial) + SUNIX 406x (8 port serial) + SUNIX 407x (2 port serial and 1 port parallel) + SUNIX 408x (2 port serial and 2 port parallel) + SUNIX 409x (4 port serial and 2 port parallel) + Ethernet Adapters + 3Com 3c501 [A] [B] [C] + 3Com 3c503 [B] + 3Com 3c505 [A] [B] [C] + 3Com 3c507 [A] [B] [C] + 3Com 3c509, 3c579, and 3c59x (disabling PnP on 3c509B is + recommended) + 3Com 3c515 [B] + 3Com 3c9xx Etherlink XL adapters, including: + 3Com 3c900/3c900B PCI adapters + 3Com 3c905/3c905B/3c905C PCI adapters + 3Com 3c980/3c980C server adapters + 3Com 3cSOHO apapter + 3Com 3c900B-FL and 3c900B-FL/FX fiber optic + adapters + 3Com 3c555/3c556/3c556B MiniPCI adapters + Dell on-board 3c920 + Dell Precision on-board 3c905B + Dell OptiPlex GX1 on-board 3c918 + Dell Latitude laptop docking station embedded + 3c905 + NVidia nForce2 integrated 3Com 9201 (nForce2-ST, nForce2-GT) + 3Com 3c990 3XP Typhoon/Sidewinder PCI adapters, including: [A] + [B] [C] + 3C990-TX-95 + 3C990-TX-97 + 3C990-TX-SVR95 + 3C990-TX-SVR97 + Adaptec "Starfire" AIC-6915 based PCI adapters, including: [G] + Adaptec Single32 ANA-69011 + Adaptec Single64 ANA-62011 and ANA-62020 + Adaptec Duo64 ANA-62022 + Adaptec Quartet64 ANA-62044 + ADMtek AL981 ("Comet") and AN983 ("Centaur-P") based PCI + adapters, including: + Accton EN2242 MiniPCI + Linksys LNE100TX v4.x + Mototech ME316 + ADMtek AN986-based USB adapters, including: [A] [B] [C] + Abocom UFE1000 + Abocom DSB650TX + Accton USB320-EC + Accton SpeedStream Ethernet + Admtek Pegasus, Pegasus II + Billionton Systems USB100 + Corega FEther USB-TX + D-Link DSB-650, 650TX, 650TX-PNA + Elecom LD-USB + Elsa Microlink USB2Ethernet + I/O Data USB ETTX + Kingston KNU101TX + LinkSys USB100TX, USB100H1 and USB10TA + Melco Inc. LUA-TX + Siemens SpeedStream USB + Smartbridces smartNIC 2 + SMC 2202USB + SMC EZ Connect USB + SOHOware NUB100 + AMD LANCE and PCnet-based ISA Ethernet adapters, including: [B] + Novell NE1500T + Novell NE2100 + Kingston 21xx + AMD PCnet-based PCI Ethernet adapters, including: [B] [C] + BOCALANcard/PCI + AT&T StarLAN 10, EN100, and StarLAN Fiber + ASIX 88140A/88141 PCI Ethernet adapters, including: + CNet Pro110B + Alfa Inc. GFC2204 + CATC USB-EL1210A-based USB adapters, including: [G] + CATC Netmate and Netmate II + Belkin F5U011/F5U111 + Davicom DM9009, DM9100, DM9102, and DM9102A based PCI adapters, + including: + Jaton XpressNet + DEC EtherWORKS III adapters, including: [G] + DEC DE203, DE204, DE205 + Digital DC21x4x-based PCI Ethernet adapters, including: + Older SMC PCI EtherPower 10, 10/100 (models + 8432, 9332, and 9334) + Older LinkSys 10, 10/100 (newer models are + supported by other drivers) + Znyx ZX3xx + Cogent EM100FX and EM440TX + Digital PCI DE435, EISA DE425, DE450, DE500 + Asante 21140A + D-Link DFE-570TX Quad port + Digital DC2114x-based four port cards, including: + Adaptec ANA-6944A + Cogent EM400 + Compex 400TX + CompuShack Goldline Quattro + Phobos P430TX + Znyx ZX346 + Intel EtherExpress 16 [A] [B] [C] + Intel EtherExpress PRO/10 ISA [A] [B] [C] + Intel i8255x-based (except the i82556) PCI adapters, + including: + Intel EtherExpress PRO/10+ + Intel EtherExpress PRO/100, PRO/100B, and PRO/100+ + Intel EtherExpress PRO/100+ "Management Adapter" + Intel EtherExpress PRO/100 Dual Port + Intel PRO/100 VE, PRO/100 VM, and PRO/100 S + Intel 21145-based PCI adapters + Kawasaki LSI KL5KUSB101B-based USB adapters, including: [A] + [B] [C] + 3Com 3c19250 + 3Com 3c460 HomeConnect + ADS Technologies USB-10T + Aox USB101 + ATen UC10T + Corega USB-T + D-Link DSB-650 + Entegra NET-USB-E45 + Kawasaki USB101 + LinkSys USB10T + Netgear EA101 + Peracom USB + SMC 2102/2104USB + I/O Data USB-ET/T + Lite-On PNIC/PNIC-II-based adapters, including: + Kingston KNE110TX + LinkSys LNE100TX + Matrox Networks FastNIC 10/100 + Netgear FA310TX + Macronix 98713/713A/715/715A/725/727/732-based adapters, + including: + Accton EN1217 + Addtron AEF-320TX/AEF-330TX + CNet PRO120A/B + Complex RL-100TX + NDC Communications SOHOware SFA110A + SVEC PN102-TX Fast Ethernet card + Myson Technologies MTD803 3-in-1 Fast Ethernet adapters + National Semiconductor DP83815-based PCI adapters, + including: [B] [C] + Netgear FA311/FA312 + Novell NE1000, NE2000 [B] + RealTek 8129, RealTek 8139 Ethernet adapters, including: + Accton MPX 5030/5038 + Allied Telesyn AT2550 + D-Link DFE530TX+, DFE538TX + Encore ENL832-TX 10/100 M PCI + Genius GF100TXR + KTX-9130TX 10/100 Fast Ethernet + Longshine LCS-8038TX-R + NDC NE100TX-E + Netronix EA-1210 Net Ether 10/100 + Nortel BayStack 21 + OvisLink LEF-8129TX, LEF-8139TX + SMC EZ Card 10/100 PCI 1211-TX + RealTek RTL8150L based USB adapters, including: [G] + Melco Inc. LUA-KTX + GreenHouse GH-USB100B + Linksys USB100M + SiS 900 and SiS 7016-based PCI adapters, including: [B] [C] + Mototech ME313 + NetSurf NS-KFE30D + SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards [B] + SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards) [B] + (See special notice later in this document) + SMC 8416 EtherEZ PnP (with PnP mode off) [B] + SMC 9432 (EtherPower II) EPIC 10/100 [C] + Sun Happy Meal PCI adapters, including: [G] + Fast Ethernet + Quad Fast Ethernet + Sundance ST201-based PCI adapters, including: [G] + D-Link DFE-550TX + Texas Instruments ThunderLAN PCI adapters, including: [C] + Compaq Netelligent PCI Adapters + Compaq NetFlex 3/P + Compaq Deskpro integrated adapter + Compaq Prosignia integrated adapter + Olicom OC2135, OC2183, OC2325, OC2326 + Racore 8165 and 8148 + TI ThunderLAN adapters + VIA Rhine/RhineII/RhineIII Ethernet adapters, including: [C] + Addtron AEF-360TX + Hawking PN102TX + D-Link DFE530TX + Winbond W89C840F Ethernet adapters, including: [A] + Trendware TE100-PCIE + Compex RL100-ATX 10/100baseTX + Wireless Ethernet Adapters + Compact Flash Adapters (will show up as PCMCIA adapters) + Buffalo AirStation CF [A] [B] [C] + ELSA XI800 CF [A] [B] [C] + PCMCIA Adapters + 3Com AirConnect 3CRWE737A PCMCIA [A] [B] [C] + ACTIONTEC HWC01170 PCMCIA [A] [B] [C] + Addtron AWP-100 PCMCIA [A] [B] [C] + Agere Orinoco PCMCIA [A] [B] [C] + Aironet 4500/4800 802.11DS ISA PnP, PCMCIA and PCI [A] [B] + BUFFALO AirStation PCMCIA [A] [B] [C] + Cabletron RoamAbout PCMCIA [A] [B] [C] + Cisco 340/350 802.11DS PCMCIA and PCI [A] [B] + Compaq Agency NC5004 PCMCIA [A] [B] [C] + Contec FLEXLAN/FX-DS110-PCC PCMCIA [A] [B] [C] + Corega PCC-11 PCMCIA [A] [B] [C] + Corega PCCA-11 PCMCIA [A] [B] [C] + Corega PCCB-11 PCMCIA [A] [B] [C] + Corega CGWLPCIA11 PCMCIA [A] [B] [C] + Dlink DWL650 PCMCIA [A] [B] [C] + ELSA XI300 PCMCIA [A] [B] [C] + ELSA XI325 PCMCIA [A] [B] [C] + ELSA XI325H PCMCIA [A] [B] [C] + EMTAC A2424i PCMCIA [A] [B] [C] + Ericsson Wireless LAN CARD C11 PCMCIA [A] [B] [C] + Gemtek WL-311 PCMCIA [A] [B] [C] + Hawking Technology WE110P PCMCIA [A] [B] [C] + I-O DATA WN-B11/PCM PCMCIA [A] [B] [C] + Intel PRO/Wireless 2011 PCMCIA [A] [B] [C] + Intersil Prism II PCMCIA [A] [B] [C] + Linksys Instant Wireless WPC11 PCMCIA [A] [B] [C] + Linksys Instant Wireless WPC11 2.5 PCMCIA + [A] [B] [C] + Linksys Instant Wireless WPC11 3.0 PCMCIA + [A] [B] [C] + Lucent WaveLAN PCMCIA [A] [B] [C] + NANOSPEED ROOT-RZ2000 PCMCIA [A] [B] [C] + NEC CMZ-RT-WP PCMCIA [A] [B] [C] + Netgear MA401 PCMCIA [A] [B] [C] + Netgear MA401RA PCMCIA [A] [B] [C] + Nokia C020 Wireless LAN PCMCIA [A] [B] [C] + Nokia C110/C111 Wireless LAN PCMCIA [A] [B] [C] + NTT-ME 11Mbps Wireless LAN PCMCIA [A] [B] [C] + Proxim Harmony PCMCIA [A] [B] [C] + Proxim RangeLAN-DS PCMCIA [A] [B] [C] + RayLink Aviator2.4/Pro 802.11FH PCMCIA [A] [B] + Samsung MagicLAN SWL-2000N PCMCIA [A] [B] [C] + SMC 2632 EZ Connect PCMCIA [A] [B] [C] + Symbol Spectrum24 PCMCIA [A] [B] [C] + TDK LAK-CD011WL PCMCIA [A] [B] [C] + US Robotics 2410 PCMCIA [A] [B] [C] + US Robotics 2445 PCMCIA [A] [B] [C] + PCI Adapters + 3Com AirConnect 3CRWE777A PCI + Belkin F5D6000 PCI (a rebadged WL11000P) + Eumitcom WL11000P PCI + Dlink DWL520 PCI + Global Sun Technology GL24110P PCI (untested) + Global Sun Technology GL24110P02 PCI + Intersil Mini-PCI + LinkSys WDT11 PCI (a rebadged GL24110P02) + NDC/Sohoware NCP130 PCI + Netgear MA301 PCI + US Robotics 2415 PCI (rebadged WL11000P) + Gigabit Ethernet Adapters + Alteon Tigon I/II PCI Gigabit Ethernet boards, including: [A] + [B] [C] + 3Com 3c985 and 3c985B + Alteon ACEnic V (fiber and copper) + Digital EtherWORKS 1000SX + Farallon PN9000SX + Netgear GA620 and GA620T + SGI Tigon + Intel i82540, i82542, i82543, i82544, i82545, and i82546 + based adapters, including: + Intel PRO/1000 Gigabit Server Adapter (SX Fiber) + (PWLA8490) + Intel PRO/1000F Gigabit Server Adapter (SX Fiber) + (PWLA8490SX) + Intel PRO/1000T Server Adapter (PWLA8490T) + Intel PRO/1000XT Server Adapter (PWLA8490XT) + Intel PRO/1000XS Server Adapter (SX Fiber) (PWLA8490XF) + Intel PRO/1000T Desktop Adapter (PWLA8390T) + Intel PRO/1000XTL Lo Profile PCI Server (PWLA8490XTL) + Intel PRO/1000MT Desktop Adapter (PWLA8390MT) + Intel PRO/1000MT Server Adapter (PWLA8490MT) + Intel PRO/1000MT Dual Port Server Adapter (PWLA8492MT) + Intel PRO/1000MF Server Adapter (SX Fiber) (PWLA8490MF) + Intel PRO/1000MF Dual Port Server Adapter (SX Fiber) + (PWLA8492MF) + Intel PRO/1000MF Server Adapter (LX Fiber) (PWLA8490LX) + National Semiconductor DP83280 and DP83281 based PCI + adapters, including: [A] [B] [C] + Addtron AEG320T + Asante FriendlyNet GigaNIX 1000TA and 1000TPC + D-Link DGE-500T + LinkSys EG1032 and EG1064 + Netgear GA622T + SMC EZ Card 1000 + Surecom Technology EP-320G-TX + Level1 LXT1001 based adapters (untested), including: [*] + SMC TigerCard 1000 + D-Link DGE-500SX + Broadcom BCM570x (Tigon3) based PCI adapters, including: [A] + [B] [C] + 3Com 3c996-T + 3Com 3c996-SX + 3Com 3c996B-T + Dell PowerEdge 2550 integrated BCM5700 NIC + IBM xSeries 305 integrated BCM5703X NIC + Netgear GA302T + SysKonnect SK-9D21 + SysKonnect SK-9D41 + Sundance/Tamarack TC9021 based PCI adapters, including: [G] + D-Link DGE-550T (10/100/1000baseTX) + Antares Microsystems Gigabit Ethernet board + SysKonnect and Marvell based adapters, including: + [A] [B] [C] + SysKonnect SK-9821 (1000baseT) + SysKonnect SK-9822 (dual 1000baseT) + SysKonnect SK-9841 (1000baseLX) + SysKonnect SK-9842 (dual 1000baseLX) + SysKonnect SK-9843 (1000baseSX) + SysKonnect SK-9844 (dual 1000baseSX) + SysKonnect SK-9521 v2.0 (1000baseT 32-bit) + SysKonnect SK-9821 v2.0 (1000baseT) + SysKonnect SK-9843 v2.0 (1000baseSX) + 3Com 3c940 (1000baseT) + D-Link DGE-530T (1000baseT) + Linksys EG1032v2 (1000baseT) + Linksys EG1064v2 (1000baseT) + SMC 9452TX (1000baseT) + ATM Adapters + Efficient Networks EN-155 and Adaptec ANA-590X ATM + interfaces [*] + FDDI Adapters + Digital DEFEA EISA and PCI FDDI adapters [G] + Wan Adapters + Lan Media Corporation SSI (T1)/HSSI/DS1/DS3 WAN + interfaces [G] + Cryptography Accelerators + Broadcom Bluesteelnet uBsec 5501, 5601, 5801, 5802, 5805, + 5820, 5821, 5822, 5823 [G] + Hifn 6500-based boards [G] + Hifn 7751/7811/7951/7955/7956-based boards (hifn), + including: [G] + Soekris Engineering vpn1201, vpn1211, vpn1401, and vpn1411 + GTGI PowerCrypt Encryption Accelerator + NetSec 7751 + Hifn 7751 and 9751 reference boards + Invertex AEON + SafeNet SafeXcel 1141/1741 [G] + PC Cards (PCMCIA [B] and CardBus [B] [C]) + ATA cards, including: + ATA/IDE card drives + ATA/IDE CD-ROM adapters + CF/ATA flash cards and disk drives + Ethernet adapters, including: + 3Com EtherLink and EtherLink XL-based LAN PC + cards, including: + 3Com 3c556, 3c562 + 3Com 3c574TX, 3c[CX]FE574BT + 3Com 3c589, 3c589[BCDE] + 3Com 3c575TX, 3c[CX]FE575[BC]T CardBus + 3Com 3c[CX]FEM656, 3c[CX]FEM656[BC] CardBus + Intel/DEC 21443 "Tulip" clones, including: + ADMtex AN985 Centaur-C CardBus + IBM EtherJet 10/100 CardBus + SMC EZ CardBus 10/100 + Xircom X3201 CardBus adapters, including + RealPort models + Intel i8255x-based, including: + Intel PRO/100 CardBus II + NE2000-based, including: + Accton EN2212, EN2216 + Allied Telesis LA-PCM + AmbiCom AMB8002T + Arowana FE + Belkin F5D5020 + Billionton Systems LNT-10TN + CNet NE2000 + Compex Linkport ENET-B + Corega PCC-T, PCC-TD, EtherII PCC-T, + Corega FastEther PCC-T, FastEther PCC-TX + Corega FastEther PCC-TXD, FastEther PCC-TXF + D-Link DE-650, DE-660, DE-660+, DFE-670TXD + Dayna CommuniCard E + Digital DEPCM-XX + Dual NE2000 + Edimax NE2000 + Genius ME 3000II SE + Grey Cell GCS2000 Gold II + GVC NIC-2000p, NP0335 + Hawking PN650TX + I-O DATA PCLA, PCLA/TE + IC-Card + Kingston KNE-PC2 + Linksys PCMPC100, EC2T Combo, EthernetCard + Linksys Combo EthernetCard, Trust Combo EthernetCard + Linksys Etherfast 10/100 + MACNICA ME1 for JEIDA + Melco LPC3-TX + National Semiconductor InfoMover + NDC Instant-Link + Netgear FA410TX, FA410TXC, FA411 + Network Everywhere NP10T + New Media LiveWire 10/100 + Planet SmartCom 2000 + Planex FNW-3600-T, FNW-3700-T + Premax PE-200 + RPTI EP-400, EP-401 + Seiko Epson EN10B + SMC EZCard, 8041 + Socket Communications LP-CF, LP-E + SVEC PN650TX, ComboCard, LANCard + Synergy S21810 + Tamarack NE2000 + Telecom Device TCD-HPC100 + Wisecom T210CT, iPort + Xircom CFE-10 + RealTek 81[23]9-based, including: + Accton MPX5030 CardBus + Corega FEther CB-TXD 10/100 Ethernet + D-Link DFE-690TXD + SMC 91Cxx-based, including: + Megahertz XJEM1144, CC10BT + SMC EtherEZ 8020BT + Xircom, including: + Xircom CreditCard CE2 + PCMCIA controllers, including: + Intel i82365 and compatibles + SCSI host adapters, including: + Adaptec SlimSCSI APA-14[56]0 + Serial ports, including: + Most modems, digital cellular modems, and serial + cards should work + Wireless Ethernet adapters: + See above + Universal Serial Bus (USB) Devices [A] [B] [C] + USB Audio [G] + USB Diamond Multimedia Rio MP3 players [G] + USB Ethernet adapters, see above [G] + USB Generic Human Interface Devices (catch-all) [G] + USB Handspring Visor [G] + USB Hubs + USB Keyboards + USB Mass Storage devices, i.e., USB floppy drives and + USB memory stick controllers + USB Mice [G] + USB Modems [G] + USB Printers [G] + USB Scanners [G] + USB-USB cables [G] + USB Y@p phone [*] + Pointing Devices [G] + "Logitech"-style bus mice + "Microsoft"-style bus mice + "PS/2"-style mice + Serial mice (uses serial port driver) + Sound Devices [G] + AMD 768 and 8111 AC'97 + C-Media CMI8[37]38 + Cirrus Logic CrystalClear CS4280, CS4281 + Ensoniq AudioPCI + ESS Tech ES188[78], ES888 + ESS Solo-1 PCI AudioDrive + ESS Maestro 1, 2 and 2E and clones + ESS Maestro 3 and Allegro 1 + Forte Media FM801 audio + Gravis Ultrasound and Ultrasound Max + Intel i810/i820 and 440MX AC'97 + NeoMagic 256AV/ZX + nVidia nForce and nForce AC'97 + SiS 7012 AC'97 + SoundBlaster ISA cards and 100% compatibles + SoundBlaster PCI128 + SoundBlaster Live! and PCI512 (EMU10k1) + Trident 4DWAVE-DX/NX and clones (SiS 7018, ALi M5451) + VIA VT82C686A SouthBridge integrated AC'97 audio + Yamaha OPL3-SA3 + Yamaha DS-XG + Yamaha and Roland ISA/ISA PnP MIDI UART + [The following drivers are not extensively tested:] + Personal Sound System + ProAudio Spectrum + S3 SonicVibes + Windows Sound System + Radio Receiver Devices + AIMS Lab Radiotrack FM radio + AIMS Lab Radiotrack II FM radio + Aztech/PackardBell FM radio + Brooktree 848/849/878/879-based TV tuner + D-Link DSB-R100 USB radio + Forte Media FM801 audio + SoundForte RadioLink SF16-FMR FM radio + SoundForte RadioLink SF16-FMR2 FM radio + Miscellaneous Devices + APM power management, + Brooktree 8[47][89] based frame grabber and TV tuner cards, + including: [G] + Hauppauge Wincast TV + STB TV PCI Television Tuner + Miro PC TV + Intel Smart Video Recorder III + IMS TV Turbo + AVer Media TV/FM + Hardware monitoring sensors, including: [G] + National Semiconductor LM78, LM78-J, LM79 + Winbond W83697HF, W83627HF, W83627THF, W83781D, W83782D + VIA VT82C686A, VT8231 + ITE IT8705F, IT8712F + SiS SiS950 + Many kinds of ISA Plug-and-Play cards + Nearly all SB-style audio cards + Nearly all joystick ports + Nearly all Yamaha-style audio cards + Many NE2000-style Ethernet cards + Most serial port or modem cards + NE2100 Ethernet cards + +Drivers for hardware marked with [G] are only included in the GENERIC +kernels, but are NOT included on the various distribution floppies +(including the cd-rom boot image). +Drivers for hardware marked with [A] are not included in floppy A. +Drivers for hardware marked with [B] are not included in floppy B. +Drivers for hardware marked with [C] are not included in floppy C. +Support for devices marked with [*] is not included in the GENERIC kernel, +and will require you to compile a custom kernel to enable it. + + +Hardware that we do NOT currently support, but get many questions +about: + NCR 5380-based and 53400-based SCSI host adapters + QIC-40 and QIC-80 tape drives (these are the tape drives + that connect to the floppy disk controller) + Multiprocessor motherboards (though they will run fine using + one processor only) + Sony and Panasonic proprietary CD-ROM interfaces + Parallel-port ZIP drives (SCSI and ATAPI ZIP drives work fine) + Intel i82556 (EtherExpress PRO/100A) and i82596 (EtherExpress + PRO/10 PCI) Ethernet adapters + Hewlett-Packard PC-LAN+ (HP27xxx) Ethernet adapters + Aureal Vortex sound cards + Winmodems + Infrared devices, such as commonly found on laptops + Firewire + Mylex and Intel RAID controllers + PCMCIA: + Memory cards + Most multifunction cards + +We are planning future support for many of these devices. + +To be detected by the distributed kernels, some devices must +be configured with specific settings. Here's their list: + +Device Name Port IRQ DRQ Misc +------ ---- ---- --- --- ---- +Serial ports pccom0 0x3f8 4 [8250/16450/16550/clones] + pccom1 0x2f8 3 [8250/16450/16550/clones] + pccom2 0x3e8 5 [8250/16450/16550/clones] + ast0 0x1a0 5 [AST 4-port serial card] + cy0 12 iomem 0xd4000 [Cyclom + serial card] + +Parallel ports lpt0 0x378 7 [interrupt-driven or polling] + lpt1 0x278 [polling only] + lpt2 0x3bc [polling only] + +MFM/ESDI/IDE/RLL hard disk controllers + wdc0 0x1f0 14 [supports two disks or atapi] + wdc1 0x170 15 [supports two disks or atapi] + +Floppy controller + fdc0 0x3f0 6 2 [supports two disks] + +AHA-154x, AHA-174x (in compatibility mode), or BT-54x SCSI host adapters + aha0 0x330 any any + aha1 0x334 any any + +BT445, BT74x, or BT9xx SCSI host adapters + bha0 0x330 any any + bha1 0x334 any any + +Ultrastor 14f, 24f (if it works), or 34f SCSI host adapters + uha0 0x330 any any + uha1 0x334 any any + +AHA-152x, AIC-6260- or AIC-6360-based SCSI host adapters + aic0 0x340 11 any + +Seagate ST0[12], Future Domain TMC-8xx based SCSI controllers + sea0 5 iomem 0xc8000 + +WD7000 and TMC-7000 SCSI host adapters + wds0 0x350 15 6 + wds1 0x358 11 5 + +SCSI disks sd0 first SCSI disk (by SCSI id) + sd1 second SCSI disk (by SCSI id) + sd2 third SCSI disk (by SCSI id) + sd3 fourth SCSI disk (by SCSI id) + +SCSI tapes st0 first SCSI tape (by SCSI id) + st1 second SCSI tape (by SCSI id) + +SCSI CD-ROMs cd0 first SCSI CD-ROM (by SCSI id) + cd1 second SCSI CD-ROM (by SCSI id) + +SMC/WD 8003, 8013, Elite16, and Elite16 Ultra Ethernet boards + we0 0x280 9 iomem 0xd0000 + we1 0x300 10 iomem 0xcc000 + +Novell NE1000, or NE2000 Ethernet boards + ne0 0x240 9 iomem 0xd8000 + ne1 0x300 10 + ne2 0x280 9 + +3COM 3c501 Ethernet boards + el0 0x300 9 + +3COM 3c503 Ethernet boards + ec0 0x250 9 iomem 0xd8000 + +3COM 3c505/Etherlink+ Ethernet boards + eg0 0x310 5 + +AT&T StarLAN 10, EN100, or StarLAN Fiber, or 3COM 3c507 Ethernet boards + ie0 0x360 7 iomem 0xd0000 + +EtherExpress boards + ie1 0x300 10 + +IsoLan, NE2100, and DEPCA + le0 0x360 15 6 + +Intel EtherExpress PRO/10 + ex0 0x320 5 + +PCI ethernet boards need to have an interrupt, either assigned in your +PCI BIOS, or autoconfigured. + +Hardware not listed in the above table doesn't need any specific +configuration. + + +Special care for SMC Elite Ultra: + + The Elite Ultra is very sensitive to how its I/O port is treated. + Mistreating it can cause a number of effects -- anything from + the card not responding when the kernel probes, to the soft + configuration being corrupted or wiped completely. + + By default, the kernel ships with device we1 configured for the + 'default' Elite Ultra locations, comprising of port 0x300, irq 10, + and memory location 0xcc000. This matches a hard coded jumper on + the board as well a common soft config setting. + + Unfortunately, the kernel's autoconfiguration process (specifically, + some of the devices it probes for) causes conflicts with the SMC + Elite Ultra, and very often causes it to lose its configuration and + fail its own probe. If this happens, you must boot the computer + into DOS, and run the EzSetup program from SMC (if you do not have + a copy on the floppy accompanying your board, you can download it + from ftp://ftp.darmstadt.gmd.de/pub/pc/hardware/nic/smc/gez122.exe - + it is not available from SMC anymore). This program will allow you + to reconfigure and recover a card that has lost its configuration + with a minimum of hassle. + + In order to avoid blowing away the card, one *must* use the + run-time kernel configuration system when booting the Install + kernel. This is done by giving the -c flag to the initial boot + request. Following the loading of the kernel, the user is + presented with a + + UKC> + + prompt. At this prompt, a variety of commands may be issued, but + the relevant one to getting the SMC Elite Ultra running is + 'disable'. The wt0, el0, and ie1 devices all need to be disabled. + This is done by typing 'disable' followed by the name of the + device, i.e., 'disable wt0', and pressing return. + + If, for some reason, your Elite Ultra is not configured at the + 'default' location the kernel is expecting it, you may also use + the 'change' command in the UKC system to modify where the kernel + will look for it. Typing 'change we1' will allow you to modify + those settings. Note that running the card at an i/o port of + anything other then 0x300 at this point is not recommended, and is + beyond the scope of this document-- by doing so you risk other + device probes wreaking the havoc we are trying to avoid. + + When all three extra devices are disabled and any changes made, + the 'quit' command will exit the UKC. The kernel should then + boot, and find your Elite Ultra on device we1. + diff --git a/distrib/notes/amd64/install b/distrib/notes/amd64/install new file mode 100644 index 00000000000..6a2df1a1113 --- /dev/null +++ b/distrib/notes/amd64/install @@ -0,0 +1,89 @@ +dnl $OpenBSD: install,v 1.1 2004/02/07 21:29:10 deraadt Exp $ +OpenBSDInstallPrelude + +If OpenBSD will be sharing the disk with DOS or another operating +system, you should have already completed the section of these notes +that instructed you on how to prepare your hard disk. You should know +the size of the OpenBSD area of the disk and its offset from the +beginning of the disk. You will need this information when setting up +your OpenBSD partitions. If your BIOS uses translated geometry, you +should use this geometry for the remainder of the install. This is +only necessary if you are sharing the disk with other operating systems +that use the translated geometry. + +There are several ways to install OpenBSD onto a disk. The easiest way, +should your computer support it, is to boot off the OpenBSD CD-ROM, or +off the bootable CD-ROM mini image. Otherwise, you can boot from a 3.5" +1.44MB floppy disk if your machine has a floppy drive. + +OpenBSDInstallPart2 + + With either the CD-ROM or the floppy in the drive, reboot your + computer. You might have to play with your BIOS options to let the + computer boot from the installation media, rather than the hard + disk. + + It will take a while to load the kernel from a floppy or slow + speed CD-ROM drive, most likely more than a minute. If some + action doesn't eventually happen, or the spinning cursor has + stopped and nothing further has happened, either your boot floppy + is bad or you are having hardware problems. If trying another + floppy disk doesn't help, try booting after disabling your CPU's + internal and external caches (if any). If it still doesn't work, + OpenBSD probably can't be run on your hardware. This can probably + be considered a bug, so you might want to report it. + If you do, please {:-include-:} as many details about your system + configuration as you can. + + +OpenBSDBootMsgs + + You will next be asked for your terminal type. You should just + hit return to select the default (vt220). + +OpenBSDInstallPart3({:- or "wd0" for IDE/RLL/ESDI/ST506 drives-:}) + + Next you will have to edit or create a disk label for the disk + OpenBSD is being installed on. If there are any existing + partitions defined (for any operating system), and a disk label + is not found, you will first be given an opportunity to run + fdisk and create an OpenBSD partition. + + If fdisk is being invoked on your behalf, it will start by + displaying the current partitions defined and then allow you + to modify this information, add new partitions and change + which partition to boot from by default. If you make a mistake, + you will be allowed to repeat this procedure as necessary to + correct this. Note that you should make OpenBSD be the active + partition at least until the install has been completed. + +OpenBSDInstallPart4({:- If you have DOS or Linux partitions + defined on the disk, these will usually show up as partition + 'h', 'i' and so on.-:}) + + Note that all OpenBSD partitions in the disk label must have an + offset that makes it start within the OpenBSD part of the disk, + and a size that keeps it inside of that portion of the disk. This + is within the bounds of the 'c' partition if the disk is not being + shared with other operating systems, and within the OpenBSD fdisk + partition if the disk is being shared. + +OpenBSDInstallPart5(wd0) + +OpenBSDInstallNet({:-CD-ROM, -:},nofloppy) + +OpenBSDFTPInstall + +OpenBSDHTTPInstall + +OpenBSDTAPEInstall + +OpenBSDCDROMInstall + +OpenBSDDISKInstall({:-"wdN" or -:},,{:- or MS-DOS-:}) + +OpenBSDCommonFS + +OpenBSDCommonURL + +OpenBSDCongratulations diff --git a/distrib/notes/amd64/prep b/distrib/notes/amd64/prep new file mode 100644 index 00000000000..8f017bdc943 --- /dev/null +++ b/distrib/notes/amd64/prep @@ -0,0 +1,68 @@ +NOTE: If you wish to install OpenBSD on your whole disk, i.e. you do +not want DOS or any other operating system to reside on your hard +disk, you can skip this section and go on to the section that +describes installation, below. If you're upgrading your system from a +previous release of OpenBSD, you should have proceeded directly to the +section about upgrading; you need none of the information presented +here. + +First and foremost, before beginning the installation process, MAKE +SURE YOU HAVE A RELIABLE BACKUP of any data on your hard disk that you +wish to keep. Repartitioning your hard disk is an excellent way to +destroy important data. + +Second, if you are using a disk controller which supports disk geometry +translation, be sure to use the same parameters for OpenBSD as for DOS +or the other operating systems installed on your disk. If you do not, +it will be much harder to make OpenBSD properly coexist with them. +Utilities exist which will print out the disk geometry which DOS sees; +some versions of DOS "fdisk" also do this. If you have an "EIDE" hard +disk, DOS and OpenBSD probably won't see the same geometry, and you must +be careful to find out the DOS geometry and tell OpenBSD about it during +the installation. + +Third (but related to the second point above), if you are using a hard +disk with more sectors than DOS or your controller's BIOS supports without +some kind of software translation utility or other kludge, you MUST +BE SURE that all partitions which you want to boot from must start and end +below cylinder 1024 by the BIOS's idea of the disk, and that all DOS +partitions MUST EXIST ENTIRELY BELOW cylinder 1024, or you will either not +be able to boot OpenBSD, not be able to boot DOS, or you may experience +data loss or filesystem corruption. Be sure you aren't using geometry +translation that you don't know about, but that the DOS "fdisk" program +does! + +The OpenBSD root partition must also reside completely within the BIOS +supported part of the hard disk -- this would typically be 504M, 2G or 8G, +depending upon the age of the machine and its BIOS. Due to a limit of the +OpenBSD boot loader, the root partition must be within the first 8G even if +the BIOS supports more. Note that only the root partition has this issue, +once OpenBSD is loaded, the entire disk is available for use. + +Fourth, use the other operating system's "fdisk" program or partition +editor to create at least one of the partitions to be used for that +operating system. If that operating system is already set up to use the +entire disk, you will have to back it up, remove and recreate a smaller +partition for it, and then restore the data from that partition. You do +not have to create an OpenBSD partition at this time, the OpenBSD install- +ation will give you an opportunity to create the partition needed for +OpenBSD. + +Finally, do whatever is necessary to restore order to the partition +you took space away from. If it was a DOS partition, you probably +will need to use "format" to create a new file system on it, and then +restore your important files from your backups. Other operating +systems will have different needs; most will need to reformat the +partition, and if it was their "main" partition, will probably need +to be reinstalled. + +Once you've backed all your data up, there is a tool called fips 2.0 +that can shrink your FAT-based DOS/Windows partition to make room for +OpenBSD. It is included in the MACHINE tools area of this distribution as +a convenience. It is strongly advised that you read its documentation +and understand the consequences of your actions before using it. In some +cases, defragmenting your disk and running fips may be much faster than +reinstalling your DOS partition from the backup. + +Your hard disk is now prepared to have OpenBSD installed on it, and +you should proceed with the installation instructions. diff --git a/distrib/notes/amd64/upgrade b/distrib/notes/amd64/upgrade new file mode 100644 index 00000000000..48e2b2689c4 --- /dev/null +++ b/distrib/notes/amd64/upgrade @@ -0,0 +1,103 @@ +dnl $OpenBSD: upgrade,v 1.1 2004/02/07 21:29:10 deraadt Exp $ +dnl OpenBSDUpgrade({:-the CD-ROM or an installation floppy as you would do for +dnl a new installation-:}) +Due to the change from a.out to ELF binary format in OpenBSD OSREV, +upgrades can be a complex, delicate process. The best solution, whenever +possible, is to backup your data and reinstall from scratch. + +The second best solution is to remove all ports, third party programs and +libraries installed on your system; upgrade; and then add ELF versions of +the removed files. + +In all cases, once you start the upgrade you MUST complete it. If the +upgrade process fails or is abandoned before it completes you will almost +certainly be left with a non-functional system. + +Finally, you cannot use the bsd.rd kernel to upgrade the system. The +existing bootblocks on your system cannot boot the OSREV bsd.rd. + +If you must do an upgrade while preserving the functionality of any +existing a.out binary files, then the rest of this section will guide you +through that process. + +The two main hurdles in upgrading from an a.out system to an ELF OpenBSD +OSREV system while preserving the functioning of a.out binaries are: +- the a.out binary emulation, required for compatibility with a.out + binaries using shared libraries, is not enabled by default, and requires + an explicit configuration change. +- a.out shared libraries (lib*.so) need to be moved to a specific location + for proper operation of older binaries. + +Before you start the upgrade process, the a.out emulation area needs to be +set up. It needs to be put inside a /emul/a.out hierarchy. This directory can, +however, be a symbolic link, should the available space in the root partition +not be enough. + +It is recommended that the following instructions and commands are issued in +single-user mode. + +The /emul/a.out hierarchy should be populated by the a.out shared libraries. +An easy way to do it is to run the following commands as root: + + mkdir -p /emul/a.out/var/run + tar cf - /sbin/ldconfig /usr/bin/ldd /usr/libexec/ld.so | + tar -C /emul/a.out -xpf - + for lib in $(/sbin/ldconfig -r | + awk '/=>/ { print $3 }'); + do + dirname $lib; + done | sort -u > /root/a.out-libdirs + tar cf - $(find $(< /root/a.out-libdirs) -name "lib*.so.*") | + tar -C /emul/a.out -xpf - + +Then, a cache of these shared libraries must be generated with: + + cp /var/run/ld.so.hints /var/run/ld.so.hints.backup + /sbin/ldconfig -s $(/usr/bin/sed 's,^/,/emul/a.out/,' /root/a.out-libdirs) + /bin/mv /var/run/ld.so.hints /emul/a.out/var/run + /bin/mv /var/run/ld.so.hints.backups /var/run/ld.so.hints + +The last step before the upgrade is to enable the a.out emulation, in +order to be sure that /etc/rc.local or any other customization you have +made to the system will still run: + + echo "kern.emul.aout=1" >> /etc/sysctl.conf + + +ATTENTION! Several configuration files under /etc, such as /etc/login.conf, +will refer to existing a.out binaries. DO NOT UPGRADE YOUR SYSTEM UNLESS +YOU HAVE ENABLED A.OUT EMULATION FIRST! After you merge configuration files +changes and replace or remove your existing a.out binaries, it will be +possible to disable a.out emulation. + + +The upgrade is now possible. Boot from the CD-ROM or an installation +floppy, as you would do for a new installation. + +When prompted, select the (U)pgrade option rather than the (I)nstall +option at the prompt in the install process. + +The upgrade script will ask you for the existing root partition, and +will use the existing filesystems defined in /etc/fstab to install the +new system in. It will also use your existing network parameters. + +From then, the upgrade procedure is very close to the installation +procedure described earlier in this document. Note that the upgrade +procedure will not let you pick the ``etc{:--:}OSrev.tgz'' set, so as to +preserve your files in `/etc' which you are likely to have customized +since a previous installation. + +When the upgrade procedure tells you that the upgrade is complete, do not +reboot the system yet. + +However, it is strongly advised that you unpack the etc{:--:}OSrev.tgz set in +a temporary directory and merge changes by hand, since all components of +your system may not function correctly until your files in `/etc' are +updated. + +After the upgrade is completed, it is now possible to remove the old a.out +shared libraries from their initial locations: + + rm -f $(file $(find $(< /root/a.out-libdirs) -name "lib*.so.*") | + awk -F: '/demand paged/ { print $1 }') + rm -f /root/a.out-libdirs diff --git a/distrib/notes/amd64/whatis b/distrib/notes/amd64/whatis new file mode 100644 index 00000000000..15bbdcc830c --- /dev/null +++ b/distrib/notes/amd64/whatis @@ -0,0 +1,5 @@ +dnl $OpenBSD: whatis,v 1.1 2004/02/07 21:29:10 deraadt Exp $ +For the MACHINE, OpenBSD OSREV brings greater stability and security, +including a stricter memory permission scheme. As a side effect of the +full security audit, many userland programs have been significantly +cleaned up and debugged. diff --git a/distrib/notes/amd64/xfer b/distrib/notes/amd64/xfer new file mode 100644 index 00000000000..9432057b87f --- /dev/null +++ b/distrib/notes/amd64/xfer @@ -0,0 +1,28 @@ +dnl $OpenBSD: xfer,v 1.1 2004/02/07 21:29:10 deraadt Exp $ +Installation is supported from several media types, including: + + CD-ROM + FFS partitions + DOS (FAT) partitions + EXT2 partitions + Tape +dnl Remote NFS partition + FTP + HTTP + +If you can't (or don't want to) boot off a CD-ROM, you'll need to have +a floppy disk (1.44MB required). + +OpenBSDXferFloppyFromDOS + +OpenBSDXferFloppyFromUNIX + + +OpenBSDXferShortPrelude + + +OpenBSDXferBareTape(xbase xfont xlink xserv xshare) + +dnl OpenBSDXferNFS +dnl +OpenBSDXferFFS |