create a dmoz folder under the bin folder
create a urls text file to contain the urls:
http://www.britishhorrorfilms.co.uk/rillington.shtml
http://www.shoestring.org/mmi_revs/10-rillington-place.html
http://www.tvguide.com/movies/database/ShowMovie.asp?MI=22983
http://us.imdb.com/title/tt0066730/
http://www.geocities.com/aaronbcaldwell/1984.html
http://orwell.ru/a_life/movies/m84_01.htm
http://www.britmovie.co.uk/genres/fiction/filmography/014.html
http://adrianmco.batcave.net/1984.htm
http://us.imdb.com/title/tt0114746/
http://www.geocities.com/darkdaze18/
http://apolloguide.com/mov_revtemp.asp?Title=13th+Warrior,+The
http://www.boxofficemojo.com/13thwarrior.html
http://movie-reviews.colossus.net/movies/t/13th_warrior.html
http://ter.air0day.com/13thwarrior.shtml
http://www.metacritic.com/video/titles/13thwarrior
http://us.imdb.com/title/tt0120657/
http://www.all-reviews.com/videos/thirteenth-warrior.htm
http://www.haro-online.com/movies/13th_warrior.html
http://www.rottentomatoes.com/movie-1091574/
http://upcomingmovies.com/13thwarrior.html
http://www.brunching.com/selfmade/selfmade-thirteenthwarrior.html
http://www.filmtracks.com/titles/13th_warrior.html
http://www.100girls.net/
http://imdb.com/title/tt0214388/
http://us.imdb.com/title/tt0146394/
http://us.imdb.com/title/tt0085121/

tingan@tingan-laptop:~/download/spider/nutch/bin$ cd dmoz/
tingan@tingan-laptop:~/download/spider/nutch/bin/dmoz$ ls
urls
tingan@tingan-laptop:~/download/spider/nutch/bin/dmoz$ gedit urls
tingan@tingan-laptop:~/download/spider/nutch/bin/dmoz$ cd ..
tingan@tingan-laptop:~/download/spider/nutch/bin$ ./nutch inject crawl-20091123183328/crawldb/ dmoz/
Injector: starting
Injector: crawlDb: crawl-20091123183328/crawldb
Injector: urlDir: dmoz
Injector: Converting injected urls to crawl db entries.
Injector: Merging injected urls into crawl db.
Injector: done

1. download and install tomcat 5.5 or tomcat 6.0, you can install both.
2. set JAVA_HOME, CLASSPATH environment variable
sudo gedit .bashrc  or sudo gedit .profile
export JAVA_HOME=/usr/lib/jvm/java-6-sun
#export CATALINA_HOME=/usr/share/tomcat5.5
export CATALINA_HOME=/home/tingan/download/Java/apache-tomcat-6.0.20
export JAVA_BIN=$JAVA_HOME/bin
export PATH=$PATH:$JAVA_HOME/bin:$CATALINA_HOME/bin
export CLASSPATH=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar:/home/tingan/download/spider/nutch/lib:$CATALINA_HOME/common/lib/jsp-api.jar:$CATALINA_HOME/common/lib/servlet-api.jar
 
in the process of run nutch command line, it shows the error that the java class .
Exception in thread “main” java.lang.NoClassDefFoundError: org/apache/nutch/crawl/Crawl
I copy the nutch-1.0.jar to the $JAVA_HOME/lib/nutch.jar and add a line to the CLASSPATH variable.

3. test nutch command line
/home/tingan/download/spider/nutch/bin

关于nutch-0.9在使用过程中的错误

悬赏：5 发布时间：2008-08-07 提问人：zhaojuan8 (初级程序员)

crawl started in: mydir rootUrlDir = url threads = 4 depth = 2 Injector: starting Injector: crawlDb: mydir/crawldb Injector: urlDir: url Injector: Converting injected urls to crawl db entries. Injector: Merging injected urls into crawl db. Injector: done Generator: Selecting best-scoring urls due for fetch. Generator: starting Generator: segment: mydir/segments/20080713015110 Generator: filtering: false Generator: topN: 2147483647 Generator: jobtracker is 'local', generating exactly one partition. Generator: Partitioning selected urls by host, for politeness. Generator: done. Fetcher: starting Fetcher: segment: mydir/segments/20080713015110 Fetcher: threads: 4 fetching http://wwww.sina.com.cn/ fetch of http://wwww.sina.com.cn/ failed with: org.apache.<span class="hilite1">nutch</span>.protocol.http.api.HttpException: <span class="hilite2">java</span>.net.UnknownHostException: wwww.sina.com.cn Fetcher: done CrawlDb update: starting CrawlDb update: db: mydir/crawldb CrawlDb update: segments: [mydir/segments/20080713015110] CrawlDb update: additions allowed: true CrawlDb update: URL normalizing: true CrawlDb update: URL filtering: true CrawlDb update: Merging segment data into db. CrawlDb update: done Generator: Selecting best-scoring urls due for fetch. Generator: starting Generator: segment: mydir/segments/20080713015119 Generator: filtering: false Generator: topN: 2147483647 Generator: jobtracker is 'local', generating exactly one partition. Generator: Partitioning selected urls by host, for politeness. Generator: done. Fetcher: starting Fetcher: segment: mydir/segments/20080713015119 Fetcher: threads: 4 fetching http://wwww.sina.com.cn/ fetch of http://wwww.sina.com.cn/ failed with: org.apache.<span class="hilite1">nutch</span>.protocol.http.api.HttpException: <span class="hilite2">java</span>.net.UnknownHostException: wwww.sina.com.cn Fetcher: done CrawlDb update: starting CrawlDb update: db: mydir/crawldb CrawlDb update: segments: [mydir/segments/20080713015119] CrawlDb update: additions allowed: true CrawlDb update: URL normalizing: true CrawlDb update: URL filtering: true CrawlDb update: Merging segment data into db. CrawlDb update: done LinkDb: starting LinkDb: linkdb: mydir/linkdb LinkDb: URL normalize: true LinkDb: URL filter: true LinkDb: adding segment: mydir/segments/20080713015110 LinkDb: adding segment: mydir/segments/20080713015119 LinkDb: done Indexer: starting Indexer: linkdb: mydir/linkdb Indexer: adding segment: mydir/segments/20080713015110 Indexer: adding segment: mydir/segments/20080713015119 Optimizing index. Indexer: done Dedup: starting Dedup: adding indexes in: mydir/indexes <span class="hilite4">Exception</span> in thread "main" <span class="hilite2">java</span>.<span class="hilite3">io</span>.IOException: <span class="hilite5">Job</span> failed! 	at org.apache.hadoop.mapred.JobClient.runJob(JobClient.<span class="hilite2">java</span>:604) 	at org.apache.<span class="hilite1">nutch</span>.indexer.DeleteDuplicates.dedup(DeleteDuplicates.<span class="hilite2">java</span>:439) 	at org.apache.<span class="hilite1">nutch</span>.crawl.Crawl.main(Crawl.<span class="hilite2">java</span>:135) 

# accept hosts in MY.DOMAIN.NAME +^http://([a-z0-9]*\.)*sina.com.cn/

1、首先安装JDK

　　Java6 在命令行输入 apt-get install sun-Java6-jre sun-Java6-jdk 可以自行选择是否安装jre

　　Java5 在命令行输入 apt-get install sun-Java5-jre sun-Java5-jdk

　　多个jdk可以同时安装，而且可以随时更改当前的默认jdk

　　在命令行输入 sudo update-alternatives –config Javac 来更改当前默认jdk

　　sun-Java5-doc和sun-Java6-doc是jdk的文档的安装程序，但是不包括jdk文档。

　　在安装jdk文档前，必须到sun的网站下载jdk文档。你下载的文档可以是任意语言，包括中文例如你 安装jdk5的文档，应该在安装前把下载的文档存放到/tmp/jdk-1_5_0-doc.zip；再例如你安装jdk6的文档，应该在安装前将下载的 文档存放到 /tmp/jdk-6-doc.zip。当然你也可以不在安装前做这件事情，因为安装的过程会提示你这么做，请注意看终端窗口的提示。

　　写入环境变量 gedit /etc/environment

　　在编辑器中加入 Java_HOME=/usr/lib/jvm/Java-6-sun

　　classpath不必配置，错误的classpath会导致许多问题。jvm会知道自带的classpath。对于自定义的classpath，可以在运行、编译时加上-classpath参数来指定。至于环境变量，当你写的程序需要时再指定也不迟

　　要使配置生效必须在命令行输入 . /etc/environment

　　如果需要还要修改系统虚拟机的优先级顺序调整： sudo gedit /etc/jvm

　　jdk安装完毕，在终端输入 Java －version 查看是否安装成功（或直接输入Java）

　　2、安装　　

　　从tomcat官方网站下载绿色的即可，解压后运行bin目录下的startup.sh

　　在浏览器输入http://localhost:8080 查看tomcat是否启动

　　要关闭tomcat只要运行bin目录下shutdown.sh即可

　　如果需要tomcat开机启动可以参照一下方法：

　　修改/etc/rc.local 文件 gedit /etc/rc.local 加入

　　Java_HOME=/usr/lib/jvm/Java-6-sun

　　CLASSPATH=.:/usr/lib/jvm/Java-6-sun/lib

　　JRE_HOME=/usr/lib/jvm/Java-6-sun/jre

　　export JRE_HOME

　　export CLASSPATH

　　export Java_HOME

　　/home/allenwei/Tomcat/apache-tomcat-6.0.14/bin/startup.sh //你放tomcat的目录

　　修改/etc/profile 输入 gedit /etc/profile，增加以下行：

　　Java_HOME=/usr/lib/jvm/Java-6-sun

　　CATALINA_HOME=/home/test/Tomcat/apache-tomcat-6.0.14

　　export Java_HOME CATALINA_HOME

　　重启系统后tomcat就可以随开机启动了

　　3、安装mysql

　　首先 sudo apt-get install mysql-server mysql-client

　　安装完成后输入 sudo /etc/init.d/mysql start 启动mysql

　　此时需要修改root的密码

　　查看默认密码输入 sudo gedit /etc/mysql/debian.cnf 在［client］段可以看到用户名密码

　　输入 mysql -uroot -p 登录，提示输入密码，输入在debian.cnf文件中的密码

　　修改密码 输入 GRANT ALL PRIVILEGES ON *.* TO root@localhostIDENTIFIED BY “你要修改的密码”

　　此时mysql 的安装完成

　　您也可以安装mysql 的图形化管理工具 sudo apt-get mysql-admin mysql-query-browser

　　4、eclipse 和 netbeans 的安装就很简单了，从官方网站上下载 deb包，安装即可。　

parse_url

Array
(
    [scheme] => http
    [host] => hostname
    [user] => username
    [pass] => password
    [path] => /path
    [query] => arg=value
    [fragment] => anchor
)
<big><big><b>Http_build_query</b></big></big>

ftp://ftp.example.com/pub/files/current/?a=b&a=c<br />

ubuntu中

sudo apt-get install doxygen  doxygen-gui
启动GUI程序
doxywizard

Doxygen formatting conventions

Doxygen is a documentation generation system. The documentation is extracted directly from the sources, which makes it much easier to keep the documentation consistent with the source code.

There is an excellent Doxygen manual at the Doxygen site. The following notes pertain to the Drupal implementation of Doxygen.

General documentation syntax

To document a block of code, the syntax we use is:

/**
 * Documentation here.
 */

Doxygen will parse any comments located in such a block. Our style is to use as few Doxygen-specific commands as possible, so as to keep the source legible. Any mentions of functions or file names within the documentation will automatically link to the referenced code, so typically no markup need be introduced to produce links.

Text formatting (and API parser conformance)

Doxygen directives

/**<br /> * Summary here; one sentence on one line (even if it exceeds 80 chars).<br /> *<br /> * A more detailed description goes here.<br /> *<br /> * A blank line forms a paragraph. There should be no trailing white-space<br /> * anywhere.<br /> *<br /> * @param $first<br /> *   "@param" is a Doxygen directive to describe a function parameter. Like some<br /> *   other directives, it takes a term/summary on the same line, and a<br /> *   description (this text) indented by 2 spaces on the next line. All<br /> *   descriptive text should wrap at 80 chars.<br /> *   Newlines are NOT supported within directives; if a newline would be before<br /> *   this text, it would be appended to the general description above.<br /> * @param $second<br /> *   There should be no newline between multiple directives of the same type.<br /> *<br /> * @return<br /> *   "@return" is a different Doxygen directive to describe the return value of<br /> *   a function, if there is any.<br /> */<br />

Lists

 * @param $variables<br /> *   An associative array containing:<br /> *   - tags: An array of labels for the controls in the pager:<br /> *     - first: A string to use for the first pager element.<br /> *     - last: A string to use for the last pager element.<br /> *   - element: An optional integer to distinguish between multiple pagers on<br /> *     one page.<br /> *   Any further description - still belonging to the same param.<br /> * This no longer belongs to the param. There should be a newline before this<br /> * paragraph, but it was left out for clarity.<br />

Lists can appear everywhere in Doxygen, but the documentation parser requires to follow a strict syntax to make them appear correctly in the parsed HTML output:

• The list bullet/hyphen is aligned with (uses the same indentation level as) the paragraph before it, no newline before or after the list.
• No newlines between list items.
• Each list item starts with the key, followed by a colon, followed by a space, followed by the key description. The key description starts capitalized.
• If a list item exceeds 80 chars, it needs to wrap, and the following lines need to be aligned with the key (intended by 2 more spaces).
• If there should appear text after the list that still belongs to the block before the list, then it uses the same alignment/indentation as the initial text.
• Again: within a Doxygen directive, blank lines are NOT supported.
• Lists can appear within lists, and the same rules apply recursively.

Links

/**<br /> * @see foo_bar()<br /> * @see ajax.inc<br /> * @see MyModuleClass<br /> * @see <a href="http://drupal.org/node/1354" title="http://drupal.org/node/1354" rel="nofollow">http://drupal.org/node/1354</a><br /> */<br />

The @see directive may be used to link to (existing) functions, files, or URLs. @see directives should always be placed on an own line.

/**<br /> * See also @link group_name Link text @endlink<br /> */<br />

The @link directive may be used to output a HTML link, but also to link to Doxygen groups that are defined elsewhere via @defgroup.

Documenting files

It is good practice to provide a comment describing what a file does at the start of it. For example:

<?php<br />// $Id: theme.inc,v 1.202 2004/07/08 16:08:21 dries Exp $<br /><br />/**<br /> * @file<br /> * The theme system, which controls the output of Drupal.<br /> *<br /> * The theme system allows for nearly all output of the Drupal system to be<br /> * customized by user themes.<br /> */<br />

The line immediately following the @file directive is a summary that will be shown in the list of all files in the generated documentation. If the line begins with a verb, that verb should be in present tense, e.g., “Handles file uploads.” Further description may follow after a blank PHPDoc line.

In general, @file directives should not contain large descriptions, because those are better placed into @defgroup directives, so developers can look up high-level documentation by reading the “group” topic. See http://api.drupal.org/api/groups for a list of API topics/groups.

To add CVS ID-Tags to your file, add a // $Id$ to your file. CVS will automatically expand it to the format shown above. In the future, you don’t have to care about that as CVS will update these information automatically.

For .install files, the following template is used:

/**<br /> * @file<br /> * Install, update and uninstall functions for the XXX module.<br /> */<br />

Documenting functions

All functions that may be called by other files should be documented; private functions optionally may be documented as well. A function documentation block should immediately precede the declaration of the function itself, like so:

/**<br /> * Verifies the syntax of the given e-mail address.<br /> *<br /> * Empty e-mail addresses are allowed. See RFC 2822 for details.<br /> *<br /> * @param $mail<br /> *   A string containing an email address.<br /> *<br /> * @return<br /> *   TRUE if the address is in a valid format.<br /> */<br />function valid_email_address($mail) {<br />

The first line of the block should contain a brief description of what the function does, limited to 80 characters, and beginning with a verb in the form “Does such and such” (third person, as in “This function does such and such”, rather than second person imperative “Do such and such”). A longer description with usage notes should follow after a blank line, if more explanation is needed. Each parameter should be listed with a @param directive, with a description indented on the following line. After all the parameters, a @return directive should be used to document the return value if there is one. There is a blank line between the @param and @return directives.

Functions that are easily described in one line may omit these directives, as follows:

/**<br /> * Converts an associative array to an anonymous object.<br /> */<br />function array2object($array) {<br />

The parameters and return value must be described within this one-line description in this case.

Documenting hook implementations

Many modules consist largely of hook implementations. If the implementation is rather standard and does not require more explanation than the hook reference provides, a shorthand documentation form may be used:

/**<br /> * Implements hook_help().<br /> */<br />function blog_help($section) {<br />  // ...<br />}<br />

This generates a link to the hook reference, reminds the developer that this is a hook implementation, and avoids having to document parameters and return values that are the same for every implementation of the hook.

Documenting forms

/**<br /> * Form builder for the user login form.<br /> *<br /> * @param $msg<br /> *   The message to display.<br /> *<br /> * @see user_login_form_validate()<br /> * @see user_login_form_submit()<br /> * @ingroup forms<br /> */<br />function user_login_form(&$form_state, $msg = '')<br />

In order to provide a quick reference for themers, we tag all form builder functions so that Doxygen can group them together. The form builder function is defined as any function meant to be used as an argument for drupal_get_form(). To do this, add a grouping instruction to the documentation of the function. Additionally, while submit, validate and other handlers for the form are not meant to be in this group, you should provide a @see to provide an easy reference to handlers that are attached to the form.

/**<br /> * Form validation handler for user_login_form().<br /> *<br /> * @see user_login_form()<br /> * @see user_login_form_submit()<br /> */<br />function user_login_form_validate($form, &$form_state) {<br />  ...<br />}<br /><br />/**<br /> * Form submission handler for user_login_form().<br /> *<br /> * @see user_login_form()<br /> * @see user_login_form_validate()<br /> */<br />function user_login_form_submit($form, &$form_state) {<br />  ...<br />}<br />

Documenting themeable functions

In order to provide a quick reference for theme developers, we tag all themeable functions so that Doxygen can group them on one page. To do this, add a grouping instruction to the documentation of all such functions:

/**<br /> * Formats a query pager.<br /> *<br /> * ...<br /> *<br /> * @ingroup themeable<br /> */<br />function theme_pager($tags = array(), $limit = 10, $element = 0, $attributes = array()) {<br />  ...<br />}<br />

Documenting theme templates

If a template and a preprocess function is used instead of a theming function, an empty function definition of the theme function that is not used should be placed in the contributed documentation (contributions/docs/developer/theme.php).

The template itself should be documented with a @file directive and contain a list of the variables that the template_preprocess_HOOK has prepared for it. If any of these variables contain data that is unsafe to output for XSS reasons, they should be documented; otherwise it can be assumed that variables available have already been appropriately filtered. Anything not listed should not be assumed to be safe to output. It should also contain a @see directive to link back to the preprocessor and the theme_X function.

<?php<br />// $Id$<br /><br />/**<br /> * @file<br /> * Default theme implementation to display a list of forums.<br /> *<br /> * Available variables:<br /> * - $forums: An array of forums to display.<br /> *<br /> * Each $forum in $forums contains:<br /> * - $forum->is_container: Is TRUE if the forum can contain other forums. Is<br /> *   FALSE if the forum can contain only topics.<br /> * - $forum->depth: How deep the forum is in the current hierarchy.<br /> * - $forum->name: The name of the forum.<br /> * - $forum->link: The URL to link to this forum.<br /> * - $forum->description: The description of this forum.<br /> * - $forum->new_topics: True if the forum contains unread posts.<br /> * - $forum->new_url: A URL to the forum's unread posts.<br /> * - $forum->new_text: Text for the above URL which tells how many new posts.<br /> * - $forum->old_topics: A count of posts that have already been read.<br /> * - $forum->num_posts: The total number of posts in the forum.<br /> * - $forum->last_reply: Text representing the last time a forum was posted<br /> *   or commented in.<br /> *<br /> * @see template_preprocess_forum_list()<br /> */<br />

The template_preprocess_HOOK function should also contain appropriate @see directives.

Documenting contributed modules and themes

• Don’t use @mainpage. There can be only one @mainpage in the contributions repository, which is reserved for an index page of all contributes modules and themes.
• Use Doxygen Modules (@defgroup, @ingroup, @addtogroup, see “Limitations and hints” below) sparingly. There are currently over 2,200 module directories in contrib, many of them consisting of more than one module. If each of these modules used just one @defgroup, there would be more than 2,200 entries in the global Module list. If each used more than one …
• If you do use Doxygen Modules, make sure you give them a unique namespace, which would be your module’s name. E.g. @defgroup views ... for the views.module, @defgroup views_ui ... for the views_ui.module. Don’t use group names which are defined in Drupal core (hooks, themeable, file, batch, database, forms, form_api, format, image, validation, search, etc.).

A recommended way of using Doxygen grouping in contributed modules and themes is the following:

/**<br /> * @defgroup example Example module functionality<br /> * @{<br /> * Longer description of your module's API.<br /> */<br /><br />/**<br /> * Load an example.<br /> * ...<br /> */<br />function example_load() ...<br /><br />/**<br /> * Save an example.<br /> * ...<br /> */<br />function example_save() ...<br /><br />/**<br /> * @} End of "defgroup example".<br /> */<br />

This defines the primary Doxygen group. The syntax is @defgroup [internal_name] [Summary]. The internal name has to be prefixed with the module name (unless it is located in Drupal core’s include files).

Other functions in other files (or even entirely different modules) can then declare @ingroup example to put themselves into the same group.

Limitations and hints

Drupal’s Doxygen processing module, api.module, currently only supports a small subset of all Doxygen commands and makes some assumptions about the formatting of the source. Code to be processed by api.module is advised to stick to these conventions.

Api.module currently supports only one of Doxygen’s three grouping mechanisms: Modules (@defgroup, @ingroup, @addtogroup, @{, @}). When using those, please note the following:

• Modules work at a global level, creating a new page for each group. They should be used only to group functions that provide some kind of API, which possibly spans multiple files. Or the other way round: they should not be used to group functions in a file when these functions are only used in that very file. Thats what Member Groups are for (which unfortunately aren’t supported by api.module yet).
• @defgroups can be defined only once – trying to define a second @defgroup name with a name already used will result in an error. Use @defgroup name in the “most important” section/file of that group and add to it from other places with @addtogroup / @ingroup.
• The name in @defgroup name Explaination of that group must be single-word identifier, like a PHP variable or function name. Or, as regular expression: [a-zA-Z_][a-zA-Z0-9_]*. Dots, hyphens, etc. are not allowed.

To see how a real Doxygen processes and displays the current Drupal code documentation (both core and contrib), have a look at ax’ Drupal site. Especially, look at the “doxygen error logs” and help improving Drupals code documentation.

Doxygen常用指令介绍

Doxygen注释风格

1 类的申明
/**
*   class declaration
*/

2 变量申明
/**< val’s brief. val’s details1. */

3 函数申明
  /**
  * a normal member taking two arguments and returning an integer value.
  * @param a an integer argument.
  * @param s a constant character pointer.
  * @see Test()
  * @see ~Test()
  * @see testMeToo()
  * @see publicVar()
  * @return The test results
  */

psfig

Example:

\noindent
\psfig{file=fig1.eps,width=\textwidth}
\noindent{{\bfseries Fig.~1} \ Example of the interesting object for which
we aim to obtain near-IR $J$ and $H$ surface photometry.}

Note that in this example, we did not use a \begin{figure} … \end{figure} environment. If you happen to have an EPS file in which the figure was in landscape orientation, then you can add an angle option as follows: <br />

psfig{file=fig1.eps,width=textwidth,angle=-90}

epsfig

Example:

\null<br />\newcommand{\txw}{\textwidth}<br />\begin{figure}[t!]<br />\mbox{<br />   \epsfig{file=fig1a.eps,width=0.325\txw,clip=}<br />   \epsfig{file=fig1b.eps,width=0.325\txw,clip=}<br />   \epsfig{file=fig1c.eps,width=0.325\txw,clip=}<br />}\par<br />\mbox{<br />   \epsfig{file=fig1d.eps,width=0.325\txw,clip=}<br />   \epsfig{file=fig1e.eps,width=0.325\txw,clip=}<br />   \makebox[0.325\txw]{\rule{0pt}{0.325\txw}}   <br />}<br />\caption{{\sc Figure~1} Five out of six ain't bad.}<br />\end{figure}<br />\vfill\clearpage<br />

Example of a full page, multi-panel figure. Five panels contain a figure, while the sixth was filled with a phantom space of the same width and height as the other panels. All sizes are expressed as a fraction of the current textwidth. Should that at some point change, then the figures will automatically scale with that change. There is an empty clip= option in the \epsfig commands. Should an EPS figure have been produced with copious amounts of white space around the area of interest or should you happen to have a PS instead of EPS file (i.e, without a %BoundingBox statement), then a new BoundingBox may be specified, e.g.:clip="[92 345 538 742]"

8.6.2 plotone, plottwo, and plotfiddle

Example:

begin{figure} <br />    \epsscale{0.85}<br />    \plotone{sample.eps}<br />    \caption{Sample figure showing important results.}<br />\end{figure}<br />

\begin{figure}<br />\plottwo{fig2a.eps}{fig2b.eps}<br />\caption{{\sc Fig.~2} (\emph{a}) field surrounding target \#1; (\emph{b})<br />   detail of the inner 70~kpc.\label{targetfov}}<br />\end{figure}<br />

If you need to rotate or make other transformations to a figure, you may use the \plotfiddle command:

\plotfiddle{PSFILE}{VSIZE}{ROTANG}{HSCALE}{VSCALE}{HTRANS}{VTRANS}<br />\plotfiddle{sample.eps}{2.6in}{-90.}{32.}{32.}{-250}{225}<br />

includegraphics

Example:

\begin{figure} \resizebox{\textwidth}{!} {\includegraphics[bb=10 20 100 300,clip,angle=-90,width=\textwidth]{empty.eps} \caption{Mostly empty field, demonstrating the need for a larger-aperture telescope and high-throughput camera.} \label{FigEmpty} \end{figure}

• Java

Please do not make any edits to this article. Its contents are currently under review and being merged with the Ubuntu Server Guide. To find the Ubuntu Server Guide related to your specific version, please go to:

• https://help.ubuntu.com/ and click on Ubuntu Server Guide

Sun Microsystems developed Java, which is many things depending on who you ask. It is a language, and an execution environment and probably many more things. On this page Java refers to the software that executes programs compiled to Java byte codes (akin to machine language).

Running Java under Ubuntu

In order to run Java programs and Java applets, you must have a Java environment installed. The GCJ flavor of Java is installed as default, and is usually fine for most purposes. If it is not installed, JavaInstallation describes how to install some opensource flavors of Java. You may, however, have a need to run the Sun flavor of Java if something does not work correctly.

To get Sun Java under Ubuntu 7.04 or later running on Intel or PowerPC platform, you should enable the Universe repository in Add/Remove programs, and install either the openjdk-6-jre package or the sun-java6-bin package. (Note: PowerPC version is slow).

To get Sun Java under Ubuntu 6.06 or 6.10 running on Intel x86 platform, you should enable the Universe repository in Add/Remove programs, and install the sun-java5-bin package.

Note: The same commands will work under Xubuntu/Kubuntu (using Add/Remove or the Adept Package Installer).

Choosing the default Java to use

Just installing new Java flavours does not change the default Java pointed to by /usr/bin/java. You must explicitly set this:

• Open a Terminal window

• Run sudo update-java-alternatives -l to see the current configuration and possibilities.

• Run sudo update-java-alternatives -s XXXX to set the XXX java version as default. For Sun Java 6 this would be sudo update-java-alternatives -s java-6-sun

• Run java -version to ensure that the correct version is being called.

You can also use the following command to interactively make the change;

• Open a Terminal window

• Run sudo update-alternatives --config java

• Follow the onscreen prompt

ubuntu
agi doxygen doxygen-gui
doxywizard to show up the GUI application.

Info File Details

name (Required)

The displayed name of your module. It should follow the Drupal 6 capitalization standard: only the first letter of the first word is capitalized (“Example module”, not “example module” or “Example Module”).
name = On this date

description (Required)

A short, preferably one line description that will tell the administrator what this module does on the module administration page. Remember, overly long descriptions can make this page difficult to work with, so please try to be concise. This field is limited to 255 characters.

description = A block module that lists links to content such as blog entries or forum discussions that were created one week ago.

Note that special characters in this description must be substituted with the HTML entity values. For example, use description = This is my "crazy@email.com" email address instead of description = This is my "crazy@email.com" email address
If the description has single quotes or apostrophes in it then you can simply put the entire string inside double quotes. For example, description = "Please don't use this unless you know what you are doing."

core (Required)

As of version 6.x, Drupal core will refuse to enable or run modules that aren’t explicitly written for the right version of core. The .info file must specify which Drupal core compatiblity any module or theme has been ported to. This is accomplished by means of the new core attribute in the .info files.

core = 6.x

Note: the drupal.org packaging script automatically sets this value based on the Drupal core compatibility setting on each release node, so users downloading packaged releases from drupal.org will always get the right thing. However, for sites that deploy Drupal directly from CVS, it helps if this value is added to the .info files for the module. This is also a good way to indicate to users of each module what version of core the HEAD of CVS is compatibile with at any given time.

dependencies (Optional)

There are a couple of extra options that may appear in the .info file, one of which are module dependencies. If a module requires another module to be enabled, list each module (filename) required in the following syntax:

dependencies[] = taxonomy
dependencies[] = comment

For the example module, these don’t apply and we will simply omit them. If dependencies are assigned for a module, Drupal will not allow it to be activated until the required dependencies are met.

package (Optional)

If a module has a package string, on the admin/build/modules page it will be listed with other modules with the same category. If a package string is not assigned, it will simply be listed in the ‘Other’. Not assigning a package for your module is perfectly ok; in general packages are best used for modules that are distributed together or are meant to be used together. If in doubt, leave this field blank.

package = "Your arbitrary grouping string"

Suggested examples of appropriate items for the package field:

• Audio
• Bot
• CCK
• Chat
• E-Commerce
• Event
• Feed Parser
• Organic groups
• Station
• Video
• Views
• Voting (if it uses/requires VotingAPI)

The files use the ini format and can include a ; $Id$ to have CVS insert the file ID information.

For more information on ini file formatting, see the PHP.net parse_ini_file documentation.