03-15-2007
Windows is a collection of OS's and you can't really lump them together. XP has the NTFS filesystem which has rather powerful file permission capabilities. You can use a FAT filesystem with XP but Microsoft recommends ntfs. In my mind the glaring difference between Windows/Unix is that Unix is multi-user. Diff number 2 would be the XP GUI shell (explorer). Internally, unix has a monolithic kernel while XP has a microkernel (more or less). (Linux is also monolithic and this was the subject of a flamewar between Tovalds and Tennenbaum. Please remember our rules and do not start a flame war here. The thread will be quickly closed should that happen.) And a final large difference is the windows registry concept.
Your diagram does not strike me as correct. The shell should be a layer unto itself.
Swapping is moving entire processes into core or back to the swap area. At first Unix could swap but had no paging. After CPU's had MMU's paging became possible. Now unix pages all the the time and rarely swaps as a last resort. Some OS's (and I am thinking of HP-UX in particular) no longer swap at all. This leaves that swap area with a poor name! (Encrypted passwords have been removed from the password file too. Users rarely have home directories in /usr anymore. Unix has evolved a lot...)
8 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
Chapters on Linux and Unix:
http://www.prenhall.com/divisions/esm/app/author_tanenbaum/custom/mos2e/
Slides, figures, code, lots of goodies on-line!
CHAPTER 10 CASE STUDY 1: UNIX AND LINUX 671
10.1. HISTORY OF UNIX 672
10.1.1. UNICS 672
... (1 Reply)
Discussion started by: Neo
1 Replies
2. Filesystems, Disks and Memory
We are currently running two servers each with remote file systems mounted on each other. They need upgrading from Solaris 2.6 to 8.
Does anyone know if there is a problem with having one server running Solaris 2.6 and the other v8?? Until we have time to upgrade them both. (2 Replies)
Discussion started by: hesmas
2 Replies
3. UNIX for Advanced & Expert Users
I am interested in hearing anyones opinions on what OS they would choose to run a MySQl db and the reasons why, of course. I have a task to build a db server for a project that will be very busy if things work as the creative minds think that it will. I am running a FreeBSD box right now on... (0 Replies)
Discussion started by: smtpgeek
0 Replies
4. UNIX for Advanced & Expert Users
Dear administrators I want to post the following question and, honestly, I don't know in which forum to post it since its general meaning.
my question is: Where the operating system are going?
Microkernel, monolithich or hybrid ?
Because this question involves more forums at the same but... (2 Replies)
Discussion started by: Puntino
2 Replies
5. UNIX for Dummies Questions & Answers
Hi :)
I have unix Operating Systems 5
I need working for user logout befor 10 minutes,In the
case that he is not active :o
what do I do? :rolleyes: (4 Replies)
Discussion started by: fakhwork
4 Replies
6. Fedora
Hello. I own a MacBook (black) running Leopard (Mac OS X 10.5.8), and I'm curious about a few things -- any help will be very, very much appreciated. I'm pretty much a newbie to Unix, although I have some very basic command-line skills with Mac OS X's Terminal. So while I know how to work the... (13 Replies)
Discussion started by: Tron55555
13 Replies
7. Programming
The assembly code generated by assembler, from a C-source code depends on the CPU architecture underlying it, eg x-86 . Then does the assembler output of a simple C-source code (containing common function-calls of both windows and linux) differ between Operating Systems ? (1 Reply)
Discussion started by: vishwamitra
1 Replies
8. Google Chrome OS
we have
windows
linux- redhat ubuntu -or more i don't know
unix- solares
snow-lepord
and recently chrome
what do you think
well when i sow that all has extentions like exe -dsb i felt scared (1 Reply)
Discussion started by: Anna Hussie
1 Replies
LEARN ABOUT DEBIAN
xpamethod
xpamethod(7) SAORD Documentation xpamethod(7)
NAME
XPAMethod - XPA Communication Methods
SYNOPSIS
XPA supports both inet and unix (local) socket communication.
DESCRIPTION
XPA uses sockets for communication between processes. It supports three methods of socket communication: inet, localhost, and unix. In gen-
eral, the same method should be employed for all XPA processes in a session and the global environment variable XPA_METHOD should be used
to set up the desired method. By default, the preferred method is "inet", which is appropriate for most users. You can set up a different
method by typing something like:
setenv XPA_METHOD local # unix csh
XPA_METHOD=local; export XPA_METHOD # unix sh, bash, windows/cygwin
set XPA_METHOD=localhost # dos/windows
The options for XPA_METHOD are: inet, unix (or local), and localhost. On Unix machines, this environment setup command can be placed in
your shell init file (.cshrc, .profile, .bashrc, etc.) On Windows platforms, it can be placed in your AUTOEXEC.BAT file (I think!).
By default, inet sockets are used by XPA. These are the standard Internet sockets that are used by programs such as Netscape, ftp. etc.
Inet sockets utilize the IP address of the given machine and a (usually random) port number to communicate between processes on the same
machine or between different machines on the Internet. (Note that XPA has an Access Control mechanism to prevent unauthorized access of XPA
access points by other computers on the Net). For users connected to the Internet, this usually is the appropriate communication method.
For more information about setting up XPA communication between machines, see Communication Between Machines.
In you are using XPA on a machine without an Internet connection, then inet sockets are not appropriate. In fact, an XPA process often will
hang for many seconds while waiting for a response from the Domain Name Service (DNS) when using inet sockets. Instead of inet sockets,
users on Unix platforms can also use unix sockets (also known as local sockets). These sockets are based on the local file system and do
not make use of the DNS. They generally are considered to be faster than inet sockets, but they are not implemented under Windows. Use
local sockets as a first resort if you are on a Unix machine that is not connected to the Internet.
Users not connected to the Internet also can use localhost sockets. These are also inet-type sockets but the IP address used for the local
machine is the localhost address, 0x7F000001, instead of the real IP of the machine. Depending on how sockets are set up for a given plat-
form, communication with the DNS usually is not required in this case (though of course, XPA cannot interact with other machines). The
localhost method will generally work on both Unix and Windows platforms, but whether the DNS is required or not is subject to individual
configurations.
A final warning/reminder: if your XPA-enabled server hangs at startup time and your XPA_METHOD is inet, the problem probably is related to
an incorrect Internet configuration. This can be confirmed by using the unix method or (usually) the localhost method. You can use these
alternate methods if other hosts do not need access to the XPA server.
SEE ALSO
See xpa(7) for a list of XPA help pages
version 2.1.14 June 7, 2012 xpamethod(7)