From: wonge@fraser.sfu.ca (Edmund Wong)
Subject: Yes! Remote login works... kinda... 
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Wed, 30 Dec 1992 11:19:47 GMT


    Hi all.  I'm sure some of you may have realized that I've
been on c.o.l. for some time and have regularly bothered most of
you 'bout remote logins.

    Well, I KINDA have it working.  Not necessarily the BEST idea,
but here's how I got it working.  I KNOW it's the the BEST way, but
hey.   

     When someone phones in, I just login as a root, and do a
"getty -h 2400 ttys1".  And they see the prompt a few seconds after
connection.  HOWEVER, the problem with this is:-

    1) I am NOT gonna sit in front of the terminal all day to
       execute that command whenever someone phones in.

    2) When the person logs off, the person's id is still 'logged'
       on, well, when I do a 'w', it shows the person still on,
       even if the guy is logged off!! 

    3) Related to 2, somehow, when that happens, the modem is
       locked, so I can't use minicom or anything.  Kermit is
       alright.  Does anyone know how to unlock /dev/modem?

     So basically, what I did was umm.. 'cheating', so to speak.
     
      Right now, when the computer reboots and loads the linux
stuff, it skips the usual 'init' stuff and therefore it bypasses
'inittab' FOR SOME UNKNOWN REASON.   Moreover, the 'getty' and
'uugetty' is not setup at all.  I don't know what I did to the system
to get it COMPLETELY IGNORING the INIT sequence, or even the
'rc' sequence!!! ARGGh.... 

      So right now, the following happens when I reboot and
when linux reloads:-

     ttys0 at 0x03f8 (irq = 4) is a 16450
     ttys1 at 0x02f8 (irq = 3) is a 16450
     8 virtual consoles
     lp_init: lp1 exists (0)
     No Logitech bus mouse detected.
     No PS/2 type pointing device detected.
     No Microsoft bus mouse detected.
     No ATI bus mouse detected
     Memory: 6640k/8448k available (356k kernel, 384k reserved, 68k data)
     Floppy drive(s): fd0 is 1.2M, fd1 is 1.44M
     sock_init: initializing family 1 (AF_UNIX)
     scsi : 0 hosts.
     scsi : detected 0 SCSI disks 0 tapes 0 CD-ROM drives total.
     hda :
       part 1 start 53 size 135362 end 135414
       part 2 start 135415 size 103350 end 238764
     Partition table ok.
     Linux version 0.98.pl1-37 (root@softland) 10/12/92 14:54:40

     Softlanding Software (604) 360-0188, ...
     Welcome to Linux SLS .98.p5.  Type "menu" for a menu driven interface

     login:


  So like, it skips the 'init' part.  HOW do I know that?  Well, before
I screwed around with the system, it gave me MAJOR "socket" errors,
and stuff like that... Somehow I prefer it not throwing out errors,
but when it ignores my inittab or whatever, then something must be done.

  My question, after all the background information is given, is
WHY is it skipping the 'init' sequence where it checks for the
'tty's and the ttys's?   Related to the opening sequence of events,
how do I get it to display "(root@eagles)" <or something else> instead
of "(root@softland)"?  

  So can I take it, from the above info, that my TCP/IP ISN'T setup
properly, and if so, how do I set it up?  

 Anyhow, I'm PLEADING for some help here...  

  Pleeeez... preeetttyy pleeeez can someone help me....???
<grin-I hope my grovelling might persuade someone to help me> :)
 

      
-- 
InterNet: wonge@fraser.sfu.ca  |  "Fail not; Learn Not.
                               |  It is with failing, that one learns,
                               |  So by Learning, one must fail." - Edmund Wong
Newsgroups: comp.os.linux