On Tue, 25 Feb 1997, KLE wrote:
> Hi,

Hi,
 
> yesterday was a really black monday.
> 
> I copied in RiscOs a large file (8MB).
> Afterwards I copied the SA Kernel 4958
> vi unixfs into the /tmp dir on the RiscBSD
> partition.

Ahh, /tmp? or /var/tmp? if you filled /tmp the default boot scripts clear
it, but /tmp is also where temporary files are stored by processes

> Then I tried to boot and what happened ?
> Some strange errors occured:
> Bad super blocks ...
> Either the copying of the large file or the
> copying of the kernel to RiscBSD via unixfs
> DESTROYED my RiscBSD partition.

Did you kill unixfs when you finished using it?  before booting RiscBSD?
I've heard that not doing so can be harmful, however I'm not sure if
that's true or not.

> When I start bb_riscbsd  it shows
> that 3121 cylinders are used by RiscOS and
> in brackets bb_riscbsd shows (used cylinders 0-3122)
> but if I figure it out I think it should be 3123 
> cyclinders which RISCOS uses. Are I wrong ?

bb-riscbsd gives inclusive values, so it's reporting 3123 cylinders

> The RiscBSD partition starts at 3123.

Yes that's right...

> It's a bit boring to install RiscBSD everyday new!

I can imagine, but if you've got all the sets on disc somewhere it doesn't
take that long (I know these things, I've reinstalled about 4 times,
related to swapping discs etc)

> Any ideas ?

How far through the boot does it get? past the device detection? can you
get into single tasking mode?


Chris Gilbert