Background: To increase community engagement and to give our new BSD section a healthy and prosperous new life, AdminDev created the “BSD Challenge” (BSD Challenge). The *BSD challenge is based off of the “1 Year Linux Challenge” (1 Year Linux Challenge) but focused on *BSD instead of Linux. The premise is to use *BSD for one year and to document your adventure in a thread. At the end of the 1 year, you will be awarded with a badge for your efforts.
Purpose/Goals: To install, use, and to maintain a DragonFlyBSD (https://www.dragonflybsd.org/) desktop system running the openbox WM (http://openbox.org/wiki/Main_Page) for a year to complete the *BSD challenge. As well as to compile some applications from sauce (source), and to document the journey and actions, as much as personally possible in detail. As well as to try and help answer users/readers questions.
Materials: Dell AIO Inspiron (Inspiron one 2320, with a non-stock 500GB Western Digital HD), Wired Mouse ( ), HP USB 2.0 Keyboard (E145614), DragonFlyBSD CD (dfly-x86_64-5.4.1_REL.iso), DragonFlyBSD mailing list (https://www.dragonflybsd.org/mailinglists/), Openbox WM (http://openbox.org/wiki/Main_Page), Burniso2cd
Method: DragonflyBSD will be installed on a Dell Inspiron AIO via a DVD-RW disc. The installation of pre-built packages will be done thru the terminal with the package manager (pkg), and source based applications will be compiled via the make command in the ports tree. Documentation will happen live, as soon as things are being worked on.
Other Notes: My grammar and writing skills are trash tier ranked. Please ignore. . I don’t see myself doing too many complex tasks, as I am a very basic computer user. Although, I hope to at least try to set up and use and familiarize myself with jails and maybe some other more complex things.
The actual start of the journey will begin on post #54. I will document what I am doing down below in the reply section of the thread, and then summarize what I did in those posts and include those summaries under the Summary of Results section here in the OP, as well as include a link back to the post in the thread for what it is that I summarized.
I have chosen to take part in the BSD challenge to help increase community engagement within the forum and of course to get a forum badge . DragonFlyBSD is the vehicle of choice for the challenge as i have used it once before in the past, and it is something that I am somewhat familiar with. It is also something that is quite unique, as when I joined the challenge no one else had chosen it. Of course I was the first to join the official challenge (I’m not gloating ), so that may explain that.
DragonFlyBSD is written by Matthew Dillon, a former Amiga developer from the late 80s to early 90s, and a former FreeBSD developer from 1994 to 2003. DragonFlyBSD differs significantly from its parent, FreeBSD, in that it defaults with its homemade file system, Hammer 2. There are also some other changes that can be seen on their Wikipedia page. One could also ask of the differences of the two *BSDs on the DragonFlyBSD community mailing list.
TODO LIST :
- Download DragonflyBSD (completed on March 25th 2019)
- Install DragonflyBSD (WIP March 25th 2019) (installed on 4/29/19)
- Setup and move in (done on 4/29/29)
- Get used to terminal commands
Summary of Results
Can’t get DragonFlyBSD to install. (March 25th 2019) Goalkeepers DragonFlyBSD Adventures
- Was able to install and setup of DragonFlyBSD on the 29th of March. When I installed the system the first time, I didn’t enable bootblacks which was why I received that screen about selecting a proper boot device. I then went back, to the live CD, and enabled bootblocks on the drive and rebooted. I was greeted with this image:
At this screen, all I was supposed to do was hit the
enterkey on the keyboard and then the system would have booted. Goalkeepers DragonFlyBSD Adventures
It seems that if you do a UEFI install, you need to manually do bootblocks as I did thru another option on the live CD. After the system is installed on a non UEFI install, a screen will prompt you to enable bootblocks.