From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue,  3 Jan 2012 22:42:19 +0100
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-ID: <20120103214219.GA17347@polynum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
Subject: [9fans] ramfs, fossil, venti etc.
Topicbox-Message-UUID: 53b76aa0-ead7-11e9-9d60-3106f5b1d025

Hello,

Since I will have to fix and redo my Plan9 installation, I'd like to
have some tips about disks layout, in order to prevent another "disk
full" inconvenience.

My date is organized, at least, in three distinct chunks:

1) The data that I use read-only (written by someone else and that can
be retrieved at will). So are the sources for the OSes etc., that I may
backup (on optical disks) from time to time, but for what I don't need
an archival filesystem (no snapshots; no backup)
	=> For this, if I understand: fossil alone, no venti, and setting
	snaptime so that the low epoch is very need to the higher one.

2) Really transient data: /tmp, typically. For that ramfs(4) seems the
right candidate, and fossil will be a waste of space.

3) Data that I do care about, because I'm the writer and I do need the
ability to go back in the archives. So, in this case: fossil+venti.

Do I get the things approximately correct above?

Second question: I know the amount of my data; I guess the amount of
tmp data; what is the amount of space needed for a whole install and the
sources (leaving aside contrib/ packages)?

Thanks for any tip!

PS: not really related. Has someone tried GRUB+etherboot to
install/reinstall Plan9 by network without a PXE able network card?
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C