diff options
Diffstat (limited to 'community')
| -rw-r--r-- | community/weblogs/ArneBab/niches_for_the_hurd.mdwn | 28 |
1 files changed, 22 insertions, 6 deletions
diff --git a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn index ecfcc4c8..8b6c4226 100644 --- a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn +++ b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn @@ -139,11 +139,20 @@ aren't possible. * hello world. * transparently bind FTP into the filesystem * hostmux + ftpfs -> connect to FTP automatically via asking for a dir named after the hostname -> fully transparent FTP filesystem: "touch ftp: ; settrans ftp: /hurd/hostmux /hurd/ftpfs / " - * bind any filesystem at any place in the filesystem (you have access to) without needing to be root. + * bind any filesystem at any place in the directory tree (you have access to) without needing to be root. * elegantly mount iso images and similar as unprivileged user. - Other useful stuff: * Install deb-packages from an ftp server via 'dpkg -iO ftp://foo/bar/*.deb' + * remount a filesystem readonly as regular user: fsysopts /foo -r + * give a process additional group and user permissions at runtime: + $ groups + root + $ ps -L # gives me the PID of my login bash -> bashPID + ... + $ addauth -p bashPID -g mail + $ groups + root mail - Having a complete GNU System (but not yet on every hardware, and only about half the software Debian offers has been ported). @@ -159,11 +168,18 @@ aren't possible. - A filesystem-based package manager. -- A framework for confining individual applications is really just one -possible use case of the hurdish subenvironments. Writing the tools -necessary for that should be quite doable in a few months. It's probably -not really much coding -- most of the work would be figuring out how it -should be set up exactly. +- subhurds for regular users + * A framework for confining individual applications is + really just one possible use case of the hurdish + subenvironments. Writing the tools necessary for that + should be quite doable in a few months. It's probably + not really much coding -- most of the work would be + figuring out how it should be set up exactly. + * subusers + * "subdo": + # Example: Let a virus run free, but any effect vanishes + # once the subhurd closes. + $ subdo --no-lasting-changes ./virus - Running parts of the Hurd on different computers, maybe even with shared servers on dedicated hardware (Cloud Computing when the servers can be made to migrate from |