You are not logged in.
If you boot a live-usb, refractainstaller will install the running system. It doesn't need to ask for an iso.
~/.cache is in the rsync excludes list. If yours got copied, then something is wrong. Check the excludes list - /usr/lib/refractasnapshot/snapshot_excludes.list and make sure other excluded items did not get copied. Add anything else here that you want excluded.
In the config file, /etc/refractasnapshot.conf are some options for using compression to make the iso file smaller. You might want to uncomment one of them if you have not already done so. (look for mksq_opt)
You should be able to install to a partition on another usb stick just the same as if you installed to a partition on a hard disk.
I would make a plain backup of my important files without trying to squeeze them into an iso file.
I know two ways to make a live-iso that boots legacy bios or uefi.
1. live-sdk https://dev1galaxy.org/viewtopic.php?id=551
2. refractasnapshot https://refracta.org/docs/readme.refractasnapshot.txt
The latter is easier - it makes a bootable live-iso copy of your installed system. That could be a hardware install or a VM.
Make sure you have a line for chimaera-security in /etc/apt/sources.list
deb http://deb.devuan.org/merged chimaera-security main
You can add 'contrib' and 'non-free' to the end of that line if you have those repos enabled on your other line(s).
Post your sources.list here if you're not sure.
Run these commands at the grub prompt. Adjust the device names if I guessed wrong. Use tab-completion to get the version strings on kernel and initrd. Last command is 'boot' and press ENTER (or maybe ctrl-x).
set root=(hd3,msdos1) # assuming the /boot partition is sdc1
linux /vmlinuz-<version> ro root=/dev/sdc2 # assuming the root partition is sdc2
initrd /initrd.img-<version>
boot
After you boot into the system, get a root terminal and run update-grub That should create a new boot menu.
Both accounts should have been copied into the iso, but the default setting is to boot to the primary user (uid:gid 1000:1000).
To boot to the other user with the iso you already made, edit the boot screen to add username=<whatever the other user's name is>
(Press TAB to edit bios boot menu, press e to edit uefi boot menu)
To make an iso that boots to the second user by default, edit /etc/refractasnapshot.conf to set the desired username.
I'm guessing that you didn't have the wicd metapackage installed. If you did have it, you would have automatically gotten network-manager to replace it. You can bring up the wired connection and install n-m with the following commands (as root).
dhclient eth0
apt update
apt install network-manager-gnome
Or, if you don't want a gui program for connecting to the network, you could just edit /etc/network/interfaces and add the following:
auto eth0
iface eth0 inet dhcp
You can do one or the other, but don't do both of those things.
This video shows a path through the maze of debian-installer to make an encrypted lvm install. Devuan uses the debian-installer with a few modifications. The partitioning is the same in both.
https://www.youtube.com/watch?v=GEl2S5MI-WU
Maybe some qt package is missing. Here's what I have installed that has qt in the name (or description)
Compare what's in your laptop to this list or one like this from your desktop.
$ dpkg -l |grep qt
ii libaudqt2:amd64 4.0.5-1 amd64 audacious media player (libaudqt shared library)
ii libqt5core5a:amd64 5.15.2+dfsg-9 amd64 Qt 5 core module
ii libqt5dbus5:amd64 5.15.2+dfsg-9 amd64 Qt 5 D-Bus module
ii libqt5designer5:amd64 5.15.2-5 amd64 Qt 5 designer module
ii libqt5gui5:amd64 5.15.2+dfsg-9 amd64 Qt 5 GUI module
ii libqt5help5:amd64 5.15.2-5 amd64 Qt 5 help module
ii libqt5multimedia5:amd64 5.15.2-3 amd64 Qt 5 Multimedia module
ii libqt5network5:amd64 5.15.2+dfsg-9 amd64 Qt 5 network module
ii libqt5opengl5:amd64 5.15.2+dfsg-9 amd64 Qt 5 OpenGL module
ii libqt5positioning5:amd64 5.15.2+dfsg-2 amd64 Qt Positioning module
ii libqt5printsupport5:amd64 5.15.2+dfsg-9 amd64 Qt 5 print support module
ii libqt5qml5:amd64 5.15.2+dfsg-6 amd64 Qt 5 QML module
ii libqt5qmlmodels5:amd64 5.15.2+dfsg-6 amd64 Qt 5 QML Models library
ii libqt5quick5:amd64 5.15.2+dfsg-6 amd64 Qt 5 Quick library
ii libqt5quickwidgets5:amd64 5.15.2+dfsg-6 amd64 Qt 5 Quick Widgets library
ii libqt5sql5:amd64 5.15.2+dfsg-9 amd64 Qt 5 SQL module
ii libqt5svg5:amd64 5.15.2-3 amd64 Qt 5 SVG module
ii libqt5test5:amd64 5.15.2+dfsg-9 amd64 Qt 5 test module
ii libqt5webchannel5:amd64 5.15.2-2 amd64 Web communication library for Qt
ii libqt5webengine-data 5.15.2+dfsg-3 all Web content engine library for Qt - Data
ii libqt5webengine5:amd64 5.15.2+dfsg-3 amd64 Web content engine library for Qt
ii libqt5webenginecore5:amd64 5.15.2+dfsg-3 amd64 Web content engine library for Qt - Core
ii libqt5webenginewidgets5:amd64 5.15.2+dfsg-3 amd64 Web content engine library for Qt - Widget
ii libqt5widgets5:amd64 5.15.2+dfsg-9 amd64 Qt 5 widgets module
ii libqt5x11extras5:amd64 5.15.2-2 amd64 Qt 5 X11 extras
ii libqt5xml5:amd64 5.15.2+dfsg-9 amd64 Qt 5 XML module
ii python3-pyqt5 5.15.2+dfsg-3 amd64 Python 3 bindings for Qt5
ii python3-pyqt5.qtsvg 5.15.2+dfsg-3 amd64 Python 3 bindings for Qt5's SVG module
ii python3-pyqt5.qtwebchannel 5.15.2+dfsg-3 amd64 Python 3 bindings for Qt5's WebChannel module
ii python3-pyqt5.qtwebengine 5.15.2-2 amd64 Python 3 bindings for Qt5's WebEngine module
ii python3-pyqt5.sip 12.8.1-1+b2 amd64 runtime module for Python extensions using SIP
ii qt5-image-formats-plugins:amd64 5.15.2-2 amd64 Qt 5 Image Formats module
ii vlc-plugin-qt:amd64 3.0.18-0+deb11u1 amd64 multimedia player and streamer (Qt plugin)
To change an installed system from sysvinit to runit:
apt install runit-init
Follow any instructions on the screen and then reboot.
There's also a new package that has some runit scripts. See this post: https://dev1galaxy.org/viewtopic.php?id=5555
What do "complete load" and "complete reload" mean?
Did you run 'apt update' and 'apt upgrade' before installing calibre?
What is different between the two installations? Calibre runs fine on my chimaera laptop.
If you want a regular installation on the new stick, you can treat it like a hard drive. Partition it with gparted and then just install to that drive with refractainstaller. If you want to be able to use that stick on other computers, you'll need to make sure there's a bootloader on it. (and maybe a few other things to do.)
If you want a live-usb with persistence, I recommend using refracta2usb so that you can create a multi-boot live-usb with multiple persistent volumes (either partitions or loopback files). In that case, make the first partition fat32 and big enough to hold all the live-isos you want to use. And then make at least one linux partition for the persistent volume(s).
The scripts in /etc/cron.* and /etc/rc.local will run as root. Any that you set in your desktop startup apps will run as your user.
For every hour, you could put a script in /etc/cron.hourly.
For running something upon login, you would probably put it in some file that gets sourced at login or in your desktop's startup apps. (e.g. .bashrc, .profile, .xsettings, or other. I'm not sure what's most appropriate.)
For running something when you boot up, you could put commands in /etc/rc.local.
If the ubuntu root filesystem is encrypted, then os-prober in chimaera won't see it. Likewise, os-prober in ubuntu won't see the encrypted devuan. You will have to manually create a menuentry in ubuntu for the chimaera installation.
In ubuntu, put something like this in /etc/grub.d/40_custom and then run update-grub
menuentry 'Devuan' {
set root=(hd1,msdos1)
linux /vmlinuz ro root=/dev/mapper/your-vg-lg-name
initrd /initrd.img
}
Notes:
(hd1,msdos1) assumes that the /boot partition is the first partition on the second hard drive and it has msdos partition table.
/dev/mapper/your-vg-lg-name is the name of the logical volume that holds devuan's root filesystem.
If you switch the order of the hard drives permanently, either through bios settings or opening the box and switching cables, you could do the above procedure in devuan to get a menu entry for the encrypted ubuntu. (If it's not encrypted, then running os-prober should automatically add an entry for it.)
I didn't know yt-dlp was in the repo. The backports version is the same as what's in ceres/sid now, so there's nothing new to backport.
I keep a copy of the script in my user's bin/ and I have a script to wget the latest version from git. Apparently, that script is not needed - you should be able to run yt-dlp -U to update to the latest.
fsmithred wrote:amd64 devuan desktop-live isos (xfce) in qemu with 3G ram. ...
Each release uses more resources. Run ps_mem.py to see that each program uses more resources in each release. I've been watching this for over 20 years and it's consistent.
Yes, but now it would be interesting to know if 3G ram uses less memory than 8G ram or 16G ram or 32G ram.
Chimaera with 2G and 5G:
total used free shared buff/cache available
Mem: 1982 332 1013 15 636 1492
Swap: 0 0 0
total used free shared buff/cache available
Mem: 4932 320 3975 15 636 4379
Swap: 0 0 0
Daedalus with 2G and 5G:
total used free shared buff/cache available
Mem: 1974 546 765 14 828 1427
Swap: 0 0 0
total used free shared buff/cache available
Mem: 4924 656 3681 14 828 4268
Swap: 0 0 0
amd64 devuan desktop-live isos (xfce) in qemu with 3G ram.
Beowulf:
total used free shared buff/cache available
Mem: 3002 273 1963 15 766 2561
Swap: 0 0 0
Chimaera:
total used free shared buff/cache available
Mem: 2987 343 2004 15 639 2482
Swap: 0 0 0
Daedalus:
total used free shared buff/cache available
Mem: 2979 557 1761 14 830 2422
Swap: 0 0 0
Each release uses more resources. Run ps_mem.py to see that each program uses more resources in each release. I've been watching this for over 20 years and it's consistent.
Head_on_a_Stick wrote:... The default Xfce desktop for Devuan uses SLiM or LightDM and both run X under the root user so both are vulnerable to this exploit.
Starting the desktop via GDM or startx will cause X to be run under the normal user and so avoid this vulnerability completely. ... )
Perhaps I have not understood the problem correctly. SLiM or LightDM is clear. But I am thinking about it:
How is it with SDDM?
When I start Plasma Wayland, that is o.k.
But if I start e.g. LXDE with SDDM, how is that.
lxdm and sddm both run X as root. To check that, run
ps aux |grep X
I thought reportbug was fixed, but I don't know for sure. I always use email to report bugs.
Send email to bugs@devuan.org
Subject line should be descriptive
First line of bug should have:
Package: <packagename>
And then the body of the email with explanation of the problem.
It's also not a bad idea to report the problem here first, in case it's not really a bug.
Instructions are here: https://bugs.devuan.org/Reporting.html
New cryptsetup-modified-functions is now in ceres. It'll migrate down to daedalus next week. I know that it installs correctly, but I can't test to see if it does what it's supposed to do. Please test and let me know. Thanks.
$ apt policy cryptsetup-modified-functions
cryptsetup-modified-functions:
Installed: 2023.02.12
Candidate: 2023.02.12
Version table:
*** 2023.02.12 100
100 /var/lib/dpkg/status
23.02.12 10
10 http://deb.devuan.org/merged ceres/main amd64 Packages
Also, I noticed that this section still has a long timeout loop. In the past, I reduced the timeout to 1, I think. Is it still a problem?
_do_stop_remove() {
local name="$1" i rv=0
for i in 1 2 4 8 16 32; do
remove_mapping "$name" 3<&- && break || rv=$?
if [ $rv -eq 1 ] || [ $rv -eq 2 -a $i -gt 16 ]; then
log_action_end_msg $rv
break
fi
log_action_cont_msg "$name busy..."
sleep $i
done
}
I did two installs today with devuan_daedalus_5.0.preview-20230206_amd64_netinstall.iso.
One had an encrypted root partition and unencrypted /boot partition.
The other had encrypted lvm with unencrypted /boot partition, via Guided Partitioning in the installer.
I see no delay in shutdown with either system.
I can still update cryptsetup-modified-functions and build it for ceres/daedalus if there are cases where it's needed.
@devujan: Please put the final version you want me to use in a code box to make it easy for me. (so I don't screw it up.) Thanks.
Thank you!
I guess I will be reviving the cryptsetup-modified-functions package for daedalus.
rolfie wrote:Outlook to Chimaera: there the issue is fixed.
rolfie
In Deadalus the problem is back....
--------------------------patch-----------------------------------------------
--- /lib/cryptsetup/cryptdisks-functions.orig 2023-01-31 21:00:09.967829315 +0100
+++ /lib/cryptsetup/cryptdisks-functions 2023-01-31 21:10:31.023816298 +0100
@@ -184,8 +184,16 @@
# Removes all mappings in crypttab, except the ones holding the root
# file system or /usr
do_stop() {
- local devno_rootfs devno_usr
+ local devno_rootfs devno_usr vgs vg
dmsetup mknodes
+ if [ -x /sbin/lvm ]; then
+ vgs="$(/sbin/lvm vgscan | sed -n '/"/s/^.*"\([^'\'']*\)".*$/\1/p')"
+ if [ -n "${vgs}" ]; then
+ for vg in ${vgs}; do
+ /sbin/lvm vgchange -a n ${vg} >/dev/null 2>&1
+ done
+ fi
+ fi
log_action_begin_msg "Stopping $INITSTATE crypto disks"devno_rootfs="$(get_mnt_devno /)" || devno_rootfs=""
--------------------------patch/----------------------------------------------Above patch mitigates the problem for me (Daedalus FDE && LVM).
Best wishes
Jan
What is this about?
I'm not aware of any "cooldown time between searches" here?
I see it if I'm not logged in. Do a search, try to do another search immediately and it says I have to wait 30 seconds. When I'm logged in, there is no delay for the second search.
Note: I poked around the admin section looking for that setting, but I couldn't find it.
What would be the benefit of a Devuan-specific community repository, as opposed to a Debian-wide one?
Unless you're not intending it to be Devuan-specific, in which case I amend the above to: what would you consider to be the benefits of a Debian-wide community repository?
I imagine that a Debian-wide community repository would not exclude software that requires systemd. One for Devuan would need to exclude things that won't install on Devuan. If you're running Debian, you will probably be able to use anything that's in the crapton repo.