06-07-2011
Unix was designed as a multi-user, multi-tasking operating system. Windows, initially, was not really designed for this.. and still carries some poor design choices even after recognizing the need for handling multiple users and tasks. Windows attempt at handling multiple users was to create the idea of required client OS installations in addition to what they called a server OS installation. And this is still their primary model for handling multiple users. With Unix, there doesn't have to be any distinction of client vs. server, which is useful when you consider the cost of Windows CALs.
Because Unix systems are simply general purpose multi-user, multi-tasking entities, Unix can be made into pretty much anything (there isn't a hard paradigm that is difficult to thwart with Unix... the whole client/server model of Windows can be VERY limiting).
Unix tends to focus on the idea of processes and files as the core. Windows core consists of a set of API's that cover many very specific areas. The flexibility of Unix is in the elegant simplicity of its model. True, you can make a very insecure Unix platform, but unlike Windows, you can also make a very secure platform as well. The Windows core consists of legacy APIs, redundant APIs, deprecated APIs and the ever growing set of new APIs... and since it's an API driven model, there are lots of security issues... arguably, it's not fixable.
There are even more elegant solutions out there than Unix... but just the few good design choices made early on have allowed Unix (and even Linux) to stand the test of time.
Unix can be used to make small footprint appliances (e.g. even mobile phone devices... many of which are Linux based). Windows required a whole DIFFERENT OS and API stack to support small footprint appliances, and indeed, even so, there are many choices even in that space (WinCE, Windows Mobile, etc.)... all different, all unique... and it multiplies the security issues that have to be taken into account.
Unix, simple design, flexible OS, a gazillion possibilities.
Windows, complex design, insecure and risky, limited possibilities (by design).
Just my two cents... I specialize in Unix/Linux + Windows integration...
This User Gave Thanks to cjcox For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I recently joined this forum and new to UNIX.
Is there any difference between UNIX operating system and UNIX open server? Please explain. (1 Reply)
Discussion started by: Manjit
1 Replies
2. UNIX for Dummies Questions & Answers
My situation is that we have production unix scripts that ftp files over to a windows server. I'm not sure if its a 2000 or 2003 server as I dont work on server, more on the unix side. It turns out that they are changing servers on the network. So they are migrating our data over from say Server 1... (1 Reply)
Discussion started by: NycUnxer
1 Replies
3. AIX
Hi Friends,
I have this script for ftping files from AIX server to local windows xp.
#!/bin/sh
HOST='localsystem.net'
USER='myid_onlocal'
PASSWD='mypwd_onlocal'
FILE='file.txt' ##This is a file on server(AIX)
ftp -n $HOST <<END_SCRIPT
quote USER $USER
quote PASS $PASSWD
put $FILE... (1 Reply)
Discussion started by: rajsharma
1 Replies
4. Shell Programming and Scripting
Hi,
I have perl script abc.pl which runs perfectly fine on windows ( execution from cmd).
Now i tried to execute the same perl module on the AIX server after defining the captureoutput.pm and other relevant changes.
But its behaving very weirdly as a portion of the URL which is formed by... (3 Replies)
Discussion started by: slayer0611
3 Replies
5. Shell Programming and Scripting
Can anybody please help me on how to code for the below requirement:
I need to write a shell script (on different unix server) to copy files from multiple folders (ex. BRN-000001) from one windows server (\\boldls-mwe-dev4)to a different windows server(\\rrwin-ewhd04.ecomad.int). This shell... (4 Replies)
Discussion started by: SravsJaya
4 Replies
6. What is on Your Mind?
Hi..
What is the difference between linux and windows? (2 Replies)
Discussion started by: billcrosby
2 Replies
7. Linux
Hi,
What is the difference between Linux and Windows?
Thanks. (1 Reply)
Discussion started by: billcrosby
1 Replies
8. Linux
Hi,
What is the difference between Linux and Windows?
Thanks. (5 Replies)
Discussion started by: billcrosby
5 Replies
9. Shell Programming and Scripting
hi guys,
i need a script to sftp the file from windows to unix server ....(before that i have to check whether the file exists in the windows server or not
and again i have to reverse sftp the files from unix to windows server.....
regards,
Vasa Saikumar. (13 Replies)
Discussion started by: hemanthsaikumar
13 Replies
10. UNIX for Beginners Questions & Answers
I have heard that UNIX disk storage is costlier than Windows Disk storage. Is that true? If not why we have limited storage on UNIX systems? Windows disk storage is so cheap nowadays. Is it not true for UNIX disks? (8 Replies)
Discussion started by: Soham
8 Replies
LEARN ABOUT XFREE86
ddi_dma_numwin
ddi_dma_numwin(9F) Kernel Functions for Drivers ddi_dma_numwin(9F)
NAME
ddi_dma_numwin - retrieve number of DMA windows
SYNOPSIS
#include <sys/ddi.h>
#include <sys/sunddi.h>
int ddi_dma_numwin(ddi_dma_handle_t handle, uint_t *nwinp);
PARAMETERS
handle The DMA handle previously allocated by a call to ddi_dma_alloc_handle(9F).
nwinp Upon a successful return, nwinp will contain the number of DMA windows for this object.
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI).
DESCRIPTION
ddi_dma_numwin() returns the number of DMA windows for a DMA object if partial resource allocation was permitted.
RETURN VALUES
ddi_dma_numwin() returns:
DDI_SUCCESS Successfully filled in the number of DMA windows.
DDI_FAILURE DMA windows are not activated.
CONTEXT
ddi_dma_numwin() can be called from user, kernel, or interrupt context.
SEE ALSO
ddi_dma_addr_bind_handle(9F), ddi_dma_alloc_handle(9F), ddi_dma_buf_bind_handle(9F), ddi_dma_unbind_handle(9F)
Writing Device Drivers
SunOS 5.10 29 Sep 1994 ddi_dma_numwin(9F)