change, but I've been testing this on thud and silvia for quite a
while, also I haven't gotten any bug reports from the ports list, so
I'm going to let it loose!
It cleans up this file quite a bit, now I can go in and start adding
some more "interesting" things.... ;)
calls.
Found by: gcc -Wstrict-prototypes after I supplied some of the 5000+
missing prototypes. Now I have 9000+ lines of warnings and errors
about bogus conversions of function pointers.
Note that conf.c, although there was an import conflict, it did not
require intervention, as it was the $Id$ tag. It would have become
rev 1.8 on checkout so there's no point changing it from 1.7 to
1.1.1.3 as the "-j" option wanted to do.. Trust me.. :-)
page. I tried all three modes (rwhod, rwhod -m, rwhod -m 32) on a machine
with 2 ethernet interfaces and they all worked.
Submitted by: Bill Fenner <fenner@parc.xerox.com>
Note, I tested this on a NEC Versa, IBM 750C, and a IBM 755CX w/out
problems. The card still works fine in TP mode.
Submitted by: schwarz@alpharel.com (Steve Schwarz)
Reviewed by: jleppek@suw2k.ess.harris.com (James Leppek)
oo
Turns out, it's pretty important if you use PAX for backup. In the man
page for PAX, there is an error (OK, we could call it a "potentially
catastrophic incompleteness"). It reads:
> The command:
>
> pax -r -v -f filename
>
> gives the verbose table of contents for an archive stored in filename.
Yup, it does do that. With a side effect: it also _replaces_ all the
files that come in from the archive. As is my custom, I did my
backup-validation real soon after the backup was written. Precisely
because I've seen the same sort of thing happen on other systems. So all
that file-restoring didn't do a lot of damage. Probably helped my
fragmentation somewhat (aha, an online defragger?) It did confuse one
hapless user, who lost an email message he _knew_ he hadn't deleted.
Apparently the system restored the file as of just before that critical
message came in.
The correct entry should read:
> The command:
>
> pax -v -f filename
>
> gives the verbose table of contents for an archive stored in filename.
Submitted by: John Beckett <jbeckett@southern.edu> via the BSDI mailing list
Remove some rare-used semigraphics from VT100 entry, it really helps many
not-fully compatible emulators and don't degradate original vt100 much.
Add VT200 keys set to VT100 k1-k4, it not affects original VT100 since no one
program tests keys presense, but helps emulators to work
1: It stops invalid files being created in the cvs tree
2: It stops the import from aborting without mailing a commit message..
The first is simple, it opens the file for reading before touching the
repository, and the second catches the pieces when it hits an unreadable
file rather than just aborting mid-way through, leaving the repository in
a bit mess.
Reviewed by: rgrimes
actually a timeout only. The existing behaviour caused a
mcd0: timeout getreply
at halt/reboot time.
Submitted by: graichen@sirius.physik.fu-berlin.de (Thomas Graichen)
/usr/include/ufs/ufs/quota (#include <ufs/ufs/quota.h>) that seems to work
ok though.
Closes PR # docs/670: quotactl man page incorr...
Submitted by: evans@scnc.k12.mi.us (Jeffrey Evans)
traps occurred. This also helps ddb backtrace through trap frames.
Backtracing through syscall and interrupt frames still doesn't work
but it is relatively unimportant and more expensive to fix.
ISA GAT mode and hidden refresh seem to cause reliability problems
on Saturn based systems and are now reported when booting with '-v'.
Submitted by: Danny J. Zerkel <dzerkel@feephi.phofarm.com>
Fix for PR #510. The original problem was that __ivaliduser() was
failing to grant access to a machine listed in a +@netgroup specified
in /etc/hosts.equiv, even though the host being checked was most
certainly in the +@netgroup.
The /etc/hosts.equiv file in question looked like this:
localhost
+@netgroup
The reason for the failure was had to do with gethostbyaddr(). Inside
the __ivaliduser() routine, we need to do a gethostbyaddr() in order
to get back the actual name of the host we're trying to validate since
we're only passed its IP address. The hostname returned by gethostbyaddr()
is later passed as an argument to innetgr(). The problem is that
__icheckhost() later does a gethostbyname() of its own, which clobbers
the buffer returned by gethostbyaddr().
The fix is just to copy the hostname into a private buffer and use
_that_ as the 'host' argument that gets passed to innetgr().
And here I was crawling all over the innetgr() code thinking the
problem was there. *sigh*
Anthony Yee-Hang Chan <yeehang@netcom.com>
Bill Fenner <fenner@parc.xerox.com>
Brian Tao <taob@gate.sinica.edu.tw>
Chris Stenton <jacs@gnome.co.uk>
Chuck Robey <chuckr@Glue.umd.edu>
Cornelis van der Laan <nils@guru.ims.uni-stuttgart.de>
Craig Struble <cstruble@vt.edu>
Dave Chapeskie <dchapes@ale.zeus.leitch.com>
Don Whiteside <dwhite@anshar.shadow.net>
Eric L. Hernes <erich@lodgenet.com>
Frank Nobis <fn@trinity.radio-do.de>
Janusz Kokot <janek@gaja.ipan.lublin.pl>
Javier Martin Rueda <jmrueda@diatel.upm.es>
Josh MacDonald <jmacd@uclink.berkeley.edu>
Lucas James <Lucas.James@ldjpc.apana.org.au>
Marc Ramirez <mrami@mramirez.sy.yale.edu
Marc van Kempen <wmbfmk@urc.tue.nl>
Michael Smith <msmith@atrad.adelaide.edu.au>
NIIMI Satoshi <sa2c@and.or.jp>
Nobuyuki Koganemaru <kogane@kces.koganemaru.co.jp>
Peter Wemm <peter@haywire.DIALix.COM>
Philippe Charnier <charnier@lirmm.fr>
Rob Snow <rsnow@txdirect.net>
Richard Stallman <rms@gnu.ai.mit.edu>
Thomas Gellekum <thomas@ghpc8.ihf.rwth-aachen.de>
Tom Samplonius <tom@misery.sdf.com>
Torbjorn Granlund <tege@matematik.su.se>
Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
These are the people who appeared in the "Submitted by:" lines of the
commit messages that I still have in my mail archive. Since they are
my commit messages, most of them are porters and port bug-fixers.
You will probably notice at least one major "celebrity" in there. Yes
you're right, that's him, he sent me a patch for emacs (what else? :)
By the way, if you are a committer, now may be a good time to add
yourself to this list by yourself, provided you made at least one
commit before. We don't do that for you, you have to claim credit
for yourself. :)
and graft it into chpass.
Chpass can now tell when it's being asked to operate on an NIS
user and it displayes the appropriate message in the editor
template ("Changing NIS information for foo"). After the changes
have been made, chpass will promte the user for his NIS password.
If the password is correct, the changes are committed to yppasswdd.
Hopefully, this should make NIS more transparent to the end user.
Note that even the superuser needs to know a user's password before
he can change any NIS information (such is the nature of yppasswdd).
Also, changes to the password field are not permitted -- that's what
yppasswd is for. (The superuser may specify a new password, but
again, he needs to know the user's original password before he can
change it.)
'NIS information unchanged' or '/etc/master.passwd unchanged'
depending on which was is being modified (conditional on -DYP).
This is to save me the trouble of writing a whole other error
routine (nis_error()?) for the upcoming changes to passwd and
chpass.
