On Wednesday 23 September 2009 01:52 pm, Paul Saenz wrote: > Mostly you don't have to worry about the disk filling up if by some > process going wild in desktops, but it is a common practice to make > separate partitions for servers to protect from this problem. This > problem may be more a thing of the past, since hard drives are so big > now, and usually if a process goes wild the system monitor program > will detect it before it fills up, as long a someone is monitoring > the system monitor.
I haven't added to this thread previously because most of my linux experience is with servers in our datacenter. While I do use linux on the desktop, I'm hardly an expert and always use the default partition scheme on desktop and laptop systems. (I've never trust the separate /home partition to save data; I always do a full /home backup and then reinstall from scratch before reloading /home.) For servers we still think partitions are important, even on our current 1TB systems. We haven't had a separate /boot partition in a while; we never automatically restart with an updated Kernel, so I believe we're safe against having systems that won't reboot because a full /boot makes it impossible to install all the needed Kernel files during an update. However, your point makes sense and I'll seriously consider it for the future. In my opinion logs should always be in a separate partition; they can proliferate quickly under many scenarios. And for us, with public shared webservers, the more important reason to put /tmp on it's own partition is so we can mount it more restrictively than we do other partitions, to avoid some of the script-kiddie stuff out there. Jeff -- Jeff Lasman, Nobaloney Internet Services P.O. Box 52200, Riverside, CA 92517 Our jplists address used on lists is for list email only voice: +1 951 643-5345, or see: "http://www.nobaloney.net/contactus.html"; _______________________________________________ LinuxUsers mailing list [email protected] http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
