... and then we had wonderful souvlaki! OPPA!!!

ᕕ(ᐛ)ᕗ

Well the original comment I responded to said

It's not the binary. It's that the logs it writes are in binary so can't be read without a program.

Of course, a text editor is also a "program", but I assumed they were saying they preferred plain text logs.

If you aren't agreeing with them then you need to state your position more clearly when you hop in.

Something something robe and wizard hat

I can't live with out the CachyOS patches. I need the optimized repos which you can add to Artix but really shouldn't. I got the CachyOs kernel installed in Artix. I was so surprised that didn't break anything. All of the tinkering for a system that's less capable than CachyOS just didn't seem worth it and I gave up.

Predictable, more-or-less identical systemd, with its stance on limiting eveything and being secure by default is more of a security risk than old-timey inits that were different for every distribution with init scripts made by different people with different abilities and customizations?

When I started my ops journey systemd wasn't there, and it was far harder to make compatible software. Also if you are designing a system how exactly general use systems come into picture at all?

By every reasonable measure systemd is a win, it started to appear even in automotive industry, which is regulated as hell, by 2022 (when I left).

You can read systemd logs with strings program (part of binutils). Even if the file itself corrupted due to a crash.

I may have written that in a confusing way. I'm saying systemd's job is service management. Systemd-resolved is an unnecessary bit of scope creep.

it's not just you. it's either systemd or no GNOME or KDE (technically possible if working around bugs is your 9-5).

I know. My simple criteria is pretty simple: Does my computer boot and show me pretty pictures of kittens after it boots. If it does, I do not care.

The only distro I recognize on their list of systemd-free distros is PCLinux. I actually used it for a bit a long time ago. Not a bad distro, but not a great one either. So I moved on.

Nup. No taksies-backsies.

I'll take the opportunity to manipulate a slight misunderstanding in your words to drive home my point on an inconsequential post on the internet, to hide my insecurities, and project out on them, of not getting laid no matter what keyboard I have. It is the Lemmy user way 🙏

Also, do you remember the model of the keyboard you had when you got laid? Asking for a friend.

Being subjected to both OpenRC and Systemd, I can appreciate both but Systemd is convenient and gets the job done. Maybe it's how the service is packaged and not OpenRC's fault, but I get better logging with Systemd services. Status of a failing service on OpenRC is it exited and that's all I get. Guess I have to fuck around and find the logs myself (because search results are people telling you to find them), whereas its a better time in Systemd.

Systemd is stable and can get the job done, I don't love how it does it, but I accept that it's a reasonable choice.

Something need/s/ed to replace X11. The fact that I still can't autohotkey in Wayland is fucking insane. 9/10 of my current issues in Linux are Wayland-related. We're being corralled into wayland as distros drop X11 and I don't have time to keep chasing that fox.

Underrated comment. Sauce: https://knowyourmeme.com/sensitive/memes/i-put-on-my-robe-and-wizard-hat

Yea what a hot take that was, critiquing words that were never there and then calling the person an idiot.

I initially agreed with your take there but I actually think they're a great argument for their point. head and tail are the exact same abstraction. Their implementations will be quite different, but they both serve "provided this data, give me these lines". Consider instead that these are simply operations on arrays and actually they map perfectly to Python slices: data[:10] and data[-10:]. This abstraction mapping also shows that, imo, the tool should provide data[n:m] and it would still be entirely consistent with the Unix philosophy. In fact, this tool exists in the Unix toolkit: sed -n n,mp. Three tools then are currently required for the simple concept of "slice lines". I also think it's a bit of a mess. You could replace head with sed fairly easily: sed -n '1,10p' but not tail (it is possible, but quite slow and very opaque)

As an aside I actually found this quite frustrating myself because I don't like reaching for sed in the n:m case (I always forget and end up piping head to tail) and ended up writing my own tool for essentially this style of slicing input, also replacing probably my least favorite use of my least favorite Unix tool, dd, to slice arbitrary byte sequences. The tool doesn't feel overloaded and I use it quite often.

(I'm sure many people have written this same tool. There is probably a widely known open source option that I've just never come across)

Funny thing is, that's not even his best stuff! Yaarrrrrr!!

https://forums.freebsd.org/threads/gnome-to-have-stronger-dependency-on-systemd.98260/

I've been running KDE on Alpine since Alpine v3.20 and I haven't had any issues with it that I haven't had on, say, Debian. If I'm not mistaken all components of KDE that depend on systemd are replaceable by standalone projects.

systemd-resolved is a service. It's not scope-creep. It's its own thing built in the systemd framework.

i have had the same experience with logs and OpenRC
usually i resort to manually running the commands and watching output

Wayland enforces security to stop one process sniffing or injecting input into another. X11 basically has zero security boundaries. So certain things are easier in X11, but then again the price to pay is too much.

So things like virtual mouse positioning, autohotkey, screen capture are harder to do but not insurmountable. It requires protocols that the client / desktop understand and which are fit for purpose. Big desktops like GNOME & KDE Plasma do support xdg-desktop-portal which allows hotkeys to be registered with the desktop, and could potentially be what you need.

Good to know I'm not the only one. I've resorted to the same when Docker would freak out on Alpine.

I need mouse and keyboard control to do testing automation.

I want keyboard interception so i can make dozens of !faxnumber, !address, !bashloop, !bashwhile macros to use text replacement on

You can do this in every other OS. It wasn't even a primary exploit, just something some devs decided to die on a hill over.

Wayland has been reasonably used for a decade, at what point would you consider unreasonbly difficult to transition into insurmountable

Stuff like ydotool, wtype exist and presumably there are others for this. Search on automation testing on Wayland and see.

Since it is a niche I'm not surprised if it wasn't a critical path for Wayland adoption but clearly there are solutions that work for certain compositors and I assume people working on a more robust solution. But allowing one piece of software to sniff or inject input, or capture its content is an obvious security flaw and Wayland devs are right to put it front and centre. If a desktop is to allow those things then it should be through a security model instead of in the absence of one.

I have ydotool, it is unable to do anything but put the mouse at 0,0

I have tried every product, got all the way into python before I was able to even do relative.

edit: just tried again because it's been a while. The best I can do with ydotool is move the mouse cursor to -99999,-99999 to get it ot go to 0,0 then go to 100,100. It is, to this day, unable to to an absolute position, but is able to do relative.

I just tried espanso too, doesn't work in kate or konsole, or web browsers.

I'm running in to the same stuff i've been running into for 3 years, none of the apps that are intended to do this actually do it in Wayland.

I just want to be able to use mouse automation and test replacement, i don't think that's a big ask.

The first thing I would try is booting from a live USB, mounting the old install, regenerating inframfs then update GRUB from terminal (it may or may not let you from terminal in the GRUB menu also)

I did all that and more already. That's why I ultimately gave up. It's rare that I can't fix a Linux issue, but this is one of those rare cases.

That sucks sorry dude hope there wasn't too much non-backed-up data

Well I can still access all the data from a live usb so I already backed up the most important stuff.

Maybe the people who downvoted didn't think the points were cogent or well-written.

It scrolls like crap on my desktop Firefox, too. WTF is this person doing with their website code?