Hello,
i have a simple question, i worked on some packages to getting access to my
smartphone(Xiaomi Mi4 with Android 6) via MTP.
But all attempts ended up that i cannot see any device. So is this a problem
with NetBSD ReFUSE or a problem with the port?
The library libmtp(in Pkgsrc) comes with
Updating src tree:
P src/bin/dd/dd.c
P src/bin/echo/echo.c
P src/bin/expr/expr.y
P src/bin/ls/main.c
P src/bin/ps/ps.c
P src/bin/sync/sync.c
P src/bin/test/test.c
P src/distrib/sets/lists/base/shl.mi
P src/distrib/sets/lists/comp/mi
P src/distrib/sets/lists/comp/shl.mi
P src/distrib/sets/lists/deb
Hi,
On 2016/09/05 1:00, Frank Kardel wrote:
> running the -current (7.99.36) with 7.99.16 userland reliably traps at:
>
> src/sys/netinet/ip_mroute.c:1751
>
> on an multi-homed i386 system running mrouted.
>
> A 7.99.16 kernel survives that fine. Do we have a userland dependency or
> is this a
Good evening,
On Wed, 10 Aug 2016, Hubert Feyrer wrote:
I've added a bit more information below[2], but to cut a long story short -
what excact build.sh options does one use these days to cross-build
-current/amd64 from OS X? Did I miss any documentation[3]
It seems this was resolved somewhe
Hi !
running the -current (7.99.36) with 7.99.16 userland reliably traps at:
src/sys/netinet/ip_mroute.c:1751
on an multi-homed i386 system running mrouted.
A 7.99.16 kernel survives that fine. Do we have a userland dependency or
is this a new regression from the network stack multiprocessing
