So far, you have created THREE accounts on the Wiki. I enabled the first:

I deleted the second (it had a slightly different email address, lots of digits in there):
And then you created a third:
This third account is still there, but I have not enabled it (you already have one) and because first I want to learn from this thread what you are trying to accomplish here. The Wiki is a serious documentation project and not a blog. I don't accept articles from someone who thinks spending a few hours in Slackware is sufficient to be able to tell other people how things should be done.

Because it is a TXT document and not a MS Word file or PDF, you think that this README would or should not cover all expects of encrypting your computer? You're wrong there. I wrote that README_CRYPT, long ago, as the source of information for setting up your encrypted Slackware, along with the README-LVM. There should not be a need for more documentation since the user may have nothing at hand except the Slackware DVD he just received from the Slackware Store.

If you think you require background knowledge that is not in the README, and it is not basic Linux or Slackware knowledge you have not yet mastered... show us what's missing and it can be added to the README. That's still the primary place for accurate information.

If you have suggestions to fix the README text, show us textual diffs and don't end up in vague descriptions please. A write-up on early-ssh is not in the scope of that README and would be good material for a Wiki article.

3 members found this post helpful.

Your writing is not up to scratch for Slackware docs.

Not sure why you are judging my character from posts I am making about an OS question. The truth is difficult to come to terms, still isn't going to stop from enjoying working with linux/operating systems. Millenials make other millenials look bad.

I have posted some examples earlier and am now playing around with using UUIDs in /etc/crypttab instead of /dev/sda (idk if it will work seems like it does on Ubuntu in the least) to solve the issue that encrypting swap partition has in that it formats itself every boot and shutdown (as it says on the readme). Using the UUIDs would be useful so the wrong partition wont get formatted if someone has a hotswap machine set up and removes a drive or something.

If I dedicate every free amount of time I have no doubt, but I did not want to spend a lot of time figuring out how to navigate the UI of the docs wiki simply because of time constraints. If I google search "Arch wiki contributing" I get this first link https://wiki.archlinux.org/index.php...i:Contributing and off the bat I am informed of the etiquette, just like slackdocs. However, if I keep scrolling I am actually told how to start a new page under "Creating". That info is not existent on the slackdocs contributing page, moreso that it gives info about editing existing docs and not making your own, so I went on here to ask for some additional info and I get treated with a "Really. Can't you just read the front page of the Wiki first? This thread is a waste." because I did not spend 2-3 hours looking over the entire page. I respond and the blame is still on me, I am from the "outside" so to speak coming into your "bubble" so I know how it goes. We can all just try and be a bit realistic though.

I don't know what happened with the first account, I think I used an email I no longer had access to so I made a new one with a similar looking email I have, and then I could not log in in there anymore so I made another, I believe.

I have been using Slackware since 2014 (or earlier?)....this is a new LQ account I made, my old one had a bunch of posts asking how to set up web/mail/vsftpd servers under CentOS and when I switched to Slackware I did not even need any assistance except for a few things because the CentOS config files are very close to vanilla like Slackware (unlike Debian/Ubuntu). I forgot the password to that account though so I made a new one. This is also my first time ever setting up disk encryption and I was using the README_CRYPT file but I ran into a lot of errors where the solutions were fragmented on LQ and not in one central place.

That is basically what I want to do with the slackware doc I wish to make, as well as add a portion for being able to decrypt the drive on a headless machine. I have already successfully done it on my machine so it works. Another user helped me/did all of the work for that but it still fragmented in yet another LQ thread.

You can't base my writing skills off of a thread post, I write these quickly and then sometime make some edits to them. Why are you guys so rude here? This has turned into a whole thing just because I had a question because I could not figure out how to navigate the UI of the docs wiki. I guess now one of you will quote that portion and say if I can't figure it out myself I shouldn't be writing it. Come on.

I've reset the password for your first account and changed the email address it uses to the one you entered for the second and third account. You should soon have an email with the password.

Okay thank you, do you think for the time being I should post the doc to https://www.linuxquestions.org/quest...ss-stories-23/ (as a member mentioned) see how the feedback goes and then think about writing it on a doc at a later time?

I think you should post a diff to the original Slackware README and the README you modified according to your adventures. That is what I would consider the most relevant information.
Then you can post a personal story on LQ if you want, and polish that so that its quality is worthy of the Wiki.

Hi,

I see no rudeness but direct statements. No personal attacks either. You seem to have thin skin. You might need to thicken up a bit. If you do write something related to the topic. Expect feedback! No hand holding, just direct comments. As to your navigation skills then you should learn to use doc page search.

Maybe you should look at https://www.linuxquestions.org/quest...#faq_lqwelcome so you can compose a proper post/query.

You were rude to me when you quote my post to you but strike through your reply. That type of habit/etiquette will not make you many friends here.

Your reading or viewing doc page is on you. If you had read the page you would/should have found the proper methods. https://docs.slackware.com/start is an easy format and layout. You could have done a search on that page to get to something you may have over looked. You do know how to search? Search is just under the navigation set on the left bar.
Hope this helps.
Have fun & enjoy!

I just wanted to give some words of encouragement. Do not be discouraged. Your attempt / desire to contribute is a good one. Consider the feed back, and slight friction you are experiencing, encouraging.

1 members found this post helpful.

Technical writing should be tightly focused. Your writing is rambling. I'm not being rude by telling you that. Before you were born I had been an English tutor at a west of Ireland university for years. Students expected me to critique their writing, not to give them a shoulder to cry on. Besides, you were exceptionally rude in your OP, by insulting those far older and more experienced than you. I really dislike that attitude among your age group.

When I write on here it is rambling but if I write a doc I will for sure change the writing style. Its the equivalent of having a casual conversation vs writing a company email. Thanks