Indeed, I wonder why the LSB or someone else doesn't come up with a cross-distribution way to manage such ABI transitions so that we can keep both sets of libraries around with a Soname that corresponds to the ABI version.
Kund of. For the analogy to be complete, every Unix vendor would have had to proclaimed Linux as the One True Replacement, and dropped their existing products in favour of it.
UT2004 is the best commercial Linux program I've come across in this regard.
Most of the ones I have have broken in the years since their release because they statically linked against Glibc. While this works in theory, when the binary is run on a system with a newer Glibc it will segfault as soon as the program tries to do something involving loading a dynamic module (eg, using networking functions).
all kinds of features in the libc (locale (through iconv), NSS, IDN,...) require dynamic linking to load the appropriate external code. We have very limited support for doing this in statically linked code. But it requires that the dynamically loaded modules available at runtime must come from the same glibc version as the code linked into the application. And it is completely unsupported to dynamically load DSOs this way which are not part of glibc.
This is the reason that, Civ: Call To Power segfaults when I try to play a network game.
So, if you are developing/porting a closed source on/to Linux, please please please be careful about which libs you link to statically, and which you link to dynamically. You should always link dynamically to Glibc.
Whether you build other libraries into your binary should depend on how stable they are, and how likely they are to exist in ten years time. Backwards-compatible versions of libs like Glib or GTK will be around forever; the Sonames of their most recent versions (2.6/2.8) are still at 2.0 and show no sign of changing soon; and the older version of the libraries, with Soname 1.2, are still provided by every distribution.
Users of UT2004, Doom 3, HLDS and every other closed source program written with C++ have something else to worry about: the upcoming GCC 4.0 ABI transition. GCC 4.0 changes the C++ ABI from version 102 to version 1002; once your distro recompiles with the new ABI, any program dynamically linking to a C++ library will stop working.
UT2004/Doom 3 are certainly safe, since they are actively maintained; but no one will recompile Civ CTP, HLDS and other unmaintained programs.:(
I think the AC meant that OS X wouldn't have got very far without the history/legacy/support of all the Mac OS = 9 users who adopted it. Without the momentum from those users OS X would have sunk like a copy of BeOS.
No, the 400,000 are freed up by being released from their jobs. They can now invest their time in inventing new things, creating new businesses, sources of wealth, etc.
Look at the HD players from Xclef. I got the HD-500 (40 gigs) 18 months ago and can do nothing but recommend it.
I had two problems with it: it didn't play Ogg Vorbis files until last month when they released a firmware update that made it work (I was super-chuffed by that, wow!); and it's ugly (I don't see a firmware patch fixing that any time soon).
The barrier to entry for providing cable services is too high. The cable companies want to keep it that way--why else are they so anxious to outlaw municipal wifi?:)
Slashdot Mirror
Meh, that's the price you pay for using an unstable and unstandardised language.
Reading the Debian transition plan I see that LSB 3 intends to stabilise the C++ ABI at version 2 (the one used by GCC 3.4 and above, I think).
Go away and read The Case for Mars.
Indeed, I wonder why the LSB or someone else doesn't come up with a cross-distribution way to manage such ABI transitions so that we can keep both sets of libraries around with a Soname that corresponds to the ABI version.
libstdc++.so.6 -> libstdc++.so.6.0.3
libstdc++.so.6c1002 -> libstdc++.so.6.0.3c1002
Anyone?
Kund of. For the analogy to be complete, every Unix vendor would have had to proclaimed Linux as the One True Replacement, and dropped their existing products in favour of it.
UT2004 is the best commercial Linux program I've come across in this regard.
Most of the ones I have have broken in the years since their release because they statically linked against Glibc. While this works in theory, when the binary is run on a system with a newer Glibc it will segfault as soon as the program tries to do something involving loading a dynamic module (eg, using networking functions).
From Static Linking considered harmful:
This is the reason that, Civ: Call To Power segfaults when I try to play a network game.
So, if you are developing/porting a closed source on/to Linux, please please please be careful about which libs you link to statically, and which you link to dynamically. You should always link dynamically to Glibc.
Whether you build other libraries into your binary should depend on how stable they are, and how likely they are to exist in ten years time. Backwards-compatible versions of libs like Glib or GTK will be around forever; the Sonames of their most recent versions (2.6/2.8) are still at 2.0 and show no sign of changing soon; and the older version of the libraries, with Soname 1.2, are still provided by every distribution.
Users of UT2004, Doom 3, HLDS and every other closed source program written with C++ have something else to worry about: the upcoming GCC 4.0 ABI transition. GCC 4.0 changes the C++ ABI from version 102 to version 1002; once your distro recompiles with the new ABI, any program dynamically linking to a C++ library will stop working.
UT2004/Doom 3 are certainly safe, since they are actively maintained; but no one will recompile Civ CTP, HLDS and other unmaintained programs. :(
I think the AC meant that OS X wouldn't have got very far without the history/legacy/support of all the Mac OS = 9 users who adopted it. Without the momentum from those users OS X would have sunk like a copy of BeOS.
No, the 400,000 are freed up by being released from their jobs. They can now invest their time in inventing new things, creating new businesses, sources of wealth, etc.
You really should stop relying on Fox News for all your information.
Look at the HD players from Xclef. I got the HD-500 (40 gigs) 18 months ago and can do nothing but recommend it.
I had two problems with it: it didn't play Ogg Vorbis files until last month when they released a firmware update that made it work (I was super-chuffed by that, wow!); and it's ugly (I don't see a firmware patch fixing that any time soon).
Get Process Explorer from sysinternals. You can use it to close any file handle that a process has open.
setfacl and friends.
1989 called. They want their copy of the Unix Haters' Handbook back.
So then, where's the news?
Anyone know the key of the setting to disable this?
They'd just lobby to get the politicians who are making trouble for them replaced with more... agreeable alternatives.
I'm pretty sure you can adjust your security policy to disallow untrusted activex downloads, along with a lot of other crap.
Maybe this is a dupe that didn't hit the front page first time around.
Talk about follow the Javascript trail... why can't sites just serve up a nice Object tag with the url of the data!
It is the job of the browser to choose a plugin; its idea of the association between plugins and MIME types is always correct.
Hardcoding the associations in Javascript is retarded; how is the web developer supposed to know this information better than my browser?
For real? Please provide a link if so :)
Tribes died when Sierra canned Tribes 2. This is news? :)
I assumed that "The X Window System" was correct (or at least American) English.
This never made sense to me until I realised that it's just a window system called X. Compare to the W Window System, the Dave Window System, etc.
The only real fix is to go back in time and make them pick a better name.
How will a critical mass of people ever walk away, if stories such as this one aren't around to make them aware of the issues involved?
The barrier to entry for providing cable services is too high. The cable companies want to keep it that way--why else are they so anxious to outlaw municipal wifi? :)
Not yet. :( I looked into doing it myself a few months ago, but I don't really know enough about stats to make an accurate prediction.