You are not logged in.
I guess since I didn't specify a font it varies based on whatever the system's default might be
I do not know IM well enough to be certain, but I believe that there may be a clue in the following:
On the IM cli font page it speaks of a -list font option. For 'convert' that leads to an XML file that suggests that the default font (for me with IM6) is AvantGarde-Book:
$ convert -list font | head
Path: /etc/ImageMagick-6/type-urw-base35.xml
Font: AvantGarde-Book
family: AvantGarde
style: Normal
stretch: Normal
weight: 400
glyphs: /usr/share/fonts/type1/urw-base35/URWGothic-Book.t1Here is how to do it cli-method. You will need ImageMagick installed. That also installs more image-tools than you can shake a stick at, including the one that we shall use ('convert').
First, create a directory, call it "Devuan-Font" (whatever). Start a Terminal from that dir & download the Devuan logo:
$ wget https://git.devuan.org/devuan/documentation/raw/branch/master/art/graphics/logo/devuan-logo.png
--2023-08-19 14:30:48-- https://git.devuan.org/devuan/documentation/raw/branch/master/art/graphics/logo/devuan-logo.png
Resolving git.devuan.org (git.devuan.org)... 116.202.138.212, 2a01:4f8:a0:3284::74ca:8ad4
Connecting to git.devuan.org (git.devuan.org)|116.202.138.212|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3316 (3.2K) [image/png]
Saving to: ‘devuan-logo.png’
devuan-logo.png 100%[===================>] 3.24K --.-KB/s in 0s
2023-08-19 14:30:48 (47.2 MB/s) - ‘devuan-logo.png’ saved [3316/3316]
$ file devuan-logo.png
devuan-logo.png: PNG image data, 230 x 48, 8-bit gray+alpha, non-interlacedNow create a script file & run it.
$ chmod 0700 convert-logo
$ cat convert-logo
convert devuan-logo.png \
-gravity North-East -background transparent -splice 0x18 \
-font NimbusSans-Italic -pointsize 15 \
-annotate +4+2 'Powered by' devuan-powered-by.png
$ ./convert-logoThat creates exactly what is wanted. The exact details (font, text size, location, background colours, etc., etc.) can all be modified in exactly the way that you want.
The startup scripts (remember, this is initscripts, not systemd) are in /etc/init.d, etc:
/etc/init.d/ntp
/etc/rc2.d/S03ntp
/etc/rc2.d/S03ntpsec
/etc/rc3.d/S03ntp
/etc/rc3.d/S03ntpsec
/etc/rc4.d/S03ntp
/etc/rc4.d/S03ntpsec
/etc/rc5.d/S03ntp
/etc/rc5.d/S03ntpsecThis is the init.d script:
#!/bin/sh
### BEGIN INIT INFO
# Provides: ntp
# Required-Start: $network $remote_fs $syslog
# Required-Stop: $network $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop:
# Short-Description: Start NTP daemon
### END INIT INFOPATH=/sbin:/bin:/usr/sbin:/usr/bin
. /lib/lsb/init-functions
DAEMON=/usr/sbin/ntpd
PIDFILE=/var/run/ntpd.pidtest -x $DAEMON || exit 0
if [ -r /etc/default/ntp ]; then
. /etc/default/ntp
fiif [ -e /run/ntp.conf.dhcp ]; then
NTPD_OPTS="$NTPD_OPTS -c /run/ntp.conf.dhcp"
fiRUNASUSER=ntp
UGID=$(getent passwd $RUNASUSER | cut -f 3,4 -d:) || true
if test "$(uname -s)" = "Linux"; then
NTPD_OPTS="$NTPD_OPTS -u $UGID"
ficase $1 in
start)
log_daemon_msg "Starting NTP server" "ntpd"
if [ -z "$UGID" ]; then
log_failure_msg "user \"$RUNASUSER\" does not exist"
exit 1
fi
start-stop-daemon --start --quiet --oknodo --pidfile $PIDFILE --startas $DAEMON -- -p $PIDFILE $NTPD_OPTS
log_end_msg $?
;;
stop)
log_daemon_msg "Stopping NTP server" "ntpd"
start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE --retry=TERM/30/KILL/5 --exec $DAEMON
log_end_msg $?
rm -f $PIDFILE
;;
restart|force-reload)
$0 stop && sleep 2 && $0 start
;;
try-restart)
if $0 status >/dev/null; then
$0 restart
else
exit 0
fi
;;
reload)
exit 3
;;
status)
status_of_proc $DAEMON "NTP server"
;;
*)
echo "Usage: $0 {start|stop|restart|try-restart|force-reload|status}"
exit 2
;;
esac
Now you can trace the scripts through & find out where it is failing (although you should have more than one error message to tell you what is happening.
HTH
Whilst searching for the ntp startup script I came across this:
$ less /usr/sbin/ntpdate#! /bin/sh
#
# ntpdate - emulate the crufty old ntpdate utility from NTP Classic
#
# Not documented, as this is strictly a backward-compatibility shim. It's
# based on the recipes at
# http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate
# with corrections for modern ntpdig options.
update:
removed extraneous ']'.
An important difference between Chimaera & Daedalus where firmware is concerned (affecting graphics, bluetooth & all the rest): the Chimaera sources.list is as rolfie set out, but Daedalus is different:
$ cat /etc/apt/sources.list
deb http://deb.devuan.org/merged daedalus main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-updates main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-security main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-proposed-updates main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-backports main non-free-firmware non-free contribComment-out the last two lines whilst you install.
ntpdate has been deprecated for quite some time. You will NOT find it in Devuan (nor Debian] to download. Try apt search nptdate if you do not believe me (it returns zilch).
The word on the Debian beach is found within less /usr/share/doc/ntpdate/NEWS.Debian.gz (dated to Jan 16 2023) which says:
ntpsec (1.2.1+dfsg1-6) unstable; urgency=low
ntpsec is replacing ntp in Debian.
If you were already using ntpsec, you can stop reading now. For
those coming from ntp, NTPsec is a drop-in replacement for common
configurations, but some things have been removed or changed in the
name of security and/or maintainability:
https://docs.ntpsec.org/latest/ntpsec.html
sudo apt-get dist-upgrade involved ~2,000 files & the final sudo apt autoremove involved scores of files being removed.
Considering the size of the install (it was huge) it went without problems. Restarting (new kernel) gave a blank screen, which was heart-stopping (I've had to do repairs on remote servers from the grub command-line in the past and do not want to ever have to repeat that again). Restarting the computer then gave Recovering Journal which is excellent considering the alternative, but not really something that you want to see.
Naturally I've got gripes. Don't much like the colour scheme (sorry, the blue is too bright for my taste). The fonts are different everywhere. mlocate has gone & been replaced by plocate.
The grub startup screen was missing the Devuan theme, and the default Debian grub screen is pants. It probably happened due to a wrong choice during setup, but here is how to fix that: The file to look for is /etc/default/grub. There were two files in that dir:
grub
grub.ucf-old
Doing a diff showed that the old file referenced the Devuan theme. I therefor added the following line at the bottom of 'grub':
$ tail /etc/default/grub
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
GRUB_THEME=/usr/share/desktop-base/grub-themes/desktop-grub-theme/theme.txtThe final fix is to run update-grub and now the Devuan theme shows on startup.
Upgrade to Daedalus from Chimaera page
This is what my /etc/apt/sources.list looks like after I remembered to comment-out the Chimaera releases (the first attempt to upgrade did not work because of that!):
$ cat /etc/apt/sources.list
deb http://deb.devuan.org/merged daedalus main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-updates main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-security main non-free-firmware non-free contrib
# deb http://deb.devuan.org/merged daedalus-proposed-updates main non-free-firmware non-free contrib
# deb http://deb.devuan.org/merged daedalus-backports main non-free-firmware non-free contribI've now issued sudo apt-get update & several hundred updated files are installing.
Isn't it blooming amazing that anyone can design these things?
Have you cleared your cache? I had to to see the changes.
You are right. Shift-f5 & there we are: "Daedalus 5.0 is the current stable release."
Ah well. Let's see how well prepared everything is.
The Devuan Home page *still* says "Chimaera 4.0 is the current stable release", whilst the Devuan Releases page bravely says "Daedalus stable released:2023-08-14".
I got bitten too many times trying to bridge conflicting releases, so am trying to be patient until those two pages reconcile themselves.
It has to be said that the earlier bad experiences were with CentOS, and that was because RedHat deployed technological measures to prevent folks from in-place upgrading from one major release to the next (presumably to force a new release to be purchased but I don't actually know why, I just know that they did it). It's bad enough dealing with a difficult Home-based system, but 10 x worse when it is a remote server that your finances depend upon. Everything was fine going from 3 => 4, but then it got more & more difficult and by CentOS-6 it was clear that going from 6 to 7 was going to be impossible unless you wiped the disk clean. Despicable twats.
Doing my ordinary daily apt update just now and - although no updates available - got the first-time-ever message:
N: Repository 'http://deb.devuan.org/merged chimaera-security InRelease' changed its 'Suite' value from 'stable-security' to 'oldstable-security'
Devuan.org Home page still says:
Devuan Releases
Chimaera 4.0 is the current stable release.
Beowulf 3.1 point release has moved to oldstable status.
Hopefully this will get you a little closer; I'm running Chimaera myself:
$ apt search udhcpc
Sorting... Done
Full Text Search... Done
busybox/stable,now 1:1.30.1-6+b3 amd64 [installed,automatic]
Tiny utilities for small and embedded systems
udhcpc/stable 1:1.30.1-6+b3 amd64
Provides the busybox DHCP client implementation
$ apt-cache policy udhcpc
udhcpc:
Installed: (none)
Candidate: 1:1.30.1-6+b3
Version table:
1:1.30.1-6+b3 500
500 http://deb.devuan.org/merged chimaera/main amd64 PackagesAs soon as I can find out how to discover it, I'll tell you a location for the .deb.
HTH
I'm waiting for the "official" Daedalus release. Thanks for the info.
From memory, that is the error message that I received shortly before posting this msg.
Steps to get to that point:
Click an internal bookmark for the Forum Index
(internal to my own browser-setup, which is to say not directly connected with Dev1)
I refreshed the page & after a short delay got re-directed to the normal index listing (and forgot to copy the error before doing so).
Extra: Clicking any forum section- or post-link seems to have a delay before completion for the past day or so.
xfce4 has it's own 'startx': /usr/bin/startxfce4. Here is the head (options at bottom):
$ head -50 /usr/bin/startxfce4
#!/bin/sh
#
# xfce4
#
# Copyright (C) 1996-2003 Olivier Fourdan (fourdan@xfce.org)
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
#
if test "x$*" != "x"
then
OPTS=""
for OPT in $*
do
if test "x$OPT" = "x--help"
then
# print help and exit
echo "Usage:"
echo " startxfce4 [OPTIONS...]"
echo
echo "Options:"
echo " --help Show help options"
echo " --with-ck-launch Start xfce4-session inside a"
echo " ConsoleKit session"
echo
exit 0
elif test "x$OPT" = "x--with-ck-launch"
then
# try to launch xfce4-session with ck-launch-session in xinitrc
XFCE4_SESSION_WITH_CK="1"
export XFCE4_SESSION_WITH_CK
else
# append
OPTS="$OPTS $OPT"
fi
donePerhaps try that?
Lord, but these threads are full of noise. Please stop it.
Most applications people would want/need in WINE are 32-bit.
Agree. Which is why WINE is (IMO) deprecated for modern Linux, which almost entirely is powered by 64-bit cpus.
This thread is about Daedalus, not Chimaera.
I'm actually reasonably capable of reading the thread title. However, if I can pass over that & like an idiot try to implement it in Chimaera (for the second time), so can others. Hence my post to try to help others not do that.
This has been written about a number of times. Do not attempt to mix the architectures for WINE. Cannot work (been there, done that).
Hello. Check your source list. It should look like this
deb http://deb.devuan.org/merged daedalus main non-free-firmware contrib non-free
Adding 'non-free-firmware' gives continuous errors in Chimaera:
All packages are up to date.
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://deb.devuan.org/merged chimaera InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_GB' as repository 'http://deb.devuan.org/merged chimaera InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://deb.devuan.org/merged chimaera InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://deb.devuan.org/merged chimaera-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_GB' as repository 'http://deb.devuan.org/merged chimaera-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://deb.devuan.org/merged chimaera-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://deb.devuan.org/merged chimaera-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://deb.devuan.org/merged chimaera-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_GB' as repository 'http://deb.devuan.org/merged chimaera-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://deb.devuan.org/merged chimaera-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_GB' as repository 'http://deb.devuan.org/merged chimaera-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://deb.devuan.org/merged chimaera-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://deb.devuan.org/merged chimaera-backports InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_GB' as repository 'http://deb.devuan.org/merged chimaera-backports InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://deb.devuan.org/merged chimaera-backports InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)$
$ cat /etc/apt/sources.list
# 2023-02-01 added non-free-firmware; see https://dev1galaxy.org/viewtopic.php?pid=40751
# 2023-02-01 above removed as not active in Chimaera
deb http://deb.devuan.org/merged/ chimaera main contrib non-free
deb http://deb.devuan.org/merged/ chimaera-security main contrib non-free
deb http://deb.devuan.org/merged/ chimaera-updates main contrib non-free
# changed next line following https://dev1galaxy.org/viewtopic.php?pid=38033#p38033
# deb http://deb.devuan.org/devuan/ chimaera-proposed-updates contrib non-free main
deb http://deb.devuan.org/merged/ chimaera-proposed-updates main contrib non-free
deb http://deb.devuan.org/merged/ chimaera-backports main contrib non-freeGah!
I blame forgetfulness (aka old age):
$ ps aux | grep cron
root 1516 0.0 0.0 8684 3460 ? Ss Jul01 0:01 /usr/sbin/cron
alexk 8432 0.0 0.0 6372 712 pts/0 S+ 14:52 0:00 grep --color=auto cronit's look like that we see the grep process ! not the crond !? Am I right?
Correct (I got the exact same result). Cron is NOT running in your system (you have grepped for 'crond', and therefore in the ps listing it shows the full command-line, which includes 'crond'). If Cron *was* running there would be at least 2 ps lines containing 'crond', one for the daemon & one for grep.
Synaptic 0.90.2
Tried just now, no problems (no update neither, because I update daily using a self-written script).
$ uname -a
Linux ng3 6.1.0-0.deb11.7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-2~bpo11+1 (2023-04-23) x86_64 GNU/Linux
$ cat /etc/os-release
PRETTY_NAME="Devuan GNU/Linux 4 (chimaera)"
NAME="Devuan GNU/Linux"
VERSION_ID="4"
VERSION="4 (chimaera)"
VERSION_CODENAME="chimaera"
ID=devuan
ID_LIKE=debian
HOME_URL="https://www.devuan.org/"
SUPPORT_URL="https://devuan.org/os/community"
BUG_REPORT_URL="https://bugs.devuan.org/"$ apt search gtk | fgrep -i installed
# …
gir1.2-ayatanaappindicator3-0.1/stable,now 0.5.5-2+deb11u2 amd64 [installed,automatic]
gir1.2-gtk-3.0/stable,now 3.24.24-4+deb11u3 amd64 [installed,automatic]
gir1.2-gtksource-3.0/stable,now 3.24.11-2 amd64 [installed,automatic]
gir1.2-gtksource-4/stable,now 4.8.0-1 amd64 [installed,automatic]
gir1.2-javascriptcoregtk-4.0/stable-security,stable-proposed-updates,now 2.40.2-1~deb11u1 amd64 [installed]
gir1.2-keybinder-3.0/stable,now 0.3.2-1.1 amd64 [installed,automatic]
gir1.2-pango-1.0/stable,now 1.46.2-3 amd64 [installed,automatic]
gir1.2-soup-2.4/stable,now 2.72.0-2 amd64 [installed,automatic]
gir1.2-webkit2-4.0/stable-security,stable-proposed-updates,now 2.40.2-1~deb11u1 amd64 [installed]
gksu/now 2.0.2-9+b1 amd64 [installed,local]
gpick/stable,now 0.2.6-1 amd64 [installed]
spell-checking library for GTK+ applications - installed tests
gstreamer1.0-gtk3/stable-security,stable-proposed-updates,now 1.18.4-2+deb11u2 amd64 [installed,automatic]
gtk-update-icon-cache/stable,now 3.24.24-4+deb11u3 amd64 [installed,automatic]
gtk2-engines/stable,now 1:2.20.2-5 amd64 [installed,automatic]
gtk3-engines-xfce/now 3.2.0-4 amd64 [installed,local]
gtk3-nooverlayscrollbar/stable,now 7.0.1-5 all [installed,automatic]
# …I got a bunch of Bind updates today:
$ tail /var/log/apt/history.log
Commandline: apt upgrade
Requested-By: alexk (1000)
Upgrade: josm-latest:amd64 (1.5.svn18763, 1.5.svn18765), libx11-xcb1:amd64 (2:1.7.2-1, 2:1.7.2-1+deb11u1), libx11-data:amd64 (2:1.7.2-1, 2:1.7.2-1+deb11u1), libx11-dev:amd64 (2:1.7.2-1, 2:1.7.2-1+deb11u1), libx11-doc:amd64 (2:1.7.2-1, 2:1.7.2-1+deb11u1), libx11-6:amd64 (2:1.7.2-1, 2:1.7.2-1+deb11u1)
End-Date: 2023-06-21 10:57:12
Start-Date: 2023-06-26 15:49:36
Commandline: apt upgrade
Requested-By: alexk (1000)
Upgrade: josm-latest:amd64 (1.5.svn18765, 1.5.svn18770), bind9-host:amd64 (1:9.16.37-1~deb11u1, 1:9.16.42-1~deb11u1), bind9-dnsutils:amd64 (1:9.16.37-1~deb11u1, 1:9.16.42-1~deb11u1), bind9-libs:amd64 (1:9.16.37-1~deb11u1, 1:9.16.42-1~deb11u1), dnsutils:amd64 (1:9.16.37-1~deb11u1, 1:9.16.42-1~deb11u1)
End-Date: 2023-06-26 15:50:44Thanks for the use of 'neofetch' - works nicely on my Chimaera system, yet I never knew it existed:
$ apt search neofetch
Sorting... Done
Full Text Search... Done
neofetch/stable,now 7.1.0-2 all [installed]
Shows Linux System Information with Distribution Logoalexk@ng3:~$ neofetch
..,,;;;::;,.. alexk@ng3
`':ddd;:,. ---------
`'dPPd:,. OS: Devuan GNU/Linux 4 (chimaera) x86_64
`:b$$b`. Model: 90BJ008CUK Lenovo H30-05
'P$$$d` Kernel: 6.1.0-0.deb11.7-amd64
.$$$$$` Uptime: 1 day, 11 hours, 58 mins
;$$$$$P Packages: 2724 (dpkg)
.:P$$$$$$` Shell: bash 5.1.4
.,:b$$$$$$$;' Resolution: 1366x768
.,:dP$$$$$$$$b:' DE: Xfce 4.16
.,:;db$$$$$$$$$$Pd'` WM: Xfwm4
,db$$$$$$$$$$$$$$b:'` WM Theme: Default
:$$$$$$$$$$$$b:'` Theme: Clearlooks-Phenix-Deepsea [GTK2], Adw
`$$$$$bd:''` Icons: oxygen [GTK2], Adwaita [GTK3]
`'''` Terminal: xfce4-terminal
Terminal Font: Monospace 12
CPU: AMD A8-7410 APU with AMD Radeon R5 Grap
GPU: AMD ATI Radeon R4/R5 Graphics
Memory: 1770MiB / 7356MiBPS
I see the colours in the terminal, but cannot display them as background in BBCode. Here they are as text (does not work within code tags):
>EEE8D5DC322F859900B58900268BD2D336822AA198073642<
>FDF6E3CB4B1693A1A1839496657B836C71C4586E75002B36<