You are not logged in.
Pages: 1
In a few days I'll get a new workstation pc and am considering what changes to make to my partition setup.
On my current setup there's a data partition mounted as /data that has 2 purposes :
- stuff that needs to be accessible by multiple users (local package repo, chroots)
- stuff that takes up a lot of space
For both tasks write access for specific groups/users is needed.
I'd prefer to have less folders in / and /srv appears to be suitable.
What do you feel is better ?
Last edited by Lone_Wolf (2026-01-09 23:10:34)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
well - given zfs usually does the same for a pool with default options as a zfs user myself i don't see nothin wrong with that
aside maybe storing shared data on a nas and using fast network - but i guess there's a reason for have the storage local to the workstation
Offline
I tend to either put directories in /, or in /home/. e.g. /home/arch/ used to contain everything related to packaging (git repos, chroots).
Offline
The bug is very cumbersome. I will be letting it go :-)
Offline
or in /home
well - iirc there was a topic about using a folder in /home based on group permissions for shared data - it had various pros and cons but i can't remember if this got a "final" answer
Offline
There's nothing special about /home - it's 755 like / or /srv ?
The special aspects would be that it's typically used for /home/$USER as $HOME (so sou're somewhat blocking $USER names) and (probably more relevant) that it's often not the / root partition (and significantly larger)
If you want to allow users to share data with others (and w/o ACLs) I'd go w/ bind-mounts out of their $HOME into some public path - allowing the user full control, restricting everyone else to read-only and the user can refine that via the GID
You'd have /srv typically used for data that's meant to leave the system, but if this is a strictly local host that doesn't run any server services and /srv is just an empty dir, I'd not see any reason not to use that as local server path.
@ReDress, did you reply to the wrong thread?
Offline
I'll definitely use bind mounts and/or ACLs but since https://bbs.archlinux.org/viewtopic.php?id=299394 I've become wary of opening /home/$USER to others.
/home/not-a-user/ though seems reasonable.
Some of the contents are shared with public systems, but contact is always initiated from the workstation.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
not sure if ACL can be used with network block devices https://github.com/NetworkBlockDevice/nbd/ but maybe if its possible then it could be an option.
In that case you can put a big hard drive disk into the work station and make it available as a network block device ? and grant the permissions with ACL for the users ? Not sure if both can work together to be honest but hey, maybe that could make you not spend money in the nas chest ![]()
str( @soyg ) == str( @potplant ) btw!
Offline
not sure if ACL can be used with network block devices https://github.com/NetworkBlockDevice/nbd/ but maybe if its possible then it could be an option.
In that case you can put a big hard drive disk into the work station and make it available as a network block device ? and grant the permissions with ACL for the users ? Not sure if both can work together to be honest but hey, maybe that could make you not spend money in the nas chest
DO Not. Own my threads
Offline
I've been busy converting my install to the new workstation and decided I prefer separation between things, so am keeping /data .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Pages: 1