new kernel => which linux now?

mjt <mjtobler DeleteThis @removethis_mail.ru> wrote in message news:<i82Gc.5606$oD3.1273@newsread1.news.pas.earthlink.net>...
> Doru-Catalin Togea wrote:
>
> > If I compile and run the latest 2.6 kernel, will I still run FC1?
>
> ... Linux is the *kernel*, Linux/GNU is the kernel
> with the base utilities. a distro is Linux/GNU and
> a bunch of other stuff thrown in.
>
> to answer your question directly: yes
> .

So, that means if I have RedHat 6.0 with Kernel 2.2.17 (or 2.2.26),
can I compile and install kernel 2.6.n ?

Regards

Marco A. Cruz Quevedo

Marco A. Cruz Q. wrote:
> mjt <mjtobler.TakeThisOut@removethis_mail.ru> wrote in message news:<i82Gc.5606$oD3.1273@newsread1.news.pas.earthlink.net>...
>
>>Doru-Catalin Togea wrote:
>>
>>
>>>If I compile and run the latest 2.6 kernel, will I still run FC1?
>>
>>... Linux is the *kernel*, Linux/GNU is the kernel
>>with the base utilities. a distro is Linux/GNU and
>>a bunch of other stuff thrown in.
>>
>>to answer your question directly: yes
>>.
>
>
> So, that means if I have RedHat 6.0 with Kernel 2.2.17 (or 2.2.26),
> can I compile and install kernel 2.6.n ?
>
> Regards
>
> Marco A. Cruz Quevedo

Yes.

nl

Nick LaBrie wrote:
> Marco A. Cruz Q. wrote:
....
>> So, that means if I have RedHat 6.0 with Kernel 2.2.17 (or 2.2.26),
>> can I compile and install kernel 2.6.n ?
>>
>> Regards
>>
>> Marco A. Cruz Quevedo
>
>
> Yes.
>

With MUCH pain and anguish.. Yes. The time you would spend
on this probably costs more than purchasing/downloading a
newer dist. RH 6.0 is just too old, too bug ridden, too
insecure, etc.. I'm not saying you can't "compile"
the kernel, but actually ending up with a runable system
would be a amazing feat.

People who answer "Yes" need to prove that they've
actually done the deed. My guess is that they have
not.... and I can't really blame them.

So.. my best answer (for 99% of the cases) would be NO
to upgrading to a 2.6 kernel for a RH 6.0 user.

Chris Cox <ccox_nopenotthis.DeleteThis@airmail.net> wrote in message news:<cceiqf$u6q@library2.airnews.net>...
> Nick LaBrie wrote:
> > Marco A. Cruz Q. wrote:
> ...
> >> So, that means if I have RedHat 6.0 with Kernel 2.2.17 (or 2.2.26),
> >> can I compile and install kernel 2.6.n ?
> >>
> >> Regards
> >>
> >> Marco A. Cruz Quevedo
> >
> >
> > Yes.
> >
>
> With MUCH pain and anguish.. Yes. The time you would spend
> on this probably costs more than purchasing/downloading a
> newer dist. RH 6.0 is just too old, too bug ridden, too
> insecure, etc.. I'm not saying you can't "compile"
> the kernel, but actually ending up with a runable system
> would be a amazing feat.
>
> People who answer "Yes" need to prove that they've
> actually done the deed. My guess is that they have
> not.... and I can't really blame them.
>
> So.. my best answer (for 99% of the cases) would be NO
> to upgrading to a 2.6 kernel for a RH 6.0 user.

Thanks for the advise, but i have not had any problem when upgraded
from 2.2.5 to 2.2.17 but I have this problem:

Recently I downloaded the last kernel (2.2.26) and recompiled with the
well known commands:
make mrproper
copy ~/.config .config (restored the previous kernel configuration
file)
make menuconfig
make depend
make bzImage
make modules
make modules_install
make install (*)

The same steps were performed when upgraded from 2.2.5 to 2.2.17 and
there were no problems, but now the kernel does not boot. The system
freezes before executing runlevel 3 (the default). If at this stage, I
press ctrl-alt-del, the system reboots and now it starts up!

1. What is missing?
2. What is wrong?
3. The same happened when I patched the kernel from 2.17 to 2.18

(*) I have not found any reference about this command, but without it,
the new kernel is not installed. why?

Thanks in advance

Marco A. Cruz Quevedo

Chris Cox wrote:
> Nick LaBrie wrote:
>
>> Marco A. Cruz Q. wrote:
>
> ...
>
>>> So, that means if I have RedHat 6.0 with Kernel 2.2.17 (or 2.2.26),
>>> can I compile and install kernel 2.6.n ?
>>>
>>> Regards
>>>
>>> Marco A. Cruz Quevedo
>>
>>
>>
>> Yes.
>>
>
> With MUCH pain and anguish.. Yes. The time you would spend
> on this probably costs more than purchasing/downloading a
> newer dist. RH 6.0 is just too old, too bug ridden, too
> insecure, etc.. I'm not saying you can't "compile"
> the kernel, but actually ending up with a runable system
> would be a amazing feat.
>
> People who answer "Yes" need to prove that they've
> actually done the deed. My guess is that they have
> not.... and I can't really blame them.
>
> So.. my best answer (for 99% of the cases) would be NO
> to upgrading to a 2.6 kernel for a RH 6.0 user.
>

I certainly haven't done it. With my "Yes" answer, I simply meant that
yes, it CAN be done.

Now, WHY anyone would want to do that is another question, for the exact
reason you pointed out

nl

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.setup Marco A. Cruz Q. <macruzq RemoveThis @todito.com> suggested:
> Chris Cox <ccox_nopenotthis RemoveThis @airmail.net> wrote in message news:<cceiqf$u6q@library2.airnews.net>...
>> Nick LaBrie wrote:
>> > Marco A. Cruz Q. wrote:
[..]
> Thanks for the advise, but i have not had any problem when upgraded
> from 2.2.5 to 2.2.17 but I have this problem:

> Recently I downloaded the last kernel (2.2.26) and recompiled with the
> well known commands:
> make mrproper
> copy ~/.config .config (restored the previous kernel configuration
> file)
> make menuconfig

Use 'make oldconfig' at this point instead of 'make menuconfig'
and always check Documentation/Changes if your system meets
anything needed.

[..]

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo zvpunry RemoveThis @urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFA65pGAkPEju3Se5QRAjLPAKCf6KZYtnpBSIo3iuXXfF0K6YfRCQCgzBi2
TY0s5uGmzZ7gcJ2JO3qDHOg=
=Dcpr
-----END PGP SIGNATURE-----

macruzq DeleteThis @todito.com (Marco A. Cruz Q.) writes:

]Chris Cox <ccox_nopenotthis DeleteThis @airmail.net> wrote in message news:<cceiqf$u6q@library2.airnews.net>...
]> Nick LaBrie wrote:
]> > Marco A. Cruz Q. wrote:
]> ...
]> >> So, that means if I have RedHat 6.0 with Kernel 2.2.17 (or 2.2.26),
]> >> can I compile and install kernel 2.6.n ?
]> >>
]> >> Regards
]> >>
]> >> Marco A. Cruz Quevedo
]> >
]> >
]> > Yes.
]> >
]>
]> With MUCH pain and anguish.. Yes. The time you would spend
]> on this probably costs more than purchasing/downloading a
]> newer dist. RH 6.0 is just too old, too bug ridden, too
]> insecure, etc.. I'm not saying you can't "compile"
]> the kernel, but actually ending up with a runable system
]> would be a amazing feat.
]>
]> People who answer "Yes" need to prove that they've
]> actually done the deed. My guess is that they have
]> not.... and I can't really blame them.
]>
]> So.. my best answer (for 99% of the cases) would be NO
]> to upgrading to a 2.6 kernel for a RH 6.0 user.

]Thanks for the advise, but i have not had any problem when upgraded
]from 2.2.5 to 2.2.17 but I have this problem:

The 2.2.17 is the "same" kernel as 2.2.5-- ie it is simply a modification
of it-- bug fixes, small changes. 2.6 is an entirely different kernel tree,
a complete rewrite of 2.4 which was a rewrite of 2.2.


]Recently I downloaded the last kernel (2.2.26) and recompiled with the
]well known commands:
] make mrproper
] copy ~/.config .config (restored the previous kernel configuration
]file)
] make menuconfig
] make depend
] make bzImage
] make modules
] make modules_install
] make install (*)

]The same steps were performed when upgraded from 2.2.5 to 2.2.17 and
]there were no problems, but now the kernel does not boot. The system
]freezes before executing runlevel 3 (the default). If at this stage, I
]press ctrl-alt-del, the system reboots and now it starts up!

]1. What is missing?

And how would we know? Really we are not mind readers.
Exactly where does it halt? What is on the screen when it freezes,...

]2. What is wrong?

You did not properly intialise the costwarty, and as a result, the
intabluator loops, ignoring the setting in the scwerrt file.

]3. The same happened when I patched the kernel from 2.17 to 2.18

](*) I have not found any reference about this command, but without it,
]the new kernel is not installed. why?

Because that is the command which installs the kernel.
]Thanks in advance

]Marco A. Cruz Quevedo