Me in IT UNIX/Linux consultancy

There are a few ways to start (and stop) daemons at specific runlevels. For Fedora you could use modify how Apache (httpd) is started:

chkconfig --level 4 httpd on

This is a simple command line tool to tell the the startup facility to enable (on) the Apache (httpd) daemon at runlevel 4 (--level 4). Works great and fast, but the script httpd must have some parameters in the file to let chkconfig know what to do with it:

The lines chkconfig and description are mandatory. In this example, the chkconfig line tells the startup facility to start in runlevel 4, with a "priority" of 85. This priority can be seen with ls /etc/rc4.d. The numbers of the startup script represent the order of how they are started.

ln -s /etc/init.d/httpd /etc/rc4.d/S85httpd

A much simpler, more simplistic method to start Apache. This command symbolically links /etc/rc4.d/S85httpd to the startup script of Apache. Don't forget to also stop the daemons with this set of links:

ntsysv

A text-based graphical menu to enable or disable services.

serviceconf and system-config-services

A graphical interface to enable or disable services.

Booting a computer to run Linux is quite a complex procedure. Happily it's understandable, so correctable when things break.

1. P.O.S.T. The computer is powered on, the computer shows you a screen to configure some basic settings, the BIOS and tests itself. Not much Linux here!
2. Boatloader Grub, Lilo or some other boot loader is started. The bootloader is a small piece of code that is able to start loading the kernel. Mostly you will have some options to edit boot parameters, like "single" to start in single user mode.
3. The kernel This is where Linux starts, you'll see all kinds of (cryptic) messages scrolling over your screen. Use dmesg to see them again after booting.
4. INIT The process "init" is started, the first process on a Linux machine. Init read /etc/inittab and launches RC.
5. RC This facility is responsible for starting all the daemons and programs that make Linux a server.

Bootloader errors and fixes

The bootloader could point to a kernel that's not there, or adds a boot parameter that incorrect. A.k.a. a typo. Review your Grub or Lilo configuration and try again. Grub is a lot easier to debug, is has a minimalistic shell included.

Kernel errors and fixes

You could have built a kernel that's not suitable for your computer. I hope you have left and old kernel on your system, use Grub to select that kernel and boot it.

Init errors and fixes

Init is quite simple, it reads /etc/inittab and starts RC. When you have "played around with" /etc/inittab and made a typo somewhere, you might need to boot of a CD to fix the typo.

RC errors and fixes

This is the part where many "errors" can occur, like: "Apache is not starting". Review the startup script in /etc/init.d, review that there a script and it has no errors in it. Also read the article about controlling daemons.

These modern day computers are so fast, that "cat"-ting a file scrolls by at an unreadable speed!

Here is a small shell script to slowly cat files or standard input:

And here is how to use it:

Amazing what computers can do!

I tried to explain what "chrooting" is to a group of starting Linux gurus. It seemed rather difficult to explain. So, maybe an illustrated article will explain what chroot is.

From chroot's manpage:

And in my own words:

Here is an example of how chroot can be used to reset a root password on an existing system. (Even works when the bootloader (grub) has a password set.)

1. Insert a linux boot or install CD/DVD and make the computer boot from that cd.
2. When the CD boots and starts the installer, hit [CTRL]+[ALT]+[F2] to go to a shell.
3. Now that you have a shell available, you must mount the / (maybe /usr too) directory. Mostly you don't know what directory was the / directory, so you will end up mounting an unmounting a few times. mkdir /mnt/a && mount /dev/sda5 /mnt/a && mount /dev/sda3 /mnt/a/usr
4. When you have the required mountpoints mounted, execute a chroot, like this: chroot /mnt/a /bin/sh
5. Now you can execute passwd, which is actually /mnt/a/usr/bin/passwd. The password will be updated in /etc/shadow, which is actually /mnt/a/etc/shadow

Here is a screenshot to illustrate the procedure: (click to enlarge)

If you are a normal (non-root) user on Fedora Core 9, you are able to reboot a machine without the usage of a password. Reboot initiates all kind of scripts that should normally be run as root, while "reboot" does not have a set user id bit set:

From the man page of consolehelper I find:

And in /etc/pam.d/reboot there is:

And from the manpage of pam_console.so:

So; reboot is permitted by non-root users when they are logged into the console. To test this, login to a machine, try "reboot":

The "set user id"-bit (or setuid-bit) is a potentially dangerous permission type. Wrong usage of setuid can result in unauthorized access to your system.

What it means

When a setuid bit is set to an executable, the script will be executed as if it was executed by the owner of the file. So for example this script has a setuid bit set:

This script may be executable by anybody. When executed by the user "robert" for example, it will inherit permissions as if it was executed by root.

Imagine that this script contains the command "reboot"; in that case anybody would be able to reboot the machine.

How you can set it

Very easy:

or

What you can do with it

Here is a small demonstration, first showing that a user can't write to /etc/passwd.

Now set the setuid bit:

With the setuid bit on, the user is able to write to /etc/passwd:

See the dangerous situation we have just created? Undo it by executing # chmod u-s /bin/echo.

How to detect (and resolve) it

Please notice that there are many files on a system that have setuid bits, like:

• /bin/mount - because a user needs to be able to mount a cdrom or floppy.
• /bin/ping
• /usr/bin/crontab

Most people on the windows platform know Cygwin. ("Cygwin is a Linux-like environment for Windows.") As I never use Windows, I feared programs like these, but it turns out cygwin is quite usable. It's even possible to run shell scripts that normally run on my Mac OS X machine.

Download the installer, select all packages you want. (Don't worry, all "generic" tools (ls, cd, grep, awk, ps, bash) are installed by default.) I added "openssh", "netcat", "xterm" and some others. Dependencies will be resolved automatically. The installer downloads everything. You can run the installer again to add extra packages.

You end up with a "Cygwin" icon. Double click it to start your terminal. It's not really a terminal, but looks quite like it.

Some things are strange or missing, like "top" that's missing, permissions (ls -al) look strange, just as the directory structure. But; take some distance from these details and conclude that you have "bash" running on your windows machine!

Have you ever used the command comm? It's a Linux command used to compare two (sorted) files. Comm produces three columns of output:
1: Lines only in file 1.
2: Lines only in file 2.
3: Lines in bothe files.

You can surpress columns by using options like "-1", "-2", "-12" and so on.

Imagine file 1 contains:

And file 2 contains:

Than these options (left) would produce this output (right):

Option	output	explanation
-1	ACD	Show lines only in file 2 and in both files
-2	ABC	Show lines only in file 1 and in both files
-3	BD	Show lines in file 1 and in file 2, but not in both files
-12	AC	Show lines in both files
-13	D	Show lines only in file 2
-23	B	Show lines only in file 1
-123	(no output)	Surppress all columns

When you are new to Linux or don't use Linux on a daily basis, finding out how file permissions work can be challenging. Here is an as short as possible guide, which can be applied on UNIX, Linux, Mac OS X, FreeBSD, OpenBSD, and other UNIX-like operating systems. We'll call those systems *nix in this guide.

*nix splits permissions in thee groups for files and directories:

1. Owner This is the person/account that owns the file.
2. Group This refers to a set of users. 1 or more persons/accounts can be member of a group.
3. World If you'r not the Owner, and not part of a Group for a specific file or directory, you automatically match World. Normally the permissions given to World, are restricted.

Besides ownership of files and directories, certain permissions can be given as well:

1. Read The entity (Owner, Group or World) is allowed to read a file.
2. Write The entity is allowed to write a file, or to create files in the directory for which these permissions are set.
3. Execute The entity is allowed to execute the file (scripts or binaries) or to change into this directory.

These permissions are set using chmod. (Change Mode.) Ownsership of file is altered with chown. (Change Ownser)

Chmod wants to know what permissions you give to a file or directory. This value is built up on four fields.

The zeroth field represents the special bits. (Set User id, Set Group id and Stikcy bit, see below.) Most users will not set this bit, which makes it "0" by default, which means: "No special permissions set."
The first field represents the permissions you give to the Owner.
The second field represents the permissions you give to the Group.
The third fiels represents the permissions you give to the World.

Chmod uses numerical arguments to set permissions, to illustrate it a bit: chmod 750 myscript.sh would change permissions for the file myscript.sh.

Read permissions equals a value of 4.
Write permissios equals a value of 2.
Execute permissions equals a value of 1.

Add the numbers representing the permissions you'd like to give to a Owner, Group or World.

So here is a list of common permissions:

• 750 - The Owner may read, write and execute. The Group may read and execute. (but not write) The world may not do anything with this file.
• 755 - Same as above, but the world may now also read and execute the file.
• 700 - The Owner may do everything, the Group and the world may not do anything.
• 640 - The Owner may read and write, the Group may read and the world may not do anything.
• 644 - Same as above, but the world may now also read the file.
• 600 - The Owner may read and write, the rest may not do anything.

Some "weird" permissions, mostly because they are broken or very rare:

• 000 - Nobody may do anything with this file. Effectively archive the file. Maybe removing the file would be more appropriate.
• 007 - The Owner and Group can't do anything, but the World can. I can't think of a situation where this would apply.
• 100 and 300 - The Owner may execute but not read, so the execute will not work.
• 200 - The owner may write, but not read. The only situation I could imagine is a logfile where some application may write to, but is not allowed to read the file.

There are some special permissions you can give, these permissions go into the zeroth field. You'd use chmod like this to set no special permissions: chmod 0750 myscript.sh.

1. Sticky bit A value of 1. This bit is commonly set to directories and means that you may only remove file in such a directory that are owned by you. The filesystem /tmp is commonly set with that bit; everyone can write there, but you can only remove/rename files that are owned by yourself.
2. Set Group id A value of 2. The file is executed as the Group of the file. Some groups have quite some premissions. Imagine /bin/rm (to remove files and directories) having a Set Group id bit, all users in the Group of /bin/rm may remove a whole lot of files. When you are using Set User id or Set Group id bits, you should be very sure you know what you are doing.
3. Set User id A value of 4. If this permission is given, the program is executed as the Ownser of the file. Could be dangerous; think of a PHP script that tries to reboot a machine...

So 4750 would mean the file may be executed by the owner and the group, and will be executed as the owner.

Imagine a script would have 4775 permissions and would be owned by root:users; a user could edit the script, and the world could execute it with roots permission!

Just to remind you once more; Set Group or User id bits are dangerous, know what you are doing when using them!

When you would like to use TFTP on your Mac OS X machine, take these simple steps:

1. Change /System/Library/LaunchDaemons/tftp.plist Quite simple; remove two lines <key>Disabled</key> and <true/>. Besides that, I added the -l option with <string>-l</string>, but that's optional.
2. Load tftp.plist into launchd The command launchdctl load /System/Library/LaunchDaemons/tftp.plist will do that.
3. Monitor /var/log/system.log With the command tail -f /var/log/system.log

Now place the required files in /private/tftpboot and you are done!