| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
comparisions have been made as string comparisions, even in cases
where both operands clearly qualified as integers.
The fix is to make the parser properly analyzing whether an operand is
a valid integer or not.
|
|
|
|
|
|
| |
fix /usr/lib/*.so problems.
Submitted by: davidg
|
|
|
|
| |
first relative path warning was disabled in old case
|
|
|
|
| |
like in csh.c
|
|
|
|
| |
close PR 598
|
|
|
|
| |
errors.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
stream, such as a rsh or vi pipeline.
The error message is:
stty: TIOCGETD: Operation not supported
It's immediately obvious to the knowledgable hacker type, but not
exactly comforting to the user who's not native to unix. It's
especially confusing if there's a stty command in their .cshrc and
it's showing up on rsh output.
(Fixes PR #bin/573)
Submitted by: peter@haywire.dialix.com (Peter Wemm)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
cpio/copyout.c:
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.
pax/pax.h:
Use the system macros for major(), minor() and makedev().
pax already checks _all_ output conversions for overflow. This has the
undesirable effect that failure to convert relatively useless fields
such as st_dev for regular files causes files not to be output. pax
doesn't report exactly which fields couldn't be converted.
tar/create.c:
Don't output a file if the major or minor its rdev would be truncated.
Print a message about the skipped files to stderr and report the error
in the exit status.
tar/tar.c:
For not immediately fatal errors, exit with status 1, not the error count
(mod 256).
All:
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).
|
|
|
|
|
| |
in initial directory.
Obtained from: idea from NetBSD
|
|
|
|
|
|
| |
which /bin/ls
.//bin/ls
Obtained from: NetBSD
|
|
|
|
|
| |
sensing TCSADRAIN/TCSAFLUSH
Obtained from: NetBSD
|
|
|
|
|
|
|
|
|
|
| |
documented and is incompatible with gnu cp. It has very few good effects
(it recovers some disk space) and many bad ones:
- special files are unlinked after certain errors.
- the data may not be recoverable if the source is a special file or fifo.
- unlinking destroys the target attributes as well as the target data.
- unlinking doesn't actually remove the target data if the target is multiply
linked.
|
| |
|
|
|
|
| |
Reviewed by: phk
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
There is a bug in sh: the built in command "fc -l" generates
a core dump (*NULL in not_fcnumber).
According to the sh manual page (fc -l [-nr] [first [last]]), fc -l
is a correct sequence (in that case, values are defaulted to -16 and -1)
but fails when first is not given.
|
|
|
|
|
|
|
|
|
| |
and `rtsflow' are the components of `crtscts'. `dtrflow' and `dsrflow' are
new and not yet supported. `dtrflow' may be useful for Cyclades serial
careds, which have h/w support for it and no h/w support for `rtsflow'.
print.c:
Report NTTYDISC in case the line is in this obsolescent state.
|
|
|
|
| |
weren't TIOCSETD'd unless another option changed something.
|
|
|
|
|
|
|
| |
cchars2 not used
can't set or report MIN or TIME == 255
TIOCSETD on wrong fd
PPPDISC is not reported
|
| |
|
|
|
|
| |
was breaking this before has been fixed.
|
| |
|
|
|
|
|
|
| |
with `+'. This breaks tradition and violates Posix 1003.2.
Discoverd by: luigi@labinfo.iet.unipi.it (Luigi Rizzo)
|
|
|
|
| |
fifos.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
/usr/src/bin. Note that some patches are still needed in that directory.
I (Joerg) finished most of Philippe's cleanup. /bin/sh will still
need *allot* of work, however.
Submitted by: charnier@lirmm.fr (Philippe Charnier)
|
|
|
|
| |
just like it was in 1.1.5.
|
|
|
|
| |
Noticed by: Mike Murphy <mrm@Sceard.COM>
|
|
|
|
|
|
|
|
| |
of queuing mails only can be restored by uncommenting a CFLAGS+= line
in the makefile, so sites that _really_ need this (perhaps some huge
mail hubs) can still have it. The majority of FreeBSD boxes is better
served with an immediate delivery (and last time i've been asking on
the list, nobody complained).
|
|
|
|
|
|
| |
Reviewed by:
Submitted by:
Obtained from:
|
|
|
|
| |
Submitted by: "Philippe Charnier" <charnier@lirmm.fr>
|
|
|
|
| |
namespace pollution in <time.h>.
|
| |
|
|
|
|
| |
treat 0xFF as valid character.
|
| |
|
|
|
|
|
| |
domainame has referenced getdomainname(2) instead of getdomainname(3).
bug report docs/137.
|
|
|
|
| |
a substitution range.
|
|
|
|
| |
inside backquotes. Reversed my previous fix.
|
|
|
|
| |
Should solve our problems with edit-pr.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
stat the pathname "" in order to decide that the pathname "/" is
a directory. This caused `cp kernel /' to fail if the kernel has
the POSIX behaviour of not allowing the pathname "" to be an alias
for ".". It presumably also caused `cp /etc/motd /' to fail in
the unlikely event that "." is not stat'able.
Be more careful about concatenating pathnames: don't check that
the pathname fits until prefixes have been discarded (the check
was too strict). Print the final pathname in error messages.
Terminate the target directory name properly for error messages.
Don't add a slash between components if there is already a slash.
|
|
|
|
|
|
| |
Document aliases for the flags.
The formatting of the section describing the flags is poor.
|
|
|
|
|
| |
Convert "" to "." for "cd" and "cd ''". chdir("") is required to fail
on POSIX systems.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix several bugs involving the obsolescent -d and -t options:
-d 0 and -t 0 were ignored
-t -600 was a usage error
-d 'atoi is not suitable for parsing args' and -t duh were not usage errors
Change some error messages to say which call to settimeofday failed.
Restore casts of NULL in function calls.
Finish conversion to using err() instead of perror().
|
|
|
|
|
|
|
| |
in cases where it does not run on a terminal. This is important
e.g. for commands like
env COLUMNS=132 ls -CR | lpr -Psome-wide-printer
|
|
|
|
| |
for secure/bin/ed ...
|
|
|
|
|
| |
so that `ln -fs' works when the source is a symlink pointing to a non-
existent file.
|
|
|
|
|
|
|
|
|
| |
* PATCHES MAGIC LEVEL PATCH THAT GOT US HERE
* -------------------- ----- ----------------------
* CURRENT PATCH LEVEL: 1 00051
* -------------------- ----- ----------------------
*
* 14 Aug 92 David Greenman Fixed NEWVM mempages calculation
|