From: "André Luiz Duarte de Queiroz" <"andre.luiz..."@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: How to set a new user?
Date: Fri, 16 Oct 2015 10:24:51 -0700 (PDT) [thread overview]
Message-ID: <09d8d259-7f89-4098-b84b-292cc4a0038a@googlegroups.com> (raw)
In-Reply-To: <16bad968-2175-4279-94a8-a0d87d8dfa17@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 3053 bytes --]
Thank you, Stefan! This clarifies a few things, and a lot of others too!! ;)
It seems I'll learn very much about Linux and its 'guts' moving to Void
Linux, what is a fine irony, since I was looking for a distro 'simpler'
than my current one, and which 'just works' ! So far, I've got my share of
troubles with "*systemd*" implementations (I lost TWO HDs due to errors
related to it!...), and I was willing to find a "systemd free" distro which
isn't too much complicated to install and configure! I think I found it! :)
Now, its' a question of free time and *easy mind* to sit at my desktop,
start my VM with Void Linux/LXDE, make all personal settings I want and, if
successful, install Void Linux "officially" at a partition in my 500 GB
Hard Drive! BTW, can I maintain my current '/home' partition (from my
current system, Mageia) without any hassle ?...
Regards to all!
Em sexta-feira, 16 de outubro de 2015 11:58:31 UTC-3, Stefan Mühlinghaus
escreveu:
>
> The groups on your system will probably vary somewhat from that list since
> you will have diffent software installed and without the software that uses
> the groups having them is quite pointless. That means you should not just
> create groups on your system that are not already there.
>
> Serveral groups just allow access to some hardware on your system. These
> are for example *floppy, dialout, audio, video, cdrom, scanner, network*.
> You need to add your user to these groups if that kind of hardware exists
> and your user needs access to it.
> *audio*, *video*, *cdrom* and *scanner* are probably good ideas.
> Networking is usually established by root during boot so your user
> probably will not need to be in *network* or *dialout*.
> You need to be in the *kvm* group if you want to use KVM-based virtual
> machines.
>
> *wireshark*, *clamav*, *socklog* and *pulse-access* are really only
> relevant if you are using the corresponding software and then it depends on
> the software what it actually means to be in the group. Wireshark is a
> network protocol analyzer, ClamAV is a virus scanner and Socklog a system
> message logger. If you do not have/use these programs you do not need to be
> in their groups. You you are using PulseAudio for audio on your system it
> may be a good idea for your user to be in the *pulse-access* group to
> gain access to the PulseAudio server.
>
> If you create a new user it usually gets its own group with the same name
> as the user itself. What the members of this group can or cannot do is
> completely up to you. You may also add your user to the *users* group but
> unless you explicitly give this group any special meaning it does not give
> you any advantages.
>
> The *wheel* group is used by *su* and *sudo* to determine who may gain
> root access via these commands. If you want that your user should be in
> *wheel*. You however also need to configure that behaviour in
> /etc/sudoers.
>
> I hope this clarifies a few things :)
>
[-- Attachment #1.2: Type: text/html, Size: 3681 bytes --]
next prev parent reply other threads:[~2015-10-16 17:24 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 [this message]
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
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=09d8d259-7f89-4098-b84b-292cc4a0038a@googlegroups.com \
--to="andre.luiz..."@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).