Obsolete Lustre Wiki - User contributions [en]

Submitting Patches

2009-12-15T13:39:06Z

Abond:

'''''NOTICE:''''' The transition from CVS to Git will take place on Monday, December 14. For more information about the transition, see the [[Git Transition Notice]]. For details about how to migrate to Git, see [[Migrating to Git]]. Until the transition takes place, you can access information about using CVS at [[Accessing CVS]].

----

When you are ready to have your patch reviewed, follow the process described below for submitting it using Bugzilla.

'''''Note:''''' It is sometimes desirable to solicit reviews of a patch on the [mailto:lustre-devel@lists.lustre.org lustre-devel] mailing list to expose the patch to a wider audience. However, this will ''NOT'' put the patch on track to being accepted into the Lustre repository.

=== Submitting Patches for Review ===

To have your changes accepted into a mainline Lustre branch, your code must be reviewed and approved by senior Lustre engineers. Following these steps will speed up review of your changes and increase the likelihood of success:

1. Read, complete, and return the form found at [http://wiki.lustre.org/images/c/cd/Sun_Contributor_Agreement_1_5.pdf Contributor Agreement]. We cannot accept your contributions without this form. See [[Contribution_Policy|Contribution Policy]] for more information.

2. Testing the patch is required before it can be submitted. The patch must include any new tests specific to the bug/feature. See [[Testing Lustre Code]] for specific details. If you have completed testing of the patch, set the "acc-sm_passed_''release''" flag to "+" for the branch(es) that passed testing in step 4 below.

3. Generate a patch with ''diff -upN'', ''git diff'', or ''git format-patch''. Please do not send other kinds of patches unless your reviewer requests them.

The command for generating a patch is:<pre>
[lustre]$ git diff {basebranch} > {patchname}.diff
</pre>
where ''{basebranch}'' is the branch you are patching against (''b1_6'', ''b1_8'', or ''master''). Note this patch will include committed and uncommitted changes on your branch. If you have nicely squashed your commit history, feel free to use ''git format-patch''. If you are unfamiliar with this process, use ''git diff''.

If sending changes with ''git format-patch'' we ask that you follow the standard commit message format when making your commits, so that the patch can more easily be identified in the future. If you are doing a rebase, you will get a chance to modify/combine your commit messages. Commit messages for final patches should look like this:
<pre>
b=<bugno> <Single line summary of change>

<In depth description>

i=<inspector1>
i=<inspector2>
</pre>

If you are not using git format-patch, then simply adding the above lines at the start of the submission email is enough.

4. Find or file a bug corresponding to your contribution in [http://bugzilla.lustre.org/ Bugzilla]. For more information about Bugzilla, see the [[Developers_Guide_to_Bugzilla_for_Lustre|Developers Guide to Bugzilla]], the [https://bugzilla.lustre.org/page.cgi?id=bug-writing.html Bugzilla - Bug Writing Guidelines], or the [https://bugzilla.lustre.org/docs/html/using.html Bugzilla User Guide].

* Provide the patch as an Attachment (click on "Add an Attachment")
* Select the "patch" box.
** If submitting a new bug with a patch attached, follow normal bug submission procedures. The support team will assign the bug and inspections as appropriate.
** If working with an Lustre internal engineer, under "Flags" set the ''inspection'' flag to "?" and copy the email address of the engineer into the adjacent ''Requestee:'' field.
** If you have not been collaborating with someone on the Lustre team and don't know who should review your work, assign the inspection to ''lustre-rmg-team@sun.com''
* Click on "commit" to submit the attachment and inspection request.

5. One or more reviewers will submit comments regarding your patch. Iterate the patch until you receive inspection approval or the bug is closed.

6. Once you have approval, mail the patch to [mailto:lustre-gate-20@sun.com lustre-gate-20], [mailto:lustre-gate-20@sun.com lustre-gate-16], or [mailto:lustre-gate-16@sun.com lustre-gate-18] (for Lustre 2.0, 1.6, or 1.8 respectively). Include the bug number and reviewer in the commit message, along with a concise description of the change.

regular user (unprotected page) --[[User:Ab|Ab]] 13:33, 15 December 2009 (UTC)

editor user (protected page) --[[User:Abond|Abond]] 13:38, 15 December 2009 (UTC)

Submitting Patches

2009-12-15T13:38:09Z

Abond:

'''''NOTICE:''''' The transition from CVS to Git will take place on Monday, December 14. For more information about the transition, see the [[Git Transition Notice]]. For details about how to migrate to Git, see [[Migrating to Git]]. Until the transition takes place, you can access information about using CVS at [[Accessing CVS]].

----

When you are ready to have your patch reviewed, follow the process described below for submitting it using Bugzilla.

'''''Note:''''' It is sometimes desirable to solicit reviews of a patch on the [mailto:lustre-devel@lists.lustre.org lustre-devel] mailing list to expose the patch to a wider audience. However, this will ''NOT'' put the patch on track to being accepted into the Lustre repository.

=== Submitting Patches for Review ===

To have your changes accepted into a mainline Lustre branch, your code must be reviewed and approved by senior Lustre engineers. Following these steps will speed up review of your changes and increase the likelihood of success:

1. Read, complete, and return the form found at [http://wiki.lustre.org/images/c/cd/Sun_Contributor_Agreement_1_5.pdf Contributor Agreement]. We cannot accept your contributions without this form. See [[Contribution_Policy|Contribution Policy]] for more information.

2. Testing the patch is required before it can be submitted. The patch must include any new tests specific to the bug/feature. See [[Testing Lustre Code]] for specific details. If you have completed testing of the patch, set the "acc-sm_passed_''release''" flag to "+" for the branch(es) that passed testing in step 4 below.

3. Generate a patch with ''diff -upN'', ''git diff'', or ''git format-patch''. Please do not send other kinds of patches unless your reviewer requests them.

The command for generating a patch is:<pre>
[lustre]$ git diff {basebranch} > {patchname}.diff
</pre>
where ''{basebranch}'' is the branch you are patching against (''b1_6'', ''b1_8'', or ''master''). Note this patch will include committed and uncommitted changes on your branch. If you have nicely squashed your commit history, feel free to use ''git format-patch''. If you are unfamiliar with this process, use ''git diff''.

If sending changes with ''git format-patch'' we ask that you follow the standard commit message format when making your commits, so that the patch can more easily be identified in the future. If you are doing a rebase, you will get a chance to modify/combine your commit messages. Commit messages for final patches should look like this:
<pre>
b=<bugno> <Single line summary of change>

<In depth description>

i=<inspector1>
i=<inspector2>
</pre>

If you are not using git format-patch, then simply adding the above lines at the start of the submission email is enough.

4. Find or file a bug corresponding to your contribution in [http://bugzilla.lustre.org/ Bugzilla]. For more information about Bugzilla, see the [[Developers_Guide_to_Bugzilla_for_Lustre|Developers Guide to Bugzilla]], the [https://bugzilla.lustre.org/page.cgi?id=bug-writing.html Bugzilla - Bug Writing Guidelines], or the [https://bugzilla.lustre.org/docs/html/using.html Bugzilla User Guide].

* Provide the patch as an Attachment (click on "Add an Attachment")
* Select the "patch" box.
** If submitting a new bug with a patch attached, follow normal bug submission procedures. The support team will assign the bug and inspections as appropriate.
** If working with an Lustre internal engineer, under "Flags" set the ''inspection'' flag to "?" and copy the email address of the engineer into the adjacent ''Requestee:'' field.
** If you have not been collaborating with someone on the Lustre team and don't know who should review your work, assign the inspection to ''lustre-rmg-team@sun.com''
* Click on "commit" to submit the attachment and inspection request.

5. One or more reviewers will submit comments regarding your patch. Iterate the patch until you receive inspection approval or the bug is closed.

6. Once you have approval, mail the patch to [mailto:lustre-gate-20@sun.com lustre-gate-20], [mailto:lustre-gate-20@sun.com lustre-gate-16], or [mailto:lustre-gate-16@sun.com lustre-gate-18] (for Lustre 2.0, 1.6, or 1.8 respectively). Include the bug number and reviewer in the commit message, along with a concise description of the change.

regular user (unprotected page) --[[User:Ab|Ab]] 13:33, 15 December 2009 (UTC)
test --[[User:Abond|Abond]] 13:38, 15 December 2009 (UTC)

GetInvolved:Get Involved

2009-07-01T18:45:05Z

Abond:

Find out about what the Lustre Community is doing, and get involved.

<div class="categoryLeft">

<big><strong>Community</strong></big>

Lustre user community events and resources.

* Sign up for one or more [[Mailing_Lists|Lustre Mailing Lists]]
* [[Lustre_User_Group|Lustre User Group 2009]] Lustre community's premier event to learn and share knowledge about Lustre technology.
** [[Lug_08|Lustre User Group 2008]] Agenda, presentations and panel discussions from the 2008 program (slide decks and videos available).
** [[Lug_07|Lustre User Group 2007]] Agenda and presentations from the 2007 program (slide decks available).
** [[Lug_06|Lustre User Group 2006]] Agenda and presentations from the 2006 program (slide decks available).
* Developers, find out how to [[Contribution_Policy|contribute code or test]].
* Read case studies and other [[Lustre_Publications|Lustre publications]], including Lustre engineering presentations.

</div>
<div class="categoryRight">

<big><strong>Community Development Projects</strong></big>
Interesting projects from the Lustre user community that are available for public use.

* [http://wiki.lustre.org/images/d/d9/Lustre-amanda.pdf Backup and Recovery: Amanda and Lustre] Use an Amanda client to back up a Lustre filesystem from Lustre clients.(PDF)
* [http://sourceforge.net/projects/lmt LLNL - Lustre Monitoring Tool] Tracks activity of server nodes (MDS, OSS and portals routers) for one or more Lustre filesystems.
* [http://www.bullopensource.org/lustre/ Bull - Open Source Tools for Lustre] Manage one or more Lustre filesystems from an administrative node.
* [http://shine-wiki.async.eu/wiki/Home CEA Administration Tool for Lustre 1.6] Set up and manage a Lustre filesystem on a cluster.

</div>
<div class="categoryRight">

<big><strong>Lustre Centres of Excellence</strong></big>

Find out about active Lustre Centres of Excellence (LCEs).

* [http://ornl-lce.clusterfs.com/index.php?title=Main_Page Lustre Centre of Excellence at Oak Ridge National Laboratory]
<p>
Other Lustre Centers of Excellence are located at: Naval Research Laboratory.
<br>
<br>
Additionally, there are several Lustre Development Centers that work with Sun to make significant code and testing contributions to Lustre and the Lustre Community. These centers are located at CEA, Juelich, LLNL, and Sandia.

GetInvolved:Get Involved

2009-07-01T18:44:49Z

Abond:

Find out about what the Lustre Community is doing, and get involved..

<div class="categoryLeft">

<big><strong>Community</strong></big>

Lustre user community events and resources.

* Sign up for one or more [[Mailing_Lists|Lustre Mailing Lists]]
* [[Lustre_User_Group|Lustre User Group 2009]] Lustre community's premier event to learn and share knowledge about Lustre technology.
** [[Lug_08|Lustre User Group 2008]] Agenda, presentations and panel discussions from the 2008 program (slide decks and videos available).
** [[Lug_07|Lustre User Group 2007]] Agenda and presentations from the 2007 program (slide decks available).
** [[Lug_06|Lustre User Group 2006]] Agenda and presentations from the 2006 program (slide decks available).
* Developers, find out how to [[Contribution_Policy|contribute code or test]].
* Read case studies and other [[Lustre_Publications|Lustre publications]], including Lustre engineering presentations.

</div>
<div class="categoryRight">

<big><strong>Community Development Projects</strong></big>
Interesting projects from the Lustre user community that are available for public use.

* [http://wiki.lustre.org/images/d/d9/Lustre-amanda.pdf Backup and Recovery: Amanda and Lustre] Use an Amanda client to back up a Lustre filesystem from Lustre clients.(PDF)
* [http://sourceforge.net/projects/lmt LLNL - Lustre Monitoring Tool] Tracks activity of server nodes (MDS, OSS and portals routers) for one or more Lustre filesystems.
* [http://www.bullopensource.org/lustre/ Bull - Open Source Tools for Lustre] Manage one or more Lustre filesystems from an administrative node.
* [http://shine-wiki.async.eu/wiki/Home CEA Administration Tool for Lustre 1.6] Set up and manage a Lustre filesystem on a cluster.

</div>
<div class="categoryRight">

<big><strong>Lustre Centres of Excellence</strong></big>

Find out about active Lustre Centres of Excellence (LCEs).

* [http://ornl-lce.clusterfs.com/index.php?title=Main_Page Lustre Centre of Excellence at Oak Ridge National Laboratory]
<p>
Other Lustre Centers of Excellence are located at: Naval Research Laboratory.
<br>
<br>
Additionally, there are several Lustre Development Centers that work with Sun to make significant code and testing contributions to Lustre and the Lustre Community. These centers are located at CEA, Juelich, LLNL, and Sandia.

File:LustreFS.flv

2008-09-15T11:24:55Z

Abond: test file

test file

File:TsingHua-3.gif

2007-08-02T13:41:11Z

Abond: test

test

User:Abond/cfslustre.js

2007-05-07T11:11:54Z

Abond:

User:Abond

2007-05-06T21:24:48Z

Abond:

== How to set up wikEd ==

'''Original version'''

http://en.wikipedia.org/wiki/User:Cacycle/wikEd#Installation

'''wiki.lustre.org version'''

1. Log in under your username

2. Click the following link to edit your ''User:YourUsername/cfslustre.js'' page: [http://wiki.lustre.org/index.php?title=Special:Mypage/cfslustre.js&action=edit Special:Mypage/cfslustre.js],
otherwise open the respective page by hand

3. Add the following code to that edit page:

<pre>
// install [[User:Cacycle/wikEd]] in-browser text editor

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"></script>');
</pre>

If there is already code on your ''User:YourUsername/cfslustre.js'' page, please make sure not to paste the installation code between /*...*/ tags.

5. Save the page

6. Refresh your browser's cache: hold down Shift while clicking Reload (or press Ctrl-Shift-R)

7. The wikEd logo should now be displayed on top of every page next to the log out link

User:Abond

2007-05-06T21:23:22Z

Abond:

== How to set up wikEd ==

'''Original version'''

http://en.wikipedia.org/wiki/User:Cacycle/wikEd#Installation

'''wiki.lustre.org version'''

1. Log in under your username

2. Click the following link to edit your ''User:YourUsername/cfslustre.js'' page: [http://wiki.lustre.org/index.php?title=Special:Mypage/cfslustre.js&action=edit Special:Mypage/cfslustre.js],
otherwise open the respective page by hand

3. Add the following code to that edit page:

<pre>
// install [[User:Cacycle/wikEd]] in-browser text editor

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"></script>');
</pre>

If there is already code on your User:YourUsername/cfslustre.js page, please make sure not to paste the installation code between /*...*/ tags.

5. Save the page

6. Refresh your browser's cache: hold down Shift while clicking Reload (or press Ctrl-Shift-R)

7. The wikEd logo should now be displayed on top of every page next to the log out link

User:Abond

2007-05-06T21:22:16Z

Abond:

== How to set up wikEd ==

'''Original version'''

http://en.wikipedia.org/wiki/User:Cacycle/wikEd#Installation

'''wiki.lustre.org version'''

1. Log in under your username

2. Click the following link to edit your ''User:YourUsername/cfslustre.js'' page: [http://wiki.lustre.org/index.php?title=Special:Mypage/cfslustre.js&action=edit Special:Mypage/cfslustre.js],
otherwise open the respective page by hand

3. Add the following code to that edit page:

<pre>
// install [[User:Cacycle/wikEd]] in-browser text editor

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"></script>');
</pre>

If there is already code on your User:YourUsername/monobook.js page, please make sure not to paste the installation code between /*...*/ tags.

5. Save the page

6. Refresh your browser's cache: hold down Shift while clicking Reload (or press Ctrl-Shift-R)

7. The wikEd logo should now be displayed on top of every page next to the log out link

User:Abond/cfslustre.js

2007-05-06T19:39:24Z

Abond:

// install [[User:Cacycle/wikEd]] in-browser text editor
document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"> </script>');

var wikEdSkipBrowserTest = true;
var wikEdShowSourceButton = true;

User:Abond

2007-05-06T19:26:09Z

Abond:

== How to set up wikEd ==

'''Original'''

http://en.wikipedia.org/wiki/User:Cacycle/wikEd#Installation

'''wiki.lustre.org version'''

1. Log in under your username

2. Click the following link to edit your ''User:YourUsername/cfslustre.js'' page: [http://wiki.lustre.org/index.php?title=Special:Mypage/cfslustre.js&action=edit Special:Mypage/cfslustre.js],
otherwise open the respective page by hand

3. Add the following code to that edit page:

<pre>
// install [[User:Cacycle/wikEd]] in-browser text editor

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"></script>');
</pre>

If there is already code on your User:YourUsername/monobook.js page, please make sure not to paste the installation code between /*...*/ tags.

5. Save the page

6. Refresh your browser's cache: hold down Shift while clicking Reload (or press Ctrl-Shift-R)

7. The wikEd logo should now be displayed on top of every page next to the log out link

User:Abond/cfslustre.js

2007-05-06T18:52:23Z

Abond:

User:Abond/cfslustre.js

2007-05-06T18:40:02Z

Abond:

// install [[User:Cacycle/wikEd]] in-browser text editor
document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript">
+ var wikEdSkipBrowserTest = true; var wikEdShowSourceButton = true; </script>');

User:Abond/cfslustre.js

2007-05-06T18:30:45Z

Abond:

// install [[User:Cacycle/wikEd]] in-browser text editor
document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"> </script>');
<script type="text/javascript">
var wikEdSkipBrowserTest = true;
var wikEdShowSourceButton = true;
</script>

User:Abond/cfslustre.js

2007-05-06T18:19:58Z

Abond:

// install [[User:Cacycle/wikEd]] in-browser text editor
document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"> </script>');
<script>
var wikEdSkipBrowserTest = true;
var wikEdShowSourceButton = true;
</script>

User:Abond/cfslustre.js

2007-05-06T18:10:46Z

Abond:

// install [[User:Cacycle/wikEd]] in-browser text editor
document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript">
+ var wikEdSkipBrowserTest = true;
+ var wikEdShowSourceButton = true; </script>');

User:Abond

2007-05-06T17:52:07Z

Abond:

== How to set up wikEd ==

(http://en.wikipedia.org/wiki/User:Cacycle/wikEd#Installation) :

'''wiki.lustre.org version'''

1. Log in under your username

2. Click the following link to edit your ''User:YourUsername/cfslustre.js'' page: [http://wiki.lustre.org/index.php?title=Special:Mypage/cfslustre.js&action=edit Special:Mypage/cfslustre.js],
otherwise open the respective page by hand

3. Add the following code to that edit page:

<pre>
// install [[User:Cacycle/wikEd]] in-browser text editor

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"></script>');
</pre>

If there is already code on your User:YourUsername/monobook.js page, please make sure not to paste the installation code between /*...*/ tags.

5. Save the page

6. Refresh your browser's cache: hold down Shift while clicking Reload (or press Ctrl-Shift-R)

7. The wikEd logo should now be displayed on top of every page next to the log out link

User:Abond

2007-05-06T17:42:17Z

Abond:

== How to set up wikEd ==

(http://en.wikipedia.org/wiki/User:Cacycle/wikEd#Installation) :

'''wiki.lustre.org version'''

1. Log in under your username

2. Click the following link to edit your ''User:YourUsername/cfslustre.js'': [http://wiki.lustre.org/index.php?title=Special:Mypage/cfslustre.js&action=edit Special:Mypage/cfslustre.js] page,
otherwise open the respective page by hand

3. Add the following code to that edit page:

<pre>
// install [[User:Cacycle/wikEd]] in-browser text editor

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"></script>');
</pre>

If there is already code on your User:YourUsername/monobook.js page, please make sure not to paste the installation code between /*...*/ tags.

5. Save the page

6. Refresh your browser's cache: hold down Shift while clicking Reload (or press Ctrl-Shift-R)

7. The wikEd logo should now be displayed on top of every page next to the log out link

User:Abond

2007-05-06T17:41:38Z

Abond:

== How to set up wikEd ==

(http://en.wikipedia.org/wiki/User:Cacycle/wikEd#Installation) :

'''wiki.lustre.org version'''

1. Log in under your username

2. Click the following link to edit your [http://wiki.lustre.org/index.php?title=Special:Mypage/cfslustre.js&action=edit|Special:Mypage/cfslustre.js] page,
otherwise open the respective page by hand

3. Add the following code to that edit page:

<pre>
// install [[User:Cacycle/wikEd]] in-browser text editor

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"></script>');
</pre>

If there is already code on your User:YourUsername/monobook.js page, please make sure not to paste the installation code between /*...*/ tags.

5. Save the page

6. Refresh your browser's cache: hold down Shift while clicking Reload (or press Ctrl-Shift-R)

7. The wikEd logo should now be displayed on top of every page next to the log out link

User:Abond

2007-05-06T17:39:44Z

Abond:

== How to set up wikEd ==

(http://en.wikipedia.org/wiki/User:Cacycle/wikEd#Installation) :

'''wiki.lustre.org version'''

1. Log in under your username

2. Click the following link to edit your [''User:YourUsername/cfslustre.js'' http://wiki.lustre.org/index.php?title=Special:Mypage/cfslustre.js&action=edit|Special:Mypage/cfslustre.js] page. , otherwise open the respective page by hand

3. Add the following code to that edit page:

<pre>
// install [[User:Cacycle/wikEd]] in-browser text editor

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"></script>');
</pre>

If there is already code on your User:YourUsername/monobook.js page, please make sure not to paste the installation code between /*...*/ tags.

5. Save the page

6. Refresh your browser's cache: hold down Shift while clicking Reload (or press Ctrl-Shift-R)

7. The wikEd logo should now be displayed on top of every page next to the log out link

User:Abond

2007-05-06T17:38:26Z

Abond: /* wiki.lustre.org version */

== How to set up wikEd ==

(http://en.wikipedia.org/wiki/User:Cacycle/wikEd#Installation) :

'''wiki.lustre.org version'''

1. Log in under your username

2. Click the following link to edit your [''User:YourUsername/cfslustre.js'' http://wiki.lustre.org/index.php?title=Special:Mypage/cfslustre.js&action=edit|Special:Mypage/cfslustre.js] page. , otherwise open the respective page by hand

3. Add the following code to that edit page:

<pre>
// install [[User:Cacycle/wikEd]] in-browser text editor

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"></script>');
</pre>

If there is already code on your User:YourUsername/monobook.js page, please make sure not to paste the installation code between /*...*/ tags.

5. Save the page

6. Refresh your browser's cache: hold down Shift while clicking Reload (or press Ctrl-Shift-R)

7. The wikEd logo should now be displayed on top of every page next to the log out link

User:Abond

2007-05-06T14:35:19Z

Abond:

== How to set up wikEd ==

(http://en.wikipedia.org/wiki/User:Cacycle/wikEd#Installation) :

=== wiki.lustre.org version ===

1. Log in under your username

2. Click the following link to edit your [''User:YourUsername/cfslustre.js'' http://wiki.lustre.org/index.php?title=Special:Mypage/cfslustre.js&action=edit|Special:Mypage/cfslustre.js] page. , otherwise open the respective page by hand

3. Add the following code to that edit page:

// install [[User:Cacycle/wikEd]] in-browser text editor

document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript"></script>');

If there is already code on your User:YourUsername/monobook.js page, please make sure not to paste the installation code between /*...*/ tags.

5. Save the page

6. Refresh your browser's cache: hold down Shift while clicking Reload (or press Ctrl-Shift-R)

7. The wikEd logo should now be displayed on top of every page next to the log out link

User:Abond/cfslustre.js

2007-05-04T18:10:18Z

Abond:

User:Abond/cfs lustre.js

2007-05-04T17:08:34Z

Abond: