On Thu, 11 Mar 2010 08:03:21 -0500
"Walter Dnes" wrote:
> PS, why isn't there a "gzcat" command in Gentoo?
It is "zcat" no g.
On Thu, 11 Mar 2010 08:03:21 -0500, Walter Dnes wrote:
> PS, why isn't there a "gzcat" command in Gentoo?
Because it's called zcat.
--
Neil Bothwick
Marriage is a relationship in which one person
is always right and the other is a husband
signature.asc
Description: PGP signature
On Wed, Mar 10, 2010 at 01:55:30PM +, Mick wrote
> If you had not enabled framebuffer in your old kernel then I can't
> think how it would show up as enabled in your new kernel (as far as I
> know fb is not enabled by default on any kernels that I've ever built)
I'm running textmode console
On Wednesday 10 March 2010 16:19:34 Tanstaafl wrote:
> On 2010-03-10 9:07 AM, Alan McKinnon wrote:
> > The current opinion of the current author of the kernel upgrade
> > guide says what you quoted.
> >
> > It's his opinion, it's what he thinks will work best for the
> > majority of people. It's p
On Wed, Mar 10, 2010 at 8:35 AM, Neil Bothwick wrote:
> No you're not. But it is far easier to miss important changes without
> oldconfig to point them out to you by shoving them in your face.
That's how I use it. I do oldconfig as a kind of "kernel config diff"
and then follow it by menuconfig a
On 2010-03-10 9:35 AM, Neil Bothwick wrote:
> On Wed, 10 Mar 2010 09:27:19 -0500, Tanstaafl wrote:
>> But... my understanding is that, by copying your old .config to the
>> new kernel dir before running make menuconfig, you *are* reusing
>> your old config... I sure hope I'm not reading *that* wron
On Wed, 10 Mar 2010 14:09:25 +, Mick wrote:
> Now, doing that for the first time may be too confusing for someone
> who is not familiar with the process of rolling up their own kernel,
> therefore the handbook has to cater for the lowest common denominator
> and advises to go about it in a lon
On Wed, 10 Mar 2010 09:27:19 -0500, Tanstaafl wrote:
> > I see what you mean about the guide and consider it wrong, especially
> > for an advanced section. You are more likely to run into problems
> > when not reusing your old config that when using make oldconfig.
>
> But... my understanding i
On 2010-03-10 9:09 AM, Neil Bothwick wrote:
> Whatever the guide says, the third part of the kernel version is
> considered the minor revision, anything after that is a patch level.
Gotcha - and I guess I was using those terms in my own way - the guide
didn't use the word major or minor - I just
On 2010-03-10 9:07 AM, Alan McKinnon wrote:
> The current opinion of the current author of the kernel upgrade
> guide says what you quoted.
>
> It's his opinion, it's what he thinks will work best for the
> majority of people. It's probably also the wording that has been
> proven to result in the
On Wednesday 10 March 2010 15:46:03 Tanstaafl wrote:
> On 2010-03-10 8:38 AM, Dale wrote:
> > I use make oldconfig all the time and have only had problems with it
> > once. I would trust make oldconfig looong before I would even think to
> > trust genkernel. I have never got it to work for me.
>
On Wed, 10 Mar 2010 08:56:24 -0500, Tanstaafl wrote:
> > The .30, .31 is the minor kernel version. You shouldn't use oldconfig
> > when going from 2.4 to 2.6 but from 2.6.m to 2.6.n is safe.
>
> Again, not according to the official upgrade guide - it specifically
> uses 2.6.9-r1 to 2.6.9-r2 as
On 10 March 2010 13:56, Tanstaafl wrote:
> On 2010-03-10 8:47 AM, Neil Bothwick wrote:
>> On Wed, 10 Mar 2010 08:22:41 -0500, Tanstaafl wrote:
>>
Today is when running a lilo menu with "production" and "experimental"
kernels saved me. "production" is 2.6.30-r8. "experimental" is
2
On Wednesday 10 March 2010 15:22:41 Tanstaafl wrote:
> On 2010-03-09 8:36 PM, Walter Dnes wrote:
> > Today is when running a lilo menu with "production" and "experimental"
> > kernels saved me. "production" is 2.6.30-r8. "experimental" is
> > 2.6.31-r6 or 2.6.31-r10 (same problems with either one
On 2010-03-10 8:47 AM, Neil Bothwick wrote:
> On Wed, 10 Mar 2010 08:22:41 -0500, Tanstaafl wrote:
>
>>> Today is when running a lilo menu with "production" and "experimental"
>>> kernels saved me. "production" is 2.6.30-r8. "experimental" is
>>> 2.6.31-r6 or 2.6.31-r10 (same problems with eithe
On 10 March 2010 01:36, Walter Dnes wrote:
> Today is when running a lilo menu with "production" and "experimental"
> kernels saved me. "production" is 2.6.30-r8. "experimental" is
> 2.6.31-r6 or 2.6.31-r10 (same problems with either one). I set
> /usr/src/linux to point at 2.6.31-r6 (or 10),
On Wed, 10 Mar 2010 08:22:41 -0500, Tanstaafl wrote:
> > Today is when running a lilo menu with "production" and "experimental"
> > kernels saved me. "production" is 2.6.30-r8. "experimental" is
> > 2.6.31-r6 or 2.6.31-r10 (same problems with either one). I set
> > /usr/src/linux to point at 2.
On 2010-03-10 8:38 AM, Dale wrote:
> I use make oldconfig all the time and have only had problems with it
> once. I would trust make oldconfig looong before I would even think to
> trust genkernel. I have never got it to work for me.
>
> Using make oldconfig should be fine for the OP.
My point
Tanstaafl wrote:
On 2010-03-09 8:36 PM, Walter Dnes wrote:
Today is when running a lilo menu with "production" and "experimental"
kernels saved me. "production" is 2.6.30-r8. "experimental" is
2.6.31-r6 or 2.6.31-r10 (same problems with either one). I set
/usr/src/linux to point at 2.6.31
On 2010-03-09 8:36 PM, Walter Dnes wrote:
> Today is when running a lilo menu with "production" and "experimental"
> kernels saved me. "production" is 2.6.30-r8. "experimental" is
> 2.6.31-r6 or 2.6.31-r10 (same problems with either one). I set
> /usr/src/linux to point at 2.6.31-r6 (or 10), cop
Walter,
I'd advise going back through and running a "make menuconfig" on
2.6.31-r6/10 and verify that everything is in order.
The reason that I say this is that, in the event that your kernel -DID-
revert back to defaults, if you have a non-ext2/3 partition, it isn't going
t recognize it (EXT4, Re
21 matches
Mail list logo