You are not logged in.
I think the option should be applied as per dhclient.conf(5).
Disclaimer: I don't use dhclient.
Id prefer to hire White or Japanese Men as the programmers
not j3ws , blacks , Indians or Chinese
Burn in hell you fucking racist cunt.
Running this command at boot will disable the lid switch at the kernel level:
echo 'PNP0C0D:00' | sudo tee /sys/bus/acpi/drivers/button/unbind
The sysfsutils package provides /etc/sysfs.conf, which can be used to set values in /sys/.
However:
after closing and reopening the laptop lid the display settings are severely messed up
Did you try removing the xserver-xorg-video-intel package? It is said to be more buggy than the modesetting DDX driver which is used as a fallback in the absence of that package. The DDX driver draws the screen for most desktops so it's more likely to be the culprit than the i915 kernel driver (which is responsible for the direct hardware interface).
Only install the linux-image-amd64 package. It always depends on the latest version.
PlusNet must have removed the entry for deb.devuan.org in the last couple of weeks.
I'm with PlusNet:
alpine:~$ dig +short @192.168.0.1 deb.devuan.org
deb.rr.devuan.org.
5.9.122.185
125.228.189.120
185.183.113.131
185.178.192.43
46.4.50.2
160.16.137.156
195.85.215.180
185.38.15.81
158.69.153.121
89.174.102.150
141.84.43.19
131.188.12.211
130.225.254.116
185.203.114.135
95.216.15.86
200.236.31.1
alpine:~$is using a distro without systemd being targeted by GCHQ?
No.
alpine:~$ ls -l /sbin/init
lrwxrwxrwx 1 root root 12 Feb 13 10:10 /sbin/init -> /bin/busybox
alpine:~$I think dumping NetworkManager and using /etc/network/interfaces would make more sense on a Raspberry Pi. Or anything else for that matter.
Is there an estimate for when 5.13 kernel will be available in Devuan packages?
That kernel version will never be available for the current stable release. The kernel only gets backported security & bug fixes after the release, no (major) version bumps are provided.
Is wlan0 listed in /etc/network/interfaces? If so then NetworkManager will ignore it.
Invaluable resource for fans of the standard text editor.
archie:~$ echo $EDITOR
ed
archie:~$Oh yes.
Try
Package: pulseaudio:amd64
Pin: version *
Pin-Priority: -1
Package: pulseaudio:i386
Pin: version *
Pin-Priority: -1-10 is bloat — P < 0 is all that is required ![]()
EDIT: check with this after editing the preferences file:
# apt update
$ apt policyEDIT2: this stanza might work by itself (I can't check atm):
Package: pulseaudio:*
Pin: version *
Pin-Priority: -1EDIT3: confirmed, the above stanza is all that is needed to block all architectures of the package:
Pinned packages:
pulseaudio -> 14.2-2 with priority -1
pulseaudio:i386 -> 14.2-2 with priority -1Bump!
Do we have anything like pledge in Linux-land? Looks like a security must-have.
We do now:
Porting OpenBSD pledge() to Linux
Nice.
Is to common for a package to be in unstable and stable and not in testing ?
Yes. Packages with release critical (RC) bugs are automatically blocked from transition to testing.
This is a great relief to me. I've been worrying for a while now.
I was probably too harsh. Having a bad morning. Sorry all.
No firmware available for my wifi. A little annoying
What's annoying are entitled users attempting to use a distribution without even the vaguest understanding of how or why they work. Idiot.
Installer couldn't find it anywhere
AFAIUI the installer only scans the first device found, which is a bug. Otherwise see https://www.debian.org/releases/stable/ … 04.en.html
Running mount directly gives me uninterpretable errors (just "bad argument", I think) for all the relevant partitions.
The busybox shell's mount command requires the -t option. Paraphrasing error messages is also really fucking annoying btw.
install the firmware
Ah, so you finally did discover the documentation then? Why the fuck did you complain earlier then? Troll.
Rebooted. UEFI cannot find grub.
Again with the fucking paraphrasing. Twat.
it installed the kernel and initramfs file on the main partition rather than the EFI partition for inexplicable reasons
So you didn't configure the partitioning stage correctly then? Another PEBKAC...
Ran wpa_supplicant directly just as a program rather than service. It says it finds my card and everything is OK, but wifi scan cannot find any networks.
Sounds like it's missing the firmware. Anybody with half a brain would check dmesg & /lib/firmware/ but this person is special, apparently.
I installed some time ago Virtualbox on my Devuan Chimaera
How did you do that? VirtualBox is of insufficient quality to be included in the stable release.
Compare the outputs of these commands in the various systems:
lspci -knn | grep -A3 Network
ip linkThe first will show your card and drivers, the second will list all network interfaces. Post them all here (using code tags) if you can't make any sense of them.
Just find the file containing the repository:
grep -R 'download.opensuse.org' /etc/apt/sources.list{,.d/*}Then edit the file and remove the repository line. Or just delete the file if it only has one line.
No need to reinstall.
Eversion by Alastair Reynolds. An interesting story with some nice twists and a satisfying ending.
But this can be disabled?
The user can disable 3rd party certificates, yes. I've removed all manufacturer-supplied certificates from my machine and just use a single certificate I created.
Some devices (usually discrete GPUs) can require the official Microsoft certificate to be allowed for their pre-installed firmware but the hash can be read from the TPM chip and enrolled into the SecureBoot database. Or so I have read :-)
is the option in the bios to disable secure boot no longer available?
The seems to be present in the PDF to which I linked in the OP. So far.
ThinkPads preinstalled with Linux (or supplied without an operating system, as mine was) will already have 3rd party certificates enabled so I presume that would also be true for other Linux laptop vendors. Thankfully.
As of 2022 all new Lenovo machines require that the 3rd party UEFI SecureBoot certificate used by Linux distributions (including De{bi,vu}an) be authorised from the firmware ("BIOS") options. No Linux installer will boot on the machines until this is done.
Reference: https://download.lenovo.com/pccbbs/mobi … re_PCs.pdf
Looks like this is a requirement enforced by Microsoft and so might apply to all manufacturers. Nice.
But, what will happen to the distros that fundamentally depend on Systemd?
He might continue working on it but even if he doesn't the project will continue.
It's back already. Apparently it was removed from testing on 2022-06-25 then added back this morning:
https://tracker.debian.org/pkg/synaptic
Not sure why it was removed but it was an automatic operation:
https://tracker.debian.org/news/1339850 … m-testing/
EDIT: yet another indication of the superior usability of unstable compared to testing. The OP should probably at least add the ceres sources to pull from if critical system components are needed in future; testing can stay broken for a while sometimes.