HEADLINE SELinux installed by default DESCRIPTION Not sure what else to say...
Please no.. Apparmor is far more usable and functionally equivalent.
In the docker world, it would be a huge improvement.
91–100 of 329 posts
Earlier quoted context omitted.
> rename testing to something with a positive > connotation that doesn't suggest it's for > testing only. Isn't unstable what you want to use? The reason it's called "testing" is because it's a branch of Debian that's "in testing for stable". IIRC packages have to be 2 weeks in unstable without bugs before migrating to testing. So it's explicitly not a bleeding edge release, but a preparation release for the next sta…
At the very least "unstable" has a name with a negative connotation. It has the air of it being the user's fault if you use it and stuff breaks. I don't know what the practical breakage situation is, so I don't know if renaming and repositioning unstable would make more sense than doing it with testing. My point is that it would be good for non-expert end users who like Debian's community image and who want security…
If you haven't tried it, give it a shot. You may be surprised.
Earlier quoted context omitted.
Is there a valid reason to move to git from any other VCS a person happy with, regarding time and resources one have to spend on it instead of productive work?
I can't contrast git with all the different VCS tools that are available, but different tools have different capabilities with respect to working offline and reconciling branches. At any rate, it was an honest question. I'm not familiar with any salient reasons to not use git. If the only reason is that some developers still haven't learned git yet, I guess that's an answer. Not a very satisfying one to me, but it's…
Earlier quoted context omitted.
These don't work for WiFi drivers as I pointed out because they're not actually the firmware, they're packages to download the firmware. That obviously doesn't work if you don't have a network connection.
No, those do contain the firmware. https://anonscm.debian.org/cgit/kernel/firmware-nonfree.git
Earlier quoted context omitted.
Is there a valid reason to move to git from any other VCS a person happy with, regarding time and resources one have to spend on it instead of productive work?
I can't contrast git with all the different VCS tools that are available, but different tools have different capabilities with respect to working offline and reconciling branches. At any rate, it was an honest question. I'm not familiar with any salient reasons to not use git. If the only reason is that some developers still haven't learned git yet, I guess that's an answer. Not a very satisfying one to me, but it's…
Sadly, mercurial-buildpackage in Debian is a dead-end. :-(
HEADER 100% reproducible packages DESCRIPTION While having over 90% of packages reproducible already is awesome, 100% would be even better. The stretch release announcement describes best why: > Thanks to the Reproducible Builds project, over 90% of the source packages included in Debian 9 will build bit-for-bit identical binary packages. This is an important verification feature which protects users from malicious a…
HEADER 100% reproducible packages DESCRIPTION While having over 90% of packages reproducible already is awesome, 100% would be even better. The stretch release announcement describes best why: > Thanks to the Reproducible Builds project, over 90% of the source packages included in Debian 9 will build bit-for-bit identical binary packages. This is an important verification feature which protects users from malicious a…
DESCRIPTION: a consensus on the next generation of package management. Please. We have had decades of fragmentation (not to mention duplicated innovation) around the RPM vs DEB ecosystem. Which is why it is still hard for beginners to want to use Linux - try explaining to anyone who comes from a Mac about rpm vs deb vs whatever else. Which is why they would pay for the mac rather than use Linux ("its too hard to install software").
Its not just my opinion - PackageKit (https://www.freedesktop.org/software/PackageKit/pk-intro.htm...) was invented for this reason. So you could have Gnome Software Manager that can work the same on every flavor of Linux. Its time to build this the right way.
You have an opportunity now - but again the camps are getting fragmented. We now have snap (ubuntu/deb) vs flatpkg (redhat) all over again. And pretty strongly divided camps are beginning to form around them. It seems that the new rhetoric is snap for servers and flatpkg for desktops... which absolutely doesnt make sense.
Debian is the place to make this stand - systemd was adopted from fedora despite Ubuntu making a strong push for something else. Debian made Ubuntu adopt systemd. I dont think anyone has anything but respect for that process. Debian 10 must take a stand on this.
Earlier quoted context omitted.
I would love some type of toggle, or "last chance to turn back" during install as far as being able to signal what type of init system I'd like to use.
The problem is that no-one has incorporated a modification to the Debian installer to have this. There are so-called "preseed" hooks that one can use to manually alter what packages the Debian installer installs. Putting in place pre-seed hooks that permitted something other than systemd to be installed ab initio was one of the first things that the Devuan people did, about two and a half years ago. But no-one to my…
HEADLINE: Repurpose testing as a rolling release positioned for not-just-testing usage DESCRIPTION: There are users who'd like to use a non-corporate community distro but who don't need or want software to be as old as software in Debian stable. The standard answer is "use testing" (e.g. http://ral-arturo.org/2017/05/11/debian-myths.html ), but 1) security support for testing is documented to be slower than for stabl…