>Why isn't there provision for file "types" at least >(mknod types b and c come to mind)?
that's a particularly bad example to pick. those shouldn't exist at all.
>Why isn't there provision for file "types" at least >(mknod types b and c come to mind)?
that's a particularly bad example to pick. those shouldn't exist at all.