Okay. I'm feel like a complete dumbass, but is there a SuSE 2.2.18 kernel out there somewhere? All I can seem to find on ftp.suse.com is 2.2.16. Thanks... Ken
I'm using a 2.2.18 kernel with Suse. I had to patch it to 2.2.18 from Suse
6.4's 2.2.14. Suse's book doesn't cover this and I had a hard time finding
info on the web about it also. Alot of Linux How-Tos and FAQs don't amount
to crap because no one tends to update them.
I had to use 3 different Linux books to figure out how to update a kernel by
using patches. It was fairly simple but the fact that I had to compile
information from multiple searches had me kinda confused. Now, I can't
really remember how I did it! :o)
Time for me to hit the books....thinking about this, I'm now intrigued as to
how I did it. I need to add the procedure to my Linux notes so if I have to
do it again, I won't have the problems I had the first time I did this.
Ron Sinclair
http://members.tripod.com/~WIGGLIT
http://members.fortunecity.com/wigglit
ICN 3765104
irc.mdsog.net, #dsm
----- Original Message -----
From: "Ken Hughes"
Okay. I'm feel like a complete dumbass, but is there a SuSE 2.2.18 kernel out there somewhere? All I can seem to find on ftp.suse.com is 2.2.16.
Thanks...
Ken
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
* Ron Sinclair (sinclair@zma.attmil.ne.jp) [010223 23:43]:
I'm using a 2.2.18 kernel with Suse. I had to patch it to 2.2.18 from Suse 6.4's 2.2.14. Suse's book doesn't cover this and I had a hard time finding info on the web about it also. Alot of Linux How-Tos and FAQs don't amount to crap because no one tends to update them.
Maybe you should update the Kernel-HOWTO then. The kernels and SuSE patches can always be found here: ftp.suse.com:/pub/people/mantel/next -- -ckm
Maybe you should update the Kernel-HOWTO then.
The kernels and SuSE patches can always be found here: ftp.suse.com:/pub/people/man
I used generic, non-Suse-specific kernel patches...worked fine for me, but I tried to use them on my other linux box, which uses TurboLinux 6.0. The kernel wouldn't accept the patches. This happened awhile back and I cannot remember the actual verbiage the kernel spit out when trying to patch the default TurboLinux kernel. About the Kernel-HOWTO, I'll leave the revising to someone that's more attuned to working with Linux. I still consider myself not an expert nor a beginner, but someone in-between. I think that someone adding their 2 cents to a Kernel-HOWTO needs to know a bit more than I do concerning this topic. I can only say that I know that what I used to make my burner works for ME...I cannot say how, just that it works. Maybe someone with a bit more background in the subject matter is best suited for your suggestion. I'm not going to try to update something that I only understand on the surface. What I WILL do is create a HOWTO for myself and maybe post it on my page for others that are looking for simple instructions on how to do this. I think a cut-and-dry HOWTO would benefit many newbies and mid-level users. My main beef with alot of the HOWTOs is that most are very dry and tend to be loaded with geek terminology. For example, me being an ex-military man, if I started spouting out twenty thousand military acronyms during a discussion that relates to something that's military but the audience is civilians or new recruits, I would lose MANY in the discussion from the onset. If I found a HOWTO that put everything in layman's terms, then I would be extremely happy, but I've yet to see that. I spend more time referencing a reference of a reference than actually finding an answer to my ONE problem. It took me over a year to get my burner working with Suse and when I found the answer, I was like, "WTF?!?! I could have had this working a LONG time ago." I found my answer in a "...for Dummies" book instead of a HOWTO...kinda ironic, eh? Ron Sinclair http://members.tripod.com/~WIGGLIT http://members.fortunecity.com/wigglit ICN 3765104 irc.mdsog.net, #dsm
Christopher Mahmood wrote:
The kernels and SuSE patches can always be found here: ftp.suse.com:/pub/people/mantel/next
Thanks! That's exactly what I was looking for. Is there a reason why there isn't a link on the suse.com web site that points folks to this? Ken
Ken Hughes wrote:
Christopher Mahmood wrote:
The kernels and SuSE patches can always be found here: ftp.suse.com:/pub/people/mantel/next
Thanks! That's exactly what I was looking for. Is there a reason why there isn't a link on the suse.com web site that points folks to this?
There's no link because I'm not sure these kernels are 'official' SuSE kernels. I think any 'official' kernel updates will be put in the update directory on the ftp server. Hubert does do a very good job of keeping the kernels in his ftp directory up to date, though. Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
* Ken Hughes (ken@taclug.org) [010224 11:46]:
Christopher Mahmood wrote:
The kernels and SuSE patches can always be found here: ftp.suse.com:/pub/people/mantel/next
Thanks! That's exactly what I was looking for. Is there a reason why there isn't a link on the suse.com web site that points folks to this?
That would take all of the fun and mystery out of the ftp server. -- -ckm
On Saturday 24 February 2001 02:42, Ron Sinclair wrote:
I'm using a 2.2.18 kernel with Suse. I had to patch it to 2.2.18 from Suse 6.4's 2.2.14. Suse's book doesn't cover this and I had a hard time finding info on the web about it also. Alot of Linux How-Tos and FAQs don't amount to crap because no one tends to update them.
I had to use 3 different Linux books to figure out how to update a kernel by using patches. It was fairly simple but the fact that I had to compile information from multiple searches had me kinda confused. Now, I can't really remember how I did it! :o)
Time for me to hit the books....thinking about this, I'm now intrigued as to how I did it. I need to add the procedure to my Linux notes so if I have to do it again, I won't have the problems I had the first time I did this.
Ron Sinclair Ron,
IIRC I found the answer to how to do this .... yup, here it is: http://<dochost>/sdb/en/html/kernelpatch.html Dochost is pretty good. It can be a bit of a jumble at times, and when it gets broken from the most recent apache upgrade or whatever, I start to wonder how useful it is. This would probably be less of problem if I had dochost installed on a less volatile sever. Unfortunately, AFAIK, there is no way to install package specific documentation with out installing the package. This makes it impossible to have a single dochost which provides all information I'm interested in. Steve
I suppose this is sheer ignorance on my part about how SuSE tweaks code, but I've actually never understood why I should use SuSE's kernels as opposed to just compiling from vanilla source at kernel.org I realize that RedHat contorts their kernels out of all recognition for their distro, but for SuSE I've found that (for me) the vanilla kernels work at least as well as the distribution-specific ones. No problems at all with vanilla 2.2.17 through 2.4.2 (other than taking care to ugrade the appropriate supporting packages, of course). Have I been missing something? --Kevin On Fri, 23 Feb 2001, Ken Hughes wrote:
Okay. I'm feel like a complete dumbass, but is there a SuSE 2.2.18 kernel out there somewhere? All I can seem to find on ftp.suse.com is 2.2.16.
Thanks...
Ken
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If you don't use any of the features in the SuSE kernel that isn't by default in the vanilla kernel, then there's no wonder that the vanilla one works just as well :-) The SuSE kernel adds value to the 2.2 series, with amongs other things ReiserFS, better USB, and very probably a few other things that I havn't used myself :-) Just the ReiserFS has been reason enough for me to stick with the SuSE kernels. See.... tosi@dustpuppy:~ > df Filesystem 1k-blocks Used Available Use% Mounted on * /dev/hda3 12417856 3916728 8501128 32% / /dev/hda1 85520 3286 77818 5% /boot * /dev/hdb2 6160700 5311848 848852 87% /home tosi@dustpuppy:~ > mount * /dev/hda3 on / type reiserfs (rw) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/hda1 on /boot type ext2 (rw) * /dev/hdb2 on /home type reiserfs (rw) /proc/bus/usb on /proc/bus/usb type usbdevfs (rw) tosi@dustpuppy:~ > Notice the "*" marked fields... With kernel 2.2 this wasn't possible, except if you either used the SuSE supplied kernel, or patched ReiserFS into the vanilla kernel yourself. - My data is valuable enough for me so not to be messing around with kernel patches on a rainy day :-) - -tosi
I suppose this is sheer ignorance on my part about how SuSE tweaks code, but I've actually never understood why I should use SuSE's kernels as opposed to just compiling from vanilla source at kernel.org I realize that RedHat contorts their kernels out of all recognition for their distro, but for SuSE I've found that (for me) the vanilla kernels work at least as well as the distribution-specific ones. No problems at all with vanilla 2.2.17 through 2.4.2 (other than taking care to ugrade the appropriate supporting packages, of course). Have I been missing something?
--Kevin
On Fri, 23 Feb 2001, Ken Hughes wrote:
Okay. I'm feel like a complete dumbass, but is there a SuSE 2.2.18 kernel out there somewhere? All I can seem to find on ftp.suse.com is 2.2.16.
Thanks...
Ken
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org
iD8DBQE6l7xm6mRH+PEpr2YRApujAJ4l2S8oVPDIbpKHMAFpJUBF9I7PPQCcCfqT oBjn3K0OuOTEJHSkCzjpEOw= =sWgf -----END PGP SIGNATURE-----
Quoting Tor Sigurdsson on Sat, Feb 24, 2001 at 01:51:30PM +0000:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
If you don't use any of the features in the SuSE kernel that isn't by default in the vanilla kernel, then there's no wonder that the vanilla one works just as well :-)
The SuSE kernel adds value to the 2.2 series, with amongs other things ReiserFS, better USB, and very probably a few other things that I havn't used myself :-)
I use vanilla kernels with SuSE and patch reiserfs support from the reiser site and intall the utils. If you use 2.2.18, usb support is pretty good. I have had several different devices work with this kernel like keyspan usb to serial adaptors, etc. All in all, the patched kernels are nice; but one can definitely move to their own kernels with only a little work. I neve thought of the patch to get reiser support into the 2.2 kernels that I use particularly problemmatic. -- Michael Perry mperry@tsoft.com ------------------
On Sat, Feb 24, 2001 at 08:22:14AM +0000, klcroxen wrote:
I suppose this is sheer ignorance on my part about how SuSE tweaks code, but I've actually never understood why I should use SuSE's kernels as opposed to just compiling from vanilla source at kernel.org I realize that RedHat contorts their kernels out of all recognition for their distro, but for SuSE I've found that (for me) the vanilla kernels work at least as well as the distribution-specific ones. No problems at all with vanilla 2.2.17 through 2.4.2 (other than taking care to ugrade the appropriate supporting packages, of course). Have I been missing something?
The only problems I have run into deal with some of the backports. For instance, I just compiled 2.2.18 a few hours ago. I had to remove the usbdevfs line for my /etc/fstab, and I had to change an option in Yast. The SuSE kernels do have some nice features, but if you don't use them, then quite frankly, you won't notice the difference if you compile from vanilla sources. I sure don't. Victor Cardona
participants (9)
-
Chris Reeves
-
Christopher Mahmood
-
Ken Hughes
-
klcroxen
-
Michael Perry
-
Ron Sinclair
-
Steven T. Hatton
-
Tor Sigurdsson
-
Victor R. Cardona