From owner-freebsd-current Tue Jan 5 08:12:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01249 for freebsd-current-outgoing; Tue, 5 Jan 1999 08:12:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01223 for ; Tue, 5 Jan 1999 08:12:28 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id KAA03361; Tue, 5 Jan 1999 10:11:20 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id KAA03357; Tue, 5 Jan 1999 10:11:19 -0600 (CST) Message-ID: <00d001be38c6$200aeea0$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Alfred Perlstein" , "Blaz Zupan" Cc: Subject: Re: Kernel cannot mount root with new bootblocks Date: Tue, 5 Jan 1999 10:11:58 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In light of all the boot problems I have seen, are there still plans to go ELF Kernel tomorrow? I think you will see that people are going to take a wait and see aproach with CURRENT if this happens. Tom Veldhouse veldy@visi.com -----Original Message----- From: Alfred Perlstein To: Blaz Zupan Cc: freebsd-current@FreeBSD.ORG Date: Tuesday, January 05, 1999 10:08 AM Subject: Re: Kernel cannot mount root with new bootblocks > >On Tue, 5 Jan 1999, Blaz Zupan wrote: > >> Here is my setup. I have two SCSI disks connected to an Adaptec 2940, the >> first is a Quantum 540MB (SCSI ID 0), containing Windows 95, the second >> is a NEC 1.5GB (SCSI ID 1) containing FreeBSD: > >[snip] > >> This is -current as of yesterday, with the latest boot code (installed >> with "disklabel -B da1" and empty /boot/boot.conf). FreeBSD disk was >> originally installed dangerously dedicated. >> >> Suggestions on how to fix this will be much appreciated. > >If someone else doesn't have a better solution you can try wiring the scsi >devices down, look in LINT for this, a really bad hack is defining the: >"kernel on XXX" line. > >good luck, >-Alfred > > > >> Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz >> Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message