Having toyed around for a while in <a href="/tags/qemu/" rel="tag">#QEMU</a> <a href="/tags/vm/" rel="tag">#VM</a> boxes with <a href="/tags/freebsd/" rel="tag">#FreeBSD</a>, <a href="/tags/openbsd/" rel="tag">#OpenBSD</a> and <a href="/tags/netbsd/" rel="tag">#NetBSD</a> as well. I found that <a href="/tags/gpart/" rel="tag">#gpart</a> in FreeBSD is intuitive and easy to use for disk partition manipulation, followed by gpt in NetBSD. For me, powerful and flexible as fdisk is, it has always been mysteriously difficult and fighting.<br><a href="/tags/usebsd/" rel="tag">#UseBSD</a> <a href="/tags/runbsd/" rel="tag">#RUNBSD</a> <a href="/tags/bsd/" rel="tag">#BSD</a> <a href="/tags/foss/" rel="tag">#FOSS</a> <a href="/tags/unix/" rel="tag">#UNIX</a><br>
gpart
And oh boy all terms seem so foreign to me as a long time <a href="/tags/linux/" rel="tag">#Linux</a> user. The same disk is called ada0 with a partition like ada0p2 in <a href="/tags/freebsd/" rel="tag">#FreeBSD</a>, will be called something like sd0 with sd0h in <a href="/tags/openbsd/" rel="tag">#OpenBSD</a>, ld0 and dk2 in <a href="/tags/netbsd/" rel="tag">#NetBSD</a> . Then to experiment, all the <a href="/tags/dkctl/" rel="tag">#dkctl</a>, <a href="/tags/disklabel/" rel="tag">#disklabel</a> and <a href="/tags/fdisk/" rel="tag">#fdisk</a> commands are like blue and red wires on a dynamite you have to get rid of 😱. Linux distros nowadays seem to be going to the <a href="/tags/gdisk/" rel="tag">#gdisk</a> way which feels very much like <a href="/tags/gpart/" rel="tag">#gpart</a> in FreeBSD.<br><a href="/tags/usebsd/" rel="tag">#UseBSD</a> <a href="/tags/runbsd/" rel="tag">#RUNBSD</a> <a href="/tags/bsd/" rel="tag">#BSD</a> <a href="/tags/foss/" rel="tag">#FOSS</a> <a href="/tags/unix/" rel="tag">#UNIX</a> <a href="/tags/linux/" rel="tag">#Linux</a><br>
Edited 137d ago