| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Reviewed by: anholt (mentor)
Approved by: re (scottl)
|
|
|
|
|
|
| |
until it does.
Approved by: re (dwhite)
|
|
|
|
| |
Approved by: re (blanket manpages)
|
|
|
|
|
| |
Approved by: re (blanket)
OK'ed by: gad
|
|
|
|
|
|
|
|
| |
was a separator character immediately before it. This wasn't likely to
happen in #-lines, but we might as well get it right. Also fix it so
that "" and "" will create a zero-length argument.
Approved by: re (blanket `env')
|
|
|
|
|
| |
Noticed by: Matthew D Fuller
Approved by: re (blanket `env')
|
|
|
|
|
|
|
|
| |
start with a '/', they are more supported (by POSIX and SUSv3) than
filenames which have an '=' in them.
Noticed by: tjr
Approved by: re (blanket `env')
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
apart a string, and supports some text substitutions. This can be
used to provide all the flexibility (and more!) that was lost by recent
changes to how the kernel parses #!-lines in shell scripts.
The '-P' option provides a way to specify an alternate set of directories
to use when searching for the 'utility' program to run. This way you can
be sure what directories are used for that search, without changing the
value of PATH that the user has set. Note that on FreeBSD 6.0, this
option is worthless unless the '-S' option is also used.
Approved by: re (blanket `env')
|
|
|
|
|
|
|
| |
without checking it for an equals-sign. If it starts with a slash, then
it cannot be a request to set the value of a valid environment variable.
Approved by: re (blanket `env')
|
|
|
|
|
|
|
| |
it does not happen until all single-letter options are processed. This will
be important for the -S option, which will be coming soon.
Approved by: re (blanket `env')
|
|
|
|
|
|
|
| |
it is doing, and what order it does them. This will be much more useful as
more options are added.
Approved by: re (blanket `env')
|
|
|
|
| |
Approved by: re
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
| |
Submitted by: Joerg Sonnenberger <joerg@britannica.bec.de>
MFC after: 1 week
|
|
|
|
| |
Discussed with: ru
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
stealing ki_spare[0] to hold a pointer.
|
|
|
|
| |
issues bde pointed out.
|
|
|
|
| |
Approved by: ceri (mentor)
|
|
|
|
|
|
|
|
| |
defined in user's $HOME/.login_conf.
PR: bin/75001
Submitted by: Rostislav Krasny
MFC after: 2 weeks
|
| |
|
| |
|
|
|
|
| |
an initial value.
|
| |
|
|
|
|
| |
an initial value.
|
| |
|
|
|
|
|
|
|
| |
malloc(9) statistics from kernel memory or a kernel coredump, to catch
up with recent changes to adopt per-CPU malloc(9) statistics. The new
routines walk the per-CPU statistics pools and coalesce them for
presentation to the user.
|
|
|
|
|
| |
statistics, not graph and statistical test output. Useful for automated
processing.
|
|
|
|
| |
Noticed by: juli
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
sections, so that users of one can learn about the others easily.
|
|
|
|
| |
Approved by: bms (mentor)
|
|
|
|
|
|
| |
the string. Until now this caused no harm, because the buffer code used
to tack two NULs onto buffers. With the new, soon to come, parsing code
this isn't the case anymore in all cases, so fix this.
|
|
|
|
|
|
| |
Makefile.
Requested by: ru
|
|
|
|
|
|
|
| |
string to the end of the error message. I think we used errx()
there when we really wanted an err().
MFC after: 1 week
|
|
|
|
|
|
| |
this clear by constifying the return value.
Obtained from: DragonFlyBSD
|
|
|
|
|
|
| |
to has always been set to NULL for some time now.
Obtained from: DragonFlyBSD
|
|
|
|
| |
the default shell in the Makefile.
|
| |
|
|
|
|
| |
with %jd.
|
|
|
|
|
|
| |
consistency with the rest of make.
Obtained from: DragonFlyBSD (except for the rename)
|
|
|
|
|
|
|
| |
rename the function to be consistent with the naming scheme in the rest
of make. No functional changes.
Obtained from: DragonFlyBSD (idea and most of shell.h)
|
|
|
|
|
|
| |
the default shell.
Idea from: DragonFlyBSD
|
|
|
|
|
|
| |
before executing the shell. Until now this was done when the default
shell was the ksh. This failed if the default shell was sh or csh and
the user switched to ksh.
|
|
|
|
| |
target.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
set the current shell to DEFSHELL. Put all these specifications into
a list. Add user specified new shells to this list. If the user
just selects one of the already know shells just pick the right one
off the list. This let's one do something like:
# Full specification of the user's shell. This also selects the shell.
.SHELL: name=myshell path=/somewhere/foo echo=loud ...
FOO != bar # use myshell here
.SHELL: name=sh
BAR != baz # use /bin/sh here
.SHELL: name=myshell # no need for full spec here.
# continue to use the user's special shell.
|