Language Selection

English French German Italian Portuguese Spanish

Beastie of an OS

Filed under
Reviews
BSD
-s

Once a distro goes into beta 3, most of the major choices are in place. In looking at the 3rd testing versions of distributions, one can get a fairly good idea of what a distro might be like once it's released. The only experience I've had with a BSD clone or derivative was with my PC-BSD review some months ago. That install was as simple as 1, 2, 3... or click, click, click. I'd heard the horror stories about other BSD installs, yet downloaded 6.0 beta 3 with hope. Was this going to be a brain-burning, hair-pulling, data-losing proposition? What happened with my attempted FreeBSD 6.0 Beta 3 install?

As this is my first foray into FreeBSD, this isn't so much a "what's new" as it is a "what's here".

First off, the install was much easier than running it... at first. But as with many new things, once you learn how, you wonder why you were nervous to begin with. The installer was easy enough. I had read the docs on FreeBSD before and as I recall, it sounded like a cross between lfs and gentoo. But if that was true then, it certainly isn't true now. The FreeBSD installer was a nice ascii graphical type installer that walks one through the install in much the same manner as Slackware. Can you install Slackware? Then you can install FreeBSD. In fact it even looks very much like Slackware's.

The most difficult step for the newcomer might be the fdisk step. I even experienced a sweaty-palm moment. The FreeBSD fdisk didn't seem to see all my partitions, or rather it saw the extended partition as one big empty slice. I toyed with the idea of inputting the start and end block numbers in and seeing if it installed on the correct partition, but chickened out of that. It was already complaining that it didn't agree with the geometry reported for the partitions it did see. I chose to put FreeBSD on the first partition of the drive - former spot reserved for, if not the current home of, Windows. It is now a Unix slice.

The rest of the install is fairly straight forward. One picks out the type of install they'd like, if I recall correctly, something like: developer, developer + kernel, developer + kernel + X11, etc., or as I chose ALL. It takes about 10 minutes to install the system, then it asks about packages and ports. I chose many many packages I'd need including KDE, gnome, and all the other window managers available during install. Turns out there are many many more available through their package manager. This step takes some time, probably a 1/2 hour or so, but then it gets to the configuration portion. It asks some questions about your net connection preferences, root password, setting up users & groups, and some other hardware. All this was quite easy to follow and complete.

I didn't choose to install its bootloader, instead I googled and discovered one only needs an entry in their linux lilo.conf very similar to ones we used for Windows. In fact, it's almost exactly like that. Mine looks like so:
other=/dev/hda1
table=/dev/hda
label=FreeBSD

Then run lilo and yippee! Upon reboot, lilo hands off to the FreeBSD
bootloader and your new system boots as desired.

One is booted to a terminal for logging in. First thing I always do is setup X. I fired up my console browsers in an attempt to download the NVIDIA drivers, but that failed as NVIDIA changed their site since I last downloaded their drivers with a text browser. I used to think how nice that one could use Links/Lynx to do that, but now their stupid javascript license agreement ruins it. So, I improvised. Since my FreeBSD is still not seeing anything in my extended partition, I had to make other arrangements. This was all in vain as the install bombed out very early on. It shot an error something about NOOBJ is deprecated to NO_OBJ or some such and I knew it was vesa for me. Xorg NV drivers lock my machine up fairly tight no matter the boot options I use.

However, there was no /etc/X11/xorg.conf skeleton in place and copying one from another install wasn't an option, so I was left to run Xorg -configure. This sets up a test file in /root called xorg.conf.new, and one can test their configuration with Xorg -config xorg.conf.new. If it works well, then you can cp it to /etc/X11/xorg.conf, and I did.

Now to start KDE, or actually more accurately, KDM. I wanted to be able to check out all the window managers and figured KDM was my best bet. But where the heck was it? As with many Linux commands, fortunately "which" is in my BSD Unix clone and it worked quite well. I found xinit was located in /usr/X11R6/bin and kdm was located at /usr/local/bin/kdm. So su to root and issue the command /usr/X11R6/bin/xinit /usr/local/bin/kdm and we are in business. In the future to expedite things, I learned startkde was in /usr/local/bin/startkde. One finds the standard and complete KDE 3.4.2 upon startup or one of many other window managers.

        

        

Many ports get installed into /usr/local with FreeBSD and there is no /opt directory. In fact the directory structure may be similar in some ways to Linux, but to me, it was more different than alike. Many binaries are located in /usr/libexec and /usr/X11R6/libexec. But how does one find something not in their path? As you might recall in Linux systems, you can't use locate or slocate until you build the database, and regularly update it. But "which updatedb" didn't turn up anything. Thank goodness for google. To build and update that locate database, one needs to issue /usr/libexec/locate.updatedb

The kernel sources are located in /usr/src/sys/i386/ and the modules reside in /boot/kernel. I don't know which kernel I'm actually running, as uname -a reveals

tuxmachine# uname -a
FreeBSD tuxmachine.tuxmachines.org 6.0-BETA3 FreeBSD 6.0-BETA3 #0: Mon Aug 22 22:59:46 UTC 2005 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386

I supposed I was still thinking Linux and expecting 2.6something. I try to remember we're dealing with a horse of a different color here. Anyway, at this point, if support for something wasn't in default, then I just won't use it. Maybe later.

One of those things not in the default kernel build was support for my bttv card. But sound was there and instead of modprobe snd_emu10k1, one issues kldload snd_emu10k1. For convenience I googled again and found that /boot/defaults/loader.conf is where one sets up their modules to autoload upon boot. Some commandline equivalents might be:

  • kldload = modprobe
  • kldunload = rmmod
  • kldstat = lsmod

But what about installing other software? I always like to have mplayer installed and GIMP is a must-have. But what do I do? Well, google of course. I found that the installer for FreeBSD is pkg_add. A lot of software is located in /usr/ports/. One could just navigate to the package directory of choice and issue a make install or one can use pkg_add <name of package>. Using the -r flag tells it to search remotely and get the latest available. It tries to sort out dependencies as well, but if there are issues, one might try portupgrade <package name> Mplayer isn't available, but gimp is as well as bash_completion.

There are many similarities between FreeBSD and Linux, but there are subtle differences as well. One major difference is the naming convention of devices. For example, ethX are vrX and hdX are acdX. As stated the directory structure is quite a bit different and I found commandline flags must be typed before the filename.

So, all in all, I found FreeBSD to be a capable desktop system. I've experienced a few konqueror crashes, but no other stability problems. I think their strongpoint is still in the server market and I'd probably appreciate it more there. If one checks in with Netcraft, they will find that almost 1/2 of the longest running systems by average uptime are FreeBSD.

I now recall how it feels to be the newbie stumbling around in a strange operating system. One wonderful resource where I found some answers to some of my issues is the BSDWiki. There is also some documentation as well as latest news on the FreeBSD website. I could very easily adapt to FreeBSD if something catastrophic happened where all the Linuxes (Lini?) suddenly vanished off the face of the earth. I can't say what's new in this release since the last stable or even the other betas, but I can state that many of the applications are of the lastest (stable) versions available. Try it, you might like it!

I have some additional Screenshots in the gallery.

More in Tux Machines

today's howtos

  • Top 12 Things to Do After Installing Linux Mint 21 (Vanessa)

    Linux Mint is one of the highly rated Linux distribution for desktops. Recently Linux Mint 21, code name Vanessa has been released. We have already covered an article which shows Linux mint 21 Installation steps. In this article, we will learn what are the Top 12 things to do after installing Linux Mint 21.

  • Creating a NixOS live USB for a full featured APU router

    At home, I'm running my own router to manage Internet, run DHCP, do filter and caching etc... I'm using an APU2 running OpenBSD, it works great so far, but I was curious to know if I could manage to run NixOS on it without having to deal with serial console and installation.

  • Internxt – Web3 Ready Privacy-centric Cloud Storage with Linux client

    Cloud storage has grown in importance in our daily digital lives. Almost all of us utilise some form of cloud storage service to ensure that our crucial information are kept forever. While cloud storage allows us to keep our data and retrieve them whenever and wherever we want, not all of them are as private and safe as Internxt.

  • How To Enable Dark Mode on Chromebook
  • Link: The MGR Window System

    The MGR Window System (via) is a brief introduction to MGR, an interesting and under-mentioned Unix windowing system, including a screenshot. I once used MGR myself and have reasonably fond memories of it, so it's nice to see more writing about it on the Internet.

Programming Leftovers

  • BaCon dependency removed from OE

    Many years ago, I was keen on BaCon. It converts traditional BASIC language to C and then calls gcc to create an executable. The problem I have is that it is cross-compiler-unfriendly. Host x86_64 and target x86_64, compiled in OE, it would generated executables, but some simply didn't work. Host x86_64, target i686, compiling in OE is broken. I have previously rewritten some in C, however, there still remained picscale', 'popup', 'pup_event_ipc', 'find_cat' and 'debdb2pupdb'.

  • Dirk Eddelbuettel: RApiSerialize 0.1.1 on CRAN: Updates

    A new release 0.1.1 of RApiSerialize is now on CRAN. While this is the first release in seven years (!!), it brings mostly minor internal updates along with the option of using serialization format 3. The package is used by both my RcppRedis as well as by Travers excellent qs package. Neither one of us has a need to switch to format 3 yet so format 2 remains the default. But along with other standard updates to package internals, it was straightforward to offer the newer format so that is what we did.

  • coarse or lazy? -- wingolog

    One of the things that had perplexed me about the Immix collector was how to effectively defragment the heap via evacuation while keeping just 2-3% of space as free blocks for an evacuation reserve. [...] To Immix, a "recyclable" block is partially full: it contains surviving data from a previous collection, but also some holes in which to allocate. But when would you have recyclable blocks at evacuation-time? Evacuation occurs as part of collection. Collection usually occurs when there's no more memory in which to allocate. At that point any recyclable block would have been allocated into already, and won't become recyclable again until the next trace of the heap identifies the block's surviving data. Of course after the next trace they could become "empty", if no object survives, or "full", if all lines have survivor objects.

  • Type-On Typewriter Animation in Nuke

    Users of AfterEffects are used to a plethora of presets for text animation. Unfortunately, text animation in Nuke is significantly limited in that the contents of the text field cannot be easily animated. I was working on producing a music video in which type-on text shows the lyrics in time with the music and ran into the limitation. I was not willing to mask letters individually using roto tools and instead decided to write a small python program that generates the animation in side of Nuke.

  • Multiple Inline SVGs (From QuickChart)

    I’m working on generating some stats and accompanying graphs for my blog (blog post to come on this…). For the charts, I’m using the quickchart.io API (a tool I’ve used before) and it’s beautifully simple: pass data as a URL, get back a chart. It’s working. My build hits the quickchart API, gets an SVG, and inlines it into my HTML. It looks great!

Games: Porting Doom, ScummVM, and The Legend of Zelda: Breath of the Wild

Debian Hiding Issues and Suppressing Volunteers' Dissent

  • Debian Suicide FYI: Lucas Nussbaum & Debian attempted exploit of OVH Hosting insider

    When Debian cabalists wanted to steal the domain debian-multimedia.org in 2014, they didn't go to a lawyer or the World Intellectual Property Organization. The Debian Project Leader (DPL), Lucas Nussbaum, who is a professor at Université de Lorraine, France, relied on another Debian Developer to tap the shoulder of an insider at OVH, which is also a French company, to see if the domain registration could be hijacked covertly. According to the email below, OVH managers didn't want to get involved in Debian dirty politics.

  • Ownership of debian.community domain [Ed: This statement was issued on a Sunday; they've solved none of the underlying issues, they're just gagging those who speak about Debian issues]

    The World Intellectual Property Organization (WIPO), under its Uniform Domain-Name Dispute-Resolution Policy (UDRP), decided that ownership of the debian.community domain should be transferred to the Debian Project. The appointed panel found that the disputed domain name is identical to a trademark in which the Complainant has rights.