251–260 of 428 posts
It can be a little hard to navigate to so the .torrent links for x86-64 are Minimal: https://cdimage.debian.org/debian-cd/current/amd64/bt-cd/deb... Full: https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/de...
Does anyone have any suggestions for a 32-bit distro that's still being updated?
As an owner of two i386 systems (both netbooks built around Intel's Atom N270), that run Debian, I am a little sad. I understand the reasoning, and I won't deny it is a very niche platform by now. But I had hoped Debian, with a history of supporting a wide range of platforms, would keep i386 going for a while longer. Fortunately, bookworm will continue to receive updates for almost 3 years, so I am not in a hurry to…
My ~/.config/mpv/config:
#inicio
ytdl-format=bestvideo[height #inicio de fichero
--format=bestvideo[heightyt-dlp wrapper
#!/bin/sh
. $HOME/src/yt-dlp/bin/activate
$HOME/src/yt-dlp/bin/yt-dlp "$@"
#!/bin/sh
. $HOME/src/streamlink/bin/activate
$HOME/src/streamlink/bin/yt-dlp "$@"
mkdir -p ~/src/streamlink
cd ~/src/streamlink
virtualenv .
. bin/activate
pip3 install -U streamlink
mkdir -p ~/src/yt-dlp
cd ~/src/yt-dlp
virtualenv .
. bin/activate
pip3 install -U yt-dlp
Overall it's a really fast machine. CWM+XTerm+Tmux it's my main environment. I have some SSH connection open to somewhere else at the 3rd tag (virtual desktop), and the 2nd one for Dillo.
I'm very sad to see them drop support for 32-bit, since that is the computer on which I have been using Debian for the past 10 years... Does anyone have any suggestions for a 32-bit distro that's still being updated?
Earlier quoted context omitted.
>I've never had a Debian system break without it being my fault in some way. Debian is great but I can't say this is a shared experience. In particular, I've been bitten by Debian's heavy patching of kernel in Debian stable (specifically, backport regressions in the fast-moving DRM subsystem leading to hard-to-debug crashes), despite Debian releases technically having the "same" kernel for a duration of a release. In…
> Debian's heavy patching of kernel in Debian stable Needs citation. Debian stable uses upstream LTS kernels and I'm not aware of any heavy patching they do on top of that. Upstream -stable trees are very relaxed in patches they accept and unfortunately they don't get serious testing before being released either (you can see there's a new release in every -stable tree like every week), so that's probably what you've…
Earlier quoted context omitted.
Not by Debian it isn't. https://www.debian.org/releases/ Buster has not been supported by Debian for many years. Buster LTS was EOL last summer. Note that LTS is supported by volunteers via a non-profit, not Debian (though they do a good job). ELTS is paid support, again not by Debian. Do look at Debian's wiki for more info on support timeframes, and what LTS and ELTS means.
Freexian is for-profit, and all the LTS/ELTS contributors are Debian maintainers, and LTS is part of Debian, while ELTS is publicly available too, but in an external archive. https://wiki.debian.org/LTS https://wiki.debian.org/LTS/Team https://wiki.debian.org/LTS/Extended https://wiki.debian.org/LTS/Funding
Back to LTS:
Debian LTS is not handled by the Debian Security and Release teams, but by a separate group of volunteers and companies interested in making it a success.
To the point, Freexian is 100% not Debian, not "part" of Debian, it merely uses Debian's infra gratis for LTS. This does not detract from the good work they do, but we must also not confuse a private company, and its goals, with Debian and its goals.
LTS tries its best, but only supports what it can. Not its fault. Thus they do give preference to packages which are more widely used, and which they have received donations for.
So wildly popular things such as apache2, mariadb, and so on are very much going to be handled. Some rare package which has 400 users worldwide? Not so much.
LTS will very much take patches and any help, but that still ties in to the number of users. If a packages has 400 users worldwide, and most have moved on to the next release? Well, I hope you see my point.
(I've moved customers off of LTS for using rare packages, whilst reassuring them that LAMP servers are very much supported due to this. Popularity counts here, due to efforts of volunteers and externals.)
--
ELTS only supports a further subset of packages. It's not "full" support. I think one would be exceptionally unwise to use it, for say a desktop. That is, unless they were paying for support and had obtained a list of all packages supported.
--
https://www.freexian.com/lts/extended/docs/debian-10-support...
"Note that when you request a quote, we send you back a list of packages that are not supported or that have limitations in their support so that you can take an informed decision."
Yes, I know that page has a git repo and so on for some support information.
But my points are; not the full distro is supported, you have to track this yourself, you need to be diligent, and even so you need to be sure you're not running rarer packages.
Once again, I do want to reiterate, these are both excellent programs. They do a good job, they're dedicated, but we must be aware of the limitations here.
An example being the differences between security support for main, non-free, contrib in stable Debian:
https://www.debian.org/security/faq#contrib
As you can see, there is no actual guaranteed security support for contrib and non-free. The reasons are logical, however, users need to be aware of the nuance here.
Just as they need to be aware of the nuance of LTS and ELTS.
For example, all of my server installs have non-free, non-free-firmware and contrib blocked via pinning in preferences.d, with only specific absolutely required packages then allowed back in.
(For example I may allow command line apps, but not anything network connected, and only with a once over of functionality and SUID bits and other such things)
--
Really, I see LTS as a crutch that normal users should never use. I suggest we collectively not encourage Desktop users (for example) to use LTS.
Earlier quoted context omitted.
On boot has been the standard for a long time and is still the most common. I am personally surprised to hear that now Debian and some distros do it via various automated ways at time intervals.
It's a systemd thing, see `man systemd-tmpfiles`.
Earlier quoted context omitted.
Bear in mind, LTS and ELTS are not Debian maintained. The wiki has more info on this.
The folks behind Debian LTS and Freexian ELTS are all Debian members/contributors, and the Debian LTS changes end up in the Debian archive, while the Freexian ELTS ones are publicly available, just in an external archive. https://wiki.debian.org/LTS https://wiki.debian.org/LTS/Team https://wiki.debian.org/LTS/Funding https://wiki.debian.org/LTS/Extended
Earlier quoted context omitted.
The only thing I can say against Debian is that it tends to start new server software immediately after install, before I have a chance to configure it properly. Defaults are sane for most packages, but, still, it scares me a little. In that I like the Red Hat approach of installing and leaving it off until I decide to turn it on.
Just have sane firewall rules and you are good. E.g. if I install openssh-server and it auto starts, it doesn't make it out of my machine because my nftables does not allow inbound on port 22. It's just knowing the default behaviour and adjusting your practices for it.
I have been using Debian Trixie for a few months in testing now, I can attest that its a great, stable operating system. Definitely better than Ubuntu in terms of user experience.
The only complaint on a fresh install is that Cinnamon seems to use a ton of CPU when there's a little moving thingy anywhere on the screen (a browser tab that has a loading icon in the tab list is sufficient). This is most noticeable when you have a VM without graphics acceleration (don't ask why in the world my job requires that). Graphics without acceleration is always heavy, but this is an extra process doing wha…
In Gnome, Blender becomes unresponsive but everything else is still usuable. In Cinnamon, the entire system becomes unresponsive.