mp3 sounds crap at 15kbps, and you'd find it hard to get more out of voice cellular calls. Also, mp3 imposes intolerable latency -- even if you had the bandwidth it would sound like a walkie-talkie.
Nope. Access controls are no more a router feature than they are a switch feature. They're just a feature that decent networking equipment has, no matter which layer it is operating on.
In the paper they detail how they handle ARP. All other broadcasts you can get away with dropping these days; use multicast instead. (Yes, that will break NETBIOS broadcast name lookups. So sad.)
How do you prevent some clown from anywhere in that 100,000 machine cloud from poaching another machine's IP address (either maliciously or by an accidental typo)?
That is a solved problem if you use decent switches. You can apply pretty much any policy you like.
In Europe we simply let the network do the triangulation. Any phone will work. The Wiki page doesn't seem to specify whether the US system is handset-based or network-based.
It gets valuable proof that Linux is a serious industrial strength system
It's used on set top boxes. Not exactly the epitome of reliability or performance, and certainly not "industrial strength". Also, the companies were doing their best to hide the fact that Linux is used.
What does the community get out of the fact that YouSee, Stofa, and Viasat use Linux?
All the Danes on Slashdot probably know about Viasat's business practices, which are about as close to fraud as you can get without losing in court, so I don't need to warn anyone against signing contracts with them.
The tradeoff supposedly was that RISC would give you less powerful instructions which were easier for the CPU to decode, but then it was expected that it would be more difficult for compilers or humans to write the instructions. It didn't turn out that way. E.g. x86 comes from the time of constrained 8-bit processors, and back then there were no wasteful niceties in the instruction encoding. Most of the worst nastiness is gone as of x86_64, and assemblers hide some of the rest from you.
If you want to program CISC, at least go for M68k/ColdFire, but you won't find many user-programmable devices with ColdFire anymore. ARM is everywhere. My personal favourite is SPARC, and SPARC machines are relatively easy to come by.
Sure, it was patched, but it wasn't exactly all over the news. Neither is this one for Linux, but it managed to get mentioned on Slashdot.
Local privilege escalation is hard to guard against with current mainstream operating systems. The attack surface is very large and it is hard to completely verify interfaces. That said, Linux team seems to be doing fairly well overall. We're certainly a long way from the "good" old days when crashme would crash pretty much any Unix system. OpenBSD is doing even better, masturbating monkeys or not.
Both these problems won't find a solution any time soon, so don't expect the cores of your 64-core CPU of 2015 to be much faster than the cores of today.
At least they'll be connected to more cache and faster memory. Hopefully the third level cache will be shared among several cores.
 263. Med bÃde eller fængsel indtil 6 mÃ¥neder straffes den, som uberettiget
1) bryder eller unddrager nogen et brev, telegram eller anden lukket meddelelse eller optegnelse eller gÃr sig bekendt med indholdet,
"With a fine or with imprisonment up to 6 months is punished the person, who without authorization
1) break [the seal of] or deny someone a letter, telegram or other closed message or record, or acquaints themselves with the contents,"
Sorry for the lousy translation, the original is in legalese. In particular, "without authorization" is bad translation, but I don't have a better one.
You probably want a commented version of the Danish Criminal Code if you want the subtleties explained, and I don't have one. There has of course been discussions about whether emails are "closed messages or records", but this has been decided by the courts, and they are.
While it's lame and unethical to exploit such a mistake, I doubt there would be any legal recourse if that person were to do anything they wanted with the information they received. The sender could be penalized for disclosing information to an unauthorized party, but there's no obligation on the part of the receiver of the email.
I have limited knowledge of US laws, but under Danish law the recipient of the mail is not allowed to pass the information on, or even read further when they realize the mistake.
Also, if you search for Quicken files on a network with the intention of publishing statistics on how many files are shared by accident, that would be entirely legal. On the other hand, if your plan is to defraud someone, you can be prosecuted for that from the time you take the first step in that crime, even if that step is exactly the same step the researcher was doing, and even if the police stop you before you get the chance to actually cause any harm. Proving that was the intent can be difficult, of course.
I don't think getting data from a folder someone has publicly shared is wrong.
Around here, if you get an email by mistake (e.g. the wrong address was entered, or someone sent a private email to a work account which you are legally monitoring), you have no right to read it. You have to stop reading as soon as you realize that the email isn't for your eyes, and you have no right to share or use the information you received by mistake.
I think that analogy is quite close to the case of opening someone's Quicken file.
You don't have to cover the edge cases of people living in the middle of nowhere, so they throw off the average in unrealistic ways.
You don't have very high expectations. Try this map. I can't find a comparable map for Alaska, but the little information I can find looks rather bleak.
If you are going to build cell towers in the US you either have to get a bunch of different kinds for the different kinds of weather, or over engineer them to handle all types. Either option adds significant costs.
The economies of scale work in your favour when you try to cover the US.
The Finnish Meteorolical Institute has a good overview. Finland and Alaska sound like they have about the same climate, and I would imagine that Alaska has harsher weather than the US average.
In other words, you don't actually know and are just guessing based on your preconceived ideas about Finland and the United States? Thanks for clarifying that for us:)
What the fuck did you expect? Two years research?
I used the word "expect" in my first reply already, in reply to this:
more harsh weather conditions across the US than Finland also
which makes a statement without any guard words whatsoever. I could have just gone with "citation needed", but that is rather impolite.
Mobile phones in Europe are subsidized by calls from fixed lines. Since you do not pay to receive calls, there are two rates for calls FROM land lines: a cheap rate to other land lines, and an expensive rate to mobile phones. Some carriers get more than half their income from incoming calls. When you call from a cell phone to a cell phone with a different carrier, the originating carrier usually pays more to the terminating carrier than the customer pays.
So don't use a land line to call a cell phone in Europe. Use another cell phone; their plans are almost universally cheaper.
Finland has 17 inhabitants per square kilometre on average. US is at 30. I would expect that Finland has universal cell phone coverage like the other Nordic countries, but unlike the US.
It also seems quite unlikely that the US has "more harsh weather conditions than Finland".
everyone who jumped to it early because it was the new bright and shiny thing should consider being a bit more cautious next time.
The only regret I have about my X25-M is that I didn't get one when they first came out but waited till 6 months ago. The only comparable speed increase in Linux I have ever experienced was when I upgraded my parents' 486 from 8MB to 20MB RAM.
Slashdot Mirror
mp3 sounds crap at 15kbps, and you'd find it hard to get more out of voice cellular calls. Also, mp3 imposes intolerable latency -- even if you had the bandwidth it would sound like a walkie-talkie.
Quote fail. Sorry.
and then it becomes... say it with me, a router
Nope. Access controls are no more a router feature than they are a switch feature. They're just a feature that decent networking equipment has, no matter which layer it is operating on.
What do you do about broadcast storms?
In the paper they detail how they handle ARP. All other broadcasts you can get away with dropping these days; use multicast instead. (Yes, that will break NETBIOS broadcast name lookups. So sad.)
How do you prevent some clown from anywhere in that 100,000 machine cloud from poaching another machine's IP address (either maliciously or by an accidental typo)?
That is a solved problem if you use decent switches. You can apply pretty much any policy you like.
In Europe we simply let the network do the triangulation. Any phone will work. The Wiki page doesn't seem to specify whether the US system is handset-based or network-based.
It gets valuable proof that Linux is a serious industrial strength system
It's used on set top boxes. Not exactly the epitome of reliability or performance, and certainly not "industrial strength". Also, the companies were doing their best to hide the fact that Linux is used.
What does the community get out of the fact that YouSee, Stofa, and Viasat use Linux?
All the Danes on Slashdot probably know about Viasat's business practices, which are about as close to fraud as you can get without losing in court, so I don't need to warn anyone against signing contracts with them.
The tradeoff supposedly was that RISC would give you less powerful instructions which were easier for the CPU to decode, but then it was expected that it would be more difficult for compilers or humans to write the instructions. It didn't turn out that way. E.g. x86 comes from the time of constrained 8-bit processors, and back then there were no wasteful niceties in the instruction encoding. Most of the worst nastiness is gone as of x86_64, and assemblers hide some of the rest from you.
If you want to program CISC, at least go for M68k/ColdFire, but you won't find many user-programmable devices with ColdFire anymore. ARM is everywhere. My personal favourite is SPARC, and SPARC machines are relatively easy to come by.
That's the most original description of Theo and his team I've ever seen!
No it isn't, I blatantly stole it from Linus Torvalds...
Sure, it was patched, but it wasn't exactly all over the news. Neither is this one for Linux, but it managed to get mentioned on Slashdot.
Local privilege escalation is hard to guard against with current mainstream operating systems. The attack surface is very large and it is hard to completely verify interfaces. That said, Linux team seems to be doing fairly well overall. We're certainly a long way from the "good" old days when crashme would crash pretty much any Unix system. OpenBSD is doing even better, masturbating monkeys or not.
Generally people don't care about local privilege escalation on Windows. Like this vulnerability.
Both these problems won't find a solution any time soon, so don't expect the cores of your 64-core CPU of 2015 to be much faster than the cores of today.
At least they'll be connected to more cache and faster memory. Hopefully the third level cache will be shared among several cores.
Yay, Slashdot still can't handle Danish characters. Slashdot will probably be stuck in the 80's forever.
 263. Med bÃde eller fængsel indtil 6 mÃ¥neder straffes den, som uberettiget
1) bryder eller unddrager nogen et brev, telegram eller anden lukket meddelelse eller optegnelse eller gÃr sig bekendt med indholdet,
"With a fine or with imprisonment up to 6 months is punished the person, who without authorization
1) break [the seal of] or deny someone a letter, telegram or other closed message or record, or acquaints themselves with the contents,"
Sorry for the lousy translation, the original is in legalese. In particular, "without authorization" is bad translation, but I don't have a better one.
You probably want a commented version of the Danish Criminal Code if you want the subtleties explained, and I don't have one. There has of course been discussions about whether emails are "closed messages or records", but this has been decided by the courts, and they are.
While it's lame and unethical to exploit such a mistake, I doubt there would be any legal recourse if that person were to do anything they wanted with the information they received. The sender could be penalized for disclosing information to an unauthorized party, but there's no obligation on the part of the receiver of the email.
I have limited knowledge of US laws, but under Danish law the recipient of the mail is not allowed to pass the information on, or even read further when they realize the mistake.
Also, if you search for Quicken files on a network with the intention of publishing statistics on how many files are shared by accident, that would be entirely legal. On the other hand, if your plan is to defraud someone, you can be prosecuted for that from the time you take the first step in that crime, even if that step is exactly the same step the researcher was doing, and even if the police stop you before you get the chance to actually cause any harm. Proving that was the intent can be difficult, of course.
Cripes, with some of the crazy emails around here, I -have- to read the entire email to be absolutely sure it wasn't for me.
Well, you aren't obligated beyond your abilities...
I don't think getting data from a folder someone has publicly shared is wrong.
Around here, if you get an email by mistake (e.g. the wrong address was entered, or someone sent a private email to a work account which you are legally monitoring), you have no right to read it. You have to stop reading as soon as you realize that the email isn't for your eyes, and you have no right to share or use the information you received by mistake.
I think that analogy is quite close to the case of opening someone's Quicken file.
You don't have to cover the edge cases of people living in the middle of nowhere, so they throw off the average in unrealistic ways.
You don't have very high expectations. Try this map. I can't find a comparable map for Alaska, but the little information I can find looks rather bleak.
If you are going to build cell towers in the US you either have to get a bunch of different kinds for the different kinds of weather, or over engineer them to handle all types. Either option adds significant costs.
The economies of scale work in your favour when you try to cover the US.
The Finnish Meteorolical Institute has a good overview. Finland and Alaska sound like they have about the same climate, and I would imagine that Alaska has harsher weather than the US average.
In other words, you don't actually know and are just guessing based on your preconceived ideas about Finland and the United States? Thanks for clarifying that for us :)
What the fuck did you expect? Two years research?
I used the word "expect" in my first reply already, in reply to this:
more harsh weather conditions across the US than Finland also
which makes a statement without any guard words whatsoever. I could have just gone with "citation needed", but that is rather impolite.
Ok, I guess you can calculate that way, but I obviously meant per area. Of course a significantly larger area is going to have more natural disasters.
Per area, I would guess that Finland has the US beat, at least when it comes to destroying cell phone towers.
Mobile phones in Europe are subsidized by calls from fixed lines. Since you do not pay to receive calls, there are two rates for calls FROM land lines: a cheap rate to other land lines, and an expensive rate to mobile phones. Some carriers get more than half their income from incoming calls. When you call from a cell phone to a cell phone with a different carrier, the originating carrier usually pays more to the terminating carrier than the customer pays.
So don't use a land line to call a cell phone in Europe. Use another cell phone; their plans are almost universally cheaper.
Finland has 17 inhabitants per square kilometre on average. US is at 30. I would expect that Finland has universal cell phone coverage like the other Nordic countries, but unlike the US.
It also seems quite unlikely that the US has "more harsh weather conditions than Finland".
everyone who jumped to it early because it was the new bright and shiny thing should consider being a bit more cautious next time.
The only regret I have about my X25-M is that I didn't get one when they first came out but waited till 6 months ago. The only comparable speed increase in Linux I have ever experienced was when I upgraded my parents' 486 from 8MB to 20MB RAM.
Nope, but if you invent a way to store a whole C program in an XML file, along with a way to compile and edit the thing, you might have it.
Hopefully there's no prior art for that (until this moment).