From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: init/login problems
Date: Tue, 27 Apr 2004 23:01:24 -0600 [thread overview]
Message-ID: <001d01c42cdd$daf4d710$0a00a8c0@merlin> (raw)
In-Reply-To: <20040428030755.GA1653@lava-net.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The big problem your having I think is that you aren't listing the terminal
type on the command line for agetty. You have to do that or the program
won't know what terminal to emulate. Because your not listing one, it is
trying to use ttytype to find a mapping. That file is used to map specific
tty lines to specific terminal types. The solution is to specifically list
the terminal type. IN this case, the type should be linux and it should go
right after the tty line specification. So, your line should look like this:
c6:1235:respawn:/sbin/agetty 38400 tty6 linux
- ---
Joseph C. Lininger
jbahm@pcdesk.net
note, the following is used for automated processing. Please leave in tact
if quoting me in a reply.
Verification: 5eab38a77ac40416e075be8f50607ff7
- ----- Original Message -----
From: "Igor Gueths" <igueths@lava-net.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, April 27, 2004 9:07 PM
Subject: Re: init/login problems
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have both getty and agetty here. The only reason I switched was bc I
> thought perhaps Agetty was causing my problem. However, I might as well
> switch since it's clear that the getty program isn't the problem. Have
> you ever encountered behavior similar to what i described earlier? If so
> how did you fix it? Thanks!
> On Tue, Apr 27, 2004 at 10:05:26PM -0500, Gregory Nowak wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Sorry, I can't help, since I don't use getty.
>>
>> Greg
>>
>>
>> On Tue, Apr 27, 2004 at 11:02:37PM -0400, Igor Gueths wrote:
>> > Hi there. Upon further examination of syslog entries, I realize now
>> > that
>> > getty is complaining of a missing /etc/ttytype file. This file never
>> > existed to begin with. Any way I can perhaps create one? I've tried
>> > several different forms of syntax and getty appears to not like it.
>>
>> - --
>> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.3 (GNU/Linux)
>>
>> iD8DBQFAjx927s9z/XlyUyARApotAKDfMf1GWYiykUEXTVehSriaod7IFACfXbyq
>> NHPyQX6RW+ZUApfiVIpS1AA=
>> =ablk
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> - --
> Failure is not an option, it comes bundled with your Microsoft product.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFAjyAKNohoaf1zXJMRAobaAJ9Bi+u+/dHyhUOV0spScAdgUPvMzwCgjB2c
> 2wMmknztDcNJyWFdcQFa43c=
> =2akq
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
iQA/AwUBQI86oienap9Jqj2wEQILIQCg9Dxp+LdaW0RzJ6o163N9g1sZPOMAoIlV
zPQAuvnFx2nNexuuWZ6vwL1+
=9cCu
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Chuck Hallenbeck
` Joseph C. Lininger [this message]
` Joseph C. Lininger
` Igor Gueths
` Chuck Hallenbeck
` Alex Snow
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='001d01c42cdd$daf4d710$0a00a8c0@merlin' \
--to=jbahm@pcdesk.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).