{.}

just some of the things i keep having to look up. . .

hostname stuff

vi etc/hosts
hostname [zonefile.net]
cat /etc/HOSTNAME
vi /etc/sysconfig/network
service xinetd restart
cat /proc/sys/kernel/hostname

named stuff

named-checkzone zonefile.net ./zonefile.net.db
named-checkconf
dig soa zonefile.net

package stuff

packages, list: rpm -qa

runlevel stuff

runlevels:
Runlevel 0: Halt System - To shutdown the system
Runlevel 1: Single user mode
Runlevel 2: Basic multi user mode without NFS
Runlevel 3: Full multi user mode (text based)
Runlevel 4: unused
Runlevel 5: Multi user mode with Graphical User Interface
Runlevel 6: Reboot System

Runlevels 1 and 2 are generally used for debugging purposed
only, and are not used during normal operations. Most desktop
linux distributions boot into runlevel 5, which starts up the
Graphical Login Prompt. This allows the user to use the system
with X-Windows server enabled. Most servers boot into runlevel
3, which starts the text based login prompt

service stuff

services: chkconfig –list, chkconfig –help
service –status-all|more
chkconfig –level 35 named on
chkconfig –add mailman

service saslauthd start

if some apache-owned process is hanging around causing an address already in use error, try
netstat -A inet -lnp
lsof -i tcp:443

useradmin stuff

mkpasswd uname

where things live
mailman: /var/mailman
dbs: /var/lib/mysql

note: this is all fairly specific to my difficulty in adapting from years of freebsd use to linux. another post has some more general unix tips that somehow never stick in my head. (ironically, typing these entries up is good memorization practice.) what would happen if information architecture principles were applied to formal unix documentation? i suppose the world would come to an end.

Posted in geekery, unix. You may comment on this entry.