Antonio, On Sat, Feb 27, 2010 at 08:11:40PM -0600, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Nikolay, > > Wvdial is an excellent tool, it is recommended to have, but not > required. Most distros come with kppp and some use Gnome PPP which is > a frontend for wvdial. I agree. Since recommending the wvdial is a recurring theme on the list, and since people sometimes do not read ModemData.txt before sending it to the list, I thought that the recommendation can be made by the scanModem tool more explicitly. > Also wvdial exists on other distributions like Fedora, OpenSuse, > moreover there are distributions like Slackware which do not carry it, > but going to Slackbuilds.org > > http://slackbuilds.org/repository/13.0/network/wvdial/ > but one needs wvstreams also > http://slackbuilds.org/repository/13.0/libraries/wvstreams/ > > and applying the scripts one can build wvdial packages for it. Well, there are a lot of things Slackware doesn't carry :) At this point, it is basically a toolbox for building embedded/ special purpose distributions. > What I have some questions about is the lsb-release. > Some distributions don't follow Linux Standard Base. How does it make > a difference with respect to wvdial? I don't think it makes any difference for wvdial. However, under Ubuntu, the lsb_release utility is available and can be used to find the codename of the release and the corresponding wvdial *.zip package. BTW shouldn't 'apt-get install wvdial' just do its job? Why is there a need for a dedicated *.zip file on http://linmodems.technion.ac.il/packages/ ? -- Nick Zhuravlev www.auriga.com > > /etc/lsb-release not found > > Regards, > > Antonio > > On 2/27/10, Nikolay Zhuravlev <xxor@xxxxxxx> wrote: > > Marvin/All, > > > > It seem to happen pretty often that people need to be reminded > > here in the list about installing the wvdial package first. > > Maybe scanModem could be modified to instruct a user to > > install the wvdial and then rerun the scanModem. > > This important bit of info seems to get lost in ModemData.txt > > > > And then scanModem could recognize the Ubuntu system and > > provide some more specific info like this: > > > > <<< > > if [ -f /etc/issue ] && grep -q Ubuntu /etc/issue; then cat <<EOF > > > > For Ubuntu users, there are at the bottom of > > http://linmodems.technion.ac.il/packages/ > > packages with the files necessary to install wvdial, with names like: > > EOF > > > > if lsb_release -c | grep -q jaunty; then cat <<EOF > > wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems. > > wvdial_jaunty_i386.zip for 32 bit systems. > > EOF > > > > elif lsb_release -c | grep -q karmic; then cat <<EOF > > wvdial_karmic_i386.zip for 32 bit systems. > > EOF > > else cat <<EOF > > wvdial_*.zip > > EOF > > fi > > cat <<EOF > > These are about 1 MB in size. After downloaded and copied into your > > Linux partition: > > $ unzip wv*.zip > > Within the new folder: > > $ sudo dpkg -i *.deb > > will complete the wvdial installation > > Please read Modem/DOCs/wvdial.txt for usage information. > > EOF > > fi > >>>> > > > > -- > > Nick Zhuravlev > > www.auriga.com > > > > > > On Sat, Feb 20, 2010 at 07:52:01AM -0500, Marvin Stodolsky > > <marvin.stodolsky@xxxxxxxxx> wrote: > > > >> Divesh > >> > >> The dialer utility package WVDIAL does not appear to be installed on > >> your System. > >> For Ubuntu users, there are at the bottom of > >> http://linmodems.technion.ac.il/packages/ > >> packages with the files necessary to install wvdial: > >> wvdial_karmic_i386.zip for 32 bit systems. > >> These are about 1 MB in size. After downloaded and copied into your > >> Linux partition: > >> $ unzip wv*.zip > >> Within the new folder: > >> $ sudo dpkg -i *.deb > >> will complete the wvdial installation > >> Please read Modem/DOCs/wvdial.txt for usage information > >> > >
