lpd run in a mode where the it listens only to the local unix domain
socket and not to the network. Changes are similar but not identical
to the supplied patches.
it to "."
- include sockio.h if needed to define SIOCGIFCONF (for svr4)
- use POSIX signals and wait macros
- add -S silent flag, so that the client does not print messages unless there
is something wrong
- use flock or lockf as appropriate
- use fstatfs or fstatvfs to find out if a filesystem is mounted over nfs,
don't depend on the major() = 255 hack; it only works on legacy systems.
- use gzip -cf to make sure that gzip compresses the file even when the file
would expand.
- punt on defining vsnprintf if _IOSTRG is not defined; use sprintf...
To compile sup on systems other than NetBSD, you'll need a copy of daemon.c,
vis.c, vis.h and sys/cdefs.h. Maybe we should keep those in the distribution?
on tech-kern. (See man page.) Implementation by Greg Hudson.
Also, remove special case for i386 in vector handling, although this code isn't
actually used any more.
The problem here is setuid(euid) is used far too much. Since I removed
many of these calls, and added no new ones, I do not think this weakens
security. In fact, it quite likely improves it quite a bit, since
access() is called as the real userid, and the file is opened for printing
as the real userid rather than the (setuid-root) effective one.
map. SunOS ypservers maps place the host name in the key and the val,
but HP-UX and NetBSD ypservers maps place the hostname only in the
key, leaving the val empty. Since there is no clear standard for this map,
best to play it safe.
there are some PC/Mac oriented devices that use non-standard speeds,
furthermore that's just not the way we do things anymore.
"Bad" baud rates are no longer caught with their own error message,
but the condition will still be diagnosed when the tcsetattr() fails.
- check malloc returns
- null terminate strncpy() strings
- use snprintf instead of sprintf
- pass the right arguments to the right functions
- check usage
- use err(3) and warn(3) instead of printfs.
Correct length arg to haddrtoa() in report of duplicate address.
The string value for a generic tag should not include the null.
(Including the null in reponses really annoys HP printers!)
When reading hardware addresses, allow colon separators
(only works if the whole H/W address is in quotes).
Also, change `.Os 4.2' => `.Os 4.4' (this man page is from 4.4 lite), and
for now, refer to the "BSD 4.3 Line printer manual", because that is what
we now have in lpr/SMM.doc (SMM.doc needs updating too).
believe that's been missing for so long!)
While I'm here, remove all of the non-hp300 cruft. The hp300 port is the
only thing that uses config.old(8) now'a'days. Yes, this is a little
embarassing.
by Mike Grupenhoff <kashmir@umiacs.umd.edu> in PR #2485.
While I'm here, do some long-overdue cleanup, including function prototypes,
and update for modern libkvm interfaces.
ypbind; sleep 10; ypwhich
to fail (where failure is defined as ypwhich hangs until it gives up,
complaining about not being able to communicate with ypbind). Failure
mode pointed out by Chris G. Demetriou <cgd@cs.cmu.edu>.
of NFS packets over TCP. Upgrade to 3.0.4 while at it. 3.0.4 fixes previous
fix made to util.c too; 'official' fix applied instead (very minor difference).
Fixes to be sent to maintainers RSN.
- new fbio.h in arch/amiga/include, defining only FBIOSVIDEO
- add an IOCTL translation to arch/amiga/dev/grf.c
- add screenblank to the list of specials to build on amiga.
Update the documentation of the vnode flags so that it lists only (and all)
of the flags understood by the program. (The documentation is likely in need
of more cleanup.)
'out' arg to svc_sendreply must point to a long if outproc is
xdr_long. It was pointing to an 'int', and that was crashing on the
alpha, due to bad alignment.
some machines (because on those (64-bit) machines, -1L is
0xffffffffffffffff, but a u_int32_t will never be sign extended).
Compare to 0xffffffff; that's what was really meant, anyway.
machines (Alpha). fixed sized types, not 'timeval's should go over
the net, and the stuff that goes over the net can't necessarily be
passed directly to functions that expect timevals.
order to match the function prototype and to work with compilers that
default to unsigned chars.
Compare the getopt() return value with -1 instead of EOF.
order to match the function prototype and to work with compilers that
default to unsigned chars.
Compare the getopt() return value with -1 instead of EOF.
in XXX-marked comments in the recent attachment changes), this was a
long-standing bug in config.
The problem: If a device is attached to a device via an attribute exported
by that device (i.e. foo* at bar0, where 'bar' exports an attribute that
'foo' attaches to), but the device attached to is not present in the
kernel configuration file, AND another device which exports an attribute
that 'foo' attaches to _is_ present (e.g. a device baz0, if one could
specify 'foo0 at baz0'), then: the configuration file will (incorrectly)
be accepted by config, and the resulting ioconf.c will include a bogus
cfdata entry for the device (in the example, 'foo*'). This typically
causes the resulting kernel to crash during autoconfiguration.
The solution: Be much more careful about keeping track of where a device
was attached, and, in particular, if a device was attached to another device,
_always_ keep track of what device it was attached to. Then, when
cross-checking, if the attached-to device isn't present, give up and do not
check attributes. Also, document the process much more thoroughly.
used for checking device attachment names as are used for device name
checking, because device names can be used as attachment names. (Actually,
less strict rules could be used, but there's little point in that.) This
was not a mistake of design, this was just a mistake; i misunderstood
the devbase name checking code.
right/consistent. If you had something like:
file file.c foo bar baz needs-flag
and any one of foo, bar, or baz caused it to be brought into the compile,
in the header you'd end up with:
#define NFOO 1
#define NBAR 1
#define NBAZ 1
even if only one of them were selected. Other headers might have had a
different (inconsistent) set of definitions, depending on whether any of
their components were included, and any files necessary for the unspecified
options would not actually be present in the Makefile files list. The
correct behaviour for the example above if only 'foo' is selected by
the config file is:
#define NFOO 1
#define NBAR 0
#define NBAZ 0
which is what config now does. This bug has been present for a while.
(I don't know for sure that it was present in 4.4-Lite2, but from looking
at the Lite2 config sources, it appears to be there.)
- split softc size and match/attach out from cfdriver into
a new struct cfattach.
- new "attach" directive for files.*. May specify the name of
the cfattach structure, so that devices may be easily attached
to parents with different autoconfiguration semantics.
lists to not have a newline properly emitted. (It was emitting a
newline only if the line position was != 7. However, the only time the
line position was 7 was right after the initial variable assignment
string (e.g. "OBJS=\t") was printed.)
This fix is a kludge:
- make the nfs filehandle conditional on v2 and v3
- set the nfs_args fields for the version and the
file handle size.
- make the file handle pointer type void * so that
it works on both nfsv2 and nfsv3
- fix the mountd rpc results parsing.
A proper fix should:
- register an nfsv3 server for amd.
- make amd try v2/v3 mounts exactly like mount_nfs does.
- understand the nfsv3 mount options.
- cleanup the #undef's in the protocol header.
Also in order to auto-recognize v2 vs v3, I moved the inclusion of
<sys/mount.h> to am.h.
Darren Reed <darrenr@vitruvius.arbld.unimelb.edu.au> in PR #1227.
This change is slightly different than the one submitted by Darren in
that the DIRECTED_BROADCAST compile-time option will behave like it used
to so that existing configurations utilizing it won't have to change.
ghudson