chroot specify dir to chroot to for GUEST and CHROOT users, to
override -a anondir or the user's homedir.
homedir specify dir to change to upon login; also used for ~ expansion
and $HOME for subprocesses)
both of these can take % escapes: %u (username), %d (homedir), %c (class).
* fix NLST to take a pathname not a STRING, so that ~ expansion works
* modify CWD to use the homedir parsed from curclass.homedir
* implement format_path(dst, src), to parse src expanding % escapes (see above)
into dst.
* rename format_file() to display_file()
bootblock revision strings, use bootbock_name[] (i.e. "NetBSD/sun3")
in initial bootblock messages instead of just "NetBSD"
while here, do sligh Makefile cleanup to share more code between them and also
to make buildable on NetBSD 1.4.1 (my test compile system)
get rid of the XX define hack for netboot & ufsboot, build xxboot.c as
part of libsa - previos main() was renamed to xxboot_main(), main()
is now in respective conf.c files and calls xxboot_main() with
appropriate name of boot block type
XXX I had no chance to actually test the resulting bootblocks, but the
changes were fairly streightforward and should no influence functionality of
boot code
between it and hostname:username is optional as well (some software relies
in this); while here, covert to use sscanf() instead of explicit parse code,
sprinkle some comments
dumpit(): change so that the price is total price for this entry, instead of
beeing price per copy
Addresses bin/9996 by Brian Stark, though the implementation differs from
patch code attached to it.
been around since 386BSD-0.1 import; they have been present in 4.4BSD-Lite
at least, can't currently check if even in 4.3BSD
put note aboud eventual removing of compatibility formats to NOTES, it's
hardly a bug description
- Fix the number of colmuns left for proc. args. Previously, an effect of
NUL was canceled implicitly, but now we must handle it explicitly.
- Fix the width for tty name.
this could result in garbage being written to the PCI status register,
which is unlikely to have had a serious effect. This was with us from
an #if 0 added in rev 1.6.
matt