Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 5 Apr 2002 02:46:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 5 Apr 2002 02:46:31 -0500 Received: from hermine.idb.hist.no ([158.38.50.15]:21004 "HELO hermine.idb.hist.no") by vger.kernel.org with SMTP id ; Fri, 5 Apr 2002 02:46:20 -0500 Message-ID: <3CAD55F7.55C56F96@aitel.hist.no> Date: Fri, 05 Apr 2002 09:44:55 +0200 From: Helge Hafting X-Mailer: Mozilla 4.76 [no] (X11; U; Linux 2.5.7-dj3 i686) X-Accept-Language: no, en, en MIME-Version: 1.0 To: joeja@mindspring.com CC: linux-kernel@vger.kernel.org Subject: Re: faster boots? In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org joeja@mindspring.com wrote: > > Think pre init scripts.... > > no apache was install on this machine, no iptables scripts, etc. > > I'm actually talking about the time from where Linux spits out all this crap about probing irq's, ide drive found with dma etc. That kind of stuff. Compile your own kernel with drivers only for hardware you actually have and use during boot. Omit all other drivers. That gets rid of a lot of probing, and the time from "kernel loaded" to "starting init" gets quite short. Also, some drivers lets you specify irq's etc. on the kernel command line - that may avoid further probing. Drivers for things not needed in the kernel boot process (cdrom, floppy, ethernet, etc.) can be made modular. That avoids time-consuming cd spinup and probing of non-boot devices. The kernel boot is only a few seconds on my office machine. The bios boot is one long delay, the initscripts another. Helge Hafting - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/