freebsd at edvax.de
Mon Sep 28 09:08:57 UTC 2015
On Sun, 27 Sep 2015 19:00:47 -0600 (MDT), Warren Block wrote:
> On Sun, 27 Sep 2015, William A. Mahaffey III wrote:
> > If I use disklabel to add a 'd' slice, will that mess up what is already
> > there ? What is the syntax for that, I don't see it in the disklabel/bsdlabel
> > man page ? The man page for disklabel/bsdlabel shows a way to initialize a
> > whole disk using 'fdisk -BI <dev>' & implies that this will create a 'da0s1'
> > slice in the process. However it will also wipe out what is already there. If
> > I do that, can I then copy the img-file contents in some way ? Thanks & TIA
> > :-) ....
> Please stop using fdisk and bsdlabel. gpart(8) does everything they do
> and is easier to use.
But it works so nicely, especially for all the many
non-standard settings! :-)
Sure, gpart (and in a related context, GPT) is the
way to go for 99% of use cases. Somehow I still like
the ability to ditch partitioning at all and just
newfs a device, or make a "one big bootable partition"
with two bsdlabel commands. This knowledge will soon
go down the drain, together with other "old craft"
of UNIX skills many decades old. :-)
> Messing with a bsdlabel installer image is probably a waste of time, but
> yes, you can add a partition (a bsdlabel partition). Or you can
> probably use growfs to expand the filesystem to the size of the drive.
It's probably much easier to create a custom bootable
image (even as a live file system) which is able to
run bsdinstall and maybe even has pkg and some desired
packages available. For example, have created my own
USB images for different purposes, and it's actually
not that hard. Still the OS does not provide an easy
means to do this (like a "make <something>" command),
but there are several ports to help with this task.
> If you already have images on the network, consider mounting them with
> NFS instead.
This is only an option for networked machines. However,
as soon as you're going to install packages via pkg,
Internet connection (and therefore network) is mandatory,
either for accessing images or to write to a "scratch
space" for program outputs you want to review later.
Still the idea of being able to write to the installation
image (maybe to a _different_ partition on it) is good:
In case no network can be reached, you can still store
stuff on it - I can imagine many purposes. :-)
As the installation image is best dealt with bsdlabel,
resizing 'c' and adding a 'd' partition should be possible,
with the commands run through a mdconfig'ured virtual
node connected to the image file. As I said, I haven't
tried this, but it's probably possible. In worst case,
it's a "try & fail" issue. :-)
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
More information about the freebsd-questions