Suggestion. "Sticky" Topic for Important Announcments and/or Fixes, Additions, etc.
 

Perhaps there should be a "sticky" topic heading here where "bulletins" can be posted so we don't have to read through all the posts here and other sites to literally stumble across
important news, e.g., the KDE 3.5.10 files for Slackware 13,
and the problem and fix with the multilib files?
If the board software allows it, limit posting privileges to the thread to a select few, such as Mr. Volkerding, AlienBob, etc.
Just a thought.

I find the search function really good here... In fact Google often reminds me of the wealth of knowledge in the old posts here.

I suppose it's a good Idea that requires extra effort on the maintainers end... I personally think wading through a sticky post after 3 months of not reading it would be quite annoying. I would end up using the search feature anyway!

But here is an advanced search in case you are looking for the KDE stuff still.

Advanced Search
Key term: KDE
Forum: Slackware
http://www.linuxquestions.org/questi...?highlight=KDE

just scanning it a bit produces
ftp://ftp.slackware.com/pub/slackwar...for-slack13.0/

Never realized the unsupported section on the mirrors

I think the problem comes up when there is something that you don't really know about. I agree that the search function is great, as well as google, but if it's something that you have no clue even exists it would be nice if there was a bulletin or something. I had no clue about kde 3.X for Slack 13 until someone posted it in a thread that I just happened to read.

Exactly!
Thanks.

There was another recent post about the disappearing keyboard/mouse problem, so.....
Bump!
:D

Hi,

I think a 'sticky' of that type would require someone to work full time to maintain. If there's a major problem then I would think a 'security notice/update' would cover most problems.

With such a mix of hardware available and using different flavors of Slackware each problem would be unique. If it's a upstream problem then the user should address in that manner. Just too many variables to contend with. A knowledge base/wiki style may work but that too would be labor intensive. :)

'*buntu-fy-ing' the Slackware distribution doesn't get my vote!

:hattip:

While you are entitled to your opinion, you completely missed the point!

The KDE 3.5.10 files for Slackware 13 and the trouble with the multilib files are not equipment specific issues.

Please see the original post and reply number two (post #3).

Thanks.

I think the idea of stickies is already in place. I recall Robby placing a sticky on the forum for hal issues awhile back. The developers are on top of this.

Ok - who decides which subjects should/should not be included? Who decides when a topic is now exhausted/resolved/irrelevant? Will we be using only the alerts raised by Slackware or will something else be used? - and who will decide on the criteria for "important" announcements and fixes? Also, as I have said before - no one ever reads the stickies - so where is the value of a sticky over a naturally occuring thread that will raise to the top via forum Darwinism and then die when it has served it's purpose.

As one of the mods of this forum, the answer to any of these questions is "not me". Also, we do have a Linux-News forum that could be used for this.

A "sticky" front and center, where these events are posted as they happen would certainly be appreciated by this user. One central place where a user can go and read down the list to see if there is any important "news" before he goes about a project such as replacing KDE 4.xx in Slackware 13 with KDE 3.5.x or installing the multilib files.
I know it would have saved me a lot of grief AND TIME had I known about the problem with the multilib files BEFORE I installed them, THE FIRST TIME.
It is not like everyone has the time to wade through every last post on this or every other Linux forum and stumble across the information hidden inside a topic on another subject.
The way some of you guys act you would think Slackware is a mysterious Eastern religion, not an operating system, whose secrets should only be known to the high priests of the temple.
Sheesh.......

Dude.....give me a break! How about you read the release notes before you install. The above is a direct quote from the release notes for Slackware 13.0. The kde3-compat library issue was announced. It is expected that you will read the provided documentation prior to an upgrade/install.

Hi,

I did not miss the point in my opinion but feel that you really can't expect to document as you seem to fair.

A lot of information is there for a user to find. Centralized? LQ & Google are the best points. Sure, maybe not as convenient but there's no way to be selective for ideas or issues that must be posted within that sticky to satisfy all. I have tried to include problems/quirks or just basic information by working with the 'sticky' for 'So you want to be a Slacker! What do I do next?'. Too be selective and fair to all can be difficult. What do you include or exclude?

You are being specific with your example. Document it. If unknown then post a query.

If you feel this is really an issue then why not create a Slackware specific wiki for a knowledge base with the content as such. From my experience with 'Slackware-Links' you will be spending a lot of time on the maintenance let alone for content. :hattip:

Hi,

Calm down!

You must approach the temple with a quiet hush to walk before Bob and his deacons. :jawa:

Search engine! Keywords! You could do a Google search for 'Slackware 13 KDE "3.5"'.:) How much more would you need? Refine the search.

No one knows your needs better than yourself.

The helpers, Mods and others on this forum are here to help whenever possible. But too attack with a snide remark as you did is a insult to me. Your the one labeling the use of a OS as a religion. It's a tool that is used to help me and others to be enlightened so we can approach the sacred alter. So if you must insult then do it properly.
:hattip:

It would seem that you want LQ to have copies of the release notes (as shown by onebuck), but our copy would always be behind the copy on the distro site. Really, the distro site is always going to be the "go to" place for any identified problems.

Practical your reading comprehension, dude, as I've never mentioned the kde-3 compatibility library and there is NOTHING in the release notes about the KDE 3.5 files that later became available for Slackware 13 so you could replace 4.xx with 3.5.10.

http://www.slackware.org/releasenotes/13.0.php