the descend can jump several directories down in one hit, eg: when a user
mentions multiple directories on the command line, eg: "cvs diff
sys/i386/isa/snd sys/sys". The problem is that the chdir()s are
pushed/popped to account for this, but the "full path" merely has
the last component chopped off on the way back up. This busts lots
of things when the recursion is backing up more than one directory (such
as in the example). This causes 'cvs diff' to emit bogus Index: lines,
'cvs update' to do really stupid things, 'cvs commit' to record incorrect
pathnames etc. I'm not sure that what I've done is quite correct, there
seems to be a comment that implies some sort of problem with "." vs. ""
equivalence or not, perhaps this is a problem on some other OS's, but
I've not (yet) found any problems. This bug has been present since
at least cvs-1.8.1.
This should fix problems noted by several people including asami and jmg.
This change changes the default handling of linemode so that older and/or
stupider telnet clients can still get wakeup characters like <ESC> and
<CTRL>D to work correctly multiple times on the same line, as in csh
"set filec" operations. It also causes CR and LF characters to be read by
apps in certain terminal modes consistently, as opposed to returning
CR sometimes and LF sometimes, which broke existing apps. The change
was shown to fix the problem demonstrated in the FreeBSD telnet client,
along with the telnet client in Solaris, SCO, Windows '95 & NT, DEC OSF,
NCSA, and others.
A similar change was incorporated in the non-crypto version of telnetd.
This resolves bin/771 and bin/1037.
it can be built via BINFORMAT=elf in the environment. Most likely
some of the directory defines such as STANDARD_EXEC_PREFIX will
change again soon, as we settle on the proper locations for the
various components.
Note, the build still fails when it tries to compile libgcc2.c
using the ELF compiler, unless arrangements have been made for the
compiler to find the ELF assembler instead of the a.out assembler.
but adapted to run within cvs instead of rcs.
The stuff I hacked together didn't strip out "/Attic/" for files
on branches when the HEAD version was cvs rm'ed.
on maintaining contributed software.
The merge from our FreeBSD maintained v1.81 to the author's v2.0
yielded only one small difference (a duplicate inclusion of errno.h
in btreeop/btreeop.c) which for now I will leave alone and submit
back to the author; we'll catch it on the vendor branch in v2.1.
Reviewed by: jdp
The print_nfs.c changes are pretty extensive; this is partially because
LBL did a lot of cleanup and partially because I removed lots of
pointless changes away from the LBL style.
PR: 3371
mostly-Submitted by: Chris Timmons <skynyrd@opus.cts.cwu.edu>
log messages after they've been entered. This is more flexible than
using the editinfo script since it works for all log message types
and doesn't have to deal with trying to run the editor for the user.
The problem is that the verifymsg script can't modify the file like
editinfo can, which makes it useless for cleaning up the message (as is
needed for remote commits etc). This change causes the verifymsg handler
to read back the message after the verify script has run and returned an
"OK" exit code.
(they're currently in src/contrib/ipfilter/ipfilter/ by mistake, if someone
from core would like to delete that directory with three files as I'm not
meant to do that :)
few more memory leaks and cleaned up getopt usage. These were done shortly
after the last one I imported. Very little has changed other than that.
(except for some doc updates)
Obtained from: cyclic.com
When using a local repository that is only written to by CVSup - which
I assume doesn't do the cvs locking protocol - this option might be a
speedup since cvs will not create lock files.
such as within an anoncvs server, or from a CDROM repository.
Cyclic (the cvs maintainers) do not like this approach and have an
alternative read-only system, but that requires a read/write repository to
work (which rules out CDROM).
Obtained from: OpenBSD
controls the RCSINCEXC encironment variable for our rcs version, and
also convert the rest of the checkout enhancements from rcs into cvs's
fast checkout code. (yes, cvs doesn't call 'co' anymore)
We now have fine grained individual keyword expansion control and can
set the keyword to anything the user wants.
Also, a new keyword, $CVSHeader$ comes in from rcs, it's like $Header$
except that it shows the pathname relative to the cvsroot. eg:
$FreeBSD: src/bin/ls/ls.c,v 1.10.2.14 1997/05/17 13:15:45 peter Exp $
^^^^^^^^^^^^^^^^^
The idea for this comes from $XFree86$ which expands like $CVSHeader$.
The "local id" string can be set to expand like Id, Header or CVSHeader.
(Matching support for this is apparently happening in cvsup right now)
This is not complete yet in that it doesn't drive our version of RCS
completely, but it does work fine when you do the appropriate magic.
Obtained from: OpenBSD source tree
"-pg" and gprof(1) instead. FreeBSD does not support plain "-p" or
prof(1).
Plain "-p" is still allowed when just compiling. In the compile
phase, "-p" is identical "-pg". It is used by <bsd.lib.mk> for
building profiled object files.
Change "Found end of tape. Load next tape ..." messages to say
"volume" instead of tape. Running cpio off of /dev/fd0 and having
it say "give me the next tape" is kind of ludicrous.. :-)
and opened the archive file. This allows "cpio -o -O output_file"
to create the output file with the callers proper umask.
Closed PR# 1391
Add setlocale LC_ALL (from ache).
- Fix gross spelling and typographical errors pointed out by Keith Bostic.
- Mention -l, --link is only usable with "-p".
Obtained from: old gnu/usr.bin/cpio v2.3.
stops regular files with unrepresentable rdevs from being rejected
and makes the output independent of unpreservable metadata.
Don't output a file if the major, minor or totality of its rdev would be
truncated. Print a message about the skipped files to stderr but don't
report the error in the exit status. cpio's abysmal error handling doesn't
allow continuing after an error, and the rdev checks had to be misplaced
to avoid the problem of returning an error code from routines that return
void.
Minor numbers are limited to 21 bits in pax's ustar format and to 18
bits in archives created by gnu tar (gnu tar wastes 3 bits for padding).
pax's and cpio's ustar format is incompatible with gnu tar's ustar
format for other reasons (see cpio/README).
Submitted by: bde via old gnu/usr.bin/cpio v2.3.
broken for gdb -k, but the section limits weren't used much in previous
versions of gdb in FreeBSD. Now they are used for backtracing when full
symbols aren't available, and in some other new cases.
This should be fixed properly by someone who knows bfd.
This should be fixed in 2.2.
The .Fx macro was missing 2.1.7.
Add 2.2.5 to both .Os and .Fx. If I'm wrong about the version
number, no big deal - it can be removed later, but I wanted
to be able to get this into 2.2 so that when I'm using a
2.2 system ome months down the line, man pages intended for (what I
think will be the next 2.2 release) will be formatted properly.
Also fix a typo in a comment.
history was lost with FreeBSD-1.x and they were blown away
by the gdb-4.16 merge. I needed this to debug e_exp.S ...
Restored even older code (from 386BSD-0.0) for converting the
FP registers to doubles. floatformat_to_double() and/or
valprint() still don't understand NaNs.
Removed unnecessary #include of obsolete <sys/dir.h> again.
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
--forceentry=TEXT will override any entries contained in the info
file. Second, I made it recognize that "gmp" and "gmp.info" are
the same when looking for whether the info file being installed is
already installed.
info entry. It's a real shame that install-info can't override these.
I'll fix the repository for this (and the readline commit as well) once
this has been fixed properly... Looking at the install-info source gives
me a headache. :-( This should be enough to get the tree to build again.
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.
Kernel Interfaces Manual
This was needed because of a few man pages like keyboard(4)
which caused the header to become unreadable with the longer
description.
This has some (all?) of the DNSSEC key management/distribution mechanism
in place. (The SIG and KEY RR's)
Obtained from: Paul Vixie / ISC / ftp.isc.org
this will make it less likely to misinterpret arrow keys as seperate
keys when running over anything slower than a console.
This has been talked about for a while, I hope it's long enough but not
too long to be annoying.
do it themselves. (Some of these programs actually depended on this
beyond compiling the definition of struct ifinfo!) Also fix up some
other #include messes while we're at it.
as performed by the multicast kernel modifications. However, BSD
already had IPPROTO_ENCAP defined as 98 (RFC 1241 encapsulation).
This changes the use of IPPROTO_ENCAP to IPPROTO_IPIP, which is
the BSD name for IP proto 4.
fully registered.
(This is the second try, the first import ignored .info files but not .info-*
files, for some reason. I'm going to make this consistent.)
Reviewed by: core
Approved for: 2.2
Without this, compiled programs die with FP errors.
This is originally credited to: jlemon@netcom.com (Jonathan Lemon), and
has been forwarded to me by quite a few of people.
(implemented better, admittedly) with a new option, '-S'. If the
maintainers of traceroute (Van?) add a -S option, we will then be in
conflict.
Also added a too-brief description of the option in the man page. Someone
with a better command of English than I at the moment should probably look
over it and rephrase it.
Reviewed by: pst, jkh
#include_next <string.h> wasfailing since the /usr/include directory is
first on FreeBSD, and since it was already past it, it failed some of
the tests.
The symptom was an assembler warning
"GOT relocation burb: `___EXCEPTION_TABLE__' should be global"
followed (sometimes) by a core dump. The fix makes the compiler
generate the correct GOTOFF addressing for that symbol, rather than the
GOT addressing it was emitting before.
Warning: There is still at least one serious bug in the i386 exception
code for PIC. The exception code that is generated clobbers the GOT
register (%ebx) and then tries to use it later. That leads to core
dumps at program execution time. I know where the problem is, but I do
not have a fix for it at this time. Until it is fixed, exceptions will
not work in PIC code. This is a general problem for all i386 platforms;
it is not specific to FreeBSD.
I.e., "cvs -H init" went ahead and initialized the repository, and did
not print out a usage message. Not nice.
Also added the "init" command to the list that comes out when you type
"cvs --help-commands". There is still not a word about it in the manual
page.
Yes, I am sending these fixes to the FSF.
