From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: David Jander <david@protonic.nl>
Cc: Michael Olbrich <m.olbrich@pengutronix.de>,
"ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Resend: Home dir fixup for root in systemd
Date: Wed, 27 Jul 2016 14:04:53 +0200 [thread overview]
Message-ID: <CABDcavYCsNnZQnE9_s5Qh1UgPB0o0jdK0a_vQQS3Rq41p9BYEg@mail.gmail.com> (raw)
In-Reply-To: <20160727075124.28de2cdf@erd980>
[-- Attachment #1.1: Type: text/plain, Size: 1467 bytes --]
Hi David,
2016-07-27 7:51 GMT+02:00 David Jander <david@protonic.nl>:
> > I think that the default /etc/passwd (and many other files that are
> > distributed
> > with ptxdist) should be taken just as generic examples. Ptxdist BSPs are
> > expected
>
> Generic examples are expected to at least be semantically correct. This
> isn't.
>
I would not say it is not "semantically correct". It just does not match
the assumptions in systemd (yes, I am aware that systemd is not the only
place where this assumption is made)
[...]
> > > To solve the problem, there are really only two options AFAICS:
>
> >
> > > 1.- Change PTXdist and all places in it that assume the $HOME=/home
> for
> > > root.
> > > No idea how many places that are, nor how many users already depend on
> > > this
> > > historic assumption.
> > >
> > > or
> > >
> > > 2.- Patch systemd to adapt to the reality of PTXdist.
> > >
> >
> > Yes, or
> >
> > 3.- Customize the files in your BSP :-)
>
> No. Like I said in my previous e-mail (the part after this part, that you
> omitted from the quote), this way the default PTXdist stays broken and my
> intention is to fix just that.
>
Yes, I know what you said and I understand the intention. Here I was just
replying to the part where you say "there are really only two options".
What I say is that there are actually three options. I fully understand
that you don't like option #3, but that doesn't mean it does not exist :)
Best,
Guillermo
[-- Attachment #1.2: Type: text/html, Size: 2407 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-07-27 12:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 12:09 David Jander
2016-07-26 13:19 ` Guillermo Rodriguez Garcia
2016-07-26 14:00 ` David Jander
2016-07-26 15:13 ` Ben Stuyts
2016-07-27 5:41 ` David Jander
2016-07-26 17:50 ` Guillermo Rodriguez Garcia
2016-07-27 5:51 ` David Jander
2016-07-27 12:04 ` Guillermo Rodriguez Garcia [this message]
2016-07-27 6:55 ` Michael Olbrich
2016-07-27 8:55 ` David Jander
2016-07-27 9:04 ` Michael Olbrich
2016-07-27 9:11 ` Artur Wiebe
2016-07-27 9:29 ` David Jander
2016-07-27 10:43 ` Michael Olbrich
2016-07-27 11:24 ` David Jander
2016-07-29 8:07 ` Tim Sander
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=CABDcavYCsNnZQnE9_s5Qh1UgPB0o0jdK0a_vQQS3Rq41p9BYEg@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--cc=david@protonic.nl \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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