Started using FreeBSD on an old laptop reddit / freebsd ---------------------------------------------------------------------- _DESTRUCTION · 2020-10-05 14:29 BSD ---------------------------------------------------------------------- snk · 2020-10-05 14:41 The [FreeBSD Handbook](https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/) is always the first stop. You'll get walkthroughs there on everything from first time installation to more advanced stuff like running network services for your domain. There's some good sections there on usage, package installation/upgrades, and day-to-day system administration stuff that might be what you're looking for. ---------------------------------------------------------------------- gumnos · 2020-10-05 15:18 without knowing what the "fixes on the internet" instructed you to do, it's hard to shed light on what they actually did. On the whole, the CLI is largely portable across platforms. You might encounter a few small differences, but usually the man-pages will help you track down what's happening. If you feel inadequate here, pretty much any command-line tutorial or books will help you get up to speed regardless of whether you are on Linux or a BSD. There will be platform-specific tools, but they tend to fit in with the CLI-command- ecosystem. ---------------------------------------------------------------------- [deleted] · 2020-10-05 15:39 [deleted] ---------------------------------------------------------------------- Yaroze · 2020-10-05 15:49 The beep is known as a bell - sysctl allows you to edit operational tunables (see them as tiny cogs) within the operating system. By setting *hw.syscons.bell* you told the operating system to stop activating the bell cog and thas deactivating the pc's speaker bell. Most applications have "-h" argument, or "vim -h". If that fails then and if it's sane application it should also have a man page which you can access via: "man appName" ---------------------------------------------------------------------- Yaroze · 2020-10-05 15:54 Start with the basics, Myself would recommend: - Edit the default message of the day message upon login to display a fortune cookie - Create an SSH Banner and test it - Configure a Secondary IP address - Configure a WebServer and bind it to the second ip address only Then adventure out in to creating a jail and then configure the web- server within that. ---------------------------------------------------------------------- gumnos · 2020-10-05 16:09 /u/Yaroze gave a good answer to the first half of your reply re. the `sysctl` vs. the bell. Over in the GNU world, most of their utilities take a `--help` option that will provide a summary of how it can be used. The convention has become common enough that many non-GNU utilities also have support for a `--help` option. In the BSD world, you're generally referred to the `man` pages which have exhaustive documentation on options. So if you're using `vi(1)` (which on BSD systems is actually `nvi`), you can read up on `man vi` for fairly thorough coverage of available `vi` commands. If you've installed `vim`, it does support `--help`, but also comes with its own internal help system that you can access by typing :help from within vim. And `vim` has internal documentation that is some of the best I've ever encountered. ---------------------------------------------------------------------- GPruts · 2020-10-05 20:11 Good idea going for FreeBSD! Indeed go for the handbook as others have said. This is something that's pretty unique about FreeBSD: The documentation is excellent and kept up to date with every release. Only Arch approaches the same completeness but it's much less structured due to being a wiki. With FreeBSD it's much clearer what's the 'official' way of doing things. Due to the fragmentation of Linux this is kinda lacking there. The jails and zfs are also super features though these days Linux has both as well (not jails as such but docker's kinda similar) But anyway in terms of what to set up, depends what you want to use it for. Start with getting X up and running if you want a desktop. With services, play with the jails for sure as they add great security. And look at the differences between packages and ports: Eventually you'll end up needing some compile-time flags that aren't in a package so you'll have to use the ports collection. Which is a bit similar to Arch's AUR in how it's used, if you know that. ---------------------------------------------------------------------- Jazzynupe · 2020-10-05 20:34 If you are a visual learner, there are also some walk throughs on YouTube as well. Some are better than others but they can help you understand some of the ins and outs. Most go through the basics of installation but some actually get into using it a bit more. I can understand how reading a thick walk-through without some refreshing interaction or discussion can drag down the process. But those videos may be helpful supplement to the handbook. ---------------------------------------------------------------------- [deleted] · 2020-10-06 20:59 [deleted] ---------------------------------------------------------------------- GPruts · 2020-10-08 11:02 Yes what I also like about FreeBSD is that it doesn't follow commerce strongly. Big parties like Microsoft, Google, IBM (through RedHat), Canonical have a big influence on the Linux kernel. A lot of patches being submitted are just to improve their usecases involving cloud operations. But with all the commercial influence comes general direction away from pure openness. FreeBSD is largely free from this type of involvement. It's not as bleeding edge due to the lower investment but it's got sure and steady progress. I think in this case the BSD license stops companies investing in it as the results can be used freely by anyone. IMO that's a good thing, it keeps the product more pure :) But the end to end ownership by one team is definitely good, and it is really what makes other OSes (like macOS and Windows) work well.