From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
pkg-qemu-devel@lists.alioth.debian.org,
Cole Robinson <crobinso@redhat.com>,
Miroslav Rezanina <mrezanin@redhat.com>
Subject: Re: [PATCH] modules: load modules from versioned /var/run dir
Date: Fri, 13 Mar 2020 10:55:57 +0000 [thread overview]
Message-ID: <20200313105557.GC962573@redhat.com> (raw)
In-Reply-To: <d837839f-e1e5-3cbf-b8fd-a2a6cc4ad5ce@redhat.com>
On Fri, Mar 13, 2020 at 08:45:21AM +0100, Paolo Bonzini wrote:
> On 13/03/20 08:34, Michael Tokarev wrote:
> >> The use of /var/run makes me a little uneasy. I guess it's related to
> >> wanting to uninstall the old package so the .so in their original
> >> location cannot be used (even if they had a versioned path)?
> >
> > BTW, this is /run nowadays, not /var/run, as far as I can see.
>
> /var/run is still symlinked to /run. QEMU generally uses /var/run,
> though we could consider switching sooner or later.
Only Linux commonly uses /run, others still use /var/run.
We really only need a "configure --rundir=/run" arg to override the
default, in the same way distros pick /etc and /var, instead of
/usr/etc and /usr/var.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-03-13 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 13:26 [PATCH] modules: load modules from versioned /var/run dir Christian Ehrhardt
2020-03-06 14:41 ` no-reply
2020-03-09 11:59 ` Christian Ehrhardt
2020-03-10 9:39 ` Stefan Hajnoczi
2020-03-10 11:47 ` Christian Ehrhardt
2020-03-16 11:21 ` Stefan Hajnoczi
2020-03-10 12:09 ` Daniel P. Berrangé
2020-03-10 13:16 ` Christian Ehrhardt
2020-03-13 7:34 ` Michael Tokarev
2020-03-13 7:45 ` Paolo Bonzini
2020-03-13 10:55 ` Daniel P. Berrangé [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-04 9:37 Best practices to handle shared objects through qemu upgrades? Christian Ehrhardt
2020-03-04 9:39 ` [PATCH] modules: load modules from versioned /var/run dir Christian Ehrhardt
2020-03-06 10:54 ` Stefan Hajnoczi
2020-03-06 13:27 ` Christian Ehrhardt
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=20200313105557.GC962573@redhat.com \
--to=berrange@redhat.com \
--cc=christian.ehrhardt@canonical.com \
--cc=crobinso@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=mrezanin@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pkg-qemu-devel@lists.alioth.debian.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.