From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 19 Apr 2009 10:43:38 -0400 Message-ID: <509071940904190743l4c49f944h1d90e08d8189ab42@mail.gmail.com> From: Anthony Sorace To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Adventures of a home user Topicbox-Message-UUID: e8aa9644-ead4-11e9-9d60-3106f5b1d025 Jim Habegger wrote: // Adding a new user: that's not a 9vx issue; either you're misreading the documentation or it's incorrectly written (i'm not sure which bit you're reading for that). those commands are intended to be given to the file server, fossil, after connecting to the console posted in /srv. You'd get exactly the same response under qemu or on real hardware. it's worth noting, however, that 9vx is a bit different here in that, unlike most plan9 installations, it doesn't use fossil as its root file system (by default). instead of taking a large array of bits and turning it into a file system itself (as fossil does, typically using a disk partition as that array of bits, sometimes a regular file), 9vx uses the underlying host OS file system (via the #Z kernel device). there's no reason to "add users" in this sense because #Z doesn't offer connection authentication and doesn't regulate user access in the same way. issues around swapping out the root file server are where most of 9vx's differences come from (and, in my experience, reduced stability, but i'm not sure how widespread that is). things like replica often misbehave, as well. it'd be worth putting together a diff guide of sorts.