ServerBuddies Support Blog

restricted deletion flag or sticky bit is a single bit

The restricted deletion flag or sticky bit is a single bit, whose interpretation depends on the file type. For directories, it prevents unprivileged users from removing or renaming a file in the directory unless they own the file or the directory; this is called the restricted deletion flag for the directory, and is commonly found on world-writable directories like /tmp.

For regular files on some older systems, the bit saves the program’s text image on the swap device so it will load more quickly when run; this is called the sticky bit.

The letters rwxXst select file mode bits for the affected users: read (r), write (w), execute (or search for directories) (x), execute/search only if the file is a directory or already has execute permission for some user (X), set user or group ID on execution (s), restricted deletion flag or sticky bit (t). Instead of one or more of these let-ters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file’s group (g), and the permissions granted to users that are in neither of the two preceding categories (o).

A numeric mode is from one to four octal digits (0-7), derived by adding up the bits with values 4, 2, and 1. Omitted digits are assumed to be leading zeros. The first digit selects the set user ID (4) and set group ID (2) and restricted deletion or sticky (1) attributes. The second digit selects permissions for the user who owns the file: read (4), write (2), and execute (1); the third selects permissions for other users in the file’s group, with the same values; and the fourth for other users not in the file’s group, with the same values.

Only the person who created the file within a directory may delete it, even if other people have write permission. You can turn it on by typing:

Query/enable (E)IDE 32-bit I/O support using hdparm

Check your current disk status.

-c Query/enable (E)IDE 32-bit I/O support. A numeric parameter can be used to enable/disable 32-bit I/O support: Currently sup-ported values include 0 to disable 32-bit I/O support, 1 to enable 32-bit data transfers, and 3 to enable 32-bit data trans-fers with a special sync sequence required by many chipsets.

The value 3 works with nearly all 32-bit IDE chipsets, but incurs slightly more overhead. Note that “32-bit” refers to data transfers across a PCI or VLB bus to

ln: Make links between files

A “hard link” is another name for an existing file; the link and the original are indistinguishable. Technically speaking, they share the same inode, and the inode contains all the information about a
file–indeed, it is not incorrect to say that the inode _is_ the file. On all existing implementations, you cannot make a hard link to a directory, and hard links cannot cross file system boundaries. (These
restrictions are not mandated by POSIX, however.)

“Symbolic links” (”symlinks” for short), on the other hand, are a special file type (which not all kernels support: System V release 3 (and older) systems lack symlinks) in which the link file actually
refers to a different file, by name.

`ln’ makes links between files. By default, it makes hard links; with the `-s’ option, it makes symbolic (or “soft”) links. Synopses:

* If two file names are given, `ln’ creates a link to the first file from the second.

* If one TARGET is given, `ln’ creates a link to that file in the current directory.

Example:

LiteSpeed Web Server Installation Steps

Installation Instructions for LiteSpeed Web Server.

Download From : http://www.litespeedtech.com/litespeed-web-server-downloads.html

1. Extract the package at convinent location by using

or

if you are not using the GNU tar

2. Type

3. If you want to install to system directory, you need to become root first.

Type

4. Follow the instruction on the screen.

Verifying Installed Packages

Over the course of a system’s normal usage, files get changed. This could be as innocent as simply changing a configuration file in the /etc directory or as problematic as a file being corrupted by a power failure. To assist in the detection of these changes, RPM allows users and administrators to verify the integrity of an installed package.

The command

or

Will verify all installed packages. RPM then computes the MD5 checksum of all files on the disk and compares them to the stored MD5 sums from the original RPMs. The output of the command is a line indicating any files that differ from the versions that were originally installed and a code indicating how the file has changed.