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.
Note that this is pretty light at the moment.. It's been gutted to remove
references to older features no longer in the driver.
Curses-based port monitoring is intended for the future.. :-)
Obtained from: Andy Rutter, <andy@acronym.co.uk>
moved to the driver proper, so that <machine/si.h> can be #included by user
programs without needing to include stuff from /sys/i386/isa..
Various (now) redundant features removed, eg: the locks on IXANY and HWFLOW
as these are now done with the "initial" and "lock" termios devices.
Note that it still (for reasons unknown) appears to be masking data to
7-bit with ppp - hence the cleanup to support the debugging via 'sicontrol'
Add a section on /etc/sysconfig and the new configuration scheme
Corrections from Brad Midgley and David O'Brien (from the lists).
Formatting changes for the ASCII version.
Change about Motif from SWiM to Lasermoon.
The FreeBSD goal section needs more meat, Jordan :-)
This was originally ported to BSDI by Andy Rutter <andy@acronym.co.uk>.
At the end of the day, this code has very little in common with Andy's
version, or the Specialix SYSV version. Essentially it has been gradually
and almost completely rewritten, with LOTS of advice and inspiration from
Bruce Evans. There are a couple of missing bits still, but they are minor.
The user-mode "sicontrol" program is in sad shape and will come in soon.
Transparent printing died a timely death.. Maybe later..
Jeremy Rolls @ Specialix (Development directory) has confirmed this is OK
to distribute, and Andy personally sent me his version that I started from.
Although this driver stood up to a nasty stress-test in this form, I am not
confident that there are no nasty bugs lurking.
People are welcome to try it, but dont go out and buy one just yet.. :-)
And *DONT* use it on a mission-critical machine... This is ALPHA QUALITY!
