On 31 Jan 2002 at 10:46, Bob George wrote: <SNIP> >There are a lot of schools on partitioning, and some folks probably get >pretty excited about the subject. There is debate about how big exactly >various partitions should be. But first, let's keep in mind WHY you want to >partition.
I must say, I agree with pretty much everything that was said here about partitioning. >Typically, you want AT LEAST two partitions. One for swap space, and another >for the Linux filesystem. > >SWAP: The recommendation I've seen (and use) for size of the swap space is 2 >X RAM. Apparently, any less really doesn't gain you anything. Up to 1 X RAM >size, and Linux is just mirroring physical memory. This is something that >has been optimized, fixed but has apparently become an issue in the latest >kernels again. If anyone cares, I can try to find some references for this, >but I think 2 X RAM size is a good general recommendation. Maybe more if >your system is tight on RAM. Keep in mind, if memory and swap fill, you >won't get much done, so better to err for more here. In our LUG, some guys >routinely throw a half-gig at swap for heavy production systems with the >thought that running out is NOT a good thing. Too little is a bad thing, too >much is wasteful. > >LINUX FILESYSTEM: You COULD put everything else on one large Linux (ext2) >partition. If you have a lot of space on a drive and just want to keep >things simple, this works fine. The problem is when you fill up various >parts of the filesystem, odd and unwonderful things begin happening. Filling >up root (/), in particular, is a bad idea. So a common recommendation is to >split various parts of the filesystem that are prone to filling up into >separate areas (partitions) so they don't step on each other. The guidelines >I've used are for each of the following to be split off: > >1. swap - HAS to be separate > >2. / (root) - Should be large enough to accomodate some growth, but not >overly huge. Linux isn't that big. > >3. /var - Lots of things like printing and mail spool files and log files go >here. 500MB if I've got lots of disk space, but 250MB generally seems to be >PLENTY, especially if you make sure log files don't grow out of control. > >4. /tmp - Temporary file space, used by various programs. 200MB is usually >plenty. Again, I give it 500 if I'm on a huge drive. > >5. /home - User home directories. This is where user files get stored. By >default, if you're using Samba to store user files on the server, this is >where a user's "My Documents" will get pointed (assuming you've set it all >up that way). In my case, that's where the vast majority of disk space gets >used. This is also the "most important" stuff, so I want it backed up and >protected. Consider allocating most or all of your SCSI RAID space for >/home. > >6. /usr - "Non-core" system and program files. If you're going to be putting >a lot of stuff (X etc.) on, /usr might get fairly large. Balance between >/usr and /home based on how much you'll work at the actual Linux console >versus from Windows machines accessing it. <SNIP> >> Sooo, here I am today. I no longer need internet sharing or ipchains >> (unless linux can do it better than a linksys router and Zone alarm >running >> on all the clients.) "Better" is indeed one of those words that tends to provoke wars. Or at least flames. :-) At the most basic level, a Linux box and the Linksys router probably will come out about the same. One reason that so many people are deploying Linux boxes as firewalls is because: A: They've got an old PC laying around, that no-one can use on their desktop - i.e. free hardware B: They've been wanting to play around with Linux anyway, to see what all the hype's about. That said, there are some nifty things that you can do with Linux that you just can't do with the Linksys box. On the other hand, most people don't have to do those tasks. <SNIP> >> The best hardware I could scrounge up for the task is below: >> >> Agenda full tower case 300 watt power supply >> >> AIR 586EP Motherboard with onboard SCSI (Adaptec 7870P) > >Do a bit of research and make sure that the SCSI controller is well >supported. (More on SCSI below). > >> 2 PCI slots and 5 EISA >> AMI Bios Date 12/15/93 >> >> The processor is a Pentium running at 66 mhz >> >> 32 meg ram > >That all sounds quite promising! > >> Diamond Speedstar 64 PCI (Cirrus Logic Chip CI-GD5434-HC-C) (This is not t >he >> same Diamond I had problems with, I put that in a windoz box.) > >Again, do a bit of research before embarking. I've got an old Diamond >Speedstar and it works fine, but I don't do X with it. I wouldn't expect any >problems, but do check. > >> I have 2 nics in the box from the last go round, but I believe I only need >> one now. Let me know If I should remove one nic to simplify things. The 2 >> nics are: >> >> 3com Fast Etherlink XL PCI 3C905-T4 >> Linksys Ether16 Lan Card ISA > >One will suffice for now, and adding another later is no big deal. Keep the >3Com in for performance reasons. That card is well supported. > >> I have 3 full height SCSI drives. After I finish off a little more sheet >> metal work and add another fan, they will all reside in the full tower. Looks like a good set of hardware. I've had good experience with 3Com's 3C905s in our Linux boxes. <SNIP> >> I am currently in need of a loooong 50 pin SCSI ribbon cable w/ about 5-6 >> drops. Anyone have one they want to get rid of? > >I have one, but I'm keeping it! You might try Dalco or someplace similar. I use Computer Gate for most of my cable purchases. Cheapest place I've ever found cables, especially on the really expensive ones. http://www.computergate.com You'll want Part#:CFHS4 - seven internal 50-pin SCSI connectors, allowing you to plug in up to six devices. $3.95 ObSurvPC: Computer Gate also stocks MFM/RLL drive cable sets. Know anyone else that does? *grin* Part#:CFHDDA(AT) >> I think I have answered all the questions. Anything else? > <SNIP all the distribution stuff> I must agree with all that was said about the various distributions. For a beginner, one is pretty much the same as the others. I've had good success with Slackware and Red Hat, myself. Your mileage may vary. >> As for that C64, It is still up in my attic, in it's original box, in >> perfect condition, with a few other hardware goodies and many shoeboxes of >> software. One day when I have a ton of free time (like when I am retired >> ;-) I will drag it our and fool around. > >Did you check out Or's links to a web server running on a C-64? It's >connected via a serial SLIP link to a Linux box. THERE's a project for ya! >:) > >- Bob The C64 is one of the afore-mentioned projects where the Linksys box just won't cut it. From what I understand, the Linux box at that site is acting as a router, routing packets from the Ethernet interface to the RS-232 serial interface and vice versa. Interesting project, and one I'm considering to get my TRS-80 on line. Anthony J. Albert =========================================================== Anthony J. Albert [EMAIL PROTECTED] Systems and Software Support Specialist Postmaster Computer Services - University of Maine, Presque Isle "Ta'Lon, is that you?" "It's me most days, except for those days when I don't feel quite like myself and I suppose that I am someone else, but for now, yes, it is me." -G'Kar and Ta'Lon, Babylon 5 episode: _The_Ragged_Edge_ To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with unsubscribe SURVPC in the body of the message. Also, trim this footer from any quoted replies. More info can be found at; http://www.softcon.com/archives/SURVPC.html
