7 ms·

Having had to work on a locked down linux (stupid corporate rules) system for the last couple of months the dedication to user freedom sounds enticing: https://

by flukus 8y ago

Having had to work on a locked down linux (stupid corporate rules) system for the last couple of months the dedication to user freedom sounds enticing: https://www.gnu.org/software/hurd/community/weblogs/ArneBab/technical-advantages-of-the-hurd.html https://www.gnu.org/software/hurd/community/weblogs/ArneBab/... . As a user being able to install packages without root and start my own services and mount network drives without root would make my life a lot easier.

berti 8y ago
Polkit already allows regular users to manage services [1]. Of course that would require the admins responsible for the system to set it up in such a way. [1] https://wiki.archlinux.org/index.php/Polkit#Allow_management_of_individual_systemd_units_by_regular_users https://wiki.archlinux.org/index.php/Polkit#Allow_management...
yjftsjthsd-h 8y ago
> As a user being able to install packages without root and start my own services The future is today:) Nix is a package manager that can run without root. Gentoo prefix installs are an option. Or if you want something more traditional, proot can run a decent number of distros. Maybe also fakeroot? Haven't tried that personally. No idea if there's a FUSE module for NFS/CIFS, though sshfs is a thing.
- pjmlp 8y ago
  There are ways to prevent users to run any kind of executable from $HOME.
  - yjftsjthsd-h 8y ago
    Oh, you have a policy problem rather than a technical problem. In that case, I'm not sure how it would help to have a system where user control was normal, since invariably it would be locked down in exactly the same way. I don't think HURD will prevent mounting /home with noexec.
    - pjmlp 8y ago
      I am not the OP, and by the way, mounting /home with noexec isn't the only way to prevent execution. :)
jcelerier 8y ago
> As a user being able to install packages without root and start my own services and mount network drives without root would make my life a lot easier. ... but that's not a problem of linux, that's a problem of your company rules. They would put similar rules whatever the OS.
- flukus 8y ago
  Locked down was probably not the right word, I'm just a normal user with no root access. It is a linux problem because the admins are trying to do something pretty sensible, not let a single user screw up the machine for everyone and restricting users is how linux achieves this, HURD took a different approach.

by flukus 8y ago

berti 8y ago

Polkit already allows regular users to manage services [1]. Of course that would require the admins responsible for the system to set it up in such a way. [1] https://wiki.archlinux.org/index.php/Polkit#Allow_management_of_individual_systemd_units_by_regular_users https://wiki.archlinux.org/index.php/Polkit#Allow_management...

yjftsjthsd-h 8y ago

> As a user being able to install packages without root and start my own services The future is today:) Nix is a package manager that can run without root. Gentoo prefix installs are an option. Or if you want something more traditional, proot can run a decent number of distros. Maybe also fakeroot? Haven't tried that personally. No idea if there's a FUSE module for NFS/CIFS, though sshfs is a thing.

pjmlp 8y ago
There are ways to prevent users to run any kind of executable from $HOME.
- yjftsjthsd-h 8y ago
  Oh, you have a policy problem rather than a technical problem. In that case, I'm not sure how it would help to have a system where user control was normal, since invariably it would be locked down in exactly the same way. I don't think HURD will prevent mounting /home with noexec.
  - pjmlp 8y ago
    I am not the OP, and by the way, mounting /home with noexec isn't the only way to prevent execution. :)

jcelerier 8y ago

> As a user being able to install packages without root and start my own services and mount network drives without root would make my life a lot easier. ... but that's not a problem of linux, that's a problem of your company rules. They would put similar rules whatever the OS.

flukus 8y ago
Locked down was probably not the right word, I'm just a normal user with no root access. It is a linux problem because the admins are trying to do something pretty sensible, not let a single user screw up the machine for everyone and restricting users is how linux achieves this, HURD took a different approach.