Finding unintuitive commands. (was Re: Three Random Simple Questions)

[Peter Garrett]

On Thu, 20 Oct 2005 11:18:27 -0700
Scott <angrykeyboarder at gmail.com> wrote:

> 
> >Thank you for your responses. I might not have made it clear before that
> >I am a newbie, so while I took the advice as far as I understood it, I
> >did have a hard time processing it.

Regarding finding obscure commands (and these are IMO extremely obscure ;-)  )

You can use the packaging system to track down the executables/binaries thus:

peter at prospero:~$ dpkg -L bittorrent | grep bin
/usr/bin
/usr/bin/btcompletedir.bittorrent
/usr/bin/btdownloadcurses.bittorrent
/usr/bin/btdownloadheadless.bittorrent
/usr/bin/btlaunchmany.bittorrent
/usr/bin/btlaunchmanycurses.bittorrent
/usr/bin/btmakemetafile.bittorrent
/usr/bin/btreannounce.bittorrent
/usr/bin/btrename.bittorrent
/usr/bin/btshowmetainfo.bittorrent
/usr/bin/bttrack.bittorrent

Of course it *still* isn't really clear how the heck you use these commands.... At this point it's worth typing 

apropos bittorrent

which outputs a whole *heap* of possible man pages to be puzzled by....  :-/

I'm of the view that this particular package needs some serious documentation love, and some sensible command names, but I don't know the first thing about the subject of bittorrent, so I can't really help to clean up the mess ;-)

I just offer the above strategy as one way to proceed when the command is as unintuitive as these ones!

Peter
-- 

Linux User #343161