A hyper mouse or normal mouse but you cannot click
*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'll try FreeBSD again. Only problem with FreeBSD after trying to follow documentation and configuring I couldn't even get a proper XWindows session to work. Installing on actual hardware is not an option. Right now I am just experimenting to see where it goes, which is why I am running a VM instead.
Consider giving OpenBSD a try. Xorg works OOTB, and then you can add whatever WM or DE you prefer, or just configure what's in base (fvwm or cwm) to your liking. Here's a couple of good guides:
Consider giving OpenBSD a try. Xorg works OOTB, and then you can add whatever WM or DE you prefer, or just configure what's in base (fvwm or cwm) to your liking. Here's a couple of good guides:
I actually did try OpenBSD in a VM, and yes I did get into X after install. If I were to switch from Linux to BSD, or have an extra machine to play with, it would still have to be FreeBSD or a derivative there of, at least for me the main reason for this is the lack of a journaled FS in OpenBSD. ZFS looks very attractive, and I am glad BSD (at least FreeBSD), finally decided to add a proper modern journaling FS, as I would probably not put any stock into UFS+ or UFS2 . The features ZFS has to offer looks great, particularly data storage; unless XFS support ever were to be added. Ironic that ext4 read/write is supported in FreeBSD, and something like SGI's XFS port to Linux isn't; but those are just details.
If I were to switch from Linux to BSD, or have an extra machine to play with, it would still have to be FreeBSD or a derivative there of, at least for me the main reason for this is the lack of a journaled FS in OpenBSD.
Search the web for OpenBSD FFS with "soft updates".
Quote:
Originally Posted by Jeebizz
ZFS looks very attractive, and I am glad BSD (at least FreeBSD), finally decided to add a proper modern journaling FS.
ZFS is a lot more than just a journalising FS.
As a file server, FreeBSD+ZFS is a good option, but when I see someone struggling to get a mouse working on GhostBSD (a desktop oriented OS) and then not able to start X on FreeBSD, I'd have to assume that they're not interested in running a file server?
No I am not interested in running a fileserver, but I have an external HD (formatted XFS). I'd keep it that way if BSD supported SGI's XFS, but obviously it does not. Sure BSD supports ext4 but I am just not impressed by ext4. Soft updates or ZFS , sorry I'll go with ZFS.
Sure BSD supports ext4 but I am just not impressed by ext4.
As far as I'm aware there is no rw ext4 support in any *BSD. In OpenBSD there is ro support as I recall.
OpenBSD (and FreeBSD?) support ext2/ext3, but without ext3's journaling. So ext3 is treated as ext2. So you would probably not want to mount ext3 as rw either.
(XFS is supported ro by FreeBSD, either that or rw support might be experimental - can't recall which.)
Experimental does not sound promising, and even if I were on ext3, then my best bet would still be FreeBSD / derivative and not OpenBSD. I rather do not understand why support for XFS in FreeBSD would be experimental since the source for that has been out at least over a decade now, so implementation should have resolved any major issues (one would think). OpenBSD just does not seem viable as a third option (as my second alternative choice would be Devuan Linux).
Also I honestly do not care about binary blobs. If I have to run the NVIDIA driver to get my graphics to work correctly, thats another tick for FreeBSD over OpenBSD. I am not so ideologically driven to narrow down my hardware choices over the idea of just absolute no closed hardware. If my NVIDIA card works in FreeBSD just fine with the NVVIDIA driver, thats good enough for me. So, FreeBSD / derivative is my final answer on that issue.
Experimental does not sound promising, and even if I were on ext3, then my best bet would still be FreeBSD / derivative and not OpenBSD. I rather do not understand why support for XFS in FreeBSD would be experimental since the source for that has been out at least over a decade now, so implementation should have resolved any major issues (one would think). OpenBSD just does not seem viable as a third option (as my second alternative choice would be Devuan Linux).
For XFS, someone has to do the work and want to do the work and maintain it. Until that happens, you won't have proper XFS support. Plus there is ZFS, so perhaps no real incentives?
Quote:
Originally Posted by Jeebizz
Also I honestly do not care about binary blobs. If I have to run the NVIDIA driver to get my graphics to work correctly, thats another tick for FreeBSD over OpenBSD. I am not so ideologically driven to narrow down my hardware choices over the idea of just absolute no closed hardware. If my NVIDIA card works in FreeBSD just fine with the NVVIDIA driver, thats good enough for me. So, FreeBSD / derivative is my final answer on that issue.
Nvida UNIX driver is for Linux/Solaris/FreeBSD as that's what the vendor chose to support.
For XFS, someone has to do the work and want to do the work and maintain it. Until that happens, you won't have proper XFS support. Plus there is ZFS, so perhaps no real incentives?
So then, FreeBSD it is?
Quote:
Originally Posted by cynwulf
Nvida UNIX driver is for Linux/Solaris/FreeBSD as that's what the vendor chose to support.
Again, looks like I will be choosing FreeBSD over OpenBSD then.
Or there is always derivatives - maybe I'll give TrueOS a spin this time.
YMMV, but I find TrueOS to be kinda buggy. And Lumina (although you can certainly change it) has got to be one of the most awful, eye-cancerous desktop environments, EVER.
YMMV, but I find TrueOS to be kinda buggy. And Lumina (although you can certainly change it) has got to be one of the most awful, eye-cancerous desktop environments, EVER.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.