Usually one would install task-xfce-desktop and be happy with that. It would bring in that s.c. "standard" xfce desktop environment with all its bells and whistles. Though it appears you want something else.

If you want to do it with tasksel I think you need to reconfigure rather than install.

EDIT: no I was wrong about tasksel; you just run it as root.

try with

SUSPEND_MODULES=xhci_hcd

in /etc/pm/config.d/something

EDIT: That of course will stop wake-up via USB keyboard...

This looks like "the broken xhci_hcd problem" from 2015 is back... at the time it was solved by unloading the module before sleep and loading it back on resume.

It appears that the documentation page you linked
https://www.devuan.org/os/documentation … all-devuan
skips a couple of dialoges:
1. between its 9 and 10 is a dialogue to select which disk to work with, and
2. between its 10 and 11 is a dialog that presents an overview of all disk layouts.

If the #11 dialog in your case includes sdb, you need to choose the "No" option to go back to the partitioner and undo any partitioning of sdb that you have chosen.

I would say that technically the story is that the partitioning software shows all avaiable drives of the system, and it's the person installing that decides and selects which drives to partition and how to use them for installation.

However, it's the software is the debian package partman. If you feel strongly about it you should lodge a bug report about the package to bugs.debian.org.

You may try with a TAB and then add console=ttyS0,115200 to the boot parameters somewhere early, and then you also need to tell qemu to offer the serial on the console perhaps multiplexed with the qemu monitor by adding -serial mon:stdio to its arguments. That will do well until the first reboot where you also need to have configured the bootup init system to offer serial login.

Which issue?

Clearly mount doesn't find any partition with label DEVUAN501 so the preamble moves on to the Ventoy patch in order to loopback the ISO image if it finds that, which it does. The loopback device is next presented to the installer which then is quite happy using that.

Sounds good. (though I wouldn't keep my software at a microsoft site)

Perhaps check out https://www.debian.org/doc/manuals/maint-guide/ and get your package into the debian collection...

Ok.

Perhaps it requires "netconsole"  for entering password if you don't have console access.
See https://www.kernel.org/doc/Documentatio … onsole.txt

That would  mean to use the "netconsole=" boot parameter rather than (or maybe together with) the "ip=" parameter. At the console end you can run a "socat" process, as per exmaple "3)" on that page.

EDIT: you might also want/need the pty option on the socat service, to make it "user friendlier".

EDIT 2: It's probably obvious, but I don't know anything about "clevis" or "tang", so keep filtering my loose ideas.

ok; ctrl+f4 shifts to vt4, which is dedicated to tail -f /var/log/syslog of the installer. Thus, you can use ctrl+f2 and less /var/log/syslog to explore that, or use nc to transfer it to another host.

Yes, "excalibur" is a testing release, and this is a good find.

@edsonwolf: please lodge a Debian bug report for package partman-crypto which apparently expects libgcc_s.so.1 to be an installed library in the installer but lacks dependency to ensure that. Specifically, it does depend on libc6-udeb rather than libc6 with the significant difference that it lacks the dependency on libgcc_s.so.1. The partman-crypto developer(s) need to decide how to handle that.

NOTE: a "Debian bug report" is an email to mailto:submit@bugs.debian.org where the first two body text lines would be

and the rest of the body would be any useful notes to in particular assist the developers in repeating the issue.

Bringing in javascript so members can avoid maintaining existential presence while composing a post is ruled out on policy grounds. That includes variant solution ideas such as adding javascript only for Altoid or expanding the timer concept to make the limit a profile setting.

(Well that last one is technically ruled out by virtue of its implied complexity relative to the body count at the developer team's morning tea)

Off hand a thing one could do without javascript would be an automatic preview kicking in after, say, 28 minutes (by using a so called "refresh tag"), but that would probably be more annoying than helpful.

The idle timer is a "security measure" where the underlying concern is "identity theft" with respect to forum posts. It's a common solution: a session key cookie with time limited validity where every interaction within that time either yields a new such key or (the weaker but simpler approach) just get a validity time extension for the current session key. Other solutions are possible but the morning tea body count is a barrier.