xcutie

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

Frag mal deine Großeltern. In deren Jugend hat ein Döner nur 2 Reichsmark gekostet.

[–] xcutie@linux.community 14 points 11 months ago

Sure they could, but why would they?

[–] xcutie@linux.community 10 points 11 months ago (1 children)

My dog is neutered

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

Hollies - Long dark road?

[–] xcutie@linux.community 26 points 1 year ago (5 children)

Is this "Don't be evil!"?

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

Ultima Underworld 1

Baldur's Gate 2

[–] xcutie@linux.community 8 points 1 year 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 1 year ago

Birds aren't real!

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

Joe - just for quick edits on a text file

[–] xcutie@linux.community 1 points 2 years 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 8 points 2 years ago* (last edited 2 years 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 ›