A nice tool "hypnotix", an M3U IPTV player and there are even SlackBuild for it there :
https://github.com/mxnt10/Slackware15-Reposity

1 members found this post helpful.

I have a problem with my testing installation Slackware 15:

The installation went perfect, but after reboot; it aprered some grub text!
i installed Lilo on the parttion; then i had to instll it on the MBR!

I never use grub!

PD:
the other thing is with Slackpkg, it is not working correctly.

# slackpkg update returns nothing!

thanks.

This is the wrong thread for installation problems. It sounds like grub was in your mbr and since you first tried installing lilo to the partition (why??) it did not overwrite the grub in the mbr. When you installed lilo to the mbr, it did overwrite grub there. For slackpkg : did you check that you had a working connection to internet and did you uncomment one (and only one) mirror in /etc/slackpkg/mirrors file, are you doing this with root account, su or sudo?

a good advice for clean installs:

zero out your MBR before partitioning the drive.

NOTE:
Know what you do, train on unimportant data first!

1 members found this post helpful.

linux-firmwares , compressed (we save 400 megabytes of hdd space under firmwares folder)

https://www.linuxquestions.org/quest...ml#post6323257

https://www.linuxquestions.org/quest...ml#post6323271

Thank you fourtysixandtwo for posting the info about the install.log
I have had slackpkg+ installed on all my systems for a while now and have been ignorant of this very useful log.

BTW neither the slackware package contents of slackpkg+ [ /var/log/packages/slackpkg+-1.7.10-noarch-1mt ] or the man page for slackpkgplus.conf mention the install.log
I did find it in the doc README [ /usr/doc/slackpkg+-1.7.10/README ]

I just looked through ~/tools/ which is where I download third-party software to build/install myself, looking for anything I'd like to have Pat start including in Slackware, but none of it made the grade. I'd rather he focused on what Slackware already has, and kept it up-to-date and free of bugs and security vulns. The rest of this stuff, I'll keep installing/troubleshooting myself.

One thing, though, I'd love it if Slackware started including sbotools or sbopkg (or both, if you don't want to play favorites).

I've asked for this before, and was told it wouldn't happen, but wanted to mention it anyway just to keep the idea alive. I have friends for whom the lack of a yum/apt-get like for Slackware unofficial packages is a sticking point for trying Slackware. Right now my tentative plan is to make USB install media for them, with sbopkg and a few other goodies added in (like packages for palemoon and java, and some of my own tools), when Slackware 15.0 is released.

On a tangental note, I worry that Patrick isn't monetizing Slackware enough. The Patreon is doing okay, but not great. If he has to take another job to help pay the bills, the time between Slackware releases will only take longer.

Maybe he has some kind of plan to drive new users to the Patreon when Slackware 15.0 is released? That would be a big load off my mind.

4 members found this post helpful.

You could have a look at GUIX, it's a package manager (and a distro too) that can be installed on most GNU/Linux systems, and it automates package management. It's not a normal package manager either, if you install it in Slackware it will seperate itself and the installed packages from the rest of the system, as far as I understand.

It's probably not so easy to install, but if you or your friends want easy access to packages on Slackware it's something to consider.

Provide as metadata runtime dependencies of each package, maybe assuming that a minimum set of packages (core system) be installed. This information could be included in PACKAGES.TXT like when this file is completed to be used by slapt-get.

Rationale: help folks not wanting a full Slackware installation to expand the system and keep it up to date.

The difficulty being that if built on top of a full installation, the packages will include optional dependencies, so ideally these dependencies would be could computed while building Slackware From Scratch or something like that?

If not for Slackware 15.1, maybe later...

gnu-unifont from SBo would be a nice addition. I really like the idea of having a near-universal fallback font for terminal emulators.

1 members found this post helpful.

I've been thinking to myself, that it would be nice / useful if those were included in something like /extra/third-party-pkgtools

just a thought anyway.

Of this I have no doubt. After all, it's a well-known fact that Pat views us--the Slackware user-base--as sheep to be driven hither and thither.

In case the sarcasm of my previous statement wasn't obvious, let me put it another way: if you are of the opinion that an OS should drive the users--instead of the other way around--I'd suggest iOS or android... Then, one's mind could be unloaded even more! ;-)

2 members found this post helpful.

I know this is a really bad idea from a security stand point. But since Slackware doesn't make a user account during install it would be nice if the installer would give you an option to add "PermitRootLogin yes" to sshd_config so that it would be possible to ssh into a fresh Slackware install. If any one comments that this is a terrible idea I will not argue, but it's not unheard of. Red Hat derivatives have PermitRootLogin in their default installs.

3 members found this post helpful.

As long as it is disabled by default, and requires user interaction to enable it - then in principle I have no real objections - along with of course an obligatory warning next to the option.

1 members found this post helpful.