▲ 47 ▼ What's your favourite "just works, day after day" Linux software? (lemdro.id) submitted 4 months ago by cm0002@lemdro.id to c/linux@programming.dev 38 comments fedilink hide all child comments
[–] Tja@programming.dev 20 points 4 months ago (8 children) Those a fighting words permalink fedilink source parent hideshow 8 child comments replies: [–] shrugs@piefed.social 12 points 4 months ago (7 children) here you go: systemd is so much better then sysv-init, it's not even funny I really can't take people serious that think sysv-init was the superior system. I mean for real, have you ever worked with it and all it's shortcomings? It wasnt even a system, it was a bunch of bad init scripts permalink fedilink source parent hideshow 7 child comments replies: [–] Tja@programming.dev 5 points 4 months ago It was a bunch of bad init scripts, but it was our bunch of bad init scripts. permalink fedilink source parent [–] terabyterex@lemmy.world 3 points 4 months ago i started my professional software development career in 1999. the amount of older guys who called the web stupid and a fad or "gopher is the future of the internet" was crazy. people hate change permalink fedilink source parent [–] sage@lemmy.blahaj.zone 2 points 4 months ago (2 children) Nobody argued that sysv was better. Just that there are other options, apart from systemd. permalink fedilink source parent hideshow 2 child comments replies: [–] Mountainaire@lemmy.world 1 point 4 months ago (1 child) And yet you refuse to give examples... permalink fedilink source parent hideshow 1 child comment replies: [–] sage@lemmy.blahaj.zone 1 point 3 months ago I use OpenRC on my desktop. permalink fedilink source parent [–] ZombieCyborgFromOuterSpace@piefed.ca 1 point 4 months ago (1 child) I've been using it since I started using Linux 26 years ago until Ubuntu switched to upstart and then systemD. It did the job and was very easy to work with. I knew what the scripts did and I could write my own. And it didn't ask for a date of birth either. permalink fedilink source parent hideshow 1 child comment replies: [–] shrugs@piefed.social 1 point 4 months ago funny, I also started around 2000 with Linux, so we have the same time under our belt. I remember doing manually dependency resolving downloading packages from freshmeat.net Let's be honest, I hated that "/etc/init.d/apache2 start" went obsolete, muscle memory and habit are a bitch, but you have to move on sometimes. Otherwise, are you really arguing that some obscure start-stop-daemon wrapper that sometimes worked and sometimes didn't, because they were created for suse not redhat were superior? systemd monitors the daemons, can show you used cpu time, can start daemons depending of if the system is connected to ac or uses battery or if a port got a magic package, it know which resources a service needs and much more, all without needing to manually write scripts. Do we really compare that to some scripts with bullshittery like: case $1 in start): start-stop-daemon $service_name ;; *) echo fuck off exit 1 ;; sorry to be so blunt, and im pretty drunk saying this: sherly you can't be serious, and don't call me sherly. permalink fedilink source parent
[–] shrugs@piefed.social 12 points 4 months ago (7 children) here you go: systemd is so much better then sysv-init, it's not even funny I really can't take people serious that think sysv-init was the superior system. I mean for real, have you ever worked with it and all it's shortcomings? It wasnt even a system, it was a bunch of bad init scripts permalink fedilink source parent hideshow 7 child comments replies: [–] Tja@programming.dev 5 points 4 months ago It was a bunch of bad init scripts, but it was our bunch of bad init scripts. permalink fedilink source parent [–] terabyterex@lemmy.world 3 points 4 months ago i started my professional software development career in 1999. the amount of older guys who called the web stupid and a fad or "gopher is the future of the internet" was crazy. people hate change permalink fedilink source parent [–] sage@lemmy.blahaj.zone 2 points 4 months ago (2 children) Nobody argued that sysv was better. Just that there are other options, apart from systemd. permalink fedilink source parent hideshow 2 child comments replies: [–] Mountainaire@lemmy.world 1 point 4 months ago (1 child) And yet you refuse to give examples... permalink fedilink source parent hideshow 1 child comment replies: [–] sage@lemmy.blahaj.zone 1 point 3 months ago I use OpenRC on my desktop. permalink fedilink source parent [–] ZombieCyborgFromOuterSpace@piefed.ca 1 point 4 months ago (1 child) I've been using it since I started using Linux 26 years ago until Ubuntu switched to upstart and then systemD. It did the job and was very easy to work with. I knew what the scripts did and I could write my own. And it didn't ask for a date of birth either. permalink fedilink source parent hideshow 1 child comment replies: [–] shrugs@piefed.social 1 point 4 months ago funny, I also started around 2000 with Linux, so we have the same time under our belt. I remember doing manually dependency resolving downloading packages from freshmeat.net Let's be honest, I hated that "/etc/init.d/apache2 start" went obsolete, muscle memory and habit are a bitch, but you have to move on sometimes. Otherwise, are you really arguing that some obscure start-stop-daemon wrapper that sometimes worked and sometimes didn't, because they were created for suse not redhat were superior? systemd monitors the daemons, can show you used cpu time, can start daemons depending of if the system is connected to ac or uses battery or if a port got a magic package, it know which resources a service needs and much more, all without needing to manually write scripts. Do we really compare that to some scripts with bullshittery like: case $1 in start): start-stop-daemon $service_name ;; *) echo fuck off exit 1 ;; sorry to be so blunt, and im pretty drunk saying this: sherly you can't be serious, and don't call me sherly. permalink fedilink source parent
[–] Tja@programming.dev 5 points 4 months ago It was a bunch of bad init scripts, but it was our bunch of bad init scripts. permalink fedilink source parent
[–] terabyterex@lemmy.world 3 points 4 months ago i started my professional software development career in 1999. the amount of older guys who called the web stupid and a fad or "gopher is the future of the internet" was crazy. people hate change permalink fedilink source parent
[–] sage@lemmy.blahaj.zone 2 points 4 months ago (2 children) Nobody argued that sysv was better. Just that there are other options, apart from systemd. permalink fedilink source parent hideshow 2 child comments replies: [–] Mountainaire@lemmy.world 1 point 4 months ago (1 child) And yet you refuse to give examples... permalink fedilink source parent hideshow 1 child comment replies: [–] sage@lemmy.blahaj.zone 1 point 3 months ago I use OpenRC on my desktop. permalink fedilink source parent
[–] Mountainaire@lemmy.world 1 point 4 months ago (1 child) And yet you refuse to give examples... permalink fedilink source parent hideshow 1 child comment replies: [–] sage@lemmy.blahaj.zone 1 point 3 months ago I use OpenRC on my desktop. permalink fedilink source parent
[–] sage@lemmy.blahaj.zone 1 point 3 months ago I use OpenRC on my desktop. permalink fedilink source parent
[–] ZombieCyborgFromOuterSpace@piefed.ca 1 point 4 months ago (1 child) I've been using it since I started using Linux 26 years ago until Ubuntu switched to upstart and then systemD. It did the job and was very easy to work with. I knew what the scripts did and I could write my own. And it didn't ask for a date of birth either. permalink fedilink source parent hideshow 1 child comment replies: [–] shrugs@piefed.social 1 point 4 months ago funny, I also started around 2000 with Linux, so we have the same time under our belt. I remember doing manually dependency resolving downloading packages from freshmeat.net Let's be honest, I hated that "/etc/init.d/apache2 start" went obsolete, muscle memory and habit are a bitch, but you have to move on sometimes. Otherwise, are you really arguing that some obscure start-stop-daemon wrapper that sometimes worked and sometimes didn't, because they were created for suse not redhat were superior? systemd monitors the daemons, can show you used cpu time, can start daemons depending of if the system is connected to ac or uses battery or if a port got a magic package, it know which resources a service needs and much more, all without needing to manually write scripts. Do we really compare that to some scripts with bullshittery like: case $1 in start): start-stop-daemon $service_name ;; *) echo fuck off exit 1 ;; sorry to be so blunt, and im pretty drunk saying this: sherly you can't be serious, and don't call me sherly. permalink fedilink source parent
[–] shrugs@piefed.social 1 point 4 months ago funny, I also started around 2000 with Linux, so we have the same time under our belt. I remember doing manually dependency resolving downloading packages from freshmeat.net Let's be honest, I hated that "/etc/init.d/apache2 start" went obsolete, muscle memory and habit are a bitch, but you have to move on sometimes. Otherwise, are you really arguing that some obscure start-stop-daemon wrapper that sometimes worked and sometimes didn't, because they were created for suse not redhat were superior? systemd monitors the daemons, can show you used cpu time, can start daemons depending of if the system is connected to ac or uses battery or if a port got a magic package, it know which resources a service needs and much more, all without needing to manually write scripts. Do we really compare that to some scripts with bullshittery like: case $1 in start): start-stop-daemon $service_name ;; *) echo fuck off exit 1 ;; sorry to be so blunt, and im pretty drunk saying this: sherly you can't be serious, and don't call me sherly. permalink fedilink source parent