markc@wpi.wpi.edu (Mark B. Cohen) (03/02/90)
First of all, I'd like to thank everyone who responded to my
query regarding the ulimit. Had the csh limit command given
me a reasonable response, I probably would have not gone
off on the wrong track.
A new question:
The discussions in c.s.i.p(.p) and c.u.i386 regarding
screen blankers have gotten me intrigued. Is there such
an animal as a screen blanker for which will run under
uPort?
Also:
Is there a device or parameters for a mknod which would
always refer to the _current foreground console_?
That is to say: The (virtual) console currently being
displayed on the monitor. I know that /dev/tty always
refers to the process' terminal -- not the current screen.
I'd like to use this device for several applications.
First, should I end up writing my own screen blanker,
what I would do is have a deamon monitor the last
access/read/write time of this device, and if the
elapsed time reaches a certain value, blank the screen.
Another application I have in mind is for notification
deamons. When some system/external event occurs, I'd
like a notificaton message available on the screen.
Using wall(1) would not work because I'd like the message
to be output on the currently displayed screen, even if the
only process associated with that console is a getty.
I don't think even directly accessing the video memory would
work in this case, since the deamon would still need to know
which page to use.
Lastly:
Are there any sources available for csh-type shells?
There are some things I'd like to to change and fix
-- including the internal limit command. :-)
If anyone has pointers to a csh source and would like
to modify it for the Ohio State tcsh extensions, diffs
are available for anon ftp here at wpi.wpi.edu [130.215.24.1]
Thanks again,
and TIA too.
Mark Cohen
--
Internet: markc@wpi.wpi.edu "This is drugs...
UUCP: uunet!wpi.wpi.edu!markc this is your brain...
BITnet: markc@wpi.bitnet this is your breakfast."