From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: MIME-Version: 1.0 In-Reply-To: <20160727075124.28de2cdf@erd980> References: <20160726140925.16dc99e7@erd980> <20160726160034.40ee8b05@erd980> <20160727075124.28de2cdf@erd980> From: Guillermo Rodriguez Garcia Date: Wed, 27 Jul 2016 14:04:53 +0200 Message-ID: Subject: Re: [ptxdist] Resend: Home dir fixup for root in systemd List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: multipart/mixed; boundary="===============0818471088==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: David Jander Cc: Michael Olbrich , "ptxdist@pengutronix.de" --===============0818471088== Content-Type: multipart/alternative; boundary=94eb2c0919f2436aff05389cd340 --94eb2c0919f2436aff05389cd340 Content-Type: text/plain; charset=UTF-8 Hi David, 2016-07-27 7:51 GMT+02:00 David Jander : > > 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 --94eb2c0919f2436aff05389cd340 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi David,

2016-07-27 7:51 GMT+02:00 David Jander <<= a href=3D"mailto:david@protonic.nl" target=3D"_blank">david@protonic.nl= >:
> I thin= k that the default /etc/passwd (and many other files that are
> distributed
> with ptxdist) should be taken just as generic examples. Ptxdist BSPs a= re
> expected

Generic examples are expected to at least be semantically correct. T= his isn't.

I would not say it is no= t "semantically correct". It just does not match the assumptions = in systemd (yes, I am aware that systemd is not the only place where this a= ssumption is made)
=C2=A0
[...]
> > To solve the pro= blem, there are really only two options AFAICS:
> >
> >=C2=A0 1.- Change PTXdist and all places in it that assume the $HO= ME=3D/home for
> > root.
> >=C2=A0 No idea how many places that are, nor how many users alread= y depend on
> > this
> >=C2=A0 historic assumption.
> >
> > or
> >
> >=C2=A0 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 k= now 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". Wh= at 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
--94eb2c0919f2436aff05389cd340-- --===============0818471088== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0818471088==--