9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mats Olsson <plan9.meo@gmail.com>
To: mischief@9.offblast.org
Cc: 9fans@9fans.net
Subject: Re: [9fans] Adding a new user.
Date: Tue,  2 Dec 2014 22:13:04 +0100	[thread overview]
Message-ID: <CAEj9f0+5_cWZn7GY_hi+R6kOqXtQp5uVaK=r7Mq7noJ7+K5u1A@mail.gmail.com> (raw)
In-Reply-To: <CAEj9f0KEzWa5odmRCq=G=kWtdDnOiUKG4A8PeEX6p4MsGD-Hxg@mail.gmail.com>

Hi again!

Missed "adm" in adm +<user> in my brief explanation earlier. Think
I'll first check for a command in /bin/rc that would be more
appropriate than 'uname'. There just must be one more obvious that
I've missed. Well, will see tomorrow.

Best wishes,
Mats

2014-12-02 21:54 GMT+01:00, Mats Olsson <plan9.meo@gmail.com>:
> OK my bad. The question I asked was like thinking out loud without
> giving details. So I'm using Plan 9 on the Raspberry Pi (Plan 9 from
> Bell Labs that is). The problem is that after running "uname <user>
> <user>" (can't reproduce right now since my screen/TV is occupied) the
> rc shell is put on hold and in the documentation (just have a single
> side printout so I can't give any accurate source of it right now)
> says that you can give sys and adm rights to that user by continuing
> with: uname sys +<user> and uname +<user> witch gives you error
> messages (can't be more specific now because of the forementioned
> reasons). Then we also have the problem with this specific platform
> that defaults to user glenda without prompt. The cmdline.txt looks
> like this; readparts=1 nobootprompt=local user=glenda ipconfig= so the
> system must be halted to change the user. The file cmdline.txt is kind
> of the init file in several OS's for the Raspberry Pi. My first test
> would be to run "uname <user> <user> and ctrl+alt+del to reboot and
> cut the powed to change the user in the cmdline.txt file. Hopefully (I
> think it was possible to get into the system again) I get i to Plan 9
> and can run: "/sys/lib/newuser" as said in the "doc" I have. Now I
> should have asked (and do) if this is the right thing to do? or what
> could get me another user than the default? I hope you bear with me
> even if this whole thing went backwards. First the question and then
> the problem or more correct the situation. Thankful for any hints in
> the right direction or just what you guys think about the situation.
> I'll give it a try tomorrow anyhow. Thanks for showing interest!
>
> Kind regards,
> Mats
>
> 2014-12-02 19:08 GMT+01:00, mischief@9.offblast.org
> <mischief@9.offblast.org>:
>> what 'doc' do you refer to? what didn't work properly? nobody can help
>> you
>> if you don't explain what the problem is.
>>
>



  reply	other threads:[~2014-12-02 21:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 16:33 Mats Olsson
2014-12-02 16:42 ` Jacob Todd
2014-12-02 18:08 ` mischief
2014-12-02 20:54   ` Mats Olsson
2014-12-02 21:13     ` Mats Olsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-12-02 21:08 sl
2014-12-03  0:37 ` erik quanstrom
2014-12-03  0:41   ` erik quanstrom
2014-12-03  8:31     ` Mats Olsson
2014-12-03  9:00       ` Mats Olsson
2014-12-02 17:10 sl
2004-02-27  5:17 [9fans] adding " David Caplan
2004-02-27  4:34 ` andrey mirtchovski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEj9f0+5_cWZn7GY_hi+R6kOqXtQp5uVaK=r7Mq7noJ7+K5u1A@mail.gmail.com' \
    --to=plan9.meo@gmail.com \
    --cc=9fans@9fans.net \
    --cc=mischief@9.offblast.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).