Debian was often the only linux os that worked on old "spacestations" of mine. Great sentiment
And I mean Debian 12, not some old version, much more impressive
Do you mean SparcStations?
Debian 13 “Trixie”
291–300 of 428 posts
Re: Debian 13 “Trixie”
#292> The overall disk usage for trixie is 403,854,660 kB (403 GB) That's too big. I'm going to need a smaller distro.
You're probably being sarcastic, but in the eventuality you aren't, this is if you install every single package.
No, it’s actually the disk usage of hosting a full mirror, other users commented on that
Re: Debian 13 “Trixie”
#293Earlier quoted context omitted.
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.
Aren't firewall rules part of the "configuration" the OP talked about?
No, because you can install and configure the firewall before you install package X. (without knowing anything about X, your firewall defaults can just prevent X from doing anything)
But you can't (easily) configure package X itself before you install it; and after you install it, it runs immediately so you only get to configure it after the first run.
Re: Debian 13 “Trixie”
#294Earlier quoted context omitted.
Hopefully i386 (or perhaps a new i386-like port with added support for 64-bit time values) can move to the unofficial Debian Ports infrastructure for Debian 14 (forky) or Debian 15 (duke). Debian Ports has a m68k port, so supporting one for i386 shouldn't be a huge problem.
In case anyone wants to do that, here is the doc for new ports: https://wiki.debian.org/PortsDocs/New
Much of that information has to do with creating a new hardware port from scratch. The i386 support just needs to be "demoted" to the Debian ports infrastructure once it's officially scheduled to get dropped from the main Debian repository (which could well happen starting either in Debian forky or duke), and this can probably be done with some special handling.
(Answering the "to what end?" question, a lot of 32bit-only hardware is still available and dirt cheap in the second-hand market (e.g. early "netbooks"), much of it quite well-built and enjoyable to use. While such hardware can no longer realistically browse the "modern" web, it can still find a lot of use for more lightweight tasks, including acting as a "thin client" for more powerful machines.)
Re: Debian 13 “Trixie”
#295I have used Debian starting sometime around slink. I still type "apt-get ..." and it still works reasonably well. There have definitely been hiccups in upgrades over the last 25+ years but the amount of time/effort dealing with those is almost nothing in comparison to other linux and non-OSS systems I've dealt with over the same span of time. My only regret is not contributing more to the community. The thing I like…
Which one was slink?
My first Debian install was in 1996. I had no real idea what I was doing, but it was amazing to me that I could remote-display windows from machines across campus, and it was alien compared to the windows 3.x/95 I was used to at that point. There was no apt at that point, or none that I was aware of, and adding new stuff was painful.
I started using debian preferentially as my workstation/desktop OS in about 2005, and was installing it on embedded systems (linksys nslu2) to make micro servers by … etch I think it was.
By 2008 I was at IBM and they allowed a choice of windows or redhat on your laptop, and if you were adventurous there was experimental support for Ubuntu which might work on Debian. I made it work and discovered that among 330k people there were 22 of us running it!
Always loved it, it always just made more sense than other distros somehow. My daily driver is a Mac now, but I still have a few Debian machines around.
Re: Debian 13 “Trixie”
#296They only mentioned it briefly, and not by number, but this release includes 95%+ bit-for-bit reproducibility on AMD64, ARM64, and RISC-V across more than 30,000 packages (92% mean across all architectures). Congratulations to the team--phenomenal work! https://reproduce.debian.net/
Is there a tool on a given debian trixie system to know what installed packages are not currently reproducible?
Alternative to parsing the reproduce web site :)
Re: Debian 13 “Trixie”
#297A total of seven architectures are officially supported for "trixie": "trixie" 64-bit PC (amd64), 64-bit ARM (arm64), ARM EABI (armel), ARMv7 (EABI hard-float ABI, armhf), 64-bit little-endian PowerPC (ppc64el), 64-bit little-endian RISC-V (riscv64), IBM System z (s390x) It's good to see RISC-V becoming a first-class citizen, despite the general lack of hardware using it at the moment. I do wonder, where are PowerPC…
[deleted]
Re: Debian 13 “Trixie”
#298A total of seven architectures are officially supported for "trixie": "trixie" 64-bit PC (amd64), 64-bit ARM (arm64), ARM EABI (armel), ARMv7 (EABI hard-float ABI, armhf), 64-bit little-endian PowerPC (ppc64el), 64-bit little-endian RISC-V (riscv64), IBM System z (s390x) It's good to see RISC-V becoming a first-class citizen, despite the general lack of hardware using it at the moment. I do wonder, where are PowerPC…
> I do wonder, where are PowerPC and IBM System z being used these days?
IBM.
And they own redhat, so I imagine they put a lot of time and money into making the kernel work.
Why Debian in particular, not sure.
Re: Debian 13 “Trixie”
#299Earlier 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.
That is a workaround for a ridiculous issue.
Re: Debian 13 “Trixie”
#300Writing this from my Debian system, it's a great distro that has been excellent to me as a daily driver. I switched to Debian 6 after Ubuntu went way downhill and haven't had cause to regret it. I like Debian's measured pragmatism with ideology, how it's a distro of free software by default but it also makes it easy to install non-free software or firmware blobs. I like Debian's package guidelines, I like dpkg, I lik…
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.
It is a well-known issue with probably less well-known solutions, cf. https://unix.stackexchange.com/questions/723675/debian-ubunt...>
echo exit 101 > /usr/sbin/policy-rc.d
chmod +x /usr/sbin/policy-rc.d