You are not logged in.
I've never tried to hibernate with a swapfile. There is a uswsusp module in the pm-utils package. I have no idea how you would use it. (dpkg-reconfigure uswsusp won't work)
$ apt-file find uswsusp
pm-utils: /usr/lib/pm-utils/module.d/uswsusp
One more time...
Newer chimaera live isos (4.0.2) are uploaded. I'm sure I tested the installer this time and it works.
(note: torrent and magent link haven't been updated yet at this time Sep 10, 16:36 UTC.)
The live installer would have made a swapfile in the root partition if you had not chosen to use the swap partition. So yes, it's possible to have a swapfile. To be sure, check to see if /swapfile already exists.
refractainstaller does the following, where bs=1024 and count=1048576:
dd if=/dev/zero of=/target/swapfile bs="$swapfile_blocksize" count="$swapfile_count" ; check_exit
mkswap /target/swapfile ; check_exit
chmod 600 /target/swapfile
The values for bs and count are in /etc/refractainstaller in case anyone wants to change the size of the swapfile. Currently it's set to 256mb. And then you have to edit the swap entry in /etc/fstab. Mine looks like this:
/swapfile none swap sw 0 0
refractainstaller base & gui 9.6.3 are built and will migrate down through the repos. I'll rebuild isos this weekend.
They're also here: https://sourceforge.net/projects/refracta/files/tools/
(for anyone who can't wait or those who are not using devuan)
Nah, don't mark it as solved yet. I screwed up again. The diversion of anacron gets removed in the live session AFTER the system gets copied to hard disk. It needs to happen in a chroot. The good news is that it'll do the right thing if you run the installer twice without rebooting the iso.
If someone wants to change it in place, go to line 2043 in /usr/bin/refractainstaller-yad or line 1893 in /usr/bin/refractainstaller and change this
# Remove diversion of anacron
if [ -e /usr/sbin/anacron.orig.anacron ] ; then
rm -f /usr/sbin/anacron
dpkg-divert --rename --remove /usr/sbin/anacron
fi
to this
# Remove diversion of anacron
if [ -e /target/usr/sbin/anacron.orig.anacron ] ; then
rm -f /target/usr/sbin/anacron
chroot /target dpkg-divert --rename --remove /usr/sbin/anacron
fi
Really sorry about that. I think I need a vacation.
Morgennebel wrote:fsmithred wrote:To do a new install with the existing live isos, you can just download the package in a terminal with wget, check the sha256sum and install with dpkg or gdebi. Then run the installer.
I tried the server and netinstall ISOs. Both do not have dpkg available (or I did not found them in /usr/sbin, /sbin or /usr/bin).
You need first to chroot to /target first. dpkg is then available.
# chroot /target
# dpkg -i ....Ciao, -MN
For the installer isos, yeah, you need to chroot. But for the live isos, you don't. The desktop-live has the entire xfce desktop for you to work with plus all the system commands. It is a full system, and the live installer just copies the running system to hard disk. That means any changes you make in configs or packages in the running system will be copied to the installation. The minimal-live doesn't have xorg, but it's still a complete system and will act the same way, just in console only.
fsmithred wrote:New live isos with new repo key and new refractainstaller with anacron fix are uploaded.
Thanks! But FYI you have one more expired key to renew. ;-D
gpg: assuming signed data in 'SHA256SUMS.txt' gpg: Signature made Wed Sep 7 18:11:12 2022 CEST gpg: using RSA key 67F5013216271E85C251E480A73823D3094C5620 gpg: Good signature from "fsmithred (aka fsr) <fsmithred@gmail.com>" [expired] gpg: Note: This key has expired!
I fixed that a long time ago. You need to run
gpg --keyserver keyserver.ubuntu.com --refresh-keys
gpg --list-keys 094c5620
pub rsa4096 2017-10-07 [SC] [expires: 2025-05-02]
67F5013216271E85C251E480A73823D3094C5620
uid [ultimate] fsmithred (aka fsr) <fsmithred@gmail.com>
sub rsa4096 2017-10-07 [E] [expires: 2025-05-02]
New live isos with new repo key and new refractainstaller with anacron fix are uploaded.
No, wget as listed above does not work, because there is no http://deb.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2022.09.04_all.deb,
You must have hit a mirror that wasn't fully updated. If you pick one from the mirror list, you can go to the same directory and find the .deb package.
https://pkgmaster.devuan.org/mirror_list.txt
I don't know the details of how it works, but grub has modules for crypto and for luks. Look under /boot/grub/.
Yeah, I almost warned you about the double password entry. It's very slow, too. I should have said that I recommend it if that's what you really want. Another way to make /boot secure is to remove it from the hard disk and put it on a usb stick. Then you can't boot without the stick. (also inconvenient.)
fsmithred wrote:To do a new install with the existing live isos, you can just download the package in a terminal with wget, check the sha256sum and install with dpkg or gdebi. Then run the installer.
I tried the server and netinstall ISOs. Both do not have dpkg available (or I did not found them in /usr/sbin, /sbin or /usr/bin).
For the installer isos (server, desktop, netinstall) the following might work in a shell:
anna install devuan-keyring_2022.09.04_all.deb
or maybe...
anna install /pool/DEBIAN/main/d/dpkg/dpkg_1.20.9_amd64.deb
dpkg -i devuan-keyring_2022.09.04_all.deb
For the live isos (minimal-live, desktop-live) dpkg is installed and will work. Only the desktop-live has gdebi.
Yes, new live isos are coming soon. The fixed version of the installer is currently in chimaera-proposed-updates.
To use the current isos, wget the new keyring in the live session, and install it with dpkg or gdebi before running the installer.
To do a new install with the existing live isos, you can just download the package in a terminal with wget, check the sha256sum and install with dpkg or gdebi. Then run the installer.
If you download the file and want a checksum, here they are:
$ md5sum devuan-keyring_2022.09.04_all.deb
6209781a66b39c95c012765bc7ca2297 devuan-keyring_2022.09.04_all.deb
$ sha256sum devuan-keyring_2022.09.04_all.deb
96c4a206e8dfdc21138ec619687ef9acf36e1524dd39190c040164f37cc3468d devuan-keyring_2022.09.04_all.deb
yes
then copying /usr/share/keyrings/devuan-keyring.gpg => /etc/apt/trusted.gpg.d
and deleting /etc/apt/trusted.gpg.d/devuan-keyring-2017-archive.gpg
apt-get update works.Temporary solution pending that of the developers.
I believe those extra steps are only needed if you installed the first package made today, dated 2022.09.03, but the second package with date 2022.09.04 copies the new file for you.
New keyring just got built and needs to get into the repos and propagate to the mirrors.
Use option '--no-install-recommends' when you install the nvidia driver. This will prevent nvidia-persistenced from being installed and will eliminate the conflict. You won't miss the package when it's absent.
0:0 is the display you're running on. If you run more than one xserver at a time, they will get unique display numbers.
I don't know what programs supply any of this, but I learned this early in my linux adventures.
Create a second user.
Drop to console with ctrl-alt-F1 (or I guess crtl-shift-F1 on your keyboard)
Log in as the second user.
Run startx -- :1
You will now be in an xsession as the second user on vt08 and display :1.
ctrl-alt-F7 to go to the first xsession
ctrl-alt-F8 to get back to the second xsession
When you're done playing, close that second xsession, log out second user and go back to vt07.
FDE usually refers to a setup that has /boot part of the encrypted volume. I recommend using one of the live isos. Refractainstaller knows how to do it. I can never remember all the steps and the right words, which is why I put it into a script.
Tell the installer you want to encrypt the root partition and don't select a separate boot. Added bonus - don't select a swap partition and let the installer put a small swap file on the encrypted root partition.
If you would rather diagnose and fix your current situation, you probably should show us what's in crypttab, fstab, a menuentry from grub.cfg and whatever you put into /etc/default/grub. And maybe fdisk -l, too.
To make --no-install-recommends the default for your system,
echo 'APT::Install-Recommends "0";' > /etc/apt/apt.conf.d/00norecommends
I can't reproduce the error. I'm running daedalus, installed mariadb-server, then installed the version from ceres. So I upgraded from 1:10.6.8-1 to 1:10.6.9-1 without error. The service got stopped and started successfully.
I don't know what else to do. Maybe someone running ceres would get a different result.
Well, maybe dpkg --configure -a or dpkg-reconfigure mariadb-server-10.6
Not ours. (There's no "devuan" in the version.) So you won't find it in our bug system. Check debian bug reports.
The package still contains an init script, so it can use systemd or sysvinit.
What exactly happened? Did you lose the package upgrading to ceres from daedalus, or on a regular upgrade in ceres, or the package just refuses to install. Did you get any error messages?
apt-cache search mariadb-server
mariadb-server - MariaDB database server (metapackage depending on the latest version)
mariadb-server-10.6 - MariaDB database server binaries
mariadb-server-core-10.6 - MariaDB database core server files
apt policy mariadb-server
mariadb-server:
Installed: (none)
Candidate: 1:10.6.8-1
Version table:
1:10.6.9-1 10
10 http://deb.devuan.org/merged ceres/main amd64 Packages
1:10.6.8-1 500
500 http://deb.devuan.org/merged daedalus/main amd64 Packages
$ apt policy mariadb-server-10.6
mariadb-server-10.6:
Installed: (none)
Candidate: 1:10.6.8-1
Version table:
1:10.6.9-1 10
10 http://deb.devuan.org/merged ceres/main amd64 Packages
1:10.6.8-1 500
500 http://deb.devuan.org/merged daedalus/main amd64 Packages
$ apt-file list mariadb-server-10.6
mariadb-server-10.6: /etc/init.d/mariadb
<snip>
There's an old version of setnet in ascii and an older version in experimental. I'm pretty sure it's still in the minimal-live isos.
The default network manager in jessie, ascii and beowulf was wicd. I don't know why that's missing for you. In Beowulf, you could use network-manager or connman instead if you want.
Install either wicd or network-manager-gnome. I think that either one of those will get put into your desktop startup apps automatically.
Make sure that policykit-1-gnome is installed.
See the section on Session Management and policykit backends in the beowulf release notes:
https://files.devuan.org/devuan_beowulf … _notes.txt
You might want to switch from consolekit to elogind.