How does #FreeBSD handle this?

browsers are 2-3% faster than in #xenocara

trackpad and trackpoint are not working as expected

whole setup a bit more complicated (starting from tty0, installing extra packages, extra line in fbtab, etc)

for this week at least i'm switching back to good old #x11 and #cwm :)

cc: @haddock@bsd.network

also curious if recent changes help in any way...

other windows (incl. #firefox) are respecting settings from /etc/X11/xenodm/Xresources

Xcursor.size: 96
Xcursor.theme: dmz

4.32 vimb
7.36 qutebrowser
7.96 firefox
9.76 iridium
9.78 ungoogled-chromium

notes: when i re-run the tests scores are changing (just slightly); at some point openbsd frozen during vimb test (just once, couldn't reproduce, worked well after reboot)

o_O

if yes, how?
if not, why not?

feels like it's a bit too much...

on a positive note i only need to configure it once for a new laptop and then i can reinstall everything on exactly the same or similar thinkpad in just a few minutes :)

one day i'm going to try x13s (iirc it's fanless)

everything what i need is tested and working.
(haven't tested: fingerprint sensor)
(work in progress: microphone)

\o/

#thinkpad t14 gen3 i5 1245u running #openbsd 7.8 -stable

• facename spleen-6
• scaled up to 18px
• no antialiasing

• minimal cpu freq (400 mhz)
• minimal backlight (level 1)
• wifi on, but inactive
• bluetooth off
• xenodm on, but inactive (no windows open)
• only default services running
• single shell script running (calling apm every minute and writing a few lines into to a file)
• nothing else connected (no exteral displays, no usb, no ethernet)

• audio(ok)
• battery(ok)
• display port(ok)
• ethernet(ok)
• ssd(ok)
• trackpad(ok)
• trackpoint(ok)
• usb(ok)
• video(ok)
• wireless(ok) --- after fw_update
• hibernation(ok)
• suspend/resume(ok)
• bluetooth(no)

• fingerprint(not tested)
• microphone(not tested)
• webcam(not tested)

everything is okay, but even while idle the fan is at ~2000 rpm and temperature is about +40ºC...

after silent macbook air m1 it's just too noisy :)

why some of the files listed twice? o_O
#openbsd

The Book of PF, 4th Edition: It's Here, It's Real https://nxdomain.no/~peter/its_real_its_here.html #openbsd #freebsd #pf #packetfilter #networking #firewall #networktrickery #security #freesoftware #libresoftware @nostarch

i'm looking for some boards that already supported by openbsd

Goodbye pledge "tmppath", hello unveil("/tmp", "rwc")! ​

Some observant #OpenBSD users may have noticed developers removing the pledge(2) "tmppath" promise from all base utilities that were using it along with a handful of ports, because this promise, well.. it kinda sucks, and it predates a much better solution: unveil(2).

More info & some backstory in Theo de Raadt's commit.

deraadt@ modified src/{sys,lib}/*: pledge "tmppath" goes away because it sucks. The history is kind of
sad: unveil(2) was invented by Bob Beck and myself because a couple of us struggled and couldn't expand the "tmppath" mechanism to general use.
unveil(2) ended up being kind of "upside down" different, and so we never deleted "tmppath" because the refactorings seemed complicated.
However over the last two weeks, we're removed all the "tmppath" in base pretty easily, and the 18 ports using it have also been fixed.
The majority of situations now use unveil "/tmp" "rwc", unveil "/" "r" or similar, and then pledge "rpath wpath cpath", and this is generally needed to satisfy the mkstemp(3) family of functions in libc.
Use of "tmppath" will now cause pledge(2) to return EINVAL. There is no backwards compatible way of mimic the behaviour correctly using kernel-internal unveil hackery.
Prompted by a report from David Leadbeater; and extensive conversations with beck and semarie.

if it's not working on #openbsd, then will switch back to good old x1 gen 5 :)

let me know if you can recommend anything else.

see also
x1 carbon gen 11 by reyk
x1 carbon gen 9 by xosc
x1 nano gen 1 by jcs

Heads up for #OpenBSD 7.8 users, backports for chromium, iridium, ungoogled-chromium ports have been committed, updated -stable packages should be showing up in the next few days!

chromium has historically only received updates in -current, but it appears sthen@ has managed to backport them!

https://marc.info/?l=openbsd-ports-cvs&m=177195097807729&w=2