| Age | Commit message (Collapse) | Author |
|---|
|
|
|
not one changed, we should not exit with an error but zero to indicate
success (matches solaris behaviour).
need to track wether files were skipped because of the -u checks for that
and take that into account later when taking the exit code decision.
ok theo, comments from otto and miod
|
|
directory cannot be written and ~/ed.hup path has to be built up. Also
pay special care that HOME is an absolute path name.
With input by millert.
ok deraadt, millert
|
|
while here, make the description of -m more consistent for mkdir,
mkfifo, and mknod.
add a touch of .Ex for mkdir too.
|
|
from Jacek Masiulaniec, via ray@
ok ray@
|
|
like bash and zsh do. Requested by espie@, OK deraadt@
|
|
ok sobrado
|
|
|
|
a single time before we print anything, if needed. Uses a flag to
specify which formats need the kernel info donlist() provides.
OK deraadt@
|
|
I got fooled by patch(1). Sorry.
|
|
but only do the final popfile call after yyparse() is done.
This also fixes config reload on SIGHUP for some daemons.
Spotted by otto@. OK deraadt@
|
|
|
|
policies since mkdir(2) will be called for each directory in the path,
even things like / or /usr. We now use a hybrid approach uses stat(2)
until either we find something missing or we reach that last component.
Then we switch to calling mkdir(). Tested by bernd@ and chl@
|
|
|
|
ok krw@
|
|
|
|
of date for ever (no ksh builtins), and since we have two shells, pointing
to one page or the other is never going to work; so remove MLINKS for
csh(1); the cd(1) and wait(1) pages (also builtins); and update any trailing
Xr's;
please, there are tools like whence, man, and locate for finding this stuff;
ok deraadt miod
|
|
race condition in mkdir -p that may lead to an erroneous successful exit status.
reported by Ralf Wildenhues <Ralf.Wildenhues at gmx.de>
fix based on a suggested patch by Bruno Carnazzi <bcarnazzi at gmail.com>,
largely inspired by NetBSD mkdir()s implementation
looks OK otto@ OK millert@
|
|
OK otto@
|
|
as close as we can get given that it's used unsigned. Matches
recent change to scp.c, prompted by djm@
|
|
"warning: field width is not type int"
"looks good" otto@
|
|
from otto@
prompted by otto@ who is aftk for now
|
|
from tobias@
ok millert@ tobias@
|
|
sys/dev/pci/pciide.c from naddy@
|
|
sys/netinet/in_pcb.c and sys/net/bridgestp.c ok henning@
sys/dev/pci/bktr/* ok jakemsr@
|
|
|
|
it with a simple filter in the yylex() loop.
The compression in lgetc() didn't happen for quoted strings,
thus creating a regression when tabs were used in variables.
Some testing by todd@ and pyr@
OK deraadt@
|
|
ok millert@
|
|
ok gilles@ millert@
From Tim van der Molen <tbvdm.lists at xs4all.nl>
|
|
ok ray@ gilles@
|
|
|
|
- tidy up SEE ALSO
|
|
ok beck
|
|
ok beck
|
|
showing the names of signals, it may also convert the exit status of
commands terminated by signals to their names. flesh out the description
of -l accordingly.
issue spotted by
|
|
from Nicholas Marriott, ok otto
|
|
tested by deraadt@ on a gcc2 arch
looks ok ray@ ok deraadt@
|
|
ok jmc@
|
|
Requested and OK deraadt@
|
|
expand to space or tab, and a \ followed by newline should be ignored
(as a line continuation). compatible with the needs of hoststated
(which has the most strict quoted string requirements), and ifstated
(where one commonly does line continuations in strings).
pointed out by mpf, discussed with pyr
|
|
|
|
yylex implementation and the code which interacts with yylex. this also
brings the future potential for include support to all of the parsers.
in the future please do not silly modifications to one of these files
without checking if you are de-unifying the code.
checked by developers in all these areas.
|
|
as found in hoststated, and make all the code diff as clean as possible. a
few issues remain mostly surrounding include support, which will likely be
added to more of the grammers soon.
ok norby pyr, others
|
|
|
|
ok millert@
|
|
cp(1) and ln(1) must have a synopsis consistent with mkdir(1),
mv(1), rmdir(1) and others
ok jmc@, millert@, otto@
|
|
|
|
of ip addresses and such. this change is being pushed into all the pfctl
derived parsers, starting with the easy ones. chio does not yet use
the NUMBER token, but may one day. ok krw
|
|
based on a diff from debian: see their bug#296446. ok millert@
sobrado@
|
|
and the ERR trap won't get called at all. ok millert@
|
