From owner-freebsd-questions Sun Aug 9 11:19:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07230 for freebsd-questions-outgoing; Sun, 9 Aug 1998 11:19:20 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from jaguar.ir.miami.edu (jaguar.ir.miami.edu [129.171.32.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07222 for ; Sun, 9 Aug 1998 11:19:12 -0700 (PDT) (envelope-from marcus@miami.edu) Received: from jaguar.ir.miami.edu ("port 4290"@jaguar.ir.miami.edu) by jaguar.ir.miami.edu (PMDF V5.1-10 #24029) with SMTP id <0EXF00K6KPJDJE@jaguar.ir.miami.edu> for freebsd-questions@FreeBSD.ORG; Sun, 9 Aug 1998 14:18:49 -0400 (EDT) Date: Sun, 09 Aug 1998 14:18:49 -0400 (EDT) From: "Joe \"Marcus\" Clarke" Subject: Re: FreeBSD boot time In-reply-to: <19980809173836.AAA14205%ha1.rdc1.bc.wave.home.com@cr649276-a.surrey1.bc.wave.home.com> To: Geoff Ludwiczak Cc: freebsd-questions@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rebuilding your kernel will do the trick. The problem exists with the defaul disks that are placed off of your secondary IDE controller. If you don't have any disks off of it, remove them from the kernel config and rebuild. By saying IDE disks exist when they don't, FreeBSD tries to probe for them, and the timeout is pretty long. Only include the disks (cdroms) that you have attached to your controllers. Joe Clarke On Sun, 9 Aug 1998, Geoff Ludwiczak wrote: > Hi, > > I just installed FreeBSD 2.2.7, and I love the Operating System, but it's a > pain starting it up. It takes quite a while to probe my hard drives and > cdrom. Is there any way to fix this by maybe rebuilding the kernel > possibly??? > > Thank you > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message