Can I share my home among multiple operating systems?












1














Is it possible to have on the same hard disk a single home partition (e.g. EXT4), shared by multiple operating systems?



What I would like to do is to install Linux, HURD and DragonFlyBSD on the same system, having a single home.



To solve the problem of conflicting configuration files, could this be a solution:



/home/
user1/
user1_linux/
user1_hurd/
user1_dfbsd/


where user1 is a pseudo-user directory where all the "normal" files are, and the others are the real OS-specific user directories where configuration and OS-specific files go.



Then each OS should have access rights to user1/ and its own dedicated user directory only.










share|improve this question
























  • The only way I can see this being remotely possible is if you had some sort of single sign-on (SSO)
    – Ramhound
    Dec 6 at 19:24






  • 3




    Take a look at this answer from Unix.SE - unix.stackexchange.com/questions/6344/…
    – Michael Frank
    Dec 6 at 19:38










  • @MichaelFrank - Your link provides a good answer to my question. Thank you.
    – Pietro
    Dec 7 at 11:56
















1














Is it possible to have on the same hard disk a single home partition (e.g. EXT4), shared by multiple operating systems?



What I would like to do is to install Linux, HURD and DragonFlyBSD on the same system, having a single home.



To solve the problem of conflicting configuration files, could this be a solution:



/home/
user1/
user1_linux/
user1_hurd/
user1_dfbsd/


where user1 is a pseudo-user directory where all the "normal" files are, and the others are the real OS-specific user directories where configuration and OS-specific files go.



Then each OS should have access rights to user1/ and its own dedicated user directory only.










share|improve this question
























  • The only way I can see this being remotely possible is if you had some sort of single sign-on (SSO)
    – Ramhound
    Dec 6 at 19:24






  • 3




    Take a look at this answer from Unix.SE - unix.stackexchange.com/questions/6344/…
    – Michael Frank
    Dec 6 at 19:38










  • @MichaelFrank - Your link provides a good answer to my question. Thank you.
    – Pietro
    Dec 7 at 11:56














1












1








1







Is it possible to have on the same hard disk a single home partition (e.g. EXT4), shared by multiple operating systems?



What I would like to do is to install Linux, HURD and DragonFlyBSD on the same system, having a single home.



To solve the problem of conflicting configuration files, could this be a solution:



/home/
user1/
user1_linux/
user1_hurd/
user1_dfbsd/


where user1 is a pseudo-user directory where all the "normal" files are, and the others are the real OS-specific user directories where configuration and OS-specific files go.



Then each OS should have access rights to user1/ and its own dedicated user directory only.










share|improve this question















Is it possible to have on the same hard disk a single home partition (e.g. EXT4), shared by multiple operating systems?



What I would like to do is to install Linux, HURD and DragonFlyBSD on the same system, having a single home.



To solve the problem of conflicting configuration files, could this be a solution:



/home/
user1/
user1_linux/
user1_hurd/
user1_dfbsd/


where user1 is a pseudo-user directory where all the "normal" files are, and the others are the real OS-specific user directories where configuration and OS-specific files go.



Then each OS should have access rights to user1/ and its own dedicated user directory only.







linux home-directory bsd hurd






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 7 at 11:50

























asked Dec 6 at 19:06









Pietro

6242922




6242922












  • The only way I can see this being remotely possible is if you had some sort of single sign-on (SSO)
    – Ramhound
    Dec 6 at 19:24






  • 3




    Take a look at this answer from Unix.SE - unix.stackexchange.com/questions/6344/…
    – Michael Frank
    Dec 6 at 19:38










  • @MichaelFrank - Your link provides a good answer to my question. Thank you.
    – Pietro
    Dec 7 at 11:56


















  • The only way I can see this being remotely possible is if you had some sort of single sign-on (SSO)
    – Ramhound
    Dec 6 at 19:24






  • 3




    Take a look at this answer from Unix.SE - unix.stackexchange.com/questions/6344/…
    – Michael Frank
    Dec 6 at 19:38










  • @MichaelFrank - Your link provides a good answer to my question. Thank you.
    – Pietro
    Dec 7 at 11:56
















The only way I can see this being remotely possible is if you had some sort of single sign-on (SSO)
– Ramhound
Dec 6 at 19:24




The only way I can see this being remotely possible is if you had some sort of single sign-on (SSO)
– Ramhound
Dec 6 at 19:24




3




3




Take a look at this answer from Unix.SE - unix.stackexchange.com/questions/6344/…
– Michael Frank
Dec 6 at 19:38




Take a look at this answer from Unix.SE - unix.stackexchange.com/questions/6344/…
– Michael Frank
Dec 6 at 19:38












@MichaelFrank - Your link provides a good answer to my question. Thank you.
– Pietro
Dec 7 at 11:56




@MichaelFrank - Your link provides a good answer to my question. Thank you.
– Pietro
Dec 7 at 11:56










1 Answer
1






active

oldest

votes


















3














This is certainly possible, by putting /home on a separate partition and mounting it in each of the operating systems. However, this is virtually guaranteed to lead to big problems.



I would like to propose an alternative solution which has served me well for eight years now: a version controlled repository of a minimal set of utilities and configuration files which I can be sufficiently sure will not break when used on different platforms and even slightly different versions of applications:





  • Configuration for lots of applications.


  • .gitignore files listing the files and directories which are either pointless to version control (such as logs), contain secrets (such as license files), or are just too hard to properly version control (such as those mixing runtime stuff like window size into a configuration file in a single line of JSON/XML).

  • doc/ files to remind myself of things I rarely need which are not configuration.

  • examples/ of code.

  • patches/ to the base system to work with set -o errexit in the .bashrc. This was an experiment to ensure that my .bashrc was sane by exiting from it early in case of any issues whatsoever. It is feasible to do so, but third party code broke some things.

  • shell-includes/ is used only for scripts/arch_linux_system_upgrade.sh, which is how I prefer to update Arch Linux.

  • make-includes/ adds some utility targets to the Makefile

  • The Makefile can be used to


    • Clean up configuration for easier version control.

    • Run some minor tests on the repository contents.

    • Create symlinks to the dotfiles in my home directory to avoid having to copy back and forth.

    • Start user services pulseaudio and redshift.








share|improve this answer























  • How does the config repository work?
    – Xen2050
    Dec 7 at 9:30










  • The readme only says how to install & test. But just the basic steps of what it does would suffice, like a how-to outline of how someone could make their own scripts. (Without more info your answer's basically a link-only answer too)
    – Xen2050
    Dec 7 at 10:52











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1381447%2fcan-i-share-my-home-among-multiple-operating-systems%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














This is certainly possible, by putting /home on a separate partition and mounting it in each of the operating systems. However, this is virtually guaranteed to lead to big problems.



I would like to propose an alternative solution which has served me well for eight years now: a version controlled repository of a minimal set of utilities and configuration files which I can be sufficiently sure will not break when used on different platforms and even slightly different versions of applications:





  • Configuration for lots of applications.


  • .gitignore files listing the files and directories which are either pointless to version control (such as logs), contain secrets (such as license files), or are just too hard to properly version control (such as those mixing runtime stuff like window size into a configuration file in a single line of JSON/XML).

  • doc/ files to remind myself of things I rarely need which are not configuration.

  • examples/ of code.

  • patches/ to the base system to work with set -o errexit in the .bashrc. This was an experiment to ensure that my .bashrc was sane by exiting from it early in case of any issues whatsoever. It is feasible to do so, but third party code broke some things.

  • shell-includes/ is used only for scripts/arch_linux_system_upgrade.sh, which is how I prefer to update Arch Linux.

  • make-includes/ adds some utility targets to the Makefile

  • The Makefile can be used to


    • Clean up configuration for easier version control.

    • Run some minor tests on the repository contents.

    • Create symlinks to the dotfiles in my home directory to avoid having to copy back and forth.

    • Start user services pulseaudio and redshift.








share|improve this answer























  • How does the config repository work?
    – Xen2050
    Dec 7 at 9:30










  • The readme only says how to install & test. But just the basic steps of what it does would suffice, like a how-to outline of how someone could make their own scripts. (Without more info your answer's basically a link-only answer too)
    – Xen2050
    Dec 7 at 10:52
















3














This is certainly possible, by putting /home on a separate partition and mounting it in each of the operating systems. However, this is virtually guaranteed to lead to big problems.



I would like to propose an alternative solution which has served me well for eight years now: a version controlled repository of a minimal set of utilities and configuration files which I can be sufficiently sure will not break when used on different platforms and even slightly different versions of applications:





  • Configuration for lots of applications.


  • .gitignore files listing the files and directories which are either pointless to version control (such as logs), contain secrets (such as license files), or are just too hard to properly version control (such as those mixing runtime stuff like window size into a configuration file in a single line of JSON/XML).

  • doc/ files to remind myself of things I rarely need which are not configuration.

  • examples/ of code.

  • patches/ to the base system to work with set -o errexit in the .bashrc. This was an experiment to ensure that my .bashrc was sane by exiting from it early in case of any issues whatsoever. It is feasible to do so, but third party code broke some things.

  • shell-includes/ is used only for scripts/arch_linux_system_upgrade.sh, which is how I prefer to update Arch Linux.

  • make-includes/ adds some utility targets to the Makefile

  • The Makefile can be used to


    • Clean up configuration for easier version control.

    • Run some minor tests on the repository contents.

    • Create symlinks to the dotfiles in my home directory to avoid having to copy back and forth.

    • Start user services pulseaudio and redshift.








share|improve this answer























  • How does the config repository work?
    – Xen2050
    Dec 7 at 9:30










  • The readme only says how to install & test. But just the basic steps of what it does would suffice, like a how-to outline of how someone could make their own scripts. (Without more info your answer's basically a link-only answer too)
    – Xen2050
    Dec 7 at 10:52














3












3








3






This is certainly possible, by putting /home on a separate partition and mounting it in each of the operating systems. However, this is virtually guaranteed to lead to big problems.



I would like to propose an alternative solution which has served me well for eight years now: a version controlled repository of a minimal set of utilities and configuration files which I can be sufficiently sure will not break when used on different platforms and even slightly different versions of applications:





  • Configuration for lots of applications.


  • .gitignore files listing the files and directories which are either pointless to version control (such as logs), contain secrets (such as license files), or are just too hard to properly version control (such as those mixing runtime stuff like window size into a configuration file in a single line of JSON/XML).

  • doc/ files to remind myself of things I rarely need which are not configuration.

  • examples/ of code.

  • patches/ to the base system to work with set -o errexit in the .bashrc. This was an experiment to ensure that my .bashrc was sane by exiting from it early in case of any issues whatsoever. It is feasible to do so, but third party code broke some things.

  • shell-includes/ is used only for scripts/arch_linux_system_upgrade.sh, which is how I prefer to update Arch Linux.

  • make-includes/ adds some utility targets to the Makefile

  • The Makefile can be used to


    • Clean up configuration for easier version control.

    • Run some minor tests on the repository contents.

    • Create symlinks to the dotfiles in my home directory to avoid having to copy back and forth.

    • Start user services pulseaudio and redshift.








share|improve this answer














This is certainly possible, by putting /home on a separate partition and mounting it in each of the operating systems. However, this is virtually guaranteed to lead to big problems.



I would like to propose an alternative solution which has served me well for eight years now: a version controlled repository of a minimal set of utilities and configuration files which I can be sufficiently sure will not break when used on different platforms and even slightly different versions of applications:





  • Configuration for lots of applications.


  • .gitignore files listing the files and directories which are either pointless to version control (such as logs), contain secrets (such as license files), or are just too hard to properly version control (such as those mixing runtime stuff like window size into a configuration file in a single line of JSON/XML).

  • doc/ files to remind myself of things I rarely need which are not configuration.

  • examples/ of code.

  • patches/ to the base system to work with set -o errexit in the .bashrc. This was an experiment to ensure that my .bashrc was sane by exiting from it early in case of any issues whatsoever. It is feasible to do so, but third party code broke some things.

  • shell-includes/ is used only for scripts/arch_linux_system_upgrade.sh, which is how I prefer to update Arch Linux.

  • make-includes/ adds some utility targets to the Makefile

  • The Makefile can be used to


    • Clean up configuration for easier version control.

    • Run some minor tests on the repository contents.

    • Create symlinks to the dotfiles in my home directory to avoid having to copy back and forth.

    • Start user services pulseaudio and redshift.









share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 7 at 20:24

























answered Dec 6 at 21:57









l0b0

5,44122341




5,44122341












  • How does the config repository work?
    – Xen2050
    Dec 7 at 9:30










  • The readme only says how to install & test. But just the basic steps of what it does would suffice, like a how-to outline of how someone could make their own scripts. (Without more info your answer's basically a link-only answer too)
    – Xen2050
    Dec 7 at 10:52


















  • How does the config repository work?
    – Xen2050
    Dec 7 at 9:30










  • The readme only says how to install & test. But just the basic steps of what it does would suffice, like a how-to outline of how someone could make their own scripts. (Without more info your answer's basically a link-only answer too)
    – Xen2050
    Dec 7 at 10:52
















How does the config repository work?
– Xen2050
Dec 7 at 9:30




How does the config repository work?
– Xen2050
Dec 7 at 9:30












The readme only says how to install & test. But just the basic steps of what it does would suffice, like a how-to outline of how someone could make their own scripts. (Without more info your answer's basically a link-only answer too)
– Xen2050
Dec 7 at 10:52




The readme only says how to install & test. But just the basic steps of what it does would suffice, like a how-to outline of how someone could make their own scripts. (Without more info your answer's basically a link-only answer too)
– Xen2050
Dec 7 at 10:52


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1381447%2fcan-i-share-my-home-among-multiple-operating-systems%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Plaza Victoria

Brian Clough

Cáceres