> Date: Fri, 19 Apr 1996 02:18:50 -0400
> From: Chris G Demetriou <Chris_G_Demetriou@UX2.SP.CS.CMU.EDU>

> > To get this all in one file (/etc is cluttered enough, and I'd rather
> > not to have to consult two different files to see what's configured for
> > a single tty), I propose that a second field be added for the action
> > name (like my earlier proposal). Let it be glob matched as well,
> > and add ACTION to the environment too. Example:
> > 
> > # This line just needs one related device chown'ed
> > /dev/wsconsole	login	chown ${USER} /dev/wsmouse
> > /dev/wsconsole	logout	chown root /dev/wsmouse
> > # This line has several related devices, which are
> > # handled by the external program /etc/console.sh
> > /dev/kdconsole	*	/etc/console.sh ${ACTION}
> 
> again, i'd really like to get rid of the full paths in the tty name
> field, and replace them with the names used in /etc/ttys, unless
> there's a good reason not to.

Ah, I get it now!  Duh!  (An example would have helped, Chris 8^)
So, you want the file format to look something like this: (right?)

	# device name (without /dev/) (spaces/tabs) command...
	wsconsole		chown $USER /dev/wsmouse

> as for specifying both login and logout, sounds reasonable to me, and
> allowing that to be wildcarded, sounds reasonable to me as long as
> there's not too much implementation hair.

It looks a little hairy to me.  Maybe Ty would like to offer an
outline of the tty_relatives() function he proposes.

Gordon