From: ny6p01@gmail.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] SOLVED - Mouse does not work with kernel-3.5.0
Date: Sun, 29 Jul 2012 20:00:28 -0700 [thread overview]
Message-ID: <20120730030028.GA9572@badass.gateway.2wire.net> (raw)
In-Reply-To: <201207290141.33359.peter@humphrey.ukfsn.org>
On Sun, Jul 29, 2012 at 01:41:33AM +0100, Peter Humphrey wrote:
> On Saturday 28 July 2012 21:19:44 Alan McKinnon wrote:
>
> > I use both:
>
> Me too (sorry), though I find myself using oldconfig more often than
> menuconfig these days, unless I want to comb right through the config
> looking for things I could improve.
>
> > first oldconfig to find the newly added stuff...then menuconfig, mostly
> > looking for driver pages that have lots of things set - I can't
> > possibly have all of that hardware so logically few things must be
> > set. menuconfig also lets me easily see things I hve never explicitly
> > set (which oldconfig can't do) and labels them (NEW) which is
> > distinctly different to what oldconfig calls new stuff
>
> Is it really? I thought they ought to be the same. And the only snag
> with menuconfig for finding new options is that you have to navigate every
> single menu - quite time-consuming*.
>
> > And in menuconfig, the / key engages search, just like in vim
>
> Ah. I knew about the ? key since it's in the prompt. Seems I can drop
> the shift. Ta.
>
> * Speaking of consuming time, would someone with an i7 please tell me
> how long it takes to compile a new kernel? I'd like to compare it with
> my i5, which after mrproper and copying the .config in from /boot, where
> I store it for safe keeping, was 2 min 7 sec just now. (This is related
> to another thread; perhaps I should have asked this there instead.)
Just by way of comparison, my Centrino laptop does it in about an hour flat.
Terry
next prev parent reply other threads:[~2012-07-30 3:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 9:30 [gentoo-user] Mouse does not work with kernel-3.5.0 v_2e
2012-07-26 9:36 ` Neil Bothwick
2012-07-26 9:55 ` v_2e
2012-07-28 6:35 ` Bryan Gardiner
2012-07-28 9:04 ` Dale
2012-07-28 10:22 ` [gentoo-user] SOLVED - " v_2e
2012-07-28 15:24 ` Neil Bothwick
2012-07-28 15:59 ` Pandu Poluan
2012-07-28 16:30 ` Mick
2012-07-28 20:19 ` Alan McKinnon
2012-07-29 0:41 ` Peter Humphrey
2012-07-30 3:00 ` ny6p01 [this message]
2012-07-28 23:14 ` Dale
2012-07-28 22:34 ` ny6p01
2012-07-28 23:14 ` Alan McKinnon
2012-07-28 22:59 ` Dale
2012-07-29 0:45 ` [OT] " Peter Humphrey
2012-07-29 4:54 ` Bryan Gardiner
2012-07-28 9:48 ` [gentoo-user] " v_2e
2012-07-28 10:24 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120730030028.GA9572@badass.gateway.2wire.net \
--to=ny6p01@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox