Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is it a desktop system? If so, I typically do this
Code:
/boot (100MB) -- first linux install only
/swap (512MB)-- both distros can use the same swap partition
/ (10GB) -- distro 1, includes /home partition
/ (10GB) -- distro 2, includes /home and /boot partition
/shared (Large) -- this is where I keep all my common files.
I've never needed a swap file larger than 512MB. My old Celeron 400MHz runs a minimal KDE desktop and still never uses swap, even though it only has 256MB RAM. I guess if you do heavy video editing or the like, you might need a bigger swap. But otherwise, you're probably wasting disk space.
In my limited experience, shareing a /home partition is a nightmare. You can get some weird things happening with config files in /home (like kde config files, etc) because the different distros might use different versions of the same program with slightly different format config files.
I install the first distro grub to the MBR and put the config files on the /boot partition. I install the 2nd distro grub to the / partition and chainload it with the first. This way, if you ever decide to nuke the first distro, the boot files are still there to let you chainload the second.
I've never used LVM's, but read a bit about them. It sounds like they're good for large storage system (like a media partition for MythTV, music, videos, etc) since it makes it easy to grow your filesystem if you need more space. In my reading, my impression is that it can cause a lot of heartache recovering from a problem if the entire install is done on LVM.
So I guess my inclination if you wanted to try LVM would be to install the / and /boot partitions on standard partitions. Then if you wanted a large partition for media (or maybe like the large /shared partition I talked about), it would be okay to use that as LVM.
If the user names are unique, then sharing the /home partition will cause no problem. One potential problem either way you do it is with the common directory for the user between the two distros. You will want to make sure that the UID you use for your username is the same in both distro's. Red Hat and SuSE for example start at different numbers, 500 and 1000 respectively.
Do I want to make the UID the same for all users on both distro's?
Also - one servers - do they seperate the /home directory to another partition? I will be trained on servers when I start my new job which is about a month from now - however I am trying to get a head start.
Also - one servers - do they seperate the /home directory to another partition?
For a SERVER, at WORK, I'd expect lots more seperate partitions than just /home. You will probably run into seperate partitions for:
Code:
/
/boot
/tmp
/usr
/usr/local
/opt
/srv
/home
...just to name a few. It depends on what your server is setup to do, and how many people and/or applications it supports. Many of these filesystems may well be remote, on a SAN, possibly using Veritos instead of LVM. You should expect some form of logical volume management.
Of course, my idea of a server at work may not match your idea of a server...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.