Introduction
Introduction Statistics Contact Development Disclaimer Help
Installing FreeBSD
Sunday Feb 17 5:10:38 2019
Several years ago I tried installing some variant of BSD (do not
remember which one) without any success. I only remember you had to
prepare something called slices (ie. partitions on your hard disk)
and the whole thing was not easy to do, not for a newbie at least.
Over the years and after using other unix-like operating systems I
was well ready to try the installation again. Oh man, much to my
surprise it was so, so easy that I still cannot believe it myself.
The current version is 12 and even though I had to repeat the steps
couple of times since I didn't exactly know what the installer trie
to accomplish in certain steps, the process was easy as 1,2,3.
Unlike my first time years ago, this time I chose installing to the
entire hard drive so I didn't have to worry about partitions (I do
not even know whether the system still calls them slices or not).
The downside of such an easy and quick installation is that you end
up with a truly barebones system, no graphical environment, very
little software installed. Well, I guess that a newbie can feel
lost in such an scenario. Imagine that the first program I had to
install was "pkg" the package manager. Oh my...
After that, almost everything was downhill. I had to get used to so
applications I had hardly ever used like the csh and urxvt (I knew
about urxvt but never it used extensively).
Then after installing x-org, i3, mc, elinks, screen I could use
FreeBSD like a pro. Until I discovered that dillo was compiled
without --enable-ssl. I tried hard to install it from the ports
enabling ssl but to no avail. So I made the switch to surf (from
the suckless project) and now I can really be happy with my new
system.
p.s. From the top of my head I also installed mplayer for multimedi
stuff.
You are viewing proxied material from sdf.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.