Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13561] New: Create a new user defining users-table.txt not working fine
Date: Wed, 24 Feb 2021 08:07:16 +0000	[thread overview]
Message-ID: <bug-13561-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=13561

            Bug ID: 13561
           Summary: Create a new user defining users-table.txt not working
                    fine
           Product: buildroot
           Version: 2020.02.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: al004140 at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

I am trying to create a new admin user in my rootfs, following suggested
procedure, with this steps:

$ make menuconfig 
    > System Configuration 
        > (board/company/users-table.txt) Path to the users tables 
    > Save and exit

Then created the file:

$ cat board/company/users-table.txt
admin -1 admin -1 =supersecret /home/admin /bin/sh - Admin user

And finally:

$ make all

The process ends fine, without errors.

After that, the targetfs build doesn't includes admin user nor in /etc/shadow
nor in /etc/passwd. 

However, the same procedure is working as expected when using a buildroot
2018.02.7. Please some help with this! Thx!

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-02-24  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  8:07 bugzilla at busybox.net [this message]
2021-02-24 10:50 ` [Buildroot] [Bug 13561] Create a new user defining users-table.txt not working fine bugzilla at busybox.net

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=bug-13561-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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