The reason your mgetty entry in inittab doesn't cause mgetty to run is that
you don't have it running on your default runlevel. Putting aside the small
inconsistencies in the two versions of the line you posted (namely,
>My string in inittab is as below
>
>s1:45:respawn:/sbin/mgetty 38400 /dev/modem /etc/ppp/conf.mgetty.ttyS1
>vt100
and the one from the full inittab,
>s1:456:respawn:/sbin/mgetty /dec/modem /etc/ppp/conf.mgetty.ttyS1 vt100
)
the problem is that your default runlevel is level 3, specified by this
inittab line:
>id:3:initdefault:
Since you have the modem mgetty running only on runlevels 4, 5, and maybe 6,
it doesn't start. To fix this, add a 3 to the second field in the s1 line.
Also, fix the "/dec/modem" entry in the second version (should be
/dev/modem" if that wasn't just a typo in your e-mail). Don't know if you
have to specify the 38400 or not; try it both ways and see which works, I guess.
At 11:05 AM 4/22/99 -0600, Jacob (Mettavihari) wrote [abridged]:
>I found the file mgetty and set that in inittab,
>but it would not come up when rebooting.
>
>When I mannually install it with the command
>/sbin/mgetty /dev/modem -s 38400 vt100
>then it get up and ps -ax finds it.
>and I am able to login at 19200
>
>My string in inittab is as below
>
>s1:45:respawn:/sbin/mgetty 38400 /dev/modem /etc/ppp/conf.mgetty.ttyS1
>vt100
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
