Hello Allan, it looks that, besides using openbsd as server in the cloud, it was quite a while I wasn't running X on a client, actually it was xenodm the thing, now I know. I had formerly tried to start it manually as normal user (as well as startx), but, reading updated faq, I discovered it's run as a service from root. Now everything works back. Unless for the fact which I discovered that, with 256M RAM, no serious www browser runs anymore (at 6.2 still something worked besides netsurf and dillo, a sign of the times!).
Btw, does "rcctl enable xenodm" also allow running programs remotely with ssh -X|Y u...@obsd.box, or is there something more to do? Thanks again and have a nice day! Pasha On Sat, Apr 18, 2020 at 4:54 AM Allan Streib <astr...@indiana.edu> wrote: > Paolo Aglialoro <paol...@gmail.com> writes: > > > considering that 6.6 nuked X for my T23 as mentioned in previous recent > > post, I decided to refresh my old Dell L400, which was lagging behind at > > 6.2, with a fresh 6.6 install. > > > > Unfortunately X crashes. The first error in the log file was about > setting > > machdep.allowaperture=1 and rebooting (I always used 2 before). After > > changing its value in sysctl.conf to 1, this is the new error in the log > > file: > > Are you using xenodm instead of startx? Beginning in 6.5, "Xorg(1), the > X window server, is no longer installed setuid. xenodm(1) should be used > to start X." > > https://www.openbsd.org/65.html >
