Yeah, but the chances of Microsoft releasing a security patch are pretty low, and the chances of them telling you what was patched is even lower, so it's probably a non-issue.
Not only that, but the majority of the messages talking about Linux vulnerabilities deal with small things, like ways to figure out if a user exists on a system, or ways to DOS a service, or exloits that only work if you already have an account on the Linux box. The Windows bugs, however, are more often remotely exploitable arbitrary code execution, major freakin' flaws.
I've seen so many people driving around with those little do-nut spares on their cars, I'd pretty much bet that if cars were designed to be able to continue driving with the loss of a wheel, we'd be seeing lots of cars driving a few wheels short.
Heh, I used to do something similar with Commodor Vic-20's on display at the local K-Mart. Put up a nice "Press any key to begin demo" screen, then when a key is hit, send a shrill tone to the speaker, and poke into a memory location that'd crash the computer. Walk across the store, and wait for the alarm.
That's one less person who's going to take my future computer job!
Yes, and he totally blew away the line. She couldn't weigh less than a duck, she had to weigh the same as a duck, becuase if she weighs the same as a duck, then she's made of wood, and therefore, she's a witch.
I mean, if I come to work, as a network administrator, and I see a warchalking symbol outside my office, that's a HUGE red flag for me to go fix my network.
Our company recently switched from Netscape Mail Server to Exchange 5.5. They then turned off all non-Microsoft protocols, like IMAP and POP, so suddenly, my beutiful Linux machine couldn't get mail, and they were making me switch to Outlook on Windows (ick) However, they did leave webmail as an option for me, woohoo. So, I just broke out my Perl and LWP and now I have a script that quite handily grabs all my mail from the webmail interface and populates it into my standard Unix mail spool. Problem solved.
Here, I'd be willing to do the work that night, given that I, too, had no pressing engagements keeping me from it. However, if this employee shows this to be a pattern, they are *never* available during off hours, then yeah, you have to tell them they aren't cut out for this line of work. I had to do that not too long ago. We moved a guy out of my department and made him a computer operator (instead of an administrator) We got someone to replace him who was willing to put in the hours, he got a job where he could come in at 8:30 and leave at 5:30 and never had to carry a pager. Everyone won.
>- Integrated support for Windows NT®, FTP, HTTP, >Appletalk, and Novell environments, which enables >consolidated administration in heterogeneous >networks. Wow! They have "integrated support" for >FTP and HTTP!!! OMG! >And you only need to patch it every 5min!
not to menion, integrated support for Appletalk? Has anyone here ever used Microsoft's implementation of Appletalk? It's probably the worst written piece of code I've ever seen. NetAtalk on linux outperforms it on half the hardware. The only reason Appletalk support is in Windows at all is an attempt to get NT/2000 servers into Macintosh environments. Then they can say "See how crappy Appletalk runs? See how much you've paid for this Microsoft box? Well, if you really want to get this thing working right, you need to get rid of your macs and put in Windows PCs."
When did it jump? When Futurama started. It seems like as soon as they started making Futurama, Matt put all his time into that show (which admitedly is great) and turned away from The Simpsons. The writing seems much more like the writing of The Family Guy than Simpsons. I wouldn't be suprised to hear that they hired some of The Family Guy's writers.
Heh, Lego for adults. I like that. I guess I'm just more into toys. Plus, HP has bitten me more than once when it's come time to upgrade. Can't just plop another CPU or another mobo in the case, you need to get pretty much a totally new computer. Different preference.
I have never bought an OEM box for myself. I like picking out the right mix of hardware for my needs. But, I am very hessitant to do the same thing for a production server. If my home machine goes down, no one calls me at 3am telling me to fix it right now. (heh) So, if for no other reason than it gives me someone to blame, I'll buy OEM boxen for the office.
I'm not sure I understand your problem with putting together your own machine. Why is the hassle of inserting some components and screwing in a few screws not worth the cost savings to you? Not to mention the fact that if you build it yourself, you know what is in it. You put in the sound card you like, the CPU you like, the ethernet card you like, etc etc etc.
I've both built my own, and bought from manufacturers. What I'm paying for when I buy a Dell computer, be it a laptop or a server, isn't so much the name as the support. Buying a box from one vendor instead of buying all the parts from different vendors gets you out of the "It's not our fault, blame the mobo manufacturer" "It's not our fault, blaime the CPU manufacturer" crap.
Actually, you don't need to install a VNC client on the remote machines. You can access an use a machine running VNC server straight from any java capable web browser.
I would still have to say that the software itself shouldn't be illegal. It's sort of like owning a tiger. I should be allowed to own a tiger, but if I let it get out, and it kills someone, I should be held responsible. Same with virus software. If I write it, and run it on my LAN to prove a security hole, that should be fine. If I allow it out of my posession, and someone turns it loose on the internet, I should be held responsible. That includes if someone hacks into my network, steals the virus and then turns it loose. I'm still responsible. Same as if someone sneaked into my back yard and set my tiger free.
Slashdot Mirror
In that order, eh? So, they get Outhouses, then get TiVos. I wonder what the correlation there is...
Ok, now imagine a beowulf cluster of timeshared supercomputers.....
Aww, man, I was gonna guess!
Yeah, but the chances of Microsoft releasing a security patch are pretty low, and the chances of them telling you what was patched is even lower, so it's probably a non-issue.
Not only that, but the majority of the messages talking about Linux vulnerabilities deal with small things, like ways to figure out if a user exists on a system, or ways to DOS a service, or exloits that only work if you already have an account on the Linux box. The Windows bugs, however, are more often remotely exploitable arbitrary code execution, major freakin' flaws.
Well, I hate to tell you this way, but your mother just died.
I've seen so many people driving around with those little do-nut spares on their cars, I'd pretty much bet that if cars were designed to be able to continue driving with the loss of a wheel, we'd be seeing lots of cars driving a few wheels short.
Heh, I used to do something similar with Commodor Vic-20's on display at the local K-Mart. Put up a nice "Press any key to begin demo" screen, then when a key is hit, send a shrill tone to the speaker, and poke into a memory location that'd crash the computer. Walk across the store, and wait for the alarm.
That's one less person who's going to take my future computer job!
Yes, and he totally blew away the line. She couldn't weigh less than a duck, she had to weigh the same as a duck, becuase if she weighs the same as a duck, then she's made of wood, and therefore, she's a witch.
I mean, if I come to work, as a network administrator, and I see a warchalking symbol outside my office, that's a HUGE red flag for me to go fix my network.
But, since they are not disseminating music on devices designed to prevent authorized output, the original post was correct, no?
Because /. doesn't have a back page?
I doubt it. Big company. Mandates come from on high, we just have to live with them the best we can.
Actually, Evolution doesn't support Exchange 5.5. And, my company appreciates all the work I do. Doesn't yours?
Our company recently switched from Netscape Mail Server to Exchange 5.5. They then turned off all non-Microsoft protocols, like IMAP and POP, so suddenly, my beutiful Linux machine couldn't get mail, and they were making me switch to Outlook on Windows (ick) However, they did leave webmail as an option for me, woohoo. So, I just broke out my Perl and LWP and now I have a script that quite handily grabs all my mail from the webmail interface and populates it into my standard Unix mail spool. Problem solved.
Here, I'd be willing to do the work that night, given that I, too, had no pressing engagements keeping me from it. However, if this employee shows this to be a pattern, they are *never* available during off hours, then yeah, you have to tell them they aren't cut out for this line of work. I had to do that not too long ago. We moved a guy out of my department and made him a computer operator (instead of an administrator) We got someone to replace him who was willing to put in the hours, he got a job where he could come in at 8:30 and leave at 5:30 and never had to carry a pager. Everyone won.
>- Integrated support for Windows NT®, FTP, HTTP, >Appletalk, and Novell environments, which enables >consolidated administration in heterogeneous >networks. Wow! They have "integrated support" for >FTP and HTTP!!! OMG!
>And you only need to patch it every 5min!
not to menion, integrated support for Appletalk? Has anyone here ever used Microsoft's implementation of Appletalk? It's probably the worst written piece of code I've ever seen. NetAtalk on linux outperforms it on half the hardware. The only reason Appletalk support is in Windows at all is an attempt to get NT/2000 servers into Macintosh environments. Then they can say "See how crappy Appletalk runs? See how much you've paid for this Microsoft box? Well, if you really want to get this thing working right, you need to get rid of your macs and put in Windows PCs."
When did it jump? When Futurama started. It seems like as soon as they started making Futurama, Matt put all his time into that show (which admitedly is great) and turned away from The Simpsons. The writing seems much more like the writing of The Family Guy than Simpsons. I wouldn't be suprised to hear that they hired some of The Family Guy's writers.
Heh, Lego for adults. I like that. I guess I'm just more into toys. Plus, HP has bitten me more than once when it's come time to upgrade. Can't just plop another CPU or another mobo in the case, you need to get pretty much a totally new computer. Different preference.
I have never bought an OEM box for myself. I like picking out the right mix of hardware for my needs. But, I am very hessitant to do the same thing for a production server. If my home machine goes down, no one calls me at 3am telling me to fix it right now. (heh) So, if for no other reason than it gives me someone to blame, I'll buy OEM boxen for the office.
It's not my fault! I'll call Dell!
I'm not sure I understand your problem with putting together your own machine. Why is the hassle of inserting some components and screwing in a few screws not worth the cost savings to you? Not to mention the fact that if you build it yourself, you know what is in it. You put in the sound card you like, the CPU you like, the ethernet card you like, etc etc etc.
I've both built my own, and bought from manufacturers. What I'm paying for when I buy a Dell computer, be it a laptop or a server, isn't so much the name as the support. Buying a box from one vendor instead of buying all the parts from different vendors gets you out of the "It's not our fault, blame the mobo manufacturer" "It's not our fault, blaime the CPU manufacturer" crap.
Plus, the Dell 1U servers look way cool....
Actually, you don't need to install a VNC client on the remote machines. You can access an use a machine running VNC server straight from any java capable web browser.
There's a great way to make Ximian run much faster
rpm -e `rpm -qa | grep -i nautilus`
Nautilus is pretty, but you certainly don't need it to get the most out of your system.
I would still have to say that the software itself shouldn't be illegal. It's sort of like owning a tiger. I should be allowed to own a tiger, but if I let it get out, and it kills someone, I should be held responsible. Same with virus software. If I write it, and run it on my LAN to prove a security hole, that should be fine. If I allow it out of my posession, and someone turns it loose on the internet, I should be held responsible. That includes if someone hacks into my network, steals the virus and then turns it loose. I'm still responsible. Same as if someone sneaked into my back yard and set my tiger free.