You are not logged in.
Different thread: https://dev1galaxy.org/viewtopic.php?pid=18933#p18933
Simmer down, man! It's not all about you, y'know. I think you are overreacting just a tad. I agree with most of what you've been saying, but you seem to be seeing enemies where they're not.
Well said. Impatience, impulsiveness and drama will derail the best-intentioned efforts.
Whoa!!! That comment was more of a general statement rather than specifically directed at you. I have beat that drum many times on devuan channels. Mostly it falls on deaf ears and that is frustrating yet I keep trying. Perhaps it is true of all software (or other) projects that there are always too few people who will roll up their sleeves and commit. It is also true that we each have our unique talents.
I have held back because I'm not clear on exactly how you would implement the ideas/protections that we have discussed in some detail. If we agree that the 5 "Pillars" of GNU-Linux are the only way to protect truly free software what is the plan to ensure that it becomes the defacto standard?
No need to pick up your marbles and go home. Really. You won't find a more receptive audience than you will here. ![]()
if you find a piece of something you can fix, great. but if nobody knows it exists, that sadly wont help much.
Have at it. Plenty of bugs to choose from. We know they exist but it's easier to talk.
Note that some of these reports may not actually be "bugs" but we don't know because no one is checking.
Soon you will not be able to choose not to run systemd. Systemd is "capturing" the GNU-Linux "commons" that we have shared for decades through a web of hard dependencies. The only choice will be not to use GNU-Linux.
Blah, blah, blah . . . all this talk is not going to save GNU-Linux. Only DOING can accomplish that.
Has anyone given ungoogled chromium a spin?
From the ASCII 2.1 point release announcement
What about ARM and virtual images?
Going forward, ARM and also virtual images will be provided by the greater Devuan community rather than as part of official releases. Users are being encouraged to build and contribute ARM images for their particular hardware. This will increase the variety of images available and allow the release schedule of the installer ISOs to move forward more quickly.
Images can be built using using arm-sdk and vm-sdk: https://devuan.org/os/distro-kit
Arm-related discussion happens at #devuan-arm (Freenode) and https://dev1galaxy.org/viewforum.php?id=24
Images will eventually be available via p2p torrent(s).
That is pretty much where I got all twisted around trying to make my point.
We always knew it wanted to be the systemd OS.
I have spent quite some time thinking about this and wanted to add a bit of discussion to the Free Software page of the website. I wanted to convey the concept that "free" software that limited users freedoms wasn't really free. Lack of modularity was a primary concern. Then I was reminded that there was the freedom to restore modularity so I've been letting a response around that argument simmer in the back of my mind. Perhaps between us we could come up with something.
Are you related to e e cummings? lol!
The mini.iso is for internal pre-release testing and not part of an official Devuan release. If you want to run beowulf, install ascii and upgrade. iirc there are some unofficial beowulf options at refracta.org. fsmithred should be able to clarify that.
Would I benefit from using the Country Code in the sources.list?
deb.devuan.org is recommended but you can also choose a mirror from the list of available mirrors that might suit you better.
What is amprolla and what does it do . . . or not do? At the First Devuan Conference in April, Katolaz' presentation "The Quest for Minimalism" answered these questions. This audio of the amprolla section enhances understanding of the screenshots below.




Posting for clarity that in Devuan we advise not to use the Suite designations because doing so can cause unexpected "breakage". Here's why:
Codenames or suites?
The release codenames or suite designations in /etc/apt/sources.list indicate which release will be used when updating and upgrading packages. Note that the suite names stable and testing will refer to different releases over time.
As of this writing, stable refers to Devuan ASCII (Debian Stretch) and testing refers to Devuan Beowulf (Debian Buster). Once Beowulf is officially released, stable will refer to Beowulf and testing will refer to the next release in development, Chimaera (Debian Bullseye).
However, if your ASCII sources.list refers to the release codename ascii you will remain on ASCII until you change your sources.list. That means that you will have more control over when the upgrade happens. And if you are using beowulf in your sources.list you will move seamlessly to the new stable version of Beowulf when it is released.
To avoid the possibility of mixing two potentially incompatible repositories, Devuan recommends using release codenames in sources.list.
Source: https://devuan.org/os/releases
Good find!
I found this link more informative than reddit:
https://www.patreon.com/posts/31633933
Yes. Just haven't gotten around to it yet.
I think this is it:
And abolishing source distributions would stop global warming within months!
bitcoins are the real energy hogs.
If you use "testing" in your sources you will get Debian Bullseye and fubar your install. Always use the release name in your sources list. This is explained on the website. Look for "Codenames or suites?".
Please continue discussion at this existing thread:
HoaS . . . see the link on my first post in this thread that was rejected by the OP.
The ones that are actually harmful and not just imagination are listed here:
https://pkgmaster.devuan.org/bannedpackages.txt
If they are also listed here, let us know: