Wednesday, June 26, 2013

A Tutorial Introduction to GNU Emacs

A Tutorial Introduction to GNU Emacs

Introduction and History

 

GNU Emacs is a free, portable, extensible text editor. That it is free means specifically that the source code is freely copyable and redistributable. That it is portable means that it runs on many machines under many different operating systems, so that you can probably count on being able to use the same editor no matter what machine you're using. That it is extensible means that you can not only customize all aspects of its usage (from key bindings through fonts, colors, windows, mousage and menus), but you can program Emacs to do entirely new things that its designers never thought of.
Because of all this, Emacs is an extremely successful program, and does more for you than any other editor. It's particularly good for programmers. If you use a common programming language, Emacs probably provides a mode that makes it especially easy to edit code in that language, providing context sensitive indentation and layout. It also probably allows you to compile your programs inside Emacs, with links from error messages to source code; debug your programs inside Emacs, with links to the source; interact directly with the language interpretor (where appropriate); manage change logs; jump directly to a location in the source by symbol (function or variable name); and interact with your revision control system.

CLICK HERE

Tuesday, June 25, 2013

XEmacs Tutorial Introduction

XEmacs Tutorial Introduction

Sarah Waterson

 You should be reading this document using a browser such as Netscape. In addition, you will be running XEmacs so that you can try out the commands given here. Don't worry! If you don't know how to start XEmacs yet, you will soon. It is very important that you follow the instructions closely and accurately. READ EVERYTHING! Occasionally you will be asked to type some Unix commands in an xterm window, so you should make sure that you have an xterm window open as well. 

 

CLICK HERE

Friday, June 21, 2013

Guide to Writing SE Linux Policy

Guide to Writing SE Linux Policy

Faye Coker

This document continues on from the Getting Started with SE Linux HOWTO, and covers writing SE Linux policy as well as discussing configuration files you will be dealing with. It is aimed at people starting out with writing their own SE Linux policies. If you have not already done so, please read the Getting Started with SE Linux HOWTO in order to become familiar with basic concepts. Any mention of "old SE Linux" refers to the original release of SE Linux for 2.4.x kernels. "New SE Linux" refers to SE Linux for 2.6.x kernels for which a backport is available for 2.4.
Please make sure you also read the NSA's document called Configuring the SE Linux Policy as material in this HOWTO refers to its contents.
This HOWTO tries to be as basic as possible. With learning how to write SE Linux policy, it's mostly a matter of just getting in there and doing it, as many things are not documented at this time. Keep practising, look at existing policies, study the kernel log messages. A lot of what you try might be guesswork which is perfectly okay, because things will gradually fall in to place.
This document has been tested on a test system but more guinea pigs are always welcome.

CLICK HERE
 

Secure Programming for Linux and Unix HOWTO

Secure Programming for Linux and Unix HOWTO

David A. Wheeler

This book provides a set of design and implementation guidelines for writing secure programs for Linux and Unix systems. Such programs include application programs used as viewers of remote data, web applications (including CGI scripts), network servers, and setuid/setgid programs. Specific guidelines for C, C++, Java, Perl, PHP, Python, Tcl, and Ada95 are included.

 

CLICK HERE

Securing and Hardening Red Hat Linux Production Systems

Securing and Hardening Red Hat Linux Production Systems

A Practical Guide to Basic Linux Security in Production Enterprise Environments

Written by Werner Puschitz
 
This Linux Security HOWTO is intended for a technical audience, Linux system administrators, and security people in corporations and organizations that have to use commercial Linux distributions for their production environment. If you are a Linux expert then you may find familiar material here, but you will have difficulties to find documentation on various topics like restricting su access to system and shared accounts only as covered in this article, see Restricting su Access to System and Shared Accounts.
If you need to make Linux production systems compliant with various audit requirements, then this article should offer a good baseline and starting point. The main objective of this Linux Security guide is to discuss basic Linux security requirements including account policies for production systems that are being audited. This document covers various system services like SSH which are usually enabled and required on all Linux production servers. But it does not cover services or applications like Apache, Samba etc., since these applications/services are usually not needed across all Linux servers and should therefore not be installed on all systems. In fact, these applications warrant their own security HOWTO. Also, this article does not cover security features that require kernel patching. This is not an option for most companies due to vendor support issues. 
 
CLICK HERE

Linux Security Administrator's Guide

Linux Security Administrator's Guide

Dave Wreski

 This document is a general overview of security issues that face the administrator of Linux systems. It covers general security philosophy and a number of specific examples of how to better secure your Linux system from intruders. Also included are pointers to security related material and programs.






CLICK HERE

Linux Packet Filtering and iptables

Linux Packet Filtering and iptables

Oskar Andreasson

 

 

Why this document was written

Well, I found a big empty space in the HOWTO's out there lacking in information about the iptables and Netfilter functions in the new Linux 2.4.x kernels. Among other things, I'm going to try to answer questions that some might have about the new possibilities like state matching. Most of this will be illustrated with an example rc.firewall.txt file that you can use in your /etc/rc.d/ scripts. Yes, this file was originally based upon the masquerading HOWTO for those of you who recognize it.

CLICK HERE

Table of Contents - Linux Security for Beginners

Table of Contents - Linux Security for Beginners

There is a saying in the security world that the only truly safe computer system is one that is disconnected from the network, switched off and buried six feet under ground. The sentiment may be somewhat true but it is hardly a practical solution to the problems we face today in protecting servers and desktops from outside intrusion.
There are more computer systems connected to the internet either directly or via local area networks than at any time in the history of technology and the numbers are growing at a rapid rate. It seems that not a month goes by without another story in the news about the internal network of a major corporation being compromised by an intruder. 
The simple fact is that there really is no such thing as a truly secure system as long is it is connected to a network. If the large corporations with expensive firewalls and talented IT staff can’t always stop criminals from breaking in what chance do the rest of us have?
Fortunately all is not lost and we do not have to pull the network cables out of the back of our computer systems. With careful planning and system configuration it is quite possible to create a secure environment that will cause the hacker to move on to the next, easier target without rendering the entire system useless. 

 

Building Internet Firewalls .

Building Internet Firewalls
By D. Brent Chapman & Elizabeth D. Zwicky; ISBN 1-56592-124-0, 517 pages.
First Edition, November 1995.


CLICK HERE

Linux Administrator's Security Guide

Linux Administrator's Security Guide

Author: Kurt Seifried

What is computer security?

Security is risk management. - unknown
"A computer is secure if you can depend on it and it's software to behave as you expect" - Practical UNIX and Internet Security
Security is: availability, consistency, access control, data confidentiality, authentication. 
"The principal objective of computer security is to protect and assure the confidentiality, integrity, and availability of automated information systems and the data they contain."
There are numerous definitions for "computer security", and most of them are correct. Essentially computer security means enforcement of usage policies, this must be done since people and software have flaws that can result in accidents, but also because someone may want to steal your information, use your resources inappropriately or simply deny you the use of your resources.

CLICK HERE

Securing Debian Manual

Securing Debian Manual 

 This document describes security in the Debian project and in the Debian operating system. Starting with the process of securing and hardening the default Debian GNU/Linux distribution installation, it also covers some of the common tasks to set up a secure network environment using Debian GNU/Linux, gives additional information on the security tools available and talks about how security is enforced in Debian by the security and audit team. 

Wednesday, June 19, 2013

Network Security Tools

Network Security Tools

  

This concise, high-end guide shows experienced administrators how to customize and extend popular open source security tools such as Nikto, Ettercap, and Nessus. It also addresses port scanners, packet injectors, network sniffers, and web assessment tools. Network Security Tools is the one resource you want at your side when locking down your network. 

Saturday, June 15, 2013

The Design and Implementation of the 4.4BSD Operating System

The FreeBSD Corporate Networker's Guide

FreeBSD system programming

FreeBSD system programming

Nathan Boeger 

 Mana Tominaga 

 

Welcome to the FreeBSD System Programming book. Please note that this is a work in progress and feedback is appreciated! please note a few things first:
  • We have written the book in a new format. I have read many programming books that have covered many different areas. Personally, I found it hard to follow code with no comments or switching back and forth between text explaining code and the code. So in this book, after chapter 1, I have split the code and text into separate pieces. The source code for each chapter is online and fully downloaded able. That way if you only want to check out the source code examples you can view them only. And if you want to understand the concepts you can read the text or even have them side by side. Please let us know your thoughts on this
  • The book was ordinally intended to be published in hard copy form. However, this has changed and the book was converted using txt2html and some quick edits by hand. Therefore you might find that the HTML formatting is not consistent or hard to follow. We would like feedback on this. Please let us know what style would be the easiest to read.
  • If you would like to participate please contact the authors.You can view the work online or choose to download the chapter as txt.
  • Contributors:
    Francis Gudin (updates to Chapter 1, 2, 3, 4, 5, 6, 7, and 8)
    Ceri Davies (converting to DocBook)
CLICK HERE
 

 

The Linux+FreeBSD mini-HOWTO

The Linux+FreeBSD mini-HOWTO

Niels Kristian Bech Jensen

 

 This document describes how to use Linux and FreeBSD on the same system. It introduces FreeBSD and discusses how the two operating systems can cooperate, e.g. by sharing swap space. You should probably have some experience with Linux or FreeBSD and hard drive partitioning (fdisk) before you read this document. The tips herein are tested using FreeBSD 2.2.2, but they should be valid for newer versions as well. Do not hesitate to mail me if you have comments, questions or suggestions about this document. I would also like to hear from people who have experience using Linux together with NetBSD or OpenBSD.

CLICK HERE

FreeBSD Developers' Handbook

FreeBSD Developers' Handbook

 

Welcome to the Developers' Handbook. This manual is a work in progress and is the work of many individuals. Many sections do not yet exist and some of those that do exist need to be updated. If you are interested in helping with this project, send email to the FreeBSD documentation project mailing list.
The latest version of this document is always available from the FreeBSD World Wide Web server. It may also be downloaded in a variety of formats and compression options from the FreeBSD FTP server or one of the numerous mirror sites.

CLICK HERE

Thursday, June 13, 2013

Motif Programming Manual, Vol 6A, 2nd Edition

Motif Programming Manual, Vol 6A, 2nd Edition

By David Brennan, Dan Heller, Paula Ferguson

Publisher: O'Reilly Media

Released: September 1993

Pages: 1014

  

The Motif Programming Manual is a source for complete, accurate, and insightful guidance on Motif application programming. There is no other book that covers the ground as thoroughly or as well as this one. The book has been updated to Motif 1.2, but is still usable with Motif 1.1.
The Motif Programming Manual describes how to write applications using the Motif toolkit from the Open Software Foundation (OSF). The book goes into detail on every Motif widget class, with useful examples that will help programmers to develop their own code. Anyone doing Motif programming who doesn't want to have to figure it out on their own needs this book.
In addition to information on Motif, the book is full of tips about programming in general and about user interface design.
Contents include:
  • An introduction to the Motif programming model, how it is based on the X Toolkit Intrinsics, and how it differs from them.
  • Chapters on each of the Motif widget classes, explaining them in depth, with useful examples that will help you to improve your own code. For example, the chapter on menus shows how to develop utility functions that generalize and simplify menu creation. All of the code shown in the book is available free of charge over the Internet or via UUCP.
  • Coverage of the drag-and-drop mechanism for transferring data. Two extensive examples show how to implement custom drag source and drop site functionality in a Motif application.
  • A tutorial on UIL. The chapters on UIL describe all of the techniques used to create an interface with this prototyping tool. The numerous examples cover the basics and explore ways to use UIL to facilitate rapid prototyping.
  • ,/ul>The book assumes competence with the C programming language, as well as familiarity with fundamental X Window System concepts. The Motif Programming Manual is not only the most comprehensive guide to writing applications with Motif, it is an integral part of the most widely used series of books on X as a whole. It complements and builds upon the earlier books in the X Window System Series from O'Reilly & Associates, as well as on OSF's own Motif Style Guide. Best when paired with Volume 6B, Motif Reference Manual.

 CLICK HERE

AIXwindows Programming Guide

AIXwindows Programming Guide

AIX 5L Version 5.1
AIXwindows Programming Guide
Third Edition (April 2001)

Highlighting

The following highlighting conventions are used in this book:

Bold Identifies commands, subroutines, keywords, files, structures, directories, and other items whose names are predefined by the system. Also identifies graphical objects such as buttons, labels, and icons that the user selects.
Italics Identifies parameters whose actual names or values are to be supplied by the user.
Monospace Identifies examples of specific data values, examples of text similar to what you might see displayed, examples of portions of program code similar to what you might write as a programmer, messages from the system, or information you should actually type.

 CLICK HERE

Basic Graphics Programming With The Xlib Library

Basic Graphics Programming With The Xlib Library

 

 

This tutorial is the first in a series of "would-be" tutorials about graphical programming in the X window environment. By itself, it is useless. A real X programmer usually uses a much higher level of abstraction, such as using Motif (or its free version, lesstiff), GTK, QT and similar libraries. However, we need to start somewhere. More than this, knowing how things work down below is never a bad idea.
After reading this tutorial, one would be able to write very simple graphical programs, but not programs with a descent user interface. For such programs, one of the previously mentioned libraries would be used.

CLICK HERE

Motif Programming

Motif Programming

A. D. Marshall 1998/9

This book introduces the fundamentals of Motif programming and addreses wider issues concerning the X Window system. The aim of this book is to provide a practical introduction to writing Motif programs. The key principles of Motif programming are always supported by example programs.
The X Window system is very large and this book does not attempt to detail every aspect of either X or Motif. This book is not intended to be a complete reference on the subject.
The book is organised into logical parts, it begins by introducing the X Window system and Motif and goes on to study individual components in detail in specific Chapters. In the remainder of this Chapter we concentrate on why Motif and related areas are important and give a brief history of the development of Motif.

Xlib programming: a short tutorial

Xlib programming: a short tutorial

I haven't found anything very satisfying on the Web as an Xlib tutorial. Many of them are too much Motif-oriented for my taste. Furthermore, I answer questions about X programming almost daily, so I've started to put together some small coursewares.

Important note:

the example programs are written in C++, but this is mainly for the ability to declare variables anywhere.

CLICK HERE

Xlib programming manual

Xlib programming manual

 

CLICK HERE

X Window and Motif Programming Guide (D. Marshall)

X Window and Motif Programming Guide (D. Marshall)

 

CLICK HERE

An Introduction to Tkinter

An Introduction to Tkinter

Fredrik Lundh

 

 

The Tkinter module ("Tk interface") is the standard Python interface to the Tk GUI toolkit from Scriptics (formerly developed by Sun Labs).
Both Tk and Tkinter are available on most Unix platforms, as well as on Windows and Macintosh systems. Starting with the 8.0 release, Tk offers native look and feel on all platforms.
Tkinter consists of a number of modules. The Tk interface is located in a binary module named _tkinter (this was tkinter in earlier versions). This module contains the low-level interface to Tk, and should never be used directly by application programmers. It is usually a shared library (or DLL), but might in some cases be statically linked with the Python interpreter.
In addition to the Tk interface module, Tkinter includes a number of Python modules. The two most important modules are the Tkinter module itself, and a module called Tkconstants. The former automatically imports the latter, so to use Tkinter, all you need to do is to import one module:
    import Tkinter
Or, more often:
    from Tkinter import *
 
CLICK HERE 

X Window System Architecture Overview HOWTO

X Window System Architecture Overview HOWTO

Daniel Manrique

 

 This document provides an overview of the X Window System's architecture, give a better understanding of its design, which components integrate with X and fit together to provide a working graphical environment and what choices are there regarding such components as window managers, toolkits and widget libraries, and desktop environments.

 

CLICK HERE

Wednesday, June 12, 2013

Cygwin User's Guide

Cygwin User's Guide

 

Cygwin is a Linux-like environment for Windows. It consists of a DLL (cygwin1.dll), which acts as an emulation layer providing substantial POSIX (Portable Operating System Interface) system call functionality, and a collection of tools, which provide a Linux look and feel. The Cygwin DLL works with all x86 and AMD64 versions of Windows NT since Windows XP SP3. The API follows the Single Unix Specification as much as possible, and then Linux practice. The major differences between Cygwin and Linux is the C library (newlib instead of glibc).
With Cygwin installed, users have access to many standard UNIX utilities. They can be used from one of the provided shells such as bash or from the Windows Command Prompt. Additionally, programmers may write Win32 console or GUI applications that make use of the standard Microsoft Win32 API and/or the Cygwin API. As a result, it is possible to easily port many significant UNIX programs without the need for extensive changes to the source code. This includes configuring and building most of the available GNU software (including the development tools included with the Cygwin distribution).

CLICK HERE

GTK+ 3 Reference Manual

GTK+ 3 Reference Manual

GTK+ is the primary library used to construct user interfaces in GNOME applications. It provides user interface controls and signal callbacks to control user interfaces.


CLICK HERE

Grokking the GIMP

Grokking the GIMP

by
Carey Bunks
Grokking the GIMP  

Book Overview

The first part of this book focuses on mastering core tools: layers, selections, masks, and colorspaces. The second part builds on the first by presenting an in-depth treatment of touchup, enhancement, compositing, rendering, and image creation for the web. The following gives a synopsis of what you will find in each chapter.
Chapter 1 reviews the GIMP basics. It introduces the GIMP dialogs, reviews window features, and explains a host of functions that are basic but should not be taken for granted. An experienced GIMP user could quickly flip through this chapter of the book, especially if he or she's already familiar with the main features of version 1.2.
Chapter 2 covers layers. Layers are the fundamental building blocks of the GIMP. They are the image unit that plays the most important role in our work, and it is important to understand them and the functions that manipulate them. Even if you are already familiar with layers, this chapter will be worth reviewing because it contains many insights into how to use layers efficiently and effectively.
Chapters 3 and 4 give a unified and in-depth presentation of selections and masks. To the casual observer selections and masks may seem like very different animals. However, they are really complementary implementations of the same thing. The goal of both is to isolate a part of an image. Selections do this by selecting a group of pixels in the image, and masks do it by masking some pixels, leaving the rest exposed. Thus, selections are masks, and masks are selections. These two chapters explain how selections and masks can be made to work efficiently and effectively together.
Because selections are often the most time-consuming part of any project, Chapter 3 compares the different selection tools and describes the applications for which each is best suited. Chapter 4 makes the conceptual link from selections to masks. This chapter describes a host of advanced mask techniques, including methods for refining selection edges and a super technique for finding natural masks you won't want to miss.
Chapter 5 adds the final component of our basic skill set by describing colorspaces and the tools used to get results with color. The first half of this chapter is conceptual, covering RGB and HSV colorspaces. The second half covers the GIMP's blending modes. These are often poorly understood and under-utilized by beginning users. As will be seen in later chapters, the blending modes are valuable tools, without which many needed operations would be quite impossible. The material covered in this chapter is critical for color correction, compositing, rendering, and web graphics... the entire second half of the book! The chapter's intuitive approach explains the aspects of color theory you'll need for your GIMP projects.
Chapter 6 presents techniques for photo touchup and enhancement. The main feature of this chapter is the use of Curves, a poorly understood but amazingly powerful tool. I think that the material covered in this chapter alone is worth the price of the book. In addition to the use of Curves, this chapter also covers the use of the Clone tool for the elimination of blemishes and the use of a sharpening filter, oddly named Unsharp Mask.
One of the most interesting, fun, and useful uses of the GIMP is compositing. Compositing is collage, photo montage, and all the techniques that go with these. Compositing is probably the premiere use of an image manipulation program such as the GIMP, and Chapter 7 covers this topic in detail. This chapter more than any other depends on using the methods and techniques presented in the earlier chapters and is strongly oriented around project work. The projects show how to effectively use selections, masks, and color correction techniques, among other tools, to achieve terrific compositing results.
Chapter 8 describes the tools and techniques for creating shadows, punchouts, and bevels. In addition, it gives an in-depth description of the Emboss and Bump map filters. These are powerful tools for creating 3D effects in images
Chapter 9 is the final chapter of this book. It covers some of the most useful features in the GIMP for Internet web applications. This chapter describes tools for creating animated GIFs and clickable image maps. It also covers several other topics that are required reading for anyone creating graphics for the web.


Volume 3: OPEN LOOK User's Guide

Volume 3: OPEN LOOK User's Guide

Ian Darwin, Valerie Quercia, and Tim O'Reilly
Unpublished, 1993


I started working on Volume 3: OPEN LOOK in the eary 1990s, when Sun made the XView source code freely available. (Please remember this: it really was the world's first open source commercial toolkit for the X Window System; "Open Motif" came almost two decades later, after the freeware QT and GTK toolkit were in wide circulation.)
As the 1990s rolled on, the Unix industry came to a pitched battle between Motif (backed by IBM, DEC, HP, and SCO) and OPEN LOOK (backed by Sun and AT&T).
Around 1993, I finished the book, and happened to be travelling to California so I delivered the manuscript for review to Tim O'Reilly in person, in his office an hour north of San Francisco. He looked at it, and said something like, "So, did you hear about the announcement on Tuesday?" In response to my blank stare, he related that Sun had capitulated on OPEN LOOK in return for the other vendors capitulating on Sun's desktop tools (Calendar Manager &c, plus the ToolTalk technology underlying it), and the vendors had all joined together to form the Common Open Systems Environment group, whose first project was to be the Common Desktop Environment (CDE). And it was to be based on Motif, not OPEN LOOK.
The upshot was that Volume 3: OPEN LOOK never was published, despite a long period of indecision. (Tim asked readers in their then-hardcopy magazine/catalog if they thought it should be published, but results were inconclusive.)
Finally, in 1995, I decided to take the bull by the horns and publish an XView and OPEN LOOK CD-ROM. I got permission from O'Reilly & Associates to include Vol3 OL and Vol 7A and 7B, collected as much other OPEN LOOK stuff as I could, including the example code from competing publishers' books, and burned a CD. I had a few hundred copies pressed, and I sold it over the net for the rest of the 1990s. It only sold a few hundred copies, and the last copy sold in 2002. It never caught on in a big way, for some reason. There are, of course, a lot of "could have, should have" items here, but rather than dwell on them, I'm simply releasing it for free to benefit anybody who still uses OPEN LOOK.


Tuesday, June 11, 2013

XEmacs Tutorial Table of Contents

XEmacs Tutorial Table of Contents

 

 

How To Use This Document

You should be reading this document using a browser such as Netscape. In addition, you will be running XEmacs so that you can try out the commands given here. Don't worry! If you don't know how to start XEmacs yet, you will soon. It is very important that you follow the instructions closely and accurately. READ EVERYTHING! Occasionally you will be asked to type some Unix commands in an xterm window, so you should make sure that you have an xterm window open as well. The following icons are used to help you move through this tutorial:
 
 

The keyboard icon indicates that input is expected from you. Most of the time you will be asked to input something into an XEmacs window. Pay close attention to the instructions! Sometimes you will be switching over to an xterm window for input. 

The left arrow will take you to the PREVIOUS page of the turorial. 

The right arrow is the CONTINUE arrow. It will take you to the next page of the tutorial. 

A TABLE OF CONTENTS is provided for more flexible movement and is accessible from the bottom of each page via this UP arrow icon. 
If you are brand new to XEmacs, it is recommended that you follow the CONTINUE links at the bottom of each page sequentially, as the tutorial is organized into one continuous lesson. 

CLICK HERE

The Official Samba-3 HOWTO and Reference Guide

The Official Samba-3 HOWTO and Reference Guide

John H. Terpstra

and

Jelmer R. Vernooij

 Samba is a big, complex project. The Samba project is ambitious and exciting. The team
behind Samba is a group of some thirty individuals who are spread the world over and
come from an interesting range of backgrounds. This team includes scientists, engineers,
programmers, business people, and students.
Team members were drawn into active participation through the desire to help deliver
an exciting level of transparent interoperability between Microsoft Windows and the non-
Microsoft information technology world.
The slogan that unites the efforts behind the Samba project says: Samba, Opening Windows
to a Wider World! The goal behind the project is one of removing barriers to interoperability.
Samba provides file and print services for Microsoft Windows clients. These services may be
hosted off any TCP/IP-enabled platform. The original deployment platforms were UNIX
and Linux, though today it is in common use across a broad variety of systems.


Samba-3 by Example Practical Exercises to Successful Deployment

Samba-3 by Example Practical Exercises to Successful Deployment
 

Second Edition
John H. Terpstra

The cover artwork of this book continues the freedom theme of the first edition of “Samba-3
by Example.” The history of civilization demonstrates the fragile nature of freedom. It can
be lost in a moment, and once lost, the cost of recovering liberty can be incredible. The previous
edition cover featured Alfred the Great who liberated England from the constant assault
of Vikings and Norsemen. Events in England that finally liberated the common people
came about in small steps, but the result should not be under-estimated. Today, as always,
freedom and liberty are seldom appreciated until they are lost. If we can not quantify what
is the value of freedom, we shall be little motivated to protect it.
Samba-3 by Example Cover Artwork: The British houses of parliament are a symbol of the
Westminster system of government. This form of government permits the people to govern
themselves at the lowest level, yet it provides for courts of appeal that are designed to
protect freedom and to hold back all forces of tyranny. The clock is a pertinent symbol of
the importance of time and place.
The information technology industry is being challenged by the imposition of new laws,
hostile litigation, and the imposition of significant constraint of practice that threatens
to remove the freedom to develop and deploy open source software solutions. Samba is a
software solution that epitomizes freedom of choice in network interoperability for Microsoft
Windows clients.
I hope you will take the time needed to deploy it well, and that you may realize the greatest
benefits that may be obtained. You are free to use it in ways never considered, but in doing
so there may be some obstacles. Every obstacle that is overcome adds to the freedom you
can enjoy. Use Samba well, and it will serve you well.


CLICK HERE

Using Samba

Using Samba

Robert Eckstein, David Collier-Brown, Peter Kelly

1st Edition November 1999

 

 

This book, which has been officially adopted by the Samba team under an open content license, is a comprehensive guide to Samba administration, including such recent additions as integration with Windows NT domains and the SWAT graphic configuration tool.
Samba is a cross-platform triumph: it turns a Unix or Linux system into a file and print server for Microsoft Windows network clients. Now you can let users store their files (and even important executables) in a single place for easy sharing and backup, protected by Unix or NT security mechanisms, and still offer such transparent access that PC users don't even realize they're going to another system. The magic behind Samba is that it recognizes and speaks the SMB protocol developed by Microsoft for file and printer sharing on its own systems.
Basic Samba configuration is simple, but you'll want to make sure your security settings are just right and find out about the full range of options (how do you like your filenames mangled?). Trouble-shooting, security, connectivity, performance, and logging are thoroughly covered with examples in this book.
Samba is so robust, flexible, and secure that many people are choosing it over Windows NT for their file and print services. Furthermore, Samba is proving to be a necessity for the many organizations that have an existing Unix or Linux system and want to tie in PCs running Microsoft software. Samba is also open source software, licensed under the GNU General Public License.
The authors present the most common configurations and problems in an easy-to-follow manner, along with instructions for getting the most out of Samba. Whether you're playing on one note or a full three-octave range, this book will give you an efficient and secure server. The included CD-ROM holds sources and ready-to-install binaries, plus other useful information.
 

 

 

Using Samba, 2nd Edition

Using Samba, 2nd Edition

By Jay Ts, Robert Eckstein, David Collier-Brown

Publisher: O'Reilly Media

Released: February 2003

Pages: 560

 

 

This book, which has been officially adopted by the Samba Team and is under the GNU Free Documentation License (FDL), is a comprehensive guide to Samba administration. The 2nd edition focuses on Samba 2.2 and covers the most important features of 3.0, which was under development as this book went to print.
Samba is a cross-platform triumph: it turns a Unix or Linux system into a file and print server for Microsoft Windows network clients. Samba is so robust, flexible, fast, and secure that many people are choosing it over Windows NT/2000/XP for their file and print services. Samba is also free software, licensed under the GNU General Public License.
This book will help you make file and print sharing as robust, powerful, and efficient as possible. The authors delve into the internals of the Windows activities and protocols to an unprecedented degree, explaining the strengths and weaknesses of each feature in Windows domains and in Samba itself.
Using Samba takes you from basic installation and configuration--on both the client and server side, for a wide range of systems--to subtle details of security, cross-platform compatibility, and resource discovery that make the difference between whether a user sees the folder they expect or a cryptic error message.
The range of this book knows few bounds. Wondering how to integrate Samba's authentication with that of a Windows PDC? How to get Samba to serve Microsoft Dfs shares? How to share files on Mac OS X? These and a dozen other issues of interest to system administrators are covered. A whole chapter is dedicated to troubleshooting.
Whether you're playing on one note or a full three-octave range, on your personal computer or an enterprise network, Using Samba will give you an efficient and secure server.

CLICK HERE

Guide to IP Layer Network Administration with Linux

Guide to IP Layer Network Administration with Linux

Version 0.4.5

Author: Martin A. Brown

 

I assume a few things about the reader. First, the reader has a basic understanding (at least) of IP addressing and networking. If this is not the case, or the reader has some trouble following my networking examples, I have provided a section of links to IP layer tutorials and general introductory documentation in the appendix. Second, I assume the reader is comfortable with command line tools and the Linux, Unix, or BSD environments. Finally, I assume the reader has working network cards and a Linux OS. For assistance with Ethernet cards, the there exists a good Ethernet HOWTO.
The examples I give are intended as tutorial examples only. The user should understand and accept the ramifications of using these examples on his/her own machines. I recommend that before running any example on a production machine, the user test in a controlled environment. I accept no responsibility for damage, misconfiguration or loss of any kind as a result of referring to this documentation. Proceed with caution at your own risk.
This guide has been written primarily as a companion reference to IP networking on Ethernets. Although I do allude to other link layer types occasionally in this book, the focus has been IP as used in Ethernet. Ethernet is one of the most common networking devices supported under linux, and is practically ubiquitous.

 

CLICK HERE

Wireless LAN resources for Linux

Wireless LAN resources for Linux

 

The Linux Wireless LAN Howto is an Open Source project sponsored by Hewlett Packard (through my contribution) since 1996, and built with the contribution of many Linux users all over the world.

I first got involved in the Wireless LAN world by hacking the Wavelan drivers for Linux. I'm quite curious, so I start gathering information to know how the damn beasty was working.
Then, I realised that there was no central point where you could find all this information, links to the drivers and issues with Linux. So, I start stuffing it on my web pages, and it slowly evolved to what you see now.
I'm no longer active on the Wavelan drivers, but I'm also still following the work of Wireless LAN (called as well WLAN or Radio Ethernet), especially in relation with Linux. So, once every century, I update my Linux Wireless LAN Howto (html and pdf available below) and the collection of URLs (after the howto). I hope that it is usefull to someone...

CLICK HERE

 

An Introduction to Socket Programming

An Introduction to Socket Programming

(by) Reg Quinton

These course notes are directed at Unix application programmers who want to develop client/server applications in the TCP/IP domain (with some hints for those who want to write UDP/IP applications). Since the Berkeley socket interface has become something of a standard these notes will apply to programmers on other platforms.
Fundamental concepts are covered including network addressing, well known services, sockets and ports. Sample applications are examined with a view to developing similar applications that serve other contexts. Our goals are
  • to develop a function, tcpopen(server,service), to connect to service.
  • to develop a server that we can connect to.
This course requires an understanding of the C programming language and an appreciation of the programming environment (ie. compilers, loaders, libraries, Makefiles and the RCS revision control system). If you want to know about socket programming with perl(1) then see below but you should read everything first.

CLICK HERE

UNIX Socket FAQ

 UNIX Socket FAQ

 

CLICK HERE

Linux Packet Filtering and iptables

Linux Packet Filtering and iptables

Oskar Andreasson

 

 

About the author

I am someone with too many old computers on his hands. I have my own LAN and want all my machines to be connected to the Internet, whilst at the same time making my LAN fairly secure. The new iptables is a good upgrade from the old ipchains in this regard. With ipchains, you could make a fairly secure network by dropping all incoming packages not destined for given ports. However, things like passive FTP or outgoing DCC in IRC would cause problems. They assign ports on the server, tell the client about it, and then let the client connect. There were some teething problems in the iptables code that I ran into in the beginning, and in some respects I found the code not quite ready for release in full production. Today, I'd recommend everyone who uses ipchains or even older ipfwadm etc., to upgrade - unless they are happy with what their current code is capable of and if it does what they need. I would even go as far as saying that iptables beats quiet a lot of the commercial firewall implementations that I have seen so far.

Monday, June 10, 2013

Networking Guide


Networking Guide

This Networking Guide contains information on configuring, administering, and using the TCP/IP and IPX/SPX(TM) protocol stacks to provide SCO OpenServer(TM) users with access to various networking services.  



CLICK HERE

Linux IPv6 HOWTO (en)

Linux IPv6 HOWTO (en)

Peter Bieringer

The goal of the Linux IPv6 HOWTO is to answer both basic and advanced questions about IPv6 on the Linux operating system. This HOWTO will provide the reader with enough information to install, configure, and use IPv6 applications on Linux machines. Intermediate releases of this HOWTO are available at mirrors.bieringer.de or mirrors.deepspace6.net. See also revision history for changes.


CLICK HERE

UNIX Network Programming with TCP/IP

UNIX Network Programming with TCP/IP

Short Course Notes

Alan Dix

 

CLICK HERE


Network programming under Unix systems

Network programming under Unix systems

 This document is meant to provide people who already have a knowledge of Programming in C, with the knowledge necessary to write Unix programs that use the network (actually, the Internet). It is supposed to save you all the time it took me to learn how to do this, due to lack of decent online documentation about the subject.
The idea is to explain only the really necessary information for writing client and server applications, leaving less "urgent" information for the appendices, and even less important information for the "see also" part. By the way, I'm not providing an Index, because usually indexed documents scare me away, and I want this document to look friendly to *me*, hoping it will also look friendly to you.

OK, lets get down to business.

CLICK HERE

Sunday, June 9, 2013

TCP/IP Network Administration .

TCP/IP Network Administration

By Craig Hunt; ISBN 1-56592-322-7, 630 pages.
Second Edition, December 1997.

All of us who use a UNIX desktop system - engineers, educators, scientists, and business people - have second careers as UNIX system administrators. Networking these computers gives us new tasks as network administrators.
Network administration and system administration are two different jobs. System administration tasks such as adding users and doing backups are isolated to one independent computer system. Not so with network administration. Once you place your computer on a network, it interacts with many other systems. The way you do network administration tasks has effects, good and bad, not only on your system but on other systems on the network. A sound understanding of basic network administration benefits everyone.
Networking computers dramatically enhances their ability to communicate - and most computers are used more for communication than computation. Many mainframes and supercomputers are busy crunching the numbers for business and science, but the number of such systems pales in comparison to the millions of systems busy moving mail to a remote colleague or retrieving information from a remote repository. Further, when you think of the hundreds of millions of desktop systems that are used primarily for preparing documents to communicate ideas from one person to another, it is easy to see why most computers can be viewed as communications devices.
The positive impact of computer communications increases with the number and type of computers that participate in the network. One of the greatbenefits of TCP/IP is that it provides interoperable communications between all types of hardware and all kinds of operating systems.
This book is a practical, step-by-step guide to configuring and managing TCP/IP networking software on UNIX computer systems. TCP/IP is the software package that dominates UNIX data communications. It is the leading communications software for UNIX local area networks and enterprise intranets, and for the foundation of the worldwide Internet.
The name "TCP/IP" refers to an entire suite of data communications protocols. The suite gets its name from two of the protocols that belong to it: the Transmission Control Protocol and the Internet Protocol. Although there are many other protocols in the suite, TCP and IP are certainly two of the most important.

DNS & BIND

DNS & BIND

By Cricket Liu & Paul Albitz; ISBN 1-56592-512-2, 502 pages.
Third Edition, September 1998.

The Domain Name System is basically a database of host information. Admittedly, you get a lot with that: funny dotted names, networked name servers, a shadowy "name space." But keep in mind that, in the end, the service DNS provides is information about internet hosts.
We've already covered some important aspects of DNS , including its client-server architecture and the structure of the DNS database. However, we haven't gone into much detail, and we haven't explained the nuts and bolts of DNS 's operation.
In this chapter, we'll explain and illustrate the mechanisms that make DNS work. We'll also introduce the terms you'll need to know to read the rest of the book (and to converse intelligently with your fellow domain administrators).
First, though, let's take a more detailed look at concepts introduced in the previous chapter. We'll try to add enough detail to spice it up a little.

Practical UNIX & Internet Security

Practical UNIX & Internet Security

By Simson Garfinkel & Gene Spafford; ISBN 1-56592-148-8, 1004 pages.
Second Edition, April 1996.

In today's world of international networks and electronic commerce, every computer system is a potential target. Rarely does a month go by without news of some major network or organization having its computers penetrated by unknown computer criminals. Although some computer "hackers" (see the sidebar below) have said that such intrusions are merely teenage pranks or fun and games, these intrusions have become more sinister in recent years: computers have been rendered inoperable; records have been surreptitiously altered; software has been replaced with secret "back doors" in place; proprietary information has been copied without authorization; and millions of passwords have been captured from unsuspecting users.
Even if nothing is removed or altered, system administrators must often spend hours or days reloading and reconfiguring a compromised system to regain some level of confidence in the system's integrity. There is no way to know the motives of an intruder and the worst must be assumed. People who break into systems simply to "look around" do real damage, even if they do not read confidential mail and do not delete any files. If computer security was once the subject of fun and games, those days have long since passed.
Many different kinds of people break into computer systems. Some people - perhaps the most widely publicized - are the equivalent of reckless teenagers out on electronic joy rides. Like youths who "borrow" fast cars, their main goal isn't necessarily to do damage, but to have what they consider to be a good time. Others are far more dangerous: some people who compromise system security are sociopaths, joyriding around the networks bent on inflicting damage on unsuspecting computer systems. Others see themselves at "war" with rival hackers; woe to innocent users and systems who happen to get in the way of cyberspace "drive-by shootings!" Still others are out for valuable corporate information, which they hope to resell for profit. There are also elements of organized crime, spies and saboteurs motivated by both greed and politics, terrorists, and single-minded anarchists using computers and networks.

Building Internet Firewalls .

Building Internet Firewalls

By D. Brent Chapman & Elizabeth D. Zwicky; ISBN 1-56592-124-0, 517 pages.
First Edition, November 1995.

It is scarcely possible to enter a bookstore, read a magazine or a newspaper, or listen to a news broadcast without seeing or hearing something about the Internet in some guise. It's become so popular that it no longer requires explanations when mentioned in nontechnical publications, and it gets mentioned plenty, in magazines ranging from The New Yorker to Bead and Button . While nontechnical publications are obsessed with the Internet, the technical publications have moved on and are obsessed with security. It's a logical progression; once the first excitement of having a superhighway in your neighborhood wears off, you're bound to notice that not only does it let you travel, it lets a very large number of strangers show up where you are, and not all of them are people you would have invited.
Both views are true: The Internet is a marvelous technological advance that provides access to information, and the ability to publish information, in revolutionary ways. But it's also a major danger that provides the ability to pollute and destroy information in revolutionary ways. This book is about one way to balance the advantages and the risks - to take part in the Internet while still protecting yourself.
Later in this chapter, we describe different models of security people have used to protect their data and resources on the Internet. Our emphasis in this book is on the network security model and, in particular, the use of Internet firewalls. A firewall is a form of protection that allows a network to connect to the Internet while maintaining a degree of security. The section later in this chapter called "What is an Internet Firewall?" describes the basics of firewalls and summarize what they can - and cannot - do to help make your site secure. Before we discuss what you can do with a firewall, though, we want to describe briefly why you need one. What are you protecting on your systems? What types of attacks and attackers are we seeing today? What types of security can you use to protect your site?

sendmail Desktop Reference

sendmail Desktop Reference

By Bryan Costales & Eric Allman; ISBN 1-56592-278-6, 74 pages.
First Edition, March 1997.

The sendmail program is a Mail Transport Agent (MTA). It accepts mail from Mail User Agents (MUAs), mail users (humans), and other MTAs. It then delivers that mail to Mail Delivery Agents (MDAs) on the local machine, or transports that mail to another MTA at another machine. The behavior ofsendmail is determined by its command line and by commands in its configuration file.
The sendmail program is written and maintained by Eric Allman at sendmail.org . Versions V8.7 and earlier are no longer supported and are no longer considered secure. If you are not currently running V8.8, we recommend you upgrade now. This Desktop Reference covers sendmail version 8.8.5.
This Desktop Reference is a companion to the second edition of the sendmail book by Bryan Costales with Eric Allman, published by O'Reilly & Associates. Section numbers herein reference the section numbers in that book. This is a reference guide only - for detail or tutorial information, refer to the full sendmail book.

Sendmail

sendmail

By Bryan Costales & Eric Allman; ISBN 1-56592-222-0, 1050 pages.
Second Edition, January 1997.
Imagine yourself with pen and paper, writing a letter to a friend far away. You finish the letter and sign it, reflect on what you've written, then tuck the letter into an envelope. You put your friend's address on the front, your return address in the left-hand corner, and a stamp in the right-hand corner, and the letter is ready for mailing. Electronic mail  - ail for short) is prepared in much the same way, but a computer is used instead of pen and paper.
The post office transports real letters in real envelopes, whereas sendmail transports electronic letters in electronic envelopes. If your friend (the recipient) is in the same neighborhood (on the same machine), only a single post office ( sendmail running locally) is involved. If your friend is distant, the mail message will be forwarded from the local post office ( sendmail running locally) to a distant one ( sendmail running remotely) for delivery. Althoughsendmail is similar to a post office in many ways, it is superior in others:
  • Delivery typically takes seconds rather than days.
  • Address changes (forwarding) take effect immediately, and mail can be forwarded anywhere in the world.
  • Host addresses are looked up dynamically. Therefore, machines can be moved or renamed, and email delivery will still succeed.
  • Mail can be delivered through programs that access other networks (such as UUCP and BITNET). This would be like the post office using United Parcel Service to deliver an overnight letter.
This analogy between a post office and sendmail will break down as we explore sendmail in more detail. But the analogy serves a role in this introductory material, so we will continue to use it to illuminate a few of sendmail 's more obscure points.

Building Internet Firewalls, 2nd Edition.


by Elizabeth D. Zwicky, Simon Cooper and D. Brent Chapman
ISBN: 1-56592-871-7
Second edition, published June 2000


It is scarcely possible to enter a bookstore, read a magazine or a newspaper, or listen to a news broadcast without seeing or hearing something about the Internet in some guise. It's become so popular that no advertisement is complete without a reference to a web page. While nontechnical publications are obsessed with the Internet, the technical publications have moved on and are obsessed with security. It's a logical progression; once the first excitement of having a superhighway in your neighborhood wears off, you're bound to notice that not only does it let you travel, it lets a very large number of strangers show up where you are, and not all of them are people you would have invited.
Both views are true: The Internet is a marvelous technological advance that provides access to information, and the ability to publish information, in revolutionary ways. But it's also a major danger that provides the ability to pollute and destroy information in revolutionary ways. This book is about one way to balance the advantages and the risks -- to take part in the Internet while still protecting yourself.
Later in this chapter, we describe different models of security that people have used to protect their data and resources on the Internet. Our emphasis in this book is on the network security model and, in particular, the use of Internet firewalls. A firewall is a form of protection that allows a network to connect to the Internet while maintaining a degree of security. The section later in this chapter called "What is an Internet Firewall?" describes the basics of firewalls and summarizes what they can -- and cannot -- do to help make your site secure. Before we discuss what you can do with a firewall, though, we want to describe briefly why you need one. What are you protecting on your systems? What types of attacks and attackers are common? What types of security can you use to protect your site?


DNS and BIND, 4th Edition.


by Paul Albitz and Cricket Liu
ISBN: 0-596-00158-4
Fourth edition, published April 2001.

The Domain Name System is basically a database of host information. Admittedly, you get a lot with that: funny dotted names, networked name servers, a shadowy "namespace." But keep in mind that, in the end, the service DNS provides is information about internet hosts.
We've already covered some important aspects of DNS, including its client-server architecture and the structure of the DNS database. However, we haven't gone into much detail, and we haven't explained the nuts and bolts of DNS's operation.
In this chapter, we explain and illustrate the mechanisms that make DNS work. We also introduce the terms you'll need to know to read the rest of the book (and to converse intelligently with your fellow zone administrators).
First, though, let's take a more detailed look at concepts introduced in the previous chapter. We'll try to add enough detail to spice it up a little.

Network Troubleshooting Tools.


by Joseph D. Sloan
ISBN: 0-596-00186-X
First edition, published August 2001.

The first step in diagnosing a network problem is to collect information. This includes collecting information from your users as to the nature of the problems they are having, and it includes collecting data from your network. Your success will depend, in large part, on your efficiency in collecting this information and on the quality of the information you collect. This book is about tools you can use and techniques and strategies to optimize their use. Rather than trying to cover all aspects of troubleshooting, this book focuses on this first crucial step, data collection.
There is an extraordinary variety of tools available for this purpose, and more become available daily. Very capable people are selflessly devoting enormous amounts of time and effort to developing these tools. We all owe a tremendous debt to these individuals. But with the variety of tools available, it is easy to be overwhelmed. Fortunately, while the number of tools is large, data collection need not be overwhelming. A small number of tools can be used to solve most problems. This book centers on a core set of freely available tools, with pointers to additional tools that might be needed in some circumstances.

Essential SNMP.


by Douglas R. Mauro and Kevin J. Schmidt
ISBN: 0-596-00020-0
First edition, published July 2001.

In today's complex network of routers, switches, and servers, it can seem like a daunting task to manage all the devices on your network and make sure they're not only up and running but performing optimally. This is where the Simple Network Management Protocol (SNMP) can help. SNMP was introduced in 1988 to meet the growing need for a standard for managing Internet Protocol (IP) devices. SNMP provides its users with a "simple" set of operations that allows these devices to be managed remotely.
This book is aimed toward system administrators who would like to begin using SNMP to manage their servers or routers, but who lack the knowledge or understanding to do so. We try to give you a basic understanding of what SNMP is and how it works; beyond that, we show you how to put SNMP into practice, using a number of widely available tools. Above all, we want this to be a practical book -- a book that helps you keep track of what your network is doing.

Managing NFS and NIS, 2nd Edition.


by Hal Stern, Mike Eisler and Ricardo Labiaga
ISBN: 1-56592-510-6
Second edition, published June 2001.

The Network Information Service (NIS) and Network File System (NFS) are services that allow you to build distributed computing systems that are both consistent in their appearance and transparent in the way files and data are shared.
NIS provides a distributed database system for common configuration files. NIS servers manage copies of the database files, and NIS clients request information from the servers instead of using their own, local copies of these files. For example, the /etc/hosts file is managed by NIS. A few NIS servers manage copies of the information in the hosts file, and all NIS clients ask these servers for host address information instead of looking in their own/etc/hosts file. Once NIS is running, it is no longer necessary to manage every /etc/hosts file on every machine in the network -- simply updating the NIS servers ensures that all machines will be able to retrieve the new configuraton file information.
NFS is a distributed filesystem. An NFS server has one or more filesystems that are mounted by NFS clients; to the NFS clients, the remote disks look like local disks. NFS filesystems are mounted using the standard Unix mount command, and all Unix utilities work just as well with NFS-mounted files as they do with files on local disks. NFS makes system administration easier because it eliminates the need to maintain multiple copies of files on several machines: all NFS clients share a single copy of the file on the NFS server. NFS also makes life easier for users: instead of logging on to many different systems and moving files from one system to another, a user can stay on one system and access all the files that he or she needs within one consistent file tree.
This book contains detailed descriptions of these services, including configuration information, network design and planning considerations, and debugging, tuning, and analysis tips. If you are going to be installing a new network, expanding or fixing an existing network, or looking for mechanisms to manage data in a distributed environment, you should find this book helpful.

SSH, The Secure Shell: The Definitive Guide.


by Daniel J. Barrett and Richard E. Silverman
ISBN: 0-596-00011-1
First edition, published February 2001.

Many people today have multiple computer accounts. If you're a reasonably savvy user, you might have a personal account with an Internet service provider (ISP), a work account on your employer's local network, and one or more PCs at home. You might also have permission to use other accounts owned by family members or friends.
If you have multiple accounts, it's natural to want to make connections between them. For instance, you might want to copy files between computers over a network, log into one account remotely from another, or transmit commands to a remote computer for execution. Various programs exist for these purposes, such as ftp and rcp for file transfers, telnet and rlogin for remote logins, and rsh for remote execution of commands.
Unfortunately, many of these network-related programs have a fundamental problem: they lack security. If you transmit a sensitive file via the Internet, an intruder can potentially intercept and read the data. Even worse, if you log onto another computer remotely using a program such as telnet, your username and password can be intercepted as they travel over the network. Yikes!
How can these serious problems be prevented? You can use an encryption program to scramble your data into a secret code nobody else can read. You can install a firewall, a device that shields portions of a computer network from intruders. Or you can use a wide range of other solutions, alone or combined, with varying complexity and cost.

CLICK HERE

TCP/IP Network Administration, 3rd Edition.



by Craig Hunt
ISBN: 0-596-00297-1
Third Edition, published April 2002.

All of us who use a Unix desktop system -- engineers, educators, scientists, and business people -- have second careers as Unix system administrators. Networking these computers gives us new tasks as network administrators.
Network administration and system administration are two different jobs. System administration tasks such as adding users and doing backups are isolated to one independent computer system. Not so with network administration. Once you place your computer on a network, it interacts with many other systems. The way you do network administration tasks has effects, good and bad, not only on your system but on other systems on the network. A sound understanding of basic network administration benefits everyone.
Networking your computers dramatically enhances their ability to communicate -- and most computers are used more for communication than computation. Many mainframes and supercomputers are busy crunching the numbers for business and science, but the number of these systems in use pales in comparison to the millions of systems busy moving mail to a remote colleague or retrieving information from a remote repository. Further, when you think of the hundreds of millions of desktop systems that are used primarily for preparing documents to communicate ideas from one person to another, it is easy to see why most computers can be viewed as communications devices.
The positive impact of computer communications increases with the number and type of computers that participate in the network. One of the great benefits of TCP/IP is that it provides interoperable communications between all types of hardware and all kinds of operating systems.
The name "TCP/IP" refers to an entire suite of data communications protocols. The suite gets its name from two of the protocols that belong to it: the Transmission Control Protocol (TCP) and the Internet Protocol (IP). TCP/IP is the traditional name for this protocol suite and it is the name used in this book. The TCP/IP protocol suite is also called the Internet Protocol Suite (IPS). Both names are acceptable.
This book is a practical, step-by-step guide to configuring and managing TCP/IP networking software on Unix computer systems. TCP/IP is the leading communications software for local area networks and enterprise intranets, and it is the foundation of the worldwide Internet. TCP/IP is the most important networking software available to a Unix network administrator.

Linux Network Administrator's Guide, 2nd Edition

Linux Network Administrator's Guide, 2nd Edition

By Olaf Kirch & Terry Dawson
2nd Edition June 2000



Linux, a Unix-compatible operating system that runs on personal computers and larger servers, is valued above all for its networking strengths. The Linux Network Administrator's Guide spells out all the information needed for joining a network, whether it's a simple UUCP connection or a full LAN with a Linux system serving as a firewall, an NFS or NIS file server, and a mail and news hub.
This book, which is one of the most successful to come from the Linux Documentation Project and remains freely distributable under its license, touches on all the essential networking software included with the operating system, plus some hardware considerations. Fully updated, the book now covers firewalls, including the use of ipchains and iptables (netfilter), masquerading, and accounting. Other new topics include Novell (NCP/IPX) support and INN (news administration). Original material on serial connections, UUCP, routing and DNS, mail and News, SLIP and PPP, NFS, and NIS has been thoroughly updated. Kernel options reflect the 2.2 kernel. However, some topics covered in other books (notably Samba and web server administration) are not in this book.
Topics include:
  • Introduction to TCP/IP
  • Configuring network and serial hardware
  • Domain Name Service
  • Serial line communications using SLIP and PPP
  • NIS and NFS
  • Taylor UUCP
  • Administering electronic mail, including sendmail and Exim
  • Administering Netnews, including INN and several news readers
  • Firewalling using ipfwadm, ipchains, and iptables (netfilter)
  • Masquerading and accounting
  • IPX configuration for a Novell Netware network


Filesystem Hierarchy Standard

Filesystem Hierarchy Standard

Introduction

This page is the home of the Filesystem Hierarchy Standard (FHS).The current version is 2.3. It was announced on January 29, 2004.
The filesystem standard has been designed to be used by Unix distribution developers, package developers, and system implementors. However, it is primarily intended to be a reference and is not a tutorial on how to manage a Unix filesystem or directory hierarchy.

FHS Development

The mailing list is available to discuss interpretations of the FHS document and of possible future changes and additions. All proposals should be submitted as bugs on bugs.freestandards.org using the "FHS" component). To be regarded seriously, proposals should include a unified patch to the sgml source (create the attachment after you've opened the bug, please do not cut-and-paste patches into comments).The process is overseen by FHS editors, Rusty Russell, Daniel Quinlan, and Christopher Yeoh.

VERSION 2.2 PDF

VERSION 2.3 PDF