+
+ Applications
+
+
+ Processes Unix format text files for pcdos by
+forcing the line endings to be Carriage Return plus Line Feed (CRLF).
+
+
+ Turns the files passed on the command line into a
+stream of CGI compatible text output. The javascript show_file method
+(see the
+source for this page) is preferred since it is lighter weight and
+doesn't
+need cgi, but there are some situations where cgi is the only option
+(older
+browsers or requirements of no javascript).
+
+
+ Replaces the suffix of all filenames in the current
+directory
+with a different suffix. Suffix here is defined as the set of
+characters
+after the last period ('.') in the name. Note this will not work
+for
+names without suffices.
+
+
+ Copies files from a source directory into a
+destination directory. The files are only copied when they are
+missing in the destination or when the destination version has
+different contents. The syntax looks like this:
+ cpdiff source destination
+The assumption is that the files in the source directory are somehow
+better, newer or more complete than the set of files in the destination.
+
+
+ Similar to cpdiff, but this utility sets the
+destination file's time stamp to "now". This should cause the new
+or changed files in the destination directory to be more recent than
+anything else in there. This is helpful sometimes for forcing
+compilation of modified source files.
+
+
+
+ Wraps the cygwin cvs command for pcdos/win32.
+ Any
+unfriendly backward slashes are flipped to be forward slashes.
+
+
+
+ Compares two directory hierarchies and the files
+they
+contain. The first parameter is a directory
+to compare against "this" directory;
+every subdirectory "here" will be traversed in order to build the
+output file that shows the differences. An optional second
+argument can be used to specify a different directory than the current
+one as the source of the comparison (the first argument is always the
+destination of the comparison).
+
+ Collects the contents of the files whose names are
+passed on the command line into one gigundo stream which is passed to
+standard output. The output can be piped into another file as desired.
+
+ Performs some useful activities for the shell
+environment. Using the environment variable for FEISTY_MEOW_SCRIPTS (which
+is set in the appropriate startup files to be the shell scripts
+directory, where all this stuff lives), generate_aliases will create
+all of the aliases files for the combinations of operating systems and
+types of shells supported. Currently this includes Linux, Unix,
+PCDOS, OS/2 and MS-WIN32 (9x, NT, 2K, XP, etc) for
+supported operating systems. The shell languages supported are
+dos's command, nt's cmd, unix's sh and bash, and perl. This script will also look for
+any files ending in ".sh" or ".pl" and it will create aliases for them
+in forms appropriate to the different shells. The .zz_feisty_loading
+subdirectory is created under the home directory as a storage place for the generated script
+files.
+
+
+ Generates a signature file from the nechung
+database
+using the 'nechung' application. See the Feisty Meow Concerns Codebase for the nechung
+application.
+ The database for nechung resides in the whole Feisty Meow Concerns code package in "feisty_meow/infobase".
+
+
+ Renames all of the files passed on the command line
+such that they are only in lower-case. Useful if you're tired of
+passing mistakenly re-capitalized names from a defective 8.3 OS (e.g.
+Doze95/98) to
+a file system where you care about the case.
+
+ Finds all executable files in the current directory
+(and subdirectories) and runs them. The output of the programs is
+sent to standard output. Standard error is used to report which
+file is being worked on, plus the running programs' own standard error
+streams are merged into runner's standard error stream. This
+makes it nice to do something like:
+ runner >runs.log
+where the runs.log file will contain the output of each program that
+was executed and the console will be sent messages as each program is
+started and finished (and errors show up at the console also).
+
+
+ Makes deleting files and directories a little less
+nerve-wracking. If you substitute safedel as an alias for rm or
+del or deltree or whatever, it will make a zipped backup of the items
+before they are actually deleted. Safedel keeps track of a number
+that is attached to each zip to enforce uniquely numbered
+archives. They are stored in a directory named "zz_safedel_keep"
+that is stored under the temorary directory (specified by the
+environment
+variable named TMP). A report of the contents of the compressed
+trash
+is appended to a file named "zz_safedel.rpt" in the TMP directory.
+Occasional
+cleaning of the deleted files folder is recommend, but this utility has
+saved
+my various parts several times already.
+
+
+
+ A snarf utility that packages up the
+important configuration files in a Linux installation.
+
+
+ A selective snarf of the source hierarchy.
+This
+collects the code that I manage. As such, this is probably
+irrelevant to anyone but CAK.
+
+ Gathers all "important" files from the home
+directory.
+ This
+is somewhat personally tuned but it includes files and directories that
+have
+"project", "notes", or "crucial" in their name.
+
+
+ A source code grabbing snarfer. The entire
+source
+code hierarchy is snarfed. Note that one should edit the
+hierarchy
+location to make it appropriate for your local source code.
+
+
+ Offers a directory listing along with total file
+sizes
+and disk free space.
+
+
+
+ This is a helper utility that synchronizes the binary
+outputs from a build process with an existing installed location. Given a target directory, the executable
+programs and dynamic libraries that exist there will be synchronized
+with the build repository's versions. This is kind of a quickie
+upgrade process, as long as the files in the target location are not
+locked by other processes.
+
+
+ Uses the snarfer utilities to undo a previously
+snarfed file. A folder named "snarf_BASE" is created for the
+contents, where BASE
+is replaced with the basename of the snarf file (that is, without the
+".snarf"
+suffix). The number that tracks the snarf files of this type is
+updated
+such that the next snarf file will be at least one higher than this
+snarf's
+sorta
+unique number. The number will be managed correctly if you're
+always
+unsnarfing the most recent snarf files before creating any new snarfs.
+
+
+ Since all of my file deletion commands are aliases
+to safedel, it is hard to actually remove a
+file. If I'm really really sure that a file or directory needs to
+be
+permanently deleted, then this command can be used. It shows the
+names
+it is removing also, but it does _not_ ask for confirmation.
+
+
+ Tests the system for survival
+past the year 2038, which is when the Unix time scale runs out of bits
+for the number of seconds since 1970 measured in a 32 bit integer.
+
+
+ Removes empty directories and directories
+containing only
+unimportant crud (see "filename_helper.pl").
+If there are no arguments, then the current directory is cleaned up;
+any subdirectories
+will be traversed into and removed if it seems appropriate.
+Otherwise,
+zapdirs operates on the arguments passed to it as if they are directory
+names
+to be cleaned.
+
+ |
+
+