As a contributor to SlackDocs, I second that comment. If the document author is shown, try searching for the document author in the Search box and look for a wiki:user entry. Authors may leave a trail to personal contact there, as they recognise that their articles may have errors, omissions or information that has become obsolete. If that draws a blank, try the mailing list. Both these approaches are more proactive than leaving comments on the discussion tab, which may remain unread by the original author for long periods.

1 members found this post helpful.

Eric, as stated above, I'm as guilty as the rest of inactivity. I am NOT, by any means, a Slackware guru. My main function when joining this project was to provide clear and literate editing skills in the English language.

Unfortunately, there have been some not-so-good changes/events in my life lately, so my online time is limited. To be honest, I'm not even sure I will have online access in my home much longer.

That being said, if you need to demote me from an Admin/Editor or expunge me completely, that would be understandable. There would be no ill feelings on my part should that occur.

If my situation improves and allows me more time, I would definitely be back "on the job" in the future. I don't know, at this point, when or how long that will be.

Regards,

~Eric L.

That distinction between howtos and slackbook was not something I realised! Seems that last night I was not seeing things in the best light. Just my luck.

It's working somewhat better tonight.

regards,
Biff.

1 members found this post helpful.

Personally I feel bad that I've never contributed (even though I'm registered). The reason is that, every time I look at SlackDocs, I find what I need. It might not be perfect, or pretty, or up-to-date, or have the general approach to a problem that I first thought of, but I still find what I need.

I hope this makes everybody who set up or has contributed to SlackDocs feel more appreciated. It's a pity it took this kick up the backside just to make me remember to say thank you.

One of the things that makes the Arch wiki much less useful than it was, is that they have 'updated' it so that all the non-systemd info has disappeared. That's a pity. There are plenty of places in SlackDocs that need to have newer Slackware releases added, but hopefully the SlackDocs contributors can find ways of putting newer info in without taking all the older info out.

5 members found this post helpful.

This is why I don't generally like the concept of wikis: one day the information can just poof! and it's lost forever. I like old fashioned textfile HOWTO's. Even if they get changed you will almost certainly be able to find an older version of it somewhere out there.

1 members found this post helpful.

Yes, and HOWTOs on github, with Pull Requests raised to change them have got to be best of all... so long as someone is there to look at the PRs that is!!!

Actually, now that I re-read your post, I understand that you mean the wiki itself may disappear, not just some text on the page. But I'll keep what I originally wrote below because I already wrote it

=================================

But with wikis, the information should never be gone. It keeps a revision history so you can go view previous versions of the page.

For example, we have the AMD Catalyst archwiki page, but if you go back in the history you can find all the previous edits. It may not be the easiest thing to find what you're looking for, but if you know around when it was on the wiki (or when it should've been), you can go back to those dates and hopefully find the information you want.

1 members found this post helpful.

hi all,
just added my first contribution: Connect to Microsoft SQL Server with ODBC and PHP feel free to correct it

2 members found this post helpful.

And here is mine.

Actually the thing I like least about my article is the reference 'securely_bridging_ethernet', but I couldn't figure out how to change that. It's late now, maybe another night I'll figure it out.

2 members found this post helpful.

What don't you like about 'securely_bridging_ethernet'? The page name? Do you want to rename it, and thereby the URL to the article? An admin can do that for you if you tell us what the new name should be.

Since I didn't explicitly mention OpenVPN I felt it may lead to confusion with kernel bridging. There is also the VDE project which also does ethernet bridging. If you think it's OK I'm happy to leave it as it is but truth is I'm unsure what to call it myself!

Yes I thought too that the title was not covering the content properly. If you come up with something better, let me know.

OK, so let's just go with 'ethernet_bridging_with_openvpn' for now.

Another thing: There's something seriously screwed up with the media manager upload for images. I click on upload and nothing happens. I drag a file and sometimes I get the filename appearing in the upload but mostly not. I can't quite figure out the magic combination that makes this work.

regards,
Biff.

PS: Tried with Chromium and Firefox, pretty much the same thing.

I think I worked it out. You need to click on upload a few times, and then you need to drag your file over the drop area, and then it works. At least that worked for me just now. If it doesn't work, then refresh the page and repeat that until it does (click and then drag).

A minor annoyance for the edit box for 'select files' is that you're supposed to put in your sub-category between colons. When you type in this category it's going to invariably contain underscores. Due to the edit box being undersized those underscores are not visible for me unless I go to a very small zoom (ctrl-minus in Firefox), meaning I don't know if I've typed them most of the time!

Another bigger annoyance is that it won't let me upload .xml files. I created a diagram with the online drawing utility draw.io, and I'd like to upload the companion XML in case someone wants to make modifications in the future, however the docs site refuses to let me upload a file with .xml extension. I don't really want to change the extension if I can avoid it, and I'd hate to be keeping the xml somewhere else.

It turned out to be a quick one tonight: Phoronix Test Suite