Sponsored Content
Full Discussion: TTY Insane
Top Forums UNIX for Dummies Questions & Answers TTY Insane Post 302349349 by danny.hudson on Monday 31st of August 2009 06:15:23 PM
Old 08-31-2009
eeprom from remote machine shows the following for ttya-mode...

ttya-mode=9600,8,n,1,-

Is the trailing hyphen a problem?

All this worked fine until a few days ago...?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Insane question : Playing mp3 file from Sun Sparc

hi, i know this is crazy. but i can do this from linux in intel platform. just wonder can my Sun Solaris 8 sparc can do the same thing? (2 Replies)
Discussion started by: champion
2 Replies

2. AIX

tty

Hi All can anyone tell me what is the meaning of tty,or give me an example of this? (1 Reply)
Discussion started by: magasem
1 Replies

3. AIX

Tty Over Run

dears i have two IBM p630 application servers, they are running hacmp 5.2 as the clustering software. from the output of errpt on one of the nodes i am receiving the following error: 9D30B78E 0530020007 T S tty1 RECEIVER OVER-RUN ON INPUT please are there any ideas about how... (0 Replies)
Discussion started by: TheEngineer
0 Replies

4. UNIX for Dummies Questions & Answers

pts and tty

hi iam very new to linux can anyone tell me about pts and tty acctually today morning i logged into my pc at 9:51 when i have given #who it has given sam tty7 9:51 sam pts/1 10:11 so what does it mean (1 Reply)
Discussion started by: praneel2k
1 Replies

5. Solaris

tty hack

hi all, what i want to do when user open terminal like tty5 and do his work i want to see his terminal how can i do this (1 Reply)
Discussion started by: xxmasrawy
1 Replies

6. UNIX for Advanced & Expert Users

tty changes?

I am not sure if I am using the correct terminology but somehow my tty keeps changing on me. The man pages are confusing to me on what exactly the tty is. This is what I see when I run the tty command. Could anyone explain why my tty keeps changing? ~ $ tty /dev/pts/1 ~ $ tty /dev/pts/0 (6 Replies)
Discussion started by: cokedude
6 Replies

7. Shell Programming and Scripting

Insane redirection behavior

Hi guys, I know computers don't misbehave. But I'm puzzled by what's happening right know in a script : I simplified the example to point out what seems weird to me. Don't try to find any sense to this stupid script. There are 10 rows in /tmp/tmp.txt i=0 tmpfile=/tmp/tmp.txt while... (3 Replies)
Discussion started by: chebarbudo
3 Replies

8. Solaris

Installing software -going insane

I have Solaris 10 update 11 installed on a virtual machine which I use for my lunix class (I'm studying I.T. but have little unix experience). So I have root access* I'm also do C programming in my course and would love to do it on my Solaris machine. So I looked into installing GCC and... (5 Replies)
Discussion started by: goformickey
5 Replies

9. Shell Programming and Scripting

Python: Redirecting to tty and reading from tty

In bash, you can do something like this: #!/bin/bash echo -n "What is your name? " > /dev/tty read thename < /dev/tty How can I do the same in python? I have a python script that has the following content: #!/usr/bin/python2.7 import getpass import sys import telnetlib import... (2 Replies)
Discussion started by: SkySmart
2 Replies
EEPROM(8)						    BSD System Manager's Manual 						 EEPROM(8)

NAME
eeprom -- display or modify contents of the EEPROM or openprom SUN 3 SYNOPSIS eeprom [-] [-c] [-f device] [-i] [field[=value] ...] SPARC, SPARC64, MACPPC and PREP SYNOPSIS eeprom [-] [-c] [-f device] [-i] [-v] [field[=value] ...] DESCRIPTION
eeprom provides an interface for displaying and changing the contents of the EEPROM or openprom. The eeprom tool is only installed on sup- ported platforms. Without any arguments, eeprom will list all of the known fields and their corresponding values. When given the name of a specific field, eeprom will display that value or set it if the field name is followed by '=' and a value. Only the super-user may modify the contents of the EEPROM or openprom. The options are as follows: - Commands are taken from stdin and displayed on stdout. -c eeprom will fix incorrect checksum values and exit. This flag is quietly ignored on systems with an openprom. -f device On systems with an EEPROM, use device instead of the default /dev/eeprom. On systems with an openprom, use device instead of the default /dev/openprom. -i If checksum values are incorrect, eeprom will ignore them and continue after displaying a warning. This flag is quietly ignored on systems with an openprom. The following options are valid only on the SPARC and will produce an error when used on a Sun 3: -v On systems with an openprom, be verbose when setting a value. Systems with an EEPROM are always verbose. The -v option is also present on sparc64, macppc, and prep systems. FIELDS AND VALUES
The following fields and values are for systems with an EEPROM: hwupdate A valid date, such as ``7/12/95''. The strings ``today'' and ``now'' are also acceptable. memsize How much memory, in megabytes, is installed in the system. memtest How much memory, in megabytes, is to be tested upon power-up. scrsize The size of the screen. Acceptable values are ``1024x1024'', ``1152x900'', ``1600x1280'', and ``1440x1440''. watchdog_reboot If true, the system will reboot upon reset. Otherwise, the system will fall into the monitor. default_boot If true, the system will use the boot device stored in bootdev. bootdev Specifies the default boot device in the form cc(x,x,x), where 'cc' is a combination of two letters such as 'sd' or 'le' and each 'x' is a hexadecimal number between 0 and ff, less the prepending '0x'. kbdtype This value is ``0'' for all Sun keyboards. console Specifies the console type. Valid values are ``b&w'', ``ttya'', ``ttyb'', ``color'', and ``p4opt''. keyclick If true, the keys click annoyingly. diagdev This is a string very similar to that used by bootdev. It specifies the default boot device when the diagnostic switch is turned on. diagpath A 40-character, NULL-terminated string specifying the kernel or standalone program to load when the diagnostic switch is turned on. columns An 8-bit integer specifying the number of columns on the console. rows An 8-bit integer specifying the number of rows on the console. ttya_use_baud Use the baud rate stored in ttya_baud instead of the default 9600. ttya_baud A 16-bit integer specifying the baud rate to use on ttya. ttya_no_rtsdtr If true, disables RTS/DTR. ttyb_use_baud Similar to ttya_use_baud, but for ttyb. ttyb_baud Similar to ttya_baud, but for ttyb. ttyb_no_rtsdtr Similar to ttya_no_rtsdtr, but for ttyb. banner An 80-character, NULL-terminated string to use at power-up instead of the default Sun banner. Note that the secure, bad_login, and password fields are not currently supported. Since the openprom is designed such that the field names are arbitrary, explaining them here is dubious. Below are field names and values that one is likely to see on a system with an openprom. NOTE: this list may be incomplete or incorrect due to differences between revisions of the openprom. sunmon-compat? If true, the old EEPROM-style interface will be used while in the monitor, rather than the openprom-style interface. selftest-#megs A 32-bit integer specifying the number of megabytes of memory to test upon power-up. oem-logo A 64bitx64bit bitmap in Sun Iconedit format. To set the bitmap, give the pathname of the file containing the image. NOTE: this property is not yet supported. oem-logo? If true, enables the use of the bitmap stored in oem-logo rather than the default Sun logo. oem-banner A string to use at power up, rather than the default Sun banner. oem-banner? If true, enables the use of the banner stored in oem-banner rather than the default Sun banner. ttya-mode A string of five comma separated fields in the format ``9600,8,n,1,-''. The first field is the baud rate. The sec- ond field is the number of data bits. The third field is the parity; acceptable values for parity are 'n' (none), 'e' (even), 'o' (odd), 'm' (mark), and 's' (space). The fourth field is the number of stop bits. The fifth field is the 'handshake' field; acceptable values are '-' (none), 'h' (RTS/CTS), and 's' (Xon/Xoff). ttya-rts-dtr-off If true, the system will ignore RTS/DTR. ttya-ignore-cd If true, the system will ignore carrier detect. ttyb-mode Similar to ttya-mode, but for ttyb. ttyb-rts-dtr-off Similar to ttya-rts-dtr-off, but for ttyb. ttyb-ignore-cd Similar to ttya-ignore-cd, but for ttyb. sbus-probe-list Four digits in the format ``0123'' specifying which order to probe the sbus at power-up. It is unlikely that this value should ever be changed. screen-#columns An 8-bit integer specifying the number of columns on the console. screen-#rows An 8-bit integer specifying the number of rows on the console. auto-boot? If true, the system will boot automatically at power-up. watchdog-reboot? If true, the system will reboot upon reset. Otherwise, system will fall into the monitor. input-device One of the strings ``keyboard'', ``ttya'', or ``ttyb'' specifying the default console input device. output-device One of the strings ``screen'', ``ttya'', or ``ttyb'' specifying the default console output device. keyboard-click? If true, the keys click annoyingly. sd-targets A string in the format ``31204567'' describing the translation of physical to logical target. st-targets Similar to sd-targets, but for tapes. The default translation is ``45670123''. scsi-initiator-id The SCSI ID of the on-board SCSI controller. hardware-revision A 7-character string describing a date, such as ``25May95''. last-hardware-update Similar to hardware-revision, describing when the CPU was last updated. diag-switch? If true, the system will boot and run in diagnostic mode. FILES
/dev/eeprom The EEPROM device on systems with an EEPROM. /dev/openprom The openprom device on systems with an openprom. /dev/nvram The nvram device on PReP systems. SEE ALSO
ofctl(8) BUGS
The fields and their values are not necessarily well defined on systems with an openprom. Your mileage may vary. There are a few fields known to exist in some revisions of the EEPROM and/or openprom that are not yet supported. Most notable are those relating to password protection of the EEPROM or openprom. Avoid gratuitously changing the contents of the EEPROM. It has a limited number of write cycles. The date parser isn't very intelligent. BSD
February 27, 2007 BSD
All times are GMT -4. The time now is 03:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy