> From: Tom Browder [mailto:tom.brow...@gmail.com] > > I provide a Linux VM with two virtual drives to a client. One drive > is a boot disk and the other drive contains a single partition mounted > as /usr/local. That's where the client should keep his work.
Since you may be upgrading or replacing the OS in the future, I would advise against using a standard well known path such as /usr/local, where you likely have OS-dependent apps. I would advise instead, using something like /data where you can safely assume you pass the /data partition from system to system, you will not end up conflicting with anything OS-dependent. I think you'll do well to avoid using any partitions at all. You might "pvcreate" the raw device, and vgcreate, and lvcreate, and vgscan. This will give you flexibility in terms of expanding, and some stuff like that ... But you don't gain much that way, as you could alternatively, mkfs.ext4 directly the raw device (no partitions.) If you later expand the device, you can resize2fs and it works very well. So LVM only gives you a marginal little bit of extra flexiblity. ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
