You are not logged in.
Perhaps I should withhold updating until it is released or limit it to the security repo only.
I fail to see why Trixie (which in Devuan is Excalibur) is in the hard freeze state all you will ever get for updates at this point are bug fixes/security updates of the frozen software versions already installed. Once the new OS software is released as stable then the security archive starts to get packages as those issues come up.
Okay, I will try to find the advice I missed.
You may also want to apt update then apt upgrade. It appears your kernel is two versions (-35 vs -37) behind the present released version by Debian which Devuan follows very closely. Most times on my main Devuan machine I will get the new kernel before it hits the Debian archives for those other machines I have running Debian systemd free.
Who's asking it to look for vmlinux?
I have no clue nor the interest to search the source to find out why the stupid things "Skipping BTF generation" step is looking for vmlinux now I notice instead of the vmlinuz that is there when the auto-complete gave it to me on my Debian system when I was wondering it was not finding what I knew had to be there to boot.. I went systemd free with after seeing how easy it is to do on a Devuan conversion.
seeder1@8400t:~$ acp systemd
systemd:
Installed: (none)
Candidate: (none)
Version table:
254.26-1~bpo12+1 -1
100 http://ftp.ca.debian.org/debian bookworm-backports/main amd64 Packages
252.38-1~deb12u1 -1
500 http://ftp.ca.debian.org/debian bookworm-proposed-updates/main amd64 Packages
500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
252.36-1~deb12u1 -1
500 http://ftp.ca.debian.org/debian bookworm/main amd64 Packages
Though now I remember I have system like it with compiler and everything necessary just for shits and giggles since I have some time on my hands..
seeder1@8400t:~$ acp gcc
gcc:
Installed: 4:12.2.0-3
Candidate: 4:12.2.0-3
Version table:
*** 4:12.2.0-3 500
500 http://ftp.ca.debian.org/debian bookworm/main amd64 Packages
100 /var/lib/dpkg/status
seeder1@8400t:~$ acp build-essential
build-essential:
Installed: 12.9
Candidate: 12.9
Version table:
*** 12.9 500
500 http://ftp.ca.debian.org/debian bookworm/main amd64 Packages
100 /var/lib/dpkg/status
seeder1@8400t:~$ acp make
make:
Installed: 4.3-4.1
Candidate: 4.3-4.1
Version table:
*** 4.3-4.1 500
500 http://ftp.ca.debian.org/debian bookworm/main amd64 Packages
100 /var/lib/dpkg/status
seeder1@8400t:~$ acp git
git:
Installed: 1:2.39.5-0+deb12u2
Candidate: 1:2.39.5-0+deb12u2
Version table:
*** 1:2.39.5-0+deb12u2 500
500 http://ftp.ca.debian.org/debian bookworm/main amd64 Packages
500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
100 /var/lib/dpkg/status
seeder1@8400t:~$ acp linux-headers-$(uname -r)
linux-headers-6.1.0-37-amd64:
Installed: 6.1.140-1
Candidate: 6.1.140-1
Version table:
*** 6.1.140-1 500
500 http://ftp.ca.debian.org/debian bookworm-proposed-updates/main amd64 Packages
500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
100 /var/lib/dpkg/status
seeder1@8400t:~$ alias acp
alias acp='apt-cache policy'
seeder1@8400t:~$ ll src
ls: cannot access 'src': No such file or directory
seeder1@8400t:~$ mkdir src
seeder1@8400t:~$ cd src
seeder1@8400t:~/src$ git clone https://github.com/lwfinger/rtw89.git
Cloning into 'rtw89'...
remote: Enumerating objects: 7524, done.
remote: Counting objects: 100% (1755/1755), done.
remote: Compressing objects: 100% (94/94), done.
remote: Total 7524 (delta 1703), reused 1661 (delta 1661), pack-reused 5769 (from 2)
Receiving objects: 100% (7524/7524), 7.99 MiB | 23.11 MiB/s, done.
Resolving deltas: 100% (6041/6041), done.
seeder1@8400t:~/src$ cd rtw89
eeder1@8400t:~/src/rtw89$ make
make -C /lib/modules/6.1.0-37-amd64/build M=/home/seeder1/src/rtw89 modules
make[1]: Entering directory '/usr/src/linux-headers-6.1.0-37-amd64'
CC [M] /home/seeder1/src/rtw89/core.o
/home/seeder1/src/rtw89/core.c:1751:11: warning: ‘rtw89_rxdesc_to_nl_he_gi’ defined but not used [-Wunused-function]
1751 | static u8 rtw89_rxdesc_to_nl_he_gi(struct rtw89_dev *rtwdev,
| ^~~~~~~~~~~~~~~~~~~~~~~~
CC [M] /home/seeder1/src/rtw89/mac80211.o
CC [M] /home/seeder1/src/rtw89/mac.o
snip......
Skipping BTF generation for /home/seeder1/src/rtw89/rtw_8852c.ko due to unavailability of vmlinux
CC [M] /home/seeder1/src/rtw89/rtw_8852ce.mod.o
LD [M] /home/seeder1/src/rtw89/rtw_8852ce.ko
BTF [M] /home/seeder1/src/rtw89/rtw_8852ce.ko
Skipping BTF generation for /home/seeder1/src/rtw89/rtw_8852ce.ko due to unavailability of vmlinux
CC [M] /home/seeder1/src/rtw89/rtw_8922a.mod.o
LD [M] /home/seeder1/src/rtw89/rtw_8922a.ko
BTF [M] /home/seeder1/src/rtw89/rtw_8922a.ko
Skipping BTF generation for /home/seeder1/src/rtw89/rtw_8922a.ko due to unavailability of vmlinux
CC [M] /home/seeder1/src/rtw89/rtw_8922ae.mod.o
LD [M] /home/seeder1/src/rtw89/rtw_8922ae.ko
BTF [M] /home/seeder1/src/rtw89/rtw_8922ae.ko
Skipping BTF generation for /home/seeder1/src/rtw89/rtw_8922ae.ko due to unavailability of vmlinux
make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-37-amd64'
seeder1@8400t:~/src/rtw89$ ll /vmlinuz
0 lrwxrwxrwx 1 root root 27 Jun 28 09:58 /vmlinuz -> boot/vmlinuz-6.1.0-37-amd64
With the result being the bottom of the snipped output with some stupid foolishness about not being able to find vmlinuz which is clearly there. Who knows if the the make install would work I am not interested in seeing if that step works. But if the OP will actually listen to advice given he can try and and find out.
They did. Read the makefile.
I will help with generic advice on compiling and on the odd occasion will read and build the driver on a system, this is not one of them times. Most times though I will not install dev tools just to do that. The OP has enough problems following advice given, my effort level in that case is not that high to go that extra mile.
Any suggestions?
Yes firstly stop trying to compile as root do the ./configure, and ./make steps as a normal user then when needing to install the module use sudo make install this is the only step that requires the root user to get done. And I see nothing about the ./configure step being done. Lastly where does this crazy line come from make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.1.0-35-amd64/build. You are already on the x86_64 arch with the kernel headers installed and since it is the same arch you are not cross-compiling, try make instead. Start with newly extracted source for the proper driver as pointed out above the source you try to use is out of date according to the posting by steve_v. You want the linked rtw_89 and you just might have chance of having some success in getting it done.
If I want to take an HDD with a personal install (choice of applications) and use it in several different systems, can I make such an HDD with a typical "Live" disk?
Certainly can and is what my cloning script does. It takes my live running system and clones it to the drive I choose which I then boot it on. When booting the boot process does hardware probes which will load the required drivers for the system booted on. Where you can run into problems is when you have nvidia card using the proprietary drivers that will fail on machine without one in it that can use the driver installed. I rarely do installs any more it is simple clone boot then clone onto new machine once booted. Edit three files to change the UUIDs required for the new machine drive to ensure proper booting once done and reboot to new install with all of my previous information and settings intact.
The way it can be done with a live USB is by booting the live installer on your original install. with new machine drive connected to it. Then you open a terminal and partition the new drive and format it. You then mount the current install drive partitions and the new install drive partitions. Using the rsync program you copy byte for byte the original to the new drive then make the UUID changes in the already mentioned three files for EFI install, MBR no clue. Take the drive put it in the new machine and it should just boot. I made post just the other day giving all of the commands needed to do it.
Edit: The thread that contains the instructions.
and choose the right drivers for whatever system the disk has been placed in? Or is that a special mode that has to be configured by expert devs?
That is by definition what most live boot systems are. They are designed to have pretty much all the drivers needed to boot on most hardware. Now there are some live boot systems which only boot on certain hardware like a Pi or other such specialized hardware. But for the most part the 32 and 64 bit live disks for the most common Intel/AMD processors will boot on the vast majority of the hardware out there doing what you want without any extra effort.
it's vey sad whats being happening in other linux forums bro, .... didn't cared about Xlibre or his wack creator, that was a very, very crazy situation! Anyways we feel a lot better being here, thanks again!
I have noticed this too in Linux fourms lately the total buy in to the coporate parasite control agenda that they are foisting onto linux with the systemd and wayland garbage. With the Gnome trolls leading the charge for it for well over a decade now.
When you use one of those 'whole partition' transfer utilities to copy a system from an old HD to an SSD, does the OS notice the change in hardware?
I do not use them utilities. Here is my method on booted live usb using rsync. First you create the new partitions on the drive to be copied to. below is example of the cloning operationing on one of my machines for EFI booting I have no clue on MBR drive.
et to a second cloning to the Samsung NVMe 128GB external enclosure drive the
extra one I have a duplicate.
root@9600k:~# gdisk /dev/sdb
GPT fdisk (gdisk) version 1.0.10
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y
Command (? for help): n
Partition number (1-128, default 1):
First sector (34-250069646, default = 2048) or {+-}size{KMGTP}:
Last sector (2048-250069646, default = 250068991) or {+-}size{KMGTP}: 500MB
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300): ef00
Changed type of partition to 'EFI system partition'
Command (? for help): n
Partition number (2-128, default 2):
First sector (34-250069646, default = 1026048) or {+-}size{KMGTP}:
Last sector (1026048-250069646, default = 250068991) or {+-}size{KMGTP}:
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300):
Changed type of partition to 'Linux filesystem'
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
The formatting of the drive I go first partitiion EFI system which needs to be fat32, ext4 for second and third partition, the /root and /home partitions.
root@9600k:~# mkfs.vfat -F 32 /dev/sdb1
root@9600k:~# mkfs.vfat -F 32 /dev/sdb1
root@9600k:~# fatlabel /dev/sdb1 DRIVEEFI
root@9600k:~# mkfs.ext4 -m 0 -L DRIVEROOT /dev/sdb2
root@9600k:~# mkfs.ext4 -m 0 -L DRIVEHOME /dev/sdb3
The -m 0 reserves not space on the partitions the default without is 5% and the -L gives you partition label.
Now the actual copying/cloning from booted usb. Open terminal from desktop environment use these commands.
sudo mkdir /tmp/oldroot
sudo mkdir /tmp/newroot
sudo mkdir /tmp/oldhome
sudo mkdir /tmp/newhome
sudo mkdir /tmp/oldefi
sudo mkdir /tmp/newefi
Then mount the partitions using sudo fdisk -l to determine the actual drive letter number of the partition to be cloned.
sudo mount /dev/sda1 /tmp/oldefi
sudo mount /dev/sdb1 /tmp/newefi
sudo mount /dev/sda2 /tmp/oldroot
sudo mount /dev/sdb2 /tmp/newroot
sudo mount /dev/sda3 /tmp/oldhome
sudo mount /dev/sdb3 /tmp/newhome
Now clone.
sudo scp -r /tmp/oldefi/* /tmp/newefi/
sudo rsync -avP /tmp/oldroot/* /tmp/newroot/
sudo rsync -avP /tmp/oldhome/* /tmp/newhome/
Once the cloning is done you need to edit some files for the new UUIDs on the cloned to drive so it will boot. To get the required information use the sudo blkid command an example of its output below.
Mushkin 480GB SSD
/dev/sda1: LABEL_FATBOOT="MUSHKINEFI" LABEL="MUSHKINEFI" UUID="6465-9332" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="d2a1b57d-794c-4ed8-9c76-1c6d12108f6b"
/dev/sda2: LABEL="MushkinRoot" UUID="03fec226-03dd-40de-8728-1bf7ae86239d" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="4e0572c1-cac9-4319-bd7f-90c9806d0a26"
/dev/sda3: LABEL="MushkinHome" UUID="6db5ea58-64bd-45db-aa1c-004c6b782f04" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="319d59c2-0efe-4d3b-a37e-8c1e517ee813"
There you can see where to get them from. Now three files need to be edited on a Devuan EFI system. The first.
root@9600k:~# cat /boot/efi/EFI/debian/grub.cfg
search.fs_uuid 766dcfc3-a1e4-495f-86e2-570205723fef root
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
On the cloned drive this file would be /tmp/newefi/EFI/debian/grub.cfg you edit with your favourite editor to change to new UUID for the new / from the blkid command earlier. The second is the /tmp/newroot/etc/fstab where you edit all three the old EFI, / and /home to the new UUIDs for them. Lastly
Here I show example from script I have that does all of this part on live running system.
# My Mushkin 8500t intenal
sed -i "s/6977106c-69db-4634-b33f-9a03da4b46ed/03fec226-03dd-40de-8728-1bf7ae86239d/g" /root/bin/boot_mushkin_8500t_grub.cfg
So the command to do it on cloned drive would be.
sed -i "s/oldrootUUID/newrootUUID/g" /tmp/newroot/boot/grub/grub.cfg
Then you can reboot and when the new drive is selected from the one time EFI boot menu it should just fire up. Now I look back this shows two partition drive in the gdisk step just continue on with next partition if desired. I have done this hundreds of times and it works every time unless I forget to edit a UUID when manually, my scripts run it flawless to back and restore to my various machines and drives. Good luck if you use this method it should just work unless I have stupid typo I missed when checking it over..
Lets hope some talented programmers in debian take this up.
I have my doubts on that Debian seems to have gone full on in on the corporate control of GNU/Linux. All their actions over the last decade or so prove this including the reason this project exists. I would be happy to be wrong in this but all signs point to it being true.
say that this is not a minimal system installation, because Plasma does not fall into the understanding of minimalism.
It is a minimalist way of getting a graphical installation on the computer without all the extras that get pulled in by the meta package method of installing and is what I do every time as well. Which is obviously his goal when doing such he did not say he wants next to nothing installed.. Your understanding of what he wants in a minimal install is totally wrong for this situation.
But maybe I am wrong and there is no such thing, not even with "snap".
You are not wrong, never seen it on Linux, it is always the web app. Even when it is wrapped into an application by someone you are stuck with the web app. Which means no video calling at all only an option for voice call. And of course using the cell phone to link the app to be able to use it on your computer.
seems to be the (only) way to get Whatsapp on the linux-laptop
You have obviously missed the https://web.whatsapp.com/ option. This works the same as any of those supposed applications which are a wrapper for the web app instead of using it directly in the web browser.
Strange that clean/autoclean aren't in the man pages for apt.
It appears they are only mentioned with a reference to read apt-get man page.
edit-sources (work-in-progress)
edit-sources lets you edit your sources.list(5) files in your
preferred text editor while also providing basic sanity checks.
showsrc, depends, rdepends, policy (summarised in apt-cache(8))
source, build-dep, download, changelog, clean, distclean, autoclean
(summarised in apt-get(8))
Edit: that would be in excalibur it is not in a previous version of apt on a bookworm based install.
7. sudo apt upgrade
That should be sudo apt full-upgrade or the older now depreciated sudo apt dist-upgrade to use the command to upgrade a distribution properly to the next one coming.
You are welcome good to see you got it sorted.
I have both and it works fine.
root@9600k:~# ll /bin/xdotool
84 -rwxr-xr-x 1 root root 85376 Apr 6 12:26 /bin/xdotool*
root@9600k:~# ll /usr/bin/xdotool
84 -rwxr-xr-x 1 root root 85376 Apr 6 12:26 /usr/bin/xdotool*
That said it appears only the /usr/bin/xdotool is listed in the package.
root@9600k:~# dpkg -L xdotool
/.
/usr
/usr/bin
/usr/bin/xdotool
/usr/share
/usr/share/doc
/usr/share/doc/xdotool
/usr/share/doc/xdotool/README
/usr/share/doc/xdotool/changelog.Debian.gz
/usr/share/doc/xdotool/changelog.gz
/usr/share/doc/xdotool/copyright
/usr/share/doc/xdotool/examples
/usr/share/doc/xdotool/examples/ffsp.sh
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/xdotool.1.gz
So I would use rm /bin/xdotool as root and see if it will complete once you use the /usr/lib/usrmerge/convert-usrmerge as it suggests after removing the file it complains about.
Once done do the apt autoremove to get rid of the usrmerge it is not needed once done.
root@9600k:~# apt policy usrmerge
usrmerge:
Installed: (none)
Candidate: 39+nmu2
Version table:
39+nmu2 950
950 http://de.deb.devuan.org/merged excalibur/main amd64 Packages
600 http://de.deb.devuan.org/merged unstable/main amd64 Packages
Edit: Though now reading it again and checking it appears it completed almost three years ago for me and the /bin is now the symbolic link it is supposed to be, never seen that problem in my install notes when I check those.
root@9600k:~# ll /
total 2097236
0 lrwxrwxrwx 1 root root 7 Aug 28 2022 bin -> usr/bin/
snip....
Does this mean that the apache2 service will reload (not restart) twice a day (*/12)? It's not scary, but it's not necessary. IMHO.
If you tell the job to do it that is what it will do. I for one fail to see why you would be trying to renew a certification twice a day as it is. I would think a monthly job at the most would be the idea or depending on the length of the certificate a yearly job would most likely be the best. This twice a day foolishness in the comments make very little sense if their process is that useless it is needed I would not be trusting them for anything as critical as security of my website. You could do a separate script for the apache2 reload that wold test something like the date on certificate then it will only reload if it has changed.
but I usually use galculator for years now, very small and fast and does what I need.
I use this in my .bash_functions file works well
# https://github.com/addyosmani/dotfiles/blob/master/.functions#L1-L17
# Simple calculator
function calc() {
local result=""
result="$(printf "scale=10;$*\n" | bc --mathlib | tr -d '\\\n')"
# └─ default (when `--mathlib` is used) is 20
#
if [[ "$result" == *.* ]]; then
# improve the output for decimal numbers
printf "$result" |
sed -e 's/^\./0./' `# add "0" for cases like ".5"` \
-e 's/^-\./-0./' `# add "0" for cases like "-.5"`\
-e 's/0*$//;s/\.$//' # remove trailing zeros
else
printf "$result"
fi
printf "\n"
}
It is not too happy with negative results but I will live with it.
zeus@9600k:~$ calc 2^4
16
zeus@9600k:~$ calc 2*4
8
zeus@9600k:~$ calc 2/4
0.5
zeus@9600k:~$ calc 2-4
bash: printf: -2: invalid option
printf: usage: printf [-v var] format [arguments]
zeus@9600k:~$ calc 2+4
6
At what point would I need a "clipboard manager"?
When you want to access previous items that have been in the clipboard using a history function to not be limited to the last entry in the paste buffer or as some of them offer it have preexisting entries that will paste when wanted as they are selected for use. I will add my vote for CopyQ a lovely program that works without problems for me for many years now.
Should i add --post-hook "service apache2 reload" to
I would give.
0 */12 * * * root test -x /usr/bin/certbot -a \! -d /run/systemd/system && perl -e 'sleep int(rand(43200))' && certbot -q renew && service apache2 reload
A try using the same idea it does after the certbot renews the certificate perhaps even /etc/init.d/ apache2 reload as the command to ensure no stupid path problems as happens with cron as it does not have the same path as the user does when it tries to execute commands. I always do this with my entries to ensure it has no choice but to do what I tell it to do. For example my root crontab.
root@9600k:~# crontab -l
# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
snip....
# m h dom mon dow command
## Run my rsync snapshot script at fifteen minutes after it every four hours.
15 */4 * * * /root/bin/snapshot_root.sh > /dev/null 2>&1
## Run trim on my SSD drives every Saturday at 5am borrowed idea from MX Linux.
0 05 * * sat /root/bin/fstrim-MX.sh > /dev/null 2>&1
should certbot deb package from Debian be patched for Devuan?
No it tells you that changes are needed if running systemd which Devuan does not do so it is proper as it is. The line in the package is correct, the line you suggest to use is the one that is wrongly formatted with the 0,12 shown by you.
Your cron entry misses the user field.
Also has error with the 0,12 instead of the properly shown 0/12 for every twelve hours in the example above it for the hour to run field.
* unless there has been some error in the processing / sanitising for use in Devuan for which a bug report should be filed with the Devuan maintainers.
No nothing with the systemd gets installed when getting the package on your machine. Who knows afterwards I have nothing to test it with.
root@9600k:~# apt install open-iscsi
Installing:
open-iscsi
Installing dependencies:
libisns0t64 libopeniscsiusr
Summary:
Upgrading: 0, Installing: 3, Removing: 0, Not Upgrading: 3
Download size: 475 kB
Space needed: 2,183 kB / 17.9 GB available
Continue? [Y/n] y
Get:1 http://ca.deb.devuan.org/merged excalibur/main amd64 libopeniscsiusr amd64 2.1.11-1 [61.1 kB]
Get:2 http://ca.deb.devuan.org/merged excalibur/main amd64 libisns0t64 amd64 0.101-1+b1 [93.5 kB]
Get:3 http://ca.deb.devuan.org/merged excalibur/main amd64 open-iscsi amd64 2.1.11-1 [320 kB]
Fetched 475 kB in 5s (88.6 kB/s)
Preconfiguring packages ...
Selecting previously unselected package libopeniscsiusr.
(Reading database ... 192304 files and directories currently installed.)
Preparing to unpack .../libopeniscsiusr_2.1.11-1_amd64.deb ...
Unpacking libopeniscsiusr (2.1.11-1) ...
Selecting previously unselected package libisns0t64:amd64.
Preparing to unpack .../libisns0t64_0.101-1+b1_amd64.deb ...
Unpacking libisns0t64:amd64 (0.101-1+b1) ...
Selecting previously unselected package open-iscsi.
Preparing to unpack .../open-iscsi_2.1.11-1_amd64.deb ...
Unpacking open-iscsi (2.1.11-1) ...
Setting up libisns0t64:amd64 (0.101-1+b1) ...
Setting up libopeniscsiusr (2.1.11-1) ...
Setting up open-iscsi (2.1.11-1) ...
Processing triggers for libc-bin (2.41-7) ...
Processing triggers for man-db (2.13.0-1) ...
Processing triggers for initramfs-tools (0.147) ...
update-initramfs: Generating /boot/initrd.img-6.12.22-amd64