Now, there's the problem. Within a few months time, it will get increasingly more difficult to find business desktops and laptop systems that will run XP. The consumer already has no choice. That's what "support" means. PC manufacturers, developers, everyone who's getting along, will no longer develop and test products for XP. This better sinks in: in a year's time, it's virtually impossible to get new (business class) hardware that runs this ancient OS. If you need to replace, update, upgrade or expand, you will be stuck, and you will be forced into migration at the least convenient moment.
Apparently, nobody knows or remembers that BPA is (including me), the summary doesn't tell us why it's interesting -- which is crucial -- instead it just copies the two least-informative lines out of a apparent non-story, and Slashdot is happy to dump the link on the front page.
If it weren't for that lazy cock of an editor we could be having an informed discussion about this. Instead, some more of these and Slashdot is on its way to become a damn link posting contest. kdawson, if you don't feel like writing articles about stuff then I'd prefer that you don't even try.
Ah, after scanning the thread for your posts I gather that your classroom switch blew up. That's tough. Could you get a network up and running in virtual machines? Linux boxes on KVM with vyatta or something?
Now, I know that unteer is not necessarily looking for a bunch of videos of the OSI model to show, but I think this one: http://www.youtube.com/watch?v=vtsEH4HeVlw&feature=related in particular touches all the points you could educate people on to get a good onderstanding of the networking picture. I know that it was this kind of explanation (the need for the layers and the understanding of encapsulation) that got me started on networking many years ago.
There must be better vids out there that animate the process of encapsulation. All implementation details and technologies then stem from the theory.
I don't know if it's necessary or particularly helpful to simulate a detailed homogeneous network model. Confining the examples to specific, well-known protocols at first doesn't do justice to the actual practice of networking. If you educate them layer by layer (from the ground up), you can possibly make it easier on yourself, by building on previous lessons and tailoring the presentation to the subject at hand. So, first lesson is physical media, properties of electricity, light, EM waves, go on to frames, what a switch does and why, why 802.3 doesn't work for wireless, expand to logical networks and routing (where you prepare a fictional/virtual router and tell them what a huge mess the Internet would be without them). If you got your students going on the extremely esoteric matter of binding applications to the transport layer, maybe then you could throw in some live examples of a http or telnet session, but I wouldn't recommend it as an introduction.
Run her over properly, next time, thank you. I feel sorry for the car driver who got sucked into this mess. I'd try to prove the opposite; like others mentioned before, this sounds like trolling for damages.
The Mass Effect universe is so big, the movie does not have to replicate every element in the game to be faithful. The universe may even be suited to make it an Umptilogy, progressing storylines of several species throughout the universe. Like LOTR, but less boring.
It has nothing to do with "the average customer". The OEM is required to offer product support for OEM versions of Microsoft products which come pre-installed on hardware they sell. The OEM may also not charge for support in the first 90 days after purchase. You must be a) not aware of the OEM licensing terms or b) your shop is doing something really stupid/illegal.
The parent is wrong w.r.t. the factoring part, but it does make sense.
You don't factor the public key (it may even be prime), but you can factor the public modulo (which is part of both the public-key and private-key pair).
The modulo is a product of two prime numbers (with certain properties) and it mathematically links the public and private keys together.
There is only one correct answer to factoring the modulo, and if you do so you have figured the relationship between the public and private key. Then you can not only derive the private key from the public key, but then you also know for certain that it is the correct private key.
They don't take it away. You just get the leftover bandwidth, after everybody who uses the internet in bursts. Strictly speaking, you must be causing delays to other customer's traffic first before you notice any throttling.
TFA says that it may cause packet loss in extreme situations, but I wonder if they couldn't just guarantee 25% or so just to keep the connection reliable.
Excuse me, this was intended as a general comment. I don't want to imply you didn't understand the throttling part. But it may imply that it's hard to notice when you're being throttled, and rather difficult to find the limits of this system.
Internet packets to and from a specific subscriber are assigned 'Priority Best Effort' (PBE) queueing by default, and the traffic rate is throttled by switching packets to lower priority 'Best Effort' (BE) queueing.
So, throttling in this case simple means that your traffic is delivered after alle PBE traffic (all other customers) was dealt with in the router's queues. That also means that you'll hardly notice the difference when there's no congestion, but it may also cause complete packet loss at busy times.
Something TFS fails to note is this, at the bottom of TFA:
Comcast has also imposed a monthly 250GB bandwidth usage cap on all of its customers, and it will, after one warning, terminate service for one year to those who exceed that cap twice within a six-month period.
I have to go to computer stores with my Dad when he tries to buy something simple like an ethernet cable or a power strip or he'll come home with a Cisco switch and an APC rackmount battery backup.
That's the good part. On the switch though, make sure to get the shiny ones with a support contract, otherwise wiring the house with 40Gbit redundant etherchannels will be easier than getting new firmware for the damn thing.
The OEM agreement that the PC and laptop manufacturers have with MS, otoh, is very real. As it stands now, they are simply required to ship their products with the OS installed and, not in the least, the manufacturer must also support the OS upto a period of 90 days. In return they receive the OEM discount. That means that if the manufacturer decides to stick with Windows, then it will tailor the product so that it works with Windows. The development and testing that goes with creating a decent product that works with a specific OS is a major part of the business that must somehow be paid for. If a large part of Lenovo's customer base were refunded on the OS, they'd not only lose a lot of revenue but also incur the support issues, negative side-effects of hard/software incompatibily as well as risk losing Microsoft OEM status. Either way, the price of hardware would just go up.
That said, I reckon that going with an ever-evolving OS with a gazillion different flavors (maybe not BSD but Linux in general) would require quite a spine, not to mention love for human kind and a matching bank account.
Slashdot Mirror
AC: The above trick is also pretty good if you don't want to stare at someone's eyes but you don't also want to start looking around either.
What was your score on the Turing Test? "Human but coward."
if XP works for you, stick with it
Now, there's the problem. Within a few months time, it will get increasingly more difficult to find business desktops and laptop systems that will run XP. The consumer already has no choice. That's what "support" means. PC manufacturers, developers, everyone who's getting along, will no longer develop and test products for XP. This better sinks in: in a year's time, it's virtually impossible to get new (business class) hardware that runs this ancient OS. If you need to replace, update, upgrade or expand, you will be stuck, and you will be forced into migration at the least convenient moment.
"Stick with XP". No, that's really good advice.
Pay attention!
There is just one previous appearance of this topic here, back in 2009, at http://science.slashdot.org/article.pl?sid=09/05/24/1830239
Apparently, nobody knows or remembers that BPA is (including me), the summary doesn't tell us why it's interesting -- which is crucial -- instead it just copies the two least-informative lines out of a apparent non-story, and Slashdot is happy to dump the link on the front page.
If it weren't for that lazy cock of an editor we could be having an informed discussion about this. Instead, some more of these and Slashdot is on its way to become a damn link posting contest. kdawson, if you don't feel like writing articles about stuff then I'd prefer that you don't even try.
Ah, after scanning the thread for your posts I gather that your classroom switch blew up. That's tough. Could you get a network up and running in virtual machines? Linux boxes on KVM with vyatta or something?
What, nobody mentioned osischool?
ARP: http://www.osischool.com/protocol/arp/basic
Routing: http://www.osischool.com/protocol/routing/static-routing
And a few more.
Now, I know that unteer is not necessarily looking for a bunch of videos of the OSI model to show, but I think this one: http://www.youtube.com/watch?v=vtsEH4HeVlw&feature=related in particular touches all the points you could educate people on to get a good onderstanding of the networking picture. I know that it was this kind of explanation (the need for the layers and the understanding of encapsulation) that got me started on networking many years ago.
There must be better vids out there that animate the process of encapsulation. All implementation details and technologies then stem from the theory.
I don't know if it's necessary or particularly helpful to simulate a detailed homogeneous network model. Confining the examples to specific, well-known protocols at first doesn't do justice to the actual practice of networking. If you educate them layer by layer (from the ground up), you can possibly make it easier on yourself, by building on previous lessons and tailoring the presentation to the subject at hand. So, first lesson is physical media, properties of electricity, light, EM waves, go on to frames, what a switch does and why, why 802.3 doesn't work for wireless, expand to logical networks and routing (where you prepare a fictional/virtual router and tell them what a huge mess the Internet would be without them). If you got your students going on the extremely esoteric matter of binding applications to the transport layer, maybe then you could throw in some live examples of a http or telnet session, but I wouldn't recommend it as an introduction.
Good luck.
Run her over properly, next time, thank you. I feel sorry for the car driver who got sucked into this mess. I'd try to prove the opposite; like others mentioned before, this sounds like trolling for damages.
The Mass Effect universe is so big, the movie does not have to replicate every element in the game to be faithful. The universe may even be suited to make it an Umptilogy, progressing storylines of several species throughout the universe. Like LOTR, but less boring.
It has nothing to do with "the average customer". The OEM is required to offer product support for OEM versions of Microsoft products which come pre-installed on hardware they sell. The OEM may also not charge for support in the first 90 days after purchase. You must be a) not aware of the OEM licensing terms or b) your shop is doing something really stupid/illegal.
The parent is wrong w.r.t. the factoring part, but it does make sense.
You don't factor the public key (it may even be prime), but you can factor the public modulo (which is part of both the public-key and private-key pair).
The modulo is a product of two prime numbers (with certain properties) and it mathematically links the public and private keys together.
There is only one correct answer to factoring the modulo, and if you do so you have figured the relationship between the public and private key. Then you can not only derive the private key from the public key, but then you also know for certain that it is the correct private key.
http://fringe.davesource.com/Fringe/Crypt/RSA/Algorithm.html
Huhuhhuh... He said Descent.
I threw up after playing that for four hours straight.
They don't take it away. You just get the leftover bandwidth, after everybody who uses the internet in bursts. Strictly speaking, you must be causing delays to other customer's traffic first before you notice any throttling.
TFA says that it may cause packet loss in extreme situations, but I wonder if they couldn't just guarantee 25% or so just to keep the connection reliable.
Excuse me, this was intended as a general comment. I don't want to imply you didn't understand the throttling part. But it may imply that it's hard to notice when you're being throttled, and rather difficult to find the limits of this system.
Internet packets to and from a specific subscriber are assigned 'Priority Best Effort' (PBE) queueing by default, and the traffic rate is throttled by switching packets to lower priority 'Best Effort' (BE) queueing.
So, throttling in this case simple means that your traffic is delivered after alle PBE traffic (all other customers) was dealt with in the router's queues.
That also means that you'll hardly notice the difference when there's no congestion, but it may also cause complete packet loss at busy times.
Something TFS fails to note is this, at the bottom of TFA:
Comcast has also imposed a monthly 250GB bandwidth usage cap on all of its customers, and it will, after one warning, terminate service for one year to those who exceed that cap twice within a six-month period.
He's trying to ask if you have any aspirin.
Can you please just show the mathematical equation for this curve of which you speak? That way we won't have to use imprecise words.
y = x on a learning curve with a shallow incline.
That's because time slows down if your head is into complicated stuff.
Anything that Cisco Systems, Alcatel-Lucent, Corning, Ericsson, Motorola and Nokia do is evil, restricts freedoms and is inefficient by definition.
So please, stop this evil QoS in it's tracks.
There, fixed that for you.
The other 59% of disk space occupied by legal software consists entirely of Adobe Reader.
Worked for the guy with the Verizon Math story :D
That was a myth.
I have to go to computer stores with my Dad when he tries to buy something simple like an ethernet cable or a power strip or he'll come home with a Cisco switch and an APC rackmount battery backup.
That's the good part. On the switch though, make sure to get the shiny ones with a support contract, otherwise wiring the house with 40Gbit redundant etherchannels will be easier than getting new firmware for the damn thing.
lets readers glance at pages and browse through them quickly without having to wait for multiple page elements to load
That's easy enough for them to say, with a spare copy of the Internet.
Allegedly.
I'll get back to that after loading page 2.
1) Get the most awesome PC game title
2) Get the even more awesome iPhone controller
3) ?!??
4) Lose!
There was never anybody to kill in the first place.
Hell yeah.
The OEM agreement that the PC and laptop manufacturers have with MS, otoh, is very real. As it stands now, they are simply required to ship their products with the OS installed and, not in the least, the manufacturer must also support the OS upto a period of 90 days. In return they receive the OEM discount.
That means that if the manufacturer decides to stick with Windows, then it will tailor the product so that it works with Windows. The development and testing that goes with creating a decent product that works with a specific OS is a major part of the business that must somehow be paid for. If a large part of Lenovo's customer base were refunded on the OS, they'd not only lose a lot of revenue but also incur the support issues, negative side-effects of hard/software incompatibily as well as risk losing Microsoft OEM status. Either way, the price of hardware would just go up.
That said, I reckon that going with an ever-evolving OS with a gazillion different flavors (maybe not BSD but Linux in general) would require quite a spine, not to mention love for human kind and a matching bank account.