Subject: port-sun3/1726: [dM] (sun3) ufsboot gives no second chances
To: None <email@example.com>
From: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
Date: 11/03/1995 21:29:42
>Synopsis: [dM] (sun3) ufsboot gives no second chances
>Responsible: gnats-admin (GNATS administrator)
>Arrival-Date: Fri Nov 3 21:50:02 1995
>Originator: der Mouse
>Release: 1.1_ALPHA, sup of Nov 2 AM
Machine is Sun-3/150, disk is:
vmes0 at mainbus0
si0 at vmes0 addr 0xff200000 level 2 vector 0x40
scsibus0 at si0
si0 targ 0 lun 0: <SEAGATE, ST15230N, 0498> SCSI2 0/direct fixed
sd0 at scsibus0: 4095MB, 3992 cyl, 19 head, 110 sec, 512 bytes/sec
though I suspect it has nothing to do with the details of the
disk, and possibly isn't even sun3-specific.
If you once give a nonexistent filename to ufsboot, all further
attempts produce a confusing and unhelpful failure, a failure
that shouldn't be happening at all.
>b nebtsd -s
Boot: sd(0,0,0)nebtsd -s
>> NetBSD ufsboot [$Revision: 1.2 $]
boot: nebtsd: No such file or directory
boot: netbsd: Unknown error: code 24
All further attempts produce the same "Unknown error: code 24",
regardless of whether they exist or not, as far as I can tell.
Upon resetting at this point with the back panel switch,
though, booting with
>b netbsd -s
works fine; it's not anything wrong with /netbsd itself.
Unknown. I browsed through ufsboot source and didn't see
anything obvious, but I must admit a certain lack of
understanding of what's going on there.