| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
character comes from a string.
|
| |
|
| |
|
|
|
|
|
| |
- Include init.h in the generated init.c.
- Generate prototypes and put the brace on the next line.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
converting the stat() call to a lstat() call, which will cover the
situation. One can exercise this bug by referring a dangling link with
something like */the-link.
Approved by: re (scottl)
Submitted by: Simon 'corecode' Schubert [corecode fs ei tum de]
Obtained from: NetBSD via DragonFlyBSD (NetBSD rev. 1.51 and DragonFly
rev. 1.6)
MFC After: 3 days
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
|
|
|
|
| |
promised by the Argument List Processing section introduction.
What follows the option in the options list is its long name,
not its argument (as is the case for the -c option). Also
sort references in the SEE ALSO section.
Approved by: re (blanket)
|
|
|
|
|
|
|
|
|
|
| |
benefit of scripts start out as: #!/bin/sh -- # -*- perl -*-
With this fix in place, we can commit a change to kern/imgact_shell.c
so FreeBSD will process the `#!' line in shell-scripts in a more
standard fashion.
PR: 16393
Mentioned on: freebsd-arch
|
|
|
|
|
|
|
|
| |
- Move the description of the ``-c string'' option closer to the option itself.
- Add an ENVIRONMENT section (1)
- Add more .Xr cross references to the SEE ALSO section.
Obtained from: NetBSD (1)
|
|
|
|
|
|
|
| |
This makes the resulting output more aesthetically pleasing in
text-only terminals:
Reviewed by: ru
|
|
|
|
| |
Obtained from: NetBSD
|
|
|
|
| |
Submitted by: mini
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
work as expected when they have a "shebang line" of:
#!/bin/sh -- # -*- perl -*- -p
This specific line is recommended in some perl documentation, and I think
I've seen similar lines in documentation for ruby and python. Those
write-ups expect `sh' to ignore everything after the '--' if the first
thing after the '--' is a '#'. See chapter 19, "The Command-Line Interface"
in 3rd edition of "Programming Perl", for some discussion of why perl
recommends using this line in some circumstances.
The above line does work on solaris, irix and aix (as three data points),
and it used to work on FreeBSD by means of a similar patch to execve().
However, that change to execve() effected *all* shells (which caused
other problems), and that processing was recently removed.
PR: 16393 (the original request to fix the same issue)
Reviewed by: freebsd-current (looking at a slightly different patch)
MFC after: 1 week
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Reviewed by: ru
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
XXX from Tor: "The shell can also go into a similar loop if the child was
killed by signal 127, since the shell would believe the child to have
only stopped (WIFSTOPPED() macro returns nonzero value). Disallowing
signals 127 and 128 will fix that problem." See kern/19402 for details.
PR: bin/66242
Submitted by: tegge
Analysis and testcase by: demon
MFC after: 3 weeks
|
|
|
|
|
|
|
|
| |
instead of just !, this allows one to more easily locate/understand
the section of the manpage in question.
Additional wording correction by: keramida
Reviewed by: keramida
|
|
|
|
|
|
|
|
| |
considered an error according to the Open Group Base Specification.
PR: standards/45738
Submitted by: Matthias Andree <matthias.andree@web.de>
MFC after: 3 days
|
|
|
|
| |
by POSIX.
|
| |
|
| |
|
|
|
|
| |
Approved by: das (mentor)
|
|
|
|
| |
the top-level shell instance, too.
|
|
|
|
| |
OK'ed by: imp, core
|
|
|
|
|
|
|
| |
to strip binaries by specifying it in the STRIPBIN environment
variable honoured by install(1).
MFC after: 3 days
|
|
|
|
| |
Use WARNS?= instead of WARNS=
|
| |
|
|
|
|
|
|
|
| |
a system that has sys_nsig > NSIG (i.e. when libc is upgraded.)
Submitted by: Matt Dillon
Reviewed by: bde
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Only use return value from system call if system call succeeded.
Tested with `make world` and some of my own scripts.
This should be MFCed soon. While /bin/sh is hard to test the fix is
obviously correct and can be assumed not to break something else
(famous last words...).
|
|
|
|
|
|
|
| |
is important if we add new signals later. From DragonflyBSD:
jobs.c:1.4, trap.c:1.3.
Obtained from: DragonflyBSD
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Joe Marcus Clarke <marcus@FreeBSD.ORG>, subshells could lose a
non-zero exit status.
This commit is Joe's proposed patch. Thanks!
I verified that the problem Joe found is fixed and I ran a full world
with this patch.
I don't plan to ever commit language patches to /bin/sh again. It is
a minefield too big to navigate without a full-time committment, which
I am not willing to do on our /bin/sh.
Under normal circumstances I would recommend using NetBSD's sh which
has a lot of language fixes (like the ones what these patches were
about) but unfortunately they had implemented broken signal behaviour
for shellscript containing interactive programs. Similar issues apply
to pdksh which is OpenBSD's sh.
From my perspective bash2 is the only really working bourne sh out
there and that one is GPLed. Oh well.
|
|
|
|
|
|
|
| |
should slightly reduce the number of system calls in critical portions of
the shell, and select a more efficient path through the fdalloc code.
Reviewed by: bde
|
| |
|
|
|
|
|
|
| |
PR: misc/60730
Submitted by: Eugene Grosbein
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sh -e behaviour was incorrect when && and || statements where used in
"if" clauses.
This is the patch submitted by MORI Kouji <mori@tri.asanuma.co.jp>.
It fixes the issue at hand, but sh fixes like this are super-hard to
verify that they don't break anything else. I ran some of my old test
cases and a few big GNU configure scripts that detected mistakes
before, with the previous sh, patched sh and bash. No differences in
behaviour found. MFC recommended after longer than usual time.
Compiles on i386 and sledge.
|
|
|
|
|
|
|
|
| |
when grepping for JOBS. The recent style cleanup replaced the space with
a tab and broke job control detection. Little edits, disastrous consequences.
Submitted by: Peter Edwards <pmedwards@eircom.net>
X-MFC when: in about 5 weeks with the other sh arithmetic fixes.
|
| |
|
|
|
|
| |
Submitted by: Enache Adrian <enache@rdslink.ro>
|
|
|
|
| |
Submitted by: Stefan Farfeleder
|