Moving w3m out of standard

[Rich Kulawiec]

As an die-hard old-school (err, make that, "ancient school") 'nix admin
I applaud the idea of trying to keep installs minimal, both for space
and security reasons.

On the other hand, I recognize the value of having some basic utilities
handy to administer services, test them, debug them, and fix them.
Like many other people, I've got a favorite set that I often find
useful.  I try to keep that set restricted to those that I can run
on a low-bandwidth ssh connection, because that's often exactly
what I have to do, and I try to avoid overlapping tools (although
arguably two of my choices, curl and wget, at least partially do so).

My suggestion is that discussion take place over (a) whether it makes
sense or not to bundle a collection of such tools for easy installation,
and (b) what tools might be good candidates for inclusion.  Here are
the ones that I've used across a variety of 'nix systems; I don't
claim that this list is the best or most inclusive or anything, it
just happens to be the toolset that I've found lets me deal with
most of the things I've had to deal with.

	curl
	dig (part of the BIND distribution)
	lslk
	lsof
	mutt
	nmap
	patch
	rsync
	screen
	surfraw (I *said* I was ancient-school)
	tcpdump
	top
	traceroute
	w3m
	wget

---Rsk