Language Selection

English French German Italian Portuguese Spanish

DesktopBSD Day 13 - Installing onto a Harddrive

Filed under
BSD

If there is one thing I don’t fondly remember about the PC-BSD series, it is the problems I had finding a hard drive that would be accepted as ‘good enough’ by the installer. The PC-BSD installer refused to cooperate with seven harddrives, ranging from 20 Gb to 120 Gb in size, reporting CRC errors etc. In the end only an old 6,4 Gb drive was deemed okay. Of course, it’s not bad to have a good hardware checkup, but in all cases the drives were and are still quite functional with Windows and various Linux distributions on them.

With this in mind I expected DesktopBSD to act similarly. I could have opted to go for the 6,4 Gb drive immediately, but that’s not the way of the empirical researcher. Again I went through the stack of hard drives. Yep, same list of errors and refusals. The DesktopBSD installer is somewhat smarter than the PC-BSD installer. Where PC-BSD would just start the install routine (only to fail at each attempted package), DesktopBSD would immediately halt with an error message.

More Here




More in Tux Machines

Games and Emulation

Linux Devices

Koozali SME Server 8.2 Reaches End of Life on March 31, Upgrade to Koozali SME 9

Koozali Foundation, through Terry Fage, announced the availability of a final set of updates for the Koozali SME Server 8.2 operating system, which will reach end of life this week. Patching some of the reported bugs, the new packages released today for Koozali SME Server 8.2 are e-smith-ibays-2.2.0-16.el5.sme.noarch.rpm, e-smith-manager-2.2.0-14.el5.sme.noarch.rpm, smeserver-clamav-2.2.0-15.el5.sme.noarch.rpm, smeserver-locale-*-2.2.0-56.el5.sme.noarch.rpm, and smeserver-yum-2.2.0-26.el5.sme.noarch.rpm. Read more

Development News

  • GCC for New Contributors
    I’m a relative newcomer to GCC, so I thought it was worth documenting some of the hurdles I ran into when I started working on GCC, to try to make it easier for others to start hacking on GCC. Hence this guide.
  • #1: Easy Package Registration
    Last month, Brian Ripley announced on r-devel that registration of routines would now be tested for by R CMD check in r-devel (which by next month will become R 3.4.0). A NOTE will be issued now, this will presumably turn into a WARNING at some point. Writing R Extensions has an updated introduction) of the topic.
  • Emacs as C IDE and JHBuild
    Although Builder clearly is The Future as GNOME IDE, I still all my coding in Emacs, mostly because I have been using it for such a long time that my brain is to all the shortcuts and workflows. But Emacs can be a good IDE too. The most obvious everyday features that I want from an IDE are good source code navigation and active assistance while editing. In the first category are tasks like jumping to symbol's definition, find all callers of a function and such things. For editing, auto-completion, immediate warnings and error reporting, semantic-aware re-factoring are a must. Specifically for GNOME related development, I need all this to also work with JHBuild.