Different ws(4) xinput properties for different wscons(4) mouses

id=6 [slave keyboard (3)] In order for scrolling to work on the trackpoint, i need to emulate scroll buttons while the middle button is pressed and the thinkpad's red nub is moved. $ cat ~/.xsession | fgrep xinput xinput set-prop "/dev/wsmouse" "WS Pointer Whe

Re: ws

e history for this? > > On 14/04/2019, Bryan Steele wrote: >> 'workstation console' at least sounds plausible. >> https://www.netbsd.org/docs/guide/en/chap-cons.html > > ws for workstation is correct. However, wobj is the odd one out in > that list, and it stands for write to /usr/obj: > https://www.openbsd.org/faq/faq5.html#Miscellanea >

Re: ws

> etc >> >> It seems to be a quite old practice and common with other BSDs. >> Anybody has the history for this? On 14/04/2019, Bryan Steele wrote: > 'workstation console' at least sounds plausible. > https://www.netbsd.org/docs/guide/en/chap-cons.html ws f

Re: ws

On Sun, Apr 14, 2019 at 11:31:33AM +0900, Jerome Pinot wrote: > Hi, > > I'm curious to know what is the origin of the "w(s)" prefix we have > on some OpenBSD specific places, like: > - wscons > -wsmoused > - wskbd > - wsrc > - wobj > etc > > It seems to be a quite old practice and common with oth

ws

Hi, I'm curious to know what is the origin of the "w(s)" prefix we have on some OpenBSD specific places, like: - wscons -wsmoused - wskbd - wsrc - wobj etc It seems to be a quite old practice and common with other BSDs. Anybody has the history for this? Thanks! -- Jerome Pinot

Problems with ASUS P9D WS (socket 1150, Haswell Xeon E3-1230V3)

Hi, I have problems booting OpenBSD from SATA hard drives with the ASUS P9D WS mainboard. I've successfully verified that OpenBSD can boot with this mainboard since booting OpenBSD works without problems via USB (see dmesg). However, OpenBSD doesn't boot from SATA hard drives at

Re: Shutting down OpenBSD VM when closing VMWare WS or ESX

* Alexander Farber [090411 16:42]: > Hello, > > I use several OpenBSD/i386 (versions 4.3 and 4.4) > VMs under VMWare Workstation and ESX. > They work great for my purposes (few LAMP servers + > 1 OpenVPN server), but there is one annoyance: > > when I close the VMWare or shutdown the host, > the

Shutting down OpenBSD VM when closing VMWare WS or ESX

Hello, I use several OpenBSD/i386 (versions 4.3 and 4.4) VMs under VMWare Workstation and ESX. They work great for my purposes (few LAMP servers + 1 OpenVPN server), but there is one annoyance: when I close the VMWare or shutdown the host, then the OpenBSD VMs aren't shutdown properly. I've trie