Goswin von Brederlow goswin-...@web.de writes:
Note that in a chroot any mountpoints inside the chroot have their
prefix removed (/home/mrvn/chroot becomes /) while others are left as
is. That is wrong too IMHO. The filesystem the chroots / is on should
become / even if the chroot is a
On 01/20/2012 07:16 AM, Filipus Klutiero wrote:
Today I tried figuring out how much disk space a small file took. I used
stat, but that turned out surprisingly difficult:
First of all, `du` is probably a better tool to this use case. Anyway...
# LANG=C stat htpasswd.setup
File:
Pádraig Brady wrote:
...
As for %o, if you'd ask me what I/O block size means without any
context, I'm far from being sure I would answer it means size on
disk. I suggest to call this Size on disk, or Size used on the
filesystem.
I/O implies transfer.
So it corresponds to an optimal
On 01/20/2012 02:03 PM, Jim Meyering wrote:
Pádraig Brady wrote:
...
As for %o, if you'd ask me what I/O block size means without any
context, I'm far from being sure I would answer it means size on
disk. I suggest to call this Size on disk, or Size used on the
filesystem.
I/O implies
On Fri, 20 Jan 2012, Goswin von Brederlow wrote:
Henrique de Moraes Holschuh h...@debian.org writes:
On Thu, 19 Jan 2012, Paul Eggert wrote:
On 01/19/12 07:29, Henrique de Moraes Holschuh wrote:
Note: there is no reason why the kernel could not return the mount
information with shadowed
Hi Pádraig and Jim,
On 2012-01-20 09:15, Pádraig Brady wrote:
On 01/20/2012 02:03 PM, Jim Meyering wrote:
Pádraig Brady wrote:
...
As for %o, if you'd ask me what I/O block size means without any
context, I'm far from being sure I would answer it means size on
disk. I suggest to call this
On 01/20/2012 05:47 PM, Filipus Klutiero wrote:
Hi Pádraig and Jim,
On 2012-01-20 09:15, Pádraig Brady wrote:
On 01/20/2012 02:03 PM, Jim Meyering wrote:
Pádraig Brady wrote:
...
As for %o, if you'd ask me what I/O block size means without any
context, I'm far from being sure I would
On 01/20/2012 06:15 AM, Pádraig Brady wrote:
I'll go with optimal I/O transfer size hint,
There's no guarantee that it's optimal,
and I/O is always transfer, so how about
something like I/O buffer size hint instead?
On 01/21/2012 12:26 AM, Paul Eggert wrote:
On 01/20/2012 06:15 AM, Pádraig Brady wrote:
I'll go with optimal I/O transfer size hint,
There's no guarantee that it's optimal,
and I/O is always transfer, so how about
something like I/O buffer size hint instead?
Well I used optimal so
