Difference between revisions of "TODO"
From AMule Project FAQ
Line 4: | Line 4: | ||
== Most urgent stuff == | == Most urgent stuff == | ||
− | #Permission failing (see | + | #Requirements on platforms |
+ | #Permission failing (see [[TODO#Notes]]) | ||
#Safe servers list | #Safe servers list | ||
#Go on for Kademlia specific articles | #Go on for Kademlia specific articles | ||
Line 19: | Line 20: | ||
== Always TODOs == | == Always TODOs == | ||
*Translate [[Main Page|this wiki]]'s articles | *Translate [[Main Page|this wiki]]'s articles | ||
+ | |||
+ | == Notes == | ||
[21:10] <Redarg> in the preferences the security tab is filled with : Files 664, Directory 775. In the temp directory and in the finished Directory the files get a 644 | [21:10] <Redarg> in the preferences the security tab is filled with : Files 664, Directory 775. In the temp directory and in the finished Directory the files get a 644 |
Revision as of 20:44, 1 December 2005
Before we start
Check this wiki's FAQ if you haven't already taken a look at it.
Most urgent stuff
- Requirements on platforms
- Permission failing (see TODO#Notes)
- Safe servers list
- Go on for Kademlia specific articles
- Document missing files and Kademlia files (and explain defaults in config file)
- Write good "aMule usage" documents
- (Re)work on the utilities FAQs and articles
- Network packets and protocol design (and EC)
Someday stuff
- Only first word's appearance is linked (damn team decitions...)
- Split large articles into samller articles straight to topic
- Rework the Main Page and the whole wiki structure
Always TODOs
- Translate this wiki's articles
Notes
[21:10] <Redarg> in the preferences the security tab is filled with : Files 664, Directory 775. In the temp directory and in the finished Directory the files get a 644 [21:17] <Redarg> 664 and 775 sounds good [21:18] <ken> Redarg, what does "umask" show? [21:19] <Redarg> 0022 [21:22] <ken> Well, that means "don't let files be read by group or others". It's causing the difference between the permissions you set in aMule preferences and those you're actually seeing. [21:23] <ken> You need to arrange for the command "umake 0002" to be run before aMule is run. Do that either in your shell startup commands, or in a script you use to launch amule. [21:24] <ken> s/umake/umask