Re: [tlug] FreeBSD.....Linux what's the difference

[Matt Doughty <mdoughty@example.com>]

> 
> Linux seems to do better on iffy hardware.  Probably (hopefully?) not an 
> issue on a server, especially a mission critical one, but for example, on a 
> dying hard drive, Linux and MS would still install but FreeBSD would fail 
> to install. (I'm only experienced with FreeBSD, so when I say BSD, please 
> realize that's what I mean)

This would be a 'good thing'(tm). I don't want to install an OS on a HD that
is later going fail and take my data with it. So chalk up a point for *BSD.
> 
> KVM switches--which might be an issue--BSD doesn't deal with them well if 
> you have to run X for any reason.  The mouse won't work, if you have to do 
> any point and wimp stuff (he says, writing in Windows--hey, I spent the 
> last few days on distro installing binges.)  :)  One has to start the 
> machine while the KVM is focused upon it and then start X for the mouse to 
> work--once that's done, you can usually switch away and back without problem.
> ASUS motherboards and X--the Problem Report was just closed two days ago. 
> If this is an issue, and for some reason, you have to do something with X 
> before upgrading to current stable (heh, how's that for an 
> oxymoron--meaning, of course, the present day stable) you have to edit 
> /usr/src/sys/i386/i386/i686_mem.c  (If this is an issue let me know, and 
> I'll give you the particulars.)  However, the problem is fixed--did a cvsup 
> and build and install world, and it's now working.

I have had more KVM issues with linux actually so YMMV. As for hardware
specific quirks all of the OSes have them it is centainly true that you
will have wider support for linux OTOH NetBSD has considerably better
USB support.  The reality is that with any of the *nixes you need to 
check and make sure your hardware is supported before you buy.
> 
> Much of this may not be an issue on a server, but might be if you're 
> playing with it at home before putting it on the server.  Also, if playing 
> with it at home first, be sure that, if using IDE, that you have shielded 
> 80 pin ATA100 (at least) IDE cable or you'll get a bunch of errors on boot 
> (though it will work without problem)
> 

But the question is whether that is because of a problem in the BSD driver
or are the linux/windows drivers either not seeing or just ignoring the
errors? If the drive works fine anyway then there certainly is no idication
that the BSD driver is functionally inferior. It might just be either more
informative or more thourough in its testing.

--Matt