20000716 sparc -current snapshot failed
Erik E. Fair
ffs ${TARGDI
R}
This script has to be run when the kernel is in 'insecure' mode.
The best way is to run this script in single-user mode.
*** Error code 1
Stop.
Why is this in the "make snapshot" script if it requires single-user
mode execution? Is there some way we can make it permissible for vnd
in multiuser mode without compromising security?
Erik <fa...@clock.org>
Bill Sommerfeld
> mode execution?
Because it's required to build the snapshot, since install/boot
filesystem images are part of the snapshot.
> Is there some way we can make it permissible for vnd
> in multiuser mode without compromising security?
yes, but it's a lot of work; you need to write a read-write
"standalone" filesystem library.
one of my long-term goals is to change the build to completely avoid
the need to use vnd and native filesystems for filesystem image
construction during the build.
- Bill
Erik E. Fair
cordon off that script with a target of its own, to be executed
manually after the rest of the automated build is done.
Erik
Bill Sommerfeld
> cordon off that script with a target of its own, to be executed
> manually after the rest of the automated build is done.
*NO*
People building snapshots will forget to do this and produce snapshots
which can't be used to install new systems.
We have enough trouble with sparc install to begin with... why make it
harder?
- Bill
Havard...@runit.sintef.no
> single-user mode execution?
It doesn't. It requires either single-user mode execution *or* a
kernel running with INSECURE defined, which is what I (need to)
do on my snapshot-building hosts.
It is however my humble opinion that the suggestion which the
binstall script spews out in this context is unreasonable, since
it precludes doing "make snapshot" while logged in over the
network (which is what I always do).
- Håvard