Serverbeach is a dedicated hosting company. They're not going to be scanning memory as they don't have local access to the server. It must be some sort of web crawling or spidering that they do.
So Server Beach has an automated system that detected copyright infringement in a "cache" file and automatically shut down the server before checking to see if it was actually visible to the public (which according to the article it was not)?
If content is visible to your dedicated (not managed) hosting company, who doesn't have any login access to your servers, then yes, the content is visible to the public. Access to it may be obscured, due to removed links to it or however it was supposedly 'removed', but still available to the Internet and henceforth public.
That's because you're trying to buy an old CPU in brand new condition, long after production has stopped. Usually, the best window to buy a CPU new is when the next generation comes out, but you are already 4 (2 ticks + 2 tocks) generations behind. You can easily find the Q9550s used for less than $100.
Read more carefully. It was the husband of one of the partners at the firm representing Samsung, which does not appear to have even been actively involved in the case. Your bias is showing.
You can have a distributed DDoS protection service, where you BGP anycast the IP range being attacked to multiple cities, and deploy DDoS mitigation equipment to each of those locations. In the event that the attack is concentrated in one region, where your DDoS mitigation equipment is unable to keep up, you can then do a localized null route (that doesn't get advertised to the rest of your iBGP mesh), to drop the traffic for that particular region but still stay up for the rest of the world.
Null routes work on destination IPs only, not source IPs, so if one were to take your advice, they would effectively be doing the attackers' job for them. Null routes are for preventing a DoS attack from affecting other customers/services, not for keeping a server up and available during an attack. The only way to block source IPs on routers is with ACLs, but these are only effective against very simple DOS where a small number of sources are attacking you. For a large scale DDoS, with sources from several different ranges attacking protocol/ports on IP addresses where legitimate traffic needs to go (which any smart attacker would do), ACLs aren't going to do it.
CLI commands are not necessarily hacks; they are often the proper way of doing things. Just because they are powerful and flexible enough, that they allow for people who don't know what they're doing to break their systems, doesn't mean that they are inherently bad. It's the GUI's that are often the hacks; they've just been vetted to perform tasks in a standardized, predefined manner. For the most part in Linux land, they are effectively workarounds so that people don't need to learn the proper commands. It's when the GUI is incomplete that users are forced to run the proper commands using the CLI, but those commands themselves are not hacks.
Canada is a colony of the crown, much like Australia. It is primarily a British-US culture save for some belligerent Frenchies in the East.
Canada's original culture was North America Indian including Eskimos (Inuit), which have been marginalized by western culture.
Canada's best comedies are take-offs of British shows (Canda's worst Driver) and their original stuff "Corner Gas" is marginally funny. (Kenny vs Spenny, Kids in the Hall, etc successes are short-lived) Anyone sufficiently funny winds up in the US (Lorn Micheal's, Micheal J Fox, etc) however these people are more "American" than Canadian.
Don't get me wrong, I love Canada. But the culture isn't original, it is derivative at best, copied at worst.
Canada hasn't been a colony since 1867.
What makes Lorn Michaels and Michael J. Fox more American than Canadian? If anything, can you not say that American culture is affected by Canadians?
The majority of transit providers use a BGP prefix list to limit what IP addresses you are permitted to advertise to them either through manual management of the list or by using a routing registry, so it's not nearly as common as you're implying. The exception is when it comes to peering, but there aren't that many networks that do a significant amount of peering. And if any of your peers catch you IP hijacking, they're likely to de-peer pretty quickly if they discover you're hijacking IP's. Yes, there are a few transit providers who don't follow this properly (the few instances I recall of IP hijacking usually revolved around Sprint), but it's false to assume that just anyone with a BGP connection can just hijack anyone's IP address.
That's ridiculous. I'm all for acknowledging BSD's contributions, but you can't possibly claim nobody would've implemented a stack if the BSD project hadn't. It's as ridiculous as saying the FreeBSD project wouldn't have existed until today without GCC.
Of course we would be on the net, someone else would've written a networking stack for Linux and Microsoft would have either written their own or bought one of the companies which sold third party stacks for Windows.
Sure, except the Linux stack and the Microsoft stack probably wouldn't have been compatible, meaning fragmented networks. In other words, either no universal network of networks i.e. the Internet, or everyone would have been forced to go with Microsoft's solution. One of the benefits of a very liberal license is it's easy for other Operating Systems to adopt. OpenSSH is another obvious example of this.
If they want to give 90% back - which is common behavior for proprietary derivatives of BSD licensed codebases - they can't. They have to give back 100%, or stay out.
And if that's not to their liking, the only thing they miss out on is the gratis skilled labor of strangers. They are still free to write their own code under any license they want. I just don't see the problem, unless of course there is a sense of entitlement to something no one actually owes them. That's the only explanation for why anyone would experience any distress over this.
Or maybe, because the rest of us lose out on the 90% they would have given back?
Flash has worked pretty well on FreeBSD for years now, using nspluginwrapper. ext2 has pretty much always been supported, and ext3 can be mounted as ext2.
No, the article is just written by morons... Current high end Xeons ship without coolers, as have Xeons for many generations, this is because Intel have no clue where the chip is going –it could be into a 1U system, or it could be into something enormous. Basically... Move along, nothing to see here.
Get your facts straight. Xeons still come with coolers if you buy the retail package, or without coolers if you buy OEM, just like with consumer CPUs.
8% is pretty decent, considering most people working in the industry wouldn't even qualify as 'well-trained, ready-to-go'. At least with graduates, there's still the possibility of them getting there, as opposed to all the grossly incompetent veterans with too much ego to ever learn anything new.
What's not desktop ready about the *BSD's these days? What's lacking?
The last annoyances like flash support are now easy enough to get working on FreeBSD, portupgrade -PP and freebsd-update make it easy to upgrade both apps and OS using binaries, and nvidia drivers have been around for years. And if you need a dumbed down install process, there's always PC-BSD.
An OS consists of not only the kernel, but also the userland. You need to be able to interface with the kernel at least at some level. Just because GNU/Linux's userland is indistinguishable from third party applications doesn't mean that all operating systems are complete with kernels alone.
Well, any potential future employer can now see how litigious she is, which is going to be much worse than having unrelated spam links show up. I don't think too many employers want to hire a lawsuit waiting to happen.
In any case, if China and Japan duke it out, it won't be about dirt, it will be about a century long conflict (which incidentally has had Japan framed up as the villains more often than China)
Yeah, funny how a massacre with mass murder (in the 100,000's) and rape (in the 10,000's) kind of paints one side as more of a villain.
That's only because consumer routers have to do stupid crap like NAT and firewalling. ISP routers just push traffic at the IP level, and do not track TCP state whatsoever.
We can argue about degrees of freeness, but the fact that there were debates about the use of drivers (wireless I think), from BSD into Linux, I think it is fair to say there are restrictions implied in BSD too.
Note, I think it is 100% fair to say that BSD is more free for the recipient than GPL.
Right, BSD licensing does not give the freedom to license BSD code under a different license just because you make modifications to it. No license allows that, so you can't really call it a restriction. You can license your own modifications under any license you like however, unlike the GPL.
Right. Comcast has to pay their upstreams (although probably very little per Mb), but AT&T and Verizon (MCI) operate Tier 1 networks, so they are the upstreams. No transit necessary, as per the definition of Tier 1.
Slashdot Mirror
Serverbeach is a dedicated hosting company. They're not going to be scanning memory as they don't have local access to the server. It must be some sort of web crawling or spidering that they do.
So Server Beach has an automated system that detected copyright infringement in a "cache" file and automatically shut down the server before checking to see if it was actually visible to the public (which according to the article it was not)?
If content is visible to your dedicated (not managed) hosting company, who doesn't have any login access to your servers, then yes, the content is visible to the public. Access to it may be obscured, due to removed links to it or however it was supposedly 'removed', but still available to the Internet and henceforth public.
That's because you're trying to buy an old CPU in brand new condition, long after production has stopped. Usually, the best window to buy a CPU new is when the next generation comes out, but you are already 4 (2 ticks + 2 tocks) generations behind. You can easily find the Q9550s used for less than $100.
Read more carefully. It was the husband of one of the partners at the firm representing Samsung, which does not appear to have even been actively involved in the case. Your bias is showing.
You can have a distributed DDoS protection service, where you BGP anycast the IP range being attacked to multiple cities, and deploy DDoS mitigation equipment to each of those locations. In the event that the attack is concentrated in one region, where your DDoS mitigation equipment is unable to keep up, you can then do a localized null route (that doesn't get advertised to the rest of your iBGP mesh), to drop the traffic for that particular region but still stay up for the rest of the world.
Null routes work on destination IPs only, not source IPs, so if one were to take your advice, they would effectively be doing the attackers' job for them. Null routes are for preventing a DoS attack from affecting other customers/services, not for keeping a server up and available during an attack. The only way to block source IPs on routers is with ACLs, but these are only effective against very simple DOS where a small number of sources are attacking you. For a large scale DDoS, with sources from several different ranges attacking protocol/ports on IP addresses where legitimate traffic needs to go (which any smart attacker would do), ACLs aren't going to do it.
CLI commands are not necessarily hacks; they are often the proper way of doing things. Just because they are powerful and flexible enough, that they allow for people who don't know what they're doing to break their systems, doesn't mean that they are inherently bad. It's the GUI's that are often the hacks; they've just been vetted to perform tasks in a standardized, predefined manner. For the most part in Linux land, they are effectively workarounds so that people don't need to learn the proper commands. It's when the GUI is incomplete that users are forced to run the proper commands using the CLI, but those commands themselves are not hacks.
Ack, modded up your original post but modded down this one purely by mistake. Will comment to undo
Canada is a colony of the crown, much like Australia. It is primarily a British-US culture save for some belligerent Frenchies in the East. Canada's original culture was North America Indian including Eskimos (Inuit), which have been marginalized by western culture. Canada's best comedies are take-offs of British shows (Canda's worst Driver) and their original stuff "Corner Gas" is marginally funny. (Kenny vs Spenny, Kids in the Hall, etc successes are short-lived) Anyone sufficiently funny winds up in the US (Lorn Micheal's, Micheal J Fox, etc) however these people are more "American" than Canadian.
Don't get me wrong, I love Canada. But the culture isn't original, it is derivative at best, copied at worst.
Canada hasn't been a colony since 1867. What makes Lorn Michaels and Michael J. Fox more American than Canadian? If anything, can you not say that American culture is affected by Canadians?
The majority of transit providers use a BGP prefix list to limit what IP addresses you are permitted to advertise to them either through manual management of the list or by using a routing registry, so it's not nearly as common as you're implying. The exception is when it comes to peering, but there aren't that many networks that do a significant amount of peering. And if any of your peers catch you IP hijacking, they're likely to de-peer pretty quickly if they discover you're hijacking IP's. Yes, there are a few transit providers who don't follow this properly (the few instances I recall of IP hijacking usually revolved around Sprint), but it's false to assume that just anyone with a BGP connection can just hijack anyone's IP address.
That's ridiculous. I'm all for acknowledging BSD's contributions, but you can't possibly claim nobody would've implemented a stack if the BSD project hadn't. It's as ridiculous as saying the FreeBSD project wouldn't have existed until today without GCC.
Of course we would be on the net, someone else would've written a networking stack for Linux and Microsoft would have either written their own or bought one of the companies which sold third party stacks for Windows.
Sure, except the Linux stack and the Microsoft stack probably wouldn't have been compatible, meaning fragmented networks. In other words, either no universal network of networks i.e. the Internet, or everyone would have been forced to go with Microsoft's solution. One of the benefits of a very liberal license is it's easy for other Operating Systems to adopt. OpenSSH is another obvious example of this.
If they want to give 90% back - which is common behavior for proprietary derivatives of BSD licensed codebases - they can't. They have to give back 100%, or stay out.
And if that's not to their liking, the only thing they miss out on is the gratis skilled labor of strangers. They are still free to write their own code under any license they want. I just don't see the problem, unless of course there is a sense of entitlement to something no one actually owes them. That's the only explanation for why anyone would experience any distress over this.
Or maybe, because the rest of us lose out on the 90% they would have given back?
Flash has worked pretty well on FreeBSD for years now, using nspluginwrapper. ext2 has pretty much always been supported, and ext3 can be mounted as ext2.
No, the article is just written by morons... Current high end Xeons ship without coolers, as have Xeons for many generations, this is because Intel have no clue where the chip is going –it could be into a 1U system, or it could be into something enormous. Basically... Move along, nothing to see here.
Get your facts straight. Xeons still come with coolers if you buy the retail package, or without coolers if you buy OEM, just like with consumer CPUs.
8% is pretty decent, considering most people working in the industry wouldn't even qualify as 'well-trained, ready-to-go'. At least with graduates, there's still the possibility of them getting there, as opposed to all the grossly incompetent veterans with too much ego to ever learn anything new.
What's not desktop ready about the *BSD's these days? What's lacking? The last annoyances like flash support are now easy enough to get working on FreeBSD, portupgrade -PP and freebsd-update make it easy to upgrade both apps and OS using binaries, and nvidia drivers have been around for years. And if you need a dumbed down install process, there's always PC-BSD.
An OS consists of not only the kernel, but also the userland. You need to be able to interface with the kernel at least at some level. Just because GNU/Linux's userland is indistinguishable from third party applications doesn't mean that all operating systems are complete with kernels alone.
Well, any potential future employer can now see how litigious she is, which is going to be much worse than having unrelated spam links show up. I don't think too many employers want to hire a lawsuit waiting to happen.
In any case, if China and Japan duke it out, it won't be about dirt, it will be about a century long conflict (which incidentally has had Japan framed up as the villains more often than China)
Yeah, funny how a massacre with mass murder (in the 100,000's) and rape (in the 10,000's) kind of paints one side as more of a villain.
Or you could just read the latest buying guide from Anandtech. http://www.anandtech.com/tag/guides
Because OpenBSD is represented by a blowfish? It's FreeBSD that has Beastie as its mascot.
That's only because consumer routers have to do stupid crap like NAT and firewalling. ISP routers just push traffic at the IP level, and do not track TCP state whatsoever.
You could just root for the lawyers.
We can argue about degrees of freeness, but the fact that there were debates about the use of drivers (wireless I think), from BSD into Linux, I think it is fair to say there are restrictions implied in BSD too.
Note, I think it is 100% fair to say that BSD is more free for the recipient than GPL.
Right, BSD licensing does not give the freedom to license BSD code under a different license just because you make modifications to it. No license allows that, so you can't really call it a restriction. You can license your own modifications under any license you like however, unlike the GPL.
Right. Comcast has to pay their upstreams (although probably very little per Mb), but AT&T and Verizon (MCI) operate Tier 1 networks, so they are the upstreams. No transit necessary, as per the definition of Tier 1.