jlee@sobeco.com (j.lee) (05/24/91)
Running /dev/MKDEV script on our system seems to invoke "mknod" more than once using the same type/major/minor arguments with different names. This will result in several different inodes being assigned for the same device. Is this always safe, or can some devices get confused if openned/closed via more than one inode at once? Jeff Lee -- jlee@sobeco.com || jonah@cs.toronto.edu
trevc@tecate.mips.com (Trevor Cotton) (05/25/91)
In article <1991May24.142146.28886@sobeco.com>, jlee@sobeco.com (j.lee) writes: |> Running /dev/MKDEV script on our system seems to invoke "mknod" more than |> once using the same type/major/minor arguments with different names. This |> will result in several different inodes being assigned for the same device. |> Is this always safe, or can some devices get confused if openned/closed via |> more than one inode at once? |> |> Jeff Lee -- jlee@sobeco.com || jonah@cs.toronto.edu It is not a good idea, as some devices can get confused ( specifically, streams clone devices ). This will be fixed in the next release of RISC/os. -- --trevc-- Trevor Cotton, Sustaining Engineering, MIPS Computer Systems Inc. MS 6-05, 930 DeGuigne Drive, Sunnyvale, CA 94088-3650 Tel: +1 408 524 7286 Fax: +1 408 524 7521 Email: {wyse,ames,decwrl,pyramid}!mips!trevc trevc@mips.com