From: Phil Blundell <pb@pbcl.net>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Patrick Ohly <patrick.ohly@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] rootfs-postcommands.bbclass: sort passwd entries
Date: Sun, 08 Jan 2017 09:36:55 +0000 [thread overview]
Message-ID: <1483868215.4360.185.camel@pbcl.net> (raw)
In-Reply-To: <1483829528.4367.142.camel@linuxfoundation.org>
On Sat, 2017-01-07 at 22:52 +0000, Richard Purdie wrote:
> On Sat, 2017-01-07 at 20:00 +0100, Patrick Ohly wrote:
> >
> > On Sat, 2017-01-07 at 09:59 +0000, Phil Blundell wrote:
> > >
> > > That sounds like a good idea. And in that case, maybe it would
> > > be
> > > better to sort on uid rather than username? That would preserve
> > > the
> > > "traditional" ordering in the file, i.e. root first.
> > I had thought about that, but then did not pursue that further
> > because
> > it would have made sorting quite a bit more complex (needs to know
> > about
> > line content, id not present in each file).
> >
> > I can give it a try, though, if that's considered worth some
> > additional
> > complexity.
>
> I think those functions can be python functions and this might not be
> too bad to write in python....
I'm not sure it's that complicated. Maybe I'm overlooking something
obvious, but something like "sort -t: -k3n" seems like it ought to
suffice for sorting /etc/passwd and /etc/group on numeric id.
I didn't understand Patrick's comment about "id not present in each
file" though, maybe that's the key to the extra complexity.
p.
next prev parent reply other threads:[~2017-01-08 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 15:38 [PATCH 1/1] rootfs-postcommands.bbclass: sort passwd entries Patrick Ohly
2017-01-06 21:17 ` Phil Blundell
2017-01-07 8:06 ` Patrick Ohly
2017-01-07 9:59 ` Phil Blundell
2017-01-07 19:00 ` Patrick Ohly
2017-01-07 22:52 ` Richard Purdie
2017-01-08 9:36 ` Phil Blundell [this message]
2017-01-08 14:04 ` Patrick Ohly
2017-01-09 10:09 ` [PATCH V2 " Patrick Ohly
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=1483868215.4360.185.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.com \
--cc=richard.purdie@linuxfoundation.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