Open GoogleCodeExporter opened 9 years ago
This is caused by changeset 134 -- I don't use dotu for my servers and after
updating go9p, "9p" from p9p suddenly fails to connect.
Ultimately the problem boils down to the default Users implementation not
implementing Uname2User.
For my case (non-dotu server & client) I'd be happy to have my server provide a
custom Users implentation, but this seems like a suboptimal solution for the
original report (dotu server & non-dotu client).
Original comment by sqw...@gmail.com
on 8 Aug 2014 at 4:43
The best solution I see that doesn't break backwards compatibility is to have
osUsers defer to the os/user package. The downside is os/user wasn't
implemented on all platforms until go 1.1 -- but I think everything was in
place for linux at 1.0's launch, and the p.Users interface doesn't port very
well to windows/plan 9 anyway (non-integer UIDs).
Go still doesn't provide an interface to get at the name of a group[1] which
seems discouraging, but is not that important since user groups are not part of
the 9p protocol itself - they are a server-side concept.
[1] http://code.google.com/p/go/issues/detail?id=2617
I've attached a patch to that effect.
Original comment by sqw...@gmail.com
on 11 Aug 2014 at 2:00
Attachments:
Use of "os/user" unfortunately means that cross compiling during go build may not work as CGO_ENABLED=1 is required.
closed by #44 ?
Yes this is fixed, I think by c1542d058224b (which was also applied to the code.google.com repo while it was active).
Original issue reported on code.google.com by
lo...@bettens.org
on 23 Jul 2014 at 8:29