Subject: Re: [netatalk-admins] specifying zones with nbplkup?
From: dkelly@hiwaay.net
Date: Wed Aug 27 1997 - 22:25:25 EDT
wesley.craig@umich.edu replies:
>
> > From: dkelly@hiwaay.net
> > To: netatalk-admins@umich.edu
>
> > I think nbplkup(1) should have more detail.
>
> It used to have all of the detail, but since papd, afpd, pap, aecho,
> and anything else for netatalk that's written correctly uses nbp_name()
> to do the parsing, I moved the detail there.
I agree, the information is all there. But it was about a hair's width
shy of being comprehesable on the first couple of reads. The example
given shows great promise:
EXAMPLE
Find all devices of type LaserWriter in the local zone.
example% nbplkup :LaserWriter
Petoskey:LaserWriter 7942.129:218
Gloucester:LaserWriter 8200.188:186
Rahway:LaserWriter 7942.2:138
517 Center:LaserWriter 7942.2:132
ionia:LaserWriter 7942.2:136
Evil DEC from Hell:LaserWriter 7942.2:130
Hamtramck:LaserWriter 7942.2:134
Iron Mountain :LaserWriter 7942.128:250
example%
but the addition of a couple of lines saying something like:
nbplkup on a specific zone:
example% nbplkup "@Bld 7"
Search for LaserWriters on a specific zone:
example% nbplkup ":LaserWriter@Bld 7"
would go a long ways. And that's all I'm suggesting. No need for example
output.
I keep forgetting the command to list all zones. Might be good to add
to SEE ALSO as I wonder about that when looking at the nbplkup page. Or
is it nbplkup that lists all zones?
-- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:26:30 EST