A preserved package may not be deleted by pkg_delete(1) (unless the -f
option is given), and the preserved capability will be carried into
any binary package. pkg_add(1) will also keep the preserved capability
if it was present in the binary package.
The "preserve" capability can be given to a package by using the
PKG_PRESERVE definition in a package Makefile in pkgsrc.
Ride on the recently-bumped lib/version.h for new functionality.
"0700, modified by umask", to "0777, modified by umask".
This matches the behaviour of mkdir(1) and just about every other command...
This change is useful when running with '-W', where the mode of the
new directory won't be changed to what's specified in the specfile.
(I.e, an UNPRIVED build, with a umask of 022).
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.
