docs.slackware.com is meant to be the "official" documentation, the central resource and the first place a user is supposed to look.

1 members found this post helpful.

convtags is a bidirectional converter that can help performing this process:

DokuWiki source page ⇒ AsciiDoc source page ⇒ PO file ⇒ Translated PO file ⇒ AsciiDoc translated page ⇒ Dokuwiki translated page

It automates conversions in red.

See http://slint.fr/misc/convtags/README and this article on SlackDocs to know more.

there is some "silent" articles deleletion on slackdocs?
i think, i remember, i wrote on slackdocs article about how to make software raid 1 with one disc, and today i try to search it, but found nothing....?

there also is very uncomfortable, you cant see just listing of all your own, writed, articles!

Hello, WiseDraco!

There have been no deletions that I know of on the SlackDocs site. Your well written article on software RAID is still there where you left it...

https://docs.slackware.com/howtos:mi...eshoot_howto?s[]=raid

The best way to find an article that you're looking for on a wiki-type site is to use the search feature. For example, I typed in "RAID" in the search just now and your article was the very first hit.

Hope this helped.

Have a wonderful day!

~Eric

No, no, no!
that one article, who you mentioned - is just started yesterday. but i remember ( meybe wrongly -i am old now), that, i am writing article years ago about how to install slackware on software raid 1 with only one disc.....
and i cannot find it.

search feature also cant help, and anyway - better is have to listings with own made articles, like as there, in LQ - "my posts", "my threads" - that was much, much too easy, than "find feature", i think....

Ah... sorry. I didn't see the date that this article was posted. My mistake. About the older article, though, I don't know what may have happened to it. I did not delete it. And if Alien Bob or one of the other editors had deleted it, you should have been notified first.

And yes, the search function is not the best thing in the world. Unfortunately, the wiki doesn't work like a board/forum. We just have to deal with it. You can always search for your username and everything that you've contributed or commented on at SlackDocs will show up in the results.

Cheers,

~Eric L.

1 members found this post helpful.

ok, thanks for info.

my memory not very good in last years,sadly, and maybe i am confusing something, but i feel, i something write an article about building that raid....
ok, try to search, maybe it is not about raid itself, but a part of "installing slackware"....?


try to finish that, new article, and also copy it to my own "web as notebook to remember some things", where i feel to oriented a bit more easy, because i use there my own tags for articles


BTW, is to be very good to put in each slackware iso documentation from slackdoc server .....what you think about it?
when you install and configure system after install, is much more easy read textfile with howto from local filesystem, than going to web...

HA! Yes, it's definitely easier to read a how-to on a document in your hand while trying to install Slack on your system. All the documents on the wiki are printable. You just need to click the PDF button on the top row over any article and the wiki will generate a .pdf document for you that you can download and print. That's how I usually do it. I also archive the pages I've downloaded to my system for later use.

Hmm... on the .iso? I'm not sure Pat V. would want to do it that way. Maybe he'll read this post and offer his thoughts.

Thanks for your participation and contributions to the SlackDocs wiki, WiseDraco!

2 members found this post helpful.

Thank you, for slackdocs project !

1 members found this post helpful.

I learned that when changing motherboards one must check /etc/udev/rules.d/ for a file like "70-persistent-net.rules." It will contain something like The ATTR{address}=="00:32:0e:3e:8a:0e" will be wrong for the new ethernet device and eth0 will not be created. Network setup by /etc/rc.d/rc.inet1 will fail and it will appear that your ethernet simply doesn't work.

Solution is:
There is probably a udev command that would avoid the need for a reboot.

2 members found this post helpful.

Wrong thread, sorry!

tl;dr but holy hell is there some out of date documentation around. i dont think i need to note where and when the docs are from and not EVERY doc can or should be updated but maybe start with whats on slackware.com? it needs to be said that the slackware devs act like the most elite developers ever but you cant even maintain an up to date website?

http://www.slackware.com/faq/do_faq.php?faq=general

This has zero to do with the Slackware Documentation Project which uses a hostname in the slackware.com domain to add to its credibility but is otherwise independent of Slackware and the content of its distro webite.

2 members found this post helpful.

i was reffering to ALL documentation that is appropriately linked with slackware and as i said i know not all of it can or should be updated. but may i ask why the website which is where users would logically look first hasnt been updated since the 90s? and thats not the only source but the most visible i would think... you have to understand that non slackware devs view all of the slackware contributers as a team. if its not the case thats fine too. maybe Pat can answer my and our query. and its a legitemate question not meant to be rude but not everyone runs slackware 7 anymore. i can start a new thread if thats more appropriate but the fact remains thaat only the people using slackware for 20 years(ish... slight exageration meaning many years) know just how out of date most ALL of the documentation is. when is the last time you "googled" for slackware help? im guessing you havent in forever but alot of people do.

its my opinion that the slackware "team" as a whole owes slackware "users" as a whole a better effort on documentation "as a whole".

just one slackers opinion

Oh these people! Tell you what, take all your criticisms, put them into a nice, new, modern website, then send PV, Eric, Robbie and others a link to that site and see if they like it, approve it, or say take a hike. What do you think the Slackware website needs or is lacking?

I see that you also use Debian, have you had a look at their site? Good luck with that. At least the info. on Slackware sites are still relevant and the commands and mechanisms still work because they are (for the most part) still the same. How many diagrams of a wheel do we need to see that it is round and it rolls.