Aurelien Jarno aurel...@aurel32.net writes:
The problem actually from here sys/sys/mount.h, and is not specific to
procfs:
| #define MNAMELEN88 /* size of on/from name bufs */
...
| #define OMNAMELEN (88 - 2 * sizeof(long)) /* size of on/from
name bufs */
The
Jens Thiele a écrit :
Aurelien Jarno aurel...@aurel32.net writes:
Actually it doesn't, it's just that the chroot's name I used was a bit
smaller.
ok
If we find from where this limit come, we can probably increase
it (most probably in the kernel).
Looking at the reported limits:
Aurelien Jarno aurel...@aurel32.net writes:
Actually it doesn't, it's just that the chroot's name I used was a bit
smaller.
ok
If we find from where this limit come, we can probably increase
it (most probably in the kernel).
Looking at the reported limits:
cat test.c make -k test
How did you work around the file name too long error message when
using the nullfs for the bind mount?
Greetings
Jens
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Jens Thiele a écrit :
How did you work around the file name too long error message when
using the nullfs for the bind mount?
I haven't seen such a problem. Do you have more details about it?
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurel...@aurel32.net
Aurelien Jarno aurel...@aurel32.net writes:
Jens Thiele a écrit :
How did you work around the file name too long error message when
using the nullfs for the bind mount?
I haven't seen such a problem. Do you have more details about it?
The mount seems to hit a length limit:
I: 10mount:
On Mon, Feb 01, 2010 at 09:45:33PM +0100, Jens Thiele wrote:
Aurelien Jarno aurel...@aurel32.net writes:
Jens Thiele a écrit :
How did you work around the file name too long error message when
using the nullfs for the bind mount?
I haven't seen such a problem. Do you have more
Aurelien Jarno aurel...@aurel32.net writes:
Which kernel are you using? I don't have this problem, but I am using a
8.0 kernel, which may have removed such a limit.
That was my first thought, too. But after updating to the 8.0 kernel it
still happened. For you the exact same mount call works?
On Mon, Feb 01, 2010 at 11:49:50PM +0100, Jens Thiele wrote:
Aurelien Jarno aurel...@aurel32.net writes:
Which kernel are you using? I don't have this problem, but I am using a
8.0 kernel, which may have removed such a limit.
That was my first thought, too. But after updating to the 8.0
9 matches
Mail list logo