No - it's called incompetence on the part of the people writing Windows where ANY programmer of ANY software can force a reboot any time - or at least demand the user reboot for no rational reason at all.
I'm not even sure about this "lazy programmer" stuff. Why would a programmer ASK for a reboot? He's putting his crap in the Registry, which supposedly he can do with no problem. His program isn't even running after install until I call it, so it's not like it's a service or a server he HAS to restart.
So why is he doing it?
BECAUSE HE'S BEEN TOLD TO, that's why! I'll bet if you hunt around the Windows programming books, you'll find there is some sort of "recommendation" that after updating the Registry or dropping DLLs in the system directories, that a program "should" reboot to "insure system stability" or whatever.
If this stuff was true back in Windows 98 and isn't true on Windows XP, somebody - like Microsoft - should start telling the developers regularly.
This is the number one thing I absolutely CANNOT STAND on Windows! If they're doing it because they think end users will "accidentally" bring up the Task Manager and "accidentally" kill the kernel, they could at least put the warning BEFORE you try to actually kill a process - not twenty minutes after. They could change the freakin' interface to something more rational.
Yes, there is a command line tool that will supposedly kill processes quickly.
Is this why people buy Windows - to run a command line tool? Gee, how is this better than Linux?
Well, according to the article, Visa will be the same thing - a "new" OS with a new theme - which is the point of the discussion.
The problem for the masses is: are they going to care about ANY new features for Windows when they haven't figured out how to use XP yet? Based on the 60% or so market penetration of XP, that leaves a lot of people who didn't care about XP and aren't likely to care about Visa.
Certainly the new features are not going to be terribly exciting for corporate management.
I predict Visa will only achieve 60% market penetration in FIVE YEARS vrs three or so for XP.
Meanwhile Linux will achieve 10% - possibly even 20% - market penetration in those same five years.
Actually, yes, I can - depending on how stupid that administrator ACTUALLY IS.
The way I see it, if City College has hundreds of machines running on the domain, including a couple dozen in my own office area, it should be trivial to insure that ONE NEW ONE runs as well immediately.
The fact that a very sharp tech who does this stuff daily could not do this tells me either that his boss is an idiot (very likely given the management around here) OR that no matter HOW smart his boss is, Windows has found a way to screw him - MUCH more likely.
The bottom line: he should have been able to plug in the box, do a mouse click, and put the system on the network. As long as neither Windows nor Linux can do this, they're crap - as I've said repeatedly.
You are required by/. policy to identify yourself as a Windows Shill by reporting the above number next to your/. ID.
Violators will be forced to watch reruns of Bill Gates interviews. (I know, it's not much of a punishment for guys like you, but it's the worst the/. administrators could come up with.)
Yeah, right - there are plenty of people who will tell you that Windows servers hose themselves on at least a weekly basis and have to be rebooted to unhose themselves.
If this is a "non-issue", THEN WHY IS MICROSOFT MENTIONING IT?/. Windows Shill Serial Number 127588...
That is undoubtedly true - but it's also a problem with Windows because half the Windows sys admins in the industry apparently can't figure how to configure AD or anything else on a Windows server so it works reliably.
I took the Windows 2003 Server course last semester at City College, and after that experience I'm not surprised. Besides having a mountain of Management Consoles, menus and dialogs to wade through to do practically ANYTHING, the computer LAB system - with students running canned exercises out of a textbook - managed to fail enough times to make me extremely wary of using this crap in a production environment. The teacher - who is an outside contractor who does Windows consulting including servers, etc. and knows Windows servers well - had plenty of trouble keeping the DHCP server running - freakin' DHCP!
Even the lab exercises wouldn't necessarily work the same way for every student and the teacher couldn't figure out why - just too many possibilities between server setups, permissions, domains, and the various components we were exercising.
The tech who set me up today is very sharp and hooks people up all the time here at City College. He's baffled and had to call the main IT office who had nothing brilliant to suggest but try joining the domain tomorrow. Try suggesting that in a real corporate production environment.
They're going to take the "t" out like I do and call it "Visa" - because you're going to max yours out buying the hardware to run this thing, AND pay the license fees.
"will also save costs by reducing the number of times computers will have to be rebooted."
I'm so excited! All these wonderful enhancement for Visa (once again, folks, the "t" is missing for a reason!) have got me drooling.
I just had a new machine installed at work. The tech let me copy my old machine stuff up to a network server, and back down on the new machine. Then he set me up for the Windows domain.
Can't log on - "Cannot connect to the domain. The domain may be down or unavailable, or the account might be wrong. Try again later." After several tries including Sysprep'ing the machine again, etc.
So we're trying tomorrow morning, because apparently the freakin' AD servers don't replicate often enough, nor do they replicate from the closest server to my subnet, but from the main one located thirty blocks away. So it will be, oh, two or three months probably before the freakin' AD server my machine logs onto is notified that I exist.
Brilliant.
Rest of the day I spent installing my stuff that had to be uninstalled because it was on the other drive I no longer have. So my Winamp, Firefox, Thunderbird, jEdit, SQLTools all work.
It's just Windows networking that doesn't work.
I JUST CAN'T WAIT for a Windows which won't have to be rebooted as often.
This will really justify buying that new 3GHz CPU with 1GB RAM and 100GB of hard disk necessary to run the OS ALONE.
Problem is, their hardware (combined with their support fees, etc.) is more expensive than commodity hardware and thus offers less performance for the same money.
As long as they aren't selling commodity hardware, running Linux on proprietary hardware merely staves off their demise by a few extra years. As does pushing the enterprise class capabilities of Solaris, which Linux will have one of these days anyway.
There's no possible way they can ever compete with Intel and the Far East at producing commodity hardware - unless they were to do what IBM did with Lenovo and basically sell out to a Far East company and get a piece of a larger pie.
They might survive strictly as a high-end hardware company using Linux for the niche markets that need extra-high performance for a premium price. There are companies that do that. IBM's mainframes are in that position. But they won't be a market leader or even a market significant factor in that position. They certainly won't be a multi-billion dollar company.
Ah, I see you've been to a number of San Francisco sex clubs.
(I personally have not except one evening at the PowerExchange where I got no benefit at all from anyone. Note that the PowerExchange has three floors and a dungeon - the bottom two are hetero, the middle couples only, the top for gay men. Check it out next time you're in town. Pick your floor.)
Uhm, well, actually, if you're black and you get caught walking around a white neighborhood with a (big) screwdriver in your back pocket, yes, you will be arrested for possession of "burglars tools."
That's quite common in a lot of places, I believe.
In other words, as soon as you finish eating Pringles, you've committed a crime.
Next I expect the cops will label shitting the result as another criminal act.
You gotta wonder where they find the morons who become cops. I used to wonder that in the Federal joint, where correctional officers are even DUMBER than either military types OR cops. Most of them are wannabe cops who couldn't pass the tests, or military drop-outs.
We had one idiot at Florence FCI who was well-known as a wannabe cop who had apparently ratted out some of his fellow officers in one of the local forces, and as a result had been kicked off the force. Every time he went into a cop bar, he got his ass kicked.
I also used to wonder where they found the sort of goons the New York Police Department hired when I saw the clowns charged with that incident of sodomizing the guy with a broom handle. I mean, knuckle-draggin' orangutans would be insulted to be compared to those guys. You want to see what a Nazi concentration camp guard looks like, check those guys out.
The interesting thing about my 2000-XP problem was that both systems continued to boot fine and work fine in every respect except what follows.
What would happen - and this made me pull my hair out for a couple days - was that you could create directories on the partitions across the 137GB boundary and create files in them - but neither OS could SEE directories or files created by the other OS. I could even clear a partition off in one OS and the other OS would say it was still there! This eventually (I'm slow sometimes) made it obvious to me that they were reading the partition table as referring to two separate places on the hard drive.
It wasn't until I found an obscure Microsoft Knowledgebase article that said Windows 2000 with SP3 would incorrectly read partition tables on "some hard disks" that I realized what was happening. Notice the inutterable ambiguity of that article - "some hard disks". Which ones? Why? Obviously Microsoft didn't know either or wasn't inclined to say. Obviously they didn't want to admit that their LBA48 support in SP3 was bad.
So keep in mind if you ever install Windows 2000 on a hard drive over 137GB - install it with Service Pack FOUR already applied. Better yet, just install XP.
I agree that the prevalence of broadband makes worms more interesting to write and has undoubtedly caused more virus writers to write them, but you still have to have the actual vulnerabilities to make them practical. Actually, a lot of the worms target systems like SQL Server which presumably are on corporate networks with a minimum of T-1 access anyway. DSL is just icing on the cake to reach some home users or small businesses.
Nowadays, apparently, phishing scams and the like are more interesting, so there seem to be fewer worms. Or perhaps Microsoft has finally patched most of those vulnerabilities, at least as far as corporate systems are concerned.
I'd say the prevalence of spammer zombie networks indicates more end-user ignorance than Windows vulnerabilities at this point - Microsoft has probably patched most of the vulnerabilities, but hundreds of thousands of users haven't patched their systems. So it's still easy to create zombie networks.
She loses everything - cell phone, tin whistles, sisters...even herself.
Caroline Corr: "She's dizzy. She gets lost and stuff...You know, in airports, you're looking for Andrea. And she's lost her passport...she's lost her boarding pass."
Slashdot Mirror
No - it's called incompetence on the part of the people writing Windows where ANY programmer of ANY software can force a reboot any time - or at least demand the user reboot for no rational reason at all.
I'm not even sure about this "lazy programmer" stuff. Why would a programmer ASK for a reboot? He's putting his crap in the Registry, which supposedly he can do with no problem. His program isn't even running after install until I call it, so it's not like it's a service or a server he HAS to restart.
So why is he doing it?
BECAUSE HE'S BEEN TOLD TO, that's why! I'll bet if you hunt around the Windows programming books, you'll find there is some sort of "recommendation" that after updating the Registry or dropping DLLs in the system directories, that a program "should" reboot to "insure system stability" or whatever.
If this stuff was true back in Windows 98 and isn't true on Windows XP, somebody - like Microsoft - should start telling the developers regularly.
Amen, brother! I wish I had mod points!
This is the number one thing I absolutely CANNOT STAND on Windows! If they're doing it because they think end users will "accidentally" bring up the Task Manager and "accidentally" kill the kernel, they could at least put the warning BEFORE you try to actually kill a process - not twenty minutes after. They could change the freakin' interface to something more rational.
Yes, there is a command line tool that will supposedly kill processes quickly.
Is this why people buy Windows - to run a command line tool? Gee, how is this better than Linux?
"If you could care less, that means that you do care somewhat. Otherwise, you couldn't care less."
How many times do I have to explain to you pedants that using the phrase "could care less" is a second-order dismissal?
It means, "I could care less - NOT!" It's dismissing the notion that one COULD care less because one already doesn't care at all.
It may have started as bad grammar, like a lot of slang does, but it has meaning now.
If that doesn't work for you, does "Fuck off, pedant!" help?
And sometimes shutting down requires a reboot...:-)
"windows XP with a new theme"
Well, according to the article, Visa will be the same thing - a "new" OS with a new theme - which is the point of the discussion.
The problem for the masses is: are they going to care about ANY new features for Windows when they haven't figured out how to use XP yet? Based on the 60% or so market penetration of XP, that leaves a lot of people who didn't care about XP and aren't likely to care about Visa.
Certainly the new features are not going to be terribly exciting for corporate management.
I predict Visa will only achieve 60% market penetration in FIVE YEARS vrs three or so for XP.
Meanwhile Linux will achieve 10% - possibly even 20% - market penetration in those same five years.
Actually, yes, I can - depending on how stupid that administrator ACTUALLY IS.
The way I see it, if City College has hundreds of machines running on the domain, including a couple dozen in my own office area, it should be trivial to insure that ONE NEW ONE runs as well immediately.
The fact that a very sharp tech who does this stuff daily could not do this tells me either that his boss is an idiot (very likely given the management around here) OR that no matter HOW smart his boss is, Windows has found a way to screw him - MUCH more likely.
The bottom line: he should have been able to plug in the box, do a mouse click, and put the system on the network. As long as neither Windows nor Linux can do this, they're crap - as I've said repeatedly.
The difference is: Linux is FREE crap.
"Single point of failure"
And I MEAN it!
You're really pushing it, dude.
Start using that
You are required by
Violators will be forced to watch reruns of Bill Gates interviews. (I know, it's not much of a punishment for guys like you, but it's the worst the
Yeah, right - there are plenty of people who will tell you that Windows servers hose themselves on at least a weekly basis and have to be rebooted to unhose themselves.
/. Windows Shill Serial Number 127588...
If this is a "non-issue", THEN WHY IS MICROSOFT MENTIONING IT?
Really - is that why I had to reboot XP today to install ZipGenius - a fuckin' archive program?
XP cannot BE well-configured as long as it has a Registry and Microsoft has never heard of rereading a configuration file.
And symlinks everywhere else.
That is undoubtedly true - but it's also a problem with Windows because half the Windows sys admins in the industry apparently can't figure how to configure AD or anything else on a Windows server so it works reliably.
I took the Windows 2003 Server course last semester at City College, and after that experience I'm not surprised. Besides having a mountain of Management Consoles, menus and dialogs to wade through to do practically ANYTHING, the computer LAB system - with students running canned exercises out of a textbook - managed to fail enough times to make me extremely wary of using this crap in a production environment. The teacher - who is an outside contractor who does Windows consulting including servers, etc. and knows Windows servers well - had plenty of trouble keeping the DHCP server running - freakin' DHCP!
Even the lab exercises wouldn't necessarily work the same way for every student and the teacher couldn't figure out why - just too many possibilities between server setups, permissions, domains, and the various components we were exercising.
The tech who set me up today is very sharp and hooks people up all the time here at City College. He's baffled and had to call the main IT office who had nothing brilliant to suggest but try joining the domain tomorrow. Try suggesting that in a real corporate production environment.
They're going to take the "t" out like I do and call it "Visa" - because you're going to max yours out buying the hardware to run this thing, AND pay the license fees.
I think they are referring to the fact that I had to reboot Windows today to install freakin' ZipGenius...a fucking archive program.
Okay, that's probably the programmer's fault, but still, why is it so easy and necessary for programmers to do this crap?
Because there's a Registry, that's why.
And Microsoft has never heard of rereading a config file.
"will also save costs by reducing the number of times computers will have to be rebooted."
I'm so excited! All these wonderful enhancement for Visa (once again, folks, the "t" is missing for a reason!) have got me drooling.
I just had a new machine installed at work. The tech let me copy my old machine stuff up to a network server, and back down on the new machine. Then he set me up for the Windows domain.
Can't log on - "Cannot connect to the domain. The domain may be down or unavailable, or the account might be wrong. Try again later." After several tries including Sysprep'ing the machine again, etc.
So we're trying tomorrow morning, because apparently the freakin' AD servers don't replicate often enough, nor do they replicate from the closest server to my subnet, but from the main one located thirty blocks away. So it will be, oh, two or three months probably before the freakin' AD server my machine logs onto is notified that I exist.
Brilliant.
Rest of the day I spent installing my stuff that had to be uninstalled because it was on the other drive I no longer have. So my Winamp, Firefox, Thunderbird, jEdit, SQLTools all work.
It's just Windows networking that doesn't work.
I JUST CAN'T WAIT for a Windows which won't have to be rebooted as often.
This will really justify buying that new 3GHz CPU with 1GB RAM and 100GB of hard disk necessary to run the OS ALONE.
I'm SO stoked.
Because if you rat on your fellow cops, you're history in that force.
True for virtually every police force. Remember "Serpico"?
Problem is, their hardware (combined with their support fees, etc.) is more expensive than commodity hardware and thus offers less performance for the same money.
As long as they aren't selling commodity hardware, running Linux on proprietary hardware merely staves off their demise by a few extra years. As does pushing the enterprise class capabilities of Solaris, which Linux will have one of these days anyway.
There's no possible way they can ever compete with Intel and the Far East at producing commodity hardware - unless they were to do what IBM did with Lenovo and basically sell out to a Far East company and get a piece of a larger pie.
They might survive strictly as a high-end hardware company using Linux for the niche markets that need extra-high performance for a premium price. There are companies that do that. IBM's mainframes are in that position. But they won't be a market leader or even a market significant factor in that position. They certainly won't be a multi-billion dollar company.
They're simply doomed and they know it.
Ah, I see you've been to a number of San Francisco sex clubs.
(I personally have not except one evening at the PowerExchange where I got no benefit at all from anyone. Note that the PowerExchange has three floors and a dungeon - the bottom two are hetero, the middle couples only, the top for gay men. Check it out next time you're in town. Pick your floor.)
Yup - and do I like Kim Polese - member of the team that created and namer of Java, founder of Marimba, and presently CEO of SpikeSource.
And have you ever seen Dr. Fiorella Terenzi, the astrophysicist? Makes music from radio telescope data.
Or Dr. Clio Cresswell, the Australian mathematician who wrote a book on "Mathematics and Sex"?
Editors: Wan Hung Low, and Sum Yung Boy.
Publisher: Man Hang Low
Uhm, well, actually, if you're black and you get caught walking around a white neighborhood with a (big) screwdriver in your back pocket, yes, you will be arrested for possession of "burglars tools."
That's quite common in a lot of places, I believe.
In other words, as soon as you finish eating Pringles, you've committed a crime.
Next I expect the cops will label shitting the result as another criminal act.
You gotta wonder where they find the morons who become cops. I used to wonder that in the Federal joint, where correctional officers are even DUMBER than either military types OR cops. Most of them are wannabe cops who couldn't pass the tests, or military drop-outs.
We had one idiot at Florence FCI who was well-known as a wannabe cop who had apparently ratted out some of his fellow officers in one of the local forces, and as a result had been kicked off the force. Every time he went into a cop bar, he got his ass kicked.
I also used to wonder where they found the sort of goons the New York Police Department hired when I saw the clowns charged with that incident of sodomizing the guy with a broom handle. I mean, knuckle-draggin' orangutans would be insulted to be compared to those guys. You want to see what a Nazi concentration camp guard looks like, check those guys out.
The interesting thing about my 2000-XP problem was that both systems continued to boot fine and work fine in every respect except what follows.
What would happen - and this made me pull my hair out for a couple days - was that you could create directories on the partitions across the 137GB boundary and create files in them - but neither OS could SEE directories or files created by the other OS. I could even clear a partition off in one OS and the other OS would say it was still there! This eventually (I'm slow sometimes) made it obvious to me that they were reading the partition table as referring to two separate places on the hard drive.
It wasn't until I found an obscure Microsoft Knowledgebase article that said Windows 2000 with SP3 would incorrectly read partition tables on "some hard disks" that I realized what was happening. Notice the inutterable ambiguity of that article - "some hard disks". Which ones? Why? Obviously Microsoft didn't know either or wasn't inclined to say. Obviously they didn't want to admit that their LBA48 support in SP3 was bad.
So keep in mind if you ever install Windows 2000 on a hard drive over 137GB - install it with Service Pack FOUR already applied. Better yet, just install XP.
I agree that the prevalence of broadband makes worms more interesting to write and has undoubtedly caused more virus writers to write them, but you still have to have the actual vulnerabilities to make them practical. Actually, a lot of the worms target systems like SQL Server which presumably are on corporate networks with a minimum of T-1 access anyway. DSL is just icing on the cake to reach some home users or small businesses.
Nowadays, apparently, phishing scams and the like are more interesting, so there seem to be fewer worms. Or perhaps Microsoft has finally patched most of those vulnerabilities, at least as far as corporate systems are concerned.
I'd say the prevalence of spammer zombie networks indicates more end-user ignorance than Windows vulnerabilities at this point - Microsoft has probably patched most of the vulnerabilities, but hundreds of thousands of users haven't patched their systems. So it's still easy to create zombie networks.
She loses everything - cell phone, tin whistles, sisters...even herself.
Caroline Corr: "She's dizzy. She gets lost and stuff...You know, in airports, you're looking for Andrea. And she's lost her passport...she's lost her boarding pass."