The cute-looking Tux had a problem. Everyone thought Tux disliked Windows and

therefore wouldn't talk with anything that had 'Win' in it. This thought spread

around quite a bit, and therefore most Windows users would have no truck with

tux.

But getting Windows to recognise a Linux machine or for that matter getting

Linux to recognise Windows-based computers in a network is as simple as configuring

PPP (Point to Point Protocol) is used to connect the Red hat Linux system to

the ISP through the modem. PPP is faster and more efficient. It uses the TCP/IP

network protocol. SLIP(Serial Line Interface Protocol) is also used as the replacement

but it is not as successful as PPP. Most of the ISP's prefer PPP.

Note that I've written most of this document from memory. It appears to be

correct; if I've missed something or if you have any questions or comments,

feel free to

href="mailto:rjmooney@aboveground.cx">drop me a note

Described Network

Here's my network setup:

Time was when after writing their own device driver program, boys fancied they

had grown up into men. Till Linus Torvalds came along and made them feel rather

puny. Torvalds set out to write an entire kernel and the results, if one were

to go by the cult following Linux still commands, were quite spectacular!

So what's a kernel? Here's how the Linux Kernel How-To describes it:

When running a local area network, one of the goals is usually to provide an environment to the users that make the network transparent. An important step for this is to keep vital data such as user account information (e.g. /etc/hosts, /etc/passwd and /etc/group files) synchronized between all hosts. For host name resolution, a powerful and sophisticated service - DNS exists. For other tasks, there is no such specialized service. Moreover, if you manage only a small closed intranet without Internet connectivity, setting up DNS may not seem worth the trouble for many administrators.

Customizable error response

Customizable error response, the Apache style, comes in three flavors:

1) Plain text

ErrorDocument 500 "The server made a boo boo.

Note: The (") marks it as text, it does not get output.

2) Local redirects

ErrorDocument 404 /missing.html to redirect to local URL /missing.html

ErrorDocument 404 /cgi-bin/missing_handler.pl

Note: You can redirect to a script or a document using server-side-includes.

Dynamic Shared Object (DSO) Support

To be able to use the functionality of a module which was built as a DSO you have to place corresponding 'LoadModule' lines at this location so the directives contained in it are actually available before they are used. Please read the file README.DSO in the Apache 1.3 distribution for more details about the DSO mechanism and run 'httpd -l' for the list of already built-in (statically linked and thus always available) modules in your httpd binary.

Basically for communication where there is a client-server flavor, the server process creates a socket and the client socket accesses the server through client socket techniques.

Socket

A socket is fundamentally nothing but an end point of communication. It can be of two types: Physical socket and Logical socket. In Logical socket operating system has its system calls, which creates them. Now for client-server access the socket needs three things to provide service or ask for service.

1) Service name (example: telnet)

2) Protocol (TCP-stream)

This article is basically written for Rsync, a very fast, flexible and robust backup utility. We will look at how you can utilize and configure this program to take the daily backup from your production servers.

What is Rsync?

So now that you have installed FreeBSD, what do you do next? Well there are lots of things you can configure. Here, we bring you an article that focuses on various aspects like environment, shells, etc, which need configuration. This should set the ball rolling.