Thanks to all who answered to my question.
I will not submit the patch then. I agree with all the people that
answered to my question, we must provide man pages easy to read for
first time users but, as Theo said, "man -k" can certainly help.
Even if someone does not know how reading the manual p
On Tue, Nov 07, 2006 at 07:39:35PM -0500, Nick Guenther wrote:
> On 11/7/06, Jason McIntyre <[EMAIL PROTECTED]> wrote:
> >
> >just before i replied to this, someone else posted that setting up
> >wireless is non-trivial for a beginner. how can we make it clearer? i
> >plug in my card; ral(4) shows
On 11/7/06, Nick Guenther <[EMAIL PROTECTED]> wrote:
On 11/7/06, Jason McIntyre <[EMAIL PROTECTED]> wrote:
>
> just before i replied to this, someone else posted that setting up
> wireless is non-trivial for a beginner. how can we make it clearer? i
> plug in my card; ral(4) shows up in dmesg; ma
On 11/7/06, Jason McIntyre <[EMAIL PROTECTED]> wrote:
just before i replied to this, someone else posted that setting up
wireless is non-trivial for a beginner. how can we make it clearer? i
plug in my card; ral(4) shows up in dmesg; man ral; /EXAMPLES
Beginners do not know that "ral0 attache
OTECTED] On Behalf
Of
> Bob Beck
> Sent: Tuesday, November 07, 2006 1:42 PM
> To: misc@openbsd.org
> Subject: Re: proposed patch for ifconfig(8) man page
>
> * Jason McIntyre <[EMAIL PROTECTED]> [2006-11-07 11:25]:
> > On Tue, Nov 07, 2006 at 06:52:19PM +0100, Igor Sobrad
On Tue, Nov 07, 2006 at 11:42:01AM -0700, Bob Beck wrote:
>
> To give you an example. let us answer the simple question of "how do
> I join wireless network "bob"" - the answer from the lists is "use
> ifconfig" - ok, so if I read the man page for ifconfig, there is
> notably no examples of
Bob Beck wrote:
* Jason McIntyre <[EMAIL PROTECTED]> [2006-11-07 11:25]:
On Tue, Nov 07, 2006 at 06:52:19PM +0100, Igor Sobrado wrote:
Can I suggest adding atalk(4), inet6(4), ipsec(4), pf(4), pflog(4),
eon(5), hostapd(8), and tcpdump(8) to the "SEE ALSO" section of
ifconfig(8)? I thin
> Just want to say that I totally agree with Igor - joining new networks to
> yer obsd box is non-trivial if you are a beginner - collecting a few more
> instructive examples in ifconfig(8) would not be amiss in my opinion.
You've got to be joking. Every wireless man page has sufficient details.
Hi list,
I have not followed every message in the thread so forgive me if I write
something totally irrelevant
Just want to say that I totally agree with Igor - joining new networks to
yer obsd box is non-trivial if you are a beginner - collecting a few more
instructive examples in ifconfig(8
> The core problem is simple - a user will be told "use ifconfig"
> to do something not "use ath" - so they start at the ifconfig(8) point.
> What's the best way to make that as painless as possible?
man -k is the solution to that. Increasing the length of the Xr's
at the bottom of the ma
* Jason McIntyre <[EMAIL PROTECTED]> [2006-11-07 11:25]:
> On Tue, Nov 07, 2006 at 06:52:19PM +0100, Igor Sobrado wrote:
> >
> > Can I suggest adding atalk(4), inet6(4), ipsec(4), pf(4), pflog(4),
> > eon(5), hostapd(8), and tcpdump(8) to the "SEE ALSO" section of
> > ifconfig(8)? I think that, a
On Tue, Nov 07, 2006 at 06:52:19PM +0100, Igor Sobrado wrote:
>
> Can I suggest adding atalk(4), inet6(4), ipsec(4), pf(4), pflog(4),
> eon(5), hostapd(8), and tcpdump(8) to the "SEE ALSO" section of
> ifconfig(8)? I think that, as these manual pages are being cited
> in the ifconfig(8) manual pa
Hello,
Can I suggest adding atalk(4), inet6(4), ipsec(4), pf(4), pflog(4),
eon(5), hostapd(8), and tcpdump(8) to the "SEE ALSO" section of
ifconfig(8)? I think that, as these manual pages are being cited
in the ifconfig(8) manual page, they should be added to this section.
Just want to check the
13 matches
Mail list logo
