into the DESTDIR in the beforeinstall rule in src/share/info/Makefile.
Then each info file that gets installed into the dir file using
install-info.
It has struck me that there's going to be a problem bootstrapping
this change, since parts of install will fail until install-info
is installed. Maybe someone who knows best how to deal with this can
fix it.
intelligent enough to take default section and entry names
for the purpose of being able to use it on old texinfo files
in the source tree. This involved very minor modifications and
the new options --defsection and --defentry which behave just like
--section and --entry but ignore their argument if the info file
is annotated with the information. This change should only be
neccesary as long as there are old-style texinfo source in the tree.
This has the effect of making every link a "passthrough" which means the
TCP or UDP port won't be freed after link deletion -- so there could be
eventual port exhaustion if the program were allowed to operate long
enough.
Submitted by: Charles Mott <cmott@srv.net>
to be used to expand things beyond the size of the buffer passed in. Also
do a general cleanup of sprintf -> snprintf as well as strcpy and strncat
safety. Also expand some buffers to allow for the largest possible data
that might be used.
This is a 2.2 candidate. However, it needs to be vetted on -current
since little testing has been done on this due to my lack of PPP on
this machine.
Reviewed by: Jordan Hubbard, Peter Wemm, Guido van Rooij
return EX_TEMPFAIL if the file was already locked. This makes it easier
to distinguish between lock collisions and failures within the command
being executed.
Also, don't complain if the unlink() fails in the cleanup handler. It
doesn't matter anyway, and it obscured the exit status returned from
the command that was executed.
HTML is compliant with the 3.2 DTD.
Sanity preservation and bug prevention - define frequently used
constructs as entities.
What remains to be done is better hypertextification which includes
breaking large documents into managable chunks, and managing links.
There are currently some (easy to avioid) situations that result
in multiple anchors with the same name, or links nested within other
links. :(
