From: Peter Humphrey <prh@gotadsl.co.uk>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Terminal control codes
Date: Mon, 29 Jan 2007 17:13:52 +0000 [thread overview]
Message-ID: <200701291713.52279.prh@gotadsl.co.uk> (raw)
In-Reply-To: <200701291543.12012.pauldv@gentoo.org>
On Monday 29 Jan 2007, Paul de Vrieze wrote:
> On Sunday 14 January 2007 18:36, Peter Humphrey wrote:
> > On Tuesday 02 January 2007 17:09, I wrote:
> > > Secondly, another FAQ says to send setterm codes to /dev/vc/X, but
> > > since (I assume) the rise of udev those devices don't exist any more.
> >
> > Can anyone help me here? I need to know where to send "setterm -blank
> > 0" to prevent screen blanking on vc1-6 and 12. Or have I to find the
> > blanking code in the source (which source?) and switch it off there?
> > Maybe there's an option to a configure script somewhere.
>
> Try /dev/vcs{1..12} or /dev/tty{1..12}
Nice idea, but no joy. From a little code skimming I've done it seems
that /dev/vcsN is the text content of the console, while /dev/vcsaN is
its "text/attributes", whatever that means. I assume that /dev/ttyN is just
the device to which a program sends things for display.
It looks as though a new format of codes is needed to switch blanking off:
perhaps an escape string? That's a straw I'm clutching at, notice ;-)
--
Rgds
Peter
--
gentoo-amd64@gentoo.org mailing list
prev parent reply other threads:[~2007-01-29 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 17:09 [gentoo-amd64] Terminal control codes Peter Humphrey
2007-01-03 4:06 ` [gentoo-amd64] " Duncan
2007-01-14 17:26 ` Peter Humphrey
2007-01-14 17:36 ` [gentoo-amd64] " Peter Humphrey
2007-01-29 14:43 ` Paul de Vrieze
2007-01-29 17:13 ` Peter Humphrey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200701291713.52279.prh@gotadsl.co.uk \
--to=prh@gotadsl.co.uk \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox