Message-Id: <3.0.1.32.19980127083623.007f7740@yacker.xiotech.com>
Date: Tue, 27 Jan 1998 08:36:23 -0600
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
From: Randy Maas <randym AT acm DOT org>
Subject: Re: invent inode docs
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.980127160034.1230E-100000@is>
References: <3 DOT 0 DOT 1 DOT 32 DOT 19980127075128 DOT 007ee3b0 AT yacker DOT xiotech DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

At 04:11 PM 1/27/98 +0200, you wrote:
>You mean Fileutils, yes?
(rub-eyes, sip coffee, check archives).. yes, you are correct!  Building a
sh-utils for stty is another on my "to try" list.  I doubt stty is useful
for anyone else, but it is a way to help identify issues related to
building a /dev/ttyS* fsext that behaves unixy or atleast linuxy.

>So what do you put into st_dev?
1+'z'-'a' for anything other than a file that should appear in a drive's
file space.

>st_dev up to 31, and we use -1 for character devices, so you can use 
>anything that's beyond 31.

Can -1 be recommended for all character devices? (like /dev/ttyS* and such)

>If this is too complex and too much code, then probably your solution is 
>better.  Just make sure it handles all the quirks and subtleties.

I would agree avoiding putting it into djgpp for as long as possible.
Especially since there probably is an easier way..

all the best,
Randy