[[!meta copyright="Copyright © 2024 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] [[!tag stable_URL]] The word "mux" is reserved in the Hurd terminology to mean invoking user specific translators based on the filename, which is what usermux and [[hostmux]] do. While, `hostmux` invokes a translator based on the host name, `usermux` invokes a translator based on the user name. You should be able to use `usermux` with [[nfs]]. ## irc log 2010-08-25 does that mean you could very easily use nfs to automatically mount the home folders of users by just accessing them? that's usermux, yes I am confused where is the difference ? usermux is specialized in user names i.e. it can translate it into a uid before giving it as parameter to the underlying translator, for instance what I meant is a little different, I think: each user has his/her own computer with the disk and all can access each others folders as if they were local that could be done too it's a bit like autofs on linux settrans -ca nfs: /hurd/usermux /hurd/nfs server && cd nfs:/puplic ^-- is that right? youpi: but it can be done by anyone, not just root. ArneBab: sure giselher: I guess so and that is a huge difference. It lowers a barrier, hopefully to such an extend that many more users can utilize it. but it'll distinguish different computers? once the hurd has many more users, that is :) s/but/but how anatoly: by a level of directories cd nfs:/foo.bar:/blabla - it's how it should be?