On 19/01/18 10:45 PM, Michael Hamilton wrote:
Is creating the above unnecessary?
It depends. BtrFS has somewhat of a 'One file system to rule them all' attitude, but then again, many people also created those as subdirectories when they only had a single partition or a simple 'system + /home'. myself, i've always been obsessive to a flaw about having mountable file system. I'm a great beeliver in functional partitioning. As in "Code is code and data is data". Taken to some .... well extremes. oh, i'm rigours about having, for example, ~/bin and ~/lib and /usr/local/bin, /ur/local/lib. But I'm also obsessive about putting all the Apache data and functionality under /srv. I use RubyOnRails and that, too, is pretty good about code/data divisions. So, yes, for me /var is a separate mountable file system. You need all those "parts". What goes in them is, well 'data', but it is 'variable data' such as the databases -- and of course the spool and the logs :-) Whether you let BtrFS implement them as subdivisions -- subvolumes -- of the single volume or implement them as a separate file system is a decision on your part. As they say "YMMV". You really need to make this decision at install time; trying to 'fix it up' afterwards is a !PAIN!. BTDT. -- 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