The keychain

 Where it all started

I have several computers at home and usually one or two at work. It wasn't uncommon for me to wonder where I had last placed a web link or where the principle copy of a file resided. I decided to scoop all the web links onto a memory stick and, thus was born, "Redstick". The notion of centralizing such information spread to the issue of locating current files and then providing links or some way to find either the file or notes about same. The idea just grew.

A major improvement in the history of personal organization happened the day I declared that "Redstick" held the principle copies of all my files and that everything else was a backup. That notion upped the priority of moving all current files to the memory stick and it reduced the importance of many computers in my life. Computers were now just machines holding certain combinations of applications - and they were places to edit files on Redstick. Now I felt like I always had with me the information needed for any task. I quit wondering where a particular file was or what the state of backups was. It was very liberating. But, after several months of hard, daily (hourly?) use, I can see that the stick is slowing down and I read that these wonderful things will actually wear out.

In October '07, a set of scripts now move selected html files to a real website. The revised files no longer distinguish between Web and local files; some personal, budget-related files, are not moved to the Web for obvious reasons.

The memory stick is an 8GB Verbatim unit. The 8GB allows us to store our 4GB of digital images; the scripts etc are relatively small.


link is on the Web and thus can't be viewed unless the computer has a connection to the Internet. In all most other cases, links reference "local" files on the "keychain memory stick". The exception to this general rule occurs when a memory stick is made such that it omits certain personal information. If a link should happen to refer to such personal information, the browser will show the standard "couldn't load that page" error message.

There are Linux applications (programs) on the keychain, Cygwin programs, and Windows applications. Each type of program resides in a directory (folder) corresponding to that program type.

You could copy programs from the memstick to a program directory on the computer you're using. I prefer to add the memory stick to the path of the computer.

Installing on cygwin

Each cygwin shell should contain a copy of what's in this memory stick as /home*/*/.bash_profile. That logic will modify the PATH whenever a shell is started up.

The cygwin startup scripts have been massaged to address Redstick issues. These files are in public/bin/cygBashfiles/* and can figure out which drive letter corresponds to Redstick. The files intelligently set aliases and path variables, like $web and $scripts.

Installing on linux

Fedora 8 is coming to my world soon. I expect to clone the cygwin files to handle startup issues.

Installing on Windows

Uploading to website

  1. prompt> -web -o /cygdrive/c/tmp
  2. upload help at
  3. echo planeName > ftpcmds.txt
  4. echo 1stPwd >> ftpcmds.txt
  5. echo dir >> ftpcmds.txt
  6. echo bye >> ftpcmds.txt
  7. ftp -i -v < ftpcmds.txt > ftp.out

Todo List for this memstick project

file: about.html