Andreas Gruenbacher <[EMAIL PROTECTED]> writes:
> The user does a ``make menuconfig'', and expects to see sane defaults.
> What kconfig really does is take the running kernel's configuration
> instead. This is a ad choice; it makes much more sense to take
> arch/$ARCH/defconfig.
IIRC the vanilla
Hi,
On Wed, 19 Jan 2005, Andreas Gruenbacher wrote:
> Okay, more verbose then. On your machine which is running kernel version
> x you build kernel version y. You grab the version y kernel source tree,
> let's say a vendor tree, which has meaningful default configurations in
>
On Wed, 2005-01-19 at 19:18, Roman Zippel wrote:
> Hi,
>
> On Wed, 19 Jan 2005, Andreas Gruenbacher wrote:
>
> > > > A user ran into the following problem: They grab a SuSE kernel-source
> > > > package that is more recent than their running kernel. The tree under
> > > > /usr/src/linux is
Hi,
On Wed, 19 Jan 2005, Andreas Gruenbacher wrote:
> > > A user ran into the following problem: They grab a SuSE kernel-source
> > > package that is more recent than their running kernel. The tree under
> > > /usr/src/linux is unconfigured by default; there is no .config. User
> > > does a
On Tue, 2005-01-18 at 21:15, Roman Zippel wrote:
> Hi,
>
> On Tue, 18 Jan 2005, Andreas Gruenbacher wrote:
>
> > A user ran into the following problem: They grab a SuSE kernel-source
> > package that is more recent than their running kernel. The tree under
> > /usr/src/linux is unconfigured by
On Tue, 2005-01-18 at 21:15, Roman Zippel wrote:
Hi,
On Tue, 18 Jan 2005, Andreas Gruenbacher wrote:
A user ran into the following problem: They grab a SuSE kernel-source
package that is more recent than their running kernel. The tree under
/usr/src/linux is unconfigured by default;
Hi,
On Wed, 19 Jan 2005, Andreas Gruenbacher wrote:
A user ran into the following problem: They grab a SuSE kernel-source
package that is more recent than their running kernel. The tree under
/usr/src/linux is unconfigured by default; there is no .config. User
does a ``make
On Wed, 2005-01-19 at 19:18, Roman Zippel wrote:
Hi,
On Wed, 19 Jan 2005, Andreas Gruenbacher wrote:
A user ran into the following problem: They grab a SuSE kernel-source
package that is more recent than their running kernel. The tree under
/usr/src/linux is unconfigured by
Hi,
On Wed, 19 Jan 2005, Andreas Gruenbacher wrote:
Okay, more verbose then. On your machine which is running kernel version
x you build kernel version y. You grab the version y kernel source tree,
let's say a vendor tree, which has meaningful default configurations in
arch/$ARCH/defconfig.
Andreas Gruenbacher [EMAIL PROTECTED] writes:
The user does a ``make menuconfig'', and expects to see sane defaults.
What kconfig really does is take the running kernel's configuration
instead. This is a ad choice; it makes much more sense to take
arch/$ARCH/defconfig.
IIRC the vanilla
Hi,
On Tue, 18 Jan 2005, Andreas Gruenbacher wrote:
> A user ran into the following problem: They grab a SuSE kernel-source
> package that is more recent than their running kernel. The tree under
> /usr/src/linux is unconfigured by default; there is no .config. User
> does a ``make menuconfig'',
A user ran into the following problem: They grab a SuSE kernel-source
package that is more recent than their running kernel. The tree under
/usr/src/linux is unconfigured by default; there is no .config. User
does a ``make menuconfig'', which gets its default values from
/boot/config-$(uname -r).
A user ran into the following problem: They grab a SuSE kernel-source
package that is more recent than their running kernel. The tree under
/usr/src/linux is unconfigured by default; there is no .config. User
does a ``make menuconfig'', which gets its default values from
/boot/config-$(uname -r).
Hi,
On Tue, 18 Jan 2005, Andreas Gruenbacher wrote:
A user ran into the following problem: They grab a SuSE kernel-source
package that is more recent than their running kernel. The tree under
/usr/src/linux is unconfigured by default; there is no .config. User
does a ``make menuconfig'',
14 matches
Mail list logo
