I'm using a following very simple and clear way instead of mfsBSD:
- Reboot into "rescue mode" (feature provided by any hoster)
- SSH to remote machine rebooted in "rescue mode" and run two commands:
- wget ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64
/ISO-IMAGES/10.2/FreeBSD-10.2-RELEASE-amd64-bootonly.iso
- kvm -curses -m 13000 -hda /dev/sda -hdb /dev/sdb -cdrom
~/FreeBSD-10.2-RELEASE-amd64-bootonly.iso -boot d
That's all lol ). From this moment you just follow standard FreeBSD
installation procedure (I prefer ZfsOnRoot mode).
On 02/25/16 23:30, Terje Elde wrote:
> On 26 Feb 2016, at 06:50, Robert Ayrapetyan
<[email protected]> wrote:
>
> Yeah, finally I've decided to re-install from an official iso.
> I've found some services in crontab I didn't liked at all - they
were submitting a lot of info to a third-party servers (officially for
monitoring purposes).
> p.s. Under "instance" I mean a dedicated unmanaged server.
With a dedicated unmanaged, a reinstall would be my preference as
well. There's an interesting option for this, called mfsBSD. It can be
a bit of hassle to set it up the first time (just a bit), but once
it's up, it'll give you an image that you can simply dd onto the
harddrive(s), and boot from. It then runs only in memory, no longer
dependent on the drives, and allows you to ssh in, and do an install
just like you would from a dvd.
The reason that it can be a slight hassle, is that unless your
provider has DHCP, you'd have to configure IP etc in the image, so
it'd be able to bring up networking correctly.
Other options that can be interesting for setups like this, is using
geli for disk-encryption.
Terje
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "[email protected]"