You are not logged in.
- Topics: Active | Unanswered
#126 Devuan Derivatives » Refracta - HDD space required? » 2022-10-15 14:56:41
- pcalvert
- Replies: 2
I was wondering how much disk space is needed for Refracta. I have an old laptop HDD in an external case that I was thinking of using for a test installation. I believe that there is a 7.5 GB, Windows 2000 partition on that HDD that I could sacrifice for the test installation. Would that be big enough? I'm not planning to install any software, just some firmware packages.
Also, I noticed that the forum link on the Refracta website appears to be dead. It should probably be replaced with this link.
#127 Re: Other Issues » Broken after dist-upgrade Daedalus » 2022-10-14 19:26:25
Monitoring this forum may be helpful for Ceres users:
Siduction Forum » Upgrade Warnings (DE / EN)
https://forum.siduction.org/index.php?board=22.0
Of course, that's more applicable to Debian than Devuan, but monitoring that forum is likely be at least somewhat helpful for Ceres users.
#128 Re: Devuan » Devuan kFreeBSD » 2022-10-14 18:58:54
I believe that the Hyperbola Project working on something similar. Maybe giving them a hand would be the way to go.
#129 Hardware & System Configuration » ACPI 2.0 question » 2022-10-12 20:50:00
- pcalvert
- Replies: 3
I have a desktop computer with an Intel-based ASUS motherboard from 2009 that has the old-style BIOS. I was recently looking through the settings and noticed that ACPI 2.0 is disabled by default. Should I enable it or leave it the way it is? The computer shuts down, hibernates, and suspends normally, so I am inclined to leave it the way it is, but if there is a good reason to enable it, I will.
#130 Re: Hardware & System Configuration » [SOLVED] TP-Link AX3000 (Archer TX3000E) PCIe WiFi card not working on Refracta » 2022-10-12 20:41:14
Thank you everyone for your replies. Hopefully, installing Chimaera will solve this problem. If not, I am willing to go as far as installing Daedalus or Ceres.
#131 Re: Hardware & System Configuration » [SOLVED] TP-Link AX3000 (Archer TX3000E) PCIe WiFi card not working on Refracta » 2022-10-10 18:30:10
Hi Marjorie,
Thank you for your replies. I tried this workaround (hack) and had partial success:
https://notes.prkr.ca/2021/10/Intel-AX2 … Mint-20-2/
I found that here:
https://forums.linuxmint.com/viewtopic.php?p=2092127
After renaming the PNVM file and rebooting, there was no change. However, I then decided to run update-initramfs and reboot again. After doing so, I could see two local network devices -- the router and a wireless printer. Unfortunately, attempting to connect to the router was unsuccessful.
I will probably not spend much more time on this since I've been planning to install Chimaera. I would already be running it except for the fact that something urgent recently got in the way.
#132 Hardware & System Configuration » [SOLVED] TP-Link AX3000 (Archer TX3000E) PCIe WiFi card not working on Refracta » 2022-10-10 02:51:02
- pcalvert
- Replies: 7
I recently purchased a "TP-Link WiFi 6 AX3000 PCIe WiFi Card (Archer TX3000E)" from Amazon and installed it in my desktop computer. My current OS is Beowulf-based Refracta. I installed firmware-iwlwifi from Beowulf (Buster) backports, but the card does not appear to be working.
Here is some (hopefully) relevant information:
$ uname -a
Linux refracta 5.10.0-0.deb10.16-amd64 #1 SMP Debian 5.10.127-2~bpo10+1 (2022-07-28) x86_64 GNU/Linux$ lspci -knn |grep -i -A5 network
01:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a)
Subsystem: Intel Corporation Device [8086:0020]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00$ dmesg |grep iwlwifi
[ 15.257720] iwlwifi 0000:01:00.0: firmware: direct-loading firmware iwlwifi-ty-a0-gf-a0-59.ucode
[ 15.257752] iwlwifi 0000:01:00.0: api flags index 2 larger than supported by driver
[ 15.257820] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28
[ 15.259105] iwlwifi 0000:01:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm
[ 15.259172] iwlwifi 0000:01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 17.521002] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[ 17.703923] iwlwifi 0000:01:00.0: firmware: direct-loading firmware iwlwifi-ty-a0-gf-a0.pnvm
[ 17.703950] iwlwifi 0000:01:00.0: loaded PNVM version 0x324cd670
[ 17.953703] iwlwifi 0000:01:00.0: Timeout waiting for PNVM load!
[ 17.953751] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
[ 17.953785] iwlwifi 0000:01:00.0: iwl_trans_send_cmd bad state = 0
[ 17.965793] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
[ 17.977709] iwlwifi 0000:01:00.0: retry init count 0
[ 17.978211] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[ 18.401722] iwlwifi 0000:01:00.0: Timeout waiting for PNVM load!
[ 18.401768] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
[ 18.401802] iwlwifi 0000:01:00.0: iwl_trans_send_cmd bad state = 0
[ 18.413819] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
[ 18.425759] iwlwifi 0000:01:00.0: retry init count 1
[ 18.426235] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[ 18.849710] iwlwifi 0000:01:00.0: Timeout waiting for PNVM load!
[ 18.849792] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
[ 18.849854] iwlwifi 0000:01:00.0: iwl_trans_send_cmd bad state = 0
[ 18.862103] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
[ 18.874390] iwlwifi 0000:01:00.0: retry init count 2# grep -i fail kern.log
Oct 8 21:59:29 refracta kernel: [ 0.531173] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 8 21:59:29 refracta kernel: [ 11.848003] platform regulatory.0: firmware: failed to load regulatory.db (-2)
Oct 8 21:59:29 refracta kernel: [ 11.848129] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Oct 8 21:59:29 refracta kernel: [ 11.848139] cfg80211: failed to load regulatory.db
Oct 8 21:59:29 refracta kernel: [ 13.012137] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-59.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.012190] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-59.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.012228] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-58.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.012275] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-58.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.012297] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-57.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.012344] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-57.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.012365] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-56.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.012410] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-56.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.012432] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-55.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.012477] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-55.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.012498] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-54.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.012561] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-54.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.012582] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-53.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.012676] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-53.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.012700] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-52.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.012780] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-52.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.012799] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-51.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.012878] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-51.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.012899] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-50.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.012977] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-50.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.012998] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-49.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.013077] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-49.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.013098] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-48.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.013177] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-48.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.013198] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-47.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.013276] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-47.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.013304] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-46.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.013389] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-46.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.013412] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-45.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.013490] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-45.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.013510] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-44.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.013589] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-44.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.013609] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-43.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.013688] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-43.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.013744] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-42.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.013823] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-42.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.013844] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-41.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.013922] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-41.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.013943] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-40.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.014030] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-40.ucode failed with error -2
Oct 8 21:59:29 refracta kernel: [ 13.014053] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-39.ucode (-2)
Oct 8 21:59:29 refracta kernel: [ 13.014147] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-39.ucode failed with error -2
Oct 8 21:59:43 refracta kernel: [ 74.316064] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Oct 8 22:05:24 refracta kernel: [ 0.530090] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 8 22:05:24 refracta kernel: [ 11.490114] platform regulatory.0: firmware: failed to load regulatory.db (-2)
Oct 8 22:05:24 refracta kernel: [ 11.490224] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Oct 8 22:05:24 refracta kernel: [ 11.490231] cfg80211: failed to load regulatory.db
Oct 8 22:05:24 refracta kernel: [ 14.150194] iwlwifi 0000:01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
Oct 8 22:05:24 refracta kernel: [ 16.809751] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 8 22:05:24 refracta kernel: [ 16.821800] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 8 22:05:24 refracta kernel: [ 17.261819] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 8 22:05:24 refracta kernel: [ 17.273814] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 8 22:05:24 refracta kernel: [ 17.709819] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 8 22:05:24 refracta kernel: [ 17.721843] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 8 22:05:37 refracta kernel: [ 39.785007] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Oct 9 13:07:32 refracta kernel: [ 0.528058] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 9 13:07:32 refracta kernel: [ 12.211680] platform regulatory.0: firmware: failed to load regulatory.db (-2)
Oct 9 13:07:32 refracta kernel: [ 12.211782] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Oct 9 13:07:32 refracta kernel: [ 12.211791] cfg80211: failed to load regulatory.db
Oct 9 13:07:32 refracta kernel: [ 14.805559] iwlwifi 0000:01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
Oct 9 13:07:32 refracta kernel: [ 17.457229] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 9 13:07:32 refracta kernel: [ 17.469243] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 9 13:07:32 refracta kernel: [ 17.905242] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 9 13:07:32 refracta kernel: [ 17.917262] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 9 13:07:32 refracta kernel: [ 18.353220] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 9 13:07:32 refracta kernel: [ 18.365234] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 9 13:07:46 refracta kernel: [ 40.665598] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Oct 9 13:15:53 refracta kernel: [ 0.531163] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 9 13:15:53 refracta kernel: [ 42.062592] platform regulatory.0: firmware: failed to load regulatory.db (-2)
Oct 9 13:15:53 refracta kernel: [ 42.062713] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Oct 9 13:15:53 refracta kernel: [ 42.062722] cfg80211: failed to load regulatory.db
Oct 9 13:15:53 refracta kernel: [ 44.950297] iwlwifi 0000:01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
Oct 9 13:15:53 refracta kernel: [ 47.621714] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 9 13:15:53 refracta kernel: [ 47.634009] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 9 13:15:53 refracta kernel: [ 48.069733] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 9 13:15:53 refracta kernel: [ 48.081711] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 9 13:15:53 refracta kernel: [ 48.521752] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 9 13:15:53 refracta kernel: [ 48.533731] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 9 13:16:07 refracta kernel: [ 70.568770] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Oct 9 15:31:02 refracta kernel: [ 0.528841] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 9 15:31:02 refracta kernel: [ 12.646318] platform regulatory.0: firmware: failed to load regulatory.db (-2)
Oct 9 15:31:02 refracta kernel: [ 12.646430] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Oct 9 15:31:02 refracta kernel: [ 12.646437] cfg80211: failed to load regulatory.db
Oct 9 15:31:02 refracta kernel: [ 15.259172] iwlwifi 0000:01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
Oct 9 15:31:02 refracta kernel: [ 17.953751] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 9 15:31:02 refracta kernel: [ 17.965793] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 9 15:31:02 refracta kernel: [ 18.401768] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 9 15:31:02 refracta kernel: [ 18.413819] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 9 15:31:02 refracta kernel: [ 18.849792] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct 9 15:31:02 refracta kernel: [ 18.862103] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct 9 15:31:15 refracta kernel: [ 40.319270] vboxdrv: module verification failed: signature and/or required key missing - tainting kernelAny thoughts or ideas on what the problem is or might be?
#133 Re: Off-topic » Executables in home directory » 2022-07-17 15:15:44
Hi Chris,
Thank you for your suggestions. My plan is to move those directories immediately after installation, while the system is offline, so the risk of malware ever being able to write to those directories should be very, very small.
#134 Off-topic » Executables in home directory » 2022-07-16 11:02:40
- pcalvert
- Replies: 2
I was just digging around in my home directory and noticed that some software puts executable files in there, which is something that I'm not a fan of. I like to put home on a separate partition that is marked "nosuid, noexec" in the fstab file. Obviously, this will cause problems for executable files that are in my home directory.
So far, these are the places where I've found executable files:
~/bin
~/.local/bin
~/.wineDoes anyone know if there are any others? My original plan was to move these to a directory on the root (system) partition and replace the originals with symbolic links. I'll probably do that if I can depend on executable files to only be present in a few, predictable locations in my home directory.
By the way, the reason for doing this is that I have a personal security policy, and part of that policy is that "threat gate" applications like web browsers, email clients, etc., should not have write access to any file system where files can be executed. That way, if any malicious code (e.g., a malware "dropper") is written to disk, that code will not be allowed to execute.
#135 Re: Other Issues » Chimaera and VirtualBox after kernel update » 2022-07-16 03:54:41
PS: One tips, reboot on oldier kernel…
(if available)
This works. I had the same problem on Beowulf because I use a kernel from backports. After spending a lot of time trying to repair Windows 8.1, I began to suspect that the problem is not in the guest but on the host. I decided to try rebooting with the previous kernel, and when I did the problem was gone.
#136 Re: Devuan Derivatives » Lion Linux » 2022-07-05 06:23:48
I don't really understand the essence of this distribution. After all, you can always install a minimal system and then install what you need.
Although that is technically true, many people are not willing or able to do that. They may lack the necessary experience required, or they may be lazy, impatient, etc.
#137 Re: Installation » [SOLVED] Anacron symlinked to "true", again. » 2022-06-28 23:04:58
I could put the fix in a postinstall script in the next version, but I think the user should be warned and asked to OK it.
I don't think that's really necessary. On a live system it doesn't make sense to have anacron running. However, once the system has been installed, having anacron running is the normal and expected behavior. IMO, asking the user to OK the fix is asking for trouble since some users will likely be confused by this.
#138 Off-topic » Linux Hardening Guide » 2022-06-12 13:36:11
- pcalvert
- Replies: 2
I recently started looking for guides on how to harden GNU/Linux systems. This is the best one that I've found so far:
#139 Re: Installation » [SOLVED] UFW causes errors under Chimaera » 2022-05-27 01:56:43
I recommend giving FireHOL a try. It uses a simple, human-readable configuration file.
Package name: firehol
More info:
https://firehol.org/
https://packages.debian.org/stable/firehol
For most desktop and laptop computers, the default configuration should be sufficient. For a server you would need to configure the firewall according to the services that are running on it.
#140 Re: Installation » Why is only main repo is active in sources.list? » 2022-05-05 07:26:04
non-free: propriatary stuff - you want to enable this when you need firmware for your hardware to work
Most people probably will need to enable non-free in order to install one of these packages:
amd64-microcode
intel-microcode
#141 Re: Hardware & System Configuration » Important - log4j exploit alarm affecting Linux » 2022-03-18 16:18:14
I have LibreOffice installed and a search for "log4j" found nothing. However, I am selective about what I install and don't allow software to install recommended packages by default. It looks like I installed LibreOffice Writer and then later installed LibreOffice Math. Those are the only parts of LibreOffice that I installed because I really don't have a need for the rest of it. Because of LibreOffice's bloat, I've long preferred to use AbiWord and Gnumeric instead.
My result:
$ apt list | grep installed | grep java
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
javascript-common/oldstable,now 11 all [installed,automatic]
libjavascriptcoregtk-4.0-18/oldstable-security,now 2.34.6-1~deb10u1 amd64 [installed,automatic]Here's another option worth considering:
https://portableapps.com/apps/office/li … legacy-5.4
I sometimes use that in a Windows XP VM.
#142 Re: Other Issues » [SOLVED] Beowulf kernel upgrade oddity » 2022-03-08 19:03:24
@OP: can we see the full output of
# apt update
From yesterday (I still had the terminal window open):
# apt update
Hit:1 http://iweb.dl.sourceforge.net/project/ubuntuzilla/mozilla/apt all InRelease
Hit:2 http://deb.devuan.org/merged beowulf InRelease
Hit:3 http://deb.devuan.org/merged beowulf-updates InRelease
Get:4 http://deb.devuan.org/merged beowulf-security InRelease [26.5 kB]
Hit:5 http://deb.devuan.org/merged beowulf-backports InRelease
Fetched 26.5 kB in 4s (7,067 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.From just a few minutes ago:
# apt update
Hit:1 http://versaweb.dl.sourceforge.net/project/ubuntuzilla/mozilla/apt all InRelease
Get:2 http://deb.devuan.org/merged beowulf InRelease [33.8 kB]
Get:3 http://deb.devuan.org/merged beowulf-updates InRelease [26.7 kB]
Get:4 http://deb.devuan.org/merged beowulf-security InRelease [26.5 kB]
Get:5 http://deb.devuan.org/merged beowulf-backports InRelease [26.9 kB]
Get:6 http://deb.devuan.org/merged beowulf-backports/main amd64 Packages [491 kB]
Fetched 605 kB in 4s (151 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.# apt list --upgradable
Listing... Done
linux-headers-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64 [upgradable from: 5.10.70-1~bpo10+1]
linux-image-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64 [upgradable from: 5.10.70-1~bpo10+1]So, the upgrade was NOT available yesterday, but now it is.
#143 Other Issues » [SOLVED] Beowulf kernel upgrade oddity » 2022-03-08 01:49:44
- pcalvert
- Replies: 4
I am using a kernel from backports on Beowulf and just noticed something strange.
$ apt policy linux-image-amd64
linux-image-amd64:
Installed: 5.10.70-1~bpo10+1
Candidate: 5.10.70-1~bpo10+1
Version table:
*** 5.10.70-1~bpo10+1 100
100 http://deb.devuan.org/merged beowulf-backports/main amd64 Packages
100 /var/lib/dpkg/status
4.19+105+deb10u13 500
500 http://deb.devuan.org/merged beowulf/main amd64 Packages
4.19+105+deb10u9 500
500 http://deb.devuan.org/merged beowulf-security/main amd64 PackagesSearching my apt package cache shows that the latest kernel I have is dated 30-October-2021:
$ ls -l /var/cache/apt/archives |grep linux-image-
-rw-r--r-- 1 root root 48399932 Jul 19 2021 linux-image-4.19.0-17-amd64_4.19.194-3_amd64.deb
-rw-r--r-- 1 root root 53423672 Aug 19 2021 linux-image-5.10.0-0.bpo.8-amd64_5.10.46-4~bpo10+1_amd64.deb
-rw-r--r-- 1 root root 53505900 Oct 30 16:58 linux-image-5.10.0-0.bpo.9-amd64_5.10.70-1~bpo10+1_amd64.deb
-rw-r--r-- 1 root root 1504 Aug 19 2021 linux-image-amd64_5.10.46-4~bpo10+1_amd64.debA little research shows that the version I have is the latest version available for download:
Package: linux-image-5.10.0-0.bpo.9-amd64 (5.10.70-1~bpo10+1)
https://packages.debian.org/buster-back … po.9-amd64
However, if you click on the Debian Changelog link on the right-hand side of that page, you'll see this at the top of the page:
linux-signed-amd64 (5.10.92+1~bpo10+1) buster-backports; urgency=medium
* Sign kernel from linux 5.10.92-1~bpo10+1
* Rebuild for buster-backports:
- Change ABI number to 0.bpo.11
-- Ben Hutchings <benh@debian.org> Thu, 03 Feb 2022 19:49:50 +0100February 3, 2022 was over a month ago. What's going on?
#144 Re: Hardware & System Configuration » Severe damage to ext4 filesystem - advice needed » 2022-02-13 15:00:10
This is the approach that I use:
df -hThat shows me my mounted drives. If I see (for example) that /dev/sdb is my "highest" drive, then I'll guess that the USB stick will be /dev/sdc.
Although my guess has usually been correct, I always verify it like this:
# fdisk -l /dev/sdcI then look at the output of fdisk to see if the size of /dev/sdc (and other drive info) matches what I expect. It usually does, but if were to ever see something I wasn't expecting, then I would know to be extra careful before proceeding.
#145 Re: Installation » How to have updated firefox-esr in Chimaera? » 2022-01-06 17:19:23
Yeah, it really is impossible to tell what Chrome is doing. It even adds Google's repositories in an install script, which freaks me out.
Speaking of Google Chrome, I just saw this article today:
Google makes the perfect case for why you shouldn't use Chrome
#146 Re: Installation » How to have updated firefox-esr in Chimaera? » 2021-12-29 15:13:53
But hey, the big G offers a Chrome .deb that should be compatible with Devuan. The telemetry for that makes FF looks like a paragon of privacy but you know that, right?
If I used it at all, I would only use Google Chrome in a VM. I installed it once on my main system, and noticed some odd behavior after doing so. It might have been a coincidence, but the strange behavior went away after I became suspicious and uninstalled Google Chrome, so I am inclined to believe that Google Chrome was somehow responsible.
#147 Re: Installation » how to clone a partition with os installed? » 2021-12-24 15:12:06
I would boot from a live CD/DVD/USB system and use partclone to clone the partitions. I would use Refracta or the Devuan live DVD and install partclone using apt. Alternatively, you could use the GParted live CD, which comes with partclone. However, the GParted live CD seems a little rough around the edges, and is based on Debian Sid, so I'd recommend that you not use it.
Download links for Devuan:
https://www.devuan.org/get-devuan
Download links for Refracta:
https://get.refracta.org/
Info about the GParted live CD:
https://gparted.org/livecd.php
Download links for the GParted live CD:
https://sourceforge.net/projects/gparte … ve-stable/
#148 Re: Devuan Derivatives » Refracta 11 (Chimaera) isos » 2021-12-11 14:15:13
That worked. Thanks for the prompt reply!
#149 Re: Devuan Derivatives » Refracta 11 (Chimaera) isos » 2021-12-11 12:52:01
Unless I did something wrong, it looks like your key has expired.
$ gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt
gpg: Signature made Tue 16 Nov 2021 09:35:28 AM EST
gpg: using RSA key 67F5013216271E85C251E480A73823D3094C5620
gpg: Good signature from "fsmithred (aka fsr) <fsmithred@g***l.com>" [expired]
gpg: Note: This key has expired!
Primary key fingerprint: 67F5 0132 1627 1E85 C251 E480 A738 23D3 094C 5620#150 Re: Hardware & System Configuration » Attention Dual/Multi-booters: Latest GRUB (2.06-2) disables os-prober » 2021-12-01 23:28:52
https://www.gnu.org/software/grub/manua … figuration
It is disabled by default since automatic and silent execution of os-prober, and creating boot entries based on that data, is a potential attack vector.
It seems to me that there's a simple solution that will solve this problem -- ask the user to confirm that the information obtained from os-prober is correct. Or write the info to the appropriate config file, but commented out, along with a comment above it explaining why it's commented out and the importance of verifying that the information is correct before uncommenting it.
Board footer
