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.
@vtel57 should you wish to "re-activate" but not sure where to start editing or make clarification on errors i know exist, may i mentioned this contribution :
The idea is that its complementary "attempt" of an explanation of what goes on in a SlackBuild mainly aimed at less tech/able people (like myself) to complement a real life slackbuild that can be downloaded:
Hi @vtel57 thanks for reply. Eric set me straight at the beginning rather embarrassingly with English (i'm English he's not ) and syntax. Apart from that i'm the only contributor.
I did it after reading through template for slackbuild, trying to understand it and applying it to do a SlackBuild for Latex2html which i submitted.
it should really not be a "how to " since now you don't really write a SlackBuild anymore just adapt a SlackBuild template. Thus it was meant to be an explanation to go with the SlackBuild you can find on slackbuilds.Also that its meant for people like myself.
As you can see from my rating I don't have much ability but when I was trying to get my latex2html accepted I couldn't find an up todate explanation and i noted in the docs.slackware.com the line
"Who can help? Anyone can, from your uncle Ed who tinkers with Slackware on his old laptop to Linux gurus with development level skill sets." which i interpreted as, it doesn't matter if your not that able or clever your welcome and can still contribute.
There is a section which I tried to interpret but am probably wrong, which means there may be erroneous material. I did put a shout out to editors last line of
it should really not be a "how to " since now you don't really write a SlackBuild anymore just adapt a SlackBuild template. Thus it was meant to be an explanation to go with the SlackBuild you can find on slackbuilds.Also that its meant for people like myself.
That was a good write up. Enjoyed reading it.
I am one of those who does write my own scripts. Of course I started out using the SlackBuild scripts and SBo scripts before I branched out to do my own. I wanted some extras that SBo scripts don't and can't provide, plus my build environment is also different that SBo's.
"Who can help? Anyone can, from your uncle Ed who tinkers with Slackware on his old laptop to Linux gurus with development level skill sets." which i interpreted as, it doesn't matter if your not that able or clever your welcome and can still contribute.
There is a section which I tried to interpret but am probably wrong, which means there may be erroneous material. I did put a shout out to editors last line of
In the beginning, we had quite a few active editors to screen submissions. Nowadays, though, it's pretty much Eric H. and myself... and I've been somewhat remiss about keeping an eye on things there.
As Chris says above, I read your article and thought it to be quite well done. A long time in the past, I attempted a few SlackBuilds "from scratch", but I found that most SlackBuilds I needed on my system were already in existence, so I didn't bother anymore. For this reason, I cannot second guess your thesis on its technical merits. E. Hameleers or R. Workman or others are going to be MUCH more qualified to check on it for you. I'm good at grammar/spelling/punctuation. If there is erroneous information in the article, it's going to require a smarter person than I to detect and edit it.
On a submission-driven wiki like docs.slackware.com, there's always going to be some information submitted that's not necessarily accurate. It happens. Editors are supposed to catch it and correct it.
Anyway, all's well for the moment.
Have a great weekend! #Stay_Healthy!
Last edited by vtel57; 06-19-2020 at 09:17 AM.
Reason: Amended ~Eric L.
the erroneous material is i think my explanation :
If i understand the above block of code correctly its using the “find” on the basis of permissions and following symbolic links using the “-L flag”. If i understand this correctly its basically setting directories to 755 in order to enable a “cd” into them and files so that root can read write. If this is true I might have expected
Is there a way to get notified of new submissions to SlackDocs? I like reading contributions to it, but there aren't enough for me to add the site to my daily sites to check, because after so long without updates, I'll forget to keep going there.
I'll have to read through the SlackBuild article once I get some time.
> Is there a way to get notified of new submissions to SlackDocs?
I seem to remember as an Admin at docs.slackwere.com that I used to get email notifications of changes to the wiki. I do NOT get them as a regular Editor, though.
Eric H. (AlienBob) will have to answer this one, bassmadrigal. Sorry. I have insufficient data and/or memory.
Ah, yes! Thanks. I had completely forgotten about the RSS. Unfortunately, even that would require regular monitoring by those interested in the new submissions. I haven't loaded up my RSS feeds in months.
There's a RSS feed but it's not limited to new submissions.
Thanks. Maybe I'll have to get akregator up and running again. I used to use that, but it crashed at some point and lost me all my feeds and I was too lazy to set it back up.
Hi,
As some of you may know, I am the founder, maintainer and systems administrator for the Slackware UK mirror and hosting service specifically targeted at the Slackware Linux community.
The service has been running for over 10 years now - I started out small, with a PC under a desk and a 2Mbits/sec SDSL connection. From simply offering a mirror of Slackware Linux, the service has grown
and grown into what it is today - dedicated servers with Gigabit connectivity for all things Slackware!
I would like to think Slackware UK has grown to be one of the largest repositories of Slackware related projects and files on the internet - in fact, I cannot think of anywhere else that provides access to so many resources in one location.
Slackware UK isn't just about mirroring software that you can find elsewhere on the internet - I offer free full file hosting to Slackware related projects, distributions and package maintainers. There are several projects which use Slackware UK as their primary hosting solution; including SlackwareARM, Absolute Linux, Freeslack, Slint, Cinnamon SlackBuild (CSB) and MATE SlackBuild (MSB), to name but a few. I also offer a mirror of the entire Slackware Linux trees and other projects such as Zenwalk, and packages provided by alienBOB (Eric Hameleers) and rworkman (Robby Workman). I also maintain an in-house (with thanks to alienBOB) cumulative archive of all packages distributed since the very first release of Slackware64.
So, why am I asking for Patrons? Simply to cover some of the costs and expenses for running the service. I am not looking to profiteer on the back of Slackware Linux or Patrick's work - in fact, I encourage you to visit Pat's Patreon page and sign up to become one of his patrons also. I only ask that, if you regularly use Slackware UK or one of the projects that I host, you would kindly consider becoming a patron of the service, if you have the means.
Any donations are gratefully received and every little helps. If you wish to donate as a one off or an amount which is not available on Patreon, please see the Slackware UK website for PayPal links.
Thank you for reading
Hopefully you can help.
Have fun & enjoy Slackware!
Last edited by onebuck; 09-28-2020 at 09:04 AM.
Reason: add link for original thread,
The liveslak project received some interesting new features.
Most importantly, the hard disk installer of the Slackware Live Edition - called "setup2hd" - was expanded. In the past, it used to allow only the installation of the Live OS to your hard drive. But I received requests to also make it possible for setup2hd to install regular Slackware like the official installer does. It sounded like a good idea, and starting with liveslak release 1.3.7 the "setup2hd" program will let you choose from more package SOURCES than just the Live OS. In addition to the Live OS, you can now choose to install regular Slackware from a NFS, HTTP, FTP or Samba server. In other words, Slackware's network install feature was added.
Why is this different from the setup program on the official Slackware ISO? Well, the most obvious improvement is that you are working in a graphical desktop environment (the Live OS). You can run the setup2hd hard disk installation in an X terminal while you keep doing other stuff like reading online materials or watching a video to pass the time. Moreover, you can install stable Slackware 14.2 from the Live OS. That means MMC and NVMe drives are supported during installation (which is something the official Slackware 14.2 installer does not provide for).
And to top it off, I am now also adding "setup2hd" to the small XFCE ISOs. Word of caution: the XFCE ISOs do not contain a "huge" kernel which means if you want to install the stripped-down XFCE OS to your hard drive, you will have to do a manual "chroot" after installation completes and before you reboot, to edit /etc/lilo.conf and add a section for the "generic" kernel. and then run the "lilo" command to make it stick. Hopefully the "liloconfig" command will learn how to do that for you, sometime soon. You can always perform a Slackware network installation from the XFCE Live OS of course! The second new feature is the ability of liveslak to configure a custom background image for Plasma5-based Live OS. The custom image is used when generating the Live ISO, as the background for the SDDM login greeter, your desktop wallpaper, and for the lock-screen backdrop.
What I still want to achieve is adding similar functionality to the XFCE and Gnome based Live variants. The snag is that the configuration needs to be scriptable, i.e. when the "live" user logs in everything must already be in place and pre-configured. For Plasma5 that was not trivial to work out, and I have zero Gnome and XFCE scripted desktop configuration knowledge. Suggestions and code snippets are welcome.
Wed Nov 4 02:31:05 UTC 2020 [2903]: Getting ChangeLog.txt...
0a1,424
> Tue Nov 3 22:32:22 UTC 2020
> Welcome to vtown, volkerdi's friendly takeover of alienBOB's ktown Plasma 5
> packages! Enormous thanks are due to alienBOB for maintaining and leading
> testing of Plasma 5 on the side, even as I wore out his patience (and likely
> others as well). But now this has made it into /testing and it won't be all
> that long before it'll hit the main tree, so test it out and let me know if
> anything broke. Several packages have been given back their upstream names
> since there's no real reason to do otherwise unless we were going to support
> installing KDE4 at the same time, and we aren't. Qt4 won't even be sticking
> around, but probably slackbuilds.org will take it up. I dropped kaudiocreator
> (won't build), ktuberling and klettres (rather bloated for the probably limited
> appeal), user-manager (seems to have been dropped by upstream), kdelibs (KDE4
> library, not going to support that), kwebkitpart, and kpat (not adding three
> new dependences only used for a solitaire game). In addition, it's probable
> that digikam and its dependencies will be dropped. It's a great program, but
> in my opinion it's just a little too big (especially the source) to ship by
> default. To install the vtown packages, first you'll want to remove any KDE4
> packages (the KDE and KDEI series in the main tree), any previous ktown packages
> from alienBOB, and then install all of the packages in vtown/deps and vtown/kde
> using upgradepkg --install-new. The previous advice on ConsoleKit2 was to remove
> it since we've switched to elogind, but if you've got the latest rc.M it
> shouldn't matter since ConsoleKit2 will not be started if elogind is installed.
> Speaking of elogind, you'll probably notice that once elogind is installed X
> or Wayland sessions will launch in the current console rather than on console 7.
> Regarding the build numbers, the one before _vtown_ is the build number that
> will be used when the merge to the main tree happens, and the one after _vtown_
> is used in case any rebuilds need to happen while vtown is in /testing. That's
> about it for the notes on this one. Thanks again to alienBOB, and to my friends
> in the US - don't forget to vote. :-)
Thanks PV & AlienBob!!
Have fun & enjoy Slackware!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
If there is erroneous information in the article, it's going to require a smarter person than I to detect and edit it. 
Slackware UK mirror and hosting service help needed
