Slashdot Mirror

How about a program that compiles and runs in seven different languages?
http://www.nyx.net/~gthompso/poly/polyglot.txt

Or a program that prints its own source code?
http://www.nyx.net/~gthompso/quine.htm

Or just a whole collection of weird programming-related stuff?
http://www.catseye.mb.ca/

(OK, so I'm way too late to the party and nobody's going to read this, but hey :)

First off, I've posted my experiments with watercooling about a half dozen times on slashdot. It's old. It's been done. Nobody has considered any safety issues whatsoever. I am not an expert, so don't sue me if your machine, home, signifigant other, cat, and car erupt into flames. None of the commerical kits really detail how to do a professional installation. For most people, it is more work than you want to even THINK about. It took me a solid day of testing and another solid day of construction to get my kit installed.

http://www.nyx.net/~smanley/watercool

You need to install a GFCI to protect against a ground loop. If there is a short to ground, this will kill the power instantly. You MUST have one if you connect liquid to a mains supply, as most systems do.

Secondly, pure water is a insulator. Aren't YOU smart. Put it in an average watercooler for 15 minutes and you now have a very good conductor. Hella good, probably. In a few months, even better. Water isn't called the "universal solvent" for anything - it will pick up enough ions to be conductive from just about anything. Hint; you're running it though copper blocks in most cases, and the other surfaces aren't pristine.

There are many other precautions. I've run for almost a year without a problem, but I took my time. I am looking to watercoool my home games machine now, as I believe you can probably get away without any fan on the system whatsoever. The noise reduction IS worth it when the girlfriend gets bitchy that your desk is whining like a supercharged honda when she's trying to sleep - and it's down the hall! Heh.

Other experiments I'm thinking about include using a convection system that might stabilize at mid-50's C with no pump or fans whatsoever.

My $0.02..

Since the topic is disks it might be the time to point to the Multi Disk HOWTO (part of the LDP) that gives you the practical detail on how to make the most of your disk(s).

BTW one important topic that was not mentioned in earlier threads is that with SCSI disks you can be sure you have flushed a file from disk cache to platters but NOT on ATA drives. While this may sound banal, this is hugely important to database people in the event of crashes. Check up on the comp.arch.storage newsgroup for the sordid details. ATA pretends it flushes but does not in a guaranteed fashion, all in order to gain speed. Sure, it is OK for home use but not in business.

I've been running a reliable water cooled setup (including many moves, dropping upside down, upgrades, etc) for over 6 months now. It works great. I have install details written up for anyone who's interested. The noise went from deafening to a mild hum.

I'm currently gathering pieces for a passive watercooled setup (no fans) that handles cooling the video, system chip and processor. The power supply fan will be removed and replaced with a low-voltage 120mm top-mounted fan that runs silently with good airflow (for HD cooling as well).

Rather than mount the radiator inside the case, the radiator will be top mounted with a custom lexan mount. This moves the heat outside the system (closed box). In addition, the inside will be sound deadened with leftover Dynamat Extreme from my car stereo install. This should result in a cool looking, silent machine, with no compromises. It isn't going to be cheap though.

Also, for your masochistic programming pleasure, you may be interested in the polyglot list and the quine page.

For even more zany programming fun, check out Esoteric topics in Computer Programming. Oh, and my own pathetic attempt at a similar page, Miscreant Programming Languages.

Also, for your masochistic programming pleasure, you may be interested in the polyglot list and the quine page.

For even more zany programming fun, check out Esoteric topics in Computer Programming. Oh, and my own pathetic attempt at a similar page, Miscreant Programming Languages.

Also, for your masochistic programming pleasure, you may be interested in the polyglot list and the quine page.

For even more zany programming fun, check out Esoteric topics in Computer Programming. Oh, and my own pathetic attempt at a similar page, Miscreant Programming Languages.

check the following page for source code that can be used in many languages...

polyglots list

The only polyglot archive i am aware of on the whole internet

Everything2 entry on polyglots

For performance the short, short summary is that IDE wins in single threading IO due to small, low latency command overhead while SCSI wins out for multi threaded IO due to command queueing. Sure, it is in the IDE specs too these days but it is rarely implemented.

Check out the HOWTO and if you see a mistake do contact the autor, the LDT relies on feedback from you the readers and experts.

For performance the short, short summary is that IDE wins in single threading IO due to small, low latency command overhead while SCSI wins out for multi threaded IO due to command queueing. Sure, it is in the IDE specs too these days but it is rarely implemented.

Check out the HOWTO and if you see a mistake do contact the autor, the LDT relies on feedback from you the readers and experts.

I'm not sure why you think there needs to be a government mandated control of such a network. The whole point of the ISM band is that it's unregulated - but I'm pretty sure that the powers that be didn't expect 802.11 technology to be quite so sucessful. 802.11 is designed to be highly tolerant of noise, and I suspect the density can get quite high, either as it is now, or with a derivative technology.

How about another model? One were everyone, or a larger percentage of the community all get a commodity wireless access point and join up in a management framework, basically managed chaos, like the Sydney Wireless. I have a couple links on my community wireless page, too. With enough network overlap, you'd have pretty good coverage - maybe better than standard cell links. The bandwidth on these technologies is quite high, and 11mbit may only be the starting point.

But oh, what a world it might be if control of the communications medium - or, perhaps better phrased, control of A communications medium - went truely into the hands of the masses. I already know of two college campuses where students are running their own dorm networks to combat draconian policies on file sharing and gaming using 802.11. What if that ramped up to city wide? What if people start setting up their own WANs, and leasing their own fiber backbones? Or hell, even running their own fiber backbones, like has been done in Sweden?

Remeber BBSes? There was no tradegy of the commons there, and those formed pretty sophisticated networks towards the end. And no doubt caused a few LEOs to have kittens then..

I run a watercooled machine as my primary work box. It's great, and the noise savings were incredible. No more whirrrrrr. Fits snugly into a standard mid tower case.

I have a page up with all the details of contsruction for you who are interested. I've been running it for a few months, 24/7, and there have been no problems whatsoever. I took a few additional precautions, but the system as been moved around several times without any difficulties whatsoever and I highly recommend it to others who are interested.

The polyglot quines were on the polyglot page i linked, not the quine page i linked (both of which were on nyx.net..). The quine page was linked in case a given reader didn't know what a quine was. The C/LISP hybrid quine was the 10th entry on the polyglot page. It was this one.

Sorry if i was unclear.

Anyway, a few polyglot-related links:

• here is the only Polyglot archive anywhere on the internet that i am aware of. Please, please read this link. It's amazing. My favorite is i think the quine (!!) which is simultaneously valid in C and Scheme. (It exploits the fact that ; is a comment operator in scheme, and is a really neat little read..)
• Here is the only polyglot i'm aware of which is not in the above archive.
• Here's a short little writeup on polyglots i did for everything2.com. It isn't that interesting.

With the crazy-ass language redefinition capabilities in perl 6, i think we can expect to see a resurgence in some very odd polyglots very soon..

Grrr.. mean, mean slashdot editors.. telling us the IOCCC winners were announced just so we can wait in suspense for a full month to see the entries.. bleh. I love the IOCCC..

Anyway, a few polyglot-related links:

• here is the only Polyglot archive anywhere on the internet that i am aware of. Please, please read this link. It's amazing. My favorite is i think the quine (!!) which is simultaneously valid in C and Scheme. (It exploits the fact that ; is a comment operator in scheme, and is a really neat little read..)
• Here is the only polyglot i'm aware of which is not in the above archive.
• Here's a short little writeup on polyglots i did for everything2.com. It isn't that interesting.

With the crazy-ass language redefinition capabilities in perl 6, i think we can expect to see a resurgence in some very odd polyglots very soon..

Grrr.. mean, mean slashdot editors.. telling us the IOCCC winners were announced just so we can wait in suspense for a full month to see the entries.. bleh. I love the IOCCC..

They overlooked something that might be life saving, and that's the installation of a GFCI outlet. It's very easy to do, I built one for my watercooled machine on a extension cord. Without one, a (rare) but possible failure of the pump could mean that current decides to return to ground through you. Ouch.

For what it's worth, I run a custom watercooled setup that I managed to get squeezed completely inside a standard PC case. It works great, no problems. I still need intake/exhaust fans, though, and until I put an intelligent controller in it isn't that much quiter than a normal setup in a good case. It works a lot better though :).

Visit the quines page at http://www.nyx.net/~gthompso/quine.htm, it has source for self-printing programs in over 60 languages!

For anyone who's interested in watercooling a work/production machine, I had great results and gained a LOT of stabilty. Just be sure to install a GFCI on the outlet! The importance of this isn't mentioned in a lot of the commercial kits and could be a life-saving precaution.

The URL to the install, where I got it, how I managed to make it all fit inside a standard mid-tower case along with 4 hard drives and 2 cdroms, etc, can be found at: www.nyx.net/~smanley/watercool

Definately a great learning experience!

There are some good examples of quines (self-replicating programs) at http://www.nyx.net/~gthompso/quine.htm

Also, I like Esoteric Topics in Computer Programming

And corewars before that was the great-granddaddy.

Crobots original page

This kind of game came out 16 years ago as C-Robots.

Try Gray Scale Mosaic

http://www.nyx.net/~kpearson/distrib.html

I am running Genome@home now, and have designed over 40 genes! Its pretty neat for a biology nerd like myself. This Is a great collection of all known distributed computing projects. Neat ones are Golem@home and SaferMarkets and MoneyBee.

A user named "kpearson" has an excellent Distributed Computing compilation site from which you can see the latest news, view all completed projects, and visit the websites of any active project you may have an interest in.

So, if you don't trust a commercial company with your idle CPU cycles, look on the Active Projects list for something run by a non-profit org, or an educational facility. There's dozens of projects available to suit your particular cup of tea.

-Tex

A user named "kpearson" has an excellent Distributed Computing compilation site from which you can see the latest news, view all completed projects, and visit the websites of any active project you may have an interest in.

So, if you don't trust a commercial company with your idle CPU cycles, look on the Active Projects list for something run by a non-profit org, or an educational facility. There's dozens of projects available to suit your particular cup of tea.

-Tex

Or use Google

See : Nyx

This was a thread during the whole TiVo hacking topic. Jim Buzzbee was cool enough to post with a link to a wonderful individual who hacked together his own TiVo/Satalite reciever with full menus and even a remote. The plans are here. I really wanna make one if I can scrounge up the money!!

It was called nyx. And it looks like it's still around.

I remember stumbling across it from the public Gopher (remember Gopher?) server at the local university (Michigan State).

I don't know if it was around in '83, though.

(A quick stroll over to altavista tells me that it's still around as nyx.net. You can read the history. It started in '87 on a PDP11 and later migrated to a Pyramid.)

Given that the source isn't included, I can't help but wonder at what the code looks like

Just go up a level and you will find plenty of C++ and Eiffel code, along with Victor's notes including `Project Plan Summary', `Time Recording Log' `Defect Recording Log' for both C++/Eiffel versions. The previous link was just an Appendix.

given statements like In fact, Eiffel (by its use of copy-by-reference instead of by-value) could realize big wins over C++ , which shows an apparent unfamiliarity with C++ reference parameters, which can make huge differences in execution time with strings.

Victor has a strong background in C/C++ and has even developed game software that has brought in a little cash and the thrill of seeing my game on the "cheapware" racks at the local software store.

Eiffel is not for everyone, most can't even (and don't want to) read the Pascal/Ada syntax. The language landscape is incredibly competitive and it is just interesting to note that Eiffel has moved along with the rest. As I said in another post, SmallEiffel has added a new dimension to the Eiffel world. For most this doesn't matter, but at least we should know it exists.

• http://www.elj.com/eiffel/getting-started/doc/

From the Eiffel/C++ perspective, the following articles are worth a look:

• Eiffel for Native Speakers of C++
• The Eiffel Contract for C++ Programmers
  ( the application of Design by Contract in many contexts is also available)
• The Personal Software Process: Eiffel vs C++
  ( The results for compile time, Executable size and Executable speed may surprise a few!! SmallEiffel - The GNU Eiffel compiler - really adds a new dimension to the Eiffel World!! )

The Eiffel to C++ terminology mapping page is also worth a look.

• http://www.elj.com/eiffel/getting-started/doc/

From the Eiffel/C++ perspective, the following articles are worth a look:

• Eiffel for Native Speakers of C++
• The Eiffel Contract for C++ Programmers
  ( the application of Design by Contract in many contexts is also available)
• The Personal Software Process: Eiffel vs C++
  ( The results for compile time, Executable size and Executable speed may surprise a few!! SmallEiffel - The GNU Eiffel compiler - really adds a new dimension to the Eiffel World!! )

The Eiffel to C++ terminology mapping page is also worth a look.

• http://www.elj.com/eiffel/getting-started/doc/

From the Eiffel/C++ perspective, the following articles are worth a look:

• Eiffel for Native Speakers of C++
• The Eiffel Contract for C++ Programmers
  ( the application of Design by Contract in many contexts is also available)
• The Personal Software Process: Eiffel vs C++
  ( The results for compile time, Executable size and Executable speed may surprise a few!! SmallEiffel - The GNU Eiffel compiler - really adds a new dimension to the Eiffel World!! )

The Eiffel to C++ terminology mapping page is also worth a look.

• http://www.elj.com/eiffel/getting-started/doc/

From the Eiffel/C++ perspective, the following articles are worth a look:

• Eiffel for Native Speakers of C++
• The Eiffel Contract for C++ Programmers
  ( the application of Design by Contract in many contexts is also available)
• The Personal Software Process: Eiffel vs C++
  ( The results for compile time, Executable size and Executable speed may surprise a few!! SmallEiffel - The GNU Eiffel compiler - really adds a new dimension to the Eiffel World!! )

The Eiffel to C++ terminology mapping page is also worth a look.

char*f="char*f=%c%s%c;main()
{printf(f,34,f,34,10);}%c";
main(){printf(f,34,f,34,10);}

Check out the Intercal quine. It's the most painful piece of source I've ever seen (and I keep up with the ioccc).

--neil

Way back when I wrote a little java applet that did this. It was pretty easy. When loaded it just connected back to the server, port 25, and did a SMTP conversation. A header trace on the email would show that it indeed did originate on the box of the person viewing the page. I made the originator as root because I couldn't get the "real" user name. I still have the applet on-line, but it no longer really sends mail because my web server doesn't have a SMTP server running anymore. The source is here

Rather than pontificate here I'll rather direct you to some rather compreghensive documentation in the form of the Multi Disk HOWTO. It is part of the Linux Documentation Project but don't let that fool you, the HOWTO has examples of SunOS servers, practical implementations, clustering and more. It does look like what you are looking for.

There are guides, principles, a guided method and examples of several implementations. And if you need more you could try mailing the author

Rather than pontificate here I'll rather direct you to some rather compreghensive documentation in the form of the Multi Disk HOWTO. It is part of the Linux Documentation Project but don't let that fool you, the HOWTO has examples of SunOS servers, practical implementations, clustering and more. It does look like what you are looking for.

There are guides, principles, a guided method and examples of several implementations. And if you need more you could try mailing the author

At least one gives a rather in depth description of the issue, the Multi Disk HOWTO which is very much about tuning in general. It is way to big to quote here so I' rather suggest the interested readers look at the following chapters listed below (straight from the Multi Disk HOWTO homepage):

• disk drives and speed
• File System Features which even starts off discussing swap. Pay special attention to interleaving issues.
• Terms which gives more info on speed limitations and what speed really is
• Physical track positioningan old but still good technique
• Disk layout for general layout issues
• The need for swap
• An example setting using 4 interleaved swap partitions.
• Single drive swap positioning optimisation

Note that the swap partiotn limit in old kernels depends on the architecture of the processor, namely if it is a 32- or 64-bits processor.

If you have any comments to the HOWTO I hope you can take direct contact with the author so more people can benefit from your insight.

At least one gives a rather in depth description of the issue, the Multi Disk HOWTO which is very much about tuning in general. It is way to big to quote here so I' rather suggest the interested readers look at the following chapters listed below (straight from the Multi Disk HOWTO homepage):

• disk drives and speed
• File System Features which even starts off discussing swap. Pay special attention to interleaving issues.
• Terms which gives more info on speed limitations and what speed really is
• Physical track positioningan old but still good technique
• Disk layout for general layout issues
• The need for swap
• An example setting using 4 interleaved swap partitions.
• Single drive swap positioning optimisation

Note that the swap partiotn limit in old kernels depends on the architecture of the processor, namely if it is a 32- or 64-bits processor.

If you have any comments to the HOWTO I hope you can take direct contact with the author so more people can benefit from your insight.

At least one gives a rather in depth description of the issue, the Multi Disk HOWTO which is very much about tuning in general. It is way to big to quote here so I' rather suggest the interested readers look at the following chapters listed below (straight from the Multi Disk HOWTO homepage):

• disk drives and speed
• File System Features which even starts off discussing swap. Pay special attention to interleaving issues.
• Terms which gives more info on speed limitations and what speed really is
• Physical track positioningan old but still good technique
• Disk layout for general layout issues
• The need for swap
• An example setting using 4 interleaved swap partitions.
• Single drive swap positioning optimisation

Note that the swap partiotn limit in old kernels depends on the architecture of the processor, namely if it is a 32- or 64-bits processor.

If you have any comments to the HOWTO I hope you can take direct contact with the author so more people can benefit from your insight.

At least one gives a rather in depth description of the issue, the Multi Disk HOWTO which is very much about tuning in general. It is way to big to quote here so I' rather suggest the interested readers look at the following chapters listed below (straight from the Multi Disk HOWTO homepage):

• disk drives and speed
• File System Features which even starts off discussing swap. Pay special attention to interleaving issues.
• Terms which gives more info on speed limitations and what speed really is
• Physical track positioningan old but still good technique
• Disk layout for general layout issues
• The need for swap
• An example setting using 4 interleaved swap partitions.
• Single drive swap positioning optimisation

Note that the swap partiotn limit in old kernels depends on the architecture of the processor, namely if it is a 32- or 64-bits processor.

If you have any comments to the HOWTO I hope you can take direct contact with the author so more people can benefit from your insight.

At least one gives a rather in depth description of the issue, the Multi Disk HOWTO which is very much about tuning in general. It is way to big to quote here so I' rather suggest the interested readers look at the following chapters listed below (straight from the Multi Disk HOWTO homepage):

• disk drives and speed
• File System Features which even starts off discussing swap. Pay special attention to interleaving issues.
• Terms which gives more info on speed limitations and what speed really is
• Physical track positioningan old but still good technique
• Disk layout for general layout issues
• The need for swap
• An example setting using 4 interleaved swap partitions.
• Single drive swap positioning optimisation

Note that the swap partiotn limit in old kernels depends on the architecture of the processor, namely if it is a 32- or 64-bits processor.

If you have any comments to the HOWTO I hope you can take direct contact with the author so more people can benefit from your insight.

At least one gives a rather in depth description of the issue, the Multi Disk HOWTO which is very much about tuning in general. It is way to big to quote here so I' rather suggest the interested readers look at the following chapters listed below (straight from the Multi Disk HOWTO homepage):

• disk drives and speed
• File System Features which even starts off discussing swap. Pay special attention to interleaving issues.
• Terms which gives more info on speed limitations and what speed really is
• Physical track positioningan old but still good technique
• Disk layout for general layout issues
• The need for swap
• An example setting using 4 interleaved swap partitions.
• Single drive swap positioning optimisation

Note that the swap partiotn limit in old kernels depends on the architecture of the processor, namely if it is a 32- or 64-bits processor.

If you have any comments to the HOWTO I hope you can take direct contact with the author so more people can benefit from your insight.

At least one gives a rather in depth description of the issue, the Multi Disk HOWTO which is very much about tuning in general. It is way to big to quote here so I' rather suggest the interested readers look at the following chapters listed below (straight from the Multi Disk HOWTO homepage):

• disk drives and speed
• File System Features which even starts off discussing swap. Pay special attention to interleaving issues.
• Terms which gives more info on speed limitations and what speed really is
• Physical track positioningan old but still good technique
• Disk layout for general layout issues
• The need for swap
• An example setting using 4 interleaved swap partitions.
• Single drive swap positioning optimisation

Note that the swap partiotn limit in old kernels depends on the architecture of the processor, namely if it is a 32- or 64-bits processor.

If you have any comments to the HOWTO I hope you can take direct contact with the author so more people can benefit from your insight.

At least one gives a rather in depth description of the issue, the Multi Disk HOWTO which is very much about tuning in general. It is way to big to quote here so I' rather suggest the interested readers look at the following chapters listed below (straight from the Multi Disk HOWTO homepage):

• disk drives and speed
• File System Features which even starts off discussing swap. Pay special attention to interleaving issues.
• Terms which gives more info on speed limitations and what speed really is
• Physical track positioningan old but still good technique
• Disk layout for general layout issues
• The need for swap
• An example setting using 4 interleaved swap partitions.
• Single drive swap positioning optimisation

Note that the swap partiotn limit in old kernels depends on the architecture of the processor, namely if it is a 32- or 64-bits processor.

If you have any comments to the HOWTO I hope you can take direct contact with the author so more people can benefit from your insight.

At least one gives a rather in depth description of the issue, the Multi Disk HOWTO which is very much about tuning in general. It is way to big to quote here so I' rather suggest the interested readers look at the following chapters listed below (straight from the Multi Disk HOWTO homepage):

• disk drives and speed
• File System Features which even starts off discussing swap. Pay special attention to interleaving issues.
• Terms which gives more info on speed limitations and what speed really is
• Physical track positioningan old but still good technique
• Disk layout for general layout issues
• The need for swap
• An example setting using 4 interleaved swap partitions.
• Single drive swap positioning optimisation

Note that the swap partiotn limit in old kernels depends on the architecture of the processor, namely if it is a 32- or 64-bits processor.

If you have any comments to the HOWTO I hope you can take direct contact with the author so more people can benefit from your insight.