Date: Mon, 26 May 2008 23:39:59 +0200 From: Roland Smith <rsmith@xs4all.nl> To: Andrew Brampton <andrew@bramp.freeserve.co.uk> Cc: Mark Ovens <parish@magichamster.com>, freebsd-questions@freebsd.org Subject: Re: Kernel for Dual Core Message-ID: <20080526213959.GA5952@slackbox.xs4all.nl> In-Reply-To: <045c01c8bf60$13f50710$0a00a8c0@Andrew> References: <483ADEA1.40206@webrz.net> <483AF28F.1080102@magichamster.com> <045c01c8bf60$13f50710$0a00a8c0@Andrew>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Mon, May 26, 2008 at 07:41:13PM +0100, Andrew Brampton wrote: > From: "Mark Ovens" <parish@magichamster.com> > >> The advantage of building a custom kernel is that you remove anything your >> system doesn't have which saves time when booting as the kernel won't be >> probing for devices that it will never find - for example. mine is an >> all-SCSI system so my kernel doesn't have any IDE or floppy devices in it >> - and it makes the kernel smaller (although that isn't really an issue >> these days). > > > With FreeBSD and Linux I don't spend much time customising my kernel incase > I remove a module that I actually need. Does anyone know of a tool which > can probe for your devices and then suggest which modules can safely be > disabled? Either 'dmesg|less' or 'pciconf -lv|less' or 'ls /dev' will show you which drivers are in use. If you see in the pciconf output a line starting with 'none', you have found a device without a driver. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkg7Li8ACgkQEnfvsMMhpyWsUQCgneTupyVUkI3TK21WnaJlPWV/ MI8An22/heVHXi3H5rs9fcXJFZOdGpgd =XNrQ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080526213959.GA5952>