From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] 9 Atom - installation troubles
Date: Sat, 6 Dec 2014 19:47:52 +0200 [thread overview]
Message-ID: <4f652f4bfe78d198f5e2c85660f30d30@proxima.alt.za> (raw)
In-Reply-To: <20141206164233.Horde.ZwYDh1thBjLGXZFj1Slpuw1@ssl.eumx.net>
> This is detailed in the manpage for dial(2), which I know
> because I went through the exact process Lucio did but
> concluded there was no way someone would make things that
> hard for themselves... so I checked the documentation.
I could not find a _description{ for netmkaddr in the dial(2) man
page, but I wasn't looking very hard because I already had an
alternative solution in mind. The alternative solution didn't work
and Steve's suggestion, applied where it made better sense to me,
worked a treat. So now I know.
If I come up with a description for netmkaddr(2) worth adding to the
dial(2) man page, I'll submit a patch.
Lucio.
next prev parent reply other threads:[~2014-12-06 17:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 10:02 lucio
2014-12-05 14:20 ` erik quanstrom
2014-12-05 17:47 ` lucio
2014-12-06 19:02 ` erik quanstrom
2014-12-07 4:26 ` lucio
2014-12-07 5:15 ` lucio
2014-12-07 7:26 ` erik quanstrom
2014-12-07 7:33 ` erik quanstrom
2014-12-05 18:04 ` lucio
2014-12-05 18:15 ` lucio
2014-12-05 20:38 ` Wes Kussmaul
2014-12-05 21:23 ` Skip Tavakkolian
2014-12-06 4:43 ` lucio
2014-12-05 22:21 ` Bakul Shah
2014-12-06 4:57 ` lucio
2014-12-06 16:34 ` erik quanstrom
2014-12-06 18:12 ` lucio
2014-12-06 18:53 ` erik quanstrom
2014-12-06 5:06 ` lucio
2014-12-06 9:09 ` lucio
2014-12-06 9:27 ` Bakul Shah
2014-12-06 10:28 ` Quintile
2014-12-06 13:40 ` lucio
2014-12-06 16:29 ` erik quanstrom
2014-12-06 16:42 ` Kurt H Maier
2014-12-06 17:47 ` lucio [this message]
2014-12-06 13:43 ` lucio
2014-12-06 14:06 ` lucio
2014-12-06 14:30 ` lucio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f652f4bfe78d198f5e2c85660f30d30@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).