Date: Tue, 13 Oct 1998 12:20:45 +0200 (CEST) From: Mikael Karpberg <karpen@ocean.campus.luth.se> To: mike@smith.net.au (Mike Smith) Cc: hackers@FreeBSD.ORG Subject: Re: BETA problems... Message-ID: <199810131020.MAA14896@ocean.campus.luth.se> In-Reply-To: <199810130120.SAA01157@dingo.cdrom.com> from Mike Smith at "Oct 12, 98 06:20:39 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
According to Mike Smith: > > At the "boot:" prompt, it would find the kernel at bios unit 1, but for > > some inane reason it fails to recognize that the disk is NOT wd1, but wd2. > > So you would manually have to enter "1:wd(2,a)kernel" or it would assume > > "1:wd(1,a)kernel", and panic when trying to mount root. Why is this, and > > shouldn't it be fixed? > > > > _Is_ it fixed in new boot code, perhaps? > > No. It's almost impossible to get the distinction right. Ick :-( > The difficulty lies in working out which physical drives the BIOS > numbers correspond to. Unless you have a *very* new system, there is > simply no way to know that the BIOS drive 0x81 is in fact wd2. In > order for this to work, the user has to provide the missing data, > either by typing 1:wd(2a)kernel every time (tedious) or putting it in > /boot.config. Well... sysinstall knows you will have this problem since it knows you have a wd2 but not wd1. it seems it would be trivial to make sysinstall put a /kernel.config with that info in it on the root if you put the root on wd2? > Note that you are wrong; the disk is *not* wd1, it's wd2. Check your > kernel config if you don't believe me. Umm... that's what I said: "...that the disk is NOT wd1, but wd2." :-) /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810131020.MAA14896>