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.
That's a good request. However, since docs.Slackware.com is a user-driven wiki, we would need someone with the knowledge and experience with what you're speaking of above to submit a change to the existing article or create a new one of their own.
Any takers?
---
EDIT for additional information:
I just noticed that Jeremy Hansen aka bassmadrigal is the original author of that How-To. He is very active here at LQ.org. Hopefully, he will see this and reply to you. ~E.
I just noticed that Jeremy Hansen aka bassmadrigal is the original author of that How-To. He is very active here at LQ.org. Hopefully, he will see this and reply to you. ~E.
I'll try and get some time to work on it this weekend, however, there really isn't much different if you specify the UUID in the mkinitrd command (except that you don't need a boot= entry at the top). I haven't checked to see if the root option for elilo works the same as lilo, so that might need some tweaking...
I am creating an account today on https://docs.slackware.com. I am not familiar with how these wiki's work atm, though it shouldn't take very long. I will spend some time on here learning how the logistics work. The reason I am doing this is because:
It's something to do.
If opportunities are available for tweaking/tuning pages up, then I would be glad to do that.
Just having additional experience in other areas for the community in contributing.
Mainly the 2nd/3rd reasons are the primary influence for me. There are a few pages I'm sure could use some more cosmetic tailoring. I haven't really noticed anything yet, but I also haven't been on there long enough to notice anything. I'm not talking about editing, I am specifically talking about potential errata/typos/punctuation/etc. I'm sure the core team is working diligently on their jobs, so the least I can do is maybe learn some skills to fix the piddly things they don't have time for. That way, they can focus on what's important. I really would like to know more details about how we can contribute on the wiki, if possible. If I have the wrong idea on this, please let me know. I just remember clicking on the "getting involved link," so I read the pages on that and it seemed like this type of volunteer opportunity was for anyone.
Skills I have:
English (college level)
Technical Writing
I do know a bit of Japanese/Spanish, but it's not enough to mention above. I am diligently learning Japanese a couple hours a day, so maybe when I am able to get my JLPT exams finished I will add that to a potential opportunity for future elements.
Thanks,
-ul7
elcore kindly directed me over here. Sorry I need to get better at not making pointless threads. I guess this is an appropriate place to post this? I'm sure it couldn't hurt to have more bodies available for help. I'm willing do to help where I can!
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. All are welcome. All can contribute something of value to this project.
Last edited by captain_sensible; 09-15-2020 at 02:51 PM.
@Captain_Sensible... Firstly, thank you for your contribution to docs.slackware.com!
I created a discussion page for your document and have done some editing to it. I've left this message on the discussion page:
Quote:
16 November 2020 @1027hrs (EST): Edited this new article for spelling, punctuation, grammar/usage. Most mistakes were minor. I did NOT attempt to proof or correct any information in the code boxes. ~vtel57 (nocturnal.slacker - V. T. Eric Layton)
Please check your article when you have a chance and let me know if you're OK with this latest edit. I'm letting you know this out of courtesy, but in the future, you'll only be notified of edits on the discussion page.
Again, thank you very much for your contribution. I'm looking forward to the continuing article. I may not be as fast to edit (real life time issues), but today I just happened to have the time.
at @vtel57 thanks very much , i have no problem with edits , suggestions corrections and so on. Appreciate the courtesy to let me know.
I will be able to see whats gone on from old revisions.
Thought i would put down some of my experience. I'm getting to the point where i forgot more than i know now.
Next i'm going to look at xampp and alternative apache, using composer to download CodeIgniter 4.0.4 from the perspective of a slackware user trying to make web dev easy
Last edited by captain_sensible; 11-16-2020 at 01:58 PM.
Reason:
I can wiggle my way around HTML and PHP, but xampp, apache, etc... beyond my skimpy web-dev skill set. I'll stick with correcting spelling, punctuation, grammar/usage.
Thanks again for the interesting and informative tutorial. Sharing of knowledge is what it's all about!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.