Don't give them ideas!

It's interesting how different it can be. The first language we were tought in CS was Moscow ML (Similar to Standard ML, or SML). After that we actually learned MIPS assembly, followed by C. We didn't learn Java until the very end. This gave us a fairly decent grasp of the inner workings of a computer, and I'll forever thank them for it. In our first year, we were asked to construct a MIPS compatible architecture in a simulator (logisim). That was extremely fun, and it really opened my eyes to what a computer really is.

Why this compromise? There's a huge need for developers to start thinking in terms of multicore CPUs. Offering them this solution is just postponing the inevitable. We need change now.

Just install Xpdf/evince and be happy. You don't need embedded crap in your documents.

Tell me about it. I've been playing around with PICs lately and I've recently compared a compiled C program (mikroC) to a program that I wrote myself in assembler. Its task was simply to output "Hello World!" to a HD44780 LCD module, and whereas I could suffice with about 20-30 lines of code, whereas the compiled program required about 120 lines to do exactly the same thing!

The compiler created about 10 subroutines out of thin air. It was a mess!

So their last name is McBrides?

(Sorry... I'm from Sweden, and I found that funny.)

I got this setup by experimentation, so I'm afrad I have no links, but I can describe my setup in more detail. I use OpenWrt on my wireless router (WGT634U). Recent versions use a web based configuration interface known as LuCI, which can be used in addition to configuring the device through the standard command line interface. Since it's based on the Linux kernel, you can use all of iptables to configure this behaviour. Using LuCI, this is a simple process, and you can define VLANs to your liking. OpenWrt

For this setup you need a router capable of allowing/denying connections based on source/destination interface (it's ideal if it can run OpenWrt, because it makes setup a lot easier).

You'll need to create two wireless interfaces, one with WEP/WPA encryption and one with WPA2 encryption. Next, configure the WEP/WPA interface so that it can't access anything except your external (internet) interface, creating something similar to a VLAN. You should be done. There's plenty of information on the OpenWrt site, but a good starting point is that you read about iptables and routing.

I hope this helps in some way.

One solution is to set up two access points: one with WEP, which is locked down to only access the external network, and only for certain ports, and one with WPA2, which can also access the internal network. Some routers can host multiple virtual access points (multiple interfaces), so there's no need for extra hardware in that case.

This setup has worked well for me with my DS in the past, although I didn't limit the port range on the WEP access point.

One can hope that they release a .ppd, making the printer usable under GNU/Linux, *BSD and OS X at the same time.

If you will, a package repository can be viewed as some kind of appstore, in the sense that it's a centralized repository for applications. Perhaps a contributing factor to RHX's demise is that there already exists a plethora of package management systems, and that Red Hat users felt that it was a confusing addition to the mix. Freedom of choice is a good thing, but too many options are more likely to confuse consumers, making no solution stand out.

Interesting, I have exactly the same problem. Until recently I played the bass guitar in a Gothic rock band, so my theory is that you're more vulnerable to musical distraction if you are/were a musician/producer.

Dear musicians/producers, help me prove/disprove my theory!

From the article:

I'd love to se a man with a PDP-11 sticking out of his skull.

Damn! Out of mod points!

You forget about the windows users, you insensitive clod!

Best thing I've read today!