You are not logged in.
In a terminal: Both commands will extract the archive's content in the current directory
$ 7z /path/to/arch.zip
$ unzip /path/to/arch.zip
Multitasking in compression is a trick that zst does.
I don't use it very often, since the command-line switches and defaults are sick, but (de-)compression works nicely.
Did you skip Chimaera?
dist-upgrade works fine form one version to the next release.
I would check that sysvinit is installed (and running if booted):
apt list --installed | grep sysvinit-core
apt list --installed | grep systemd
Obviously, there should be sysvinit-core and no systemd. Then:
apt update
apt -s upgrade
apt upgrade
apt -s dist-upgrade
apt dist-upgrade
usually did it (without forcing or expicit de-installs).
The apt -s lines are optional. They do a simulation to spot problems. It might be tricky to solve dependencies in an interrupted migration.
Some programs will be de-installed during migration, so there is stuff to re-install.
And optional clean-up at the end: apt clean and/or apt autoremove
--
PS: Booted installtion with sysvinit:
$ ps ax | head -2
PID TTY STAT TIME COMMAND
1 ? Ss 0:00 init [2]
In case of systemd: PID 1 is "/sbin/init"
Continuing the migration in a chroot should work. I would do so too.
Network-manager most likely needs updated configuration after migration (see below).
--
Remembering the migration of my notebook to chimaera:
One thing that happens during migration is: The network-device's name changes (from forgotten) to "wlan0" in case of wifi.
The network-manager's config files were still pointing to the prior device name. This was the reason for "no network connection".
The alternative to reconfigure network-manager was to restore the prior network device names:
# echo 'GRUB_CMDLINE_LINUX="net.ifnames=1"' >>/etc/default/grub
# update-grub
# reboot
Using update-grub may or may not be a bad idea in your multi-boot case.
A quick boot-up was impossible - the default time-out is 60 seconds until isc-dhcp-client skips waiting for an IP address. I would not mind if this happens in the background, but it is blocking the boot process.
The fix / config file is:
cat /etc/dhcp/dhclient.conf | grep timeout
#timeout 60;
timeout 10;
I know, it's not rocket science, but it took me ages to finally do it.
Just thinking: The confirm-paste add-on may have been useful in former times, where "paste something with a newline character" lead to direct execution. But this is not the case anymore; pressing the [ENTER] key seems mandatory in bash.
Do you have a specific need for openjdk-8?
Maybe a newer version is already installed.
apt list --installed | grep openjdk
maybe
$ pstree
gives a hint?
# apt dist-upgrade
works too in such cases.
Are there files in "$HOME/.wine/drive_c/windows/system32" ?
I would proabaly start with a fresh wine setup.
$ mv .wine .wine_old # backup
$ winecfg
It looks like a firefox (variant), which is good form my point of view.
What is midoris selling point?
Is the mouse's batterie charged?
Can't remember haveing mouse problems the past decade or so. Would you mind sharing the manufacturer?
Are you looking for a local DNS cache or DNS resolver?
Like e.g. dnsmasq or unbound. Most likely these can be configured to use encrypted connections.
Edit: Just the colour.
2nd search hit was: https://askubuntu.com/questions/1479606 … untu-23-04
pipewire is a good option for bluetooth, and the answer is for debian 12. Probably worth a try.
Probably nothing.
It's ceres - wait until it's fixed or fix it yourself.
None of my business, but do you really want to use the equivalent of debian SID?
The nvme might be physically an older M.2 ssd with sata interface.
Did you reset gimp's config?
mv .config/GIMP .config/GIMP_DEF
To be sure: Create a new user and start gimp.
The point of zerofree (or just doing cat /dev/zero>zero.bin; rm zero.bin) is to reduce the size of a packed image file created with
dd or cat, e.g. cat /dev/sdXn | gzip >sdXn.img.gz.
When creating a partition image file as sparse file, these sectors are omitted anyway.
ceres is sid.
No solution, just some thoughts:
"libdconf1=0.38.0-2" looks like chimaera. Maybe something is left-over? (packages on hold? Or pinning in /etc/apt/preferecenes)?
ntpd: on one system upgraded to daedalus I did: apt purge ntp; apt install ntpsec.
https://unix.stackexchange.com/question … -browse-re
shows some examples using e2image, also for a qcow2- image. Not sure whether this works for your case too.
Same for me.
Adding alreaday installed programs reduces the loss, but it's just trial and error.
EDIT:
Some more runs: Added iteratively "programs to remove" to install. The next one would be acceptable, but not sure about the desktop-* packages:
apt install -s elogind- seatd udisks2 kate libpolkit-qt5-1-1 alsa-tools-gui pm-utils
The following packages will be REMOVED:
desktop-base elogind libpam-elogind libpolkit-gobject-elogind-1-0 libpolkit-gobject-elogind-1-dev light-locker lightdm task-desktop task-lxde-desktop
I stumbled upon https://unix.stackexchange.com/question … browse-res , which is awesome!
Cite:
e2image can be used to create an image of an ext4 file system, while only copying sectors which are in use:
e2image -ra /dev/sda1 /path/to/file.img
file.img will be created as a sparse file, so it will only occupy the space which is really used in the file system, even though its apparent size will reflect the capacity of the file system. It can be mounted directly, like any file system image:
This will save a massive amount of time when making a backup image and it's mountable. Excellent!
One question remains: How can the sparse file "trick" ls?
.
.
.
.
PS:
Since more than a decade I was happily doing:
su -
mount /dev/sda1 /mnt
cat /dev/zero>/mnt/null.dat # until "no space left on device"
rm /mnt/null.dat
umount /dev/sda1
cat /dev/sda1 | gzip >sda1.img.gz
The image-archive sda1.img.gz has a size of about half the partition's effective data-content, but is not mountable of course.
You can always run a simulation and see what would happen, e.g.:
sudo apt install -s elogind- libpam-ck-connector sway seatd
On my machine: Beside loosing some packages, there will be consolekit and seatd for elogind.
Looks like the network is down.
One possibility is to reset the network device names to debian sytle again (devuan: "eth0", debian: "enp???").
Existing network configuration files then should work as before.
su -
echo 'GRUB_CMDLINE_LINUX="net.ifnames=1"' >>/etc/default/grub
update-grub
reboot
If that does not work:
Through recursive dependencies to systemd, it is possible that networkmanger (or connman or whatever) was deinstalled.
That is more complicated; basically you need to download any *.deb-files to install by yourself.
WiFI: I do not know how to configure manually.