You are not logged in.
Choose 'Expert install' from the boot menu of the installer isos and you will get more questions, including one that allows you to proceed without installing a bootloader.
it fails trying to install the bootloader. It fails before I can select UEFI or MBR.
The bootloader section of the installer does not give you a choice of uefi or bios. That choice is made when you boot the system. You can check this by booting the installer media and when you get to the first screen asking about locale, press alt-F2 to open a shell and run ls /sys/firmware/efi and if that directory exists, you booted in uefi mode.
If the boot device menu doesn't exist or doesn't give you a choice between legacy or uefi for the usb, then check your motherboard settings for the boot order or possibly whether to use legacy or uefi first on removable media.
The isos will boot on uefi or bios systems depending on what the motherboard is set to do. When you boot some removable media, bring up the boot device menu and make sure you select a legacy boot option, not the uefi option. Just setting the board to boot usb or DVD first in the bios settings might not be enough to get it to boot the way you want.
If i do not plug in the stick, then the boot process runs fine to the end but of course without /home mounted....
Maybe a script started by rc.local at the end of boot that checks to see if /home is mounted, and if it is not, it runs 'cryptsetup open <whatever>' and asks for the password. If your boot process without the usb stick is landing at a graphical login screen, you'll probably need to disable the display manager. Maybe the same script that mounts /home could start the DM, too.
Edit: Something like this. I didn't test this but I think it will work. Adjust the names for your setup.Disable the display manager in runlevel 2 using update-rc.d or sysv-rc-conf
#!/bin/sh
if grep -q '/dev/mapper/<name>' /proc/mounts ; then
/etc/init.d/<display-manager> start
else
cryptsetup open /dev/whatever <name>
mount /dev/mapper/<name> <mountpoint>
/etc/init.d/<display-manager> start
fi
exit 0
You noticed! It's been less than an hour since the repo links got changed. So yeah, we are in the midst of the change. Give the mirrors a couple hours to catch up. When we're sure everything else is in place, the website will be updated and there will be an official announcement. Stable installer isos and live isos are already in place.
Are you trying to migrate debian stretch to devuan or are you on some other release of debian? The instructions for migration are not the same for every release. And sometimes you have to do something different from the instructions. Say more about what you're doing.
This page might have the answer. It looks like you have to use a keyscript. https://stackoverflow.com/questions/197 … o-keyboard
I've never done that. I use a keyfile, and if the keyfile is doesn't work, I have a keyslot with a passphrase that I can use to fix it (make a new keyfile) after booting a live-CD or live-USB.
.
already running
I guess your test works. Since it's already running, runit doesn't have to start it or log it. Find out why/how it's running already.
The xfce configuration files are in /etc/xdg/xfce4/ for the defaults, and any changes the user makes to the desktop are stored in ~/.config/xfce4. Other desktop configs are also in ~/.config.
One thing you can try is to move the configs out of the way, log out and log in again. That will make it like the very first login. Then you can inspect the old configs to see if something changed.
Devuan Daedalus is the same as Debian Bookworm. We use the exact same kernel.
$ grep -i fanotify /boot/config-6.1.0-9-amd64
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
Looks like it's in Chimaera, too.
$ grep -i fanotify /boot/config-5.10.0-23-amd64
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
It ;probably means that you still have some debian repository enabled in /etc/apt/source.list/ or sources.list.d/
The version it says will be installed is the version currently in trixie (debian testing).
Make sure you use codenames in sources.list. (i.e. daedalus) not "stable" or "testing".
Run 'apt update' after any changes in your sources.
"Systemd 254 is already available in Arch-Testing, Debian and, oddly enough, Devuan-Unstable,
Nope.
root@devuan:/home/user# aptitude -s install systemd
No candidate version found for systemd
Unable to apply some actions, aborting
root@devuan:/home/user# apt policy libc6
libc6:
Installed: 2.36-9
Candidate: 2.36-9
Version table:
2.37-6 10
500 http://deb.devuan.org/merged ceres/main amd64 Packages
*** 2.36-9 100
100 /var/lib/dpkg/status
root@devuan:/home/user# apt policy systemd
systemd:
Installed: (none)
Candidate: (none)
Version table:
root@devuan:/home/user# grep -v ^# /etc/apt/sources.list
deb http://deb.devuan.org/merged ceres main
I don't see it either. That's weird - they have i386 for 78, 102 and 115, but they skipped 91. You might find a suitable version somewhere else. I don't know if Mozilla makes old versions available, or maybe some brownish distro has one that works.
http://archive.debian.org/debian-securi … refox-esr/
Edit: I just noticed that those might be too old.
Better...
http://ftp.us.debian.org/debian/pool/ma … refox-esr/
I've been playing with an ASUS EEE this week, trying to figure out what software to use on it. There's an old Refracta Jessie on it that runs fine, but daedalus is slow. Anyway, I'm posting this from the firefox-esr I just installed after increasing my swapfile to 2G (same as the RAM). Scrolling is a little choppy, but it seems to be working ok. Only two tabs are open, so I'm not even using half my RAM. Youtube video is choppy, but the audio is smooth. I think the cpu is the limiting issue.
I like links2 for lightweight graphical browsing. It makes the internet look like 1995, which I find very soothing.
I've seen the disk order change when booting with usb in some cases such that what was /dev/sda when booting from internal drive is called some other device name in the installer.
For some reason I had it in my head/was convinced that is was loading to RAM ... 8^°
I wonder where I got that from?
Live isos can boot the entire iso into RAM. That's an option in live-boot that isn't available in the installer isos. Add "toram" or maybe "toram=filesystem.squashfs" to the boot command for a live-usb and then it's not running from the usb stick. You could even remove the usb stick and keep running the system. Booting that way might allow you to install over the imaged usb, but then you have to get it right the first time or else start over with imaging the stick.
Adding something like this to the qemu command might help for some things:
-smp cores=2,threads=2
I don't know what else you could do. I do know that you could make it a lot slower by removing the '-enable-kvm' option.
The the system you're running is a debian-based live system, you could boot the whole iso to RAM and run from there. Booting will be slower but opening programs will be very fast. Add the word "toram" to the boot command or possibly add "toram=filsystem.squashfs" depending on how the usb stick is arranged.
Are you sure it's the network that's slow? I find the whole system to be slow inside a virtual machine.
I could never figure out how to use virt-manager, so I just use plain qemu. Something like this to boot the iso file from your hard drive...
qemu-system-x86_64 -enable-kvm -m 2048 -cdrom devuan_whatever.iso
Change the 2048 to however much RAM you want to give it (in MB)
Edit: Fixed typo.
Bookworm to Daedalus should be similar to the migration of Bullseye to Chimaera.
https://www.devuan.org/os/documentation … o-chimaera
Here's a script to do it for you or look at the code for clues about what issues might come up. This script has probably had very little testing with bookworm/daedalus, but it was modified from bullseye/daedalus.
https://git.devuan.org/farmatito/migration
Basic Daedalus sources.list
deb http://deb.devuan.org/merged daedalus main
deb http://deb.devuan.org/merged daedalus-updates main
deb http://deb.devuan.org/merged daedalus-security main
You could also look at some discussions on this forum about migrating from bullseye to chimaera. There are a few different approaches, and they don't all work for everyone.
*** Make sure you backup important files before you do this. ***
It's not clear what you want to accomplish.
1. If your usb stick is set up with a persistent volume to save changes in the live system, you can install qemu in it. If you don't have persistence set up, you would be better off making a new live-usb with a system that has qemu installed.
2. If you want to install qemu, it would be easier to install it from the devuan repo instead of compiling it from source.
3. Where is the other OS you want to boot? Are you planning to install it into a VM inside your live system? Is there a virtual hard disk with a system already on it?
Most of our packages are from debian, unchanged. That includes python3-venv.
Applications Menu -> Multimedia -> Pulse Audio Volume Control (aka pavucontrol)
If you're not in XFCE, it's probably a slightly different path in the menu. If you still can't find it, open a terminal and run /usr/bin/pavucontrol
Sometimes an update or upgrade will fail if you happen to hit a mirror when it's updating itself. In this case, trying after a few minutes will fix it.
Please post your /etc/apt/sources.list to make sure it's correct.