From owner-freebsd-current Thu Jan 28 19:01:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05518 for freebsd-current-outgoing; Thu, 28 Jan 1999 19:01:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05508 for ; Thu, 28 Jan 1999 19:01:18 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA27559; Thu, 28 Jan 1999 18:55:57 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdp27553; Fri Jan 29 02:55:47 1999 Date: Thu, 28 Jan 1999 18:55:42 -0800 (PST) From: Julian Elischer To: IdiotSwitch Editor cc: current@FreeBSD.ORG Subject: Re: Ideas? In-Reply-To: <001e01be4a68$1f4ac2c0$1900000a@chopper.my.intranet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Jan 1999, IdiotSwitch Editor wrote: > I can't code, so I wouldn't know how to implement these. Or even if it's > possible. > > Parallel device loading. I know that freebsd's boot sequence can continue > loading new devices while waiting for other devices to respond with irq's > and whatnot. However, could this be taken a step further and have multiple > devices actually searched in parallel? Things such as network cards could > be scanned for at the same time as harddisks. Would that save time? I know > harddisks (IDE ones anyway) take a little while to respond. Already being worked on.. > > The other thing I notice is that fsck, when it runs only does one disk at a > given time. I can see only doing one partition of a disk at a time (for > obvious reasons), but would it not be possible to run it on say wd0 and wd2 > at the same time? Yeah.. I know, shut down properly and I won't have that > problem :) Thing is, various things have crashed my system twice, and > that's the most annoying part. fsck already does this in some cases.. (read the man page for full details I guess) > > Anyhow. Like I said. I can't do it myself, but leave it up to you to > consider the importance and possibly implementation strategy. good try. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message