On 27.07.2017 06:13, Narcis Garcia wrote:
vzquota does in OpenVZ does what LXC doesn't.
Sure ? Proxmox somehow manages to do it (via lxc). Maybe look at
their code to find out how its done.
--mtx
___
Dng mailing list
Dng@lists.dyne.org
https://mai
Le 26/07/2017 à 22:00, Christopher Clements a écrit :
Wouldn't this work? (no error checking of course XD)
off_t lseek(int fd, off_t offset, int whence);
ssize_t write(int fd, const void *buf, size_t count);
ssize_t pwrite(int fd, const void *buf, size_t count, off_t
offset) {
On 27.07.2017 08:22, Didier Kryn wrote:
At first glance at least, it means that file offsets are managed in the
kernel or VFS
Of course they are. That's required for any sane multiprocessing
implementation. And some files/devices don't even have the notion
of a current position (IOW: not seeka
Hi Ralph,
On 07/18/2017 05:54 AM, Ralph Ronnquist wrote:
debhttp://auto.mirror.devuan.org/devuan/ experimental main
deb-srchttp://auto.mirror.devuan.org/devuan/ experimental main
There is no package named vdev-dbgsym in debian/control:
http://auto.mirror.devuan.org/devuan/pool/main/v/vdev/
El 27/07/17 a les 09:51, Enrico Weigelt, metux IT consult ha escrit:
> On 27.07.2017 06:13, Narcis Garcia wrote:
>
>> vzquota does in OpenVZ does what LXC doesn't.
>
> Sure ? Proxmox somehow manages to do it (via lxc). Maybe look at
> their code to find out how its done.
>
* Proxmox VE distribu
On 27.07.2017 17:35, Narcis Garcia wrote:
El 27/07/17 a les 09:51, Enrico Weigelt, metux IT consult ha escrit:
On 27.07.2017 06:13, Narcis Garcia wrote:
vzquota does in OpenVZ does what LXC doesn't.
Sure ? Proxmox somehow manages to do it (via lxc). Maybe look at
their code to find out how i
On 27-07-17 22:13, Enrico Weigelt, metux IT consult wrote:
On 27.07.2017 17:35, Narcis Garcia wrote:
El 27/07/17 a les 09:51, Enrico Weigelt, metux IT consult ha escrit:
On 27.07.2017 06:13, Narcis Garcia wrote:
vzquota does in OpenVZ does what LXC doesn't.
Sure ? Proxmox somehow manages to
Yes, I don't know why it's built, and I'm not sure what it is, but it
came with the release building. Presumably some setting could be changed
to avoid it, but I haven't looked into it. So far I've managed to just
ignore it :-)
regards,
Ralph.
aitor_czr wrote on 28/07/17 02:24:
Hi Ralph,
O
On Fri, 2017-07-28 at 07:27 +1000, Ralph Ronnquist wrote:
> Yes, I don't know why it's built, and I'm not sure what it is, but
> it
> came with the release building. Presumably some setting could be
> changed
> to avoid it, but I haven't looked into it. So far I've managed to
> just
> ignore it
