Hello,
On Fri, May 20, 2005 at 04:17:43PM -0400, Richard B. Johnson wrote:
> Well I started out opening /dev/vcs, lseeking to 64, and writing
> a string. This "sort of" worked, but screen attributes got messed
> up so the "blue" screen attribute 0x17 ended up eventually being
> black.
/dev/vcsa != /dev/vcs !!!!
There are two different devices, as far as I remember, one is only for
the characters itself on the console, and one includes attributes as well ...
FYI Documentation/devices.txt:
0 = /dev/vcs Current vc text contents
1 = /dev/vcs1 tty1 text contents
[...]
128 = /dev/vcsa Current vc text/attribute contents
129 = /dev/vcsa1 tty1 text/attribute contents
- Gábor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
