what, having device files in the root? Seems good to me, or rather, I
don't see what's wrong with it. If you or the program have permissions and
access to mknod you can stick a device file anywhere in the filesystem I
suppose. Seems to me their location in the filesystem is more a matter of
convenience than necessity, so if you wanted to put them elsewhere (say on
a ramdisk filesystem which doesn't get backed up?) that shouldn't be a bad
thing. Not sure if it's a good (meaningful, effective) thing, though.
--
Jack Coates
Monkeynoodle: It's what's for dinner!
On Sat, 17 Feb 2001 [EMAIL PROTECTED] wrote:
> On 17 Feb 2001, at 6:49, Jack Coates wrote:
>
> > I'd be inclined to stick to your existing system -- it seems sick
> > and wrong to put device files in /tmp and I don't understand what
> > they'd be doing there instead of /dev. There may well be a good
> > reason (permissions? why not chmod the /dev entry?) but until one
> > comes forward...
>
> I noticed too, that /tmp defaults to being built into / which
> includes /dev; thus unless /tmp is separated out it can have device
> files created in it.
>
> Is THIS a bad thing?
>
>
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
