Without the right tools, the task at hand often takes far greater
time and effort. All tradesmen know this basic rule of doing
business. Obviously computer systems and network design,
implementation, and administration are not immune to this law.
In fact, as the system grows in size and complexity, the right tools
are essential. This is one of those epiphanies that is like a
right of passage in the Unix world. And the next can be summed
up as "the simple solution is almost always the correct one" or
"the beauty of (or in) simplicity." Many will never reach
these conclusions within their lifetime.
The point? Two fold; avoid complexity and automate, automate,
automate! Let the tools do the work for you, reducing your
OPEX. Its the double-edged dagger that kills the cycle of the
urobouros for the computing
industry. Of course, data representation, statistics, & etc.
help the planning and development processes.
Stick to the basics - keep the overheads low and keep the network
offering simple, stable, fast, and cheap.
We are experienced with many tools and have developed several of our
own over the years. This includes complete packages to one-page shell
scripts, and modifying other folk's software.
So, here is a tool catalog, one that will surely grow. This
includes tools that we have been involved in the development of,
or altered and some that we simply find very useful.
See the package's home page for copyright, license, and additional
Disclaimer: Shrubbery Networks, does not endorse these
packages nor do we provide support. Please contact the authors
of the respective package(s) for more information.
Then theres the following collection of data which we enjoy having at
our finger tips and its of general utility. Some of them are just
links, others are local copies, which is a life saver when it's source
happens to have server maintenance at the same time that we need the
This version is rather old, but
it comes in handy sometimes
- RFCs, STDs, etc
or find the originals at
- RFCs at the IETF
or RFCs at ISI
- The RFC
- WG drafts
- Solaris 2.9 Answer_books
/ Filesystem Hierarchy Standard
- SUSv3 / Single Unix Specification
but its best for you to get it from the source,
The Open Group