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

Stable kernels 4.19.9, 4.14.88, 4.9.145, 4.4.167, and 3.18.129

Software: Vivaldi, QEMU and Manpages

  • Vivaldi 2.2 adds tweakable toolbars and Netflix for Linux
    UPSTART WEB BROWSER Vivaldi has released version 2.2, with a number of new features which continue its aim to differentiate itself from other Chromium browsers. The privacy passionate progeny of Opera co-founder Jon Von Tetzchner boasts improved tab management, support for pop-out video windows, configurable toolbars and updates to acccessibility. [...] "Customizing a browser as per your needs is not only a thing for pros and geeks. The key is to create something that works for you," says Vivaldi CEO Jon von Tetzchner. "Features are what draw people to Vivaldi and details are what keep them there. That's why we are always striving to fit every use case and giving our users different ways to browse."
  • QEMU 3.1 Released For Advancing The Linux Open-Source Virtualization Stack
    The QEMU emulator that is widely used by the open-source Linux virtualization stack is out with its version 3.1 feature release. This is the QEMU update that is adding multi-threaded Tiny Code Generator support, display improvements, adds the Cortex-A72 model and other ARM improvements, and various other enhancements.
  • What are Linux man pages?
    Have you ever sought help on a technical issue, only to be told RTFM? What is that acronym? In a safe-for-work translation, it means Read The Freaking Manual. That's all fine and good when you working with something that has a downloadable PDF file containing all the necessary information you need. But what about a Linux command? There are no manuals to be had. Or are there?

OSS Leftovers

  • JFrog Empowers Millions of Open Source Go Developers, Announces Community's First Public Go Repository
    JFrog, the Universal DevOps technology leader known for enabling liquid software via continuous software update flows, is announcing the coming availability of JFrog GoCenter, the first-ever central repository for software modules developed in the popular Go programming language. GoCenter is a free, open source and public service that will be provided for the broad Go community in early 2019, and is being showcased at KubeCon Seattle.
  • Open Sesame
    Although it’s free for users, people invest time in making the technology better or creating it in the first place. [...] When a project is open-source, it means that the software, hardware or data are open for users to use, access, change or distribute for free. An open-source project can also make it easier to bring a team together to develop a project, Davis says.
  • Fuchsia SDK and ‘device’ now included in Android Open Source Project
    Fuchsia, Google’s future OS project, is getting more connected to Android. The search giant has added two Fuchsia items to its Android Open Source Project (AOSP) code. A new commit posted to the AOSP Gerrit — an online code collaboration and management tool — added two Fuchsia ‘repos’ to the primary ‘manifest’ of AOSP. In other words, developers added two Fuchsia files to the instructions that tell Google’s download tool ‘Repo’ what to include when a user downloads AOSP. Further, for those unfamiliar with AOSP, it’s a compilation of Android made available for anyone to use.
  • Fuchsia SDK & Test Device Appear In Android Open Source Project
    Google has taken substantial new steps toward the release of its long-awaited new operating system Fuchsia, based on recently noticed changes to the Android Open Source Project (AOSP) codebase. Although AOSP is most often connected to Android OS and development on that platform, Fuchsia OS has now appeared as both an SDK and test device in the repository. According to comments on the commits, the OS's repositories being included in the Android master manifest equates to an added 760MB. The Gerrit UI also shows changes to approximately 977 files in total with the addition of the Fuchsia software development kit (SDK) and a related test device. Interestingly, the test device SDK seems to be based on or at least tested with the configuration for 'Walleye' -- Google's codename for one of the Pixel 2 handsets.
  • ‘This is not a big boys club’: FINOS seeks to open up open source
    Attend an event about open source development and collaboration in financial technology, and you will see developers and executives from Capital One, Barclays, JPMorgan Chase, BlackRock and perhaps a handful of other financial institutions, along with open-source-focused vendors like Red Hat (now part of IBM).
  • The Autoware Foundation - An Open Alliance for Autonomous Driving Technology
  • What is Open Source & Why Should You Care?
    The term ‘open source’ is used with excitement throughout multiple industries, yet folks are still asking a lot of questions, chief among them: What is open source & why should I care? Well, for industrial and process manufacturing, open source is rapidly becoming a fundamental for the digitalization of these industries. Industrial automation users, system integrators, machine builders, and automation suppliers that understand how to embrace and leverage open source are dramatically improving their odds of being effective competitors in their respective industries.
  • QLC Chain to open source WinQ server router, focuses on multi-sig smart contracts
    QLC Chain has released its bi-weekly report, which highlights development progress of the public blockchain and VPN routers, adjustment of QLC Chain’s development plan, and updates to WinQ 2.0. Recently, an incentive program was announced for VPN operators and active community members to test the platform.

Servers: Apache Cassandra, Kubernetes and Red Hat

  • Instaclustr Releases Three Open Source Projects That Facilitate Cassandra-Kubernetes Integration and LDAP/Kerberos Authentication
  • Instaclustr Announces Three Open Source Projects That Facilitate Cassandra-Kubernetes Integration and LDAP/Kerberos Authentication
    Instaclustr, the leading provider of completely managed solutions for scalable open source technologies, today announced the availability of three open source projects purpose-built to expand developers’ capabilities using Apache Cassandra and address pain points. These projects include an open source Cassandra operator for more seamlessly running and operating Cassandra within Kubernetes, and open source LDAP and Kerberos authenticator plug-ins for Cassandra.
  • Instaclustr expands Apache Cassandra with new open-source software
    Instaclustr Pty Ltd., which sells hosted and managed versions of popular open-source software Apache Cassandra, Spark and Kafka, is giving back to the community with three projects of its own. The company says it’s open-sourcing three “purpose-built” projects aimed at addressing pain points and expanding the capabilities of the Apache Cassandra database. Apache Cassandra is a distributed database that’s used to manage large amounts of structured data while providing continuous availability with no single point of failure.
  • Kubernetes open-source project matures as commercialization accelerates
    This week, the annual KubeCon + CloudNativeCon North America 2018 event taking place in Seattle will give the cloud computing industry a chance to take stock of how far Kubernetes has come. On the flip side, the show also will work through the issues that may be preventing this open-source container orchestration platform from achieving its full potential. Kubernetes has been a banner story in high tech throughout 2018, and the technology looks like it will continue its momentum toward ubiquitous adoption in coming years. The Kubernetes ecosystem has become amazingly vibrant, though that’s a double-edged sword.
  • Kubernetes caretaker auditions for Hoarders; takes in another open source project
    At the Cloud Native Computing Foundation's (CNCF) KubeCon + CloudNativeCon North America 2018 meetup on Tuesday, the CNCF revealed it will adopt, shelter and nourish an itinerant jumble of letters known on the street as "etcd." Pronounced "et-cee-dee" among those who dare speak its name, etcd is a distributed key-value store. It hails from the Linux /etc/ directory, which lives in the root folder and stores configuration files and related subdirectories.
  • Kubernetes and serverless are getting chummy in open source
    But the Cloud Native Computing Foundation — home to Kubernetes, the popular open-source container orchestration platform — wants everyone to know it’s not partial to either containers or serverless, and there’s room for both, and others, in next-generation enterprise technology. “We love serverless in CNCF,” said Chris Aniszczyk (pictured), chief technology officer and chief operating officer of CNCF. “We just view it as another kind of programmatic model that eventually runs on some type of containerized stack.”
  • Atomist Announces Delivery to Kubernetes With Its Open Source SDM, adds GitLab Support
    Atomist, the software delivery automation company, today announced the ability for developers to now deliver to Kubernetes using the open source Software Delivery Machine (SDM) in local mode. SDM local is completely open source and now supports delivery to Kubernetes, whether a single-node cluster on a laptop using minikube or a fully-managed Kubernetes service.
  • Why Kubernetes Is Successful and Boring
    Google has had a common message throughout 2018 about Kubernetes, and the message is simple: Kubernetes is boring. At the KubeCon + CloudNativeCon NA 2018 event here, Google engineer and conference co-chair Janet Kuo echoed comments made by her peer Aparna Sinha, group product manager at Google, at the Kubecon and CloudNativecon Europe 2018 keynotes in May, which is simply that Kubernetes is boring, and boring is good. Kuo said in the early days of Kubernetes the focus was on building fast and adding new features. By 2015, a focus was added to make it easier for users and administrators to build, deploy and use Kubernetes. At this point in the maturity cycle of Kubernetes, Kuo commented that adoption has moved from the early stage of adopters to more mainstream deployments. "Kubernetes is now getting so solid and so mature and so great, that it is very, very boring," Kuo said during her keynote. "Boring is good; it means that lots of companies are already using it, and it just works." Kuo added that being boring means organizations can just focus on delivering business value, rather than spending time on making Kubernetes usable.
  • Kubernetes Federation Evolution
    Deploying applications to a kubernetes cluster is well defined and can in some cases be as simple as kubectl create -f app.yaml. The user’s story to deploy apps across multiple clusters has not been that simple. How should an app workload be distributed? Should the app resources be replicated into all clusters, or replicated into selected clusters or partitioned into clusters? How is the access to clusters managed? What happens if some of the resources, which user wants to distribute pre-exist in all or fewer clusters in some form. In SIG multicluster, our journey has revealed that there are multiple possible models to solve these problems and there probably is no single best fit all scenario solution. Federation however is the single biggest kubernetes open source sub project which has seen maximum interest and contribution from the community in this problem space. The project initially reused the k8s API to do away with any added usage complexity for an existing k8s user. This became non-viable because of problems best discussed in this community update.
  • [Red Hat] Men: Step out of your bubble to champion gender diversity
    According to Catalyst Canada, men represent more than 95 per cent of the CEO positions in Canada’s 100 largest publicly traded companies. With such a big divide, those who are leaders must help define the role those with power and privilege play. Many men want to get more involved, but we must go about it the right way. We want to respect the successful work that has already been done, find the right fit for our skills and learn from our female leaders who have the deep knowledge of this issue. As Tanya van Biesen, executive director of Catalyst Canada, has said: “The path to gender equity is a journey. There is no silver bullet – only commitment and action.” As leaders, our self-worth is often measured by meeting hard targets and achieving financial goals. Stepping forward to become an advocate for gender diversity is uncharted territory for many of us. Yet, it is a business imperative with a body of evidence demonstrating a positive effect on the bottom line.
  • IBM's $34 billion Red Hat acquisition came after deal talks with Microsoft, Google, and Amazon, sources say
    When IBM announced its $34 billion acquisition of Red Hat on October 28, the tech word was struck by the huge price tag, as well as its potential to revive IBM's struggling cloud business. But as it turns out, things could have gone a lot differently. Microsoft, Google, and Amazon all engaged in deal discussions with Red Hat and looked closely into an acquisition in the months and weeks before Red Hat struck a deal with IBM, according to sources familiar with the deal. As an open-source software company, Red Hat is strategic because of its popularity with developers. It's also is the largest commercial maker of the Linux operating system. IBM wanted the technology to enhance its hybrid-cloud project and to give its portfolio an edge. Red Hat indicated in a public filing on November 30 that three unnamed companies considered making bids in addition to IBM. CNBC reported in October that Google had looked into buying Red Hat. But Microsoft and Amazon's deal talks with Red Hat have not been previously reported.
  • IBM goes hard in open source so enterprises can take it easy
    IBM’s investment in open source goes back years. Big Blue went all-in on Kubernetes, the popular open-source container orchestration platform about two years ago, according to Chris Rosen (pictured), program director, offering management, IBM Container Service and IBM Container Registry. The company contributes to the open-source Cloud Native Computing Foundation upstream and then simplifies the technology for end users.
  • Arista EOS containers integrated with Red Hat, Tigera products
    Arista has integrated the containerized version of its network operating system with Red Hat and Tigera software to support containers running on public, private and hybrid clouds. Arista released this week a technology preview of the integration of containerized Arista EOS with Tigera Calico, the open source control plane the company developed to distribute security policy rules across containers and virtual machines running on cloud environments. Arista plans to make the integration generally available in 2019 within the Tigera Secure Enterprise Edition product.
  • Contrail, Red Hat treat multicloud-network headache with Kubernetes
    A number of computing customers lately are asking for a smarter network. This might mean programmability, transparency, multiple lanes for prioritized web traffic, etc. The question is, will software developers and administrators need to get smarter in order to use such networks? Don’t they have their hands full already refactoring applications and managing distributed cloud environments? Developers these days simply want to consume the network in the same way they consume compute and storage. They don’t want the job of configuring it — at least not if that entails plunging deep below the application layer. “The app is the thing that’s going to consume these things, and the app developer doesn’t necessarily want to worry about IP address and port numbers and firewall rules and things like that,” said Scott Sneddon (pictured, left), senior director and chief evangelist of cloud at Juniper Networks Inc.