Void Linux discussion
 help / color / mirror / Atom feed
From: Userx Xbw <use...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: How to set a new user?
Date: Sat, 30 Jan 2016 10:00:05 -0800 (PST)	[thread overview]
Message-ID: <ac1eecfb-7b4e-4099-8b71-71b756070d14@googlegroups.com> (raw)
In-Reply-To: <a07f7be3-f91b-4380-9400-2197d478ff10@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 1958 bytes --]

Oh yes in that log in screen .. it looks like a little long white-ist box, 
click into there enter root then the password you gave it during installing 
it on VBox 





On Thursday, October 15, 2015 at 3:21:10 PM UTC-5, André Luiz Duarte de 
Queiroz wrote:
>
> Hi, I've just installed Void Linux in a virtual machine from its liveCD 
> (X86_64 version, with LXDE), for testing purposes; I'm looking for a distro 
> "systemd free" to, eventually, replace my current desktop system (Mageia) 
> and, so far, I'm very impressed and hopeful with Void Linux! Both liveCDs 
> I've got ('flavours' LXDE, and XFCE with "musl") run so fast they look  
> already installed in the HD! Quite impressive!!
>
> However, I've some doubts; after installed LXDE version at a VirtualBox 
> virtual machine, when trying o run it for the first time, I've found that 
> there was only root user defined; there's no common uses set during 
> installing process...
>
> In the initial screen, the system requires user login. I tried to login as 
> anon with default password, but it failed. I did login as root user (" su 
> "), with the password I set during installing (that text only installing 
> tool is much more simple than graphical tools I'm used with using Mageia 
> and other distros... but it works!). Being a KDE user (running Mageia), I'm 
> not used with LCDE sessions, and just don't know where/how to set a common 
> user, once login as "su" is not a good policy, even when working in a 
> virtual machine...! I couldn't find yet any graphical tool to set a new 
> user and other system settings, should I make this through a terminal?
>
> I have other doubts about setting the system, especially some related to 
> multi-language input in Void Linux (with ibus), but I shall wait to clarify 
> such topics after have solved basic settings of the system.
> I look forward to have a sooner reply from you, folks!
> Regards!
>

[-- Attachment #1.2: Type: text/html, Size: 2151 bytes --]

  parent reply	other threads:[~2016-01-30 18:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 20:21 André Luiz Duarte de Queiroz
2015-10-15 21:39 ` Steve Prybylx
     [not found]   ` <20151016130852.6e65eeda5dbfd698031cea3d@t-online.de>
2015-10-16 11:15     ` Googlemail
2015-10-16 12:53       ` André Luiz Duarte de Queiroz
2015-10-16 14:58 ` Stefan Mühlinghaus
2015-10-16 17:22   ` André Luiz Duarte de Queiroz
2015-10-16 17:24   ` André Luiz Duarte de Queiroz
2016-01-29  2:43   ` Userx Xbw
2015-10-17 10:34 ` Stefan Mühlinghaus
2016-01-30 17:58 ` Userx Xbw
2016-01-30 18:00 ` Userx Xbw [this message]
2016-02-03 20:34 ` Toribio

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=ac1eecfb-7b4e-4099-8b71-71b756070d14@googlegroups.com \
    --to="use..."@gmail.com \
    --cc="void..."@googlegroups.com \
    /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).