On 05/15/2015 05:45 PM, Felix Miata wrote:
I guess I could copy the contents of /home to one of my other machines, and completely reinstall everything (as a last resort). I believe the file systems are ext4. Can they be resized (make /home smaller and then make / bigger)?
They can, but it's not a process to be taken lightly. You might not be able to grow / without first creating more freespace.
This is the inherent problem with the fixed provisioning attitude we've had dumped on us, is implicit in the YAST defaults, and goes back to the early days of UNIX when a 10 MEG was considered large. Its archaic and ridiculous in the these days of >50G drives, never mind the 1T drives that are available for under $50. http://www.tigerdirect.ca/applications/SearchTools/item-details.asp?EdpNo=8988939&Sku=WED-102408284 That's $50 CANADIAN! http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=744346&CatId=139 or even http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=9751340&CatId=139 I am at a loss to understand why Yast does not recommend using LVM for drives over a certain threshold. Linux and UNIX before it has a long history of rogue processes consuming /tmp or many examples of rogue programs downloaded into /tmp being used to hack the system. The default in Yast should be, at the very least, to have a separate /tmp which is mounted noexec,nosuid and stickbit. Filling /tmp should NOT mean filling /. Filling /var/spool should NOT mean filling /. Filling /usr/tmp or /var/tmp should not mean filling /. Why oh why are we repeating the mistakes of the last century? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org