Re: [DNG] Conversion from BullsEye to Devuan Fails
On Tue, 7 Dec 2021 08:05:35 -0600 Kent West via Dng wrote: > Hi! > > Following the instructions at > https://www.devuan.org/os/documentation/install-guides/chimaera/bullseye-to-chimaera > > I've tried it on two VirtualBox VMs (one two different Debian host boxes - > a Dell desktop and a Dell laptop). Both VMs were minimal Debian installs. > > I commented out all the lines in /etc/apt/sources.list and added the > following as the only lines in the file: > > deb http://deb.devuan.org/merged chimaera main deb > http://deb.devuan.org/merged chimaera-updates main deb > http://deb.devuan.org/merged chimaera-security main #deb > http://deb.devuan.org/merged chimaera-backports main > > Then I ran > > # apt-get update --allow-insecure-repositories > > which generated a dozen or so warnings/errors, which I assume is normal for > the process, so I ignored them. > > Then I ran > > # apt-get install devuan-keyring --allow-unauthenticated > > which generated a warning or two in the process. But the process appeared > to complete properly. > > Then I did > > # apt-get update > > which installed a few things, and appeared to complete properly. > > Then I did > > # apt-get upgrade > > which insisted I type in the phrase, "Yes, do as I say!". This generated > warnings/errors about too many errors processing systemd. > > The next step, > > # apt-get install eudev > > installed "openntpd" and then generated a warning that there is no init > system and policy-rc.d missing. > > The next step, the command to "reboot", resulted with "-bash: reboot: > command not found". Furthermore, the "shutdown" command can not be found. > The only way I could find to reboot was to do a VM reset. > > On reboot, there were messages about recovering the journal and clearing > orphaned inodes, then: > > run-init: can't execute '/sbin/init': No such file or directory > Target filesystem doesn't have requested /sbin/init. > run-init: can't execute (/sbin/init, /etc/init/, /bin/init): No such file > or directory > /bin/sh: 0: can't access tty; job control turned off > > The next step > > # apt-get dist-upgrade > > failed, partly because the file system is mounted read-only. Although I can > remount it as read-write, whatever is broken with the system is broken, and > the rest of these instructions aren't going to work. You just run into the > next problem (non-working network). This, too, can be fixed, but then you > run into another problem. Etc. > > > TL;DR - The conversion instructions don't work with Debian Bullseye 11.1, > at least not on minimal Debian VMs using VirtualBox on Debian, for me. > > I can just wipe these two VMs and start from scratch, no problem. But > thought whoever wrote that conversion page might need to know my experience. > > Hi, would you like to the test this conversion script at: https://git.devuan.org/farmatito/migration Hope it helps. Ciao, Tito ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Use fscrypt with pam authentication
Good day. I'm reposting this because I didn't register to the list the 1st time. First of all let me tell you that the dev1galaxy forum registration doesn't work (blank screen upon finishing registration). If someone here is engaged with it, pease have a look. Now, I just installed devuan on my laptop and wanted to protect my home folder using fscrypt and pam. I followed the instructions on the official github page. I installed both devuan packages, did 'sudo pam-auth-update'. I successfully encrypt my home folder and when I log in through the terminal, the home direcotry gets unlocked. Now to the problem. If I log in with 'slim' (the graphical interface), my screen hangs with dark blue background and nothing else. I thought that maybe somehow it doesn't unlock the folder and that is true - on fresh boot if I enter my login details, the the screen hangs and checking with the terminal (as root), the files aren't decrypted. I tried to manually unlock the folder and log in with slim with no success. Unfortunately I'm not aware how 'pam' works, nor I find any info in the logs (Xorg.log, slim.log, syslog). I was searching for the problem and found something that might be related, but out of my scope, so it may be helpful to you: https://github.com/systemd/systemd/commit/ab79099d1684457d040ee7c28b2012e8c1ea9a4f https://githubmemory.com/repo/google/fscrypt/issues/95 I added my /etc/pam.d/elogind-user the following line: session optional pam_keyinit.so force revoke with no luck. Thanks for your time, I'll be glad for any directions. Regards, Kul ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Use fscrypt with pam authentication
Good day. First of all let me tell you that the dev1galaxy forum registration doesn't work (http error 500 upon finishing registration). If someone here is engaged with it, pease have a look. Now, I just installed devuan on my laptop and wanted to protect my home folder using fscrypt and pam. I followed the instructions on the official github page. I installed both devuan packages, did 'sudo pam-auth-update'. I successfully encrypt my home folder and when I log in through the terminal, the home direcotry gets unlocked. Now to the problem. If I log in with 'slim' (the graphical interface), my screen hangs with dark blue background and nothing else. I thought that maybe somehow it doesn't unlock the folder and that is true - on fresh boot if I enter my login details, the the screen hangs and checking with the terminal (as root), the files aren't decrypted. I tried to manually unlock the folder and log in with slim with no success. Unfortunately I'm not aware how 'pam' works, nor I find any info in the logs (Xorg.log, slim.log, syslog). I was searching for the problem and found something that might be related, but out of my scope, so it may be helpful to you: https://github.com/systemd/systemd/commit/ab79099d1684457d040ee7c28b2012e8c1ea9a4f https://githubmemory.com/repo/google/fscrypt/issues/95 I added my /etc/pam.d/elogind-user the following line: session optional pam_keyinit.so force revoke with no luck. Thanks for your time, I'll be glad for any directions. Regards, Kul ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Conversion from BullsEye to Devuan Fails
Hi! Following the instructions at https://www.devuan.org/os/documentation/install-guides/chimaera/bullseye-to-chimaera I've tried it on two VirtualBox VMs (one two different Debian host boxes - a Dell desktop and a Dell laptop). Both VMs were minimal Debian installs. I commented out all the lines in /etc/apt/sources.list and added the following as the only lines in the file: deb http://deb.devuan.org/merged chimaera main deb http://deb.devuan.org/merged chimaera-updates main deb http://deb.devuan.org/merged chimaera-security main #deb http://deb.devuan.org/merged chimaera-backports main Then I ran # apt-get update --allow-insecure-repositories which generated a dozen or so warnings/errors, which I assume is normal for the process, so I ignored them. Then I ran # apt-get install devuan-keyring --allow-unauthenticated which generated a warning or two in the process. But the process appeared to complete properly. Then I did # apt-get update which installed a few things, and appeared to complete properly. Then I did # apt-get upgrade which insisted I type in the phrase, "Yes, do as I say!". This generated warnings/errors about too many errors processing systemd. The next step, # apt-get install eudev installed "openntpd" and then generated a warning that there is no init system and policy-rc.d missing. The next step, the command to "reboot", resulted with "-bash: reboot: command not found". Furthermore, the "shutdown" command can not be found. The only way I could find to reboot was to do a VM reset. On reboot, there were messages about recovering the journal and clearing orphaned inodes, then: run-init: can't execute '/sbin/init': No such file or directory Target filesystem doesn't have requested /sbin/init. run-init: can't execute (/sbin/init, /etc/init/, /bin/init): No such file or directory /bin/sh: 0: can't access tty; job control turned off The next step # apt-get dist-upgrade failed, partly because the file system is mounted read-only. Although I can remount it as read-write, whatever is broken with the system is broken, and the rest of these instructions aren't going to work. You just run into the next problem (non-working network). This, too, can be fixed, but then you run into another problem. Etc. TL;DR - The conversion instructions don't work with Debian Bullseye 11.1, at least not on minimal Debian VMs using VirtualBox on Debian, for me. I can just wipe these two VMs and start from scratch, no problem. But thought whoever wrote that conversion page might need to know my experience. -- Kent West<")))>< Westing Peacefully - http://kentwest.blogspot.com ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Avoid "unlock your keyring" prompt without desktop environment
Le 10/12/2021 à 16:20, Haines Brown a écrit : > I do not run any DE. On a new installation of skypeforlinux it priodically > asks me to unlock my keyring. I do not use a keyring. For me it id it already for some years already. I think it just wants to force the key wallet. I just refuse. On the last release I even experienced crashes. Poor quality. -- Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Avoid "unlock your keyring" prompt without desktop environment
I do not run any DE. On a new installation of skypeforlinux it priodically asks me to unlock my keyring. I do not use a keyring. A standard approach is to disable keyring prompts from seahorse. I do not have seahorse installed. I also do not have debian-keyring installed I do not have a /etc.pamd.gdem file I do not have a /etc/pamd./sddm file But strangely I do have a ~.local/share/keyrings/default file that simply has the line: default_keyring. How do I keep skypeforlinux from asking for keyring pw? -- Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Trouble verifying installation download.
Well, downloaded the wrong iso didn't I? I've got the right one and all seems fine now. The iso mentioned in my last post may still have a small problem though. Sorry for the noise. ~/Downloads/Devuan $ sha256 -C isoSHA256SUMS devuan_chimaera_4.0.0_amd64_netinstall.iso (SHA256) devuan_chimaera_4.0.0_amd64_netinstall.iso: OK ~/Downloads/Devuan $ gpg --verify isoSHA256SUMS isoSHA256SUMS isoSHA256SUMS.asc gpg --verify isoSHA256SUMS.asc gpg: assuming signed data in 'isoSHA256SUMS' gpg: Signature made Thu Oct 14 14:01:09 2021 BST gpg:using RSA key E93D7167A4F5FA9E9FED497770285BA5CF280BA4 gpg: Good signature from "Ralph Ronnquist (rrq) " [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E93D 7167 A4F5 FA9E 9FED 4977 7028 5BA5 CF28 0BA4 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Trouble verifying installation download.
Hi I decided to do an ascii re-install of Devuan Chimera and was not able to verify the download completely. The shasum was good but the verification failed due to an expired key. This is a log of my terminal activity after downloading the iso and keys files through firefox: ~/Downloads/Devuan $ sha256 -C SHASUMS.txt devuan_chimaera_4.0.0_amd64_minimal-live.iso (SHA256) devuan_chimaera_4.0.0_amd64_minimal-live.iso: OK ~/Downloads/Devuan $ gpg --import devuan-devs.gpg gpg: key 27B9FAA4EBAA93A1: 3 signatures not checked due to missing keys gpg: key 27B9FAA4EBAA93A1: public key "Daniel Reurich (Centurion_Dan) " imported gpg: key D95DDF2BF71AAAEB: 2 signatures not checked due to missing keys gpg: key D95DDF2BF71AAAEB: public key "fsmithred (aka fsr) " imported gpg: key 73B35DA54ACB7D10: 15 signatures not checked due to missing keys gpg: key 73B35DA54ACB7D10: public key "Denis Roio (Jaromil) " imported gpg: key 5F20B3AE0B5F062F: 17 signatures not checked due to missing keys gpg: key 5F20B3AE0B5F062F: public key "Vincenzo (KatolaZ) Nicosia " imported gpg: key DFEDF580D6132D50: 29 signatures not checked due to missing keys gpg: key DFEDF580D6132D50: public key "Franco Lanza (nextime) " imported gpg: key B876CB44FA1B0274: public key "parazyd " imported gpg: key A73823D3094C5620: 1 signature not checked due to a missing key gpg: key A73823D3094C5620: public key "fsmithred (aka fsr) " imported gpg: key 70285BA5CF280BA4: public key "Ralph Ronnquist (rrq) " imported gpg: Total number processed: 8 gpg: imported: 8 gpg: marginals needed: 3 completes needed: 1 trust model: pgp gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u ~/Downloads/Devuan $ gpg --verify SHASUMS.txt.asc gpg: assuming signed data in 'SHASUMS.txt' gpg: Signature made Fri Oct 15 01:26:06 2021 BST gpg:using RSA key 67F5013216271E85C251E480A73823D3094C5620 gpg: Good signature from "fsmithred (aka fsr) " [expired] gpg: Note: This key has expired! Primary key fingerprint: 67F5 0132 1627 1E85 C251 E480 A738 23D3 094C 5620 Many Thanks PS this was done on an OpenBSD system so the sha256 command is a little different. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Migrating from Docker to Podman
> On 10 Dec 2021, at 19:01, wirelessd...@gmail.com wrote: > > > >>> On 10 Dec 2021, at 18:27, d...@d404.nl wrote: >>> >>> On 10-12-2021 02:57, wirelessduck--- via Dng wrote: >>> Has anyone noticed issues when trying to switch from Docker to Podman >>> in Devuan chimaera? >>> >>> I'm getting an error when trying to run the latest `hadolint` image in >>> Podman which doesn't occur under Docker. >>> >>> $ docker run -it docker.io/hadolint/hadolint:v2.8.0 hadolint >>> Please provide a Dockerfile >>> >>> $ podman run -it docker.io/hadolint/hadolint:v2.8.0 hadolint >>> hadolint: getXdgDirectory:getHomeDirectory:getUserEntryForID: does not >>> exist (No such file or directory) >>> >>> Does this happen for anyone else, or have I broken something? I just >>> uninstalled docker and ran `apt-get install podman >>> debian-podman-config-override` so I haven't touched any other >>> configuration settings yet. >>> >>> Podman does provide an upstream package repository >>> (https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/podman) >>> which I wanted to use to try the newer release version but >>> unfortunately their podman package has a dependency on >>> `dbus-user-session` making it unusable from Devuan. I'll try to spin >>> up a daedalus VM to test the newer version if the repositories for >>> that are ready to go. >>> >> If i remember correctly Podman coming from Redhat depends heavily on systemd >> which is of course not available in Devuan. But please let us know if you >> succeed to run it under Devuan. >> >> Grtz >> >> Nick > > The packages in the Debian archive do not have a systemd dependency, for both > bullseye/chimaera and also bookworm/daedalus and also sid/ceres too. > > I can run the hello-world image, and also the hadolint-debian and > hadolint-alpine images too without problem. So after more testing with Devuan testing and Debian testing it fails on both of those for the latest Podman version. If I test on Debian 11 with the upstream Kubic repository, then it is successful. This leads me to think there is possibly something missing from the Debian packaging for Podman. I will report on Debian BTS. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Migrating from Docker to Podman
> On 10 Dec 2021, at 18:27, d...@d404.nl wrote: > > On 10-12-2021 02:57, wirelessduck--- via Dng wrote: >> Has anyone noticed issues when trying to switch from Docker to Podman >> in Devuan chimaera? >> >> I'm getting an error when trying to run the latest `hadolint` image in >> Podman which doesn't occur under Docker. >> >> $ docker run -it docker.io/hadolint/hadolint:v2.8.0 hadolint >> Please provide a Dockerfile >> >> $ podman run -it docker.io/hadolint/hadolint:v2.8.0 hadolint >> hadolint: getXdgDirectory:getHomeDirectory:getUserEntryForID: does not >> exist (No such file or directory) >> >> Does this happen for anyone else, or have I broken something? I just >> uninstalled docker and ran `apt-get install podman >> debian-podman-config-override` so I haven't touched any other >> configuration settings yet. >> >> Podman does provide an upstream package repository >> (https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/podman) >> which I wanted to use to try the newer release version but >> unfortunately their podman package has a dependency on >> `dbus-user-session` making it unusable from Devuan. I'll try to spin >> up a daedalus VM to test the newer version if the repositories for >> that are ready to go. >> > If i remember correctly Podman coming from Redhat depends heavily on systemd > which is of course not available in Devuan. But please let us know if you > succeed to run it under Devuan. > > Grtz > > Nick The packages in the Debian archive do not have a systemd dependency, for both bullseye/chimaera and also bookworm/daedalus and also sid/ceres too. I can run the hello-world image, and also the hadolint-debian and hadolint-alpine images too without problem. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
