There was the old bootchart2 package but it was replaced with a version that uses systemd-analyze plot.

The .deb is installable in chimaera but the related pybootchartgui package is not (because the Python dependencies cannot be satisfied).

To install that clone the upstream git repository:

git clone https://github.com/xrmx/bootchart
cd bootchart
make

Then run

./pybootchartgui.py

Once the bootchard tarball is created (see below).

To run bootchard append these kernel parameters:

initcall_debug printk.time=y init=/sbin/bootchartd

Then check /var/log/bootchart.tgz, which is a tarball containing all the log files.

What makes you think that? What do you actually see during the boot process? Where exactly is the delay experienced?

Unfortunately I have no idea how to debug boot delays under sysvinit. I don't know of any equivalent for systemd-analyze, which can be tremendously useful for this sort of thing, as can the systemd journal.

Perhaps check /var/log/syslog to see if there are any clues there.

Use ~/.Xresources to set the text size in xterm.

Here's my font configuration:

*vt100.faceName: mono:size=11

See the RESOURCES section of man xterm for a full list of options.

Or use this:

xterm -fa mono:size=11

It would not be appropriate to apply this option to x-terminal-emulator because it would break if that alternative was changed to point to a different emulator.

There's nothing to fix. The package version will never change because that's how Devuan releases work.

The youtube-dl version has been updated by pip and is stored under /usr/local/bin/, confirm this for yourself with

which youtube-dl

Then try

# pip3 uninstall youtube-dl
which youtube-dl
youtube-dl --version

It isn't recommended to mix APT python packages with pip but in this case youtube-dl has to change regularly because YouTube modify their APIs to try and stop them and pip doesn't need any other dependencies for this package so it shouldn't wreck any system Python packages. Just don't make a habit of it

Obligatory xkcd link: https://xkcd.com/1987/

OpenBSD can also run startx as the normal user. But xenodm(1) is recommended for that operating system.

https://www.openbsd.org/faq/faq11.html#StartingX

Yes and my point was that Debian have now released v11.2 of bullseye so there should be corresponding packages in https://pkgmaster.devuan.org/merged/dis … ates/main/ but it seems to be empty.

Compare the sizes of Packages.xz in Debian (2.5K) to Devuan (32 bytes: it is an empty file). That doesn't look right to me. But perhaps I'm missing something obvious, in which case my apologies for the noise.

@OP: sorry for the off-topic diversion.

^ This is not correct. Running startx as a normal user is better than using LightDM or SLiM because it runs X under the normal user. See https://www.debian.org/releases/stretch … uires-root for the Debian stretch release announcement that states this unequivocally.

I've just installed Devuan daedalus in a VM using the devuan_daedalus_5.0.preview-20220103_i386_netinstall.iso image and that command does not work for my user. I need to run this from TTY1 to avoid a permissions error:

xinit -- vt1

However startx works just fine and starts an X session with xterm.

I think you are confused and have posted a problem about the wrong command...

And just to note:

Don't do that, you can completely break your system with a single typo.

Use this instead:

SUDO_EDITOR=nano visudo

^ That will check the file before saving it.

Yes indeed, sorry Ralph I was getting confused there.

If I navigate to https://pkgmaster.devuan.org/devuan/dis … ates/main/ I can't see any Contents-* files and the Packages.{gz,xz} files at https://pkgmaster.devuan.org/devuan/dis … ary-amd64/ are completely empty.

Is there a problem with Amprolla?

Well APT wasn't aware of those sources in your last post

Did you try apt update && apt full-upgrade (as root)? You should see references to all the components of the chimaera, chimaera-updates and chimaera-security repositories in the output of the first command.

Those sources seem fine.

What happens when you run

# apt update
# apt full-upgrade

If there are any problems with the second command post the output here in full. Please use code tags when posting terminal output (as I have above), they greatly aid readability.

EDIT: hold on, where's your chimaera-updates?

You should have this line in /etc/apt/sources.list:

deb http://deb.devuan.org/merged chimaera-updates  main contrib non-free

If it's not there add it and apt update && apt upgrade again.

EDIT2: and you should probably also add contrib non-free to the chimaera-security line, just in case.

Read the link.

There is a tor package available from the Devuan repositories so why don't you just use that?