ave pointer type.
https://github.com/WireGuard/wgctrl-go/pull/54
Seems to work fine, and no more Cgo!
On Friday, May 17, 2019 at 1:22:36 PM UTC-4, Jan Mercl wrote:
>
>
>
> On Fri, May 17, 2019, 19:09 Matt Layher >
> wrote:
>
>> Thanks for the insight, this is very us
Thanks for the insight, this is very useful information. Perhaps I'll look
into the mmap route.
- Matt
On Friday, May 17, 2019 at 12:54:28 PM UTC-4, Ian Lance Taylor wrote:
>
> On Fri, May 17, 2019 at 7:44 AM Matt Layher > wrote:
> >
> >> Pointers passed to un
at if if the driver retains this pointers... In reading
Ian's email, the top-level pointer will be retained and not collected,
and it has references to the contained pointers.
-Original Message-
From: Robert Engels
Sent: May 17, 2019 10:45 AM
To: Matt Layher , g
time,
Matt
On Friday, May 17, 2019 at 10:32:44 AM UTC-4, Ian Lance Taylor wrote:
>
> On Thu, May 16, 2019 at 5:24 AM Matt Layher > wrote:
> >
> > I'm working on a project that involves an ioctl API on OpenBSD. The idea
> is that you store a memory address in a un
Hey folks,
I'm working on a project that involves an ioctl API on OpenBSD. The idea is
that you store a memory address in a union within another structure, and
then invoke the ioctl. When it returns, both the structure itself and the
memory pointed at by the address in the union are filled with
oking File.
So my question still stands, as far as I know.
On Monday, March 25, 2019 at 2:36:29 PM UTC-4, Robert Engels wrote:
>
> File is cross-platform. I am pretty sure no syscall. is guaranteed to
> be available on any given platform.
>
> -Original Message-
> Fr
t time to add a deprecation notice to the File method on
various package net types, in favor of SyscallConn?
Perhaps there's some benefit to File that I'm not seeing. If so, I'd be
curious to find out!
Thanks,
Matt Layher (@mdlayher)
--
You received this message because you
Hi all, I'm here to share a project I've been working on:
https://github.com/mdlayher/wireguardctrl
I'm not quite finished with this package yet (see issues), but now that
I've got both the kernel and userspace APIs working, I figured it was time
to share it to a more broad audience.
For those
Hey Francesc,
Will there be any lightning talk slots available for the devroom? I've
submitted a full length talk proposal elsewhere but would be happy to
submit a lightning talk proposal for the Go devroom, if that's an option.
Thanks for your time!
On Monday, October 9, 2017 at 4:24:31 PM U
Approach number one is the correct way, IMO.
That's what I've always
done: https://godoc.org/github.com/mdlayher/netlink#Conn.Execute.
- Matt
On Tuesday, June 6, 2017 at 3:56:43 PM UTC-4, M2 wrote:
>
> I need to expose 2 ways of doing the same thing.
>
> - The first way is very simple, always d
for CN_IDX_PROC I guess
that may be a special case given what it is.
Be interested to know if your module avoids this issue somehow?
On 22/02/2017 21:17, Matt Layher wrote:
> 1. "Only processes with an effective UID of 0 or the CAP_NET_ADMIN capability
may send or listen to a netlink m
ues.
>
> On Wednesday, February 22, 2017 at 1:13:26 PM UTC-5, Steven Hartland
> wrote:
>>
>> One thing you don't mention, which we found particularly frustrating with
>> netlink, is that using it can often need cap_net_admin :(
>>
>> On 22/02/2017
we found particularly frustrating with
> netlink, is that using it can often need cap_net_admin :(
>
> On 22/02/2017 17:38, Matt Layher wrote:
>
> Hey all,
>
> I recently spent some time working with Linux's netlink IPC mechanism in
> Go. Because I had a hard time findin
your time!
- Matt Layher
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
14 matches
Mail list logo
