>>I prefer to use UNIX:
>>1. because it allowes me to automate my day-to-day tasks easily, and
>> with little or no additional payment;
>>2. It gives me smooth and transparent remote access method;
>>3. It is robust enough to stay up heavily loaded for months and months
>> (latest experience: 112 days up for RS6000 running 3 Oracle- and
>> apps simultaneiously, AND DNS for at least 3000 computers.
>>eventually it went down after
>> long-time out-of-memory condition);
>>4. It has lots of very robust RDBMS, including those for free;
>>5. It has lots of free applications which really help to get work done;
>>6. And I prefer Linux, because among all this it has VERY LOV COST,
>> big amount of supported software, and lots of cheap personal
>>I think, guys, this is the way to advocate Linux, not bashing NT and 95.
>>It's getting boring!
>Agreed. M$ stuff doesn't even try to fill the same niche
>as *nix systems. *nix are multitasking AND multiuser!
>>Who can add something to the list I offered above?
>Number 7 is _Linux_ related, not necessarily UNIX.
>7. Because the source code is available, we can make changes to
>fit OUR needs much easier than MS can fill their customers. For
> a) I came across a new ne2000 pci clone that most drivers
> wouldn't recognize AS an ne2000. In the Linux kernel I
> modified the ne2000 code so that it DID accept this card
> as ne2000. (Actually I just had to add ID numbers to a
> few arrays)
> b) When trying to install Linux on a Thinkpad which needed
> special parameters for the floppy, I was able to compile
> a special kernel with those parameters set so that it
> could be done with a single boot/root floppy without a
> need to prompt users for the parameters.
c) I decided that I _really_ didn't want to start our web
server as root, but I _really_ wanted it to listen
at port 80. Took a whole 15 minutes to find the
socket code that enforces this restriction and
comment it out. I'm sure I'm a bad person for doing
this but it makes my life easier.
Quote:>8. Remote administration is a snap. Virtually anything which
>can be done at the console can be done from thousands of miles
>away. This includes even changing the kernel, rebooting, etc.
Yuppers, 100%. We have a whole bunch of _completly_ headless (i.e. no
display, no keyboard) machines. Nothing like testing out new drivers
on a headless machine! Makes you a _very_ careful coder. Relink, cp,
/sbin/lilo, /sbin/reboot, and wait and see what happens. If you*
up you get to pop the covers and shove in the one shared video card and
debug. So I tend to try _very_ hard not to make mistakes.