summaryrefslogtreecommitdiffstats
path: root/share
Commit message (Collapse)AuthorAgeFilesLines
* Remove nsswitch.conf from the list of examples, because there is nonectar2003-09-151-1/+0
| | | | | | such example. Reported by: blackend
* Better explain what INSTALL="install -C" does, and warn that this maysheldonh2003-09-151-2/+4
| | | | | | | | | be hardwired into makefiles, including those under /usr/share/mk. The reporter submitted a patch, but I've watered it down. Reported by: Ian Freislich <ianf@za.uu.net> MFC after: 3 weeks
* Remove invalid statement about the maximum number of swap drives.hmp2003-09-141-2/+1
| | | | | PR: docs/55276 Submitted by: Roderick van Domburg <r.s.a.vandomburg@student.utwente.nl>
* Update supported Ethernet Controllers as per the Hardware Notes.hmp2003-09-141-0/+4
| | | | | | PR: docs/55559 Submitted by: Lukas Ertl <l.ertl@univie.ac.at> MFC after: 3 days
* Get rid of duplicates.ru2003-09-149-9/+9
|
* Retire the WITH_LIBMAP compile knob; libmap is now a standard feature.mdodd2003-09-131-3/+0
|
* Document /var/empty as generic empty directory, not sshd specificeivind2003-09-131-2/+3
|
* asami is no longer our ports lead, so remove a statement sayingeivind2003-09-131-3/+0
| | | | the ports collection is maintained by asami and the ports team.
* mdoc(7): Fix common mistakes made in the SEE ALSO section.ru2003-09-125-6/+6
|
* Remove double usage of performance, and combine it to one.hmp2003-09-121-1/+1
|
* Using prefix=/usr will put these files in /usr/gnats, not /usr/ports.ceri2003-09-121-1/+1
|
* Add the ports/dns and ports/polish categories.ceri2003-09-124-0/+6
|
* Add missing .Elnaddy2003-09-111-0/+1
| | | | Approved by: ru
* compaq WL110 is a lucent cardimp2003-09-101-1/+1
| | | | Submitted by Jeremy Bingham
* mdoc(7): Properly mark C headers.ru2003-09-1023-33/+33
|
* mdoc(7): Moved #include directives into the SYNOPSIS section.ru2003-09-101-3/+3
|
* Typo.ru2003-09-101-1/+1
|
* The re.4 manpage has been checked in now, so hook it back up.ceri2003-09-091-0/+1
|
* Add a device driver for the Broadcom BCM4401 ethernet controller,wpaul2003-09-092-0/+100
| | | | | | | | | | | | | | written by Stuart Walsh and Duncan Barclay (with some kibbitzing by me). I'm checking it in on Stuart's behalf. The BCM4401 is built into several x86 laptop and desktop systems. For the moment, I have only enabled it in the x86 kernel config because although it's a PCI device, I haven't heard of any standalone NICs that use it. If somebody knows of one, we can easily add it to the other arches. This driver uses register/structure data gleaned from the Linux driver released by Broadcom, but does not contain any of the code from the Linux driver itself. It uses busdma.
* Add the re.4 man page, which I forgot to do last night.wpaul2003-09-091-0/+200
|
* mdoc(7): Use the new feature of the .In macro.ru2003-09-0854-107/+105
|
* Looks like the re.4 man page didn't make it in the last commit,dougb2003-09-081-1/+0
| | | | so unhook it to get the build back in action.
* Take the support for the 8139C+/8169/8169S/8110S chips out of thewpaul2003-09-082-15/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | rl(4) driver and put it in a new re(4) driver. The re(4) driver shares the if_rlreg.h file with rl(4) but is a separate module. (Ultimately I may change this. For now, it's convenient.) rl(4) has been modified so that it will never attach to an 8139C+ chip, leaving it to re(4) instead. Only re(4) has the PCI IDs to match the 8169/8169S/8110S gigE chips. if_re.c contains the same basic code that was originally bolted onto if_rl.c, with the following updates: - Added support for jumbo frames. Currently, there seems to be a limit of approximately 6200 bytes for jumbo frames on transmit. (This was determined via experimentation.) The 8169S/8110S chips apparently are limited to 7.5K frames on transmit. This may require some more work, though the framework to handle jumbo frames on RX is in place: the re_rxeof() routine will gather up frames than span multiple 2K clusters into a single mbuf list. - Fixed bug in re_txeof(): if we reap some of the TX buffers, but there are still some pending, re-arm the timer before exiting re_txeof() so that another timeout interrupt will be generated, just in case re_start() doesn't do it for us. - Handle the 'link state changed' interrupt - Fix a detach bug. If re(4) is loaded as a module, and you do tcpdump -i re0, then you do 'kldunload if_re,' the system will panic after a few seconds. This happens because ether_ifdetach() ends up calling the BPF detach code, which notices the interface is in promiscuous mode and tries to switch promisc mode off while detaching the BPF listner. This ultimately results in a call to re_ioctl() (due to SIOCSIFFLAGS), which in turn calls re_init() to handle the IFF_PROMISC flag change. Unfortunately, calling re_init() here turns the chip back on and restarts the 1-second timeout loop that drives re_tick(). By the time the timeout fires, if_re.ko has been unloaded, which results in a call to invalid code and blows up the system. To fix this, I cleared the IFF_UP flag before calling ether_ifdetach(), which stops the ioctl routine from trying to reset the chip. - Modified comments in re_rxeof() relating to the difference in RX descriptor status bit layout between the 8139C+ and the gigE chips. The layout is different because the frame length field was expanded from 12 bits to 13, and they got rid of one of the status bits to make room. - Add diagnostic code (re_diag()) to test for the case where a user has installed a broken 32-bit 8169 PCI NIC in a 64-bit slot. Some NICs have the REQ64# and ACK64# lines connected even though the board is 32-bit only (in this case, they should be pulled high). This fools the chip into doing 64-bit DMA transfers even though there is no 64-bit data path. To detect this, re_diag() puts the chip into digital loopback mode and sets the receiver to promiscuous mode, then initiates a single 64-byte packet transmission. The frame is echoed back to the host, and if the frame contents are intact, we know DMA is working correctly, otherwise we complain loudly on the console and abort the device attach. (At the moment, I don't know of any way to work around the problem other than physically modifying the board, so until/unless I can think of a software workaround, this will have do to.) - Created re(4) man page - Modified rlphy.c to allow re(4) to attach as well as rl(4). Note that this code works for the sample 8169/Marvell 88E1000 NIC that I have, but probably won't work for the 8169S/8110S chips. RealTek has sent me some sample NICs, but they haven't arrived yet. I will probably need to add an rlgphy driver to handle the on-board PHY in the 8169S/8110S (it needs special DSP initialization).
* Change an `is' to a `was' in the AUTHORS section.hmp2003-09-071-1/+1
| | | | Recommended by: jmallett
* - No need to create libfoo.so -> libfoo.so.X symlinks in /lib,ru2003-09-071-3/+8
| | | | | | | | | | | | as it was decided that our toolchain will revert to looking for libraries in /usr/lib only. - Make /usr/lib/libfoo.so -> /lib/libfoo.so.X symlinks absolute so that they still work if /usr is symlinked. - Remove stale /usr/lib/libfoo.so.X libraries during install. Discussed with: gordon, obrien, peter
* Implement sed(1) commands using the make(1)'s RE variable modifier.ru2003-09-071-3/+3
| | | | (This almost eliminates the need of a sed(1) during installworld.)
* make sure we really don't have a tty when installing rules. This preventsjmg2003-09-071-3/+3
| | | | | | | a flush command from asking a question (you can't see): If there is no tty associated with the process, this is implied. MFC after: 1 day
* Document msize which is often needed with maddr.jb2003-09-071-0/+2
|
* Hook-up the uart(4) manpage.marcel2003-09-071-0/+1
| | | | Reminded by: bmah@
* Mdoc Review:hmp2003-09-061-3/+5
| | | | | | | | * Remove extraneous .Pp in SYNOPSIS * Remove hard sentence break * Add the AUTHORS section
* The uart(4) driver is an universal driver for various UART hardware.marcel2003-09-061-0/+115
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It improves on sio(4) in the following areas: o Fully newbusified to allow for memory mapped I/O. This is a must for ia64 and sparc64, o Machine dependent code to take full advantage of machine and firm- ware specific ways to define serial consoles and/or debug ports. o Hardware abstraction layer to allow the driver to be used with various UARTs, such as the well-known ns8250 family of UARTs, the Siemens sab82532 or the Zilog Z8530. This is especially important for pc98 and sparc64 where it's common to have different UARTs, o The notion of system devices to unkludge low-level consoles and remote gdb ports and provides the mechanics necessary to support the keyboard on sparc64 (which is UART based). o The notion of a kernel interface so that a UART can be tied to something other than the well-known TTY interface. This is needed on sparc64 to present the user with a device and ioctl handling suitable for a keyboard, but also allows us to cleanly hide an UART when used as a debug port. Following is a list of features and bugs/flaws specific to the ns8250 family of UARTs as compared to their support in sio(4): o The uart(4) driver determines the FIFO size and automaticly takes advantages of larger FIFOs and/or additional features. Note that since I don't have sufficient access to 16[679]5x UARTs, hardware flow control has not been enabled. This is almost trivial to do, provided one can test. The downside of this is that broken UARTs are more likely to not work correctly with uart(4). The need for tunables or knobs may be large enough to warrant their creation. o The uart(4) driver does not share the same bumpy history as sio(4) and will therefore not provide the necessary hooks, tweaks, quirks or work-arounds to deal with once common hardware. To that extend, uart(4) supports a subset of the UARTs that sio(4) supports. The question before us is whether the subset is sufficient for current hardware. o There is no support for multiport UARTs in uart(4). The decision behind this is that uart(4) deals with one EIA RS232-C interface. Packaging of multiple interfaces in a single chip or on a single expansion board is beyond the scope of uart(4) and is now mostly left for puc(4) to deal with. Lack of hardware made it impossible to actually implement such a dependency other than is present for the dual channel SAB82532 and Z8350 SCCs. The current list of missing features is: o No configuration capabilities. A set of tunables and sysctls is being worked out. There are likely not going to be any or much compile-time knobs. Such configuration does not fit well with current hardware. o No support for the PPS API. This is partly dependent on the ability to configure uart(4) and partly dependent on having sufficient information to implement it properly. As usual, the manpage is present but lacks the attention the software has gotten.
* Catch up isp.4 manpage with hardware notes.bmah2003-09-061-0/+4
| | | | | PR: 55558 Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
* Remove hard sentence breaks.hmp2003-09-061-9/+10
|
* Add stg(4) manpage and hook up to the section 4 manpage build.bmah2003-09-062-0/+71
| | | | | PR: 55605 Submitted by: Bob Bishop <rb@gid.co.uk>
* Change /dev/rsa0 and /dev/rwt0 references to sa0 and wt0.roam2003-09-051-5/+5
| | | | | | PR: 55925 Submitted by: Michael L. Squires <mikes@siralan.org> MFC after: 1 month
* Catch up with the hardware notes: list the supported cards.roam2003-09-051-4/+32
| | | | | | PR: 55645 Submitted by: Lukas Ertl <l.ertl@univie.ac.at> MFC after: 1 month
* Catch up with the hardware notes: list the supported cards.roam2003-09-051-4/+39
| | | | | | PR: 55643 Submitted by: Lukas Ertl <l.ertl@univie.ac.at> MFC after: 1 month
* Catch up with the hardware notes: list the supported Compaq controllers.roam2003-09-051-1/+3
| | | | | PR: 55641 Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
* Document the SC_NO_SUSPEND_VTYSWITCH kernel config option.roam2003-09-051-0/+7
| | | | | PR: 55562 Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
* o Fix a typo in rev. 1.196: ifconfig 9 -> ifconfig 8.maxim2003-09-051-1/+1
| | | | | PR: docs/56488 Submitted by: Yoshihiko Sarumaru <mistral@imasy.or.jp>
* Correct troff usage; typo fixes.jkoshy2003-09-051-9/+9
|
* Allow the PS version of this paper to be built.jkoshy2003-09-051-1/+8
|
* Make the creation of the OpenSSL whatis(1) database conditional onru2003-09-041-0/+2
| | | | NOCRYPT and NO_OPENSSL.
* Emergency backout of rev 1.152. This is a 100% guaranteed way to totallypeter2003-09-041-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | hose your system. You end up with just about everything statically linked (except for libpam.so), which then causes all the pam users to fail. eg: login, sshd, su etc all stop working because dlopen no longer works because there is no libc.so in memory anymore. gcc passes -L/usr/lib to ld. The /usr/lib/libxxx.so symlink is *not* a compatability link. It is actually the primary link. There should be no symlinks in /lib at all. Only /lib/libXX.so.Y. peter@daintree[9:27pm]/usr/bin-104> file yppasswd yppasswd: setuid ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 5.1.1, dynamically linked (uses shared libs), stripped peter@daintree[9:27pm]/usr/bin-105> ldd yppasswd yppasswd: libpam.so.2 => /usr/lib/libpam.so.2 (0x280d1000) peter@daintree[9:28pm]/usr/bin-106> Note no libc.so.5. Hence libpam.so.2 has unresolved dependencies. I believe this is also the cause of the recent buildworld failures when pam_krb5.so references -lcrypto stuff etc and when librpcsvc.so references des_setparity() etc. This change could not possibly have worked, unless there are other missing changes to the gcc configuration. It won't work with ports versions of gcc either.
* As ld(1) was taught to look into /lib, there's no longer a reasonru2003-09-031-4/+0
| | | | | | | for having compatibility .so symlinks. Submitted by: obrien Reviewed by: gordon
* Fix typo in the last commit.ken2003-09-031-1/+1
| | | | | Pointed out by: njl MFC after: 3 days
* Move dynamic sysctl(8) variable creation for the cd(4) and da(4) driversken2003-09-034-56/+132
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | out of cdregister() and daregister(), which are run from interrupt context. The sysctl code does blocking mallocs (M_WAITOK), which causes problems if malloc(9) actually needs to sleep. The eventual fix for this issue will involve moving the CAM probe process inside a kernel thread. For now, though, I have fixed the issue by moving dynamic sysctl variable creation for these two drivers to a task queue running in a kernel thread. The existing task queues (taskqueue_swi and taskqueue_swi_giant) run in software interrupt handlers, which wouldn't fix the problem at hand. So I have created a new task queue, taskqueue_thread, that runs inside a kernel thread. (It also runs outside of Giant -- clients must explicitly acquire and release Giant in their taskqueue functions.) scsi_cd.c: Remove sysctl variable creation code from cdregister(), and move it to a new function, cdsysctlinit(). Queue cdsysctlinit() to the taskqueue_thread taskqueue once we have fully registered the cd(4) driver instance. scsi_da.c: Remove sysctl variable creation code from daregister(), and move it to move it to a new function, dasysctlinit(). Queue dasysctlinit() to the taskqueue_thread taskqueue once we have fully registered the da(4) instance. taskqueue.h: Declare the new taskqueue_thread taskqueue, update some comments. subr_taskqueue.c: Create the new kernel thread taskqueue. This taskqueue runs outside of Giant, so any functions queued to it would need to explicitly acquire/release Giant if they need it. cd.4: Update the cd(4) man page to talk about the minimum command size sysctl/loader tunable. Also note that the changer variables are available as loader tunables as well. da.4: Update the da(4) man page to cover the retry_count, default_timeout and minimum_cmd_size sysctl variables/loader tunables. Remove references to /dev/r???, they aren't used any longer. cd.9: Update the cd(9) man page to describe the CD_Q_10_BYTE_ONLY quirk. taskqueue.9: Update the taskqueue(9) man page to describe the new thread task queue, and the taskqueue_swi_giant queue. MFC after: 3 days
* CardBus instead of Cardbus. Add I/O Data WN-AG/CB and Prixim Skylineimp2003-09-012-12/+19
| | | | | | | 4030 cards. Special Thanks: shigeru yamamoto-san for the kind donation of I/O Data and other wireless cards
* Catch up my(4) with hardware notes by adding Myson MTD89X to list ofsimon2003-08-311-0/+2
| | | | | | | | supported devices. Submitted by: Lukas Ertl <l.ertl@univie.ac.at> PR: docs/56244 Confirmed by: driver source code
* Whitespace diff reduction between bsd.prog.mk and bsd.lib.mk outputs.ru2003-08-312-2/+19
|
OpenPOWER on IntegriCloud