[Ping sktsee] Re: Agere WinModem 56k on Thinkpad - Working!

NoOp glgxg at sbcglobal.net
Thu Jul 14 22:07:03 UTC 2011


On 07/14/2011 12:17 PM, sktsee wrote:
...
> The following line should read exactly:
> $ sudo update-rc.d martian start 45 2 3 4 5 . stop 55 0 1 6 .

$ sudo update-rc.d martian start 45 2 3 4 5 . stop 55 0 1 6 .
[sudo] password for gg:
update-rc.d: warning: /etc/init.d/martian missing LSB keyword
'required-start'

update-rc.d: warning: /etc/init.d/martian missing LSB keyword
'required-stop'

update-rc.d: warning: /etc/init.d/martian missing LSB keyword 'default-stop'

update-rc.d: warning: martian stop runlevel arguments (0 1 6) do not
match LSB Default-Stop values (none)
 Adding system startup for /etc/init.d/martian ...
   /etc/rc0.d/K55martian -> ../init.d/martian
   /etc/rc1.d/K55martian -> ../init.d/martian
   /etc/rc6.d/K55martian -> ../init.d/martian
   /etc/rc2.d/S45martian -> ../init.d/martian
   /etc/rc3.d/S45martian -> ../init.d/martian
   /etc/rc4.d/S45martian -> ../init.d/martian
   /etc/rc5.d/S45martian -> ../init.d/martian

> 
> As far as the warnings go, it looks like update-rc.d tightened up on 
> sysv script requirements as I don't remember getting those messages back 
> then, Anyway, it's easy to remedy. All you need is a section like the 
> following under #!/bin/sh in /etc/init.d/martian
> 
> ### BEGIN INIT INFO
> # Provides:    martian_modem
> # Required-Start:
> # Required-Stop:
> # Should-Start:
> # Default-Start:     2 3 4 5
> # Default-Stop:      0 1 6
> # Short-Description: martian modem driver
> ### END INIT INFO

Do I leave in:
### BEGIN INIT INFO
# Provides: martian_modem
# Default-Start: 2 3 4 5
# Short-Description: martian_modem
# Description: martian_modem
# Author: Stefan Puch
# Adjustments for 2006/11 release A. Chentsov
### END INIT INFO
> 
> By the time it starts everything that martian_modem requires to work 
> should already be running, so the Required/Should values are left blank.
> 
> Lastly, since you're having to restart the daemon in order to use efax, 
> there could be an issue with efax trying to lock /dev/ttySM0 but can't. 
> Check /var/lock and see if wvdial/gnome-ppp left a stale lock when it 
> closed.
> 

No stale lock. And gnome-ppp has the same issue:
--> WvDial: Internet dialer version 1.60
--> Cannot open /dev/ttySM0: Permission denied
--> Cannot open /dev/ttySM0: Permission denied
--> Cannot open /dev/ttySM0: Permission denied






More information about the ubuntu-users mailing list