A plan for a remote install and reinstall of FreeBSD
In our guides/howto section there are two interesting guides about installing FreeBSD without using sysinstall.
However, these guides assume you have physical access to the machine. But what if you have not, and the machine is in a datacenter 200 kms away?
My suggestion is have a small, say 2 Gigabyte, FreeBSD on the disk. This mini-FreeBSD installation is only used for a sysinstall-less install of the 'real' FreeBSD in the other slice(s).
The partitioning plan for this remote machine:
ad0s1 = 2 Gigabyte mini-FreeBSD only to be used for installing or reinstalling, the "real FBSD" on the other slices ad0s2 = Real FreeBSD "/", swap, "/usr" ad0s3 = Real FreeBSD "/tmp", "/var", "/var/tmp" , "/var/log" i ad0s4 = Real FreeBSD "/usr/local", "/home", "/var", "/var/mail"
There is 8 labels restriction per slice (at least for the disklabel or bsdlabel utility).
The glabel man page doesn't mention any limit in number of glabel'led partitions.
During the growing pains of the FreebSD 5.x series, I became am more focussed on OpenBSD, so I have never used glabel yet.
An overview of this 'bsdlabel' 8 partition/file system limit
1) a = "/" (reserved for "/" on the booting slice") 2) b = swap (reserved for swap) 3) c = complete slice (cannot be used) 4) d = 5) e = 6) f = 7) g = 8) h =
separate file systems for the following you have used them all.
1 "/usr" 2 "/var" 3 "/home" 4 "/tmp"
A reason for example is that you don't want an attacker to fill your "/var/log" logs with junk and thus leaving no more space for "/var/mail".
1 "/" 2 swap 3 "/usr" 4 "/usr/local" 5 "/usr/ports" 6 "/tmp" 7 "/var" 8 "/var/tmp" 9 "/var/log" 10 "/var/mail" 11 "/home"
from ad0s1 (the mini-FBSD), to ad0s2, which has the "/" filesystem of your new fresh install and
If next year yeat another new file system for FreeBSD emerges, let us call it YANFS, you can use the
the 'real' FBSD in slice 2,3 and 4 to first update your mini 'fixit" FBSD in slice 1 so it has all the
AFter changing the active partition from slice 2 to slice 1, you reboot and are in an "fixit" environment where you can (I am willing to bet on it) follow the Ultra-Modern FreeBSD Install with YANFS (vermaden way)
Does this sound like a good plan? I don't mean the bet, but the idea of using a mini-FBSD to create the equivalent of a Fixit or Rescue CD environment.
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
|Thread||Thread Starter||Forum||Replies||Last Post|
|Remote backups server using FreeBSD, ZFS, and Rsync||phoenix||Guides||1||4th March 2010 11:17 PM|
|System messed up, should I just reinstall?||AncientDragonfly||FreeBSD Ports and Packages||22||22nd April 2009 04:33 AM|
|Remote FreeBSD server upgrade - Guide!||carpman||Guides||8||5th April 2009 05:37 PM|
|Remote OpenBSD ssh-based install problems||artix||OpenBSD Installation and Upgrading||7||13th March 2009 07:52 PM|
|Remote OpenBSD install via ssh.||Dazhelpwiz||Guides||0||23rd May 2008 12:07 AM|