From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15745] Adding custom user account does nothing when the user table text file dose not have a terminating newline
Date: Thu, 31 Aug 2023 07:24:02 +0000 [thread overview]
Message-ID: <bug-15745-163-4opOijWvma@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15745-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15745
--- Comment #1 from Edgar Bonet <bonet@grenoble.cnrs.fr> ---
> Adding a newline at the end fixes it and works as expected.
Do you mean that the file should end with *two* newline characters?
Note that, in a Unix environment, a text file is by definition a
sequence of LF-terminated lines of text. This implies that a non-empty
file that does not end with an LF character is not a valid text file.
The manual does mention that users tables are “regular text files”. If
the user account creation fails to parse an invalid text file, I would
not consider it a bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-31 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 22:05 [Buildroot] [Bug 15745] New: Adding custom user account does nothing when the user table text file dose not have a terminating newline bugzilla
2023-08-31 7:24 ` bugzilla [this message]
2023-08-31 17:48 ` [Buildroot] [Bug 15745] " bugzilla
2023-08-31 17:49 ` bugzilla
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-15745-163-4opOijWvma@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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