Re: [DNG] Chimaera CPU stuck

[Hector Gonzalez Jaime via Dng]

On 9/14/22 14:54, Luciano Mannucci wrote:

On Wed, 14 Sep 2022 12:37:41 -0500
Hector Gonzalez Jaime via Dng  wrote:


kernel:[ 7336.007287] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[swapper/0:0]

if I write to the disk via dd nothing wrong happens...

Luciano.

Check which scheduler you are using, for virtual machine loads you might
want to use "deadline", assuming your disk is sda, the first command
checks your scheduler, the second changes to deadline.

cat /sys/block/sda/queue/scheduler

echo "deadline" >/sys/block/sda/queue/schedule

Well, the disk seems to be "vda".
Issueing root@bobby:~# cat /sys/block/vda/queue/scheduler gives:

[mq-deadline] none

Is it wrong?


It's as it should be.  Did you check this on the hypervisor?  The use of 
vda suggests this was checked on a VM, please check the physical host, 
which is the one doing the I/O for your VM.  The physical host is also 
the one that needs to have a few dedicated processors to perform I/O for 
the VMs.





Luciano.


--
Hector Gonzalez
ca...@genac.org

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

Re: [DNG] Chimaera CPU stuck

[Hector Gonzalez Jaime via Dng]

On 9/14/22 10:02, Luciano Mannucci wrote:

On Wed, 14 Sep 2022 12:49:19 +0200
Luciano Mannucci  wrote:


vm.dirty_background_bytes=67108864
vm.dirty_bytes=268435456

Maybe this additional information is helpful:

https://forum.proxmox.com/threads/io-performance-tuning.15893/
https://lonesysadmin.net/2013/12/22/better-linux-disk-caching-performance-vm-dirty_ratio/

Hope that helps,

Yes, it does!
Works like a charm!

I've been to quick...
Now only if the data comes from the local LAN (not drossing routers or
firewalls) I still get

   kernel:[ 7336.007287] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[swapper/0:0]

if I write to the disk via dd nothing wrong happens...

Luciano.


Check which scheduler you are using, for virtual machine loads you might 
want to use "deadline", assuming your disk is sda, the first command 
checks your scheduler, the second changes to deadline.


cat /sys/block/sda/queue/scheduler

echo "deadline" >/sys/block/sda/queue/scheduler

--
Hector Gonzalez
ca...@genac.org

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

Re: [DNG] OpenVPN 2.5.1-3+devuan1 packaging vs best practices

[Hector Gonzalez Jaime via Dng]

On 7/26/22 10:00, Ken Dibble wrote:

On 7/25/22 09:29, Ken Dibble wrote:


This is the first time I have seen this with any package.

I have no idea whether it has happened with packages not installed on 
my systems.


It is my understanding that best practice is noexec on /tmp and that 
this is a Debian recommendation.


Here is the relevant line from /etc/fstab.

tmpfs   /tmp    tmpfs defaults,noatime,mode=1777,nosuid,noexec,nodev  
0  0



Here is the error message.

sudo apt-get dist-upgrade

.

.

Preconfiguring packages ...
Can't exec "/tmp/openvpn.config.NDxHMl": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178.
open2: exec of /tmp/openvpn.config.NDxHMl configure 2.5.1-3+devuan1 
failed: Permission denied at /usr/share/perl5/Debconf/ConfModule.pm 
line 59.

.

.

The (apparent) recommendation from bug report 129289 in 2002 is to set

APT::ExtractTemplates::TempDir
in apt.conf to some directory which is mounted with exec

and
As of version 0.5.8, apt supports TMPDIR for determining where
apt-extracttemplates puts its temporary files. If you have a noexec
/tmp, use this or other documented means to make apt-extracttemplates
use a directory that does accept executables

As of 2018 Bug #887099, merged with sundry other bug reports of the same type
Control: reassign -1 debconf 1.5.61
Control: forcemerge 566247 -1
This appears to be a generic issue in debconf, so I'm reassigning it to
debconf and merging it with the existing bugs tracking the same issue.

There doesn't seem to be any activity after that.

Is there a best practice for the method of selecting and setting this 
directory?


Thanks,

Ken



Replying to my own message:

It appears that this problem with debconf has been around for 2 
decades and


the maintainers are at odds with the debian position about "/tmp" and 
noexec.



That being said I am going with

echo "APT::ExtractTemplates::TempDir \"/var/tmp\";" 
>/etc/apt/apt.conf.d/50extracttemplates


unless someone has a better idea or a reason not to.

I am aware that Debian does not by default clean up /var/tmp and it 
will be my responsibility to


check it for things left around.

This would just make /var/tmp the target for attacks instead of /tmp  if 
you protect /tmp with noexec, you should do the same with /var/tmp.


I think you could use any root writable dir, I don't see why it would 
need to be writable by all users, if apt* is running as root.


If you think it's simpler, you can create a file, say 
/etc/apt/apt.conf.d/99-remounttmp.conf  with this:



DPkg {
    // Auto re-mounting of a exec-only /tmp
    Pre-Invoke { "mount -o remount,exec /tmp"; };
    Post-Invoke { "test ${NO_APT_REMOUNT:-no} = yes || mount -o 
remount,noexec /tmp || true"; };

};

I don't remember where I found this, but have used it for a while.



Thanks,

Ken


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


--
Hector Gonzalez
ca...@genac.org

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

Re: [DNG] moving to a new system

[Hector Gonzalez Jaime via Dng]

On 6/24/22 10:56, o1bigtenor via Dng wrote:

On Fri, Jun 24, 2022 at 10:19 AM Dr. Nikolaus Klepp via Dng
 wrote:

Anno domini 2022 Fri, 24 Jun 09:05:39 -0500
  o1bigtenor via Dng scripsit:

Greetings

Hoping that I'm not asking too many questions.

(moving from debian testing to devuan testing (daedalus)
the old system is under 5.17.xx and the new one is on 5.18
if that makes for differences)

(I've learnt the hard way that just winging things means a LOT more
work and even a greater chance for issues.)

My existing system has been a work in progress for over 10 years. So
I've gotten things
set up quite the way that I like them so things change slowly but in
that there are also
less 'terror' moments when everything has gone 'goofy'.

Is there any way to move over things like settings (and all the other
pamphernania) for browsers and libreoffice and the like?

I was thinking of doing things by using scp from the old system to the new one.

Dunno if that would create issues or not.

Any better ideas - - - - well I'm all ears!!!

Move your home directory to the new system ... and use rsync, not scp.


That seems simple - - - - except I've never used rsync yet.

Suggestions for a good recipe to follow- - - please?



from the new system (this will overwrite /home files if you have them):

rsync -avxKSH root@oldsystem:/home/ /home/

means make a backup, show what you do, don't change filesystems, keep 
dirlinks, use sparse files, and keep hard links, from 
root@oldsystem:/home/ to your local /home/


Just don't do this for the root filesystem, unless it is to put it 
somewhere else


This will use ssh for authentication, either use a key for 
authenticating, (man ssh-keygen) or change the user to what it needs to be.


man rsync explains the options in detail.  You can interrupt this 
command and run it again, it will continue where it left.




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


--
Hector Gonzalez
ca...@genac.org

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

Re: [DNG] trouble with rdiff-backup

[Hector Gonzalez Jaime via Dng]

On 4/24/22 12:17, Hendrik Boom wrote:

Suddenly it cannot write on a file system.  Presumably the backup drive?  The 
one it has already filled with 215831712 iK blocks and has abother 1608278664 
available?

Then more complaints about banned unicode characters, and then another similar 
backtrace ending with

OSError: [Errno 30] Read-only file system

Is anyone else having problems like these?  Is rdiff-backup busted?  Or is my 
new backup drive or my USB interface busted?


This might mean your system detected a format problem with your backup disk, 
have you tried to remount it?  Check your kernel log,
if there is such a problem it would remount the disk read only.  You can verify 
with the mount command and no arguments.
If that is the case, you should umount the disk, and run fsck on it before 
trying to mount the disk again.

--
Hector Gonzalez
ca...@genac.org

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

Re: [DNG] PHP 8.1 depends on systemd?

[Hector Gonzalez Jaime via Dng]

I has had that dependency for a while, you should try the php packages 
from tdrnetworks:


deb https://pkgs.tdrnetworks.com/apt/devuan chimaera main

On 1/29/22 05:47, Mathieu ROY via Dng wrote:

Hello,

Trying to upgrade to PHP 8.1, I found out it now depends on systemd or 
systemd-tmpfiles (no package available).


https://packages.debian.org/bookworm/php8.1-fpm

Is it a choice made on Debian side or is PHP now really depending on 
systemd?



Regards,

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


--
Hector Gonzalez
ca...@genac.org

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

Re: [DNG] kernel-update: initramfs fails to find swap

[Hector Gonzalez Jaime via Dng]

On 1/21/22 11:03, Florian Zieboll via Dng wrote:

On Fri, 21 Jan 2022 10:34:28 -0500
tempforever  wrote:


Something to check/verify:
If swap is listed in /etc/fstab, then make sure it is listed by UUID
rather than block-id.
I mention this, since I have a (commented out) swap line in /etc/fstab


Yes, in the fstab, the swap partition is active and defined by (the
correct) UUID.
You should try the kernel in backports, 5.10.x failed to find my root 
partition, removing -quiet made it work sometimes, and changing to 5.15 
fixed it.

___
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] Refracta have a static IP

[Hector Gonzalez Jaime via Dng]

On 7/13/21 3:41 PM, Steve Litt wrote:

Hi all,

I'm trying to make my new Chimera based Refracta have a static IP
address at 192.168.0.199/24, in order that every other computer on the
192.168.0.0/24 subnet can easily access it, and so I can put it on my
LAN DNS.

So I made my /etc/network/interfaces look like the following, which
follows the guidelines of "man interfaces":

===
auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet static
   address 192.168.0.199
   gateway 192.168.0.1
===

Unfortunately, instead of the IP address being 192.168.0.199, it's a
DHCP supplied 192.168.0.204 . What additional steps must I take to get
my desired 192.168.0.199?
Steve, this happens when you still have a dhcp client running, Check if 
you have something like isc-dhcp-client running and stop it, then you 
can configure the interface on your own.

Additional note: When I used 192.168.0.40, which I KNOW is not in my
leased DHCP range, the result was the same. What must I do to get a
static IP at 192.168.0.199/24 ?

Thanks,

SteveT

Steve Litt
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


--
Hector Gonzalez
ca...@genac.org

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

Re: [DNG] routing tables.

[Hector Gonzalez Jaime via Dng]

On 5/17/21 1:35 PM, Hendrik Boom wrote:

I have found several authoritative-looking web pages on instructions to
display and edit the routing tables.

But none of them explains what the routing tabe entries *mean*.


The routing table entries show the way your host can find other 
networks, local or remote.  Each entry describes how to reach every 
connected network, and what it considers to be local to your 
connection.  A special route, the default route, shows how to reach 
networks outside of your local scope.


Other routing table entries may show how to reach other networks.

When you configure your interface ethv0, a route to its local network 
will be shown, for example:


with "ip route":

192.168.1.0/24 dev ethv0 proto kernel scope link src 192.168.1.10

with "netstat -rn" :

Destination Gateway Genmask Flags   MSS Window  irtt 
Iface
192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
ethv0


They both describe the same route, to network 192.168.1.0, with a 24 bit 
netmask (meaning you have 8 bits left for hosts in your network, from 
192.168.1.1 to 192.168.1.254, with 192.168.1.0 being used to reference 
the network itself, and 192.168.1.255 as the broadcast address, where 
you would send data meant for every host in your network).


If you want to reach say network 192.168.90.0/24 which is reacheable via 
host 192.168.1.2, you could add a route like this:


ip route add 192.168.90.0/24 via 192.168.1.2

A special route to network 0.0.0.0/0 is the default route, which is used 
to reach any network of which your host has no knowledge. With ip show 
it looks like this:


default via 192.168.1.1 dev ethv0 onlink

with netstat -rn it looks like this:

Destination Gateway Genmask Flags   MSS Window  irtt 
Iface

0.0.0.0 192.168.1.1   0.0.0.0 UG    0 0  0 ethv0

With route it can be added as:

route add -net default gw 192.168.1.1

once you have your interface configured.

--
Hector Gonzalez
ca...@genac.org

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

Re: [DNG] Fwd: Distribution upgrade issue

[Hector Gonzalez Jaime via Dng]

On 2/22/21 3:30 PM, Antony Stone wrote:

On Monday 22 February 2021 at 22:26:17, Hector Gonzalez Jaime via Dng wrote:


I've seen your original problem frequently, mysql and mariadb both are
turned off during upgrades, and then apt-get goes on to install other
packages, which might require a database to be running and have no
control over this.  A workaround is, whenever you have mysql (or
mariadb) present, update it first and alone, like this:

apt-get update
apt-get install default-mysql-server  # this command depends on your
version, just reinstall mysql's server first.
apt-get upgrade
apt-get dist-upgrade

This way mysql gets updated first, and will be running for the rest of
your system.

I like that - it sounds like an excellent tip (hard to see how it might be
included in an automated update process, but that would of course be even
better).

Have you ever mentioned this to the Debian project, to see whether they
consider this either to be a bug in the upgrade process, or at least a
workaround worth documenting for people doing the upgrade?
I had only seen this with external packages, so, no, I've never 
mentioned it.  I think if packages depend on a database of any kind to 
be updated, they should wait for it to be done before they run their 
scripts, but then again, the database might not even be configured to 
run in the same system.


Antony.


--
Hector Gonzalez
ca...@genac.org

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

Re: [DNG] Fwd: Distribution upgrade issue

[Hector Gonzalez Jaime via Dng]

On 2/22/21 1:59 PM, Curtis Maurand via Dng wrote:



On 2/22/21 4:26 AM, Pontus Goffe via Dng wrote:


Putting this back on list.

I still think you are doing it wrong, after changing your 
sources.list(s) you should, at least

apt-get update
apt-get upgrade
apt-get dist-upgrade


Ah. you have an extra step.  The following is from the website doc.

Update the package lists from the Beowulf repository.

|root@devuan:~# apt-get update|

Devuan Jessie users should now upgrade the Devuan repository keyring, 
and update the package lists again so packages can be authenticated.


|root@devuan:~# apt-get install devuan-keyring|
|root@devuan:~# apt-get update|

If xscreensaver is running you should kill it now as it needs to be 
stopped before it can be upgraded.


|root@devuan:~# killall xscreensaver|

Now you can perform the upgrade.

|root@devuan:~# apt-get dist-upgrade|

I've seen your original problem frequently, mysql and mariadb both are 
turned off during upgrades, and then apt-get goes on to install other 
packages, which might require a database to be running and have no 
control over this.  A workaround is, whenever you have mysql (or 
mariadb) present, update it first and alone, like this:


apt-get update
apt-get install default-mysql-server  # this command depends on your 
version, just reinstall mysql's server first.

apt-get upgrade
apt-get dist-upgrade

This way mysql gets updated first, and will be running for the rest of 
your system.



Hector Gonzalez
ca...@genac.org

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

Re: [DNG] Migrating from Buster to Beowulf - feedback needed

[Hector Gonzalez via Dng]

> On Sep 6, 2019, at 10:41 AM, goli...@devuan.org wrote:
> 
> On 2019-09-06 07:33, Hendrik Boom wrote:
>> On Thu, Sep 05, 2019 at 11:27:03PM -0500, goli...@devuan.org wrote:
>>> Dear Dev1ers,
>>> Many of you have asked how you can help Devuan.  Well, here's an opportunity
>>> - especially for those who keep asking when Beowulf will be released!
>>> There have been reports that the migration process from Debian Buster to
>>> Devuan Beowulf is not as straight-forward as Wheezy/Jessie to Jessie and/or
>>> Stretch to ASCII. If we are to offer migration as an "official" option, we
>>> will need to document specific issues and provide solutions in our
>>> documentation.
>>> So . . . please roll up your sleeves, give it a try and let us know if you
>>> were able to migrate successfully from Buster to Beowulf.  What issues did
>>> you have?  How did you work around them?  Are there any blockers?
>> I've got buster on a partition I never use and was thinking of deleting.
>> I could try crossgrading to beowulf before I delete it.
>> Would that help?  It would not likely get any actual usage to discover
>> problems beyond the actual crossgrade itself.
>> -- hendrik
> 
> Yes.  Please do!  If you can spare the time, would also be helpful to know if 
> the basics work after the migration.  Thanks.
> 
> golinux

I made a Buster droplet with digitalocean, and then upgraded it to Beowulf, 
other than the need to download devuan-keyring by hand, it was painless.  It 
has no desktop software, but apache, mariadb, and php-fpm work fine.

The process was:
update the sources.list and point it to devuan beowulf
download and install devuan-keyring
apt-get install sysvinit-core
reboot
apt-get dist-upgrade
apt-get purge systemd
apt-get purge unscd   #this might be digitalocean´s choice, but it gives me 
trouble adding users and groups.
I think I rebooted another time after this, and that was it.

--
Héctor González
ca...@genac.org

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

Re: [DNG] Switching to OpenRC

[Hector Gonzalez]

On 05/15/2018 06:23 AM, Martin Steigerwald wrote:


This basically did it for me. But this warning has been unhelpful for me:

%:/var/lib/dpkg/info# grep -A 2 "sysv" *openrc*
openrc.postinst:echo "*** WARNING: if you are replacing sysv-rc by OpenRC, 
then you must ***"
openrc.postinst-echo "*** reboot immediately using the following command:
***"
openrc.postinst-echo 'for file in /etc/rc0.d/K*; do s=`basename $(readlink 
"$file")` ; /etc/init.d/$s stop; done'

(Devuan Ascii with sysvinit-core, systemd package already purged)

What this did on my system is: Stop all services and then sit there. It
did not reboot. I asked a co-worker to reboot the machine via the
hypervisor and it worked.



This happens because runlevel 0 ends with "K12halt", so the warning is 
wrong, if you want to reboot you should use runlevel 6, the last command 
it runs is "K12reboot".


--
Héctor González
ca...@genac.org

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

Re: [DNG] machine locks up switching between console and X session

[Hector Gonzalez]

On 04/26/2018 01:05 PM, Lars Noodén wrote:

On 04/26/2018 08:42 PM, Florian Zieboll wrote:
[snip]

in one of your previous mails you pasted the output of your attempt to
install the "nvidia-driver" package. If you follow down the dependency
chain by manually trying to install the "not installable" predepends,
sooner or later you'll reach the package, which is the root of this
problem; apt will give you a more detailed error message for it. [snip]

Thanks.  Following one dependency chain from nvidia-driver-bin, it
arrives at 'nvidia-installer-cleanup' which has no installation candidate.

Looking at the Nvidia site, it looks like the right driver for the
GM108M (GeForce 940MX) might be 390 which should be provided by
nvidia-driver-bin in Devuan.

# apt-cache show nvidia-driver-bin | head -n 3
Package: nvidia-driver-bin
Source: nvidia-graphics-drivers
Version: 390.48-2~bpo9+1

/Lars

# apt-get install nvidia-driver-bin nvidia-alternative
nvidia-legacy-check nvidia-installer-cleanup
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package nvidia-installer-cleanup is not available, but is referred to by
another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'nvidia-installer-cleanup' has no installation candidate
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
I have that package installed, this is the list of nvidia related 
packages in my system (running ascii):


ii  glx-alternative-nvidia 
0.7.4   amd64 allows the 
selection of NVIDIA as GLX provider
ii  libegl-nvidia0:amd64 
375.82-1~deb9u1 amd64 NVIDIA binary 
EGL library
ri  libegl1-nvidia:amd64 
375.82-1~deb9u1 amd64 NVIDIA binary 
EGL library (non-GLVND variant)
ii  libgl1-nvidia-glx:amd64 
375.82-1~deb9u1 amd64 NVIDIA binary 
OpenGL/GLX library (non-GLVND variant)
ii  libgl1-nvidia-glx:i386 
375.82-1~deb9u1 i386 NVIDIA binary 
OpenGL/GLX library (non-GLVND variant)
ii  libgldispatch0-nvidia:amd64 
375.82-1~deb9u1 amd64 Vendor neutral 
GL dispatch library -- libGLdispatch
ii  libglx-nvidia0:amd64 
375.82-1~deb9u1 amd64 NVIDIA binary 
GLX library
ii  libglx0-glvnd-nvidia:amd64 
375.82-1~deb9u1 amd64 Vendor neutral 
GL dispatch library -- libGLX
ii  libnvidia-eglcore:amd64 
375.82-1~deb9u1 amd64 NVIDIA binary 
EGL core libraries
ii  libnvidia-glcore:amd64 
375.82-1~deb9u1 amd64 NVIDIA binary 
OpenGL/GLX core libraries
ri  libnvidia-glcore:i386 
375.82-1~deb9u1 i386 NVIDIA binary 
OpenGL/GLX core libraries
ri  libnvidia-ml1:amd64 
375.82-1~deb9u1 amd64 NVIDIA 
Management Library (NVML) runtime library
ii  nvidia-alternative 
375.82-1~deb9u1 amd64 allows the 
selection of NVIDIA as GLX provider
ii  nvidia-detect 375.82-1~deb9u1 
amd64 NVIDIA GPU detection utility
ri  nvidia-driver 375.82-1~deb9u1 
amd64 NVIDIA metapackage
ri  nvidia-driver-bin 
375.82-1~deb9u1 amd64 NVIDIA driver 
support binaries
ii  nvidia-driver-libs:amd64 
375.82-1~deb9u1 amd64 NVIDIA 
metapackage (OpenGL/GLX/EGL/GLES libraries)
ii  nvidia-installer-cleanup 
20151021+4  amd64 cleanup after 
driver installation with the nvidia-installer
ri  nvidia-kernel-common 
20151021+4  amd64 NVIDIA binary 
kernel module support files
ri  nvidia-kernel-dkms 
375.82-1~deb9u1 amd64 NVIDIA binary 
kernel module DKMS source
ii  nvidia-kernel-source 
375.82-1~deb9u1 amd64 NVIDIA binary 
kernel module source
ri  nvidia-kernel-support 
375.82-1~deb9u1 amd64 NVIDIA binary 
kernel module support files
ii  nvidia-legacy-check 
375.82-1~deb9u1 amd64 check for 
NVIDIA GPUs requiring a legacy driver
ii  nvidia-modprobe 384.111-2~deb9u1    
amd64 utility to load NVIDIA kernel modules and create device nodes
ii  nvidia-settings 384.111-1~deb9u1    
amd64 tool for configuring the NVIDIA graphics driver
ri  nvidia-support 20151021+4  
amd64 NVIDIA binary graphics driver support files
ri  nvidia-vdpau-driver:amd64 
375.82-1~deb9u1 amd64 Vi

Re: [DNG] New policykit-1 packages in ASCII

[Hector Gonzalez]

On 04/19/2018 09:33 AM, Edward Bartolo wrote:

Quoting output from 'apt-get upgrade':
"he following packages have been kept back:
   desktop-base libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0
   linux-image-amd64 policykit-1"

Still NO luck! Only logoff works in XFCE under ASCII. However, the
power button still succeeds to tell the OS to shutdown.
Edward, I just tried this with XFCE under ASCII, but used  'apt-get 
dist-upgrade'  because it needs to pull some dependencies.

all buttons work, logout, shutdown, suspend...

--
Héctor González
ca...@genac.org

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

Re: [DNG] Error when upgrading eudev

[Hector Gonzalez]

On 02/12/2018 03:54 PM, KatolaZ wrote:

On Mon, Feb 12, 2018 at 03:44:16PM -0600, Hector Gonzalez wrote:

[cut]


Please send the full report of:

   apt-cache policy eudev
   apt-cache policy udev

Here it is, I had backports enabled, removed it and the situation remains
the same.

With ascii-backports:

apt-cache policy eudev
eudev:
   Installed: 3.2.2-devuan2.7
   Candidate: 3.2.2-devuan2.7
   Version table:
  *** 3.2.2-devuan2.7 100
     100 /var/lib/dpkg/status
  3.2.2-11 500
     500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages


Hector, eudev_3.2.2-devuan2.7 is a very old version, replaced about
2.5 months ago (and with a wrong +devuan version number).

You should be able to solve the problem with:

   # apt-get install eudev=3.2.2-11 libeudev1=3.2.2-11

HTH

Thank you, that fixed it.



KatolaZ



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


--
Héctor González
ca...@genac.org

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

Re: [DNG] Error when upgrading eudev

[Hector Gonzalez]

On 02/12/2018 03:29 PM, KatolaZ wrote:

On Mon, Feb 12, 2018 at 03:20:11PM -0600, Hector Gonzalez wrote:


On 02/12/2018 02:18 PM, KatolaZ wrote:

The new version of eudev (3.2.2-11) just hit the repos and is already
available from pkgmaster.devuan.org. Thanks a lot to Svante. I will
have a look at the push glitch later on.

Is it available for i386?  I have a multiarch config and if I try to upgrade
it it gives this error:

  libeudev1 : Breaks: libeudev1:i386 (!= 3.2.2-devuan2.7) but 3.2.2-11 is to
be installed
  libeudev1:i386 : Breaks: libeudev1 (!= 3.2.2-11) but 3.2.2-devuan2.7 is to
be installed



Please send the full report of:

   apt-cache policy eudev
   apt-cache policy udev
Here it is, I had backports enabled, removed it and the situation 
remains the same.


With ascii-backports:

apt-cache policy eudev
eudev:
  Installed: 3.2.2-devuan2.7
  Candidate: 3.2.2-devuan2.7
  Version table:
 *** 3.2.2-devuan2.7 100
    100 /var/lib/dpkg/status
 3.2.2-11 500
    500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages

apt-cache policy udev
udev:
  Installed: 1:3.2.2+devuan2.10
  Candidate: 1:3.2.2+devuan2.10
  Version table:
 *** 1:3.2.2+devuan2.10 500
    500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
    100 /var/lib/dpkg/status
 236-3~bpo9+1 100
    100 http://pkgmaster.devuan.org/merged ascii-backports/main 
amd64 Packages


Without ascii-backports:

apt-cache policy eudev
eudev:
  Installed: 3.2.2-devuan2.7
  Candidate: 3.2.2-devuan2.7
  Version table:
 *** 3.2.2-devuan2.7 100
    100 /var/lib/dpkg/status
 3.2.2-11 500
    500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages

apt-cache policy udev
udev:
  Installed: 1:3.2.2+devuan2.10
  Candidate: 1:3.2.2+devuan2.10
  Version table:
 *** 1:3.2.2+devuan2.10 500
    500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
    100 /var/lib/dpkg/status

And the last one for i386:

apt-cache policy eudev:i386
eudev:i386:
  Installed: (none)
  Candidate: 3.2.2-11
  Version table:
 3.2.2-11 500
    500 http://pkgmaster.devuan.org/merged ascii/main i386 Packages

apt-cache policy udev:i386
udev:i386:
  Installed: (none)
  Candidate: 1:3.2.2+devuan2.10
  Version table:
 1:3.2.2+devuan2.10 500
    500 http://pkgmaster.devuan.org/merged ascii/main i386 Packages



   
HND


KatolaZ




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


--
Héctor González
ca...@genac.org

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

Re: [DNG] Error when upgrading eudev

[Hector Gonzalez]

On 02/12/2018 02:18 PM, KatolaZ wrote:

The new version of eudev (3.2.2-11) just hit the repos and is already
available from pkgmaster.devuan.org. Thanks a lot to Svante. I will
have a look at the push glitch later on.
Is it available for i386?  I have a multiarch config and if I try to 
upgrade it it gives this error:


 libeudev1 : Breaks: libeudev1:i386 (!= 3.2.2-devuan2.7) but 3.2.2-11 
is to be installed
 libeudev1:i386 : Breaks: libeudev1 (!= 3.2.2-11) but 3.2.2-devuan2.7 
is to be installed





HND

KatolaZ



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


--
Héctor González
ca...@genac.org

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

Re: [DNG] git - gnutls_handshake() failed

[Hector Gonzalez]

On 02/07/2018 01:23 PM, dev wrote:

Hello all,
Would someone on Ascii please try cloning this repo and reply? I'm
getting a gnutls error and not sure where to look for the problem.
Thanks


$ git clone https://github.com/Eronarn/deploying-applications-with-ansible

Cloning into 'deploying-applications-with-ansible'...
fatal: unable to access
'https://github.com/Eronarn/deploying-applications-with-ansible/':
gnutls_handshake() failed: Public key signature verification has failed.
This is probably caused by an old library stuck in your system from 
jessie, I had the same, you might be seeing this bug: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834724


Check if you have libgnutls-deb0-28 installed and remove it.  If it 
would uninstall more packages, you may have mixed repositories (I had 
packages installed from debian-multimedia causing this)

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


--
Héctor González
ca...@genac.org

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

Re: [DNG] desktop screen recording with sound?

[Hector Gonzalez]

On 02/02/2018 04:36 PM, KatolaZ wrote:

On Fri, Feb 02, 2018 at 04:24:33PM -0600, goli...@dyne.org wrote:

On 2018-02-02 15:51, dev wrote:

On 02/02/2018 02:53 PM, KatolaZ wrote:

This is not a mish-mash. This is basically a Debian jessie with
additional wheezy and Ubuntu repos... :) No surprise you have problems
with dependencies.


Alrighty then... time to upgrade to Ascii. I'll see if I can find the
howto.

Thanks
___


I can't believe you'll be able to upgrade that broken install.  Start fresh
with a new Jessie install and upgrade to ascii with a proper sources.list
for devuan only..


Well, with appropriate pinning you can probably turn whatever modern
Debian derivative into a Debian etch, if you like (the main problem
being to find a mirror that still has Debian etch, but I must have the
fill CD set somewhere...) :P



You can use http://archive.debian.org/debian/dists/etch/ -or any of the 
other versions there-


It's probably easier, if you have LVM and spare space, to create a new 
volume, install with debootstrap, bind mount /dev, /dev/pts, /proc and 
/sys, chroot to it, make a new initrd, and point grub to boot from it.  
It needs you to have a proper fstab, install a kernel, grub2 (grub-pc if 
I remember correctly), and any software you might need to boot, like 
lvm, mdadm and any firmware your machine requires.


Check carefully your grub configuration to make sure it will boot.



So I guess it must be possible to get a proper devuan jessie/ascii
from a MeDeBunVuan, without reinstalling.

I have never needed to reinstall a De??an on a machine, except for an
upgrade from wheezy to Debian jessie/testing that failed miserably,
for the first time ever. I guess that was some kind of signal sent by
the universe, that I didn't understand on that occasion (it was year 2
BD1 [Before Devuan] ) ;)

HND

KatolaZ



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


--
Héctor González
ca...@genac.org

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

Re: [DNG] Help with Spectre and Meltdow

[Hector Gonzalez]

On 01/17/2018 11:51 AM, William C Vaughan wrote:

Date: Wed, 17 Jan 2018 14:09:09 +0100
From: Didier Kryn mailto:k...@in2p3.fr>>
To: dng@lists.dyne.org 
Subject: Re: [DNG] Help with Spectre and Meltdown
Message-ID: <1bf9d308-fc02-7cf6-7a70-50c817e24...@in2p3.fr 
>

Content-Type: text/plain; charset=utf-8; format=flowed

Le 17/01/2018 à 13:59, vmlinux a écrit :
>
> On January 16, 2018 6:50:32 PM CST, KatolaZ > wrote:

> [Snip]
>
> ::
> ::The only affected component is the kernel. Patch exist for jessie,
> ::AFAWN, there is no way to
> ::effectively patch Spectre.
>
> I haven't had time to actually read up on it, however, isn't there a micro code mitigation 
available from Intel? I'm assuming this is some sort of cpu firmware 
update but not sure you can flash a cpu :/ so...

>
> https://www.reddit.com/r/sysadmin/comments/7pe2ew/intel_spectre_microcode_update/.compact 


>
 Still reading (subjects only) the mailing list of Linux on Dell
Poweredge, it seems they provide a means do download and install a new
microcode. Dunno how to do the same core-i7 of my laptop...



intel microcode is available as a debian package (non-free), you can see 
the tracker here: https://tracker.debian.org/pkg/intel-microcode you 
want the version from 20180108 which is in testing.  The package adds 
firmware patches during boot, and they stay in memory, so the package 
should remain installed afterwards.  The process is explained here:  
https://wiki.debian.org/Microcode


There are trackers for the CVE's associated with spectre too:

https://security-tracker.debian.org/tracker/CVE-2017-5715
https://security-tracker.debian.org/tracker/CVE-2017-5753

The xenbits.xen.org link in the notes of these trackers has a good 
explanation of the bugs.



     Didier

I just flashed the EFI/BIOS on my I7 XPS-13 several days ago. For 
non-Windows machines you copy the provided DOS ".exe" to a USB, 
restart the machine, and hit F12 (nearly always on Dell) and select 
"Flash / update the BIOS" or something close to that, after which just 
follow the instructions. Most newer Dell machines have the SA-00086 
updates available. Older machines might not.  Here's the relevant link:


Dell intel flash patches for meltdown/spectre 






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


--
Héctor González
ca...@genac.org

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

Re: [DNG] Advice?

[Hector Gonzalez]

On 11/05/2017 09:49 PM, rodolico wrote:

I've been watching devuan for a while, and like what I see. I had
planned a migration of our servers from Debian to a combination of
devuan and freebsd in the future, and have been leaving everything as
LTS wheezy for now.

Now, our plans have to be accelerated due to a recent problem with
wheezy and Xen.

My questions are:

1. is
https://git.devuan.org/dev1fanboy/Upgrade-Install-Devuan/wikis/Upgrade-to-Devuan
still the way to go?
I haven't had a problem with it, but you should try this with a virtual 
server first.  You can use a virtualbox machine as a Xen Dom0, and test 
your process there (yes, I've done that).



2. Has anyone tested Xen (as a DOM0) with devuan, or will we be doing
this first.


Yes, It works fine, I have several Xen Dom0 running in production, the 
oldest one has been running devuan for over a year now, it has 20 DomU's 
now.



Any suggestions/recommendations would be greatly appreciated.
Make backups, test your backups, and don't overwrite your backups with 
new versions, and try out your process with virtual machines first.


Rod


--
Héctor González
ca...@genac.org

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

Re: [DNG] New behaviour under Devuan.

[Hector Gonzalez]

On 09/22/2017 05:10 AM, Didier Kryn wrote:

Le 22/09/2017 à 01:32, Arnt Karlsen a écrit :

You can probably justify 'xhost +' if this is one of those
I'm-the-only-user machines.  Thank Ghu, remote network access to the X
server is no longer enabled by default on Linux hosts.  (The right way
to do remote X11, IMO, is via 'ssh -yu...@example.com', thereby
forwarding X11 across the authenticated ssh tunnel.)

One can argue that you should use 'ssh -Y' even locally so you get out
of the habit of using 'xhost +'.  I won't argue that, but will just
put it out there.

..my prefecence was the -X option: ssh -X root@localhost
until Debian killed it with some new policy.


AFAIR, ssh -Y is used for backward compatibility with old software 
(like libroot), but, normally, -X is enough.


I don't know how one can prevent you from running ssh -X 
root@localhost . Permission to do so is set/unset in 
/etc/ssh/sshd_config .


But gksu or gksudo do not require ssh at all.


You can also do this, assuming your original user is "user":
XAUTHORITY=~user/.Xauthority
export XAUTHORITY
DISPLAY=:0.0
export DISPLAY
and use x with that.  You don't add permissions, and there is no need to 
use ssh to forward localhost connections.  If XAUTHORITY is missing, you 
need xauth installed, but that should already be there if you have ssh 
and X anyway.  root should have permission to read ~user/.Xauthority 
unless you are using a non local home directory.


--
Héctor González
ca...@genac.org

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

Re: [DNG] using os-prober

[Hector Gonzalez]

On 08/28/2017 06:59 PM, Hendrik Boom wrote:

On Mon, Aug 28, 2017 at 06:50:42PM -0500, Hector Gonzalez wrote:

On 08/28/2017 06:35 PM, Hendrik Boom wrote:

On Mon, Aug 28, 2017 at 03:56:13PM -0700, Gregory Nowak wrote:

On Mon, Aug 28, 2017 at 06:37:04PM -0400, Hendrik Boom wrote:

Now I can't figure out how to set options so that update-grub uses
os-prober.

You do have the os-prober package installed, yes?

Yes.

root@notlookedfor:/boot/grub# which os-prober
/usr/bin/os-prober
root@notlookedfor:/boot/grub#

I'm running a Devuan Jessie system.
-- hendrik


I did this a few days ago, try commenting out the option completely, the
default is to run os-prober.

Originally, the option was not present at all.  I added the option in
myself.  Being totally absent should be as good as commented out,
right?

Anyway, as I mentined in another post a few minutes ago, it does seem
to be recognising it after all, but as a unknown Linux distro,
failing tto notice it's Devun.  And I don't get a bootmenu stanza.

-- hendrik
Ok, I just found out the problem with my test install, I installed with 
debootstrap, but forgot to add a kernel.  Please check your /target/boot 
directory, it may be empty, os-prober finds library files, and assumes 
it's a bootable linux system, but checks for a kernel at a later time.  
If you want it identified as a debian system, copy etc/devuan_version to 
etc/debian_version (I don't know if it has any side effects, but it's 
easier to rename the grub entry).


--
Héctor González
ca...@genac.org

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

Re: [DNG] using os-prober

[Hector Gonzalez]

On 08/28/2017 06:35 PM, Hendrik Boom wrote:

On Mon, Aug 28, 2017 at 03:56:13PM -0700, Gregory Nowak wrote:

On Mon, Aug 28, 2017 at 06:37:04PM -0400, Hendrik Boom wrote:

Now I can't figure out how to set options so that update-grub uses
os-prober.

You do have the os-prober package installed, yes?

Yes.

root@notlookedfor:/boot/grub# which os-prober
/usr/bin/os-prober
root@notlookedfor:/boot/grub#

I'm running a Devuan Jessie system.
  
-- hendrik




I did this a few days ago, try commenting out the option completely, the 
default is to run os-prober.


--
Héctor González
ca...@genac.org

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

Re: [DNG] d1h pre-requisites

[Hector Gonzalez]

The package is called gnupg, itis on jessie, and if I recall correctly, 
it should also be already part of your system.  You can find out with:  
dpkg -l | grep gnupg



On 08/17/2017 10:00 AM, Gary Olzeke wrote:
Trying to follow the d1h article at dev1galaxy.org 
 id=#549

it says it needs "gpg (for package signing)"
apt-get can't find the package on jessie   or experimental-main
'
that should mean that it isn't in debian either ??!!
'
I found this from google  - is it the same?
GnuPG  2.1.23 2017-08-09 6373k

TIA - garyz



--
Héctor González
ca...@genac.org

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

Re: [DNG] Devuan ready VPS?

[Hector Gonzalez]

On 06/07/2017 10:43 AM, Emiliano Marini wrote:
Yep, but often they compile and ship they're own flavours of Debian 
using custom kernels, and pointing apt to their own repos.


Have someone tried a migration to Devuan on a DigitalOcean droplet?


I have several, some with DO's debian kernel, and others with devuan's 
kernel.


To boot devuan's kernel you just install the kernel package, and grub, 
and then select "DigitalOcean GrubLoader v0.2" from the droplet's kernel 
menu.


--
Héctor González
ca...@genac.org

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

Re: [DNG] problem installing postgresql

[Hector Gonzalez]

On 04/18/2017 08:52 PM, Hendrik Boom wrote:
> In the middle of installing several packages using
> apt-get install postgresql ruby-sass
> I get a message.
>
> Setting up postgresql-common (165+deb8u2) ...
> supported-versions: WARNING! Unknown distribution: devuan
> /usr/share/postgresql-common/supported-versions: 64: 
> /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter not set
> /usr/share/postgresql-common/supported-versions: 67: 
> /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter not set
> Please submit this as a bug report to your distribution.
> Adding user postgres to group ssl-cert
>
> Evidently postgresql doesn't know about devuan.
> Could it be because I don't have a /etc/debian_version file, but only 
> a /etc/devuan_version file?  Or does it discover I'm using devuan by 
> other means?
>
> -- hendrik
Please check https://git.devuan.org/devuan/devuan-project/issues/57 
Joril made a patch that fixes this.


-- 

Héctor González
ca...@genac.org

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

Re: [DNG] defective RAID

[Hector Gonzalez]

On 03/27/2017 10:14 AM, Hendrik Boom wrote:


Indeed, I have one RAID with old metadata with only /boot on it.
Another with new metadata containing many LVM partitions.

you can erase the partitions (and metadata) on the outdated disk, 
booting from a rescue CD (or live CD), with the updated disk 
disconnected, that way you don't risk any accidental RAID operation.  
Then boot from the updated disks, and then you can re-create the 
partitions and use mdadm to fix it.



--
Héctor González
ca...@genac.org

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