Please be sure to use the right dev name!
You might have a look into /var/log/messages to get the right name after
connecting the stick.
On 07.07.2015 11:59, Matthias Play wrote:
You might als download dfly-x86_64-4.2.1_REL.img.bz2 instead and put it
on an USB stick for booting. Issue the command:
bzcat dfly-x86_64-4.2.1_REL.img.bz2 | dd of=<USB dev> bs=1M
and replace <usb dev> with the stick's dev name (something like /dev/daX
with X>=8).
After that you should be able to boot from the stick.
On 07.07.2015 10:17, Bret Busby wrote:
Hello.
At the web page at
http://www.dragonflybsd.org/download/
is stated that the iso for dragonflybsd is a LiveCD, and the image is at
http://mirror-master.dragonflybsd.org/iso-images/dfly-x86_64-4.2.1_REL.iso.bz2
which is a bz2 file of about 200MB, which I have downloaded.
I did not see any instructions for dealing with this file, so, is it a
self-extracting iso file, such that the bz2 file is to be written to a
disc, and then the disc with the bz2 file, used for booting, or, is
the file required to be extracted to a directory which is then to be
written to the disc for booting?
Also, with the previous references to the mate GUI, does the iso image
come with mate incorporated into it, so that a user can boot the
LiveCD and thence examine the mate GUI?
Thank you in anticipation.
