Re: [DNG] WAIT_ONLINE_METHOD=none

2019-02-16 Thread Didier Kryn
Le 16/02/2019 à 23:42, Dr. Nikolaus Klepp a écrit : So openssh is blocked by random, which by some unknown reason takes ~ 30 seconds to start on 4.19 (in contrast to ~ 1 second o 4.9)     I've read things about that in other lists. There's a new requirement to have a big enough amount of

Re: [DNG] WAIT_ONLINE_METHOD=none

2019-02-16 Thread Dr. Nikolaus Klepp
Anno domini 2019 Sat, 16 Feb 23:23:23 +0100 Didier Kryn scripsit: > Le 16/02/2019 à 21:56, Dr. Nikolaus Klepp a écrit : > > I have tried "ifplugd" the last days, but that did not work especially > > well: It worked when starting without network and connecting within a hour > > or so, but it

Re: [DNG] WAIT_ONLINE_METHOD=none

2019-02-16 Thread Didier Kryn
Le 16/02/2019 à 21:56, Dr. Nikolaus Klepp a écrit : I have tried "ifplugd" the last days, but that did not work especially well: It worked when starting without network and connecting within a hour or so, but it failed when connecting after several hours.     Strange. Mostly worked fine for

Re: [DNG] WAIT_ONLINE_METHOD=none

2019-02-16 Thread Dr. Nikolaus Klepp
hi Aitor! Anno domini 2019 Wed, 13 Feb 23:12:25 +0100 aitor_czr scripsit: > Hi, > > On 13/2/19 16:59, Dr. Nikolaus Klepp wrote: > >>     If your ethernet cable can be either plugged or unplugged and you > >> want your system to react when you plug/unplug a cable in, then you need > >> a

Re: [DNG] xdm broken?

2019-02-16 Thread Ozi Traveller via Dng
Ok thanks KatolaZ! Ozi On Sun, Feb 17, 2019 at 7:15 AM KatolaZ wrote: > On Sun, Feb 17, 2019 at 06:58:01AM +1100, Ozi Traveller via Dng wrote: > > Hi Alessandro > > > > Th existing install was working with slim. However after installing xdm > > startx run as a normal user wouldn't start, but

Re: [DNG] xdm broken?

2019-02-16 Thread KatolaZ
On Sun, Feb 17, 2019 at 06:58:01AM +1100, Ozi Traveller via Dng wrote: > Hi Alessandro > > Th existing install was working with slim. However after installing xdm > startx run as a normal user wouldn't start, but it did run as root. > Ozi, please have a look at the Ascii release notes:

Re: [DNG] xdm broken?

2019-02-16 Thread Ozi Traveller via Dng
Hi Alessandro Th existing install was working with slim. However after installing xdm startx run as a normal user wouldn't start, but it did run as root. Also I'm logged in on another console, and have jwm running and also pcmanfm. It looks like slim is still running though. ozi On Sun, Feb

Re: [DNG] Tips about eudev

2019-02-16 Thread aitor_czr
Hi, On 16/2/19 10:12, aitor_czr wrote: Hi all, The function: kill_udevd() {     start-stop-daemon --stop --name udevd --user root --pidfile /run/udev.pid     --remove-pidfile --oknodo --quiet --retry 5 } located in debian/eudev.prerm throws the following error: "... No udevd found

Re: [DNG] iptables forced obsolescence over upgrade

2019-02-16 Thread Alessandro Selli
On 16/02/19 at 11:26, chillfan--- via Dng wrote: > And of course I don't need nft   Yes, you do.   For some reason  you don't *want* it, but that's a different matter. -- Alessandro Selli VOIP SIP: dhatarat...@ekiga.net Chiave firma e cifratura PGP/GPG signing and encoding key:

Re: [DNG] xdm broken?

2019-02-16 Thread Alessandro Selli
On 15/02/19 at 21:39, Ozi Traveller via Dng wrote: > Hi > > I have installed xdm, and it starts when I boot up,  but doesn't start > xorg when I login.   Please check that Xorg is installed.  You should have the executable /usr/bin/Xorg in place installed by package xserver-xorg-core.  Then you

Re: [DNG] iptables forced obsolescence over upgrade

2019-02-16 Thread chillfan--- via Dng
Imo this is nowhere near a pleasant way to do things for users. It would have been much better to just provide a separate iptables nft package by default during the install, as they really haven't given iptables the axe yet. publickey - chillfan@protonmail.com - 0xB179B25B.asc Description:

Re: [DNG] iptables forced obsolescence over upgrade

2019-02-16 Thread chillfan--- via Dng
So it turns out if you have the proper nft support (nft + compat module probably) in your kernel then iptables will continue to work. The ifup failure looks like this: iptables-restore/1.8.2 Failed to initialize nft: Protocol not supported run-parts: /etc/network/if-pre-up.d/iptables exited

Re: [DNG] iptables forced obsolescence over upgrade

2019-02-16 Thread chillfan--- via Dng
Yeah, although the nft wiki seems to suggest it will replace iptables they seem to be coexisting at the moment. The problem with iptables is it expects you to have nft support. A quick find command shows some changes in the provided binaries. /sbin/iptables-save /sbin/iptables

[DNG] Tips about eudev

2019-02-16 Thread aitor_czr
Hi all, The function: kill_udevd() {     start-stop-daemon --stop --name udevd --user root --pidfile /run/udev.pid     --remove-pidfile --oknodo --quiet --retry 5 } located in debian/eudev.prerm throws the following error: "... No udevd found running; none killed." It should be replaced

Re: [DNG] iptables forced obsolescence over upgrade

2019-02-16 Thread KatolaZ
On Fri, Feb 15, 2019 at 11:25:36PM +, chillfan--- via Dng wrote: > Of the most stupid thing to happen over an upgrade.. Debian have forcibly > broken a security feature. Which is to say, don't expect your firewall to > still be functioning when you upgrade to Buster. And expect it to cause