SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
@LuckyCyborg You are excused I'm not too interested in a big back and forth on the issue, but I stand by disqualifying graphical root logins as basically a good thing™. Up to the Slackware people what they want to do about it.
This is a pretty minor thing, however on every package update it is easy to overlook it: would it be possible to add a bash completion symlink creation step to the git package?
Something on the line of:
Hello,
lrzip and minicom both install usr/bin/lrz but the two commands are very different and should be kept away from each other.
I fixed the minicom slackbuild, but my patch may be too drastic.
Regards,
And WHY you claim that @ZhaoLin1457 said that phrase, when just I've written it?
I have no idea what happened there - i made the [snip] and fired the [enter] key and now its there - I am amazed and confused the same as you
But, yeah, I don't like where the whole Open Source/Free Software community is heading to - lack of sanity and too much self confidence for my taste on way too many places.
Perhaps that comes for a reason - back in the day one had to do quite substantial amount of footwork before even standing a chance to make any reasonable code - nowdyas all one has to do is install a suite; enable few plugins mirror a repo out there and just start tweaking/twiddling an half baked project on and on...
Back in the day people started from the ground - nowdays it seems as if newbies stat from high above the clouds already, and it shows IMHO.
@LuckyCyborg You are excused I'm not too interested in a big back and forth on the issue, but I stand by disqualifying graphical root logins as basically a good thing™. Up to the Slackware people what they want to do about it.
Excuse my ignorance, but what happened with that old adagio, how it was?
"Slackware makes absolutely no assumptions about how you use the system"
From this to fully blocking the most powerful user to use a particular desktop environment as he/her likes is a long way, isn't?
I think that's one thing to recommend, to explain, to educate that some actions may be dangerous and it is entirely another thing to lock down software.
I've just tested "startkwayland" as root. This Wayland/Plasma5 did not even start as root, even it works well as a regular user.
So, I ask you:
who is the owner of my own computer? Me or Slackware?
Excuse my ignorance, but what happened with that old adagio, how it was?
"Slackware makes absolutely no assumptions about how you use the system"
I have no horse in this race (I don't start WMs/DEs as root, but don't really care if other people want to), but there's also the Slackware tries to ships packages as upstream intends and as such, Pat tries to minimize patching the source.
Yes, he's patched kate and konqueror (or was it dolphin or both, I can't remember) to allow root usage, but opening single GUI applications as root are a far cry from a whole WM/DE. The potential security implications are far higher running everything as root compared to a single program here or there.
Quote:
Originally Posted by ZhaoLin1457
who is the owner of my own computer? Me or Slackware?
You definitely are the owner of your computer, which means that if Pat decides to not patch Plasma5 for this, you're welcome to do it yourself.
Please consider a built-in Slackware way for a user ~/.xsession-errors file. I think Slackware is the only distro I have used not directly supporting the log file. Perhaps the file could be user-defined and enabled/disabled in /etc/default/xsession-log or something similar. Possibly using /etc/xprofile. Or in an /etc/X11/Xsession file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I'm not too interested in a big back and forth on the issue, but I stand by disqualifying graphical root logins as basically a good thing™. Up to the Slackware people what they want to do about it.
