You are not logged in.
lol
Well it was worth a try.
I am on Ceres almost year and nothing is broke yet.
Give it time
And enjoy the massively outdated packages during the upcoming freeze. The Debian devs sometimes even leave critical bugs unfixed in the development branches until the release is done...
its NOT subjective
I respectfully disagree. Change my mind :-)
Check for enabled services, systemd likes to automount efivarfs rw so perhaps a sysvinit script has been added to do the same thing.
To disable access to UEFI NVRAM variables use the noefi kernel parameter.
If I understand policy correctly, I would be asking for a backport of 5.0.2 from testing to be made available for Bullseye in Backports. If I were the package maintainer receiving that request, my response would likely be something along the lines of "Why are you making more work for me? Eyes on Bookworm.", because experience suggests backporting a major 5.x.x version to a system built at the time 4.x.x was stable frequently gets hairy. If that kind of work were the norm, I would expect Backports to be a bit of an unstable mess.
The lxcfs package was backported for the Debian stretch release[1] so it looks possible, at least.
You could even try it yourself:
https://wiki.debian.org/SimpleBackportCreation
^ That would ensure a ~bpo version suffix, which eases transitions between releases.
When you say "The stable release is so named because the version numbers do not change.", does that mean Updates are more like :
lxcfs-4.0.7-1 + patches => lxcfs-4.0.7-2 + patches => lxcfs-4.0.7-3 +patches => lxcfs-4.0.7-4
In which case patches are generally limited to bug squashing and mitigating security concerns?
Yes, that's right.
If I were to produce a patch against lxcfs-4.0.7-1 that exclusively corrected the lxcfs presentation of /proc/meminfo ... would that be welcomed within the Debian ecosystem and worthy of an lxcfs-4.0.7-2 package being released?
I would hope so. I think you should submit the patch. See https://www.debian.org/Bugs/Reporting for the preferred method.
Perhaps what I am looking for is a grey area between Backports and Updates where the software vendor has addressed minor issues within a major release and deemed a minor release is warranted. Do these minor releases get picked up in the Debian update cycle? Or do folks just wait for the next Debian stable release?
There are regular point releases that provides security and other bug fixes without major package version increments. There are some notable exceptions, however: firefox-esr & chromium will both be kept up to date with the respective upstream versions (although chromium can lag a little).
rolfie has already told the OP how to use su correctly. Let's see if they can put the pieces together...
how one effectively approaches/advocates/assists toward greater symmetry between stable vendor releases and distribution updates without stepping on toes within the Debian ecosystem.
File a WNPP bug report with Debian to request that the newer version of lxcfs be added to the stable-backports repository.
The stable release is so named because the version numbers do not change.
Can you show me an example of theloop you mentioned?
I already have. Replace [stuff] with the commands to be repeated.
Been trying to get it to work, but it gives me the unexpected end issue when I try...
Show us your attempts.
Tell me one best benchmarks
https://steamcommunity.com/sharedfiles/ … =500334237
Witch Devuan stable or unstable?
Stable. Unless you enjoy fixing broken systems.
EDIT:
Anything with boot speeds of under a couple of seconds is startling to me
Hold on to your hat Andy:
archie:~$ systemd-analyze
Startup finished in 210ms (userspace)
multi-user.target reached after 210ms in userspace.
archie:~$ systemd-analyze blame --no-p
49ms systemd-resolved.service
33ms user@1000.service
20ms systemd-journal-flush.service
20ms systemd-logind.service
19ms systemd-tmpfiles-setup.service
12ms iwd.service
11ms dbus.service
10ms systemd-journald.service
9ms systemd-tmpfiles-setup-dev.service
9ms nftables.service
5ms systemd-remount-fs.service
5ms dev-hugepages.mount
4ms sys-fs-fuse-connections.mount
4ms systemd-update-utmp.service
4ms user-runtime-dir@1000.service
2ms systemd-user-sessions.service
archie:~$
you need en_US.UTF-8
^ This.
how can you achieve that with Devuan?
# dpkg-reconfigure locales
1.Arch(vanilla)
2.Devuan Ceres
3.Artix(no systemd Arch)The fasted for me is Artix, second is Devuan, third Arch
Which benchmarks are you using? Care to share them?
What Linux is better for
My first PC, modern - AMD r2600, radeon rx580, 32gb ram
I think may be vanilla Arch? I love play different games old and new)
That's an old Ryzen so I would expect Devuan to do well against Arch. Run the same games on both and compare framerates. CS:GO runs marginally faster under Arch for me (compared to Debian bullseye) but I have a 5th generation Ryzen.
Only mitigations=off is needed. I also do that :-)
Use this to check:
for i in /sys/devices/system/cpu/vulnerabilities/* ; do echo "$(basename $i): $(cat $i)" ; done
I would also recommend disabling all desktop trackers & miners, along with the display manager. And X, but that might just be me.
https://wiki.archlinux.org/title/Improving_performance is a good reference but not everything there will apply to Devuan, for obvious reasons. Devuan is already faster than vanilla Arch anyway
When the devices are missing does thunar show any error messages when started from a terminal? How about the X.Org log?
I think the package should be fixed in Debian. I myself use Debian with runit as PID1 instead of systemd so I would very much like bugs such as these to be fixed there.
is there a finite limit?
No. Use this construct to start an infinite loop:
while : ; do
[stuff]
done
https://pubs.opengroup.org/onlinepubs/0 … colon.html
how many files would be a bad idea to have in one folder for someone like me?
Infinite files would be a bad idea. Otherwise the image tiles are about 100KiB in size so it depends how big your hard drive is. Many files would only cause a slowdown if you tried to view them all at once, for example in a graphical file manager with thumbnails enabled.
Yeah, it's hellauseful in scripts — for example, get the UUID of the root partition with findmnt -no uuid /.
The problem and potential solutions are described here:
https://forums.debian.net/viewtopic.php?t=104157
LightDM & SLiM can be co-installed, use this to select between the two:
# apt install lightdm
# dpkg-reconfigure lightdm
I don't recommend either though because they run X under the root user. GDM runs X under the normal user, which is _much_ better.
EDIT: try
# apt install lightdm slim-
^ That installs LightDM and removes SLiM in one swell foop.
Can we see
cat /etc/fstab
findmnt
Thanks!
#!/bin/sh
dir="$HOME/WallpaperZone"
count="1"
mkdir -p "$dir"
while [ $count -lt 11 ] ; do
starfish -o "$dir"/Wallpaper"$count"
count=$((count+1)) # ah ha ha
done
Add set -eo pipefail as the first line (after the shebang) if you want the script to exit after any of the commands fail.
EDIT: that example provides 10 images, change the -lt 11 bit to modify that.
EDIT2: added counting Count reference. I love jokes in the comments.
On Devuan dhclient is already there, so I tried to append the 'prepend domain-name-servers 8.8.8.8, 8.8.4.4;' line but to no effect.
What does "no effect" mean, exactly? Are you sure Devuan is using dhclient? Did you try disabling it and populating /etc/resolv.conf manually instead?
If accessing Google's DNS directly fixes your problem then the problem probably lies with the router or ISP, as xinomilo notes.
Shall I file a bug report for this?
I would say yes. But the Debian package maintainer is under no obligation to add support for non-systemd boxen.
the 2 dxvk packages already exist in Debian in the unstable branch
- dxvk and dxvk-wine64-developementand can be installed using synaptic package manager. just by adding unstable branch temporarily in to Peppermint OS Debian Base Repo settings
using peppermint OS Debian Base i was able to install it....
Do not do that, it will break your system.
Please read https://wiki.debian.org/DontBreakDebian.
It's the ultimate "gene therapy" — the only winning move is not to play :-)
Not that I know of but I've been using iwd for a good long while now so I don't keep up with wpa_supplicant. That ctrl_interface line is only needed for wpagui though, at least AFAIK.
Use the /etc/network/interfaces format suggested in https://wiki.debian.org/WiFi/HowToUse#W … d_WPA2-PSK instead.
I also subscribe to the VHEM. I smoke far too much weed to be fertile anyway
The only thing I use iw for is power management; ip & iwctl do all the legwork in my system.
You should try iwd, it's lighter & more secure than wpa_supplicant with fewer dependencies.