Dev1 Galaxy Forum / Migrating from Buster to Beowulf - feedback needed

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (little) — Fri, 08 Jan 2021 03:48:10 +0000

So I bashed through a number of commands. I installed sysvinit-core, yes. I ended up removing the kernel, and then reinstalling it. Quite a mess, but I was able to get it to complete the install. At one point, it reboot with no eth0 iface, so the emergency console was used, and then after installing eudev and rebooting, everything looked right. I'll try to update this post with some steps for future reference. It was not straightforward, but it was possible. I suspect because this was a VPS.

Maybe I would've had better luck if I followed the instructions in this thread I had followed before for the RPI. Anyways, alls well that ends well.

EDIT: full guide to get migration working here: http://dev1galaxy.org/viewtopic.php?pid=26751#p26751

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (Head_on_a_Stick) — Thu, 07 Jan 2021 21:46:41 +0000

Did you try installing sysvinit-core before attempting to install eudev?

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (little) — Thu, 07 Jan 2021 19:27:54 +0000

No dice. Reboot works, but apt-get dist-upgrade results in being prompted to remove the running kernel. I don't agree to that, and then it breaks down.

I'm afraid I need to find a different VPS vendor. One that supports custom ISOs. For what it's worth, I migrated an identical Jessie or Stretch (forget now) Debian to Devuan some years ago with this vendor. Back then, the only trick was adding /etc/inittab. Now with Buster it's resulting in below.

Removing linux-image-amd64 (4.19+105+deb10u8) ...
Removing linux-image-4.19.0-13-amd64 (4.19.160-2) ...
E: Aborting removal of the running kernel
dpkg: error processing package linux-image-4.19.0-13-amd64 (--remove):
 installed linux-image-4.19.0-13-amd64 package pre-removal script subprocess returned error exit status 1
Removing bluetooth (5.50-1.2~deb10u1) ...
Removing bluez (5.50-1.2~deb10u1) ...
dpkg: initramfs-tools-core: dependency problems, but removing anyway as you requested:
 initramfs-tools depends on initramfs-tools-core (= 0.133+deb10u1).

Removing initramfs-tools-core (0.133+deb10u1) ...
Removing udev (241-7~deb10u5) ...
dpkg: initramfs-tools: dependency problems, but removing anyway as you requested:
 linux-image-4.19.0-13-amd64 depends on initramfs-tools (>= 0.120+deb8u2) | linux-initramfs-tool; however:
  Package initramfs-tools is to be removed.

  Package linux-initramfs-tool is not installed.
  Package initramfs-tools which provides linux-initramfs-tool is to be removed.
 linux-image-4.19.0-13-amd64 depends on initramfs-tools (>= 0.120+deb8u2) | linux-initramfs-tool; however:
  Package initramfs-tools is to be removed.
  Package linux-initramfs-tool is not installed.
  Package initramfs-tools which provides linux-initramfs-tool is to be removed.

Removing initramfs-tools (0.133+deb10u1) ...
Errors were encountered while processing:
 linux-image-4.19.0-13-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@vps:/#

Then:

root@vps:~# apt-get install eudev
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 eudev : Depends: libeudev1 (= 3.2.7-6) but it is not going to be installed
         Breaks: systemd (> 220) but 241-7~deb10u5 is to be installed
 linux-image-4.19.0-13-amd64 : Depends: initramfs-tools (>= 0.120+deb8u2) but it is not going to be installed or
                                        linux-initramfs-tool
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
root@vps:~# apt-get purge systemd libnss-systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 dbus-user-session : Depends: systemd but it is not going to be installed
 libpam-systemd : Depends: systemd (= 241-7~deb10u5) but it is not going to be installed
 linux-image-4.19.0-13-amd64 : Depends: initramfs-tools (>= 0.120+deb8u2) but it is not going to be installed or
                                        linux-initramfs-tool
 systemd-sysv : PreDepends: systemd but it is not going to be installed
                Recommends: libnss-systemd but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
root@vps:~# apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... failed.
The following packages have unmet dependencies:
 linux-image-4.19.0-13-amd64 : Depends: initramfs-tools (>= 0.120+deb8u2) but it is not installed or
                                        linux-initramfs-tool
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
root@vps:~#

Finally, stuck in dependency hell.

root@vps:~# sudo apt-get install libeudev1
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libeudev1 : Conflicts: libudev1 (< 1:3.2.7-6)
 linux-image-4.19.0-13-amd64 : Depends: initramfs-tools (>= 0.120+deb8u2) but it is not going to be installed or
                                        linux-initramfs-tool
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
root@vps:~# sudo apt-get install initramfs-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 initramfs-tools : Depends: initramfs-tools-core (= 0.133+deb10u1) but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
root@vps:~# sudo apt-get install initramfs-tools initramfs-tools-core
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 initramfs-tools-core : Depends: udev
                        Recommends: pigz but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
root@vps:~#

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (the_edge123) — Thu, 07 Jan 2021 07:46:37 +0000

IIRC, you may reboot and continue the migration with:

apt-get dist-upgrade

--
Fabien

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (little) — Thu, 07 Jan 2021 02:15:28 +0000

Sorry, I wasn't clear. I did. See below:

root@vps:~# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  aspell-eu-es
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
root@vps:~#

Reboot I think would be unwise as it didn't install eudev. Trying to install eudev again results in the same error. The only hint is that it's holding packages, and also on a VPS (yet kvm).

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (nixer) — Wed, 06 Jan 2021 23:54:37 +0000

From the link you posted above:

Once this is done eudev needs to be installed. Note that if you’re using Gnome it will be removed by this command, but can be installed again after migration.
root@debian:~# apt-get install eudev
The last command is known to cause package breaks but we will fix this as part of the migration process.
root@debian:~# apt-get -f install

Did you run "apt -f install"? Or "apt-get -f install"?

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (little) — Wed, 06 Jan 2021 22:19:17 +0000

Having trouble with a Debian Buster VPS migrating to Beowulf. Dependency issues when trying to install eudev. See below. (some sections omitted for brevity). To be clear, I am following the docs from devuan.org (https://www.devuan.org/os/documentation/dev1fanboy/en/buster-to-beowulf ). Not the earlier instructions in this thread.

root@vps:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  aspell-eu-es
Use 'apt autoremove' to remove it.
The following packages have been kept back:
  libcolord2 libudev1 udev util-linux
The following packages will be upgraded:
  base-files bsdutils ca-certificates distro-info-data fdisk libblkid1 libfdisk1 libmount1 libpcsclite1 libprocps7 libsmartcols1 libuuid1
  mount procps python3-reportbug reportbug rsyslog sysvinit-utils task-amharic task-arabic task-asturian task-basque task-belarusian
  task-bengali task-bosnian task-brazilian-portuguese task-bulgarian task-catalan task-chinese-s task-chinese-t task-croatian
  task-cyrillic task-czech task-danish task-dutch task-english task-esperanto task-estonian task-finnish task-french task-galician
  task-german task-greek task-gujarati task-hebrew task-hindi task-hungarian task-icelandic task-irish task-italian task-japanese
  task-kazakh task-khmer task-korean task-kurdish task-laptop task-latvian task-lithuanian task-macedonian task-malayalam task-marathi
  task-northern-sami task-norwegian task-persian task-polish task-portuguese task-punjabi task-romanian task-russian task-serbian
  task-slovak task-slovenian task-spanish task-swedish task-tagalog task-tamil task-telugu task-thai task-turkish task-ukrainian
  task-welsh tasksel tasksel-data tzdata util-linux-locales uuid-runtime
86 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Need to get 4,510 kB of archives.
After this operation, 644 kB of additional disk space will be used.
Do you want to continue? [Y/n]

etting up task-khmer (3.54+devuan3) ...
Setting up task-gujarati (3.54+devuan3) ...
Setting up task-northern-sami (3.54+devuan3) ...
Setting up task-belarusian (3.54+devuan3) ...
Setting up task-english (3.54+devuan3) ...
Processing triggers for systemd (241-7~deb10u5) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for ca-certificates (20200601~deb10u1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.

root@vps:~# apt-get install eudev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dconf-gsettings-backend : Depends: dconf-service (>= 0.30.1-2) but it is not going to be installed
                           Depends: dconf-service (< 0.30.1-2.1~) but it is not going to be installed
 libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
root@vps:~#

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (pcalvert) — Sat, 23 May 2020 09:44:51 +0000

I migrated a new Debian Buster system to Beowulf, and things went well (for the most part). There is a problem, though. After the desktop appears, there is constant, non-stop disk activity. Running top shows a couple of CPU hogs:

udevd      20 to 30 % CPU
udisksd    14 to 20% CPU
udevd      1 to 2 % CPU

Based on a hunch, I uninstalled gvfs and the problem went away.

Phil

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (the_edge123) — Tue, 19 May 2020 07:17:21 +0000

The migration went well from https://beta.devuan.org/os/documentatio … to-beowulf.
--
Fabien

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (Andre4freedom) — Wed, 12 Feb 2020 12:25:28 +0000

Dear Admins, dear Members,
as requested, here my experience with Beowulf.
I always use the Cinnamon desktop and OpenRC. Starting with a fresh install of ASCII 2.1.
Of course, that installs NetworkManager, Lightdm and all, which I'm happy with.
I have Beowulf running on PCs, laptops and servers and couldn't be happier. Updates never broke my systems.

Here the steps I used to update from ASCII 2.1 to Beowulf:
1. Install Devuan Ascii (2.1)
(install all updates and upgrades: sudo apt update; sudo apt upgrade; reboot)

2. sudo vi /etc/pam.d/lightdm-greeter
--> ...
--> # Setup session
--> session required pam_unix.so
--> #session optional pam_systemd.so
--> session optional pam_elogind.so

3. sudo vi /etc/apt/sources.list
--> # comment the "deb cdrom:...= - line
--> # Replace every word ascii with the word beowulf

4. sudo apt udate
5. sudo apt upgrade
6. sudo apt dist-upgrade
7. sudo apt autoremove

8. reboot
9. vi sudo vi /etc/pulse/client.conf.d/00-disable-autospawn.conf
--> # On linux systems, disable autospawn by default
--> # If you are not using systemd, comment out this line
--> #autospawn=no

10. logout - login --> ok

The only wish I have is to get the cinnamon tool to install and configure languages. I'm quite happy with English, but some users prefer French or German when they log in.

A big thank to the Devuan Team - a real high-light in this increasingly "complex" world.

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (dgrif) — Wed, 12 Feb 2020 03:50:11 +0000

> Actually, if you check http://deb.devuan.org/merged/dists/, beowulf-security, beowulf-updates, beowulf-backports, and
> beowulf-proposed-updates all exist now.
>
>Michael

I will check the above repositories when I return home. I did the actual migration a couple of weeks before posting, and promptly went on an out-of-town trip after making the post. Overall I am pleased with the system and the fact that SysVinit is still viable. (I'm probably a "stick in the mud" type having been around Unix since before SysV was licensed commercially.)

Dan

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (mknoop) — Wed, 05 Feb 2020 07:03:58 +0000

Congratulations Dan,

It looks to me like you did a good job. I hope it all works for you. Just a note:

"Also the "beowulf-security" doesn't yet exist (because it's "testing"?) so I commented it out from sources.list. Once the keyring was installed, I removed the "[trusted=yes]" from sources.list."

Actually, if you check http://deb.devuan.org/merged/dists/, beowulf-security, beowulf-updates, beowulf-backports, and beowulf-proposed-updates all exist now.

Michael

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (dgrif) — Wed, 05 Feb 2020 03:17:43 +0000

Hello,

I am new to Devuan, but not to Debian (started pre-Sarge). I have been avoiding systemd through Debian Stretch, but I upgraded to Buster after the "systemd-shim" was removed. This caused LXDE to be removed because systemd was strictly prevented from being installed. The Devuan web page had instructions for migrating from Debian Stretch to ASCII. Since I was at Buster already I figured that migrating to Beowulf was appropriate even though there was no explicit recipe available.

I was successful at migrating from Debian Buster to Devuan Beowulf and then installed LXDE and everything is right with the world. Here is a synopsis of my process that I typed immediately after the task was completed.

Dan Griffin
---->
Migration to Devuan Beowulf (testing) from Debian Buster.

Buster system is bare-bones using SysVinit and wicd. Not much else because I did the Stretch to Buster upgrade after "systemd-shim" was removed from Debian.

The Devuan instructions start with Debian Jessie or Stretch to Devuan Ascii (stable) but I'm betting that I can do this trick. Please take a look at

https://devuan.org/os/documentation/dev … e-to-ascii

for the process that I am basing this migration upon. The early steps for removing systemd were not necessary since it was already gone.

First step, changing the sources.list file needs the entry
[trusted=yes] on the line

deb [trusted=yes] http://deb.devuan.org/merged buster main contrib non-free

because my Buster version of apt-get would not create the proper data base without it.

Then I could "apt-get install devuan-keyring" without errors.

Also the "beowulf-security" doesn't yet exist (because it's "testing"?) so I commented it out from sources.list. Once the keyring was installed, I removed the "[trusted=yes]" from sources.list.

Once the update is happy, then I did
apt-get upgrade
apt-get upgrade --with-new-pkgs
apt-get dist-upgrade

Now for the big test. Reboot the system!

Hooray, it does boot. And the X server comes up (/usr/lib/xorg/Xorg) along with lightdm. These two items were working before.

Now to install my choice, LXDE, which I couldn't do in Buster because of stupid dependencies that required all of systemd.

Trying first "apt-get install lxde-core" and it doesn't go because of dependencies not scheduled for installation. I tracked this down to "policykit-1". So I installed "policykit-1" and then "apt-get install lxde-core" worked without requiring any systemd stuff.

Now for another reboot to see what might be working.

Lo and behold a miracle. The LXDE desktop appears, complete with my appropriate icons on the desktop and behavior settings. Firefox works, Thunderbird works, LXTerminal works, and I have yet to find a command line program that doesn't work. But then I haven't tried everything.

Threw in an "update-initramfs" followed by "update-grub" for good measure. Probably not necessary, but shouldn't hurt.

So now I am going to move data and stuff from my old laptop with a broken hinge and very slow processor onto this system and let it sit on the desk in my basement.

Hopefully you will find my experience useful.

Dan

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (little) — Thu, 30 Jan 2020 06:48:40 +0000

I tested Nixer's instructions with Raspbian Buster on an RPI3 and had no issues today. Everything is working well.

I did notice that when /etc/network/interfaces was changed, the DHCP ip also changed. Quite minor.

There was an error with avahi-daemon. I'll copy it below:

//
? avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-01-30 04:58:10 GMT; 1h 17min ago
 Main PID: 312 (avahi-daemon)
   Status: "avahi-daemon 0.7 starting up."
    Tasks: 2 (limit: 1164)
   Memory: 1016.0K
   CGroup: /system.slice/avahi-daemon.service
           ??312 avahi-daemon: running [raspberrypi.local]
           ??342 avahi-daemon: chroot helper

Jan 30 04:58:15 raspberrypi avahi-daemon[312]: New relevant interface eth0.IPv4 for mDNS.
Jan 30 04:58:15 raspberrypi avahi-daemon[312]: Registering new address record for 192.168.1.240 on eth0.IPv4.
Jan 30 06:08:55 raspberrypi avahi-daemon[312]: Files changed, reloading.
Jan 30 06:08:55 raspberrypi avahi-daemon[312]: No service file found in /etc/avahi/services.
Jan 30 06:08:55 raspberrypi avahi-daemon[312]: Files changed, reloading.
Jan 30 06:08:55 raspberrypi avahi-daemon[312]: No service file found in /etc/avahi/services.
Jan 30 06:15:20 raspberrypi avahi-daemon[312]: Files changed, reloading.
Jan 30 06:15:20 raspberrypi avahi-daemon[312]: No service file found in /etc/avahi/services.
Jan 30 06:15:20 raspberrypi avahi-daemon[312]: Files changed, reloading.
Jan 30 06:15:20 raspberrypi avahi-daemon[312]: No service file found in /etc/avahi/services.
dpkg: error processing package avahi-daemon (--configure):
 installed avahi-daemon package post-installation script subprocess returned error exit status 1
Setting up tasksel (3.54+devuan3) ...
Setting up libdevmapper1.02.1:armhf (2:1.02.155-3) ...
Setting up libparted2:armhf (3.2-25) ...
Setting up tasksel-data (3.54+devuan3) ...
Setting up dmsetup (2:1.02.155-3) ...
update-initramfs: deferring update (trigger activated)
Setting up libcryptsetup12:armhf (2:2.1.0-5+deb10u2) ...
Setting up parted (3.2-25) ...
Setting up nfs-common (1:1.3.4-2.5) ...
nfs-utils.service is a disabled or a static unit not running, not starting it.
insserv: warning: current start runlevel(s) (empty) of script `nfs-common' overrides LSB defaults (S).
insserv: warning: current stop runlevel(s) (0 1 6 S) of script `nfs-common' overrides LSB defaults (0 1 6).
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
Processing triggers for systemd (241-7~deb10u2+rpi1) ...
Errors were encountered while processing:
 avahi-daemon
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@raspberrypi:/etc/apt#
//

This was after 1. devuan repos were added, and then 2. apt upgrade was run. I simply did an apt remove avahi-daemon, as I don't need it.
After that, there was no problem.

Re: Migrating from Buster to Beowulf - feedback needed

dummy@example.com (bimon) — Wed, 06 Nov 2019 04:31:45 +0000

For example a brave browser can run in a beowulf VM and still render its GUI on Ascii host by the following command:

ssh ice "brave-browser &";

Then you will have super stable ascii host with its Xorg server

and beowulf and ceres simultaneously running in different KVM vms for experiments with fresher GUI programs while they are still not released as stable.

Btw, this config has defended me from Ganstalkers' EMI and browser plugin attacks even on a slow HDD as ZFS vdev without any SSD caching:

https://archive.is/ggHIK

https://web.archive.org/web/20191106043 … ssues/9518

VM specific datasets are:

zfs set sync=disabled

for performance, having regular snapshots of course to rollback if a dataset gets any corruption due to unexpected reset, power loss, etc.

With a SSD it would work even faster which would be noticeable at least during computer power on when ZFS caches are cold yet, but after an hour of work HDDs become fast too after ZFS ARC gets already hot enough.

And a high IO attack from browser plugins becomes useless. Computer cannot be hung anymore by this method.