ping Transhour (and RedDog, too)
- Glad to see you're still about and growing. I haven't tried Antergos but I worked in Arch for several months and it is decent and certainly far more free than Ubuntu. I just bought a Thinkpad T61 through eBay for really cheap (Joanna Rutkowska's recommendation for best security at hardware level) wiped Vista Business and installed 14.2 (took 15 minutes) and it is truly a work of Science and Art. My main box is still 14.0 and with years of work on it I am slow to change it. I just haven't felt a compelling need to upgrade it since everything still works so well. However 14.2 is definitely a step up so I probably will soon. I'm very pleased with KDE Plasma 5 since they got the resources properly sorted even by default. Runs great even with just a Core 2 Duo 2 GHz and 4GB ram. It does have a decent Quadro graphics system and the 340.96 I installed just with nVidia's script works magnificently.
If you have any interest in seeing the advances in Slackware, the new Live version takes very little time and effort and is excellent.Hello Red_Dog
Originally Posted by _Red_Dog_
I am slowly and slowly inching my bum towards slackware as with years that weird girl becomes more and more attractive in theory lolol.
Jokes aside, I figured I'd ask OCN's slackman himself -
My biggest fear is slackbuilds. Has anyone ported something like zenwalk's pkg manager to Slack at least unofficially? Or is still manual dependency resolution?
Although I'm not really OCN's Slackman, just more vocal perhaps, it's good to hear you have an interest in "the weird girl" LOL. She may be kinky but she's straightforward
Slackbuilds are truly not to be feared. They are a case of making things easier with no detriment to the basic concept that the Base OpSys is sacrosanct and should never be at risk.. This is because all they do is automate the compile process from source and install it to /tmp where you can decide to go ahead and complete (installpkg) or not. The few that require it, list any dependencies.
I do understand that since almost every other distro uses auto dependency resolving that it seems fearful to the outsider but it is really a net gain given the way in which releases are built assuming one opts for the recommended full install. There just are very few dependencies not already in the system and those are all painstakingly assembled to work together. This is partly why Slackware doesn't release as many upgrades (aside from -Current/testing) as others, but the result is a fully integrated system that never requires deep maintenance.
However to answer your pointed question directly, Yes there are at least 2 x 3rd Party developers of management software addons that handle dependencies. I actually don't know much about them because I don't see the need and prefer the "solid as a rock" benefit of having absolutely nothing done "behind my back" so I know instantly what went wrong on the extremely rare occasion that anything does which always consists solely of a new app not running the way I want it to. It is trivial to then go back and fix that, taking just a few minutes. Anyway I only even know of their existence because i see posts about them on LQN Slackware section. In their defense, they very often are marked "Solved" in just a day or two. I still have zero interest.
Originally Posted by _Red_Dog_
Also are there any issues with slack's LILO and deploying it inside VMs like behyve or SmartOS's kvm? because it seems I should be able to easily gear it using the initial installation, than ssh change few files and never ever touch it again ^^
I use VMs as little as possible but I am an exception so I'm not 100% certain but I see no reason for any problems based on two things - LILO is so simple and basic it is both it's strength and weakness. It is only weak in that it appears that it is stagnant but that is only because there is no need to reinvent the wheel. It just works and is trivial to configure how the user wishes. It's only drawback is that I can see is that it isn't as amenable to boot splash screens but I prefer watching the notifications of kernel loading anyway. 14.2 comes with grub installed but not activated by default now.. So if lilo doesn't twirl ur beanie, grub will.
Originally Posted by _Red_Dog_
*reason why I ask is because I looked at slack's installation and it seems to use batches of packages and you can kinda mix/match that to make a "server for you" type of thing. Which is very interesting. But maybe I am not understanding something O_o
You seem to understand quite correctly. Slackware in more than just one way is THE MOST VANILLA LINUX available as an actual distro anyone can get. I don't consider Linux From Scratch a true distro since everything is totally up to you. I vastly prefer the philosophy and guiding principles of Patrick Volkerding in never pre-supposing what anyone wants to use Slackware for. He only assumes everyone wants a well-integrated system that someone with 20+ years of experience at extremely deep levels who is willing to put devastating man/hours into for very little recompense beyond pride in a beautiful product. Yes, users like me do donate and buy Tshirts and Hoodies (how can one resist a Slackware 1337 shirt?) but he ain't exactly gettin' rich if you catch my drift. It is a labor of love and beauty.
Another important aspect to consider is that Documentation is superb and the level of active help is of extreme high quality for several reasons, the most important is probably because so many users are very long time users (well in excess of 10 years) , are people that do the work at deep levels because they prefer that, and reflect the love and dedication that builds Slackware and a philosophy that resists change for change's sake. This last thing is important to anyone who uses his PC a lot since there just isn't an ever present steep learning curve. Once you have the basics down you can trust those to continue to work for decades. and I'm not only talking about systemd, which still has no place in Slackware.
Just as I mentioned to Transhour the Live version is extremely good and a full working system, not just a preview. That said, nothing succeeds like commitment and all that is required to get started is free space of 20GB or more, and to download an iso and install it. The installer is the same installer that has been used for decades and simplicity itself - perfectly straightforward and step-by-step.
If you'd like, check out this video on a network install of Slackware employing only the Disk 1 (Install) from a new user's perspective. It's a bit slow as it is on an old P4 system and I disagree with his choice to not install KDE but it does show the easy process. It is actually even easier to install Full Recommended since you don't have to bother with deselecting all the drivers and WM/DEs that he goes through.. Deselecting ONLY diminishes hard drive space since the USER determines any extra running services (about 18 minutes into video). Slack is not a "kitchen sink" resource hog like many distros are. This why it is still so fast (apart from internet install) once installed. Note that initially his system takes awhile because he uses an initrd (not required except on encrypted systems) and has an ancient 40GB PATA hard drive.. There are much faster videos but this guy had never used Slackware before and makes choices on-the-fly so I figured you'd like to see worst case. He even makes the mistake of relying on the VESA graphics driver which is painfully slow.Installing Any Slackware - New user
Hope you give it a shot and certainly let us all know if you do or ever need any help.
. .Edited by enorbet2 - 7/10/16 at 6:07pm