From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <32d987d50705090750x67913339l163cf0e4a29feb97@mail.gmail.com> Date: Wed, 9 May 2007 16:50:26 +0200 From: "Federico Benavento" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] Problems setting up a cpu/auth/file server In-Reply-To: <9C7C2B42-4D4C-4B70-B78A-F273F75726A9@tinker.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <32d987d50705082154s355867e5vd1630b8a954a0c79@mail.gmail.com> <9C7C2B42-4D4C-4B70-B78A-F273F75726A9@tinker.com> Topicbox-Message-UUID: 60f3ed06-ead2-11e9-9d60-3106f5b1d025 > Is it normal to set up a user that is a member of sys, in this > case kim, so that that user can do system maintenance? > yes, the wiki suppose that bootes is that special *user", I have a cpu/auth/fs server where "fgb" is "bootes". > Or, should I log in as sys when I need to do maintenance? > > Should I assign passwords to sys and adm? Normally I would > think so. > no, you should login as the user you want to be the hostowner, typically bootes. ah, just in case, a typical error that people usually get is something like "server lies" because some pass don't agree. that's due to a mistmatch in the passwd you typed when you rebooted after you echoed jklds > /dev/sdC0/nvram good luck and welcome to Plan 9 -- Federico G. Benavento