Now what reply does that deserve? Probably a sarcastic one.
Welcome to the Atlas Steel/Empire State Building in the Sumerian United States of America!:):):)
Without the steel the building wouldn't stand up, and large proportion of the total mass is steel presumably from a single supplier, but they don't have naming rights to the building.
What makes you think NVIDIA's proprietary driver is "part of the Linux OS"?
It's part of the software layer between the hardware and the application layer. What else can it be called?
it isn't even available for most ports of the Linux kernel!
Uncompress the tarfile of the source code for the kernel module that talks to it and compile. For a while there was no support for 2.4.*, but it's there now. If you want support for other than intel*86 hardware, then you have some source code to look at in the kernel module.
Everyone that was using linux before the RMS bandwagon renaming thing had heard of gnu, and most had read the GPL, if only out of curiousity. The FSF is a very fine organisation, but they don't "own" linux, so why should they be able to force a new name down everyones throats? It's the sort of behavior you expect from rich annoying tourists, and not from the professional organisation that they have shown themselves to be.
Hmm, you swallowed the M$ line that the shell (internet explorer) is part of the OS. I argue that it isn't. If I want to use "csh" or "ash" on linux I can, because THE SHELL TALKS TO THE OS - at least that's what the books I've read about shell scripting have said.
If you take the line that the base distribution (as in Slackware "A" floppies without which nothing much can run) of linux is the OS, then GNU does not decide what goes into it. The Debian people do, or RedHat, or Slackware etc. Hence you get a distribution called Slackware Linux and not a distribution called gnu/linux.
GNU does not decide what goes into linux, so it is not gnu/linux.
My previous point was that there are parts of the linux kernel that GNU would never allow in their own OS if they had control. They don't, so it isn't theirs - it is linux with gnu tools. The whole gnu/linux naming thing is even more recent than the linux mascot, and was to increase the visability of gnu.
Also, isn't hurd an OS built on a mach kernel, or is it just a kernel? I thought it was the entire OS - correct me if I'm wrong.
It's not a particularly big jump in terms other than hardware support.
An anonymous but illuminated poster wrote:
Only if you ignore the complicated things like the enterprise directory system which delayed NT 5.0 by 2 years. Toss in the distributed file system, the transaction monitor, the clustering support,
Ok, quite a few things have been done other than hardware support, but not a great deal for six years of effort and acquisition of all the VMS developers (which was my point to the poster that implied that XP evolved from win95 in five years). Something approaching the quality of VMS might have been expected - instead of XP being what we were promised Windows2k would be.
Ten bucks says that Warwick Alison wrote QCOM. All his APIs suck and are deprecated eventually. He just simply needs to take a course in OO programming for dummies.
Bullshit. He was doing object oriented programming with C++ on an Atari ST well over a decade ago.
Check out Qt nethack for something he did years ago before he went to Troll - it's now been ported to the iPac.
I hear ya! With each passing week, I want to move to Germany more and more.
What's more they know how to treat Scientologists properly over there, and don't let them use the "Religeon" argument to disguise their pyramid selling con and dodge tax.
Barking up the wrong code tree
on
Five Years of KDE
·
· Score: 2, Informative
Or, rather, to use the same 5 year timespan, in 5 years, Microsoft went from Windows 95 to WindowsXP
Wrong tree.
In six years microsoft have gone from NT 4 to windows XP. It's not a particularly big jump in terms other than hardware support.
Wouldn't the pitch remain the same as long as the speakers vibrate at the same rate? Wouldn't the sound just travel at a different speed, but still have the same frequency (although a different wavelength)? Huh.
There's a good description here of what happens when you speak with a throat full of helium, complete with sound files to demonstrate. To sum things up, there is an APPARENT change in pitch due to the waveform changing.
A similar thing should happen with a speaker, since the sound will resonate through the gas within the speaker cone.
I am fairly certain that the phenomina that causes our voices to get higher pitched when we inhale helium and then talk would not affect speakers filled with helium since the gas would have no part in driving the cones.
If the part of the speaker which moves and generates the sound (the cone) is in the helium on its outer face , then the higher wave speed of the helium (different speed of sound) will change the pitch. If it is in air then it won't - the same as when you talk underwater you still sound about the same - because you have a larynx full of air and not water.
If all the sound then follows the same path (through the same amount of helium) then it will sound OK. If some sound travels all of the way through air and some through helium and air, then there will be a noticable echo if (a) you are close to the speakers or (b) the helium filled bladders are really big.
Also, if these things are so light, it would be funny to see the speakers push so much air that the air-cabinet starts floating away..
Looks like the roadies still have a job, they'll just need a lot more duct tape!
If you shift the frequency of the sound down a bit (maybe with a bit of compression too) pumping the sound out of helium filled speakers shouldn't be a problem.
To me calling Linux Linux/GNU would be better than calling it GNU/Linux
How about Linux with GNU tools, because that is what it is. Calling it gnu/linux is completely inaccurate anyway, since there are non-GPL kernel modules about that the FSF would never allow if it was their choice.
<RANT>
If you are in a habit of calling every little or large utility part of the OS, (is gcc part of the OS? Be serious please) or even calling the shell part of the OS (eg. Internet Explorer) then there is a lot of stuff that is not part of the gnu project.
The whole attitude is summed up by this quote from RMS: "It's not like I'm asking for it to be called "Stallix"".
It's good to see that Linus is far less interested in the issue than I am - and I'm only interested because I'm sick of newbies "correcting" me every time I use the word linux on USENET (and hence killing the thread).</RANT>
Xfree86 is limited in its power in terms of the ability to render interfaces.
Xfree86 is not the interface.
The window manager is the interface.
X has been able to handle hardware accelerated OpenGL for some enormous length of time. I don't know when SGI were doing OpenGL on X, but I do know that it predated the game DOOM.
It's up to those who write the window managers to use the hardware via X drivers for their interfaces. That is how the 3D & accelerated games and apps do it. Projects such as "evas" provide a library to simplify this. "SDL" also does this.
For years it's been possible to have things like animated icons by continually animating the root window, and have your window manager put a transparent (empty) icon on top of the same size - but that is a nasty hack. you might want the root window (or the CPU for that matter) to do other stuff.
Perhaps by promoting berlin you'd get more people to develop window managers.
Berlin uses a different model - I don't know if it will even allow a choice of window managers. It's also more of a single user with no network access solution. It's to get around the "bloat" in X due to networking and security.
No coincidence that BeOS postdates MIME types while Windows and MacOS predate them. Being unable to copy a non-existent RFC hardly qualifies as "buggering it up".
That's true, QDOS predated MIME types. Windows XP however is somewhat newer and so has no excuse. I might give WinXP a try though, I've heard that it now has all of the multiuser functionality that CP/M (which predated QDOS and ran on personal computers) had and Win2k hasn't. Now I'll be able stop EVERY user on the local network seeing ALL of my files in the shared directories, without having to create lots of shared directories for different groups.
Now we just need to be able to run dodgy shareware without it having admin permissions to the whole box.
Who wouldn't want to wear 3d glasses and some virtual gloves and be in an interface similar to the covert government chem lab programs. Imagine just picking up your hand with a glove on, and seeing your hand in a 3d world, taking the window and moving it with your hand,
I played with something like that at Expo 88 (in the year 1988), in the Japanese pavillion. I wouldn't put much credit on the conspiracy angle, just on the funding vs interest angle.
Trying to portray this as a personality spat is bogus.
I think it was more about priorities than personalities. Some of the E development people were pissed off that gtk (and hence E at that point) wouldn't work on platforms such as solaris & were, of course, more interested in E than fixing gtk. Some of the gnome people didn't like the idea of Raster doing his own widget set, Raster didn't want to be limited by what gtk had then, (the KDE support spat may have just been some vocal newbies that had recently heard of the GPL) and sometime later one of the RedHat people (who is probably not there anymore) wanted E to get to the look and feel of Win*, work on linux i86, and stop at that.
Also I think at that time of the switch "certain interests" had never heard of gnome or Enlightenment - it was well before the fanfare of the gnome 1.0 release, and RedHat was almost the only company that was paying people to write linux applications.
Anyway, I'm not talking about something that happened last year or the year before - I think it happened early in the days of the 0.16 rewrite of E or late in the days of 0.15 and was dropped within a couple of months. If you can find the e-devel mailing list archeives you'll find more.
Gnome picked up E because it was getting lots of user attention that Gnome wanted to share.
That sounds like RMS and linux:) (No flames please, the gnu OS is hurd, and gnu tools are on an enormous range of platforms.)
However, I believe the gnome people had purer motives and that they just wanted a window manager. Those that only wanted to try to teach Trolltech a lesson for having a different licence for Qt were in a (vocal) minority, and I believe they've moved on from gnome to something else now that only the code matters.
Anonymous also wrote:
Once it was clear that E had it's own development schedule and mission that wasn't under control of nor fully compatible with Gnome, there was no reason for the Linux companies to continue funding E.
Funding?
RedHat gave Raster (the writer of Enlightenment) a job, which is a bit different to gnome funding anyone.
and then there was the whole E thing when people were getting frustrated and quitting their jobs.
When E was adopted as the gnome window manager, incorporation of a few things broke E on everything but i86 platforms, gtk was in a SERIOUS state of flux at the time and at least one individual got extremely upset at the idea of Raster having his own widgets, and possibly supporting kde hints in the future (which was done). Hence E went back to being a cross-platform window manager designed to work with both gnome and kde.
The gimp toolkit (gtk) has of course improved enormourly since then and is now cross platform. Athough, if something like thai language support in pango is broken, then it won't compile. It was an intersting exercise finding that I couldn't configure pango to leave it out and couldn't have gtk without pango.
The bit about Raster getting frustrated with his job was between him and an unprofessional middle manager at RedHat (who probably didn't last long) that hadn't quite worked out how to use email. It became very public because the guy didn't know how to use email.
The last stable release of Enlightenment is from last year.
Then be unstable!
Play with new versions of window managers that are in development. If they die on you you have nothing to lose but a single line in.xinitrc.
But beware - it is a good idea to start *nix up in text mode if you're going to use a window manager in development (or especially a video driver in development).
Why read less than ten books and take one exam so that you can call yourself an Engineer, when you can take another and call yourself a Microsoft Certified Surpreme Court Judge?
Hydrogen burns quickly because the shock wave moves a few times faster than an explosion in air (light gas => higher speed of sound = speed of shock waves). The fire is will be over and gone before most things will become hot enough to ignite, or before large steel beams have warmed up above room temperature at the centre.
Someone I used to work with was at ground zero of a small hydrogen explosion in a university lab in Gothemburg, Sweden. He was in the middle of a roomfull of escaped hydrogen gas when it caught fire. He lost his eyebrows, but the fire did not burn long enough for his hair or clothes to stay alight. Apparently the force of the explosion was enough to dislodge bricks from the wall some distance away, so it was better for him to be inside the explosion and getting hit with the force from a small amount going up, than at the outer edge, where you get hit with everything between you and the centre.
.. and of course this has EVERYTHING to do with gnome 2..
Of course it does - it's only version 2 to play catch up with KDE version numbers, silly really.
Anyone why thought that gnome 1.0 was called that because it was stable (in was more unstable than many earlier releases) was sadly deluded. Lets keep the silly politics out of *nix.
Slashdot Mirror
Welcome to the Atlas Steel/Empire State Building in the Sumerian United States of America! :) :) :)
Without the steel the building wouldn't stand up, and large proportion of the total mass is steel presumably from a single supplier, but they don't have naming rights to the building.
It's part of the software layer between the hardware and the application layer. What else can it be called? Uncompress the tarfile of the source code for the kernel module that talks to it and compile. For a while there was no support for 2.4.*, but it's there now. If you want support for other than intel*86 hardware, then you have some source code to look at in the kernel module.Everyone that was using linux before the RMS bandwagon renaming thing had heard of gnu, and most had read the GPL, if only out of curiousity. The FSF is a very fine organisation, but they don't "own" linux, so why should they be able to force a new name down everyones throats? It's the sort of behavior you expect from rich annoying tourists, and not from the professional organisation that they have shown themselves to be.
If you take the line that the base distribution (as in Slackware "A" floppies without which nothing much can run) of linux is the OS, then GNU does not decide what goes into it. The Debian people do, or RedHat, or Slackware etc. Hence you get a distribution called Slackware Linux and not a distribution called gnu/linux.
GNU does not decide what goes into linux, so it is not gnu/linux.
My previous point was that there are parts of the linux kernel that GNU would never allow in their own OS if they had control. They don't, so it isn't theirs - it is linux with gnu tools. The whole gnu/linux naming thing is even more recent than the linux mascot, and was to increase the visability of gnu.
Also, isn't hurd an OS built on a mach kernel, or is it just a kernel? I thought it was the entire OS - correct me if I'm wrong.
There are parts of the Linux OS (eg. Nvidia binary module) which would NEVER be allowed in a GNU operating system
- therefore GNU does not have control of the development or implementation of the operating system
- therefore it is not a GNU operating sytem.
"Sheer mass of code" is not a valid argument in this case, things like gcc are not part of the OS, they are applications - they happen in userspace.
Check out Qt nethack for something he did years ago before he went to Troll - it's now been ported to the iPac.
Loco gringos!
In six years microsoft have gone from NT 4 to windows XP. It's not a particularly big jump in terms other than hardware support.
A similar thing should happen with a speaker, since the sound will resonate through the gas within the speaker cone.
If all the sound then follows the same path (through the same amount of helium) then it will sound OK. If some sound travels all of the way through air and some through helium and air, then there will be a noticable echo if (a) you are close to the speakers or (b) the helium filled bladders are really big.
If you shift the frequency of the sound down a bit (maybe with a bit of compression too) pumping the sound out of helium filled speakers shouldn't be a problem.
<RANT> If you are in a habit of calling every little or large utility part of the OS, (is gcc part of the OS? Be serious please) or even calling the shell part of the OS (eg. Internet Explorer) then there is a lot of stuff that is not part of the gnu project.
The whole attitude is summed up by this quote from RMS: "It's not like I'm asking for it to be called "Stallix"".
It's good to see that Linus is far less interested in the issue than I am - and I'm only interested because I'm sick of newbies "correcting" me every time I use the word linux on USENET (and hence killing the thread).</RANT>
The window manager is the interface.
X has been able to handle hardware accelerated OpenGL for some enormous length of time. I don't know when SGI were doing OpenGL on X, but I do know that it predated the game DOOM.
It's up to those who write the window managers to use the hardware via X drivers for their interfaces. That is how the 3D & accelerated games and apps do it. Projects such as "evas" provide a library to simplify this. "SDL" also does this.
For years it's been possible to have things like animated icons by continually animating the root window, and have your window manager put a transparent (empty) icon on top of the same size - but that is a nasty hack. you might want the root window (or the CPU for that matter) to do other stuff.
Berlin uses a different model - I don't know if it will even allow a choice of window managers. It's also more of a single user with no network access solution. It's to get around the "bloat" in X due to networking and security.Now we just need to be able to run dodgy shareware without it having admin permissions to the whole box.
A while back E could do this, but it can't anymore after the rewrite. Check out the "Oceanview" theme for E v0.15*, it was very cool.
Also I think at that time of the switch "certain interests" had never heard of gnome or Enlightenment - it was well before the fanfare of the gnome 1.0 release, and RedHat was almost the only company that was paying people to write linux applications.
Anyway, I'm not talking about something that happened last year or the year before - I think it happened early in the days of the 0.16 rewrite of E or late in the days of 0.15 and was dropped within a couple of months. If you can find the e-devel mailing list archeives you'll find more.
However, I believe the gnome people had purer motives and that they just wanted a window manager. Those that only wanted to try to teach Trolltech a lesson for having a different licence for Qt were in a (vocal) minority, and I believe they've moved on from gnome to something else now that only the code matters.
Anonymous also wrote:
Funding?RedHat gave Raster (the writer of Enlightenment) a job, which is a bit different to gnome funding anyone.
The gimp toolkit (gtk) has of course improved enormourly since then and is now cross platform. Athough, if something like thai language support in pango is broken, then it won't compile. It was an intersting exercise finding that I couldn't configure pango to leave it out and couldn't have gtk without pango.
The bit about Raster getting frustrated with his job was between him and an unprofessional middle manager at RedHat (who probably didn't last long) that hadn't quite worked out how to use email. It became very public because the guy didn't know how to use email.
Play with new versions of window managers that are in development. If they die on you you have nothing to lose but a single line in .xinitrc.
But beware - it is a good idea to start *nix up in text mode if you're going to use a window manager in development (or especially a video driver in development).
Why read less than ten books and take one exam so that you can call yourself an Engineer, when you can take another and call yourself a Microsoft Certified Surpreme Court Judge?
Someone I used to work with was at ground zero of a small hydrogen explosion in a university lab in Gothemburg, Sweden. He was in the middle of a roomfull of escaped hydrogen gas when it caught fire. He lost his eyebrows, but the fire did not burn long enough for his hair or clothes to stay alight. Apparently the force of the explosion was enough to dislodge bricks from the wall some distance away, so it was better for him to be inside the explosion and getting hit with the force from a small amount going up, than at the outer edge, where you get hit with everything between you and the centre.
Anyone why thought that gnome 1.0 was called that because it was stable (in was more unstable than many earlier releases) was sadly deluded. Lets keep the silly politics out of *nix.