Italicized words are things you fill in with your own information.
Bold items are actual Linux names to pay special attention to.
[things inside “square brackets” are my comments and are not part of the command. You wont see them on the screen or in any system file].
Underlined word and phrases are section headings.
# In code, configuration files and scripts, “#” (pound) is a “Rem” (remark) statement and is not processed.
# or $, In Command Line Examples, indicates the “prompt”, you type what is to the right of the “#” or “$”
Installation and Configuration
Partitions:
My Configurations: *(All three took a “everything” installation.)
Sony Vaio Laptop 8-99 (Lynx3)
Partition “mount point” Partition Name Size Set / Actual Size
/boot hda1 10 14
/usr hda5 1024 1439 (set to “can grow”)
/home hda6 500 502
/usr/local hda7 500 502
/opt hda8 200 206
(swap) hda9 120 125
/usr/src hda10 100 103
/tmp hda11 100 103
/var hda12 1024 1026
/ (root) hda13 1024 1026
IBM PC 350 8-12-99 (Lynx1)
Partition “mount point” Partition Name Size Set / Actual Size
/boot hda1 11 11
/usr hda5 1200 1200
(swap) hda6 140 141
/var hda11 100 102
/home hda8 100 102
5/tmp hda9 50 51
/usr/local hda10 50 51
/usr/src hda7 65 66 had to be raised from 50 to 65 for everything
/opt hda12 25 27
/ (root) hda13 400 685 (set to “can grow”)
333 MHz (Brian’s, Lynx2)
Partition “mount point” Partition Name Size Set / Actual Size
/boot hda1 10 11
/usr hda5 1200 1200
(swap) hda6 110 110
/home hda7 200 200 (using for /home/www/ document roots)
/usr/local hda8 100 515 (set to “can grow”)
/usr/src hda9 100 102
/opt hda10 100 102
/var hda11 100 102
/tmp hda12 50 51
/ (root) hda13 500 500
3098 total
Note: /tmp, I read somewhere that this partision should not be over 100MB, as Linux wont use it. 8-99.
333 MHz (Brian’s, Lynx2) [11-10-99]
Partition “mount point” Partition Name Size Set / Actual Size
/boot hda1 11 15
/usr hda6 1200 1024
(swap) hda11 110 125
/home hda5 200 13288(using for /home/www/ document roots)
/usr/local hda7 100 502(set to “can grow”)
/usr/src hda10 100 203
/opt hda9 100 203
/var hda8 100 502
/tmp hda12 50 101
/ (root) hda13 500 502
16467 total
*note: The very larg /home partition takes awhile to mount… during amd deamon.
Installation Information is stored in /tmp/install.log
From RedHat Linux On-Line docs.
http://www.redhat.com/corp/support/manuals/RHL-5.2-Manual/install-guide/manual/doc020.html#s2.7.5
2.7 Disk Partitions
Please Note: If you intend to perform a workstation- or server-class installation, and you already have sufficient unpartitioned disk space available, you don't need to read this section, and may turn to Section HYPERLINK "doc021.html" \l "s2.8" 2.8 . Otherwise, please read this section in order to determine the best approach to freeing disk space for your Red Hat Linux installation.
In order to install Red Hat Linux, you must make disk space available for it. This disk space needs to be separate from the disk space used by other operating systems you may have installed on your computer, such as Windows, OS/2, or even a different version of Linux.
A disk can be divided into different partitions. Each partition can be accessed as if it was a separate disk. Furthermore, each partition has a type that is used to indicate how information is stored in the partition. For example, there are different partition types used by DOS, OS/2, and Linux.
Please Note: You must install Red Hat Linux to one or more partitions having a partition type of ``Linux native''. Red Hat Linux also requires a swap partition, which has a partition type of ``Linux swap''. This means that an installation of Red Hat Linux requires at least two partitions:
· One or more partitions of type ``Linux native''
· A partition of type ``Linux swap''
We will discuss partitioning issues in more detail below. For now, keep in mind that Red Hat Linux requires at least two dedicated partitions, and that you cannot install Red Hat Linux to a DOS/Windows partition!
Even if you will be installing Red Hat Linux on its own hard disk, or on a computer which contains no other operating system, you'll still need to create partitions for Red Hat Linux to use. In this case it's pretty easy, as there are no other partitions on the hard disk to worry about.
On the other hand, you may wish to install Red Hat Linux on a disk which already contains software or data from a different operating system. Things can get a little trickier in this situation, since a mistake can destroy your existing partitions, not to mention the data they contain!
During the installation process, you'll be given the chance to create partitions for Red Hat Linux. At this point, your main concern is making sure you have sufficient disk space available to create those partitions. Let's review the different ways to free up space for Red Hat Linux partitions.
2.7.1 Partition Naming Scheme
Linux refers to disk partitions using a combination of letters and numbers which may be confusing, particularly if you're used to the ``C drive'' way of referring to hard disks and their partitions. Red Hat Linux uses a naming scheme that is more flexible and conveys more information than the approach used by other operating systems. Here is a summary:
First Two Letters -- The first two letters of the partition name indicate the type of device on which the partition resides. You'll normally see either hd (for IDE disks), or sd (for SCSI disks).
The Next Letter -- This letter indicates which device the partition is on. For example,
/dev/hda (the first IDE hard disk) or /dev/sdb (the second SCSI disk).
The number The final number denotes the partition. The first four (primary or extended) partitions are numbered 1 through 4. Logical partitions start at 5. E.g., /dev/hda3 is the third primary or extended partition on the first IDE hard disk; /dev/sdb6 is the second logical partition on the second SCSI hard disk.
Keep this information in mind; it will make things easier to understand when you're setting up the partitions Red Hat Linux requires.
2.7.2 Repartitioning Strategies
There are three possible scenarios you may face when attempting to repartition your hard disk:
· Unpartitioned free space is available.
· An unused partition is available.
· Free space in an actively used partition is available.
Let's look at each scenario in order.
2.7.2.1 Using Unpartitioned Free Space
In this situation, the partitions already defined do not span the entire hard disk, leaving unallocated space that is not part of any defined partition. If you think about it, an unused hard disk also falls into this category; the only difference is that all the space is not part of any defined partition.
In this case, you can simply create the necessary partitions from the unused space.
2.7.2.2 Using Space From An Unused Partition
Last year you replaced that tiny 105MB hard drive on your Windows system with a 1.2GB monster. You partitioned it into two equal parts, figuring that you'd use the C: ``drive'' (really the drive's first partition) for Windows, and the D: ``drive'' (really the drive's second partition) for your collection of freeware programs downloaded from the Internet. Well, you'd been so used to using C: that you never put anything of substance on D:.
If you find yourself in this situation, you can use the space allocated to the unused partition. In this case, you'll first need to delete the partition, and then create the appropriate Linux partitions in its place. You can either delete the partition using DOS fdisk, or you'll be given the opportunity to do so during a custom-class installation.
2.7.2.3 Using Free Space From An Active Partition
This is the most common situation. It is also, unfortunately, the hardest to deal with. The main problem is that you have enough free space, but it's presently allocated to a partition that is in use. If you purchased a computer with pre-installed software, the hard disk most likely has one massive partition holding the operating system and data.
Aside from adding a new hard drive to your system, you have two choices:
Destructive Repartitioning -- Basically, you delete the single large partition, and create several smaller ones. As you might imagine, any data you had in that partition is destroyed. This means that making a complete backup is necessary. For your own sake, make two backups, use verification (if available in your backup software), and try to read data from your backup before you delete the partition. Note also that if there was an operating system of some type installed on that partition, it will need to be reinstalled as well.
After creating a smaller partition for your existing software, you can reinstall any software, restore your data, and continue with your Red Hat Linux installation.
Non-Destructive Repartitioning -- Here, you run a program that does the seemingly impossible; it makes a big partition smaller without losing any of the files stored in that partition. Many people have found this method to be reliable and trouble-free. What software should you use to perform this feat? There are several disk management software products on the market; you'll have to do some research to find the one that is best for your situation.
[Intel Systems: As a convenience to our customers, we provide the fips utility. This is a freely available program that can resize FAT (File Allocation Table) partitions. It's included on the Red Hat Linux/Intel CD-ROM in the dosutils directory.
Please Note: Many people have successfully used fips to repartition their hard drives. However, because of the nature of the operations carried out by fips, and the wide variety of hardware and software configurations under which it must run, Red Hat, Inc. cannot guarantee that fips will work properly on your system. Therefore, no installation support whatsoever is available for fips; use it at your own risk.
That said, if you decide to repartition your hard drive with fips, it is vital that you do two things:
· Perform a Backup -- Make two copies of all the important data on your computer. These copies should be to removable media (such as tape or diskettes), and you should make sure they are readable before proceeding.
· Read the Documentation -- Completely read the fips documentation, located in the /dosutils/fipsdocs subdirectory on Red Hat Linux/Intel CD 1.
Should use decide to use fips, be aware that after fips runs you will be left with two partitions: the one you resized, and the one fips created out of the newly-freed space. If your goal is to use that space to install Red Hat Linux, you should delete the newly-created partition, either by using fdisk under your current operating system, or while setting up partitions during a custom-class installation. ]
2.7.3 Disk Partitions and Other Operating Systems
If your Red Hat Linux partitions will be sharing a hard disk with partitions used by other operating systems, most of the time you'll have no problems. However, there are certain combinations of Linux and other operating systems that require extra care. Information on creating disk partitions compatible with other operating systems is available in several HOWTOs and Mini-HOWTOs, available on the Red Hat Linux CD in the doc/HOWTO and doc/HOWTO/mini directories. In particular, the Mini-HOWTOs whose names start with Linux+ are quite helpful.
[Intel Systems: If Red Hat Linux/Intel will coexist on your machine with OS/2, you must create your disk partitions with the OS/2 partitioning software---otherwise, OS/2 may not recognize the disk partitions. During the installation, do not create any new partitions, but do set the proper partition types for your Linux partitions using the Linux fdisk.]
2.7.4 One Last Wrinkle: Using LILO
[Intel Systems: LILO (the LInux LOader) is the most commonly used method to boot Red Hat Linux on Intel-based systems. Being an operating system loader, LILO operates ``outside'' of any operating system, using only the Basic I/O System (or BIOS) built into the computer hardware itself. This section describes LILO's interactions with PC BIOSes, and is specific to Intel-compatible computers. ]
[Alpha Systems: Alpha owners may skip ahead to Section HYPERLINK "doc020.html" \l "s2.7.5" 2.7.5 .]
[SPARC Systems: SPARC owners may skip ahead to Section HYPERLINK "doc020.html" \l "s2.7.5" 2.7.5 .]
2.7.4.1 BIOS-Related Limitations Impacting LILO
LILO is subject to some limitations imposed by the BIOS in most Intel-based computers. Specifically, most BIOSes can't access more than two hard drives and they can't access any data stored beyond cylinder 1023 (the 1024th cylinder) of any drive. Note that some recent BIOSes do not have these limitations, but this is by no means universal.
All the data LILO needs to access at boot time (including the Linux kernel) are located in the /boot directory, which is normally part of the root partition (known as /). Here are the guidelines you must follow if you are going to use LILO to boot your Red Hat Linux system:
On First Two IDE Drives -- If you have 2 IDE (or EIDE) drives, /boot must be located on one of them. Note that this two-drive limit also includes any IDE CD-ROM drives on your primary IDE controller. So, if you have one IDE hard drive, and one IDE CD-ROM on your primary controller, /boot must be located on the first hard drive only, even if you have other hard drives on your secondary IDE controller.
On First IDE Or First SCSI Drive -- If you have one IDE (or EIDE) drive and one or more SCSI drives, /boot must be located either on the IDE drive or the SCSI drive at ID 0. No other SCSI IDs will work.
On First Two SCSI Drives -- If you have only SCSI hard drives, /boot must be located on a drive at ID 0 or ID 1. No other SCSI IDs will work.
Partition Completely Below Cylinder 1023 -- No matter which of the above configurations apply, the partition that holds /boot must be located entirely below cylinder 1023. If the partition holding /boot straddles cylinder 1023, you may face a situation where LILO will work initially (because all the necessary information is below cylinder 1023), but will fail if a new kernel is to be loaded, and that kernel resides above cylinder 1023.
As mentioned earlier, it is possible that some of the newer BIOSes may permit LILO to work with configurations that don't meet our guidelines. Likewise, some of LILO's more esoteric features may be used to get a Linux system started, even if the configuration doesn't meet our guidelines. However, due to the number of variables involved, Red Hat, Inc. cannot support such extraordinary efforts.
Please Note: Disk Druid as well as the workstation- and server-class installs take these BIOS-related limitations into account. However, if you decide to use fdisk instead, it is your responsibility to ensure that you keep these limitations in mind.
2.7.5 How Many Partitions?
Although you can install Red Hat Linux in a single large partition (subject to any of the partitioning considerations we've mentioned so far), it's a much better idea to split things up a bit. We recommend the following layout as a compromise between single-partition simplicity, and multi-partition flexibility:
Please Note: If you plan to install all the software packages that come with Red Hat Linux, you will need to use the larger partitions sizes shown here. In fact, you may want to increase the sizes above our recommendations, to allow for future growth without needing to repartition.
A swap partition -- Swap partitions are used to support virtual memory. If your computer has 16 MB of RAM or less, you must create a swap partition. Even if you have more memory, a swap partition is still recommended. The minimum size of your swap partition should be equal to your computer's RAM, or 16 MB (whichever is larger). The largest useable swap partition is roughly 127 MB, so making a swap partition larger than that will result in wasted space. Note, however, that you can create and use more than one swap partition (although this is usually only necessary for large server installations).
A root partition -- The root partition is where / (the root directory) resides. It only needs to contain things necessary to boot your system, as well as system configuration files. A root partition of 50 MB to 100 MB works well for most systems.
[Intel Systems: Don't forget the LILO constraints we mentioned in Section HYPERLINK "doc020.html" \l "s2.7.4" 2.7.4 !]
A /usr partition -- The /usr partition is where much of the software on a Red Hat Linux system resides. This partition should be between 300 MB and 700 MB, depending on how many packages you plan to install. If at all possible, try to be generous with the /usr partition. Any RPM-based packages you install later will (in general) use more space from /usr than from any other partition.
A /home partition -- This is where users' home directories go; the size of /home depends on how many users you plan to have on your Red Hat Linux system and what they might store in their home directories.
[Alpha Systems: The following partition is specific to Red Hat Linux/Alpha installations.]
A MILO partition -- Alpha owners that will be using MILO to boot their systems should create a 1.5 MB DOS partition where MILO can be copied after the installation is complete.
Additionally, your circumstances may warrant creating one of more of the following partitions:
A /usr/local partition -- Traditionally, /usr/local has been used to hold things you wish to keep separate from the rest of your Red Hat Linux system, such as software that is not available as an RPM package. The size depends on the amount of such software you anticipate putting on your system.
A /usr/src partition -- There are two things that normally are stored in /usr/src on a Red Hat Linux system:
Linux Kernel Sources -- The complete sources for the Linux kernel are stored here, and new kernels are built here. At present, the kernel sources are approximately 30MB in size. Keep in mind that you'll want to have additional free space for building kernels, and you may want to keep more than one version of the kernel available.
Sources For RPM-Based Packages -- If a source package file (aka SRPM) is installed, the files are stored here. Note that, unless specified otherwise, any packages built will also use a build directory located here.
· Again, the size of this partition would depend on the amount of software you anticipate building.
A /tmp partition -- As the name implies, the /tmp partition is for temporary files. Creating a partition dedicated to /tmp is a good idea for larger, multiuser systems or network server machines. The reason is that many active users can fill the root partition (/), which is where /tmp is located. It's not necessary to dedicate a partition to /tmp on single-user workstations.
A /var partition -- Your Red Hat Linux system will write to log files in /var/log. Files queued for printing will normally be written to /var/spool. These are just two examples of data that is written to /var. Unless otherwise configured, /var will be part of the root filesystem, and normally will not have much available free space. If you anticipate a lot of print, mail, or log activity on your system, you might want to consider creating a partition dedicated to /var. In general, only multiuser or server systems would make effective use of a separate /var filesystem.
An /opt partition -- Some third-party software is designed to install itself under /opt. Unless an /opt partition is created, software that attempts to install itself under /opt will end up on the root partition, which may not have sufficient free space. Of course, this is not the only way of solving the /opt problem; it is also possible to create an /opt symbolic link to another partition with more space (such as /usr).
A /boot partition -- While many of the partitions mentioned here make sense only for very large, active systems, this partition might be very useful on a small system, where free space is tight. If you recall, back in Section HYPERLINK "doc020.html" \l "s2.7.4" 2.7.4 , we discussed the various limitatons imposed by the standard PC BIOS, and how these limitations impact the LILO bootloader. All the files LILO needs to access (at boot time) are in the /boot directory. Since the files (including the Linux kernel) in /boot only take up a megabyte or so, if you're having trouble finding space for a 100 MB root partition in a place where LILO can get at it, you might have better luck trying to squeeze in a 5-10 MB (generously oversized) partition for /boot. You'll still need to create a root partition, but it can now be located anywhere on your system -- the BIOS restrictions only apply to the partition holding /boot.
Linux / Unix Command Utilities / Files
/etc/sysconfig: console, keyboard, network, pcmcia, static-routes, amd, clock, init, mouse
and network-scripts.
/etc/ amd.conf, ld.so.conf, nsswitch.conf, sendmail.cw
csh.cshrc, lilo.conf, ntp.conf, smb.conf
dosemu.conf, logrotate.conf, nwserv.conf, syslog.conf
enscript.cfg, ltrace.conf, paper.config, timidity.cfg
gated.conf, sample lynx.cfg, pine.conf, updatedb.conf
gpm-root.conf, man.config, pine.conf.fixed, wine.conf
host.conf, mtools.conf, pwdb.conf, yp.conf
inetd.conf, named.conf, resolv.conf, ypserv.conf
ld.so.cache, nscd.conf, sendmail.cf
/bin arch dd gunzip mktemp rmdir true ash df gzip more rpm umount
ash.static dmesg hostname mount rvi uname awk dnsdomainname igawk mt
rview userconf basename doexec ipcalc mv sed usleep bash domainname kill netconf setserial vi bsh echo ksh netstat sfxload view cat ed linuxconf nice sh xconf chgrp egrep ln nisdomainname sleep ypdomainname chmod ex loadkeys pidof sort zcat chown false login ping stty zsh consolechars fgrep lpdconf ps su cp fsconf ls pwd sync cpio gawk mail red tar csh gawk-3.0.3 mkdir remadmin tcsh date grep mknod rm touch
Used and Edited Configuration Files:
/usr/include/apache/http_vhost.h
/usr/include/linuxconf/netconf_def.h
/user/include/linuxconf/usercon.h and .p
/etc/http/conf/httpd.conf
/etc/profile (start up variables, i.e., set alias’)
/etc/ftpaccess (define who can and can not do what, read overwrite, rename etc.)
/etc/ftpgroups
/etc/ftpusers (lists users who may Not login using ftp, i.e., root by default)
/etc/users
/etc/passwd (information about users)
/etc/group (information about groups)
/etc/host.conf (local host info)
/etc/inetd.conf (services available trhough the INETD TCP/IP super server)
/etc/host.allow
System Start up Files (known as “run-leve
/etc/ftpaccess:
virtual <address> <root|banner|logfile> <path>
Enables the virtual ftp server capabilities. The <address> is the ip address of the virtual server. The second argument specifies that the <path> is either the path to the root of the file system for this virtual server, the banner presented to the user when connecting to this virtual server, or the log- file where transfers are recorded for this virtual server. If the log file is not specified the default log file will be used. All other message files and permissions as well as any other settings in this file apply to all virtual servers.
Utilities, configuration
netconf Configuration utility for Network components.
netstat: Network Status. #netstat -a, -i. -nr,
linuxconf Linux Configuration Utility.
userconf Utility that jumps right to User Data with in LinuxConf
fsconf File System Configuration Utility.
ifconfig Displays networking Information. /sbin/ifconfig -a (#ifconifg dev_name ie eth0, pp0)
/etc/host: Define Host Name and IP addresses.
/etc/httpd/conf: Httpd (Apache Web Server) configuration file
/etc/default/useradd This file is used to define “defaults” of a new user when created w/ useradd
/etc/passwd PassWord file
/etc/shadow Shadow Passwords
/etc/group Lists Group ID’s
Most Used Utilities and “Command Prompt” system utilities are located in /bin
mkdir
ed (editor)
ex (another editor)
login
pwd
ls
kill
ln
echo
domainname
dnsdomainname
hostname
etc..,
Help= [command_name --help] (works for most commands and internal applettes).
Console: Linux like Unix is Multitasking in that more that one “terminal” can be run. Like wise you can use more than one Console. Use Alt + fx (x= number 1 thru 12) to start new or switch between instances of Console.
file properties: drwxrwxrwx (type.owner.group.others)(d=dir or l=sym link, r=read, w=write, x=execute).
ls List contents of current directory
ls -l List contents of current directory in Long Format
ls -a List contents of current directory Including Hiden Files
ls -t List contents of current directory Sorted by Time last Modified
ls -u List contents of current directory Sorted by Time last Accessed
ls -C List contents of current directory in Multicolumns, Sorted Down
ls -F List contents of current directory, but places a Slash (/) after directories and an
Asterisk (*) after executable files.
ls –R List contents of current directory and Lists Subdirectories in All Branches of current dir tree.
*Don’t do this if you don’t have time to wait, Ctrl + Z, X, C or Break, do not work unless you pipe ( | ) to more.
pwd Print Working Directory, prints the absolute path to your current directory location.
mkdir Make Directory, create a Directory in your Current directory.
(a directory can be made else where, but path is needed, ie. mkdir /usr/home/test)
rmdir Remove Directory. Must be empty.
rm Removes files..Unless you use some option switches.. #rm –rf directory_name will delete recursivly, all files and directories (-r) and not prompt for user interaction (f).
cd Change Directory (Linux cd ; C shell, cd ~ ; Bourne shell $home, returns you to your Home Dir)
mv Move files or directories. This is also how you "Rename" a file or dir, (mv NewName)
(to move to Home Dir, mv$HOME/filename.. (the .. keeps file name the same))
cp Copy a file or directory
cp -r Copy Directories and files, Including All Sub-Directories (Recursive Copy)
ln Link File. Referencing a File from Multiple Dirs. (in the dir you want the link type ln then path
to the file and Enter an Alias name for the file)
domainname Displays Domain Name (haven’t seen anything from this).
dnsdomainname Displays Domain Name per DNS, go figure.
hostname Displays Host Name, www.domain_name.tld
chfn Allows users to Change there Full Name.
chsh Allows users to Change there login Shell.
chpasswd1Change many PassWords in a batch format or process.
chmod Change the access mode (permissions) of files. Only the owner may change its mode.
ifconfig Displays networking Information. /sbin/ifconfig -a (#ifconifg dev_name ie eth0, pp0)
ifup ifup device. To start ppp0 (modem) type ifup ppp0, this will start a ppp connection.
ifdown ifdown device. To stop ppp0 (modem), type ipdown ppp0, this will hang up ppp connections.
netstat Network Status. #netstat –a (all info) #netstat –nr (diplay routing table).
route add Add a Route to a network.
df Displays Filesystem Information. –h =human readable format, -I =inode instead of blocks.
last Displays listing of logins, ordered from current to oldest.
set Set variables and processes. Many more options than in DOS. (# help set|more).
uptime Displays the Time, number of current users, how long the system has been Up, and the average system load for the past 5, 10 and 15 mins.
snice Used to change the Scheduling of specified processes.
w Lists the users that are currently logged in and the processes they are running.
watch Watches a running program ( watch [-n seconds] program [arguments].
top Real-time monitor of system performance and running commands or deamons. [exit = Ctrl+C]
ntop Real-time monitoring of Network performance in X11.
vmstat Virtual Memory Statistics.
free Displays the amount of Free and used memory.
ps Snap shot of running Processes.
tload Prints a graph of the current System Load to a specified tty.
users Displays currently logged in Users.
last Displays the Last x number of logins.
chvt Change Virtual Terminals. (# chvt n [number of virtual term to jump to, 1 thru 12).
openvt Opens a new program in a New Virtual Terminal. Not available in all distrabutions.
tty Displays the current Virtual Terminal, i.e., /dev/tty1; /dev/tty3 etc..
useradd Add a new User [useradd –m –c “comment” user_name] Now you need to run passwd as –p doesn’t work. Default user profile is set in /etc/default/useradd.
passwd1 Used to set a PassWord. Root can change any password, a user can change their own. #passwd.
Note:
Adding a user concists of three steps:
Step 1: #useradd -m -c “Full_Name” user_name
Step 2: #passwd user_name
new_password
retype new_password
Step 3:#rm -rf /home/User_Name/Desktop
Step 4: #chmod -v (verbose) (-c, like v, but changes only) -R a+rx Directory_Name
Step 5: #echo “This is the new home of User_Name.tld” >/home/user_name/index.html
ftp File Transfer Protocol
mount Mount “attaches” a device to the operating system, so that it may be accessed.
#mount /dev/hda1 /MountPoint ie, root
#mount -t msdos /dev/fd0 /floppy
#mount -t iso9660 /dev/cdrom /mnt/cdrom
* Temperarly Mounted Devices (/mnt) will be available in /mnt
kill - 9 pid (process No ID) (kill -l lists options and the pid id can be gotten with top (ctrl+c to exit))
pico Pico is a text editor, easiest to use (that I’ve found), use form command prompt.
vi VI is also a text editor, it works like ed (EDitor from OS/2). Difficult to use
cat Display the content of a text file, much like “type file_name” in DOS. #cat file_name.
rpm Redhat Package Manager. Used to install rpm aware programs.
# rpm –ivh file_name.rev_no.rpm
ex “Expand” Vi Improved (Vim), Writes file info to screen Editor. not bad
rvi Another VI, finally figured out how to quit vi’s, enter :qa! enter.
view View contents of a file.
info Displays the Credit and version Information for a file, can be used on executables. Use Ctrl + Z to exit.
fsck ext2 file system utility like chkdsk.
e2fsck Some kind of partition – block repair tool
ln Create Link can have different names but will have the same inode number
ln file_name link_name. ls –i will show the inode numbers.
ln –s Create Symbolic Link ( -s = symlink) form one file to another. Link will then point to origanal file. The symlink can have a different name than the origanal and will have different inode numbers. ln –s file_name link_name.
fdformat Format Utility used to format floppy disks. fdformat /dev/fd0.
quota Displays the drive space Quotas or limits of a given user.
history Displays the History of what is in your keyboard buffer (what you’ve type on the console).
gzip1 Gzip is a utility for compressing files to a *.gz file formate.
gunzip1 Used to “unzip” *.gz compressed files. [gunzip filename; tar –xvf filename]l
tar1 Compression utility for compressing and decompressing *.tar files.
skill Sends a termination or other signal to a Set of running processes.
find The Find command does just that finds files. example: #find index.html / -maxdepth 10
[this statment is: find the file index.html in the root (/) and search a maximum depth of 10 subdirectories (-maxdepth 10)]. [This command is for shit.]
--version Display Version information #command-file_name –version.
Stop:
Web Server: /etc/rc.d/ini.d/httpd.init stop
Linux Server: shutdown –h now
-k don’t really shutdown, only warn
-r reboot after shutdown
-h halt after shutdown (shut off mach.)
-f do a “fast” reboot.
-n do not go through “init” but go down real fast
-c cancel a running shutdown
-t secs: delay between warning and kill signal
(time argument is mandatory! w/o wait use “now”
hault also works
Ctrl + Alt + Del works great for a reboot.
reboot works well too.
Linuxconfig can also serve as a means of shutdown:
linuxconf –shutdown5
Counsole Keyboard Shortcuts:
Ctrl + Esc, Alt + Esc or Tab; Displays a list of all available system commands. (500 to 2900 commands)
Shift + Delete Works like Windows “Cut” command
Shift + Insert Works like Windows “Paste” command
KDE Keyboard Shortcuts:
Ctrl + Alt + Esc activates the Kill utility
Ctrl + f1 Displays Menu ( useful when you loose your mouse, which you will )
Colored display of files and directories at command prompt of 6.0:
light blue: Link files, these are like “shortcuts” to a file that is located elsewhere.
green: Executable Files, that not to say some or most light blue link files can’t be exacted.
dark blue: Directories.
white: Text or ASCII files. Non-Executable.
.sh Files with .sh are Script Files.
Forgot Root PassWord: @ LILO: prompt> type linux single> this will log you in as root, bash$ shell, where you can remove or change the passwd. [use command passwd, Don’t use linuxconf.. Won’t work]
Help File Locations:
man files: /user/man/manx
Apache: /usr/lib/comanche/docs/
Useful Things I’ve Done.
NOTES ON:
Alias:
Alias’ I set each day, as I can’t find the file to edit again. 8-12-99 7am, found it. profile
alias d=’dir –a –l’
alias cl='clear'
alias cls='clear'
alias cp='cp -i'
alias d='dir -a -l|more'
alias dw='dir -x'
alias lf='ls -F'
alias ls='ls --color=always -p -F' or
alias ls=’ls –color=auto -p -F’
alias lsf='ls -F'
alias mv='mv -i'
alias pi='pico'
alias rm='rm -i'
alias df='df -h'
Fail to Load, Lilo:
8-12-99: 3:30am
APM; went to linuxconfg, controlfiles control panel control services and disabled, as well as pcmcia. *Worked NOTE: Don’t confuse APM with AMD (Auto Mount Daemon), which you need!
Unable to initialize hdb? could not find this, unless Linux is picking up CD-ROM as slave IDE from BIOS.
Server Alias Only Used In Virtual Host? *Removed Aliases from netconfg , DNS, but now (8-12-99 7am), something else is not defined or spelled wrong, rebooting to try and read,,, long error, taking lots of reboots.
Adduser: There are “default” configureation files or “templates” that define a new user. These files are located in /etc/default/useradd (useradd being a text file).
You can display these default setting by typing useradd –D.
The command line syntax for adding a user is: #useradd –m –c “Comment (ie Full Name)” –pPass_Word User_Name.
Note: 10.29.99, I’m having trouble “bumping” the passwd file (updating password token). After I’ve created a user at the commnad line, the password is not acctivated. If you use the linuxconf utility, upon leaving you can “Activate Changes”. What’s doing this. At this point the only way to set password is to restart server or after useradd, use passwd at the command prompt to set password. That seems to Activate Token right away.
AddUser Script: 01-04-2000
· #useradd -mc “real_name” -d directory_name.tld user_name
· #rm -rf /home/user_name.tld/Desktop
· #echo “This is the new home of user_name” > /home/user_name.tld/index.html
· #chmod -cR +xr /home/user_name.tld
· #passwd user_name
Appending new VirtualHost to httpd.conf file. (Work in progress, test state only Beta 1)
· #cp /etc/httpd/conf/httpd.conf+newuser.txt /etc/httpd/conf/httpd.conf
·
“GUI’s”
To Start: startx, X, xfree86, XFree86
Confiruragtion: XFree86Config, xf86conifg,
(The above depend on the version number and distribution).
twm Tab Window Manager, very basic, clean /etc/X11/twm
.xinitrc file: twm exec xterm &
fvwm Bob Nation’s manager is a descendant of the twm manager /etc/X11/fvwm
fvwm2 Bob Nation’s also, w/ enhancements like 3D window frames/etc/X11/fvwm2
AfterStep Descendant of or Taken from the NeXTStep OS /etc/X11R6/AfterStep
Config files: /usr/share/afterstep; Docs: #lynx /usr/share/afterstep/doc/afterstep.html
gnome Gnome
/bin, /usr/bin, /usr/X11R6/bin1
kde Stock GUI w/ RedHat (RH) Linux, version 5.2
Icon Files:
GNOME:
/usr/share/pixmaps
Drag ‘n Drop copy with-in a singal window or between windows is done by holding the Ctrl key while dragging. If you don’t use Ctrl, You’ll be MOVEING.
Documentation: /usr/lib/comanche/docs
Vhost: /usr/include/apache/http_vhost.h
/etc/httpd/conf/httpd.conf
Check for Syntax Errors: #httpd –t
Logs:
/etc/log/httpd/error_log : will list reasons for failure
/etc/log/httpd/access_log
/usr/include/apache/http_log.h : and some others.
System Log:
/etc/log/messages : Shows the messages you see during boot.
Also:
/etc/log/boot.log or /var/log/boot.log
It appears you need to chmod a+x directory_name the directory to be offered ( ie. surfmi.net)
Create Test HTTP Page:
Using a text editor like pico, type a simple text string i.e.,
#pico index.html,
Add some text, Save and Close..
Any web browser will now interpet this file as a web page.
Note:
It seems that when you create a Virtual Host in LinuxConf, the directory is created in /home/* and the rights are set to drwxr—xr-x which is the rights I found that you need to display a http “home page”.
Example of httpd.conf
ServerName lynx2.i-is.com
# Listen 3000
# Listen 12.34.56.78:80
Listen 209.254.100.3:80
Listen 209.254.100.3:8080
NameVirtualHost 209.254.100.3
#Landis, Log locations set to default, this is a trial so I don't have #to add them to every Vhost directive.
ErrorLog /etc/httpd/logs/error_log
RefererLog /etc/httpd/logs/referer_log
TransferLog /etc/httpd/logs/access_log
AgentLog /etc/httpd/logs/agent_log
<VirtualHost 209.254.100.3>
ServerAdmin root@localhost
ServerName home.surfmi.net
DocumentRoot /home/home.surfmi.net
ErrorLog /etc/httpd/logs/error_log
RefererLog /etc/httpd/logs/referer_log
TransferLog /etc/httpd/logs/access_log
AgentLog /etc/httpd/logs/agent_log
</VirtualHost>
<VirtualHost 209.254.100.3>
ServerAdmin info@www.classicsbydesign.com
ServerName www.classicsbydesign.com
DocumentRoot /home/classicsbydesign.com
ErrorLog /etc/httpd/logs/error_log
RefererLog /etc/httpd/logs/referer_log
TransferLog /etc/httpd/logs/access_log
AgentLog /etc/httpd/logs/agent_log
</VirtualHost>
<VirtualHost 209.254.100.3>
ServerAdmin info@www.surfmi.net
ServerName www.realracers.com
DocumentRoot /home/realracers.com
</VirtualHost>
<VirtualHost 209.254.100.3>
ServerAdmin info@www.surfmi.net
ServerName www.vensel.com
DocumentRoot /home/vensel.com
ErrorLog /etc/httpd/logs/error_log
RefererLog /etc/httpd/logs/referer_log
TransferLog /etc/httpd/logs/access_log
AgentLog /etc/httpd/logs/agent_log
</VirtualHost>
Example of Vhost section of the httpd.conf file.
Note: you can use wild cards to diclare names in httpd.conf.
ie., ServerName domain_name.tld *.domain_name.tld [I believe this to say www. home. etc….]
[Make sure to set ServerRoot early in this file, this is where the config and log files are.]
ServerRoot /etc/httpd
[Set ErrorLog location, there is a log directory in /var/log/httpd, but is linked from /etc/httpd].
ErrorLog /var/log/httpd [I put them here]
…….
Port 80 [This is the port the server should listen to].
ServerName server.domain.tld [This name is sent back to client]
#IP Address of the Physical Machine, if on the internet this is the “real IP address.
NameVirtualHost xxx.xxx.xxx.xxx [I’m going to use one of my Linux servers, 209.254.100.3]
<VirtualHost xxx.xxx.xxx.xxx>
DocumentRoot /var/log/httpd/ [Directory where the index.html document is for this domain
# I use the users home directory, as that is how I set a domain up.. as a user w/ home directory].
#The first domain listed should be the primary domain if things go bad it’s picked up by default.
ServerAdmin email_address@www.domain_name.tld [infoand errors are mailed to domain
#admins email address].
ServerName www.domain_name.tld [Name of this TopLevelDomain (Virtual Domain)]
ErrorLog /var/log/httpd/error_log
#[no leading “/” would be under the server root to /var/httpd/ set earlier].
TransferLog /var/log/httpd/access_log
#[again no leading / . directory_name to domain_name of the Vdomain which is the name of the #login user_name].
RefererLog /var/log/httpd/referer_log
AgentLog /var/log/httpd/agent_log
#If you use CGI scripts ini this domain
ScriptAlias /cgi-bin/ /var/www/cgi-bin/domain_name.tld/ [this is the path to your CGI scripts].
AddHandler cgi-script .cgi [Handler for CGI Scripts]
AddHandler cgi-script .pl [Handler for Perl Scripts].
</VirtualHost>
Notes:
Things to Look into
daemon: Daemons are programs that are run automatically to perform various system functions.
mars-nwe: MARtin Stover’s NetWare Emulator, lets linux act as NetWare Print and File server.
mcserv: Midnight Commander file management system. Allows remote system to see file system.
apmd: Advanced Power Management Daemon.
amd: AutoMounter Daemon, written for BSD, replaced by am-utils.
gated: GateD is a routing daemon handling routing protocols and replaces RouteD and Egpup.
squid: Squid is a high-performance proxy caching server for web, ftp, gopher and http data.
version: *How to display the Version Information about a given file or prcess. ie kernel version?
c------ In file/directory attibutes, what is the “c” for where a “d” is usually, far left position?
l------- In file/directory attibutes, what is the “l” for where a “d” is usually, far left position? link.
b------ In file/directory attibutes, what is the “b” for where a “d” is usually, far left position?
autopasswd Seems to send script to update passwd file.
* = Found and Written-up. LR
Appendix G Glossary
Alpha
A RISC (Reduced Instruction Set Computer) architecture developed by Digital Equipment Corporation.
ATAPI
An abbreviation for AT Attachement Packet Interface. ATAPI is the protocol by which CD-ROM drives communicate with a computer system over an IDE interface.
Binary
Although the base two-numbering system used by computers is known as binary, the word often refers to the executable form of a program. Contrast with ``source code.''
BIOS
An abbreviation for Basic Input/Output System. On PC-compatible systems, the BIOS is used to perform all necessary functions to properly initialize the system's hardware when power is first applied. The BIOS also controls the boot process, provides low-level input/output routines (hence its name) and (usually) allows the user to modify details of the system's hardware configuration.
Boot
Short for ``bootstrap.'' The process by which a computer starts running an operating system when power is applied.
Boot Diskette
A diskette used to start many Red Hat Linux installations.
Bootstrap
See ``Boot.''
CISC
An abbreviation for Complex Instruction Set Computer. A design philosophy for computers whereby the processor is designed to execute a relatively large number of different instructions, each taking a different amount of time to execute (depending on the complexity of the instruction). Contrast with RISC.
CMOS
Originally an abbreviation for Complementary Metal Oxide Semiconductor -- a semiconductor technology used in many integrated circuits. Now often used to describe the low-level hardware that contains a personal computer's BIOS setting, and the computer's hardware clock.
Cylinder
When referring to disk drives, the number of different positions the disk drive's read/write heads can take over the unit's disk platters. When viewed from above the platters, each head position describes an imaginary circle of different diameters on the platter's surface, but when viewed from the side, these circles can be thought of as a series of cylinders nested within each other, hence the term. See also Geometry.
Daemon
A daemon is a program that runs, without human intervention, to accomplish a given task. For example, lpd is a daemon that controls the flow of print jobs to a printer.
Dependencies
When referring to packages, dependencies are requirements that exist between packages. For example, package foo may require files that are installed by package bar. In this example, bar must be installed, or else foo will have unresolved dependencies. RPM will not normally allow packages with unresolved dependencies to be installed.
Device Driver
Software that controls a device that is connected to, or part of, a computer.
Disk Drive
See Hard Disk.
Disk Druid
Disk Druid is a component of the Red Hat Linux installation program that is used to partition disk drives during the installation process.
Diskette
A small mass storage device in a removable cartridge, meant to be read/written to, in a compatible drive.
Distribution
An operating system (usually Linux) that has been packaged so as to be easily installed.
Domain Name
A domain name is used to identify computers as belonging to a particular organization. Domain names are hierarchical in nature, with each level in the hierarchy being separated from other levels with a period (pronounced ``dot''). For example, Foo Incorporated's Finance department might use the domain name ``finance.foo.com.''
Driver
See Device Driver.
Dual Boot
The act of configuring a computer system to boot more than one operating system. The name is something of a misnomer, as it is possible to boot more than the two operating systems the word ``dual'' implies.
EIDE
An abbreviation for Enhanced Integrated Drive Electronics, which is a newer version of the IDE interface standard and another term for a particular implementation for IDE interfaces. EIDE makes larger and faster disk drives possible; most systems sold today use EIDE.
Errata
Errata is Latin for ``Ooops.'' HYPERLINK "footnotes.html" \l "000008" <FONTSIZE=-28 When software is found to have bugs, quite often the software is fixed, and released as errata. Red Hat Linux is no exception to the rule; we have an Errata web page at HYPERLINK "http://www.redhat.com/errata" http://www.redhat.com/errata .
Extended Partition
A segment of a disk drive that contains other partitions. See Partition.
FAQ
An abbreviation for Frequently Asked Questions. Linux information is often presented in the form of lists of questions and answers called FAQs.
fdisk
fdisk is a utility program that is used to create, delete or modify partitions on a disk drive.
Filesystem
A filesystem is the method by which information is stored on disk drives. Different operating systems normally use different filesystems, making it difficult to share the contents of a disk drive between two operating systems. However, Linux supports multiple filesystems, making it possible, for example, to read/write a partition dedicated to Windows.
Floppy
A somewhat historical term for a small mass storage device in a removable cartridge, meant to be read/written to in a compatible drive. See ``diskette.''
Formatting
The act of writing a filesystem on a disk drive.
FQDN
An abbreviation for Fully Qualified Domain Name. An FQDN is the human-readable name that includes a computer's hostname and associated domain name. For example, given a hostname of ``foo,'' and a domain name of ``bar.com,'' the FQDN would be ``foo.bar.com.''
FTP
An abbreviation for File Transfer Protocol. Also the name of a program that, as the name implies, permits the copying of files from one system on a network to another.
Gateway
In networking terms, refers to a device that connects one or more computers on a network to other networks. The device may be specialized hardware (such as a router), or may be a general-purpose computer system configured to act as a gateway.
Geometry
When referring to disk drives, the physical characteristics of the disk drive's internal organization. Note that a disk drive may report a ``logical geometry'' that is different from its ``physical geometry,'' normally to get around BIOS-related limitations. See also Cylinder, Head and Sector.
GID
Short for Group ID. The means by which a user's membership in a group is identified to various parts of Red Hat Linux. GIDs are numeric, although human-readable names are stored in the /etc/group file.
Group
Groups are a way of assigning specific access rights to certain classes of users. For example, all users working on Project X could be added to group xproj. System resources (such as disk space) devoted to Project X could then be configured to permit only members of xproj full access.
Hard Disk
A hard disk contains rotating magnetic media (in the shape of disks) that spin rapidly. Small heads float over the surface of each disk, and are used to write to and read from the disk as it rotates.
Head
When referring to disk drives, the number of read/write heads within a disk drive. For each platter in a disk drive, there are normally two heads for each platter -- one for each surface -- although one surface may go unused. See also Geometry.
Hostname
A hostname is a human-readable string of characters used to identify a particular computer system.
I18n
See Internationalization.
IDE
An abbreviation for Integrated Drive Electronics, which is the name of a standard interface used to connect primarily disk and CD-ROM drives to a computer system. See also ``EIDE'' and ``ATAPI.''
Intel
Company responsible for producing the microprocessors that most commonly appear in PC-compatible personal computers. These processors include the 80386, 80486, Pentium, Pentium Pro, and Pentium II.
Internationalization
The practice of designing and writing programs that can be easily configured to interact with the user in more than one language. Often referred to as ``i18n,'' due to the number of letters between the starting ``i'' and the ending ``n.''
IP Address
IP addresses are the method by which individual computer systems (or from a more strictly accurate interpretation, the network interfaces on those computer systems) are identified on a TCP/IP network. All IP addresses consist of four number blocks, each ranging from 0 to 255, and separated by periods.
Kernel
The central part of an operating system upon which the rest of the operating system is based.
Library
When speaking of computers, refers to a collection of routines that perform operations which are commonly required by programs. Libraries may be shared, meaning that the library routines reside in a file separate from the programs that use them. Library routines may also be ``statically linked'' to a program, meaning that copies of the library routines required by that program are physically added to the program. Such statically linked binaries do not require the existence of any library files in order to execute. Programs linked against shared libraries will not execute unless the required libraries have been installed.
LILO
A commonly-used bootstrap loader for Linux systems based on an Intel-compatible processor.
Linus Torvalds
Created Linux in 1991 while a university student.
Linuxconf
A versatile system configuration program written by Jacques Gelinas. Linuxconf provides a menu-based approach to system configuration via several different user interfaces.
Linux
A full-featured, robust, freely-available operating system originally developed by Linus Torvalds.
Logical Partition
A partition that exists within an extended partition. See also ``partition'' and ``extended partition.''
Master Boot Record
The master boot record (or MBR) is a section of a disk drive's storage space that is set aside for the purpose of saving information necessary to begin the bootstrap process on a personal computer.
MBR
See ``Master Boot Record.''
Memory
When referring to computers, memory (in general) is any hardware that can store data for later retrieval. In this context, memory usually specifically refers to RAM.
MILO
A commonly-used bootstrap loader for Linux systems based on the Alpha processor.
Module
In Linux, a module is a collection of routines that perform a system-level function, and may be dynamically loaded and unloaded from the running kernel as required. Often containing device drivers, modules are tightly bound to the version of the kernel; most modules built from one version of a kernel will not load properly on a system running another kernel version.
Mount Point
The directory under which a filesystem is accessible after being mounted.
Mount
The act of making a filesystem accessible to a system's users.
Nameserver
In TCP/IP networking terms, a nameserver is a computer that can translate a human-readable name (such as ``foo.bar.com'') into a numeric address (such as ``10.0.2.14'').
Netmask
A netmask is a set of four number blocks separated by periods. Each number is normally represented as the decimal equivalent of an eight-bit binary number, which means that each number may take any value between 0 (all eight bits cleared) and 255 (all eight bits set). Every IP address consist of two parts (the network address and the host number). The netmask is used to determine the size of these two parts. The positions of the bits that are set in the netmask are considered to represent the space reserved for the network address, while the bits that are cleared are considered to represent the space set aside for the host number.
NFS
An abbreviation for Network File System, NFS is a method of making the filesystem on a remote system accessible on the local system. From a user's perspective, an NFS-mounted filesystem is indistinguishable from a filesystem on a directly-attached disk drive.
Operating System
A collection of software that controls various resources of a computer.
Packages
Files that contain software, and written in a particular format that enables the software to be easily installed and removed.
PAM
An acronym for Pluggable Authentication Modules. PAM is an authentication system that controls access to Red Hat Linux.
Partition
A segment of a disk drive's storage space that can be accessed as if it was a complete disk drive.
Partition Table
The partition table is a section of a disk drive's storage space set aside to define the partitions that exist on that disk drive.
Partition Type
Partitions contain a field that is used to define the type of filesystem the partition is expected to contain. The partition type is actually a number, although many times the partition type is referred to by name. For example, the ``Linux Native'' partition type is 82. Note that this number is hexadecimal.
PC Card
See PCMCIA.
PCMCIA
Acronym for Personal Computer Memory Card International Association. This organization produced a series of standards that define the physical, electrical and software characteristics of small, credit card-sized devices that can contain memory, modems, network adapters and more. Also known as PC Cards, these devices are mainly used in laptop computers (although some desktop systems can use PCMCIA cards, too).
PCMCIA Support Diskette
A diskette required for Red Hat Linux installations that require the use of a PCMCIA device during the install.
Permissions
The set of identifiers that control access to files. Permissions consist of three fields: user, group, and world. The user field controls access by the user owning the file, while the group field controls access by anyone matching the file's group specification. As the name implies, the world field controls access by everyone else. Each field contains the same set of bits that specify operations that may or may not be performed, such as reading, writing and executing.
PLIP
An abbreviation for Parallel Line Internet Protocol. PLIP is a protocol that permits TCP/IP communication over a computer's parallel port using a specially-designed cable.
POSIX
A somewhat mangled abbreviation for Portable Operating System Interface. A set of standards that grew out of the UNIX operating system.
Process
A process (in somewhat simplistic terms) is one instance of a running program on a Linux system.
PS/2 Mouse
A PS/2 mouse gets its name from the original computer in which this type of mouse was first used -- the IBM PS/2. A PS/2 mouse can be easily identified by the small, round connector at the end of its cable.
RAM
An acronym for Random Access Memory. RAM is used to hold programs while they are being executed, and data while it is being processed. RAM is also volatile, meaning that information written to RAM will disappear when the computer's power is turned off.
Reboot
To restart the boot process. See also ``Boot.''
Red Hat Software
A North Carolina software company. Produces and markets sofware for the Linux operating system, including Red Hat Linux.
Rescue Diskette
A diskette containing a rudimentary system environment. As the name implies, a rescue diskette is normally used in an attempt to ``rescue'' an ailing system from the necessity of re-installing the entire operating system.
RISC
An abbreviation for Reduced Instruction Set Computer. A design philosophy for computers whereby the processor is optimized to execute a relatively small number of different instructions in a predictably small amount of time. Contrast with CISC.
ROM
An abbreviation for Read Only Memory. ROM is used to hold programs and data that must survive when the computer is turned off. Because ROM is non-volatile; data in ROM will remain unchanged the next time the computer is turned back on. As the name implies, data cannot be easily written to ROM; depending on the technology used in the ROM, writing may require special hardware, or may be impossible. A computer's BIOS may be stored in ROM.
Root
The name of the login account given full and complete access to all system resources. Also used to describe the directory named ``/''as in, ``the root directory.''
RPM
An abbreviation that stands for Red Hat Package Manager. RPM is also the name of a program that enables the installation, upgrading and removal of packages.
SCSI
An abbreviation for Small Computer System Interface, SCSI is a standard interface for connecting a wide variety of devices to a computer. Although the most popular SCSI devices are disk drives, SCSI tape drives and scanners are also common.
Sector
When referring to disk drives, the number of fixed-size (normally 512 byte) areas that can be accessed by one of the disk drive's read/write heads, in one rotation of the disk, without that head changing position. See Also Geometry.
Serial Mouse
A serial mouse is a mouse that is designed to be connected to a computer's serial port. A serial mouse can be easily identified by the rectangular-shaped connector at the end of its cable.
setgid
A system call that can be used to set the GID of a process. Programs can be written using setgid such that they can assume the group ID of any group on the system.
setuid
A system call that can be used to set the UID of a process. Programs can be written using setuid such that they can assume the user ID of any process on the system. This is considered a possible security problem if a program is ``setuid root.''
Shadow Password
Normally, each user's password is stored, encrypted, in the file /etc/passwd. This file must be readable by all users so that certain system functions will operate correctly. However, this means that copies of user's encrypted passwords are easily obtained, making it possible to run an automated password-guessing program against them. Shadow passwords, on the other hand, store the encrypted passwords in a separate highly-protected file, making it much more difficult to crack passwords.
SILO
A commonly-used bootstrap loader for Linux systems based on the SPARC processor.
SLIP
An acronym for Serial Line Internet Protocol. SLIP is a protocol that permits TCP/IP communication over serial line (typically over a dial-up modem connection).
source code
The human-readable form of instructions that comprise a program. Also known as ``sources.'' Without a program's source code, it is very difficult to modify the program.
SPARC
A RISC (Reduced Instruction Set Computer) architecture developed by Sun Microsystems.
Swap
Also known as ``swap space.'' When a program requires more memory than is physically available in the computer, currently-unused information can be written to a temporary buffer on the hard disk, called swap, thereby freeing memory. Some operating systems support swapping to a specific file, but Linux normally swaps to a dedicated swap partition. A misnomer, the term swap in Linux is used to define damand paging.
System Call
A system call is a routine that accomplishes a system-level function on behalf of a process.
TCP/IP
An abbreviation for Transmission Control Protocol/Internet Protocol, TCP/IP is the name given to the networking standard commonly used on the Internet today.
Torvalds, Linus
See Linus Torvalds.
UID
Short for User ID. The means by which a user is identified to various parts of Red Hat Linux. UIDs are numeric, although human-readable names are stored in the /etc/passwd file.
UNIX
A set of Linux-like operating systems that grew out of an original version written by some guys at a phone company. HYPERLINK "footnotes.html" \l "000009" <FONTSIZE=-29
Unmount
The act of revoking access to a filesystem. (Note that the program that unmounts filesystems is called umount.)
Virtual Console
Virtual consoles provides multiple ``screens'' on which a user may log in and run programs. One screen is displayed on the computer's monitor at any given time; a key sequence is used to switch between virtual consoles.
Widget
A standardized on-screen representation of a control that may be manipulated by the user. Scroll bars, buttons, and text boxes are all examples of widgets.
X Window System
Also known as ``X,'' this graphical user interface provides the well-known ``windows on a desktop'' metaphor common to most computer systems today. Under X, application programs act as clients, accessing the X server, which manages all screen activity. In addition, client applications may be on a different system than the X server, permitting the remote display of the applications graphical user interface.
XFree86
A free implementation of the X Window System.
Appendix G Glossary is taken from http://www.redhat.com/corp/support/manuals/RHL-6.0-Manual/install-guide/manual/doc128.html
2.1 Glossary of Terms
In this document a lot of acronyms are used. Here are the most important acronyms and a brief explanation:
DBM
DataBase Management, a library of functions which maintain key-content pairs in a data base.
DLL
Dynamically Linked Library, a library linked to an executable program at run-time.
domainname
A name "key" that is used by NIS clients to be able to locate a suitable NIS server that serves that domainname key. Please note that this does not necessarily have anything at all to do with the DNS "domain" (machine name) of the machine(s).
FTP
File Transfer Protocol, a protocol used to transfer files between two computers.
libnsl
Name services library, a library of name service calls (getpwnam, getservbyname, etc...) on SVR4 Unixes. GNU libc uses this for the NIS (YP) and NIS+ functions.
libsocket
Socket services library, a library for the socket service calls (socket, bind, listen, etc...) on SVR4 Unixes.
NIS
Network Information Service, a service that provides information, that has to be known throughout the network, to all machines on the network. There is support for NIS in Linux's standard libc library, which in the following text is referred to as "traditional NIS".
NIS+
Network Information Service (Plus :-), essentially NIS on steroids. NIS+ is designed by Sun Microsystems Inc. as a replacement for NIS with better security and better handling of _large_ installations.
NYS
This is the name of a project and stands for NIS+, YP and Switch and is managed by Peter Eriksson <peter@ifm.liu.se>. It contains among other things a complete reimplementation of the NIS (= YP) code that uses the Name Services Switch functionality of the NYS library.
NSS
Name Service Switch. The /etc/nsswitch.conf file determines the order of lookups performed when a certain piece of information is requested.
RPC
Remote Procedure Call. RPC routines allow C programs to make procedure calls on other machines across the network. When people talk about RPC they most often mean the Sun RPC variant.
YP
Yellow Pages(tm), a registered trademark in the UK of British Telecom plc.
TCP-IP
Transmission Control Protocol/Internet Protocol. It is the data communication protocol most often used on Unix machines.
Glossary of Terms taken from: http://www.redhat.com/mirrors/LDP/HOWTO/NIS-HOWTO-2.html#ss2.1
Appendix A
Under UNIX there are some widely used applications to archive and compress files. tar is used to make archives---it's like PKZIP or Winzipbut it doesn't compress, it only archives.
To make a new archive:
$ tar -cvfp archive_name.tar_file file_and_or_a_directory
This is how I Archive web site directories on WWW Server:
tar -cp –file=home.tar *.*
To extract files from an archive:
$ tar -xpvf archive_name.tar [file and or directory] * Make sure you are in the Directory Above the one contained in your Archivem, before you extract… ie.. achive /home you need to be in the root if /home is contained in the Archive.
To list the contents of an archive:
$ tar -tf archive_name.tar | less1
You can compress files using compress, which is obsolete and shouldn't be used any more, or gzip:
This creates a compressed file with extension .Z (compress) or .gz (gzip). These programs can compress only one file at a time.
$ compress <file>
$ gzip <file>
To decompress:
$ compress -d <file.Z>
$ gzip -d <file.gz>
Here's how to list the contents of a .tar.gz archive:
$ tar -ztf <file.tar.gz> | less
Tar Options:
-c Create new archive
-v Run in Verbose mode
-f The arugment that Follows is the archive name
-p Perserve user/group ownership and rights
Un”g”zip and Untar in one step:
gunzip FileName.gz; tar -xfv FileName (less the .gz sometimes no v)
FTP: Files can be gzip’d and tar’d during ftp download by:
<fixes@XFree86.org>.
Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml,v 3.103 2000/03/08 20:36:43 dawes Exp $
0- ** All file transfers are logged. If you object to this, logout now. **
230-
230- Files may be retrieved in gzip'd form by adding the extension '.gz'.
230- Directories may be retrieved as a tar file by adding '.tar'. These
230- tar files can also be gzip'd -- add '.tar.gz'.
Commands:
get file_name [get (download, receive) a file from a remote computer]
put file_name [send a file to a remote computer]
mget file_name [*.html or *.*] [Get multiple files, you’ll have to answer prompt for each]
mput file_names [*.*], put multiple files [you’ll have to answer prompt for each file]
cd Change Directory on remote computer
lcd Change Directory on Local computer
ls Most ls command work for remove computer.