So vmware came out with new version supposedly suitable for 2.4 kernel. I gave up last time and wanted to give it another shot. Well it gets further this time but still doesn't install on 7.1: What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] The directory of kernel headers (version 2.4.2) does not match your running kernel (version 2.4.2-4GB). Consequently, even if the compilation of the module was successful, the module would not load into the running kernel. What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] This is the biggest problem with SuSE. They lack standards for what they do. If you go to the ftp site you have the kernel reside in directory "images" but if you go to the update directory the kernel suddenly resides in a directory called "kernel". Why would you not call it the same. Then the kernel in the 7.1 tree is newer than the kernel in the update directory tree. I have mentioned this like a hundred times that SuSE should fix how they do package updates but they ignore their users on this. (Why to hell is licq in n* directory, Gaim is in gnm* and kicq is in k2de*. What is SuSE trying to do??? Spread out all IM clients across all directories? Where you gonna put jabber? j*??? I realize that gaim is gnome utility and kicq a kde utility and licq is not tied to a wm but jesus you have licq compiled in with kde support so what prompted you to not put it into k2de*? I know it is compiled with kde support because it crashes all the time due to kde error. At least you could create a directory im* which contains links to all instant messenger related packages. But I guess we will wait years for a sane solution like that. The single biggest problem with SuSE is standards and wasting hours and hours on finding packages.) Ok so you may have found the kernel. I don't even bother compiling my kernel because it just is too confusing and my hardware is old. But for vmware you need the source. Why would SuSE not put the source (lx_suse) packages into the same directory as the binaries? No the sources are in d2 which makes maybe sense to a SuSE employee but not to a user which has to spend ten minutes scouring directories because they in the first place don't know that the package is called lx_suse. Would SuSE please move the lx_suse packages into the kernel/images directory where any sane person would put them??? Ok so you finally installed lx_suse24 from the 7.1 tree. Remember the kernel packages in the update tree are older. Now you figure vmware is ready to get done installing. But no SuSE calls its kernel 2.4.2-4Gb (ver 11) but it's kernel from source is 2.4.2 (SuSE-6)and vmware chokes. Man I am so sick of this non-standard bullshit. You spend like an hour scouring and trying to match up programs and end up with nothing. I know only partial blame lies with SuSE because they should name their kernel something normal and the other part is on VMware which should open source their stupid plexer and the other part is that I shouldn't get so hyped about something minor but it's frustrating. Yesterday it was java servlets and pdflib and today its the kernel compatibilities. God I need a break, mk _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com
Purple Shirt schrieb:
You are so damn right, man. Your words in Suse's probably non-existing ears here.. "Working" with Suse-Linux ends you up in locating files/packages all the time and all over again. I am fed up with this non-standard-sales policy of suse! -- *º¤., ¸¸,.¤º*¨¨¨*¤ =Oliver@home= *º¤., ¸¸,.¤º*¨¨*¤ Also, wie war das denn nochmal? Da wir jetzt durch eine untaktisch kluge Fuegung eingesehen haben, dass das mit der Zusammendehnung ein echter Griff ins Klo war, sehen wir keinen weiteren Grund zur Veranlassung.
* Oliver Ob [Sun, 06 May 2001 17:48:56 +0200]:
You are so damn right, man. Your words in Suse's probably non-existing ears here..
"Working" with Suse-Linux ends you up in locating files/packages all the time and all over again.
I am fed up with this non-standard-sales policy of suse!
You've been kicked from the german SuSE list already for doing nothing than annoy people! If you continue in this style, chances are rather high it'll happen here too. -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390
Philipp Thomas schrieb:
* Oliver Ob [Sun, 06 May 2001 17:48:56 +0200]:
You are so damn right, man. Your words in Suse's probably non-existing ears here..
"Working" with Suse-Linux ends you up in locating files/packages all the time and all over again.
I am fed up with this non-standard-sales policy of suse!
You've been kicked from the german SuSE list already for doing nothing than annoy people! If you continue in this style, chances are rather high it'll happen here too.
I was not informed yet that agreeing with you and pointing out one's opinion is such a problem for german users. In fact, discussion threads on "Impressions on SuSe Versions" are very often spread over the list, so try to tolerate opinions of others. Also, it has been complained by some users that too few dudes from SuSe read and write on this list, that is why I stated "probably non-existing ears". I know that some SuSe guys are on this list under another name, but some users here feel like noone has an open ear on the topics such as in the mail that I was reacting on (see the original mail). That is all. Futhermore, if you disagree, you could have told me in PRIVATE MAIL as what you wrote has nothing at all to do with the topic above and only picks up an old disagreement on a totally different list. See it like it is: Freedom Of Speech #1 :-) I like Suse (I started with Slackware in 1996) and I know why I will use it on. Just to make this clear. I precisely know why I switched to Suse and these reasons still apply (positively on me). Friendly regards, O
* Oliver Ob
I was not informed yet that agreeing with you and pointing out one's opinion is such a problem for german users.
There is a lot of different ways of pointing out opinions.
In fact, discussion threads on "Impressions on SuSe Versions" are very often spread over the list, so try to tolerate opinions of others. Also, it has been complained by some users that too few dudes from SuSe read and write on this list, that is why I stated "probably non-existing ears". I know that some SuSe guys are on this list under another name, but some users here feel like noone has an open ear on the topics such as in the mail that I was reacting on (see the original mail). That is all.
It is *not* required for SuSE people to read these lists. We provide it as a service to the community, and participating here is something we do on our own.
Futhermore, if you disagree, you could have told me in PRIVATE MAIL as what you wrote has nothing at all to do with the topic above and only picks up an old disagreement on a totally different list.
See it like it is: Freedom Of Speech #1 :-)
I agree on freedom of speech, but if I find language/behaviour offending enough I'm in my right to kick people off the list -- no warning whatsoever.
I like Suse (I started with Slackware in 1996) and I know why I will use it on. Just to make this clear. I precisely know why I switched to Suse and these reasons still apply (positively on me).
Glad to hear :-)
Friendly regards,
Ditto, Mads Martin -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little bit more effort." -- A. P. J.
On Sat, 5 May 2001, Purple Shirt wrote:
So vmware came out with new version supposedly suitable for 2.4 kernel. I gave up last time and wanted to give it another shot.
Well it gets further this time but still doesn't install on 7.1:
What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include]
The directory of kernel headers (version 2.4.2) does not match your running kernel (version 2.4.2-4GB). Consequently, even if the compilation of the module was successful, the module would not load into the running kernel.
What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include]
This is the biggest problem with SuSE. They lack standards for what they do.
What kind of standard do you expect here? The kernel sources are installed. However, you can use the same source tree to compile different versions of the kernel (US/SMP, with BigMem or without). To differentiate between these versions, you need to give them different names. This name is defined in /usr/src/linux/include/linux/version.h. The version.h for the booted kernel is located in /boot/vmlinuz.version.h. Simply copy this one over to the correct location.
If you go to the ftp site you have the kernel reside in directory "images" but if you go to the update directory the kernel suddenly resides in a directory called "kernel". Why would you not call it the same. Then the kernel in the 7.1 tree is newer than the kernel in the update directory tree.
Yes, there is some inconsistency here. The files below "kernel" have been put in there manually and are only intended for special purposes. I agree, that a README in there would be helpful to give some more info about these files.
I have mentioned this like a hundred times that SuSE should fix how they do package updates but they ignore their users on this.
This is simply not true.
(Why to hell is licq in n* directory, Gaim is in gnm* and kicq is in k2de*. What is SuSE trying to do??? Spread out all IM clients across all directories? Where you gonna put jabber? j*???
I realize that gaim is gnome utility and kicq a kde utility and licq is not tied to a wm but jesus you have licq compiled in with kde support so what prompted you to not put it into k2de*? I know it is compiled with kde support because it crashes all the time due to kde error. At least you could create a directory im* which contains links to all instant messenger related packages. But I guess we will wait years for a sane solution like that. The single biggest problem with SuSE is standards and wasting hours and hours on finding packages.)
This is due to the fact, that we have quite a lot of people working on these packages. This is a general problem with the flat package series. Well, an ICQ client is all of the above: it's a network application (series "n"), Gaim is a GNOME app (Series gnm) and kicq is a KDE2 app (series k2de). They all fit, but I agree, this is not very consistent. I hope we can get rid of these package series someday. We now have started using the RPM Group tags, but this still will not solve the problem, since again packages fit into multiple groups. But RPM is not capable of accepting multiple Group tags :( But I doubt, that you will find any kind of "standard" about this. This is up to the distributor and everyone makes it different here (if they are not a Red Hat clone, that is).
Ok so you may have found the kernel. I don't even bother compiling my kernel because it just is too confusing and my hardware is old. But for vmware you need the source. Why would SuSE not put the source (lx_suse) packages into the same directory as the binaries? No the sources are in d2 which makes maybe sense to a SuSE employee but not to a user which has to spend ten minutes scouring directories because they in the first place don't know that the package is called lx_suse. Would SuSE please move the lx_suse packages into the kernel/images directory where any sane person would put them???
Well, the kernel sources are also required for some development, hence they ended up in the "d" series. Historically, the "kernel" subdirectory did not include RPMs and it was not a package series per se. But this sounds like a very good suggestion. I will check, if we can change this.
Ok so you finally installed lx_suse24 from the 7.1 tree. Remember the kernel packages in the update tree are older. Now you figure vmware is ready to get done installing. But no SuSE calls its kernel 2.4.2-4Gb (ver 11) but it's kernel from source is 2.4.2 (SuSE-6)and vmware chokes.
See the reasoning above. All files that need to be replaced to properly build the kernel are in /boot: vmlinuz.autoconf.h, vmlinuz.config and vmlinuz.version.h. vmlinuz.autoconf.h and vmlinuz.version.h. have to be copied into /usr/src/linux/include/linux/{version,autoconf}.h Now the compilation should do fine.
Man I am so sick of this non-standard bullshit.
What standard to you refer to here? I would love to see any reference.
You spend like an hour scouring and trying to match up programs and end up with nothing. I know only partial blame lies with SuSE because they should name their kernel something normal and the other part is on VMware which should open source their stupid plexer and the other part is that I shouldn't get so hyped about something minor but it's frustrating. Yesterday it was java servlets and pdflib and today its the kernel compatibilities.
God I need a break,
You obviously do :) LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany Say something soft & sweet. Marshmallow.
participants (5)
-
Lenz Grimmer -
Mads Martin Jørgensen -
Oliver Ob -
Philipp Thomas -
Purple Shirt