2 ms·
How do you handle it when one of your users needs a SQL server? Do they need to install this in their home directory, too? And lock down their install so that h
by chongli 13y ago
How do you handle it when one of your users needs a SQL server? Do they need to install this in their home directory, too? And lock down their install so that hopefully other users on the box can't call it?
NixOS can handle situations like this. It enables per-user package management with deterministic, immutable installs. If multiple users install the same package, it only puts one copy on the system. Each user gets their own environment where they can customize the package without affecting the other users.
- dpark 13y agoHow does that work when you factor in quotas? What if a malicious user installs every possible package? Do they kill the system? How are versions handled? Can N users install N versions of a package? (Looks like the answer is yes.) This sounds like a nice system. I'm just wondering how much of the core issue is really addressed.
- chongli 13y agoFor quotas, you probably want something like ZFS. It allows you to set both quotas and reservations. Reservations are nice in that they guarantee the specified amount of space to the given filesystem. ZFS allows the creation of many nested filesystems with different properties (including block-level compression and encryption) and uses inheritance and overrides to give you a very flexible, fine-grained level of control. ZFS also has real-time, block-level deduplication. This will dramatically cut down on the space usage when users install multiple different versions of the same package. By combining all this, you can give every user their own nix store with its own set of packages and a quota as well as a minimum reservation of space. Deduplication will take care of all the wasted space from multiple users having the same/similar packages installed.