[-] [email protected] 1 points 2 hours ago* (last edited 2 hours ago)

Omg, adding /usr/bin/env worked. Launched the daemon, and the client is able to launch and connect a WireGuard tunnel.

systemctl show-environment lists /usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin on the PATH, so maybe that's why that worked...? (I'm going to have to go read up on env).

Either way, I did a reboot to verify, and it's definitely running. Now I just need to tweak it a bit so it tries to reconnect if the network drops out, but holy shit, I appreciate the help.

[-] [email protected] 1 points 4 hours ago* (last edited 4 hours ago)

Tried that, back to 203/Exec error. It's like ExecStart wants me to specify a program to launch it, and bash clearly isn't it.

[-] [email protected] 1 points 5 hours ago

Yep, more specifically I tried sudo systemctl enable --now daemon.service. Gives the same error, and maybe that's because it's some kind of binary.

sudo /bin/bash /path/to/daemon throws the same error, but sudo /path/to/daemon does not. However, if I drop , /bin/bash from the service file, it throws a 203 error instead.

[-] [email protected] 1 points 5 hours ago

Private Internet Access

[-] [email protected] 2 points 6 hours ago

Foiled by autocorrect! There's no space in the original file, and I've edited my post to reflect that.

[-] [email protected] 1 points 6 hours ago* (last edited 6 hours ago)

Thanks, I verified that it's in the correct place. Still throwing a 126 (see the modifications in the edit).

[-] [email protected] 1 points 6 hours ago

I added the relevant user and group, and it's still throwing a 126. I checked the daemon itself, and it looks like it's a pre-compiled binary. Manually running /bin/bash /path/to/daemon gives the same error, but sudo /path/to/daemon starts the daemon.

[-] [email protected] 2 points 6 hours ago

It's an autocorrect typo. It's actually WantedBy in the file.

[-] [email protected] 1 points 6 hours ago* (last edited 6 hours ago)

The service is in that folder, but it's not automatically assuming to run as root. Maybe it's an SELinux thing, since this is on Bazzite...?

Either way, I tried adding

[Service]
User=root
Group=root
ExecStart=...

And it's still throwing that 126. It's definitely executable, but maybe it's not a bash script, though I dunno what else you'd use to run it. To manually start it, you just type sudo /path/to/daemon (no file extension).

Edit: definitely not a bash script. Kate can't read it. It looks like it's some kind of pre-compiled binary.

[-] [email protected] 2 points 7 hours ago

The latter. Autocorrect got that one.

4
submitted 8 hours ago* (last edited 2 hours ago) by [email protected] to c/[email protected]

cross-posted from: https://reddthat.com/post/21668140

I have a VPN daemon that needs to run before the client will work. Normally, this would have been set up automatically by its install script, but the system is immutable.

I've created the systemd service via sysyemctl edit --force --full daemon.service with the following parameters:

[Unit] 
Description=Blah
After=network-online.target

[Service]
User=root
Group=root
ExecStart=/usr/bin/env /path/to/daemon

[Install]
WantedBy=multi-user.target

I've verified that the daemon is actually executable, and it runs fine when I manually call it via sudo daemon. When I try to run it with sudo systemctl enable --now daemon.service, it exits with error code 126.

What am I missing?

Edit: Typo, and added the relevant user and group to the Service section. Still throwing a 126.

Solution: the system wanted /usr/bin/env in ExecStart to launch the binary. The .service file above has been edited to show the working solution.

10
submitted 9 hours ago* (last edited 2 hours ago) by [email protected] to c/[email protected]

I have a VPN daemon that needs to run before the client will work. Normally, this would have been set up automatically by its install script, but the system is immutable.

I've created the systemd service via sysyemctl edit --force --full daemon.service with the following parameters:

[Unit] 
Description=Blah
After=network-online.target

[Service]
User=root
Group=root
ExecStart=/usr/bin/env /path/to/daemon

[Install]
WantedBy=multi-user.target

I've verified that the daemon is actually executable, and it runs fine when I manually call it via sudo daemon. When I try to run it with sudo systemctl enable --now daemon.service, it exits with error code 126.

What am I missing?

Edit: typo

Edit 2: Added script modifications. Daemon appears to be some kind of pre-compiled binary.

Solution: ExecStart wanted /usr/bin/env to launch the binary. The service file above has been edited to reflect the correct solution. See this post for further discussion.

[-] [email protected] 1 points 10 hours ago

Sorry I didn't get back sooner, but I made some progress.

What do you mean with "work in progress"?

Their words (second video, I think), and more in reference to how they are still working out how they haven't yet covered all of the use cases (like maybe my needs can't currently be met by rpm-ostree or bootc). rpm-ostree has functional limitations, and bootc is still being developed. Obviously, both are still useable and useful, and Universal Blue has been using them for quite a while. I may have been reading too much into it with the "depreciation" comment.

So, did you try the following methods when installing the .run file? If so, how did it go?

It can't work on its own. Running with sh or making it executable runs the script, but it fails when it tries to write its icon and .desktop entry to /usr (it also doesn't take an --appimage-extract argument). You can use sudo rpm-ostree usroverlay to create a temporary FS overlay for /usr, but it's wiped on the next boot. Still, that allowed the installation to complete.

I discovered that it's installing all of the necessary components to /opt, and they remain functional. I was able to manually run the daemon script required and get a WireGuard tunnel established in the client.

Now, I'm trying to get a .service module to work so it can run automatically as root on a reboot with systemd. So far, it's giving me a 126 exit code, so I still haven't figured out how to escalate its privileges automatically, but this is the most progress I've made to date.

[-] [email protected] 48 points 1 day ago

The Microsoft support forums are pitifully hilarious, too.

"Hi, I need help with N. I've tried X, Y, and, Z."

"Hello, sorry to hear that you're having trouble with N. Have you tried X, Y, or Z?"

"Yes."

"I'm sorry to hear that it's still not working. Please refer to this thread, and feel free to contact Microsoft Support with any future questions. Have a nice day."

"But my problem still isn't solved. Hello?"

68
submitted 3 days ago by [email protected] to c/[email protected]

I'm working on my transition plan away from Windows and testing out various things in VMs as I do so, and one big hurdle is making sure the VPN client my work requires can connect. Bazzite is my target distro (primarily gaming, work less frequently), though other more traditionally structured ones like Pop!_OS and Garuda are possibilities.

I'm currently trying and failing to get the VPN client working in a distrobox (throws an error during connection saying PPP isn't installed or supported by the kernel). However, I can successfully get the VPN connected if I overlay the client and its dependencies via rpm-ostree install, but I read somewhere that Bazzite's philosophy is to use rpm-ostree as sparingly as possible for installing software to preserve as much containerization as possible.

Since I can get it working outside of a container, am I overthinking it? Should I just accept that this might be one of the "sparing" cases? Is Bazzite perhaps a poor fit for my use case? I've been trying to make sense of this guide, but I'm having trouble understanding how to apply it to my situation, since I'm not that familiar with Docker or Podman.

59
submitted 1 week ago by [email protected] to c/[email protected]

For example, I saw a post the other day detailing how to set up a Brother laser printer on Kinoite. That's not something I would have initially considered a potential problem to be solved. Another I ran into some years ago had to do with an Edimax WiFi dongle that used some weirdly specific Realtek 8812 radio, for which you had to set up the driver via dkms. A little prep and knowledge in advance would have saved days of searching online.

I've started a personal to-do list of things to research and make sure I have all my ducks in a row before I make the full-time switch on my main desktop, so besides the usual "back up your files" advice, I'm hoping y'all can point out some QoL things I and others may often miss!

2
submitted 1 week ago by [email protected] to c/[email protected]

As an ex-fundigelical, I think the boys get it wrong here. Perhaps the people at the top are cynical with regard to the existence of demons, but I guarantee there's a concerning number of people in the crowd who think demons are real, and they genuinely think they're fighting a holy war against them by opposing people that include "liberals and 'unhuman' communists." I used to think demons were actually real, and average people often had demons inside them, like sleeper agents waiting to be activated.

I agree that the "demonic" rhetoric is a convenient tool to justify political violence, but many of them aren't using demons as an excuse to do something they already want to do; they're doing it because they genuinely think they're saving humanity from Satan to usher in some kind of idealized 1950s utopia ~~only for white, affluent Christians.~~

In their mind, they are sincerely at war with their fellow Americans, but there's a convenient, dehumanizing layer of "demons" to make them feel better about any acts of violence or stripping of rights.

Hello, spectre of Nazism.

64
Why openSUSE? (reddthat.com)
submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/[email protected]

First, let me be clear up front that I'm not promoting the idea that there should be one "universal" Linux distro. With all the various distros out there for consumers, there's lots of discussion about Arch, Debian, and Fedora (and their various descendant projects), but I rarely see much talk about openSUSE.

Why might somebody choose that one over the others? What features or vision distinguishes it from the others?

Edit: I love all the answers! Great stuff. Thanks to everyone!

42
submitted 1 month ago by [email protected] to c/[email protected]

Now that late spring/early summer is upon us, there's increasingly more headlines about less rain in various places (recent floods notwithstanding). I'm assuming that's because water is evaporating and not returning to those places, but where is it going?

Is it arriving, now, in these bursty flash floods? Is it staying longer in the atmosphere and moving to new locations? Is more of it just staying in the atmosphere period?

22
submitted 1 month ago by [email protected] to c/[email protected]
159
submitted 1 month ago by [email protected] to c/[email protected]

Communicating trauma through art is fine, as long as you don't remind the Christian fundies that their beliefs and practices are a prime source of religious trauma for lots of people.

14
submitted 2 months ago by [email protected] to c/[email protected]
13
submitted 2 months ago by [email protected] to c/[email protected]

On the recent episode of KF #916, Alex's employee halfheartedly promised the world would end. And if that didn't happen, lots of people were allegedly going to be going to the hospital, but nobody at my office seems to be feeling anything but allergies.

Ripped off. I think the folks at Infowars might be charlatans. /s

301
submitted 3 months ago by [email protected] to c/[email protected]

Y'all, this is why you need to vote, including your local races. All an ideology like this needs to grow is fertile ground, a propaganda apparatus to spread it, and a willing legislature.

Vote like your lives depend on it, vote like your families' and friends' lives depend on it, because it very well might.

view more: next ›

Telorand

joined 1 year ago