Re: Error in adding system call in OpenBSD 6.3

On Sun, Apr 22, 2018 at 3:14 AM, Paul Irofti wrote: > On Sun, Apr 22, 2018 at 12:23:09AM +0530, Neeraj Pal wrote: >> Hello guys, >> >> I am facing some issue during adding system call on OpenBSD 6.3. I >> have shown my pathways to add system call, please guys correct me if >>

report fb_queue error in fuse_lookup to simplify debugging [tiny patch]

There are some people on @misc faced with "libfuse vnode reclaim failed" error. http://openbsd-archive.7691.n7.nabble.com/sshfuse-fusefs-libfuse-vnode-reclaim-failed-td341072.html I suggest to report errno explicitly so, people will be able to use intro(2) to find description of error diff

Despite the man, wsmouse(4) can't be shared between X(1) and wsmoused(8) (workaround included)

man wsmoused: "wsmoused will happily coexist with the X Window System, provided that the mouse device is supported by wsmouse(4). " I have wsmouse0 on pms0 (PS/2 controller emulation running on VirtualBox) When moused works on /dev/wsmouse, X reports that device /dev/wsmouse is busy and mouse

Re: Error in adding system call in OpenBSD 6.3

On Sun, Apr 22, 2018 at 12:23:09AM +0530, Neeraj Pal wrote: > Hello guys, > > I am facing some issue during adding system call on OpenBSD 6.3. I > have shown my pathways to add system call, please guys correct me if > somewhere I have forgotten something to add or build. > > 1) echo "331 { int

Error in adding system call in OpenBSD 6.3

Hello guys, I am facing some issue during adding system call on OpenBSD 6.3. I have shown my pathways to add system call, please guys correct me if somewhere I have forgotten something to add or build. 1) echo "331 { int sys_hello(void); }" >> /usr/src/sys/kern/syscalls.master 2) make