[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Please clarify correct sid packages for 2.6.16 and for 2.6.17?



Greg Madden wrote:
On Wed, 12 Jul 2006 08:30:17 -0700
RParr <RParr@TemporalArts.COM> wrote:

Could someone please clarify which is the correct set of Debian sid
packages to install for the following two situations:

1) install/update kernel 2.6.16, headers, etc.

2) install/update kernel 2.6.17, headers, etc.

both including the ability to install/build modules for nvidia, ivtv,
vmware, etc.

I have the following installed and it appears if I just did an
"apt-get dist-upgrade" I would wind up with half staying at 2.6.16
and half being upgraded to 2.6.17.

-------------------------------
ii  linux-headers-2.6-amd64-generic      2.6.16-14
Header files for Linux kernel 2.6 on all x86-64 machines
ii  linux-headers-2.6-amd64-k8           2.6.16-14
Header files for Linux kernel 2.6 on AMD64 K8 machines
ii  linux-headers-2.6.16-2               2.6.16-14
Common header files for Linux kernel 2.6.16
ii  linux-headers-2.6.16-2-amd64-generic 2.6.16-14
Header files for Linux kernel 2.6.16 on all x86-64 machi
ii  linux-headers-2.6.16-2-amd64-k8      2.6.16-14
Header files for Linux kernel 2.6.16 on AMD64 K8 machine
ii  linux-image-2.6-amd64-generic        2.6.16-14
Linux kernel 2.6 image on all x86-64 machines
ii  linux-image-2.6-amd64-k8             2.6.16-14
Linux kernel 2.6 image on AMD64 K8 machines
ii  linux-image-2.6.16-2-amd64-generic   2.6.16-14
Linux kernel 2.6.16 image on all x86-64 machines
ii  linux-image-2.6.16-2-amd64-k8        2.6.16-14
Linux kernel 2.6.16 image on AMD64 K8 machines
ii  linux-kernel-headers                 2.6.16.20-6
Linux Kernel Headers for development
ii  linux-patch-debian-2.6.16            2.6.16-14
Debian patches to version 2.6.16 of the Linux kernel
ii  linux-source-2.6.16                  2.6.16-14
Linux kernel source for version 2.6.16 with Debian patch
-------------------------------


If you do 'apt-get -s dist-upgrade' it will do a dry run showing what
it would do without the '-s' option.

Thanks.  That's how I found out it would upgrade HALF my kernel packages
to 2.6.17 and leave the other half back at 2.6.16.

It seems the kernel folks have rearranged the kernel (ie linux-*)
packages to allow moving up to 2.6.17 OR continuing with 2.6.16.  All
the traffic on the kernel list left me a bit confused as to which set of
packages was appropriate to achieve which goal. I posted this question
several days ago to the kernel list but no one answered.

I was hoping someone on this list might know and be willing to share the
secret.

R.Parr, RHCE, Temporal Arts



Reply to: