You are not logged in.
yeti wrote:So porting a De??an sibling to e.g. the NetBSD kernel, just would revive the old dreams.
—▷ https://www.debian.org/ports/netbsd/index
—▷ https://www.debian.org/ports/netbsd/alphaBesides those links show they have abandoned all such efforts in porting bsd's so the point is rather moot. Hypothetically, if a team of talented devs were to undertake such an endeavor then this might not be a moot point.
This one is not dead yet:
https://www.debian.org/ports/kfreebsd-gnu/
Check the mailing list archive and you'll see that the mailing list is still active.
Phil
I am using NoScript (v. 5.1.9) on Palemoon. Palemoon tries to dissuade people from installing NoScript, but you can safely ignore the warning and install it anyway. NoScript seems to work just fine on Palemoon.
Phil
I realize this is a bizarre topic. Bear with me.
It's not bizarre at all. I think it's a good idea. I had the same idea about two years ago when I was learning how to set up a Debian server.
Phil
Voidlinux looks nice. Unluckily only a rolling release. If enough migrants from De??an gather around it, making a spinoff in a stable+security flavor could be a plan-b too.
This looks quite interesting:
https://www.hyperbola.info/
https://wiki.hyperbola.info/doku.php?id=:en:start
https://distrowatch.com/table.php?distr … =hyperbola
I learned about it yesterday.
Phil
I'm not seeing any updates at all. The last update I saw was tcpdump on Monday.
SeaMonkey does not support Encrypted Media Extensions and therefore cannot load the Widevine Content Decryption Module.
It doesn't matter because the OP didn't mention that as a requirement; he or she requires support for the old type of Firefox extensions. If someone also wants support for Widevine, then I recommend using Chromium, or a web browser based on Chromium such as Google Chrome, Opera, Vivaldi, etc. After all, there's nothing stopping anyone from having more than one web browser.
Phil
It really isn't safe to use older browser versions. Have you considered using browsers that support legacy extensions and are still maintained with security and bug fixes? There's Pale Moon, Basilisk, and Iceweasel-UXP to choose from (and the upcoming Borealis Navigator). There are still choices out there.
While it can't be said that all legacy extensions will work on them, the vast majority will.
There's also SeaMonkey, and there's a deb package available for it from MX Linux.
For info on using the MX Linux repo with Devuan, see:
https://dev1galaxy.org/viewtopic.php?pid=17503#p17503
Phil
For comparison sake, and to give you some additional information, I am using Devuan ASCII and didn't have any problems installing WINE when I followed the Debian wiki. I also don't have any elogind packages installed. And now your experience has me wondering if there's been a big change between ASCII and Beowulf.
Phil
Be sure to study the wiki:
https://wiki.debian.org/Wine
Phil
(... I suppose you are using latest firmware...)
That is correct.
Phil
So, a customer of ours is insisting on RHEL7 (don't know why but I suspect those that make such decisions are not very technically savvy).
I think you should ask them why they want RHEL7. And perhaps you could try to explain to them why it may not be the best choice for an embedded system.
Phil
Here's mine:
# grep -R . /sys/devices/system/cpu/vulnerabilities
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic retpoline, STIBP: disabled, RSB filling
/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable
/sys/devices/system/cpu/vulnerabilities/mds:Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
/sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion; VMX: EPT disabled
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTIDoesn't look good. ![]()
Phil
@pcalvert, why pin the rest of the repository to 50?
Because aptitude was trying to pull other packages (e.g., intel-microcode) from that repo during upgrades, and pinning the rest of the repository to 50 stopped that behavior. Pinning it to 100 didn't work. I thought it would, but it didn't.
Also, their Flash package downloads updated Flash versions without needing to be updated itself so using the .deb might be the best option.
I'm not sure what you mean by that.
Phil
I use an MX repo for one package by using apt-pinning.
/etc/apt/preferences.d/mxrepo-pinning :
Package: adobe-flashplugin
Pin: origin "mxrepo.com"
Pin-Priority: 100
Package: *
Pin: origin "mxrepo.com"
Pin-Priority: 50/etc/apt/sources.list.d/mx-17.list :
# MX Community Main and Test Repos
deb http://mxrepo.com/mx/repo/ stretch non-free main
#deb http://mxrepo.com/mx/testrepo/ stretch testDownload the repo keyring and install it:
wget http://mxrepo.com/mx/repo/pool/main/m/mx-archive-keyring/mx-archive-keyring_2018.2mx17_all.deb
sudo dpkg -i mx-archive-keyring_2018.2mx17_all.debPhil
My results:
$ apt policy firefox-esr
firefox-esr:
Installed: 60.7.2esr-1~deb9u1
Candidate: 60.7.2esr-1~deb9u1
Version table:
*** 60.7.2esr-1~deb9u1 500
500 http://deb.devuan.org/merged ascii-security/main i386 Packages
100 /var/lib/dpkg/status
60.6.3esr-1~deb9u1 500
500 http://deb.devuan.org/merged ascii-updates/main i386 Packages
60.6.1esr-1~deb9u1 500
500 http://deb.devuan.org/merged ascii/main i386 PackagesDebian Stretch version: 60.8.0esr-1~deb9u1
Phil
Update: The problem seems to have been fixed.
$ apt policy firefox-esr
firefox-esr:
Installed: 60.7.1esr-1~deb9u1
Candidate: 60.7.1esr-1~deb9u1
Version table:
*** 60.7.1esr-1~deb9u1 500
500 http://deb.devuan.org/merged ascii-security/main i386 Packages
100 /var/lib/dpkg/status
60.6.3esr-1~deb9u1 500
500 http://deb.devuan.org/merged ascii-updates/main i386 Packages
60.6.1esr-1~deb9u1 500
500 http://deb.devuan.org/merged ascii/main i386 PackagesPhil
This info may help:
SSD’s, Journaling, and noatime/relatime
https://tytso.livejournal.com/61830.html
Improving the Resilience of HDDs & Ext4
https://myles.sh/improving-the-resilience-of-your-hdds/
[Especially the section on tuning ext4.]
Phil
Try using aptitude. It may give you some other options, some of which may allow you to get rid of pulseaudio and pulseaudio-utils.
Phil
I downloaded the Firefox ESR package from here:
https://packages.debian.org/stretch/firefox-esr
Then I installed it using gdebi.
Result:
$ apt policy firefox-esr
firefox-esr:
Installed: 60.7.1esr-1~deb9u1
Candidate: 60.7.1esr-1~deb9u1
Version table:
*** 60.7.1esr-1~deb9u1 100
100 /var/lib/dpkg/status
60.7.0esr-1~deb9u1 500
500 http://deb.devuan.org/merged ascii-security/main i386 Packages
60.6.3esr-1~deb9u1 500
500 http://deb.devuan.org/merged ascii-updates/main i386 Packages
60.6.1esr-1~deb9u1 500
500 http://deb.devuan.org/merged ascii/main i386 PackagesPhil
Here's my result:
$ date && apt policy thunderbird
Sun Jun 16 12:56:56 EDT 2019
thunderbird:
Installed: 1:60.7.0-1~deb9u1
Candidate: 1:60.7.0-1~deb9u1
Version table:
2:52.9.1-2~mx17+2 50
50 http://mxrepo.com/mx/repo stretch/main i386 Packages
*** 1:60.7.0-1~deb9u1 500
500 http://deb.devuan.org/merged ascii-security/main i386 Packages
100 /var/lib/dpkg/status
1:60.6.1-1~deb9u1 500
500 http://deb.devuan.org/merged ascii/main i386 PackagesHere's some more data:
$ apt policy intel-microcode:amd64
intel-microcode:amd64:
Installed: (none)
Candidate: 3.20190514.1~deb9u1
Version table:
3.20190514.1~deb9u1 500
500 http://deb.devuan.org/merged ascii-security/non-free amd64 Packages
3.20180807a.2~deb9u1 500
500 http://deb.devuan.org/merged ascii/non-free amd64 Packages$ apt policy intel-microcode
intel-microcode:
Installed: 3.20180807a.2~deb9u1
Candidate: 3.20180807a.2~deb9u1
Version table:
*** 3.20180807a.2~deb9u1 500
500 http://deb.devuan.org/merged ascii/non-free i386 Packages
100 /var/lib/dpkg/status
3.20180807a.1~deb9u1 500
500 http://deb.devuan.org/merged ascii-security/non-free i386 PackagesSo, the package for 64-bit systems is up to date, but the one for 32-bit systems is not. Although I am by no means an expert on Devuan, this seems to suggest that Amprolla is not working properly.
Phil
Here's another example:
- -------------------------------------------------------------------------
Debian Security Advisory DSA-4447-1 security@debian.org
https://www.debian.org/security/ Moritz Muehlenhoff
May 15, 2019 https://www.debian.org/security/faq
- -------------------------------------------------------------------------
Package : intel-microcode
CVE ID : CVE-2018-12126 CVE-2018-12127 CVE-2018-12130
CVE-2019-11091
This update ships updated CPU microcode for most types of Intel CPUs. It
provides mitigations for the MSBDS, MFBDS, MLPDS and MDSUM hardware
vulnerabilities.
To fully resolve these vulnerabilities it is also necessary to update
the Linux kernel packages as released in DSA 4444.
For the stable distribution (stretch), these problems have been fixed in
version 3.20190514.1~deb9u1.
We recommend that you upgrade your intel-microcode packages.
For the detailed security status of intel-microcode please refer to
its security tracker page at:
https://security-tracker.debian.org/tracker/intel-microcode
Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/More than 60 hours later and the update has not shown up yet:
$ apt policy intel-microcode
intel-microcode:
Installed: 3.20180807a.2~deb9u1
Candidate: 3.20180807a.2~deb9u1
Version table:
*** 3.20180807a.2~deb9u1 500
500 http://deb.devuan.org/merged ascii/non-free i386 Packages
100 /var/lib/dpkg/status
3.20180807a.1~deb9u1 500
500 http://deb.devuan.org/merged ascii-security/non-free i386 PackagesPhil
While I doubt Debian repositories work as intended on Devuan, let's say I want to install Lutris. The most common way to do that under Debian is to add a repo and then update and install. Could I add that Debian repo on Devuan?
Yes. The instructions for Debian found on this web page should also work for Devuan:
Phil
/etc/apt/preferences.d/mxrepo (or some other file name)
Package: * Pin: origin "mxrepo.com" Pin-Priority: 400I think that will work. The man page for apt_preferences says that origin can match a hostname. I don't know if you need to make a separate entry for la.mxrepo.com or if the one will get both.
It turned out that a pin priority of 400 is too high. Even 100 is too high. I lowered it to 50 and now it works; 99 probably would have also worked, but I didn't bother testing it since the problem was already solved.
EDIT:
I thought I had this working, but further testing (via routine usage of the system) proved me wrong. I believe I have it working now, though, using this configuration:
Package: adobe-flashplugin
Pin: origin "mxrepo.com"
Pin-Priority: 100
Package: *
Pin: origin "mxrepo.com"
Pin-Priority: 50Phil