From 4eb8d8d334f84e182eebcb9223be8fbb83ff16ce Mon Sep 17 00:00:00 2001 From: dillon Date: Mon, 13 Apr 2020 17:38:22 +0000 Subject: [PATCH] update for modern installer layout and talk about hammer2 --- .../handbook/environmentquickstart/index.mdwn | 61 ++++++++++++++----- 1 file changed, 47 insertions(+), 14 deletions(-) diff --git a/docs/handbook/environmentquickstart/index.mdwn b/docs/handbook/environmentquickstart/index.mdwn index 36607fc5..c8ef0e80 100644 --- a/docs/handbook/environmentquickstart/index.mdwn +++ b/docs/handbook/environmentquickstart/index.mdwn @@ -26,7 +26,28 @@ The configuration files for the base system can be found in `/etc`. Third-party There are several different ways to install software and which version you use depends on which DragonFly BSD version you have. You can compile things from source code, or you can use binary packages. -## Disk layout of a New Dragonfly BSD System using the HAMMER filesystem +## Disk layout of a New Dragonfly BSD System using the HAMMER2 filesystem + +HAMMER2 is now the default filesystem selected by the installer. It is not quite as feature-full as HAMMER in that there are no automatic snapshots and no undo feature, but HAMMER2 is more robust than HAMMER1 and also sports writable snapshots whereas HAMMER1 only has read-only snapshots. HAMMER2 is also a bit easier to manage. + +If you chose to install on the HAMMER2 file system during installation you will be left with a system with the following disk configuration: + + # df -h + Filesystem Size Used Avail Capacity Mounted on + /dev/serno/9VMBWDM1.s1d 288G 12G 276G 4% / + devfs 1.0K 1.0K 0B 100% /dev + /dev/serno/9VMBWDM1.s1a 1G 500M 500M 50% /boot + /dev/serno/9VMBWDM1.s1e 100G 1M 100G 0% /build + /build/usr.obj * * * * /usr/obj + /build/usr.distfiles * * * * /usr/distfiles + /build/var.cache * * * * /var/cache + /build/var.crash * * * * /var/crash + tmpfs 8G 0B 8G 0% /tmp + tmpfs 8G 0B 8G 0% /var/tmp + procfs 4.0K 4.0K 0B 100% /proc + + +## Disk layout of a New Dragonfly BSD System using the older HAMMER1 filesystem If you chose to install on the HAMMER file system during installation you will be left with a system with the following disk configuration: @@ -34,14 +55,14 @@ If you chose to install on the HAMMER file system during installation you will b Filesystem Size Used Avail Capacity Mounted on ROOT 288G 12G 276G 4% / devfs 1.0K 1.0K 0B 100% /dev - /dev/serno/9VMBWDM1.s1a 756M 138M 558M 20% /boot - /pfs/@@-1:00001 288G 12G 276G 4% /var - /pfs/@@-1:00002 288G 12G 276G 4% /tmp - /pfs/@@-1:00003 288G 12G 276G 4% /usr - /pfs/@@-1:00004 288G 12G 276G 4% /home - /pfs/@@-1:00005 288G 12G 276G 4% /usr/obj - /pfs/@@-1:00006 288G 12G 276G 4% /var/crash - /pfs/@@-1:00007 288G 12G 276G 4% /var/tmp + /dev/serno/9VMBWDM1.s1a 1G 500M 500M 50% /boot + /dev/serno/9VMBWDM1.s1e 100G 1M 100G 0% /build + /build/usr.obj * * * * /usr/obj + /build/usr.distfiles * * * * /usr/distfiles + /build/var.cache * * * * /var/cache + /build/var.crash * * * * /var/crash + tmpfs 8G 0B 8G 0% /tmp + tmpfs 8G 0B 8G 0% /var/tmp procfs 4.0K 4.0K 0B 100% /proc In this example @@ -76,24 +97,36 @@ The disk label looks as follows: 16 partitions: # size offset fstype fsuuid - a: 786432 0 4.2BSD # 768.000MB + a: 1048576 0 4.2BSD # 1024.000MB b: 8388608 786432 swap # 8192.000MB - d: 303392600 9175040 HAMMER # 296281.836MB + d: 303392600 9175040 HAMMER2 # 296281.836MB + e: * * HAMMER2 # blah blah ('e' partition is optional) a-stor_uuid: eb1c8aac-d2af-11df-b588-01138fad54f5 b-stor_uuid: eb1c8aec-d2af-11df-b588-01138fad54f5 d-stor_uuid: eb1c8b21-d2af-11df-b588-01138fad54f5 -The slice has 3 partitions: +The slice has 3 or 4 partitions: * `a` - for `/boot` * `b` - for swap -* `d` - for `/`, a HAMMER file system labeled ROOT +* `d` - for `/`, a HAMMER or HAMMER2 filesystem labeled ROOT +* `e` - for `/build`, a HAMMER or HAMMER2 filesystem labeled (typically) DATA -When you create a HAMMER file system, you must give it a label. Here, the installer labelled it as "ROOT" and mounted it as +When you create a HAMMER filesystem, you must give it a label. Here, the installer labelled it as "ROOT" and mounted it as ROOT 288G 12G 276G 4% / +When you create a HAMMER2 filesystem the label is optional and a default will be supplied based on the partition letter. Either BOOT, ROOT, SWAP, or DATA. + +## HAMMER2 PFSs + +In HAMMER2 the filesystem is typically mounted via its default label. There is no distinction between this PFS and others you might create. You can create additional PFSs or you can snapshot an existing PFS and specify a new PFS name for the snapshot. In HAMMER2, all snapshots must be independently mounted. In addition, HAMMER2 snapshots are writable entities and you can use them just as you would the original filesystem. + +HAMMER2 does not do automatic history, snapshotting, or undo. You have to snapshot a filesystem manually with the 'hammer2' utility. + +## HAMMER1 PFSs (only applicable to HAMMER1) + A PFS is a Pseudo File System inside a HAMMER file system. The HAMMER file system in which the PFSes are created is referred to as the root file system. You should not confuse the "root" file system with the label "ROOT": the label can be anything. The installer labeled it as ROOT because it is mounted at `/`. Now inside the root HAMMER file system you find the installer created 7 PFSes from the `df -h` output above, let us see how they are mounted in `/etc/fstab`: -- 2.41.0