On Tue, Dec 13, 2016 at 5:22 AM, Douglas R. Reno <renodr2...@gmail.com> wrote:
> > > On Tue, Dec 13, 2016 at 4:45 AM, akhiezer <lf...@cruziero.com> wrote: > >> > From: "Douglas R. Reno" <renodr2...@gmail.com> >> > Date: Mon, 12 Dec 2016 20:39:58 -0600 >> > Subject: Re: [blfs-dev] drop modemmanager? >> > >> > On Mon, Dec 12, 2016 at 8:36 PM, Bruce Dubbs <bruce.du...@gmail.com> >> wrote: >> > >> > > Looking at http://wiki.linuxfromscratch.org/blfs/ticket/8569, I am >> > > wondering if we should drop modemmanager from BLFS. I have no idea >> how it >> > > should be used and I don't think any devs know how to test it. >> > > >> > > I looked at a couple of references on line and it apparently can be >> used >> > > for sending or receiving cell phone text messages. >> > > >> > > In any case, if we keep in in the sysV book, we appear to need a boot >> > > script. >> > > >> > > Does anyone have more insight into this package? >> > > >> > >> > Go ahead and drop it from sysv. >> > >> > It is *required* for GNOME on systemd. I also have some experience with >> > this package as it is required for tethering a cell phone on the CDMA >> > network to a computer for data purposes. I do it all the time when I'm >> in a >> > remote area. >> > >> > The simple answer is: It's not usable on sysv. It requires systemd to >> spawn >> > the D-Bus service. That is one drawback to sysv IMO, I can't use my PC >> in a >> > remote area without being able to spawn that service. Again, why I use >> > systemd. >> >> >> ( - sounds like propaganda/fud/bllcks/'a-little-knowledge-...' .) >> >> >> I'm sorry, please try to clarify without making me mad further. > > >> Slackware uses modemmanager no-probs: >> ---- >> http://slackware.uk/slackware/slackware64-current/source/n/ModemManager/ >> [TAR] ModemManager-1.4.14.tar.xz 16-Mar-2016 12:01 1.4M >> [SPT] ModemManager.SlackBuild 20-Dec-2015 06:04 3.1K >> [CMP] WeDoNotHaveSystemD.patch.gz 22-Sep-2013 22:10 444 >> [TXT] slack-desc 31-Mar-2016 21:46 832 >> -- >> http://slackware.uk/slackware/slackware64-current/source/n/N >> etworkManager/ >> [ ] 55NetworkManager 22-Mar-2016 18:59 938 >> [TAR] NetworkManager-1.2.2.tar.xz 11-May-2016 13:03 3.6M >> [SPT] NetworkManager.SlackBuild 13-Jun-2016 04:25 5.8K >> [TXT] NetworkManager.conf 22-Apr-2016 04:58 139 >> [DIR] conf.d/ 25-Mar-2016 04:54 - >> [SPT] doinst.sh 25-Mar-2016 04:35 1.2K >> [TXT] rc.networkmanager 25-Mar-2016 22:57 2.6K >> [TXT] slack-desc 08-Oct-2013 05:28 1.0K >> ---- >> >> >> (NB though that 'apparently' b/lfs dev(s) opine(s) that it must be >> unusable on Slackware.) >> >> >> >> akh >> >> >> >> > I didn't check Slackware. I should have, because I can't think of any > other distros currently that still use sysv. The question is - does it work > on Slackware? > OK, to clear up the air after any mean-spirited snapback I might have done above, here's a patch to fix it for sysv (courtesy of Slackware, thanks Akh): -# This D-Bus service activation file is only for systemd support since -# an auto-activated ModemManager would be quite surprising for those people -# who have MM installed but turned off. Thus the Exec path available to -# D-Bus is /bin/false, but systemd knows the real Exec path due to the MM -# systemd .service file. - [D-BUS Service] Name=org.freedesktop.ModemManager1 -Exec=@sbindir@/ModemManager +Exec=/usr/sbin/ModemManager User=root -SystemdService=dbus-org.freedesktop.ModemManager1.service ModemManager should be spawned when D-Bus feels the need (probably triggered by eudev, come to think of it).
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
