I bought myself a Kensington Slimblade mouse the other day,
it is a trackball mouse with 4 buttons and scrolling features.
It mostly works out of the box, but openbsd seems to only detect
two of the buttons, leaving me without a middle click. I'd like to find
a way to program the two other butto
On 05/14, Ulf Brosziewski wrote:
> Would you mind to run
> $ xinput --test /dev/wsmouse
> in an X terminal, press each button once, grab the output,
> and post it here?
Output:
motion a[0]=1364 a[1]=907
button press 4
button release 4
motion a[0]=1365
motion a[0]=1367
motion a[0]=13
On 05/14, Ulf Brosziewski wrote:
> Hi Patrick,
>
> thanks for the infos. I'm afraid you're out of luck, it seems
> that this device would need vendor-/model-specific extensions
> in our HID-mouse driver. It only announces two "regular" buttons,
> so our driver won't look for more (what xinput sh
I've been using a 3rd gen x1 carbon for half a year now and havent had any
problems
OpenBSD 6.3-current (GENERIC.MP) #33: Mon May 7 18:59:05 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8261529600 (7878MB)
avail mem = 8003121152 (7632MB)
mpath0 at
You can get a pretty good refurbished 3th gen thinkpad x1 carbon under 900$.
I've baught two on ebay over the last year,
Hello,
On 08/19, Oliver Marugg wrote:
> I am preparing switching my desktop from another OS to OpenBSD. Is anyone
> using an Evoluent USB Wired Mouse (C/4 or 4 small) with OpenBSD? Or any
> other great ideas about an ergonomic mouse working with OpenBSD?
Most mouses should work, though I remember
Hi,
I'll be playing around with DragonflyBSD Hammer2 (and multiple offsite
backups) for a home NAS over the next few weeks. I'll probably do a
presentation about the experience at the Montreal BSD user group
afterwards. It does not require as many ressources as ZFS or BTRFS, but
offers many
Hey,
Since I'm getting off-list questions from more than one person,
I'll post here as well.
On 11/15, Patrick Marchand wrote:
> I'll be playing around with DragonflyBSD Hammer2 (and multiple offsite
> backups) for a home NAS over the next few weeks. I'll probably do
Hello,
On 11/15, Predrag Punosevac wrote:
> Patrick Marchand wrote:
> > I'll be playing around with DragonflyBSD Hammer2 (and multiple offsite
> > backups) for a home NAS over the next few weeks. I'll probably do a
> > presentation about the experience
Hi,
On 11/17, Predrag Punosevac wrote:
> Patrick Marchand wrote:
> > On 11/15, Predrag Punosevac wrote:
> > > Patrick Marchand wrote:
> > > > I'll be playing around with DragonflyBSD Hammer2 (and multiple offsite
> > > > backups) for a home
On Sat, Mar 10, 2018 at 07:22:43PM +, Otto Moerbeek wrote:
> On Sat, Mar 10, 2018 at 02:15:02PM -0500, math...@posteo.net wrote:
>
> > > You would not be the first
> > > one to have written to a file in /dev instead of a device.
> >
> > Thats exactly what happened, my /dev/sd1 is 943056 bytes
Sent this to ports, but maybe it's better for misc? Tell me if I'm
wrong.
- Forwarded message from math...@posteo.net -
> From: math...@posteo.net
> To: po...@openbsd.org
> Date: Sun, 11 Mar 2018 17:05:03 -0400
> Subject: Trying to build rust 1.24 on -current
>=20
> So I updated to -curre
> Temporary hack to get it building until semarie can generate new bootstraps:
>
> post-extract:
> cp /usr/lib/libpthread.so.25.1 \
> ${WRKDIR}/rustc-bootstrap-${MACHINE_ARCH}-1.24.0-20180213/lib/
Yep, that worked, thanks.
Like it says on the tin, I tried building golang so I could get fzf but
I get the following compilation errors. I got help to build rustlang
last time, so maybe golang is just a small fix away? I didnt see any
mention of golang in the ports mailing list in the last few days.
I'm guessing the respo
> Apparently something to do with Go according to a message I received
> off-list after writing to the maintainer of syncthing(1) earlier today:
In that case I'll wait for a diff on the golang port to appear in the
mailing list.
Hello,
I updated to the latest snapshot yesterday and when I run
pkg_add -Dsnap -u a bunch of pkg will not upgrade because it cant find
ssl.44.9
It does find 44.8 and 45 but not that specific version, last week I had
a similar issue with libm. Now I can get around the error by building
the packag
> It seems you have to update your snapshot because it's too old. It was
> shipped with the lib version 44.8 and the current is now 44.9 from the
> output. That mean your snapshot is too old and the packages have been built
> against a more recent snapshot.
>
> Regards
Hhmm I guess it's possible t
> You updated from a base snapshot that had libssl.so.44.8 to one that
> has 45.0, but skipped the intervening 44.9 one. Unfortunately, the
> package snapshot had been built against 44.9.
>
> > a similar issue with libm. Now I can get around the error by building
> > the packages in ports, but I
> > Wait a few hours until the next packages, built against 45.0, hit
> > the mirrors.
Yep retrying today all the packages installed correctly!
So I'm trying to build pijul (rust vcs based on patch theory) but it
requires rust-openssl, which only supports the latest release of
libressl (2.6). Is there a quick fix to build software that requires an
older libressl than what is currently used in snapshots? Or should I try
to patch the rust-op
> There is a patch on rust-openssl to force the build using the latest
> suppported version (see
> lang/rust/patches/patch-src_vendor_openssl-sys_build_rs).
Applying the patch worked
> Running testsuite is usually a good method to check breakage.
And the test suite passed
> For me, rust FFI is a
Output of compiling plan9port on amd64 with the april 5 snaphot
===> plan9port-20180117 depends on: bzip2-* -> bzip2-1.0.6p8
===> Verifying specs: X11 Xext c m pthread util fontconfig freetype z
===> found X11.16.1 Xext.13.0 c.92.3 m.10.1 pthread.25.1 util.13.0
fontconfig.11.0 freetype.28.2 z.5
On 04/05, Philip Guenther wrote:
> On Thu, Apr 5, 2018 at 9:50 PM, Philip Guenther wrote:
>
> > On Thu, Apr 5, 2018 at 7:53 PM, Patrick Marchand > > wrote:
> >
> >> Output of compiling plan9port on amd64 with the april 5 snaphot
> >>
> > ..
Compilation succeeds on the april 8 snapshot
On 04/08, Patrick Marchand wrote:
> Compilation succeeds on the april 8 snapshot
Though now I'm getting Abort Trap whenever I try to run the plumber or
acme. I was able to compile some programs with mk though, as I compiled
both $PLAN9/src/cmd/upas and $PLAN9/src/cmd/upas/nfs. I'
On 04/08, Theo de Raadt wrote:
> At the moment snapshots contain the MAP_STACK diff. Your program is
> setting up threads incorrectly (it has it's own thread library?),
> resulting in stacks not being mapped with MAP_STACK. Stacks must be
> carefully setup now. ktrace -di may expose the memory a
On 04/08, Gleydson Soares wrote:
> Hi Patrick,
> could you please test this diff?
> https://marc.info/?l=openbsd-ports&m=152160090624047&w=2
The diff worked, I was able to run plumber, factotum and acme without
any aborts.
Thanks!
github.com/mawww/kakoune/blob/master/src/file.cc
https://github.com/mawww/kakoune/tree/master/src
Thanks,
Patrick Marchand
> On 04/16, Stuart Henderson wrote:
> > On 2018-04-16, Patrick Marchand wrote:
> > So trying again I looked closer at what the function was doing and how
> > it was implemented for freebsd and dragonflybsd. The function
> > tries to find the executable path of kak, b
29 matches
Mail list logo
