Linux Kernel Mailing List wrote:
> Author: Ingo Molnar <[email protected]>
>
> x86 defconfig: increase CONFIG_LOG_BUF_SHIFT
>
> Impact: double the defconfig printk buffer
>
> Booting defconfigs produces more output than 128K so the output is
> truncated - double it to 256K.
>
> Signed-off-by: Ingo Molnar <[email protected]>
> ---
> arch/x86/configs/i386_defconfig | 2 +-
> arch/x86/configs/x86_64_defconfig | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Would someone attempt to explain the current purpose of defconfig files,
please?
thanks,
--
~Randy
On Sun 2008-12-28 17:39:45, Randy Dunlap wrote:
> Linux Kernel Mailing List wrote:
> > Author: Ingo Molnar <[email protected]>
> >
> > x86 defconfig: increase CONFIG_LOG_BUF_SHIFT
> >
> > Impact: double the defconfig printk buffer
> >
> > Booting defconfigs produces more output than 128K so the output is
> > truncated - double it to 256K.
> >
> > Signed-off-by: Ingo Molnar <[email protected]>
> > ---
> > arch/x86/configs/i386_defconfig | 2 +-
> > arch/x86/configs/x86_64_defconfig | 2 +-
> > 2 files changed, 2 insertions(+), 2 deletions(-)
>
>
> Would someone attempt to explain the current purpose of defconfig files,
> please?
For machines like spitz (handheld with 64MB ram, arm, and mostly fixed
configuration) defconfig is very useful. Its basically impossible to
get all the stuff right so that it boots and finds root, otherwise...
For generic PC... well something like distro's config is still nice
starting point, but...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html