Re: [DNG] Runit for Devuan: was Debian testing drop redis

[aitor]

Hi John,

On 27/10/17 11:29, John Hughes wrote:
Debian's runit maintainer, Dmitry Bogatov, was arrested, accused of 
"preparing to organize mass disorder" and making "public calls for 
terrorist activit".  He runs a TOR exit node and is accused of posting 
things that were probably posted by some other TOR user.


https://www.eff.org/deeplinks/2017/04/access-now-and-eff-condemn-arrest-tor-node-operator-dmitry-bogatov-russia 





Like in the Stalin's days gone by. I missed this new, i'll read it in 
detail today.



The last time I downloaded, compiled and installed
runit it worked just fine.
The problem is with runit-init, not runit.  runit is still in Debian 
(and, hence, Devuan).


The problem is Debian bug 861536 -- installing runit-init makes it 
impossible to shutdown or reboot until the next boot. 


As i said in a recent thread, you can shutdown/reboot doing (it requires 
granted permissions):


runit-init 0

runit-init 6

I'm working on a logout dialog for runit with suid permissions.

Cheers,

  Aitor.





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

Re: [DNG] wicd interferes with regular network admin tools

[Jimmy Johnson]

On 05/27/2018 09:05 AM, Joel Roth wrote:

Hi Devuan network users and adminstrators,

I was recently suprised to observe network interfaces
(wlan0 and eth0) going up without my issuing commands for
it. I'd disable an interface, then see it go right back up.

I somehow guessed that the culprit might be wicd, and
confirmed that a wicd process was active.  I never
ran any of the wicd admin tools.

The list of wicd features does not mention that it
interferes with managing networks using net-tools or
iproute2 commands.

Is this a bug, or a documentation bug? Certainly, the
behavior is less-than-awesome. If one wants to learn about
networking on linux, or to administer a system using
conventional command-line tools, one should know that wicd
needs to be removed.

Do net-tools and iproute2 need to warn against wicd?
Should wicd warn that it disrupts administration via net-tools?

I wonder if there is any parallel in how in linux we
administer /etc/resolv.conf.

Do you have any thoughts about clarifying how to expect the
networking environment to work under linux?



Hi Joel, treat Devuan like old school Debian and get rid of network 
manager and it's ilk, use wicd-gtk, your internet device names are no 
longer going to change, so what you see when you run 'ifconfig -a' is 
the name of your devices and probably something like eth0 and wlan0. 
Configure /etc/network/interfaces accordingly  and add 'allow-hotplug' 
for your devices. And make sure the device names are correct in wicd, 
done.  That's my opinion.


Cheers,
--
Jimmy Johnson

Devuan ASCII - TDE Trinity R14.0.5 - AMD A8-7600 - EXT4 at sda6
Registered Linux User #380263

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

Re: [DNG] wicd interferes with regular network admin tools

[Hendrik Boom]

On Sun, May 27, 2018 at 06:05:09AM -1000, Joel Roth wrote:
> Hi Devuan network users and adminstrators,
> 
> I was recently suprised to observe network interfaces
> (wlan0 and eth0) going up without my issuing commands for
> it. I'd disable an interface, then see it go right back up.
> 
> I somehow guessed that the culprit might be wicd, and
> confirmed that a wicd process was active.  I never
> ran any of the wicd admin tools.
> 
> The list of wicd features does not mention that it
> interferes with managing networks using net-tools or
> iproute2 commands.
> 
> Is this a bug, or a documentation bug? Certainly, the
> behavior is less-than-awesome. If one wants to learn about
> networking on linux, or to administer a system using
> conventional command-line tools, one should know that wicd
> needs to be removed.
> 
> Do net-tools and iproute2 need to warn against wicd?
> Should wicd warn that it disrupts administration via net-tools?
> 
> I wonder if there is any parallel in how in linux we
> administer /etc/resolv.conf.
> 
> Do you have any thoughts about clarifying how to expect the
> networking environment to work under linux?

Using ascii on my netbook here.

It has a socket for a wired ethernet, but so far I've been using wifi.
I've been using wicd to manage wifi.  I'm finding wifi at home somewhat 
unreliable.

It was more reliabe a few years ago before I moved to a condo; it's 
entirely possible that the unreliablity is because of interference from 
other wifis in other condos in the building.

My Raspberry pi, which runs Devuan ascii, has a wired link because I've 
never ound the right wifi driver.  But the wired link is quite reliable.

Last week I plugged the same wired ethernet cable into the netbook instead 
of the Raspberry Pi.  Wicd recognised it.  But when asked it to turn 
wifi off, it did that, but I was unable to get wicd to operate through 
the wired ethernet. 

I haven't yet had time to experiment further, and am entirely unsure if 
I just don't know how to use wicd, or if wicd presents unusable 
alternatives.

I'd *like* it to connect to the wired link if available, and otherwise 
to wifi.

-- hendrik

> 
> regards,
> 
> 
> -- 
> Joel Roth
>   
> 
> ___
> 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] wicd interferes with regular network admin tools

[KatolaZ]

On Sun, May 27, 2018 at 06:42:57PM +0200, Adam Borowski wrote:

[cut]

> 
> This is actually very puzzling: what we want, is a wrapper for iw which
> seeks available wifi networks, and provides a GUI to choose one.  The only
> reason such a tool would ever look at eth0 is to see if its link is up, and
> if so, skip wifi unless explicitly told to connect anyway.
> 
> So why do authors of such tools feel the need to control the state of
> non-wifi interfaces?
> 
>

Because programmers think that writing a program that does more things
than repuired is *better*. That's actually the cause of bigger
problems than wicd wanting to manage eth0...

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

Re: [DNG] wicd interferes with regular network admin tools

[Adam Borowski]

On Sun, May 27, 2018 at 05:21:50PM +0100, KatolaZ wrote:
> On Sun, May 27, 2018 at 06:05:09AM -1000, Joel Roth wrote:
> > I was recently suprised to observe network interfaces
> > (wlan0 and eth0) going up without my issuing commands for
> > it. I'd disable an interface, then see it go right back up.
> 
> Joel, unfortunately this is the problem with "smart" tools for network
> management: they think they know what is good for you, all the
> time. Both wicd and nm are particularly bad at that, since they try to
> manage network state accordingto what they have been told in their
> config, despite anything. Dunno about conman, but I guess it works
> along the same lines.

This is actually very puzzling: what we want, is a wrapper for iw which
seeks available wifi networks, and provides a GUI to choose one.  The only
reason such a tool would ever look at eth0 is to see if its link is up, and
if so, skip wifi unless explicitly told to connect anyway.

So why do authors of such tools feel the need to control the state of
non-wifi interfaces?


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ .globl _start↵.data↵rc: .ascii "/etc/init.d/rcS\0"↵.text↵_start
⣾⠁⢰⠒⠀⣿⡁ mov $57,%rax↵syscall↵cmp $0,%rax↵jne child↵parent:↵mov $61,%rax
⢿⡄⠘⠷⠚⠋⠀ mov $-1,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall↵jmp parent↵child:
⠈⠳⣄ mov $59,%rax↵mov $rc,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] wicd interferes with regular network admin tools

[KatolaZ]

On Sun, May 27, 2018 at 06:05:09AM -1000, Joel Roth wrote:
> Hi Devuan network users and adminstrators,
> 
> I was recently suprised to observe network interfaces
> (wlan0 and eth0) going up without my issuing commands for
> it. I'd disable an interface, then see it go right back up.
> 
> I somehow guessed that the culprit might be wicd, and
> confirmed that a wicd process was active.  I never
> ran any of the wicd admin tools.
> 
> The list of wicd features does not mention that it
> interferes with managing networks using net-tools or
> iproute2 commands.
> 
> Is this a bug, or a documentation bug? Certainly, the
> behavior is less-than-awesome. If one wants to learn about
> networking on linux, or to administer a system using
> conventional command-line tools, one should know that wicd
> needs to be removed.
> 
> Do net-tools and iproute2 need to warn against wicd?
> Should wicd warn that it disrupts administration via net-tools?
> 
> I wonder if there is any parallel in how in linux we
> administer /etc/resolv.conf.
> 
> Do you have any thoughts about clarifying how to expect the
> networking environment to work under linux?
> 


Joel, unfortunately this is the problem with "smart" tools for network
management: they think they know what is good for you, all the
time. Both wicd and nm are particularly bad at that, since they try to
manage network state accordingto what they have been told in their
config, despite anything. Dunno about conman, but I guess it works
along the same lines.

That's why I ended up writing setnet for myself: because stateful
network management just sucks, IMHO, and the only non-invasve way
through is by having stateless tools. But I understand that most users
expect something different.

There is not much to do about that: if a user wants to manage
networking by hand, they have to stop any other network daemon, being
it wicd, nm, or conman. 

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

[DNG] wicd interferes with regular network admin tools

[Joel Roth]

Hi Devuan network users and adminstrators,

I was recently suprised to observe network interfaces
(wlan0 and eth0) going up without my issuing commands for
it. I'd disable an interface, then see it go right back up.

I somehow guessed that the culprit might be wicd, and
confirmed that a wicd process was active.  I never
ran any of the wicd admin tools.

The list of wicd features does not mention that it
interferes with managing networks using net-tools or
iproute2 commands.

Is this a bug, or a documentation bug? Certainly, the
behavior is less-than-awesome. If one wants to learn about
networking on linux, or to administer a system using
conventional command-line tools, one should know that wicd
needs to be removed.

Do net-tools and iproute2 need to warn against wicd?
Should wicd warn that it disrupts administration via net-tools?

I wonder if there is any parallel in how in linux we
administer /etc/resolv.conf.

Do you have any thoughts about clarifying how to expect the
networking environment to work under linux?

regards,


-- 
Joel Roth
  

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

Re: [DNG] Unable to "Load missing firmware from removable media"

[fsmithred]

On 05/26/2018 04:31 PM, dan pridgeon wrote:

> This is not the case for the Netinst.iso.  Within the packages you have so 
> carefully noted, is the file containing the firmware needed for the C700 
> wireless adapter card.  I do not know the name of that file.  Knowingthat 
> list of packages, I can now begin to learn how to search those packages for 
> .fw files in order to determine thecorrect file.  The netinst.iso  asks for 
> the file named ucode13.fw which it cannot find in either the b43 or the 
> b43-open directories.  This leads to the logical conclusion that either the 
> netinst.iso is asking for the wrong.fw file, OR, it is not looking for it in 
> the right place.  From all that I've studied so far, this is an 
> inheritedstate of affairs for Devuan.  Sorry if I'm not as clear as I'd like 
> to be.  I find myself walking among giants here but I 

Now we're getting somewhere! The package I said you need is not on the
netinstall iso (I'm looking at the beta.) Below is the list of everything
in the firmware directory on the iso. It has more than just wireless
firmware, and it doesn't have all the wireless firmware. (b43-fwcutter,
firmware-b43-installer, firmware-b43-legacy-installer are missing, and
maybe others, too.)

I just tried this in a refracta iso with network disconnected.
b43-fwcutter needs to be installed before firmware-b43-installer or the
latter fails due to the missing package. Install them in the right order
and firmware-b43-installer fails because it cannot connect to
www.lwfinger.com.

You can extract the files from a deb file with 'ar x '. I did
that with the b43 installer, and I looked in /lib/firmware/b43/ and it's
empty. You have to be online if you want to get the file that will allow
you to get online. That's the exact situation we try to avoid by having
the wireless firmware installed in the live isos.

http://www.lwfinger.com/b43-firmware/ has some files. I don't know which
is the right one. You can get the file that was requested during the
install from the live iso. It's /lib/firmware/b43/ucode13.fw.


Firmware packages on beta netinstall iso:
amd64-microcode_3.20160316.3_amd64.deb
atmel-firmware_1.3-4_all.deb
bluez-firmware_1.2-3_all.deb
dahdi-firmware-nonfree_2.11.1-1_all.deb
firmware-amd-graphics_20161130-3_all.deb
firmware-atheros_20161130-3_all.deb
firmware-bnx2_20161130-3_all.deb
firmware-bnx2x_20161130-3_all.deb
firmware-brcm80211_20161130-3_all.deb
firmware-cavium_20161130-3_all.deb
firmware-crystalhd_0.0~git20120110.fdd2f19-1_all.deb
firmware-intel-sound_20161130-3_all.deb
firmware-intelwimax_20161130-3_all.deb
firmware-ipw2x00_20161130-3_all.deb
firmware-ivtv_20161130-3_all.deb
firmware-iwlwifi_20161130-3_all.deb
firmware-libertas_20161130-3_all.deb
firmware-linux-free_3.4_all.deb
firmware-misc-nonfree_20161130-3_all.deb
firmware-myricom_20161130-3_all.deb
firmware-netxen_20161130-3_all.deb
firmware-qlogic_20161130-3_all.deb
firmware-realtek_20161130-3_all.deb
firmware-samsung_20161130-3_all.deb
firmware-siano_20161130-3_all.deb
firmware-ti-connectivity_20161130-3_all.deb
firmware-zd1211_1.5-4_all.deb
hdmi2usb-fx2-firmware_0.0.0~git20151225-1_all.deb

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

[DNG] [OT] Modification of audio power amplifier.

[Edward Bartolo]

Thanks for all replies.

My first prototype test circuit seems to work as expected although I
haven't yet connected the output stage. Connecting a resistor, 10K
Ohm, from the inverting input to output, that is, the point between
the biasing diodes, resulted in an ouput voltage of 0 Volts. This
clearly shows the circuit is working. Also connecting a very high
resistance from the non-inverting input to the positive and negative
sides of the split power supply resulted in the output voltage
shifting accordingly. Voltages across all components followed
calculated values quite accurately.

After this test, I will connect the ouput stage when I finish all
modifications so that everything is compatible with the earth terminal
connected to the 0V terminal of the split power supply.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan ASCII 2.0 RC - Strange dependencies with FreeRadius?

[Rowland Penny]

On Sun, 27 May 2018 12:02:36 +0100
Mike Tubby  wrote:

> I have built a new internet router/firewall box with an old Dell R610 
> and lots of Ethernet interfaces.
> 
> Installed Devuan Ascii 2.0 RC 'non graphical' install (no X, no 
> desktop), yet when I go to install FreeRADIUS server it appears to
> want to pull in a load of cruft including:
> 
> * Java/JRE
> * fonts, icons, themes
> * GTK
> * LVM
> * make ???
> 
> ... and more?
> 
> Broken dependencies?  Any suggestions for how to maker this sane?
> 

Try adding '--no-install-recommends'

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

[DNG] Devuan ASCII 2.0 RC - Strange dependencies with FreeRadius?

[Mike Tubby]

I have built a new internet router/firewall box with an old Dell R610 
and lots of Ethernet interfaces.


Installed Devuan Ascii 2.0 RC 'non graphical' install (no X, no 
desktop), yet when I go to install FreeRADIUS server it appears to want 
to pull in a load of cruft including:


* Java/JRE
* fonts, icons, themes
* GTK
* LVM
* make ???

... and more?

Broken dependencies?  Any suggestions for how to maker this sane?

Mike


root@new-gate:/var/cache# apt-get install freeradius
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  adwaita-icon-theme at-spi2-core ca-certificates-java collectd 
collectd-core dconf-gsettings-backend dconf-service default-jre-headless 
dmeventd
  fontconfig freeradius-common freeradius-config freeradius-utils 
glib-networking glib-networking-common glib-networking-services 
gsettings-desktop-schemas
  gtk-update-icon-cache hicolor-icon-theme java-common libapr1 
libatasmart4 libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0 
libavahi-client3
  libavahi-common-data libavahi-common3 libbluetooth3 libc-ares2 
libcairo-gobject2 libcollectdclient1 libcolord2 libconfuse-common 
libconfuse1 libcroco3
  libcups2 libdatrie1 libdbi-perl libdbi1 libdconf1 
libdevmapper-event1.02.1 libepoxy0 libesmtp6 libfreeradius3 libftdi1 
libganglia1 libgdk-pixbuf2.0-0
  libgdk-pixbuf2.0-common libgps22 libgtk-3-0 libgtk-3-bin 
libgtk-3-common libhiredis0.13 libjson-glib-1.0-0 
libjson-glib-1.0-common liblcms2-2 liblua5.3-0
  liblvm2app2.2 liblvm2cmd2.02 libmemcached11 libmicrohttpd12 
libmodbus5 libmosquitto1 libnl-3-200 libnl-route-3-200 libnotify4 
libnspr4 libnss3
  libopenipmi0 liboping0 libow-3.1-5 libowcapi-3.1-5 libpango-1.0-0 
libpangocairo-1.0-0 libpangoft2-1.0-0 libprotobuf-c1 libproxy1v5 
librabbitmq4
  librdkafka1 libreadline5 librest-0.7-0 libriemann-client0 librrd8 
librsvg2-2 librsvg2-common librte-acl2 librte-cfgfile2 librte-cmdline2
  librte-cryptodev2 librte-distributor1 librte-eal3 librte-ethdev5 
librte-hash2 librte-ip-frag1 librte-jobstats1 librte-kni2 librte-kvargs1 
librte-lpm2
  librte-mbuf2 librte-mempool2 librte-meter1 librte-net1 librte-pdump1 
librte-pipeline3 librte-pmd-af-packet1 librte-pmd-bnxt1 librte-pmd-bond1
  librte-pmd-cxgbe1 librte-pmd-e1000-1 librte-pmd-ena1 librte-pmd-enic1 
librte-pmd-fm10k1 librte-pmd-i40e1 librte-pmd-ixgbe1 librte-pmd-null-crypto1
  librte-pmd-null1 librte-pmd-pcap1 librte-pmd-qede1 librte-pmd-ring2 
librte-pmd-vhost1 librte-pmd-virtio1 librte-pmd-vmxnet3-uio1 
librte-pmd-xenvirt1
  librte-port3 librte-power1 librte-reorder1 librte-ring1 librte-sched1 
librte-table2 librte-timer1 librte-vhost3 libserialport0 libsigrok2 
libsnmp-base
  libsnmp30 libsoup-gnome2.4-1 libsoup2.4-1 libtalloc2 libthai-data 
libthai0 libtokyocabinet9 libtokyotyrant3 libupsclient4 libvarnishapi1 
libvirt0
  libwbclient0 libxcomposite1 libxen-4.8 libxenstore3.0 libyajl2 
libzip4 lvm2 make notification-daemon openjdk-8-jre-headless owfs-common 
rrdtool ssl-cert

Suggested packages:
  collectd-dev librrds-perl liburi-perl libhtml-parser-perl 
libregexp-common-perl libconfig-general-perl apache2 apcupsd ceph chrony 
default-mysql-server
  gpsd hddtemp ipvsadm lm-sensors mbmon memcached nut olsrd pdns-server 
postgresql redis-server slapd time-daemon varnish zookeeper default-jre
  freeradius-ldap freeradius-postgresql freeradius-mysql 
freeradius-krb5 snmp colord cups-common libclone-perl libmldbm-perl 
libnet-daemon-perl
  libsql-statement-perl gvfs liblcms2-utils librsvg2-bin 
snmp-mibs-downloader thin-provisioning-tools make-doc libnss-mdns 
fonts-dejavu-extra
  fonts-ipafont-gothic fonts-ipafont-mincho fonts-wqy-microhei 
fonts-wqy-zenhei fonts-indic openssl-blacklist

The following NEW packages will be installed:
  adwaita-icon-theme at-spi2-core ca-certificates-java collectd 
collectd-core dconf-gsettings-backend dconf-service default-jre-headless 
dmeventd
  fontconfig freeradius freeradius-common freeradius-config 
freeradius-utils glib-networking glib-networking-common 
glib-networking-services
  gsettings-desktop-schemas gtk-update-icon-cache hicolor-icon-theme 
java-common libapr1 libatasmart4 libatk-bridge2.0-0 libatk1.0-0 
libatk1.0-data
  libatspi2.0-0 libavahi-client3 libavahi-common-data libavahi-common3 
libbluetooth3 libc-ares2 libcairo-gobject2 libcollectdclient1 libcolord2
  libconfuse-common libconfuse1 libcroco3 libcups2 libdatrie1 
libdbi-perl libdbi1 libdconf1 libdevmapper-event1.02.1 libepoxy0 
libesmtp6 libfreeradius3
  libftdi1 libganglia1 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common 
libgps22 libgtk-3-0 libgtk-3-bin libgtk-3-common libhiredis0.13 
libjson-glib-1.0-0
  libjson-glib-1.0-common liblcms2-2 liblua5.3-0 liblvm2app2.2 
liblvm2cmd2.02 libmemcached11 libmicrohttpd12 libmodbus5 libmosquitto1 
libnl-3-200
  libnl-route-3-200 libnotify4 libnspr4 libnss3 libopenipmi0 liboping0 
libow-3.1-5 libowcapi-3.1-5 libpango-1.0-0 libpangocairo-1.0-0