IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Partition layout query:
Ok, here's the setup:

96mb RAM
8gb hard drive

System will be used for database development, software development, light web browsing, and as a firewall/gateway for my Win2k machine. I'll also be running Seti@home on it.

The personal data partition isn't all that important - I'll end up mounting it using samba from my Win2k machine when I get that figured out. What partitions would you make and how would you break them down? Debian 2.2r3, and I need a swap partition as well.
New Fairly simple.
I'd do /boot, swap, then /. It might be a good idea to give /var its own partition, but you'd need to guess about how full / would get to do that effectively.

Wade

"All around me are nothing but fakes
Come with me on the biggest fake of all!"

New How I usually do my dev workstations:
32M /boot
2*RAM for sawp
~30M /boot
250-500M /
250 /tmp
250-500 /var
enough on /home for email, etc.
The rest on /usr

Then, I chown /usr/local to my main user and use that for installing dev software (/usr/local/dev), apps (/usr/local/apps), downloading things (/usr/local/dnl), and source code (/usr/local/src).

Of course, Karsten will now tell you that my laptop has everything in one partition in complete contradiction to the above advice. :-)
Regards,

-scott anderson
New I like a separate /usr/local part to throw everything into
outside the OS so a reload of the OS will not affect my stuffs.
thanx,
bill
can I have my ones and zeros back?
New What I ended up doing:
One honkin' big partition for /, one 192mb partition for swap.

Anything else, and I started getting massive FSCK errors all over the place.
New So long as it boots, that should be fine.

"All around me are nothing but fakes
Come with me on the biggest fake of all!"

New Might that be a dud drive?
With everything in a large partition it may not have yet reached parts that it was forced to use with multiple partitions. At least, I've never run into any partitioning related fsck problems on a variety of hardware/partitioning/fs combinations.

New Nope.
I did a whole fsck of the disk, no problems.
New I do it different for servers and desktop
For a server I have swap / and /u. /u is where all applications are loaded and where all data is kept. Anything anywhere else that must survive is copied to /u for safekeeping. This way, I can wipe the whole OS and install a later version, or I can format and reinstall after an awful crash or admin error without affecting my data at all or my applications.

For desktops, most applications like to keep user files and configuration stuff in /home/username/*, so I partition swap / and /home.
[link|www.aaxnet.com|AAx]
New /home is almost always a good idea.
It took me quite a while to realize that /home should be as large as possible because in each home directory there are almost no rules! I'd been trying to put stuff in /usr and /usr/src since they belonged to the system. Well, I'd been trying to convince myself of that... Then I realized that I was trying to keep /home/wwb clean for no good reason. Just a few directories are all it takes and it's easy to put in there just about everything I want to play with.

My server has a 30Gb drive just for /home. Everything else is on a separate 4Gb drive.

Wade.

"All around me are nothing but fakes
Come with me on the biggest fake of all!"

     Partition layout query: - (inthane-chan) - (9)
         Fairly simple. - (static)
         How I usually do my dev workstations: - (admin) - (1)
             I like a separate /usr/local part to throw everything into - (boxley)
         What I ended up doing: - (inthane-chan) - (3)
             So long as it boots, that should be fine. -NT - (static)
             Might that be a dud drive? - (scoenye) - (1)
                 Nope. - (inthane-chan)
         I do it different for servers and desktop - (Andrew Grygus) - (1)
             /home is almost always a good idea. - (static)

I have, if not a full ink, at least an inkling.
78 ms