creating tty's, mknod, stuck after boot with wrong tty - help

creating tty's, mknod, stuck after boot with wrong tty - help

Post by David E Be » Wed, 30 Jun 1993 02:12:26

hi linuxers,

it was a silly thing to do (as somebody already said to me) , but somehow
I deleted my tty1 and console...
Because I was/am quite unexperienced with UNIX I tried several things
and found out about the mknod command.
I did the mknod c 4 1 for the console and c 2 0 for the tty1.
it was working , but X had problems coming up (though I linked console)
then I tried to mknod tty1 like console (c 4 1 ) and I suppose it was
working fine, but I was too dumb to realise it !!
Peeping to MAKEDEV suggested to do mknod tty1 c 193 1 ..
(at least I read it this way...)
but exactly this closed my system tighly for any attempt...

Even booting is not of any help (tty1 is created wrong and console is linked)
Is there any chance to modify this or ... do .. I .. have.. to.. reinstall ??


being root is great (1 week ago) >> being root is hard.. (today) ;-)


University of Aberdeen / SCOTLAND               lab-tel: (224) 681818-53905
Ophthalmology / Immunology                      lab-fax: (224) 685158
AB9 2ZD         >>> LINUX or IMMUNOLOGY - that's the question !! <<<


1. tty-less processes with tty's open

We've been having problems with processes which apparently lose their
controlling tty but who keep that tty open.  (This is on a Sun 670
running SunOS 4.1.2.)  The symptoms are these.  When trying to telnet
into this machine, the login: prompt will be displayed for a short
time (around a second) but then the connection will be mysteriously
closed.  When trying to rlogin to this machine it's even more wacky.
I can rlogin to it, and have all my stuff in my .bash_profile run Ok,
but then when that finishes, the shell echoes "logout" and the
connection is closed.

Apparently, telnetd and rlogind are getting EOF (telnetd when it's
trying to read the login name and rlogind after it runs my shell).  We
can trace the problem to the fact that there are processes running
which, for some reason, have the "next available" tty open, so that
when telnetd/rlogind open these tty's, the open succeeds but then when
they try to read from such a tty, they get EOF.  The "offending
programs" vary.  Sometimes it's mailers (elm, pine, /usr/ucb/mail),
but that's probably because one of the primary uses of this machine is
email.  One time it was even lpr, just sitting there with no
controlling tty but yet with a tty open.  Needless to say, it's a pain
to have to remotely find out what the offending process is with
rsh/lsof/ps and then go kill it.

Does anybody have an explanation or maybe even a solution to this
problem?  Thanks in advance.

Gideon Glass

----------==========]]]]]]]]]]          [[[[[[[[[[==========----------

]]]]]]]]]]==========----------          ----------==========[[[[[[[[[[

2. 3c509 combo and bsdi

3. What's wrong with my tty ports?

4. Asynch disk I/O?

5. kernel can't see 2 network cards problem

6. What's wrong with this tty locking bash script?

7. Help with FTP in a script

8. SCO 5.0.5: Can't create /dev/tty, scoterm: no pty available errors.

9. How to map a tty port to another tty port

10. What is 'stty', 'term' & 'tty'

11. problems with tty, U469036 - bos.rte.tty.

12. - can one change tty modes for tty not stdio ?