How does it fail?
Try for example (manually):
mkfifo foo
mknod foo c 1 1
# cd /
# mknod foo c 1 1
ksh: mknod: foo: Invalid argument
FAILS with invalid argument.
What *can* be an issue is that mknod inside a chroot is not allowed, as
well as mknod as non-root (except for pipes, i.e. mknod
Hi!
On Sun, May 04, 2008 at 03:09:25PM +, Paul Pruett wrote:
>>Isn't /tmp mounted with option nodev, by chance?
>Would not explain it failing in /dev
>[...]
How does it fail?
Try for example (manually):
mkfifo foo
mknod foo c 1 1
You see mknod fail with "File exists". Even on a filesyste
Isn't /tmp mounted with option nodev, by chance?
Would not explain it failing in /dev
but a good thought.
uhmm on this computer, /tmp is on the root partition, did not make a
separate mount in fstab for it, ... yes,
probably should have made a /tmp partition so as to be able to add
options
Isn't /tmp mounted with option nodev, by chance?
on one amd64 computer
Somehow mknod will not accept device name, but it can create a fifo
works on a similar amd64 computer w/ same arch. so it was likely
it was something like this that did it:
The screw up,
on an amd64 4.3beta, in an accident, snafu,
I copied the i386 MAKEDEV to /dev and thus
5 matches
Mail list logo
