[-] xcutie@linux.community 9 points 1 month ago

Dicky McDickface

1
submitted 3 months ago by xcutie@linux.community to c/debian@lemmy.ml
[-] xcutie@linux.community 3 points 3 months ago

That's just like your opinion, man!

[-] xcutie@linux.community 14 points 3 months ago

Sure they could, but why would they?

[-] xcutie@linux.community 6 points 4 months ago

We all are high down here. Yes, we are!

[-] xcutie@linux.community 10 points 4 months ago

My dog is neutered

[-] xcutie@linux.community 26 points 5 months ago

Is this "Don't be evil!"?

[-] xcutie@linux.community 8 points 7 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 3 points 10 months ago

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

[-] xcutie@linux.community 1 points 11 months ago

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

[-] xcutie@linux.community 2 points 11 months ago* (last edited 11 months ago)

Joe - just for quick edits on a text file

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

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.

[-] xcutie@linux.community 2 points 1 year ago

IceWM. Just the bare minimum I need. But nothing more.

view more: next ›

xcutie

joined 1 year ago