| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
traditional behaviour, and it violates Posix.2.
Fixes PR # bin/880: /bin/sh incorrectly parse...
Fixes also an earlier problem report about the shell not evaluating
loops correctly. (Not files via GNATS.)
Submitted by: nnd@itfs.nsk.su (Nickolay N. Dudorov)
|
|
|
|
| |
sh's builtin/bltin.h.
|
|
|
|
|
| |
was a valid integer. The actual decision between integer and string
is now context-dependant on the operator being used.
|
|
|
|
|
|
| |
noticed on a NetBSD bugs mailing list but this is entirely my own work.
Inspired by: Scott Reynolds <scottr@plexus.com>, for NetBSD
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This means that a script containing:
echo 1
set -v
echo 2
will now produce output, like it does on SYSV machines and other 'proper'
/bin/sh implementations..
This is done by a slight restructure of the input processor allowing it to
read chunks from the file at a time, but process the data by line from the
chunk.
Obtained from: Christos Zoulas for NetBSD. <christos@deshaw.com>
|
| |
|
|
|
|
| |
sense symlink even it is unresolved
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Add setlocale LC_TIME
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
o fix brokeness for 1>&5 redirection, where `5' was an invalid file
descriptor, but no error message has been generated
o fix brokeness for redirect to/from myself case
|
|
|
|
|
|
|
|
|
| |
command and badly needed in sh(1) for everybody who wants to modify
the system-wide limits from inside /etc/rc.
The options are similar to other system's implemantations of this
command, with the FreeBSD additions for -m (memoryuse) and -p (max
processes) that are not available on other systems.
|
|
|
|
| |
Since the broken version went into 2.1, this fix should, too.
|
|
|
|
|
|
|
|
|
| |
`mv foo/ ../..' to `mv foo/ ../../foo/', not to `mv foo/ ../../'. The
latter caused a panic. Before the trailing slash changes in the kernel,
the trailing slashes caused the rename() for this mv to fail earlier, so
there was no panic in 2.0.
Fixes part of PR 760.
|
|
|
|
| |
Pointed out by: bde
|
|
|
|
| |
This also fixes loss of the sticky bit for `mv' across file systems.
|
|
|
|
|
| |
This has been broken since cat's own err() function was sloppily
replaced by the library functions warn() and err().
|
|
|
|
| |
avoid "duplicate definition" warnings.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sh -c [-aCefinuvx] command_string [ command_name [argument ...] ] 1
4.56.3 Options
-c Read commands from the command_string operand. Set the
value of special parameter 0 (see 3.5.2) from the value of
the command_name operand and the positional parameters
($1, $2, etc.) in sequence from the remaining argument
operands.
Pointed out by: Kaleb Keithly (kaleb@x.org)
|
| |
|
|
|
|
| |
unceumbered ed. Remove the superfluous .if (...) / .endif
|
|
|
|
|
| |
will allow the secure/bin/ed directory to be cleaned out and the bin/Makefile
to be cleaned up.
|
| |
|
|
|
|
|
|
|
|
| |
allow more than two tty characters.
David Greenman pointed out that when a process that had been revoked from
it's controlling tty, the "-" sign was detached from any two-character
names.
|
|
|
|
|
|
| |
Also mention sockets in the text for -F.
Partially obtained from the NetBSD commit mail list.
|
|
|
|
|
|
| |
while { sleep 1 & wait; } do echo 1; done
corrupted the job table every 4th iteration.
|
|
|
|
|
|
|
| |
e.g.:
ls |> foo.out
sh now behaves the same as it does under SunOS 4.x for this case.
|
|
|
|
|
|
|
|
|
| |
/usr/sbin/sendmail -f <> dest
rather than
/usr/sbin/sendmail -f dest.
Submitted by: Michael Butler <imb@scgt.oz.au>
Obtained from: Eric Allman <eric@cs.berkeley.edu>
|
|
|
|
|
|
|
| |
rcp and rlogin.
(patch supplied)
Submitted by: John Capo <jc@irbs.com>
|
|
|
|
|
|
|
|
| |
This gives us more room to breath with tty names, especially with drivers
that support large numbers of ports.. eg: specialix and digiboard.
This does not actually change the current tty names, it just allows room
for reporting more characters if the drivers use them.
|
|
|
|
|
|
| |
Apply my \c changes to echo. It should also be noted that this is:
A) going into 2.2, not 2.1
B) a functional no-op unless you actually use it!
|
|
|
|
|
|
| |
When comparing my recent parser change against the ash in 1.1.5.1, i
found that a couple of other problems in the same area has been fixed
there, but not in 2.2. Semicolons and EOF do also delimit words...
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The && and || tokens do also terminate a command, not only the
newline.
While i was at it, disabled trace code by default, it served no good
purpose since it required the use of a debugger anyway to be turned
on. Instead, placed a hint in the Makefile on how to turn it on.
This makes the shell ~ 10 % faster and ~ 4 KB smaller. :)
Pointed out by: jan@physik.TU-Berlin.DE (Jan Riedinger)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
oo
Turns out, it's pretty important if you use PAX for backup. In the man
page for PAX, there is an error (OK, we could call it a "potentially
catastrophic incompleteness"). It reads:
> The command:
>
> pax -r -v -f filename
>
> gives the verbose table of contents for an archive stored in filename.
Yup, it does do that. With a side effect: it also _replaces_ all the
files that come in from the archive. As is my custom, I did my
backup-validation real soon after the backup was written. Precisely
because I've seen the same sort of thing happen on other systems. So all
that file-restoring didn't do a lot of damage. Probably helped my
fragmentation somewhat (aha, an online defragger?) It did confuse one
hapless user, who lost an email message he _knew_ he hadn't deleted.
Apparently the system restored the file as of just before that critical
message came in.
The correct entry should read:
> The command:
>
> pax -v -f filename
>
> gives the verbose table of contents for an archive stored in filename.
Submitted by: John Beckett <jbeckett@southern.edu> via the BSDI mailing list
|
|
|
|
|
|
|
|
| |
cp -PRp source_file destination
Closes PR # bin/689: mv(1) manpage
Submitted by: wosch@cs.tu-berlin.de (Wolfram Schneider)
|
|
|
|
|
|
| |
closing backquote in a `foo` substitution.
Discovered by: Martin Welk <mw@theatre.pandora.sax.de>
|
|
|
|
|
| |
This fix match with what manpage said and other systems csh's do.
Submitted by: Bill Fenner <fenner@parc.xerox.com>
|