On 11/10/18 19:29, Chris Bennett wrote:
On Sat, Nov 10, 2018 at 11:36:17PM +0100, Solene wrote:
This is normal. Look at 26th October https://www.openbsd.org/faq/current.html
The suid was removed to prevent bad things to happen. Use xenodm instead of
startx.
I have switched to using xenodm. I am also think I screwed up something
during installation. It happens. Shrug.
I have found that I am stuck using fvwm, but I would like to use another
wm. Not very important which one. But I really have no idea how to
accomplish that.
The reason I think I screwed up something else is that the performance
across the board is terribly slow. Happy to reinstall from scratch.
I'm happy to find the answers reading man pages, but man fvwm wasn't
helpful for me. Which ones should I read?
Running 6.4 stable amd64
Thank you,
Chris Bennett
Chris,
After 20+ years of typing startx, I switched to xenodm about three days
ago. The FAQ, "Following -current" and the xenodm manpage are very
helpful. Thanks to all the authors !!!
Personally I use spectrwm, so I can't speak for other the wm's. In my
case, all I had to do was:
$> cp .xinitrc .xsession
$> chmod +x .xsession
... and it "just worked" as expected :-)
N.B. If you have a custom .Xresources file, like I do for xterm, then
make sure a line like the following is in your ~/.xsession.
[[ -f ~/.Xresources ]] && xrdb -load ~/.Xresources
or simply
xrdb -load ~/.Xresources
Regarding fvwm ...
Read the last 20 lines or so of /etc/X11/xenodm/Xsession and you will
understand why you are "stuck using fvwm." It helped me a lot. The
xenodm manpage is solid gold. It's very well written.
You should be able to configure your X deskop the way you want it
between those docs.
