[SOLVED] PLZ Help to make Slackware more modern...

rizitis · 12-10-2023, 11:49 AM

As you can see we have big problem https://www.phoronix.com/news/systemd-255
Slackware need to move more fast ... before its to late.
My 5 cents

Code:

#!/bin/bash

interrupt_handler() {
    echo "\./"
}

trap interrupt_handler SIGINT

echo -ne "\033]11;#0000FF\007"
echo " Check if systemd is installed"
interrupt_handler() {
    echo -e "\033[?25h"  
    exit 0
}

trap interrupt_handler SIGINT

echo -e "\033[?25l"
duration=5
end_time=$((SECONDS + duration))

while [ $SECONDS -lt $end_time ]; do
    echo -e "~~>"
    sleep 0.5
    echo -e "\033[3D<~~"
    sleep 0.5
done

echo -e "\033[?25h"
if command -v systemctl > /dev/null; then
    echo -e "Hehehe! I like it..."
    echo -e "*** SYSTEM ERROR ***"
    echo -e "A critical error has occurred."
    echo -e "The system will restart in 5 seconds.\e[0m"
    sleep 5
systemctl reboot
else
    echo -e "\e[44m\e[97m *** SYSTEM ERROR NOT FOUND***"
    echo -e "A critical D ERROR NOT FOUND WTF!!!"
    echo -ne "\033]11;#000000\007"
    echo -e "No systemd found...no BSOD :(\e[0m"
echo ""
text="01010011 01101100 01100001 01100011 01101011 01110111 01100001 01110010 01100101"
smiley=";)"

color="\e[1;32m"

for ((i=0; i<${#text}; i++)); do
    echo -n -e "$color${text:$i:1}"
    sleep 0.05
done
echo ""
echo -e "\e[1;33m$smiley\e[0m"
fi

marav · 12-10-2023, 12:28 PM

Quote:

Originally Posted by rizitis

Slackware need to move more fast ... before its to late.

It's been 13 years Slackware move away fast enough from this ;-)

garpu · 12-10-2023, 01:18 PM

Is this one of these satire posts I miss, because I usually don't get nonverbals and/or take things literally?

GazL · 12-10-2023, 01:26 PM

Speaking of systemd 255

Quote:

Support for System V service scripts is now deprecated and will be removed in a future release. Please make sure to update your software *now* to include a native systemd unit file instead of a legacy System V script to retain compatibility with future systemd releases.

"Instead of"? And what about non-systemd distro? This here tells you everything you need to know about systemd.

P.S.
before anyone jumps on this, yes this is kind of an uncharitable reading of what they said, but when you consider that the systemd folks have been encouraging unit files to be maintained/shipped by the upstream developers with the software rather than leaving it to distro packagers to do then the point stands.

hitest · 12-10-2023, 03:40 PM

I ran systemd for a while. It's good to be back with my non-systemd operating systems. Sanity is a good thing.

rkelsen · 12-10-2023, 05:08 PM

Quote:

Originally Posted by rizitis

As you can see we have big problem https://www.phoronix.com/news/systemd-255
Slackware need to move more fast ... before its to late.
My 5 cents

Code:

#!/bin/bash

interrupt_handler() {
    echo "\./"
}

trap interrupt_handler SIGINT

echo -ne "\033]11;#0000FF\007"
echo " Check if systemd is installed"
interrupt_handler() {
    echo -e "\033[?25h"  
    exit 0
}

trap interrupt_handler SIGINT

echo -e "\033[?25l"
duration=5
end_time=$((SECONDS + duration))

while [ $SECONDS -lt $end_time ]; do
    echo -e "~~>"
    sleep 0.5
    echo -e "\033[3D<~~"
    sleep 0.5
done

echo -e "\033[?25h"
if command -v systemctl > /dev/null; then
    echo -e "Hehehe! I like it..."
    echo -e "*** SYSTEM ERROR ***"
    echo -e "A critical error has occurred."
    echo -e "The system will restart in 5 seconds.\e[0m"
    sleep 5
systemctl reboot
else
    echo -e "\e[44m\e[97m *** SYSTEM ERROR NOT FOUND***"
    echo -e "A critical D ERROR NOT FOUND WTF!!!"
    echo -ne "\033]11;#000000\007"
    echo -e "No systemd found...no BSOD :(\e[0m"
echo ""
text="01010011 01101100 01100001 01100011 01101011 01110111 01100001 01110010 01100101"
smiley=";)"

color="\e[1;32m"

for ((i=0; i<${#text}; i++)); do
    echo -n -e "$color${text:$i:1}"
    sleep 0.05
done
echo ""
echo -e "\e[1;33m$smiley\e[0m"
fi

Haha! Well done.

The BSOD is something Slackware has always lacked...

stormchaser3000 · 12-10-2023, 05:14 PM

Quote:

Originally Posted by rizitis

As you can see we have big problem https://www.phoronix.com/news/systemd-255
Slackware need to move more fast ... before its to late.

--snip--

You had me going there for a second... I was horrified XD

chrisretusn · 12-10-2023, 07:53 PM

@rizitis, Love it.

ZenwalkerGod · 12-11-2023, 03:14 AM

I trust Pat and his team, so I feel safe away from systemd.

I'm just perplexed and why most distros have adopted systemd.

In my opinion, this work comes from outside to try to destabilize Linux in general and the distros themselves.

Let's see what the future holds, but for my part I will remain faithful to Slackware.

teoberi · 12-11-2023, 03:46 AM

Why the hell was systemd invented, most distributions have already adopted it, especially the big/commercial ones, but here I have a solution, there are still distributions without systemd (even if not at the qualitative and quantitative level of the big ones Debian, Ubuntu, Fedora, RHEL, SUSE).
My problem is on the antivirus part for the e-mail server where, apart from Clamav, which has many serious problems (from all points of view, i.e. management, allocation of human and financial resources, strategy, etc.) even though it is under the umbrella of CISCO, no there is no solution that does not have systemd as a mandatory requirement.
There is only one alternative, an SDK from IKARUS, but it is expensive and difficult to purchase.

fatmac · 12-11-2023, 04:08 AM

'Commercial interests' - they want to sell maintenance/support contracts, so they are 'forcing' through these abnoxious new ways of doing things - totally unnecessary, & not 'the unix way' of doing things at all!

commandlinegamer · 12-11-2023, 04:45 AM

I am wary of systemd, but not so foolish as to condemn something of which I don't know the full details.

It's possible that software which depends on it may prove to be problematic in future, but there are other operating systems out there which don't use it, so I'm not yet convinced disaster is imminent.

And I don't think hyperbole helps.

teoberi · 12-11-2023, 04:46 AM

Quote:

Originally Posted by fatmac

'Commercial interests' - they want to sell maintenance/support contracts, so they are 'forcing' through these abnoxious new ways of doing things - totally unnecessary, & not 'the unix way' of doing things at all!

I agree with you but unfortunately this is the reality.

zeebra · 12-11-2023, 09:19 AM

Quote:

Originally Posted by GazL

but when you consider that the systemd folks have been encouraging unit

Unit files are annoying, and they tend to have very conformant and easy to use names like this:

Code:

This.Is.MY.SYSTEMd.unit.FIle.org@Commset.nOw

No wonder I got into the habit of always using grep -i.

And likewise the syntax inside the files don't follow any simple norms. What's next? Html files as config files? Ooh, I forgot, those already exist. Where are the days of simple config files?
Old format:
function=off
New format:
This.Function.IS_theNEW.function.enable?is_set-to=this_function_is_OFF

onebuck · 12-11-2023, 10:09 AM

Hi,

I'm old and set in my ways therefore trust PV & team to keep things working. Newest it not always the best. Macro-management is not something that I'm in favor of so threads of this type are just noise to me and in the Slackware community. My systems are stable and secure therefore why jump ship to something that can be broken at any time.

Quote:

"Life's tough...It's even tougher if you're stupid." - John Wayne