You are not logged in.
I personally would like to give an indication as to why those hacks are needed. There are plenty of hacks but this section will focus on those thrust upon us by upstream decisions.
How about just "Triage"? (Rather than init triage)
I thought of that too but IMO it is too general. Perhaps it could be clarified in the forum description, something like this:
Triage
Explore workarounds to fix unwanted upstream decisions
Maybe that's getting closer?
Why are systemd files present in Devuan?
Have you tried heads?
Init Freedom Hacks?
Unfortunately, if we want to include other poettering elephants like pulseaudio for discussion, it can't be limited to init. Maybe just "Freedom Hacks"?
Thanks for the ideas. Now let's go deeper . . . IMO, "FOSS" is too general and philosophical. Also it's about more than systemd. I see it being about unnecessary "complification", removal of working options and core structure just because. What ever happened to "KISS" and "if it works, don't fix it". Please keep trying. We also will need a very short description of what the new category will encompass.
EDIT: Also FOSS is a non-starter because systemd passes the test technically if not in spirit.
There are workarounds to Devuan systemd dependencies scattered around this board. It would be nice if they were all in one place so they could be easily found. I suggest a new forum category, Devuan systemd dependency workarounds which should only contain solutions to Devuan systemd dependencies.
Thanks for suggesting this. Your proposal was discussed today at our weekly meet and we think it would be useful. Problem is that we need a shorter name. Suggestions welcome.
- Init Triage
- Regaining Control
When someone finds a solution to a Devuan systemd dependency, the solution could be cross posted to Devuan systemd dependency workarounds by the person who found the workaround or anyone else. Similar posts could be made for pulseaudio and networkmanager at least.
Or threads/posts could just be moved.
I suggest that this category be moderated to reduce cruft. Any post not related to a systemd workarounds gets moved to another category.
Sometimes threads are moved or split but content is kept intact. We have an aversion to rewriting history. ![]()
Been growing with and grooving on this since the mid-70s:
It's takes them about 3 minutes to settle in but after that it is heaven.
Minimalism rules!
Nah. How about some Kathak?
@jobbautista9 . . . Thank you for taking the initiative to do that. ![]()
I have deleted users who have never posted at their request. But wouldn't delete a user who has a history of posts.
Note that a user would only want to install specific packages from backports if needed. Updating everything in backports could create unpleasant, unintended consequences.
I hope Devuan fork this package and add the necessary init scripts. It's really annoying when you install a package just for it to not work afterwards, and you're forced to find a workaround yourself.
You could start by submitting the patch to Debian. If that fails, you are welcome to maintain it long-term for Devuan. ![]()
Yes
. For example, xlupe has a nice slider bar to easily change magnifications.
Isn't that what the scroll wheel is for? Why go fumbling about for a slider . . .
Was it your intention to link to the generic Debian wiki landing page (on which I didn't see a DontBreakDebian section)?
Of course not. I fixed it.
Use PPAs with Debian or Devuan at your own risk. Please take DontBreakDebian to heart. Also read this page on the Devuan website.
edit: corrected incomplete link
Posts about Kali are not even answered on the Debian forum because Kali is not Debian. Devuan is even further away from Debian. Did you try searching for "kali" on this forum? There are some mentions here and there which could possibly be useful to you. FYI, ParrotSec OS is building a version on Devuan so there may be some pointers if you check that out.
amprolla was misbehaving but I haven't seen any discussion about it being fixed. It is summer after all . . .
Happy to hear that. It's a good idea to read the release notes because there are always a few "gotchas" with each new release.
From the beowulf release notes:
If you are already on Beowulf, just run this command to get to the
current release version:apt update && apt dist-upgrade
The first time you do this after Beowulf has gone Stable, you will get
a warning that the repository changed its 'Suite' value from 'testing'
to 'stable'. Answer 'yes' to proceed. Note that aptitude or apt-get will
fail this first time. Only apt will ask you to accept the change.
golinux misses gksu . . .
Also note that it is a very-bad-idea to use the suite names in sources.list because Devuan and Debian are not always in sync. It is safer to use codenames to avoid unintended consequences. Please see https://devuan.org/os/releases.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
Repeated for truth. Best signature ever!
Gnome has some rough edges period and does not play well with others. I have a hard time understanding why anyone would want to use it especially on a distribution whose philosophy leans in the opposite direction of Gnome's. Classic square peg|round hole thinking.
Case in point:
https://linuxreviews.org/Mpv_drops_GNOME_support
Any judgmental evaluation has multiple perspectives. Best to be aware of them all. ![]()