Sven Hartge (2018-01-18):
> This was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885325, fixed
> in systemd 236-3. It has migrated to Buster yesterday, so upgrading will
> fix it for you.
I was not expected such a tight race condition between when I checked
this and when I wrote the mail.
T
On 2018-01-18 15:57 +0100, Nicolas George wrote:
> David Wright (2018-01-18):
>> I can't replicate this on stretch. What versions of what are
>> you running?
>
> Sorry, I should have mentioned it: it's Buster, up-to-date by a few
> days.
>
>> Could you give some explicit commands, and where to typ
Nicolas George wrote:
> I noticed that for some time, sshd is being started in a separate
> filesystem namespace. As a consequence, mounts done from a SSH shell are
> not visible from the main system, and that disrupts my use habits.
This was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885
David Wright (2018-01-18):
> I can't replicate this on stretch. What versions of what are
> you running?
Sorry, I should have mentioned it: it's Buster, up-to-date by a few
days.
> Could you give some explicit commands, and where to type them.
ssh box
mkdir /tmp/dummy
sudo mount -t tmpfs dummy /
On Thu 18 Jan 2018 at 14:59:34 (+0100), Nicolas George wrote:
> Hi.
>
> I noticed that for some time, sshd is being started in a separate
> filesystem namespace. As a consequence, mounts done from a SSH shell are
> not visible from the main system, and that disrupts my use habits.
>
> Is it on pu
Hi.
I noticed that for some time, sshd is being started in a separate
filesystem namespace. As a consequence, mounts done from a SSH shell are
not visible from the main system, and that disrupts my use habits.
Is it on purpose?
I have tracked things in the source code to exec_needs_mount_namespa
6 matches
Mail list logo
