i've tried x11-wm/enlightenment, it's impressive, regret not trying before!

it has even GUI setup process in first start

I am following the handbook docs.freebsd.org/en/books/handbook/x11 but when I run 'xrandr' I get "Can't Open Display"?

pike: is Xorg started?

no, Handbook doesn't mention that it should be running :)

ok, it does mention it "after the X server has been started" But Handbook seems to skip many parts here

Like how to setup a monitor

pike: you don't need to nowadays?

I'm starting to wonder if FreeBSD doesn't like this Lenovo Thinkpad X260

looks like I need to use SCFB driver

pike: did you load the DRM drivers? Xorg can't start without it or use framebuffer device

also check that if your DRM packages match with your OSVERSION

it would suck if there's no accelerated X driver for Intel HD 520

pike: i think there is

pike: i915

ok, then this page is wrong :) wiki.freebsd.org/Laptops/Thinkpad_X260

pike: didn't know this page. Laptops/Thinkpad_X260 (last edited 2021-12-17T19:44:22+0000 by ViniciusZavam)

pike: maybe something changed after that date?

hopefully something improved since 2021

yeah

pike: maybe install drm-kmod together with x11-drivers/xf86-video-intel

looks like this is gonna be an adventure :)

pike: yeah, hopefully with a happy end

ivy: I would not

actually, hold up

ivy: apparently I capsicumized bhyveload(8) last year, so I guess it's not all that bad

it effectively exposes a dirfd for -h path, but naturally that has restricted rights(4)

SECURITY CONSIDERATIONS in the manpage documents the remaining concerns

kevans: thanks

sounds like it's fine with a warning to the user...

Hey, upgraded to 14.3 via 13.3 and 13.5 (with freebsd-install). trying to run bash i get "ld-elf.so.1: Shared object "libncurses.so.8" not found, required by "libreadline.so.8""

I might've tried to run it before doing a proper pkg upgrade -f , can there be some linker cache thing being wrong or outdated ? (I noticed that /lib/libncursesw.so.9 exists now)

Some upgraded library version ?

rebuild bash

or update the package

jonaslund, After any major number upgrade, and some minor numbers (I always do it), always run "pkg upgrade -f" to upgrade ALL of the binary packages. That should install an updated bash but most importantly install the dependent libraries needed too.

Make sure you have not "locked" the package (pkg lock bash) that would prevent bash package from updating, but not the shared libraries it uses. This situation can cause an older program to need older shared libraries which were removed during an upgrade. The solution there is to unlock any locked package and then upgrade -f it.