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.
I just chose to go with another distro that sets up a wifi network right out of the box.
Like Debian and Ubuntu.
Are you sure about that? Wireless works out-of-the-box on Debian? Perhaps if one is lucky, but most, if not everyone, who uses wireless must do more work to get it working than Slackware users do. (Proprietary drivers are not included in Debian's official repositories.)
Quote:
Originally Posted by Richard Cranium
As a Slackware user, why would I give a rat's ass what debian provides?
In debian the startx app is in the xinit package. And you need a manually created ~/.xinitrc file to execute the window manager you intend to use.
exec cwm
Or whatever applies. It's not rocket science and most of it is well documented.
Each window manager package in Slackware includes a ready made xinitrc file. All the user has to do is select the WM they want to use by running the 'xwmconfig' dialog. The root user can also run the exact same dialog to change the system-wide default window-manager used by users who haven't made an individual choice. Seriously, anyone who finds this difficult needs to take their computer back to the shop and ask for a refund on the grounds that "They're too stupid to own a computer and should never have been sold one."
To be fair, there are certain aspects of Slackware that can be a bit of a challenge: this isn't one of them.
And don't forget pkgtool for making changes to network setup, default DE/WM, etc. From its man page:
Quote:
Pkgtool can also be used to re-run the menu-driven scripts normally executed at the end of a Slackware installation. This is useful for doing basic reconfiguration
As a Slackware user, why would I give a rat's ass what debian provides?
Because the naming convertions are likely the same or at least similar. But if typing random words and pushing enter on the command line until something interesting happens is your thing, then more power to you.
Keep in mind that most of the work that Pat has done in order to make Slackware compatible with UEFI came from the Debian folks.
The more you know...
The grub2 script that I modified for Slackware most certainly came from Debian; that's not the issue.
It annoys me to no end to have users of other distributions give advice in this forum using tools and procedures that are applicable to their distribution but not to Slackware, apparently without even realizing that what they wrote doesn't apply.
I don't attempt to provide advice in the Debian/RedHat/Centos forums since I know that I don't know enough about how those distributions work to effectively do so.
In retrospect, it may very well be that the person to whom I so testily replied believes that it is blindingly obvious that what works in Debian won't necessarily work as such in Slackware and so didn't bother to point it out.
It annoys me to no end to have users of other distributions give advice in this forum using tools and procedures that are applicable to their distribution but not to Slackware, apparently without even realizing that what they wrote doesn't apply.
So you're saying that using startx and having a ~/.xinitrc does work AT ALL in slackware? As implied by commenting that it doesn't apply.
Sure, various distros have methodologies that may not be known by all, even those who use that distro. And those methodologies may not apply if you venture from the pavement by grabbing a source package not provided by the distro. Also bear in mind that not all threads originate in the forums they end up in.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.