From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/2] wvdial: Add package
Date: Mon, 16 Oct 2017 14:42:58 +0200 [thread overview]
Message-ID: <20171016124258.ifkxltowsfi4lcap@pengutronix.de> (raw)
In-Reply-To: <20171016123641.n7riuoikvlgrjb6v@lenoch>
Hi Ladis,
On Mon, Oct 16, 2017 at 02:36:41PM +0200, Ladislav Michl wrote:
> On Mon, Oct 16, 2017 at 02:15:30PM +0200, Sascha Hauer wrote:
> > Back in the good old days wvdial was used to easily connect
> > a modem to the internet without having to write chat scripts
> > manually. Some people still use modems, so add support for
> > wvdial to ptxdist.
>
> What is the advantage using it over ModemManager in the good
> recent days (except size and legacy reasons)?
> This is serious question, I'm ready to kick ModemManager
> if this proves to be a better solution.
I did this on customer request for an ancient, pre-dbus powerPC system.
I doubt it's a better solution than ModemManager.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-10-16 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 12:15 [ptxdist] [PATCH 1/2] wvstreams: " Sascha Hauer
2017-10-16 12:15 ` [ptxdist] [PATCH 2/2] wvdial: " Sascha Hauer
2017-10-16 12:36 ` Ladislav Michl
2017-10-16 12:42 ` Sascha Hauer [this message]
2017-10-16 12:16 ` [ptxdist] [PATCH 1/2] wvstreams: " Sascha Hauer
-- strict thread matches above, loose matches on Subject: below --
2017-09-29 13:52 Sascha Hauer
2017-09-29 13:52 ` [ptxdist] [PATCH 2/2] wvdial: " Sascha Hauer
2017-09-30 11:02 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171016124258.ifkxltowsfi4lcap@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=ladis@linux-mips.org \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox