On Tue, Nov 12, 2019 at 03:09:27PM +0100, Oguz Bektas wrote:
> hi,
>
> built the latest git version of pve-common and pve-container with
> wolfgang's patches.
>
> with running kernel: 5.0.21-4-pve
> and the latest pve-kernel-5.3
>
> found a small issue while testing.
>
> when one has an older k
On Tue, Nov 12, 2019 at 03:09:27PM +0100, Oguz Bektas wrote:
> hi,
>
> built the latest git version of pve-common and pve-container with
> wolfgang's patches.
>
> with running kernel: 5.0.21-4-pve
> and the latest pve-kernel-5.3
forgot to mention that it worked as expected with the newer kernel
>
hi,
built the latest git version of pve-common and pve-container with
wolfgang's patches.
with running kernel: 5.0.21-4-pve
and the latest pve-kernel-5.3
found a small issue while testing.
when one has an older kernel and tries to hotplug a mountpoint
--
sounds all good, need to take a closer look at the meat tough :)
> Oguz, can you please give this also a testing spin?
ok
___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
On 11/8/19 11:06 AM, Wolfgang Bumiller wrote:
> The pve-common path of this patch set should be straight forward:
> minor additions to ProcFSTools and Tools, as well as the new mount api
> constants added to Syscall.pm.
>
It is, thus applied that one already.
> The container part then makes use
The pve-common path of this patch set should be straight forward:
minor additions to ProcFSTools and Tools, as well as the new mount api
constants added to Syscall.pm.
The container part then makes use of the new mount api in case the
currently running kernel supports it. The hope for the future w
