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. The runnig kernel's configuration may also work > for that kernel source tree, or it may not. How is that more verbose? Please provide an example config that worked under 2.4 but doesn't produce a reasonable result under 2.6. > > So they should first try the 2.6 kernel provided by the distribution and > > then try compiling their own kernel. In this situation it's actually more > > likely that they produce a working kernel with the current behaviour, the > > defconfig is not a guarantee for a working kernel either. > > You assume that the user is already running the kind of kernel he is > trying to produce. Al least to me this assumption seems weird. Why is that weird? bye, Roman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
