Color accomplished little as I see it. Sure, it looks pretty, but I don't NEED my appointments and phone numbers to look pretty. I want something that won't eat battery life-- which brings up another point. The older Palms used standard alkaline batteries, lasted months on them. The newer ones need special power packs and chargers-- makes taking one on a week long hike a bit of an exercise.
Now we have an entirely new OS that requires still more beefed up battery packs and fancy electronics-- and I STILL just use it for appointments and phone numbers.
...that this is done by the New York Times, who requires you to register so they can sell your personal info (or at least demographic information) for more "almighty bucks."
Certainly learning one unix will prepare you for the others - much easier than going, eg, between unix and windows. But if you think these hassles are cost free, I don't want you making decisions in my company.
Of course it's not "cost free," but at the same time, it's hardly worth hiring a different admin for every different OS you run. Sure, it's challenging, but it's not something a good tech will shrink from.
That's what I thought, until I ran into some Mac user who categorically refused to do anything sensibly. He had a bunch of files he wanted to share across his network, and rather than setting up an FTP server like anyone else would have done, he chose to do it all over Appletalk. That would have been fine if PCs didn't need to access it, and the archaic mess would up on our helpdesk.
We didn't have any advice for him past "use TCP/IP like a sensible man, you fscking idiot."
Right-- but that's a local issue. Odds are when it comes to networking, it's either going to work or it's not. The point is, you can trace it to see WHY it's not working a hell of a lot more easily than you can with an OS that no one here's ever seen beneath the hood of.
The details are different, and the syntax changes, but by and large things tend to work the same way in the holistic sense.
But odds are that whatever your Unix vendor is, he's going to have more worthwhile advice than "format and reinstall." Even open source OSen made by teams of developers are likely to have extensive support forums. But let's not turn this into a religious war...
Right-- all you'd have to worry about in this case would be updates. You're not likely to have the problems you would with an Apple or MS network, in that machines won't be able to talk to one another.
There's something to be said for Unix's adherence to standards, unlike a certain closed source vendor...
Provided you go with all Open Source systems, I don't imagine you'd be too stretched to maintain it. They'll all talk to one another just fine across a network-- all you'd probably have to worry about would be patching different packages in different ways.
It's when you get into closed source proprietary crap that speaks some protocol no one else has ever heard of that you run into trouble.
As you and others have said, if nothing goes bad, it doesn't take much maintenance to keep running, though it's adding new service that needs resources and causes mistakes that break things.
Yeah, but you should SEE how many people it takes to fix things when it goes wrong. We had a guy in a pickup truck driving a new mainframe processor assembly from Boston to northern Maine one day just to get things up again...
Here's to network stability in Europe for the next week.
It does, but right now they're focused solely on "keeping it up" until the trustees come to a conclusion. The only "project" is to keep the network up so half of Europe doesn't drop offline. I'd imagine all expansions are on hold until they figure out whether they're selling the old equipment on Ebay once the switch gets flipped...
It's great that they're doing this, but how long can they keep it up? I mean, it's great that they're volunteering like this, but you can only go so long without a source of income. After a few weeks, bills start to pile up, or a major router breaks and needs replacing. Running a network's not ridiculously hard, but it does take money...
For a day or so, you can keep most large networks running with only one person or so. I work in a NOC that handles access for over 2000 sites, and for nights and holidays (weekends too), we have exactly one person here.
Though when things go bad, we have other people on call-- it can get hectic.
So if all goes well, they could hold out for quite some time (until something important breaks).
Well, look at the massive companies we have now *coughVerizoncough*. Doesn't it seem that they're slowly getting back to the point that AT&T was at? Doesn't seem to be much point in breaking up a company if they're going to rejoin down the road...
When will device manufacturers make a decent product and leave me the fuck alone after the sale?
Unfortunately, according to trade publications it's 4 times easier to sell to an existing customer than to get a new one. That's a huge market, and people view it as "leaving money on the table" if you don't try to sell more stuff to existing customers.
Slashdot Mirror
No, they're playing the market. I have friends who are considering getting a Mac solely due to the iPod.
Yes, due to the many wi-fi access points one could find in the middle of the Atlantic in 1943...
Companies can't get away with imprisoning/killing you. The government can have you locked up with all of ten minutes notice-- Intel can't.
Part three The Matrix Revolutions is also in production and will be released in December 2000
Damn, what cave have I been living in?
I use mine as an ebook reader, too-- there's something nice about having a few good books (such as field guides) with you on an excursion...
Color accomplished little as I see it. Sure, it looks pretty, but I don't NEED my appointments and phone numbers to look pretty. I want something that won't eat battery life-- which brings up another point.
The older Palms used standard alkaline batteries, lasted months on them. The newer ones need special power packs and chargers-- makes taking one on a week long hike a bit of an exercise.
Now we have an entirely new OS that requires still more beefed up battery packs and fancy electronics-- and I STILL just use it for appointments and phone numbers.
Unfortunately, those of us with Handsprings can't upgrade OSes-- every time Palm comes out with a new OS, we have to buy a new PDA to go with it...
...that this is done by the New York Times, who requires you to register so they can sell your personal info (or at least demographic information) for more "almighty bucks."
Hmm, last I heard NASA was still focusing on ion emissions as the "future of propulsion."
If that hasn't been dismissed yet, I might suspect that they're spreading themselves a mite thin...
Certainly learning one unix will prepare you for the others - much easier than going, eg, between unix and windows. But if you think these hassles are cost free, I don't want you making decisions in my company.
Of course it's not "cost free," but at the same time, it's hardly worth hiring a different admin for every different OS you run. Sure, it's challenging, but it's not something a good tech will shrink from.
That's what I thought, until I ran into some Mac user who categorically refused to do anything sensibly. He had a bunch of files he wanted to share across his network, and rather than setting up an FTP server like anyone else would have done, he chose to do it all over Appletalk. That would have been fine if PCs didn't need to access it, and the archaic mess would up on our helpdesk.
We didn't have any advice for him past "use TCP/IP like a sensible man, you fscking idiot."
Right-- but that's a local issue. Odds are when it comes to networking, it's either going to work or it's not. The point is, you can trace it to see WHY it's not working a hell of a lot more easily than you can with an OS that no one here's ever seen beneath the hood of.
The details are different, and the syntax changes, but by and large things tend to work the same way in the holistic sense.
But odds are that whatever your Unix vendor is, he's going to have more worthwhile advice than "format and reinstall." Even open source OSen made by teams of developers are likely to have extensive support forums. But let's not turn this into a religious war...
Right-- all you'd have to worry about in this case would be updates. You're not likely to have the problems you would with an Apple or MS network, in that machines won't be able to talk to one another.
There's something to be said for Unix's adherence to standards, unlike a certain closed source vendor...
Provided you go with all Open Source systems, I don't imagine you'd be too stretched to maintain it. They'll all talk to one another just fine across a network-- all you'd probably have to worry about would be patching different packages in different ways.
It's when you get into closed source proprietary crap that speaks some protocol no one else has ever heard of that you run into trouble.
Heh, it sounds like you work at my school. I can't stand how many faculty members seem to think they're "above the law..."
Don't 'spose you work in Maine, do you?
As you and others have said, if nothing goes bad, it doesn't take much maintenance to keep running, though it's adding new service that needs resources and causes mistakes that break things.
Yeah, but you should SEE how many people it takes to fix things when it goes wrong. We had a guy in a pickup truck driving a new mainframe processor assembly from Boston to northern Maine one day just to get things up again...
Here's to network stability in Europe for the next week.
Assuming that they go down, how much of an impact will it have?
No kidding. The NOC I work at has dual monitors on most machines here, the way it's been working is one is a flat panel, one's a CRT.
But we're state sponsored, so it's the taxpayers' money. Not sure how economical it would be if we were a corporate entity.
It does, but right now they're focused solely on "keeping it up" until the trustees come to a conclusion. The only "project" is to keep the network up so half of Europe doesn't drop offline. I'd imagine all expansions are on hold until they figure out whether they're selling the old equipment on Ebay once the switch gets flipped...
It's great that they're doing this, but how long can they keep it up? I mean, it's great that they're volunteering like this, but you can only go so long without a source of income. After a few weeks, bills start to pile up, or a major router breaks and needs replacing. Running a network's not ridiculously hard, but it does take money...
For a day or so, you can keep most large networks running with only one person or so. I work in a NOC that handles access for over 2000 sites, and for nights and holidays (weekends too), we have exactly one person here.
Though when things go bad, we have other people on call-- it can get hectic.
So if all goes well, they could hold out for quite some time (until something important breaks).
I disagree. That's like saying I shouldn't take a shower only because I'm going to get dirty again tomorrow.
Hmm... weren't there provisions stating they couldn't rejoin for X number of years? Otherwise they could just become AT&T the next day...
Well, look at the massive companies we have now *coughVerizoncough*. Doesn't it seem that they're slowly getting back to the point that AT&T was at? Doesn't seem to be much point in breaking up a company if they're going to rejoin down the road...
When will device manufacturers make a decent product and leave me the fuck alone after the sale?
Unfortunately, according to trade publications it's 4 times easier to sell to an existing customer than to get a new one. That's a huge market, and people view it as "leaving money on the table" if you don't try to sell more stuff to existing customers.