Re: [aclug-L] Newbie on the loose {Dicussion}
[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
On Thu, Aug 20, 1998 at 12:17:51AM -0500, Cory T. Lamb wrote:
> Okay gang I'm not doubting the validity of this scheme I just wonder if
> what I'm doing has any flaws or if there are any benifits to either way.
> On the 4 systems that I have put Linux on, I have used the same scheme:
>
> 1) A /boot partition of 5M
> 2) A swap partition of [size = M of true ram]
> 3) A root partition of [remainder]
> The reasoning behind this is that I figured Linux could better allocate
> the / partition than I could and it doesn't matter how big the / partition
> is [<= 1024 cylinders] because the kernel boots from /boot. I'm just
> wondering if by not setting things up exactly, am I in danger of some sort
> of suprise?
>
> I would be very interested (if it isn't to forward to ask) to see some
> other peoples partition tables and explanations of them.
OK, here's one of mine on a single SCSI disk. It's got the least DASD
(argh, I've been at IBM too long) of all my machines so it has the simplest
setup.
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/sda1 31077 13847 15626 47% /
/dev/sda3 792800 429164 322671 57% /usr
/dev/sda5 101075 23572 72284 25% /var
/dev/sda6 349910 91 331748 0% /opt
/dev/sda7 46632 20 44204 0% /tmp
/dev/sda8 147740 33927 106184 24% /usr/local
/dev/sda9 513147 403456 83186 83% /home
This is a server with about everything you could want on it (compilers,
X apps, etc). I gave it 30MB on root for the hack of it, 20MB is usually
plenty. /usr is it's own filesystem, since according to the Linux Filesystem
Standard we should be able to mount it read only.
/var is it's own partition becuase /var has a tendancy to fill up when
things go wrong. This way, if /var/ fills up, it won't take the system with
it. Mail is currently on /var, but if I put too many more users on the system
/var/spool/mail will become its own partition.
/opt is for installing some special packages like Applixware that I really
don't feel should go in /usr/local. This is a personal preference and
doesn't really make any difference in the way the system works.
/tmp also has a tendance to fill up and it lets me limit the amount of
crap that users put out there.
/usr/local is for stuff that isn't part of the distribution (Debian 2.0).
Anything we compile by hand goes here...
I did a separate /home since I'm too lazy to do quotas and I don't want
my users brining down the system by filling up /.
Remember, this is a server, so it's a bit different than a personal
workstation. I do, however, use the same set up on my workstations,
because it works. Most of partitioning is personal preference and depends
a lot on how you use the system.
Anyway, that's my $0.02.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Invincibility depends on one's self; bkreed@xxxxxxx
The enemy's vulnerability on him. bkreed@xxxxxxxxxxx
--Sun Tzu Bryan Kennedy Reed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---
This is the Air Capitol Linux Users Group discussion list. If you
want to unsubscribe, send the word "unsubscribe" to
aclug-L-request@xxxxxxxxxxxx. If you want to post to the list, send your
message to aclug-L@xxxxxxxxxxxx.
|
|