This might be a bit long but I wanted to share my method. When downloading you can put *.rpm's anywhere. The install process puts the active files in the correct places, NOT in the current directory. No so when you compile and make. Then it often spreads under the current directory.
After much experimentation and evolution and partitioning over the years I use the following strategy: I create an extra partition called /space or /extra or /homex or /stuff using the rest of the HDD space after the installation or a full separate drive. It usually amounts to several Gigabytes. I have a few things I typically put out there. (1) a backup area for daily/weekly compressions of the /home area, configurations, or mini-backups of other machines across the network. (2) an area called /rawsoft for raw software. Sometimes I have the distro CD's in there and that's where I put all the software I download. /rawsoft is often subdivided as follows: /rawsoft /rawsoft/apps /rawsoft/drivers /rawsoft/os (operating systems) /rawsoft/apps may have subdirectories for each utility or package I download borrow or otherwise acquire and along with the *.rpm I'll put text and html files that have to do with installation or other documentation /rawsoft/drivers has subdirectories for each device or subdivisions for version numbers, etc. /rawsoft/os is for operating systems and distros. I'll often have the i386 for win98 or NT-4 there for access if I need it. I used to have separate partitions for backups and software but it's better use of space if I combine them because one may only have megabytes with gigs of empty space depending on how I use the machine (learned that over time). An alternate temp area, out on /extra (separate filesystem), can be useful and can sometimes enhance security. "J.D. Abolins" wrote: > On Fri, 11 Jan 2002, Wayne wrote: > > > John, your proposed newbie questions aren't so trivial. I've had my hands > <snipped> > > Oops. Now I don't feel so bad being perplexed by some of these things. <g> > > One item that should be relatively simple that I had to deal with > initially was "Where do I put files that I am downloading or installing?" > > This would a be good time to go over the basics of /etc, /bin, /usr, /var, > /tmp, /home, /opt, ... normative uses. Especially good for those coming in > from Windows where they are used to C:\Program Files\ and C:\My > Documents\. In one of the older Linux magazines, there was good summary of > the dirs and their Windows "equivalents". > > > Password recovery is the only easy thing you mentioned. (what's that say for > > security?) :) > > Depends how you secure the machine. Unshadowed passwords can allow you to > do a crack program against /etc/passwd but you have to get the file first. > The method I was think of for the newbies is the simple method of booting > up as a single user and resetting the pw. > > The key security warning with this is: If a person can have uninterrupted > physical access to the machine, security is very difficult. Applies to any > platform or OS. There have been so many firms that go to a fairly decent > lenght to use security software on their servers but had the server > sitting in an open area or an unlocked room. > > J.D. Abolins > Meyda Online -- Infosec & Privacy Studies > New Website: http://www.MeydaOnline.com
