in the WPA distribution when building without native crypto.
For hostapd in particular, using crypto_libc.c unconditionally meant that
up until now the program has been pretty much unusable for anything which
requires cryptographic key exchanges. E.g. WPA/WPA2.
Also add support for a range of authentication protocols (EAP) in hostapd
if we're building with native crypto support.
specified using a file name on the running system, while the secondary
bootstrap is specified using a file name relative to the root of the
file systrem in which the installation is being performed.
Inspired by PR 39728 by der Mouse
refers to tgz files or to a directory in which tgz files have already
been extracted, make it an error for the files that should have come
from etc.tgz to be missing. This is intended to prevent users from
accidentally deleting necessary files when they run "postinstall -s
xetc.tgz fix".
Use the absence of .../etc/mtree/set.etc in the extracted directory
as a test for the error case.
- Use lstat instead of stat to find the destination path. we can make a symlink
to a broken symlink this way.
- When calling process to create a link, check if the source is a symlink
instead of trying to remove what the symlink points to!
- Don't create hard links to directories.
XXX: NB. Still sup is broken when used with the delete option. This is because
in the delete pass, it goes and tries to delete all files in the old list
that don't exist in the new list. This is a problem when a directory becomes
a symlink to a hierarchy that contains the same names. Then sup will cross
the symlink and start deleting files and directories from the destination.
This is not easily fixed. Don't use sup with symlink/rsymlink and the delete
option at the same time or *be careful*!
rpcgen offers no mechanism to call it from the rpcgen-created main().
So, use the preprocessor to rename that mymain() and provide another
main() that loads the config file first.
PR bin/12758.
Install so first file installed matches this correct manual page
name.
(Both manual pages are still installed. And only rpc.pcnfsd binary is
installed. So no change.)
So install manual page to architecture sub directory.
And add architecture to the manual page document title.
(Note that ndis(4) is already done that way.)
On netbsd-docs, I was told if it is made machine independent
in the future, we can then revert this change.
(Also add a paragraph break.)
I didn't specifically mention the platforms or what support is needed.
At least someone reading the manpage will have some idea why the tool
is missing from their system.
(Some manual pages mention this in the BUGS section, but I didn't do that.)