| Age | Commit message (Collapse) | Author |
|---|
|
From Sevan Janiyan <venture37 at geeklan dot co dot uk>.
Verified using NetBSD CVS.
|
|
|
|
Fixes a pfctl crash with an anchor name containing
an embedded nul found with the afl fuzzer.
pfctl parse.y patch from and ok deraadt@
|
|
format string, create a temporary message.
OK doug@
|
|
No yyerror() calls needed to be changed.
ok bluhm@
|
|
okay miod@, millert@
|
|
(namespace pollution!) or talking about its opinion on code.
ok krw@
|
|
found by millert@, ok deraadt@
|
|
|
|
|
|
|
|
|
|
no 'c' partition. So don't call opendev(3) with OPENDEV_PART.
ok deraadt@
|
|
allocations fails.
looks right deraadt, krw
ok henning
|
|
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@
|
|
sys/dev/pci/pciide.c from naddy@
|
|
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 beck
|
|
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
|
|
|
|
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
|
|
deraadt, henning
|
|
|
|
marked obsolete since the opendev() behaviour it turned on is now the
default.
'it can go' deraadt@
'no API of mine has ever made it into a standard' downsj@
|
|
nested getopt() calls. ok beck
|
|
|
|
ok deraadt@
|
|
|
|
check it's notion of access, avoiding problems on more tightly
coupled changers if the tape is already ejected - currently
these stupid devices return "Initialization Command Required"
sense codes but there is (as yet) no way to tell userland
that. checking the ACCESS changer flag appears safe in both
cases.
Adds support for "voltag" type for the source for a move, so
you can do "chio move voltag 0003B72 drive 0" to move a tape
with the corresponding bar code.
Documents the above, as well as status -vVa in the man page.
partly from freebsd, man page tweaks by jmc@
ok krw@
|
|
|
|
status command and options -v to request the primary volume tag, -V for
the alternate volume tag. Man page will follow shortly, along with move
support by volume tag.
|
|
|
|
the /etc/chio.conf file.
"You commit, then jmc cleans" deraadt@
|
|
|
|
|
|
|
|
|
|
changer - chio will then attempt to open the /dev/rstX device when doing
a move from a source of drive X, and will attempt to unload the tape.
this avoids issues where pickers madly attempt to grab a busy tape on
completely decoupled libraries, or fail to grab an unloaded tape
on tightly coupled libraries, the extra unload being harmless if the
media has already been ejected.
The mapping between st(4) devices and ch drives is by default a
simple mapping between picker drive X being mapped to /dev/rstX, however
for non-obvious or complicated configurations, we support a /etc/chio.conf
file in which the drives for a changer may have their corresponding
st(4) devices defined individually. chio will use the default
mapping if the /etc/chio.conf file is not present, or does not define
a st(4) device for a changer drive.
(example chio.conf and man page changes to come)
yacc parser for chio.conf written by henning@,
ok henning@, krw@
|
|
|
|
|
|
- move env var stuff to ENVIRONMENT
- clarify "status" description
- sort & simplify commands
ok jmc
|
|
- .An/.Aq for AUTHORS
|
|
suggestions, corrections and ok millert@
|
|
|
|
|
