summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merged src/lib/libtelnet rev.1.9 (fixed removing of obsolete sharedru2001-03-281-8/+5
| | | | | | | | | | library: wrong library directory, wrong library extension and wrong comment). This is mainly of historical interest, if any. The library that gets removed is aout. Also, backout the beforeinstall -> afterinstall change in rev.1.20 that was required to install proper telnet.h into /usr/include/arpa. The actual problem is in <bsd.lib.mk>, and I am going to fix it.
* Bye-bye /usr/lib/libtelnet.a. This should fix ``make release'' brokeness.ru2001-03-2815-20/+49
| | | | Approved by: markm
* Convert the allproc and proctree locks from lockmgr locks to sx locks.jhb2001-03-2829-164/+172
|
* Put a note about ee(1) update.sobomax2001-03-282-0/+4
|
* Axe out duplicate.phk2001-03-281-15/+0
| | | | | | | Not to submitter: (I don't let Jordan use my axe) PR: 24782 Submitted by: Szilveszter Adam <sziszi@petra.hos.u-szeged.hu>
* Spelling fixes.phk2001-03-281-3/+3
| | | | | PR: 20474 Submitted by: Christian Weisgerber <naddy@mips.inka.de>
* Remove duplicate.phk2001-03-281-12/+0
| | | | | PR: 19670 Submitted by: Anton Berezin <tobez@tobez.org>
* Remove a duplicate piece of chalk.phk2001-03-282-4/+0
| | | | | PR: 23132 Submitted by: Alex Kapranoff <alex@kapran.bitmcnit.bryansk.su>
* OpenBSD's g_Ctoc() returned a false error when the target buffer waspeter2001-03-281-16/+16
| | | | | | exactly the right size. Do it differently - pass a length rather than an end-of-string+1 pointer as this is more convenient anyway. Get rid of the bogus +1's.
* Pass in a pointer to the mutex's lock_object as the second argument tojhb2001-03-281-4/+4
| | | | WITNESS_SLEEP() rather than the mutex itself.
* Remove sockets found in /var/run or /var/spool/lock at boot timebrian2001-03-281-1/+1
| | | | (as well as files).
* Fix g_Ctoc() interface, approximately based on OpenBSD's recent changes.peter2001-03-281-14/+36
| | | | | | | Also, set gl_pathv to NULL after we free it, especially when dealing with realloc failures. Obtained from: OpenBSD
* Bring the PPPoE interface UP if requiredbrian2001-03-284-13/+28
| | | | Suggested by: archie
* Catch up to header include changes:jhb2001-03-2843-22/+51
| | | | | - <sys/mutex.h> now requires <sys/systm.h> - <sys/mutex.h> and <sys/sx.h> now require <sys/lock.h>
* Use mtx_initiaalized() rather than violating the internals of the mutexjhb2001-03-281-2/+1
| | | | structure.
* Rework the witness code to work with sx locks as well as mutexes.jhb2001-03-2833-3852/+1279
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Introduce lock classes and lock objects. Each lock class specifies a name and set of flags (or properties) shared by all locks of a given type. Currently there are three lock classes: spin mutexes, sleep mutexes, and sx locks. A lock object specifies properties of an additional lock along with a lock name and all of the extra stuff needed to make witness work with a given lock. This abstract lock stuff is defined in sys/lock.h. The lockmgr constants, types, and prototypes have been moved to sys/lockmgr.h. For temporary backwards compatability, sys/lock.h includes sys/lockmgr.h. - Replace proc->p_spinlocks with a per-CPU list, PCPU(spinlocks), of spin locks held. By making this per-cpu, we do not have to jump through magic hoops to deal with sched_lock changing ownership during context switches. - Replace proc->p_heldmtx, formerly a list of held sleep mutexes, with proc->p_sleeplocks, which is a list of held sleep locks including sleep mutexes and sx locks. - Add helper macros for logging lock events via the KTR_LOCK KTR logging level so that the log messages are consistent. - Add some new flags that can be passed to mtx_init(): - MTX_NOWITNESS - specifies that this lock should be ignored by witness. This is used for the mutex that blocks a sx lock for example. - MTX_QUIET - this is not new, but you can pass this to mtx_init() now and no events will be logged for this lock, so that one doesn't have to change all the individual mtx_lock/unlock() operations. - All lock objects maintain an initialized flag. Use this flag to export a mtx_initialized() macro that can be safely called from drivers. Also, we on longer walk the all_mtx list if MUTEX_DEBUG is defined as witness performs the corresponding checks using the initialized flag. - The lock order reversal messages have been improved to output slightly more accurate file and line numbers.
* - Resort some includes to deal with the new witness code coming in shortly.jhb2001-03-281-4/+8
| | | | | | - Make sure we have Giant locked before calling coredump() in sigexit(). Spotted by: peter (2)
* Add a manpage for the critical_enter/exit() functions.jhb2001-03-282-1/+99
|
* Back out previous commit until I figure out a way to do it properly.jlemon2001-03-281-11/+1
| | | | | | We really want to be able to say "auto NWAY", "limited NWAY", and "no NWAY". Unfortunately, this does not appear to be possible with the current mediaopt structure.
* Fix nasty corruption problem where a 64bit variable was being usedmarkm2001-03-281-8/+6
| | | | | | (overflowed) to catch a 256bit result. Hard work done by: jhb
* Add support for the Addtron AWA100 PCI wireless card.alfred2001-03-282-16/+157
| | | | | | | The AWA100 is a PCI board with a PLX 9052 chip that's used to talk to the pccard inserted into the board. Remove a redundant $FreeBSD while I'm here.
* Don't explicitly zero p_intr_nesting_level and p_aioinfo in fork.jhb2001-03-281-2/+0
|
* - Fix a whitespace bogon with p_blocked.jhb2001-03-281-4/+4
| | | | | - Move p_intr_nesting_level, p_aioinfo, and p_ithd into the zero'd area so that we don't have to explicitly zero them during fork().
* Switch from save/disable/restore_intr() to critical_enter/exit().jhb2001-03-2818-417/+343
|
* Catch up to the mtx_saveintr -> mtx_savecrit change.jhb2001-03-284-6/+6
|
* Use mtx_intr_enable() on sched_lock to ensure child processes always startjhb2001-03-281-2/+2
| | | | | | with interrupts enabled rather than calling the no-longer MI function enable_intr(). This is bogus anyways and in theory shouldn't even be needed.
* - Switch from using save/disable/restore_intr to using critical_enter/exitjhb2001-03-289-97/+171
| | | | | | | | | | | | | | | | | and change the u_int mtx_saveintr member of struct mtx to a critical_t mtx_savecrit. - On the alpha we no longer need a custom _get_spin_lock() macro to avoid an extra PAL call, so remove it. - Partially fix using mutexes with WITNESS in modules. Change all the _mtx_{un,}lock_{spin,}_flags() macros to accept explicit file and line parameters and rename them to use a prefix of two underscores. Inside of kern_mutex.c, generate wrapper functions for _mtx_{un,}lock_{spin,}_flags() (only using a prefix of one underscore) that are called from modules. The macros mtx_{un,}lock_{spin,}_flags() are mapped to the __mtx_* macros inside of the kernel to inline the usual case of mutex operations and map to the internal _mtx_* functions in the module case so that modules will use WITNESS and KTR logging if the kernel is compiled with support for it.
* Mention that the vga(4) driver supports 90-column video modes.dd2001-03-281-0/+10
| | | | | | PR: 26050 Submitted by: Alex Kapranoff <alex@kapran.bitmcnit.bryansk.su> Approved by: nik
* - Add the new critical_t type used to save state inside of criticaljhb2001-03-287-58/+57
| | | | | | | | | sections. - Add implementations of the critical_enter() and critical_exit() functions and remove restore_intr() and save_intr(). - Remove the somewhat bogus disable_intr() and enable_intr() functions on the alpha as the alpha actually uses a priority level and not simple bit flag on the CPU.
* Previous commit message was bogus:jhb2001-03-280-0/+0
| | | | - Switch to using critical_enter/exit instead of save/disable/restore_intr.
* Revert previous commit which had a bogus message. It actually justjhb2001-03-281-1/+1
| | | | disabled the somewhat annoying KTR log trace for clock interrupts.
* Previous commit message was bogus:jhb2001-03-280-0/+0
| | | | - Catch up to rename of mtx_saveintr to mtx_savecrit within struct mtx.
* Previous commit message was bogus, here's the real one:jhb2001-03-280-0/+0
| | | | | | | | | - Switch to using critical_enter/exit instead of save/disable/restore_intr. - Disable interrupts in Debugger(). This second change wasn't really supposed to go in, but since it's in there and is useful so that one doesn't get spammed with clock interrupts while in ddb, I'll leave it in unless people want it reverted.
* The previous commit message is bogus, this actually just removed anjhb2001-03-280-0/+0
| | | | unused variable to silence a warning.
* - Include <machine/prom.h> to get the prototype for prom_halt().jhb2001-03-289-58/+57
| | | | | | | | - If there is no gdb device, just return without trying to return any value since gdb_handle_exception() returns void. - When calling prom_halt(), pass in a value telling it to actually halt and not to randomly choose whether or not to halt or reboot depending on whatever value happened to be in a0 when the call was made.
* Last commit was broken.. It always prints '[CTRL-C to abort]'.ps2001-03-286-51/+31
| | | | | | | Move duplicate code for printing the status of the dump and checking for abort into a separate function. Pointy hat to: me
* Check whether we need to do a full restore after handling ASTs. Ifgallatin2001-03-281-4/+4
| | | | | | | | | | | | | | | an AST results in a signal being delivered, we'll need to do a full register restore so as to properly setup the signal handler. This is somewhat of a pessimization, because ast() will be called twice in this case. This fixes several problems that have been reported where signal intensive userland apps (most notably dump) have been SEGV'ing for no fault of their own. Thanks to Peter Jeremy <peter.jeremy@alcatel.com.au> for presenting the AST scenario which led to me fiinally figuring this out. Reviewed by: jhb
* o De-uglify IMPLEMENTATION NOTES section by removing unnecessary use ofrwatson2001-03-282-4/+2
| | | | .Fx
* Add some comments to two examples and extend a ``set ifaddr''.brian2001-03-282-6/+6
|
* Restore part of my fix spammed in v1.23:ache2001-03-271-1/+1
| | | | | | fseeko(file_size, SEEK_SET) -> fseek(0L, SEEK_END) 1) File may grows between operations, so fseeko to file_size may miss 2) 0L, SEEK_END is the same code using in tail in all other places
* Update the acknowledgements section.jkh2001-03-272-38/+6
|
* Finally fix __yp_ping(). We can't use the old locally defined clntudp_call()wpaul2001-03-271-239/+26
| | | | | | | method anymore since the code inside the RPC library has changed too much. Now that the clnt_dg module has the necessary code internally, we can yank out the local method code and turn on the ASYNC hack with clnt_control(). This will make the -m flag work again.
* Add a CLSET_ASYNC command, which allows us to (ab)use the clnt_dg transportwpaul2001-03-272-3/+20
| | | | | | | | | | | | | | | | | | to make asynchronous RPCs. This is needed to help fix ypbind, which can no longer override the clnt_dg_call() method (formerly the clntudp_call() method) due to all the internal descriptor locking code in TI-RPC. Turning on this flag allows us to send an RPC request, then return immediately, and handle a reply later, rather than being forced to do the request and reply in a single function call. Also fix a byte ordering bug: when clnt_dg_call() increments the XID prior to transmitting a request, it uses the raw value, which is wrong. The XID is stored in network byte order, i.e. big-endian. The CLSET_XID and CLGET_XID commands in clnt_dg_control() use ntohl()/htonl() to get the byte ordering right, but because clnt_dg_call() does not do this, using CLSET_XID/CLGET_XID doesn't actually work, unless you're on a big endian host, which we aren't (yet). Fix clnt_dg_call() to byte swap properly when doing the increment.
* New release notes: Filesystem ACLs, getfacl(1) and setfacl(1).bmah2001-03-272-0/+16
| | | | Submitted by: rwatson
* Don't leak the memory we've just malloced if we can't find thedwmalone2001-03-271-2/+2
| | | | | | | | process we're looking for. (I don't think this can currently happen, but it depends how the function is called). PR: 25932 Submitted by: David Xu <davidx@viasoft.com.cn>
* Fix tail to work on files bigger than 2GB.dwmalone2001-03-274-65/+146
| | | | | PR: 14786 Reviewed by: iedowse
* Document LOG_CONSOLE.cwt2001-03-272-3/+8
|
* Add full PAM support for account management and sessions.markm2001-03-2712-184/+686
| | | | | | | The PAM_FAIL_CHECK and PAM_END macros in su.c came from the util-linux package's PAM patches to the BSD login.c Submitted by: "David J. MacKenzie" <djm@web.us.uu.net>
* Make rev 1.5 better match the rest of dump(8)'s output.obrien2001-03-271-2/+2
|
* Do not exit if unable to read /etc/dumpdates or create it.obrien2001-03-271-2/+4
| | | | | | If one is trying to dump or repair an ill system, give the user a fighting chance. Refusing to operate w/o a very non-critical file (feature) is just plain stupid.
OpenPOWER on IntegriCloud