This might have been news 7 or 8 months ago when the chips were released.
What's next? ATX Power Supplies Explained? "Plugs into any ordinary wall socket! Flick the switch and it turns on! Use it to power your computer! You'll see them turning up in shops any day now!"
Let me give you a hint, paperweight status means it doesn't work at all... and that's just one manufacturer. I'm going to go out on a limb and guess you aren't a laptop user either. Suspend still doesn't work a significant portion of the time and support for Atheros wireless chipsets has only recently gotten usable, Ralink is average, and Broadcom is still a pile of shit (even with the STA driver.)
Then you've got stuff like Marvell controllers where the Linux driver can either do SATA or PATA, but not both.
2009 called, it wants to know what you've been smoking. Linux hardware support has certainly improved, but it still sucks.
3) resources: ok, this was a far bigger issue with previous hardware and OS's, but it's still my preference not to run/exit/run/exit multiple iterations of any program. To open a new browser for a page I might spend 30 seconds reading seems a waste (and is quite a bit slower than ctrl+t) - on a day of heavy web-browsing, I might open 100+ pages. Perhaps I'm just ignorant and the memory load/memory leakage of multiple tabs is essentially the same for tabs as for multiple iterations, but that's my 'sense' of it - tabs seem less likely to run me out of resources.
This got me thinking... I remember reading somewhere that adding tabs-in-a-thread a la Chrome would be prohibitively painful given Firefox's codebase (can't find a citation though.)... I wonder if this is just them cheating to work around it? Spawn a new instance for every new window?
No, but compared to PCs of the era I could probably get away with calling the SE/20 or SE/30 fashion accessories.
They were certainly great little machines too, but style was key (and that's where you start hearing the anecdotes about Steve micromanaging the UI design of everything.)
It uses a progressive refining encoding, and a probabilistic packet layout to keep the core 'shape' of the sound through all but the most severe conditions, so that losses are likely to only affect the details
If you'd read the article (I know, it's Slashdot etc) you'd know that's exactly what he's describing. The sound was choppy and 'thin' -- that's what happens when you add more jitter or packet loss than the setup can cope with. All things being equal I'm guessing it's not jitter, it's outright packet loss because...
it's possible (and in my mind, hopeful) that what you were experiencing is the result of the airline deliberately choking known VoIP providers, in order to not end up with a plane full of jerks yelling into their laptop for a six hour flight.
I doubt it. I'm sure it's a fairly limited pipe and I'm sure thought has been put into QoS but I doubt very much that they're specifically targeting VoIP traffic. What's more likely is that if the pipe is actually full their shaping is dropping some voice packets, on top of the existing packet loss from the system. You can easily get choppy, thin voice on bad residential DSL, I have no doubt you could get it even on good airplane wifi.
Asterisk 1.4+ has a jitter buffer for at least IAX and SIP which helps to work around jitter in most cases. Given that they know what they're doing, I assume Skype does too.
Jitter is (relatively) okay, it's packet loss that VoIP is particularly sensitive to. Packet loss at levels that will only mildly inconvenience most other traffic will screw up VoIP quite badly... there's no mention of packet loss in the article that I see, but I suspect that's what's causing the poor quality.
I did some work for an adult host years ago, a software gig. It had a tendency to fail under heavy load (cue +5 funny posts in 3.. 2...) but not with synthetic stress tests, so I spent a lot of time watching and waiting for it to fail so I could debug. Absolutely desensitizing, not just for porn but sex in general, and it persisted for a month or two after I left.
Amusing side note: I'd never worked in the industry before and haven't since, so I can't speak to whether you can generalize these numbers to all hosts... I went in there thinking there'd be a bandwidth spike around 8 or 9PM local time. Primarily an American audience, so there was a 5 or 6 hour long peak period as a 2 hour window rolled across North America. What I didn't expect was that there's a similar peak period as ~9:30AM rolls across North America... our theory was that it was people with lower bandwidth connections at home having much better access at work. Or maybe they were just bored.
In any case, if you need something from a co-worker early in the morning,... knock first.
Cameras were banned at my last job. In fact I had to sign several different layers of paperwork saying I wouldn't bring in any cameras, storage devices, blah blah blah.
No way, a 7 year old vulnerability is patched? You'll note that the lead-in to the article talks about previous PaX vulnerabilities that have been patched as well.
The point, which you have so elegantly missed, is that there can and will be issues with the implementation. To think otherwise is foolish.
We will demonstrate that in certain conditions, it is still possible to exploit stack based buffer overflows protected by PaX with all options actived, including the new ET_EXEC binary base address randomizing.
We will show that we can reduce the problem to a standard return-into-libc exploitation. Heap overflows wont be developped, but it might also be possible to exploit them in an ASLR environment using a derived technique.
Slideshows generally have bullet points. You think that might be where "Powerpoint" comes from? And jeez, I can't imagine why they named a database app "Access" You've clearly never used Hypercard or you'd know where that name comes from too. You can mock Safari as a riff off of Explorer, but how does that make it a dumb name for a browser? COM is an acronym... "Component Object Model"
... text has a clear silhouette as well, altering backgrounds and warping the text hasn't seen a great deal of effect there.
There's a limit to how you can rotate the shapes in 3D too, at a certain point they just won't look right. When it's sitting flat and rotated 90 degrees, does the fork really look like a fork or just some weird curved line?
Have two names per machine, a name for the machine itself, and a name for the services the machine provides, CNAME one to the other.
Say that machine's a webserver. Name it nelson, cname webserver01 to it. Setup monitoring using the functional names (webserver01, ns1, etc.) and use the other names for everything else. As people have said elsewhere, machines get repurposed, they rarely get renamed.
Slashdot Mirror
Er, well, here's where I got that from.
If you have a better source, that's cool.
The HostileWRT presentation appears to have been cancelled, which is too bad, it's the only thing in the summary that looks particularly interesting.
The iPhone 3.0 software release date has been given as June 17th although apparently paid developers can get the GM copy now.
You'd think a detail like that could have found its way into the summary somewhere...
He's at an art school. More appropriate advice is likely "Ask for sexual favors from both."
This might have been news 7 or 8 months ago when the chips were released.
What's next? ATX Power Supplies Explained? "Plugs into any ordinary wall socket! Flick the switch and it turns on! Use it to power your computer! You'll see them turning up in shops any day now!"
Who modded this up?
Let me give you a hint, paperweight status means it doesn't work at all... and that's just one manufacturer. I'm going to go out on a limb and guess you aren't a laptop user either. Suspend still doesn't work a significant portion of the time and support for Atheros wireless chipsets has only recently gotten usable, Ralink is average, and Broadcom is still a pile of shit (even with the STA driver.)
Then you've got stuff like Marvell controllers where the Linux driver can either do SATA or PATA, but not both.
2009 called, it wants to know what you've been smoking. Linux hardware support has certainly improved, but it still sucks.
This got me thinking... I remember reading somewhere that adding tabs-in-a-thread a la Chrome would be prohibitively painful given Firefox's codebase (can't find a citation though.) ... I wonder if this is just them cheating to work around it? Spawn a new instance for every new window?
No, but compared to PCs of the era I could probably get away with calling the SE/20 or SE/30 fashion accessories.
They were certainly great little machines too, but style was key (and that's where you start hearing the anecdotes about Steve micromanaging the UI design of everything.)
If you'd read the article (I know, it's Slashdot etc) you'd know that's exactly what he's describing. The sound was choppy and 'thin' -- that's what happens when you add more jitter or packet loss than the setup can cope with. All things being equal I'm guessing it's not jitter, it's outright packet loss because...
I doubt it. I'm sure it's a fairly limited pipe and I'm sure thought has been put into QoS but I doubt very much that they're specifically targeting VoIP traffic. What's more likely is that if the pipe is actually full their shaping is dropping some voice packets, on top of the existing packet loss from the system. You can easily get choppy, thin voice on bad residential DSL, I have no doubt you could get it even on good airplane wifi.
Asterisk 1.4+ has a jitter buffer for at least IAX and SIP which helps to work around jitter in most cases. Given that they know what they're doing, I assume Skype does too.
Jitter is (relatively) okay, it's packet loss that VoIP is particularly sensitive to. Packet loss at levels that will only mildly inconvenience most other traffic will screw up VoIP quite badly... there's no mention of packet loss in the article that I see, but I suspect that's what's causing the poor quality.
People who pay for support for commercial software which only has glibc as a supported platform (which will be most of it for the foreseeable future.)
From eglibc's mission statement:
"Retain API and ABI compatability with GLIBC wherever feasible."
Yeah, that's going to end well...
It's absolutely true.
I did some work for an adult host years ago, a software gig. It had a tendency to fail under heavy load (cue +5 funny posts in 3.. 2...) but not with synthetic stress tests, so I spent a lot of time watching and waiting for it to fail so I could debug. Absolutely desensitizing, not just for porn but sex in general, and it persisted for a month or two after I left.
Amusing side note: I'd never worked in the industry before and haven't since, so I can't speak to whether you can generalize these numbers to all hosts... I went in there thinking there'd be a bandwidth spike around 8 or 9PM local time. Primarily an American audience, so there was a 5 or 6 hour long peak period as a 2 hour window rolled across North America. What I didn't expect was that there's a similar peak period as ~9:30AM rolls across North America... our theory was that it was people with lower bandwidth connections at home having much better access at work. Or maybe they were just bored.
In any case, if you need something from a co-worker early in the morning, ... knock first.
Cameras were banned at my last job. In fact I had to sign several different layers of paperwork saying I wouldn't bring in any cameras, storage devices, blah blah blah.
What was the first thing they issued me?
A cell phone with a camera in it.
Either they're really going to regret promising that, or they're hiding some dirty little secret...
Bahaha.
Yeah. Shame that if this shapes up like the 1918 pandemic it'll be the people with the strongest immune systems who are hit the hardest.
No way, a 7 year old vulnerability is patched? You'll note that the lead-in to the article talks about previous PaX vulnerabilities that have been patched as well.
The point, which you have so elegantly missed, is that there can and will be issues with the implementation. To think otherwise is foolish.
http://www.phrack.com/issues.html?issue=59&id=9
Quoth the article:
Erm, what? A lot of those aren't silly.
Slideshows generally have bullet points. You think that might be where "Powerpoint" comes from?
And jeez, I can't imagine why they named a database app "Access"
You've clearly never used Hypercard or you'd know where that name comes from too.
You can mock Safari as a riff off of Explorer, but how does that make it a dumb name for a browser?
COM is an acronym... "Component Object Model"
Etc. etc.
... text has a clear silhouette as well, altering backgrounds and warping the text hasn't seen a great deal of effect there.
There's a limit to how you can rotate the shapes in 3D too, at a certain point they just won't look right. When it's sitting flat and rotated 90 degrees, does the fork really look like a fork or just some weird curved line?
... so what was it? I haven't found anything obvious in Google.
Yeah unless you generated them on a Debian machine...
Hans, is that you?
... because implementation is where people screw up.
Have two names per machine, a name for the machine itself, and a name for the services the machine provides, CNAME one to the other.
Say that machine's a webserver. Name it nelson, cname webserver01 to it. Setup monitoring using the functional names (webserver01, ns1, etc.) and use the other names for everything else. As people have said elsewhere, machines get repurposed, they rarely get renamed.