linux-kernel - Re: [patch] MTD: fix DOC2000/2001/2001PLUS build error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.63.0702080011160.2981@qynat.qvtvafvgr.pbz>
Date:	Thu, 8 Feb 2007 00:18:11 -0800 (PST)
From:	David Lang <david.lang@...italinsight.com>
To:	Mark Lord <lkml@....ca>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	David Woodhouse <dwmw2@...radead.org>,
	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [patch] MTD: fix DOC2000/2001/2001PLUS build error

On Tue, 6 Feb 2007, Mark Lord wrote:

> I'm with Linus 100% here.
>
> It's really irritating to upgrade to a newer kernel,
> using the same old .config file, and then discover that
> my MythTV box no longer auto-boots to record programs.
>
> The reason being, that /proc/acpi/alarm no longer exists,
> and the kernel option to configure it has mysteriously
> disappeared from the menus.
>
> After an hour of hand examining and grep'ing Kconfig files,
> I eventually find the secret little totally-unrelated option
> that has to be selected to make the ACPI alarm option visible
> again.
>
> Doh!
>
> That interface is driven entirely backwards.
> The funtionality option should always be visible,
> and should "select" (or hey, invent a better mechanism,
> I'm not fussy), the underlying crap required to let me use it.

I've been compiling and deploying kernels since 0.99 days, and I still get bit 
by this sort of thing. This is one of the reasons why I've liked the minimal 
config option that Rob Landley has proposed a few times wher eyou specify the 
things that you need and let the build system put in the nessasary dependancies.

I started out useing menuconfig, used the TCL based xconfig, but went back to 
menuconfig when the new xconfig came out (I now do most of my kernel compiles on 
remote machines that I may or may not have X access to anyway)

especially if a particular driver/feature doesn't want to compile, tracking down 
how to turn it off can be a pain. The idea that Alan posted of saying 'disabling 
this function will disable the following things as well' would be an extremely 
useful enhancement.

I think that there are more of us out here that configure and compile kernels, 
but aren't kernel hackers then most people (especialy the distros) want to 
admit. (and for that matter, many of the distro support policies activly 
discourage people from telling the distro when they compile a kernel)

David Lang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/