xcutie

joined 1 year ago
[–] xcutie@linux.community 1 points 6 months ago* (last edited 6 months ago)

Ultima Underworld 1

Baldur's Gate 2

[–] xcutie@linux.community 8 points 8 months ago

Would it not just be the easiest way to put your scripts under /etc/network/if-up.d/? Then they get run once that connection is brought up.

[–] xcutie@linux.community 0 points 10 months ago

Birds aren't real!

[–] xcutie@linux.community 3 points 11 months ago (2 children)

Ziemlich guter Podcast zu dem Mord an Burat Bektas ist vom RBB "Wer hat Burat erschossen?"

[–] xcutie@linux.community 1 points 1 year ago

I guess lately no press is good enough press for them.

[–] xcutie@linux.community 2 points 1 year ago* (last edited 1 year ago)

Joe - just for quick edits on a text file

[–] xcutie@linux.community 1 points 1 year ago

I just debuged it like every other of my scripts that failed. Again, I didn't need any special knowledge of the init process, just general (and for me: very limited) knowledge.

The answer to your other questions: I don't thing I ever did that.

[–] xcutie@linux.community 6 points 1 year ago* (last edited 1 year ago) (6 children)

I find everything so complicated with systemd.

SysV was just intuitive for me and my knowledge. There was just one directory with all the startup scripts in it. And they were run in their alphanumerical ordner. Just that simple. If I wanted to change the order in which the scripts started, I just had to rename the file. You don't want a script to run at all? Just remove it.

I assume, systemd has many advantages for a knowledged user. But for me, it still is just a hassle.

view more: ‹ prev next ›