Path: utzoo!utgpu!watserv1!watmath!att!rutgers!uwm.edu!cs.utexas.edu!fletcher
From: flee@guardian.cs.psu.edu (Felix Lee)
Newsgroups: comp.std.unix
Subject: Re: Unified I/O namespace: what's the point?
Message-ID: <13688@cs.utexas.edu>
Date: 16 Oct 90 15:32:42 GMT
References: <13220@cs.utexas.edu> <13343@cs.utexas.edu> <13390@cs.utexas.edu>
Sender: fletcher@cs.utexas.edu
Organization: Penn State Computer Science
Lines: 24
Approved: fletcher@cs.utexas.edu (Guest Moderator, Fletcher Mattox)
X-Submissions: std-unix@uunet.uu.net

Submitted-by: flee@guardian.cs.psu.edu (Felix Lee)


>On the contrary. syslog is a counterexample. While it is hardly as
>modular as I would like, it shows that (0) an fd-centric model works;

syslog shows the limitations of an fd-centric model.  B News, for
example, writes log entries in the files "log" and "errlog".  You
cannot redirect this into syslog without modifying code.

If syslog existed in the filesystem namespace, you might
	ln -s /syslog/news.info log
	ln -s /syslog/news.err errlog
or maybe even
	ln -s ~/mylog/news.err errlog
and everything would work.

Why should I have to teach all my programs about syslog when I can
just write to a filesystem object instead?
--
Felix Lee	flee@cs.psu.edu


Volume-Number: Volume 21, Number 204