The linux-wlan(tm) Company

715-D North Drive * Melbourne, FL * 32934-9244
Telephone 321.259.0737 * Fax 321.259.0286
E-Mail info@linux-wlan.com

Introduction

THESE INSTRUCTIONS ARE PROVIDED ON AN ``AS IS'' BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE INSTRUCTIONS ARE FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE INSTRUCTIONS IS WITH YOU. SHOULD ANY OF THE INSTRUCTIONS PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL AUTHOR OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF USING THESE INSTRUCTIONS. THESE INSTRUCTIONS MAY NOT BE DUPLICATED IN ANY WAY WITHOUT THE EXPRESSED WRITTEN CONSENT OF THE AUTHOR, EXCEPT IN THE FORM OF BRIEF EXCERPTS OR QUOTATIONS FOR THE PURPOSES OF REVIEW. THE INFORMATION CONTAINED HEREIN IS FOR THE PERSONAL USE OF THE READER AND MAY NOT BE INCORPORATED IN ANY PUBLICATION, DATABASE, OR SOFTWARE OF ANY KIND WITHOUT THE WRITTEN CONSENT OF THE AUTHOR.

Contents of this information written by Vipul Gupta on September 13, 1998. Vipel is not an employee of AbsoluteValue Software. Vipel is a nice guy who gave us these instructions so we could install Linux on our Toshiba Libretto, and he gave us permission to post these notes on our web site.

Installing Redhat 5.1 on a Toshiba Libretto 50CT

This note describes my experience with Redhat Linux 5.1 on a Toshiba Libretto 50CT. It includes instructions on installing Linux and adding other user applications and system programs that address:

• multimedia communicationn (LBL tools -- sdr, vic, vat, wb), and
• the special needs of nomadic users -- changing networks, power management and diconnected operation.

The Installation

In my experience, there are two main obstacles to installing Linux on a portable system. The first one is repartitioning your harddisk (of course this is not a problem if you don't mind blowing away windows). The second one is configuring X for your system, i.e. getting the right Xserver and XF86Config file. Again, this is not a problem if you can copy these files from someone already running linux on the same hardware platform. These problems aren't unsurmountable, but they can take a few hours.

Partitioning your hard disk

Unless you wish to blow away the Windows partition completely, you will need to create a separate partition for Linux. If you are lucky (like Gab and Becky), your portable already has a second hard disk partition and you can proceed with Linux installation. Otherwise, you'll have to shrink your windows partition and create a new one for Linux. While there are both commercial programs (like system commander) and freeware utilities (like FIPS, see http://www.igd.fhg.de/~aschaefe/fips/) that can repartition your hard drive non-destructively, I recommend that you back it up completely before attempting to using any of these programs.

Sorry, I can't help you with backing up your system since I've never worried about losing windows. Ask around to see if others can help (Ashley used SMB, I think, and then FIPS 2.0). Repartitioning your hard drive is a sensitive operation and can cause you to loose valuable information if you fail to take appropriate precautions. Carefully follow the instructions of your partitioning program. FIPS, for example, requires that you run scandiak and defrag earlier.

Booting Redhat on a Libretto

If your portable system provides simultaneous access to a floppy drive and a network connection, the following process is considerably simplified. You only need to follow steps 6 and 7, connect the floppy drive to your system, insert the Redhat boot floppy and reboot. This will directly take you to step 9 (you can also ignore the part about replacing the floppy drive with a network card after the supplemental image is read)

1. Boot the Libretto under Windows and create a bootable DOS floppy (if you don't have one). Test and make sure it is indeed a bootable floppy.
2. Create a subdirectory called redhat
   
   c:> mkdir redhat
   
   
3. Through disk copying, FTP or any other means, copy loadlin.exe from Redhat CD#1 (under dosutils) to the new directory.
4. The redhat boot floppy contains a DOS filesystem with vmlinuz as one of the files. Copy this kernel image to the new directory as well.
5. Finally, grab initrd51 from
   
   http://www.geocities.com/SiliconValley/Haven/5112/
   
   (mentioned at http://ecg.mit.edu/george/libretto-4.html) and lace it in the redhat directory.
6. Since we'll be using NFS installation, we'll need PCMCIA support (for the network card) during installation. For this reason, you need to create a floppy with the supplementary image provided as supp.img (look under images in CD#1). You can either use rawrite ("raw write") under DOS or dd under UNIX to create this disk. You can also borrow my disk that already has this image. The Redhat book has further details.
7. Setup an NFS server that can export the RedHat directory on the first CD (let's call it CD#1)
   
   On my Solaris server, nobel, I inserted the Redhat CD and executed
   
   share -F nfs -o ro /cdrom/cdrom0
   
   to make its contents available for NFS sharing.
8. Attach the floppy drive to the Libretto and boot it in DOS mode using the bootable DOS floppy (from Step 1). Go into the redhat directory (created in Step 2) and execute
   
   loadlin vmlinuz initrd=initrd51
   
   After a while (assuming all goes well) you should seen the red,white and blue Redhat installation screen.
9. Follow the instructions (refer to the Redhat book, if necessary). Here are some of the steps involved:
   • Choose non-expert mode
   • insert the supplemental image disk (created in Step 7) when prompted (recall that we need PCMCIA network support for an NFS installation)
   • After the contents of the supplemental disk have been read, replace floppy drive with a network card in the Libretto's PCMCIA slot.
   • Chose NFS install
   • Configure TCP/IP (you'll need an IP address from your network admin -- if you need one only temporarily, you can use 129.146.122.191 for the 122-net that runs through most of the TD offices. On this network, use a netmask of 255.255.255.0, default router as 129.146.122.1 and DNS resolver as 129.146.1.151)
   • Configure the installation path, e.g. on the TD-net, I used
     server: nobel
     path: /cdrom/cdrom0
   • SCSI (No)
   • Disk Setup (Disk Druid)
     • Make the dos partition visible under Linux (/dos)
     • Delete existing second partition and create the following two in its place
     • Create a swap partition (I chose the swap size (64MB) to be twice the size of my main memory)
     • Create a root partition (/, Linux Native, 2997MB)
   • Active Swap space (OK)
   • Format root partition
   • Select packages (since I was short on hard disk, I was picky but it is probably simplest to choose "all" -- this is the last option on the menu).
   • Start the formatting and installtion (this takes a while depending on your disk size and the packages you choose -- on a 3GB Linux partition, reformatting and installing all packages can take about 45mins)
   • Setup program will probe for a mouse (most PC mice only have two buttons whereas some X applications assume three -- I recommend choosing 3 button emulation -- pressing both buttons will simulate a middle button press).
   • Next comes X configuration and it can be tricky -- mu advise is to choose conservative options and once X is up and running you can tweak things later. (After you finish installation and are able to access the Internet, you can search for a ready made XF86Config file your system -- see the section on Desktop configuration).
   • Time Config (leave the hardware clock setting blank, choose a time zone)
   • Pickup services to start (use F1 to figure out if you need a service). Again be conservative since you can always add services later. I recommend against using ypbind at this stage. amd should never be selected since autofs is a better alternative. For DHCP, DNS etc some of the services start up server daemons not client programs. On a portable computer, you don't need them. Similarly, stay clear of routing daemons like Gated and routed for a portable system.
   • Somewhere along the line, you'll be asked if you want networking at boot time and if you wish to store the configuration you picked for NFS. Say NO now. On portable systems, sometimes you may have to boot in stand alone (no network) mode and you do not want startup services to hang looking for a network that isn't there. You can set up a flexible network switcher style menu later.
   • Boot Loader (put it on the MBR)
   • Lilo options (none) [LILO is the multi-boot image loader and can be used to boot your system under Windows or Linux at boot up time]
     
     Normally, it is good idea to make a bootable floppy during installation (you'll see prompts on how to do this). Unfortunately, on the Libretto, once you've loaded the supplemental disk, your disk is no longer accessible so skip this option.
   • Bootable partitions: make the windows partition bootable -- you can pick a label that will be displayed by Lilo as a booting option.
   • After installation finishes, reboot the system -- you can try to boot both Windows and Linux (though not at the same time). [As soon as you see LILO: being printed on your console, press the TAB key and ? to get a list of all the bootable images.]

Congratulations, your basic installation is complete. Next, you can try to get X working and setup your networking and desktop. The default Redhat kernel does not support power management so eventually you should recompile a new kernel with Advanced Power Managemnet support turned on -- that will allow you to put the Libretto in sleep/suspend mode while running Linux. You can also enable sound support and support for wireless extensions (for PCMCIA cards like the WaveLAN).

Getting on the net

I have ready-made configuration files for connecting to SWAN through a PCMCIA ethernet card and to the Internet through a Ricochet modem.

• Copy $GOODIES/ifcfg-eth0 to /etc/sysconfig/network-scripts/ifcfg-eth0 with permissions ...Modify the IP address
• Copy $GOODIES/chat-ppp0 to /etc/sysconfig/network-scripts/ifcfg-pp0 with permissions ...
• Copy $GOODIES/ifcfg-ppp0 to /etc/sysconfig/network-scripts/ifcfg-pp0 with permissions
• Copy ip-up.local and ip-down.local to /etc/ppp/ with permissions 755 (ownership root root). These scripts are called after a PPP interface has been configured. The script is called with five parameters:
  
  interface (ppp0), device (/dev/ttyS0), speed (19200) localip and remoteip
  
  My version of these scripts changes the contents of /etc/resolv.conf appropriately.
  
  ip-down.local simply "undo"es the changes made by ip-up.local.
  
  [Tip: With Redhat 5.1, even when the user chooses ifup ppp2, if no other ppp interfaces are plumbed, the first one plumbed is numbered 0 and the argument passed to ip-up.local is ppp0.]
• You can configure other network interfaces, if necessary, using netcfg. When you create a PPP interface, you'll also be able to customize a chat script (it takes the form of "expect send" pairs). I haven't yet figured out a way to use the chat script with Enigma based SWAN access. If you figure out a way to let an enduser intercept part of the chat, let me know. Steve Drach uses dip (rather than chat) to configure PPP for a SWAN connection. His e-mail on this subject is here.
• Recompiling the PCMCIA distribution doing a subsequent make install seems to overwrite redhat's default pcmcia configuration scripts. I actually like the new script -- it allows easy network switching between several network profiles associated with PCMCIA ethernet cards. The profiles are stored in /etc/pcmcia/network.opts and any one of them can be easily activated by using
  
  cardctl scheme
  
  My network.opts file currently defines three different schemes -- one each for the ethernet LANs in my office, home and lab.
  
  [See kernel compilation section below before you recompile the PCMCIA distribution].
• If you want non-root users to be able to activate/deactivate PPP interfaces and switch between different cardctl schemes, make sure that the ifcfg-ppp files say userctl=yes. Also make sure that PCMCIA package is compiled in "trusting" mode (see the following discussion on PCMCIA compilation) and that cardctl has the following permissions:
  
  -rwsr-sr-x root root /sbin/cardctl
  
  
• After you've settled on a small set of frequently used network profiles, you can set up your X desktop menus in such a way that any particluar profile can be activated by a 2-3 key strokes/mouseclicks (see the section on X configuration)

Power Management

• Recompile the kernel to support Advanced Power Management (APM). This is also a good opportunity to set the CONFIG_RADIO compile time variable which adds support for wireless extensions in radio-based network drivers (e.g. WaveLAN). The README file in /usr/src/linux/README describes how to go about compiling a new Linux kernel. You should recompile all modules (including PCMCIA modules) so they also have APM/wireless features enabled. See the PCMCIA-HOWTO in /usr/src/linux/pcmcia-cs-3.0.0 for pcmcia compilation.
• After APM is enabled in the kernel, you can use the apm command to either put your system in sleep or suspend mode. In sleep mode, the system state is left in memory and the memory is kept warm, whereas in suspend mode this state is written out to disk. Keeping the memory warm drains power but the system is able to wake up instantaneously. The Libretto 50 with a fully charged extended battery, can stay in sleep mode for nearly three and half hours (maybe more). Resuming from suspended state can take a while as the system state is restored from disk but a suspended system consumes no power. With 32MB RAM, the Libretto 50 takes 20-30 seconds to resume after a suspend.
  
  Sleep: apm -S
  Suspend: apm -s
  
  Another thing to note about the Libretto is that when apm -s is executed, the system writes out its state to disk *and also* keeps the memory warm for about 5 mins. So within the first 5 mins after initiating suspend mode, the system can resume instanataneously.
  
  [The Libretto's BIOS reserves an area on the hard disk for suspend/hibernation mode and hides that area from programs such as the Disk Druid and Fdisk so users cannot accidently put user data in that region.]
  
  Enable the "setuid on execution" bit on the apm executable so regular users can put the system in sleep/suspend mode (clearly, this is not a good idea on a multi-user system but portable computers are generally personal devices, i.e. used by only one person at a time (serial use model).
  
  Using a flashdrive (see Sandisk's web page www.sandisk.com) should reduce the resume time after a suspend to disk. Flashdrives are fully compatible with IDE drives and offer fast read times and consume lesser power compared to ordinary drives. They are also more expensive costing about $4/MB (a 220 MB drive is $880 and a $500 MB drive is roughly $1900 when purchased in small quantities -- less than a hundred). I expect to receive a 220 MB Sandisk flashdrive for evaluation in the next couple of weeks. It should be interesting to see how close it can get us to "instant on" and how it affects power consumption.
• Edit the file /etc/sysconfig/apmd created during Redhat 5.1 installation to use "-p 5 -w 10 -W" rather than "-p 10 -w 5 -W" or else the low power warning comes too late (see man apmd).
• Even with regular hard drives, you can minimize their power consumption by configuring the disk spin-down time, e.g. when I am editing or reading a file on-line (i.e. infrequent writes), I use
  
  hdparm -s 2 /dev/hda1
  
  to set the idle spin down time to 10 seconds (see man hdparm on how the argument to -s corresponds to the idle time -- for most cases, the argument is multiplied by five to arrive at the idle time). From what I can tell, the command is not remembered across sleep/resume or suspend/resume or a reboot.
  
  Using Hdparm, one can also force a disk into entering a power-save mode immediately. Like apm, this is a previliged command and you must enable setuid on execution if you want regular users to execute hdparm
  
  # chmod ugo+s /sbin/hdparm
  
  
• Eject any PCMCIA cards when they are not in use to minimize power consumption. You can also use the cardctl command (man cardctl) to power manage the PCMCIA subsystem.
• Here are some observations related to power consumption on the Libretto 50CT:
  
  It can stay in sleep mode (without suspension for nearly 5.5 hrs 330 mins). With hdparm -S 3, I was able to log in to Sun's modem pool (from home) and work for almost 1.5hrs while only using 60% of the battery ... no penalty due to disk spinning. Other observations -- libretto comes out of its sleep mode whenever a packet is received this is true for both ppp links (tested using ricochet) and ethernet (wavelan and 3com). Infact, with the ethernet card inserted it is almost impossible to keep the Libretto in Sleep mode ... there is a lot of traffic on the net and even though most of it is not meant for the Libretto, the libretto's kernel is involved in filtering those packets.
  
  With both Vic and vat running (MSNBC Satellite feed on the TD net) on the Libretto connected through the WaveLAN, the battery drains at approximately 1% per minute. While sdr was running, I couldn't get the hard disk to spin down (sdr seems to access it frequently). After sdr was terminated, and the disk spun down, battery drained as follows:
  
  At 11:21:25 battery reading was 11%
  At 11:26:05 battery reading was 5%
  At 11:30:09 battery reading was 1% (again, roughly 1% per min)
  
  but then it got interesting -- for the next 29 minutes, the power indicator stayed at 1% and finally at 11:59:04, apmd generated a "low battery" notification It seems that the battery measurement isn't very accurate close to 1% so to really determine the effect of vic/vat on battery *while* the hard disk has spun down, these experiments need to be conducted when the battery has more juice.

Desktop Configuration and Special Applications for nomads

• My XF86Config file is here. Arriving at the right XF86Config used to be a frustrating experience. Fortunately, there is a growing database of XF86Config files for many different laptops at:
  
  http://www.st.rim.or.jp/~adats/WL/XF86Config/index.html
  
  Other good sources include:
  
  ftp://ftp.redhat.com/pub/XBF/README.neomagic
  http://www.fumi.org/vaio/
  http://www.mnsinc.com/js/Neomagic.html
  http://www.st.rim.or.jp/~adats/WL/XF86Config/index.html
  http://www.cs.utexas.edu/users/kharker/linux-laptop/
  http://www.yy.cs.keio.ac.jp/~sanpei/note-list.html
  
  You'll need to place its contents in /etc/X11/XF86Config.
  
  If you can't find a ready made configuration file, you'll have to use Xconfigurator (this requires knowledge of your video chip -- manufacturer, model and the amount of Video RAM you have). After X is properly configured you may wish to enable xdm on your Libretto which will enable X by default -- users won't need to execute startx explicitly. Before enabling xdm by editing /etc/inittab and changing the default runlevel to 5, make sure that your system behaves correctly at that runlevel by trying telinit 5 (see man telinit).
  
  X is started by executing startx command.
  
  
• Previously, I mentioned that Linux provides nice mechanisms for switching network configurations and also for power management. However, I really started making full use of these (and other) features only after they were closely integrated in my desktop menus. If you'd like to experiment with my tweaks, save a copy of your /etc/X11/AnotherLevel/fvwm2rc.menus.m4 and replace its contents with those of $GOODIES/fvwm2rc.menus.m4. Also copy $GOODIES/mini-house.xpm and $GOODIES/mini-sleep.xpm (these are pixmaps used in the new menus) to the directory /usr/share/icons/mini/ (ownership root root, permissions 644).
  
  The tweaks add three options to the "Start" menu:
  1) Favourites (or Favorites :-))
  This popsup a menu of frequently used apps e.g. acrobat reader, battery-life indicator, browser, mail reader, text and image editors, file viewer, mpeg player, Mbone tools, calculator, filesync, minicom etc.
  
  If you are interetsed in adding ssh, acroread, iwconfig (for changing WaveLAN nwids), filesync (for disconnected operation) and the LBL conferencing tools (vic, vat, wb and sdr), you can grab precompiled binaries or links to them from /usr/local/bin on roverlab-15.
  
  SSH and Conferencing tools:
  
  The SSH compilation was starightforward. The LBL tools took more time -- when the LBL folks say the tools work with Tcl7.5/Tk4.1 they are serious. As I found out the hard way, the tools don't work with neither Tcl8.0/Tk8.0 (bundled with Redhat 5.1) nor Tcl7.6/Tk4.2 (which is supposed to fix bugs in Tcl7.5/Tk4.1)
  
  [All versions of Tcl/Tk are avialable under software central at http://www.scriptics.com/)]
  
  The vic and vat sources require two small changes before they can be compiled successfully:
  
  In config.h, search for int gethostid(void) (around line 86) and add "&& !defined(linux)" (without quotes) on the line before the gethostid line.
  
  In inet.h, search for the msghdr declaration (around line 97) and change the line immediately before it to read
  
  #if defined(Win32)
  
  i.e. remove the reference to linux.
  
  Vat also requires that sound be properly configured on your system. I used sndconfig and selected the following options for the Libretto 50CT (for this to work, you must also enable sound support in your kernel)
  
  Card Type: Soundblaster Pro
  Card Settings:
  IO Port 0x240
  IRQ 5
  8-bit DMA 0
  
  Sndconfig sets up /dev/audio so .au files can be played by sending them directly to /dev/audio, e.g.
  
  cat welcome.au > /dev/audio
  
  The Redhat installtion includes sox (see man sox) which can convert between all kinds of audio file formats.
  
  Even with the Libretto's 75 Mhz Pentium processor and a wavelan connection (without QoS), vic and vat perform reasonably well. You can walk around the corridors listening/ watching MSNBC.
  
  Filesync:
  
  I've ported filesync from Solaris 2.7 to Linux. Linux does not implement nftw (the new file tree walk) or gmatch so these had to be simulated using ftw and fnmatch. There were other changes as well but nothing major. I've also added a simple Tk front end to filesync. Filesync allows a user to replicate a directory structure and keep the original and the replica in synch. I have replicated a set of five files with the following structure from my home directory on hsmpka (at Sun) to my home directory on the Libretto.
  
  public_html
  |-- Redhat-Tips
  | |-- README
  |-- networking-tips
  |-- index.html
  |-- linux.html
  `-- redhat-on-libretto.txt
  
  My home directory at Sun is available (through an NFS mount) on the Libretto whenever I have network reachability to hsmpka. Over a ricochet PPP connection to SWAN (through the TD modem pool), a filesync operation on this structure took about 1 minute. The same operation over an ethernet connection is instantaneous.
  
  2) Sleep
  
  3) Suspend
  
  The sleep option invokes sleep 5; /usr/bin/apm -S; xlock -mode random There is an interesting reason behind the five second delay before the apm command. It is meant to give the user enough time to fold down the screen before apm kicks in. Otherwise, the act of folding the screen cause the screen backlight to be turned off and this event wakes up the system. Effectively, the user leaves the system thinking it is sleeping when it is actually running at full power. The xlock command is a (mild) protection feature. In the scenario when the mobile device is left unattended (never a good idea), the xlock prevents an unauthorized user from looking at the screen contents by simply waking up the system. Some systems (but not my Libretto) waking up from sleep mode. to enable BIOS password protection does prompt for a BIOS password upon resuming after a suspend operation. Unless you are extremely paranoid (BTW, I agree that they are *really* out to get you), you should not enable BIOS password protection. I regret enabling this on my system because now everytime it resumes from suspend state, I have to wait about 5 seconds for the BIOS password prompt and wait another 15-25 seconds for the restore operation. While the total wait is the same, I find it is easier to mask a single delay of 20-30 seconds (I'd hit the power button and do something else) than it is to mask two smaller delays that require user input between them.
  
  [If you worry a lot about the privacy of information on your disk, you should consider encrypting it. Redhat 5.1 includes a script called cryptdir which simply uses crypt to encrypt all files in a directory. I don't seem to have crypt on my system (I don't have a full Redhat installation -- maybe that's why) so the script fails. Ideally, Linux could provide an application-transparent encrypted file system that automatically encrypts data on writes and decrypts it on reads. Based on how flexible the Linux filesystem code is, this shouldn't be too hard.]
  
  Under the existing "Preferences" option, the new configuration adds submenus for
  
  
  1. Network preferences (these invoke the ifup/ifdown commands for PPP interfaces and the cardctl scheme changing commands for wired/wireless ethernet interfaces)
  2. Disk spin down (invokes hdparm with different parameters), and
  3. Pine: I use two configurations for this mail reader -- one is called Sun and uses my INBOX on hsmpka and another one is called Local and reads mail from the mail spool directory on the Libretto.
  
  
  Disconnected mail:
  
  When I enter my office, I choose the office network profile, insert my ethernet card and connect to a hub in my office. If I have time to read e-mail in the office, I choose the Sun profile for Pine and read email in "conected" mode. Otherwise, I invoke fetchmail from my list of favorite programs. The .fetchmailrc file in my home directory is configured so that fetchmail uses IMAP to suck all the new messsages from my mailbox on hsmpka and delivers them to the local sendmail process.
  
  [Here's my .fetchmailrc file:
  pool hsmpka.eng.sun.com proto IMAP timeout 30:
  user , with password , is root here;
  limit 500000; expunge 50; keep
  
  
  and are replaced by my username and passowrd on the mail server hsmpka (see man fetchmail for details).]
  
  Even with a large INBOX (containing approx 2000 messages with about 10-15 new ones), fetchmail takes only about a minute to deliver them locally over a 10Mbps ethernet connection (the same thing over a Ricochet modem is a very different story -- it makes me want to clean up and reorganize my mailbox :-)). Once fetchmail completes, I am free to disconnect from the net and read my e-mail (even answer it) by choosing the local Pine profile. [Given how some meetings go, catching up on e-mail is a great way to salvage time :)]
  
  If you experience long delays as fetchmail tries to deliver mail locally, check your sendmail daemon. It may be trying to look up the sender's address using the wrong DNS resolver. Apparently, sendmail consults /etc/resolv.conf only at start up time. You may have changed your location so that the older resolver is no longer reachable. When I first experienced this problem I found that sendmail was using an @home resolver even though I was inside Sun using my office network profile. The starightforward solution is to reboot while using the Sun profile and subsequently use suspend/resume rather than reboots.
  
  Disconnected browsing:
  
  The Red Hat distribution includes wget which can recursively fetch web pages in non-interactive fashion. If you wish to browser a web site off-line, point wget at that site (see man wget for the appropriate parameters) and fetch all files to the local disk.
  
  

Other Tips

• window manager is controlled by /etc/X11/xinit/Xclients
• When using glibc, make sure networking code includes files from rather than or else compilation will fail with a number of error messages related to duplicate definitions (I've added these changes to the Linux Mobile IP code, see /home/vgupta/Mobile-IP/NewSrc/Client/mnmiplinux.c for more details).
• Lynx configuration is in /etc/lynx.cfg -- set up proxies if needed.
• mtv (an MPEG Audio/Video player from http://www.mpeg.org/ is worth the $10 shareware price.
• Linux Mobile IP software is available from
  http://playground.sun.com/pub/mobile-ip/Linux/
• The Linux DHCP client operating against a Solaris DHCP server still seems flaky (once it is stable, can put it in the menus).
• There is a an experimental irDA stack for Linux. Rememebr to execute make depend before make all. It compiles but I haven't been able to test it since I currently don't have anyone to test against. Supposedly, you can beam objects between a Linux box and the Palm III from 3Com.
• Got the Linux driver for Harris 802.11 (2 Mbps) card from Mark Mathews (see www.linux-wlan.com). The Intalk card used a later firmware revision (1.5) not supported by the curret driver. Mark will send us the older firmware. Unlike the Lucent/NCR WaveLAN card, the Harris card has a compact built-in antenna. In a couple of years, Harris expects to have a 10Mbps version.
• You can configure printer support from the control_panel application. For tdhp_1, the remote server is tdserver and remote print queue is tdhp_1. I had to blow away and recreate /var/spool/lpd/lpd.lock with group set to lp.
  
  My /etc/printcap looks like:
  
  

  #

  # This printcap is being created with printtool v.3.27

  # Any changes made here manually will be lost if printtool

  # is run later on.

  # The presence of this header means that no printcap

  # existed when printtool was run.

  #

  ##PRINTTOOL3## REMOTE POSTSCRIPT 600x600 letter {} PostScript Default {}

  tdhp_1:\

  :sd=/var/spool/lpd/tdhp_1:\

  :mx#0:\

  :sh:\

  :rm=tdserver:\

  :rp=tdhp_1:\

  :if=/var/spool/lpd/tdhp_1/filter:

  ##PRINTTOOL3## REMOTE POSTSCRIPT 600x600 letter {} PostScript Default {}

  gaudyps:\

  :sd=/var/spool/lpd/gaudyps:\

  :mx#0:\

  :sh:\

  :rm=gaudy:\

  :rp=PS:\

  :if=/var/spool/lpd/gaudyps/filter:

  # end of /etc/printcap