Thanks for the clarification. I should have been more clear: when /var is on a separate partition, the server won't boot -- period. I suppose maybe I didn't wait long enough, but I don't think so -- it just hangs.
I think this issue is worthy of some discussion, as perhaps thanks to the LSB, /var has become a catch all for everything from system runtime PID information to user mail folders and an organization's entire web space, which can, in some cases, be quite large. In this instance, we're currently talking about adding 500GB+ of publicly accessible electronic material each for every year into the foreseeable future. A couple of thoughts: This particular server has, over the last 8 years had an average up time of 200+ days. In particular, I don't much care if it boots in 10 seconds or 30 seconds. I more concerned about being able to flexibly allocate space (yes, I know I should be using LVM). Maybe it would be possible to exchange fast boot time for the partitioning flexibility that used to exist as an administrator's choice? Second, maybe some thought should be given to separating "user space" /var data from "system" /var data, since the former might require special storage, expandability, backup, redundancy requirements that don't apply to, say, the stuff in /var/run, /var/lib, or /var/log. I guess the current interim solution is to cd /var mv /var/www /data1; mv /var/Maildir /data1; ln -s /data1/var/www . ln -s /data1/var/Maildir . Maybe this is good enough. The point of the bug report was to establish that indeed the system won't boot unless /var is in /, which is a divergence from previous UNIX systems behavior. As long as this is known and documented, people can work around it. -- /var can no longer live on its own partition? https://bugs.launchpad.net/bugs/526622 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
