Posts by vazhnov

vazhnov · Other Issues

Where should I file a ticket — in bugs.devuan.org or in bugs.debian.org?

vazhnov · Other Issues

Checked with clean minimal Devuan 5 Daedalus installation: the same issue.

put openrc package on hold,
installed usrmerge,

upgraded to Devuan 6 Excalibur,

 % dpkg -l | { head -n4; grep -E -i 'sysvinit|sysv-rc|openrc|runit|sinit|66-devuan'; }
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                Version                  Architecture Description
ii  openrc                              0.45.2-2+deb12u1         amd64        dependency based service manager (runlevel change mechanism)
ii  runit-helper                        2.16.3                   all          dh-runit implementation detail
rc  sysv-rc                             3.06-4devuan3            all          System-V-like runlevel change mechanism
ii  sysvinit-core                       3.09-2devuan1            amd64        System-V-like init
ii  sysvinit-utils                      3.09-2devuan1            amd64        System-V-like utilities

 % sudo tail /var/log/boot
Mon Jul 22 02:29:13 2024: bound to 10.0.2.15 -- renewal in 35829 seconds.
Mon Jul 22 02:29:13 2024: done.
Mon Jul 22 02:29:13 2024: Cleaning up temporary files....
Mon Jul 22 02:29:13 2024:  * Mounting cgroup filesystem ...                                                                                                                         [ ok ]
INIT: Entering runlevel: 2
Mon Jul 22 02:29:14 2024: Setting up console font and keymap...done.
Mon Jul 22 02:29:14 2024: Starting enhanced syslogd: rsyslogd.
Mon Jul 22 02:29:14 2024: Starting periodic command scheduler: cron.
Mon Jul 22 02:29:14 2024: Starting system message bus: dbus.
Mon Jul 22 02:29:14 2024: Starting session management daemon: elogind.
Mon Jul 22 02:29:14 2024: Starting OpenBSD Secure Shell server: sshd.
Mon Jul 22 02:29:14 2024:  * ERROR: rc.local needs service(s) 0, 6

restarted the OS,

then upgraded the openrc package only:

alexey@devuan6-aqemu1 ~ % sudo apt-get -V --no-install-recommends dist-upgrade                               
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
   librc1 (0.45.2-2+deb12u1)
The following NEW packages will be installed:
   librc1t64 (0.54.2-1)
The following packages will be upgraded:
   openrc (0.45.2-2+deb12u1 => 0.54.2-1)
1 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 217 kB of archives.
After this operation, 82.9 kB of additional disk space will be used.
…
 * Caching service dependencies ...
Service `rc.local' needs non existent service `0'
Service `rc.local' needs non existent service `6'
Error: udev is the name of a real and virtual service.                                                                                                                                      [ ok ]
…

and restarted the OS. OpenSSH couldn't start, I had to start it manually from console:

alexey@devuan6-aqemu1 ~ % sudo tail /var/log/boot
INIT: Entering runlevel: 2
Mon Jul 22 02:39:27 2024: Setting up console font and keymap...done.
Mon Jul 22 02:39:27 2024: Starting enhanced syslogd: rsyslogd.
Mon Jul 22 02:39:28 2024: Starting periodic command scheduler: cron.
Mon Jul 22 02:39:28 2024: Starting system message bus: dbus.
Mon Jul 22 02:39:28 2024: Starting session management daemon: elogind.
Mon Jul 22 02:39:28 2024: Starting OpenBSD Secure Shell server: sshd * start-stop-daemon: pam error: Authentication failure
Mon Jul 22 02:39:28 2024:  * start-stop-daemon: failed to start `/usr/sbin/sshd'
Mon Jul 22 02:39:28 2024:  failed!
Mon Jul 22 02:39:28 2024:  * ERROR: rc.local needs service(s) 0, 6

And also workaround with copying /usr/sbin/start-stop-daemon into /usr/lib/rc/sbin/start-stop-daemon solves the issue.

vazhnov · Other Issues

Currently there are two versions of start-stop-daemon binaries from two packages:

 % dpkg -S start-stop-daemon|sort                      
dpkg: /usr/sbin/start-stop-daemon
dpkg: /usr/share/man/de/man8/start-stop-daemon.8.gz
dpkg: /usr/share/man/fr/man8/start-stop-daemon.8.gz
dpkg: /usr/share/man/man8/start-stop-daemon.8.gz
dpkg: /usr/share/man/nl/man8/start-stop-daemon.8.gz
dpkg: /usr/share/man/pt/man8/start-stop-daemon.8.gz
dpkg: /usr/share/man/sv/man8/start-stop-daemon.8.gz
openrc: /usr/lib/rc/sbin/start-stop-daemon
openrc: /usr/lib/rc/sh/start-stop-daemon.sh

They are different:

 % file /usr/sbin/start-stop-daemon /usr/lib/rc/sbin/start-stop-daemon
/usr/sbin/start-stop-daemon:        ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=fb0de15cbe08c53aa308fddb2925afe3423ed34e, for GNU/Linux 3.2.0, stripped
/usr/lib/rc/sbin/start-stop-daemon: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=6b69feea4068615a048ce10c763efb5869f798f8, for GNU/Linux 3.2.0, stripped

As an experiment, I decided to make OpenRC version of start-stop-daemon as the main one:

sudo cp -pv /usr/sbin/start-stop-daemon /usr/sbin/start-stop-daemon.dpkg
sudo cp -pv /usr/lib/rc/sbin/start-stop-daemon /usr/sbin/start-stop-daemon

After this change, I see no difference in Devuan shutdown/start (the same errors and SSHD can't start), but this time I couldn't start SSHD manually with sudo /etc/init.d/ssh start, I received the same error "start-stop-daemon: pam error: Authentication failure". Before the binaries swap, I was able to start the SSHD manually.

Then I returned binaries back and made second experiment:

sudo cp -pv /usr/sbin/start-stop-daemon.dpkg /usr/lib/rc/sbin/start-stop-daemon

And now my system starts and stops normally, SSHD starts automatically!

vazhnov · Other Issues

fsmithred, thanks. This is OpenRC-related issue, probably connected with an upgrade openrc:amd64 (0.54-2, 0.54.2-1).

I've added rc_verbose=yes into /etc/rc.conf and now I see in /var/log/boot:

Tue Jul  9 00:07:18 2024: Starting system message bus: dbus * start-stop-daemon: fopen `/var/run/dbus/pid': No such file or directory
Tue Jul  9 00:07:18 2024:  * Detaching to start `/usr/bin/dbus-daemon' ...
Tue Jul  9 00:07:18 2024: .
Tue Jul  9 00:07:18 2024:  * Executing: /usr/lib/rc/sh/openrc-run.sh /usr/lib/rc/sh/openrc-run.sh /etc/init.d/avahi-daemon start
Tue Jul  9 00:07:18 2024: Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Tue Jul  9 00:07:18 2024:  * Executing: /usr/lib/rc/sh/openrc-run.sh /usr/lib/rc/sh/openrc-run.sh /etc/init.d/bootlogs start
Tue Jul  9 00:07:19 2024:  * Executing: /usr/lib/rc/sh/openrc-run.sh /usr/lib/rc/sh/openrc-run.sh /etc/init.d/console-setup.sh start
Tue Jul  9 00:07:19 2024: Setting up console font and keymap...done.
Tue Jul  9 00:07:19 2024:  * Executing: /usr/lib/rc/sh/openrc-run.sh /usr/lib/rc/sh/openrc-run.sh /etc/init.d/cron start
Tue Jul  9 00:07:19 2024: Starting periodic command scheduler: cron.
Tue Jul  9 00:07:19 2024:  * Executing: /usr/lib/rc/sh/openrc-run.sh /usr/lib/rc/sh/openrc-run.sh /etc/init.d/earlyoom start
Tue Jul  9 00:07:19 2024:  * Executing: /usr/lib/rc/sh/openrc-run.sh /usr/lib/rc/sh/openrc-run.sh /etc/init.d/elogind start
Tue Jul  9 00:07:19 2024: Starting session management daemon: elogind * start-stop-daemon: fopen `/run/elogind.pid': No such file or directory
Tue Jul  9 00:07:19 2024:  * Detaching to start `/usr/libexec/elogind' ...
Tue Jul  9 00:07:19 2024: .
Tue Jul  9 00:07:19 2024:  * Executing: /usr/lib/rc/sh/openrc-run.sh /usr/lib/rc/sh/openrc-run.sh /etc/init.d/sudo start
Tue Jul  9 00:07:19 2024:  * Executing: /usr/lib/rc/sh/openrc-run.sh /usr/lib/rc/sh/openrc-run.sh /etc/init.d/rmnologin start
Tue Jul  9 00:07:19 2024:  * Executing: /usr/lib/rc/sh/openrc-run.sh /usr/lib/rc/sh/openrc-run.sh /etc/init.d/rsync start
Tue Jul  9 00:07:19 2024:  * Executing: /usr/lib/rc/sh/openrc-run.sh /usr/lib/rc/sh/openrc-run.sh /etc/init.d/ssh start
Tue Jul  9 00:07:19 2024: Starting OpenBSD Secure Shell server: sshd * start-stop-daemon: fopen `/run/sshd.pid': No such file or directory
Tue Jul  9 00:07:19 2024:  * Detaching to start `/usr/sbin/sshd' ...
Tue Jul  9 00:07:19 2024:  *   start-stop-daemon: pam error: Authentication failure
Tue Jul  9 00:07:20 2024:  *   start-stop-daemon: failed to start `/usr/sbin/sshd'
Tue Jul  9 00:07:20 2024:  failed!
Tue Jul  9 00:07:20 2024:  * ERROR: rc.local needs service(s) 0, 6
Tue Jul  9 00:07:20 2024:  * Executing: /usr/lib/rc/sh/openrc-run.sh /usr/lib/rc/sh/openrc-run.sh /etc/init.d/stop-bootlogd start

I don't have custom records in /etc/fstab to mount /run…

Analysing git diff debian/0.54-2 debian/0.54.2-1 in https://salsa.debian.org/debian/openrc (web diff).

vazhnov · Other Issues

Also I found that after the upgrade, Devuan fails to stop some services at shutdown:

2024-07-07T01:00:07.694393+02:00 devuan6-kube01 shutdown[2776]: shutting down for system reboot
2024-07-07T01:00:07.802340+02:00 devuan6-kube01 init: Switching to runlevel: 6
2024-07-07T01:00:07.803922+02:00 devuan6-kube01 kernel: Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
2024-07-07T01:00:07.810263+02:00 devuan6-kube01 init: No inittab.d directory found
2024-07-07T01:00:07.916679+02:00 devuan6-kube01 start-stop-daemon: Will stop /usr/sbin/sshd
2024-07-07T01:00:07.916702+02:00 devuan6-kube01 start-stop-daemon: Will stop PID 1833
2024-07-07T01:00:07.917112+02:00 devuan6-kube01 start-stop-daemon: Sending signal 15 to PID 1833
2024-07-07T01:00:07.950597+02:00 devuan6-kube01 /etc/init.d/rsync[2806]: ERROR: rsync failed to stop
2024-07-07T01:00:08.032347+02:00 devuan6-kube01 start-stop-daemon: Will stop PID 1765
2024-07-07T01:00:08.032929+02:00 devuan6-kube01 start-stop-daemon: Sending signal 15 to PID 1765
2024-07-07T01:00:08.216425+02:00 devuan6-kube01 avahi-daemon[1643]: Got SIGTERM, quitting.
2024-07-07T01:00:08.217919+02:00 devuan6-kube01 avahi-daemon[1643]: Leaving mDNS multicast group on interface eth0.IPv6 with address 2a01:112f:xxx:yyy:zzz:xxx:yyy:zzz.
2024-07-07T01:00:08.218882+02:00 devuan6-kube01 avahi-daemon[1643]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.155.137.
2024-07-07T01:00:08.219253+02:00 devuan6-kube01 avahi-daemon[1643]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1.
2024-07-07T01:00:08.219426+02:00 devuan6-kube01 avahi-daemon[1643]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
2024-07-07T01:00:08.236026+02:00 devuan6-kube01 avahi-daemon[1643]: avahi-daemon 0.8 exiting.
2024-07-07T01:00:08.364213+02:00 devuan6-kube01 start-stop-daemon: Will stop PID 1625
2024-07-07T01:00:08.364234+02:00 devuan6-kube01 start-stop-daemon: Will stop processes owned by UID 100
2024-07-07T01:00:08.364783+02:00 devuan6-kube01 start-stop-daemon: Sending signal 15 to PID 1625
2024-07-07T01:00:08.387275+02:00 devuan6-kube01 /etc/init.d/dbus[2928]: ERROR: dbus failed to stop

vazhnov · Other Issues

Hi!

I have a Proxmox host with KVM virtual machine with Devuan GNU/Linux 6 (excalibur/ceres) + OpenRC init.

Yesterday I've installed updates in the virtual machine guest and after reboot, SSHD couldn't start:

/var/log/syslog:

2024-07-07T01:00:42.824732+02:00 devuan6-kube01 /etc/init.d/ssh[1822]: start-stop-daemon: pam error: Authentication failure
2024-07-07T01:00:42.830420+02:00 devuan6-kube01 /etc/init.d/ssh[1821]: start-stop-daemon: failed to start `/usr/sbin/sshd'

Updates, from /var/log/apt/history.log:

Start-Date: 2024-07-07  00:59:42
Commandline: apt-get -V --no-install-recommends dist-upgrade
Requested-By: alexey (1000)
Upgrade: base-passwd:amd64 (3.6.3, 3.6.4), libeinfo1:amd64 (0.54-2, 0.54.2-1), gping:amd64 (1.16.1-1, 1.16.1-2), debian-keyring:amd64 (2024.03.24, 2024.06.24), librc1t64:amd64 (0.54-2, 0.54.2-1), openrc:amd64 (0.54-2, 0.54.2-1), ruby-xmlrpc:amd64 (0.3.2-2, 0.3.3-2)
End-Date: 2024-07-07  00:59:56

When I login through KVM console and start the service manually with sudo service ssh start, it starts.

I will investigate this. Just wanted to notify users to not install the latest updates if they have similar configuration.

vazhnov · ARM Builds

Just FYI: I've installed Debian OS image https://raspi.debian.net/tested/2023061 … orm.img.xz and it has no obsolete packages.

After the first boot, I successfully updated all the packages, including Linux kernel:

root@rpi3-20230612:~# uname -a
Linux rpi3-20230612 6.1.0-9-arm64 #1 SMP Debian 6.1.27-1 (2023-05-08) aarch64 GNU/Linux

root@rpi3-20230612:~# apt-get -V --no-install-recommends dist-upgrade
…
The following NEW packages will be installed:
   linux-image-6.1.0-13-arm64 (6.1.55-1)
The following packages will be upgraded:
   base-files (12.4 => 12.4+deb12u2)
…
   linux-image-arm64 (6.1.27-1 => 6.1.55-1)

After reboot:

root@rpi3-20230612:~# uname -a
Linux rpi3-20230612 6.1.0-13-arm64 #1 SMP Debian 6.1.55-1 (2023-09-29) aarch64 GNU/Linux

root@rpi3-20230612:~# apt-cache policy linux-image-6.1.0-13-arm64
linux-image-6.1.0-13-arm64:
  Installed: 6.1.55-1
  Candidate: 6.1.55-1
  Version table:
 *** 6.1.55-1 500
        500 http://deb.debian.org/debian bookworm/main arm64 Packages
        100 /var/lib/dpkg/status

Firmware packages:

root@rpi3-20230612:~# dpkg -l|grep -i firmware
ii  bluez-firmware               1.2-9                  all          Firmware for Bluetooth devices
ii  firmware-brcm80211           20230210-5             all          Binary firmware for Broadcom/Cypress 802.11 wireless cards
ii  firmware-linux-free          20200122-1             all          Binary firmware for various drivers in the Linux kernel
ii  raspi-firmware               1.20220830+ds-1        all          Raspberry Pi family GPU firmware and bootloaders

Their /etc/apt/sources.list is

deb http://deb.debian.org/debian bookworm main non-free-firmware non-free
deb http://deb.debian.org/debian bookworm-updates main non-free-firmware non-free
deb http://security.debian.org/debian-security bookworm-security main non-free-firmware non-free
# Backports are _not_ enabled by default.
# Enable them by uncommenting the following line:
# deb http://deb.debian.org/debian bookworm-backports main non-free-firmware

vazhnov · ARM Builds

c0rnelius c0rnelius, thank you for links!

So, these Raspberry PI builds doesn't have possibility to update these custom-made packages automatically (as other packages, with apt). Sad. I think this should be described somewhere in chapter "Known issues".

vazhnov · ARM Builds

Hello!

I've downloaded an image https://arm-files.devuan.org/RaspberryP … 2-0243.zip and installed it. It works fine, but I see 3 obsolete packages:

root@devuanpi:~# apt list '?obsolete'
Listing... Done
linux-headers-bcm2710-rpi-3/now 6.1.54-1 arm64 [installed,local]
linux-image-bcm2710-rpi-3/now 6.1.54-1 arm64 [installed,local]
raspberrypi-sys-mods/now 20220224 arm64 [installed,local]

root@devuanpi:~# apt-cache policy linux-image-bcm2710-rpi-3
linux-image-bcm2710-rpi-3:
  Installed: 6.1.54-1
  Candidate: 6.1.54-1
  Version table:
 *** 6.1.54-1 100
        100 /var/lib/dpkg/status
…

The sources file /etc/apt/sources.list was:

deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmware

I replaced it with

deb http://pl.deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
deb http://pl.deb.devuan.org/merged daedalus-updates main contrib non-free non-free-firmware
deb http://pl.deb.devuan.org/merged daedalus-security main contrib non-free non-free-firmware
deb http://pl.deb.devuan.org/merged daedalus-backports main contrib non-free non-free-firmware

but still the same — 3 obsolete packages.

I'm afraid they will never be updated.

Is there any way to add an official repository for them?

Also, where can I found script/pipeline which creates these images? could you please add this information into https://arm-files.devuan.org/README.txt?

vazhnov · Packaging for Devuan

Here is an original init script /etc/init.d/avahi-daemon from avahi-daemon version 0.8-7:

#!/bin/sh
### BEGIN INIT INFO
# Provides:          avahi avahi-daemon
# Required-Start:    $remote_fs dbus
# Required-Stop:     $remote_fs dbus
# Should-Start:	     $syslog
# Should-Stop:       $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Avahi mDNS/DNS-SD Daemon
# Description:       Zeroconf daemon for configuring your network 
#                    automatically
### END INIT INFO

PATH=/sbin:/bin:/usr/sbin:/usr/bin
DESC="Avahi mDNS/DNS-SD Daemon"
NAME="avahi-daemon"
DAEMON="/usr/sbin/$NAME"
SCRIPTNAME=/etc/init.d/$NAME

# Gracefully exit if the package has been removed.
test -x $DAEMON || exit 0

. /lib/lsb/init-functions

# Include avahi-daemon defaults if available.
test -f /etc/default/avahi-daemon && . /etc/default/avahi-daemon

DISABLE_TAG="/var/run/avahi-daemon/disabled-for-unicast-local"

#
#       Function that starts the daemon/service.
#
d_start() {
    $DAEMON -c && return 0

    if [ -e $DISABLE_TAG -a "$AVAHI_DAEMON_DETECT_LOCAL" != "0" ]; then
        # Disabled because of the existance of an unicast .local domain
        log_warning_msg "avahi-daemon disabled because there is a unicast .local domain"
        exit 0;
    fi;

    $DAEMON -D
}

#
#       Function that stops the daemon/service.
#
d_stop() {
    if $DAEMON -c ; then
       $DAEMON -k
    fi
}

#
#       Function that reload the config file for the daemon/service.
#
d_reload() {
    $DAEMON -c && $DAEMON -r
}

#
#       Function that check the status of the daemon/service.
#
d_status() {
    $DAEMON -c && { echo "$DESC is running"; exit 0; } || { echo "$DESC is not running"; exit 3; }
}

case "$1" in
    start)
        log_daemon_msg "Starting $DESC" "$NAME"
        d_start
        log_end_msg $?
        ;;
    stop)
        log_daemon_msg "Stopping $DESC" "$NAME"
        d_stop
        log_end_msg $?
        ;;
    reload|force-reload)
        log_daemon_msg "Reloading services for $DESC" "$NAME"
        d_reload
        log_end_msg $?
        ;;
    restart)
        log_daemon_msg "Restarting $DESC" "$NAME"
        d_stop
        if [ "$?" -eq 0 ]; then
                d_start
                log_end_msg $?
        else
                log_end_msg 1
        fi
        ;;
    status)
        d_status
        ;;
    *)
        echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload|reload|status}" >&2
        exit 3
        ;;
esac

exit 0

vazhnov · Packaging for Devuan

I use Devuan 5 daedalus/ceres with repository:

deb http://deb.devuan.org/merged daedalus main non-free contrib

Today I've got update:

The following packages will be upgraded:
   avahi-autoipd (0.8-7 => 0.8-8)
   avahi-daemon (0.8-7 => 0.8-8)
   avahi-utils (0.8-7 => 0.8-8)

and I saw

Removing obsolete conffile /etc/init.d/avahi-daemon ...

Here is that I found: https://tracker.debian.org/news/1417862 … -unstable/.

Probably it is time to do a Devuan fork of this package.

vazhnov · Devuan

Because there is no possibility to automate images creation in hub.docker.com with free account, I decided to learn GitLab pipelines and created this: https://gitlab.com/vazhnov/devuan-docker-images.

Images to be created automatically: Devuan 4 Chimaera — every month, Devuan 5 Daedalus — every week. The schedule is here: https://gitlab.com/vazhnov/devuan-docke … _schedules.

Container images registry: https://gitlab.com/vazhnov/devuan-docke … r_registry.

The code is still not perfect, I'm working on it.
It would be great to have an access to another GitLab instance without strict limits.

vazhnov · Installation

I think the root cause is that the key BB23C00C61FC752C expired:

 $ gpg --list-keys BB23C00C61FC752C
pub   rsa4096 2017-09-04 [SC] [expired: 2022-09-03]
      E032601B7CA10BC3EA53FA81BB23C00C61FC752C
uid           [ expired] Devuan Repository (Amprolla3 on Nemesis) <repository@devuan.org>

The same key described on the page https://www.devuan.org/os/keyring , fingerprint is E032 601B 7CA1 0BC3 EA53 FA81 BB23 C00C 61FC 752C.

 $ apt-key list
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
/etc/apt/trusted.gpg.d/debian-archive-bullseye-automatic.gpg
------------------------------------------------------------
pub   rsa4096 2021-01-17 [SC] [expires: 2029-01-15]
      1F89 983E 0081 FDE0 18F3  CC96 73A4 F27B 8DD4 7936
uid           [ unknown] Debian Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>
sub   rsa4096 2021-01-17 [S] [expires: 2029-01-15]

/etc/apt/trusted.gpg.d/debian-archive-bullseye-security-automatic.gpg
---------------------------------------------------------------------
pub   rsa4096 2021-01-17 [SC] [expires: 2029-01-15]
      AC53 0D52 0F2F 3269 F5E9  8313 A484 4904 4AAD 5C5D
uid           [ unknown] Debian Security Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>
sub   rsa4096 2021-01-17 [S] [expires: 2029-01-15]

/etc/apt/trusted.gpg.d/debian-archive-bullseye-stable.gpg
---------------------------------------------------------
pub   rsa4096 2021-02-13 [SC] [expires: 2029-02-11]
      A428 5295 FC7B 1A81 6000  62A9 605C 66F0 0D6C 9793
uid           [ unknown] Debian Stable Release Key (11/bullseye) <debian-release@lists.debian.org>

/etc/apt/trusted.gpg.d/debian-archive-buster-automatic.gpg
----------------------------------------------------------
pub   rsa4096 2019-04-14 [SC] [expires: 2027-04-12]
      80D1 5823 B7FD 1561 F9F7  BCDD DC30 D7C2 3CBB ABEE
uid           [ unknown] Debian Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>
sub   rsa4096 2019-04-14 [S] [expires: 2027-04-12]

/etc/apt/trusted.gpg.d/debian-archive-buster-security-automatic.gpg
-------------------------------------------------------------------
pub   rsa4096 2019-04-14 [SC] [expires: 2027-04-12]
      5E61 B217 265D A980 7A23  C5FF 4DFA B270 CAA9 6DFA
uid           [ unknown] Debian Security Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>
sub   rsa4096 2019-04-14 [S] [expires: 2027-04-12]

/etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg
-------------------------------------------------------
pub   rsa4096 2019-02-05 [SC] [expires: 2027-02-03]
      6D33 866E DD8F FA41 C014  3AED DCC9 EFBF 77E1 1517
uid           [ unknown] Debian Stable Release Key (10/buster) <debian-release@lists.debian.org>

/etc/apt/trusted.gpg.d/debian-archive-stretch-automatic.gpg
-----------------------------------------------------------
pub   rsa4096 2017-05-22 [SC] [expires: 2025-05-20]
      E1CF 20DD FFE4 B89E 8026  58F1 E0B1 1894 F66A EC98
uid           [ unknown] Debian Archive Automatic Signing Key (9/stretch) <ftpmaster@debian.org>
sub   rsa4096 2017-05-22 [S] [expires: 2025-05-20]

/etc/apt/trusted.gpg.d/debian-archive-stretch-security-automatic.gpg
--------------------------------------------------------------------
pub   rsa4096 2017-05-22 [SC] [expires: 2025-05-20]
      6ED6 F5CB 5FA6 FB2F 460A  E88E EDA0 D238 8AE2 2BA9
uid           [ unknown] Debian Security Archive Automatic Signing Key (9/stretch) <ftpmaster@debian.org>
sub   rsa4096 2017-05-22 [S] [expires: 2025-05-20]

/etc/apt/trusted.gpg.d/debian-archive-stretch-stable.gpg
--------------------------------------------------------
pub   rsa4096 2017-05-20 [SC] [expires: 2025-05-18]
      067E 3C45 6BAE 240A CEE8  8F6F EF0F 382A 1A7B 6500
uid           [ unknown] Debian Stable Release Key (9/stretch) <debian-release@lists.debian.org>

/etc/apt/trusted.gpg.d/devuan-keyring-2016-archive.gpg
------------------------------------------------------
pub   rsa2048 2014-12-02 [SC]
      72E3 CB77 3315 DFA2 E464  743D 9453 2124 5419 22FB
uid           [ unknown] Devuan Repository (Primary Devuan signing key) <repository@devuan.org>
sub   rsa2048 2014-12-02 [E]
sub   rsa4096 2016-04-26 [S]

/etc/apt/trusted.gpg.d/devuan-keyring-2016-cdimage.gpg
------------------------------------------------------
pub   rsa4096 2016-10-06 [SC]
      CF19 21B2 D91C 6435 848E  8100 99C4 6A90 B1FB 3B59
uid           [ unknown] Devuan ISO Toaster (Devuan GNU+Linux) <onelove@devuan.org>
sub   rsa4096 2016-10-06 [E]

/etc/apt/trusted.gpg.d/devuan-keyring-2017-archive.gpg
------------------------------------------------------
pub   rsa4096 2017-09-04 [SC] [expired: 2022-09-03]
      E032 601B 7CA1 0BC3 EA53  FA81 BB23 C00C 61FC 752C
uid           [ expired] Devuan Repository (Amprolla3 on Nemesis) <repository@devuan.org>

and:

 $ ls -lAF /etc/apt/trusted.gpg.d
total 80
-rw-r--r-- 1 root root 8700 Feb 25  2021 debian-archive-bullseye-automatic.gpg
-rw-r--r-- 1 root root 8709 Feb 25  2021 debian-archive-bullseye-security-automatic.gpg
-rw-r--r-- 1 root root 2453 Feb 25  2021 debian-archive-bullseye-stable.gpg
-rw-r--r-- 1 root root 8132 Feb 25  2021 debian-archive-buster-automatic.gpg
-rw-r--r-- 1 root root 8141 Feb 25  2021 debian-archive-buster-security-automatic.gpg
-rw-r--r-- 1 root root 2332 Feb 25  2021 debian-archive-buster-stable.gpg
-rw-r--r-- 1 root root 7443 Feb 25  2021 debian-archive-stretch-automatic.gpg
-rw-r--r-- 1 root root 7452 Feb 25  2021 debian-archive-stretch-security-automatic.gpg
-rw-r--r-- 1 root root 2263 Feb 25  2021 debian-archive-stretch-stable.gpg
-rw-r--r-- 1 root root 3637 Oct  3  2017 devuan-keyring-2016-archive.gpg
-rw-r--r-- 1 root root 2233 Oct  3  2017 devuan-keyring-2016-cdimage.gpg
-rw-r--r-- 1 root root 3638 Oct  3  2017 devuan-keyring-2017-archive.gpg

 $ dpkg -S /etc/apt/trusted.gpg.d/devuan-keyring-2017-archive.gpg
devuan-keyring: /etc/apt/trusted.gpg.d/devuan-keyring-2017-archive.gpg

 $ apt-cache policy devuan-keyring 
devuan-keyring:
  Installed: 2017.10.03
  Candidate: 2017.10.03
  Version table:
 *** 2017.10.03 500
        500 http://pl.deb.devuan.org/merged daedalus/main amd64 Packages
        100 /var/lib/dpkg/status

vazhnov · Devuan

Works since yesterday:

 $ curl -6 -v http://pl.deb.devuan.org 
*   Trying 2001:41d0:8:732b::587:52b3:80...
* Connected to pl.deb.devuan.org (2001:41d0:8:732b::587:52b3) port 80 (#0)
> GET / HTTP/1.1
> Host: pl.deb.devuan.org
> User-Agent: curl/7.83.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Server: nginx/1.18.0
< Date: Sun, 15 May 2022 11:01:41 GMT
< Content-Type: text/html
< Content-Length: 169
< Connection: keep-alive
< Location: http://deb.devuan.org/
< 
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.18.0</center>
</body>
</html>
* Connection #0 to host pl.deb.devuan.org left intact

vazhnov · Devuan

This issue is not about country codes, but about http://pkgmaster.devuan.org connectivity.
But thank you for information!

vazhnov · Devuan

Hello!

I use IPv6-only Devuan workstation.

Today I see an error, when run apt update:

  Could not connect to pl.deb.devuan.org:80 (2001:41d0:a:511b::98e4:cc90). - connect (113: No route to host)

 $ host pl.deb.devuan.org
pl.deb.devuan.org is an alias for pl.deb.rr.devuan.org.
pl.deb.rr.devuan.org is an alias for pkgmaster.devuan.org.
pkgmaster.devuan.org has address 5.135.82.179
pkgmaster.devuan.org has IPv6 address 2001:41d0:a:511b::98e4:cc90

Also I've checked from another datacenter:

 $ curl -6 -v http://pl.deb.devuan.org
*   Trying 2001:41d0:a:511b::98e4:cc90:80...
* connect to 2001:41d0:a:511b::98e4:cc90 port 80 failed: Connection timed out
* Failed to connect to pl.deb.devuan.org port 80: Connection timed out
* Closing connection 0
curl: (28) Failed to connect to pl.deb.devuan.org port 80: Connection timed out

Could you please check your IPv6 connectivity?

vazhnov · Hardware & System Configuration

Intro

I've installed a fresh minimal OS from the image "devuan_daedalus_5.0.preview-20211122_amd64_server.iso" (from the mirror https://mirror.leaseweb.com/devuan/devu … aller-iso/). I chose OpenRC init system.

Host system: Proxmox (based on Debian 10 oldstable).
Virtualisation: QEMU/KVM.

Error

On first boot, I found an error:

ERROR: elogind needs service(s) dbus

Troubleshooting

As I found, there is no init-script in the package dbus 1.12.20-3+devuan2:

user@devuan5-01 ~ % dpkg -L dbus|sort|grep init
user@devuan5-01 ~ % apt-cache policy dbus
dbus:
  Installed: 1.12.20-3+devuan2
  Candidate: 1.12.20-3+devuan2
  Version table:
 *** 1.12.20-3+devuan2 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages
        100 /var/lib/dpkg/status

user@devuan5-01 ~ % dpkg -l|grep -i dbus
ii  at-spi2-core                        2.42.0-2                           amd64        Assistive Technology Service Provider Interface (dbus core)
ii  dbus                                1.12.20-3+devuan2                  amd64        simple interprocess messaging system (system message bus)
ii  dbus-bin                            1.12.20-3+devuan2                  amd64        simple interprocess messaging system (command line utilities)
ii  dbus-daemon                         1.12.20-3+devuan2                  amd64        simple interprocess messaging system (reference message bus)
ii  dbus-session-bus-common             1.12.20-3+devuan2                  all          simple interprocess messaging system (session bus configuration)
ii  dbus-system-bus-common              1.12.20-3+devuan2                  all          simple interprocess messaging system (system bus configuration)
ii  dbus-x11                            1.12.20-3+devuan2                  amd64        simple interprocess messaging system (X11 deps)
ii  libdbus-1-3:amd64                   1.12.20-3+devuan2                  amd64        simple interprocess messaging system (library)

But, in the same minimal system with Devuan 4 Chimaera:

user@devuan4-02 ~ % dpkg -L dbus|sort|grep init
/etc/init.d
/etc/init.d/dbus
user@devuan4-02 ~ % apt-cache policy dbus
dbus:
  Installed: 1.12.20-2+devuan2
  Candidate: 1.12.20-2+devuan2
  Version table:
 *** 1.12.20-2+devuan2 500
        500 http://deb.devuan.org/merged chimaera/main amd64 Packages
        100 /var/lib/dpkg/status

user@devuan4-02 ~ % dpkg -l|grep -i dbus
ii  at-spi2-core                        2.38.0-4                           amd64        Assistive Technology Service Provider Interface (dbus core)
ii  dbus                                1.12.20-2+devuan2                  amd64        simple interprocess messaging system (daemon and utilities)
ii  dbus-x11                            1.12.20-2+devuan2                  amd64        simple interprocess messaging system (X11 deps)
ii  libdbus-1-3:amd64                   1.12.20-2+devuan2                  amd64        simple interprocess messaging system (library)

Fix

So, I copied the init script /etc/init.d/dbus and ran:

sudo rc-update add dbus default

Now dbus starts:

user@devuan5-01 ~ % sudo service dbus status         
dbus is running.

user@devuan5-01 ~ % ls -lAF /var/run/dbus
total 4
-rw-r--r-- 1 root root 5 Nov 28 19:30 pid
srwxrwxrwx 1 root root 0 Nov 28 19:30 system_bus_socket=

vazhnov · Devuan

Hi all!

I created another one public repository with Devuan docker images and a small documentation: https://hub.docker.com/r/vazhnov/devuan
Images are tiny, about 30 MB compressed.

Also I see another unofficial Devuan images repositories: https://hub.docker.com/search?q=devuan&type=image

Any ideas how to create official one?

vazhnov · Hardware & System Configuration

I created unofficial one with a short documentation: https://hub.docker.com/r/vazhnov/devuan

vazhnov · Installation

Checked the same steps with Devuan 4 Chimaera and fresh content of "debian-cloud-images" repository — image created successfully:

 % ls -l /tmp/image*                 
-rw-r--r-- 1 root  root       37004 Nov  8 03:01 /tmp/image_buster_ec2_amd64.build-fai.json
-rw-r--r-- 1 lenin lenin      37806 Nov  8 03:02 /tmp/image_buster_ec2_amd64.build.json
-rw-r--r-- 1 root  root       15460 Nov  8 03:01 /tmp/image_buster_ec2_amd64.build.junit.xml
-rw-r--r-- 1 root  root       42430 Nov  8 03:01 /tmp/image_buster_ec2_amd64.info
-rw-r--r-- 1 root  root  8589934592 Nov  8 03:01 /tmp/image_buster_ec2_amd64.raw
-rw-r--r-- 1 lenin lenin  775700480 Nov  8 03:01 /tmp/image_buster_ec2_amd64.tar
 % file /tmp/image_buster_ec2_amd64.raw
/tmp/image_buster_ec2_amd64.raw: DOS/MBR boot sector, extended partition table (last)

vazhnov · Installation

Devuan 3:

root@devuan3-01:~# for i in proc sys dev;do findmnt /$i;done
TARGET SOURCE FSTYPE OPTIONS
/proc  proc   proc   rw,nosuid,nodev,noexec,relatime
TARGET SOURCE FSTYPE OPTIONS
/sys   sysfs  sysfs  rw,nosuid,nodev,noexec,relatime
TARGET SOURCE FSTYPE   OPTIONS
/dev   udev   devtmpfs rw,nosuid,relatime,size=1005164k,nr_inodes=251291,mode=755

Debian 10:

root@debian10-01:~# for i in proc sys dev;do findmnt /$i;done
TARGET SOURCE FSTYPE OPTIONS
/proc  proc   proc   rw,nosuid,nodev,noexec,relatime
TARGET SOURCE FSTYPE OPTIONS
/sys   sysfs  sysfs  rw,nosuid,nodev,noexec,relatime
TARGET SOURCE FSTYPE   OPTIONS
/dev   udev   devtmpfs rw,nosuid,relatime,size=1006728k,nr_inodes=251682,mode=755

No difference except size and nr_inodes.

vazhnov · Installation

I'm trying to create clean minimal Devuan image for AWS.

As I know, Debian uses Fully automatic installation (FAI) to create AWS AMIs: https://wiki.debian.org/Cloud/SystemsComparison, https://wiki.debian.org/Cloud/AmazonEC2Image.

So first I tried to repeat process of Debian image creation by FAI. Next step will be: change FAI configuration to build Devuan image.

System: I use KVM virtual machine (Proxmox 6/Debian 10 buster) with Devuan guest:

lenin@devuan3-01 ~ % cat /etc/os-release
PRETTY_NAME="Devuan GNU/Linux 3 (beowulf)"
NAME="Devuan GNU/Linux"
VERSION_ID="3"
VERSION="3 (beowulf)"
VERSION_CODENAME=beowulf
ID=debian
ID_LIKE=debian
HOME_URL="https://www.devuan.org/"
SUPPORT_URL="https://devuan.org/os/community"
BUG_REPORT_URL="https://bugs.devuan.org/"

Commands I used:

sudo apt-get -V install fai-server fai-setup-storage qemu-utils
sudo apt-get -V --no-install-recommends install ca-certificates debsums dosfstools fai-server fai-setup-storage make python3 python3-libcloud python3-marshmallow python3-pytest python3-yaml qemu-utils udev
git clone "git@salsa.debian.org:cloud-team/debian-cloud-images.git"
cd debian-cloud-images
make DESTDIR=/tmp/ image_buster_ec2_amd64

(also I changed apt_cdn=http://192.168.1.1:3142/deb.debian.org and security_cdn=http://192.168.1.1:3142/security.debian.org URLs to use apt-cacher-ng).

Result:

…
Setting up grub-cloud-amd64 (0.0.4) ...
grub-probe: error: failed to get canonical path of `/dev/loop0p1'.
Installing for i386-pc platform.
grub-install: error: failed to get canonical path of `/dev/loop0p1'.
dpkg: error processing package grub-cloud-amd64 (--configure):
 installed grub-cloud-amd64 package post-installation script subprocess returned error exit status 1
…

Errors were encountered while processing:
 grub-cloud-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
ERROR: 25600 25600
ERROR: chroot /tmp/fai-diskimage.M61Y2t apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confnew --fix-missing install --no-install-recommends openssh-server cloud-initramfs-growroot sudo libpam-systemd unattended-upgrades chrony apt-utils ifupdown init iptables iputils-ping isc-dhcp-client less logrotate nano netbase rsyslog vim-tiny whiptail python-boto bsdmainutils awscli python3-boto cloud-init cloud-guest-utils linux-image-cloud-amd64 apparmor grub-cloud-amd64 return code 100
install_packages: executing chroot /tmp/fai-diskimage.M61Y2t apt-get clean
install_packages: executing chroot /tmp/fai-diskimage.M61Y2t dpkg --configure --pending
Setting up grub-cloud-amd64 (0.0.4) ...
grub-probe: error: failed to get canonical path of `/dev/loop0p1'.
Installing for i386-pc platform.
grub-install: error: failed to get canonical path of `/dev/loop0p1'.
dpkg: error processing package grub-cloud-amd64 (--configure):
 installed grub-cloud-amd64 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 grub-cloud-amd64
ERROR: 256 256
ERROR: chroot /tmp/fai-diskimage.M61Y2t dpkg --configure --pending return code 1
install_packages: executing chroot /tmp/fai-diskimage.M61Y2t dpkg -C
The following packages are only half configured, probably due to problems
configuring them the first time.  The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
 grub-cloud-amd64     GRand Unified Bootloader (cloud setup)

install_packages: executing chroot /tmp/fai-diskimage.M61Y2t apt-get clean
2 errors during executing of install_packages
Error in task instsoft. Code: 471
Traceback: task_error task_instsoft task task_install task task_action task main
FATAL ERROR. Installation stopped.
Size of disk image and filename: 800M	/tmp/image_buster_ec2_amd64.raw
Image created by: /usr/sbin/fai-diskimage --verbose --hostname debian --class DEBIAN,CLOUD,TYPE_DEV,BUSTER,EXTRAS,EC2,IPV6_DHCP,AMD64,GRUB_CLOUD_AMD64,LOCALDEBS,LINUX_IMAGE_CLOUD,LAST --size 8G --cspace /home/lenin/debian-cloud-images/src/debian_cloud_images/build/fai_config /tmp/image_buster_ec2_amd64.raw
Traceback (most recent call last):
  File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/lenin/debian-cloud-images/src/debian_cloud_images/cli/__main__.py", line 38, in <module>
    main()
  File "/home/lenin/debian-cloud-images/src/debian_cloud_images/cli/__main__.py", line 34, in main
    args.cls(argparser=parser, **vars(args))()
  File "/home/lenin/debian-cloud-images/src/debian_cloud_images/cli/build.py", line 417, in __call__
    self.fai(not self.noop)
  File "/home/lenin/debian-cloud-images/src/debian_cloud_images/build/fai.py", line 47, in __call__
    raise subprocess.CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '('sudo', 'env', 'PYTHONPATH=/home/lenin/debian-cloud-images/src/debian_cloud_images/build/../..', 'CLOUD_BUILD_DATA=/home/lenin/debian-cloud-images/src/debian_cloud_images/data', 'CLOUD_BUILD_INFO={"type": "dev", "release": "buster", "release_id": "10", "release_baseid": "10", "vendor": "ec2", "arch": "amd64", "build_id": "manual", "version": "202007051951"}', 'CLOUD_BUILD_NAME=image_buster_ec2_amd64', 'CLOUD_BUILD_OUTPUT_DIR=/tmp', 'CLOUD_RELEASE_ID=ec2', 'CLOUD_RELEASE_VERSION=202007051951', 'fai-diskimage', '--verbose', '--hostname', 'debian', '--class', 'DEBIAN,CLOUD,TYPE_DEV,BUSTER,EXTRAS,EC2,IPV6_DHCP,AMD64,GRUB_CLOUD_AMD64,LOCALDEBS,LINUX_IMAGE_CLOUD,LAST', '--size', '8G', '--cspace', '/home/lenin/debian-cloud-images/src/debian_cloud_images/build/fai_config', '/tmp/image_buster_ec2_amd64.raw')' returned non-zero exit status 1.
make: *** [Makefile:14: image_buster_ec2_amd64] Error 1

Before the error, disks are:

lenin@devuan3-01 ~ % sudo lsblk
NAME       MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0        7:0    0    8G  0 loop 
├─loop0p1  259:0    0  7.9G  0 part /tmp/fai-diskimage.M61Y2t
├─loop0p14 259:1    0    3M  0 part 
└─loop0p15 259:2    0  124M  0 part /tmp/fai-diskimage.M61Y2t/boot/efi
sr0         11:0    1  620M  0 rom  
vda        254:0    0   32G  0 disk 
├─vda1     254:1    0   30G  0 part /
├─vda2     254:2    0    1K  0 part 
└─vda5     254:5    0    2G  0 part [SWAP]
lenin@devuan3-01 ~ % sudo blkid|grep loop| sort
/dev/loop0p14: PARTUUID="f298765a-20f9-2543-8fe7-2749d86cdd61"
/dev/loop0p15: SEC_TYPE="msdos" UUID="4FCA-6200" TYPE="vfat" PARTUUID="5afa65b1-da1b-3648-b04c-c16bc2da197e"
/dev/loop0p1: UUID="f69236e0-7497-40a3-9e78-79d095a33e20" TYPE="ext4" PARTUUID="87e7358e-67ec-ba46-8dc5-91ecdd661c0e"
/dev/loop0: PTUUID="7553b010-f107-3449-9c99-5db320211b37" PTTYPE="gpt"

lenin@devuan3-01 ~ % ls -lAF /tmp/fai-diskimage.M61Y2t
total 88
drwxr-xr-x   2 root  root   4096 Jul  5 19:54 bin/
drwxr-xr-x   3 root  root   4096 Jul  5 19:54 boot/
drwxr-xr-x   4 root  root   4096 Jul  5 19:52 dev/
drwxr-xr-x  71 root  root   4096 Jul  5 19:55 etc/
drwxr-xr-x   2 root  root   4096 May  2 19:39 home/
drwxr-xr-x  12 root  root   4096 Jul  5 19:54 lib/
drwxr-xr-x   2 root  root   4096 Jul  5 19:52 lib64/
drwxr-xr-x   2 lenin lenin  4096 Jun 20 15:40 localdebs/
drwx------   2 root  root  16384 Jul  5 19:51 lost+found/
drwxr-xr-x   2 root  root   4096 Jul  5 19:52 media/
drwxr-xr-x   2 root  root   4096 Jul  5 19:52 mnt/
drwxr-xr-x   2 root  root   4096 Jul  5 19:52 opt/
dr-xr-xr-x 106 root  root      0 Jul  1 00:29 proc/
drwx------   2 root  root   4096 Jul  5 19:52 root/
drwxr-xr-x   5 root  root   4096 Jul  5 19:53 run/
drwxr-xr-x   2 root  root   4096 Jul  5 19:54 sbin/
drwxr-xr-x   2 root  root   4096 Jul  5 19:52 srv/
dr-xr-xr-x  13 root  root      0 Jul  1 00:29 sys/
drwxrwxrwt   2 root  root   4096 Jul  5 19:54 tmp/
drwxr-xr-x  10 root  root   4096 Jul  5 19:52 usr/
drwxr-xr-x  11 root  root   4096 Jul  5 19:52 var/

I tried to repeat the same steps on the same Debian KVM virtual machine, it finished without error.

Any idea how to prevent this error, "grub-probe: error: failed to get canonical path of `/dev/loop0p1'"?

vazhnov · ARM Builds

fsmithred wrote:

We built beowulf installer images for armel, armhf and ppc64el. If you have appropriate hardware, please test and report.

My try with Devuan installer for armhf described here: https://dev1galaxy.org/viewtopic.php?id=3551

vazhnov · ARM Builds

Problem 2: ISO image

What have I do here?

[            (1*installer)  2 shell  3 shell  4- log           ][ Jan 01  0:02 ]

   ┌─────────┤ [!!] Scan hard drives for an installer ISO image ├──────────┐    
   │                                                                       │    
   │                 Failed to find an installer ISO image                 │    
   │ No installer ISO images were found. If you downloaded the ISO image,  │    
   │ it may have a bad filename (not ending in ".iso"), or it may be on a  │    
   │ file system that could not be mounted.                                │    
   │                                                                       │    
   │ You'll have to use an alternative installation method, select another │    
   │ device to look for ISO image, or try again after you've fixed it.     │    
   │                                                                       │    
   │     <Go Back>                                          <Continue>     │    
   │                                                                       │    
   └───────────────────────────────────────────────────────────────────────┘

<Tab> moves; <Space> selects; <Enter> activates buttons

Which ISO image to use? I tried https://pkgmaster.devuan.org/devuan/dis … t/mini.iso — it is too small, only 33MB, and error is the same.

vazhnov · ARM Builds

Installer started after some manipulations (I'm not sure about addresses, especially kernel_addr_r=0x70008000):

=> setenv distro_bootpart ${mmcpart}
=> printenv distro_bootpart         
distro_bootpart=1
=> setenv boot_targets mmc
=> printenv boot_targets
boot_targets=mmc
=> setenv fdtfile ${fdt_file}
=> printenv fdtfile
fdtfile=imx53-qsrb.dtb
=> setenv bootpart ${mmcpart}
=> printenv bootpart
bootpart=1
=> setenv devnum ${mmcdev}
=> printenv devnum
devnum=0
=> setenv console ttymxc0
=> printenv console
=> setenv devtype mmc
=> printenv devtype  
devtype=mmc
=> setenv fdt_addr_r ${fdt_addr}
=> printenv fdt_addr_r                                    
fdt_addr_r=0x71000000
=> setenv ramdisk_addr_r ${loadaddr}
=> printenv ramdisk_addr_r          
ramdisk_addr_r=0x72000000
=> setenv kernel_addr_r 0x70008000
=> printenv kernel_addr_r
kernel_addr_r=0x70008000
=> boot

The officially official Devuan Forum!

#1 Re: Other Issues » OpenSSH fails to start with the latest update in Devuan 6 Excalibur » 2024-08-21 18:58:31

#2 Re: Other Issues » OpenSSH fails to start with the latest update in Devuan 6 Excalibur » 2024-07-21 22:51:57

#3 Re: Other Issues » OpenSSH fails to start with the latest update in Devuan 6 Excalibur » 2024-07-10 22:03:51

#4 Re: Other Issues » OpenSSH fails to start with the latest update in Devuan 6 Excalibur » 2024-07-08 22:34:16

#5 Re: Other Issues » OpenSSH fails to start with the latest update in Devuan 6 Excalibur » 2024-07-07 12:19:06

#6 Other Issues » OpenSSH fails to start with the latest update in Devuan 6 Excalibur » 2024-07-07 12:02:22

#7 Re: ARM Builds » Obsolete packages in Raspberry Pi image » 2023-10-14 10:18:36

#8 Re: ARM Builds » Obsolete packages in Raspberry Pi image » 2023-10-11 19:51:42

#9 ARM Builds » Obsolete packages in Raspberry Pi image » 2023-10-10 18:54:10

#10 Re: Packaging for Devuan » avahi-daemon doesn't have init script since v0.8-8 » 2023-02-11 12:33:59

#11 Packaging for Devuan » avahi-daemon doesn't have init script since v0.8-8 » 2023-02-10 21:49:28

#12 Re: Devuan » [SOLVED] Docker images » 2022-12-25 23:59:39

#13 Re: Installation » [SOLVED] apt-get update: gpg error (expired key) » 2022-09-03 12:10:04

#14 Re: Devuan » [SOLVED] pkgmaster.devuan.org unaccessible through IPv6 » 2022-05-15 11:02:20

#15 Re: Devuan » [SOLVED] pkgmaster.devuan.org unaccessible through IPv6 » 2022-05-13 20:47:40

#16 Devuan » [SOLVED] pkgmaster.devuan.org unaccessible through IPv6 » 2022-05-13 18:04:54

#17 Hardware & System Configuration » [SOLVED] Devuan 5 Daedalus: dbus init script absent » 2021-11-28 18:36:54

Intro

Error

Troubleshooting

Fix

#18 Devuan » [SOLVED] Docker images » 2021-01-31 22:49:17

#19 Re: Hardware & System Configuration » devuan docker image? » 2021-01-31 22:30:12

#20 Re: Installation » AWS EC2 AMI by FAI: grub-probe: error: failed to get canonical path » 2020-11-08 00:09:55

#21 Re: Installation » AWS EC2 AMI by FAI: grub-probe: error: failed to get canonical path » 2020-07-05 18:23:55

#22 Installation » AWS EC2 AMI by FAI: grub-probe: error: failed to get canonical path » 2020-07-05 17:21:35

#23 Re: ARM Builds » Installer images for armel, armhf and ppc64 need testing » 2020-05-31 13:12:32

#24 Re: ARM Builds » Devuan installer can't start on MX53 Loco (i.MX53 Quick Start board) » 2020-05-31 13:08:53

Problem 2: ISO image

#25 Re: ARM Builds » Devuan installer can't start on MX53 Loco (i.MX53 Quick Start board) » 2020-05-31 11:22:13

Board footer