Re: Corel/Debian Linux Installer
"Christopher W. Curtis" <ccurtis@aet-usa.com> writes:
> Hello all (not on list),
...
> Also, I would like to try to emphasize filesystem layout on the partitions
> so that they can be used most effectively:
>
> / -- small, 32-64MB, mounted readonly, 0% reserve
I have 24 MB used on my Alpha with an usual amount of software
installed. Maybe 32 MB is a bit short, but normaly its enough. 64Mb is
nearly overkill.
> /etc -- small, 16-32MB, mounted read-write, 0% reserve
/etc CAN'T be a seperate partition. /etc/fstab would not be available
to mount /etc.
> /usr -- dependent on packages selected, readonly, 2% reserve
> /var -- dependent on packages selected, read-write, 5% reserve
32 MB for var are normaly fine. squid, mail, printing needs more.
> /opt,/usr/local -- medium, read-write, 2-5% reserve
> I say read-write for /usr/local/var, etc.
> /home -- remainder, read-write, 2% reserve (assume large)
I have 50 MB home, but >1GB /usr/local.
/tmp is pretty important and most people forget to create a partition
for it.
/var/squid, /var/spool should be partitions too, /var/cache as well
and so on indefinitly.
The perfect partition scheme must be fit to the specific situation and
useage. Maybe a tool to resize ext2 partitions would be a good
solution to the problem.
> The key being readonly status being assigned to filesystems where it is
> useful and makes sense, the rest are just eh guidelines that I've used in
> the past and which have worked well. /lib may be a problem with kernel
Nobody I know has / readonly or /usr readonly. Running potato and its
rapid changes makes that undoable, but for a production system I agree
that everything should be readonly if possible. Another usefull
benefit is, that after a crash readonly filesystems are clean.
...
> And on another aside, I think that /usr/share/doc is a good idea; this
> isn't binary data and can safely be exported/remote mounted.
So can a lot of other stuff as well and /usr/doc is good for
historical reasons.
> $0.02, but _please_ pick packages first.
The amount of packages installed only affects /usr to any relevant
extend. /var/squid and /var/spool might be exceptions to that, but
that can't be detected from the package list.
> And then configure while installing in the background, like OpenLinux.
> That is very slick.
We are working on that. :)
May the Source be with you.
Goswin
Reply to: