and then all the other fields. (I.e, like -D except with the name
first instead of last).
Consistenly strsvis(3) encode path names (even for -C and -D).
- -f, which allows to restrict edquota to only one quota-enabled filesystem
- -s and -h, which allows to set soft and hard limits respectively, without
the need to edit a file.
This fixes the problem that pkg_add(1) drops setuid/setgid bit.
This problem occurs on pax(1) based tar environment.
pkgtools/pkg_install should be fixed, too.
stay in no-longer existing dir and continue with removal of db-files;
otherwise, the packages contents would be removed, but the package not
uninstalled. Pointed out by Grant in PR pkg/18384. OK'd by hubertf.
for config_time.h) that contains, for example:
/* Sun Nov 17 05:37:51 2002 GMT */
#define CONFIG_TIME 1037511471
#define CONFIG_YEAR 2002
#define CONFIG_MONTH 11
#define CONFIG_DATE 17
#define CONFIG_HOUR 5
#define CONFIG_MINS 37
#define CONFIG_SECS 51
These values represent the current time as of when config was last
run, so that functions (eg, inittodr()) can use these values instead
of being updated once every year or so with the "current" time.
The associated modification to Makefile.kern.inc makes config_time.h
depend on this depend on this and the kernel Makefile, so that
granularity of kernel builds is not reduced.
means that the appropriate combination of checking for KERNEL_BUILD,
RELEASEDIR, DESTDIR, and/or BSD_PKG_MK, can allow the setting of COPTS
or CFLAGS (or anything else) depending on the specific task at hand.
Personally, I think that per-kernel install rules are the best part.
party software packages to the kernel. The statment:
package "../path/to/some/directory/files.package"
is equivalent to the sequence:
prefix "../path/to/some/directory"
include "files.package"
prefix
conversion constant.
Remove flags
-c Create IBSS: use ifconfig wi0 mediaopt adhoc, which turns on the
802.11-compliant behavior
-e enable WEP: use ifconfig wi0 nwkey ...
-f set channel: use ifconfig wi0 chan ch
-k set WEP keys: use ifconfig wi0 nwkey ...
-n set desired SSID to join in IBSS mode: use ifconfig wi0 nwid id
-p set the desired port type: use ifconfig wi0 mediaopt ...
-q set SSID to create: use ifconfig wi0 nwid ...
-t set TX rate: ifconfig wi0 media ...
-A set authentication type: ifconfig wi0 nwkey ...
-S set maximum sleep interval: ifconfig wi0 powersavesleep ...
-P enable power management: ifconfig wi0 powersave
-T select WEP key for transmitted packets: ifconfig wi0 nwkey n:k1,k2,k3,k4
-Z unimplemented
which duplicate ifconfig functions. This leaves flags
-a access point density
-o print out statistics counters
-s set station name for Lucent WaveMANAGER software
-M enable/disable "microwave oven robustness"
-R enable/disable roaming function
which affect wi(4)-specific parameters, and flags
-D scan once for access points
-d maximum data length
-m set MAC address
-r set RTS/CTS threshold
which affect 802.11-standard parameters and activities (so may not
belong in wiconfig, in the long-term). The new flag, -g, also
affects an 802.11 parameter.
"*************" rather than a single asterisk - it's just as difficult
to hash to the longer password since the asterisk character itself is
not in its alphabet, and pwd_mkdb now thinks it's a valid DES password.
On both my 4000/60 and SIMH, a boot program NOT loaded at 0 consistently
is loaded +0x5200 too high in memory, which which causes a fatal trap back
into the console even before the self-relocating code can run. "wHATEver."
"iostat -x" now shows these (ala linux/solaris), but this is only splitting
the read/write bytes/transactions, not adding any new metrics. "systat
iostat" now has two new commands to switch between combined/separate mode
for both it's numbers & bar modes.
- all command executions now use the path [execvp/execlp/system].
- normalize the macro names as <COMMAND>_CMD.
- in some OS's full pathnames for commands can still be provided, but this
is not the default.
This was needed to fix -DTAR_FULLPATHNAME="/usr/bin/tar"
allowing for the following:
file foo.c foobar | bar
defflag BAR
device foobar
...to be expressed in the following (more natural) way:
define foo
file foo.c foo
defflag BAR: foo
device foobar: foo
allows for the following:
define foo
define bar { }: foo
device foobar: bar
An instance of "foobar" will select "bar", which will in turn select
"foo" due to "bar"'s dependency on "foo".
Circular dependencies are not allowed, and a dependency may also not
be an interface attribute.
instead, rely upon libnbcompat to provide a workaround (which returns
an error if the target is a symlink).
Should fix another MacOS X build issue due to missing lchown(2).
that HAVE_STRUCT_STAT_ST_FLAGS implies this.
- Set HAVE_LCHFLAGS for native builds
- Clean up {CLEAR,SET,CHANGE}FLAGS macros, and only provide if
HAVE_STRUCT_STAT_ST_FLAGS is set.
(Fixes compilation as a tool on MacOS X, noted by Allen Briggs.)
now carries the name of the attachment (e.g. "tlp_pci" or "audio"),
and cfattach structures are registered at boot time on a per-driver
basis. The cfdriver and cfattach pointers are cached in the device
structure when attached.
can be a variable length field, so check the (fixed length) password
length, rather then the length of the whole password+salt+cipher.
Use a cipher type of "$2a" for blowfish.
password types, and their associated lengths, and check in useradd or
usermod whether the given encrypted password has the correct length.
This removes the (duplicated) hardcoded lengths which had crept in
with the last commit, and also checks the length of the given password
against the expected length.
a vector of indices into the cfdata table to specify potential parents,
record the interface attributes that devices have and add a new "parent
spec" structure which lists the iattr, as well as optionally listing
specific parent device instances.
See:
http://mail-index.netbsd.org/tech-kern/2002/09/25/0014.html
...for a detailed description.
While here, const poison some things, as suggested by Matt Thomas.
jmmv