Why do IT people really bash Windows?
This is page 5 of the discussion. Read the opening post
Windows Forum
This is page 5 of the discussion. Read the opening post
by jmgarvin
Has it come to this? Defending an unstable OS with: but it has thousands of sucessful executions before it crashes!
On and Linux has wonderful driver support, no thanks to many manufacturers. The driver community has really done a bang up job with wireless, nvidia/ati, and various "unsupported" hardware (ala Winmodems).
by wdewey
If you are using market saturation as your indicator then there shouldn't be any bashing except for Microsoft because there hasn't ever been any company with that kind of market share (in desktop computers). Also, People bash Windows Servers and they are not the Joe Blow Internet types either.
All I am saying is that there are industry leading companies that have solid reputations for quality, and then there are those that have reputations that don't quite live up to their talk.
Bill Dewey
though some bias may have crept in as I'm a software engineer, who's put his time in on admin and support as well.
There again, because I'm a software engineer maybe I have some vague appreciation of how software should be designed and as an admin how I'd like it to be designed.
Oh well back to work now, design decison to make, should I have an oval button that may work or pehaps a hexagonal one. It's got to glow on mouseover as well, very imporant that and I've got to come up with an icon. It will indicate this backs up your critical data that you can not afford to lose it under any circumstances if you want to stay in business.
Hmmm
The MS standard appears to a rather boring OK in 12 pt sans serif bold, we can do better than that surely.
Tahoma I think for starters.
by jmgarvin
I'm not going to beta test Vista. I never said I loved Windows, I just said you shouldn't bash the OS.
Anyway, you opening paragraph is a bit harsh isn't it? You assume to much. Maybe I'm just taking the whole tone of your post wrong but it does seem a little harsh to me.
Ahh, who cares anyway. It's only some 1's and 0's in the end. It's not like you're really being mean. :)
by hal 9000
Sorry if it didn't come through that well. I sort of get sidetracked and lost it a bit.
But I'll be Beta Testing Vista and have a new product ordered to play with. Not because I really want to but because it is a job requirement. :(
Col ]:)
Boo Coke! :D
Actually they both have their ups and downs. I just like Pepsi a bit more than coke. :)
by alacrity
Why is it that I ran my entire company for 4 years on NT 4 server and Windows 98 workstations. Then upgraded the workstations to Windows 2000. Now I have Small Business Server 2003 and Windows XP pro, SP 2 and have been running the server since LAST august with only the reboots needed for patches and those apps that INSIST you reboot even though you don't HAVE to. And my general workstations run for many weeks without problem. MS Office (Outlook, Word, Excel, Front Page, Publisher, power point - often all running at the same time), QuickBooks Pro, Hot sync software for Pocket PC enabled phone, Several web pages (hey.. I ain't ALL work) Symantec antivirus and /or Firewall, AVG, Spybot and/or Ad Aware, etc, etc. This workstation I'm on now hasn't been re-booted since the last Norton AV update forced me into it 3 weeks ago. My last install of NT 4 SERVER wasn't rebooted for nearly 3 YEARS!
I say it IS possible to produce a stable system using Microsoft products, I have 14 years of Proof! End users that I support (most have used my services for over 11 years) all START with a stable system and then muck it up so that I have to get it straight again, but that isn't MICROSOFT's fault! the USER messed it up. OR malware messes it up, but Microsoft products have treated me and the companies I support very well. From time to time I have to tell a user "No, That's not a good idea" becasue of some security risk left open in MS products. Sometime it takes Microsoft a lumbering long damn time to close the hole. My time spent building $30,000,000 CRAY computers taught me that simply slapping a "fix" on one place just might break something you don't know about in another place. I remember one system designer asking if he could "just move the edge connector 20 mils over" and got approval from his manager. that caused nearly THREE Million Bucks to be spent to correct the problem caused downstream from his department. Microsoft MUST be as sure as they can be that the "fix" they throw out to patch some hole does not create a new hole somewhere else.
My last point (made somewhere up above, I think) is that it IS possible to have a stable solid system using Microsoft products. If you are NOT able to do this, perhaps it's because your skills are not up to snuff. Actually I firmly believe that it's NOT your tech skills that are too LOW, but too HIGH..
Just my $.02
Alacrity
by roaming
by slsb
I agree with many that posted concerning Microsoft's security and stability. It could also be how long they have been around.
I also think that they get bashed alot for being the "big dogs". Not to get too political... it's like whoever is President gets bashed alot for doing right or wrong actions.. doesn't really matter who is in office. Pretty much the point is that the bigger you are, the more $H!t will get thrown at you.
As a side note (and the best reason), it might just be if the company or executive staff (or its marketing or anything else about the place) can be made fun of on Saturday Night Live or MadTV. :-)
by hal 9000
Admittedly I come from a Mechanical Engineering background but a Catastrophic event implies to me at least the total destruction of the thing how do you have something considered as "Very Catastrophic" when the thing is already destroyed.?
Like how much more can be destroyed when it is totally destroyed in the first place?
Col ]:)
by hal 9000
Is that with a Nix server you don't have to reboot when you apply patches or new Applications only Kernel Upgrades.
Admittedly I do come from a Unix background and I'm not used to all the rebooting that Windows requires. Instead of considering several weeks up time as good I would be considering only several months up time because of a patch bad.
But if you've never used a Nix you'll never know what the unnecessary steps that you are going through and the extra money that you have to waste on security which shouldn't be necessary and is affecting your bottom line.
Col ]:)
by ungle
Yo, dude. Windows is (effectively) the same. The only reason reboots are necessary is
a. You don't know what you're doing,
b. Sloppy packaging or
c. one of those MS patches that in the MS world is effetively a patch on the kernel.
I do agree with the several weeks bit, though. I recently was involved in a move of the Asia head office of the financial house I was working for at the time, and discovered one of the trader's PCs (extremely heavily used) had been up for 4 months.
by jmgarvin
by doublebeat
I read some responses that mentioned standards between Operating Systems, and computers. I think that this would be a good place to start if people think total OS compatibility is in the future. There are some areas of technology where this is already in practice, such as the battle of the Web Browsers!
The organization known as the W3C, or World Wide Web Consortium, is setting standards in HTML formatting and rendering. As usual, Microsoft is lagging behind in complying with these standards. They have a dilemma. Some sites are designed around IE, and don't work well in Firefox or Opera since their design relies on certain faluts in IE's page rendering or display.
If an organization was set up to lay out the ground rules for compatibility, and the software AND hardware vendors were made to follow it, cross-platform compatibility would be possible. Vendors would have to spend time making sure their products met stability standards, along with even display or testing standards. This would not only improve the user's experience, but make it possible for people to choose what OS to run. All the software and hardware would work on all the platforms.
One can only dream . . .
Of course, the best way to make all this better would be to make EVERYTHING open source. Human Knowledge belongs to the world!
Again . . . One can only DREAM!
by apotheon
Let's see . . .
POSIX standard (with which basically all unix-like OSes are compliant)
LSB (Linux Standard Base)
FHS (Filesystem Hierarchy Standard)
Meanwhile, you've got Windows of any stripe, which complies with
. . .
nothing.
Windows XP Pro isn't even fully compatible with Windows 2000 Pro.
Microsoft aims for market dominance. One of the tactics it uses is intentional standards violation and intentional interoperability problems. This is one reason of many that a lot of people prefer Linux: they like a system that aims to be [b]more[/b] compatible with both its own variations and those of other OSes. While Microsoft keeps changing its implementation of SMB the SMB protocol and CIFS, in an attempt to discourage interoperability with other OSes, the open source crowd using Linux is constantly improving on Samba so that it can access new versions of Windows SMB/CIFS networks without losing the ability to interoperate with older Windows versions and any other system that might use SMB, such as other Linux systems, new and old.
by doublebeat
Well, I guess we have come to the conclusion that open source is the way to go. I think that while linux runs great for me, it's not going to gain a share of the desktop market unless it becomes more operable with Windows. This isn't going to happen unless Microsoft uses file systems like ext2 or ReiserFS, or releases the code to read and write properly to NTFS. I guess that is what I meant by standards. Use a common filesystem, a library format that can be understood by multiple systems, and the like.
We can be almost sure that this will never happen. As long as Microsoft continues to be like they are. I wouldn't say that their product is inferior because of bad code. Linux is superior simply becase anyone can see how it works and design driver or device to mesh perfectly with it. If Microsoft would make a better effort to ensure drivers and programs that operate inside it don't degrade performance.
Microsoft is attempting to implement some form of standard. Signing drivers and stamping systems with their logo is their first step. Maybe they are becoming better . . .?
I think Windows needs a whole makeover. If Microsoft can start from the ground, and can follow a few simple steps like I mentioned earlier, they'd have a better product and a happier user group.
by rkuhn040172
I'll answer any and all of your questions, however, I grow tired of arguing with you.
I am a business tech. I am employed to minimize disruption, maximum profits, improve processes, and service my customers.
I, unlike you, don't tell other people what is in their best interest. I, unlike you, am open to all and any solutions based on my customers expectations, goals, needs, etc.
I, unlike you, am not egoistical. I, unlike you, don't have several hours a day to waste responding to posts on TR.
I will always help educate my customers but will ultimately go with their decision and make the most of it...whether that be Linux, Windows, or whatever.
No decision is made in a vaccuum. And not all decions are perfect (including Linux). To insult those that choose Windows is unprofessional at the very least.
To pretend that Linux doesn't have its fair share of security issues is naive.
As a matter of fact, I browsed through the Linux section on TR and you seem to like responding more to Windows issues (taking jabs) than helping those with Linux issues...I wish I had the time to count the number of responses to prove my point but I have better things to do.
I will point out though, that several of you recommeded a MCSE to someone as opposed to a Linux cert, mentioned SATA isn't supported yet, openly admitted to less support, software, drivers, etc, and overall are alot more honest in the Linux section that your repeated jabs in the Windows sections.
Being closed minded is one of man's greatest weaknesses. I have repeatedly mentioned I am open to any and all solutions.
Linux may be technically superior. But I live in the Midwest of the USA and Linux isn't anywhere near where it needs to be.
Not to say it won't be one day. I but live and work in the "real" world and Linux at this point in time just isn't significant enough to gather anything other than mere curiousity.
Counter that...you'll tell me I'm wrong, because of course, you know my life's experiences better than I do, don't you?
by rkuhn040172
by roaming
by laidlaws
I don't agree. Your argument assumes that every OS is fundamentally O.K., and all problems arise from how you use it.
I wish that you were right about Windows. Somebody tried to tell me that Windows was O.K, but the applications written for it were unreliable. The opposite is the fact. There are plenty of very good applications let down by the Windows OS.
When Microsoft get rid of the mindset that Windows is automatically good, and everybody should love it without looking; when they have a real assessment of the quality of their product and do something about it: that is when they will start getting customers coming back (me included.) I would love to be using Windows right now, instead of doing all I can to avoid it.
Doug.
by apotheon
I think you're misunderstanding what's happening. Windows devotees have a tendency to see Windows and Linux as being "in competition", but based on my experience Linux enthusiasts typically just want to see the Windows stranglehold broken, and take umbrage at the blatant fibbing of the Microsoft marketing department.
Y'see, I don't think Hal is trying to win you over to his "side". Have you ever seen him post a major troll-post like this thing about IT people "bashing" Windows, implying ulterior motives? The entire discussion starts with someone wildly speculating about Windows haters, making Windows out to be the operating system used by superior intellects who understand that anyone complaining about the failings of Windows must be using it wrong. Yes, that's right, anyone that points out flaws in Windows must be incompetent. Security vulnerabilities are the effect of wider-spread use, regular system crashes are somehow magically the fault of the user or the application developer, and everything that ever goes wrong with a Windows box is [i]someone else's fault[/i].
News flash: If your OS locks up or crashes, it's the OS that's a problem. If someone can exploit a single application to leverage system-wide permissions escalation, it's the OS that's a problem. If you have to restart the computer regularly, it's the OS that's a problem. Don't even get me started on Service Pack 2 for Windows XP, EULAs and license payment schemes for anything after Windows 2000 SP2, or the Microsoft policy of making you pay to report a bug whether you get any help out of it or not.
There are occasional Linux users who play the same game in reverse, making crap up as they go along in their attempts to aggrandize Linux and denigrate Windows. There are bad apples in every camp. They are fewer and farther between, however, for one simple reason: there are many, many more people familiar only with Windows and not Linux than there are familiar only with Linux and not Windows. Show me someone who is propagandizing rather than arguing the actual merits of a system, and I'll show you someone not terribly familiar with one system or another. Show me someone discussing the [b]actual characteristics of the systems[/b], however, and you're probably dealing with someone that has extensive familiarity with both, such as Hal, jmgarvin, or me.
If any of the three of us ever "bash" Windows "unfairly", it's in jest. Catch us in a real debate like this, and you'll see that everything you've read that looks like "bashing" is a response to some absurd misrepresentation of the facts with relevant, technical know-how. Hal has been dealing with both Windows and Linux systems since Jesus was an end-user, I carry multimple MS certifications and am the heterogenous networking specialist (integrating Linux and Windows solutions) for an IT consultancy, and jmgarvin [b]teaches[/b] about computers [b]professionally[/b], for cryin' out loud. We're not snot-nosed know-nothings being a bully to Microsoft in the playground. All three of us are IT professionals, knowledgeable experts, and quite unwilling to speculate outside our experience without a clear label on what we're saying as speculation.
Meanwhile, I've lost count of the number of times I've provided (here at TR) counter-examples, architectural surveys of Windows, and links to vulnerability-tracking resources to debunk claims that the only security problem Windows has is popularity.
In the end, people like Hal aren't trying to win you over to a "side". They're just correcting misapprehensions and blatant Microsoft marketing department falsehoods, offering the benefit of their experience.
. . . or do you really think Hal doesn't know what he's talking about? He clearly has issues as a writer, and should never be a journalist, but it's hard to find an IT worker that obviously knows his sh*t better than Hal, about both Windows and Linux, as well as other OSes.
by wordworker
They're just correcting misapprehensions and blatant Microsoft marketing department falsehoods, offering the benefit of their experience.
Many of the Windows sysadmins who post in these discussions have just as much experience running Windows systems as you and Hal. Yet, when they attempt to say "hey my Win systems are running just fine," certain "Win-Lin" experts jump all over them and accuse them of being slaves to Bill G. and his mighty marketing machine. I think you have to admit most of the negative and derogatory comments come from the Linux or Win-Lin folks and are directed at the Win-only crowd.
I think you and I agree that IT pros need to educate themselves as much about as many operating systems as possible in order to best serve their customers. As someone interested in learning more about Linux, I am more inclined to pay attention to and respect the opinions of a Linux expert who doesn't feel compelled to use "M$" and other anti-Microsoft slang every time they post.
And you're wrong if you don't think there are "sides" here. It's not a competition, I agree, but there are two distinct camps, if you will - those who are closed-minded about open source, and those who are willing to integrate new tools, if it will help accomplish the mission.
If Linux is going to make inroads into the corporate desktop market, people in positions of influence (IT managers, directors, CIOs) need to be convinced that bringing some Linux boxes into the data center is a good idea. In *my* experience, corporate IT decision makers aren't rushing out to integrate Linux into their centers because they don't fully understand the options and benefits of open source tools.
I know many IT director-level types who would LOVE to replace their Wintel desktops with Linux boxes, if it means better security, better performance, and lower costs. But they aren't convinced - as you and Hal and others are - that Linux desktops are viable alternatives to the tried-and-true (if expensive and insecure) Windows boxes.
It seems to me you're assuming the mantle of Ambassador of Open Source Solutions, and I applaud your efforts. But all too often, what you see as "correcting misapprehensions and blatant Microsoft marketing department falsehoods" comes across as if you're telling IT pros with years of Win-only experience that they're stupid and out in left field. In short, your precious Linux may be winning the technological battle, but the Linux community is losing the public relations war. To get through to the decision makers, the Linux crowd needs to spend less time bashing Wintel and more time communicating the benefits of open source tools. I'm just sayin'.
by don-bans
Most system admins usually bash the OS for their lack of knowledge; period! I once worked in a midsize company which used Novell Netware (this was back in the days) for File and Print Services. Before my arrival, and during my few days at this company, when these Novell based Sys Admins were asked to install a Windows NT or Windows 2K system, they will look for the install disk, insert in the CDROM drive of the server, run winnt.exe or winnt32.exe and install service packs. Then they were done!!! No additional configuration... sometimes, they would not even get the latest drivers!
The outcome usually was a sloppy Win based server! Not secure, not tuned, not optimized. I usually called these admins "Default Admins" and their installations "default installations".
There are a lot of Windows Systems out there in the world today like the one I describe above. If these systems crash, or are not secure, etc... CIOs please blame it on your admins. Send them to take an MCSE certification or Linux certification course... and actually try to make sure they apply most of the knowledge they get from the classes! Learning these technologies without applying them is no use to anybody!
Anyway... my reply to you regarding the various OS is this:
Today, unlike 5 years ago, you have a choice of choosing an OS. Linux, Windows, MacOS. Make that choice and stick to it. If it serves you good, be happy.
It is almost stupid to go bashing the other OS. Most of us IT experts are not experts in everything... we could be security experts but at the same time not network or systems admin... etc.
Cisco Systems' network was once (or twice) broken into. Cisco runs a "dedicated" OS for their firewalls and network appliance. The last time I checked, it was not a Windows OS that runs in Cisco PIX firewalls and their IDS appliances. My conclusion is that a non-dedicated or multi-purpose machine running Windows, MacOS or Linux should not even be thought of as being secure! You will be dreaming thinking that these boxes are secure! Hackers are good at what they do... especially the good ones! The fact that they don't break into your feeble Linux box does not mean that they are not able to! It probably does not contain anything which they need.
by apotheon
MSwanberg: It sounds like you might actually have some interest in learning about how to use Linux. That being the case, I'll give the best quick-and-dirty beginner's advice I've got right off the top of my head.
1. Find a LUG local to you. Join the mailing list. Attend meetings. [b]Be nice.[/b] Be willing to leave your Windows expectations at the door: when you say "But Windows lets me do it this way!" you're short-circuiting the learning process for a system that does it differently. To find LUGs near you, check out http://www.linux.org/groups/ for listings by location.
2. When you've gotten familiar with someone that uses Linux (whether it's at a LUG meeting, at work, or elsewhere in your life) with whom you get along well, and this person is somewhat local to you, consider trying whatever distro they recommend and know about as your first major foray into Linuxy goodness. Sometimes, the Linux distro you actually need to get started is the one for which you can get the best help.
3. Understand that people only make judgments and offer advice based on their own experience, and be willing to take any comments people make with a grain of salt, whether they're discussing Windows, Linux, MacOS X, OS/400, or a Texas Instruments calculator. When someone says something is "better" than something else, find out what that person is evaluating, and compare it to what those who disagree are evaluating.
4. Don't get frustrated when you discover that learning a completely different way of doing things makes you not as much an expert with Linux as you are with Windows. You mention that you're a "power user" (with Windows), which in many ways means exactly nothing with Linux. The same is true in reverse: someone that is a "power user" with Linux may be at a loss in a Windows environment. The methodology for viewing hidden files at the command line in Linux, for instance, is completely different from the methodology for viewing hidden files using Windows Explorer, and it only gets more divergent as the tasks become more complex and require more expertise. Neither system is really more difficult to understand than the other, they're just each very different from the other, and thus liable to violate your expectations daily.
------------------------
Your frustration with your experience with Ubuntu is understandable, but your assessment of it is unfair, really. Ubuntu is designed as a desktop system, not a server. Yes, under the hood it's Linux, and therefore fully capable of performing any role for which Linux is suited, but it is by default a desktop distro, and as such the amount of effort it takes to vary from the default installation of that distribution to get a credible implementation of some other system role (such as a good mail server) grows somewhat.
There are pretty much three approaches to easy implementation Linux distros that are relevant here: easy desktop, clean server, and do-everything box.
The easy desktop systems are oriented toward those who want to stick something in the computer and, with a minimum of user interaction, produce an operating system environment that allows common desktop tasks like word processing, web browsing, and email communication. Anything beyond that sort of thing requires you to know more about what you're doing. Ubuntu is an example of the easy desktop distro.
The do-everything box installs everything under the sun, creating a system that has all the tools necessary to be a desktop workstation for power users, a developer's system, a webserver, a mailserver, a fileserver, and a dishwasher. Well, maybe not a dishwasher, but you can bet the kitchen sink is far from where you're sitting when you install one of these distros. This requires you to actually be a power user to get the most use out of your system for any given task (or collection of tasks), but if you're willing to sit around and do the point-and-click exploration for a while you can probably muddle through any reasonably simple implementation needs (such as setting up the Linux equivalent of Microsoft SQL Server), just as you could with Windows without being any kind of real expert. The major GUI-oriented distros, such as SuSE Pro, fall into this category.
Finally, there's the clean server type distribution. Sometimes these allow a default GUI installation, or a default server installation, or a default everything installation, but their real strength is in a nothing installation. If you choose initially to install absolutely nothing extra while installing the base OS, you'll get a minimal set of tools and find yourself booting into a shell interface with very little there. With either a broadband connection or a prodigious CD collection at hand, you can then proceed to install everything you need, but [b]only[/b] what you need, to do exactly what you want with this system. How easy and simple this is depends on which distro you choose and what software management options are available and typical for the distro, but ultimately when you're using this sort of setup you know that any failures with the system's implementation are your own fault. You generally have to screw up, whether through inattention or ignorance, to get undesirable effects with such a system. It's pretty easy for a newbie to screw up through ignorance with such a system, though, because when you're doing a lean and mean install like that you're expected to know what you're doing. This is my preferred approach to Linux installation, though I prefer slick, simple tools at my disposal to do things quickly and easily rather than having to (for instance) compile everything from source when installing it, or having to track my own dependencies one package at a time, so I use Debian, which offers apt, the most comprehensive and well-developed software management system available, measured for the things that matter to me at least. Obviously, Debian would then be the example of this type of system that I mention here.
You've mentioned being frustrated by the fact that Ubuntu is billed as being easy for the newbie to understand but failing to serve your purposes as a mail server. You've got to understand that it's billed as being easy for the newbie [b]because it's oriented to simple end-user desktop use[/b]. As for the complaint that it's not blatantly obvious that Ubuntu is really intended more for the desktop than the server, look at Windows: Windows XP Home (or even Pro) is a desktop system, and Windows Server 2003 is meant as a server. The average end-user hasn't even [b]heard of[/b] WS2k3. If you want to find out about the various distros and what their target audiences are, you have to ask around. If you ask for a distro that's "easy to learn", and that's the only criteria you offer, you'll get handed a desktop system, but if you ask about a distro that's relatively easy to set up as a mail server, you'll have to be prepared to ask for more specifics, just as you would for any other specialized task, like GUI development, web server, or gaming platforms.
You can surf the web and email from Ubuntu. I know this for a fact. Fire up something like Thunderbird, or whatever other default GUI mail user agent you've got, and you're in business. You said you wanted to get Sendmail running, then complain about how a PocketPC system can be used to check email, though; you're talking about two different things. That's like comparing Outlook Express with Microsoft Exchange. All you need for checking and sending email is some client like Thunderbird, Evolution, or KMail. Ubuntu defaults to the GNOME dekstop, and I don't recall what the default email client is in GNOME, but it should be easy enough to find it in the GNOME equivalent of the Start menu. All it takes is an Internet connection and the usual POP or IMAP configuration.
Ubuntu comes with an email server worthy MTA (Postfix, according to a cursory Google search) installed by default, and if you can find a full-fledged desktop-worthy distro that doesn't come with gcc (the standard C/C++ compiler on Linux systems) installed I'll give you a dollar. Yes, the easy to use Linux distros [b]do[/b] comes with these things.
------------------------
If you don't like editing configuration files, I'm afraid I'm going to have to suggest you stay out of the Linux equivalent of the registry and go back to using GUI configuration tools. Your experiences with RH8 are outdated, mind you, and it's true that Linux hasn't always been as accessible to the new user as it is now, but you should be able to configure any major Linux distro's defaults to suit your needs even more easily than you could tweak Windows configuration options, these days.
------------------------
You refuse to use newer hardware for Linux, and yet you expect the first Linux distro(s) you try out (without researching for suitability) to work perfectly on badly obsolete hardware. To give you a rough comparison in Windows terms, you're effectively expecting to have no problems installing XP Home, XP Pro, Media Center, or Server 2k3 on a Pentium 400MHz. You're simply going to run into problems doing something like that.
------------------------
Lack of games on Linux is definitely a legitimate reason to choose Windows, but it's not a legitimate reason to complain about the failings of Linux. Linux doesn't have as many professional games designed for it. Games such as Unreal Tournament and Neverwinter Nights will run on Linux, but others like Command and Conquer: Generals will not. It's kinda hit and miss, and that's the fault of the game designers. In fact, of the gaming industry's major hits that run on Linux, probably half only run on Linux because a bunch of Linux enthusiasts persevered in the face of a great deal of resistance from game vendors. The other half run on Linux because the game vendors have embraced Linux as another platform for their games, and created something specifically for Linux gamers. As I said, it's hit and miss, but don't blame it on the OS. Just use the OS you need for a given game, if you really want to play the game, and hope like the rest of us that eventually the game vendors will start developing for all platforms equally.
I'm not much of a gamer, so this really isn't an issue for me. The two games I've ever liked (Command and Conquer: Generals, and City of Heroes) enough to actually buy both run on Windows only, and as a result I've ended up not playing them these days.
------------------------
As far as books are concerned, I find that the more-advanced books are useful primarily as resources when you need to look something up and are just having no luck with manpages, Google, or a LUG mailing list. Don't bother buying them to introduce yourself to Linux in an orderly fashion. The way to get into Linux as a Windows power user picking up a brand new OS is really just to find a way to get yourself mentored in, preferably by someone local. I ended up learning how to get Linux going basically without help, and it was an interesting challenge to get past my initial misconceptions learned through long experience with Windows, but once I got past the hump things really started coming easily, and making a lot more sense to me than Windows ever did. I won't swear that the experience will be the same for you, but I don't see why it wouldn't be; I just recommend getting local help if at all possible to ease the process.
If you want to hit me up for help as you go along, feel free. Use my profile contact to get in touch with me (which will get us started talking to each other with email) and, for quick responses when I'm online, let me know if you've got a preferred IM service (AIM, MSN Messenger, Y!M, ICQ: I use all four). I'll offer what help I can from afar. I'd do the same with Windows, but you might get a little more grumbling from me over Windows-related issues if that's what you needed. Heh. I have my preferred environment, I'm afraid.
Best o' luck.
by jdclyde
I have long suspected TR will troll it's self to stir up the nest.
How many times have you seen someone start an argument just because they like to see people get going? I see it all the time. Used to do it to my little sister all the time. ;\
by wordworker
I refer to the "learning linux" post above. You gave a thoughtful and useful answer to the question, "how does an experienced Wintel person get his/her toes wet in the linux pool?"
I applaud you and encourage you to use your own advice when responding to Winzealots in future discussions - BE NICE. ;] You just might convert some of us old fogies over to the open source side of the tent. I for one now keep a Knoppix CD in my bag o' tricks. I feel a little less like a tech-dinosaur already.
These threads remind me of the days when I had to explain the DOS command line to old COBOL programmers who wondered where the card reader attached to the brand-new Wang PC the law firm bought.
by apotheon
Nice comparison.
I try to be as nice as possible when people ask me for help. Generally, you'll probably find that the Linux community as a whole is like that, particularly on most LUG mailing lists. Problems arise when someone comes in saying "Man, I don't have these problems with Windows." That's not a request for help: it's a statement about Linux vs. Windows. If your actual post, on the other hand, is "I'm used to Windows, which does this, and Linux isn't responding to what I'm doing, which is this. What am I doing wrong?" you'll get much more help.
Yeah, I could probably make more of an effort to be nice, but I'm often too lazy to go that extra mile when the person supposedly asking for information hasn't gone that extra mile first. I tend to figure, subconsciously at least, that if someone can't be bothered to ask nicely, I'm not obligated to answer nicely. It's not like I'm being paid for the help I provide at TR.
When I deal with clients of the consultancy, on the other hand, I bend over backwards to be as helpful as possible, regardless of initial tone. They're paying my bills.
By the way, thanks for the kudos.
by paul
Are you just winding us up ? heh heh !
nice one. Yeah well anyway back on planet earth !
It's not usually crashes which cause techies to
venomously explete at Bill Gates. Actually its mainly to do with inconsistencies between services, programs, and drivers, written by microsoft. The fact is that while Linux isn't great for the desktop, it offers a simplicity and
sturdiness of design that microsoft cannot replicate in its serverware. MS bashers are usually talking about the stuff like having to reboot every time you update the server etc. As far as compatibility is concerned - Unix is what the internet is based on hence http:// the forward
slashes are indicative of a Unix protocol. Microsoft is certainly not the standard of compatibility on the web.
by jdclyde
the HTML tag, although often bastardized to HTM by MS products.
"The internet is a fad" is something that always makes me laugh when I look at the way MS people portray the internet now.
Even look at how you are getting into this discussion board. TCP/IP is a unix protocol that was ADOPTED by MS to be able to play on the then entirely UNIX based internet.
But they always want to refer to the OSI model which is just a illistration of the TCP/IP model, theroetically to make it "easier to understand".
Ask an MS rep how alternat browsers will veiw a website made in FrontPage using the wizards and see what your response will be. I know AOL is goofy as a browser, but do I really not want someone to be able to give me money for my products/services just because I don't like their browser? AOL people traditionally are the ones with more money than brains anyways! EXACTLY the people I want as customers! Throw extra money at the issue so you don't have to know/do ANYTHING.
by apotheon
Personally, I avoid using such terms as "M$". They don't strike me as being terribly appropriate. I call it Microsoft, or MS, and I call it Windows. I don't tend to use the off-color terms that others sometimes do, in large part because I don't want someone to fixate on what I say as being biased and overlook the content of my statements.
That's really what's happening, here, much of the time. The moment someone says "Windoze" or "Micro$not", people tend to dismiss what he or she has to say. While I think that sort of pet insult of the MS empire isn't the best way to represent one's opinions, and might be evidence of poor communication skills under some circumstances, I still try to look past such things to see what is actually being said, what is to be learned from the post, and so on. I don't dismiss it out of hand.
I don't want to be the official Ambassador here. I don't want to tell anyone they're stupid, either. On the other hand, I'm inclined to offer my perspective where I think it's of value. I'm actually not the most diplomatic person in the world when I don't have to be: I'm quite brutally honest lot of the time, and that's probably part of the reason people take what I say amiss at times when I correct misunderstandings of the relation of Windows to Linux and vice-versa. When I see ignorance, I call it ignorance, and figure it's the subject's fault if he assumes I'm using a neutral term with pejorative intent. Ignorance isn't the same as stupidity, but peoplge get defensive when the term is used and react as though stupidity were the term used.
One of the reasons I don't do more to soften the blow is simple: my goal isn't to market Linux. My goal is simply to state what's true to the best of my ability. There will always be people who will believe inaccurate data, and I'm not in a position to significantly alter that. Frankly, I don't much care to. I'm looking for someone with information to share when I come here, and looking for people interested in learning rather than picking fights. I'm not a Linux proselytizer, I'm a Linux enthusiast and professional. I don't need others to adopt my OS of choice to feel my choice is validated.
The statement that Linux in some way "needs" to better market itself assumes the Linux community is interested in market share. The Linux community as a whole doesn't give a damn about market share: it's made up of individuals who care about the number of developers involved in Linux development, the ease of access to Linux technology, and the functionality of their computers. Market share is about doing "better than" someone else on some statistical scale, and the open source community is only about doing well, regardless of what anyone else is doing.
by jmgarvin
"The time and money spent re-educating your end users to Linux is much higher than the cost of security issues and maintanence of Windows."
This I'd have to see a study (not paid for by MS) for.
"If all you run is Linux, you are more vulnerable than I am"
Can you explain this? I'm not sure I understand...
by mrleo1957
What a stupid comment. Bug-ridden software is what causes crashes, not the operator.
I've used every OS from CPM on up. Windows is the only OS I've used that you can have the lastest drivers, all fully-approved parts, and still get crashes for no apparent reason.
by david.hirst
by techystuff
Why defend a buggy OS, I agree users mostley bust the OS, the OS shouldn't allow it to happen, or have I just talked myself out of a job :-(
Note: My old Acorn just needed rebooting as the OS was in ROM. Shame it wasn't developed more, as it was the right way to go. The only reason I say this, is I sometimes get bored rebuilding Windoze all the time :-(
I think eventually everything will be server driven, no more busted OS's only hardware to replace. The End
by tommy higbee
> 1. Yes, the command shell does imitate Linux/Unix a lot. So what's the problem?
Not a problem, just the point that a) yes, you can do that in Windows, but b) not really as well
> 2. The Command shell already has the environment variables %date% and %time%. What's your point?
> Yeah, I guess you can't put the result of some programs into environment variables on-the-fly, but who cares, because there's...
%date% and %time% are not the point, scriptability of program output is the point. Besides, those variables were only available starting with (I think) Windows NT.
> 3. Windows Scripting... ever heard of it?
Of course. Nearly mentioned it, but it was just a little too far off the topic of pipelines and redirection.
> I write down-n-dirty scripts that do all manner of things that you could never do with ANY BASH-type scripting
a) You'd be surprised at the sophisticated tools/applications that have been done with BASH or KSH scripting. (e.g. Metamail, Arch)
b) But you're really getting off the topic of the command line and talking about scripting languages
c) And since Unix has plenty of scripting languages too, most of which have also been ported to Windows .... well, I just don't see much point in comparing scripting languages.
> 4. The Command shell does indeed let you redirect STDERR. Trouble is, few program are written to take advantage of this separate output.
So it does. I seem to remember some problems with it, though... But since I don't remember what they were, I'll just concede your point.
> A buddy put me onto CygWin, which is a Unix-like shell that runs in Windows. Didn't take me long to see it didn't offer me anything that I couldn't already do in Windows.
Depends on what you're wanting to do. If all you want is better scripting support, and you've already climbed past the Windows Scripting Host learning curve, it may not be much use to you. But Cygwin is more than a bash shell. It's a Unix compatibility layer. Cygwin will let you port just about any Unix application or program to Windows. I use it to run a Unix X server on Windows...
In the time I've had XP installed (several months I'd say), I've never once had a BSOD. I don't think there IS one for this version of Windows. :) It's surprisingly stable on my machine. I've had apps disappear or stop running, but I just would click the close button to close them, or end them in the task manager. And that isn't too often that I'd even have to do that. Rarely, in fact.
I guess I'm one of the luckier ones that have little problems with the XP Pro version. Now SE? That's another story. :D
by hal 9000
At least here at TR granted I do use that word about my son who sees my computer that he has stolen as nothing more than a glorified play station. :)
But what I do constantly find interesting is that at every MS meeting that I attend and where I do talk to the Technical people rather than the marketing people I'm constantly told that I'm expecting way too much from Windows. Why is it then that the very people who are responsible for at the very least fixing the problems are saying this?
As for Sys Admins who have only had experience with Windows I actually pity them and in no way consider them as Stupid it's just that they don't know any better as they lack the experience. It's exactly like you have only driven small moped so that is what you expect a motor cycle to be like and you have no experience what a real motor cycle like a Ducati can do and how it behaves. These people are being force feed the Microsoft Marketing Lie which just doesn't wash with me.
Almost every Windows Only Sys Admin thinks that it is normal to have to reboot when a program is installed or a patch applied. It's not that they are Stupid buy just that they do not know that there is a different way of doing things.
AS for the server side of Microsoft it really is M$ as I'm constantly paying vast amounts of money for the Server Application OS or whatever you wish to call it and then extra for excess license fees. One company that I know very well uses 2003 SBE for their small network it is a Doctors Surgery with 18 workstations and 1 server with all the medical files on it. Now currently well previously until I told the owner how to fix the problem they could only have 10 concurrent connections to the File Server for the times when there where more Doctors there they just got used to having to wait to get access to the files. The solution was to buy additional Licenses for only $80.00 AU per box. Now that was only a few boxes and only a few Hundred $ on top of the already expensive OS that they had paid for. It is things like that that do really get to me particularly as I had to fix the mess that was made up by so called "Professionals" just to get a Script from a Doctor without waiting a very long time for the network to allow him access to the file server. It was something that I didn't get paid for and I only did it to make my life easier as I no longer do any Government or Medical work. But this should never have arisen in the first place. But the people who sold the complete system and where Microsoft Certified where not interested in selling a working network just the hardware and the software out of the box with no additional work needed. They just didn't care!
Of course it only gets far worse in a Big environment where I do use 2003 ES quite a lot but only for Domain controllers the real backbone servers are always Linux/ BSD or something else as the license fees are just way less. And I'm not talking about downloaded ISO images but boxed sets from the makers here. They are just plain and simple easier to setup and far cheaper to buy initially as well as being cheaper to run in the long term.
Col ]:)
by ungle
...so I see a blue screen. When my Linux machine (or the software running on it) screws up it's memory and I have reboot it, just because I don't see a cute blue (or red) screen with a memory dump doesn't make it any less destructive!
A reboot is a reboot. OS wars are pointless. They've all got their good and bad points. If your main complaint of Windows is the color scheme then talk to MS. They may change it for you. What color would you like?
by jmgarvin
by david.hirst
I think the main reason that people bash MS is the plain and simple fact that Microsoft with all its financial power and resources still charge a considerable amount of money for their products and services which are in some respects less secure or reliable than those of cheaper or free open source projects.
And then its down to the us and them groups who use MS or Linux or whatever other OS is out there.
Personally even though I have had my ups and downs with MS software over the years I still find that they are reliable enough for me to do the tasks I wish to perform day in and day out and I always think, "things can only get better"
by ungle
Switching from Unix to Windows....that would very much depend on the job you are doing - right tools for the job. Using vi as an editor...THAT'S whats stupid!
""you can't blame the OS" is obviously a serious rookie" Anyone who can't keep a windows server up for more than 14 days probably should not accuse others of being rookies.
In my experience, including one company with 15,000 Windows desktops, 5,000 Windows servers, 1400 Linux servers and I don't know how many Sun boxes, 99.9% of all problems on all OS platforms are caused by the software installed on top of the OS, not the OS itself. On Windows, because it dominates the desktop, that means usually caused by the user.
Beleive me, if Linux had the market share that Windows enjoys, you'd get all the spyware, trojans and other problems on them. Just think, if I was a spyware writer, would I write spyware for 5% of the global machines, most of which are run by computer enthusiasts, or would I write it for the 90% of global machines run by my mother in law who will click "OK" to anything? Not much of a choice!
Linux as a desktop OS plain sux. As a web server...wouldn't touch anything else!
by ungle
...because you seem adamant about this horrible instability.
Without wanting to be rude (honestly!), I can only assume you are doing something wrong.
I would start looking at standardized builds and reduced user rights. Talk the companies you work for into it, it will reduce dramatically the overheads. Yes the users will scream initially, but what are their machines for? Work!
Reduced user rights will also resolve the whole spyware issue for you. Remember, with only a few exceptions, the spyware the user downloads will run in the context of the current user. If that user has limited rights to the system, so does the spyware - it doesn't matter if the users click "OK" it still can't install itself.
Win32 OSs are inferior to *nix based OSs. Why?
The *nix OS design is much older and less assailable. It was created and developed largely through the efforts of people seeking higher knowledge or design elegance. It is well thought out, tried and true.
Market dominion and monetary enrichment are the driving forces at Microsoft. Win32 OS's are released to maximize profit, not because they represent any level of excellence, ie. Windows ME. Also, any claim of superiority in product was completely discredited when the 2KSP4 source code was leaked.
The fact that a much larger percentage of people use Win32 than *nix is just illogical and insulting to any real computer person. However, insult becomes injury very quickly when that same person has to perform the huge workload required to keep Win32 secure and reliable.
I think the bashing starts, when you blow a gasket trying to reconcile the marketing hype and the Microsoft promises with reality.
by mswanberg
EXCELLENT post, my man. I am printing it out to keep and refer to.
I guess the thing that's bitten me is the "easy to learn Linux" monniker that some of these newer distros throw out. Actually, they should say, "easy to USE Linux". I was hoping to actually learn the OS. Heck, I know how to use Thunderbird and Firefox (have both of them on my Windows boxes... very much the same on both OSes). I want to get into the meat of it. After all, if I used Ubuntu for e-mail and web-surfing and then came to you and said, "Hey, I KNOW Linux!" you'd laugh your ass off. "No you don't!" you would say. And I would cry. :-)
Kind of like if I wrote my "Hello, world" app in Java, I couldn't exactly put Java on my resume, could I?
I have no problem editing conf files, really. In fact, I think it's a pretty cool way to do things. But my issue is that the sources I've seen never ever tell you WHY I'm doing something. They always just say, "put this line in this file". There never seems to be a "if you wanted to do this, then you would change this. And this is what the various parms mean." Maybe I do need a good reference book. But I do appreciate your idea of finding a mentor.
Your post was an excellent foray into the nature of Linux. You yourself seem to be saying, "yeah, it's tough. It makes little sense sometimes. But it's worth it."
A few points of clarification. By "power user" I meant that I want my PCs to do more than just e-mail and web-surfing. I want them to record TV, convert video, play music, IM, allow me to write code for the stuff I can't find good programs for, etc. etc. All in all, what I'm saying is that the simple desktop distro is probably not for me.
Yes, I know the difference between an e-mail server and an e-mail client. My point was, if all I wanted was a web-surfing e-mail-reading machine, then I don't need to sacrifice a box to the Linux gods. I can do those simple tasks on, say, my PocketPC. But I want more out my desktop machines.
As an analogy, I feel as if I traded in my S2000 for another car that everyone promises me is way better. But I get in it, and it's like a Toyota Echo, and I have to stuff my head under the hood for days at a time to try and coax the "betterness" out of it. And everything I try doesn't work. But people keep telling me, "Man, aren't you glad you dumped that 0-60 in 5.2 piece of garbage for this awesome ride?" And all I can think is, "man, wish I had my S back."
I guess it's a little like "buyer's remorse" on my part, even though most Linux distros are free. :-)
In the end, if it were easy to learn, then it wouldn't be worth it, would it? I'll keep plugging...
-Mike
by djameson
by yuvipanda
by jmgarvin
by jmgarvin
1) Some apps require the user to have admin privs. This is a HUGE security issue
2) Windows doesn't have "user space." User space is smudged together with kernel space and other user space. It just doesn't make sense. It is far to easy to have and effect on EVERY PROFILE with a plain jane user.
3) Malware typically doesn't "install." It over writes dlls or just executes (and not just in user space). Spyware is a HUGE issue and if this was the solution, we wouldn't be having the problems we are having now.
by apotheon
by ron
by ron
by apotheon
I'm afraid you're going to have to elaborate a little bit on your wild assertions.
1. What's so stupid about using vi?
2. Why do you think that greater adoption of Linux systems would cause clicking OK to suddenly become more dangerous for Linux than it already is, when strict privilege separation on Linux systems prevents clicking OK from having the same system-wide implications it has on a Windows system?
3. What possible reason could you have for thinking Linux on the desktop is so stupid, while the city government of Munich (for instance) has the opposite opinion?
I notice you haven't satisfactorily explained any of the above.
by raven2
by apotheon
In addition to what jmgarvin said, I only have this to add:
I suppose you've never heard of things like ActiveX if you really think prohibiting administrator access to end users solves all those security problems.
by apotheon
Something to keep in mind when trying to migrate your "power user" skills from Windows to Linux is this: You didn't become a power user of Windows by sitting down at a Windows machine and exclaiming "This is easy!!!" You did so through years of working with Windows, learning its ins and outs, and picking up hints and tricks like how (to use an example from my own life) to turn off the desktop in the Win2k registry to increase general system responsiveness by probably 20% without loss of any functionality I actually used anyway (and, in fact, system security is increased marginally). This was not a trick I knew the moment I sat down, or for which I knew to Google off the top of my head. By the same token, there's a lot to learn about the flexibility and power of Linux that you can't get simply by putting an Ubuntu CD in the drive.
Regarding your issues with configuration files not being adequately explained, and other issues with finding helpful information: manpages are youre new buddy. Learn to navigate and understand the format of manpages, and you'll quickly learn to be self-instructing with Linux. The shell command "man [argument]", where "argument" is something about which you want information, will prove invaluable if you become a regular Linux user. There's a manpage for just about every command on your system, and if you can't find a manpage there's probably a help page (or, possibly, an info page, but the info system requires its own manpage to use and it pretty much tends to just duplicate the contents of manpages). So, try "man [argument]", and if that doesn't work, try "help [argument]". The difference is that help is for shell-native commands, and man is for separate programs (and other stuff) accessed from the shell.
Something many people don't know about manpages, and that can be of keen interest to you with your desire to learn more about configuration files, is that there's often a manpage for configuration files as well. For instance, using a Debian machine here, there's an obscure X server configuration file, /etc/X11/Xwrapper.config, and there's a manpage for it. I didn't even know this configuration file existed until just now, I decided to hunt up a random configuration file and found it. I typed "man Xwrapper.config", and it spat out a manpage that explains what it is and everything I need to know about it, in great detail. Surprisingly, it's a very small configuration file with very limited scope, and is very easy to understand with the help of the manpage.
Considering that manpages use less (or, on systems where less isn't installed, they use more), you have the ability to search for key terms very easily in manpages too, if you want to skip all the explanation and go directly to a description of a given configuration option. Open the manpage and type "/[search string]", where "search string" (minus brackets, as always) is whatever term it is for which you're searching. Probably the most important thing to remember when using manpages is that, just like less (or more), hitting the q key allows you to exit the manpage.
As I say, manpages are your new buddy. In short, Linux [b]is your reference book for Linux[/b]. The command "man" is actually short for "manual", and the whole collection of manpages is basically the definitive Linux manual. When someone says you should RTFM, that's the manual to which they refer in the Linux world.
By the way, you mentioned some multimedia uses for Linux. If you're interested in creating a highly-functional multimedia system as the centerpiece of your home entertainment system, I recommend looking into a Linux distribution called MythTV. It's Tivo, but better, with a lot of ability to hook into everything else under the sun related to your home entertainment system. I know someone that's actually running a 16-drive RAID rackmount system with MythTV in his closet (though I don't think he actually has all 16 drive bays filled yet).
Ultimately, Ubuntu doesn't have to be a Ford escort. It can be turned into an S2000, with a bit of work. Being specifically designed as an end-user's desktop system, though, it's more difficult to turn that into (for instance) a credible mail server than it is to do the same with plain-vanilla Debian. In fact the only thing it's not easier to do with something like Debian, Slackware, Gentoo, et cetera, than it is for a specialized large default install system is duplicate exactly the setup of that large default install. Since most people aren't actually interested in duplicating every last detail of such a system, though, and would actually like to change some things, you're probably better off with something that allows for a lean initial install and very flexible custom configuration, once you know how to make that work for you. I tend to view Ubuntu as a crutch to help wean immigrants from the Windows world off the Microsoft wheelchair. With Debian, on the other hand, I've tied on a pair of quality running shoes, and I'm sprinting. Sure, it took me some time and effort to get into shape to run like this, but I get around a lot faster now, a lot more flexibly, and without any more effort. In fact, lugging that crutch around can get pretty tiring.
. . . and thanks for the kudos. I'm glad I could be of assistance. As I said, feel free to hit me up with questions off the discussion forum if you want to.
by ungle
Vi is stupid because of one word: Emacs. And that would be the beginnning.
Yes, I've been force to build websites with vi, and even now if I want to edit my personal site directly on the server I'm forced to use vi. But I wouldn't use Notepad on Windows, why would I want to use Vi on Linux? I got into IT because I was excited about the advances in technology, not because I wanted to stop them!
The comment "Why do you think that greater adoption of Linux systems would cause clicking OK to suddenly become more dangerous for Linux than it already is, when strict privilege separation on Linux systems prevents clicking OK from having the same system-wide implications it has on a Windows system" is naive at best: If people log onto Linux as root, they do indeed have the system wide acces exactly as it is under Windows. I'm all for controling user rights under Windows, but I was refering to my grandma getting a PC and installing Linux on it herself. She'd use root as her default UID. Take a look at Lindows. Install it, and unless you go to the trouble of searching out how to create a new UID you'll have root privileges. Dude, you sound like you ran from Windows at the Win 98 stage. At that point I would agree 100%, which is why I set IT policy at my company to absolutely ban Win 95,98,ME on the network. Again, using Win 95,98,ME is...dare I say it? STUPID.
Finally, one body's adoption of a platform does not end the arguments on it's operability...or this discussion thread would not exist. I've used Linux as a desktop OS, I've use Open Office (I even installed it on a Windows machine. I uninstalled it about a week later). I'm not saying this out of ignorance, Linux has a long way to go to compete with Windows on the desktop.
I'll say it again: The right tools for the job. Don't discriminate just because you don't like dorky looking billionaires with glasses!
by ungle
jmgarvin, get OFF Win95,98,ME - which ever it is you are using - and get on to XP. That comment was born of ignorace. User profiles are separated and protected from another non-admin user from modifying them JUST as they are under Linux. A non-admin user CANNOT affect all other profiles on a machine as suggested. Besides, in an enterprise environment, the profiles are not held on the machine but on the profile server. If you have knowledge to the contrary I would LOVE to hear about it!
apotheon, if you'd like to explain to me how ActiveX (COM to us developers) exposes greater danger, I'd be interested to hear. It's just another shared library, a concept, although slightly different, used in Linux, Sun and MacOS as well. Did you hear about the latest zlib vunerabilities? They affected EVERY OS because they are installed as a shared library.
I guess My initial reaction to this forum was correct: People fear what they don't understand.
by ungle
Totally about the sloppy packaging. It REALLY gets up my nose. However, this discussion is about OS.
I've run Linux for a long time now. I'm totally pissed of with how often I've got to patch software/kernel.
by ungle
...And the same to be said of fly-by-nighters who don't know how to do similar tasks on Windows and who run home to mama crying when they can't figure it out!
Fortunately I don't fit either catagory...
by jmgarvin
just run cron job and restart the service if need be...Not much to it...
How often do you REALLY need to patch/update your software, unless your are running bleeding edge?
by hal 9000
But here we get a book all of about 12 pages long but it sure looks pretty. Green for the Home and Blue for the Pro editions. :)
But I wouldn't use the Plug & Pray as you already have everything plugged in and you know it works as you are seeing a picture on the screen it's only when you actually start the install that the Praying begins in earnest. ;)
Col ]:)
by jmgarvin
"jmgarvin, get OFF Win95,98,ME - which ever it is you are using - and get on to XP. That comment was born of ignorace. User profiles are separated and protected from another non-admin user from modifying them JUST as they are under Linux. A non-admin user CANNOT affect all other profiles on a machine as suggested. Besides, in an enterprise environment, the profiles are not held on the machine but on the profile server. If you have knowledge to the contrary I would LOVE to hear about it!"
Ok here it goes. In Windows NT, 2k, and XP user profiles are seperate only marginally. The problem is this: User Space, Kernel Space, and Executive Space are not exclusive. Each can (and does) overlap the other. This means I can affect the entire computer, not just a specific user space. It also doesn't help that IE is a huge security problem because it is built RIGHT INTO THE OS! I can take advantage of that and have an effect on all users equally (because IE is univeral).
What you are thinking of is user accounts.While each account is "seperate," the memory space that users fill over laps and can be taken advantage of. Sure, I can be authenticated via a domain, but locally user information is still stored, even if I don't have local drive access.
Take a look at the Windows Top 10 from Sans:
http://www.sans.org/top20/
"apotheon, if you'd like to explain to me how ActiveX (COM to us developers) exposes greater danger, I'd be interested to hear. It's just another shared library, a concept, although slightly different, used in Linux, Sun and MacOS as well. Did you hear about the latest zlib vunerabilities? They affected EVERY OS because they are installed as a shared library."
ActiveX is a mess:
http://www.us-cert.gov/cas/techalerts/TA04-184A.html
http://search.cert.org/query.html?rq=0&ht=0&qp=&qs=&qc=&pw=100%25&ws=1&la=&qm=0&st=1&nh=25&lk=1&rf=2&oq=&rq=0&si=1&col=xtracert&col=trandedu&col=vulnotes&col=techtips&col=research&col=certadv&col=incnotes&col=secimp&qt=activex&x=0&y=0
http://search.sans.org/search?q=activex&ie=&site=SANS&output=xml_no_dtd&restrict=SANS&client=SANS&lr=&proxystylesheet=SANS&oe=&submit.x=0&submit.y=0&submit=Search
"I guess My initial reaction to this forum was correct: People fear what they don't understand."
People that are security oriented and not just techs understand a little more deeply what is going on in the OS. Apotheon is very well versed in both low (kernel) level security and higher level. I know security from a sys admin and net admin point of view. I also am studying how to BREAK security in various systems, and guess what...Windows keeps cropping up on my list because I can take advantage of the poor seperation of Kernel and User.
Having been in IT longer than Bill, I remember what life was like before Windows, before MS-DOS ... and I can say without hesitation that Bill/MS and Steve/Apple have done as much to hurt the growth of the industry as they did to help it. Neither of these men entered the industry with any sense of professionalism, and they tended to surround themselves with people who, like themselves, didn't really deal with real-world problems or needs or issues. I don't view either Microsoft or Apple as technology companies; I view MS as a marketing company and Apple as a toy company.
Consider: is there any object in the business/industrial universe, apart from actual human beings, that fails as often and as unpredictably as a computer running a Microsoft operating system? We EXPECT those computers to crash, we expect them to crash often, and we expect them to crash unpredictably - and because of MS's stranglehold on the market, we have been forced to accept this very low standard of mediocrity, and for so long now that we can't imagine things any other way.
To accept that this is how it is reflects pragmatism; to say that it could not have been any other way is nonsense. There were a multitude of different courses that the evolution of personal computing could have taken, and there certainly could have been far more professionalism and quality, and far less technological narcissism ...
by ungle
Yes, dear, the kernel, executive, and - to a lesser degree - user spaces do overlap, as they must. And how exactly does this differ from Linux???
Of course profiles are stored locally - as a COPY of the server stored profile (it's called a "Roaming profile". Thought you'd like to look it up). Still, try access a local profile of another user unless you have admin rights (or have been granted rights by and admin). Yes, care must be taken while designing applications to ensure security amongst users. Again, this is not unique to Windows (although, I'll admit there are more cowboy developers designing Windows apps that Linux apps!)
Yes IE is universal. Again, try changing any of it without the appropriate credentials. Curious: Do you give users on Linux boxes root access?? Thought not. Stop doing it on Windows!
"ActiveX is a mess:" Nice links. Unfortunately they are all incidentally about ActiveX components. Guess what? buffer over/under runs are not the exclusive domain of activex. ZLIB, for example, is NOT activex and yet shows the same weakness.
I would agree that the time for COM is now passed, but again, the vunerabilities are for individual components, not the concept. Linux and Sun have both had their fair share of buffer over/under run vunerabilities.
Again, all OS have shared components. Don't waste your biases to try to blame this on Windows
by apotheon
by apotheon
by ungle
That was well put.
I've been parroting this all the way through, but we simply must put biases aside and use the best tools for the job.
Interestingly enough, most major corporations do regular cost/benefit analysis before upgrading OS on machines. For example, recently a company I was working with replaced 300 Sun boxes with Linux. The performance was better, the hardware considerably cheaper, and support equally good (Redhat).
At the same time, some services running on Linux were migrated to Windows because...oh, no, here I go...it was cheaper TCO. Go figure! Of course, because of the industry we could not use "free" linux but were required to buy RedHat enterprise servers with support.
However, mission critical financial data (it was a trading company) remained on Sun, so that "...We can sue someone if something goes wrong..." (I kid you not!)
Although I dislike MS licensing, I have worse gripes: IBM. Take a look at licensing on an AS/400. $200,000 for an old DOS box??? (Kidding with that description, before someone attacks me for it!!)
by apotheon
Talk about your useless religious war. You think vi is stupid because of Emacs? Holy crap.
Okay. I prefer vi over Emacs. Yes, I'm in that camp. I'll give you one of the standard holy war responses, since you're clearly in the other camp:
Why would I want Emacs? I already have an OS.
Either vi or Emacs is a more productivity-enhancing application than MS Word could ever be, at least for anything where .doc or .rtf formats aren't necessary. The interface allows the skilled operator to navigate through a document and edit it far more quickly than the point-and-click interface of every Windows app under the sun. Later initial development doesn't necessarily mean better technology. For many uses, vi is far better than anything that runs on Windows (excpeting, of course, Windows ports of vi).
Logging into Linux as root, by the way, doesn't create the same security issues as logging into Windows as administrator. Just logging in doesn't automatically make things start executing. Unlike in Windows, you have to actually choose to execute code in some way for it to execute, and you can't execute some Word macro virus by double-clicking it when it's disguised as an MP3 like you can in Windows. Aside from that, you don't have to log in as root in Linux except to perform very specific administrative tasks, whereas in Windows you have to be logged in with administrator access to do common, everyday stuff, and worse yet you don't have to be logged in as administrator in Windows for many types of malware to successfully escalate privileges so that it can execute with administrative privileges, regardless of what user account you're using. Windows is more full of holes than Alpine Lace cheese.
Lindows doesn't exactly exist any longer. I have no idea whether Linspire (what Lindows became) defaults to having root-only account for the user, but if it does then it's nearly as bad as Windows, and is exempt from much of some of what I've said about improved system security under Linux.
The main Windows release I've used (and still have to use from time to time) is, by choice, Win2k Pro, SP2. This is for a number of reasons, including stability, security, and licensing. I'm forced by circumstance to use WinXP Pro from time to time, and I'm currently involved in a software development project that involves WS2k3 with MS SQL Server. I occasionally have to support clients running Windows 98 or NT 4.0 Workstation. I also have supported a current client of the consultancy that has a Win2k Server system. I also support a number of Windows XP Pro systems as clients on the consultancy's own network. This is all in addition to what Linux systems I support and use, and the seventy-ish Linux servers in the Wikimedia datacenter. So, no, I'm not just talking about Windows 9x or ME.
As for dorky looking billionaires with glasses, you might as well describe me as a dorky looking thousandaire with glasses, and would prefer to be a billionaire (though I tend to wear contacts). Prejudice on that score is not an issue.
by apotheon
"[i]Yes, dear, the kernel, executive, and - to a lesser degree - user spaces do overlap, as they must. And how exactly does this differ from Linux???[/i]"
The statement that they "must" overlap is patently false. Unices maintain strict privilege separation. In fact, simply put, no user has access to anything that doesn't either "belong" to that user or get explicitly assigned permissions that allow that user to access it. In other words, it takes willful implementation of poor security policy to blur those lines, and because of the separation of executive from user and kernel spaces users can execute applications to which they are assigned access without that execution allowing them to compromise files or activate other executables to which they have no assigned access.
"[i]Of course profiles are stored locally - as a COPY of the server stored profile[/i]"
I really don't think jmgarvin was making a big deal about the profile itself, so much as just pointing out that the profile's data is stored locally as well as remotely. His salient point was the fact that no matter what you do with the profile data, the user privileges are the real problem, and user privileges are not as well protected as they should be. They bleed over into each others' user spaces, the executive space, and even the kernel space.
"[i]Yes IE is universal. Again, try changing any of it without the appropriate credentials. Curious: Do you give users on Linux boxes root access?? Thought not. Stop doing it on Windows![/i]"
That's not really the point. Obviously, poor security policy will come back to bite you, but the fact of the matter is that a lot of Windows functionality is designed to short-circuit security privilege separation because much of Windows doesn't work without direct access to executive or even kernel space. This sort of thing allows for very easy unauthorized privilege escalation on Windows systems (yes, even Windows XP, which shows signs of beginning to address user account permissions separation but not much, and doesn't address privilege escalation vulnerabilities provided by the Explorer executable's universality, COM/ActiveX controls, and so on). With a reverse engineer's understanding of Windows system architecture, scripting tools to automate privilege escalation is a (relatively) trivial task. The same is not true of the various unices, where such shortcuts just really don't exist.
"[i]Nice links. Unfortunately they are all incidentally about ActiveX components. Guess what? buffer over/under runs are not the exclusive domain of activex.[/i]"
The problem isn't just that there are buffer overrun exploits for ActiveX and the like. The problem is that ActiveX has vulnerabilities like that [b]and allows remote code execution[/b], and furthermore is necessary for even the most trivial of tasks much of the time such that turning it off neuters the capabilities of the Windows system. Even worse than ActiveX, though, is the ubiquitous and irresponsible use of RPCs internally for interprocess communication [b]within the core Windows platform[/b]. This is the sort of thing that made the Slammer worm possible in the first place, and effectively "shut down the Internet" because of the presence of a couple of Microsoft systems in key points of failure.
by jmgarvin
I've explained the issues and you pop up straw men. I enjoy teaching, but you obviously do not want to learn.
Apotheon said everything very well in the post above mine, so I won't duplicate. However, I will say the problem is that you won't admit to security flaws and that in it self is a security flaw. Please learn to be less bias when dealing with security so that we don't have to deal with crippling malware...
by ungle
Summary:
I like both operating systems, and believe they both have their place. I will continue to do so. I don't believe they need be comapred because they are, IN MY OPINION, suited for a different market space (even though MS would like to topple Linux)
I do not dislike Linux. I do not believe that it is suited, at this stage, to a desktop environment. I think Linux rules the roost in the Internet arena.
I also believe that those who go after Windows are either using it in the wrong place, or are simply enjoying a witch hunt.
Use the right tools for the job. Somtimes that means Windows.
by ungle
The remote code execution was due to the buffer overrun. ActiveX is not NECESSARY for even the most jovian of task.
Sloppy security will come back to bite you regardless of the OS.
As jmgarvin says, I'm tired of dealing with those who do not want to learn.
I enjoy both operating systems, will continue to do so, and fortunately won't allow the OS bigotry of others deter me.
by sudheer_tp
Hi all,
Looking into all of ur arguments, just I wanted to tell something.
All u peoples are talking and enjoying ur job and etc., all becz of ur IT even me.
I was PC support engg, then system admin, then network admin and now I am in database and application admin. I like all the OS. All the OS?s have its own identity and skills.
Just go 20-25 years back may be more, when the common people were not using computers. That time UNIX, Mac OS others are thr in the OS market including MS-Dos.
The computer was costing very high.
Then comes the Windows 3.1 then u all know windows for workgroup, win95, 98 etc.
Just think since a Microsoft window was so user friendly and any non-computer experts can use very easily, started becoming more and more popular. Then more people started using computer and at the same time hardware prices gone down. Now u can get the computer in some hundred $.
Then all techs like u all started thinking and started developing more and more programs and applications. All becz it started only when more and more comman people started using computer. That is becz of Microsoft.
At the same time if MS was not introduced its user-friendly interface OS in that period, then the techs like u and me all would be still 10 year back in technology.
Just for the sake of blaming don?t blame Microsoft. Becz of that now IT is like this, if not it would have taken some more years to come to this level.
by hal 9000
If anyone was actually responsible it was IBM who produced the first Open Architecture Computer platform for the PC. Of course they stitched up a deal with MS for software & an OS which every clone then copied. Even today we still refer to anything that is a PC as an IBM Clone. MS where only there as a side issue and it could have been any number of other players who got into bed with IBM. Of course it was Bill Gates who sold his product hard and cheap to IBM working on the idea of making a little money per unit and that would make him quite a lot of money over all with all the sales of IBM PC's. But he didn't offer the same deals to the White Box makers as IBM had and that was where he really racked in the money.Even at the time IBM accepted that the products that MS had where by no means the best but they cover a wide range so it saved the Powers the Be at IBM needing to negotiate with several of the top line software providers for something that MS could supply at a fraction of the price. This suited both Bill Gates and MS in general until they wanted to make a copy of a Unix Prototype and that was where the marriage soured between the two as IBM wanted to keep the PC on DOS and the real computers on Unix. Their original idea was to have the PC as a "Home" computer where it belonged and never be allowed into a business environment where a Real computer with a decent OS and an already established Security Network Existed. DOS was never intended to be secure and everything that has come since has retained this basic design premise.
MS has not been responsible for driving the prices down at all but the number of units that are now available and the over production is what is responsible.
Really it wasn't all that long ago when we where paying 1 K per MEG of RAM and thinking just how cheap that was now for that amount of money we can not only buy 1 MEG of RAM but a complete computer with several GIG of RAM installed and Windows & Office installed. Of course the MS software accounts for roughly half the buying price of the computer. As prices of the hardware has come down the cost of the software has either remained roughly the same or gone up in price and when compared to the cost of the hardware it has dramatically increased in value.
Col ]:)
by rkuhn040172
Don't you think anything that is heavily automated (by machines say on an assemby line) will eventually come down in price?
Then, you also have those that have mastered the distribution such as Dell.
Software, on the other hand, won't come down as fast but will come down.
With the exception of intregrated IDE's and such, outsourcing with cheaper labor, etc software has less wiggle room.
It still takes highly paid professionals to write code (obviously not all software is written by professionals...side note). But now a $10 teenager can build a PC and in massive quanitites.
by jaqui
both suck!!
both have antiquated ui and app logic.
both seriously need to be rebuilt from the ground up.
( both are capable apps, but they were old when the dinosaurs went extinct )
Crap, do ya suppose we actually "are" getting too old... I remember a time folks could have a conversation about a topic like this without bickering like a bunch of high school kids, but then, that was a long, long, time ago (before foolish bickering became as accepted as windows software.)
But hey, I frequently get ticked off big time.
So what I do before posting or emailing is to actually stop and read my message and ask myself if I am going to get my point accross in a way that limits negative reaction, if it does, I send it. Now, a "real" bickerer does the same thing, but they rewrite it before they send it.
---------------------------------------
~ special note to eyes only bickerers ~
Go ahead. Make my day.
---------------------------------------
by jaqui
which distro did you use?
some are ready for and designed for easy desktop use.
my mom is a different case entirely, when I get stuck I call her, she spent years working in unix shops and knows unix so isn't lost with an *x os.
by m411tech
by jaqui
by mswanberg
Yes, I am actually quite familiar with manpages, but you have, in a few words, doubled my usability with it.
For instance, the "q" command... I was always holding Ctrl and mashing a bunch of keys in the ASDZXC area of the keyboard. Not using Linux stuff every day makes it tough to remember which key combo exits which app. Isn't it like Ctrl-D to get out of the command-line mail app?
Also, the / (slash) thing is awesome. I always used apropos to try and find stuff (Ctrl-Z to get out of that, isn't it?) and I generally found it to be somewhat daunting to wade through the results that come at me.
I am generally encouraged by people like you who seem to make Linux (and other stuff... never heard of that Win2K thing you mentioned) appear to be easy. And yes, I agree that time will equal knowledge.
I hope you can appreciate my frustration in some of the obstacles I've come up against, though. Yes, I sat down and read books about the inner workings of Windows to get more knowledge. But I never can remember reading something in a book and then it not working in practice, which has happened to me on several occasion re: Linux.
As for MythTV, I have it installed on one of my machines. Only after I got through the installation did I find out that it isn't compatible with ATI All-in-Wonder cards. So, now, until I can take some time to mess with that box, it is my 24-hour-a-day weather report. :-)
Sad, yes, but true. Especially considering I can SMS "weather 35244" to 46645 (GOOGL) and get a weather report any time I want. But I like the MythTV weather interface... very slick and cool. I just need to get some time to really play with that machine to get it up and running well.
I used to have that machine singing the TiVo-like song very well. I have a ReplayTV, but Replay doesn't handle conflicts as well as TiVo, so I built this MicroATX machine (the now MythTV box) for about $300. I then wrote a batch script and a few VBScript programs to daily go out to XMLTV and retrieve a feed, and then it interfaces with the Replay and gets all the conflicts, and then schedules those conflicts to record through the All-in-Wonder. Pretty slick. But I don't watch THAT much TV, so mostly the box just sat there. It would record 1 or 2 shows a week.
Then I have a slick system set up on another box that downloads all the shows from the Replay and also takes them from the MicroATX and re-encodes them all in divx for my Archos to be able to play (it's very particular about what it can play). In the morning, I plug in the Archos and I have all of the previous night's TV good to go. Works great for slow days at the office (don't tell my boss).
I would love to someday be that effective on Linux machines. I know there are things that exist in Linux that don't in the Windows world, so I just mainly want to know what my options are so that I can have what I want in the best fashion possible.
-Mike
by apotheon
As you phrased it in that post, ungle, I don't disagree with anything you said. I do end up spending a lot of time here looking like I'm just saying bad things about Windows, though, because I find myself debunking myths and blatant fibs related to how Windows is supposedly better than Linux, or how Linux strengths are somehow only related to things like relative unpopularity, both of which types of arguments are built on foundations of sand at best.
Yes, both OS lines have their places, in terms of functionality. I don't often see instances where Linux cannot do what Windows does, however, even if in some cases it doesn't (yet) do it quite as efficiently, and the difference is generally slight enough that licensing issues usually prompt me to assign preference an order of magnitude greater for Linux than for Windows. Some people don't care so much about licensing: I tend to view that perspective as limited and short-sighted, but there are those who disagree with me. Such is life.
Ultimately, I'm of the opinion that Microsoft's business model and software profit model are injurious to its customer base, to its industry, to the domestic economy, and to the state of affairs of my life in a number of ways. That makes up for a number of minor advantages Windows has over other OSes in generally very limited niches. As such, unless Windows is of critical importance, I avoid implementing it in my own IT operations. Customers, clients, and employers, however, get advice to the absolute best of my ability, and are informed of all consequences of potential decisions, and commonly enough my advice amounts to "Stick with Windows for now. To switch at this time would cost you more than it would save you." More often than not, however, this is the case where the Windows systems are already in place: new systems, where my advice is asked, are usually accompanied by the suggestion that Linux would do the job better.
Usually.
I recommend the best tool for the job. Licensing is part of that. You do the math.
by apotheon
Err, no. The remote code execution is not just because of a buffer overrun. I didn't even read those links: I see reports of ActiveX exploits often enough that I don't need to read a few more right now.
See, without even reading the reports linked above, I can tell you that what the buffer overrun almost certainly allowed was [b]arbitrary[/b] remote code execution. ActiveX was [b]designed[/b] to facilitate remote code execution: that's its purpose. The fact that "arbitrary" is included in this exploit is a result of an accident, rather than the design of COM/ActiveX, but the [b]actual remote code execution functionality[/b] is itself the intent of the ActiveX system. In fact, arbitrary remote code execution with ActiveX is even part of the design, but usually only when one specifically configures the system to allow it, rather than in general.
The idea with many of these buffer overrun exploits is that a data stream is dumped into some ActiveX control, overloading a memory buffer, causing unintended consequences, and producing an opportunity to execute more code. Thus, a non-arbitrary ActiveX execution can be fed a tailored executable or set of execution instructions that take advantage of a buffer overrun vulnerability, which in turn ends up producing an arbitrary remote code execution behavior.
The very fact that ActiveX allows remote code execution in the first place that bypasses user space privilege separation is the major problem of ActiveX. Privilege escalation should [b]never[/b] be an automated process, under any circumstances, but there is so little strict privilege separation in the Windows environment that unintended and automated privilege escalation states are common.
Then, of course, there are those circumstances where privilege escalation are entirely unnecessary to have significant damaging effects on the system, such as with the (mis)use of RPCs that are so ubiquitous that Windows uses it in platform internal APIs. From a security standpoint, that's insanity, absurd beyond kenning.
by apotheon
"[i]Yes, I am actually quite familiar with manpages, but you have, in a few words, doubled my usability with it.[/i]"
Good! Glad to be of service.
"[i]I was always holding Ctrl and mashing a bunch of keys in the ASDZXC area of the keyboard. Not using Linux stuff every day makes it tough to remember which key combo exits which app. Isn't it like Ctrl-D to get out of the command-line mail app?[/i]"
On Linux, Ctrl-Z suspends a program and Ctrl-C exits it. As for Ctrl-D exiting a command-line email application, I don't know. I use mutt (a command-line email application), but its exit key is Q as well. There probably is some common CLI email application that uses Ctrl-[foo] to exit it, but off the top of my head I don't know what it would be or if D is the key it uses.
If you're using something like apropros, apt-cache search, ls, or anything else that potentially gives you a LOT more stuff than you need, you can narrow down your results significantly with something like grep. For instance, if you're looking for a package relating to both GTK+ and images in the Debian apt archives, you might use the command string "apt-cache search gtk |grep image". The vertical bar character "|" is called a "pipe" (in case you're not familiar with this), and is used to send (to "pipe") a command through another command. The output of the first command is sent to the second command, and only the output of the second command is sent to STDOUT (the command line, generally: STDOUT is the env. variable for "standard output"). There are other tips and tricks out there for narrowing down output to relevant stuff, but I find grep at the shell and / within certain applications to be the most commonly useful. You should be able to use grep in conjunction with apropos to help you get usefully narrowed search results and, if you get enough stuff so that it scrolls off the top of the screen and don't have the ability to scroll back, you can always pipe the command output through less to give you the ability to scroll using arrow keys or page up and down using Ctrl-D and Ctrl-U.
"[i]never heard of that Win2K thing you mentioned[/i]"
Yeah, not many have. It's pretty rare, and is something I just found one day while working in the registry looking for something else that I needed to alter to fix a registry corruption. Not many people want the desktop turned off, anyway. Among other features that disappear when the desktop application is entirely disabled is the ability to place icons on the visible desktop for double-clicking to open the referenced applications. I prefer to use custom menus from the taskbar rather than desktop icons, though, so it was very much worthwhile to deactivate the desktop on my own system.
"[i]I hope you can appreciate my frustration in some of the obstacles I've come up against, though.[/i]"
Yes, I can understand and appreciate that. It's a reaction to the steeper initial learning curve for the behind-the-scenes uses of unixy systems, essentially.
As for your frustrations with books having what appears to be inaccurate information, to understand that you have to understand what's going on when someone writes one of these books. First of all, the people who write the books are often people who have extensive experience using the systems in question but don't necessarily know why those systems behaved the way they did. The underlying principles are what need to be taught to new arrivals, not the laundry-list set of brainless steps to take, not only because the laundry-list approach doesn't teach you to sort out how to do new things without a book, but also because the laundry-list changes between versions or even sub-versions sometimes, while the principles remain constant. Red Hat books are particularly subject to this sort of issue, as Red Hat considers itself sorta above the Linux Standard Base, and likes to do things its own way, which is often different from its own way six months ago. This can lead to some confusion from time to time: it took me an hour or so to figure out that, for some odd reason, NIC configuration files in Fedora Core 3 are in a scripts directory separate from the remainder of the networking configuration files. After extensive use of Fedora/RH, the Fedora/RH way of doing things starts to make a certain kind of internally consistent sense, but it's quite confusing at first. Also, of course, there's the simple fact that you were probably reading second and third editions of books, where stuff gets updated to deal with newer versions but sometimes not everything is updated. The same thing occurs often enough with Windows-related books too, as long as they don't come from Microsoft Press.
"[i]As for MythTV, I have it installed on one of my machines. Only after I got through the installation did I find out that it isn't compatible with ATI All-in-Wonder cards. So, now, until I can take some time to mess with that box, it is my 24-hour-a-day weather report.[/i]"
Hah. Sorry to hear it.
There are ways to get it running with All-in-Wonder cards, but I don't really know what they are, so I'm afraid you're kinda on your own there. A good LUG mailing list is worth its weight in gold for stuff like this.
Don't feel limited by location if all you need is email support, though. Join a LUG mailing list for a good LUG external to your area, if need be. I'm actually on a list for an Illinois area LUG, despite the fact I've never lived there and have never driven through the part of the state where that particular LUG is located. I'm also on three other LUG lists more local to me, but the Illinois list is a pretty good indication of the fact that value can be had from a LUG without being located anywhere near it.
"[i]I then wrote a batch script and a few VBScript programs[/i]"
Man, you really need to learn Perl. It's one of the easiest-to-learn high-power languages out there, and it's pretty much custom designed to do the sorts of things you're doing with batch and VBS scripts. If you get familiar with it, I'm pretty sure you'll fall in love with the succinctness of the language and the extremely powerful regex capability of it. In fact, Perl is sorta THE language to learn for any unix sysadmin. Perl's initial purpose was text- and file-processing, and since everything in a unix system (including processor resources, binary executables, and even device drivers) is a "file" to the filesystem and can be treated as text, Perl is likely the most powerful system administration language you'll ever come across when used on a unixy system such as Linux.
Perl is available on Windows, too, and I'm of the opinion that it's the best scripting language for the Windows platform in general (though not in some specific uses), but ActivePerl (Perl for Windows) pales in comparison with Perl's power within a unix environment.
by apotheon
You say that software won't come down in cost as fast, but will come down.
It has already dropped as far as it can go. You can have some of the best software in the world for free, right now. This is the consequence of the open source development model. I, for one, love that.
by crossleyc
by hal 9000
They do have the bulk of office desktops but there are still numerous sections of the market where any Windows system will just not fit. Anything that involves vast amounts of number crunching to achieve the desired output will not in the foreseeable future be running Windows just as the same applies that the Data input side of the industry will retain Windows as the OS of choice.
The people who think that MS owns the desktop have just fallen for the marketing hype that MS pushes so hard. Just as one example all the high end Graphic rendering places do not have Windows on their workstations only in the accounting sections where the operators are not highly trained.
Similarly in a even small Blade Array with a few hundred CPU's can you imagine just what the costs of Deploying Windows Server products would be? Even if it was scalable enough to actually perform the job!
Just grab a copy of MS's financial reports to the Stock Exchange and you'll find that they are listing Linux as a growing threat to their income and they have to do this by Law. If you grab a copy of the last few years reports you'll see a growing impact on the income of MS which I can not see being turned around in the short term as MS just doesn't have a product to compete in this part of the industry.
Col ]:)
by hal 9000
Would have being paying to do the same thing as then it was "Cool" and they could build the same hardware in the same numbers but the price was still much higher.
Do you remember when the first CDR became available we where paying $25.00 AU per disk and thinking just how cheap that was to have 700 MEG of storage space. Now the same thing only costs a few cents and these where never US made they where all made in Third World countries but at the time they could charge a premium as the supplies where not great enough. Just lick Flat Screen monitors a few years ago they where horrendously expensive but with the current over supply the price has had to come down so they still sell.
Now the main reason that the cost of Hardware has dropped so significantly is the amount being made. So it is cheaper by virtue of volume.
Software on the other hand isn't cheaper it is about the same price but it still costs the same to actually write and they are selling millions of copies instead of a few hundred thousand that where being sold previously.
As an example the old Space Invaders Chip that was used in the Arcade Games was several K each because they had to defray development costs against the expected number that would be sold. Then the PC market exploded and they no longer had to use a dedicated chip but could release the software as code and load it onto the then computers but even the very first Space Invaders modules as used by things like the Vic was only a few $ in comparison to what they used to be the same applies to the Z80 CPU, do you remember just how much one of those used to cost?
Anyway even today there are numerous applications that are so cheap as not to be funny this is quite common with games for the home user. They can start off at extremely high prices and then drop to under $20.00 AU while they are still the current production unit. Now if this can happen with one piece of software like this which only has one unit per computer just like just about all Business Software why is it that the price of the software isn't decreasing with the increase of sales of the product?
Now realistically MS can not expect us to believe that they factor in the cost for development of their software and the development costs are so great as to make it necessary to keep the price stable like it constantly is being kept.
Just how do they justify this? The costs involved in prototyping a CPU and then making the masks for it for production are very high but even still we are seeing the CPU prices constantly dropping as well as the RAM prices which use the same technology to produce and there are ongoing costs in making hardware where as software other than the occasional Patch and Service Pack can remain the same for long periods of time without change to what is sold over the counter. Also with Hardware you own it but with Software all you are actually doing is buying the right to use it and you don't even actually own the CD/DVD that it comes on.
Col ]:)
by apotheon
Software development cost is even further being called into question, now that people are starting to notice that things like Linux, Apache, the X Window System, and so on are available free of charge and have been available thusly for twenty years in some cases, and they're still being developed. New such projects are starting all the time, and you can still get them free of charge.
What's the major malfunction at Microsoft? Why does a new release of Windows cost $350 when the equivalent in Linux can be downloaded and burned to CD for the cost of the electricity and the CD?
by sean ross
True. Microsoft has it's shortcomings.
But if their products did not sell we would not be having this discussion. So my answer is economic success. Real or imagined. :)
I have used most operating systems created since 1982. Most worked well for their given purpose at the time. And had no problem with most of them.
P.s. The bashing I have generally heard is from either close mined folks. Or Li/U/nix sys admins. Sometimes, they are even one in the same.
by jmgarvin
How do you explain market leaders like Apache not getting bashed?
MS has issues with security and stability that have yet to be fixed. Most admins also find it to be lacking in the capacity of a server...so, MS gets bashed because they market as a pancia, but in reality it only fits in certain places.
by erekose mcne
by rjdrjd
by hagrinas
If an operating system crashes, or if any program crashes for that matter, it is NEVER the fault of the user. That's just plain bad programming. Good programming means that you account for what a user might do wrong as well as what a user might do right.
A good operating system should never crash under any circumstances. In the early days of Windows when it was typical for many users to experience crashes daily, the mean time between failures for more robust operating systems such as mainframes was once in 14 YEARS. Since then, mainframes have gotten much more reliable, and Windows is still poor.
A few decades ago, I instituted a policy at work requiring all software that my staff wrote to have a standard error routine. It captured critical data, including the values of each variable, and where the program was when things blew up. It looked up the relevant developer in the database and emailed this information to him/her automatically. If the contact was not on file, it sent it to a general email address (mine) so somebody would fix things.
I found that most of the time, when something blew up, the user would not bother to report it. I also found that if the problem came after the user did something wrong, the user was even less likely to call.
There were times that I notified users that the problem that they encountered was fixed, and they replied that it was their fault because they did something wrong. I told them that if the program blew up, it was something the programmer did wrong; it should have given them an appropriate error message.
If a user has an incorrect driver, the OS should give the user an error message, not blow up. If Microsoft could not figure out how to do that, then they deserve every bit of bashing they get.
An exception to this is required maintenance. If Microsoft fixed something in the OS itself, and the user did not keep current on fixes to the OS itself, then it's the fault of the computer's administrator. That might be the end user, or it might be his MIS group. But that's different from falling behind on third party software maintenance. It's acceptable for applications to blow up (assuming the OS did not cause it) as long as the OS does not go down with them. That's from the OS point of view of course. From the application's point of view, there's no excuse for buggy software.
It used to be that support existed for the sole purpose of fixing bugs. If you bought or licensed software, it was understood that it was supposed to work as documented. If something went wrong, it was up to the vendor to fix things, not wait for the next release, and then fix it only if they feel like it. Software support was not there to tell users how to use the software. That's what the manuals and training classes were for. With the advent of the PC, quality went out the window, support became something for people who could not be bothered to read instructions, and companies often won't even take error reports from users.
And that's especially true of Microsoft. They release "beta" versions of things without giving the end user any way to contact the developers. The whole purpose of beta is supposed to be so that any bugs can be fixed. But if they tell you that "it's not supported since it's beta, so you can't complain to us," then that defeats the whole purpose of even testing.
Sort by Trending