to error is human to slack is divine.
 

hi, my name is Robert, and i strayed, for crap and giggles. I tried another variant. omg what a nightmare. when your 3am cursing your laptop because its locking up htop shows no issues and all looks kosher and you can move your mouse about 2 mm every 30 minutes I was like WTF. formatted did a clean install of this other named distro it did it again. on 14.1 slackware64 right now building chromium and thank stars for slackbuilds I looked at getting the source through git, why on earth do you need to check out an arm and a leg to get a tarbal of the latest version?

but i digress, i vow never to stray (well I may do a test build or 2 of lfs just because I want to) if only I could get playonlinux and wine to work seamlessly with a few games I could convert all my boxes to slackware but alas my grandson has some requirements I can not violate and my wife does as well. and honestly there are a couple of my favourite games I haven't gotten to work Yet.

anyway now back to work on getting the box tweaked.

Robert

Praise "Bob"!

I must ask, just what was this other distro? (If you had rather not say, I understand, but I am quite curious.)

I've used Debian, Mint, and Mageia quite happily (though there has always been at least one and usually two Slackware boxes in this house). I used Ubuntu with no complaints (it came factory-installed on two of my machines back when you could easily get factory-installed Ubuntu from Dell) up until Unity compelled me to dis-unite from Ubuntu.

it was kali I think I borked it when I apt-getted some package upgrades cross debian and kali. for an alternate flash package chuckle.

backtrack gave me zero issues when it was based off slack.

kali even coughs for me when I try to virtualbox it on my main pc i7 16 gigs of ram etc.. backtrack always worked.

I just broke my slackbox but since it was new just reinstalling it now it was my fault lesson to me. first never try building chromium, a new kernel at the same time your installing the multilib package and reboot it before you 100% complete the multilib process. bad things happen to x chuckle. at least for me if I was more invested I would have gone on the main pc and tried to solve the answer but its late at night and everyone is sleeping so just redid it what I am typing on now. it currently bumping to current. then going to go through the entire multilib process religiously before i reboot

i've never had an accident on slackware I didn't cause my self, other variations I can not make that claim

okay going to fork this off into another thread I think I got a bug arggg I thought I had it damn it.

I took a look at Kali once in a VM.

Kali is most decidedly not meant for regular use. It's designed strictly for pen(etration) testing and is pretty much unsuitable for anything else. I played with it a bit and decided I was too lazy to learn how to use it, so I gave it up.

Couldn't have been said much better than this.
I use Kali off and on, just to test my own network of course, and I can always get in one way or another.

The point to Kali is that it should be ran as a LiveOS for most uses. Unless of course you have a 'job' pen testing.
It has a faster release cycle just because of that, with about 6 releases a year. Not that they are on version 11 now or anything, but minor releases. In the almost 2 years that it has been known as Kali they have released 11 times, and still on version 1.x.x

And I agree that it was better when it was BackTrack and based on Slackware.
That's from a former Debian user that recently switched!

the way i see it and i decided if I want the pen testing tools I can take the list of what i want, and modify the kernel to my liking and just mod my own Slackware distro.

I've used Kali like os's since phlak was around. I use them for pen-testing and learning on my own network. but hate being spoon fed. but overall what i must have is a stable os I can trust chuckle. hence why I made my post.

I started with Slackware. It was an accident, but quite a happy one, because, when you understand Slackware, no other distro will ever intimidate you. That doesn't mean you will understand Slackware at first; it means that Slackware teaches you how to figure stuff out. Figuring stuff out is an important skill.

Wherever I wander, I end up back at Slackware, because it is the distro of iron: it always works and never breaks. Debian, though, is a one fine distro; it's my second favorite after Slack.

IMO, it WAS one fine distro. I started having major issues with it after using it for ~15 years. So where else could I go but to Slackware? Now I cant see myself leaving, unless I start having the same problems.

Although.....
Devuan looks promising.