Yahoo's power and success comes from multi platform awareness,
For the most part, yes, but the yahoo IM client differs significantly in capability and support from platform to platform.
I checked Live.com the day it was announced. When it bitched about not using IE (when I tried to login my passport account) , I never visited it back. That is what makes every MS attempt unsuccessful. They can't live with the fact that there is a thing called HTML standard, TCPIP standard and Internet is platform neutral from beginning. They use every opportunity to alienate other OS/Browser users.
If ms does get yahoo, they may find that their desktop monopoly won't help them leverage crap as it has for all the other products they've bought and downgraded. The Internet is turf foreign to their business model and corporate mindset, and buying yahoo won't change that. As if anything could. If this deal goes through, yahoo goes down.
Firms are finding that they can skip cabling and adopt wireless networks. The next step is to give each machine a direct Internet connection, with appropriate security technology, skipping the LAN, he predicted.
If you want to call wireless technology a form of LAN technology, then the LAN doesn't really go away, does it? Designations like LAN, WAN, MAN are all kind of arbitrary. Where I work, we've got a 100Mb ethernet connection to TimeWarner's piece of the backbone. So, our web servers go from ethernet to ethernet to Internet. The only boundaries that seem to have substantive transitional meaning are the BGP ones from the point of view of the Internet. If you want to call what you have on your side of the boundary a LAN or a MAN or a non-LAN wireless LAN, go for it. If you have an ethernet connection to your ISP and think that means your wireless LAN isn't a LAN, fine.
As for wireless interference, the FCC will have to regulate any frequencies before they can be considered reliable enough for profit-motive servers to run on. The current 2.4Ghz is way too bespectacled with every fun gadget from phones to cameras to be considered on par with wires. And, no matter what you do, wireless will always be seen in the eyes of finance security types as less secure than wires.
The one scenario in which the LAN might be unrecognizable from its current form might be if the Internet ran on a global wireless mesh. A cool concept, but impractical in many ways - oceans aren't distance friendly and such a large scale mesh could be a routing behemoth dwarfing the measly 240,000 entry Internet routing table.
True nerds don't have any friends, YOU INSENSITIVE CLOD!!!
'True' Nerds do have friends - they just don't occur together in large numbers and share some focused intellectual and/or imaginative interest as opposed to a more generalized run-of-the-mill interest. Groups typically somewhere in the neighborhood of 3d4 or so.
It is something comparable to the pope releasing an "updated" version of the bible, or Stallman deciding to release an "updated" version of the GPL v2.0.
Umm... the bible is a collection of ancient literature, and the writings of hubbard are science fiction. The GPL is a legal license - it doesn't even have a plot line. How much more apples to oranges can you get?
Besides, search though I might, I could not find instructions for the holy hand grenade of antioch anywhere in the GPL. It clearly needs to be updated. And blessed some more by his holiness RMS.
This idea of his doesn't make much more sense that his idea for how the IT dept will 'go away', seeing as how this idea is built on his earlier flawed idea.
He envisions a utility computing era where "managing an entire corporate computing operation would require just one person sitting at a PC and issuing simple commands over the Internet to a distant utility."
IT seems more like accounting than electricity, except that due to the highly tractable nature of programming, it often serves more diverse needs.. Last time I looked, anyplace with more than 100 employees had more than one accountant. Really, the author seems to be on crack.
I do find the tab completion handy. The shell in IOS tab completes/lists all the parameters for a given command as well. I haven't found a way to get bash and zsh to do that.
When two routers are set up in failover, by definition one of them is primary. If only default routes are used, all traffic goes through one ISP, not both. If you're paying for the extra bandwidth, why not use it?
I don't know - I wish unix had the command parameter prompting system that the shell in IOS has. It's actually really useful. Not sure what the parameters are for any command? Press the question mark key.
You are trapped in a maze of twisty, little prompts, all alike
Actually, the prompts change with context. Configuration mode has a different prompt, and within that mode the prompts change with context indicating what you're configuring
That said, I really wish IOS would positionally preserve all comments in the config file, not just in access lists. That would be really useful, as in being able to more fully document the configuration.
How would you do failover with a linksys or d-link router? After all if one ISP has a problem, you'll want to failover to the other, right? Does linksys and d-link support BGP? How would you do complete redundancy including switches in a two-ISP setting with either linksys or d-link? How many failover routers does linksys support? Does linksys or d-link support ssh? (I'd really like to know). Does linksys support T1, frame relay, and DS3? What about E1 and E3 support?
The point is that there are a few good IT Professionals and a bunch of students who think they know it all but don't understand that working in IT isn't all about just getting the computer to work
I worked at a higher ed institution and supported a network of about a dozen or so other higher ed institutions, and saw what was going on. This just wasn't the case at all. The problem all of them had was management buy-in for solutions. They all had IT professionals who in many cases out-classed their private sector counterparts, who had no problem running email servers which could both block spam and hold up to heavy usage. Their problem, really, was that management usually wouldn't support something they didn't understand, and believed anything printed on an 8x10 glossy.
So, email servers with nearly perfect track records were replaced with exchange servers and all the broken functionality/features therein. Upgrading network equipment, managing a network (WAN and LAN), inventorying a cable plant, securing web servers (MS salesbots also assured many of the PHBs IIS was already secure), and a host of other initiatives that IT staff tried to do at a number of institutions got little to no support/buyin from management. Which at least at those institutions the move to yahoo mail, gmail, and hotmail amongst staff and students became widespread.
From what I could tell, the real problem wasn't a lack of skill in the IT staff, but a lack of support starting at the top of most institutions I saw.
Slashdot Mirror
For the most part, yes, but the yahoo IM client differs significantly in capability and support from platform to platform.
If ms does get yahoo, they may find that their desktop monopoly won't help them leverage crap as it has for all the other products they've bought and downgraded. The Internet is turf foreign to their business model and corporate mindset, and buying yahoo won't change that. As if anything could. If this deal goes through, yahoo goes down.
If you want to call wireless technology a form of LAN technology, then the LAN doesn't really go away, does it? Designations like LAN, WAN, MAN are all kind of arbitrary. Where I work, we've got a 100Mb ethernet connection to TimeWarner's piece of the backbone. So, our web servers go from ethernet to ethernet to Internet. The only boundaries that seem to have substantive transitional meaning are the BGP ones from the point of view of the Internet. If you want to call what you have on your side of the boundary a LAN or a MAN or a non-LAN wireless LAN, go for it. If you have an ethernet connection to your ISP and think that means your wireless LAN isn't a LAN, fine.
As for wireless interference, the FCC will have to regulate any frequencies before they can be considered reliable enough for profit-motive servers to run on. The current 2.4Ghz is way too bespectacled with every fun gadget from phones to cameras to be considered on par with wires. And, no matter what you do, wireless will always be seen in the eyes of finance security types as less secure than wires.
The one scenario in which the LAN might be unrecognizable from its current form might be if the Internet ran on a global wireless mesh. A cool concept, but impractical in many ways - oceans aren't distance friendly and such a large scale mesh could be a routing behemoth dwarfing the measly 240,000 entry Internet routing table.
One wonders what Dave Cutler thinks of all the Vista bloat.
Will ASUS come out with an iEEE laptop?
That's not a hack likely to take the operator by surprise.
'True' Nerds do have friends - they just don't occur together in large numbers and share some focused intellectual and/or imaginative interest as opposed to a more generalized run-of-the-mill interest. Groups typically somewhere in the neighborhood of 3d4 or so.
They're only as safe as they're built. There's nothing 'intrinsically safe' about breeder reactors.
Umm... the bible is a collection of ancient literature, and the writings of hubbard are science fiction. The GPL is a legal license - it doesn't even have a plot line. How much more apples to oranges can you get?
Besides, search though I might, I could not find instructions for the holy hand grenade of antioch anywhere in the GPL. It clearly needs to be updated. And blessed some more by his holiness RMS.
Maybe the right question to ask is "How do I become a good IT manager?"
This idea of his doesn't make much more sense that his idea for how the IT dept will 'go away', seeing as how this idea is built on his earlier flawed idea.
This brings on a new meaning to the phrase "fired due to a computer glitch".
I hope they have adequate containment measures. We wouldn't want it to just keep growing and growing...
That's right - they need to figure out a friendly way to abuse customers.
Nobody will even try to hack in to put up pics of "W" or the dick...
Except on Halloween.
Technology like this will make it harder and harder to accurately diagnose paranoia.
There is more info at Ars, and they also mention Brett Swanson's name - he's from the 'discovery' institute.
I do find the tab completion handy. The shell in IOS tab completes/lists all the parameters for a given command as well. I haven't found a way to get bash and zsh to do that.
When two routers are set up in failover, by definition one of them is primary. If only default routes are used, all traffic goes through one ISP, not both. If you're paying for the extra bandwidth, why not use it?
that the shell in IOS has.
I don't know - I wish unix had the command parameter prompting system that the shell in IOS has. It's actually really useful. Not sure what the parameters are for any command? Press the question mark key.
Actually, the prompts change with context. Configuration mode has a different prompt, and within that mode the prompts change with context indicating what you're configuring
That said, I really wish IOS would positionally preserve all comments in the config file, not just in access lists. That would be really useful, as in being able to more fully document the configuration.
How would you do failover with a linksys or d-link router? After all if one ISP has a problem, you'll want to failover to the other, right? Does linksys and d-link support BGP? How would you do complete redundancy including switches in a two-ISP setting with either linksys or d-link? How many failover routers does linksys support? Does linksys or d-link support ssh? (I'd really like to know). Does linksys support T1, frame relay, and DS3? What about E1 and E3 support?
Just in time for upcoming elections.
I worked at a higher ed institution and supported a network of about a dozen or so other higher ed institutions, and saw what was going on. This just wasn't the case at all. The problem all of them had was management buy-in for solutions. They all had IT professionals who in many cases out-classed their private sector counterparts, who had no problem running email servers which could both block spam and hold up to heavy usage. Their problem, really, was that management usually wouldn't support something they didn't understand, and believed anything printed on an 8x10 glossy.
So, email servers with nearly perfect track records were replaced with exchange servers and all the broken functionality/features therein. Upgrading network equipment, managing a network (WAN and LAN), inventorying a cable plant, securing web servers (MS salesbots also assured many of the PHBs IIS was already secure), and a host of other initiatives that IT staff tried to do at a number of institutions got little to no support/buyin from management. Which at least at those institutions the move to yahoo mail, gmail, and hotmail amongst staff and students became widespread.
From what I could tell, the real problem wasn't a lack of skill in the IT staff, but a lack of support starting at the top of most institutions I saw.