Most Eee PCs have two SSDs: a large, slow one and a small fast one. Firefox became a lot snappier once I moved my profile directory to the fast SSD. Obvious in retrospect, I know...
So, the hosts asks for a copy of the registration records with the Copyright Office. That's stupid but it's not an impossible request. Record label dude can't give records because the copyright isn't registered. Fair enough. What I don't get is why record label dude doesn't simply register the music and say the registration is being processed? That makes a lot more sense than blathering about Creative Commons, and it's actually helpful if there ever are real legal problems.
They've invested a crazy amount of money in technologies customer's don't care for (3G, all the different ways to get the Web on phones), so now they have to charge a lot for the two things people actually use (SMS and ringtones).
1. Emacs predates the Lisp machines, it was originally developed for the MIT mainframes (in TECO, with TECO as an extension language). GNU Emacs has its origins mostly in Multics Emacs, a port to a different mainframe/OS, both the first Emacs implemented in Lisp and the first Emacs extended using Lisp (also the only standard Multics program using Lisp:). The influence of actual Lisp Machine Emacsen on GNU Emacs is rather limited (remember that Stallman wasn't a big fan of the commercial Lisp companies!).
Of course, none of these systems were even remotely Unix-like, so you're entirely correct that Emacs doesn't care about the Unix philosophy:)
2. mg predates OpenBSD (it dates from the eighties, based on MicroEMACS), though the version in OpenBSD is probably the only maintained one. It isn't very Unixy: no regular expression search/replace, no filtering text through pipes (both of these are pretty much defining for the Unix philosophy). It's just as much Emacs as you could get in a 16-bit micro:) (And I don't think most Emacs users would have too much trouble with it: it only implements a tiny subset of the GNU Emacs commands, but it gets them right.)
Most of the big group releases do NOT have Trojans and other crap inserted. the big release groups pride themselves in having a clean release.
Right, but he's not talking about big release groups. He's talking about cd's sold on Cambodian markets. I can quite imagine one of those vendors wanting to operate a spam network on the side.
One irony of the situation is that Debian itself has the same problem with their branding: if you modify the distribution, you can't call it Debian any more.
It should be noted that many Debian developers consider their trademark policy to be flawed, although nobody really knows how to fix it.
Former DPL Branden Robinson discusses some of the issues in this article.
If I understand this correctly, the principal problem is not Google News but rather Google Cache. It seems that when news articles move from public to subscriber-only, Google retrieved the contents from its cache, instead of removing the article. So the issue was that Google was distributing articles instead of only linking them.
Can anybody explain why SourceForge's mail archive uses such freaking huge text? This can't be what SourceForge's web designers intended, but I don't have this problem on any other website, so I doubt it is a local problem.
This is only going to work if you're using SuSE. And if you don't compile your own kernel. It only gives vendors an excuse to call their shitty binary-only drivers "Linux support". I'd call this thing a Linux driver setback.
As far as I can tell, its main "feature" seems to be support for various legacy stuff: 16 bit platforms, OS/2, DOS, etc. And some people probably like the IDE.
And C++ doesn't have exceptions and stuff? Java is just as insecure as C/C++. It's just insecure in different ways.
I'd like to see one of those kernel-based systems make a C++ program throw an exception. Well, I guess signalling SIGSEGV kind of counts.
As others have said, most bugs and security flaws come from lazy programmers not doing the right thing.
You say that as if doing proper manual memory management is easy. It's not: that has been sufficiently demonstrated over the past few decades. Since automatic memory management is possible and cheap, it stupid not to use it.
I'd also like to see you run Java in a lightweight embedded DSP situation!
While current Java environments don't optimise for speed (instead relying on fancy JVM's), there's no reason why you couldn't compile Java to efficient machine code.
Yes, fancy tricks as PaX and ProPolice can turn remote root attacks into 'only' a denial of service (your daemon gets killed). That's definitely an improvement.
I'm no fan of Java, but at least it gives your program a chance to recover (exceptions and stuff).
Slashdot Mirror
Here's a public link to the article.
Computer crimes used to be prosecuted as "theft of electricity".
Most Eee PCs have two SSDs: a large, slow one and a small fast one. Firefox became a lot snappier once I moved my profile directory to the fast SSD. Obvious in retrospect, I know...
So, the hosts asks for a copy of the registration records with the Copyright Office. That's stupid but it's not an impossible request. Record label dude can't give records because the copyright isn't registered. Fair enough. What I don't get is why record label dude doesn't simply register the music and say the registration is being processed? That makes a lot more sense than blathering about Creative Commons, and it's actually helpful if there ever are real legal problems.
I would be very surprised if Windows 7 is anything other than Vista SP2.
Thanks.
Which supermarket was that? I completely missed it.
Comeau C++ + Dinkumware is pretty damn close to standard C++. It certainly supports "export".
They've invested a crazy amount of money in technologies customer's don't care for (3G, all the different ways to get the Web on phones), so now they have to charge a lot for the two things people actually use (SMS and ringtones).
Linux market share has increased by 117%, while Apple's increase is only 74%.
A few historical notes:
:). The influence of actual Lisp Machine Emacsen on GNU Emacs is rather limited (remember that Stallman wasn't a big fan of the commercial Lisp companies!).
:)
:) (And I don't think most Emacs users would have too much trouble with it: it only implements a tiny subset of the GNU Emacs commands, but it gets them right.)
1. Emacs predates the Lisp machines, it was originally developed for the MIT mainframes (in TECO, with TECO as an extension language). GNU Emacs has its origins mostly in Multics Emacs, a port to a different mainframe/OS, both the first Emacs implemented in Lisp and the first Emacs extended using Lisp (also the only standard Multics program using Lisp
Of course, none of these systems were even remotely Unix-like, so you're entirely correct that Emacs doesn't care about the Unix philosophy
2. mg predates OpenBSD (it dates from the eighties, based on MicroEMACS), though the version in OpenBSD is probably the only maintained one. It isn't very Unixy: no regular expression search/replace, no filtering text through pipes (both of these are pretty much defining for the Unix philosophy). It's just as much Emacs as you could get in a 16-bit micro
Most of the big group releases do NOT have Trojans and other crap inserted. the big release groups pride themselves in having a clean release. Right, but he's not talking about big release groups. He's talking about cd's sold on Cambodian markets. I can quite imagine one of those vendors wanting to operate a spam network on the side.
Wow, just like rss2email!
One irony of the situation is that Debian itself has the same problem with their branding: if you modify the distribution, you can't call it Debian any more.
It should be noted that many Debian developers consider their trademark policy to be flawed, although nobody really knows how to fix it. Former DPL Branden Robinson discusses some of the issues in this article.
If I understand this correctly, the principal problem is not Google News but rather Google Cache. It seems that when news articles move from public to subscriber-only, Google retrieved the contents from its cache, instead of removing the article. So the issue was that Google was distributing articles instead of only linking them.
Can anybody explain why SourceForge's mail archive uses such freaking huge text? This can't be what SourceForge's web designers intended, but I don't have this problem on any other website, so I doubt it is a local problem.
This is only going to work if you're using SuSE. And if you don't compile your own kernel. It only gives vendors an excuse to call their shitty binary-only drivers "Linux support". I'd call this thing a Linux driver setback.
Frankly, I'm amazed so many people looked beyond the first page.
Linking to a wiki on the slashdot front page is a not a good idea :)
As far as I can tell, its main "feature" seems to be support for various legacy stuff: 16 bit platforms, OS/2, DOS, etc. And some people probably like the IDE.
I suggest that the field and the general user experience would be greatly enhanced by limiting access to compilers/assemblers
Hah! I shall SAVE THE WORLD with my carefully hidden away TURBO PASCAL 5.0 floppy!
And C++ doesn't have exceptions and stuff? Java is just as insecure as C/C++. It's just insecure in different ways.
I'd like to see one of those kernel-based systems make a C++ program throw an exception. Well, I guess signalling SIGSEGV kind of counts.
As others have said, most bugs and security flaws come from lazy programmers not doing the right thing.
You say that as if doing proper manual memory management is easy. It's not: that has been sufficiently demonstrated over the past few decades. Since automatic memory management is possible and cheap, it stupid not to use it.
I'd also like to see you run Java in a lightweight embedded DSP situation!
While current Java environments don't optimise for speed (instead relying on fancy JVM's), there's no reason why you couldn't compile Java to efficient machine code.Yes, fancy tricks as PaX and ProPolice can turn remote root attacks into 'only' a denial of service (your daemon gets killed). That's definitely an improvement.
I'm no fan of Java, but at least it gives your program a chance to recover (exceptions and stuff).
You're probably joking,
Yeah, you probably need a new sarcasm detector.
Will there be a Windows Driver? If there isn't, this has no chance on taking off.
Yes, that's why I only use FAT filesystems on my Linux server.