mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] /usr merge
Date: Wed, 12 Apr 2017 10:27:30 +0200	[thread overview]
Message-ID: <e1e8f89b-b08c-8fd8-0c3f-8f14e4ad099c@gr13.net> (raw)
In-Reply-To: <20170411100720.h4hg35fwgd2lrqhf@pengutronix.de>

On 11.04.2017 12:07, Michael Olbrich wrote:

Hi,

> I've just pushed a large series of commits for /usr merge. This means that
> /bin, /sbin and /lib are now symlinks to the corresponding directories in
> /usr. All files are installed accordingly.

Just curious: what's the actual problem to solve ?

For my embedded projects, I haven't had an actual usecase for having
them separated, but on server systems lots of them over the past 20yrs.

Note that this separation indeed has serious reaons: separating the
base system (IOW: everything required to boot up at least to single
user mode and mount /usr - whereever it might come from). Most of the
practical usecases might be obsolete now (eg. storage is so cheap that
people rarely have the need to share /usr within clusters, etc), but
still there're lots of systems out there relying on that (maybe quite
irrelevant to ptxdist, but certainly for standard like Debian)

I'm personally agnostic to that, but I've already seen such setups
(eg. having /usr on separate SDcard) in embedded systems. So, it seems
better if that remains configurable.

> I'm not going to rehash all the arguments for this. My main motivations
> are:
> - It's where the big distros are going, so it's better tested in the long
>   term.

Note that this already caused a lot of trouble there. (eg. there've
been huge flamewars @debian). IIRC that all started w/ the systemd
mess, which suddenly introduced hard dependencies to things in /usr -
the reaction of Lennart+friends was just ranting aaginst who relies
on the separation.

> - We've had several problems in the past where programs where searched in
>   the wrong location. And busybox didn't make that any easier.

Correct me if I'm wrong, but isn't that what $PATH is for ?

> How it works in PTXdist:
> - install_copy and friends will transparently move files to /usr where
>   appropriate. So if you have packages that install files to /bin etc. it
>   should just work. If not, please sent a mail to this list.

I really have a bad feeling about such magic in existing commands,
which now suddenly change semantics. At least that should be
configurable.


--mtx


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-04-12  8:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 10:07 Michael Olbrich
2017-04-12  8:27 ` Enrico Weigelt, metux IT consult [this message]
2017-04-12  9:24   ` Michael Olbrich
2017-04-12 12:06     ` Ladislav Michl
2017-04-12 12:36     ` Enrico Weigelt, metux IT consult
2017-04-12 13:36       ` Clemens Gruber
2017-04-12 18:42       ` Alexander Dahl

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=e1e8f89b-b08c-8fd8-0c3f-8f14e4ad099c@gr13.net \
    --to=enrico.weigelt@gr13.net \
    --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