summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* mdoc(7) police: get rid of hard sentence breaks, add missing .El, etc.ru2000-12-291-7/+11
|
* Partially revert revision 1.7: Only use getnanotime instead ofgrog2000-12-291-1/+9
| | | | | | | nanotime if we would run into trouble with nanotime (i.e. if we are tracing KTR_LOCK). Reviewed by: jhb
* Fix a legacy issue. The offset for reading the MAC address is 0 usingpaul2000-12-291-1/+2
| | | | bus space, not iosize which is what it was when using inb().
* fix typos.ben2000-12-291-2/+2
| | | | | PR: 23934 Submitted by: Alex Kapranoff <alex@kapran.bitmcnit.bryansk.su>
* Add some text saying that this page may occasionally be out of date with theben2000-12-291-0/+7
| | | | real make.conf.
* Add $FreeBSD$peter2000-12-292-0/+4
|
* Map FreeBSD character device hard disks to Linux block device hard disks.paul2000-12-291-0/+14
| | | | This fixes the problem with VMWARE not being able to use raw disks.
* add a couple off offset defines for ATIO2smjacob2000-12-281-0/+3
|
* roll to 2.01.26 levelmjacob2000-12-281-5227/+4903
|
* remove MAINTAINER filemjacob2000-12-281-2/+0
|
* New release notes: vinum(4) updates, ICMP ECHO and TSTAMP replybmah2000-12-282-2/+57
| | | | | | | | | rate limiting, ICMP admin prohibited handling, PECOFF support, retired kernfs(5), killall(1) behavior restored, rm(1) -v output change, lpr(1)/lpq(1)/lpd(8) enhancements, pkg_update(1), libdisk install-time configuration of boot0 for i386. Also note MFC of an(4) changes for WEP.
* This is repo-copied from vnioctl.hphk2000-12-281-24/+24
|
* Add mdconfig into the build.phk2000-12-281-0/+1
|
* Add the "mdctl" device under the "std" stanza.phk2000-12-281-0/+1
|
* Preliminary scaffolding for the new integrated vn+md device driver.phk2000-12-282-0/+110
| | | | | | | | | | | | | | | | | I decided to work on the md(4) driver and integrate the vn(4) functionality into it mainly based on the name being more suitable. Ideally 'vd' as in "virtual disk" would probably be the most logical but our sound-master pointed out that this would cause uncontrollable fits of giggles in the brits. Another complication would the needed changes to the ramdisk boot/root functionality. The vn driver will stay around for some time after I complete this merge for transition reasons, and I'll make it whine to people that they should migrate to the md(4) driver for some time before it dies. The kernel part of the new md(4) driver will be committed after more testing.
* Fix the broken options that were in the development version I committed by ↵paul2000-12-281-1/+2
| | | | mistake.
* * Fix a segfault when timed(8) receives a packet with a bad tsp_type.ben2000-12-281-2/+17
| | | | | | | * Check that received packets aren't too short, as this could cause other problems. Reviewed by: imp, markm
* Bring the man page up to date with the current version of the script.paul2000-12-281-3/+25
|
* Add pkg_update, which can replace currently installed ports with new versionspaul2000-12-284-1/+276
| | | | while taking of updating all the dependencies.
* Remove prototypes for pthread_attr_[gs]etfloatstate(), which we don'tjasone2000-12-281-3/+0
| | | | implement.
* Move all VCS ids to a consistent location.obrien2000-12-282-6/+4
|
* Add multiple inclusion protection.obrien2000-12-282-0/+10
| | | | | PR: 23902 Submitted by: Christian Weisgerber <naddy@mips.inka.de>
* grammar gnit: "relationships (plural) _are_ complex"hoek2000-12-281-1/+1
|
* typo: modifes -> modifieshoek2000-12-282-2/+2
|
* Mdoc(7)ify.ru2000-12-281-306/+466
|
* Retire kernfs (userland part).des2000-12-288-145/+9
|
* Retire kernfs (kernel part).des2000-12-2812-921/+2
|
* Reflect rev 1.18 in crypt.c. Note that this section is somewhatpeter2000-12-281-3/+5
| | | | mangled and could do with some word-smithing.
* Hindsight is wonderful, but I got cold feet over the crypt(3) defaultpeter2000-12-281-5/+5
| | | | | | | | | | | | | | | | | so I am backing it out for now. The problem is that some random program calling crypt() could be passing a DES salt and the crypt(3) library would encrypt it in md5 mode and there would be a password mismatch as a result. I wrote a validater function for the DES code to verify that a salt is valid for DES, but I realized there were too many strange things to go wrong. passwd(1), pw(8) etc still generate md5 passwords by default for /etc/master.passwd, so this is almost academic. It is a big deal for things that have their own crypt(3)-ed password strings (.htaccess, etc etc). Those are the things I do not want to break. My DES salt recognizer basically checked if the salt was either 2 or 13 characters long, or began with '_' (_PASSWORD_EFMT1). I think it would have worked but I have seen way too much crypt() mishandling in the past.
* Merge into a single US-exportable libcrypt, which only providespeter2000-12-288-205/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | one-way hash functions for authentication purposes. There is no more "set the libcrypt->libXXXcrypt" nightmare. - Undo the libmd.so hack, use -D to hide the md5c.c internals. - Remove the symlink hacks in release/Makefile - the algorthm is set by set_crypt_format() as before. If this is not called, it tries to heuristically figure out the hash format, and if all else fails, it uses the optional auth.conf entry to chose the overall default hash. - Since source has non-hidden crypto in it there may be some issues with having the source it in some countries, so preserve the "secure/*" division. You can still build a des-free libcrypt library if you want to badly enough. This should not be a problem in the US or exporting from the US as freebsd.org had notified BXA some time ago. That makes this stuff re-exportable by anyone. - For consistancy, the default in absence of any other clues is md5. This is to try and minimize POLA across buildworld where folk may suddenly be activating des-crypt()-hash support. Since the des hash may not always be present, it seemed sensible to make the stronger md5 algorithm the default. All things being equal, no functionality is lost. Reviewed-by: jkh (flame-proof suit on)
* Send a SIGCONT when detaching or continuing the excution of a tracedps2000-12-281-0/+1
| | | | | | | | process. This fixes a problem when attaching to a process in gdb and the process staying in the STOP'd state after quiting gdb. This whole process seems a bit suspect, but this seems to work. Reviewed by: peter
* Pull out the module path from the loader. ie: if you boot frompeter2000-12-282-4/+30
| | | | | | | | /boot/kernel.foobar/* then that had better be in the path ahead of the others. Submitted by: Daniel J. O'Connor <darius@dons.net.au> PR: 23662
* When trying to deduce the diskname from the name so we can runphk2000-12-272-8/+13
| | | | | | | | | | | | | | | | | parallel fsck's one per drive, use the shortest prefix ending in a digit rather than the longest prefix ending in a digit. This makes "/dev/ad0s1a" and "/dev/ad0s2a" appear to both reside on the disk "/dev/ad0" and consequently they will be fsck'ed sequentially rather than in parallel as now. In general this heuristic is rather soft and errorprone. For instance ccd may often reside on two or more physical disks. A good solution would be to look for passes larger than 1 until no disks are found in a particular pass, that way people could put ccd stripes in pass 3... and have them fsck'ed sequentially. Reviewed by: mjacob
* Small fix for bpf compat:bmilekic2000-12-272-1/+2
| | | | | Make malloc() use M_NOWAIT istead of M_DONTWAIT and in the bpf_compat case, define M_NOWAIT to be M_DONTWAIT.
* Use official API to <sys/queue.h> instead of groping around inside thephk2000-12-271-17/+16
| | | | | | data structures. Reviewed by: imp
* Link stringlist.3 to sl_{add,find,free,init}.3ben2000-12-271-0/+2
|
* Prepare for mdoc(7)NG.ru2000-12-279-25/+19
|
* Prepare for mdoc(7)NG.ru2000-12-272-14/+10
|
* Prepare for mdoc(7)NG.ru2000-12-2773-423/+294
|
* Prepare for mdoc(7)NG.ru2000-12-277-26/+26
|
* Prepare for mdoc(7)NG.ru2000-12-273-201/+306
|
* Prepare for mdoc(7)NG.ru2000-12-271-1/+1
|
* Prepare for mdoc(7)NG.ru2000-12-276-36/+40
|
* Major bugfix and minor update. This should resolve the current issuesmsmith2000-12-279-338/+437
| | | | | | | | | | | | | | | | | | | | | | | | | with the driver locking up under load. - Restructure so that we use a static pool of commands/FIBs, rather than allocating them in clusters. The cluster allocation just made things more complicated, and allowed us to waste more memory in peak load situations. - Make queueing macros more like my other drivers. This adds queue stats for free. Add some debugging to take advantage of this. - Reimplement the periodic timeout scan. Kick the interrupt handler and the start routine every scan as well, just to be safe. Track busy commands properly. - Bring resource cleanup into line with resource allocation. We should now clean up correctly after a failed probe/unload/etc. - Try to start new commands when old ones are completed. We weren't doing this before, which could lead to deadlock when the controller was full. - Don't try to build a new command if we have found a deferred command. This could cause us to lose the deferred command. - Use diskerr() to report I/O errors. - Don't bail if the AdapterInfo structure is the wrong size. Some variation seems to be normal. We need to improve our handing of 2.x firmware sets. - Improve some comments in an attempt to try to make things clearer. - Restructure to avoid some warnings.
* change irq handler slightly, get rid of superflous messagescg2000-12-271-6/+4
|
* include tcp header files to get the prototype for tcp_seq_vs_sessassar2000-12-271-0/+2
|
* Make zalloc and zfree non-inline functions. This avoids having toassar2000-12-272-78/+77
| | | | | | | have the code calling these be compiled with the same setting for INVARIANTS and SMP. Reviewed by: dillon
* Fix a quoting problem I introduced.dougb2000-12-261-2/+2
| | | | | | Fix a tiny style problem while I'm here. Submitted by: knu
* Fix an annoying message ``gdb: ptrace(PT_GETDBREGS) failed: No such process''joerg2000-12-261-0/+15
| | | | | | | | | | | when using gdb on a remote target. The fix is to restrict PT_GETDBREGS calls to `child' and `freebsd-uthreads' targets solely. I've been in some conversation with Brian about this, and this solution seems to be the most appropriate one. PR: gnu/21685 Submitted by: bsd
* This implements a better launder limiting solution. There was a solutiondillon2000-12-2611-252/+304
| | | | | | | | | | | | | | | | | | | in 4.2-REL which I ripped out in -stable and -current when implementing the low-memory handling solution. However, maxlaunder turns out to be the saving grace in certain very heavily loaded systems (e.g. newsreader box). The new algorithm limits the number of pages laundered in the first pageout daemon pass. If that is not sufficient then suceessive will be run without any limit. Write I/O is now pipelined using two sysctls, vfs.lorunningspace and vfs.hirunningspace. This prevents excessive buffered writes in the disk queues which cause long (multi-second) delays for reads. It leads to more stable (less jerky) and generally faster I/O streaming to disk by allowing required read ops (e.g. for indirect blocks and such) to occur without interrupting the write stream, amoung other things. NOTE: eventually, filesystem write I/O pipelining needs to be done on a per-device basis. At the moment it is globalized.
OpenPOWER on IntegriCloud