> Think of the fdisk partition as a way to mark off a part of the disk for
> OpenBSD. It should generally be one contiguous block. The beginning of
> *the* OpenBSD partition holds the disklabel, which is the important part
> for marking off OpenBSD disk (sub?)partitions.
I think it would it be
Thanks Stuart.
> Try "call cpu_reset".
That made the machine reboot cleanly. Afterwards, dmesg and
dmesg.boot had captured both the 6.3 boot and the 6.3 reboot, but the
ddb session in between was missing. Is there a ddb command that
flushes the session log to the message buffer?
> Or take
Dear list
My old Dell laptop ran stably under 6.1. After I upgraded to 6.2,
the kernel started to crash with "page fault trap, code=0" every
time I started the X server. Every other time, this left the file
system in a state that fsck could not repair. I don't have a spare
laptop for
It turns out that the snapshot on Aarnet failed to match its checksum
for a blindingly obvious reason. It was corrupt.
I installed a snapshot from another mirror, started X, and crashed the
kernel. I'll try to post the details to bugs@ in a day or two, but
some hand holding would be
Thanks Stuart
> Better to test sooner, if it still fails, if you can get a good report
> written up there's still some chance of a fix before release.
The machine is a cheap Dell laptop that's about 10 years old. It's
possible that an innocent change in the software triggered a latent
hardware
Thanks for the replies. I suspect this is the answer I needed: don't
try to install a 6.2 snapshot just before version 6.3 is released,
instead wait for the release and install that.
> You need to be sure to use the bsd.rd from the snapshot!
I'm pretty sure that's what I booted. Does any other
bsd downloaded but failed its checksum test.
Possibly the answer is to ignore the checksums, but I want to ask first.
Rodney Polkinghorne
7 matches
Mail list logo
