RE: .config

[Scott Stone <SStone@example.com>]

only thing I was saying, is that Redhat, and TL, at least back when I was
directly involved, would ship you a /usr/src/linux/arch/i386/defconfig that
matched the configuration that was used to build the running kernel that you
boot with by default.

-----------------------------------------------------
Scott M. Stone <sstone@example.com>
Senior Technical Consultant - UNIX and Networking
Taos, the Sysadmin Company - Santa Clara, CA


-----Original Message-----
From: Stephen J. Turnbull [mailto:turnbull@example.com]
Sent: Thursday, August 16, 2001 6:38 PM
To: Scott Stone
Cc: 'tlug@example.com'
Subject: RE: .config


>>>>> "Scott" == Scott Stone <SStone@example.com> writes:

    Scott> Now that doesn't guarantee that those settings are the ones
    Scott> that Mandrake

Mandrake?  Buwhahahahaha.  Mandrake is "special."

Anyway, I don't get this "correct" thing.  Lots of drivers in the
stock kernels can be left out, other things may need to be included.
This is especially true for the firewalling and masquerading stuff.

And built-in/modularize settings surely will be toggled depending on
the distro's philosophy---but even that can mess you up, especially
for install kernels (which often get installed as the everyday kernel,
eg, Debian does this---it ensures that the drivers you needed to boot
and install the system eg UDMA are available post-install).

-- 
University of Tsukuba                Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences       Tel/fax: +81 (298) 53-5091
_________________  _________________  _________________  _________________
What are those straight lines for?  "XEmacs rules."