Shawn,
I absolutly agree with you ( except making /tmp 200megs ;) ) You need some
experience to know what size you should make the partitions and the best
way to get this experiance is to have a working system where you do your
day to day work and after a while you will notice that it doesn't make
sense to make a 500meg /home partition because after all you weren't as
productive as you though you would be. In this way I totally agree wtih
you, that a new user how is learning what Linux is and what linux can do
for him should probably start off with a / + swap system, but If you have
a realistic idea of how large different filesystems should be for you, I
think one should distribute filesystems on different partitions.
But maybe this item is getting too philosophic.
greetings,
Clemens
On Wed, 10 Jun 1998, Shawn McMahon wrote:
> But again, we're talking about recommendations to a new user. I think that
> if some guy is popping in here and says he's installing his first Linux
> system, and he's never administrated Unix before and has no clue how to
> partition things, he probably doesn't have any users at all. If he does,
> it's probably a couple of his buddies.
>
> Yes, there are valid reasons in some installations to have /tmp, /var, or
> even a lower level of directory be moved to a different partition.
>
> But with some new guy running Linux at home, we're more likely to seem him
> show up in the list 6 weeks later wanting to know how to make /foo larger
> and /bar smaller, because /foo is out of space and /bar has 1 gig free
> because he followed somebody's advice to create half a dozen partitions, and
> he simply didn't have the experience to know he was going to be putting a
> lot more stuff on /foo than on /bar.
>
> /tmp is a good example; in the BSD world we see folks posting constantly
> wondering why they can't send or receive a large email, and it's usually
> because /tmp is too small.
>
> So you have to repartition half your system just to make /tmp larger, when
> for a single user system it's probably just vastly better to have as few
> partitions as possible.
>
> Yes, somebody can crash you by filling /tmp if it's on /, but if the only
> other person logging on the machine is your spouse and your cousin Bob, who
> cares? It's more important that you have enough space on /tmp to get the
> job done.
>
> Some of these recommendations I'm seeing are calling for multi-gigabyte
> /home partitions. What the heck does an average newbie user need with all
> that wasted space? He's never gonna use it, everything he installs is going
> to be in /usr/local or somewhere similar, and that's gonna fill up quick as
> he experiments with various stuff.
>
> If you're paranoid and you're setting up a system that will have lusers
> logging into it, by all means isolate partitions. By all means put / on
> it's own partition, so you can mount /usr in read-only mode and fsck without
> a floppy. By all means make a 200mb /tmp partition. By all means put /home
> somewhere else so people can't crash you by farting around with the output
> of /dev/urandom.
>
> But if you're setting up a system that nobody's going to be logging into
> except administrators, such as a personal home system or a router, what do
> you need with all that junk? It just guarantees you'll have unusable wasted
> partition space.
>
> Even if you're building a Samba server, if you're keeping well ahead of your
> users you'll have plenty of warning before you fill up and crash. If you're
> worried about it, dust off your Perl manuals and build something that makes
> liberal use of system(df) and email, loud noises, pagers, etc.
>
>
>
>
> --
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
> To unsubscribe: mail [EMAIL PROTECTED] with
> "unsubscribe" as the Subject.
>
>
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.