Re: [DNG] systemd files

[Steve Litt]

On Fri, 2 Mar 2018 10:26:39 +
KatolaZ  wrote:

> On Fri, Mar 02, 2018 at 10:04:23AM +, leloft wrote:
> > Hi devs,
> > I am sorry to be troubling you with what may be a waste of your
> > valuable time, but I have a couple of questions for the list.
> > Following on from the clamav-daemon problematic uninstallation,
> > posted here
> > https://lists.dyne.org/lurker/message/20180221.210210.37932ca6.en.html
> > I have seen the following code in
> > both /etc/logrotate.d/clamav-daemon.dpkg-old
> > and /etc/logrotate.d/clamav-freshclam. 
> > 
> > /var/log/clamav/freshclam.log {
> >  rotate 12
> >  weekly
> >  compress
> >  delaycompress
> >  missingok
> >  create 640  clamav adm
> >  postrotate
> >  if [ -d /run/systemd/system ]; then
> >  systemctl -q is-active clamav-freshclam && systemctl kill
> > --signal=SIGHUP clamav-freshclam || true else
> >  /etc/init.d/clamav-freshclam reload-log > /dev/null || true
> >  fi
> >  endscript
> >  }
> > 
> > But this code is not in any of the 16 other logrotate files in this
> > folder. I do not fully understand it, and so my first
> > question is are there any suggestions why it is there and why isn't
> > it necessary in the other files? I ask because I have uncovered an
> > alarming number of systemd files throughout the computer on which I
> > installed the clamav-daemon, and am concerned that there has been a
> > bit of liberty-taking by pro-systemd 'agendaware'.  
> 
> Hi,
> 
> It's probably just that the upstream package maintainer has made the
> assumption that Debian should only run systemd, and nothing else
> ever. You might call it pro-systemd 'agendaware', if you like.

"Agendaware" is the best neologism I've heard in the past 2 years. It
tells it like it is.

SteveT

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Can I Switch to Jessie Without re-installing?

[KatolaZ]

On Fri, Mar 02, 2018 at 11:52:40PM +0100, Adam Borowski wrote:
> On Thu, Mar 01, 2018 at 02:43:53PM -0800, Chime Hart wrote:
> > Thank you for the suggestion of Jessie where I can run Voxin.  Would their
> > be a command I can run to switch from ASCII?  Thanks so much in advance
> 
> Downgrading is officially not supported, but it generally works without a
> hitch.  The easiest way is apt pinning:
> 
> Write the following to /etc/apt/preferences :
> Package: *
> Pin: release n=jessie
> Pin-Priority: 1001
> 
> then "apt dist-upgrade".  Obviously, you need to have jessie sources in
> /etc/apt/sources.list to have something to downgrade to.
> 
> The documentation is in "man apt_preferences", TL;DR: priorities >= 100
> allow upgrading, priorities > 1000 allow downgrading.
> 
> You'd probably want to delete ascii sources and comment out the preferences
> afterwards, as it's a common pitfall to leave the pin in place then forget
> it's there, which can make waste your time troubleshooting.
> 
> 

I guess you should also have ascii pinned to -1, otherwise ascii deps
won't be downgraded...

  Package: *
  Pin: release n=ascii
  Pin-Priority: -1
  
My2Cents

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Can I Switch to Jessie Without re-installing?

[Adam Borowski]

On Thu, Mar 01, 2018 at 02:43:53PM -0800, Chime Hart wrote:
> Thank you for the suggestion of Jessie where I can run Voxin.  Would their
> be a command I can run to switch from ASCII?  Thanks so much in advance

Downgrading is officially not supported, but it generally works without a
hitch.  The easiest way is apt pinning:

Write the following to /etc/apt/preferences :
Package: *
Pin: release n=jessie
Pin-Priority: 1001

then "apt dist-upgrade".  Obviously, you need to have jessie sources in
/etc/apt/sources.list to have something to downgrade to.

The documentation is in "man apt_preferences", TL;DR: priorities >= 100
allow upgrading, priorities > 1000 allow downgrading.

You'd probably want to delete ascii sources and comment out the preferences
afterwards, as it's a common pitfall to leave the pin in place then forget
it's there, which can make waste your time troubleshooting.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] systemd files

[golinux]

On 2018-03-02 04:55, Antony Stone wrote:

On Friday 02 March 2018 at 11:26:39, KatolaZ wrote:


Most of those "alarming" files are just systemd units files, put there
by daemons/packages/utilities who "also" support systemd in a way or
another. So they are not alarming but just *totally* *harmless* if you
don't have a running systemd as PID 1, since only systemd understands
and can run them.  It would be *totally* *useless* (and utterly
*stupid* IMHO) to fork, rebuild, and maintain a few more hundred
packages only because they happen to provide a systemd unit file for
those systems where systemd is used.

libsystemd0 is used by some daemons to verify if systemd is running or
not. If it's not, libsystemd is *totally* *harmless*.

HND

KatolaZ

P.S.: I guess we should consider including the last two paragraphs
above on www.devuan.org, or put it in the mailing list signature...


Good idea, I think (on the website, anyway; we don't want something 
that long

on every list posting).


Antony.



I'm not so sure that the website is an appropriate place for that 
information. Why? Questions about the presence libsystemd0 would only 
arise after Devuan is installed so it is more of a support question. A 
version of of those paras could certainly be on the forum. And including 
that info in the release notes might also be a good idea.


golinux



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] pam_limits or limits.conf different from Debian?

[Irrwahn]

Patrick Dunford wrote on 02.03.2018 13:45:
> I did some more tweaking, and basically it looks like I have to set the hard 
> limit higher as well as the soft limit, in /etc/security/limits.conf
> 
> The hard limit in Debian must be set higher somewhere else, because you don't 
> have to set that one in the same file normally.
> 
[cut]

That is consistent with my own observations. On my desktop ASCII 
machine the hard limit for nofile appeared to be set to an arbitrary 
limit of 4096. Unfortunately I, too, have no clue by what mechanism 
this limit is pre-configured.

Note, however, that you can set both the hard and soft limits to 
the same value simultaneously in /etc/security/limits.conf by using 
a '-' (hyphen) in the  field (second column); for example:

 - nofile 32000


Best regards
Urban
-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] 3G modem support in devuan jessie network-manager

[Juergen Moebius]

Hi Arnt,

Am Freitag, den 02-03-2018 um 13:07 schrieb Arnt Karlsen:
> ..e.g. dmesg will often report missing driver firmware failures.

No, this is not a firmware problem.
Thanks for your answer, but i wrote that the modem is present
in the system! I forgot to say that "modem-manager.gui"
can full handle the modem, Sending SMS, Showing Provider,
Speed, Location and so on.
Only "network-manager" ignores the Modem, i think this
is a ugly bug in devuan jessie!!!

Also in the classic Slackware worked the modem with the
network-manager,  ans Slacky is very very spartan!

Greetings,
Juergen Moebius
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Network initialisation fail in Devuan 2.0

[Patrick Dunford]

Apologies if this already covered, I only got to this list recently.

When I start the VM the network comes up not functioning, and I have to 
put in ifdown and then ifup to get it working.


This is a Virtualbox VM and has the Virtualbox guest extensions installed.

TIA

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] pam_limits or limits.conf different from Debian?

[Patrick Dunford]

I did some more tweaking, and basically it looks like I have to set the 
hard limit higher as well as the soft limit, in /etc/security/limits.conf


The hard limit in Debian must be set higher somewhere else, because you 
don't have to set that one in the same file normally.


Thanks for your assistance.


On 02/03/18 21:28, KatolaZ wrote:

On Fri, Mar 02, 2018 at 02:13:15PM +1300, Patrick Dunford wrote:

No red flags for any of that stuff

On a Debian Buster VM where the increased file limit put into limits.conf
obviously works, the result of ulimit -n comes out the same 1024 as on my
Devuan VM.

The subtleties of why one distro would use one mechanism and a similar one a
different mechanism (apparently) are all the things that frustrate people
like me :)


The thing is that I guess Devuan ASCII has not (willingly) changed any
default in that respect, so the same problem might be present in
debian stretch.

This post:

   
https://stackoverflow.com/questions/46441602/how-to-change-open-files-ulimit-n-permanently-for-normal-user-in-debian-stret

suggests that libpam-systemd seems to ignore /etc/security/limits.conf
by default. The easy way to check is by logging in from a tty, and
looking at:

  $ ulimit -n

I tried it now, setting nofile to 2, and it correctly shows the
new value. Which polkit backend are you using? We might have inherited
an unwanted behaviour in libpam-elogind, possibly.

HND

KatolaZ



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] 3G modem support in devuan jessie network-manager

[Arnt Karlsen]

On Fri, 02 Mar 2018 11:09:05 +0100, Juergen wrote in message 
<49a0ea7c62f1817f00dfd58c016ea...@auk.ak-dyndns.org>:

> Hi,
> 
> have the network-manager in jessie support for 3G modems?
> 
> Wen i plugin a USB 3G modem, then should be starting the

..as a first step: "lsusb" or "lsusb -v" before and after you 
plug in anything usb, then "dmesg", to learn _whether_ your usb 
toy, indeed is known as e.g. an usb 3G modem.

..e.g. dmesg will often report missing driver firmware failures.

> modemmanager, but in devuan jessie nothing happened.
> 
> Wen imanually starts the modemmanager und then i plugin
> the modem, this output comes in daemon.log:
> 
> Mar  2 11:02:38 devuan-wkst ModemManager[3048]: 
> (tty/ttyUSB0): released by
> modem /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3 Mar  2
> 11:02:38 devuan-wkst ModemManager[3048]:   (tty/ttyUSB1):
> released by modem /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3
> Mar  2 11:02:38 devuan-wkst ModemManager[3048]: 
> (tty/ttyUSB2): released by
> modem /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3 Mar  2
> 11:03:05 devuan-wkst ModemManager[3048]:   (ttyUSB1): port
> attributes not fully set Mar  2 11:03:05 devuan-wkst
> ModemManager[3048]:   (ttyUSB2): port attributes not fully set
> Mar  2 11:03:06 devuan-wkst ModemManager[3048]:   (ttyUSB0):
> port attributes not fully set Mar  2 11:03:18 devuan-wkst
> ModemManager[3048]:   Creating modem with plugin 'ZTE' and '3'
> ports Mar  2 11:03:18 devuan-wkst ModemManager[3048]: 
> (ttyUSB2): port attributes not fully set Mar  2 11:03:18 devuan-wkst
> ModemManager[3048]:   Modem for device at
> '/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3' successfully
> created Mar  2 11:03:18 devuan-wkst ModemManager[3048]: 
> (ttyUSB2) response array is not empty when using cached reply,
> cleaning up 5 bytes Mar  2 11:03:19 devuan-wkst ModemManager[3048]:
>   Modem: state changed (unknown -> disabled)
> 
> "mmcli -L shows this:
> 
> Found 1 modems:
>   /org/freedesktop/ModemManager1/Modem/1 [ZTE CORPORATION] MF190
> 
> And wen i configure "/etc/wvdial.conf":
> 
> Dialer 3G]
> Init2 = ATZ
> Init3 = ATQ0 V1 E1 S0=0   +FCLASS=0
> Init5 = AT+CGDCONT=1,"IP"
> ISDN = 0
> Modem = /dev/ttyUSB2
> Modem Type = Analog Modem
> Baud = 460800
> 
> and type this on command line:
> 
> root@devuan-wkst:~# wvdial 3G
> --> WvDial: Internet dialer version 1.61
> --> Initializing modem.
> --> Sending: ATZ  
> OK
> --> Sending: ATZ  
> OK
> --> Sending: ATQ0 V1 E1 S0=0   +FCLASS=0  
> OK
> --> Sending: AT+CGDCONT=1,"IP"  
> AT+CGDCONT=1,"IP"
> OK
> --> Modem initialized.  
> 
> The modem should be worked, but the network-manager ignores the modem!
> 
> Have the network-manager no support for 3G Modems?
> 
> In an Debian Jessie installation the modem works with
> network-manager, also in Slackware 14.2!
> 
> Thanks,
> Juergen Moebius
> 
> 
> 
> 
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] systemd files

[Antony Stone]

On Friday 02 March 2018 at 11:26:39, KatolaZ wrote:

> Most of those "alarming" files are just systemd units files, put there
> by daemons/packages/utilities who "also" support systemd in a way or
> another. So they are not alarming but just *totally* *harmless* if you
> don't have a running systemd as PID 1, since only systemd understands
> and can run them.  It would be *totally* *useless* (and utterly
> *stupid* IMHO) to fork, rebuild, and maintain a few more hundred
> packages only because they happen to provide a systemd unit file for
> those systems where systemd is used.
> 
> libsystemd0 is used by some daemons to verify if systemd is running or
> not. If it's not, libsystemd is *totally* *harmless*.
> 
> HND
> 
> KatolaZ
> 
> P.S.: I guess we should consider including the last two paragraphs
> above on www.devuan.org, or put it in the mailing list signature...

Good idea, I think (on the website, anyway; we don't want something that long 
on every list posting).


Antony.

-- 
When you find yourself arguing with an idiot,
you should first of all make sure that the other person isn't doing the same 
thing.

   Please reply to the list;
 please *don't* CC me.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] systemd files

[Didier Kryn]

Le 02/03/2018 à 11:04, leloft a écrit :

/var/log/clamav/freshclam.log {
  rotate 12
  weekly
  compress
  delaycompress
  missingok
  create 640  clamav adm
  postrotate
  if [ -d /run/systemd/system ]; then
  systemctl -q is-active clamav-freshclam && systemctl kill
--signal=SIGHUP clamav-freshclam || true else
  /etc/init.d/clamav-freshclam reload-log > /dev/null || true
  fi
  endscript
  }


    The section starting at "postrotate" and ending at "endscript" is a 
script to execute after the "rotation" of the log files. It seems the 
intention is to send the SIGHUP signal to clamav-freshclam. Clearly, 
clamav-freshclean needs to be told to re-open its log file when it has 
been brutally closed by logrotate.


    When the classical RC scripts are installed, the initscript is 
invoked, rather than directly sending the signal, but, no doubt, it will 
send the signal.


    Since you haven't systemd installed, you can leave the script as 
is. If you feel nervous about your script checking for a non-existing 
file whose name contains the word "systemd", you can remove the 
conditional logic and keep unconditionnally.


/etc/init.d/clamav-freshclam reload-log > /dev/null || true

        Didier


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] systemd files

[KatolaZ]

On Fri, Mar 02, 2018 at 10:26:39AM +, KatolaZ wrote:

[cut]

> >  create 640  clamav adm
> >  postrotate
> >  if [ -d /run/systemd/system ]; then
> >  systemctl -q is-active clamav-freshclam && systemctl kill
> > --signal=SIGHUP clamav-freshclam || true else
> >  /etc/init.d/clamav-freshclam reload-log > /dev/null || true
> >  fi
> >  endscript
> >  }
> > 
> > But this code is not in any of the 16 other logrotate files in this
> > folder. I do not fully understand it, and so my first
> > question is are there any suggestions why it is there and why isn't it
> > necessary in the other files? I ask because I have uncovered an alarming
> > number of systemd files throughout the computer on which I installed the
> > clamav-daemon, and am concerned that there has been a bit of
> > liberty-taking by pro-systemd 'agendaware'.
> 
> Hi,
> 
> It's probably just that the upstream package maintainer has made the
> assumption that Debian should only run systemd, and nothing else
> ever. You might call it pro-systemd 'agendaware', if you like. It just
> seems to have become a shared habit of many (but not all)
> maintainers. That's why we are here, after all...

Sorry, I must correct my statement above: the script leloft posted is
correct, and works if either systemd or something else is used as PID
1. This is evident from the if-else block, which restarts the clamav
service usinf either systemd or the corresponding sysvinit script.

This is luckily a case in which the maintainer has not been
assimilated, yet :)

Please accept my apologies

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] systemd files

[KatolaZ]

On Fri, Mar 02, 2018 at 10:04:23AM +, leloft wrote:
> Hi devs,
> I am sorry to be troubling you with what may be a waste of your
> valuable time, but I have a couple of questions for the list.  Following
> on from the clamav-daemon problematic uninstallation, posted here
> https://lists.dyne.org/lurker/message/20180221.210210.37932ca6.en.html
> I have seen the following code in
> both /etc/logrotate.d/clamav-daemon.dpkg-old
> and /etc/logrotate.d/clamav-freshclam. 
> 
> /var/log/clamav/freshclam.log {
>  rotate 12
>  weekly
>  compress
>  delaycompress
>  missingok
>  create 640  clamav adm
>  postrotate
>  if [ -d /run/systemd/system ]; then
>  systemctl -q is-active clamav-freshclam && systemctl kill
> --signal=SIGHUP clamav-freshclam || true else
>  /etc/init.d/clamav-freshclam reload-log > /dev/null || true
>  fi
>  endscript
>  }
> 
> But this code is not in any of the 16 other logrotate files in this
> folder. I do not fully understand it, and so my first
> question is are there any suggestions why it is there and why isn't it
> necessary in the other files? I ask because I have uncovered an alarming
> number of systemd files throughout the computer on which I installed the
> clamav-daemon, and am concerned that there has been a bit of
> liberty-taking by pro-systemd 'agendaware'.

Hi,

It's probably just that the upstream package maintainer has made the
assumption that Debian should only run systemd, and nothing else
ever. You might call it pro-systemd 'agendaware', if you like. It just
seems to have become a shared habit of many (but not all)
maintainers. That's why we are here, after all...

> 
> I issued $locate systemd 
> and got 200 lines of output, including 
> /etc/systemd/system/* (23 files) 
> /lib/systemd/system/* (60 files)
> /lib/x86_64-linux-gnu/libsystemd.so.0 (and 0.17.0)
> /usr/lib/systemd (25 files)
> /usr/bin/deb-systemd-helper ((and deb-systemd-invoke)
> /var/lib/systemd/deb-systemd-helper-enabled/* (68 files)
> /var/lib/dpkg/info/libsystemd):amd64* (5 files)
> 
> This seems a lot to me.  Please could you confirm that an ascii
> installation should contain 200 systemd files as part of a normal
> ascii installation.  Sorry to trouble you if these are trivial
> questions, but they feel far from that.
> Many thanks
> leloft


Most of those "alarming" files are just systemd units files, put there
by daemons/packages/utilities who "also" support systemd in a way or
another. So they are not alarming but just *totally* *harmless* if you
don't have a running systemd as PID 1, since only systemd understands
and can run them.  It would be *totally* *useless* (and utterly
*stupid* IMHO) to fork, rebuild, and maintain a few more hundred
packages only because they happen to provide a systemd unit file for
those systems where systemd is used.

libsystemd0 is used by some daemons to verify if systemd is running or
not. If it's not, libsystemd is *totally* *harmless*. 

HND

KatolaZ

P.S.: I guess we should consider including the last two paragraphs
above on www.devuan.org, or put it in the mailing list signature...

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Configure qt5 to look like gtk

[William Gallafent]

On 2018-03-02 09:03, J. Fahrner wrote:
In ascii many apps are based on qt5. Unlike qt4 there is no configure 
utility.
Does someone know how to configure qt5 to look like gtk in non-KDE 
environments? (specially in openbox environment)
I haven't tried this, but some of the ideas at 
https://wiki.archlinux.org/index.php/Uniform_look_for_Qt_and_GTK_applications#Styles_for_both_Qt_and_GTK.2B 
might help. In particular: “For Qt 5, it can be enabled by setting the 
following environment variable 
: 
QT_STYLE_OVERRIDE=adwaita. Alternatively, use qt5ct 
 package.”


There's more information at 
https://wiki.archlinux.org/index.php/Qt#Configuration_of_Qt5_apps_under_environments_other_than_KDE_Plasma 
…


HTH and good luck :)

--
Bill Gallafent

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] 3G modem support in devuan jessie network-manager

[Juergen Moebius]

Hi,

have the network-manager in jessie support for 3G modems?

Wen i plugin a USB 3G modem, then should be starting the
modemmanager, but in devuan jessie nothing happened.

Wen imanually starts the modemmanager und then i plugin
the modem, this output comes in daemon.log:

Mar  2 11:02:38 devuan-wkst ModemManager[3048]:   (tty/ttyUSB0): released 
by modem /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3
Mar  2 11:02:38 devuan-wkst ModemManager[3048]:   (tty/ttyUSB1): released 
by modem /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3
Mar  2 11:02:38 devuan-wkst ModemManager[3048]:   (tty/ttyUSB2): released 
by modem /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3
Mar  2 11:03:05 devuan-wkst ModemManager[3048]:   (ttyUSB1): port 
attributes not fully set
Mar  2 11:03:05 devuan-wkst ModemManager[3048]:   (ttyUSB2): port 
attributes not fully set
Mar  2 11:03:06 devuan-wkst ModemManager[3048]:   (ttyUSB0): port 
attributes not fully set
Mar  2 11:03:18 devuan-wkst ModemManager[3048]:   Creating modem with 
plugin 'ZTE' and '3' ports
Mar  2 11:03:18 devuan-wkst ModemManager[3048]:   (ttyUSB2): port 
attributes not fully set
Mar  2 11:03:18 devuan-wkst ModemManager[3048]:   Modem for device at 
'/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3' successfully created
Mar  2 11:03:18 devuan-wkst ModemManager[3048]:   (ttyUSB2) response 
array is not empty when using cached reply, cleaning up 5 bytes
Mar  2 11:03:19 devuan-wkst ModemManager[3048]:   Modem: state changed 
(unknown -> disabled)

"mmcli -L shows this:

Found 1 modems:
/org/freedesktop/ModemManager1/Modem/1 [ZTE CORPORATION] MF190

And wen i configure "/etc/wvdial.conf":

Dialer 3G]
Init2 = ATZ
Init3 = ATQ0 V1 E1 S0=0   +FCLASS=0
Init5 = AT+CGDCONT=1,"IP"
ISDN = 0
Modem = /dev/ttyUSB2
Modem Type = Analog Modem
Baud = 460800

and type this on command line:

root@devuan-wkst:~# wvdial 3G
--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: ATZ
OK
--> Sending: ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0   +FCLASS=0
OK
--> Sending: AT+CGDCONT=1,"IP"
AT+CGDCONT=1,"IP"
OK
--> Modem initialized.

The modem should be worked, but the network-manager ignores the modem!

Have the network-manager no support for 3G Modems?

In an Debian Jessie installation the modem works with network-manager, also
in Slackware 14.2!

Thanks,
Juergen Moebius




___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] systemd files

[leloft]

Hi devs,
I am sorry to be troubling you with what may be a waste of your
valuable time, but I have a couple of questions for the list.  Following
on from the clamav-daemon problematic uninstallation, posted here
https://lists.dyne.org/lurker/message/20180221.210210.37932ca6.en.html
I have seen the following code in
both /etc/logrotate.d/clamav-daemon.dpkg-old
and /etc/logrotate.d/clamav-freshclam. 

/var/log/clamav/freshclam.log {
 rotate 12
 weekly
 compress
 delaycompress
 missingok
 create 640  clamav adm
 postrotate
 if [ -d /run/systemd/system ]; then
 systemctl -q is-active clamav-freshclam && systemctl kill
--signal=SIGHUP clamav-freshclam || true else
 /etc/init.d/clamav-freshclam reload-log > /dev/null || true
 fi
 endscript
 }

But this code is not in any of the 16 other logrotate files in this
folder. I do not fully understand it, and so my first
question is are there any suggestions why it is there and why isn't it
necessary in the other files? I ask because I have uncovered an alarming
number of systemd files throughout the computer on which I installed the
clamav-daemon, and am concerned that there has been a bit of
liberty-taking by pro-systemd 'agendaware'.

I issued $locate systemd 
and got 200 lines of output, including 
/etc/systemd/system/* (23 files) 
/lib/systemd/system/* (60 files)
/lib/x86_64-linux-gnu/libsystemd.so.0 (and 0.17.0)
/usr/lib/systemd (25 files)
/usr/bin/deb-systemd-helper ((and deb-systemd-invoke)
/var/lib/systemd/deb-systemd-helper-enabled/* (68 files)
/var/lib/dpkg/info/libsystemd):amd64* (5 files)

This seems a lot to me.  Please could you confirm that an ascii
installation should contain 200 systemd files as part of a normal
ascii installation.  Sorry to trouble you if these are trivial
questions, but they feel far from that.
Many thanks
leloft
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Configure qt5 to look like gtk

[J. Fahrner]

In ascii many apps are based on qt5. Unlike qt4 there is no configure 
utility.
Does someone know how to configure qt5 to look like gtk in non-KDE 
environments? (specially in openbox environment)


Jochen


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] pam_limits or limits.conf different from Debian?

[KatolaZ]

On Fri, Mar 02, 2018 at 02:13:15PM +1300, Patrick Dunford wrote:
> No red flags for any of that stuff
> 
> On a Debian Buster VM where the increased file limit put into limits.conf
> obviously works, the result of ulimit -n comes out the same 1024 as on my
> Devuan VM.
> 
> The subtleties of why one distro would use one mechanism and a similar one a
> different mechanism (apparently) are all the things that frustrate people
> like me :)
> 

The thing is that I guess Devuan ASCII has not (willingly) changed any
default in that respect, so the same problem might be present in
debian stretch.

This post:

  
https://stackoverflow.com/questions/46441602/how-to-change-open-files-ulimit-n-permanently-for-normal-user-in-debian-stret

suggests that libpam-systemd seems to ignore /etc/security/limits.conf
by default. The easy way to check is by logging in from a tty, and
looking at:

 $ ulimit -n

I tried it now, setting nofile to 2, and it correctly shows the
new value. Which polkit backend are you using? We might have inherited
an unwanted behaviour in libpam-elogind, possibly.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng