From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 8/8] system/skeleton: drop lp user from shadow
Date: Mon, 27 Oct 2014 16:12:00 -0300 [thread overview]
Message-ID: <544E9900.4020201@zacarias.com.ar> (raw)
In-Reply-To: <CANxTyt5UQcLUYo7-UTWnYOCPE3eEY7C5GpTSYqokQRpB4GhA7A@mail.gmail.com>
On 10/27/2014 04:08 PM, Danomi Manchego wrote:
> I find that udev-182 logs a warning when the "lp" group isn't defined.
> Is it a "don't care"?
That's on system/skeleton/etc/group and i've kept it, this is just the
shadow copy of the (inexistant) lp user from /etc/passwd.
And udev rules don't concern with the lp user at all anyway.
But since you say udev-182 that means you're using an older BR version
aren't you?
Regards.
next prev parent reply other threads:[~2014-10-27 19:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 18:18 [Buildroot] [PATCH 1/8] dbus: drop user/group from skeleton Gustavo Zacarias
2014-10-27 18:18 ` [Buildroot] [PATCH 2/8] openssh: drop user " Gustavo Zacarias
2014-10-27 18:18 ` [Buildroot] [PATCH 3/8] system/skeleton: drop backup user Gustavo Zacarias
2014-10-27 18:18 ` [Buildroot] [PATCH 4/8] system/skeleton: drop proxy user Gustavo Zacarias
2014-10-27 18:18 ` [Buildroot] [PATCH 5/8] system/skeleton: drop valid shell from non-login users Gustavo Zacarias
2014-10-27 18:18 ` [Buildroot] [PATCH 6/8] system/skeleton: drop adm user from shadow Gustavo Zacarias
2014-10-27 18:19 ` [Buildroot] [PATCH 7/8] system/skeleton: drop shutdown " Gustavo Zacarias
2014-10-27 18:19 ` [Buildroot] [PATCH 8/8] system/skeleton: drop lp " Gustavo Zacarias
2014-10-27 19:08 ` Danomi Manchego
2014-10-27 19:12 ` Gustavo Zacarias [this message]
2014-10-27 18:28 ` [Buildroot] [PATCH 1/8] dbus: drop user/group from skeleton Thomas Petazzoni
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=544E9900.4020201@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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