I agree with others that you are expected to read documentation and use it on supported hardware. I have been using it on my laptop for some time now, though I don't need bluetooth nor do I suspend/resume much, and I don't know about battery life. I guess I use it mostly like a desktop.
About the security, which is my main reason for using it: I like having to install the things I really want, which gives me a chance to consider the security implications of them, instead of having many things pre-installed and I don't know what the total risks are. And nothing else I know of has gone since ~1996 with only 2 of the worst kind of security holes (i.e., remote exploit of something I didn't even need, but was installed by default).
In the base install are many useful things (including a web server IIRC, though the port is not exposed by default), and those are audited and have that excellent track record.
Then when you install extra things, they are usually limited by what user they run as, and usually have pledge/unveil run (limiting access to predetermined/approved syscalls and parts of the file system) so they can't break other things if compromised.
I do change my default umask (/etc/profile, sourced by shell startup files for all users) to 0077, which means putting the pkg_add command inside a script ("pa") that first sets it back to 0022 temporarily.
Also, for finding packages to install, doing pkg_add pkglocate, then using pkglocate -i, or pkg_add portslist then just searching the whole list with things like less /usr/local/share/ports-INDEX or less /usr/local/share/sqlports-list can be useful. There are very many packages available (over 12k on the amd64 platform).
About the security, which is my main reason for using it: I like having to install the things I really want, which gives me a chance to consider the security implications of them, instead of having many things pre-installed and I don't know what the total risks are. And nothing else I know of has gone since ~1996 with only 2 of the worst kind of security holes (i.e., remote exploit of something I didn't even need, but was installed by default).
In the base install are many useful things (including a web server IIRC, though the port is not exposed by default), and those are audited and have that excellent track record.
Then when you install extra things, they are usually limited by what user they run as, and usually have pledge/unveil run (limiting access to predetermined/approved syscalls and parts of the file system) so they can't break other things if compromised.
I do change my default umask (/etc/profile, sourced by shell startup files for all users) to 0077, which means putting the pkg_add command inside a script ("pa") that first sets it back to 0022 temporarily.
Also, for finding packages to install, doing pkg_add pkglocate, then using pkglocate -i, or pkg_add portslist then just searching the whole list with things like less /usr/local/share/ports-INDEX or less /usr/local/share/sqlports-list can be useful. There are very many packages available (over 12k on the amd64 platform).