Hi, guys

I have recently download a series of packages from ftp.planetmirror.com
under slackwares 9.1 directory, there's a sub-directory called patches.

tree-view
slackware 9.1/patches/
-/kernels
-/packages { precompiled using kernel
2.4.24}
-/source


Understanding that we use the upgradepkg utility to install the packages,
what would be the best way to update all necessary files including updating
the kernel from 2.4.22 to 2.4.24 or possibly to 2.6.2.

And should I download all sub-directories under the slackware9.1 / patches
directory, one more thing where should I keep the patches directory to
insure proper installation of the files.


Any insight in this matter, would be great?


Edward A.

Edward Ascencio wrote:

> Hi, guys
>
> I have recently download a series of packages from ftp.planetmirror.com
> under slackwares 9.1 directory, there's a sub-directory called patches.
>
> tree-view
> slackware 9.1/patches/
> -/kernels
> -/packages { precompiled using kernel
> 2.4.24}
> -/source
>
>
> Understanding that we use the upgradepkg utility to install the packages,
> what would be the best way to update all necessary files including updating
> the kernel from 2.4.22 to 2.4.24 or possibly to 2.6.2.
>
> And should I download all sub-directories under the slackware9.1 / patches
> directory, one more thing where should I keep the patches directory to
> insure proper installation of the files.
>
>
> Any insight in this matter, would be great?
>
>
> Edward A.

Try http://swaret.org

DB

On Wed, 18 Feb 2004 03:03:42 GMT,
Edward Ascencio <edward.associates@comcast.net> wrote:

> I have recently download a series of packages from ftp.planetmirror.com
>under slackwares 9.1 directory, there's a sub-directory called patches.
>
>tree-view
>slackware 9.1/patches/
> -/kernels
> -/packages { precompiled using kernel
>2.4.24}
> -/source
>
>
>Understanding that we use the upgradepkg utility to install the packages,
>what would be the best way to update all necessary files including updating
>the kernel from 2.4.22 to 2.4.24 or possibly to 2.6.2.


The reason there's a kernels subdirectory under patches is that
Pat released an update to the kernel that shipped with 9.l1 to protect
against a local root exploit.

Since he provides a variety of precompiled kernels in the kernels directory
he updates for them all. You only need one, (probably bare.i) and it merely
fixes the vulnerability, doesn't upgrade your kernel version.

To upgrade your kernel version you would have to apply patches
from kernel.org (or mirror) to the 2.4.22 (iirc) kernel source provided with
9.1 then compile. To jump to 2.6 is more challenging, since I think you
couldn't use "make oldconfig".


>
>And should I download all sub-directories under the slackware9.1 / patches
>directory, one more thing where should I keep the patches directory to
>insure proper installation of the files.

After you downloaded the upgraded kernel you require (see above) you can
download the patches to anwhere you like (to save time make sure you just
download patches for packages you ave installed) and then upgradepkg them.


Hope this helps.

Moss Hart

Moss Hart wrote:

> On Wed, 18 Feb 2004 03:03:42 GMT,
> Edward Ascencio <edward.associates@comcast.net> wrote:
>
>> <snip>
>
> To upgrade your kernel version you would have to apply patches
> from kernel.org (or mirror) to the 2.4.22 (iirc) kernel source provided
> with 9.1 then compile. To jump to 2.6 is more challenging, since I think
> you couldn't use "make oldconfig".
>

I've read somewhere you could use make oldconfig (see link http:/
linuxdevices.com/articles/AT3855888078.html ); would it be something
specific to Slack? (asking because i'm running Slack 9.1 & FC1, and i'm
about to upgrade!).

Thanks!

Paulo

Paulo Roberto Dallan wrote:
>
> I've read somewhere you could use make oldconfig (see link http:/
> linuxdevices.com/articles/AT3855888078.html ); would it be something
> specific to Slack? (asking because i'm running Slack 9.1 & FC1, and i'm
> about to upgrade!).

You can't use "make oldconfig" when making a major kernel change
(2.4.xx to 2.6.x) it won't work.

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.24 SMP i686 (GCC) 3.3.3
Uptime: 44 days, 7:47, 3 users, load average: 0.20, 0.19, 0.2

David wrote:

> Paulo Roberto Dallan wrote:
>>
>> I've read somewhere you could use make oldconfig (see link http:/
>> linuxdevices.com/articles/AT3855888078.html ); would it be something
>> specific to Slack? (asking because i'm running Slack 9.1 & FC1, and i'm
>> about to upgrade!).
>
> You can't use "make oldconfig" when making a major kernel change
> (2.4.xx to 2.6.x) it won't work.
>
ok, sorry, if you tell me i believe you

It is just that i read in the article mentioned above the following:

/To migrate an existing kernel configuration from a Linux distribution based
on the 2.4 kernel to a 2.6-based distribution, copy the file named .config
(located in the main source code directory for your existing Linux kernel
source code) to the directory where your Linux 2.6 kernel source code is
located. For example, to migrate a customized configuration file that you
were using with TimeSys Linux 4.1 (using the 2.4.21 kernel) for the Intel
IQ80315 reference board to TimeSys Linux based on the 2.6 kernel, you would
do the following:
# cd /opt/timesys/linux/4.1/iq80315/src/2.4.21-timesys-4.1/kernel
# cp .config /opt/timesys/linux/5.0/iq80315/src/2.6-timesys-5.0/kernel
# cd /opt/timesys/linux/5.0/iq80315/src/2.6-timesys-5.0/kernel
# make oldconfig
At this point, you will be prompted for a value for all currently undefined
kernel configuration variables. Once you supply values for these variables,
the make oldconfig command will generate an updated kernel configuration
file. You can then simply build the new kernel, or can continue kernel
configuration using a more sophisticated configuration editor such as make
xconfig./

Although the article is generic, he is using his distribution as an example.
Maybe it works there, but not for Slack, as you mentioned.

Ok, will try another way.

Thanks.

Paulo R. Dallan wrote:
> David wrote:
>
>>You can't use "make oldconfig" when making a major kernel change
>>(2.4.xx to 2.6.x) it won't work.
>
> ok, sorry, if you tell me i believe you
>
> Although the article is generic, he is using his distribution as an example.
> Maybe it works there, but not for Slack, as you mentioned.

I've never had much luck when doing it with a major kernel
upgrade (2.0.x to 2.2.x) & (2.2.x to 2.4.x). I could have been
doing something wrong I guess but I finally gave up and configure
the new kernel the first time then do make oldconfig for all of
the new releases of that kernel version.

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.25 SMP i686 (GCC) 3.3.3
Uptime: 1:58, 3 users, load average: 0.28, 0.81, 0.66