summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Remove MAINTAINER lines.obrien2003-06-146-14/+0
|
* Update and try to remain out of area where conflict exists.obrien2003-06-141-7/+0
|
* Tidy up. Sort headers.markm2003-06-1413-56/+53
|
* Minor tweaks to the build process so that we can build 5.1-current onimp2003-06-141-1/+6
| | | | | | | | | | | 4.8-stable: Must build lib/libc before libpthread. Fix how we do this to be more consistant with how lists are handled in the file. Also, don't bother to prebuild libc if we're not building libpthread. Submitted by: ru@ Reviewed by: bde@ (before ru@ submitted it)
* Put on the core hat and back out all of the CSTD= changes. Core willimp2003-06-141-14/+0
| | | | | | | deal with working with the parties to define a coherent definition for CSTD that doesn't break things. Core hat seconded by: markm
* Some glue to allow lint(1) to work on the kernel. This is notmarkm2003-06-142-2/+29
| | | | | complete without some config(8) work. Config(8) needs to provide some ${NORMAL_LINT} rules to make foo.ln files.
* Avoid dereferencing the thread pointer in smb_iod_addrq() if it's NULL.tjr2003-06-141-1/+2
| | | | | Fixes mdconfig -t vnode on smbfs: mdsetcred()'s "horrible kludge" calls into smbfs VOP_READ with a NULL uio_td.
* Don't follow smbnode n_parent pointer when NREFPARENT flag is not settjr2003-06-141-0/+2
| | | | | | in smb_fphelp(): the parent vnode may have already been recycled since we don't hold a reference to it. Fixes a panic when rebooting with mdconfig -t vnode devices referring to vnodes on a smbfs mount.
* Don't truncate the output file before making sure that we cantrhodes2003-06-141-6/+17
| | | | | | | | | | | | | | | | | | | | | read at least 1 byte from the input file without problems. This fixes a bug in uncompress(1) that causes the accidental removal of files that happen to have the same name as the output file, even when the uncompression fails and is aborted, i.e.: $ echo hello world > hello $ touch hello.Z $ ls -l hello* -rw-rw-r-- 1 giorgos giorgos 12 Jun 14 13:33 hello -rw-rw-r-- 1 giorgos giorgos 0 Jun 14 13:33 hello.Z $ ./uncompress -f hello uncompress: hello.Z: Inappropriate file type or format $ ls -l hello* -rw-rw-r-- 1 giorgos giorgos 0 Jun 14 13:33 hello.Z $ PR: 46787 Submitted by: keramida
* Do not bogusly set CSTD to the empty string.des2003-06-143-5/+0
|
* Remove the old xref to kerberos(1), and replace it with an xref totrhodes2003-06-141-1/+1
| | | | | | | kerberos(8). According to markm, the kerberos(8) manual page is installed if NO_KERBEROS is set. PR: 30443
* Fix all WARNS. Checked with "make WARNS=9". Remove unused file.markm2003-06-1410-1184/+133
|
* Set the precedence on failure reports to "bulk" so I don't get tons ofdes2003-06-141-0/+1
| | | | vacation notices every time the tree breaks.
* Add a system policy, and have the login and su policies include it ratherdes2003-06-144-23/+35
| | | | | | than duplicate it. This requires OpenPAM Dianthus, which was committed two weeks ago; installing these files on a system running a world older than June 1st, 2003 will cause login(1) and su(1) to fail.
* Revert to a known-good state. Anyone desiring to experiment with stricterdes2003-06-141-23/+9
| | | | global settings is free to do so in his or her own source tree.
* In the last clean-up of this code, the fact that the default tty modegreen2003-06-141-6/+20
| | | | | | | | information could only be gleaned from the the tty descriptor itself was neglected, so never did the tty's default settings get copied from the kernel. Specifically, this caused all manner of ctrl-keys to not work. Fix this by calling dogettytab() in all the proper places, and retrieving the terminfo temporarily in dogettytab().
* Move the *_new_altkstack() and *_dispose_altkstack() functions out of thealc2003-06-1413-222/+35
| | | | | various pmap implementations into the machine-independent vm. They were all identical.
* Only use this with a non-GCC compiler.obrien2003-06-141-0/+2
|
* Use GCC's internal built-in alloca implementation, when available.obrien2003-06-141-0/+5
| | | | Submitted by: DES
* Remove MAINTAINER= lines in the makefiles for camcontrol, iostat, libcamken2003-06-145-12/+0
| | | | | | | | and libdevstat, since the new way of doing things is to just list maintainership in src/MAINTAINERS. Also, remove duplicate entries in src/MAINTAINERS for those utilities. I already had entries for them.
* Remove kernel event tracing. The overhead is significant when runningmarcel2003-06-141-6/+0
| | | | under ski.
* Document ENOSPC.trhodes2003-06-131-0/+2
| | | | | PR: 52612 Submitted by: Marc Olzheim <marcolz@ilse.nl>
* Fix alignment requirements of tulip_rombuf by further increasingticso2003-06-132-8/+8
| | | | | | tulip_boardid size. Add a comment to tulip_rombuf about this requirement. I have had panics on alpha while probing a de card.
* When building a shared library, link it against libgcc_pic.a instead of thepeter2003-06-131-1/+2
| | | | | | | | | | | non-PIC libgcc.a. Linking non-pic code into a shared library is not a good thing. It happens to break amd64 at compile time, and the ppc folks want it too. The problem is mainly with C++ code, unwind-dw2.c in particular. Most of the other functions in libgcc.a are self contained so most of the time it isn't a problem. The dwarf2 unwinder is not safe though since it does make global variable references. Reviewed by: kan
* If the -proxy_only option is used, the -alias_address/-interfaceru2003-06-132-4/+9
| | | | | | | options are not required. Suggested by: Vaclav Petricek MFC after: 2 weeks
* Build/install the PIC version of libgcc (libcc_pic.a) for use by sharedpeter2003-06-132-0/+4
| | | | libraries that do exception unwinding.
* This is unusable on amd64. Remove it before it causes more confusion.peter2003-06-131-53/+0
| | | | | | It is only possible to do this on an ABI that has a compulsory frame pointer, which the amd64 ABI does not. Thus, it is only possible to implement this as a compiler builtin.
* We cannot use c99 on amd64 either due to lack of alloca(). libc:strptime()peter2003-06-131-2/+3
| | | | | | uses alloca() and alloca is impossible to implement as a callable function on amd64. It has to be a compiler builtin. Note that the bigger problem is that libc is not c99 clean internally.
* In the PKT_ALIAS_PROXY_ONLY mode, make sure to preserve theru2003-06-132-0/+8
| | | | | | original source IP address, as promised in the manual page. Spotted by: Vaclav Petricek
* Removed a couple of .Xo/.Xc that are leftovers of the "ninth-argumentru2003-06-132-18/+6
| | | | limit" mdoc(7) atavism.
* Clarify that original address and port when doing transparent proxyingru2003-06-132-10/+10
| | | | are _destination_ address and port.
* Added myself to the AUTHORS section.ru2003-06-132-0/+4
|
* Add a comment about the MPSAFEness of this pccard_intr handler. Givenimp2003-06-131-0/+4
| | | | | | | | how we registered pccard_intr, it is MPSAFE. However, since we register the pccard_intr handler with the flags of the ISR we call, that is the gating factor. We need do nothing specific here. Prompted by: seeing pccard_intr in a panic.
* Remove code that tries to detect if the MCLSHIFT and MSIZE macrosmux2003-06-132-92/+0
| | | | | | | are the same that those of the kernel in the KLD_MODULE case. If we ever want to detect that kind of problems, this is not the right place to do this since every network driver would be affected by such desynchronisation.
* - Document the fact that you can specify several DMA operations tomux2003-06-131-15/+28
| | | | | | | | | | | | bus_dmamap_sync() by OR'ing them together. - Don't document what BUS_DMASYNC_PREREAD|BUS_DMASYNC_PREWRITE and BUS_DMASYNC_POSTREAD|BUS_DMASYNC_POSTWRITE is supposed to do when passed to bus_dmamap_sync(). There are other possible combinations and the reader just needs to know what the individual flags do and that he can combine different DMA operations. - Use .An when listing authors. Reviewed by: hmp
* Add a retrospective entry about how having installed a broken sed(1)marcel2003-06-131-0/+18
| | | | | | can cause build failures. Triggered by: too many questions on the -current
* Use the <sys/bitstring.h> rather than <bitstring.h>phk2003-06-135-5/+5
|
* Finish the repocopy of bitstring.h to sys so it can be usedphk2003-06-132-125/+10
| | | | from kernel code.
* Style(9).mux2003-06-131-14/+17
|
* Add vm object locking to pmap_object_init_pt().alc2003-06-131-10/+12
|
* Hardwire APB's PCI buses down. If we don't do this, pciconf -l returnsjmg2003-06-131-5/+2
| | | | | | | selectors that are incorrect to use with pciconf -[rw] Fixes-PR: sparc64/50789 Ok's by: tmm
* - Use _PATH_TTY and _PATH_DEVNULL macros.mux2003-06-131-5/+9
| | | | | | | | | | | - Don't fail if we can't open /dev/null since this can happen if xargs is jail'ed or chroot'ed. These fixes were submitted by Todd Miller from the OpenBSD project. There was one problem in those fixes that broke -o, which is corrected here and should be committed to the OpenBSD repo by Todd soon. MFC in: 3 days
* Eliminated two dozens of superfluous cats and two r-cats (sorry, Jordan).ru2003-06-131-73/+51
| | | | Suggested by: Dan Nelson
* Implement the ioctl that returns a list of currently open VCCs.harti2003-06-131-0/+70
|
* Factor out the description of how to configure a CLIP into its ownharti2003-06-134-29/+130
| | | | | | man page. This will be more scaleable as more driver man pages hit the tree. Add also a description on how to do this configuration in the rc.conf script.
* Remove the documentation of the raw AAL0 access which has been removed.harti2003-06-131-28/+0
| | | | | This raw cell stuff not used in the tree and a doubt that it is used anywhere else. It was also very Midway specific.
* Make the midway driver use the new ATM phy driver. This allows one toharti2003-06-137-7/+101
| | | | | | | toggle several media options (sonet/sdh, for example) with ifconfig and to see the carrier state in ifconfig's output. It gives also read/write access (given the right privilegs) to the S/Uni registers to user space programs.
* Regen.joe2003-06-132-2/+9
|
* Allow the EPSON USB scanner 1250 to be recognised as a uscanner device.joe2003-06-132-0/+2
| | | | | | Submitted by: Cristiano Deana <deana@bmm.it> By way of: n_hibma MFC after: 3 days
* Plug a serious memory leak. The -STABLE equivalent of this patch hasdas2003-06-131-8/+20
| | | | | | | | | | | been tested extensively, but -CURRENT testing has been hampered by a number of panics that also occur without the patch. Since the destabilizing changes between 4.X and 5.X are external to unionfs, I believe this patch applies equally well to both. Thanks to scrappy for assistance testing these and other changes. MFC after: 4 days
OpenPOWER on IntegriCloud