doc listing of a full install's structure?
freebsd at edvax.de
Sat Nov 2 05:56:59 UTC 2019
On Fri, 1 Nov 2019 13:00:58 -0700, Frank Fenderbender wrote:
> I seek two
> 1) a full structural listing which I require for partitioning;
That depends on how you _want_ to partition.
Basically, you have the many choices of combining the following
two sets: GPT or MBR (GPT is recommended), "all in one" or highly
customized individual partitions.
It's hard to tell how much _space_ you're going to need, because
it depends on what you will install besides the FreeBSD OS. Further-
more, FreeBSD installs can be customized a bit at install time,
and if you recompile from source, you can have even more choice
on what to install.
> 2) the minimum-required and performance-optimizing sizes for each.
As mentioned above, this is hard, maybe impossible to tell. You
should allocate - and that's not much more than a guell - a few
100 GB at least. That doesn't say anything about being able to
perform an OS install in _less_ than 10 GB, though. ;-)
> Ubuntu 18.04 is the primary OS on the first internal drive,
> whereon exists the EFI partition and the GRUB install.
FreeBSD supports both EFI and being booted via GRUB.
> This (1-TB) internal HD will be used for FreeBSD only, however,
> I want the HD's partitions to match the structure so that
> backups are more-easily scheduled according to use, that
> data corruption is minimized, and so that system-restores
> are manageable.
How are those backups organized? If you have a "pattern"
already, you can try to use that. If you're going to dedicate
that 1 TB disk to FreeBSD (should be absolutely fine for OS,
and probably have enough space for a lot of programs and data),
just make sure GRUB gets an appropriate entry for that disk.
Install FreeBSD as if it would be the only OS on that disk,
which in fact it is. You can temporarily remove any other
disks from the system to make sure no bad things (TM( can
happen. Use labels. Then recombine, add GRUB entry, and boot
However, FreeBSD and Linux do organize and name things quite
differently, so don't assume that everything will be "the same"
on both ends. :-)
What you're attempting also depends on you backup/restore
mechanism which you didn't specify anything about. Is it a
whole disk dd image? Classic dump + restore? Some specific
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
More information about the freebsd-questions