home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!snorkelwacker.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!tytso
- From: tytso@athena.mit.edu (Theodore Y. Ts'o)
- Subject: Re: Can you access a virtual console directly?
- In-Reply-To: drew@kinglear.cs.colorado.edu's message of 14 Sep 92 17:49:31 GMT
- Message-ID: <TYTSO.92Sep14231653@SOS.mit.edu>
- Sender: news@athena.mit.edu (News system)
- Nntp-Posting-Host: sos.mit.edu
- Organization: Massachusetts Institute of Technology
- References: <1992Sep14.164729.28907@mits.mdata.fi> <1992Sep14.174931.2373@colorado.edu>
- Date: Tue, 15 Sep 1992 03:17:13 GMT
- Lines: 25
-
- In article <1992Sep14.174931.2373@colorado.edu> drew@kinglear.cs.colorado.edu (Drew Eckhardt) writes:
- >In article <1992Sep14.164729.28907@mits.mdata.fi> kennu@mits.mdata.fi (Kenneth Falck) writes:
- >>Can you access a linux virtual console directly, something like what
- >>you usually do with MSDOS when writing characters and attributes to
- >>B800:xxxx?
- >
- >Maybe, but you shouldn't.
- >
- >If you want to write to the buffer directly, you'll have to write
- >/dev/kmem, using the addresses specified in the kernel NLIST. This is
- >non-portable, and there are no gurantees that the internal structures
- >won't change in the next release.
-
- More importantly, if you have to write to /dev/kmem, you derive *no*
- speed advantage over writing to /dev/tty. Trying to write to the
- virtual console's memory is just a bad idea.
-
- Also, as Drew already pointed out, such a program wouldn't work over MGR
- or X11; and most people will probably end up running X11, or possible
- MGR, so it wouldn't be a very useful terminal program.
-
- Speaking of which, why do you want to write your own terminal program?
- What's wrong with kermit that you want to re-invent your own wheel?
-
- - Ted
-