Please create an account to participate in the Slashdot moderation system


Forgot your password?
Slashdot Deals: Prep for the CompTIA A+ certification exam. Save 95% on the CompTIA IT Certification Bundle ×

Comment Printers, otherwise known in the industry as... (Score 1) 378

Printers, otherwise known in the industry as Toner Dispensers.
Manufacturers, especially Xerox, internally (and only half-jokingly) refer to printers as Toner Dispensers. It's where they make a massive amount of their revenue from.

Sure, when they're selling a printer for a price in the 10's of $k, they're not exactly making a loss, or only just breaking even on the hardware, there's still a decent amount of margin on this - but the ongoing revenue stream (and the reason they try to get everyone onto managed print services) is in selling toner, and lots of it.

Over the life of a printer (or copier, which is just a big printer with a scanner built into it) the cost of consumables will be far greater than the initial purchase price of the machine. Generally, toner is cheaper on bigger and more expensive printers (which in itself is strange as it's the same toner) - this is why if you're printing a large volume, you're better off getting a more expensive printer with cheaper toner.

Comment Re:Why not both? (Score 2) 239

AC has far lower transmission losses over long distances, however with the advent of rooftop solar now people can generate DC closer to where they're using it.
Converting AC to DC and DC to AC will always incur losses, and as AC is far more efficient for transmission, we've historically used AC everywhere (well, except inside just about everything you plug into an electrical outlet, where DC is generally used)

Comment Re:Pre-cambrian computing (Score 1) 191

I'll have to watch that docco - After using BBC micros and BBC Model B in primary school, and the Acorn Archimedes in high school, I've followed Arm with a bit of interest. Their rise and fall and then stratospheric rise again from the ashes is an incredible story. By sheer volume, there are probably more ARM cores on the planet than any other architecture - ARM was originally the Acorn RISC Machine and was an incredible processor architecture in it's day (and, through licensing to other fabs, still is pretty impressive for it's performance per watt)

Comment Two ways... (Score 1) 173

There are two ways of doing this.

One is to look for alternative remote desktop software that does work. I've had success with TeamViewer - YMMV.

Two is to put in a lan-to-lan VPN at each site and configure your routing appropriately - either go with something like DD-WRT or get something that will do it out of the box like a Ubiquity EdgeRouter Lite ($100 and it has 3x gigabit ports and enough horsepower to route at an appreciable fraction of that rate)

Comment But how many people actually check... (Score 1) 296

The question is not whether certs are worth the time and money (I tend to believe that they're not) but if you're putting them on your resume, who is actually going to check...

Another answer for are they worth the time and money - most definitely for the certification centres.

Comment Re:Still don't trust SSDs (Score 5, Insightful) 144

Yep. I'll happily take 10x the number of IOPS and limited writes (that are in most cases many years of regular service) over "infinite" writes and moving parts. I wouldn't want to keep spinning rust in service more than 3-5 years tops, and if all the SSDs I've used will survive this long, why should I use the slower solution?

Comment Re:How is this better than iptables or pf? (Score 1) 34

Because someone has already done the hard work for you.
Time to do what you want to do = 2-4 hours or more.
Time to dump an image to a CF card and boot it - 2 minutes.
Plus, if it's based on m0n0, it'll run out of the box on embedded systems like Alix and Soekris boxes, which are amazingly reliable embedded x86 systems with no moving parts. I've got Alix-based m0n0 firewalls out there that haven't been rebooted in years and they just keep going. It's also designed to run from flash media, so writes (for logs etc) are kept to a minimum.

Comment Re:It's not a networking issue. (Score 1) 384

If I understand what you're saying, each destination IP is behind a NAT, and so from the point of view of the laptop, there are, say, 16 IP addresses that are all NATted to the individual pumps, that all happen to have the same IP on the other side of the NAT.

The question for the submitter then, is seeing that every pump has the same IP, is this IP hard-coded into the software, or can you specify the IP that you push the firmware update to?

If the software is hard-coded to assume every pump it connects to has the same IP, then you're in trouble.

"Ahead warp factor 1" - Captain Kirk