Stop Microsoft
All Things Microsoft => Microsoft as a Company => Topic started by: Druid on 8 February 2002, 21:59
-
I came across this article and thought that it might be of interest.
Surprise Settlement Splits Microsoft (http://www.satirewire.com/news/jan02/patchsoft.shtml)
Druid
-
saw that a while back too .... nice sense of humour those guys over at satirewire have (http://smile.gif)
-
Correct me if I'm wrong, but Macro$haft doesn't actually make software. Shit, even WinXP is just a patched up version of Win2K.
-
And Win2k is just a screwed up version of NT.
-
Careful now... that implies that NT wasn't screwed up!
I was most surprised a few weeks ago when I discovered that one of my NT servers had been up a whole *60 days* without a BSOD/reboot/reinstall SP6a/Security rollup farce.
Of course all of our Linux and FreeBSD servers have run continuously since the last time they needed a hardware or kernel upgrade. One of them has been up well over a year now.
Not to worry though... I am gradually and surreptitiously replacing the existing NT servers with Samba 2.2.3a. Done one already and nobody noticed. I tell a lie... a couple of people asked if I had changed anything since their network drives seemed a little faster..!
It's so difficult convincing manglement that Linux is a better solution than NT/2000. They seem to think that the mere fact that you pay through the nose for it means that it will be a high-quality and well-supported system.
-
Dam its like reading an industrial espionage novel...good work.
I think the reason the fucktards in management have that impression about $$ and MicroShit products is that...."you get what you pay for".
Or as I like to say "you pay for what you get"
:D
-
IanC, I have run Samba in place of NT servers for quite some time. In fact I have been doing contract work for a company and every time I go over there I install another Linux server for them and have replaced a few of their NT servers. None of them have been file and print servers mind you. Now tomorrow they want to set up Linux on a hefty server and eventually want to replace their main file servers. I told them I would be more than happy to help eradicate but there are several things they must consider. They are already familiar with the NT way of setting up shares and permissions etc. I have no problem personally editing the config file with "vi" for creating shares. My partners are less familiar with *NIX and can set up shares with "swat" and/or "webmin" with little trouble. I usually set up Samba as type "SERVER" and point to an NT domain controller so you can use NT domain users in the permissions. I was curious if you knew of other graphical tools that maybe an MCSE or lesser could be comfortable with?
Regarding your "uptime" on your NT server. You're uptime is only going to be as good as your last service pack. Damn it's nice to be able to upgrade without having to reboot. I have a few Linux machines with over a year of uptime!
-
Other than the two you mentioned, I'm afraid I haven't tried any other graphical tools. I refuse to employ MCSE's so anyone here who has any responsibilty for creating / modifying shares etc has the necessary clue and sudo+webmin rights to do so.
It does get a little laborious maintaining a copy of your NT user list on the Samba server as well as the Domain, but the release notes for 2.2.3a assure us that will be sorted very soon... :)
-
Imagine that! those poor misguided fools waste their precious time, and cough up their life savings into Bill Gates' chamber pot, just to get an MCSE, and then people like you make a point of refusing to employ them!
Well done!!!
-
My CV includes the phrase:
"I am not Microsoft Certified and never intend to become so."
The pimps routinely try and edit it out when they send on my CV but I don't let them...
As far as I'm concerned any company that's looking for an MCSE just doesn't really know what they're looking for and I certainly don't want to work for them...
I've signed up for RHCE (exam only) in May... that really looks like a qualification that's worth something.
-
Unfortunately the company I do a little contracting for had 0 *NIX until I started doing some work for them. Now they have several Linux boxen. And they also have 0 *NIX literate people, but I am changing that. In fact I don't believe any of them are actually MCSEs (I just use that term for anyone who only knows MS OSs). They are actually better than MCSEs because as an MCSE by default you can't even trouble-shoot your way out of a cardboard box.
-
Yeah... I've worked with (read tolerated) MCSE's before. They think they know everything when in fact they can't even properly maintain the systems they've been trained for never mind opening up their minds to anything else.
A few years ago I worked through an NT MCSE book. After I had finished it I realised why this is. The MCSE does not prepare you for real-life situations, interoperability and most disturbingly it does not give you any real problem-solving abilities. There are predefined problems to each of which they advocate only one predefined solution. There is no scope for creativity in problem resolution. If you don't do it their way, it's wrong - even if your way works just as well or better. Needless to say I decided not to waste any money on taking the exams.
Wherever possible, I prefer to take people on at a junior level who show real enthusiasm for IT, logical thinking and common sense. Their actual professional computing experience is almost irrelevant as far as I'm concerned...
-
I totally agree! The last company I worked for (about 5 years worth) had several MCSEs. Guess who they called when they had problems with their MS DNS, WINS, NetBIOS, TCP/IP, NetBEUI, registry, virus, and more problems when they couldn't figure them out? It was so bad I was spending more time fixing Win* problems even though I was the top *NIX guy at the company, I just plain got burned out on it and gave up hope.
And I don't know how many times I've been asked "Do you have your MCSE?" and I have to answer "no, and the day I need to get one is the day I get out of the computer business". It makes me sick when HR people think having an MCSE is important. When I hired people to work for me if I saw MCSE on their resume they went straight to the bottom of the pile.
I'll bet 50% of the MCSEs I've met have never touched a server or any other operating system other than MS Win95/98 and just studied the books and took the tests as their ticket into a server job. Turns out when they get into the real world they do not have a clue, nor are they apt to get a clue even after a year or more of being in the field (most, not all of them). Then, their cert becomes worthless when the next version of Win* comes out and they have to study and take more tests to become certified in the new version. When do they have time to learn real trouble-shooting and problem resolution?
So in my opinion, the *only* thing that an MCSE certification ensures, is more money for Bill Gates. It puts them on a one way course to nowhere. And if the MS empire ever *does* fall, they will be flippin' burgers, but hey, the world needs burger flippers too.
[ February 13, 2002: Message edited by: VoidMain ]
-
The MCSE programme is another one of M$'s Fear, Uncertaintly and Doubt tactics to strengthen their stranglehold on the server market. It's easy to pass (it would have to be having seen some of the muppets who have passed it!) and so there are loads of people out there proudly proclaiming their MCSE status on their CV's.
This leads companies to believe that they will always have access to a large pool of employees that are skilled in maintaining, upgrading and troubleshooting a M$-based infrastructure. This is of course seen as a Good Thing by upper manglement and thus M$ infrastructures are deployed and a policy of hiring MCSE's implemented.
Unfortunately, upper manglement are so far removed from the sharp-end of the IT infrastructure that they really don't understand the consequences of this policy. And the real killer here is...
...because they only employ MCSE's there is no-one capable of properly explaining to manglement why the infrastructure is not performing as well as it should, and no non-M$ solutions are ever considered. The company invests in more servers and M$ products because they assume they have just overloaded them and need to spread the load.
You know what's coming next.
The use of M$ products now has so many companies in the position such that to support their user base they are having to add new servers every year. Implementation and maintenance costs rise. New MSCE staff are hired to look after the spiralling numbers of servers.
Where can they go? What can they do?
".NET" says Microsoft.
"We'll take those server costs and troubles off your hands for you."
"For a fee. And by the way, if you're late paying us we'll sell your data to your competition."
"What the hell, we'll probably do that anyway. Read the EULA"
They are creating problems so that people will buy the otherwise unnecessary solution from them... a solution which will of course have its own problems.... ad infinitum.
-
quote:
Originally posted by IanC:
Wherever possible, I prefer to take people on at a junior level who show real enthusiasm for IT, logical thinking and common sense. Their actual professional computing experience is almost irrelevant as far as I'm concerned...
Amen (http://smile.gif)
If I weren't already employed I would have asked you for a job ;)
21, no degrees (college drop out, long story, don't ask (http://smile.gif) ), no actual prior professional programming experience but got hired as a (jr) programmer (this may come over a bit cocky but I wouldn't have expected otherwise (http://smile.gif) ) and have been working there for about 7 months now and am really loving it, and have learned more there in 7 months then in 2 years of college (by far ....)
We have some MCSE books lying around the office but it's still quite the mystery as to why seeing we are a linux only company (http://smile.gif)
[ February 13, 2002: Message edited by: BadKarma ]
-
Wow, lot's of smileys in that last post ....
Let's just say I'm making up for the lack of them in your posts :D
-
quote:
Originally posted by BadKarma:
Wow, lot's of smileys in that last post ....
Let's just say I'm making up for the lack of them in your posts :D
...sorry! I'm a bit of a text purist at heart :D
My experiences are very similar to yours... I did just about scrape through my degree (non-computer related) and worked in general office admin for a couple of years after. Got my first IT job supporting OS/2 for a large financial company and haven't looked back since. Diving in at the deep end and getting real experience is by far the best way to go.
As long as you're always willing to really push yourself and are not afraid to learn new concepts you should always do well in IT...!
-
Linux/*NIX people usually like to know as much as possible about everything to do with a computer. There's nothing wrong with having MCSE books (as long as you know you are looking at a one sided view and you can get them for free). I had the NT Server Resource kit and actually read the damn books which is why I could resolve the WINS, DNS, TCP/IP, etc issues with MS. I looked at it from a lower level than the "point & click" level of an MCSE and could understand the real issues. I'm sorry but you would think with the "SE" part of MCSE people could at least read and comprehend. The "SE" has become severely devalued with the MCSE. Actually, I would say it's false advertising.
-
Anyone from the area correct me if I'm wrong, but I believe they're not allowed to actually use the word 'Engineer' in the certification description in Canada...?
I think this does apply to all IT certifications, but it would be nice to think the Canadian government was so clued up as to realise that M$ certificants could never be described as "systems engineers"!
-
MCSE= Minesweeper Consultant, Solitaire Expert :D
[ February 13, 2002: Message edited by: jtpenrod ]
-
quote:
Originally posted by IanC:
It does get a little laborious maintaining a copy of your NT user list on the Samba server as well as the Domain, but the release notes for 2.2.3a assure us that will be sorted very soon... :)
IanC, I did a little Samba work today and I no longer have to maintain two userid lists. "winbind" is pretty freakin' cool! I downloaded/built/installed 2.2.3a as you suggested. I turned on encryption and made my Samba server a member of my NT domain and set "security = DOMAIN". Fired up winbind and samba and now I can use NT userids and groups not only within the samba configuration but at the *NIX level. I can make local files/directories owned my NT userIDs and set group permissions to NT groups.
In addition to that a little playing with /etc/nsswitch.conf, /etc/pam.d/login and /etc/pam.d/ssh now allows me to log in to my Linux box with an NT domain ID and password. Without having to create a local account or having to manually update any list, winbind does it all. It's very much like NIS but it let's NT play along. I can also ssh/telnet to the box using an NT ID/password. Looks like we'll be replacing those NT fileservers VERY soon at that company I mentioned!
-
Yeah, I had just discovered winbind last night and was playing with it on a test server... it was about 1 o'clock so I didn't do quite well enough to get everything working absolutely right but I reckon I'll have it sorted later today!
It does look like exactly the sort of thing Samba needs.. that way after it's all set up correctly all permissions etc can be dealt with by NT group membership and User manager and even admin types might never realise they're not dealing with an NT server!
Excellent, Smithers.
-
I only had one issue that required changing some code. I wouldn't have found the issue because I usually edit the smb.conf file in my favorite text editor (vim) but I was talking a partner though viewing a share with swat and found a bug in swat.
First the only way I could find to use the NT domain groups in the smb.conf file (found absolutely no examples anywhere) was this format:
valid users = @"MYDOMAIN+Domain Admins"
The domain MYDOMAIN has the "Domain Admins" group that I wanted to grant access to a share so you use the "@" just like with UNIX groups and the group name. With winbind the group name shows up in the form of "DOMAIN+Group". And because a lot of NT domains contain a "space" in their name they need to be quoted. The only way of quoting that I found that would work is in my "valid users" example above.
Now, "swat" doesn't expect any quote marks in the string of groups and when I view the properties of that share in swat I get just an "@" and nothing else. I realized that was because in the HTML the tag looked like:
value="@"MYDOMAIN+Domain Admins""
So you can see why only the "@" was displayed. I then started looking over the source for swat (it's a C program) and found where it spit out those types of form elements (only two places need a simple change). Now the HTML that it spits out looks like:
value='"@"MYDOMAIN+Domain Admins"'
I just replaced the double quotes in the value tag with single quotes, recompiled, and it works like a champ. And no you can't use single quotes in the group name, tried that first and it doesn't work. I wouldn't have had to change the swat code if it did work.
At any rate, it seems to be working perfectly. Will be doing more heavy duty testing tomorrow probably.
-
...excellent work, thanks for the tips. I really must learn C properly at some point so that I would stand a chance of being able to debug source code like that!
One of my first actions when I started working here was, as part of my push to secure the NT network as far as is possible, to remove or rename all of the predefined NT groups and usernames in the domain. And of course their replacements and any further groups that have since been added do not have any spaces in them. It Just Seems Wrong.
So maybe I'll be okay...
Cheers
-
quote:
Originally posted by IanC:
One of my first actions when I started working here was, as part of my push to secure the NT network as far as is possible, to remove or rename all of the predefined NT groups and usernames in the domain. And of course their replacements and any further groups that have since been added do not have any spaces in them. It Just Seems Wrong.
Good idea... on a side note, I got ACLs working today on Linux local filesystems and within Samba. Now if you access the Samba shares from an NT/2k client you can change the permissions on files and directories just like you can on an NT server. You can't really tell you are connected to something *other* than an NT server. You can add NT Domain groups or users to the ACLs and set any of the attributes that you can do on an NT server.
I had to grab the kernel source and apply the ACL patches first, and rebuild Samba with ACL support (and add a couple of other minor things). I used to use ACLs on AIX years ago, it's pretty cool being able to do it in Linux now, and even cooler to be able to do it through Samba. Goodbye NT file servers. Good riddens!