[Fwd: Re: scanmodem failing on ubuntu edgy]

[Alexandre Strube - UAB]

I am not sure where I should post a bug on this. I've been talking to
Marvin, the Linmodem's scanmodem script maintainer, and the discussion
follows:


--------- Mensaje reenviado --------
> De: Marvin Stodolsky <marvin.stodolsky at gmail.com>
> Para: discuss at linmodems.org
> Cc: Alexandre Strube <surak at surak.eti.br>
> Asunto: Re: scanmodem failing on ubuntu edgy
> Fecha: Wed, 1 Nov 2006 03:37:45 -0500
> 
> Alexandre  is correct that scanModem is broken on the new Ubuntu Edgy release,
> and likely on some other releases using new versions of common utilies.
> 
> I just did an Egdy install.  Testing revealed that the scanModem
> script is broken in several places thereunder.  Sudo, lspciand source
> Utilities are behaving in novel ways, which I don't fully understand
> yet. The source command is refusing to read (Permission denied)  the
> scanout.* working files, which is used for writing out the diagnostic
> outputs in simple simple English.  There are also additional spaces in
> some diagnostic output lines, breaking  some parses which I'll have to
> work through.
> 
> Fortunately, I retained my Ubuntu Dapper functional in another partition.
> 
> MarvS
> scanModem maintainer
> 
> 
> 
> 
> On 10/27/06, Marvin Stodolsky <marvin.stodolsky at gmail.com> wrote:
> > Alex
> >
> > The various ID settings are in the /etc/group  or /etc/groups  files
> > (not under Linux now).
> > Send that file to us from your Edgy installation.
> >
> > With respect to finding utilities like lspci, scanModem searches through
> > /bin  /sbin/  /usr/bin  and /usr/sbin
> >
> > MarvS
> >
> > On 10/27/06, Jacques Goldberg <Jacques.Goldberg at cern.ch> wrote:
> > > OK OK OK I pull back my statement.
> > >
> > > If I would have been an Ubuntu user I might have known that they put
> > > things at other places.
> > >
> > > Just to fool standard scripts perhaps - and changing the behaviour of
> > > test, just to make sure.
> > >
> > > I hope that you understand that this is  a joke and it is not directed
> > > against you in anyway:
> > >
> > >
> > > What if Ubuntu might be a "product" of Bill Gates's brain to drive
> > > people away from Linux back to eXtraPain, by making it UNIX
> > > non-complying ? ; ) ;) ;)
> > >
> > > You know, people going away because "nothing works"!
> > >
> > >
> > > Jacques
> > >
> > >
> > > Alexandre Strube wrote:
> > >
> > > > Em Sex, 2006-10-27 às 11:48 +0200, Jacques Goldberg escreveu:
> > > >
> > > >
> > > >> And, again, since "I am not an Ubuntu user, even less an Ubuntu Edgy
> > > >> one.", I wonder why do you look for lspci in /usr/bin since I have never
> > > >> seen it elsewhere that in /sbin .
> > > >>
> > > >
> > > > Jacques, that wasn't me. That was the output of scanmodem using the
> > > > command set -vx for debug output. I just cut from the whole output for
> > > > clearness.
> > > >
> > > >
> > > >> Perhaps you should do
> > > >> find / -name lspci
> > > >> to ascertain where this command resides in your machine.
> > > >>
> > > >
> > > > # locate lspci
> > > > /usr/share/man/man8/lspci.8.gz
> > > > /usr/bin/lspci
> > > > /bin/lspci
> > > >
> > > >
> > > > What made me think that the test command is somehow different is the
> > > > fact that it fails both in lspci as well as when it tests for the root
> > > > account. See the output of the test below (marked as **HERE**). Notice
> > > > that it lacks the content of $UID.
> > > >
> > > >
> > > >
> > > >
> > > >> Alexandre Strube wrote:
> > > >>
> > > >>> Running it with "set -vx", I noticed that the following test fails:
> > > >>>
> > > >>> if test "$UID" != 0 ; then
> > > >>>
> > > >     ^^^^^^^^^^^^^^^^^^^------------- This test
> > > >
> > > >>>   echo Run with Root permission:
> > > >>>   if test -n "$SUDO" ; then
> > > >>>     echo sudo $0
> > > >>>   else
> > > >>>     echo $ su - root
> > > >>>     echo # $0
> > > >>>   fi
> > > >>>   echo
> > > >>>   exit
> > > >>> fi
> > > >>>
> > > > **************** HERE *********************
> > > >
> > > >>> + test  != 0
> > > >>>
> > > > **************** HERE *********************
> > > >
> > > >>> + echo Run with Root permission:
> > > >>> Run with Root permission:
> > > >>> + test -n sudo
> > > >>> + echo sudo ./scanModem
> > > >>> sudo ./scanModem
> > > >>> + echo
> > > >>>
> > > >>> + exit
> > > >>>
> > > >>> The variable $UID, however, exists.
> > > >>> root at quad:/home/surak/Desktop# set |grep UID
> > > >>> EUID=0
> > > >>> SUDO_UID=1000
> > > >>> UID=0
> > > >>>
> > > >>> Ignoring this step makes it to fail later.
> > > >>>
> > > >>> It seems that the command "test" has been changed in edgy, because:
> > > >>> + test -z /usr/bin/lspci
> > > >>> + /usr/bin/lspci
> > > >>> (lbablabla lspci output)
> > > >>> 05:00.0 Communication controller: Agere Systems Unknown device 0620
> > > >>> +
> > > >>> + echo WARNING: /usr/bin/lspci returned error - not checking for modem
> > > >>> WARNING: /usr/bin/lspci returned error - not checking for modem
> > > >>> + echo
> > > >>>
> > > >>> + echo Exiting
> > > >>> Exiting
> > > >>> + echo
> > > >>>
> > > >>> + exit 1
> > > >>>
> > > >
> > > >
> > > >
> > >
> > >
> >