Re: [SLE] Disgruntled Customer
Michael,
So, I take it that using the SuSE RPM is what you
recommend? I have never loaded a kernel with RPMs,
just with source. Is there detailed instructions that
come with the package? Even the SuSE book covers the
source compilation, not the rpm.
Thanks, Ron
--- Michael Hasenstein
"Victor R. Cardona" wrote:
How did you install 2.2.16? I am a new user of 6.4 and was wondering if there was an automatic way of installing 2.2.16? I presume only .rpm files are used but I have tried installing 2.2.16 (with rpm files) and have not gotten very far.
How did you do it?
I just downloaded the source from www.kernel.org. I don't use any of the enhancements in the SuSE kernel, so I didn't need the rpm.
The 'enhancements' are not jsut feature updates, it's also memory management fixes and other stability fixes. Try stock 2.2.16 on a big busy server... (this is where bugs show earlier than on a lightly loaded 128 MB client machine that's rebootet once a week after doing almost nothing)
-- Michael Hasenstein http://www.suse.de/~mha/ SuSE Linux AG, Nuernberg (Germany) SuSE Inc., Oakland, California (US)
-- 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
__________________________________________________ Do You Yahoo!? Yahoo! Mail Free email you can access from anywhere! http://mail.yahoo.com/ -- 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
i am new and i recommend from source rather than rpm you might want to ask more about that On Mon, 21 Aug 2000, Ron Heron wrote: > Michael,
So, I take it that using the SuSE RPM is what you recommend? I have never loaded a kernel with RPMs, just with source. Is there detailed instructions that come with the package? Even the SuSE book covers the source compilation, not the rpm.
Thanks, Ron
--- Michael Hasenstein
wrote: "Victor R. Cardona" wrote:
How did you install 2.2.16? I am a new user of 6.4 and was wondering if there was an automatic way of installing 2.2.16? I presume only .rpm files are used but I have tried installing 2.2.16 (with rpm files) and have not gotten very far.
How did you do it?
I just downloaded the source from www.kernel.org. I don't use any of the enhancements in the SuSE kernel, so I didn't need the rpm.
The 'enhancements' are not jsut feature updates, it's also memory management fixes and other stability fixes. Try stock 2.2.16 on a big busy server... (this is where bugs show earlier than on a lightly loaded 128 MB client machine that's rebootet once a week after doing almost nothing)
-- Michael Hasenstein http://www.suse.de/~mha/ SuSE Linux AG, Nuernberg (Germany) SuSE Inc., Oakland, California (US)
-- 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
__________________________________________________ Do You Yahoo!? Yahoo! Mail Free email you can access from anywhere! http://mail.yahoo.com/
-- 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
-- Rolando Roman -- 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
Rolando Roman wrote:
i am new and i recommend from source rather than rpm you might want to ask more about that
Not essential any more these days, I only do it on big servers, but in the end that's religion. Anyway, I responded only to point out that on an rpm-based system even the sources are rpm's.... The Linux sources are a little 'special', because it's a binary rpm containing sources. In the case of the SuSE kernel, the patched sources. It is in turn made by a source rpm, which contains a pristine 2.2.16 and the SuSE patches in an extra file/files. You can find the single patches somewhere on the CD, I forgot where, if you're interested to see what exactly we do to a standard kernel. -- Michael Hasenstein http://www.suse.de/~mha/ SuSE Linux AG, Nuernberg (Germany) SuSE Inc., Oakland, California (US) -- 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
Dear SuSE, This issue IS significant for us as we use both SuSE 6.4 Intel and PPC versions and have attempted to create our own kernels without success. Given that the kernel is supposed to be reasonably Open, is it possible to find the usual adjustments that SuSE makes so we can apply them after or in due process of creating a new kernel. Creating a kernel from (6.4) lx_linux 2.2.14 + patches to 2.2.16 for the PPC doesn't produce a functional kernel so there is something else we have to do. Applying the 2.2.15 and 2.2.16 patches to lx_suse (both Intel and PPC) fails completely. Yes the 2.2.16 kernel for the PPC works, but we have no idea whats inside them. We for example don't want to have anything to do with SCSI,IPX,ARCNET,Token Rings,Sound,Video and that stuff - this is an industrial and business environment and we need performance. We DO need more advanced options at the IP Network stage and Appletalk options which we CAN get with Redhat. Likewise,if SuSE is modifing memory management facilities, then we need to know. Regards, Bruce.
Rolando Roman wrote:
i am new and i recommend from source rather than rpm you might want to ask more about that
Not essential any more these days, I only do it on big servers, but in the end that's religion.
Anyway, I responded only to point out that on an rpm-based system even the sources are rpm's.... The Linux sources are a little 'special', because it's a binary rpm containing sources. In the case of the SuSE kernel, the patched sources. It is in turn made by a source rpm, which contains a pristine 2.2.16 and the SuSE patches in an extra file/files. You can find the single patches somewhere on the CD, I forgot where, if you're interested to see what exactly we do to a standard kernel.
-- Michael Hasenstein http://www.suse.de/~mha/ SuSE Linux AG, Nuernberg (Germany) SuSE Inc., Oakland, California (US)
-- 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
-- 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
On Tue, 22 Aug 2000, Bruce wrote:
We for example don't want to have anything to do with SCSI,IPX,ARCNET,Token Rings,Sound,Video and that stuff - this is an industrial and business environment and we need performance. We DO need more advanced options at the IP Network stage and Appletalk options which we CAN get with Redhat.
You want performance, and yet you want nothing to do with SCSI and you want to use Appletalk? Remember, Appletalk performance is an oxymoron. Greg -- 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
OK, point taken. Perhaps I should have used the word 'facilities'. As for SSCI, well I suspect Raid on Firewire is more appropriate now! Appletalk - slow, but at least it works. Bruce.
On Tue, 22 Aug 2000, Bruce wrote:
We for example don't want to have anything to do with SCSI,IPX,ARCNET,Token Rings,Sound,Video and that stuff - this is an industrial and business environment and we need performance. We DO need more advanced options at the IP Network stage and Appletalk options which we CAN get with Redhat.
You want performance, and yet you want nothing to do with SCSI and you want to use Appletalk? Remember, Appletalk performance is an oxymoron.
Greg
-- 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
On Tue, 22 Aug 2000, Bruce wrote: b> Dear SuSE, b> b> This issue IS significant for us as we use both SuSE 6.4 Intel and PPC versions b> and have attempted to create our own kernels without success. Given that b> the kernel is supposed to be reasonably Open, is it possible b> to find the usual adjustments that SuSE makes so we can apply them b> after or in due process of creating a new kernel. b> Not sure where SuSE keeps these patches, but it's rather easy to create one yourself if your interested in doing so, simply do the following. 1. obtain default kernel and extract to location other then /usr/src/linux 2. enter the following on a cmd line diff -uPr <path to default kernel> <path to SuSE kernel> > SuSE-kernel-patch.dif 3. move patch to secure location for use on other machines Chances are good it will even apply to the next version kernel with a couple warnings about line locations being different in some src files. As long as you don't get any rej files then your set. I've done it myself this way a few times for the reiser, emu10k1 and USB stuff. b> Creating a kernel from (6.4) lx_linux 2.2.14 + patches to 2.2.16 for the PPC b> doesn't produce a functional kernel so there is something else we have to do. b> b> Applying the 2.2.15 and 2.2.16 patches to lx_suse (both Intel and PPC) b> fails completely. b> b> Yes the 2.2.16 kernel for the PPC works, but we have no idea whats inside them. b> b> We for example don't want to have anything to do with SCSI,IPX,ARCNET,Token b> Rings,Sound,Video and that stuff - this is an industrial and business b> environment and we need performance. We DO need more advanced options at b> the IP Network stage and Appletalk options which we CAN get with Redhat. b> b> Likewise,if SuSE is modifing memory management facilities, then we need to b> know. b> b> Regards, b> Bruce. b> b> b> b> b> >Rolando Roman wrote: b> >> b> >> i am new and i recommend from source rather than rpm you might want to ask b> >> more about that b> > b> >Not essential any more these days, I only do it on big servers, but in b> >the end that's religion. b> > b> >Anyway, I responded only to point out that on an rpm-based system even b> >the sources are rpm's.... b> >The Linux sources are a little 'special', because it's a binary rpm b> >containing sources. In the case of the SuSE kernel, the patched sources. b> >It is in turn made by a source rpm, which contains a pristine 2.2.16 and b> >the SuSE patches in an extra file/files. You can find the single patches b> >somewhere on the CD, I forgot where, if you're interested to see what b> >exactly we do to a standard kernel. b> > b> > b> >-- b> >Michael Hasenstein b> >http://www.suse.de/~mha/ b> >SuSE Linux AG, Nuernberg (Germany) b> >SuSE Inc., Oakland, California (US) b> > b> >-- b> >To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com b> >For additional commands send e-mail to suse-linux-e-help@suse.com b> >Also check the FAQ at http://www.suse.com/support/faq b> b> b> b> b> -- S.Toms - tomas@primenet.com - www.primenet.com/~tomas SuSE Linux v6.4+ - Kernel 2.2.16 Like so many Americans, she was trying to construct a life that made sense from things she found in gift shops. -- Kurt Vonnegut, Jr. -- 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
Bruce wrote:
Dear SuSE,
This issue IS significant for us as we use both SuSE 6.4 Intel and PPC versions and have attempted to create our own kernels without success. Given that the kernel is supposed to be reasonably Open, is it possible to find the usual adjustments that SuSE makes so we can apply them after or in due process of creating a new kernel.
Creating a kernel from (6.4) lx_linux 2.2.14 + patches to 2.2.16 for the PPC doesn't produce a functional kernel so there is something else we have to do.
OF COURSE this will fail. Those patches have been created against a standard kernel! What about "openness" of SuSE? If you read the kernel list you'd find ALL the patches we use there. Many are from us, many are from other people. Other companies with kernel knowhow (because they employ hackers), VA for example, also patch the standard kernel heavily. The last time I checked a Red Hat kernel their patch was 4 MB. Ever looked on CD1 into unsorted/patches? We deliver EVERY SINGLE source that's GPL. We do not deliver teh source rpm for the lx_suse.rpm package, because it is so big and all you really need are the patches. You can make an "official" (whatever that means) kernel from the lx_suse kernel by reverse-applying these patches, as you should know if you create your own kernels.
Applying the 2.2.15 and 2.2.16 patches to lx_suse (both Intel and PPC) fails completely.
See above, of course it does, and that's perfectly all right.
Yes the 2.2.16 kernel for the PPC works, but we have no idea whats inside them.
Ok, so now I told you the location of the patches - that you really could have found yourself, or do you think we keep our kernel hackers work in the safe?
We for example don't want to have anything to do with SCSI,IPX,ARCNET,Token Rings,Sound,Video and that stuff - this is an industrial and business environment and we need performance. We DO need more advanced options at the IP Network stage and Appletalk options which we CAN get with Redhat.
This is a joke, right? Not that I doubt that the Red Hat kernel is ok, they've got kernel knowhow after all, but I doubt your statement.
Likewise,if SuSE is modifing memory management facilities, then we need to know.
Would you please have a look at the Red Hat or VA patches to a standard kernel?! If you'd just subscribe to the kernel list you'd get to know EVERYTHING our hackers and others do. How more open can it get? -- Michael Hasenstein http://www.suse.de/~mha/ SuSE Linux AG, Nuernberg (Germany) SuSE Inc., Oakland, California (US) -- 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
Dear Michael, Thankyou very much for your very detailed reply. PLEASE PLEASE, I was NOT being critical or nasty about SuSE at all. I was just requesting HOWTO info so to speak. I think the SuSE disto is very good and we like to know whats going on.
This is a joke, right? Not that I doubt that the Red Hat kernel is ok, they've got kernel knowhow after all, but I doubt your statement.
Please don't think we are critical of the Suse and comparing it to Redhat. NOT AT ALL. We have abandoned Redhat for SuSE for many reasons. And one of the reasons is that I like the SuSE package (software rather than the box!) More importantly, thankYOU for all your help. Regards, Bruce. <snip>
OF COURSE this will fail. Those patches have been created against a standard kernel! What about "openness" of SuSE? If you read the kernel list you'd find ALL the patches we use there. Many are from us, many are from other people. Other companies with kernel knowhow (because they employ hackers), VA for example, also patch the standard kernel heavily. The last time I checked a Red Hat kernel their patch was 4 MB.
Ever looked on CD1 into unsorted/patches? We deliver EVERY SINGLE source that's GPL. We do not deliver teh source rpm for the lx_suse.rpm package, because it is so big and all you really need are the patches.
You can make an "official" (whatever that means) kernel from the lx_suse kernel by reverse-applying these patches, as you should know if you create your own kernels.
Applying the 2.2.15 and 2.2.16 patches to lx_suse (both Intel and PPC) fails completely.
See above, of course it does, and that's perfectly all right.
Yes the 2.2.16 kernel for the PPC works, but we have no idea whats inside them.
Ok, so now I told you the location of the patches - that you really could have found yourself, or do you think we keep our kernel hackers work in the safe?
We for example don't want to have anything to do with SCSI,IPX,ARCNET,Token Rings,Sound,Video and that stuff - this is an industrial and business environment and we need performance. We DO need more advanced options at the IP Network stage and Appletalk options which we CAN get with Redhat.
This is a joke, right? Not that I doubt that the Red Hat kernel is ok, they've got kernel knowhow after all, but I doubt your statement.
Likewise,if SuSE is modifing memory management facilities, then we need to know.
Would you please have a look at the Red Hat or VA patches to a standard kernel?! If you'd just subscribe to the kernel list you'd get to know EVERYTHING our hackers and others do. How more open can it get?
-- Michael Hasenstein http://www.suse.de/~mha/ SuSE Linux AG, Nuernberg (Germany) SuSE Inc., Oakland, California (US)
-- 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
-- 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
Bruce wrote:
Dear Michael, Thankyou very much for your very detailed reply. PLEASE PLEASE, I was NOT being critical or nasty about SuSE at all. I was just requesting HOWTO info so to speak. I think the SuSE disto is very good and we like to know whats going on.
This is a joke, right? Not that I doubt that the Red Hat kernel is ok, they've got kernel knowhow after all, but I doubt your statement.
Please don't think we are critical of the Suse and comparing it to Redhat. NOT AT ALL. We have abandoned Redhat for SuSE for many reasons. And one of the reasons is that I like the SuSE package (software rather than the box!)
Come on, not the other extreme now. -- Michael Hasenstein http://www.suse.de/~mha/ SuSE Linux AG, Nuernberg (Germany) SuSE Inc., Oakland, California (US) -- 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
Hi, On Tue, 22 Aug 2000, Michael Hasenstein wrote:
Bruce wrote:
Dear Michael, Thankyou very much for your very detailed reply. PLEASE PLEASE, I was NOT being critical or nasty about SuSE at all. I was just requesting HOWTO info so to speak. I think the SuSE disto is very good and we like to know whats going on.
This is a joke, right? Not that I doubt that the Red Hat kernel is ok, they've got kernel knowhow after all, but I doubt your statement.
Please don't think we are critical of the Suse and comparing it to Redhat. NOT AT ALL. We have abandoned Redhat for SuSE for many reasons. And one of the reasons is that I like the SuSE package (software rather than the box!)
Come on, not the other extreme now.
Calm down, guys :) Everything is fine now. LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany Screw each and every prime directive. -- 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
Michael, On Tue, 22 Aug 2000, you wrote:
Rolando Roman wrote:
i am new and i recommend from source rather than rpm you might want to ask more about that
Not essential any more these days, I only do it on big servers, but in the end that's religion.
Anyway, I responded only to point out that on an rpm-based system even the sources are rpm's.... The Linux sources are a little 'special', because it's a binary rpm containing sources. In the case of the SuSE kernel, the patched sources. It is in turn made by a source rpm, which contains a pristine 2.2.16 and the SuSE patches in an extra file/files. You can find the single patches somewhere on the CD, I forgot where, if you're interested to see what exactly we do to a standard kernel.
Can you tell me why "probe all luns" is turned on by default? It's not really that big of a problem, and I just re-compile after turning it off. Is this something that is on the more common SCSI cards like adaptec? I have an advansys, and my teac burner won't work unless I turn this off. Mike -- -------------------------------------------------------- for a great linux portal try http://www.freezer-burn.org home: http://www.an-netz.de/home/bcomber -------------------------------------------------------- -- 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
Mike wrote:
Anyway, I responded only to point out that on an rpm-based system even the sources are rpm's.... The Linux sources are a little 'special', because it's a binary rpm containing sources. In the case of the SuSE kernel, the patched sources. It is in turn made by a source rpm, which contains a pristine 2.2.16 and the SuSE patches in an extra file/files. You can find the single patches somewhere on the CD, I forgot where, if you're interested to see what exactly we do to a standard kernel.
Can you tell me why "probe all luns" is turned on by default? It's not really that big of a problem, and I just re-compile after turning it off. Is this something that is on the more common SCSI cards like adaptec? I have an advansys, and my teac burner won't work unless I turn this off.
No idea, I forwarded your question to the guy packaging the kernel. -- 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 Heron wrote:
Michael,
So, I take it that using the SuSE RPM is what you recommend? I have never loaded a kernel with RPMs, just with source. Is there detailed instructions that come with the package? Even the SuSE book covers the source compilation, not the rpm.
The package lx_suse.rpm installs the sources (/usr/src/linux-2.2.16.SuSE). For the compiled kernels, jsut install and run lilo (of course, the lilo configuration must include the kernel image installed by the rpm, which the default one does). -- Michael Hasenstein http://www.suse.de/~mha/ SuSE Linux AG, Nuernberg (Germany) SuSE Inc., Oakland, California (US) -- 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
participants (8)
-
bcomber@an-netz.de
-
bruce@toorak.com
-
ethant@pacificnet.net
-
grimmer@suse.de
-
heroron@yahoo.com
-
landie@concentric.net
-
mha@suse.com
-
tomas@primenet.com