From owner-freebsd-current Thu Jan 28 18:46:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03834 for freebsd-current-outgoing; Thu, 28 Jan 1999 18:46:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA03821 for ; Thu, 28 Jan 1999 18:46:16 -0800 (PST) (envelope-from idiotswitch@beer.com) Received: from chopper ([207.164.233.119]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id WAA00211 for ; Thu, 28 Jan 1999 22:55:42 -0500 Message-ID: <001e01be4a68$1f4ac2c0$1900000a@chopper.my.intranet> Reply-To: "IdiotSwitch Editor" From: "IdiotSwitch Editor" To: Subject: Ideas? Date: Wed, 27 Jan 1999 21:44:18 -0500 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.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. 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. Anyhow. Like I said. I can't do it myself, but leave it up to you to consider the importance and possibly implementation strategy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message