> From: Bruce Dubbs <[email protected]> > Date: Tue, 13 Dec 2016 10:24:58 -0600 > Subject: Re: [blfs-dev] drop modemmanager? > > akhiezer wrote: > >> From [email protected] Tue Dec 13 10:45:39 2016 > >> Date: Tue, 13 Dec 2016 10:45:26 +0000 > >> From: [email protected] (akhiezer) > >> To: BLFS Development List <[email protected]> > >> Subject: Re: [blfs-dev] drop modemmanager? > >> > >>> From: "Douglas R. Reno" <[email protected]> > >>> 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 <[email protected]> > >>> 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-...' .) > > We were acknowledging ignorance, not in building MM, but in > configuring/testing. >
It is at least reasonably obvious that it is the immediately-preceding para that was being addressed; and the other materials retained for overall context for the overall note. > > >> 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/NetworkManager/ > >> [ ] 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 > >> ---- > >> > > This is useful/helpful. > > >> (NB though that 'apparently' b/lfs dev(s) opine(s) that it must be > >> unusable on Slackware.) > > Why the personal slights? I would be much more appreciative of the help > without them. Ditto. > > I have heard the saying before: All of us are a lot more knowledgeable > than any one of us. > And again. hth, akh -- -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
