From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: jungle Boogie <jungleboogie0@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Openbsd update recommendation
Date: Sat, 2 Jun 2018 05:15:49 +0200 [thread overview]
Message-ID: <CAHmME9p7ZkaJO7FYTbyp39tQAKtfZhkD_5Lo5TfQpiOkM1a3kA@mail.gmail.com> (raw)
In-Reply-To: <CAKE2PDtV_5bkjPgtPBgtq4BgY2QaFB4eVD7r9MjqiLZNkAMjzQ@mail.gmail.com>
Hey Jungle,
On Sat, Jun 2, 2018 at 1:26 AM, jungle Boogie <jungleboogie0@gmail.com> wrote:
> Hi All,
>
> For openBSD instructions here:
> https://www.wireguard.com/install/#packages
>
> Curl is not apart of base, so you can either assume the users have
> curl installed, or use ftp(1) in the example. If you're doing the
> latter, you'll need a pkg_add to also include curl.
>
> https://man.openbsd.org/ftp.1
I love how OpenBSD commands keep evolving over time. Thanks for the
suggestion. I've updated the page.
> Also, I already have a go path setup. How do I get around this?
>
> cd .gopath/src/git.zx2c4.com/wireguard-go && dep ensure -vendor-only -v
> /usr/src/wireguard/wireguard-go-0.0.20180531 is not within a known GOPATH/src
> gmake: *** [Makefile:33: vendor/.created] Error 1
> gmake: Leaving directory '/usr/src/wireguard/wireguard-go-0.0.20180531'
Somebody mentioned this on IRC the other day (maybe you?), but I
didn't figure out what was going on then. I just now triaged the
issue: in ksh(1), before exec'ing a new process, it resolves all
symlinks of pwd. Try for yourself:
# ksh
# mkdir a
# ln -s a b
# cd b
# ksh -c pwd
/root/a
That's pretty weird behavior, but maybe there's an interesting reason
for it; I'll poke around tomorrow and see if I can figure it out.
In any case, I've worked around it now in the install script and
tested on a fresh OpenBSD 6.3 install, so you should now be able to
run:
# ftp -o - https://xn--4db.cc/IKuBc62Z | sh
Let me know how it goes, and thanks for the report.
Regards,
Jason
next prev parent reply other threads:[~2018-06-02 3:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 23:26 jungle Boogie
2018-06-02 3:15 ` Jason A. Donenfeld [this message]
2018-06-02 7:08 ` Jungle Boogie
2018-06-02 14:39 ` Jason A. Donenfeld
2018-06-02 20:07 ` Jungle Boogie
2018-06-02 11:56 ` Matthias Urlichs
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=CAHmME9p7ZkaJO7FYTbyp39tQAKtfZhkD_5Lo5TfQpiOkM1a3kA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=jungleboogie0@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/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).