LQWiki - User contributions [en]

User talk:Cyclop

2005-03-20T10:05:09Z

Crazyeddie: INTERCAL copyright conflict

Noticed your summary of your edit of the [[INTERCAL]] article. I'm afraid we can't copy-and-paste Wikipedia material here. The Wikipedia uses the GNU Free Documentation License, which is mutually incompatible with the Creative Commons (attribution-sharealike variant) license we use here. We can't reuse GFDL material without additional explicit permission from the original copyright holders. In the case of the Wikipedia INTERCAL article, those copyright holders are very numereous, and some of them are anonymous. Getting permission from them simply isn't practical.

A bit of a bugger, but our hands are tied. I'm afraid I'm going to have to delete the article, which we'll resurrect until such time as we can roll our own, or come across a piece of license-compatible existing documentation that we can build on. Just remember to be careful about copyrights when incorporating copyrighted text into this wiki, or any, wiki. Don't worry about it this time - just about everybody makes that mistake sooner or later. [[User:Crazyeddie|Crazyeddie]] 05:05, Mar 20, 2005 (EST)

Talk:Linux installation

2005-03-16T20:33:06Z

Crazyeddie: forums template

:)

== installing intel pro 10/100 ethenet card ==

I have just installed red hat linux 7.2 on an IBM Thinkcentre. It has an onboard intel pro 10/100 ethernet card, however the auto probe does not see it.
I have tried entering the following in grub.conf:
append="ether=10,300,eth0"
But this does not install it.
I have an added complication that the X-window drivers are not happy with the graphics card either, so I can't run any of the windows-based tools.

Help!

{{forums}} [[User:Crazyeddie|Crazyeddie]] 15:33, Mar 16, 2005 (EST)

Talk:Gateway

2005-03-14T19:53:05Z

Crazyeddie: I wouldn't worry about it

Thanks SciYro - I'll mention it to Jeremy today --[[User:Skyline|Skyline]] 05:36, Oct 18, 2004 (EDT)

----

Isn't the external link to gateway inc relevant here? In wikipedia it would, but it isn't relevant to linux as far as I can see. - [[User:Bemoeial|Bemoeial]] 07:50, Mar 14, 2005 (EST)

The article is (partially) about Gateway Inc. I think a link to Gateway's website is relevant. Gateway might not have much/any Linux documentation, but they do have documentation on hardware that somebody might be running Linux on... Even if it is irrelevant, I don't think the link is going to do much harm. I wouldn't worry about it. [[User:Crazyeddie|Crazyeddie]] 14:53, Mar 14, 2005 (EST)

Default gateway

2005-03-14T18:03:15Z

Crazyeddie:

When sending a data packet over the network, the computer takes a look at its [[routing table]] to see where to send it. If it can't find a route to the destination by looking in its own routing table, it forward the packet to the address given as '''default gateway''', sometimes called the default route.

You could say that the default route is a last resort in the routing process, although the default gateway is used very frequently, at least on workstations with only one [[NIC|network card]] communicating with computers outside of the local network.

The command <tt>[[route]] -n</tt> can be used to show what default gateway is currently set.

Talk:Main Page

2005-03-11T08:43:42Z

Crazyeddie: GPL clarification

Some older posts have been moved here: [[Talk:Main Page (archive)]] for purposes of readablity.

Where can I find Phpwiki? Because my website [http://www.paper-translation.com Academy Translation Web] is bulit by php and I want to add wiki to it.

==Suggestions for links==
* [[Open source operating systems]] BSD, etc.
* [[HOWTO]] section

* Where's the best place for cronic hardware/kernel problems? There is a largish problem revolving around APIC (not ACPI) timing issues under various linux kernels that cause the machine to freeze up hard. I'd like to add information about that, and I'm sure there are other cronic issues that deserve to have some space in the WIKI as well. -Scott Miller (5mi11er)

I'll answer in reverse order. I'd suggest creating a new hardware-and-kernel page, link to it from both the hardware and kernel page, and then link to your (new) APIC page. Your guess is as good as mine though, I've never even ''heard'' of APIC before. (I'm just barely miss being a Linux noob - the Dilbert Principle at work I guess :-)).

As for new links from the Main Page - the moderator's council (or whatever you want to call it) is currently discussing ways to implement Featured Pages. We've noticed that the Wikipedia (the uber-wiki) has a hierarchial, quasi-Table of Contents area which is similar to our current front page. However, this area is far towards the bottom of the front page, and I doubt it gets much use. What we think happened is that they started out with a quasi-TOC front page like ours, but then moved toward the current Featured Pages-dominated version of today. A quasi-TOC front page provides a skeleton for a young wiki to grow on, but as a wiki matures, it becomes harder to link to important articles. This is where Featured Pages comes in. The front page of a wiki is not a TOC, but rather a hub page that links out to the most important pages of the wiki.

So we're not ruling out new front page links by any means, but it might be wise to consider wether or not you would like a page as a Featured Page or a permament link. I will pass your suggestion along to the rest of the council. Any other moderators want to weigh in?

Anyway, welcome to the LQwiki. A obviously experienced Linux user like yourself is a welcome addition. You might want to sign your posts with four tildes - the wiki engine will translate it to a link to your userpage and a timestamp. [[User:Crazyeddie|Crazyeddie]] 03:03, Aug 25, 2004 (EDT)

==Spam links==
Just deleted what appeared to be spam links to german horoscope sites. If those were legit, someone let me know. [[User:Crazyeddie|Crazyeddie]] 03:19, Jul 3, 2004 (EDT)
:That's ok - In order to assess the appropriateness of material, all content must currently be in English, and any external sites which are linked to must also be English language based - [[LQWiki:Policies#General_policies|General policies]]

:-- [[User:Skyline|Skyline]] 06:23, Jul 3, 2004 (EDT)

==Advocacy article==
Should there be an Advocacy section linked from the Main Page?
--[[User:Bunyip|Bunyip]] 08:52, Jul 23, 2004 (EDT)

===Importing Advocacy article from Linux Documentation Project===
[[User:Crazyeddie|Crazyeddie]] 11:54, Jul 23, 2004 (EDT):Perhaps, but an Advocacy article doesn't exist yet. There's an advocacy article over at the [[Linux Documentation Project]], but we would have to get permission from the author of the article, because it looks like their license is not compatible with Creative Commons. Here's the copyright info:

===TLDP Advocacy HOWTO's copyright information===
This mini-HOWTO is Copyright © 1996-2000 by Paul L. Rogers. All rights reserved.

A verbatim copy may be reproduced or distributed in any medium physical or electronic without permission of the author. Translations are similarly permitted without express permission if it includes a notice on who translated it.

Short quotes may be used without prior consent by the author. Derivative work and partial distributions of the Advocacy mini-HOWTO must be accompanied with either a verbatim copy of this file or a pointer to the verbatim copy.

Commercial redistribution is allowed and encouraged; however, the author would like to be notified of any such distributions.

In short, we wish to promote dissemination of this information through as many channels as possible. However, we do wish to retain copyright on the HOWTO documents, and would like to be notified of any plans to redistribute the HOWTOs.

We further want that all information provided in the HOWTOs is disseminated. If you have questions, please contact Tim Bynum, the Linux HOWTO coordinator, at linux-howto@sunsite.unc.edu.

===Responses===
: The "Derivative work and partial distributions of the Advocacy mini-HOWTO must be accompanied with either a verbatim copy of this file or a pointer to the verbatim copy" bit would seem to indicate that we could add the HOWTO(s) to the wiki (it would become a "Derivative work" after the first edit), as long as we include a link to the original verbatim copy, which should not be a problem.
: [[User:Jeremy|Jeremy]] 15:27, Jul 23, 2004 (EDT)

:Yes, but could we in good faith release it under the Creative Commons and let others reuse it from us? I think you might be right, but I would feel better if we got explicit permission from the author. At least there is a single author, unlike most Wikipedia articles. I was planning on trying to incorporate TLDP HOWTOs, as soon as I got to a certain point in the [[Jargon File]] incorporation, so I've had some time to think about this. Do you have any contacts at TLDP, or should I just email the guy myself? [[User:Crazyeddie|Crazyeddie]] 18:34, Jul 23, 2004 (EDT)

===TLDP manifesto===
:: Looking at http://www.tldp.org/manifesto.html I see:
"5. LICENSE REQUIREMENTS

Anyone may copy and distribute (sell or give away) LDP documents (or other LDP works) in any media and/or format. No fees are required to be paid to the authors. It is not required that the documents be modifiable, but it is encouraged.

You can come up with your own license terms that satisfy these conditions, or you can use a previously prepared license. The LDP has a boilerplate license that you can use if you wish. Some people like to use the GPL, while others write their own. There is a project underway to create a special GPL license just for documents and this may turn out to be a good choice.

The copyright for each document should be in the name of the principal authors. "The Linux Documentation Project" isn't a formal entity and thus can't be used as a copyright owner. "

===Responses===
::This seems to fit exactly in with what we want to do. I'll contact TLDP just to verify, however. I'll post the outcome here.
:: [[User:Jeremy|Jeremy]] 00:53, Jul 24, 2004 (EDT)
::: After discussing this with TLDP, I am going to revisit the ability to add GFDL items to the LQ Wiki. Stay tuned. [[User:Jeremy|Jeremy]] 12:17, Jul 25, 2004 (EDT)

How would that work? I thought that the Creative Commons/GFDL incompatibility was pretty well established. "East is East and West is West, and ne'er the twain shall meet." As the GFDL and the CC are presently written, material under one can't be released under the other without the permission of the copyright holder (the original author in most cases). There's rumors that the FSF and the Creative Commons people are working on that issue, but until then, we're pretty well stuck with just asking for permission. Not that I would ''mind'' an easier solution, but I just don't think it's possible.[[User:Crazyeddie|Crazyeddie]] 16:40, Jul 26, 2004 (EDT)

:It would work something like this. When you enter in a doc, there would be a "this is GFDL" checkbox. That doc would then be under the GFDL and *not* the CC. There are a few problems with this, and it could get complicated quite quickly, so It's not a definite addition at this point, just somehting we are exploring. [[User:Jeremy|Jeremy]] 17:50, Jul 26, 2004 (EDT)

Hmmm. That would be possible if it was a new article, and that the changes made to it were also GFDLed. But it would lead to some articles being GFDL, some being CC. A hack, but we're kinda in a corner. I think we'd still be better off contacting the original authors and getting CC permission, since this would increase the number of options available to downstream users (they would be able to use our version under the CC and the original under the GFDL), but I'd be willing to go along if there is consensus for it. [[User:Crazyeddie|Crazyeddie]] 15:32, Jul 27, 2004 (EDT)

Jeremy, if you're still seriously considering dual-licensing, you might want to look at this first: http://en.wikipedia.org/wiki/Wikipedia_talk:Creative_commons_migration Keep in mind that I did not seriously expect this to be accepted, I was more trying to raise awareness of the problem. I would not have even suggested it if I hadn't (which I still do!) believed that the Creative Commons by-sa license is superior to the GFDL. [[User:Crazyeddie|Crazyeddie]] 19:06, Aug 2, 2004 (EDT)

----
How about changing the notice at the bottom of each edit page to ... "WITHOUT PERMISSION from the authors to post under LQWiki's [http://creativecommons.org/licenses/by-sa/1.0/ Creative Commons] license." You should add that each page is owned by the authors listed in its history. [[User:TomFrayne|TomFrayne]] 09:58, Jul 24, 2004 (EDT)

===Crazyeddie's extended post===
(added sectioning for readability) That would be an ugly hack. I think I'd rather roll our own HOWTOs than go through that. Anyway, I'm looking at this from the point of view of a general solution rather than just importing this one article. Some reasons I think we should contact the article authors and ask for explicit permission:
#The Manifesto is a suggestion or a guideline for the TLDP contributors to use when deciding what licensing scheme to use. It doesn't look like they're too big on enforcing it, or at least a few of the older articles didn't even bother appending a license. It is not a license in and of itself.
#Even if the contributors do follow the Manifesto's guidelines, they don't have to allow modifications.
#They may have released in under a copyleft modifiable license that isn't compatible with the Creative Commons such as the GFDL. I'm not sure, but I don't think the GPL is Creative Commons compatible either.
#Like the manifesto says, the LDP is not the copyright holder, so they can't unilaterally give permission.
#Even if we could use an article without permission, it would be good form to tell the author about it. For example, if the author can no longer maintain or host the original, he or she could tell their users where they could go to get an updated copy. It occurs to me that the LDP could see us as competition. It might be a good idea to stress that they can backport any changes under the Creative Commons. Anybody else have any ideas that might smooth the path?
#Letting an experienced technical writer know about this wiki is a Good Thing. This subproject gives us a good excuse.

:If you would like to start contacting authors of articles you think should be added, please feel free to do so. If you need anything from our end, let me know. [[User:Jeremy|Jeremy]] 17:54, Jul 26, 2004 (EDT)

:Okay. I'll use [[Talk:Linux Documentation Project]] as a sort of improvised "command center" in case somebody else wants to help out/take over. A good first step would be to send off a general email to their mailing list. (I'll make sure that I mention that I'm doing this as my own intiative, not as an 'offical' LQwiki project.) If you don't think it's confidental or something, could you send me a copy of the correspondence you had with them? After the general email, I'll try contacting the Advocacy HOWTO's author. If anybody has suggestions on what to incorporate next, head over to the LDP talk and let me know. [[User:Crazyeddie|Crazyeddie]] 15:23, Jul 27, 2004 (EDT)

:I have a draft email up on [[Talk:Linux Documentation Project]]. Please go idiotproof it everybody! [[User:Crazyeddie|Crazyeddie]] 16:14, Jul 27, 2004 (EDT)

::Seems completely idiotless. :) [[User:Digiot|Digiot]] 17:17, Jul 27, 2004 (EDT)

I'm placing the email on hold until I can rewrite it, to reflect my promotion to moderator. (Since I'm now moderator, it pretty much has to be an offical LQwiki project.) Also, it occurs to me that Grokdoc might want in on this. [[User:Crazyeddie|Crazyeddie]] 19:10, Aug 2, 2004 (EDT)

:Have a list of LDP howtos up over at [[Talk:Linux Documentation Project]]. Take a look over and let me know if there is a howto you want me to put on the to-do list. [[User:Crazyeddie|Crazyeddie]] 18:50, Jul 28, 2004 (EDT)

::Seems like to me the best principle would just be to prioritize them into 'niche interest' and 'outdated for a reason' and then take the remaining generally important and relevant topics and do them in chronological order. A major problem is outdated data and attacking that first would probably be most useful and most suited to wikification. Also, those authors who have abandoned or rarely update their topics might be the most receptive to passing on the maintenance of them, including relicensing or whatever it takes. [[User:Digiot|Digiot]] 22:31, Jul 28, 2004 (EDT)

:But on the other hand, abandoned or rarely updated documents also will be the hardest to get permission for. But I get your drift. I'll go over the list myself tomorrow, but I would like to know if there is any particular ones people want. This is going to take long enough that there is no reason to stick to any particular method if there's one that somebody really wants. I'll rig up some sort of voting system I suppose. I've already taken off some "removed for review" entries and I'm going to go back and remove some internationilization howtos, since those are usually written in a different language. (I'll also replace the sectioning with bullet points - didn't realize how ugly it would look until I was halfway through.) [[User:Crazyeddie|Crazyeddie]] 01:31, Jul 29, 2004 (EDT)

Okay, voting is setup (kinda). [[User:Crazyeddie|Crazyeddie]] 19:10, Aug 2, 2004 (EDT)

==Disclaimer==
A bit off the main topic, but one thing I noticed over at the TLDP... It might be wise to have a "No Warranty, As Is" type notice at the bottom of the page, down in the copyright notices. Unlike the Wikipedia (who have a similar notice, but a bit more buried) we're handing out documentation which could cause serious damage if used improperly, or if it is incorrect. In addition to it being a just plain good idea, some of the TLDP articles have that as their sole condition for modification and redistribution. If we actually do have something like that already, well, my friends don't call me "Captain Oblivious" for nothing. [[User:Crazyeddie|Crazyeddie]] 13:24, Jul 24, 2004 (EDT)

:Good idea - a disclaimer has been added. Thanks. [[User:Jeremy|Jeremy]] 12:41, Jul 25, 2004 (EDT)

I've edited it to include contributors under the "don't sue us!" umbrella. [[User:Crazyeddie|Crazyeddie]] 18:48, Aug 2, 2004 (EDT)

==Forum Revisited==
Several people have asked about a general LQwiki discussion forum. Does anybody have any objections to using this talk page as such a forum? [[User:Crazyeddie|Crazyeddie]] 14:02, Jul 24, 2004 (EDT)

== wiki software link ==

Is there a link on the main page or somewhere at the bottom where people can see what wiki software is being used here. It might be nice to link to the software's homepage, assuming it is free. I looks mostly like the software used on wikipedia, with some very nice modifications. --[[User:Paraphelion|Paraphelion]] 06:50, Feb 9, 2005 (EST)

: We do infact use MediaWiki, which is mentioned in the [[LQWiki:FAQ|FAQ]]. [[User:Jeremy|Jeremy]] 11:31, Feb 10, 2005 (EST)

:: Where is the FAQ linked? It might be nice to also mention this information in "About LQ Wiki", especially because the link is on each page. There's no reason not to have it in both. I'm surprised that the FAQ isn't linked on the about page. --[[User:Paraphelion|Paraphelion]] 02:54, Feb 15, 2005 (EST)

Could we open up our modifications to the community? It seems like there is some interest in them, and it's possible that some downstream users will make modifications that we might find useful... 15:24, Feb 10, 2005 (EST)

: At this time we realistically don't have the resources to support a release. More and more, the changes are mostly cosmetic and not functional anyway. What we will definitely do moving forward is push bug fixes (and features if there is interest) upstream so that everyone can benefit. [[User:Jeremy|Jeremy]] 22:57, Feb 10, 2005 (EST)

I'm not suggesting a full release. I'm suggesting making our patches available. For the spellchecker, for example. Last I heard, MediaWiki is reluctant to uptake spellchecking because Wikipedia servers can't handle the load. (Or at least that's what the rumors say.) If enough downstream users show an interest, I think they might change their minds. [[User:Crazyeddie|Crazyeddie]] 03:23, Feb 11, 2005 (EST)

I remember that our modifications aren't in patch form... Could we possibly give read-only access to our cvs? Are we using a cvs? [[User:Crazyeddie|Crazyeddie]] 03:41, Feb 11, 2005 (EST)

: CVS is not used for the LQ Wiki. [[User:Jeremy|Jeremy]] 16:51, Feb 11, 2005 (EST)

How about just an archive of our current PHP code? Surely y'all make backups? [[User:Crazyeddie|Crazyeddie]] 17:26, Feb 11, 2005 (EST)

: As I mentioned earlier, just releasing the code without being able to support it in any way is probably not in anyones best interest. Aside from that, I don't want it to be seen as a fork, which it isn't. Users will get 100% of the benefits by us pushing bugfixes upstream. If there is interest in the spell checker (or anything else we have here) upstream we'd be more than happy to push that too. [[User:Jeremy|Jeremy]] 10:07, Feb 13, 2005 (EST)

I'm not talking about a formal fork, with the support and code maintenance involved. I'm talking about an open documentation project, based on open source software, making its modifications to that software public.

Ideally, since we're only making modifications, not a full fork, we should make those modifications available in the form of patches. In addition to being helpful for third-party users of MediaWiki software, it would help us when it comes time for us to upgrade to the next MediaWiki release, and it would make it easier for MediaWiki to upload our modifications. I fully agree that getting MediaWiki to upload our mods is the best solution, since that would mean that we would no longer have to maintain the code ourselves.

The current method of handing out our modifications, which consists of: "email Jeremy, and he'll fish out the bit you need and email it to you" is not convenient for either party. I think I've seen about six requests for our code in wiki, and I doubt that many requests have made it to you.

As I said, I think the ideal solution is to make our modifications available in patch form. But I realize that such a move would probably involve a lot of work, and I'm trying to suggest a compromise solution. Instead of having to exchange emails, all you would have to do is grunt "Code's over there. Help yourself." We should make it clear that we don't support the code, we're just handing it out to anybody who wants it. If somebody finds a bug, they can tell us about it, but we'll probably only fix it if the bug directly affects us. Patches would be welcome.

Our main added feature is spellchecking. There has been some interest in a spellchecking feature over at the Wikipedia. However, spellchecking would put an additional strain on their servers, so they haven't rolled their own yet. I think MediaWiki would only put in spellchecking as an optional feature if there was strong interest downstream. Some downstream wikis using an experimental and unsupported spellchecker would be a strong argument in favor of formal inclusion of a spellchecker option.

Something similar could be said for any additional feature we might make in the future. If we're adding the feature ourselves, then there is probably some reason why it isn't in the MediaWiki code already, and it will only be added as an option if there is strong downstream interest. The existance of a patch would no doubt help.

Even if one of our modifications is cosmetic, and not worthy of being included in MediaWiki, we should still make it available. There is no telling what an administrator might find helpful.

The LQwiki's main need right now is additional contributors, ideally ones with experience in Linux and/or wikis. Having wiki patches available would give us greater visibility in the wiki community, especially with administrators.

We might even attract some additional administration staff, who might be willing to help with other LQ projects.

Lastly, I think that providing documentation for wiki administration falls under the subject matter of this wiki. I don't think it's a stretch to include wiki code cookbooks. [[User:Crazyeddie|Crazyeddie]] 15:46, Feb 13, 2005 (EST)

We would not be providing a sealed software package to a helpless user. We would be providing prewritten cookbook code to an administrator, who would hopefully have the coding skills needed to modify our code to their own situation. [[User:Crazyeddie|Crazyeddie]] 17:00, Feb 13, 2005 (EST)

Because MediaWiki is distributed under the GPL, you MUST make your modifications available to the public in some manner. A good reason to roll your changes back into the original is so that you don't have to re-patch your code whenever you want to upgrade to the new version. [[User:Xxxyyy|Xxxyyy]] 19:28, Mar 10, 2005 (EST)

Correction, we only have to provide the code if we redistribute the program. That's my understanding, at least. If we were handing out or selling binaries we would have to make the code available at no more cost than the cost of physically creating the media. Since we ''aren't'' handing out binaries, but only using the MediaWiki engine internally, we aren't required by the GPL to hand out code. Google, for example, uses Linux to power their proprietary search engine magic. They, or so I have heard, did make modifications to Fedora Linux in order to use it in their operations, but since they only use it internally, they don't have to hand out their top-secret secret sauce.

I just happen to think that handing out our modifications is a good idea. To a certain extent, Jeremy agrees with me. Where we differ is how to go about it.

Jeremy would love to roll back our changes to MediaWiki. Problem is, most of our changes are cosmetic, only of use to us - or so we think, no telling what another wiki-admin might do with it. MediaWiki hasn't shown much interest in adapting our changes that aren't cosmetic. The main example being the spellchecker. (Making our code more easily available might change that though.)

I'm supporting making our code available to anyone who passes by. Right now, you could get the code by emailing Jeremy (I think, don't quote me on that), but that's not exactly convenient for anybody concerened.

Jeremy is worried that if we make our code easily available, people will think we're doing our own offical fork, and expect us to maintain it and provide support. Our coding room, which consists of exactly two part-time coders, who also keep the entire LQ site up and running, simply doesn't have the resources to do that.

I'd like some compromise plan - make our modifications easily available, but also stave off any requests for support with a clear, upfront, STFU. [[User:Crazyeddie|Crazyeddie]] 03:43, Mar 11, 2005 (EST)

Talk:Game List

2005-03-10T17:48:15Z

Crazyeddie:

I would suggest organizing the list into: open source, closed source but native, and under emulation. Organize it into genre after that. [[User:Crazyeddie|Crazyeddie]] 15:25, Jan 22, 2005 (EST)

: Sounds like a good plan to me. [[User:Jeremy|Jeremy]] 18:52, Jan 22, 2005 (EST)

SciYro, since you're doing the actual work, it's your call. I don't think the matter is important enough for a vote or consensus poll or whatever. But it might save some time if we sat down and worked out how we want to organize this thing. I think your way might be better than mine. Remember that non-native games have been declared ontopic, provided that the article focuses on getting emulation running. [[User:Crazyeddie|Crazyeddie]] 16:43, Jan 23, 2005 (EST)

yes, i was planning to put non-native apps into a different page for people to see how well there windows games can be run under some of the windows emulators, as it seemed to me to be a different topic then what games exist for Linux. -- SciYro

Sounds good. Might also be good to have a single page on emulation tips in general, and then break it down into tips for each individual game - either in subsections or seperate articles, depending on length. [[User:Crazyeddie|Crazyeddie]] 17:42, Jan 23, 2005 (EST)

-----------------

Could someone who knows the loki games move them over from [[gaming]] onto this page?, i cant seem to find any relavent info on them besides they are binary, ported to native linux, and cost money (i cant find any descrition on them at all, nor can i play them to see) -- SciYro

Well, for starters, I'm pretty sure Loki went belly-up a long time ago. That might be why there isn't much information out there. [[User:Crazyeddie|Crazyeddie]] 12:45, Mar 10, 2005 (EST)

[http://en.wikipedia.org/wiki/Loki_Games Here's] the wikipedia article. Remember to paraphrase. Looks like they went out of business in 2002. They made ports of existing windows games, and did a few things that made the ports run better on Linux. [[User:Crazyeddie|Crazyeddie]] 12:47, Mar 10, 2005 (EST)

Talk:Game List

2005-03-10T17:47:54Z

Crazyeddie: loki's wikipedia link

I would suggest organizing the list into: open source, closed source but native, and under emulation. Organize it into genre after that. [[User:Crazyeddie|Crazyeddie]] 15:25, Jan 22, 2005 (EST)

: Sounds like a good plan to me. [[User:Jeremy|Jeremy]] 18:52, Jan 22, 2005 (EST)

SciYro, since you're doing the actual work, it's your call. I don't think the matter is important enough for a vote or consensus poll or whatever. But it might save some time if we sat down and worked out how we want to organize this thing. I think your way might be better than mine. Remember that non-native games have been declared ontopic, provided that the article focuses on getting emulation running. [[User:Crazyeddie|Crazyeddie]] 16:43, Jan 23, 2005 (EST)

yes, i was planning to put non-native apps into a different page for people to see how well there windows games can be run under some of the windows emulators, as it seemed to me to be a different topic then what games exist for Linux. -- SciYro

Sounds good. Might also be good to have a single page on emulation tips in general, and then break it down into tips for each individual game - either in subsections or seperate articles, depending on length. [[User:Crazyeddie|Crazyeddie]] 17:42, Jan 23, 2005 (EST)

-----------------

Could someone who knows the loki games move them over from [[gaming]] onto this page?, i cant seem to find any relavent info on them besides they are binary, ported to native linux, and cost money (i cant find any descrition on them at all, nor can i play them to see) -- SciYro

Well, for starters, I'm pretty sure Loki went belly-up a long time ago. That might be why there isn't much information out there. [[User:Crazyeddie|Crazyeddie]] 12:45, Mar 10, 2005 (EST)

[[http://en.wikipedia.org/wiki/Loki_Games Here's]] the wikipedia article. Remember to paraphrase. Looks like they went out of business in 2002. They made ports of existing windows games, and did a few things that made the ports run better on Linux. [[User:Crazyeddie|Crazyeddie]] 12:47, Mar 10, 2005 (EST)

Talk:Game List

2005-03-10T17:45:19Z

Crazyeddie: loki

Connect to the internet via dial-up connection

2005-03-08T05:42:28Z

Crazyeddie: End User Manual

'''Dial-up''' refers to a type of [[Internet]] connection. The name is derived from the fact that you must dial (in the same way you dial a phone) your [[ISP]] ('''I'''nternet '''S'''ervice '''P'''rovider)to connect to the Internet. Dial-up is also referred to as 56K, which pertains to the theoretical '''56Kbps''' ('''56''' '''K'''ilobits '''p'''er '''s'''econd) maximum speed of Dial-up.

Dial-up connections operate over standard voice phone lines, and use frequencies similar to voice transmissions. For this reason, it is not possible use a Dial-up Internet connection and phone on the same line at the same time. It also means that the phone company does not have to reconfigure your line for you to use Dial-up Internet. In order to use Dial-up however, you will need to purchase a Dial-up [[modem]] if your computer is not already equipped with one, and create an account with a suitable [[ISP]].

Because Dial-up requires minimal hardware or setup, it is cheaper than alternatives such as [[broadband]]. Unfortunately, because Dial-up uses voice frequencies to transmit data, it is also slow. As mentioned above, the maximum theoretical speed is 56 Kilobits per second. See [[bit]] and [[byte]] for information on how much this is. Unfortunately, most users will be lucky to get speeds in the high 40's, due to transmission and line quality issues.

==See also==
*[[End User Manual:Accessing the Internet#Dial-up_Connectivity]] (part of the [[End User Manual]])

User talk:Kainam

2005-03-08T05:39:52Z

Crazyeddie: don't sign articles

You don't have to sign articles. The wiki software takes care of that with the history feature. [[User:Crazyeddie|Crazyeddie]] 00:39, Mar 8, 2005 (EST)

Wheel

2005-03-08T05:38:54Z

Crazyeddie: formatting

'''Wheel''' is typically the name of the group for priveleged users on a Linux or Unix system. Can be thought of as the 'Administrators' group. Usually you don't want to add people to this group unless you want them to have very-near root priveleges.

==See also==
*[[root]]
*[[group]]

Talk:Ps

2005-03-04T20:39:54Z

Crazyeddie: forums template

How do I kill all processes owned by a user or group? I've noticed that after logout some users are still showing as active on the network.

: Write a script or something. Here's a tip,
ps au | tr -s ' ' | cut -d' ' -f1,2 | grep $username | cut -d' ' -f2
gets you the pids of all $username's processes. [[User:Dysprosia|Dysprosia]] 01:32, Aug 28, 2004 (EDT)

Could somebody write out some typical scripts for inclusion in the article? [[User:Crazyeddie|Crazyeddie]] 19:15, Aug 28, 2004 (EDT)

: It would have been Better if the author above (who should have signed his/her posts, I'm not going to bother checking the history) learnt how to write a script and wouldn't have to ask, but I can see how it would be a useful example to have in the article ;)
: I haven't tested this, though, since it'll be too much effort to minimize the disruption on my own system. [[User:Dysprosia|Dysprosia]] 03:50, Aug 29, 2004 (EDT)

I'm getting insane load on my dual xeon 35+ users and the average load is over 30. I'm looking at the ps to try and hunt down the culprits. Could someone point to a tracking tool for isolating load hogs? thanks! --[[User:DennisDaniels|DennisDaniels]] 15:42, Mar 2, 2005 (EST)

{{forums}} [[User:Crazyeddie|Crazyeddie]] 15:39, Mar 4, 2005 (EST)

User talk:D00msweek

2005-03-01T19:25:36Z

Crazyeddie: nmap copyvio

Hello, just letting you know that I removed some of the edits you made to the [[nmap]] article. It looks like some of it came directly from http://www.insecure.org/nmap/ . Since, AFAIK, we don't have permission from the owners of the site to release this material under the Creative Commons by-sa license, this was in violation of their copyright. Let me know if I've got it wrong, and I'll restore the edits.

Please keep contributing! [[User:Crazyeddie|Crazyeddie]] 14:25, Mar 1, 2005 (EST)

Nmap

2005-03-01T19:22:20Z

Crazyeddie: restoring some of D00msweek's edits

'''Nmap''' ("'''N'''etwork '''Map'''per") is a well-known utility for network exploration or security auditing. It is distributed under the [[GPL]]. It can rapidly scan a large [[network]] using raw [[IP]] [[packets]] "in novel ways" to give feedback about which hosts are active, which [[OS]] they are running, which [[port]]s/[[services]] are open and awaiting connections, etc., etc., ad infinitum.

==Tips==
(Some options require root-privelages.)

* Here's a pretty thorough scan recipe:
<tt><CODE><pre>nmap -T Aggressive -P0 -sT -p 1-65535 <insert host IP here></pre></CODE></tt>

* There is also <tt>nmapfe</tt>, which is a GUI frontend for nmap

==See also==
*[[Linux security vulnerabilities]]

==External links==
*[http://www.insecure.org/nmap/ Nmap home page]
*[http://www.insecure.org/nmap/nmap_doc.html Nmap docs]

''This article is a [[LQWiki:stub_articles|stub]] and needs to be finished. [[LQWiki:plunging_forward|Plunge forward]] and [[LQWiki:How_to_edit_a_page|help it grow]] !''

Nmap

2005-03-01T19:20:18Z

Crazyeddie: rolling back to Jor's edit - copyvio

'''Nmap''' ("'''N'''etwork '''Map'''per") is a well-known utility for network exploration or security auditing. It is distributed under the [[GPL]]. It can rapidly scan a large [[network]] using raw [[IP]] [[packets]] "in novel ways" to give feedback about which hosts are active, which [[OS]] they are running, which [[port]]s/[[services]] are open and awaiting connections, etc., etc., ad infinitum.

==Tips==

* Here's a pretty thorough scan recipe:
<tt><CODE><pre>nmap -T Aggressive -P0 -sT -p 1-65535 <insert host IP here></pre></CODE></tt>

* There is also <tt>nmapfe</tt>, which is a GUI frontend for nmap

==See also==
*[[Linux security vulnerabilities]]

==External links==
*[http://www.insecure.org/nmap/ Nmap home page]

''This article is a [[LQWiki:stub_articles|stub]] and needs to be finished. [[LQWiki:plunging_forward|Plunge forward]] and [[LQWiki:How_to_edit_a_page|help it grow]] !''

Assembly

2005-02-22T07:37:41Z

Crazyeddie: abstraction history

'''Assembly language''' is any low-level [[programming language]] which translates more or less directly to [[machine language]].

Computers only understand machine language (that's ones and zeros).

Humans have a very hard time understanding machine language, so some brave soul, somewhere, long ago, once took the time to write a program in actual machine language: a program that converts simple commands (more easily readable and typable by humans) into machine language. This program was called an assembler because it assembed machine language from something else. That something else is called assembly language, or just "assembly" for short.

Assembly made programming easier, but, at the time, was critized by "oldtimers" such as [[John von Neumann]]. This was because computers were so expensive and slow that the time grad students (who did the grunt work of coding in those days) saved programming was less expensive than the computer time needed to run the assembler. Also, assembly can't be optimized as closely as machine language - as recorded in the [[Story of Mel]]. However, that much optimization also made the code very hard to maintain. As computers became cheaper and more powerful, assembly became more popular.

Programming languages such as [[C]] are even more high level than assembly- it's even easier for humans to understand than assembly. For a program written in C to run on a computer, it first has to get compiled into assembly, and then the assembly gets assembled into machine language (which the computer can then recognize and run as an [[executable]]).

Finally, yes, there are programming languages even more high level than C, and even easier for humans to write and understand (though, some might be harder, depending on who you ask. :) ).

=== External Links ===
* [http://www.linuxassembly.org/ LinuxAssembly.org] for many resources to program in Assembly on Linux

Talk:Java

2005-02-22T07:30:41Z

Crazyeddie:

Where should we put mention of apt repositories for java?

If you're talking about apt repositories that contain the java virtual machine or java development programs, I'd put it as a subsection in the Getting Java section. If you're talking about apt repositories for programs that need java, I'd put it in a seperat section underneath Getting Java. [[User:Crazyeddie|Crazyeddie]] 03:34, Aug 23, 2004 (EDT)

Should Java be included in compiled language?

This is a bit of a gray area. Java is never compiled to machine code so technically speaking it is not a compiled language. It is compiled into byte code which is interpreted into machine code on the fly. This makes it sort of a hybrid language. As a result, I think some special mention needs to be made, but I don't want to make any changes without support of the original author.

[[User:Jtshaw|Jtshaw]] 22:16, Feb 21, 2005 (EST)

I'd put it in, along with a short description of the subtlites involved. [[User:Crazyeddie|Crazyeddie]] 02:30, Feb 22, 2005 (EST)

Crazyeddie: revert (spam)

This page lists the various programming languages by category.

Please note that the following categories do not necessarily always apply. There are a multitude of implementations, for example Perl can be interpreted or compiled to bytecode. Similarly for Scheme/Lisp (which also can be often compiled into different languages like C or Java).

==Interpreted languages==
* [[awk]]
* [[Bash]]
* [[Perl]]
* [[PHP]]
* [[Python]]
* [[Ruby]]
* [[Scheme]]
* [[Lisp]]
* [[tk]]

==Compiled languages==
* [[Basic]]
* [[C]]
* [[C plus plus|C++]]
* [[D programming language|D]]
* [[Fortran]]
* [[Java]]
* [[Pascal]]

* [[Unsafe Languages]]

==Common [[API]]s and [[Framework]]s==
* [[QT]], [[QT API]]
* [[GTK]], [[GTK API]]
* [[GNOME]], [[GNOME API]]
* [[KDE]], [[KDE API]]
* [[xlib]], [[xlib API]] Xwindows
* [[OpenGL]], [[OpenGL API]]
* [[EFL]], The Enlightenment Foundation Libraries[http://enlightenment.org/pages/efl.html]
* [[Ncurses]]
* [[GNUstep]]
* [[Tk]]
* [[libpng]]
* [[Java API]], [[JRE]], [[Java SDK]]

* [[C_plus_plus|C++]] [[GUI toolkit]]s
** [[wxWidgets]]
** [[fltk]]
** [[toad]]
** [[gtkmm]]

==See also==
*[[Programming Tips & Tricks]] - for user contributed programming tips/examples.
*[[Programming language]]
*[[Programs]]
*[[Programming-related_Commands]]
*[[Library-related_Commands_and_Files]]

People

2005-01-24T08:13:20Z

Crazyeddie: revert (spam)

[[Linux]] was originally created by Linus Torvalds with the assistance of developers around the world. This page is dedicated to those people. Here's a list of the most important contributors to the GNU/Linux community.

=Important People=
*[[Brian Behlendorf]] - President of the Apache Software Foundation and creator of the [[Apache|Apache Web Server]].
*[[Matthias Ettrich]] - Creator of the K Desktop Environment [[KDE]].
*[[Miguel de Icaza]] - founder of [[Ximian]], the [[GNOME]] project and the [[Mono]] project. He has also been a kernel and [[Wine]] contributor.
*[[ESR|Eric S. Raymond]] - One of the primary advocates of the [[Open Source]] movement.
*[[RMS|Richard M. Stallman]] - Founder of the [[Free Software]] movement.
*[[Linus Torvalds]] - Founder of the [[Linux]] kernel.
*[[Andrew Tridgell]] - Lead developer for [[Samba]].
*[[Larry Wall]] -- Creator of [[Perl]], [[rn]], and [[patch]]; and an all-around nice guy to boot.

=More People Stuff=
*[[Human Brain]] -- these people all have wonderful brains!
*[[LUG listings]] -- find other people in your area!

Gaming

2005-01-24T08:13:07Z

Crazyeddie: revert (spam)

The following is a list of articles related to playing games under Linux.

==Games for Linux==

===[[First person shooters]]===
* [[America's Army]]
* [[Doom]]
* [[Doom 3]]
* [[Heavy Metal: F.A.K.K.2]]
* [[Parsec]]
* [[Postal Plus]]
* [[Postal 2]]
* [[Quake]]
* [[Quake 2]]
* [[Quake 3 Arena]]
* [[Return to Castle Wolfenstein]]
* [[Rune]]
* [[Savage]]
* [[Soldier of Fortune]]
* [http://icculus.org/~ravage/tacops/ Tactical Ops: Assault on Terror Retail for Linux]
* [[Tribes 2]]
* [[Unreal Tournament]]
* [[Wolfenstein: Enemy Territory]]

===[[Emulators]]===
====Arcade====
* [[Daphne]]
* [[MAME]]
* [[Raine]]
* [[ZiNc]]
====Atari====
* [[Atari800]]
* [[Handy]] - Atari Lynx
* [[Hatari]] - Atari ST
* [[Stella]] - Atari 2600
* [[Virtual Jaguar]] - Atari Jaguar
====Nintendo Consoles====
=====Nes/Famicon=====
* [[DarcNES]]
* [[FakeNES]]
* [[FCE Ultra]]
* [[Hugo]]
* [[InfoNES]]
* [[TuxNES]]
* [[NEStra]]
=====Snes/Super Famicon=====
* [[SNES9X]]
* [[ZSNES]]
=====Nintendo 64=====
* [[Fake64]]
* [[Mupen64]]
=====Game Boy and Game Boy advance=====
* [[Gnuboy]]
* [[Gngb]]
* [[KiGB]]
* [[VGBA]]
* [[VisualBoy Advance]]
====Personal Computers====
* [[DOSEMU]]
* [[Dosbox|DOSBox]]
* [[OpenMSX|openMSX]] - 8-bit MSX Computer System
* [[UAE]] - Commodore Amiga
* [[VICE]] - several 8-bit computers
* [[Wine]] and [[WineX]] - Microsoft Windows
====Sega Consoles====
* [[Gens]] - Genesis/Mega Drive
* [[Generator]] - Genesis/Mega Drive
* [[Mekanix]] - several consoles
====SNK Neo Geo and Neo Geo pocket====
* [[Gngeo]]
* [[NeoPocott]]
====Sony Playstation and Playstation 2====
* [[ePSXe]]
* [[PCSX]]
* [[PCSX2]]
====Other====
* [[ScummVM]] - Classic LucasArts engine for point-and-click adventures

===Role playing games===
* [[Crossfire]]
* [[Daimonin]]
* [[FreedroidRPG]]
* [[Neverwinter Nights]]
* [[Roguelikes]]

===Racing===
* [[GLTron]]
* [[Armagetron]]
* [[Tux Racer]]
* [[Tux Kart]]
* [[Racer]]

===Arcade===
* [[Chromium]]
* [[Crack Attack]]
* [[Galaxium]]
* [[Maelstrom]]
* [[XPuyopuyo]]
* [[JumpnBump]]
* [[LiquidWar]]
* [http://xscorch.org/ XScorch]

===Simulation===
* [[BZFlag]]
* [[FreeCiv]]
* [[Lincity]]
* [[Simcity 3000]]
* [[YS Flight Simulation]]

===Strategy===
* [[Alpha Centauri]]
* [[Wesnoth]]

===Tetris-like=== 
* [[Frozen bubble]]
* [[Hextris]]
* [[Xtetris]]

===Text-based===
* [[Adventure]]
* [[BSD games]]
* [[Nethack]]
* [[Overkill]]

===Other===
* [[Dope Wars]]
* [[Freedroid]]
* [[Nighthawk]]
* [[PySol]]
* [[Simutrans]]

==See also==
* [[Persistent online worlds]]
* [[Gaming via Wine or WineX]]
* [[Half-Life Server]]
* [[XQF]] game server browser
* [[online gamer]]
* [[gaming community]]
* [[gaming clan]]
* [[mmorpg]]
* [[RPG]]
* [[FPS]]
* [[frag]]
* [[camper]], [[camp]], [[camping]], [[spawn camper]]
* [[leet]] or [[l33t]]
* [[gaming tournament]], [[tournament]], [[tourney]]
* [[3D graphics acceleration]]
* [[Loki Installers for Linux Gamers]]

==External links==
*[http://en.wikipedia.org/wiki/List_of_Linux_games List of Linux Games]
*[http://www.linuxsoft.cz/en/sw_list.php?id_kategory=23 Linux Game software]
*[http://www.happypenguin.org The Linux Game Tome] - Information on EVERY Linux game
*[http://www.riters.com/gameinfo/index.cgi/FrontPage Gameinfo Wiki] - Multiplatform Game Strategies
*[http://www.linuxgames.com/ LinuxGames.com]
*[http://icculus.org/ Icculus.org] - Lots of Linux game and development information
*[http://www.gcclinux.com/downloads/ GCCLinux.com] List of games with screenshots