fyi the site became unresponsive at about the time the load went above 200. then i tried to kill apache and mysqld. took a while. when that was done, load was at 516. and seriously, my load was at 5-10 _before_ getting slashdotted: i was tracking over 14000 bt peers.
Don't talk about better translations unless you can actually read the original text, which says "... mp3pro, which is improved for low bitrates, realaudio surround, the brand new windows media 9 beta,..." So you don't even compare the same pieces of text, but your worldlingo thing gets the context wrong, and the fish is clearly better.
Some Nokia cell phones include a variation of that game called Bantumi. The rules are slightly different, but the principle is the same. The computer's (phone's) gameplay is far from "perfect" though.
Actually I did this many years ago, as a small kid in school. Must have been around 1994 or so. Not with a laptop of course, but with one of those tiny (crappy) pocket computers. It could display one line of text on a lcd display and could be programmed in some variant of basic. It was a "sharp" if I remember correctly.
Anyway, my friend had one of those too, and we both took out the polarisation sheet from the lcd display and kept it somewhere in our pocket. We could write messages on the display, and nobody but us could see it. It was completely useless, but sorta fun. The polarisation sheet was small enough that it could be hidden in your hand and used without anyone noticing. Nobody understood what was going on (not that anyone really cared of course).
One of my biggest gripes with Linux is that
I can only assign directory or file access based on the user, group, world model. NT allows you to specify lists of
specific users.
Take a look at the implementation of POSIX Access Control Lists for Linux. It's a kernel patch that puts standardized ACLs into the Linux kernel (2.2 and 2.4) to allow setting very specific permissions for seperate files and directories. From the page:
Access Control Lists (ACLs) support more fine-grained permissions. Arbitrary users and groups can be granted or
denied access in addition to the three traditional classes of users.
This is probably very similar to the permissions on an NT system, and some other commercial Unix systems also implement those POSIX ACLs.
He's not talking about the actual game. Most games don't look like native Windows apps anyway, they come with their own user interface. Porting this isn't that hard. He's talking about the extras to a game, like level editors, that use MFC, and hence look like the usual Windows app. For those you could use "cheat" wrappers, which would make them look like Windows apps in Linux.
All we do guarantee is that your link to the server and the
links connecting the servers will be encrypted and that we are trying our best to ensure that all of the servers are
secure.
Ok, but who guarantees me that the administrators of the IRC servers don't modify the ircd source so that they can listen on my conversations? After all, only the links are encrypted, but the ircd still gets to see all traffic in plaintext.
It's good to see an IRC network with fully encrypted links, but I still wouldn't want to use it to "exchange sensitive information", because if I don't want to trust sniffers, I also don't want to trust IRC admins. For that, client-to-client encryption is needed.
Has anyone else noticed how the power consumption, heat production and size of those modern "microprocessors" slowly reaches the level of ENIAC-type of computers?
1. Earlier platforms generally had no CD-ROM.
Install via NFS or on a pre-formatted hard disk with all the necessary files. Been there, done that.
2. Earlier machines usually had a 5 1/4" floppy disk, until the late 486s started really using 3.5" floppies.
You can boot from a 5.25 floppy disk as well as from a 3.5 one. Besides from booting for the installation, there is no need at all for a floppy drive.
3. Earlier machines had RAM limitations
Many old 3/486s can use up to 16 or even 32 MB RAM. That's more than enough for a small (slow) home-sized server. Even 8 MB does the job.
4. Some earlier machines had fscked BIOSes, aside from Y2K-unfriendly BIOSes
Y2k is only an issue during boot-up, after that you can set the system's time to whatever you want. From what I've seen, Linux deals better with really old motherboards than some brand new ones.
5. Earlier machines had ISA, EISA, etc. Oh, what, you want to run GNU/Linux in something other than CGA?
There are very good SVGA cards for ISA, although running XFree with a "modern" window manager on such an old box is suicide. However, any kind of video card does the job for a "server" type of computer.
6. Earlier network cards are not all supported to get around many of these limitations
Granted, very old ISA cards might not work well, but many cards do. NE2000, old 3Com cards? No problem, work fine, and deliver good speeds too.
To make a long story short, killing support for old systems is a Bad Thing IMHO, and isn't necessary either, it would only make the kernel tarball smaller. I'm all for conditional compiles, and I actually wondered why some of the kernel patches out there (like the openwall patch) haven't been put into the mainstream kernel as 'make config' option. If they can put in accelerator thingies for Apache, why not this?
Slashdot Mirror
actually, we're now getting slashdotted AND dos'd at the same time. now THAT's some good fun.
the link is gone so its back now.
very funny :P
fyi the site became unresponsive at about the time the load went above 200. then i tried to kill apache and mysqld. took a while. when that was done, load was at 516. and seriously, my load was at 5-10 _before_ getting slashdotted: i was tracking over 14000 bt peers.
thanks for raping my site :)
Don't talk about better translations unless you can actually read the original text, which says "... mp3pro, which is improved for low bitrates, realaudio surround, the brand new windows media 9 beta, ..." So you don't even compare the same pieces of text, but your worldlingo thing gets the context wrong, and the fish is clearly better.
Some Nokia cell phones include a variation of that game called Bantumi. The rules are slightly different, but the principle is the same. The computer's (phone's) gameplay is far from "perfect" though.
Actually I did this many years ago, as a small kid in school. Must have been around 1994 or so. Not with a laptop of course, but with one of those tiny (crappy) pocket computers. It could display one line of text on a lcd display and could be programmed in some variant of basic. It was a "sharp" if I remember correctly.
Anyway, my friend had one of those too, and we both took out the polarisation sheet from the lcd display and kept it somewhere in our pocket. We could write messages on the display, and nobody but us could see it. It was completely useless, but sorta fun. The polarisation sheet was small enough that it could be hidden in your hand and used without anyone noticing. Nobody understood what was going on (not that anyone really cared of course).
Memories...
Rupert
victim of my own stupidity.. i mean
echo "</i>" >> story
Nope, didn't try it (wouldn't really need it), I only saw the announcement on Freshmeat. ;)
One of my biggest gripes with Linux is that I can only assign directory or file access based on the user, group, world model. NT allows you to specify lists of specific users.
Take a look at the implementation of POSIX Access Control Lists for Linux. It's a kernel patch that puts standardized ACLs into the Linux kernel (2.2 and 2.4) to allow setting very specific permissions for seperate files and directories. From the page:
Access Control Lists (ACLs) support more fine-grained permissions. Arbitrary users and groups can be granted or denied access in addition to the three traditional classes of users.
This is probably very similar to the permissions on an NT system, and some other commercial Unix systems also implement those POSIX ACLs.
put an there. Thanks
He's not talking about the actual game. Most games don't look like native Windows apps anyway, they come with their own user interface. Porting this isn't that hard. He's talking about the extras to a game, like level editors, that use MFC, and hence look like the usual Windows app. For those you could use "cheat" wrappers, which would make them look like Windows apps in Linux.
All we do guarantee is that your link to the server and the links connecting the servers will be encrypted and that we are trying our best to ensure that all of the servers are secure.
Ok, but who guarantees me that the administrators of the IRC servers don't modify the ircd source so that they can listen on my conversations? After all, only the links are encrypted, but the ircd still gets to see all traffic in plaintext.
It's good to see an IRC network with fully encrypted links, but I still wouldn't want to use it to "exchange sensitive information", because if I don't want to trust sniffers, I also don't want to trust IRC admins. For that, client-to-client encryption is needed.
Has anyone else noticed how the power consumption, heat production and size of those modern "microprocessors" slowly reaches the level of ENIAC-type of computers?
Let me clear up a few things here.
1. Earlier platforms generally had no CD-ROM.
Install via NFS or on a pre-formatted hard disk with all the necessary files. Been there, done that.
2. Earlier machines usually had a 5 1/4" floppy disk, until the late 486s started really using 3.5" floppies.
You can boot from a 5.25 floppy disk as well as from a 3.5 one. Besides from booting for the installation, there is no need at all for a floppy drive.
3. Earlier machines had RAM limitations
Many old 3/486s can use up to 16 or even 32 MB RAM. That's more than enough for a small (slow) home-sized server. Even 8 MB does the job.
4. Some earlier machines had fscked BIOSes, aside from Y2K-unfriendly BIOSes
Y2k is only an issue during boot-up, after that you can set the system's time to whatever you want. From what I've seen, Linux deals better with really old motherboards than some brand new ones.
5. Earlier machines had ISA, EISA, etc. Oh, what, you want to run GNU/Linux in something other than CGA?
There are very good SVGA cards for ISA, although running XFree with a "modern" window manager on such an old box is suicide. However, any kind of video card does the job for a "server" type of computer.
6. Earlier network cards are not all supported to get around many of these limitations
Granted, very old ISA cards might not work well, but many cards do. NE2000, old 3Com cards? No problem, work fine, and deliver good speeds too.
To make a long story short, killing support for old systems is a Bad Thing IMHO, and isn't necessary either, it would only make the kernel tarball smaller. I'm all for conditional compiles, and I actually wondered why some of the kernel patches out there (like the openwall patch) haven't been put into the mainstream kernel as 'make config' option. If they can put in accelerator thingies for Apache, why not this?