If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Comment

It mostly comes down to /dev/input/* handling. On single user, one could chown and chmod your way out. You need to do this for the VT as well but that is not a problem. Furthermore, it would require some UDEV handling for plugging in/out devices causing nodes in /dev/input to disappear or reappear.

I might make this a project for my parents laptop and PC. Looks doable, interesting and beneficial.

I might consider creating a privileged user for X and let the default user piggyback on it (setgid might do this) as reported in the wiki. The only thing that would result from an exploit in X would allow one to snoop keyboard/mouse data. But that also the case right now.

Comment

Having tried to use OpenBSD as a desktop lately, I've come to the point where I don't see any good reasons to use it for that purpose.
If anyone think differently, please do explain.

* Getting any modern X environment up and running is a huge chore compared to other free unix-like systems.
* Basically zero X applications are packaged for the OS.
* It is SLOW, especially X and SMP performance is terrible.
* Its hardware support is lacking.

I still have it installed, so any great ideas of how to make it a decent desktop OS is appreciated, but I'm not holding my breath...

Comment

Having tried to use OpenBSD as a desktop lately, I've come to the point where I don't see any good reasons to use it for that purpose.
If anyone think differently, please do explain.

* Getting any modern X environment up and running is a huge chore compared to other free unix-like systems.
* Basically zero X applications are packaged for the OS.
* It is SLOW, especially X and SMP performance is terrible.
* Its hardware support is lacking.

I still have it installed, so any great ideas of how to make it a decent desktop OS is appreciated, but I'm not holding my breath...

I'm running OpenBSD as my default desktop OS at home for some time now and I find it a breeze of fresh are compared to the linux world in terms of consistency and ease of use.

* Getting X up and running is just a matter of saying you want to run X in the installer and enabling xdm (or install another dm later on).
* The default applications are just the onces bundled with the OS and make sure they are licensed in accordance with the OpenBSD standard, the codebase is up to the OpenBSD standards (these guys are major clean code advocates). To install extra software you need to set your PKG_PATH environment variable to <mirror.tld>/pub/OpenBSD/`uname -r`/packages/`uname -m` where <mirror.tld> is one of http://www.openbsd.org/ftp.html and where uname -r can be replaced with snapshots if you're following -current (development branch). To search packages do pkg_info -Q <keyword> and to install do pkg_add <package-name>.
* It is true that it is slower then most linux systems. This is because they still (mostly) work via the biglock system and because they don't do quick hacks just to speed up things.
* Everything I use is supported. But I do agree that some peripherals aren't fully supported. To name the major ones: 802.11n, bluetooth and xHCI.

If you are truely willing to give OpenBSD a shot I recommend you use it for a couple of weeks and enjoy their great documentation (either via man-pages or http://www.openbsd.org/faq/). An inconsitency or something missing in the documentation is considered a bug. Also joining the mailing lists can help you a great deal (http://www.openbsd.org/mail.html).