summaryrefslogtreecommitdiffstats
path: root/usr.sbin
Commit message (Collapse)AuthorAgeFilesLines
* Add cvs Id.mpp1997-03-121-0/+1
|
* Make amd actually work instead of just compiling. The new Lite2 codepeter1997-03-122-3/+4
| | | | | | was not setting the version number in the nfs_args data to mount(2), so it was returning EFAULT. Perhaps the nfs_args version number was something we added at some point?
* Tidy up generated fstabjkh1997-03-122-12/+10
|
* Fix a long-standing bug with the label editor I just found (you couldjkh1997-03-113-26/+28
| | | | | | mount two dos partitions with the same name). Neaten up a dialog box that was encroaching on the right edge.
* YAMF22jkh1997-03-113-19/+20
|
* YAMF22 (rev 1.70.2.10, added blurb to explanations)joerg1997-03-112-2/+14
|
* Update to work under Lite2 includespeter1997-03-116-3/+9
|
* I feel sick. :-( There is some really, truely, shameful stuff in herepeter1997-03-113-10/+106
| | | | | | to try and work around the nfsv3 headers in the post-lite2-kernel era. This program somehow manages to make just about every #include conflict with everything else. :-(
* Update to compile under Lite2 fs include layoutpeter1997-03-111-0/+1
|
* Update to compile under Lite2 includespeter1997-03-111-1/+2
|
* Fix srandom arg according to Lite2ache1997-03-111-3/+3
|
* Merge from Lite2 (use special dbopen flags)peter1997-03-111-9/+12
|
* Merge Lite2 changespeter1997-03-112-153/+120
|
* Merge from Lite2 (use new getvfsbyname() interface)peter1997-03-113-11/+12
|
* Merge from Lite2 (use new getvfsbyname() and mount(2) interface, cleanup)peter1997-03-114-85/+63
|
* Merge from Lite2 (use new getvfsbyname() and mount(2) interface)peter1997-03-115-32/+32
|
* Kill sup from the main sources now that the ports version is updated.peter1997-03-1142-13660/+2
| | | | | | This puts it on the same footing as cvsup. It's been suggested on numerous occasions that I shouldn't have imported it in the first place, and now that sup has outlived it's usefulness..... Boom!
* Merge all my sysinstall changes over to the 2.1 branch.jkh1997-03-112-21/+9
| | | | I just have this feeling... :)
* YAMF22jkh1997-03-112-4/+2
|
* Sync with 2.2.jkh1997-03-107-23/+58
|
* Update russian mirrors.jkh1997-03-102-4/+4
|
* Do not re-initialize random numbers generator several times.ache1997-03-102-4/+12
| | | | Use ^ getpid() to produce better initial state.
* Detect failure open condition for direct mode nowache1997-03-101-3/+9
| | | | | Don't assume that modem descriptor must be >=3 in CloseModem, just assume it is any valid descriptor >=0
* Don't waste time scanning tun_in+10 descriptors, scan exactly whatache1997-03-103-36/+45
| | | | | | | we need now. Don't assume that file descriptor can't be 0 (many places) Protect FD_* macros from being used with negative descriptors Shorten MS EXT show help to fit 80 cols
* Add registration help screen.jkh1997-03-091-0/+82
|
* Add a registration screen so we can finally start counting our little userjkh1997-03-0917-29/+76
| | | | puppies.
* cdefs cleanupache1997-03-093-6/+4
|
* I remove pending signals completely, they are not useless, they areache1997-03-096-152/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dangerous! Signal handlers themself must be fixed to not call malloc, but no pended handlers, it will be correct fix. In finite case each signal handler can set some variable which will be analized later, but calling handler functions manually is too dangerous (f.e. signals not blocked while the handler or handlers switch executed in this case). Of course this code can be fixed instead of removing, but it not worth fixing in any case. Should go into 2.2 In addition sig.c code shows following dangerous fragments (there can be more, but I stop after two): This fragment if (fn == SIG_DFL || fn == SIG_IGN) { handler[sig-1] = (sig_type)0; <------------- here signal(sig,fn); } else { cause NULL pointer reference when signal comes "here", but more worse fragment is below: void handle_signals() { int sig; if (caused) for (sig=0; sig<__MAXSIG; sig++, caused>>=1) if (caused&1) (*handler[sig])(sig+1); } caused is bitmask which set corresponding bit on each signal coming. And now imagine, what happens when some signal comes (bit sets) while loop is executed (see caused>>=1 !!!) In this light carrier drop situation was (as gdb shows) 1. SIGSEGV in handle_signals because some junk called as *handler reference. 2. Since SIGSEGV was pended too (== never happens), it can cause various range of disasters.
* Support comments in password database (/etc/master.passwd).wosch1997-03-091-1/+9
| | | | | Comments in group database (/etc/group) are currently not supported - adduser silently delete blank lines and comments.
* Cleaned up some messages, added a check to remove a leftover popd filewosch1997-03-082-50/+227
| | | | | | | | | | from /var/mail, added a routine to delete the removed user's files from /tmp, /var/tmp, & /var/tmp/vi.recover, and added code to kill any running processes owned by the removed user). I've also added a flag for non-interactive execution, cleaned up the man page, and adjusted my address. Submitted by: ghelmer@cs.iastate.edu (Guy Helmer)
* YAMF22jkh1997-03-084-4/+16
|
* Allow comments in password database. The comments are copied fromwosch1997-03-082-4/+26
| | | | | | | | | | | | | the password file into /etc/master.passwd and optional (-p) into /etc/passwd. Enable this feature with the compile option -DPASSWD_IGNORE_COMMENTS. The character `#' introduces a comment. Leading spaces and tabs are ignored: '^[ \t]*#.*\n$' Count an empty line - only spaces, tabs or newline - also as a comment. An empty line at the bottom of /etc/master.passwd is a common novice error and increased my mail load: '^[ \t]*\n$'
* YAMF22jkh1997-03-0810-42/+116
|
* Unpend all signals before execv, it not makes any sense to pend them hereache1997-03-081-2/+2
| | | | Should go into 2.2
* Unpend fault signals like SIGSEGV, etcache1997-03-081-4/+4
| | | | | | It is too dangerous to continue with them in any case Should go into 2.2
* Add a missing docfile (whoops! Overlooked).jkh1997-03-081-0/+19
|
* YAMF22jkh1997-03-083-7/+8
|
* Unpend all killing signals to shut down this thing immediately,ache1997-03-082-9/+9
| | | | | | | or it is impossible to kill it in some situations. Unpend yet one SIGARLM (see timer.c commit) Should go into 2.2
* Don't pend SIGALRM (Timer Service) due toache1997-03-081-3/+3
| | | | | | | | | 1) When carrier dropped, old variant often forget to detect it cause unkillable loop forever (because SIGTERM pended too, but it will be separate commit) 2) Time intervals accuracy reasons Should go into 2.2
* YAMF22jkh1997-03-077-42/+43
|
* Oops, had a couple of extra parens in a couple of lines.mpp1997-03-071-3/+3
|
* Clean this man page up. Don't use hardcoded font escape codes.mpp1997-03-071-47/+50
| | | | Other mdoc cleanup.
* Add a -s option for setting the current vty. This should makebrian1997-03-075-22/+60
| | | | | | | | | life easier if a PS/2 mouse locks up the keyboard (frequent-ish, but not repeatable). Tidy up code (a bit) and make it -Wall Is this a 2.2 candidate ? (although it doesn't -Wall in 2.2 because of the lack of sys/sysproto.h
* Protect against missing initial @cwd. Closes PR#2893jkh1997-03-061-3/+7
| | | | Submitted-By: pius@iago.ienet.com
* Typo fix 'and' -> 'an'.danny1997-03-041-2/+2
| | | | This is a 2.2 candidate.
* Back out MAXLOGNAME fix, Bruce points that copyinstr require NULache1997-03-031-2/+2
|
* An odd merge from 2.2 to -current. Somehow that 2.2 nologin.5mpp1997-03-031-7/+9
| | | | | | man page was in better shape than the 3.0-current version, so I'm committing the 2.2 version to 3.0. Whatever happened, it was my fault :-).
* Fix MAXLOGNAME usage, the code has wrong assumption thatache1997-03-021-3/+3
| | | | it must be NUL terminated
* Add a missing period so that the -n option is display properlympp1997-02-281-2/+2
| | | | | | in the man page output. Closes PR# 2831. Submitted by: Marc Slemko <marcs@znep.com>
* The pccard daemon doesn't support the 'class' parameter as stated in thenate1997-02-261-5/+2
| | | | | | documentation, so remove any hints of it. Submitted by: "Brent J. Nordquist" <bjn@visi.com>
OpenPOWER on IntegriCloud