And:

(or reboot)

Well all theses tasks are performed for you if the author of this thread ran

True.

It must also be said that the installation process does run netconfig.

should have installed wicd it's in the extras directory

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.

Sometimes, the wireless antenna of your computer is disabled by a hazardous Windows driver or a borked install of a GNU/Linux distro.

One might want to run

in order to get it working again.

Fixed: Command typo. Thanks to schmatzler.

As a Slackware user, why would I give a rat's ass what debian provides?

1 members found this post helpful.

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.)

Nice comeback.

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.

It think you refer to

And don't forget pkgtool for making changes to network setup, default DE/WM, etc. From its man page:

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.

I would not be as radical as you on that.

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.

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.