array of ARG_MAX size. ARG_MAX is currently 256k, which causes a rather
serious stack overflow (kernel stacks are not very large, usually 8k).
Fixes memory corruption problems observed after accessig /proc/1/cmdline
during tests. Problem in my case manifested itself as massive lossage
in ffs_sync(), resulting in a crash, and sometimes, pooched file systems.
XXX This could, and probably should, be rewritten to use a much smaller
temporary buffer, and a loop around uiomove().
when disconnecting etc., how much data were transferred, has changed.
Symptom: SIOP invalid instructions when doing data transfers to disks that
disconnect.
XXX The bits etc. need to be defined correctly in the siopreg.h file, and
symbolic values used.
- use libhack to avoid dragging in YP and DB (saves about 108K of libc
we have no need for).
- use more of the -DSMALL utils from distrib/utils/x_* (saves about 76K)
(except x_gzip, which is actually bigger).
People who want to be able to install files which have been translated
into EBCDIC, or install over XNS, can probably figure out other ways
to get this done.
This means that a boot image again fits on a single 1.44M floppy, with
about 50k to spare.
"netbsd.gz". This speeds the boot by a small but perceptable amount.
The time between when the bootblocks print "no such file or directory"
for netbsd and when they show signs of actually having found netbsd.gz
is long enough to be noticeable, and looks bad..
autoconfiguration time; this can be done better from rc.local.
(For INSTALL kernels, WSDISPLAY_DEFAULTSCREENS can be defined which
sets up that many screens with default parameters.)
Delete "\E)0" sequences and make ":as=\E(0:ae=\E(B:"
(some terminals use "1" for "0").
This change makes it easy to use 8-bit encodings, such as ISO8859, EUC, etc.
PR #7126.
- Don't error out on P_SYSTEM or SZOMB processes; instead, do what ps(1)
would do, i.e. the p_comm in parenthesis.
- Use uvm_io() (or procfs_rwmem() if !UVM) to read the target process's
psstrings and argument vector. Using copyin() is problematic, because
it operates on the current processes! That is, the old code would
always get the `cmdline' of the process reading the file, not that of
the target process.
