27;ve described below: boot single user, leave it ro, tunefs,
then reboot while still ro.
Also, I've seen the sysctl kern.geom.debugflags=16 thing in zfs
tutorials and such, but haven't seen where it's actually necessary. I
think this is outdated and changed circa 8.0.
--
R
ely on amd64 hardware, so you probably aren't going to get people
too excited about fixing it without tracking down the exact problem
and/or sending a patch.
--
Rob Farmer
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailma
team on Linux, which Value has consistently said isn't
happening).
--
Rob Farmer
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
o hear
> what you meant there. Since an operator can use shutdown(8) to initiate the
> same shutdown sequence reboot(8) uses, it wouldn't seems to be a security
> based decision.
Shutdown runs rc.shutdown (stops all rc.d scripts). Also, halt/reboot
have options like -n and -q which ca
le in
"limited" admin groups like operator should be presumed able to
escalate to root. I think operator is allowed to run dump, among other
things. A big Windows security flaw is adding people to "Power Users,"
as if that stops anything beyon
g the way? It is, IMHO, the strangest
thing in your kernel vs. GENERIC, which you said works.
--
Rob Farmer
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-s
refuse to installworld? My date and time are correct (in
> sync).
> Any insight into this error would be GREATLY appreciated.
>
Did you run "adjkerntz -i" to set your timezone in single user? It
starts up with the assumption that your hardware clock is UTC -
depending on where yo
