diff --git a/en_US.ISO8859-1/htdocs/releases/12.0R/errata/errata.xml b/en_US.ISO8859-1/htdocs/releases/12.0R/errata/errata.xml new file mode 100644 index 0000000000..cac5612ae1 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/12.0R/errata/errata.xml @@ -0,0 +1,103 @@ + + + %release; + + %sponsor; + + %vendor; + + +]> + +
+ + &os; &release; Errata + + The &os; Project + + $FreeBSD$ + + + 2015 + + The &os; Documentation Project + + + + &tm-attrib.freebsd; + &tm-attrib.intel; + &tm-attrib.sparc; + &tm-attrib.general; + + + + This document lists errata items for &os; &release;, + containing significant information discovered after the release + or too late in the release cycle to be otherwise included in the + release documentation. + This information includes security advisories, as well as news + relating to the software or documentation that could affect its + operation or usability. An up-to-date version of this document + should always be consulted before installing this version of + &os;. + + This errata document for &os; &release; + will be maintained until the release of &os; &release.next;. + + + + + Introduction + + This errata document contains late-breaking news + about &os; &release; + Before installing this version, it is important to consult this + document to learn about any post-release discoveries or problems + that may already have been found and fixed. + + Any version of this errata document actually distributed + with the release (for example, on a CDROM distribution) will be + out of date by definition, but other copies are kept updated on + the Internet and should be consulted as the current + errata for this release. These other copies of the + errata are located at + , + plus any sites + which keep up-to-date mirrors of this location. + + Source and binary snapshots of &os; &release.branch; also + contain up-to-date copies of this document (as of the time of + the snapshot). + + For a list of all &os; CERT security advisories, see + . + + + + Security Advisories + + &security; + + + + Errata Notices + + &errata; + + + + Open Issues + + No open issues. + + + + Late-Breaking News + + No news. + +
diff --git a/en_US.ISO8859-1/htdocs/releases/12.0R/hardware/hardware.xml b/en_US.ISO8859-1/htdocs/releases/12.0R/hardware/hardware.xml new file mode 100644 index 0000000000..2b864374a4 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/12.0R/hardware/hardware.xml @@ -0,0 +1,1460 @@ + + + %release; + + %sponsor; + + %vendor; + + + + +%devauto; +]> +
+ &os; &release.current; Hardware Notes + + + The &os; Documentation Project + + $FreeBSD$ + + + 2000 + 2001 + 2002 + 2003 + 2004 + 2005 + 2006 + 2007 + 2008 + 2009 + 2010 + 2011 + 2012 + 2013 + 2014 + 2015 + 2016 + 2017 + The &os; Documentation Project + + + + &tm-attrib.freebsd; + &tm-attrib.amd; + &tm-attrib.fujitsu; + &tm-attrib.ibm; + &tm-attrib.intel; + &tm-attrib.sparc; + &tm-attrib.sun; + &tm-attrib.general; + + + + + + Introduction + + This document contains the hardware compatibility notes for + &os; &release.current;. It lists the hardware platforms + supported by &os;, as well as the various types of hardware + devices (storage controllers, network interfaces, and so on), + along with known working instances of these devices. + + + + Supported Processors and System Boards + + This section provides some architecture-specific information + about the specific processors and systems that are supported by + each architecture. + + + amd64 + + Since mid-2003 &os;/&arch.amd64; has supported the AMD64 + (Hammer) and &intel; EM64T architecture, and is + now one of the Tier-1 platforms (fully supported + architecture), which are expected to be Production Quality + with respects to all aspects of the &os; operating system, + including installation and development environments. + + Note that there are two names for this architecture, AMD64 + (AMD) and Intel EM64T (Extended Memory 64-bit Technology). + 64-bit mode of the two architectures are almost compatible + with each other, and &os;/&arch.amd64; supports them + both. + + As of this writing, the following processors are + supported: + + + + &amd.athlon;64 (Clawhammer). + + + + &amd.opteron; (Sledgehammer). + + + + &amd.sempron;. + + + + &amd.turion;. + + + + &amd.phenom;. + + + + All multi-core &intel; &xeon; processors except + Sossaman have EM64T support. + + + + The single-core &intel; &xeon; + processors Nocona, Irwindale, + Potomac, and Cranford have + EM64T support. + + + + All &intel; &core; 2 (not &core; Duo) and later + processors + + + + All &intel; &core; i range of processors + + + + All &intel; &pentium; D processors + + + + All &intel; ¢rino; Duo and ¢rino; Pro platforms + + + + &intel; &pentium; 4s and &celeron; Ds using + the Cedar Mill core have EM64T + support. + + + + Some &intel; &pentium; 4s and &celeron; Ds using + the Prescott core have EM64T support. See + the Intel + Processor Spec Finder for the definitive answer about + EM64T support in Intel processors. + + + + + &intel; EM64T is an extended version of IA-32 (x86) and + different from &intel; IA-64 (Itanium) architecture. Some of + &intel;'s old documentation refers to &intel; EM64T as + 64-bit extension technology or + IA-32e. + + Both Uniprocessor (UP) and Symmetric Multi-processor (SMP) + configurations are supported. + + In many respects, &os;/&arch.amd64; is similar to + &os;/&arch.i386;, in terms of drivers supported. Generally, + drivers that already function correctly on other 64-bit + platforms should work. + + + + + i386 + + &os;/&arch.i386; runs on a wide variety of IBM PC + compatible machines. Due to the wide range of + hardware available for this architecture, it is impossible + to exhaustively list all combinations of equipment supported + by &os;. Nevertheless, some general guidelines are + presented here. + + Almost all &i386;-compatible processors with a floating + point unit are supported. All &intel; processors beginning + with the 80486 are supported, including the 80486, &pentium;, + &pentium; Pro, &pentium; II, &pentium; III, &pentium; 4, and + variants thereof, such as the &xeon; and &celeron; processors. + All &i386;-compatible AMD processors are also supported, + including the &am486;, &am5x86;, K5, &amd.k6; (and variants), + &amd.athlon; (including Athlon-MP, Athlon-XP, Athlon-4, and + Athlon Thunderbird), and &amd.duron; processors. The AMD + Élan SC520 embedded processor is supported. The + Transmeta Crusoe is recognized and supported, as are + &i386;-compatible processors from Cyrix and NexGen. + + There is a wide variety of motherboards available for this + architecture. Motherboards using the ISA, VLB, EISA, AGP, and + PCI expansion buses are well-supported. There is some + limited support for the MCA (MicroChannel) + expansion bus used in the IBM PS/2 line of PCs. + + Symmetric multi-processor (SMP) systems are generally + supported by &os;, although in some cases, BIOS or motherboard + bugs may generate some problems. Perusal of the archives of + the &a.smp; may yield some clues. + + &os; will take advantage of SMT (Symmetric MultiThreading, + also known as HyperThreading on &intel; CPUs) on the supported + CPUs. The GENERIC kernel which is + installed by default will automatically detect the additional + logical processors. The default &os; scheduler recognizes + processor topology on the system and selects logical and + physical processors to obtain optimal performance. + The &man.smp.4; manual page has more details. + + &os; will take advantage of Physical Address Extensions + (PAE) support on CPUs that support this feature. A kernel + with the PAE feature enabled will detect + memory above 4 gigabytes and allow it to be used by the + system. This feature places constraints on the device drivers + and other features of &os; which may be used; consult the + &man.pae.4; manual page for more details. + + &os; will generally run on i386-based laptops, albeit with + varying levels of support for certain hardware features such + as sound, graphics, power management, and PCCARD expansion + slots. These features tend to vary in idiosyncratic ways + between machines, and frequently require special-case support + in &os; to work around hardware bugs or other oddities. When + in doubt, a search of the archives of the &a.mobile; may be + useful. + + Most modern laptops (as well as many desktops) use the + Advanced Configuration and Power Management (ACPI) standard. + &os; supports ACPI via the ACPI Component Architecture + reference implementation from &intel;, as described in the + &man.acpi.4; manual page. The use of ACPI causes + instabilities on some machines and it may be necessary to + disable the ACPI driver, which is normally loaded via a kernel + module. This may be accomplished by adding the following line + to /boot/device.hints: + + hint.acpi.0.disabled="1" + + Users debugging ACPI-related problems may find it useful + to disable portions of the ACPI functionality. The + &man.acpi.4; manual page has more information on how to do + this via loader tunables. + + ACPI depends on a Differentiated System Descriptor Table + (DSDT) provided by each machine's BIOS. Some machines have + bad or incomplete DSDTs, which prevents ACPI from functioning + correctly. Replacement DSDTs for some machines can be found + at the DSDT + section of the ACPI4Linux project + Web site. &os; can use these DSDTs to override the DSDT + provided by the BIOS; see the &man.acpi.4; manual page for + more information. + + + + powerpc + + All Apple PowerPC machines with built-in USB are supported, + as well a limited selection of non-Apple machines, + including KVM on POWER7 + + SMP is supported on all systems with more than + 1 processor. + + + + sparc64 + + This section describes the systems currently known to be + supported by &os; on the Fujitsu &sparc64; and Sun &ultrasparc; + platforms. + + SMP is supported on all systems with more than 1 + processor. + + When using the GENERIC kernel, + &os;/&arch.sparc64; systems not equipped with a framebuffer + supported by the &man.creator.4; (Sun Creator, Sun Creator3D + and Sun Elite3D) or &man.machfb.4; (Sun PGX and Sun PGX64 + as well as the ATI Mach64 chips found onboard in for example + &sun.blade; 100, &sun.blade; 150, &sun.ultra; 5 and &sun.ultra; 10) + driver must use the serial console. + + If you have a system that is not listed here, it may not + have been tested with &os; &release.current;. We encourage + you to try it and send a note to the &a.sparc; with your + results, including which devices work and which do not. + + The following systems are fully supported by &os;: + + + + Naturetech GENIALstation 777S + + + + &sun.blade; 100 + + + + &sun.blade; 150 + + + + &sun.enterprise; 150 + + + + &sun.enterprise; 220R + + + + &sun.enterprise; 250 + + + + &sun.enterprise; 420R + + + + &sun.enterprise; 450 + + + + &sun.fire; B100s (support for the on-board NICs first + appeared in 8.1-RELEASE) + + + + &sun.fire; V100 + + + + &sun.fire; V120 + + + + Sun &netra; t1 100/105 + + + + Sun &netra; T1 AC200/DC200 + + + + Sun &netra; t 1100 + + + + Sun &netra; t 1120 + + + + Sun &netra; t 1125 + + + + Sun &netra; t 1400/1405 + + + + Sun &netra; 120 + + + + Sun &netra; X1 + + + + Sun &sparcengine; Ultra AX1105 + + + + Sun &sparcengine; Ultra AXe + + + + Sun &sparcengine; Ultra AXi + + + + Sun &sparcengine; Ultra AXmp + + + + Sun &sparcengine; CP1500 + + + + &sun.ultra; 1 + + + + &sun.ultra; 1E + + + + &sun.ultra; 2 + + + + &sun.ultra; 5 + + + + &sun.ultra; 10 + + + + &sun.ultra; 30 + + + + &sun.ultra; 60 + + + + &sun.ultra; 80 + + + + &sun.ultra; 450 + + + + The following systems are partially supported by &os;. In + particular the fiber channel controllers in SBus-based systems are not + supported. However, it is possible to use these with a SCSI controller + supported by the &man.esp.4; driver (Sun ESP SCSI, Sun FAS Fast-SCSI + and Sun FAS366 Fast-Wide SCSI controllers). + + + + &sun.enterprise; 3500 + + + + &sun.enterprise; 4500 + + + + Starting with 7.2-RELEASE, &arch.sparc64; systems based on Sun + &ultrasparc; III and beyond are also supported by &os;, which includes + the following known working systems: + + + + &sun.blade; 1000 + + + + &sun.blade; 1500 + + + + &sun.blade; 2000 + + + + &sun.blade; 2500 + + + + &sun.fire; 280R + + + + &sun.fire; V210 + + + + &sun.fire; V215 (support first appeared in 7.3-RELEASE and 8.1-RELEASE) + + + + &sun.fire; V240 + + + + &sun.fire; V245 (support first appeared in 7.3-RELEASE and 8.1-RELEASE) + + + + &sun.fire; V250 + + + + &sun.fire; V440 (support for the on-board NICs first + appeared in 7.3-RELEASE and 8.0-RELEASE) + + + + &sun.fire; V480 (501-6780 and 501-6790 centerplanes only, for + which support first appeared in 7.3-RELEASE and 8.1-RELEASE, + other centerplanes might work beginning with 8.3-RELEASE and 9.0-RELEASE) + + + + &sun.fire; V880 + + + + &sun.fire; V890 (support first appeared in 7.4-RELEASE and 8.1-RELEASE, + non-mixed &ultrasparc; IV/IV+ CPU-configurations only) + + + + &netra; 20/&netra; T4 + + + + The following Sun &ultrasparc; systems are not tested but + believed to be also supported by &os;: + + + + &sun.fire; V125 + + + + &sun.fire; V490 (support first appeared in 7.4-RELEASE and 8.1-RELEASE, + non-mixed &ultrasparc; IV/IV+ CPU-configurations only) + + + + Starting with 7.4-RELEASE and 8.1-RELEASE, &arch.sparc64; systems based on + Fujitsu &sparc64; V are also supported by &os;, which + includes the following known working systems: + + + + Fujitsu &primepower; 250 + + + + The following Fujitsu &primepower; systems are not tested but + believed to be also supported by &os;: + + + + Fujitsu &primepower; 450 + + + + Fujitsu &primepower; 650 + + + + Fujitsu &primepower; 850 + + + + + + + + + + Supported Devices + + This section describes the devices currently known to be + supported by &os;. Other configurations may also work, but + simply have not been tested yet. Feedback, updates, and + corrections to this list are encouraged. + + Where possible, the drivers applicable to each device or + class of devices is listed. If the driver in question has a + manual page in the &os; base distribution (most should), it is + referenced here. Information on specific models of supported + devices, controllers, etc. can be found in the manual + pages. + + + The device lists in this document are being generated + automatically from &os; manual pages. This means that some + devices, which are supported by multiple drivers, may appear + multiple times. + + + + Disk Controllers + + [&arch.amd64;, &arch.i386;, &arch.sparc64;] + IDE/ATA controllers (&man.ata.4; driver) + + &hwlist.aac; + + &hwlist.adv; + + &hwlist.adw; + + &hwlist.aha; + + &hwlist.ahc; + + &hwlist.ahci; + + &hwlist.ahd; + + &hwlist.aic; + + &hwlist.amr; + + &hwlist.arcmsr; + + &hwlist.bt; + + &hwlist.ciss; + + &hwlist.dpt; + + + [&arch.amd64;, &arch.i386;] Booting from these + controllers is supported. EISA adapters are not + supported. + + + &hwlist.esp; + + &hwlist.hpt27xx; + + &hwlist.hptiop; + + &hwlist.hptmv; + + &hwlist.hptrr; + + &hwlist.ida; + + &hwlist.iir; + + &hwlist.ips; + + &hwlist.isci; + + &hwlist.isp; + + &hwlist.mfi; + + &hwlist.mlx; + + + [&arch.amd64;, &arch.i386;] Booting from these + controllers is supported. EISA adapters are not + supported. + + + &hwlist.mly; + + &hwlist.mpr; + + &hwlist.mps; + + &hwlist.mpt; + + &hwlist.mrsas; + + &hwlist.mvs; + + &hwlist.ncr; + + &hwlist.ncv; + + &hwlist.nsp; + + &hwlist.pms; + + &hwlist.pst; + + &hwlist.siis; + + &hwlist.stg; + + &hwlist.sym; + + &hwlist.trm; + + &hwlist.twa; + + &hwlist.twe; + + &hwlist.tws; + + &hwlist.vpo; + + With all supported SCSI controllers, full support is + provided for SCSI-I, SCSI-II, and SCSI-III peripherals, + including hard disks, optical disks, tape drives (including + DAT, 8mm Exabyte, Mammoth, and DLT), medium changers, + processor target devices and CD-ROM drives. WORM devices that + support CD-ROM commands are supported for read-only access by + the CD-ROM drivers (such as &man.cd.4;). WORM/CD-R/CD-RW + writing support is provided by &man.cdrecord.1;, which is a + part of the sysutils/cdrtools port in the Ports + Collection. + + The following CD-ROM type systems are supported at this + time: + + + + SCSI interface (also includes ProAudio Spectrum and + SoundBlaster SCSI) (&man.cd.4;) + + + + ATAPI IDE interface (&man.acd.4;) + + + + + + Ethernet Interfaces + + &hwlist.ae; + + &hwlist.age; + + &hwlist.ale; + + &hwlist.aue; + + &hwlist.axe; + + ASIX Electronics AX88178A/AX88179 USB Gigabit Ethernet + adapters (&man.axge.4; driver) + + &hwlist.bce; + + [&arch.amd64;, &arch.i386;] Broadcom BCM4401 based Fast + Ethernet adapters (&man.bfe.4; driver) + + &hwlist.bge; + + &hwlist.bnxt; + + &hwlist.bxe; + + &hwlist.cas; + + &hwlist.cdce; + + [&arch.amd64;, &arch.i386;] Crystal Semiconductor + CS89x0-based NICs (&man.cs.4; driver) + + &hwlist.cue; + + &hwlist.cxgb; + + &hwlist.cxgbe; + + &hwlist.dc; + + &hwlist.de; + + &hwlist.ed; + + &hwlist.em; + + &hwlist.ep; + + Agere ET1310 Gigabit Ethernet adapters + (&man.et.4; driver) + + &hwlist.ex; + + &hwlist.fe; + + &hwlist.fxp; + + &hwlist.gem; + + &hwlist.hme; + + &hwlist.ipheth; + + &hwlist.ixgb; + + &hwlist.ixgbe; + + &hwlist.ixl; + + &hwlist.jme; + + &hwlist.kue; + + &hwlist.lge; + + &hwlist.mlx4en; + + &hwlist.mlx5en; + + &hwlist.msk; + + &hwlist.mxge; + + &hwlist.my; + + &hwlist.nfe; + + &hwlist.nge; + + &hwlist.nxge; + + &hwlist.oce; + + &hwlist.pcn; + + &hwlist.qlxgb; + + &hwlist.qlxgbe; + + &hwlist.qlxge; + + &hwlist.re; + + &hwlist.rl; + + &hwlist.rue; + + &hwlist.sf; + + &hwlist.sfxge; + + &hwlist.sge; + + &hwlist.sis; + + &hwlist.sk; + + &hwlist.smsc; + + &hwlist.sn; + + &hwlist.ste; + + &hwlist.stge; + + &hwlist.ti; + + &hwlist.tl; + + [&arch.amd64;, &arch.i386;] SMC 83c17x + (EPIC)-based Ethernet NICs (&man.tx.4; driver) + + &hwlist.txp; + + &hwlist.udav; + + &hwlist.urndis; + + &hwlist.vge; + + &hwlist.vr; + + &hwlist.vte; + + &hwlist.vx; + + &hwlist.vxge; + + &hwlist.wb; + + &hwlist.xe; + + &hwlist.xl; + + + + + FDDI Interfaces + + [&arch.i386;] DEC DEFPA PCI (&man.fpa.4; driver) + + [&arch.i386;] DEC DEFEA EISA (&man.fpa.4; driver) + + + + Wireless Network Interfaces + + [&arch.amd64;, &arch.i386;] Cisco/Aironet + 802.11b wireless adapters (&man.an.4; driver) + + &hwlist.ath; + + &hwlist.bwi; + + &hwlist.bwn; + + [&arch.i386;, &arch.amd64;] Intel PRO/Wireless 2100 + MiniPCI network adapter (&man.ipw.4; driver) + + [&arch.i386;, &arch.amd64;] Intel PRO/Wireless + 2200BG/2915ABG MiniPCI and 2225BG PCI network adapters + (&man.iwi.4; driver) + + [&arch.i386;, &arch.amd64;] Intel Dual Band Wireless AC + 3160/7260/7265 IEEE 802.11ac network adapters (&man.iwm.4; + driver) + + [&arch.i386;, &arch.amd64;] Intel Wireless WiFi Link + 4965AGN IEEE 802.11n PCI network adapters + (&man.iwn.4; driver) + + [&arch.i386;, &arch.amd64;] Marvell Libertas IEEE 802.11b/g + PCI network adapters (&man.malo.4; driver) + + Marvell 88W8363 IEEE 802.11n wireless network + adapters (&man.mwl.4; driver) + + &hwlist.otus; + + &hwlist.ral; + + &hwlist.rsu; + + Realtek RTL8192C, RTL8188E, RTL8812A and RTL8821A based + PCIe IEEE 802.11b/g/n wireless network adapters (&man.rtwn.4; + driver) + + &hwlist.rum; + + &hwlist.run; + + &hwlist.uath; + + &hwlist.upgt; + + &hwlist.ural; + + &hwlist.urtw; + + [&arch.amd64;, &arch.i386;] Lucent + Technologies WaveLAN/IEEE 802.11b wireless network adapters + and workalikes using the Lucent Hermes, Intersil PRISM-II, + Intersil PRISM-2.5, Intersil Prism-3, and Symbol Spectrum24 + chipsets (&man.wi.4; driver) + + [&arch.i386;, &arch.amd64;] Intel PRO/Wireless 3945ABG + MiniPCI network adapters (&man.wpi.4; driver) + + &hwlist.zyd; + + + + Miscellaneous Networks + + &hwlist.ce; + + &hwlist.cx; + + &hwlist.cp; + + &hwlist.ctau; + + &hwlist.cm; + + + + Serial Interfaces + + [&arch.amd64;, &arch.i386;] PC standard + 8250, 16450, and 16550-based serial ports (&man.sio.4; + driver) + + &hwlist.uart; + + &hwlist.scc; + + [&arch.amd64;, &arch.i386;] AST 4 port serial card using + shared IRQ + + + + ARNET 8 port serial card using shared IRQ + + + + ARNET (now Digiboard) Sync 570/i high-speed + serial + + + + [&arch.i386;] Boca multi-port serial cards + + + + Boca BB1004 4-Port serial card (Modems + not supported) + + + + Boca IOAT66 6-Port serial card (Modems + supported) + + + + Boca BB1008 8-Port serial card (Modems + not supported) + + + + Boca BB2016 16-Port serial card (Modems + supported) + + + + [&arch.i386;] Comtrol Rocketport card (&man.rp.4; + driver) + + [&arch.i386;] Cyclades Cyclom-Y serial board (&man.cy.4; + driver) + + [&arch.i386;] STB 4 port card using shared IRQ + + [&arch.amd64;, &arch.i386;] PCI-Based multi-port serial + boards (&man.puc.4; driver) + + + + [&arch.amd64;, &arch.i386;] Actiontech 56K PCI + + + + [&arch.amd64;, &arch.i386;] Avlab Technology, PCI IO 2S + and PCI IO 4S + + + + [&arch.amd64;, &arch.i386;] Comtrol RocketPort 550 + + + + [&arch.amd64;, &arch.i386;] Decision Computers PCCOM + 4-port serial and dual port RS232/422/485 + + + + [&arch.amd64;, &arch.i386;] Dolphin Peripherals + 4025/4035/4036 + + + + [&arch.amd64;, &arch.i386;] IC Book Labs Dreadnought + 16x Lite and Pro + + + + [&arch.amd64;, &arch.i386;] Lava Computers + 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550 + + + + [&arch.amd64;, &arch.i386;] Middle Digital, Weasle + serial port + + + + [&arch.amd64;, &arch.i386;] Moxa Industio CP-114, + Smartio C104H-PCI and C168H/PCI + + + + [&arch.amd64;, &arch.i386;] NEC PK-UG-X001 and + PK-UG-X008 + + + + [&arch.amd64;, &arch.i386;] Netmos NM9835 + PCI-2S-550 + + + + [&arch.amd64;, &arch.i386;] Oxford Semiconductor + OX16PCI954 PCI UART + + + + [&arch.amd64;, &arch.i386;] Syba Tech SD-LAB + PCI-4S2P-550-ECP + + + + [&arch.amd64;, &arch.i386;] SIIG Cyber I/O PCI + 16C550/16C650/16C850 + + + + [&arch.amd64;, &arch.i386;] SIIG Cyber 2P1S PCI + 16C550/16C650/16C850 + + + + [&arch.amd64;, &arch.i386;] SIIG Cyber 2S1P PCI + 16C550/16C650/16C850 + + + + [&arch.amd64;, &arch.i386;] SIIG Cyber 4S PCI + 16C550/16C650/16C850 + + + + [&arch.amd64;, &arch.i386;] SIIG Cyber Serial (Single + and Dual) PCI 16C550/16C650/16C850 + + + + [&arch.amd64;, &arch.i386;] Syba Tech + Ltd. PCI-4S2P-550-ECP + + + + [&arch.amd64;, &arch.i386;] Titan PCI-200H and + PCI-800H + + + + [&arch.amd64;, &arch.i386;] US Robotics (3Com) 3CP5609 + modem + + + + [&arch.amd64;, &arch.i386;] VScom PCI-400 and + PCI-800 + + + + &hwlist.rc; + + + + + Sound Devices + + &hwlist.snd.ad1816; + + &hwlist.snd.als4000; + + &hwlist.snd.atiixp; + + &hwlist.snd.audiocs; + + &hwlist.snd.cmi; + + &hwlist.snd.cs4281; + + &hwlist.snd.csa; + + &hwlist.snd.ds1; + + &hwlist.snd.emu10k1; + + &hwlist.snd.emu10kx; + + &hwlist.snd.envy24; + + &hwlist.snd.envy24ht; + + &hwlist.snd.es137x; + + &hwlist.snd.ess; + + &hwlist.snd.fm801; + + &hwlist.snd.gusc; + + &hwlist.snd.hda; + + &hwlist.snd.hdspe; + + &hwlist.snd.ich; + + &hwlist.snd.maestro; + + &hwlist.snd.maestro3; + + &hwlist.snd.mss; + + &hwlist.snd.neomagic; + + &hwlist.snd.sbc; + + &hwlist.snd.solo; + + &hwlist.snd.spicds; + + &hwlist.snd.t4dwave; + + &hwlist.snd.via8233; + + &hwlist.snd.via82c686; + + &hwlist.snd.vibes; + + + + + Camera and Video Capture Devices + + &hwlist.bktr; + + [&arch.i386;] Connectix QuickCam + + + + USB Devices + + [&arch.amd64;, &arch.i386;] A + range of USB peripherals are supported; devices known to work + are listed in this section. 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. + + + [&arch.amd64;, &arch.i386;] + USB Ethernet adapters can be found in the section listing + Ethernet + interfaces. + + + + [&arch.amd64;, &arch.i386;] + USB Bluetooth adapters can be found in Bluetooth section. + + + &hwlist.ohci; + + &hwlist.uhci; + + [&arch.amd64;, &arch.i386;] USB + 2.0 controllers using the EHCI interface (&man.ehci.4; + driver) + + [&arch.amd64;, &arch.i386;] Hubs + + [&arch.amd64;, &arch.i386;] Keyboards (&man.ukbd.4; driver) + + [&arch.amd64;, &arch.i386;] Miscellaneous + + + + Assist Computer Systems PC Camera C-M1 + + + + ActiveWire I/O Board + + + + Creative Technology Video Blaster WebCam Plus + + + + D-Link DSB-R100 USB Radio (&man.ufm.4; driver) + + + + Mirunet AlphaCam Plus + + + + &hwlist.urio; + + &hwlist.umodem; + + [&arch.amd64;, &arch.i386;] Mice (&man.ums.4; driver) + + &hwlist.ulpt; + + &hwlist.ubsa; + + &hwlist.ubser; + + &hwlist.uftdi; + + &hwlist.uplcom; + + &hwlist.umct; + + &hwlist.umass; + + [&arch.amd64;, &arch.i386;] Audio Devices + (&man.uaudio.4; driver) + + &hwlist.uvisor; + + + + IEEE 1394 (Firewire) Devices + + &hwlist.fwohci; + + [&arch.amd64;, &arch.i386;, &arch.sparc64;] Serial Bus + Protocol 2 (SBP-2) storage devices (&man.sbp.4; driver) + + + + Bluetooth Devices + + &hwlist.ng.bt3c; + + &hwlist.ng.ubt; + + + + Cryptographic Accelerators + + &hwlist.hifn; + + &hwlist.safe; + + &hwlist.ubsec; + + + + Miscellaneous + + [&arch.amd64;, &arch.i386;] FAX-Modem/PCCARD + + + + MELCO IGM-PCM56K/IGM-PCM56KH + + + + Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD + terminal) + + + + [&arch.amd64;, &arch.i386;] Floppy drives + (&man.fdc.4; driver) + + [&arch.amd64;, &arch.i386;] VGA-compatible video cards + (&man.vga.4; driver) + + + Information regarding specific video cards and + compatibility with Xorg can be + found at http://www.x.org/. + + + [&arch.amd64;, &arch.i386;] Keyboards including: + + + + [&arch.i386;] AT-style keyboards (&man.atkbd.4; + driver) + + + + [&arch.amd64;, &arch.i386;] PS/2 keyboards + (&man.atkbd.4; driver) + + + + [&arch.amd64;, &arch.i386;] + USB keyboards (&man.ukbd.4; driver) + + + + [&arch.amd64;, &arch.i386;] + Pointing devices including: + + + + [&arch.amd64;, &arch.i386;] Bus mice and + compatible devices (&man.mse.4; driver) + + + + [&arch.amd64;, &arch.i386;] PS/2 mice and compatible + devices, including many laptop pointing devices + (&man.psm.4; driver) + + + + Serial mice and compatible devices + + + + [&arch.amd64;, &arch.i386;] + USB mice (&man.ums.4; driver) + + + + + &man.moused.8; has more information on using pointing + devices with &os;. Information on using pointing devices + with Xorg can be found at http://www.x.org/. + + + [&arch.amd64;, &arch.i386;] PC standard + parallel ports (&man.ppc.4; driver) + + [&arch.i386;, &arch.amd64;] PC-compatible joysticks + (&man.joy.4; driver) + + [&arch.i386;] PHS Data Communication Card/PCCARD + + + + NTT DoCoMo P-in Comp@ct + + + + Panasonic KX-PH405 + + + + SII MC-P200 + + + + [&arch.i386;] Xilinx XC6200-based reconfigurable hardware + cards compatible with the HOT1 from Virtual Computers (xrpu + driver). + + + +
diff --git a/en_US.ISO8859-1/htdocs/releases/12.0R/readme/readme.xml b/en_US.ISO8859-1/htdocs/releases/12.0R/readme/readme.xml new file mode 100644 index 0000000000..f1dbe358a1 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/12.0R/readme/readme.xml @@ -0,0 +1,411 @@ + + + %release; +]> + +
+ &os; &release.current; README + + + The &os; Project + + $FreeBSD$ + + + 2000 + 2001 + 2002 + 2003 + 2004 + 2005 + 2006 + 2007 + 2008 + 2009 + 2010 + 2011 + 2012 + 2013 + 2014 + 2015 + The &os; Documentation Project + + + + &tm-attrib.freebsd; + &tm-attrib.intel; + &tm-attrib.opengroup; + &tm-attrib.sparc; + &tm-attrib.general; + + + + This document gives a brief introduction to &os; + &release.current;. It includes some information on how to + obtain &os;, a listing of various ways to contact the &os; + Project, and pointers to some other sources of + information. + + + + + Introduction + + This distribution is a &release.type; of &os; &release.current;, the + latest point along the &release.branch; branch. + + + About &os; + + &os; is an operating system based on 4.4 BSD Lite for + AMD64 and Intel EM64T based PC hardware (&arch.amd64;), + Intel, AMD, Cyrix or NexGen x86 based PC hardware (&arch.i386;), + and &ultrasparc; machines (&arch.sparc64;). Versions + for the &arm; (&arch.arm;), &mips; (&arch.mips;), and + &powerpc; (&arch.powerpc;) architectures are currently under + development as well. &os; works with a wide variety of + peripherals and configurations and can be used for everything + from software development to games to Internet Service + Provision. + + This release of &os; contains everything you need to run + such a system, including full source code for the kernel and + all utilities in the base distribution. With the source + distribution installed, you can literally recompile the entire + system from scratch with one command, making it ideal for + students, researchers, or users who simply want to see how it + all works. + + A large collection of third-party ported software (the + Ports Collection) is also provided to make it + easy to obtain and install all your favorite traditional &unix; + utilities for &os;. Each port consists of a + set of scripts to retrieve, configure, build, and install a + piece of software, with a single command. Over &os.numports; + ports, from editors to programming languages to graphical + applications, make &os; a powerful and comprehensive operating + environment that extends far beyond what's provided by many + commercial versions of &unix;. Most ports are also available as + pre-compiled packages, which can be quickly + installed from the installation program. + + + + Target Audience + + This &release.type; is aimed primarily at early adopters + and various other users who want to get involved with the + ongoing development of &os;. While the &os; development team + tries its best to ensure that each &release.type; works as + advertised, &release.branch; is very much a + work-in-progress. + + The basic requirements for using this &release.type; are + technical proficiency with &os; and an understanding of the + ongoing development process of &os; &release.branch; (as + discussed on the &a.current;). + + For those more interested in doing business with &os; than + in experimenting with new &os; technology, formal releases + (such as &release.prev.stable;) are frequently more appropriate. + Releases undergo a period of testing and quality assurance + checking to ensure high reliability and dependability. + + This &release.type; is aimed primarily at early adopters + and various other users who want to get involved with the + ongoing development of &os;. While the &os; development team + tries its best to ensure that each &release.type; works as + advertised, &release.branch; is very much a + work-in-progress. + + The basic requirements for using this &release.type; are + technical proficiency with &os; and an understanding of the + ongoing development process of &os; &release.branch; (as + discussed on the &a.current;). + + For those more interested in doing business with &os; than + in experimenting with new &os; technology, formal releases + (such as &release.prev.stable;) are frequently more appropriate. + Releases undergo a period of testing and quality assurance + checking to ensure high reliability and dependability. + + This &release.type; of &os; is suitable for all users. It + has undergone a period of testing and quality assurance + checking to ensure the highest reliability and + dependability. + + + + + Obtaining &os; + + &os; may be obtained in a variety of ways. This section + focuses on those ways that are primarily useful for obtaining a + complete &os; distribution, rather than updating an existing + installation. + + + CDROM and DVD + + &os; -RELEASE distributions may be ordered on CDROM or DVD + from several publishers. This is frequently the most + convenient way to obtain &os; for new installations, as it + provides a convenient way to quickly reinstall the system if + necessary. Some distributions include some of the optional, + precompiled packages from the &os; Ports + Collection, or other extra material. + + A list of the CDROM and DVD publishers known to the + project are listed in the Obtaining + &os; appendix to the Handbook. + + + + FTP + + You can use FTP to retrieve &os; and any or all of its + optional packages from ftp://ftp.FreeBSD.org/, which is the official + &os; release site, or any of its + mirrors. + + Lists of locations that mirror &os; can be found in the + FTP + Sites section of the Handbook. + Finding a close (in networking terms) mirror from which to + download the distribution is highly recommended. + + Additional mirror sites are always welcome. Contact + freebsd-admin@FreeBSD.org for more details on + becoming an official mirror site. You can also find useful + information for mirror sites at the Mirroring + &os; article. + + Mirrors generally contain the ISO images generally used to + create a CDROM of a &os; release. They usually also contain + floppy disk images (for applicable platforms), as well as the + files necessary to do an installation over the network. + Finally mirrors sites usually contain a set of packages for + the most current release. + + + + + Contacting the &os; Project + + + Email and Mailing Lists + + For any questions or general technical support issues, + please send mail to the &a.questions;. + + If you're tracking the &release.branch; development efforts, you + must join the &a.current;, in order to + keep abreast of recent developments and changes that may + affect the way you use and maintain the system. + + Being a largely-volunteer effort, the &os; + Project is always happy to have extra hands willing to help—there are already far more desired enhancements than + there is time to implement them. To contact the developers on + technical matters, or with offers of help, please send mail to + the &a.hackers;. + + Please note that these mailing lists can experience + significant amounts of traffic. If you + have slow or expensive mail access, or are only interested in + keeping up with major &os; events, you may find it + preferable to subscribe instead to the &a.announce;. + + All of the mailing lists can be freely joined by anyone + wishing to do so. Visit the + &os; Mailman Info Page. This will give you more + information on joining the various lists, accessing archives, + etc. There are a number of mailing lists targeted at special + interest groups not mentioned here; more information can be + obtained either from the Mailman pages or the mailing + lists section of the &os; Web site. + + + Do not send email to the lists + asking to be subscribed. Use the Mailman interface + instead. + + + + + Submitting Problem Reports + + Suggestions, bug reports and contributions of code are + always valued—please do not hesitate to report any + problems you may find. Bug reports with attached fixes are of + course even more welcome. + + The preferred method to submit bug reports from a machine + with Internet connectivity is to use the + Bugzilla bug tracker. + Problem Reports (PRs) submitted in this way + will be filed and their progress tracked; the &os; developers + will do their best to respond to all reported bugs as soon as + possible. A list of all + active PRs is available on the &os; Web site; this + list is useful to see what potential problems other users have + encountered. + + Note that &man.send-pr.1; is deprecated. + + For more information, Writing + &os; Problem Reports, available on the &os; + Web site, has a number of helpful hints on writing and + submitting effective problem reports. + + + + + Further Reading + + There are many sources of information about &os;; some are + included with this distribution, while others are available + on-line or in print versions. + + + Release Documentation + + A number of other files provide more specific information + about this &release.type; distribution. These files are + provided in various formats. Most distributions will include + both ASCII text (.TXT) and HTML + (.HTM) renditions. Some distributions + may also include other formats such as Portable Document Format + (.PDF). + + + + README.TXT: This file, which + gives some general information about &os; as well as + some cursory notes about obtaining a + distribution. + + + + RELNOTES.TXT: The release + notes, showing what's new and different in &os; + &release.current; compared to the previous release (&os; + &release.prev;). + + + + HARDWARE.TXT: The hardware + compatibility list, showing devices with which &os; has + been tested and is known to work. + + + + ERRATA.TXT: Release errata. + Late-breaking, post-release information can be found in + this file, which is principally applicable to releases + (as opposed to snapshots). It is important to consult + this file before installing a release of &os;, as it + contains the latest information on problems which have + been found and fixed since the release was + created. + + + + + On platforms that support &man.bsdinstall.8; (currently + &arch.amd64;, &arch.i386;, and &arch.sparc64;), these documents are generally available via the + Documentation menu during installation. Once the system is + installed, you can revisit this menu by re-running the + &man.bsdinstall.8; utility. + + + It is extremely important to read the errata for any + given release before installing it, to learn about any + late-breaking news or post-release problems. + The errata file accompanying each release (most likely right + next to this file) is already out of date by definition, but + other copies are kept updated on the Internet and should be + consulted as the current errata for this + release. These other copies of the errata are located at + &url.base;/releases/ (as + well as any sites which keep up-to-date mirrors of this + location). + + + + + Manual Pages + + As with almost all &unix; like operating systems, &os; comes + with a set of on-line manual pages, accessed through the + &man.man.1; command or through the hypertext manual + pages gateway on the &os; Web site. In general, the + manual pages provide information on the different commands and + APIs available to the &os; user. + + In some cases, manual pages are written to give + information on particular topics. Notable examples of such + manual pages are &man.tuning.7; (a guide to performance tuning), + &man.security.7; (an introduction to &os; security), and + &man.style.9; (a style guide to kernel coding). + + + + Books and Articles + + Two highly-useful collections of &os;-related information, + maintained by the &os; Project, + are the &os; Handbook and &os; FAQ (Frequently Asked + Questions document). On-line versions of the Handbook + and FAQ + are always available from the &os; Documentation + page or its mirrors. If you install the + doc distribution set, you can use a Web + browser to read the Handbook and FAQ locally. In particular, + note that the Handbook contains a step-by-step guide to + installing &os;. + + A number of on-line books and articles, also maintained by + the &os; Project, cover more-specialized, &os;-related topics. + This material spans a wide range of topics, from effective use + of the mailing lists, to dual-booting &os; with other + operating systems, to guidelines for new committers. Like the + Handbook and FAQ, these documents are available from the &os; + Documentation Page or in the doc + distribution set. + + A listing of other books and documents about &os; can be + found in the bibliography + of the &os; Handbook. Because of &os;'s strong &unix; heritage, + many other articles and books written for &unix; systems are + applicable as well, some of which are also listed in the + bibliography. + + + + + Acknowledgments + + &os; represents the cumulative work of many hundreds, if not + thousands, of individuals from around the world who have worked + countless hours to bring about this &release.type;. For a + complete list of &os; developers and contributors, please see + Contributors + to &os; on the &os; Web site or any of its + mirrors. + + Special thanks also go to the many thousands of &os; users + and testers all over the world, without whom this &release.type; + simply would not have been possible. + +
diff --git a/en_US.ISO8859-1/htdocs/releases/12.0R/relnotes/relnotes.xml b/en_US.ISO8859-1/htdocs/releases/12.0R/relnotes/relnotes.xml new file mode 100644 index 0000000000..b91c4be794 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/12.0R/relnotes/relnotes.xml @@ -0,0 +1,402 @@ + + + %release; + + %sponsor; + + %vendor; + + +]> +
+ + + &os; &release.current; Release Notes + + + The &os; Project + + + $FreeBSD$ + + + + + 2016 + The &os; Documentation + Project + + + + &tm-attrib.freebsd; + &tm-attrib.ibm; + &tm-attrib.ieee; + &tm-attrib.intel; + &tm-attrib.sparc; + &tm-attrib.general; + + + + The release notes for &os; &release.current; contain + a summary of the changes made to the &os; base system on the + &release.branch; development line. This document lists + applicable security advisories that were issued since the last + release, as well as significant changes to the &os; kernel and + userland. Some brief remarks on upgrading are also + presented. + + + + + Introduction + + This document contains the release notes for &os; + &release.current;. It describes recently added, changed, or + deleted features of &os;. It also provides some notes on + upgrading from previous versions of &os;. + + The &release.type; distribution to + which these release notes apply represents the latest point + along the &release.branch; development branch since + &release.branch; was created. Information regarding pre-built, + binary &release.type; distributions along this branch can be + found at &release.url;. + + The &release.type; distribution to + which these release notes apply represents a point along the + &release.branch; development branch between &release.prev; and + the future &release.next;. Information regarding pre-built, + binary &release.type; distributions along this branch can be + found at &release.url;. + + This distribution of &os; + &release.current; is a &release.type; distribution. It can be + found at &release.url; or + any of its mirrors. More information on obtaining this (or + other) &release.type; distributions of &os; can be found in the + Obtaining + &os; appendix to the &os; + Handbook. + + All users are encouraged to consult the release errata + before installing &os;. The errata document is updated with + late-breaking information discovered late in the + release cycle or after the release. Typically, it contains + information on known bugs, security advisories, and corrections + to documentation. An up-to-date copy of the errata for &os; + &release.current; can be found on the &os; Web site. + + This document describes the most user-visible new or changed + features in &os; since &release.prev;. In general, changes + described here are unique to the &release.branch; branch unless + specifically marked as &merged; features. + + Typical release note items document recent security + advisories issued after &release.prev;, new drivers or hardware + support, new commands or options, major bug fixes, or + contributed software upgrades. They may also list changes to + major ports/packages or release engineering practices. Clearly + the release notes cannot list every single change made to &os; + between releases; this document focuses primarily on security + advisories, user-visible changes, and major architectural + improvements. + + + + Upgrading from Previous Releases of &os; + + Binary upgrades between RELEASE versions + (and snapshots of the various security branches) are supported + using the &man.freebsd-update.8; utility. The binary upgrade + procedure will update unmodified userland utilities, as well as + unmodified GENERIC kernels distributed as a part of an official + &os; release. The &man.freebsd-update.8; utility requires that + the host being upgraded have Internet connectivity. + + Source-based upgrades (those based on recompiling the &os; + base system from source code) from previous versions are + supported, according to the instructions in + /usr/src/UPDATING. + + + Upgrading &os; should only be attempted after backing up + all data and configuration files. + + + + + Security and Errata + + This section lists the various Security Advisories and + Errata Notices since &release.prev;. + + + Security Advisories + + &security; + + + + Errata Notices + + &errata; + + + + + Userland + + This section covers changes and additions to userland + applications, contributed software, and system utilities. + + + Userland Configuration Changes + +   + + + + Userland Application Changes + +   + + + + Contributed Software + +   + + + + Installation and Configuration Tools + +   + + + + <filename class="directory">/etc/rc.d</filename> + Scripts + +   + + + + <filename class="directory">/etc/periodic</filename> + Scripts + +   + + + + Runtime Libraries and API + +   + + + + ABI Compatibility + +   + + + + + Kernel + + This section covers changes to kernel configurations, system + tuning, and system control parameters that are not otherwise + categorized. + + + Kernel Bug Fixes + +   + + + + Kernel Configuration + +   + + + + System Tuning and Controls + +   + + + + + Devices and Drivers + + This section covers changes and additions to devices and + device drivers since &release.prev;. + + + Device Drivers + +   + + + + Storage Drivers + +   + + + + Network Drivers + +   + + + + + Hardware Support + + This section covers general hardware support for physical + machines, hypervisors, and virtualization environments, as well + as hardware changes and updates that do not otherwise fit in + other sections of this document. + + + Hardware Support + +   + + + + Virtualization Support + +   + + + + ARM Support + +   + + + + + Storage + + This section covers changes and additions to file systems + and other storage subsystems, both local and networked. + + + General Storage + +   + + + + Networked Storage + +   + + + + ZFS + +   + + + + &man.geom.4; + +   + + + + + Boot Loader Changes + + This section covers the boot loader, boot menu, and other + boot-related changes. + + + Boot Loader Changes + +   + + + + Boot Menu Changes + +   + + + + + Networking + + This section describes changes that affect networking in + &os;. + + + Network Protocols + +   + + + + + Ports Collection and Package Infrastructure + + This section covers changes to the &os; Ports + Collection, package infrastructure, and package maintenance and + installation tools. + + + Infrastructure Changes + +   + + + + Packaging Changes + +   + + + + + Documentation + + This section covers changes to the &os; Documentation + Project sources and toolchain. + + + Documentation Source Changes + +   + + + + Documentation Toolchain Changes + +   + + + + + Release Engineering and Integration + + This section convers changes that are specific to the + &os; Release Engineering processes. + + + Integration Changes + +   + + +
diff --git a/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/catalog.xml b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/catalog.xml new file mode 100644 index 0000000000..74f8ccd068 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/catalog.xml @@ -0,0 +1,13 @@ + + + + + + + + + + + diff --git a/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/errata.xml b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/errata.xml new file mode 100644 index 0000000000..efc21a1cb7 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/errata.xml @@ -0,0 +1,28 @@ + + + + + + + + + + Errata + Date + Topic + + + + + + No errata notices. +   +   + + + + diff --git a/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/release.ent b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/release.ent new file mode 100644 index 0000000000..cacc43401f --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/release.ent @@ -0,0 +1,81 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +]]> + +]]> + +]]> + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/release.xsl b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/release.xsl new file mode 100644 index 0000000000..f76ae683d8 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/release.xsl @@ -0,0 +1,106 @@ + + + + + + + + + + + + + + + + + +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + (Sponsored by + + + + + + + + + + + + + + + + + + (Contributed / provided by + + + + + + + + + + + + + + + + + + +

+ + + + + + + + + + + + + + diff --git a/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/security.xml b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/security.xml new file mode 100644 index 0000000000..74a8cd7211 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/security.xml @@ -0,0 +1,28 @@ + + + + + + + + + + Advisory + Date + Topic + + + + + + No advisories. +   +   + + + + diff --git a/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/sponsor.ent b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/sponsor.ent new file mode 100644 index 0000000000..c762d19008 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/sponsor.ent @@ -0,0 +1,56 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/vendor.ent b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/vendor.ent new file mode 100644 index 0000000000..75c879b71c --- /dev/null +++ b/en_US.ISO8859-1/htdocs/releases/12.0R/share/xml/vendor.ent @@ -0,0 +1,9 @@ + diff --git a/en_US.ISO8859-1/htdocs/share/examples/Makefile.relnotesng b/en_US.ISO8859-1/htdocs/share/examples/Makefile.relnotesng new file mode 100644 index 0000000000..5bbc1a1109 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/share/examples/Makefile.relnotesng @@ -0,0 +1,61 @@ +# -*- makefile -*- +# +# $FreeBSD$ +# +# Sample makefile for rendering and uploading RELNOTESng files outside +# the build tree. +# + +ARCHS= amd64 i386 powerpc sparc64 +MULTITEXTS= +UNITEXTS= hardware readme relnotes errata + +IMAGEDIR= .imagedir +RHOST= freefall.freebsd.org +RDIR= public_html/relnotes/CURRENT +DOCDIR= ./release/doc +LANG= en_US.ISO8859-1 + +DOC_PREFIX?= /usr/doc +CSS_SHEET?= ${DOC_PREFIX}/share/misc/docbook.css +FORMATS?= html txt pdf + +BUILD_OPTIONS+= URLS_ABSOLUTE=YES + +all: + (cd ${DOCDIR}; ${MAKE} DOC_PREFIX=${DOC_PREFIX} FORMATS="${FORMATS}" ${BUILD_OPTIONS} all) + +lint: + (cd ${DOCDIR}; ${MAKE} DOC_PREFIX=${DOC_PREFIX} lint) + +image: all + @echo "#" + @echo "# Creating local image" + @echo "#" + rm -rf ${IMAGEDIR} + mkdir ${IMAGEDIR} + cp -p ${CSS_SHEET} ${IMAGEDIR}/docbook.css + for i in ${ARCHS}; do \ + for j in ${MULTITEXTS}; do \ + for k in ${FORMATS}; do \ + cp -p ${DOCDIR}/${LANG}/$${j}/$${i}/article.$${k} ${IMAGEDIR}/$${j}-$${i}.$${k} ; \ + done; \ + done; \ + done + for j in ${UNITEXTS}; do \ + for k in ${FORMATS}; do \ + cp -p ${DOCDIR}/${LANG}/$${j}/article.$${k} ${IMAGEDIR}/$${j}.$${k} ; \ + done; \ + done + +push: image + @echo "#" + @echo "# Pushing to ${RHOST}" + @echo "#" +# (cd ${IMAGEDIR}; tar -cf - .) | gzip -c -9 | (ssh ${RHOST} "( cd ${RDIR}; gunzip -c | tar -xf -)" ) + (cd ${IMAGEDIR}; rsync -azuv * ${RHOST}:${RDIR}) + rm -rf ${IMAGEDIR} + +clean: + (cd ${DOCDIR}; ${MAKE} DOC_PREFIX=${DOC_PREFIX} FORMATS="${FORMATS}" clean) + rm -rf ${IMAGEDIR} diff --git a/en_US.ISO8859-1/htdocs/share/misc/dev.archlist.txt b/en_US.ISO8859-1/htdocs/share/misc/dev.archlist.txt new file mode 100644 index 0000000000..7ad81543e9 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/share/misc/dev.archlist.txt @@ -0,0 +1,176 @@ +# +# Copyright (c) 2004-2006 The FreeBSD Project +# All rights reserved. +# +# Redistribution and use in source and binary forms, with or without +# modification, are permitted provided that the following conditions +# are met: +# 1. Redistributions of source code must retain the above copyright +# notice, this list of conditions and the following disclaimer. +# 2. Redistributions in binary form must reproduce the above copyright +# notice, this list of conditions and the following disclaimer in the +# documentation and/or other materials provided with the distribution. +# +# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +# SUCH DAMAGE. +# +# $FreeBSD$ +# + +# +# This file is used by man2hwnotes.pl to set which drivers are usable +# on which architectures. +# +# Format: +# +# Empty lines, and lines beginning with "#" are ignored. +# [,...] +# +aac i386,amd64 +adv i386,amd64 +adw i386,amd64 +aha i386 +ahb i386 +ahd i386,sparc64,amd64 +aic i386,amd64 +amd i386,amd64 +arcmsr i386,amd64 +asr i386 +ath i386,amd64,sparc64 +aue i386,amd64,powerpc +axe i386,amd64,powerpc +bce i386,amd64 +bge i386,sparc64,amd64 +bktr i386 +bt i386,amd64 +bxe i386,amd64 +cdce i386,amd64,powerpc +ciss i386,amd64 +ce i386 +cm i386 +cnw i386,amd64 +cp i386 +ctau i386 +cue i386,amd64,powerpc +cx i386 +cxgb i386,amd64 +de i386,amd64 +dpt i386,amd64 +ed i386 +ep i386,amd64 +esp sparc64 +ex i386,amd64 +fe i386,amd64 +fwohci i386,sparc64,amd64,powerpc +hifn i386,amd64 +hpt27xx i386,amd64 +hptiop i386,amd64 +hptmv i386,amd64 +hptrr i386,amd64 +ida i386 +ie i386 +iir i386,amd64 +ips i386,amd64 +isci i386,amd64 +ixgb i386,amd64 +kue i386,amd64,powerpc +lge i386,amd64 +mfi i386,amd64 +mlx i386,amd64 +mly i386,amd64 +msk i386,amd64 +mxge i386,amd64 +my i386 +ncr i386,amd64 +ncv i386 +nfe i386,amd64 +ng_bt3c i386,amd64 +ng_ubt i386,amd64 +nsp i386 +nxge i386,amd64 +oce i386,amd64 +ohci i386,amd64,powerpc +oltr i386 +otus i386,amd64 +pcn i386,amd64 +pst i386 +qlxgb amd64 +qlxgbe amd64 +qlxge amd64 +rc i386 +ral i386,amd64 +rsu i386,amd64 +rue i386,amd64 +rum i386,amd64 +run i386,amd64 +safe i386,amd64 +sbp i386,sparc64,amd64 +sfgxe amd64 +sn i386,amd64 +snd_ad1816 i386,amd64 +snd_als4000 i386 +snd_atiixp i386,amd64 +snd_audiocs sparc64 +snd_cmi i386,amd64 +snd_cs4281 i386,amd64 +snd_csa i386,amd64 +snd_ds1 i386,amd64 +snd_emu10k1 i386,amd64 +snd_emu10kx i386,amd64 +snd_envy24 i386,amd64 +snd_envy24ht i386,amd64 +snd_es137x i386,sparc64,amd64 +snd_ess i386,amd64 +snd_fm801 i386,amd64 +snd_gusc i386,amd64 +snd_hda i386,amd64 +snd_hdspe i386,amd64 +snd_ich i386,amd64 +snd_maestro i386,amd64 +snd_maestro3 i386,amd64 +snd_mss i386 +snd_neomagic i386,amd64 +snd_sbc i386,amd64 +snd_solo i386,amd64 +snd_spicds i386,amd64 +snd_t4dwave i386,amd64,sparc64 +snd_via8233 i386,amd64 +snd_via82c686 i386,amd64 +snd_vibes i386,amd64 +stg i386 +ti i386,amd64,sparc64 +tl i386,amd64 +trm i386,amd64 +twa i386,amd64 +twe i386,amd64 +tws i386,amd64 +ubsa i386,amd64 +ubsec i386,amd64 +ubser i386,amd64 +ucycom i386,amd64 +udav i386,amd64 +uftdi i386,amd64 +uhci i386,amd64,powerpc +ulpt i386,amd64,powerpc +umass i386,amd64,powerpc +umodem i386,amd64 +uplcom i386,amd64 +ural i386,amd64 +urio i386,amd64,powerpc +uvisor i386,amd64 +uvscom i386,amd64 +vpo i386 +vx i386,amd64 +vxge i386,amd64 +wb i386,amd64 +xe i386,amd64 +zyd i386,amd64 diff --git a/en_US.ISO8859-1/htdocs/share/misc/man2hwnotes.pl b/en_US.ISO8859-1/htdocs/share/misc/man2hwnotes.pl new file mode 100644 index 0000000000..778f63b794 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/share/misc/man2hwnotes.pl @@ -0,0 +1,534 @@ +#!/usr/local/bin/perl -w +# Emacs should use -*- cperl -*- mode +# +# Copyright (c) 2003-2006 Simon L. Nielsen +# All rights reserved. +# +# Redistribution and use in source and binary forms, with or without +# modification, are permitted provided that the following conditions +# are met: +# 1. Redistributions of source code must retain the above copyright +# notice, this list of conditions and the following disclaimer. +# 2. Redistributions in binary form must reproduce the above copyright +# notice, this list of conditions and the following disclaimer in the +# documentation and/or other materials provided with the distribution. +# +# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +# SUCH DAMAGE. +# +# $FreeBSD$ +# + +# Parse the list of supported hardware out of section 4 manual pages +# and output it on stdout as SGML/DocBook entities. + +# The script will look for the following line in the manual page: +# .Sh HARDWARE +# and make an entity of the content until the line containing: +# .Sh +# +# For Lists only the first line will be printed. If there are +# arguments to the .It command, only the argument will be printed. + +# Usage: +# man2hwnotes.pl [-cl] [-d 0-6] [-a ] [-o ] +# [ ...] + +use strict; +#use warnings; +use Getopt::Std; +use Digest::MD5 qw(md5_hex); + +# Section from manual page to extract +my $hwlist_sect = "HARDWARE"; + +# Override default archtecture list for some devices: +my $archlist_file = "dev.archlist.txt"; +my %archlist; + +# Globals +my $compat_mode = 0; # Enable compat for old Hardware Notes style +my $debuglevel = 0; +my $only_list_out = 0; # Should only lists be generated in the output? +my @out_lines; # Single lines +my @out_dev; # Device entities + +# Getopt +my %options = (); +if (!getopts("a:cd:lo:",\%options)) { + die("$!: Invalid command line arguments in ", __LINE__, "\n"); +} + +if (defined($options{c})) { + $compat_mode = 1; +} +if (defined($options{d})) { + $debuglevel = $options{d}; +} +if (defined($options{a})) { + $archlist_file = $options{a}; +} +if (defined($options{l})) { + $only_list_out = 1; +} + +my $outputfile = $options{o}; + +if ($debuglevel > 0) { + # Don't do output buffering in debug mode. + $| = 1; +} + +load_archlist($archlist_file); + +if (defined($outputfile)) { + open(OLDOUT, ">&STDOUT") || die("$!: Could not open STDOUT in ", __LINE__, ".\n"); + open(STDOUT, ">$outputfile") || die("$!: Could not open $outputfile in ", __LINE__, ".\n"); +} + +print < +EOT + +if ($only_list_out) { + # Print the default device preamble entities + print "\n"; + print "\n"; +} + +foreach my $page (@ARGV) { + if ($page !~ m/\.4$/) { + dlog(2, "Skipped $page (not *.4)"); + next; + } + dlog(2, "Parsing $page"); + parse($page); + + if (@out_lines) { + print join("\n", @out_lines), "\n"; + } + if (@out_dev) { + print join("\n", @out_dev), "\n"; + } + + @out_lines = (); + @out_dev = (); +} + +if (defined($outputfile)) { + open(STDOUT, ">&OLDOUT") || die("$!: Could not open STDOUT in ", __LINE__, ".\n"); + close(OLDOUT) || die("$!: Could not close OLDOUT in ", __LINE__, ".\n"); +} + +sub normalize (@) { + my @lines = @_; + + foreach my $l (@lines) { + $l =~ s/\\&//g; + $l =~ s:([\x21-\x2f\x5b-\x60\x7b-\x7f]):sprintf("&\#\%d;", ord($1)):eg; + # Make sure ampersand is encoded as & since jade seems to + # be confused when it is encoded as & inside an entity. + $l =~ s/&/&/g; + } + return (wantarray) ? @lines : join "", @lines; +} + +sub parse { + my ($manpage) = @_; + + my $cur_mansection; + my $found_hwlist = 0; + my %mdocvars; + $mdocvars{isin_hwlist} = 0; + $mdocvars{isin_list} = 0; + $mdocvars{first_para} = 1; + $mdocvars{parabuf} = ""; + $mdocvars{listtype} = ""; + $mdocvars{it_nr} = 0; + + open(MANPAGE, "$manpage") || die("$!: Could not open $manpage in ", __LINE__, ".\n"); + while() { + chomp; + my $line = $_; + + dlog(5, "Read '$line'"); + + # Find commands + if (s/^\.(.*)$/$1/) { + my $cmd = $1; + + # Detect, and ignore, comment lines + if (s/^\\"(.*)$/$1/) { + next; + } + + $cmd =~ s/^([^ ]+).*$/$1/; + + if (/^Nm "?(\w+)"?/ && !defined($mdocvars{Nm})) { + dlog(3, "Setting Nm to $1"); + $mdocvars{Nm} = $1; + # "_" cannot be used for an entity name. + $mdocvars{EntNm} = $1; + $mdocvars{EntNm} =~ s,_,.,g; + + } elsif (/^Nm$/) { + if (defined($mdocvars{Nm}) && $mdocvars{Nm} ne "") { + parabuf_addline(\%mdocvars, "&man.".$mdocvars{EntNm}.".$cur_mansection;"); + } else { + dlog(2, "Warning: Bad Nm call in $manpage"); + } + + } elsif (/^Sh (.+)$/) { + dlog(4, "Setting section to $1"); + my $cur_section = $1; + + flush_out(\%mdocvars); + + if ($cur_section =~ /^${hwlist_sect}$/) { + dlog(2, "Found the device section ${hwlist_sect}"); + $mdocvars{isin_hwlist} = 1; + $found_hwlist = 1; + add_sgmltag(\%mdocvars, "&hwlist.preamble.pre; " . + "&man.".$mdocvars{EntNm}.".$cur_mansection; " . + "&hwlist.preamble.post;"); + } + } elsif ($mdocvars{isin_hwlist}) { + dlog(2, "Found a HWLIST STOP key!"); + add_sgmltag(\%mdocvars, "'>"); + $mdocvars{isin_hwlist} = 0; + } + if ($mdocvars{isin_list}) { + dlog(1, "Warning: Still in list, but just entered new " . + "section. This is probably due to missing .El; " . + "check manual page for errors."); + # If we try to recover from this we will probably + # just end with bad SGML output and it really + # should be fixed in the manual page so we don't + # even try to "fix" this. + } + + + } elsif (/^Dt ([^ ]+) ([^ ]+)/) { + dlog(4, "Setting mansection to $2"); + $mdocvars{cur_manname} = lc($1); + $cur_mansection = $2; + + # "_" cannot be used for an entity name. + $mdocvars{cur_manname} =~ s,_,.,g; + + } elsif (/^It ?(.*)$/) { + my $txt = $1; + + $mdocvars{it_nr}++; + + # Flush last item + if ($mdocvars{parabuf} ne "") { + add_listitem(\%mdocvars); + } + + # Remove quotes, if any. + $txt =~ s/"(.*)"/$1/; + + if ($mdocvars{listtype} eq "column") { + # Ignore first item when it is likely to be a + # header. + if ($mdocvars{it_nr} == 1 && $txt =~ m/^(Em|Sy) /) { + dlog(2, "Skipping header line in column list"); + next; + } + # Only extract the first column. + $txt =~ s/ Ta /\t/g; + $txt =~ s/([^\t]+)\t.*/$1/; + } + + # Remove Li commands + $txt =~ s/^Li //g; + + parabuf_addline(\%mdocvars, normalize($txt)); + } elsif (/^Bl/) { + $mdocvars{isin_list} = 1; + flush_out(\%mdocvars); + add_sgmltag(\%mdocvars, ""); + + if (/-tag/) { + $mdocvars{listtype} = "tag"; + # YACK! Hack for ata(4) + if ($mdocvars{Nm} eq "ata") { + $mdocvars{listtype} = "tagHACK"; + } + } elsif (/-bullet/) { + $mdocvars{listtype} = "bullet"; + } elsif (/-column/) { + $mdocvars{listtype} = "column"; + } else { + $mdocvars{listtype} = "unknown"; + } + dlog(2, "Listtype set to $mdocvars{listtype}"); + } elsif (/^El/) { + if ($mdocvars{parabuf} ne "") { + add_listitem(\%mdocvars); + } + + add_sgmltag(\%mdocvars, ""); + $mdocvars{isin_list} = 0; + } elsif (/^Tn (.+)$/) { + # For now we print TradeName text as regular text. + my ($txt, $punct_str) = split_punct_chars($1); + + parabuf_addline(\%mdocvars, normalize($txt . $punct_str)); + } elsif (/^Xr ([^ ]+) (.+)$/) { + my ($xr_sect, $punct_str) = split_punct_chars($2); + my $txt; + + # We need to check if the manual page exist to avoid + # breaking the doc build just because of a broken + # reference. + #$txt = "&man.$1.$xr_sect;$punct_str"; + $txt = "$1($xr_sect)$punct_str"; + parabuf_addline(\%mdocvars, normalize($txt)); + } elsif (/^Dq (.+)$/) { + my ($txt, $punct_str) = split_punct_chars($1); + + parabuf_addline(\%mdocvars, + normalize("$txt$punct_str")); + } elsif (/^Sx (.+)$/) { + if ($mdocvars{isin_hwlist}) { + dlog(1, "Warning: Reference to another section in the " . + "$hwlist_sect section in " . $mdocvars{Nm} . + "(${cur_mansection})"); + } + parabuf_addline(\%mdocvars, normalize($1)); + } elsif (/^Pa (.+)$/) { + my ($txt, $punct_str) = split_punct_chars($1); + + $txt = make_ulink($txt) . $punct_str; + parabuf_addline(\%mdocvars, normalize($txt)); + } elsif (/^Pp/) { + dlog(3, "Got Pp command - forcing new para"); + flush_out(\%mdocvars); + } elsif (/^Fx (.+)/) { + dlog(3, "Got Fx command"); + parabuf_addline(\%mdocvars, "FreeBSD $1"); + } elsif (/^Fx/) { + dlog(3, "Got Fx command"); + parabuf_addline(\%mdocvars, "FreeBSD"); + } elsif (/^Em (.+)$/) { + my ($txt, $punct_str) = split_punct_chars($1); + + parabuf_addline(\%mdocvars, + normalize("$txt$punct_str")); + } else { + # Ignore all other commands. + dlog(3, "Ignoring unknown command $cmd"); + } + } else { + # This is then regular text + parabuf_addline(\%mdocvars, normalize($_)); + } + } + close(MANPAGE) || die("$!: Could not close $manpage in ", __LINE__, ".\n"); + if (! $found_hwlist) { + dlog(2, "Hardware list not found in $manpage"); + } +} + +sub dlog { + my ($level, $txt) = @_; + + if ($level <= $debuglevel) { + print STDERR "$level: $txt\n"; + } +} + +# Output a SGML tag. +sub add_sgmltag { + my ($mdocvars, $txt) = (@_); + + # We only care about the HW list for now. + if (${$mdocvars}{isin_hwlist}) { + push(@out_dev, $txt); + } +} + +# Add a text entity, and return the used entity name. +sub add_txt_ent { + my ($itemtxt) = (@_); + my ($entity_name); + + # Convert mdoc(7) minus + $itemtxt =~ s/\\-/-/g; + + $itemtxt =~ s/'/‘/g; + + $entity_name = "hwlist." . md5_hex($itemtxt); + dlog(4, "Adding '$itemtxt' as entity $entity_name"); + push(@out_lines, ""); + + return ($entity_name); +} +sub flush_out { + my ($mdocvars) = (@_); + my ($entity_name, $out); + my $para_arch = ""; + + if (!${$mdocvars}{isin_hwlist} || ${$mdocvars}{parabuf} eq "") { + return; + } + + $entity_name = add_txt_ent(${$mdocvars}{parabuf}); + ${$mdocvars}{parabuf} = ""; + if(defined($archlist{${$mdocvars}{Nm}})) { + if ($compat_mode) { + $para_arch = ' arch="' . $archlist{${$mdocvars}{Nm}} . '"'; + } else { + $para_arch = '[' . $archlist{${$mdocvars}{Nm}} . '] '; + } + } + if ($compat_mode) { + $out = "&".$entity_name.";"; + } else { + if (${$mdocvars}{first_para}) { + $out = "".$para_arch."&".$entity_name.";"; + } else { + $out = "&".$entity_name.";"; + } + ${$mdocvars}{first_para} = 0; + } + + dlog(4, "Flushing parabuf"); + add_sgmltag($mdocvars, $out); +} + +# Add a new list item from the "parabuf". +sub add_listitem { + my ($mdocvars) = (@_); + my ($listitem, $entity_name); + my $para_arch = ""; + + $entity_name = add_txt_ent(${$mdocvars}{parabuf}); + ${$mdocvars}{parabuf} = ""; + + if ($compat_mode) { + if(defined($archlist{${$mdocvars}{Nm}})) { + $para_arch = ' arch="' . $archlist{${$mdocvars}{Nm}} . '"'; + } + } + $listitem = "&".$entity_name.";"; + dlog(4, "Adding '$listitem' to out_dev"); + push(@out_dev, $listitem); + +} + +# Add a line to the "paragraph buffer" +sub parabuf_addline { + my $mdocvars = shift; + my ($txt) = (@_); + + dlog(5, "Now in parabuf_addline for '$txt'"); + + # We only care about the HW list for now. + if (!${$mdocvars}{isin_hwlist}) { + dlog(6, "Exiting parabuf_addline due to: !\${\$mdocvars}{isin_hwlist}"); + return; + } + if ($txt eq "") { + dlog(6, "Exiting parabuf_addline due to: \$txt eq \"\""); + return; + } + + if ($only_list_out && !${$mdocvars}{isin_list}) { + dlog(6, "Exiting parabuf_addline due to: ". + "\$only_list_out && !\${\$mdocvars}{isin_list}"); + return; + } + + # We only add the first line for "tag" lists + if (${$mdocvars}{parabuf} ne "" && ${$mdocvars}{isin_list} && + ${$mdocvars}{listtype} eq "tag") { + dlog(6, "Exiting parabuf_addline due to: ". + "\${\$mdocvars}{parabuf} ne \"\" && \${\$mdocvars}{isin_list} && ". + "\${\$mdocvars}{listtype} eq \"tag\""); + return; + } + + if (${$mdocvars}{parabuf} ne "") { + ${$mdocvars}{parabuf} .= " "; + } + + dlog(4, "Adding '$txt' to parabuf"); + + ${$mdocvars}{parabuf} .= $txt; +} + +sub load_archlist { + my ($file) = (@_); + + my $lineno = 0; + + dlog(2, "Parsing archlist $file"); + + open(FILE, "$file") || die("$!: Could not open archlist $file in ", __LINE__, ".\n"); + while() { + chomp; + $lineno++; + + if (/^#/ || $_ eq "") { + next; + } + + if (/(\w+)\t([\w,]+)/) { + dlog(4, "For driver $1 setting arch to $2"); + $archlist{$1} = $2; + } else { + dlog(1, "Warning: Could not parse archlist line $lineno"); + } + } + + close(FILE); +} + +# Check if a character is a mdoc(7) punctuation character. +sub is_punct_char { + my ($str) = (@_); + + return (length($str) == 1 && $str =~ /[\.,:;()\[\]\?!]/); +} + +# Split out the punctuation characters of a mdoc(7) line. +sub split_punct_chars { + my ($str) = (@_); + my (@stritems, $stritem, $punct_str); + + $punct_str = ""; + @stritems = split(/ /, $str); + + while (defined($stritem = $stritems[$#stritems]) && + is_punct_char($stritem)) { + $punct_str = $stritem . $punct_str; + pop(@stritems); + } + + return (join(' ', @stritems), $punct_str); +} + +# Create a ulink, if the string contains an URL. +sub make_ulink { + my ($str) = (@_); + + $str =~ s,(http://[^ ]+),,; + + return $str; +} diff --git a/en_US.ISO8859-1/htdocs/share/mk/doc.relnotes.mk b/en_US.ISO8859-1/htdocs/share/mk/doc.relnotes.mk new file mode 100644 index 0000000000..6f297bf23e --- /dev/null +++ b/en_US.ISO8859-1/htdocs/share/mk/doc.relnotes.mk @@ -0,0 +1,28 @@ +# $FreeBSD$ + +DOC_PREFIX?= ../../../../ + +# XXX +RELEASETYPE!= grep -o 'release.type "[a-z]*"' ${RELN_ROOT}/share/xml/release.ent | sed 's|[a-z.]* "\([a-z]*\)"|\1|' +RELEASEURL!= grep -o 'release.url \"[^\"]*\"' ${RELN_ROOT}/share/xml/release.ent | sed 's|[^ ]* "\([^"]*\)"|\1|' +RELEASEBRANCH!= grep -o 'release.branch "\([^"]*\)"' ${RELN_ROOT}/share/xml/release.ent | sed 's|[^ ]* "\([^"]*\)"|\1|' +RELEASEMAILLIST!= grep -o 'release.maillist "\([^"]*\)"' ${RELN_ROOT}/share/xml/release.ent | sed 's|[^ ]* "\([^"]*\)"|\1|' +.if ${RELEASETYPE} == "current" +PROFILING+= --param profile.attribute "'releasetype'" --param profile.value "'current'" +.elif ${RELEASETYPE} == "snapshot" +PROFILING+= --param profile.attribute "'releasetype'" --param profile.value "'snapshot'" +.elif ${RELEASETYPE} == "release" +PROFILING+= --param profile.attribute "'releasetype'" --param profile.value "'release'" +.endif +XSLTPROCFLAGS+= --param release.url "'${RELEASEURL}'" +XSLTPROCFLAGS+= --param release.branch "'${RELEASEBRANCH}'" +XSLTPROCFLAGS+= --param release.maillist "'${RELEASEMAILLIST}'" +XSLTPROCFLAGS+= --param toc.section.depth "'3'" + +# Find the RELNOTESng document catalogs +EXTRA_CATALOGS+= file://${RELN_ROOT}/${LANGCODE}/share/xml/catalog.xml \ + file://${RELN_ROOT}/share/xml/catalog.xml + +XSLXHTML= file://${RELN_ROOT}/share/xml/release.xsl + +.include "${DOC_PREFIX}/share/mk/doc.install.mk"