From: Thomas Huth <1653577@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1653577] Re: Ability to set umask for 9pfs
Date: Sat, 11 Jan 2020 09:12:52 -0000 [thread overview]
Message-ID: <157873397315.5281.3816510941973918137.launchpad@gac.canonical.com> (raw)
In-Reply-To: 20170103031332.1493.46452.malonedeb@soybean.canonical.com
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1653577
Title:
Ability to set umask for 9pfs
Status in QEMU:
Incomplete
Bug description:
We should be able to specify the umask for 9pfs so that files created
by the guest can be accessed by other users on the host. Currently
they're only accessible by the user running qemu (and of course,
root).
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1653577/+subscriptions
next prev parent reply other threads:[~2020-01-11 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 3:13 [Qemu-devel] [Bug 1653577] [NEW] Ability to set umask for 9pfs Nathan Rennie-Waldock
2020-01-10 9:45 ` [Bug 1653577] " Thomas Huth
2020-01-10 10:42 ` Greg Kurz
2020-01-11 9:12 ` Thomas Huth [this message]
2020-03-12 4:17 ` Launchpad Bug Tracker
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=157873397315.5281.3816510941973918137.launchpad@gac.canonical.com \
--to=1653577@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 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.