| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
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?
|
| |
|
|
|
|
|
|
| |
mount two dos partitions with the same name).
Neaten up a dialog box that was encroaching on the right edge.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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. :-(
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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!
|
|
|
|
| |
I just have this feeling... :)
|
| |
|
| |
|
| |
|
|
|
|
| |
Use ^ getpid() to produce better initial state.
|
|
|
|
|
| |
Don't assume that modem descriptor must be >=3 in CloseModem,
just assume it is any valid descriptor >=0
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
puppies.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Comments in group database (/etc/group) are currently not
supported - adduser silently delete blank lines and comments.
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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$'
|
| |
|
|
|
|
| |
Should go into 2.2
|
|
|
|
|
|
| |
It is too dangerous to continue with them in any case
Should go into 2.2
|
| |
|
| |
|
|
|
|
|
|
|
| |
or it is impossible to kill it in some situations.
Unpend yet one SIGARLM (see timer.c commit)
Should go into 2.2
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
| |
Other mdoc cleanup.
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Submitted-By: pius@iago.ienet.com
|
|
|
|
| |
This is a 2.2 candidate.
|
| |
|
|
|
|
|
|
| |
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 :-).
|
|
|
|
| |
it must be NUL terminated
|
|
|
|
|
|
| |
in the man page output. Closes PR# 2831.
Submitted by: Marc Slemko <marcs@znep.com>
|
|
|
|
|
|
| |
documentation, so remove any hints of it.
Submitted by: "Brent J. Nordquist" <bjn@visi.com>
|