You missed an interesting thing about GPON/BPON though - the great part of it is that the standard 'push' TV channels - i.e. not on-demand - don't need to be IPTV. The B/GPON specs provide 870 MHz of quasi-analog bandwidth that does not affect the IP traffic (see FiOS Wikipedia page, oddly it's not discussed well on the GPON page), so it's actually most beneficial to avoid IPTV as much as possible. It's a remarkably well-thought-out standard.
to a population curve. Very slow growth at first, becoming exponential, and finally curving to a gentle more-or-less linear slope. The derivative looks like a bell curve. The graphs provided by Wikipedia appear to fit what I would expect as the derivative of a highly neurotic population curve. I bet if you graph the numbers that the graphs are supposed to represent (i.e. edits, articles, etc), as opposed to the increase thereof, you get a population curve.
tl;dr: Wikipedia is not dying. It's just becoming mature.
To give credit to the Evanglist, perhaps he was hoping coworkers and superiors at Intel would recognize the need and step up.
An interesting point. I would say he's definitely trying to get someone to step up, and Intel does have the people who could do just that... (be good for the multi-core market)
You know, I just read your comment history. I used to be a troll like you. I just posted whatever the hell came to my mind whether it be random crap or songs about my penis or just a quick "frist psot". It was a small release, a little bit of humor in my otherwise boring life.
But trolling became an addiction to me... soon I was doing everything I could to get a rise out of fellow netizens. I basically spent all my time trolling Slashot and other various forums. Of course Slashot was my favorite trolling venue because the demographic was a perfect fit for me. Imagine the endless sources of amusement Slashot gave to someone like me, a self-hating sociophobe who enjoyed nothing more than hating other people just like myself. So, for example, I would sit in front of my computer on a Friday night and blast anyone on Slashot that would post something. I would call them losers for not having anything better to do than reading Slashdot on a Friday night! Classical projection at its finest.
Of course, all addicts have to hit a rock bottom before they become willing to change their behavior. That happened to me on July 6, 2003. I remember it like it was yesterday. I had found my ultimate prey: a seasoned Slashdot poster who just couldn't resist feeding the trolls. I basically "stalked him"... hitting refresh countless time waiting for him to make a comment, then instantly posting a personal attack. He never failed to respond, which just fed my addiction. But then one day, I got a knock on my door from the FBI, cybercrimes division. It was then that my mom got scared and said, "You're moving in with your auntie and uncle in Bel-Air." I whistled for a cab and when it came near the license plate said "fresh" and it had dice in the mirror, if anything I could say that this cab was rare but I thought: "Man, forget it, yo home to Bel-air!" I pulled up to the house about seven or eight and I yelled to the cabbie "Yo homie, smell you later." I looked at my kingdom, I was finally there, to sit on my throne as the prince of Bel-air.
That would be even more expensive. Analog lines are rediculously expensive, and the phone company really likes to charge for running more than one to a residence...
Now that you mention it, one of the standard contracts signed for any kind of summer camp or whatever is a publicity release - so that THEY can use the photos for marketing.
That's not what grandparent is referring to. He's referring to the DNS server setting. Each computer has to be able to access a DNS server to resolve domain names. IPv6 autoconf doesn't have that.
You underestimate children. And the OS UI is written in Python, not compatible with anything out there.
Not compatible? You mean like how Firefox is the built-in browser and it is rediculously easy to switch to the built-in Gnome interface? Download and try the Live CD before you criticize it.
As am I, but I read about it in a trade mag from the time, wish I still had it...
So, at the risk of losing my karma for being way off-topic...
From what I read/recall, basically, a PSTN trunk router overloaded and shut down, forwarding its circuits to another trunk router, which overloaded and shut down, etc, until, basically (because the Baby Bells (read: AT&T) still ran the entire phone system at the long-distance level) no long distance calls could be made. The trade mag I read had a few lines of code that I didn't really understand that they said were responsible for the domino effect there, but that's just even more off-topic. Anyway, thus the pun about domino servers. Not referring to Lotus - IBM seems to make good products in general.
No, because bittorrent clients are only connected to trackers for a matter of seconds, if that. Bittorrent is peer-to-peer - p2p connections are getting RST'd. And there is no way for userspace software (the BT clients) to ignore RST packets (sockets are handled at kernel level), and NO, we are NOT putting BT clients in kernel space, that would be ugly at best, heh...
Sorry, but you're wrong.
If Comcast sends RST packets to both ends of the connection (and why wouldn't they?), it doesn't matter whether or not you're dropping them, it matters that the other guy isn't.
Don't all of them? I personally consider Internet absolutely critical for schools. Also the district's intranet (which I've seen consist of a single box running as a Windows Domain Master and file server). If either of these go down, things stop working.
Assuming this is a small school district, or even a moderately large one, we're not talking about an organization funded like an enterprise. These aren't the kind of organizations that can afford to hire first-class network professionals to design the infrastructure. Someone trips over an important cable, or accidentally crashes the server, or wonders why a cable is loose so they plug the other end of that crossover cable back into the same dumb switch, creating a broadcast loop that takes down that whole subnet. ...and then, of course, say nothing, because they don't realize what they did.
It's not unheard of, although it should be. I've seen all three of these happen, and all of them are pretty critical. And no, you don't wait an hour for this sort of thing, or take an hour from troubleshooting to go do something else stressful that might be that much harder due to the problem you'd be abandoning.
And like it or not, (and I really don't) there are people whose problems take precedence. Minor problems shouldn't ever take precedence over education, but sometimes they do.
Wired is not complaining that Facebook itself is difficult to access. Their complaint is that there is no way to access the data within Facebook, from without. Can you aggregate, say, your news feed, and a particular friend's Facebook "photostream" (thank you Flickr for that Web 2.0 term) alongside CNN and Slashdot on, say, Google Reader or Bloglines? If you've not tried it, the answer is no. You could, of course, point to Facebook applications, but they're embedded into Facebook, not the other way around.
What Wired is talking about is a social networking site that either is an aggregate itself of other sites (what they tried to implement, and a neat concept) or, at least, makes its data available for use on other sites.
Maybe. On the other hand, maybe they can't - companies like Dell and HP can do that because they have many people wanting it - instead of overnighting a few parts a day, or week, they have massive amounts of stock on-hand - possibly even mostly assembled and ready to ship within a few hours - ready to ship out overnight to you within a couple of days. As it is, if you're trying to make something cheaply, you need to reduce overhead. That means reducing stock on-hand that you're not moving, reducing even the space you have to put backup stock.
You're confusing where hybrid applies to Linux. It is a hybrid-monolithic macrokernel (hyphen added for clarity). Monolithic, meaning it's all in one piece. Hybrid-monolithic meaning it's all in one piece, but other pieces can be loaded into it on-the-fly. It's still a macrokernel - modules are not other processes - but not entirely monolithic.
Thank Gawd Linux isn't using any relic of an OS that started in the 1970's as its base! No, no, all 100% 21st clean legacy-free implementation there.
Indeed, thank Goddess it isn't. You'll notice it's evolved over it's ~15 years of life significantly. Journalling filesystems, ACL-enabled filesystems, b-tree filesystems... and that's just the FS concepts that nobody dreamed of in the 70s. Oh, and there are snapshot-ish FS's if that's your thing (ala VMS). New schedulers, new threading systems, new power management systems, new security systems, new memory management systems, all based on concepts that didn't exist in the 70s, or even when Linux was born.
For the record, I'd say that Linux is far past its 21st implementation. 100% clean legacy-free code? Not by a long shot. But from what I understand, most of the kernel is relatively clean. There is a lot of legacy code in it, but not much, and a lot of it is scheduled for removal from the kernel. It sticks around in that state for a while to give people time to migrate from, say, DevFS (which never reached stable, but was so nice everyone used it anyway) to udev. And some code is there that hasn't been touched for years, because someone uses it and there is no reason to throw it out. If it works, why scrap it?
Many people pay a flat rate for GPRS, just like Internet access.
You could say that, and I know for a fact the cell phone companies do as well, and they're full of shit. No offense - one would normally assume that an "unlimited" data plan does in fact mean unlimited (and does with some carriers and some plans - the ~$50 ones for Verizon's EVDO PCMCIA cards for example). Your standard ~$20/mo "unlimited" data plan is (on AT&T) capped at 6 MB. After that, you pay the same 1c/kB as everyone else. I'm sure you'd find similar restrictions in the small print on data plans for all carriers.
The normal charge - barring a limited plan that provides a discount for purchasing x bandwidth - is one cent per kilobyte on AT&T. That is in fact charging per packet, or group thereof. I'm not familiar with GPRS standards so I don't know how big a packet is/can be. Note that, as I stated above, this charge still applies when you exceed the limit on your flat-rate "unlimited" plan.
Anyway, my point here is don't knock it because there are exceptions. A lot of upper-end Internet connections charge by the packet, or rather group thereof, as well.
You forgot that SLES is Linux. (Including Cray's UNICOS derivatives.) So is Red Hat. Go ahead and add those in, and you've got about 80%, well over ten times the runner-up AIX.
Slashdot Mirror
Mod parent down - GPON is an ITU standard, there is nothing proprietary about it. See the Wikipedia article for GPON.
Excellent point.
You missed an interesting thing about GPON/BPON though - the great part of it is that the standard 'push' TV channels - i.e. not on-demand - don't need to be IPTV. The B/GPON specs provide 870 MHz of quasi-analog bandwidth that does not affect the IP traffic (see FiOS Wikipedia page, oddly it's not discussed well on the GPON page), so it's actually most beneficial to avoid IPTV as much as possible. It's a remarkably well-thought-out standard.
to a population curve. Very slow growth at first, becoming exponential, and finally curving to a gentle more-or-less linear slope. The derivative looks like a bell curve. The graphs provided by Wikipedia appear to fit what I would expect as the derivative of a highly neurotic population curve. I bet if you graph the numbers that the graphs are supposed to represent (i.e. edits, articles, etc), as opposed to the increase thereof, you get a population curve.
tl;dr: Wikipedia is not dying. It's just becoming mature.
An interesting point. I would say he's definitely trying to get someone to step up, and Intel does have the people who could do just that... (be good for the multi-core market)
News to me. Thanks!
...I have done a bad thing.
That would be even more expensive. Analog lines are rediculously expensive, and the phone company really likes to charge for running more than one to a residence...
much the same as bayimg, i imagine - not so much that the child porn is illegal, as that it offends the admins
just my 2c
Now that you mention it, one of the standard contracts signed for any kind of summer camp or whatever is a publicity release - so that THEY can use the photos for marketing.
Yeah... Networkworld is the Weekly World News of technology blogs.
That's not what grandparent is referring to. He's referring to the DNS server setting. Each computer has to be able to access a DNS server to resolve domain names. IPv6 autoconf doesn't have that.
You underestimate children. And the OS UI is written in Python, not compatible with anything out there.
Not compatible? You mean like how Firefox is the built-in browser and it is rediculously easy to switch to the built-in Gnome interface? Download and try the Live CD before you criticize it.
As am I, but I read about it in a trade mag from the time, wish I still had it...
So, at the risk of losing my karma for being way off-topic...
From what I read/recall, basically, a PSTN trunk router overloaded and shut down, forwarding its circuits to another trunk router, which overloaded and shut down, etc, until, basically (because the Baby Bells (read: AT&T) still ran the entire phone system at the long-distance level) no long distance calls could be made. The trade mag I read had a few lines of code that I didn't really understand that they said were responsible for the domino effect there, but that's just even more off-topic. Anyway, thus the pun about domino servers. Not referring to Lotus - IBM seems to make good products in general.
I thought we decided domino servers were a bad idea after the AT&T fiasco in 1994?
No, no page 2 button. MadPenguin just sucks, you're not missing anything.
No, because bittorrent clients are only connected to trackers for a matter of seconds, if that. Bittorrent is peer-to-peer - p2p connections are getting RST'd. And there is no way for userspace software (the BT clients) to ignore RST packets (sockets are handled at kernel level), and NO, we are NOT putting BT clients in kernel space, that would be ugly at best, heh...
Sorry, but you're wrong. If Comcast sends RST packets to both ends of the connection (and why wouldn't they?), it doesn't matter whether or not you're dropping them, it matters that the other guy isn't.
Don't all of them? I personally consider Internet absolutely critical for schools. Also the district's intranet (which I've seen consist of a single box running as a Windows Domain Master and file server). If either of these go down, things stop working.
Assuming this is a small school district, or even a moderately large one, we're not talking about an organization funded like an enterprise. These aren't the kind of organizations that can afford to hire first-class network professionals to design the infrastructure. Someone trips over an important cable, or accidentally crashes the server, or wonders why a cable is loose so they plug the other end of that crossover cable back into the same dumb switch, creating a broadcast loop that takes down that whole subnet.
...and then, of course, say nothing, because they don't realize what they did.
It's not unheard of, although it should be. I've seen all three of these happen, and all of them are pretty critical. And no, you don't wait an hour for this sort of thing, or take an hour from troubleshooting to go do something else stressful that might be that much harder due to the problem you'd be abandoning.
And like it or not, (and I really don't) there are people whose problems take precedence. Minor problems shouldn't ever take precedence over education, but sometimes they do.
Wired is not complaining that Facebook itself is difficult to access. Their complaint is that there is no way to access the data within Facebook, from without. Can you aggregate, say, your news feed, and a particular friend's Facebook "photostream" (thank you Flickr for that Web 2.0 term) alongside CNN and Slashdot on, say, Google Reader or Bloglines? If you've not tried it, the answer is no. You could, of course, point to Facebook applications, but they're embedded into Facebook, not the other way around.
What Wired is talking about is a social networking site that either is an aggregate itself of other sites (what they tried to implement, and a neat concept) or, at least, makes its data available for use on other sites.
Maybe. On the other hand, maybe they can't - companies like Dell and HP can do that because they have many people wanting it - instead of overnighting a few parts a day, or week, they have massive amounts of stock on-hand - possibly even mostly assembled and ready to ship within a few hours - ready to ship out overnight to you within a couple of days. As it is, if you're trying to make something cheaply, you need to reduce overhead. That means reducing stock on-hand that you're not moving, reducing even the space you have to put backup stock.
You're confusing where hybrid applies to Linux. It is a hybrid-monolithic macrokernel (hyphen added for clarity). Monolithic, meaning it's all in one piece. Hybrid-monolithic meaning it's all in one piece, but other pieces can be loaded into it on-the-fly. It's still a macrokernel - modules are not other processes - but not entirely monolithic.
Indeed, thank Goddess it isn't. You'll notice it's evolved over it's ~15 years of life significantly. Journalling filesystems, ACL-enabled filesystems, b-tree filesystems... and that's just the FS concepts that nobody dreamed of in the 70s. Oh, and there are snapshot-ish FS's if that's your thing (ala VMS). New schedulers, new threading systems, new power management systems, new security systems, new memory management systems, all based on concepts that didn't exist in the 70s, or even when Linux was born.
For the record, I'd say that Linux is far past its 21st implementation. 100% clean legacy-free code? Not by a long shot. But from what I understand, most of the kernel is relatively clean. There is a lot of legacy code in it, but not much, and a lot of it is scheduled for removal from the kernel. It sticks around in that state for a while to give people time to migrate from, say, DevFS (which never reached stable, but was so nice everyone used it anyway) to udev. And some code is there that hasn't been touched for years, because someone uses it and there is no reason to throw it out. If it works, why scrap it?
Great-grandparent, that's what we call an "Oh snap!" rebuttal.
You could say that, and I know for a fact the cell phone companies do as well, and they're full of shit. No offense - one would normally assume that an "unlimited" data plan does in fact mean unlimited (and does with some carriers and some plans - the ~$50 ones for Verizon's EVDO PCMCIA cards for example). Your standard ~$20/mo "unlimited" data plan is (on AT&T) capped at 6 MB. After that, you pay the same 1c/kB as everyone else. I'm sure you'd find similar restrictions in the small print on data plans for all carriers.
The normal charge - barring a limited plan that provides a discount for purchasing x bandwidth - is one cent per kilobyte on AT&T. That is in fact charging per packet, or group thereof. I'm not familiar with GPRS standards so I don't know how big a packet is/can be. Note that, as I stated above, this charge still applies when you exceed the limit on your flat-rate "unlimited" plan.
Anyway, my point here is don't knock it because there are exceptions. A lot of upper-end Internet connections charge by the packet, or rather group thereof, as well.
You forgot that SLES is Linux. (Including Cray's UNICOS derivatives.) So is Red Hat. Go ahead and add those in, and you've got about 80%, well over ten times the runner-up AIX.