Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I would also like to add that adding a lot of swap doesn't actually do much of anything. Staring at top when doing some serious memory or disk IO stuff (such as yum) doesn't actually use a lot. Unix/linux doesn't like swap, it's slow and unpreferred so it just doesn't use it much if ever. Almost everything is in your main memory. Also locking down /usr and even worse /etc is a decent idea if you are worried about security as it makes it almost imposable to actually do anything. Having a /home as a different partition is useful if you have a lot of users on the box, if you need to reinstall nothing in /home is lost. On web servers /var is almost always partitioned just for speed since that is where a lot of access is. These are of course IMHO. ~Ben On Thu, Mar 13, 2008 at 2:00 PM, Anthony Chaves <[hidden email]> wrote: > Hi Stephen, > > Have you considered using LVM on top of your RAID array? LVM allows you > to > allocate a portion of your space up front for what you're going to use now > and it gives you the option to add more space to a partition as it is > needed. This gives you the flexibility to adapt to your users as the > server > is used rather than making potentially bad guesses up front. > > Anthony > > On Thu, Mar 13, 2008 at 10:36 AM, Michael Tiernan < > [hidden email]> > wrote: > > > On Thu, Mar 13, 2008 at 9:45 AM, stephen goldman <[hidden email]> > wrote: > > > Looking for insight and best practices on the partitioning scheme. > > What your server is going to be used for usually helps establish this. > > > > Simple approach? Make all the disks RAID 5 and use the default install. > > > > Some questions to consider, who's going to be on the system? Just the > > admins or 'users' who are going ot be sucking up disk space? > > > > > ( I am aware of the best practice of assigning 1.5 the space the > > > physical memory) > > I'll tell you now that this is one of those things right up there with > > "what's the best editor". > > > > There's a bazillion 'rules' for how to do this. Find one you like and > > live with it. :) > > > > When I build a server that may get a memory hog in it, I use more than > > that. My baseline is usually 3 x Physical memory. Just 'cause it's > > easer to waste some then to try and add some later. > > -- > > << MCT >> Michael C Tiernan. > > Is God a performance artist? > > EGO hack vivo quod ago accido. > > http://www.linkedin.com/in/mtiernan > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > > > _______________________________________________ > > Discuss mailing list > > [hidden email] > > http://lists.blu.org/mailman/listinfo/discuss > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > Discuss mailing list > [hidden email] > http://lists.blu.org/mailman/listinfo/discuss >
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |