summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* MF4S: Syncronise with Luigi's work in -stable.joe2001-04-2419-270/+201
|
* MFS: the MFS still applies to -current until such time as someone fixesimp2001-04-245-75/+95
| | | | | rc.diskless2 to use mdconfig rather than mount_mfs. These changes are still relevant to -current.
* Add warning, and resolution, of the fsck and kernel problemimp2001-04-241-0/+9
|
* ${MAKEOBJDIRPREFIX}/usr/src/i386/usr/include/isc was being created as a plaingshapiro2001-04-241-1/+1
| | | | | | file during the bootstrapping process of a buildworld and contained the last isc include file to be installed. It was meant to be a directory for the isc include files.
* Handle IP over IP (IPPROTO_IPV4) properly.brian2001-04-245-12/+32
| | | | | | | | | We now unwrap IP/IP and apply filter rules to both the outer layer (with ``set filter blah x.x.x.x y.y.y.y ipip'') and to the payload (reinterpreted by the filter rules). ``set log tcp/ip'' will now show both the outer wrapper and the (reinterpreted) payload contents.
* Change the pfind() and zpfind() functions to lock the process that theyjhb2001-04-2435-285/+385
| | | | | | find before releasing the allproc lock and returning. Reviewed by: -smp, dfr, jake
* Pre-dirpref versions of fsck may zero out the new superblock fieldsiedowse2001-04-241-0/+6
| | | | | | | | | | | fs_contigdirs, fs_avgfilesize and fs_avgfpdir. This could cause panics if these fields were zeroed while a filesystem was mounted read-only, and then remounted read-write. Add code to ffs_reload() which copies the fs_contigdirs pointer from the previous superblock, and reinitialises fs_avgf* if necessary. Reviewed by: mckusick
* Apply 'const' liberally.archie2001-04-248-129/+134
| | | | Fix some other minor glitches.
* Back out previous commit.grog2001-04-231-0/+4
| | | | Requested by: bde
* Fix a bug introduced in the last commit: vaccess_acl_posix1 only checkedtmm2001-04-233-3/+3
| | | | | | | the file gid gainst the egid of the accessing process for the ACL_GROUP_OBJ case, and ignored supplementary groups. Approved by: rwatson
* Add als4000 subdir.orion2001-04-231-3/+3
|
* Initial version of Avance Logic ALS4000 pcm driver.orion2001-04-235-0/+1005
|
* In fsdb, call sblock_init() which is now necessary to initialiseiedowse2001-04-233-0/+3
| | | | | the global variable dev_bsize. Add a prototype for sblock_init() to fsck.h, and set the return type correctly.
* MF4S: Syncronise with Luigi's work in -stable.joe2001-04-233-116/+0
|
* Keep my dirty paws off of the $NetBSD$ id's. They're tabbed and shouldasmodai2001-04-234-5/+5
| | | | | | remain so. Submitted by: bde/obrien
* MF4S: Sync with the developments that Luigi's been doing in -stable.joe2001-04-237-1070/+8
|
* MF4S: Remove some unused error messages. (revision 1.1.2.5)joe2001-04-231-13/+1
|
* Apply style guidelines (using gident to help).joe2001-04-232-424/+471
|
* fix it so it compiles againmjacob2001-04-2312-0/+24
|
* Fix a syntax error.joe2001-04-231-2/+2
|
* fix it so it compiles again after twerpage elsewheremjacob2001-04-231-0/+2
|
* add this ridiculous include foo so it will compile againmjacob2001-04-232-0/+4
|
* Fix includes so it compiles again.mjacob2001-04-232-2/+4
|
* Update this to reflect changes in config(8) usage.phk2001-04-231-8/+5
| | | | | It finds 639 hits on kernel source from before the <sys/mount.h> change earlier today.
* mdoc(7) police: update HISTORY section.ru2001-04-231-1/+1
| | | | This interface is not available in 4.3-RELEASE.
* The semantics of the .Os call has been changed. For CURRENT,ru2001-04-233-12/+3
| | | | this currently implies the default argument of "FreeBSD 5.0".
* Fix the fix in rev.1.34.ru2001-04-231-1/+1
| | | | | Makes `cleandir' DTRT if MAKEOBJDIRPREFIX set and not empty, like in `buildworld' case.
* If the world was built using either -DNOCLEAN or -DNOCLEANDIR, it wasru2001-04-231-0/+4
| | | | | | | | | | | | | | | possible to use old generated doc-* files as the source for new ones. Wrong -mdoc files would then be installed, and man(1) failed with the following diagnostics: mdoc error: end-macro (.em) respecification is not allowed. (#41) Should this have been `.Em ...'? Put helper stuff into `beforedepend' to cleanup old files. Makefile first infected in rev 1.15. Reported via: -current
* Add sranddev.3 to MLINKSache2001-04-231-1/+1
|
* Add #include "un-namespace.h"ache2001-04-231-0/+1
|
* srand*dev() fallback code: change ^getpid() to ^(getpid() << 16) to allowache2001-04-232-2/+2
| | | | change of high word part too to produce more interesting seed distribution.
* Reinstate one more old bugfix that got lost in the tirpc commit:iedowse2001-04-232-30/+40
| | | | | | | always look up -network and -mask addresses numerically before trying getnetbyname(). Without this, we may end up attempting DNS queries on silly names such as "127.0.0.0.my-domain.com". See the commit log from revisions 1.21 and 1.20 for further details.
* Fix directory reads of MNT_UNION mounts, where entries present in bothjoerg2001-04-231-1/+2
| | | | | | | layers would be displayed twice. PR: bin/26498 Submitted by: Olliver Fromme <olli@secnetix.de>
* Move sranddev() to !ANSI_SOURCE !POSIX_SOURCE sectionache2001-04-231-1/+1
| | | | Pointed out by: bde
* Correct #includes to work with fixed sys/mount.h.grog2001-04-2385-0/+169
|
* This is not a problem but a feature of PMake.ru2001-04-231-1/+0
| | | | Pointed out by: bde
* Correct #includes to work with fixed sys/mount.h.grog2001-04-2314-0/+28
|
* Remove bogus #include and duplicate definition of AF_MAX. These weregrog2001-04-231-4/+0
| | | | | | | | made necessary by breakage in usr.sbin/pstat and usr.bin/fstat, since fixed. Suggested by: phk Unearthed by: John Hood <jhood@sitaranetworks.com>
* Include necessary header files, in preparation for fixing breakage ingrog2001-04-231-0/+2
| | | | | | sys/mount.h. Suggested by: phk
* Include correct header files, in preparation for fixing sys/mount.h.grog2001-04-232-0/+3
| | | | Suggested-by: phk
* Add .Lb entry for -ldevinfo.ru2001-04-231-0/+1
|
* mdoc(7) police: fix markup.ru2001-04-231-31/+31
|
* %DCL-I-FORMATRIGHT, Format VMS error messages pedantically correct.imp2001-04-231-2/+2
|
* Add address families AF_SLOW and AF_SCLUSTER. These are used by thegrog2001-04-232-3/+8
| | | | | | Sitara QoSworks box. Obtained from: Sitara Networks Inc.
* Add sranddev() prototypeache2001-04-231-0/+1
|
* Add sranddev() since srand() is not vary much with seed, typical timeache2001-04-232-1/+46
|
* MFS4: Do not terminate if it fails to clean something. (rev 1.12.2.5)joe2001-04-221-1/+1
|
* FFS_ROOT was made obsolete, so remove it from the PicoBSD kernels.joe2001-04-226-6/+0
|
* When exporting a directory that is not a mountpoint, mountd repeatedlyiedowse2001-04-222-0/+16
| | | | | | | | | | | | | removes the last path component until the mount() succeeds. However, the code never checks if it has passed the mountpoint, so in some cases where the mount() never succeeds, it can end up applying the flags from a mounted filesystem to the underlying one. Add a sanity check to the code which removes the last path component: test that the fsid associated with the new path is the same as that of the old one. PR: bin/7872
* Fix the `tape drive spinning indefinately upon mt stat' problem.joerg2001-04-221-2/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With the recent changes in the CAM error handling, some problems in the error handling of sa(4) have been uncovered. Basically, a number of conditions that are not actually errors have been mistreated as genuine errors. In particular: . Trying to read in variable length mode with a mismatched blocksize between the on-tape (virtual) blocks and the read(2) supplied buffer size, causing an ILI SCSI condition, have caused an attempt to retry the supposedly `errored' transfer, causing the tape to be read continuously until it eventually hit EOM. Since by default any simple mt(1) operation does an initial test read, an `mt stat' was sufficient to trigger this bug. Note that it's Justin's opinion that treating a NO SENSE as an EIO is another bug in CAM. I feel not authorized to fix cam_periph.c without another confirmation that i'm on the right track, however. . Hitting a filemark caused the read(2) syscall to return EIO, instead of returning a `short read'. Note that the current fix only solves this problem in variable length mode. Fixed length mode uses a different code path, and since i didn't grok all the intentions behind that handling, i did not touch it (IOW: it's still broken, and you get an EIO upon hitting a filemark). The solution is to keep track of those conditions inside saerror(), and upon completion to not call cam_periph_error() in that case. We need to make sure that the device gets unfrozen if needed though (in case of actual errors, cam_periph_error() does this on our behalf). Not objected by: mjacob (who currently doesn't have the time to review the patch)
OpenPOWER on IntegriCloud