Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment Re:Terrible summary, decent blog post (Score 1) 601

This is actually mentioned in the bitcoin wiki, here: https://en.bitcoin.it/wiki/Deflationary_spiral, but the author of that page doesn't think it will be a problem. Obviously you(and I) disagree.

The fact that they don't see this as a problem, while stating that "Bitcoins only deflate in value when the Bitcoin Economy is growing" shows just how delusional the strongest bitcoin supporters are. The bitcoin economy must always grow if it is to continue to be valuable to anyone. However, if it does continue to grow, it faces the very real, very large problem of being in a deflationary spiral.

Comment Re:Sprint and T-Mo should merge (Score 1) 301

True, but iDEN was basically eGSM(or GSM+, if you'd like)

http://en.wikipedia.org/wiki/Integrated_Digital_Enhanced_Network#Hardware

not sure how easily it would convert to real GSM, but to say iDEN is not GSM is a bit like saying hybrids are not ICE vehicles. Partly true, partly not.

Comment Re:So long and thanks for the OMG PONIES!!! (Score 1) 1521

nope. I registered somewhere later within the first 3 years of the site, and was bummed I waited so long and didn't get into(or under) the 100k's.

  I remember the one-line text-box CGI he had that (supposedly) would throw messages on his console. I remember the cool "I know that guy" feeling I had when they posted a KDE article that one of my college friends submitted (talk about your 6 degrees of separation/15 seconds of fame. the article was this one, before there were even comments! http://tech.slashdot.org/story/98/07/12/239217/KDE-Hits-10)

despite all our bitching about what slashdot has become over the years, thanks Rob and Hemos and everyone else coding/editing-wise who has contributed to the site.

Comment Re:New ? Hardly. (Score 2) 91

Bingo. It sounds like he's trying to take a "cloud-sourced" approach to MIMO, with a little meshiness thrown in for good measure.

Plus I think the whole "support for non-stationary receivers is a huge issue" and "needs to avoid interference that's not of its own making" aspects will make this a non-starter. Good luck getting that spectrum, or finding a big enough group of fixed-wireless customers to make this either useful or profitable.

WiMAX and LTE are already doing MIMO and beamforming (perhaps to varying degrees), so the only thing novel about this is how massively it can fail, and just how smoothly he managed to weave the ever-magical "cloud computing" buzzword into it.

Comment Re:GNU/Linux (Score 1) 335

Speaking as someone who was here before slashdot started offering user accounts(yes my uid doesn't show that, so sue me) I think many are tired of hearing about how Hurd is so much better technically, and should be putting out a release "any day now" for the past 12+ years(I say 12 instead of 20 because I believe I registered on slashdot sometime between 98-2000).

We did talk about it in more technical ways, and compare it to Linux, over and over and over. Now it's just tired. Just like so many have already said, some having said so with very good links to explain how/why.

Comment myself: load-shared routing in linux, mixed result (Score 1) 206

You might want to look into load-balanced routing. I had a linux box with 3 NIC's, one NIC per ISP and one NIC to the rest of the house. I set it up for load-shared routing via the LARTC HOWTO, and for web traffic it worked ok.

I didn't stay with it because it wasn't stable for VPN connections. The decision about which upstream link to use was somehow governed by the local/remote host pairing, plus some unknown-to-me modifier. So I could establish a VPN connection, but it wouldn't keep the connection through 1 of the two links consistently. As soon as it tried to switch the VPN connection to route through the other uplink, pow, there went my VPN session. I don't recall the exact time before failure but it was less than 2 hours in most cases. made it basically unusable for me, at that time, for working from home. Perhaps that's solved(or can be configured around) by now.

I don't know/remember how it works for p2p either, though, since it was so long ago and the decision about which upstream path for any outbound traffic to take is controlled by the kernel on that routing box.

here's the relevant section of the LARTC HOWTO, in case you want to read more or try it out:
http://lartc.org/howto/lartc.rpdb.multiple-links.html#AEN298

Comment Re:Window always tested many architectures (Score 1) 348

actually it was somewhat ironically called NS/UX. (For NonStop UNIX, I believe)

The Tandem hardware architecture was interesting, every piece of hardware in a Tandem was duplicated. backplanes, ram, disk, any and every io path, literally every hw component had a backup. Everything was hooked up like two identical non-fault-tolerant machines within a single cabinet, although with a lot of inter-communication pathways between the two(google servernet). You could actually run two system images on each Tandem if you didn't want the HW-level failsafe redundancy.

not only did each core run a copy of the OS, but I believe all the cores ran the OS in instruction-level lock-step with each other, so that a failure anywhere along the path meant transparent switchover to the backup hardware path.

that all assumes that the switchover did work, and unfortunately it didn't seem to work as smoothly as my company wanted for telco purposes. Eventually it did work halfway decently, but the MIPS processors quickly got surpassed speed-wise by every other processor architecture, and the hardware redundancy became too costly(both reliability-wise, and "do real work"-wise) compared to what could be achieved with software redundancy on faster machines. Tandem boxes were running @ 400mhz in the early 2000's, when virtually everything else was over(and sometimes well over) 1ghz.

Comment Re:NOOOOOOO (Score 1) 583

I should have also added...

there is "scripting yourself out of a job", and there is "enabling someone else to do my current job, so that I can move up to something bigger/better/nicer/etc."

In the (fortune 500) company I work for, if you make yourself irreplaceable by way of being the only person capable of doing something, you're still just as likely to get fired. The people in charge of the hirings/firings are too "stupid" to avoid any associated pain. And being the only person capable of doing something that is scriptable just means that you're limiting yourself to your current low-level responsiblilities.

Comment Re:NOOOOOOO (Score 1) 583

Yes, but this is basically a more polite version of the classic broken window fallacy.

It may keep people employed, but those same people could be much more usefully employed addressing other better problems. both now and in the past.

Comment video of "traffic stop" in question (Score 1) 485

I know I'm a day late to the conversation, which means it's probably dead. I know someone mentioned this briefly, but it's really worth watching the biker's video of the stop:

http://www.youtube.com/watch?v=BHjjF55M8JQ

If you watch the video you'll see how off-base most of the comments in this discussion are. I know, I know, slashdot, new here, etc. but those of you who think this was some regular traffic stop by a uniformed officer should now be able to see just how far FAR different it actually was from anything reasonable or sane.

Comment Re:Not only act of idiocy (Score 1) 445

Even if it's not 1/30, your math still seems suspect.

I have a 200k mortgage note on my home. I bought it early in 2004, so let's assume it's not overvalued too badly(not quite as bad as those 2007, 2008 mortgages). My monthly payment, with PMI, taxes, etc: 1700$. (thank you FHA first-time home-buyer plan)

1 year's mortgage payments: 20,400$.

that's still 1/10 the price, even lower if we didn't figure in PMI, taxes, etc. For a home that had only been in foreclosure 1 year, that still seems way higher (or lower) than the typical 30-50% discounts I hear foreclosures are going for these days.

Comment misleading title, indeed (Score 2, Informative) 227

From building two or three of these at home myself, my practical experience for someone wanting a monster file server for home, on the cheap, consists of these high/low points:

1. the other poster(s) above are 100% correct about the raid card. to get it all in one card you'll pay as much as 4-5 more hdd's, and that's on the low end for the card. decent dedicated PCI-E raid cards are still in the $300+ range for anything with 8 ports or more.

2. be careful about buying older raid cards. I have 2 16-port and 2 8-port adaptec PCI-X sata raid cards that are useless. why? they only support raid arrays up to 2tb in size. "update the firmware", you say. sure, let me just grab the latest, from 2005, I'm sure that fixes it. oh, wait, my raid cards already have that, and it doesn't remove that limitation. 8 drives, 16 drives, even, and they hard-code a limit of 2tb? lame.

3. I've seen nothing in a home-budget price range that performs as well as linux software raid. My 1.5 yr old 500$ tyan workstation mobo(S5397, in another computer) has dedicated SAS raid that can't seem to do better than 10mbyte/sec throughput. reading data from drives that individually bench out at 50-60mbyte/sec.

4. which leads me to: use linux software raid. It's much more configurable than any hardware raid card, both in supported raid levels and monitoring capabilities. raid disks/arrays can be easily moved from one machine to another, one controller to another, etc. I've moved most of my disks between machines and controllers at least once.

5. I've come to believe over time that what you're really looking for is X SATA ports, not "controller capable of doing raid over X disks". Use SATA "mass storage" cards, or raid cards that will let you use them in pass-through mode to access the individual disks directly in the OS. here you have to be careful you don't get bit by #1, 2, or 3 again, since some raid cards don't behave well when not actually doing raid (I'm still looking at you, Adaptec). this makes it easier and much cheaper, you can mix and match lower-capacity cards to get 8-20+ sata ports for raid.

5.1 "hw vs sw raid tangent" : what happens on a dedicated raid card when you run out of ports? you usually can't span raid cards, unless you get multiple identical fancy (aka expensive) raid controllers from the same manufacturer. all linux needs is hard drives recognizable by the BIOS.

6. when using software raid, buy a decent CPU. You don't need some quad-core beast, but you don't want to be waiting on the CPU to finish your raid calculations. any 2-2.5ghz C2D is probably more than adequate...I've drawn the line with anything under 2ghz.

7. kiss backups good-bye. the price of any decent backup system capable of covering this much storage is WAY over the price of this whole setup. Anything I really don't want to lose gets saved multiple places outside of the raid array, otherwise I factor the potential for data loss as a risk of operating this way. Personally I don't really see how you could do otherwise in a setup like this.

8. be prepared for bottlenecks. you're doing this on a home budget, you probably won't get 300mbyte/sec reads off of your array, no matter how many drives configured at what raid level. I can only get 10-20mbyte/sec across my gigE network going to/from my raid 5 array. This is probably due to the cheap PCI sata cards I'm using. I willingly make this trade-off to obtain the capacity I have for the price I spent.

If any of these points is an overriding concern for your intended use, then you'd have to re-evaluate the importance of all the other considerations.

For me, stability, capacity and price are top three, leading me to research linux-stable cheap sata expansion cards (which is just a nice way of saying, I buy and try probably 2x the # of controllers I actually use, to find ones that won't corrupt data, time out on random drive accesses, or simply not display the real drives to the OS, etc), and compromise by waiting a bit longer for network transfers. Usually the waiting consists of starting a big transfer and then multi-tasking other things in the foreground/elsewhere. local same-machine use of this raid array is a consideration I've never entertained, but should be included in the list for anyone who's thinking about building one.

Slashdot Top Deals

Math is like love -- a simple idea but it can get complicated. -- R. Drabek

Working...