You are not logged in.
Damn looks like you either need to edit the package or give up on the fax in it. I would think there is not a lot times you need a fax machine.
Edit: Another option is just extract the package and manually move the files to where they would normally be installed. I would think the systemctl is just restarting the CUPS daemon for it to find the new .ppd file(s) is should probably be installing, plus maybe a binary for the fax function.
Does a Debian arm64 installer iso boot syslinux?
From playing around with my Pi4 they use uboot I believe it is as they have all the files required to boot in the /boot directory with the device tree overlays (.dtb files) that are used. They do not boot the same way as other machines. Now I mount the drive for it they are in the / of the drive.
root@9600k:~# mount /dev/sdb1 /tmp/root
root@9600k:~# ll /tmp/root/
total 128528
-rwxrwxr-x 1 root root 26538 Sep 10 05:54 bcm2711-rpi-4-b.dtb
-rwxrwxr-x 1 root root 27111 Sep 10 05:54 bcm2711-rpi-cm4-io.dtb
-rwxrwxr-x 1 root root 14723 Sep 10 05:54 bcm2837-rpi-3-a-plus.dtb
-rwxrwxr-x 1 root root 14995 Sep 10 05:54 bcm2837-rpi-3-b.dtb
-rwxrwxr-x 1 root root 15351 Sep 10 05:54 bcm2837-rpi-3-b-plus.dtb
-rwxrwxr-x 1 root root 14369 Sep 10 05:54 bcm2837-rpi-cm3-io3.dtb
-rwxrwxr-x 1 root root 52456 Jul 1 22:58 bootcode.bin
-rwxrwxr-x 1 root root 99 Sep 10 05:54 cmdline.txt
-rwxrwxr-x 1 root root 289 Sep 10 05:54 config.txt
-rwxrwxr-x 1 root root 3187 Jul 1 22:58 fixup4cd.dat
-rwxrwxr-x 1 root root 5448 Jul 1 22:58 fixup4.dat
-rwxrwxr-x 1 root root 8452 Jul 1 22:58 fixup4db.dat
-rwxrwxr-x 1 root root 8454 Jul 1 22:58 fixup4x.dat
-rwxrwxr-x 1 root root 3187 Jul 1 22:58 fixup_cd.dat
-rwxrwxr-x 1 root root 7314 Jul 1 22:58 fixup.dat
-rwxrwxr-x 1 root root 10298 Jul 1 22:58 fixup_db.dat
-rwxrwxr-x 1 root root 10298 Jul 1 22:58 fixup_x.dat
-rwxrwxr-x 1 root root 27165545 Aug 11 04:17 initrd.img-5.10.0-31-arm64
-rwxrwxr-x 1 root root 27166803 Sep 10 05:54 initrd.img-5.10.0-32-arm64
-rwxrwxr-x 1 root root 793116 Jul 1 22:58 start4cd.elf
-rwxrwxr-x 1 root root 3722504 Jul 1 22:58 start4db.elf
-rwxrwxr-x 1 root root 2228800 Jul 1 22:58 start4.elf
-rwxrwxr-x 1 root root 2981192 Jul 1 22:58 start4x.elf
-rwxrwxr-x 1 root root 793116 Jul 1 22:58 start_cd.elf
-rwxrwxr-x 1 root root 4794472 Jul 1 22:58 start_db.elf
-rwxrwxr-x 1 root root 2952960 Jul 1 22:58 start.elf
-rwxrwxr-x 1 root root 3704808 Jul 1 22:58 start_x.elf
-rwxrwxr-x 1 root root 1076 Oct 1 23:58 sysconf.txt
-rwxrwxr-x 1 root root 27469760 Aug 11 04:17 vmlinuz-5.10.0-31-arm64
-rwxrwxr-x 1 root root 27469760 Sep 10 05:54 vmlinuz-5.10.0-32-arm64Edit: Now I remember and clue in that was the firmware partition that is mounted as /boot/firmware.
root@9600k:~# mount /dev/sdb2 /tmp/root
root@9600k:~# cat /tmp/root/etc/fstab
# The root file system has fs_passno=1 as per fstab(5) for automatic fsck.
LABEL=RASPIROOT / ext4 rw 0 1
# All other file systems have fs_passno=2 as per fstab(5) for automatic fsck.
LABEL=RASPIFIRM /boot/firmware vfat rw 0 2
root@9600k:~# blkid |grep RASPI |sort -n
/dev/sdb1: SEC_TYPE="msdos" LABEL_FATBOOT="RASPIFIRM" LABEL="RASPIFIRM" UUID="0570-6A9B" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="a2760bd5-f1e2-4765-a0ec-ca7ed959c066"
/dev/sdb2: LABEL="RASPIROOT" UUID="b00e7b01-391c-4729-85b4-7aa97205664a" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="08aa064e-f0a4-492e-a096-45b797c76e22"BIOS to specify what type of time was being set in the BIOS when what he was saying was to use the UTC time for my Region and Location to set the time in the BIOS. big_smile
Yes as has been pointed out you set the time in the BIOS/UEFI to the offset from UTC for your time zone. For instance in mine it is set to 4 hours less than UTC as my offset is -4 this makes everything work properly when the systems use UTC as most all *nix systems use it, like Linux, the BSDs & MacOS. Only Windows usually defaults to using local time as the multitude of postings of "why does my clock change when dual booting" can attest to.
Give the replacement package for it a try, it does not get installed by default. Either that or download the package extract it then make the edit to not call systemctl after that using the dpkg-repack to get new package to install.
zeus@9600k:~$ apt info systemctl
Package: systemctl
Version: 1.4.4181-1.1
Priority: optional
Section: admin
Source: docker-systemctl-replacement
Maintainer: Dmitry Smirnov <onlyjob@debian.org>
Installed-Size: 279 kB
Depends: python3:any
Recommends: procps
Suggests: tini | dumb-init
Conflicts: systemd
Homepage: https://github.com/gdraheim/docker-systemctl-replacement
Download-Size: 79.8 kB
APT-Sources: http://deb.devuan.org/merged excalibur/main amd64 Packages
Description: daemonless "systemctl" command to manage services without systemd
"systemctl" is a replacement command to control system daemons without
systemd. "systemctl" is useful in application containers where systemd is
not available to start/stop services.
.
This script can also be run as init of an application container (i.e. the
main "CMD" on PID 1) where it will automatically bring up all enabled
services in the "multi-user.target" and where it will reap all zombies
from background processes in the container. When stopping such a container
it will also bring down all configured services correctly before exit.When I reload Synaptic, I get the following message at the end:
That is not what is needed, we need to see the contents of the /etc/apt/sources.list file to confirm the correct lines in there.
# normal devuan sources
deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmwareYou should see a line similar to what I have above listed for the main updates, then the daedalus-updates & daedalus-security on their own lines in the file too.
What is the correct way to fix this?
Set the BIOS time to UTC or change the /etc/adjtime to say LOCAL instead of the UTC time it is now set too.
zeus@9600k:~$ cat /etc/adjtime
0.000000 1735138312 0.000000
1735138312
UTCEdit#3: sleuthing around the internet today, I guess I should have used su - to get the correct path.
From my install notes when I seen this come through.
SU changes not noticed here but may be in future so may as well set it up.
Changes in su
- The behavior of su has changed. Use 'su -' to get root's path or use
the full path to commands if you use only 'su'.
- There are several ways to get the old behavior. The easiest is to
edit /etc/default/su to add the line:
ALWAYS_SET_PATH yes
root@9600k:~# cat /etc/default/su
cat: /etc/default/su: No such file or directory
root@9600k:~# nano /etc/default/su
root@9600k:~# cat /etc/default/su
# Added to always have the PATH set for su.
ALWAYS_SET_PATH yesYou might want to create that file on your installs and install the lovely little program apt-listchanges which tells you thing like this when updating your packages..
A necro post to say thanks for the solution to getting even more of that scumbags code off my machine. Did not know I was even running it until I saw pulseaudio getting updated. Search and found this page with one of the easiest solutions I have ever done I do believe. Create an .xsessionrc with the contents from above the first one with the sleep 1 posting in it, install the pipewire-audio that removes the pulseaudio package then reboot to have working audio on the pipewire server. Perfect thanks again.
Well just chain them together like any other commands you can do.
update-rc.d cups enable; update-rc.d bluetooth enable; update-rc.d cups-registryd enablezeus@9600k:~$ ls ; pwd ; whoami
bin Documents mbox Pictures rtorrent Templates
Desktop Downloads Music Public src Videos
/home/zeus
zeusThat will execute each command one after the other when used on the command line, like I show above.