Multiple mountpoints on one partition?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Can I have separate / and /tmp but /home + /var on one partition somehow?
Separate /tmp is good because I can set it up with some quick unreliable filesystem. I often change distributions therefore separate / is a blessing - quick re-install and I'm good as long as /home and /var are untouched.
The problem is, I don't want to designate space for any of the last three - I want them to share available resources. I sometimes need more space in /var and I can see there's available space in /home that I cannot use, sometimes it's the other way around. It's frustrating. Any ideas?
mount partition root home
asked Oct 19 '16 at 11:28
cprn
3391514
add a comment |
up vote
0
down vote
favorite
Can I have separate / and /tmp but /home + /var on one partition somehow?
Separate /tmp is good because I can set it up with some quick unreliable filesystem. I often change distributions therefore separate / is a blessing - quick re-install and I'm good as long as /home and /var are untouched.
The problem is, I don't want to designate space for any of the last three - I want them to share available resources. I sometimes need more space in /var and I can see there's available space in /home that I cannot use, sometimes it's the other way around. It's frustrating. Any ideas?
mount partition root home
asked Oct 19 '16 at 11:28
cprn
3391514
You don't separate/and/usranymore. You can't do reinstalls leaving/usruntouched either (and/varnot completely).
– frostschutz
Oct 19 '16 at 11:37
1
Why? Any sources on that? What is a good practice regarding partitions separation then?
– cprn
Oct 19 '16 at 11:45
1
@Cyprian, freedesktop.org/wiki/Software/systemd/separate-usr-is-broken (it's by the systemd folks but not directly related to it)
– ilkkachu
Oct 19 '16 at 20:55
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Can I have separate / and /tmp but /home + /var on one partition somehow?
Separate /tmp is good because I can set it up with some quick unreliable filesystem. I often change distributions therefore separate / is a blessing - quick re-install and I'm good as long as /home and /var are untouched.
The problem is, I don't want to designate space for any of the last three - I want them to share available resources. I sometimes need more space in /var and I can see there's available space in /home that I cannot use, sometimes it's the other way around. It's frustrating. Any ideas?
mount partition root home
asked Oct 19 '16 at 11:28
cprn
3391514
Can I have separate / and /tmp but /home + /var on one partition somehow?
Separate /tmp is good because I can set it up with some quick unreliable filesystem. I often change distributions therefore separate / is a blessing - quick re-install and I'm good as long as /home and /var are untouched.
The problem is, I don't want to designate space for any of the last three - I want them to share available resources. I sometimes need more space in /var and I can see there's available space in /home that I cannot use, sometimes it's the other way around. It's frustrating. Any ideas?
mount partition root home
mount partition root home
asked Oct 19 '16 at 11:28
cprn
3391514
asked Oct 19 '16 at 11:28
cprn
3391514
edited Dec 4 at 18:05
asked Oct 19 '16 at 11:28
cprn
3391514
asked Oct 19 '16 at 11:28
cprn
3391514
asked Oct 19 '16 at 11:28
cprn
3391514
3391514
You don't separate/and/usranymore. You can't do reinstalls leaving/usruntouched either (and/varnot completely).
– frostschutz
Oct 19 '16 at 11:37
1
Why? Any sources on that? What is a good practice regarding partitions separation then?
– cprn
Oct 19 '16 at 11:45
1
@Cyprian, freedesktop.org/wiki/Software/systemd/separate-usr-is-broken (it's by the systemd folks but not directly related to it)
– ilkkachu
Oct 19 '16 at 20:55
add a comment |
You don't separate/and/usranymore. You can't do reinstalls leaving/usruntouched either (and/varnot completely).
– frostschutz
Oct 19 '16 at 11:37
1
Why? Any sources on that? What is a good practice regarding partitions separation then?
– cprn
Oct 19 '16 at 11:45
1
@Cyprian, freedesktop.org/wiki/Software/systemd/separate-usr-is-broken (it's by the systemd folks but not directly related to it)
– ilkkachu
Oct 19 '16 at 20:55
You don't separate
/ and /usr anymore. You can't do reinstalls leaving /usr untouched either (and /var not completely).– frostschutz
Oct 19 '16 at 11:37
You don't separate
/ and /usr anymore. You can't do reinstalls leaving /usr untouched either (and /var not completely).– frostschutz
Oct 19 '16 at 11:37
1
1
Why? Any sources on that? What is a good practice regarding partitions separation then?
– cprn
Oct 19 '16 at 11:45
Why? Any sources on that? What is a good practice regarding partitions separation then?
– cprn
Oct 19 '16 at 11:45
1
1
@Cyprian, freedesktop.org/wiki/Software/systemd/separate-usr-is-broken (it's by the systemd folks but not directly related to it)
– ilkkachu
Oct 19 '16 at 20:55
@Cyprian, freedesktop.org/wiki/Software/systemd/separate-usr-is-broken (it's by the systemd folks but not directly related to it)
– ilkkachu
Oct 19 '16 at 20:55
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
You can always mount your third partition somewhere (like /mnt/combo or something), and then bind-mount subdirectories from this mountpoint to the three designated directories.
In fstab, this would look something like
UUID=... /mnt/combo auto defaults
/mnt/combo/usr /home none bind
/mnt/combo/var /var none bind
/mnt/combo/home /home none bind
Also consider this: /home makes sense to live on a separate partition - even better, a separate drive, which can be somehow protected (raid, backups,...). /var would make sense to be separate if you really have something personal in there (websites and such), otherwise it makes no difference. /usr can definitely be part of /, it makes no sense to have it separate because on a modern system, the distinction between /bin and /usr/bin is blurred and noone cares about it anymore, and segmenting a system only creates problems if one of the partitions somehow doesn't mount.
/tmp should normally be ram-backed anyway (tmpfs), unless you really are running out of RAM, and most distros do that by default unless you change it.
Big picture: separate /home if you have to, the rest is just overhead - you probably have no reason to have different filesystem types or different permissions on any of these, and partitioning doesn't usually mean physical separation (same hard drive?).
answered Oct 19 '16 at 11:33
orion
9,0731833
How would that work during reinstall? Each time I reinstall it would write to/home,/usr,/varon root partition and afterwards I would manually "replace" mountpoints with/home,/usrand/varfrom my/mnt/combo?
– cprn
Oct 19 '16 at 11:47
Yes, that would work, if that's what you want. But then, what does a reinstall even do? You usually want to keep configuration, so keeping/etc/is more important than the rest, and there isn't much outside/usranyway on a fresh install (/bootand that's it). If you want the install to write to these partitions, you'll simply have to mount this before running installation.
– orion
Oct 19 '16 at 11:50
@CyprianGuerra take a look into kickstart files. They automate tasks during installation. If you're worried about the configuration disappearing between installs a kickstart can help you out.
– Centimane
Oct 19 '16 at 12:22
Okay, I'm marking this as a valid answer because it resolves my question... I have to re-think my idea of reinstall, though, but this is a separate issue. And no, I don't think I want to keep configs because I use reinstall as the last resort when I'm lost trying to fix whatever I broke and need a working system ASAP, default configs, default packages.
– cprn
Oct 19 '16 at 15:56
1
In that case, in my opinion, it's better to wipe clean the /usr too. Because package repositories change. Things get updated. Very likely, old applications wouldn't work with fresh install. I would strongly recommend to just have a list of packages you want... and write a script that would quickly install everything, always the same things - and maybe simulatenously fix the things you want personalized (hostname, network config,...). A simple shell script that does the full system install. Otherwise you'll spend hours debugging when compatibility breaks.
– orion
Oct 19 '16 at 16:04
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f317440%2fmultiple-mountpoints-on-one-partition%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
up vote
2
down vote
accepted
You can always mount your third partition somewhere (like /mnt/combo or something), and then bind-mount subdirectories from this mountpoint to the three designated directories.
In fstab, this would look something like
UUID=... /mnt/combo auto defaults
/mnt/combo/usr /home none bind
/mnt/combo/var /var none bind
/mnt/combo/home /home none bind
Also consider this: /home makes sense to live on a separate partition - even better, a separate drive, which can be somehow protected (raid, backups,...). /var would make sense to be separate if you really have something personal in there (websites and such), otherwise it makes no difference. /usr can definitely be part of /, it makes no sense to have it separate because on a modern system, the distinction between /bin and /usr/bin is blurred and noone cares about it anymore, and segmenting a system only creates problems if one of the partitions somehow doesn't mount.
/tmp should normally be ram-backed anyway (tmpfs), unless you really are running out of RAM, and most distros do that by default unless you change it.
Big picture: separate /home if you have to, the rest is just overhead - you probably have no reason to have different filesystem types or different permissions on any of these, and partitioning doesn't usually mean physical separation (same hard drive?).
answered Oct 19 '16 at 11:33
orion
9,0731833
How would that work during reinstall? Each time I reinstall it would write to/home,/usr,/varon root partition and afterwards I would manually "replace" mountpoints with/home,/usrand/varfrom my/mnt/combo?
– cprn
Oct 19 '16 at 11:47
Yes, that would work, if that's what you want. But then, what does a reinstall even do? You usually want to keep configuration, so keeping/etc/is more important than the rest, and there isn't much outside/usranyway on a fresh install (/bootand that's it). If you want the install to write to these partitions, you'll simply have to mount this before running installation.
– orion
Oct 19 '16 at 11:50
@CyprianGuerra take a look into kickstart files. They automate tasks during installation. If you're worried about the configuration disappearing between installs a kickstart can help you out.
– Centimane
Oct 19 '16 at 12:22
Okay, I'm marking this as a valid answer because it resolves my question... I have to re-think my idea of reinstall, though, but this is a separate issue. And no, I don't think I want to keep configs because I use reinstall as the last resort when I'm lost trying to fix whatever I broke and need a working system ASAP, default configs, default packages.
– cprn
Oct 19 '16 at 15:56
1
In that case, in my opinion, it's better to wipe clean the /usr too. Because package repositories change. Things get updated. Very likely, old applications wouldn't work with fresh install. I would strongly recommend to just have a list of packages you want... and write a script that would quickly install everything, always the same things - and maybe simulatenously fix the things you want personalized (hostname, network config,...). A simple shell script that does the full system install. Otherwise you'll spend hours debugging when compatibility breaks.
– orion
Oct 19 '16 at 16:04
add a comment |
up vote
2
down vote
accepted
You can always mount your third partition somewhere (like /mnt/combo or something), and then bind-mount subdirectories from this mountpoint to the three designated directories.
In fstab, this would look something like
UUID=... /mnt/combo auto defaults
/mnt/combo/usr /home none bind
/mnt/combo/var /var none bind
/mnt/combo/home /home none bind
Also consider this: /home makes sense to live on a separate partition - even better, a separate drive, which can be somehow protected (raid, backups,...). /var would make sense to be separate if you really have something personal in there (websites and such), otherwise it makes no difference. /usr can definitely be part of /, it makes no sense to have it separate because on a modern system, the distinction between /bin and /usr/bin is blurred and noone cares about it anymore, and segmenting a system only creates problems if one of the partitions somehow doesn't mount.
/tmp should normally be ram-backed anyway (tmpfs), unless you really are running out of RAM, and most distros do that by default unless you change it.
Big picture: separate /home if you have to, the rest is just overhead - you probably have no reason to have different filesystem types or different permissions on any of these, and partitioning doesn't usually mean physical separation (same hard drive?).
answered Oct 19 '16 at 11:33
orion
9,0731833
How would that work during reinstall? Each time I reinstall it would write to/home,/usr,/varon root partition and afterwards I would manually "replace" mountpoints with/home,/usrand/varfrom my/mnt/combo?
– cprn
Oct 19 '16 at 11:47
Yes, that would work, if that's what you want. But then, what does a reinstall even do? You usually want to keep configuration, so keeping/etc/is more important than the rest, and there isn't much outside/usranyway on a fresh install (/bootand that's it). If you want the install to write to these partitions, you'll simply have to mount this before running installation.
– orion
Oct 19 '16 at 11:50
@CyprianGuerra take a look into kickstart files. They automate tasks during installation. If you're worried about the configuration disappearing between installs a kickstart can help you out.
– Centimane
Oct 19 '16 at 12:22
Okay, I'm marking this as a valid answer because it resolves my question... I have to re-think my idea of reinstall, though, but this is a separate issue. And no, I don't think I want to keep configs because I use reinstall as the last resort when I'm lost trying to fix whatever I broke and need a working system ASAP, default configs, default packages.
– cprn
Oct 19 '16 at 15:56
1
In that case, in my opinion, it's better to wipe clean the /usr too. Because package repositories change. Things get updated. Very likely, old applications wouldn't work with fresh install. I would strongly recommend to just have a list of packages you want... and write a script that would quickly install everything, always the same things - and maybe simulatenously fix the things you want personalized (hostname, network config,...). A simple shell script that does the full system install. Otherwise you'll spend hours debugging when compatibility breaks.
– orion
Oct 19 '16 at 16:04
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
You can always mount your third partition somewhere (like /mnt/combo or something), and then bind-mount subdirectories from this mountpoint to the three designated directories.
In fstab, this would look something like
UUID=... /mnt/combo auto defaults
/mnt/combo/usr /home none bind
/mnt/combo/var /var none bind
/mnt/combo/home /home none bind
Also consider this: /home makes sense to live on a separate partition - even better, a separate drive, which can be somehow protected (raid, backups,...). /var would make sense to be separate if you really have something personal in there (websites and such), otherwise it makes no difference. /usr can definitely be part of /, it makes no sense to have it separate because on a modern system, the distinction between /bin and /usr/bin is blurred and noone cares about it anymore, and segmenting a system only creates problems if one of the partitions somehow doesn't mount.
/tmp should normally be ram-backed anyway (tmpfs), unless you really are running out of RAM, and most distros do that by default unless you change it.
Big picture: separate /home if you have to, the rest is just overhead - you probably have no reason to have different filesystem types or different permissions on any of these, and partitioning doesn't usually mean physical separation (same hard drive?).
answered Oct 19 '16 at 11:33
orion
9,0731833
You can always mount your third partition somewhere (like /mnt/combo or something), and then bind-mount subdirectories from this mountpoint to the three designated directories.
In fstab, this would look something like
UUID=... /mnt/combo auto defaults
/mnt/combo/usr /home none bind
/mnt/combo/var /var none bind
/mnt/combo/home /home none bind
Also consider this: /home makes sense to live on a separate partition - even better, a separate drive, which can be somehow protected (raid, backups,...). /var would make sense to be separate if you really have something personal in there (websites and such), otherwise it makes no difference. /usr can definitely be part of /, it makes no sense to have it separate because on a modern system, the distinction between /bin and /usr/bin is blurred and noone cares about it anymore, and segmenting a system only creates problems if one of the partitions somehow doesn't mount.
/tmp should normally be ram-backed anyway (tmpfs), unless you really are running out of RAM, and most distros do that by default unless you change it.
Big picture: separate /home if you have to, the rest is just overhead - you probably have no reason to have different filesystem types or different permissions on any of these, and partitioning doesn't usually mean physical separation (same hard drive?).
answered Oct 19 '16 at 11:33
orion
9,0731833
edited Oct 19 '16 at 11:47
answered Oct 19 '16 at 11:33
orion
9,0731833
answered Oct 19 '16 at 11:33
orion
9,0731833
answered Oct 19 '16 at 11:33
orion
9,0731833
9,0731833
How would that work during reinstall? Each time I reinstall it would write to/home,/usr,/varon root partition and afterwards I would manually "replace" mountpoints with/home,/usrand/varfrom my/mnt/combo?
– cprn
Oct 19 '16 at 11:47
Yes, that would work, if that's what you want. But then, what does a reinstall even do? You usually want to keep configuration, so keeping/etc/is more important than the rest, and there isn't much outside/usranyway on a fresh install (/bootand that's it). If you want the install to write to these partitions, you'll simply have to mount this before running installation.
– orion
Oct 19 '16 at 11:50
@CyprianGuerra take a look into kickstart files. They automate tasks during installation. If you're worried about the configuration disappearing between installs a kickstart can help you out.
– Centimane
Oct 19 '16 at 12:22
Okay, I'm marking this as a valid answer because it resolves my question... I have to re-think my idea of reinstall, though, but this is a separate issue. And no, I don't think I want to keep configs because I use reinstall as the last resort when I'm lost trying to fix whatever I broke and need a working system ASAP, default configs, default packages.
– cprn
Oct 19 '16 at 15:56
1
In that case, in my opinion, it's better to wipe clean the /usr too. Because package repositories change. Things get updated. Very likely, old applications wouldn't work with fresh install. I would strongly recommend to just have a list of packages you want... and write a script that would quickly install everything, always the same things - and maybe simulatenously fix the things you want personalized (hostname, network config,...). A simple shell script that does the full system install. Otherwise you'll spend hours debugging when compatibility breaks.
– orion
Oct 19 '16 at 16:04
add a comment |
How would that work during reinstall? Each time I reinstall it would write to/home,/usr,/varon root partition and afterwards I would manually "replace" mountpoints with/home,/usrand/varfrom my/mnt/combo?
– cprn
Oct 19 '16 at 11:47
Yes, that would work, if that's what you want. But then, what does a reinstall even do? You usually want to keep configuration, so keeping/etc/is more important than the rest, and there isn't much outside/usranyway on a fresh install (/bootand that's it). If you want the install to write to these partitions, you'll simply have to mount this before running installation.
– orion
Oct 19 '16 at 11:50
@CyprianGuerra take a look into kickstart files. They automate tasks during installation. If you're worried about the configuration disappearing between installs a kickstart can help you out.
– Centimane
Oct 19 '16 at 12:22
Okay, I'm marking this as a valid answer because it resolves my question... I have to re-think my idea of reinstall, though, but this is a separate issue. And no, I don't think I want to keep configs because I use reinstall as the last resort when I'm lost trying to fix whatever I broke and need a working system ASAP, default configs, default packages.
– cprn
Oct 19 '16 at 15:56
1
In that case, in my opinion, it's better to wipe clean the /usr too. Because package repositories change. Things get updated. Very likely, old applications wouldn't work with fresh install. I would strongly recommend to just have a list of packages you want... and write a script that would quickly install everything, always the same things - and maybe simulatenously fix the things you want personalized (hostname, network config,...). A simple shell script that does the full system install. Otherwise you'll spend hours debugging when compatibility breaks.
– orion
Oct 19 '16 at 16:04
How would that work during reinstall? Each time I reinstall it would write to
/home, /usr, /var on root partition and afterwards I would manually "replace" mountpoints with /home, /usr and /var from my /mnt/combo?– cprn
Oct 19 '16 at 11:47
How would that work during reinstall? Each time I reinstall it would write to
/home, /usr, /var on root partition and afterwards I would manually "replace" mountpoints with /home, /usr and /var from my /mnt/combo?– cprn
Oct 19 '16 at 11:47
Yes, that would work, if that's what you want. But then, what does a reinstall even do? You usually want to keep configuration, so keeping
/etc/ is more important than the rest, and there isn't much outside /usr anyway on a fresh install (/boot and that's it). If you want the install to write to these partitions, you'll simply have to mount this before running installation.– orion
Oct 19 '16 at 11:50
Yes, that would work, if that's what you want. But then, what does a reinstall even do? You usually want to keep configuration, so keeping
/etc/ is more important than the rest, and there isn't much outside /usr anyway on a fresh install (/boot and that's it). If you want the install to write to these partitions, you'll simply have to mount this before running installation.– orion
Oct 19 '16 at 11:50
@CyprianGuerra take a look into kickstart files. They automate tasks during installation. If you're worried about the configuration disappearing between installs a kickstart can help you out.
– Centimane
Oct 19 '16 at 12:22
@CyprianGuerra take a look into kickstart files. They automate tasks during installation. If you're worried about the configuration disappearing between installs a kickstart can help you out.
– Centimane
Oct 19 '16 at 12:22
Okay, I'm marking this as a valid answer because it resolves my question... I have to re-think my idea of reinstall, though, but this is a separate issue. And no, I don't think I want to keep configs because I use reinstall as the last resort when I'm lost trying to fix whatever I broke and need a working system ASAP, default configs, default packages.
– cprn
Oct 19 '16 at 15:56
Okay, I'm marking this as a valid answer because it resolves my question... I have to re-think my idea of reinstall, though, but this is a separate issue. And no, I don't think I want to keep configs because I use reinstall as the last resort when I'm lost trying to fix whatever I broke and need a working system ASAP, default configs, default packages.
– cprn
Oct 19 '16 at 15:56
1
1
In that case, in my opinion, it's better to wipe clean the /usr too. Because package repositories change. Things get updated. Very likely, old applications wouldn't work with fresh install. I would strongly recommend to just have a list of packages you want... and write a script that would quickly install everything, always the same things - and maybe simulatenously fix the things you want personalized (hostname, network config,...). A simple shell script that does the full system install. Otherwise you'll spend hours debugging when compatibility breaks.
– orion
Oct 19 '16 at 16:04
In that case, in my opinion, it's better to wipe clean the /usr too. Because package repositories change. Things get updated. Very likely, old applications wouldn't work with fresh install. I would strongly recommend to just have a list of packages you want... and write a script that would quickly install everything, always the same things - and maybe simulatenously fix the things you want personalized (hostname, network config,...). A simple shell script that does the full system install. Otherwise you'll spend hours debugging when compatibility breaks.
– orion
Oct 19 '16 at 16:04
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f317440%2fmultiple-mountpoints-on-one-partition%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
You don't separate
/and/usranymore. You can't do reinstalls leaving/usruntouched either (and/varnot completely).– frostschutz
Oct 19 '16 at 11:37
1
Why? Any sources on that? What is a good practice regarding partitions separation then?
– cprn
Oct 19 '16 at 11:45
1
@Cyprian, freedesktop.org/wiki/Software/systemd/separate-usr-is-broken (it's by the systemd folks but not directly related to it)
– ilkkachu
Oct 19 '16 at 20:55