How to add directories and subdirectories to a CVS repository

Here is a quick way to add directories and subdirectories to an existing CVS repository 

cvs add top_level_directory
find top_level_directory -type d -print | xargs cvs add
find top_level_directory -name CVS -prune -o -type f -print | xargs cvs add

The instruction below adds the top-level called top_level_directory directory to the CVS repository 

cvs add top_level_directory

The instruction below finds all subdirectories under top_level_directory and issues a cvs add command to subdirectories that are found

find <folder_name> -type d -print | xargs cvs add

The instruction below finds all files not including CVS files and issues a cvs add command

find <folder_name> -name CVS -prune -o -type f -print | xargs cvs add
 

How to compare directories using diff

The easiest way to compare directories in Linux or Unix is by using a utility called diff in the following way..

 diff –recursive <directoryA> <directoryB>

Note: there are two dashes (“-”) before the word recursive.

Debian : How to start wireless connection

Assuming you have your wireless card up and running, the only thing left to do is to type

dhclient

at the prompt when you are root user.

Xfce : How to start running xfce from the login console

There are three different ways to do this:

• You can just login with the command startxfce4
• You can add exec startxfce4 to your .xinitrc in your home directory and simply use startx.
• You put the following in your .bash_profile/.bashrc if you want that Xfce is started automatically when you login on tty1:

if [ "$(tty)" = "/dev/tty1" -o "$(tty)" = "/dev/vc/1" ] ; then startxfce4 fi

To properly give credit, please note that this information was originally sourced from

http://wiki.xfce.org/faq

How to find out what your Ethernet/Wireless MAC address is

Windows 2000 and XP

• From the Start button select Run

• In the box which appears type cmd and click OK

• A new windows will appear – at the prompt type ipconfig /all

• The MAC address will be referred to as the Physical Address and is made up of 12 characters e.g. 00-D1-AB-F2-G3-89
  You will have a separate MAC address for your wireless card and your Ethernet card. Make sure you use the correct one.

• The IP address will be listed – if you are connected to the UWA network it should begin with 144.124.

• The host name is your computer’s name

Linux

• In a privileged terminal session type: ifconfig

• This will show you a list of the network adapters installed. The MAC address is referred to here as the HWaddr

• If you have a wireless card you will see more then one MAC Address, make sure you register the right MAC address.

• To pick out your wireless MAC address type: iwconfig- your Wired one will be the other one

Vista

• Click the Start icon

• Click All Programs

• Click Accessories

• Click Command Prompt

• A new window will appear – at the prompt type ipconfig /all

• The MAC address will be referred to as the Physical Address and is made up of 12 characters e.g. 00-D1-AB-F2-G3-89
  You will have a separate MAC address for your wireless card and your Ethernet card. Make sure you use the correct one.

• The IP address will be listed – if you are connected to the UWA network it should begin with 144.124.

• The host name is your computer’s name

In order to provide proper credit, please note that this information was originally obtained from the following website:

http://www.inf.aber.ac.uk/advisory/faq/37/

Debian Etch – A Linux distribution done right

I’ve been trying a few Linux distributions and have finally found one that I have to say is just amazing. I needed something that could run on an old, late-nineties laptop. I was going to use this laptop for surfing the Internet and programming in Python and C. The laptop orignally contained Windows 98 which is pretty much unsupported now. I needed to update the laptop to a more current OS. The requirement being that the OS and the applications should be lightweight enough to support my laptop.

Before I go into describing my experience with Linux distros, let me share with you my laptop specs. It is a Toshiba Satellite 2590CDT. It uses a 400 MHz Intel Celeron, 6 GBHard Drive, and 192 MB of RAM. It also has a PCMCIA port for wireless cards and a USB 1.0 port. As you can see, this laptop is quite old and is significantly behind today’s(mid-2007) technology. Nevertheless, it is still working and useful. I’m just one of those people who just can’t stand to throw away perfectly working hardware.

The Linux distributions I tried were:

* Deli Linux
* Red Hat 8.0
* Xubuntu Feisty Fawn
* Debian Etch

Deli Linux is a lightweight distribution and consumes about 500-800 MB of hard drive space. This was what I found appealing at first. But I soon discovered that it was too lightwieght for my needs. It didn’t have all the software I needed to get my laptop up an running. In order for me to use Deli, I would need to spend countless nights getting it to work with all the hardware pieces. In addition, the browser wasn’t up to rendering today’s webpages in the same way as Firefox or IE.  It also doesn’t have an advanced package manager.

Red Hat 8.0 was one I found at a local library. I tried Red Hat when Red Hat first sold desktop Linux distros but haven’t tried it after that. It just wasn’t useful to me at the time compared to Microsoft Windows. Since Red Hat was what I knew then, it was my next choice. Although very much outdated, Red Hat 8.0’s hardware requirements were minimal and was what my laptop could provide so I decided to give it a try. It installed fine but consumed over 60% of my 6 GB hard drive. The distribution was filled with so many software applications – most I doubt I would use. I also learned that the desktop version of Red Hat was no longer supported. The last release was 9.0. After that came Fedora which requires more CPU power, RAM and hard drive capacity – more than my laptop could ever provide. So simply buying present day Red Hat-based Linux distributions was out of the question. What I found most irritating was Red Hat’s package manager also known as RPM. When trying to upgrade my software, I eventually found myself in RPM dependency hell that it made upgrading software virtually impossible. I don’t know if that has changed in Fedora or Red Hat Enterprise though.

Xubuntu Feisty Fawn caught my attention because I reasoned that I’d be able to get the latest Linux kernel, latest software,and it would be light-weight enough to be able to run on my laptop using the Xfce window manager. I liked the user interface and it made it appear that my laptop was the updated because of all the eye-candy. The start-up screen just looked so cool and futuristic. What irked me was that it couldn’t recognize my floppy and CD-ROM. No amount of web surfing could help me understand how to debug and fix this problem. Even forum posts went unanswered. I didn’t have the patience to figure out how to get it to work which led me to hunting for other distros.

I stumbled upon Debian Etch because I had read that Ubuntu was a derivative of Debian but was much more stable.  I decided to try a network install of Debian. What impressed me was that I could pick and choose to install only the software pieces I wanted during installation.  I would later find out that I can continue to install new software applications whenever I wanted without having to concern myself with dependencies.  This meant that less hard drive space was consumed. Unlike other distributions I’ve encountered where installation CDs loaded what seemed like every open-source software ever written but I probably would never use. After the install, their were some minor tweaks I needed to make that were resolved by a few Google searches. I think the most impressive thing about Debian is apt-get. It meant that I could easily upgrade or add software without hassle and without going into the fires of dependency hell. Wireless installed fine. Programming languages and tools installed fine as well. After going through all the headache from the other distributions, I was impressed with Debian. So much so, that I’m actually considering volunteering to help them out in any of their projects. This is one distribution I can stand behind for a long time. In my opinion, Debian is Linux distribution done right. It just works. So, if ever you are wondering about which Linux distribution is the best, I’d say give Debian a try…

Configuring Redhat 8.0 to work with a Linksys WPC11 v4 card

For the benefit of other Linux users, I wanted to document how I was able to install a wireless card on Redhat Linux.  It wasn’t as easy as I had hoped and after spending many hours reading Linux forums, I finally succeeded.  I’m writing this article hoping that this article will save time for other people trying to do something similar.  This article assumes some knowledge of using a Unix OS.

My hardware
1. Toshiba Satellite 2590CDT Laptop. 400 MHz Intel Celeron, 196 MB RAM, 6 GB Hard drive
2. Redhat 8.0 Linux OS
3. Wireless NIC is a Linksys WPC11 v4
4. Wireless Router Linksys WRT54GS Wireless-G

My software
1. C compiler gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
2. rtl8180_linuxdrv_v15_rh90.zip (driver from Realtek website)
3. Redhat 8.0 (not sure what other people have experienced using a different version).
4. Linux kernel 2.4.18-14

Steps
1. Uncompress the driver(.zip) file

[root@localhost temp]# unzip rtl8180_linuxdrv_v15_rh90.zip
Archive:  rtl8180_linuxdrv_v15_rh90.zip
   creating: rtl8180_1.5/
  inflating: rtl8180_1.5/Makefile
  inflating: rtl8180_1.5/priv_part.o
  inflating: rtl8180_1.5/r8180_export.h
  inflating: rtl8180_1.5/r8180_if.c
  inflating: rtl8180_1.5/r8180_if.h
  inflating: rtl8180_1.5/r8180_pci_init.c
  inflating: rtl8180_1.5/r8180_pci_init.h
  inflating: rtl8180_1.5/r8180_type.h
  inflating: rtl8180_1.5/readme
  inflating: rtl8180_1.5/rls_note_1124
  inflating: rtl8180_1.5/rtl8180_24x.o
  inflating: rtl8180_1.5/wlandown
  inflating: rtl8180_1.5/wlanup
  inflating: rtl8180_1.5/wlandrv_release_note

2. In directory called rtl8180_1.5, create “.o” files by running make.

[root@localhost rtl8180_1.5]# make
gcc -O6 -Wall -DMODULE -D__KERNEL__ -DLINUX -I /usr/src/linux-2.4.18-14/include/ -DRTL_IO_MAP -DRTL_LITTLE_ENDIAN -DRTL_ACT_AS_STA -DRTL8180_DRV_ON_PC -DENABLE_DBG_PRINT -c -o r8180_pci_init.o r8180_pci_init.c
In file included from r8180_pci_init.c:40:
r8180_type.h:62:1: warning: “ENABLE_DBG_PRINT” redefined
r8180_pci_init.c:1:1: warning: this is the location of the previous definition
gcc -O6 -Wall -DMODULE -D__KERNEL__ -DLINUX -I /usr/src/linux-2.4.18-14/include/ -DRTL_IO_MAP -DRTL_LITTLE_ENDIAN -DRTL_ACT_AS_STA -DRTL8180_DRV_ON_PC -DENABLE_DBG_PRINT -c -o r8180_if.o r8180_if.c
In file included from r8180_if.h:20,
                 from r8180_if.c:49:
r8180_type.h:62:1: warning: “ENABLE_DBG_PRINT” redefined
r8180_if.c:1:1: warning: this is the location of the previous definition
r8180_if.c:4: warning: `vcid’ defined but not used
— Generate open part open_part.o —

— Generate rtl8180 linux driver  rtl8180_24x.o on 2.4.18-14 —

[root@localhost rtl8180_1.5]#

3. After make has completed, install the driver module by running “make install”

4. Modify wlanup file located in rtl8180_1.5 directory.  What worked for me is after I edited the wlanup file the following way:

wlanup file
=========
 #————————–
 # Load wireless lan driver
 #————————–
/sbin/insmod -f /lib/modules/2.4.18-14/kernel/drivers/net/wireless/rtl8180_24x.o

case “$1″ in
 ap)
        echo “ap”
        #——————————————
        # Config AP mode
        # Assign SSID and operation channel.
        #——————————————
        /sbin/iwpriv wlan0 wlan_para ssid=BIAS
        /sbin/iwpriv wlan0 wlan_para channel=2
        ;;
 infra)
        echo “infra”
        #——————————————
        # Config infrastructure mode
        # Assign network type and desired SSID.
        #——————————————
   /sbin/iwpriv wlan0 wlan_para channel=<<<whatever channel your router is using>>>
   /sbin/iwpriv wlan0 wlan_para networktype=infra
   /sbin/iwpriv wlan0 wlan_para ssid2scan=<<<SSID of router>>>
        /sbin/iwpriv wlan0 wlan_para ssid=<<<SSID of router>>>
        ;;
 adhoc)
        echo “adhoc”
        #——————————————
        # Config infrastructure mode
        # Assign network type and desired SSID.
        # ’ssid’ and ‘channel’ are the default setting
        # and meaningful if this is the first station
        # in an IBSS.
        #——————————————
        /sbin/iwpriv wlan0 wlan_para networktype=adhoc
        /sbin/iwpriv wlan0 wlan_para ssid2scan=aaaaa
        /sbin/iwpriv wlan0 wlan_para ssid=A_WPA
        /sbin/iwpriv wlan0 wlan_para channel=2
        ;;
 *)
        /sbin/rmmod rtl8180_24x
        echo “Usage: $0 {ap | infra | adhoc}”
        exit 1
esac
 #————————–
 # Config WEP mode
 #————————–
/sbin/iwpriv wlan0 wlan_para encmode=off
/sbin/iwpriv wlan0 wlan_para wepmode=off

#/sbin/iwpriv wlan0 wlan_para encmode=wep,wepmode=wep40
#/sbin/iwpriv wlan0 wlan_para wepmode=wep40,wepdkeyid=0,wepkey40_1=1111111111
 #————————–
 # Config debugging message
 #————————–
/sbin/iwpriv wlan0 msglevel 0
 #————————–
 # Enable wireless lan driver
 #————————–
/sbin/iwpriv wlan0 enable
 #————————–
 # Configure wlan0 IP address
 #————————–
#removed because I added ifcfg-wlan0 to /etc/sysconfig/network-scripts
#/sbin/ifconfig wlan0 192.168.1.180
echo “$(/sbin/ifconfig wlan0)”
6. Bring up wireless lan by typing the following lines in a terminal

wlanup infra
dhclient wlan0

7. Verify wireless status by reading /proc/rtl8180/status.  Note that, if the wireless NIC is successfully communicating with the router, the  BSSID value here should be the similar to the MAC address of the router.  I’m not sure why they aren’t exactly the same in my setup.  Even though the number is different by 1 on the rightmost entry, I was still able to connect successfully. 

If you have another computer that can connect to the router either wired or wirelessly, you can verify the MAC address of the router by entering 192.168.1.1 in a web browser.  Then, left-click on the Status link.  The router web page should display something like this…

Firmware Version:  v7.50.0, Jan. 16, 2007                 
Current Time:  Tue, Jul 31 2007 22:57:02                 
MAC Address:  00:1C:10:38:12:57                 
Router Name:  WRT54GS

The /proc/rtl8180/status file should look something like this

—————————————
             Driver status            
—————————————

  rtl8180_pci_driver version 1.5 loaded.
  The Network is configured as Infrastructure mode.
  MacAddr = 00:0c:41:c2:0d:98
  ioaddr = 0×4800
  irq = 11
—————————————
          Wireless Link status        
—————————————

   Link Success!

   Channel number = 6
   beacon period = 100
   BSSID = 0×00 0×1c 0×10 0×38 0×12 0×58
   SSID = zambo
   Capability = 0×01
   AID = 0×01
   Operational rates = <1><2><5.5><11>Mbps
   Current TX operational rates = <11>Mbps
8. That’s it!.  Contrary to what I’ve read in a few forum threads, I didn’t make any changes to the r8180_type.h and r8180_if.h files.
Some things to verify
1. After inserting the wireless card into your laptop.  Verify that the operating system sees it.  You should get similar output as I do.

[root@localhost root]# cardctl ident
Socket 0:
  no product info available
Socket 1:
  product info: “Realtek”, “Rtl8139″
  manfid: 0×0000, 0×024c
  function: 6 (network)
[root@localhost root]#

2. Check that the driver is installed.  The driver for the wireless card is indicated as rtl8180_24x

[root@localhost root]# lsmod
Module                  Size  Used by    Tainted: GF
rtl8180_24x           249100   0
ds                      8712   2
yenta_socket           12960   2
pcmcia_core            54784   0  [ds yenta_socket]
….
<I omitted unrelated driver modules>
…
[root@localhost root]#

3. Verify that the wireless card is seen on the PCI bus in your laptop

[root@localhost root]# lspci
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX – 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX – 82443BX/ZX/DX AGP bridge (rev 03)
00:02.0 CardBus bridge: Toshiba America Info Systems ToPIC97 (rev 05)
00:02.1 CardBus bridge: Toshiba America Info Systems ToPIC97 (rev 05)
00:05.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:05.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:05.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:05.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:07.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01)
00:0a.0 Communication controller: Toshiba America Info Systems FIR Port (rev 23)
00:0c.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
01:00.0 VGA compatible controller: Trident Microsystems Cyber 9525 (rev 49)
15:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.: Unknown device 8180 (rev 20)
[root@localhost root]#

One way to recover from a “missing operating system” message

Prerequisites: You’ll need a Windows 98 Startup Disk 

I was trying to install Red Hat Linux 8 over DeLi Linux and in the process I somehow corrupted the Master Boot Record (mbr).  I probably ruined the boot up code in the hard drive when I issued “fdisk /mbr ” .    After that, I simply could not install anything into my hard drive.  Everytime I tried to boot up the computer straight from the main hard drive(C:), without the Win 98 Startup Disk, I was getting “Missing operating system.” messages.  Even after multiple fdisk /mbr commands, I still couldn’t fix the hard drive or initialize the mbr properly.  I couldn’t even format the C: drive with a DOS “format c: /s” command.

Lucky for me, there is a program called DEBUG.EXE in the Windows 98 Startup Disk that helped me out.  By the way, Startup Disks built by Windows XP don’t have this program.  When booting the computer using the Win 98 Startup Disk, copies of useful programs are copied to the C: drive including DEBUG.EXE.  Using this program, I was able to clear out the MBR on the hard drive.  This article will describe how I did this.

Caution/Disclaimer: Doing the following will cause your hard drive to start from scratch and you will lose data that was originally on your hard drive. I’m not responsible for any loss of data.

1. Boot the computer using a Windows 98 Startup Disk.  During boot, programs will be copied to your main drive (C:) including one called DEBUG.EXE
2. After boot completes, change to the C: drive by typing “C:” at the A:> prompt
3. Enter “debug” at the C: prompt
4. At the “-” prompt, type ‘a’ to start the assembly editor
5. Enter the following assembly code instructions:
6. mov dx,9000
   mov es,dx
   xor bx,bx
   mov cx,0001
   mov dx,0080
   mov ax,0301
   int 13
   int 20
7. then press ‘g’ to execute
8. If everything goes right, a critical area in your hard drive containing the MBR has now been cleared to zeroes and is ready for a fresh new Operating System installation.

Getting DeLi Linux to recognize a Xircom PCMCIA Ethernet card

I was surfing the web and came upon a lightweight Linux distribution called DeLi Linux.  DeLi Linux can be used to give life and provide extended use to old computers and, in my case, to old laptops.  Being new to Linux, I discovered that part of the challenge of installing Linux is getting it to recognize old hardware.  Compared to Windows, depending upon your experience, it could take minutes or weeks to finally have Linux properly configured.  So beware, using Linux could be a real time sink.  This article will write about the steps I needed to do to get DeLi Linux to recognize a Xircom RBE-100 PCMCIA Ethernet Card.  I didn’t find a step-by-step guide anywhere about this topic.  Instead, I found a lot of unanswered questions.  So, in the spirit of helping others, I’m posting this on the Internet hoping that you will find this article useful, informative, and save you time.

What this article won’t write about is getting an Internet connection up and running.  That will be in another article.  Also, I’m not sure if this procedure applies to other Linux distributions.

1) My hardware 

First off, let me describe my laptop.  It is a Toshiba Satellite 2590CDT.  It comes with a floppy drive, CD-ROM, and a USB 1.0 port.  I bought it in 1999 for about $1500.  It has a 400 MHz Intel Celeron processor, 64 MB of RAM, and 5 GB of hard drive space.  Like I said earlier, the network card is a Xircom RBE-100 PCMCIA.

2) Edit /etc/rc.d/pcmcia

You’ll need to define your PCIC module.  In the pcmcia file, where it says..

else
    # Slackware startup options go right here:
    # Should be either i82365 or tcic
    PCIC=
    # Put socket driver timing parameters here
    PCIC_OPTS=
    # Put pcmcia_core options here
    CORE_OPTS=
    # Put cardmgr options here
    CARDMGR_OPTS=
    # To set the PCMCIA scheme at startup…
    SCHEME=
fi

Change it to..

else
    # Slackware startup options go right here:
    # Should be either i82365 or tcic
    PCIC=yenta_socket
    # Put socket driver timing parameters here
    PCIC_OPTS=
    # Put pcmcia_core options here
    CORE_OPTS=
    # Put cardmgr options here
    CARDMGR_OPTS=
    # To set the PCMCIA scheme at startup…
    SCHEME=
fi

In addition, find out where a program called pidof is executed by typing

which pidof

You should get an output that looks like
/bin/pidof

Where it says the following in the /etc/rc.d/pcmcia…

    status)
 pid=`/sbin/pidof cardmgr`

Change it to point to the pidof program identified by running ‘which pidof’

    status)
 pid=`/bin/pidof cardmgr`

3) Load and install the hotplug program.

Something I didn’t find out until I read some fine print on a website is a program called hotplug.  It is used in conjunction with Linux kernels 2.4 and later to manage CardBus cards.  It wasn’t included as part of the DeLi Linux distribution I loaded into my Toshiba.  I’m not sure if it will be in the future.  So, you’ll need to find out if it is installed already by typing ‘which hotplug’.

If you get a message like:
which: no hotplug in (/bin:/sbin:<blah><blah><blah>)

then it is definitely not installed.

The latest version of hotplug can be downloaded from http://linux-hotplug.sourceforge.net.  Simply uncompress and follow the instructions.

You’ll know when you’ve succeeded in installing hotplug when you type ‘which hotplug’ and you get a message like this:
/sbin/hotplug

4) Verify that the ethernet card is seen and is usable by Linux

The following describes Linux commands in bold that are typed in a shell followed by resulting output.  If you have successfully executed the steps above, you should be getting similar results.

lsmod
Module                  Size  Used by    Not tainted
xircom_cb               5032   0  (unused)
ds                      6132   2
yenta_socket            9380   2
pcmcia_core            35300   0  [ds yenta_socket]
….
…
..

I purposely omitted unrelated drivers.  Note that DeLi Linux already contains the appropriate drivers for the Xircom RBE-100 contained in xircom_cb.

cardctl ident
Socket 0:
  product info: “Xircom”, “CardBus Ethernet II 10/100″, “CBEII-10/100″, “1.03″
  manfid: 0×0105, 0×0103
  function: 6 (network)
Socket 1:
  no product info available

cat /var/lib/pcmcia/stab
Socket 0: CardBus hotplug device
Socket 1: empty

cardmgr sees the Xircom as a hot plug PCI device in Socket 0.

lspci
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX – 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX – 82443BX/ZX/DX AGP bridge (rev 03)
00:02.0 CardBus bridge: Toshiba America Info Systems ToPIC97 (rev 05)
00:02.1 CardBus bridge: Toshiba America Info Systems ToPIC97 (rev 05)
00:05.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:05.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:05.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:05.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:07.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01)
00:0a.0 Communication controller: Toshiba America Info Systems FIR Port (rev 23)
00:0c.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
01:00.0 VGA compatible controller: Trident Microsystems Cyber 9525 (rev 49)
14:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03)

Device 14:00.0 is the Xircom RBE-100.

ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:10:A4:F8:DA:F9 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:11 Base address:0×4000

lo        Link encap:Local Loopback 
          LOOPBACK  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

dmesg
Yenta ISA IRQ mask 0×04b0, PCI irq 11
Socket status: 30000020
Yenta ISA IRQ mask 0×04b0, PCI irq 11
Socket status: 30000007
cs: cb_alloc(bus 20): vendor 0×115d, device 0×0003
PCI: Enabling device 14:00.0 (0000 -> 0003)
cs: IO port probe 0×0c00-0×0cff: clean.
cs: IO port probe 0×0800-0×08ff: clean.
cs: IO port probe 0×0100-0×04ff: excluding 0×378-0×37f 0×4d0-0×4d7
cs: IO port probe 0×0a00-0×0aff: clean.
PCI: Setting latency timer of device 14:00.0 to 64
eth0: Xircom cardbus revision 3 at irq 11

Here, I’ve only included the relevant information.  Notice that the Xircom card was assigned to eth0.

5) And that should be it.  Here are some references that helped me get to this point.

http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-3.html
Contains more detailed information about installing and debugging PCMCIA devices

http://www.unix-manuals.com/refs/vi-ref/vi-ref.htm
Reference guide to vi editor.  A lightweight editor that comes with the DeLi Linux distribution.  The vi editor is handy for editing the file I mentioned in step 2.

http://linux-hotplug.sourceforge.net
Contains more detailed information about the hotplug program
 

How to uncompress/unarchive Unix files

When using Unix or Linux, it is easy to forget the magic incantations needed to do something. In the spirit of sharing information and making it widely available, this article documents how to uncompress Unix files that end in particular suffixes. This list will be updated on a regular basis when I encounter different compressed formats.

For files that end in…

• name.tar.gz
  • invoke tar xvfz name.tar.gz
• name.tgz
  • invoke tar -zxvf name.tgz
• name.tar.bz2
  • invoke bunzip2 name.tar.bz2 | tar x -f
• name.zip
  • invoke unzip name.zip
  • Note: gunzip won’t work on files that have a .zip suffix.
• name.gz
  • invoke gzip -d name.gz

If there are other tar-like or other compress/uncompress commands that you know about, please let me know.