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.
For RTAI, I've not yet finished the howto, because I can't quite decide on the best demo program. In the past I've demoed this with a LED pulse-width modulated. Unfortunately the average PC has no such LEDs, at least not without some hardware connected to a parallel or serial port. And most PCs don't have them either.
I noticed while logging into docs.slackware.com I get redirected to slackdocs.alienbase.nl. The SSL Certificate is expired since April 16, 2016 on slackdocs.alienbase.nl as well. Is this intended?
I noticed while logging into docs.slackware.com I get redirected to slackdocs.alienbase.nl. The SSL Certificate is expired since April 16, 2016 on slackdocs.alienbase.nl as well. Is this intended?
I got a similar redirection and emailed Eric about it. Here's his response:
Quote:
The docs.slackware.com hostname is actually an alias for an Akamai cache server, and Akamai in turn fetches the original content from slackdocs.alienbase.nl. Perhaps you got caught off-guard when I was working on the http server reconfiguration after some of the Akamai-served URLs began to show Akamai errors instead of Wiki content.
I will however re-check the httpd server configuration and that of the dokuwiki install, because such redirection should not occur. It is confusing.
I got a similar redirection and emailed Eric about it. Here's his response:
Thanks for the clarification. I run the HTTPS Everywhere add-on in Firefox so I am automatically loading HTTPS on every site that has such a configuration.
I'm not quite sure how the discussion pages work in Slackdocs. I have a login, do I go to the discussion page for the article and then click 'edit this page' to add a comment or is there another way?
I followed Eric's excellent article and upgraded to slackware64 current from 14.2 - the problem I had though was that I neglected to installpkg the kernel-modules package for 4.14.35 so when I rebooted there were various things going awry, including my keyboard. Unfortunately, although I still had my old, working, kernel, I couldn't boot into it because I had it listed second in lilo.conf (the new kernel first) and as my keyboard wasn't responding I couldn't select it.
It was easily fixed as I just edited lilo.conf to make it the default but I can imagine a situation where the keyboard doesn't work and the new kernel doesn't boot (for whatever reason, mine was my own fault). I just thought maybe a note could be added to make sure users list a working kernel first in lilo.conf so it will load automatically on boot.
You can leave your comments on the discussion page. That is what it is for. You describe exactly how to edit the page. Add your comments at the bottom.
Be sure to timestamp the message.
If you are logged in, that's easy: press <Alt>-Y to insert a nice signature with your name and a timestamp (alternatively there's a button above the edit field that lets you do the same).
If you are logged in, that's easy: press <Alt>-Y to insert a nice signature with your name and a timestamp (alternatively there's a button above the edit field that lets you do the same).
I missed both of those the last time I commented on a discussion. Could the template for discussion pages be editted to include the Ctrl+Y option or point out there is a signature button (there were a lot of buttons, and I didn't go through all of them waiting for the tooltip to see if there was a signature option)?
I tried using the four tildes wikipedia uses for signatures, but when previewing, it didn't do anything, so I left it off. Is there also an easy way to indent for replies? Or a better way to show something as a reply to the original discussion? I guess I'm just used to wikipedia's "Talk" pages...
I followed Eric's excellent article and upgraded to slackware64 current from 14.2 - the problem I had though was that I neglected to installpkg the kernel-modules package for 4.14.35 so when I rebooted there were various things going awry, including my keyboard. Unfortunately, although I still had my old, working, kernel, I couldn't boot into it because I had it listed second in lilo.conf (the new kernel first) and as my keyboard wasn't responding I couldn't select it.
Wish there was the same excellence for converting Slackware 14.2 (and Slackware -current) from LILO to GRUB in present and future Slackware documentation.
LILO is no longer "the most used Linux Loader for the x86 flavor of Linux" as Miroslav "Misko" Skoric specifically stated on 2010-07-18 in Slackware 14.2 f-diskset's LILO mini-HOWTO v3.39
LILO
LILO is the Linux Loader and is currently the default boot loader installed with Slackware Linux. If you've used other Linux distributions before, you may be more familiar with GRUB. If you prefer to use GRUB instead, you can easily find it in the extra/ directory on one of your Slackware CDs. However, since LILO is the default Slackware bootloader, we'll focus exclusively on it.
It's too bad that GRUB gets short-shrifted in the Slackware Documentation Project even though so many users are using GRUB rather than LILO for distros besides Slackware
Hoping that Slackware GRUB users more proficient than this one will better take up the cause of better GRUB documentation rather than just vaguely pointing to the current GRUB manual https://www.gnu.org/software/grub/manual/grub/grub.html
.
.
Last edited by nycace36; 05-01-2018 at 03:20 PM.
Reason: not yet such a GRUB expert as others might expect
Wish there was the same excellence for converting Slackware 14.2 (and Slackware -current) from LILO to GRUB in present and future Slackware documentation.
LILO is no longer "the most used Linux Loader for the x86 flavor of Linux"
OK, so I will await your contribution to the Wiki documenting how to handle Grub during or after a Slackware installation. Thanks in advance. You do realize that the Wiki is a community project.
And of course, you generalization does not hold true for Slackware where LILO is the most used Linux Loader.
OK, so I will await your contribution to the Wiki documenting how to handle Grub during or after a Slackware installation. Thanks in advance. You do realize that the Wiki is a community project.
It's an interesting state of affairs, when a post suggesting people write docs gets more rep than posts with links to new articles. Not having a go or anything, but am I the only one to see the irony?
It's an interesting state of affairs, when a post suggesting people write docs gets more rep than posts with links to new articles. Not having a go or anything, but am I the only one to see the irony?
I get the impression a lot of people use the rep link as a kind of social media 'like' button rather than as a comment on the helpfulness of the post.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.