hmm, everyone else on this article seems to be saying contradictory stuff to what i was told (i.e. FTP cracked, no GPG sums, wu-ftp was the vulnerability). i am beginning to wonder how much FUD is really floating around in the talkbacks. after all: the submitter didnt even give us any evidence and all i have to go on are the few emails i had from a spokeperson for the webserver a few days ago.
i'd love to hear an offical response from the FSF, wouldnt you all?
i emailed FSF a few days ago about about missing links on the main www.gnu.org webpage; the response was that the webserver had been cracked. i asked about FTP, but i was told that they didnt think it was compromised and i was given a GPG signed list of md5sums from before and after the incident, compared and nothing had changed (bar obviously the ones in this article).
this is quite worrying, i undertand it was the ssh v1 crack (probably some script kiddy inspired by the matrix reloaded) and i was told that savannah (which currently used ssh v1 for cvs commits) will be upgraded to ssh v2 in the near future.
damn, i was gonna commit this story:-), but didnt have any more news besides the emails i got.
the article was a troll against the FSF, and luckily for us, the slashdot crowd are not all trollbait: so some of us actually read the articles and get the facts right. the submitter wrote the post in a very FSF-is-angry light, when that is the opposite of what the README file actually says.
I very much doubt FSF will ever pull the plug on SCO support. if personal opinions have ever been a reason to stop support of an OS, then win32 would not have been supported a long time ago...
yes, and the gtk/gnome developers would agree with you. thats is because gtk-1.2 has been pretty much deprecated for about 3 years now. please use gtk-2.2. it is far from ugly and has much greater cross-platform and cross-nationality support than any other GUI lib i have ever encountered.
It stops short of demanding that GCC developers strip SCO support from the compiler, and says more will be announced before the next compiler release.
did the submitter even read the README?? it says no such thing, and i quote:
"We have been urged to drop support for SCO Unix from this release of
GCC...snip...
we have decided not to take that action. The Free Software Foundation's overriding goal is to protect the freedom of the free software
community, including developers and users"
its actually a big farce... the further south you go in Ireland, the better the Guinness tastes; but only because the water gets creamer the more southerly you go, and any lardlord (worth their weight in piss) waters down their beers. hence creamier Guinness in Cork, and tangy crisp in Belfast.
i can only tell you by experience, that its just not the same if you're not in ireland. i wont even drink scottish Guinness. a lot of it has to do with how the pint is poured (people drinking it and the drink is moving throught the pipes very frequently; poured in two stages then left to settle). it is a myth that Guinness is a hard pint to pull, it is actually thr easiest, it just takes a little longer; just like any stout should.
it is made in almost every country in the world now granted, but i guarantee you the stuff i drink comes from St. James gate, Dublin.
i had Namibian-brewed Guinness once (in South Africa), and lets just say that although Namibia was the first country to recycle their toilet water, they were not the first to get it right... yuck!
hmm, whats to stop anyone making one of these things and kitting it out with an explosive or biological warhead? can radars pick these things out as being targets without seagulls etc. raising false alarms?
it is being constantly worked on, and i think it is a lot more powerful than you think;-)
ASAIK and have experienced, it completes most filetypes, when you have given the program. e.g. play will only expand audio files, xine will only expand movies. check it out again. add in the power of readline (~/.inputrc) [mayeb zsh uses this? i dunno] and i dont know why anyone would want anythign else! but hey, alternative shells is a good idea; good things in zsh will be ported to bash eventually and we all benefit. thats the wonder of free software.
it is a great idea, and i went from mandrake->LFS for the exact reasons you say. i think the mandrake implementation is just a little shakey, thats all. i haven't had a single stability problem with it since setting it up on LFS. in fact, "ls/dev" to see what is loaded is a very nice extra to having devfs./dev is actually viewable in a single screen with devfs:-D!
its gone in 2.6 is it not? i also agree with the chmod stuff... but, chmod DOES work as a temporary solution. i mean; you set the default settings in/etc/devfs.conf like you say, eg
but from then on you can change permissions on the fly using chmod. the only bad point about this is... if you unload, say, the sound card drivers; when you reload them you get the default permissions and not the ones you just told/dev/dsp to have with chmod. that sucks when you are trying to give a device to the owner of the console, and you want to have a cron job cleanup your unused modules every few hours:-(
the reason why you put the filename first is becuase that is what -f is! you have TOLD it to act this way. tar kicks ass in syntax, just compare it with zip...
-f, --file=ARCHIVE use archive file or device ARCHIVE
with regards your zsh comment: you want to get this ripping in bash;-)
does exactly what you want.
the tar thing, i dunno... it makes sense on the command line, but not in pipes. if you pipe a file to tar, its a massive overhead to have to check what kind of compression is being used (you cant do a regex on the filename in this scenario). i actually like it the way it is. and come on... its just ONE extra letter on the command line to let tar know its been compressed.
unfortunately ebay is the only way to go in the UK for older games like this; the bigger stores like virgin and hmv are mostly sold out of the lucasarts bundles, but you might get lucky in some stores.
its to alert the community to the fact that Revolution Software are freeware-ing a lot of older titles: Beneath a Steel Sky and Lure of the Temptress now, hopefully Broken Sword 1&2 next (i have the first one, but cross-platform support woudl kick ass). Hopefully, other software houses will (under the persuation of/. folk) follow, and maybe even be able to cash in on it. it has already been mentioned that Lucasarts could bundle all their older stuff on a CD using modern compression (ogg and mp3) with ScummVM and make a fortune, whilst making us all smile.
i know I'll be buying Broken Sword 3, if only to support Revolution Software for their kind act.
go read the GPL. the change to gcc was most likely a trivial one (and not needed to be submitted back to the community; although commonly done as a gesture of goodwill), a bugfix perhaps.
if it cannot be compiled by another c compiler, its probably because it is not ANSI/ISO C, not becuase you dont have changes to the compiler source.
besides the changes are for fixes to the driver code, which isn't GPL.
well, is it really a compiler then? it breaks ANSI/ISO standards and not only will this piss off 3rd parties; i suppose it could probably be argued that the compiler is a "compliment" to the executable (as documented in the GPL) and changes must therefore be submitted.
in this case, the gcc changes are related to the binary driver, so it does not make sense to try and exploit a possible loophole, i suspect it is most likely just a gcc bugfix, and that it was most likely submitted to the gcc team for future releases so that Linksys (and 3rd parties) dont have to add maintaing gcc to their list of things to do.
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. (emphasis mine)
have you checked the gcc archives to see if this change in gcc was sent to them? they dont need to do that, but i suspect they did, so that they dont need to patch future gcc versions. a lot of commerical companies use gcc, and a lot of the bug fixes are performed by those compaines and sent back to the gcc team. even apple build MacOS with gcc.
who modded this "overrated"?? parent makes a good point... the changes can be made with configure parameters to the vanilla tree. if this kind of trivial change is the only accused modification of GPL'ed code, then whoever made the complaint ought to retract their argument and apologise to Linksys for public embarressment.
Slashdot Mirror
http://ftp.gnu.org/MISSING-FILES.README
i'd love to hear an offical response from the FSF, wouldnt you all?
this is quite worrying, i undertand it was the ssh v1 crack (probably some script kiddy inspired by the matrix reloaded) and i was told that savannah (which currently used ssh v1 for cvs commits) will be upgraded to ssh v2 in the near future.
damn, i was gonna commit this story :-), but didnt have any more news besides the emails i got.
if all the "stolen" code relates to multi-processing, then why do SCO feel they can license linux running on single processor machines?
I very much doubt FSF will ever pull the plug on SCO support. if personal opinions have ever been a reason to stop support of an OS, then win32 would not have been supported a long time ago...
yes, and the gtk/gnome developers would agree with you. thats is because gtk-1.2 has been pretty much deprecated for about 3 years now. please use gtk-2.2. it is far from ugly and has much greater cross-platform and cross-nationality support than any other GUI lib i have ever encountered.
did the submitter even read the README?? it says no such thing, and i quote:
i can only tell you by experience, that its just not the same if you're not in ireland. i wont even drink scottish Guinness. a lot of it has to do with how the pint is poured (people drinking it and the drink is moving throught the pipes very frequently; poured in two stages then left to settle). it is a myth that Guinness is a hard pint to pull, it is actually thr easiest, it just takes a little longer; just like any stout should.
it is made in almost every country in the world now granted, but i guarantee you the stuff i drink comes from St. James gate, Dublin.
i had Namibian-brewed Guinness once (in South Africa), and lets just say that although Namibia was the first country to recycle their toilet water, they were not the first to get it right... yuck!
its spelt "guinness": and how many times do we have to tell you bloody foreigners... IT DOESNT TRAVEL!!! ;-)
hmm, whats to stop anyone making one of these things and kitting it out with an explosive or biological warhead? can radars pick these things out as being targets without seagulls etc. raising false alarms?
this guy has applied the patch to preprocessor definitions! yippee: unnecessary-breakage-of-source-compatibiity goodness
does zsh expand out hostnames when you are sshing places? or the command line options of a program when you type, for example
it is being constantly worked on, and i think it is a lot more powerful than you think ;-)
ASAIK and have experienced, it completes most filetypes, when you have given the program. e.g. play will only expand audio files, xine will only expand movies. check it out again. add in the power of readline (~/.inputrc) [mayeb zsh uses this? i dunno] and i dont know why anyone would want anythign else! but hey, alternative shells is a good idea; good things in zsh will be ported to bash eventually and we all benefit. thats the wonder of free software.
it is a great idea, and i went from mandrake->LFS for the exact reasons you say. i think the mandrake implementation is just a little shakey, thats all. i haven't had a single stability problem with it since setting it up on LFS. in fact, "ls /dev" to see what is loaded is a very nice extra to having devfs. /dev is actually viewable in a single screen with devfs :-D!
the reason why you put the filename first is becuase that is what -f is! you have TOLD it to act this way. tar kicks ass in syntax, just compare it with zip...
does exactly what you want.
the tar thing, i dunno... it makes sense on the command line, but not in pipes. if you pipe a file to tar, its a massive overhead to have to check what kind of compression is being used (you cant do a regex on the filename in this scenario). i actually like it the way it is. and come on... its just ONE extra letter on the command line to let tar know its been compressed.
unfortunately ebay is the only way to go in the UK for older games like this; the bigger stores like virgin and hmv are mostly sold out of the lucasarts bundles, but you might get lucky in some stores.
i know I'll be buying Broken Sword 3, if only to support Revolution Software for their kind act.
if it cannot be compiled by another c compiler, its probably because it is not ANSI/ISO C, not becuase you dont have changes to the compiler source.
besides the changes are for fixes to the driver code, which isn't GPL.
even though i just pointed out to you in another posting that "compiler" is defined explicitly in that section of the GPL...
in this case, the gcc changes are related to the binary driver, so it does not make sense to try and exploit a possible loophole, i suspect it is most likely just a gcc bugfix, and that it was most likely submitted to the gcc team for future releases so that Linksys (and 3rd parties) dont have to add maintaing gcc to their list of things to do.
ok, look here then or if you are too lazy, then i quote
have you checked the gcc archives to see if this change in gcc was sent to them? they dont need to do that, but i suspect they did, so that they dont need to patch future gcc versions. a lot of commerical companies use gcc, and a lot of the bug fixes are performed by those compaines and sent back to the gcc team. even apple build MacOS with gcc.
well, thats your interpretation, not the stance of the FSF, GCC or more importantly what is stated in the GPL.
calling the legendary gcc "a script" is just plain offensive.
who modded this "overrated"?? parent makes a good point... the changes can be made with configure parameters to the vanilla tree. if this kind of trivial change is the only accused modification of GPL'ed code, then whoever made the complaint ought to retract their argument and apologise to Linksys for public embarressment.