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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,167
Rep:
Quote:
Originally Posted by USUARIONUEVO
Hi , i think linux 5.16.x go to EOL soon , then i request a start testing config for linux 5.17
Thanks!
The 5.17.0 kernel won't be released for another week or two and at that time Mr. Volkerding may elect to add it to -current. However, if the kernel developers follow the same pattern as they have in the past, the 5.16.y series won't go End Of Life until the 5.17.y series has been out for four or five weeks.
Last edited by cwizardone; 03-06-2022 at 03:17 PM.
The 5.17.0 kernel won't be released for another week or two and at that time Mr. Volkerding may elect to add it to -current. However, if the kernel developers follow the same pattern as they have in the past, the 5.16.y series won't go End Of Life until the 5.17.y series has been out for four or five weeks.
Im not request inclusion of 5.17 , we have in the past configs for testing from rc series , *only configs , for people want start test the next stable branch under official config.
It build, but, with '--disable-network-build' option.
Just re-read, hopefully the avahi library will allow network capability, cause my printer is indeed a network printer, not connected to any computer but via ethernet to my router; so --disable-network-build might be a problem for me.
Just re-read, hopefully the avahi library will allow network capability, cause my printer is indeed a network printer, not connected to any computer but via ethernet to my router; so --disable-network-build might be a problem for me.
I very much hope hplip will be well supported on SBo including avahi, because
i very much hope that avahi won't sneak in slackware.
Avahi will link to various other packages and then can't simply uninstalled if disliked.
I guess avahi was never raised as a request, it just tries to be unavoidable.
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 462
Rep:
No non-third-party packages off the top of my head, sorry. I found out that libboost_fiber was gone when I was trying to build hhvm from the slackbuilds.org master branch.
I very much hope hplip will be well supported on SBo including avahi, because
i very much hope that avahi won't sneak in slackware.
Avahi will link to various other packages and then can't simply uninstalled if disliked.
I guess avahi was never raised as a request, it just tries to be unavoidable.
It is unfortunate, since even the likes of LibreOffice and vlc requires it - but that is not really an issue when you can build avahi yourself - now HPLIP requires it too, hopefully the library of avahi is enough, and that network capability still works - again at least that is the 'work-around', building just a library supposedly.
(Known Issues
These are patches from library authors which were found too late to be fixed in the release.
Boost.Build silently skips installation of library headers and binaries in some cases, see #104.
Fixed in PR#113, patch.
Boost.Atomic fails to build when targeting UWP, see #54. Patch.)
Add a section for GRUB configuration. Checking Slackware-HOWTO in both --current and 15.0 and there is really nothing for GRUB not even basic info / setup at least:
Quote:
4. Installing the Slackware distribution
4.1 The ADDSWAP option
4.2 The TARGET option
4.3 The SOURCE option
4.4 The SELECT option
4.5 The INSTALL option
4.6 The CONFIGURE option
4.7 LILO
4.8 Networking
Speaking of GRUB, (if someone can help Pat) , add an option during the install to provide a choice, install GRUB or LILO - or GRUB or ELILO (for UEFI). Just a thought.
Add a section for GRUB configuration. Checking Slackware-HOWTO in both --current and 15.0 and there is really nothing for GRUB not even basic info / setup at least:
Speaking of GRUB, (if someone can help Pat) , add an option during the install to provide a choice, install GRUB or LILO - or GRUB or ELILO (for UEFI). Just a thought.
FYI
Pat has already expressed his (future) interest in Didier Spaier "Slint" Grub config (in the changelog)
Code:
Wed Jan 12 22:04:33 UTC 2022
...
If your requests didn't make it
into this iteration, perhaps we will revisit them for the next -current cycle.
Some were just a little too late but will more than likely be needed next time
(I'm looking at Didier's grubconfig)
FYI
Pat has already expressed his (future) interest in Didier Spaier "Slint" Grub config (in the changelog)
Code:
Wed Jan 12 22:04:33 UTC 2022
...
If your requests didn't make it
into this iteration, perhaps we will revisit them for the next -current cycle.
Some were just a little too late but will more than likely be needed next time
(I'm looking at Didier's grubconfig)
That partially answers my request, but then again I assume once GRUB is potentially added to the installer as an option; the update to the howto will obviously follow accordingly anyways.
Tangent: Speaking of the installer, I still rather hoped that the outputs will still be changed - in terms of either choosing menu or expert - they are both exactly the same, so I still think either one (probably menu) , should be removed - if not at least the output should be changed to terse as it seems to be slightly accelerating the speed of the install.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.