Building a Large Linux Knowledgebase
linuxfan writes "It looks like LinuxQuestions.org is aiming to build the largest independent Linux-related knowledgebase using a Wiki. They are using the same software as Wikipedia (MediaWiki), are using a Creative Commons license and look to be off to a good start."
{
printf("42");
}
A feeling of having made the same mistake before: Deja Foobar
It's called Google.
What about The Linux Documentation Project? Provides plenty of knowledge to me about pretty much anything Linux related...
Hate me!
what if google dosent deliver?
This is a great idea for those of us who find certain aspects of Linux a bit daunting. Between outdated HOWTOs and sometimes cryptic MAN pages, newbies such as myself can get a bit frustrated.
My hope is that this database doesn't grow out of control with redundant and/or meaningless data.
"You're getting brutal, Sark. Brutal and needlessly sadistic."
"Thank you, Master Control"
-Sark and the MCP
The one thing keeping me from switching to Linux has a topic, but no one has posted any information there.
Does linux gaming work, or do you just have to play Neverwinter Nights over and over? (reply some good stuff here, and stick it in the wiki, too).
"If you think you have things under control, you're not going fast enough." --Mario Andretti
...since README.org was already taken.
---- Just another spud server.
This sounds like a good idea. However, there are two issues that would hinder something like this:
1. Variability between Linuxes. There are many distros out there and they all have their own ways of doing the same things.
2. Variability within Linuxes. Different distros also change their commands between versions. Any knowledge-base specific enough to be of help would have to be extremely thorough. A person working with a 2.4.22-gentoo-r3 kernel, for example, might have a different kernel than someone with the vanilla 2.4.22.
However, if enough knowledgeable people use the system, then it will hopefully conquer these problems and be useful. But for now, see the gentoo forums for what open source documentation done by a community is capable of. (However, this is only within one distro that is relatively new so it has an easier time of things.)
2.
A NYC lawyer blogs. http://www.chuangblog.com/
I know it's already being attempted but Linuquestions has the benefit of thousands of visitors a day that are constantly learning and you can actually _watch_ their learning process through the posts. And when they want to give something back...Viola, this new Wiki!
This guy is way out there
I sure hope it contains Linux dating tips!
http://google.com/linux/ - Linux searches ;)
Any technology distinguishable from magic, is insufficiently advanced.
Without wishing to sound too sarcastic, you are going to need a tad more than 19 articles to convince me you have a valid knowledge repository. I'll stick with the Linux Documentation Project for the moment thanks
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
Wikipedia is a projekt driven by an community, LinuxQuestions.org is somewhat unclear to characterise: not clearly a community only or a business company selling ads within their content.
As on always you should read the Rules before posting. registration is required, but email is optional.
Infact I used wiki last night looking for some information on file formats, and its not the first time i've used it either, but last night rather than find out all about the chewbacca defense, goatscx man and the underpant gnomes I had found some good stuff for my college project. Its much better than paid for resources with adverts and membership programs.
I contributed to its brilliance via Paypal and I'm glad there will be a linux variation of it as well, I don't use linux personally (OSX) I know I will in the future, and what better place to look?
Jonathanjk.com
Wiki's seem to bring together the reasons why the web is seen as useful (disregarding the free pr0n). Easy content creation, accessibility and ease of use. With wiki's you get the added benefit of a central repository to look for the information you need.
As wiki's grow and become known the need for search engines might lessen. The first resort for information will change from google to the relevan wiki. Google will be seen as second in importance. After all, wiki has the structure of yahoo with the benefits of quality content.
Comment removed based on user account deletion
Isn't OSDN trying to do that already? Why is an OSDN board advertising an upstart competitor like LinuxQuestions? Is this article an inside joke Michael?
Yes, but that's what they* want you to know and when they* want you to know it.
*'They' being those who buy words on Google.
A feeling of having made the same mistake before: Deja Foobar
Kind of defeats the purpose of a wiki doesn't it?
please post less and save internet space. thx.
Does it strike anyone as a bit of a negative attribute that you have to have a massive knowledgebase to use your operating system?
Microsoft has a knowledgebase as well, but only for troubleshooting, service packs, and development. I've been to their site maybe twice.
However, I've always had to rely on poorly-written HOWTOs and other documents to spend three hours just getting a sound card or USB mouse to work under X.
Call me crazy, but needing a huge database of tutorials to actually get things up and running is not exactly something you should be shouting from the rooftops.
"Sufferin' succotash."
ls /usr/share/man/*
I wish your comment was on a Wiki, because then I could edit it to remove all those apostrophes.
This sort of theme is becoming increasingly prevalent these days. Take a look at ESR's recent article on trying to get CUPS to work. The bottom line is, rather than wasting energy writing more HOWTO's to get some impossibly-difficult-to-install software working, how about spending the time making the software easier to install?? Hmmmm? Or is Linux doomed to be used only by elitists?
This seems like a great idea, untill some smartass decides to mask harmful commands as solutions to obscure problems. /bin so that when you list all the files it does an asciiart of the goatse guy, or just throws in a "sudo rm -rf /" or something.
Since it looks like anyone can update this thing, what happens when someone sneaks into a solution a command to write morse-code on the hard drive, or some command to rename all the files in
Not that I don't think this is a good idea, but without some sort of review process I would personally feel nervous about sending some of my more inexperienced friends to the site and having them execute commands all willy nilly.
I know that 99% of the users who would post something would do it out of an honest desire to help, in fact I will probably post a few things that I have had to do as obscure solutions to weird problems myself, but it only takes a single post to a problem that is just commen enough but not too comment to get a lot of people to fsck up their machines.
Famous Last Words: "hmm...wikipedia says it's edible"
If you want some tips on making some good documentation, look at the freebsd handbook, that is simply excellent. you can usually find what you are looking for in there. i know i can.
whilst in linux what i find is documentation is all around the place, man pages, howto's etc, which are helpful, but sometimes not very convenient
Marge, get me your address book, 4 beers, and my conversation hat.
I'm a contributing member of the linuxquestions site, and I personally thing Jeremy (the owner/admin) is doing a wonderful job of keeping the site up to date and adding new things. Most recently they showed their support at linuxworld with other companies and .orgs. THe addition of the wiki will further increase what they're trying to get across. I've found threads on there that I havn't found anywhere else on google or mailing lists, and most everyhting I've needed has a solution. Responses are fast, and the people are very nice, I'd reccomend it to anyone with questions.
Now keep in mind they don't just do linux, theres Solaris forums, Programming forums, AIX, distro forums, and many many more such as hardware forums, networking and a very nice HCL. I guess this is turning into an ad but I'm just trying to help out cause a little bit I guess. You'll find me there as the user Astro
Even a stopped clock gives the right time twice a day.
Nay!
sorry - just had to be contrary
Sorry, wrong story. Mean for the Gates of spam one.
Cheers,
RoadkillBunny
I dunno if the "wiki" part is anything newer than what I saw a month ago, but after jumping through several account creation / e-mail verification / etc hoops to try to post a detailed, working answer to someone else's problem (the problem and distro which happened to be the same as mine -- and for which no "good" answer had yet been provided), I kept getting denied any ability to actually post a reply to the thread. Tried for several days and gave up. I'm hoping it was a fluke... I know I need answers all the time for things, but the one time I CAN HELP and try to do so, DENIED. Blah.
How is linux ever going to gain any ground on the desktop if linux advocates are just going to bury their head in the sand and pretend that microsoft = bad/evil, and linux = perfection. He makes a fucking legit point.
I hope this post comes up for me to meta-mod.
Wikipedia
I know you are just a troll but there are a lot of crappy wiki's out there. This is one example of one that rocks!
Damn the trailing slash ruined it - the url is http://google.com/linux...
Any technology distinguishable from magic, is insufficiently advanced.
But wait, hold on! Did someone write trollish nonsense all over a beatiful how-to? Just roll back the changes.
If this scares you (and it should, it's very powerful, very new), check out wikipedia.com. It's totally self-policing and very well-kempt. You will quickly move from scared to excited.
Computers are useless. They can only give you answers.
-- Pablo Picasso
I went there once, took me 2 days to get out!!
amazing site...
What you need to know is that main returns int!!!
After some grits and a beowulf cluster of SOVIET Profit! that are belong to us, redunant jokes, for one, welcome me.
I would like to see documentation that's prolem oriented. It would start with "How do I ...?". It would list the most basic, high level steps. Then, each of those steps is a link to its own "how do I...?". You could then drill down each step that's a problem to you, and find out how to do the step. That way you don't get stuck. Sure, it would take a long time to build, but then you have pretty complete, robust documentation.
Computers are useless. They can only give you answers.
-- Pablo Picasso
I have been using Wikipedia for a while and one of the biggest selling point IMO is the great browsing experience. I often find myself actually surfing again by going from hyperlink to hyperlink, trying to soak up all the information, something I have stopped doing a while ago with most other webpages. There is lot of very good, indepth content on there.
TLDP is a bunch of mostly technical articles (HOWTO's, guides, FAQs and man pages) that are very usefull, but don't really form a coherent whole. It would be wonderfull to have a somewhat more encyclopedia oriented linux documentation to consult, that is updated consistently to boot. A encyclopedia aproach also alows you to cover a wide spectrum of topic, from, say, obscure technical details to general *nix design philosophies.
However, wiki's for this type of large projects (like wikipedia) need a certain critical mass of contributors for it to, I would think. While I don't know if this project will be "it", I think a wiki aproach would be a great idea.
Seriously. I visited the local LUG and was appalled at the attitude some of the older members had whenever a relative newbie or younger kid asked them a question. The boilerplate answer from the "gurus"?
"Just read the man pages".
I tried to hit them up for a simple answer to the nodev, user and suid options in fstab and all I got was "Read the man pages".
I wasn't looking to the answers to everything, only the differences between "user" and "nodev" options and when it is best to use them.
It is easier to build strong children than to repair broken men. -Frederick Douglass
My numero uno criteria used to decide whether or not to use a software product when evaluting (usually open source) is whether it uses a wiki for documentation. If it does, I do not investigate that product any further.
Elite Google
"The world only exists in your eyes. You can make it as big or as small as you want." - F Scott Fitzgerald
It would be helpful if SIT didn't block it and the Wikipedia.
Here is a link on MediaWiki and one on a list of sites using MediaWiki.
MediaWiki is GPL-ed, and more programmers are always welcomed.
Mind explaining why my post is "Flamebait?"
I simply made a point; an opinion of my own. If you disagree with it, reply or disregard, but don't mod it down. What makes Linux so great that it's above criticism?
"Sufferin' succotash."
How can you make sure some numbnut doesn't get rid of useful stuff?
You know, when you posted this, there maybe was 19 articles, but right now, they are at 129, and growing, as the slashdot phenomenon actually does something useful.
I encourage the whole slashdot community to participate, it's easy and much more constructive than just crashing servers for nothing.
Semantics is the gravity of abstraction
One of the most frustrating things about Linux distributions is conflicting documentation and obselete and current documentation mixed into the same directories. I'll look at some documentation for packet filtering, for example, and be left totally bewildered as to which methods and software are actually current and intended for use and which ones are considered outmoded (and, afterwards, I run off and just use OpenBSD).
It would be a great help if some of the distribution maintainers contributed to the wiki. They can say things like, "Debian 3.0 uses software X for doing Y, while Debian 4.0 uses Z, a replacement for X." Some one else can say, "Well, Fedora chose to use W for doing Y, so you have to do this this and this differently."
Eliminating ambiguity can be, perhaps, the benefit of a "real-time" wiki.
Vote in November. You won't regret it.
Add a section in the wiki, anyone can do it. And you'd get loads of answers.
Ask 8 slackers a question, get 10 awnsers (a citation, but I can't remember from who)
I think in the end, it will boil down to trust: Do I trust this source of information? And if not, how do I verify its validity?
Then again, DMOZ has already done an admirable job in maintaining a moderated link farm...which raises the question: Do we really need another one?
it's aptly called LinuxWiki. For now, (nearly) all articles are in german only, but they are going to change that. Maybe the people at LinuxQuestions.org would be interrested in some form of cooperation?
I have discovered a truly remarkable sig which this 120 chars is too small to contain.
Quoth my freshman year C Programming professor who said "void main() makes baby Jesus cry." I almost fell out of my chair with glee.
Who did what now?
Hire all the unemployed "outsourced" whiners who post on Slashdot.
I like the idea behind Wikis, but have often found that Wiki content is often out of date, or is wrong. This is particularly true with many Linux-related Wikis.
I always thought it would be a good idea for Wiki's to have a rating system, as well as a 'freshness' system. If I search for a topic, I get several articles with different ratings. If I like an article, I give it a high rating. Likewise, bad articles receive low ratings.
As an article ages and becomes less relevent to current technologies, it's score will drop. That way, if I search for how to set up my Linux box to my ADSL provider, the article written 6 months ago will usuall have a rating which is higher then some HOWTO written 4 years ago.
Are there any Wiki technologies which do this?
"Can of worms? The can is open... the worms are everywhere."
Why not?
But, it could be just nice to add the RDF descriptor of the choosen licence in order to display it on my FireFox browser using mozCC extension.
"twice as good as View Source"
Perhaps a fast way to new content for sites like wiki.linuxquestions.org would be aggregation of other sources, such as the Linux Documentation Project. That way, the LDP information could be easily (and freely) updated and expanded.
Of course, the documentation project license requires that permission is sought from authors for derivative works. Hopefully there will be few obstacles to the gaining of such permission, and perhaps LDP authors should take initiative themselves to copy and paste their articles to wikis.
Namaste
Your program, on many compilers, will work just fine with void main(). On the other hand, printf() won't work unless you #include . Nice try at being snide though.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Comment removed based on user account deletion
Hmm. The Germany government has been supporting OpenFacts for some time. I guess I've tried to get people interested in that site, but it hasn't gotten very far (in the English version, at least -- the Germans seem to be doing well in the Deutsch version)
The good news for the new project is that all OpenFacts material is public domain, so it's fair to cut-n-paste off that site (well, if there's anything very useful).
Um, and how is this site run by LinuxQuestions independent, exactly? I guess I don't quite understand how that can be the case. Whatever, I guess.
Or for brevity, {{msg:NPOV}}.
The World Wide Web is dying. Soon, we shall have only the Internet.
I don't know how LQ's wiki will end up, but if the answers from questions posted to the forums make their way into Wiki entries and are regularly maintained, then it has potential.
Almost two years ago, a resourceful hacker at our Waikato Linux Users Group set up a Wiki, and it has been a phenomenal success. We'll be surprised how often we google looking for something, and find the Wiki as the first hit!
What did we do differently? For starters, Perry imported the man pages and howtos, meaning people could link to a man page in the Wiki just by naming it (ie fstab(5)). This encourages both reading man pages and editing them, marking them up to be more useful to everyone. Another point is that now you can see which pages (and other man pages) refer to a given page, an invaluable tool that man itself can't provide!
We're thinking of dropping the HOWTOS because it's amost impossible to get changes sent up stream, and our own locally developed content tends to be better and more up to date.
Good luck to the LQ people, but there exist a number of Wikis that have the knowledge growing nicely outside of this. If you're looking for something, come check us out.
IMHO (as a Wikipedia admin) what keeps that place running smoothly is a group of roughly 200 dedicated contributors, most of whom are admins.
To make laws that man cannot, and will not obey, serves to bring all law into contempt.
--E.C. Stanton
wait a while for babelcode (www.babelcode.org).
Speaking of the Wikipedia...
I found out yesterday that my philosophy professor at Ohio State (Dr. Larry Sanger) actually created the Wikipedia. He referenced the page in a topic we were doing, and mentioned in passing that he had started the Wikipedia a few years back (although he is no longer involved with it, as of March 2002).
If anyone has any questions for him, I can personally pass them along to Dr. Sanger (assumign he has time to answer of course). He and I are on fairly good terms (I sit in the front and am the most active discussion participant in our class.)
His information is here.
My email is...neil at wehneman.com
- Neil Wehneman
My legal education, in nifty podcast format
There is so much that you can come and help us with.
Come and fill out a stub for an application you use.
Add structure to a section to facilitate, inspire, and direct future contributions.
Edit existing information into seperate sections to promote greater development in each.
Add stubs for topics that you would like to see written on.
Add stubs for questions you think others would like to know the answers to.
This is just getting started, and you can become a major contributor if you choose; it's all up to you.
> I always thought it would be a good idea for Wiki's to have a rating
> system [...] If I like an article, I give it a high rating.
> Likewise, bad articles receive low ratings.
Ohh, yeah! You could have end-user anonymous moderation, giving the posts scores with comments like "Informative" and "Funny"... frequent posters could rack up "Karma" which let them post with a score bonus.
I think that's a sure way to get a high-quality source of information.
Except, of course, people on that type of forum never read the articles!
Do daemons dream of electric sleep()?
One of the better resources for linux and open-source information is the WLUG wiki at http://wlug.org.nz
455fe10422ca29c4933f95052b792ab2
I think we have gotten to the point were knowing where to find technical information is a skill in itself.
Recently, a pc-tech friend of mine, jokingly suggested that instead of asking questions about which cpu goes with which socket, the a+ cert exam should ask: which web-site do you go to in order to find out which cpu goes with which socket? Or, where do you go to get a hardware driver?
Actually, I think that sort thing makes sense. I have long sense given up on trying to memorize all those details. Instead, I try to know which web-sites to go to. Nobody can memorize all the details anymore, somebody who knows where to go to quickly find information, can get a lot more done, a lot faster.
Hear that? ahdeoz is being alienated by your wacky Wiki ways. Stop the presses, unplug the servers, and start working on a nice, detailed PDF.
You want the truthiness? You can't handle the truthiness!
I've often thought about installing/hacking together something like slash and posting each of the howtos as "articles" or maybe each section of each howto as a sub-article. Then the howto could be discussed and kept live and up to date. After some period of time take the highest moderated posts and rewrite the howto and start over.
Slashdot's moderation system seems to mostly work and that would be the key to success for something like this. I could never think of a good name for it and wasn't good enough to pull it off so I never got around to it. Now I could probably pull it off but don't have the time and still don't have a good name.
G
I have a better idea about wiki: use it instead of CVS or on a top of CVS making possible for everyone to submit changes or to roll back the bad code. Mo more waiting when the maintainer has time to check it in - just do it yourself. If it works for open-sourced documents, why can't it work for open-sourced software?
Less is more !
I'm sorry I didn't post a lengthy comment explaining how excited I am about this news but I figured "Um... yay!" would cover it, unfortunatly it didn't so here goes.
Wow this is so f-ing awesome, I really like the idea it sounds really cool and I hope to contribute (and learn) a lot!
Sorry you couldn't get all that from "Yay!" I would of posted more but I couldn't think of anything at the time and I was running late for work.
Fuck you.
Love,
Slashdot
OCG is a known troll and this is a troll post. You'd think it was obvious by the way he plants some his own AC posts. Moderators: Congratulations! You fell for it hook, line, and sinker!
Fuck you.
Love,
Slashdot