It's important to get this bit right: .bashrc is executed every time a new shell is created. Open a new terminal window, it's executed.

.profile, on the other hand, is executed only once at log-in. This means that if you're going to add a path to PATH, this is the place to do it. Otherwise, if you add, say your personal script and executable subdirectory to the end of PATH in .bashrc, then after a while you're going to see that PATH has got a huge number of instances of "~/bin" tacked onto the end of it. This is not what you want.

To customize your prompt, see man bash and search for “PROMPTING” where you will see a bunch of specifiers. My prompt on Tru64 is established thus...

	PS1="\u@vastru64:\w> "

This shows up as:

	rbateman@vastru64:~/vgp-3.1.1/src> (first command-line character comes here)

I mistakenly created a bad kernel that became the default to which grub would boot (automatically). In figuring this out, I discovered not only how to eliminate the bad kernel, but also how to manage the grub menu.

Menu

This is as straightforward as it appears in the file /boot/grub/menu.lst: just eliminate the entries that don’t rhyme with what you want, reorder them, etc. and change the default at the top of this file to the 0-based nth item you want to be the default. The timeout is, of course, the number of seconds without interaction until the default is taken with confirmation.

	# Modified by YaST. Last modification on Fri May 18 16:39:17 MDT 2007
	default 2
	timeout 8
	gfxmenu (hd01)/boot/message

	title openSuSE 10.2 - 2.6.18.8-0.3
	   root (hd01)
	   kernel /boot/vmlinuz 2.6.18.8-0.3-default root=/dev/sda vga=0x31a showopts \
	      ide=normal apm=off noresume nosmp noapic maxcpus=0 edd=off
	   initrd /boot/initrd-2.6.19.8-0.3-default

	title Failsafe -- openSuSE 10.2 - 2.6.18.8-0.3
	   root (hd01)
	   kernel /boot/vmlinuz 2.6.18.8-0.3-default root=/dev/sda vga=normal showopts \
	      ide=nodma apm=off acpi=off noresume nosmp noapic amxcpus=0 edd=off
	   initrd /boot/initrd-2.6.19.8-0.3-default

	title openSuSE 10.2
	   root (hd01)
	   kernel /boot/vmlinuz root=/dev/sda vga=0x31a resume=/dev/sda1 splash=silent showopts
	   initrd /boot/initrd-2.6.19.8-0.3-default

	title Floppy
	   rootnoverify (hd0.0)
		 chainloader (fd0)+1
	.
	.
	.

The booting kernel...

In the directory above, /boot, two links, initrd and vmlinuz, need to be made to the corresponding files of the kernel you list as default in the menu. In my case, because I was tossing the last kernel I mistakenly built (and that didn’t work), I had to redo these links. Now I’m set because my box comes up and by default chooses the right kernel, the one with the latest NVIDIA driver linked in to support my 20" wide-aspect monitors.

From /sbin, use lspci to get a list of PCI devices, their names, model numbers, etc. For example, on my SuSE host on IBM hardware, I have the following video card:

	russ@taliesin:~> /sbin/lspci | grep VGA
	01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 TurboCache(TM)] (rev a1)

This way, I now know that I’m running an NVIDIA 6200 and can communicate that to someone else who wants to know a good card to get that will sustain two monitors.

lspci -v gets you more still.

Most packages (products, software, projects, etc.) that you encounter that are of any consequence have an associated script that’s dang handy for what it does. It’s called the “config” script. I’m not talking about the one you run before typing make (in fact, I consume it from configure.ac as I will show in a moment), but what you distribute with your product so that consumers can inquire about fundamental and crucial aspects of your product including where it’s installed, where its associated header files and libraries are (if any), the prefix to the root of where these things might be happening, etc.

For example, where is PHP on your box? On Windows, I used to type “whereis something” to find whether it existed on PATH. On Linux I have often typed “which something” to the same effect. However, typing php-config yields:

	russ@taliesin:~> php-config
	Usage: /usr/local/bin/php-config [--prefix|--includes|--ldflags|--libs|--extension-dir|--version]

(In PHP’s case, you can’t type more than one of these arguments at once, but our product’s version of this script, vas-config, does handle it giving each piece of information on subsequent new lines.)

For example, invoking with the --includes option yields very complex, but crucially useful information (to me who am working on PHP bindings for my product):

	russ@taliesin:~> php-config --includes
	-I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend

This is what I use in my configure.ac (autoconfig) script to set up where gcc will get PHP headers from. And so on.

^ ALT F1 drops to the text console.

^ ALT F7 returns to GUI.

Note that if the GUI log-in is “hung,” meaning you can’t type in a username, you can press ^ ALT F1 to get to the text console, log in as root, then, as you’re already at level 5 (most likely: you were running in GUI after all), reinit to level 3, then to level 5 whereupon you’ll get a new GUI:

	taliesin:~ # init 3
	(bunch of stuff happens here: press Enter a few times...)
	taliesin:~ # init 5
	(wait a while)

If I delete VAS or otherwise corrupt it, I may be left with the PAM files in such a state that I can’t log in, get root, etc. The steps to reversing this are:

• Reboot
• Catch coming up and change the Boot options (press <F2>) to

  	init=/bin/bash
  

  This makes bash the start-up binary instead of the standard init sequence. That way, it comes up with a root text shell.

• Go fix the problem (delete the lines from the PAM files containing vas3); this includes files

  	/etc/pam.d/common-account
  	/etc/pam.d/common-auth
  	/etc/pam.d/common-password
  	/etc/pam.d/common-session
  

• Do the following:

  	sync       # (this ensures that the modifications just made are in the filesystem)
  	shutdown -r now
  

	taliesin:/home/russ/VAS/src/preflight # sudo wireshark &*

To see what’s going on on port 88, go to

• Capture->Options
• Capture Filter: port 88
• Start

Then use/reuse Capture->Start, Stop or Restart and see the pretty colors.

* If you get an error like

	russ@taliesin:~/VAS/src/preflight> sudo wireshark &
	[3] 23994
	russ@taliesin:~/VAS/src/preflight>
	(wireshark:23994): Gtk-WARNING **: cannot open display:

	[3]+  Exit 1                  sudo wireshark

Try this instead:

	taliesin:/home/russ/VAS/src/preflight # gnomesudo wireshark &

You can't run wireshark unless you are root. On Ubuntu or other systems, you might find the working GUI sudo command to be something like gksudo.

On openSuSE Linux 10.3, I'm finding that the command is gnomesu -c wireshark &.

An example

Upon launching wireshark, I pull down the Capture menu, choose Options..., then ensure that the Interface is eth0 (my network card).

I then specify a filter. The filter syntax appears inconsistent between the various places you can set on in wireshark. In one case where I was attempting to sniff HTTP exchanges between two applications I was testing, I set the Interface to lo (meaning local or 127.0.0.1) and then used tcp port 48080.

Then, click on the Start button and the fun begins. (You're on your own now.)

	taliesin:/home/russ # iptables -I OUTPUT 1 -p udp --dport 88 -j DROP
	taliesin:/home/russ # iptables -L OUTPUT Chain OUTPUT (policy ACCEPT)
	target     prot opt source       destination
	DROP       udp  --  anywhere     anywhere    udp dpt:kerberos
	ACCEPT     0    --  anywhere     anywhere
	ACCEPT     0    --  anywhere     anywhere    state NEW,RELATED,ESTABLISHED
	LOG        0    --  anywhere     anywhere    limit: avg 3/min burst 5 LOG level warning tcp-options ip-options prefix `SFW2-OUT-ERROR '
	taliesin:/home/russ # wireshark &
	      Instructions for Wireshark:
	      1. Capture -> Options
	      2. Capture Filter: port 88
	      3. Start
	      4. watch what happens... (nothing)

	russ@taliesin:~/HEAD/VAS/src/preflight> vastool kinit
	Password for [email protected]:
	ERROR: Could not establish credentials.
	VAS_ERR_KRB5: at ticket.c:77 in _ticket_generate_good_error
	   Failed to obtain credentials. Client: [email protected], Service: krbtgt/[email protected], Server: ad64-a.a.vas
	   Caused by:
	   KRB5_KDC_UNREACH (-1765328228): Cannot contact any KDC for requested realm
	Reason: unable to reach any KDC in realm A.VAS
	taliesin:/home/russ # iptables -D OUTPUT 1

To sort files in ascending order by date...

	rbateman@vastru64:~> ls -lart

To sort lines of a file on a particular field, check out man page for...

	rbateman@vastru64:~> sort -k

How much memory is being consumed on system? How much total? Etc. top is dynamic; you have to stop it.

	russ@taliesin:~> top
	top - 14:31:57 up  1:47,  4 users,  load average: 8.72, 4.35, 1.76
	Tasks: 118 total,   1 running, 117 sleeping,   0 stopped,   0 zombie
	Cpu(s):  0.7% us,  9.8% sy,  0.0% ni,  0.0% id, 88.3% wa,  0.2% hi,  1.0% si
	Mem:   1033484k total,  1019936k used,    13548k free,    10060k buffers
	Swap:  1052216k total,     3332k used,  1048884k free,   732760k cached

	  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
	 9547 russ      18   0  2828  968  752 D 14.0  0.1   0:24.68 snhelper
	  523 root      15   0     0    0    0 S  4.7  0.0   0:07.29 kswapd0
	 5989 root      15   0  175m  41m 8560 S  0.7  4.2   0:31.17 X
	 7132 russ      15   0 57472  18m 9288 S  0.7  1.8   0:04.66 gnome-terminal
	 8631 russ      15   0 71596  30m  16m S  0.7  3.0   0:03.64 vmware-server-c
	 6096 russ      16   0 81040  37m  14m S  0.3  3.7   0:12.37 mono
	 6155 russ      16   0 98.5m  30m  19m S  0.3  3.0   0:09.11 mono
	    1 root      16   0   688  260  224 S  0.0  0.0   0:01.17 init
	    2 root      RT   0     0    0    0 S  0.0  0.0   0:00.01 migration/0
	    3 root      34  19     0    0    0 S  0.0  0.0   0:00.00 ksoftirqd/0
	    4 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/1

Use the du command with --max-depth=n to control the depth of the analysis. For example, how much diskspace are the following web site users consuming. (Some are not web sites.)

	windofkeltia:/home # du --max-depth=1 -h
	292K    ./svn
	100M    ./sonsofutahpioneers
	50M     ./utahwoodturners
	1.4M    ./pfssd
	296K    ./silvertipexpress
	3.5M    ./quicklang
	2.1M    ./morselives
	32M     ./timpwoodturners
	53M     ./russcooks
	27M     ./stgeorgetemplevisitorscenter
	505K    ./cotton
	90M     ./provotabernacle
	1.6G    ./rbateman
	0       ./bullheadranch
	13M     ./vanordenfamily
	101K    ./julene
	2.7M    ./kkearl
	13M     ./utahsdixie
	6.1M    ./covefort
	1005K   ./aintnoclouds
	101K    ./randybateman
	5.1M    ./etretatlogiciels
	81M     ./vicback
	18M     ./nuttall
	614M    ./alfredbateman
	1.2G    ./windofkeltia
	789K    ./wcpafug
	3.3M    ./stgeorgelive
	93K     ./rmbateman
	71M     ./russbateman
	161K    ./sfranson
	4.6M    ./dixiecommunications
	548M    ./russellbateman
	101K    ./krbeesley
	4.4G    .

Use this command to find out information:

	russ@taliesin:~> id
	uid=1000(russ) gid=100(users) groups=16(dialout),33(video),100(users)

In place of ftp, which for security reasons many hosts no longer permit, use scp:

	russ@taliesin:~> scp [email protected]:/data/vas/dev-isos/Isos-vas_vgp-VAS_3_0_0_25/VAS-site-3.0.0-25.iso .

Unable to get into a remote machine because of warning that “Remote host identification has changed!”? Edit ~/.ssh/known_hosts and remove the entry (it’s one long and wrapped line) corresponding to the host you wish to get into.

Of course, if the remote host isn’t joined to vintela.com, russellb simply won’t work.

Use ssh to get a console on another host than your own (or, even on your own if it serves you to do so):

	russ@taliesin:~> ssh -l username hostname.domainname

Example:

	russ@taliesin:~> /usr/bin/ssh -l russellb solaris8.vintela.com

Sample, common tar commands: to create (c) an archive, to appende (r) to it, to extract (x) it, and to see (t for “titles’) what’s in it without extracting anything...

	russ@taliesin:~> tar -cvf tar-filename files and directories...
	russ@taliesin:~> tar -rvf tar-filename
	russ@taliesin:~> tar -xvf tar-filename
	russ@taliesin:~> tar -tvf tar-filename

Use gunzip to decompress tarballs (filename.tar.gz):

	russ@taliesin:~> gunzip -d filename.tar.gz
	russ@taliesin:~> tar -xf filename.tar

Or, simply use the -z to tar:

	russ@taliesin:~> tar -xfz filename.tar.gz

Along the lines of Linux rpm is the Solaris package manager. I have had to use this in writing a super-duper installation script that covers all platforms.

• pkgadd -d package package-name (installs a package)
• pkgadd -a package package-name (upgrades a package)
• pkgrm package-name (removes an installed package)
   

  pkginfo (list out installed packages)

For example, a site-license installation on a Sun box...

	russ@taliesin:~> pkginfo | grep vasclnt
	application vasclnts             VAS Client (site)

And the others...

AIX

• installp -acdx package all (installs/upgrades a package)
• nstallp -u package-name (removes an installed package)

HP-UX

• swinstall -s $cwd/package package-name (installs/upgrades a package)
• swremove package-name (removes an installed package)

1. Search for desired software on Google or directly at sourceforge.net, go to the link on source forge and download the tarball into /tmp. The example we’ll use here is vifm.

2. Go to /tmp and decompress the tarball into a simple archive:

	russ@taliesin:~> cd /tmp
	russ@taliesin:/tmp> gunzip -d vifm-0.3a.tar.gz

3. Extract the archive:

	russ@taliesin:/tmp> tar -xf vifm-0.3a.tar

4. Go down into the directory and build it:

	russ@taliesin:/tmp> cd vifm-0.3a
	russ@taliesin:/tmp/vifm-0.3a> ./configure
	russ@taliesin:/tmp/vifm-0.3a> make

5. Go down into the src directory and run it to ensure that it works.

6. If good, go back up one level and do a make install:

	russ@taliesin:/tmp/vifm-0.3a> sudo make install

The configuration file is on the path /etc/syslog-ng/syslog-ng.conf. The path to syslog’s output, on SuSE 10 at least, is /var/log/messages. Use the following command to be able to watch it grow at the end:

	russ@taliesin:~> tail -f /var/log/messages

Sample entry lines in the SuSE 10, new-generation syslog, as used by VAS:

	source s_vas { unix_stream("dev/log"); internal(); }
	destination d_russvas { file("/home/russ/vas.$WEEKDAY.$HOUR.$MIN"); }
	filter f_vasauth { facility(auth, authpriv); }
	log { source(s_sys); filter(f_vasauth); destination(d_russvas); }

I don’t know if the above would work. Here is what I really have in my /etc/syslog-ng/syslog-ng.conf file:

	...
	filter f_daemon         { level(debug) and facility(daemon); };
	...
	destination daemondebug { file("/var/log/daemon.debug"); };
	log                     { source(src); filter(f_daemon); destination(daemondebug); };

The system log, /var/log/messages, can grow quite large. Delete it, and touch it to start over.

	rm /var/log/messages
	touch /var/log/messages
	rm /var/log/daemon.debug
	touch /var/log/daemon.debug
	/etc/init.d/syslog restart

Once any change to any of this is made, syslog must be restarted:

libroken.a means “broken” and contains all the pseudo-standard stuff missing from the build on any given platform. For example, if GNU stuff getargs and arg_printusage aren’t on the platform, this library supplies them.

Find and stop the ssh dæmon or restart it...

	russ@taliesin:~> ps -ef | grep sshd
	russ@taliesin:~> /etc/init.d/sshd stop
	russ@taliesin:~> /etc/init.d/syslog restart

On HP-UX and AIX, this works differently...

	russ@taliesin:~> /sbin/init.d/sshd stop          # (HP=UX)
	russ@taliesin:~> /etc/rc.d/init.d/ssh restart    # (AIX)

ps options are’t exactly uniform from Linux to UNIX to other Unix. Here’s how it can be solved:

	int is_daemon_running( const char *daemon_name )
	{
	   char ps_command[ 128 ], buffer[ 256 ];

	   /* create ps command for the host platform in 'ps_command'... */
	   cnt = asprintf( &ps_command,

	#if defined( SOLARIS )
	                  "ps -e -o comm | grep [%c]%s"
	#elif defined( DARWIN )
	                  "ps -ax | grep [%c]%s\\\\\\>"
	#else
	                  "ps -e | grep [%c]%s"
	#endif

	                , daemon_name, daemon_name + 1 );

	   if( ( fp = popen( command, "r" ) ) )
	      return errno;

	   while( fgets( buffer, sizeof( buffer ), fp ) )
	   {
	      if( strstr( daemon_name, buffer ) == 0 )
	         return TRUE;
	   }
	   ...
	}

Which libraries does binary sshd link?

	russ@taliesin:~> ldd `which sshd`

If you get...

	russ@taliesin:~> ldd: missing file arguments

It’s certain that there is no sshd on any of your search paths.

Using the tail of a long, dynamic file (like /var/log/messages):

	russ@taliesin:~> tail -f file

...to put yourself into a state in which every directory or file you create will have, by default, certain privileges although the privileges are slightly different depending on whether a file or a directory for the same umask setting. For the bits, 0 gives you the most rights, rwx for a directory and rw- for a file; 1 gives you rwx for a directory and rw- for a file; 2 gives you r-x and r-- for a file; last, 3 gives you r-- only. For example, ...

	russ@taliesin:~> umask 0
	russ@taliesin:~> touch poop
	russ@taliesin:~> mkdir poop.d
	russ@taliesin:~> ls -l
	-rw-rw-rw-  1 russ users   0 2006-11-01 09:35 poop
	drwxrwxrwx  2 russ users  48 2006-11-01 09:35 poop.d
	russ@taliesin:~> rm poop ; rmdir poop.d

	russ@taliesin:~> umask 0011
	russ@taliesin:~> touch poop
	russ@taliesin:~> mkdir poop.d
	russ@taliesin:~> ls -l
	-rw-rw-rw-  1 russ users   0 2006-11-01 09:35 poop
	drwxrw-rw-  2 russ users  48 2006-11-01 09:35 poop.d
	russ@taliesin:~> rm poop ; rmdir poop.d

	russ@taliesin:~> umask 0022
	russ@taliesin:~> touch poop
	russ@taliesin:~> mkdir poop.d
	russ@taliesin:~> ls -l
	-rw-r--r--  1 russ users   0 2006-11-01 09:29 poop
	drwxr-xr-x  2 russ users  48 2006-11-01 09:29 poop.d
	russ@taliesin:~> rm poop ; rmdir poop.d

	russ@taliesin:~> umask 0033
	russ@taliesin:~> touch poop
	russ@taliesin:~> mkdir poop.d
	russ@taliesin:~> ls -l
	-rw-r--r--  1 russ users   0 2006-11-01 09:35 poop
	drwxr--r--  2 russ users  48 2006-11-01 09:35 poop.d
	russ@taliesin:~> rm poop ; rmdir poop.d

	russ@taliesin:~> umask 0133
	russ@taliesin:~> touch poop
	russ@taliesin:~> mkdir poop.d
	russ@taliesin:~> ls -l
	-rw-r--r--  1 russ users   0 2006-11-01 09:35 poop
	drw-r--r--  2 russ users  48 2006-11-01 09:35 poop.d
	russ@taliesin:~> rm poop ; rmdir poop.d

The usual umask when creating massive numbers of directories (such as for a package installation) is 0022.

Command sux is a wrapper around su that transfers X credentials. This is useful for running GUI apps as root.

	russ@taliesin:~> sux /usr/ConsoleOne/bin/ConsoleOne

The find command, an example:

	russ@taliesin:~> find . -name '*.c' -print
	russ@taliesin:~> find / -name 'gcc*' -print
	russ@taliesin:~> find starting at root
	russ@taliesin:~> find . -name '*.c' -exec fgrep -H Usage: {} \;
	russ@taliesin:~> find . -name "*.[ch]" -exec fgrep -H Usage: {} \;	# both .c and .h files

Find some files matching a template; then, finding them, delete them:

	russ@taliesin:~> find . -name '*.tmp' -print
	russ@taliesin:~> find . -name '*.tmp' -exec rm {} \;

newgrp creates a new shell running as if with the gid of the specified group, requires a password created using gpasswd.

Linux (Unix) commands affected or interesting in this context:

	russ@taliesin:~> newgrp new-group-name
	russ@taliesin:~> gpasswd
	russ@taliesin:~> sg                        # (cf. sudo)
	russ@taliesin:~> groups                    # (lists groups from /etc/group)

Find out the name of the OS on the host (Linux, SunOS, HP-UX, AIX, etc.):

	russ@taliesin:~> uname -a | awk '{ print $1 }'

Hostname...

	russ@taliesin:~> uname -a | awk '{ print $2 }'

The following files exist on some Linux distros...

	/etc/SuSE-release
	/etc/redhat-release

Try pressing...

	Control Alt F1            or
	Control Alt Backspace

Create a new subdirectory to be used as a mount point first.

	russ@taliesin:~> mkdir /home/russ/vasapi
	russ@taliesin:~> sudo mount -o loop VAS-site-3.0.0-25.iso /home/russ/vasapi

To undo this...

	russ@taliesin:~> sudo umount VAS-site-3.0.0-25.iso

Renae uses this method to test builds as if ISOs.

	russ@taliesin:~> mkdir /mnt/jerry
	russ@taliesin:~> sudo mount -o ro slcflsl01.prod.quest.corp:/data/vas /mnt/jerry

To undo this...

	russ@taliesin:~> sudo umount /mnt/jerry

Then just switch to the directory and run...

	russ@taliesin:/mnt/jerry/dev-builds/junk> cd /mnt/jerry/dev-builds/junk
	russ@taliesin:/mnt/jerry/dev-builds/junk> ./install.sh -d 1 -n -a (etc.)

	russ@taliesin:~> mount [-t type] /dev/hde /cdrom

	/dev/cdrom/cd iso9660 ro,user,noauto, unhide

	russ@taliesin:~> mount /dev/cdrom
	russ@taliesin:~> mount /cd

Local printer, no auto-detect of Plug’n’Play, new port, TCP/IP at address 10.5.34.1.

To get interesting information on your host hardware (like opening the System details in the Windows control panel), the following is helpful:

	russ@taliesin:~> uname -a
	russ@taliesin:~> cat /proc/cpuinfo
	russ@taliesin:~> ps ax
	russ@taliesin:~> top                  # (gets a screenful of the most active processes)

Multihomed means that you have one network interface card (NIC), but two different IP addresses assigned to it. The other option is to have two NICs, each with its own address.

I tried VSE a little bit in an attempt to over-come the paucity of tagging from Vim, but in frustration with its broken Vi emulation, discovered Exuberant ctags and found I didn’t need VSE. Nevertheless, here are random notes on using it...

	.slickedit/vunxdefs.e

Steps to remap:

• Tools->Options->Key Bindings... look for command in list window (something like vi-goto-line)
• Click Add Key or Mouse Click
• Press the key, it should appear in the Key sequence edit field
• Click on Affect command mode, then
• Click on Bind

Can also remap ^C, ^V, ^X, etc. as copy-region, paste and cut-region.

The ctag keys in VSe are ^., ^, and ^/ (list reference).

How to set up a key on a host so that you can get into it via ssh without a password?

	russ@taliesin:~/.ssh> ssh-keygen -b 1024 -t rsa
	Generating public/private rsa key pair.
	Enter file in which to save the key (/home/russ/.ssh/id_rsa):
	Enter passphrase (empty for no passphrase):
	Enter same passphrase again:
	Your identification has been saved in /home/russ/.ssh/id_rsa.
	Your public key has been saved in /home/russ/.ssh/id_rsa.pub.
	The key fingerprint is:
	61:25:8a:15:86:ff:cb:3d:ec:7e:5c:16:2b:6f:73:b3 russ@taliesin
	russ@taliesin:~/.ssh> ll total 48
	-rw-r--r-- 1 russ users   223 2006-06-27 13:10 authorized_keys
	-rw-r--r-- 1 russ users   116 2007-03-05 11:11 config
	-rw------- 1 russ users   887 2008-07-29 14:58 id_rsa
	-rw-r--r-- 1 russ users   223 2008-07-29 14:58 id_rsa.pub
	-rw-r--r-- 1 russ users 31323 2008-07-28 08:48 known_hosts
	russ@taliesin:~/.ssh> scp id_rsa.pub [email protected]:/home/rbateman/.ssh
	[email protected]'s password:
	id_rsa.pub                                    100%  223     0.2KB/s   00:00

On the remote host...

	russ@taliesin:~/.ssh> ssh [email protected]
	[email protected]'s password:
	Last login: Thu Jul 24 10:15:35 2008 from vasx8664.vintela.com
	[rbateman@slc205613 root]# cd /home/rbateman/.ssh
	[rbateman@slc205613 .ssh]# ll
	total 28
	-rw-r--r--    1 rbateman slc           488 Jul 29 14:39 authorized_keys
	-rwxr-xr-x    1 rbateman slc          2372 Oct  9  2007 equip_all_plats.sh
	-rw-r--r--    1 rbateman slc           223 Jul 29 14:53 id_rsa.pub
	-rw-r--r--    1 rbateman slc          8865 Oct  9  2007 known_hosts
	[rbateman@slc205613 .ssh]# cat id_rsa.pub >> authorized_keys
	[rbateman@slc205613 rbateman]$
	^D
	Connection to vasx8664.vintela.com closed.

Back on the local host, we can now ssh to the remote host without a password:

	russ@taliesin:~/.ssh> ssh [email protected]
	Last login: Tue Jul 29 14:54:05 2008 from taliesin.vintela.com

locate is a great tool—much faster and easier to use than find. To get it, use YaST->Software->Software Management, type in “locate” as the filter/search string, and click findutils-locate if that package has not been installed already. This is the GNU Findutils Subpackage. Install it if need be.

Once installed, it’s probably on your PATH, so first update its index (database). It searches all your filesystem indexing the files thereon. Later, you’ll want to chron this action to run late at night while you’re asleep.

Then, use man locate to learn how to use it, however, here are a couple of examples:

	russ@taliesin:~/GWAVA> which updatedb
	/usr/bin/updatedb
	russ@taliesin:~> updatedb

	russ@taliesin:~/GWAVA> locate vicheat.gif
	/home/russ/GWAVA/vicheat.gif
	/home/russ/Quest/documents/vintela/vicheat.gif
	/home/russ/Quest/notes/vicheat.gif

	russ@taliesin:~/GWAVA> locate /web/WEB-INF/cfg | grep ASConfig.cfg
	/home/russ/dev/svn/retain/RetainServer/web/WEB-INF/cfg/ASConfig.cfg

	russ@taliesin:~/GWAVA> locate /web/WEB-INF/cfg/.svn/tmp
	/home/russ/dev/svn/retain/RetainServer/web/WEB-INF/cfg/.svn/tmp
	/home/russ/dev/svn/retain/RetainServer/web/WEB-INF/cfg/.svn/tmp/prop-base
	/home/russ/dev/svn/retain/RetainServer/web/WEB-INF/cfg/.svn/tmp/props
	/home/russ/dev/svn/retain/RetainServer/web/WEB-INF/cfg/.svn/tmp/text-base
	/home/russ/dev/svn/retain/RetainWorker/web/WEB-INF/cfg/.svn/tmp
	/home/russ/dev/svn/retain/RetainWorker/web/WEB-INF/cfg/.svn/tmp/prop-base
	/home/russ/dev/svn/retain/RetainWorker/web/WEB-INF/cfg/.svn/tmp/props
	/home/russ/dev/svn/retain/RetainWorker/web/WEB-INF/cfg/.svn/tmp/text-base

eth0 must be assigned to a zone in order for VNC to work. Go to Firewall Configurations->Interfaces.

To examine what repositories are used by Yast, you can launch Yast and choose Software->Software Repositories or you can do this:

	taliesin:/ # zypper sl
# | Enabled | Refresh | Type   | Alias                                                             | Name
--+---------+---------+--------+-------------------------------------------------------------------+-----------------------------
1 | Yes     | Yes     | yast2  | http://download.opensuse.org/repositories/openSUSE:10.3/standard/ | Main Repository (OSS)
2 | Yes     | No      | yast2  | openSUSE-10.3-OSS-Gnome 10.3                                      | openSUSE-10.3-OSS-Gnome 10.3
3 | Yes     | Yes     | yast2  | http://download.opensuse.org/distribution/10.3/repo/debug/        | Main Repository (DEBUG)
4 | Yes     | Yes     | rpm-md | Mozilla                                                           | Mozilla
5 | Yes     | Yes     | rpm-md | NVIDIA Repository                                                 | NVIDIA Repository
6 | Yes     | Yes     | rpm-md | openSUSE-10.3-Updates                                             | openSUSE-10.3-Updates