Building a Large Linux Knowledgebase 251
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."
All you'll ever need to know... (Score:4, Funny)
{
printf("42");
}
Re:All you'll ever need to know... (Score:2)
Re:All you'll ever need to know... (Score:3, Funny)
If only we had something more scientific.... like scrabble....
int main() (Score:2)
MOD PARENT UP, PLEASE (Score:4, Funny)
Quoth my freshman year C Programming professor who said "void main() makes baby Jesus cry." I almost fell out of my chair with glee.
You missed the mark by a mile. (Score:2)
MOD PARENT UP (Score:4, Insightful)
Re:MOD PARENT UP (Score:4, Insightful)
Linux is an OS by geeks, for geeks. 1 size does not fit all. As Linux gets easier and easier to use, it will take n more users of all types, but dont for one second think that it will stop being by geeks or for geeks first.
Which is not to say that software shouldn't be easier to install, just saying that it isn't about elitism.
Re:Question (Score:4, Insightful)
I tend to avoid it, it's got lots of reference stuff but is pretty short on examples, which probably explains all the good user supported sites/knowledgebases around the web.
Re:Question (Score:3, Informative)
It's not only for when you want to solve a problem but for when you want to know what you can do. And that's usually a lot harder to find out by Googling.
Re:Question (Score:3)
I'm referring more to common things like getting basic peripherals working, or a graphics card, or setting up XFree86 to use your monitor correctly, or getting a mousewheel to work. All things that automatically work in certain other operating systems.
Re:Question (Score:2)
Re:Question (Score:2)
All things that sometimes work automatically and sometimes don't in "certain other operating systems". I have visited MS and third-party knowledge bases for ALL of those things (well, not for getting XFree86 to use the monitor correctly, but DirectX? Sure)
Re:Question (Score:5, Insightful)
Does it strike anyone as a bit of a negative attribute that you have to have a massive knowledgebase to use your operating system?
The answer is that you don't, the wiki is more aimed at people who just want to find something out about Linux (ie 'How do they read e-mail without Outlook?'), are looking for a good distribution to try, or are curious and want to learn more about it (hence the technical parts)
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.
Sounds like your distro isn't that recent (or that you're useing Slack or Debian, in which case the Howtos are to be expected). Modern Distros generally take care of your mouse and sound card in a few seconds while you watch the progress bar
Not to diss you, but Linux just isn't that hard anymore.
Dear mods--a BIGGER question (Score:3, Insightful)
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?
Re:Question (Score:5, Informative)
You don't need a massive knowledge base to use Linux. The main difference is that documentation for Linux usually covers a lot more than just the kernel. It usually covers a ton of popular programs in addition to the kernel, including two entirely different desktops. Not to mention the fact that you can change so many more parameters in Linux than you can in Windows or MacOSX. For example, it is fairly simple to install another kernel if you want to on most Linux distributions but you also have the ability to compile your own kernel. This will take more documentation than either Windows or OSX but it hasn't made anything more difficult.
Re:Question (Score:3, Insightful)
Re:Question (Score:2, Informative)
However, quite a few of the HOWTO's cover things such as setting up an X-Terminal network, remote booting, setting up your own DNS server, and things of that nature. For those things, a HOWTO is great - I learned bind by reading the HOWTO enough to get it up and running, then reading through the bind docs and RFC's t
Re:Question (Score:2)
BTW X doesn't have anything to do with sound cards. Maybe you meant esd or something?
Re:Question (Score:4, Insightful)
Ignorance is bliss, maybe? Because you can find out just about anything Microsoft related via Technet. This includes troubleshooting, white papers, documents on best practices, general network design, security, etc.
If you actaully work with MS products, and dont use technet, you are definitely not working smart.
It would be NICE to say you dont need a large database, but it would be pretty ignorant to think that anything could be that way. Auto mechanics, lawyers, doctors, EVERYONE who works on complex matters is going to need a well organized resource to help them out. There is far too many details for someone to think they will know it all.
The only people who seem like they never encounter problems are those who are just good at troubleshooting and using their reference sources.
They have that.... (Score:5, Funny)
To clarify! (Score:2)
Bad link - Corrected (Score:3, Informative)
Re:To clarify! (Score:5, Informative)
Another personal favorite... (Score:5, Funny)
Re:Another personal favorite... (Score:2, Funny)
Re:They have that.... (Score:5, Insightful)
The truth is pretty simple. Google's not enough. Sometimes for the most obscure questions, either most people consider you a nub and tell you to RFTM (which, in many cases, no manual exists), or they don't know themselves how to solve the problem. So, we often spend hours and hours going through google to find out how to get X hardware to work on Y configuration to find that Alan Cox had brilliantly broken my soundcard in 2.4.20... These are the kinds of things that there really should be a one-stop place to find what you need..
Surprisingly, it's taken this long for anyone to realize this...
Re:They have that.... (Score:4, Informative)
Re:They have that.... (Score:5, Insightful)
Say you need to make a file over 2GB (very common in video processing) and you stumble across this page [netcom.com]. You come away thinking linux doesn't support large files, when really it does. In this case you can scroll all the way to the bottom and the author is nice enough to have timestamped the page - 1998. But still, how do you know whether the old information is outdated? Even if you choose some arbitrary cutoff date ("information after Jan 1, 2003 is likely to be fresh") how do you tell google to only find information after that date? You can't.
Unfortunately there's no easy solution to the problem of outdated information. Useful documentation takes attention and manpower. But perhaps an easily modifiable Wikki-format will encourage more updates and more participation than comparable efforts such as The Linux Documentation Project [slashdot.org], which is really just a smattering of FAQs, HOWTO-s, guides, and man pages with no real coherence - full of duplication and stale information.
Re:They have that.... (Score:3, Informative)
Re:They have that.... (Score:2)
I like this idea more for the people who are starting out using linux. I've been on it for a while, and have had my share of problems looking for simple answers to simple questions. Something like this will go a long way to providing a solid resource for people new to the OS, which is a very good thing.
Of course, being a Wiki and all, it applies that same supercool open source ethos to the answering of questions. You can put that information about large file sizes up there to help someone out when they
Re:They have that.... (Score:2)
I've just been into linuxquestions's wiki page and browsed into X11 configuration... It tells me that mouse is the hardest thing to get going. Rubbish. Absolutely r
Re:They have that.... (Score:2)
It certainly was true for me on both X11 installs (manual ones - first Debian then Gentoo). Getting the USB mouse recognized by the kernel in the first place was confusing, but it took me even longer to make X11 look for a USB mouse with 3 buttons and a wheel - not that the wheel worked in all apps even when the X11 configuration seemed/
Selective Intelligence (Score:2, Insightful)
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.
Re:Selective Intelligence (Score:4, Informative)
Since they are listed down the side of the page and not mixed in with the search results and the "Sponsored Links" at the top, it's kind of hard to mix them up.
And if you can buy better results from google, please let me know. Google surfers convert at a much higher rate than all of the other PPC options.
Re:They have that.... (Score:2)
Did the program "break execution", "abend", "dump core", "crap out", "stop working", "fault in the xyz subroutine"?
Sometimes the word one person would use would be completely different than another.
Or, if you simplify your search too much to avoid the above, you get so many hits, most not relevant.
But hey...it's still better than the MS Knowledgebase for th
Re:then... (Score:5, Funny)
If there is no answer on Google (groups that is), then there is no question.
Re:then... (Score:2)
"Si in googlis non est, ergo non est."
Eh? Largest? Huh? (Score:5, Informative)
What about The Linux Documentation Project [tldp.org]? Provides plenty of knowledge to me about pretty much anything Linux related...
Re:Eh? Largest? Huh? (Score:3, Insightful)
The Wikipedia should be more up-to-date.
Then again - I just Google. . . . .
Re:Eh? Largest? Huh? (Score:3, Informative)
Re:Eh? Largest? Huh? (Score:3, Interesting)
Re:Eh? Largest? Huh? (Score:4, Informative)
I mean it's a nice idea and most of the guides that were around when I first started using linux (about 9-10 years ago) were excelent. In fact, some of them are still useful but they need updating!
TLDP also needs a redesign of their site. Maybe have a section for newbies and then other sections based on what you want help on instead of just grouping all the HOWTOs together. It's a beast to look through. If I want to find information on an editor I need to know to look for vi or Emacs.. it would be nice to click on an Editors section and see all the documentation relating to editors.
Re:Eh? Largest? Huh? (Score:3, Insightful)
The difference is that this is a wiki. Anyone can update the wiki. Updating LDP docs ain't that easy - and goes through a lot of (and much needed) review cycles which takes quite some time before it is actually published.
This wiki knowledgebase idea is novel, in that it will allow more docs, pushed to the users in much more rapid fashion.
Re:Eh? Largest? Huh? (Score:2)
Re:Eh? Largest? Huh? (Score:4, Funny)
Anyone can update the wiki.
I can't wait to see the changelog for the article, "So, Which Linux Distribution is Right for Me?"
Re:Eh? Largest? Huh? (Score:3, Insightful)
For example, there currently is only _one_ Chinese support on Linux FAQ, and it not only does not talk about Simplified Chinese, which is, last time I checked, a standard, but is terribly, terribly outdated.
The very structure of LinuxQuestions.org may allow them to produce documentation that i
Re:Eh? Largest? Huh? (Score:2, Insightful)
A wiki would solve this problem, since it is so easy to add information.
I've read many howtos with information that has been slightly wrong, a path has changed, a new configuration option has been added. Usually it has been quite obvi
Re:Eh? Largest? Huh? (Score:5, Funny)
For those of you who mercifully missed out on this era, generally a HOWTO would
(a) Point you to software that no longer compiled on any platform known to man
(b) Advise you to use configuration options that existed only in development versions and never worked even then.
(c) Assume that you know how to use an equally complex program that has its own HOWTO which points you back to the one you started with.
(d) give great explanations like: Ok for this file you just use syntax like a=1 to set a equal to 1. For example to make it fly to the moon just type:
$foo53r45$::564.config <-> FALSE
DiskBo$xInvolvement.Underpantsgnome = $PROFIT$
etc...
I am exaggerating VERY slightly. Anyone remember the DIP HOWTO? According to legend the suicide rate among Linux users tripled within three weeks of its release.
Great! (Score:5, Interesting)
My hope is that this database doesn't grow out of control with redundant and/or meaningless data.
Re:Great! (Score:3, Funny)
yeah, another slashdot would be too much for the internet to handle
Re:Great! (Score:2)
gunzip
tar xvf
perl Makefile.PL
make
make test
make install
run
WTF!!!
search google
repeat
Re:Great! (Score:2)
Then you'll like Wiki (Score:5, Informative)
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 [wikipedia.com]. It's totally self-policing and very well-kempt. You will quickly move from scared to excited.
FYI (Score:3, Informative)
rats! (Score:4, Insightful)
The one thing [linuxquestions.org] 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).
Re:rats! (Score:2)
Re:rats! (Score:3, Informative)
Now if you're unfortunate enough to be using an ATI card (and fortunate enough to get the drivers working, I did, once, and then just again 2 hours ago but t
Re:rats! (Score:4, Informative)
The Loki installer for Unreal Tournament is still freely downloadable, for those with the Windows version. You can play that.
The binaries for Quake and Quake 2 are still linked to glide (I think). Fortunately, both games' source is under the GPL, so you can recompile for GLX.
There are many ATI drivers (XFree86, ATI's binaries, DRI, Gatos), but none of them do everything well (or so I've heard). NVidia's drivers are wonderful, but binary-only ([sigh]... NDA...). I wish they were able to let us help with the drivers. XFree86's nv driver is still pretty good.
You can use WINE to play many games non-native to Linux, like Half-Life (Damn You, Valve!(TM)), but it usually takes some tinkering. There is WineX, a commercial fork of WINE that specializes in getting games to work.
Finally, just have a look around; you'd be surprised at what's available.
Re:rats! (Score:2, Informative)
Re:rats! (Score:2, Informative)
Must have chosen LinuxQuestions.org... (Score:3, Funny)
Re:Must have chosen LinuxQuestions.org... (Score:2)
Software Knowledge = Hard (Score:5, Insightful)
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.
Re:Software Knowledge = Hard (Score:5, Insightful)
Re:Software Knowledge = Hard (Score:4, Insightful)
There are plenty of more reasons behind Linux's adoption rate, but think about it this way; if Microsoft and all of it's software was found to be illegal and everyone had to switch over tomorrow, how many governments, how many libraries, how many volumes of people would never touch a computer again because learning new software was too hard, due to people who knew how to use it feeling superior? GNU is all about sharing the knowledge, it's really time that we linux users take to the meaning of the GPL, and not just use it as a license to throw in people's faces.
Re:Software Knowledge = Hard (Score:2)
Yawn. That's not what it's about. A little program like ufed lets you set flags saying that you'll never need ldap support for any programs that you install. Then, next time you "emerge mod_php", it will leave out ldap support. (I know, that's a bad example because you have to specifically enable ldap support in it, but hey.) And you don't compile by hand. emerge package does it all for you. Try it out. It's go
Re:Software Knowledge = Hard (Score:2, Interesting)
Unix => Unices
Matrix => Matrices
I don't know... I'm just asking.
Linux Documentation project (Score:2)
19 Articles!!! (Score:5, Insightful)
Re:19 Articles!!! (Score:2, Insightful)
yet another wiki (Score:4, Interesting)
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 [linuxquestions.org] before posting. registration is required, but email is optional.
Wikis everywhere (Score:5, Insightful)
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.
useful wiki application (Score:4, Funny)
Re:Wikis everywhere (Score:2)
Wiki has all the structure its users give it, including none at all. Wikis can be great, but they can also be worse than useless, including but not limited to faults such as outdated, derelict information, extremely confusing structure, layout and organisation, misinformation, and so on and so on. This is not a criticism of the Wiki idea as such, I'm just saying it's not a cure for everything. With good administration and main
Comment removed (Score:3, Insightful)
Already exists: (Score:2, Funny)
Re:Already exists: (Score:3, Informative)
apropos 'foo'
ls
ls
ls
info 'foo'
ls
ls
grep 'foo'
All that, and I still couldn't find any information about foo!
This is great untill (Score:5, Interesting)
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.
Re:This is great untill (Score:4, Insightful)
So what the linux questions wiki needs for reliability is a critical mass of users; the rest takes care of itself.
Re:This is great untill (Score:2)
I know this is beside your point, but I feel like nitpicking today.. Those of us who have tried this command, know that it wouldn't do as much damage as people believe. That's because it works recursively, alphabetically deleting all files. This means it'll start with /bin/, and will come to a stop when it gets to /bin/rm, leaving everything that comes after it (including everything in the other root-level directories) untouched. If you want to do the most da
Re:This is great untill (Score:2)
rm -rf / will do just as it advertises, without seemi
tips (Score:3, Informative)
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
linuxquestions not just linux (Score:5, Informative)
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
linuxquestions, huh? (Score:4, Interesting)
wikipedia.org???? (Score:3, Funny)
amazing site...
Problem-oriented documentation (Score:4, Interesting)
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.
wiki vs TLDP (Score:4, Interesting)
TLDP [tldp.org] 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 [linuxquestions.org] will be "it", I think a wiki aproach would be a great idea.
Why the opposition to docs or info? (Score:4, Interesting)
"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.
MediaWiki (Score:3, Informative)
MediaWiki is GPL-ed, and more programmers are always welcomed.
How do you protect a wiki? (Score:3, Interesting)
How can you make sure some numbnut doesn't get rid of useful stuff?
Re:How do you protect a wiki? (Score:2)
The wiki won't help if distributions don't chip in (Score:3, Insightful)
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.
Lacking in execution (Score:2)
Ratings? Freshness? (Score:2)
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 sco
Um, OpenFacts? (Score:4, Insightful)
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.
Thoughts from someone who's done it (Score:5, Informative)
Almost two years ago, a resourceful hacker at our Waikato Linux Users Group [wlug.org.nz] 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) [wlug.org.nz]). 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. [wlug.org.nz]
slash + the howtos (Score:3, Interesting)
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
wiki for source code (Score:4, Interesting)
Re:Bad idea? (Score:2)
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!