Which 2.6.18.1 kernel goes with which Puppy? (solved)
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
Which 2.6.18.1 kernel goes with which Puppy? (solved)
While working-up a set of general directions for the upgrade of glibc version, I have stumbled across this roadblock:
At http://puptrix.org/sources/kernel-2.6.18.1/ there are six different kernels. They are:
linux-2.6.18.1-source-patched_sfs_e2compr_loglevel_via_dpath-216exp-17apr07.tar.bz2
linux-2.6.18.1-source-patched_sfs_log_via.tar.bz2
linux-2.6.18.1-source-patched_sfs_log_via_dpath-pup214.tar.bz2
linux-2.6.18.1-source-patched_sfs_loglevel_via_dpath_ksize-pup216final.tar.bz2
linux-2.6.18.1-source-patched_sfslzma_e2compr_log_via_dpath-pup216exp3.tar.bz2
linux-2.6.18.1-source-patched_sfslzma_loglevel_via_dpath-216exp-9apr07.tar.bz2
Can someone enlighten me, as to which kernel goes to which Puppy?
At http://puptrix.org/sources/kernel-2.6.18.1/ there are six different kernels. They are:
linux-2.6.18.1-source-patched_sfs_e2compr_loglevel_via_dpath-216exp-17apr07.tar.bz2
linux-2.6.18.1-source-patched_sfs_log_via.tar.bz2
linux-2.6.18.1-source-patched_sfs_log_via_dpath-pup214.tar.bz2
linux-2.6.18.1-source-patched_sfs_loglevel_via_dpath_ksize-pup216final.tar.bz2
linux-2.6.18.1-source-patched_sfslzma_e2compr_log_via_dpath-pup216exp3.tar.bz2
linux-2.6.18.1-source-patched_sfslzma_loglevel_via_dpath-216exp-9apr07.tar.bz2
Can someone enlighten me, as to which kernel goes to which Puppy?
Last edited by Sit Heel Speak on Sun 30 Nov 2008, 20:45, edited 1 time in total.
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
My first reaction is: If the name is trustworthy I see flavors 2.14 and 2.16, except the second entry referenced.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
Yes but it isn't that simple. There's Puppy 2.14, then there's TeenPup 2, Rudy Puppy, Lighthouse Puppy 2.15, Puppy-2.14-eXpand-Dofus, EcoPup, Puppy 3.01-retro, Puppy 2.14R, Puppy 2.15, Puppy 2.16, Puppy 2.16CE, and I know I'm leaving out some. I want to know which kernel was used in each of these, plus whatever ones I'm forgetting.
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
well first thought would come to mind is to pick the latest patched version, But they were all uploaded the same date and time, grrr
next I would go with the size, usually larger is better due to the fact of more patches, so that would lead to
http://puptrix.org/sources/kernel-2.6.1 ... p3.tar.bz2
I could be wrong but that the route I would take.
ttuuxxx
next I would go with the size, usually larger is better due to the fact of more patches, so that would lead to
http://puptrix.org/sources/kernel-2.6.1 ... p3.tar.bz2
I could be wrong but that the route I would take.
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
I agree. Gentoo or Sabayon handles the upgrade of glibc gracefully, effortlessly (ha ha ha ha...)...not!alienjeff wrote:...the Achilles' heel of Puppy Linux
On Puppy 4.1 or 4.11 with kernel 2.6.25.16, the upgrade is reasonably straightforward. You just need to static-compile binutils, coreutils, make, tar, and bash before rebooting to a prompt and doing the mount and ldconfig -v. Then you can reboot, shared-compile them all, strip them, boot from a live-CD and copy the new versions over. Tedious, yes, but within my ken. Neither sanitized headers nor clever chroot'ing is necessary.
I'm running into problems with 2.6.18.1 though.
Mainly I'm interested in upgrading TeenPup 2. So, if anyone knows which kernel was used in it, I will just concentrate on upgrading that distro, and everyone else can twist, twist slowly in the --er, I mean, I'll just assume those distros' originators are capable of upgrading without my help. If no one knows which kernel powers TeenPup 2, then I will just have to download all six and figure it out by direct visual examination.
uname -a was the first thing I thought of, but on TeenPup it replies "unknown."
I told you how to find out the correct kernel version to use when compiling glibc -run /lib/libc.so.6 and that will tell you which kernel headers were used to compile glibc with. The version of the kernel which you are running at the time of the compile has nothing to do with comaptibility at all. And your 'updated' glibc has nothing to do with the new kernel you compiled after installing the new glibc. The kernel does not depend on any external headers or libraries.
- john biles
- Posts: 1458
- Joined: Sun 17 Sep 2006, 14:05
- Location: Australia
- Contact:
Hello Sit Heel Speak,
TEENpup has the same Kernel as the regular puppy 2.14 maybe BarryK might have a record of what he used?
I guess with all the experimenting he does it might be hard for even him to answer.
I believe Puppy 2.14 was released in March 07 so the ones marked as April might be able to be ignored for now. I'd also be looking at the 2 not containing the numbers 216 first in your comparison.
TEENpup has the same Kernel as the regular puppy 2.14 maybe BarryK might have a record of what he used?
I guess with all the experimenting he does it might be hard for even him to answer.
I believe Puppy 2.14 was released in March 07 so the ones marked as April might be able to be ignored for now. I'd also be looking at the 2 not containing the numbers 216 first in your comparison.
Legacy OS 2017 has been released.
Re: delete
http://www.murga-linux.com/puppy/viewto ... 3&start=15amigo quoted this
Do have a look at the output from this command:
/lib/libc.so.6
It will tell you which compiler and kernel headers were used to compile your running glibc with. To find out which target was used,
to save the info as a file do this open the console and paste this
/lib/libc.so.6 >libc_info.txt
it will dump the file in root called libc_info.txt
*since ttuuxxx said sorry I removed the line its gone
big_bass
Last edited by big_bass on Tue 02 Dec 2008, 05:11, edited 2 times in total.
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
@Sit Heel Speak
Ecopup uses the standard kernel-2.6.18.1, as used in its base 2.15ce.
Im interested in knowing, what was the "latest" 2.6.18.1 kernel is the most "patched"/"tested". I believe a later ntfs driver was created after this...can this be "patched"?
Is there an kernel-2.6.18.1 "official patches and drivers" thread?
Ecopup uses the standard kernel-2.6.18.1, as used in its base 2.15ce.
Im interested in knowing, what was the "latest" 2.6.18.1 kernel is the most "patched"/"tested". I believe a later ntfs driver was created after this...can this be "patched"?
Is there an kernel-2.6.18.1 "official patches and drivers" thread?
Puppy Linux's [url=http://www.murga-linux.com/puppy/viewtopic.php?p=296352#296352]Mission[/url]
Sorry, my server is down atm!
Sorry, my server is down atm!