Difference: SuomenKielipankki:CorpusDirs (1 vs. 11)

Revision 112006-12-20 - AnssiYliJyra

Line: 1 to 1
 
META TOPICPARENT name="Trash.KitWikiSuomenKielipankki:Intro:TheCorpusServer"

How the Common Directories Are Organized?

Line: 8 to 8
 

General Design Principles

Changed:
<
<
There are five sorts of directory locations:
>
>
There are six sorts of directory locations:
 
  1. low-level: directories that start with /fs/ or /mnt/ should never be user for specifying resource locations
    • /fs/corpus3/ - a file system containing all local the language bank directories
    • /fs/corpus/ - a symbolic link to /fs/corpus3/
Changed:
<
<
    • /fs/linux/ - a file system containing all linux versions
>
>
    • /fs/linux/ - a file system containing various linux versions
 
    • /fs/gen/ - a file system containing files of a generic nature (such as manuals and data)
    • /fs/src/ - a file system containing source files
    • /fs/kielipankki/ - a file system containing the language bank data directories
Line: 22 to 22
 
    • /fs/corpus/slash-c/ - a directory containing directory /c/
    • /fs/corpus/slash-v/ - a directory containing directory /v/
  1. install directories: contains software that depends on a particular system version; should be used while installing the software
Changed:
<
<
    • /v/linux24_i386/ is a directory whose content is mainly compatible with Linux RedHat 4(Nahant Update 4 2.6.9-42.0.3.EL i686)
>
>
    • /v/linux24_i386/ is a directory whose content is mainly compatible with Linux RedHat 4(Nahant Update 4 2.6.9-42.0.3.EL i686), the current system of the corpus3.csc.fi machine.
 
    • /v/linux22_i386/ is a directory whose content is less compatible with the system
    • /v/gen/ is a directory whose content is compatible with almost any system at CSC
    • /usr/local/contrib/appl/ling/username/software/version/ is a directory that contains one particular version of the software
Deleted:
<
<
    • /wrk/ a directory that contains user's local work area
 
  1. views: directories such as /p/ and /usr/local/bin, should contain symbolic links to installed software
    • /p/ contains links to /v/ and abstracts away from its the system version; contains a standard view to /v/; hides the architecture and system version and presents a structure that can be used to access system-dependent versions through system-independent alias locations.
    • /l/ contains links to v/ and abstracts away from its the system version; contains a server-specific view of /v/
  2. shortcuts and aliases: These create alternative or shortened paths as
    • /corp/ is a compatibility shorthand for accessing /usr/local/uhling/corp/
    • /usr/local/contrib is a conventionalized alternative for our /c/
Added:
>
>
  1. temporary working areas:
    • $TMPDIR i.e. /tmp/
    • /var/
    • /usr/tmp/
    • $WRKDIR i.e. /wrk/username a directory that contains user's local, machine specific working area. The files may be recycled automatically if the files are older than 7 days.
    • $METAWRK i.e. /fs/metawrk/username/= - stores files for 30 files
    • $HOME - available till the termation of the user's customer agreement with CSC
    • $ARCHIVE - available till the termation of the user's customer agreement with CSC.
 

Where the software is to be installed?

Line: 53 to 60
 

A conceivable exception

Changed:
<
<
  • In some special cases, the software installs itself to some standard location, such as /usr/local/textlive/, and changes to this installation location may be risky. While the correct installation location would be in /v/ tree, it may be possible to configure the software for /usr/local/textlive/ (or leave it as the default). The only misadvantage of this arrangement is that the software cannot be run in a machine if it does not implement a link from /p/ to the physical of the software in location in /v/.
>
>
  • In some special cases, the software installs itself to some standard location, such as /usr/local/textlive/, and changes to this installation location may be risky. While the correct installation location would be in /v/ tree, it may be possible to configure the software for /usr/local/textlive/ (or leave it as the default). The only misadvantage of this arrangement is that the software cannot be run in a machine if it does not implement a link from a view directory such as /usr/local/textlive/ to the physical of the software in location in /v/.
  • There may be wrongly installed software. We do not need to reinstall them to the /v/ tree, but we might want to do so in the ideal world. We can also move software from view directories to the /v/ tree and add a link to the original location in a view directory, but this would require a README or more to tell that the software has been configured wrongly for a view directory.
 

Some corpus.csc.fi -specific slash-directories as low-level directories

directory real location

Revision 102006-12-19 - AnssiYliJyra

Line: 1 to 1
 
META TOPICPARENT name="Trash.KitWikiSuomenKielipankki:Intro:TheCorpusServer"
Changed:
<
<

How the Common Directories Are Organized?

>
>

How the Common Directories Are Organized?

First a warning: Often the current state falls short of this ideal, because many principles have matured after the first installations. This page describes the requirements the future installations.

 

General Design Principles

Deleted:
<
<
  • software often depends on a particular system version and, therefore, software will be installed to the /v/ directory tree
  • /p/ contains links to /v/ and abstracts away from its the system version; contains a standard view to /v/
  • /usr/local/ contains links to v/ and abstracts away from its the system version; contains a server-specific view of /v/

Parts of the Linux environment for linguists

Basically, there are the following installation directories in addition to the directories provided by the Linux system:

directory tree contents owner
/usr/bin/ user binaries that belong to the Redhat Enterprise Linux distribution root
/p/bin/ architecture-independent directories in the CSC computers ling
/v/SYSVERS/ system dependent directories in the CSC computers root, ling
/usr/local/bin/ the local binary directory ling
/f/bin/ the first binaries in the path root
 
Changed:
<
<

Some important subdirectiories of /usr/local/

>
>
There are five sorts of directory locations:
  1. low-level: directories that start with /fs/ or /mnt/ should never be user for specifying resource locations
    • /fs/corpus3/ - a file system containing all local the language bank directories
    • /fs/corpus/ - a symbolic link to /fs/corpus3/
    • /fs/linux/ - a file system containing all linux versions
    • /fs/gen/ - a file system containing files of a generic nature (such as manuals and data)
    • /fs/src/ - a file system containing source files
    • /fs/kielipankki/ - a file system containing the language bank data directories
    • /fs/metawrk/ - a file system that contains large work directories
  2. slash-directories: directories on a non-root partition that are used to extend the root directory with /v/, /p, and c
    • /fs/corpus/slash-p/ - a directory containing directory /p/
    • /fs/corpus/slash-c/ - a directory containing directory /c/
    • /fs/corpus/slash-v/ - a directory containing directory /v/
  3. install directories: contains software that depends on a particular system version; should be used while installing the software
    • /v/linux24_i386/ is a directory whose content is mainly compatible with Linux RedHat 4(Nahant Update 4 2.6.9-42.0.3.EL i686)
    • /v/linux22_i386/ is a directory whose content is less compatible with the system
    • /v/gen/ is a directory whose content is compatible with almost any system at CSC
    • /usr/local/contrib/appl/ling/username/software/version/ is a directory that contains one particular version of the software
    • /wrk/ a directory that contains user's local work area
  4. views: directories such as /p/ and /usr/local/bin, should contain symbolic links to installed software
    • /p/ contains links to /v/ and abstracts away from its the system version; contains a standard view to /v/; hides the architecture and system version and presents a structure that can be used to access system-dependent versions through system-independent alias locations.
    • /l/ contains links to v/ and abstracts away from its the system version; contains a server-specific view of /v/
  5. shortcuts and aliases: These create alternative or shortened paths as
    • /corp/ is a compatibility shorthand for accessing /usr/local/uhling/corp/
    • /usr/local/contrib is a conventionalized alternative for our /c/

Where the software is to be installed?

Often configuration scripts store the installation location to some internal variables of the software. For this reason, it is necessary to choose to have it set in a way that works with minimum amount of extra work in additional machines in CSC.

The existence of /v/ is primary while /p/ and /usr/local/appl/ are secondary

All machines can share same /v/ -locations if the necessary filesystems have been mounted to them, but not all locations in the /v/ tree need to be included to the /p/ view of it. And even if there is a link in the /p/ tree, it would be useless if its target does not exist. Thus /v/ is alway more important than /p/.

The directory names in /v/ are better fixed than the names in /fs/ or /mnt/

Software is always installed to an install directory that should exists in the first place in all CSC machines, rather than to directories that are dependent on the mount point (such as /fs/corpus3) or on the view (such as /p/bin/). There are two main locations of this type: /v/ and /c/ trees. The first is writable by the CSC staff only but the latter is available for all contributors. It is an error to install software to a low-level directory or to tell the users about a location of software using a low-level directory. The reason is that CSC reserves the right to change low-level directories overnight. For example, /fs/corpus3/ used to be /mnt/corpus2/. It may happen that such changes break the backwards-compatibility.

There are two install directories

  • The existence of /v/ is CSC-wide, while the views presented by the /p/ and /usr/local/ may not cover all the machines of CSC because all links pointing to the /v/ directory tree must be added manually to the directories under /p/ and /usr/local/. This is, thus, a simple reason, why all the software should be installed to the /v/ -tree, rather than to such unsatisfactory locations as /usr/local/, /l/, or /mnt/corpus/appl/ling/.

  • Experienced users have the right to write to directories of the form /usr/local/contrib/appl/field/username/ where field can be e.g. ling and username can be e.g. ylijyra. The user may install several versions of the same program. Under the username directory, the user should create a directory named by the software, and its subdirectory named by the version of the software. Under the assumption that two systems need different versions, the /c/ tree may contain installations for multiple architectures and linux-versions. The user is responsible for indicating which version runs in which machine. This can be done e.g. in a README-file put to /usr/local/contrib/appl/field/username/program/.

A conceivable exception

  • In some special cases, the software installs itself to some standard location, such as /usr/local/textlive/, and changes to this installation location may be risky. While the correct installation location would be in /v/ tree, it may be possible to configure the software for /usr/local/textlive/ (or leave it as the default). The only misadvantage of this arrangement is that the software cannot be run in a machine if it does not implement a link from /p/ to the physical of the software in location in /v/.

Some corpus.csc.fi -specific slash-directories as low-level directories

directory real location
/v/ /fs/corpus/slash-v/
/p/ /fs/corpus/slash-p/
/l/ /fs/corpus/slash-v/
/opt/ /fs/corpus/slash-opt/
/wrk/ /fs/corpus/slash-wrk/
/f/ /fs/corpus/slash-f/

Some important install directories of /v/

directory function
/v/linux24_i386/appl/ CSC-wide installations of application programs for linux24_i386 systems
/v/linux24_i386/appl/ling/ CSC-wide installations of linguistic software
/v/linux24_i386/appl/lang/sicstus/ CSC-wide installation of the SICStus Prolog
/v/gen/appl/texlive/ Location for storing TeXLive (we do not know whether we can use this a the install directory

Some important subdirectories of /usr/local/ and /l/

 
directory function
Added:
>
>
texlive/ A symbolic link to /v/gen/appl/texlive/
 
appl/ A symbolic link to /v/linux24_i386/appl/ that contains applications maintained by CSC.
Changed:
<
<
bin/ Server-specific executables for scientific computing.
contrib/ A base directory reserved for installations contributed by the users.
>
>
bin/ Server-specific executables for scientific computing. Contains symlinks to binaries in /usr/local/appl/
contrib/ A base directory reserved for installations contributed by the users. A symbolic link to /c/
 
kielipankki/ A base directory reserved for the linguistic resources maintained by CSC.
kotus/ A base directory reserved for the Research Institute for the Languages of Finland.
uhling/ A base directory reserved for the University of Helsinki Corpus Server (UHLCS) directories.
Changed:
<
<

Some important projections and shottcuts

/l/ /usr/local/
/c/ /usr/local/contrib/
/korpus/ includes symlinks to /usr/local/uhling/corp
/corp/ includes symlinks to /usr/local/uhling/corp
/proj/ includes symlinks to /usr/local/uhling/proj

Some "frequently asked" questions?

  • Where are /mnt/corpus/ and /fs/corpus/? The former is a symbolic link to the latter that links to /fs/corpus2/.
  • Where is /corp/? It is a symbolic link to /l/venus/corp/ and is provided for compatibility.
  • Where is /proj/? It is a directory containing symbolic links to subdirectories of /fs/corpus/slash-proj/. It is provided for compatibility.
  • What is the difference between /fs/kielipankki/ and /fs/corpus2/slash-l/kielipankki/ (or /l/kielipankki/ for short)? The content of the former is linked to the latter as a subset. The former is used by the scientists interface, while the latter is visible only to the corpus machine.
>
>

Some important compatibility shortcuts

/korpus/ includes symlinks to the subdirectories of /usr/local/kotus/korpus/ (for compatibility)
/corp/ includes symlinks to the subdirectories of /usr/local/uhling/corp/ (for compatibility)
/proj/ includes symlinks to the subdirectories of /usr/local/uhling/proj/ (for compatibility)
/mnt/ includes symlinks to the subdirectories of /fs/ (for compatibility; now all mounts are file server mounts to /fs/, while mounts used to be local and in /mnt/)
 
Deleted:
<
<

Multi-platform support

(Finnish draft text:) /c-hakemistoon kontribuoiville uutena lisätietona että mikäli asennus voidaan ja kannattaa tehdä myös 64-bittiselle linux-alustalle, kontribuoijien kannattaa tehdä se samalla kertaa, niin että voimme hyödyntää corpus4:sta 64-bittisenä sitten kun 64-bittinen linux-palvelin corpus4.csc.fi tulee saataville. 64-bittinen asennus tehdään omana versionaan hakemistoon /c/appl/ling/username/sovellus/versio-64/ jne. Tosin 64-bittisen version kääntäminen ei ole mahdollista corpus3:lla.
 

Questions and Answers

 
<--/commentPlugin-->

Revision 92006-12-19 - AnssiYliJyra

Line: 1 to 1
 
META TOPICPARENT name="Trash.KitWikiSuomenKielipankki:Intro:TheCorpusServer"

How the Common Directories Are Organized?

Added:
>
>

General Design Principles

  • software often depends on a particular system version and, therefore, software will be installed to the /v/ directory tree
  • /p/ contains links to /v/ and abstracts away from its the system version; contains a standard view to /v/
  • /usr/local/ contains links to v/ and abstracts away from its the system version; contains a server-specific view of /v/

Parts of the Linux environment for linguists

 Basically, there are the following installation directories in addition to the directories provided by the Linux system:
Changed:
<
<
/v/ used to create a multi-platform metacomputer environment at CSC root /v/
/f/bin the first binaries in the path root /fs/corpus/slash-f/
/usr/bin user binaries that belong to the Redhat Enterprise Linux distribution root /usr/bin/
/p/bin the CSC meta machine binaries ling /fs/corpus/slash-p/
/l/bin or /usr/local/bin the local binary directory ling /fs/corpus/slash-l/bin/
>
>
directory tree contents owner
/usr/bin/ user binaries that belong to the Redhat Enterprise Linux distribution root
/p/bin/ architecture-independent directories in the CSC computers ling
/v/SYSVERS/ system dependent directories in the CSC computers root, ling
/usr/local/bin/ the local binary directory ling
/f/bin/ the first binaries in the path root
 
Changed:
<
<

Some important subdirectiories of /l/ (i.e /usr/local/ )

>
>

Some important subdirectiories of /usr/local/

 
directory function
appl/ A symbolic link to /v/linux24_i386/appl/ that contains applications maintained by CSC.
Changed:
<
<
bin/ Corpus-specific executables maintained by CSC.
contrib/ Software installations contributed by the users.
kielipankki/ The linguistic resources maintained at CSC, the core of the Language Bank of Finland
kotus/ The linguistic resources maintained by the Research Institute for the Languages of Finland. This directory is not maintained by CSC.
venus/ The reserved root for the University of Helsinki Corpus Server (UHLCS) directories. This directory is not maintained by CSC.
>
>
bin/ Server-specific executables for scientific computing.
contrib/ A base directory reserved for installations contributed by the users.
kielipankki/ A base directory reserved for the linguistic resources maintained by CSC.
kotus/ A base directory reserved for the Research Institute for the Languages of Finland.
uhling/ A base directory reserved for the University of Helsinki Corpus Server (UHLCS) directories.
 

Some important projections and shottcuts

Deleted:
<
<
/corp/ includes symlinks to /usr/local/venus/corp
/proj/ includes symlinks to /usr/local/venus/proj
 
/l/ /usr/local/
/c/ /usr/local/contrib/
Changed:
<
<
/contrib/ Contributed applications approved by CSC.

General Design Principles

  • system-denpendent, but machine-independent software will be installed to the /v/ directory tree.
  • /p/ contains unform set of links to /v/
  • /usr/local/ contains links to v/
>
>
/korpus/ includes symlinks to /usr/local/uhling/corp
/corp/ includes symlinks to /usr/local/uhling/corp
/proj/ includes symlinks to /usr/local/uhling/proj
 

Some "frequently asked" questions?

  • Where are /mnt/corpus/ and /fs/corpus/? The former is a symbolic link to the latter that links to /fs/corpus2/.

Revision 82006-12-19 - AnssiYliJyra

Line: 1 to 1
 
META TOPICPARENT name="Trash.KitWikiSuomenKielipankki:Intro:TheCorpusServer"
Deleted:
<
<

The Corpus Server of the Language Bank:

 

How the Common Directories Are Organized?

Basically, there are the following installation directories in addition to the directories provided by the Linux system:

Deleted:
<
<
directory purpose owner real location
 
/v/ used to create a multi-platform metacomputer environment at CSC root /v/
/f/bin the first binaries in the path root /fs/corpus/slash-f/
/usr/bin user binaries that belong to the Redhat Enterprise Linux distribution root /usr/bin/
/p/bin the CSC meta machine binaries ling /fs/corpus/slash-p/
/l/bin or /usr/local/bin the local binary directory ling /fs/corpus/slash-l/bin/
Deleted:
<
<
/c/bin or /usr/local/contrib/bin the CSC approved links to the user-contributed binaries ling /fs/corpus/slash-c/bin/
/c/man or /usr/local/contrib/man the CSC approved links to the user-contributed man pages ling /fs/corpus/slash-c/bin/
/c/appl/CLASS/USERNAME/APPNAME/VERSION/bin the user-contributed binary directories users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/lib the user-contributed lib directories users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/man the user-contributed man directories users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/lic the user-contributed information on the license and conditions of use users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/doc the user-contributed additional documentation users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/README the user-contributed information on purpose of use and the maintenance plan and the contributor's contact information users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/REBUILD the user-contributed information on the needed actions in rebuilding and reinstalling the software users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/latest a symbolic link to the latest 32-bit i386/linux version /c/appl/CLASS/USERNAME/APPNAME/VERSION users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/latest64 a symbolic link to the latest 64-bit i386/linux version /c/appl/CLASS/USERNAME/APPNAME/VERSION users /fs/corpus/slash-c/appl/...

The user-contributed installations use the following directory naming conventions:

variable meaning
CLASS the class of software: ling = linguistics, lang = programming languages, comm = internet, ...
USERNAME the unix account of the contributing user
APPNAME the name of the application
VERSION the version of the application

When a user contributes a software to /c and asks the superuser for approval and inclusion to the global path, there are two possible scenarios for approval:

  1. ADOPTION: Depending on the type of the software and the contributor, the contributed software may be adopted as such. In that case, the adminstrator of the language bank takes over the ownership of the contributed version and links the executables to /l/cbin.
  2. REINSTALLATION: On times, the adminstrator may choose to reinstall the software. All the information for reinstalling the software must be provided to the language bank adminstrator, in the text file REBUILD. The installation may go either to /c/ or /l/, depending on the support level that will be quaranteed by CSC. In /c/, the support is basically delegated to the original contributor, while in /l/, the support is the responsibility of CSC.

What directories are in /usr/local, i.e. /l ?

directory abbreviation function
/l/kielipankki/   The linguistic resources maintained at CSC, the core of the Language Bank of Finland
/l/venus/,
/l/venus/proj/,
/l/venus/corp/

/proj contains symlinks
/corp is a symlink
The linguistic resources maintained by the Department of General Linguistics in the University of Helsinki. This directory is planned as a new location for the University of Helsinki Corpus Server UHLCS (still in venus.ling.helsinki.fi). This directory is not maintained by CSC.
/l/contrib/ i.e. /c/ Contributed applications approved by CSC.
/l/appl/ executables linked to /l/bin/ Local applications maintained centrally by CSC.
/l/bin/ in the path Symbolic links to executables of centrally maintained local applications. Contains pointers to executables in /l/bin/appl/.../.../.../bin/...
 
Changed:
<
<
According to the CSC design principles, the system-denpendent, but machine-independent software will be installed to the /v/ directory tree. Therefore, /l/ will eventually develop into a tree that contains links to /v/. Its function will be to represent a view into a subset of /v/ in a way that is relevant to the corpus server.
>
>

Some important subdirectiories of /l/ (i.e /usr/local/ )

directory function
appl/ A symbolic link to /v/linux24_i386/appl/ that contains applications maintained by CSC.
bin/ Corpus-specific executables maintained by CSC.
contrib/ Software installations contributed by the users.
kielipankki/ The linguistic resources maintained at CSC, the core of the Language Bank of Finland
kotus/ The linguistic resources maintained by the Research Institute for the Languages of Finland. This directory is not maintained by CSC.
venus/ The reserved root for the University of Helsinki Corpus Server (UHLCS) directories. This directory is not maintained by CSC.

Some important projections and shottcuts

/corp/ includes symlinks to /usr/local/venus/corp
/proj/ includes symlinks to /usr/local/venus/proj
/l/ /usr/local/
/c/ /usr/local/contrib/
/contrib/ Contributed applications approved by CSC.

General Design Principles

  • system-denpendent, but machine-independent software will be installed to the /v/ directory tree.
  • /p/ contains unform set of links to /v/
  • /usr/local/ contains links to v/
 

Some "frequently asked" questions?

  • Where are /mnt/corpus/ and /fs/corpus/? The former is a symbolic link to the latter that links to /fs/corpus2/.
  • Where is /corp/? It is a symbolic link to /l/venus/corp/ and is provided for compatibility.
Changed:
<
<
  • Where is /proj/? It is a directory containing symbolic links to subdirectories of /l/venus/proj/. It is provided for compatibility.
>
>
  • Where is /proj/? It is a directory containing symbolic links to subdirectories of /fs/corpus/slash-proj/. It is provided for compatibility.
 
  • What is the difference between /fs/kielipankki/ and /fs/corpus2/slash-l/kielipankki/ (or /l/kielipankki/ for short)? The content of the former is linked to the latter as a subset. The former is used by the scientists interface, while the latter is visible only to the corpus machine.

Multi-platform support

Revision 72006-12-12 - AnssiYliJyra

Line: 1 to 1
 
META TOPICPARENT name="Trash.KitWikiSuomenKielipankki:Intro:TheCorpusServer"
Changed:
<
<

The Corpus Server of the Language Bank: How the Common Directories Are Organized?

>
>

The Corpus Server of the Language Bank:

How the Common Directories Are Organized?

  Basically, there are the following installation directories in addition to the directories provided by the Linux system:

Revision 62006-10-21 - AnssiYliJyra

Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="SuomenKielipankki:Intro:TheCorpusServer"
>
>
META TOPICPARENT name="Trash.KitWikiSuomenKielipankki:Intro:TheCorpusServer"
 

The Corpus Server of the Language Bank: How the Common Directories Are Organized?

Basically, there are the following installation directories in addition to the directories provided by the Linux system:

Revision 52006-10-11 - AnssiYliJyra

Line: 1 to 1
 
META TOPICPARENT name="SuomenKielipankki:Intro:TheCorpusServer"

The Corpus Server of the Language Bank: How the Common Directories Are Organized?

Revision 42006-10-11 - FredKarlsson

Line: 1 to 1
 
META TOPICPARENT name="SuomenKielipankki:Intro:TheCorpusServer"

The Corpus Server of the Language Bank: How the Common Directories Are Organized?

Basically, there are the following installation directories in addition to the directories provided by the Linux system:

directory purpose owner real location
Added:
>
>
/v/ used to create a multi-platform metacomputer environment at CSC root /v/
 
/f/bin the first binaries in the path root /fs/corpus/slash-f/
Changed:
<
<
/p/bin the CSC meta machine binaries root /fs/corpus/slash-p/
>
>
/usr/bin user binaries that belong to the Redhat Enterprise Linux distribution root /usr/bin/
/p/bin the CSC meta machine binaries ling /fs/corpus/slash-p/
 
/l/bin or /usr/local/bin the local binary directory ling /fs/corpus/slash-l/bin/
Changed:
<
<
/c/bin or /usr/local/contrib/bin the local approved links to the user-contributed binaries ling /fs/corpus/slash-c/bin/
/c/man or /usr/local/contrib/man the local approved links to the user-contributed man pages ling /fs/corpus/slash-c/bin/
>
>
/c/bin or /usr/local/contrib/bin the CSC approved links to the user-contributed binaries ling /fs/corpus/slash-c/bin/
/c/man or /usr/local/contrib/man the CSC approved links to the user-contributed man pages ling /fs/corpus/slash-c/bin/
 
/c/appl/CLASS/USERNAME/APPNAME/VERSION/bin the user-contributed binary directories users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/lib the user-contributed lib directories users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/man the user-contributed man directories users /fs/corpus/slash-c/appl/...
Line: 17 to 19
 
/c/appl/CLASS/USERNAME/APPNAME/VERSION/doc the user-contributed additional documentation users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/README the user-contributed information on purpose of use and the maintenance plan and the contributor's contact information users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/REBUILD the user-contributed information on the needed actions in rebuilding and reinstalling the software users /fs/corpus/slash-c/appl/...
Changed:
<
<
/c/appl/CLASS/USERNAME/APPNAME/latest a symbolic link to the latest /c/appl/CLASS/USERNAME/APPNAME/VERSION users /fs/corpus/slash-c/appl/...
>
>
/c/appl/CLASS/USERNAME/APPNAME/latest a symbolic link to the latest 32-bit i386/linux version /c/appl/CLASS/USERNAME/APPNAME/VERSION users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/latest64 a symbolic link to the latest 64-bit i386/linux version /c/appl/CLASS/USERNAME/APPNAME/VERSION users /fs/corpus/slash-c/appl/...
  The user-contributed installations use the following directory naming conventions:
Line: 36 to 39
 
directory abbreviation function
/l/kielipankki/   The linguistic resources maintained at CSC, the core of the Language Bank of Finland
/l/venus/,
/l/venus/proj/,
/l/venus/corp/

/proj contains symlinks
/corp is a symlink
The linguistic resources maintained by the Department of General Linguistics in the University of Helsinki. This directory is planned as a new location for the University of Helsinki Corpus Server UHLCS (still in venus.ling.helsinki.fi). This directory is not maintained by CSC.
Changed:
<
<
/l/cbin/ in the path Contributed applications approved by CSC.
>
>
/l/contrib/ i.e. /c/ Contributed applications approved by CSC.
 
/l/appl/ executables linked to /l/bin/ Local applications maintained centrally by CSC.
/l/bin/ in the path Symbolic links to executables of centrally maintained local applications. Contains pointers to executables in /l/bin/appl/.../.../.../bin/...
Added:
>
>
According to the CSC design principles, the system-denpendent, but machine-independent software will be installed to the /v/ directory tree. Therefore, /l/ will eventually develop into a tree that contains links to /v/. Its function will be to represent a view into a subset of /v/ in a way that is relevant to the corpus server.
 

Some "frequently asked" questions?

  • Where are /mnt/corpus/ and /fs/corpus/? The former is a symbolic link to the latter that links to /fs/corpus2/.
  • Where is /corp/? It is a symbolic link to /l/venus/corp/ and is provided for compatibility.
  • Where is /proj/? It is a directory containing symbolic links to subdirectories of /l/venus/proj/. It is provided for compatibility.
  • What is the difference between /fs/kielipankki/ and /fs/corpus2/slash-l/kielipankki/ (or /l/kielipankki/ for short)? The content of the former is linked to the latter as a subset. The former is used by the scientists interface, while the latter is visible only to the corpus machine.
Added:
>
>

Multi-platform support

(Finnish draft text:) /c-hakemistoon kontribuoiville uutena lisätietona että mikäli asennus voidaan ja kannattaa tehdä myös 64-bittiselle linux-alustalle, kontribuoijien kannattaa tehdä se samalla kertaa, niin että voimme hyödyntää corpus4:sta 64-bittisenä sitten kun 64-bittinen linux-palvelin corpus4.csc.fi tulee saataville. 64-bittinen asennus tehdään omana versionaan hakemistoon /c/appl/ling/username/sovellus/versio-64/ jne. Tosin 64-bittisen version kääntäminen ei ole mahdollista corpus3:lla.
 
Changed:
<
<

Questions

>
>

Questions and Answers

 
 
<--/commentPlugin-->
Deleted:
<
<
  • Where can I put the man pages of contributed software? To /c/man? -- AnssiYliJyra - 16 Sep 2006 - 17:23
  -- AnssiYliJyra - 16 Sep 2006

Revision 32006-10-10 - AnssiYliJyra

Line: 1 to 1
 
META TOPICPARENT name="SuomenKielipankki:Intro:TheCorpusServer"

The Corpus Server of the Language Bank: How the Common Directories Are Organized?

Line: 8 to 8
 
/f/bin the first binaries in the path root /fs/corpus/slash-f/
/p/bin the CSC meta machine binaries root /fs/corpus/slash-p/
/l/bin or /usr/local/bin the local binary directory ling /fs/corpus/slash-l/bin/
Changed:
<
<
/l/cbin the local links to the user-contributed binaries ling /fs/corpus/slash-l/cbin/
/c/appl/CLASS/USERNAME/APPNAME/VERSION/bin the user-contributed binary directories users /fs/corpus/slash-c/appl/...
>
>
/c/bin or /usr/local/contrib/bin the local approved links to the user-contributed binaries ling /fs/corpus/slash-c/bin/
/c/man or /usr/local/contrib/man the local approved links to the user-contributed man pages ling /fs/corpus/slash-c/bin/
 
/c/appl/CLASS/USERNAME/APPNAME/VERSION/bin the user-contributed binary directories users /fs/corpus/slash-c/appl/...
Added:
>
>
/c/appl/CLASS/USERNAME/APPNAME/VERSION/lib the user-contributed lib directories users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/man the user-contributed man directories users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/lic the user-contributed information on the license and conditions of use users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/doc the user-contributed additional documentation users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/README the user-contributed information on purpose of use and the maintenance plan and the contributor's contact information users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/REBUILD the user-contributed information on the needed actions in rebuilding and reinstalling the software users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/latest a symbolic link to the latest /c/appl/CLASS/USERNAME/APPNAME/VERSION users /fs/corpus/slash-c/appl/...
  The user-contributed installations use the following directory naming conventions:
Line: 23 to 30
 When a user contributes a software to /c and asks the superuser for approval and inclusion to the global path, there are two possible scenarios for approval:
  1. ADOPTION: Depending on the type of the software and the contributor, the contributed software may be adopted as such. In that case, the adminstrator of the language bank takes over the ownership of the contributed version and links the executables to /l/cbin.
Changed:
<
<
  1. REINSTALLATION: On times, the adminstrator may choose to reinstall the software. All the information for reinstalling the software must be provided to the adminstrator. The installation may go either to /c/ or /l/, depending on the support level that will be quaranteed by CSC. In /c/, the support is basically delegated to the original contributor, while in /l/, the support is the responsibility of CSC.
>
>
  1. REINSTALLATION: On times, the adminstrator may choose to reinstall the software. All the information for reinstalling the software must be provided to the language bank adminstrator, in the text file REBUILD. The installation may go either to /c/ or /l/, depending on the support level that will be quaranteed by CSC. In /c/, the support is basically delegated to the original contributor, while in /l/, the support is the responsibility of CSC.
 

What directories are in /usr/local, i.e. /l ?

directory abbreviation function

Revision 22006-09-17 - AnssiYliJyra

Line: 1 to 1
 
META TOPICPARENT name="SuomenKielipankki:Intro:TheCorpusServer"

The Corpus Server of the Language Bank: How the Common Directories Are Organized?

Line: 25 to 25
 
  1. ADOPTION: Depending on the type of the software and the contributor, the contributed software may be adopted as such. In that case, the adminstrator of the language bank takes over the ownership of the contributed version and links the executables to /l/cbin.
  2. REINSTALLATION: On times, the adminstrator may choose to reinstall the software. All the information for reinstalling the software must be provided to the adminstrator. The installation may go either to /c/ or /l/, depending on the support level that will be quaranteed by CSC. In /c/, the support is basically delegated to the original contributor, while in /l/, the support is the responsibility of CSC.
Changed:
<
<

What directories are in /usr/local or /l ?

/l/kielipankki/ The linguistic resources maintained at CSC, the core of the Language Bank of Finland
/l/venus/,
/l/venus/proj/,
/l/venus/corp/
The linguistic resources maintained by the Department of General Linguistics in the University of Helsinki. This directory is planned as a new location for the University of Helsinki Corpus Server UHLCS (still in venus.ling.helsinki.fi). This directory is not maintained by CSC.
/l/cbin/ Contributed applications approved by CSC.
/l/appl/ Local applications maintained centrally by CSC.
/l/bin/ Symbolic links to executables of centrally maintained local applications. Contains pointers to executables in /l/bin/appl/.../.../.../bin/...
>
>

What directories are in /usr/local, i.e. /l ?

directory abbreviation function
/l/kielipankki/   The linguistic resources maintained at CSC, the core of the Language Bank of Finland
/l/venus/,
/l/venus/proj/,
/l/venus/corp/

/proj contains symlinks
/corp is a symlink
The linguistic resources maintained by the Department of General Linguistics in the University of Helsinki. This directory is planned as a new location for the University of Helsinki Corpus Server UHLCS (still in venus.ling.helsinki.fi). This directory is not maintained by CSC.
/l/cbin/ in the path Contributed applications approved by CSC.
/l/appl/ executables linked to /l/bin/ Local applications maintained centrally by CSC.
/l/bin/ in the path Symbolic links to executables of centrally maintained local applications. Contains pointers to executables in /l/bin/appl/.../.../.../bin/...
 

Some "frequently asked" questions?

Changed:
<
<
  • Where are /mnt/corpus/ and /fs/corpus/? The former is a symbolic link to the latter that links to /fs/corpus2/.
  • Where is /corp/? It is a symbolic link to /l/venus/corp/ and is provided for compatibility.
  • Where is /proj/? It is a symbolic link to /l/venus/proj/ and is provided for compatibility.
  • What is the difference between /fs/kielipankki/ and /l/kielipankki? The content of the former is linked to the latter as a subset. The former is used by the scientists interface, while the latter is visible only to the corpus machine.
>
>
  • Where are /mnt/corpus/ and /fs/corpus/? The former is a symbolic link to the latter that links to /fs/corpus2/.
  • Where is /corp/? It is a symbolic link to /l/venus/corp/ and is provided for compatibility.
  • Where is /proj/? It is a directory containing symbolic links to subdirectories of /l/venus/proj/. It is provided for compatibility.
  • What is the difference between /fs/kielipankki/ and /fs/corpus2/slash-l/kielipankki/ (or /l/kielipankki/ for short)? The content of the former is linked to the latter as a subset. The former is used by the scientists interface, while the latter is visible only to the corpus machine.
 

Questions

 
<--/commentPlugin-->
Changed:
<
<
  • Where can I put the man pages of contributed software? To /c/man? -- AnssiYliJyra - 16 Sep 2006 - 17:23
>
>
  • Where can I put the man pages of contributed software? To /c/man? -- AnssiYliJyra - 16 Sep 2006 - 17:23
 

-- AnssiYliJyra - 16 Sep 2006

Revision 12006-09-16 - AnssiYliJyra

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="SuomenKielipankki:Intro:TheCorpusServer"

The Corpus Server of the Language Bank: How the Common Directories Are Organized?

Basically, there are the following installation directories in addition to the directories provided by the Linux system:

directory purpose owner real location
/f/bin the first binaries in the path root /fs/corpus/slash-f/
/p/bin the CSC meta machine binaries root /fs/corpus/slash-p/
/l/bin or /usr/local/bin the local binary directory ling /fs/corpus/slash-l/bin/
/l/cbin the local links to the user-contributed binaries ling /fs/corpus/slash-l/cbin/
/c/appl/CLASS/USERNAME/APPNAME/VERSION/bin the user-contributed binary directories users /fs/corpus/slash-c/appl/...
/c/appl/CLASS/USERNAME/APPNAME/VERSION/bin the user-contributed binary directories users /fs/corpus/slash-c/appl/...

The user-contributed installations use the following directory naming conventions:

variable meaning
CLASS the class of software: ling = linguistics, lang = programming languages, comm = internet, ...
USERNAME the unix account of the contributing user
APPNAME the name of the application
VERSION the version of the application

When a user contributes a software to /c and asks the superuser for approval and inclusion to the global path, there are two possible scenarios for approval:

  1. ADOPTION: Depending on the type of the software and the contributor, the contributed software may be adopted as such. In that case, the adminstrator of the language bank takes over the ownership of the contributed version and links the executables to /l/cbin.
  2. REINSTALLATION: On times, the adminstrator may choose to reinstall the software. All the information for reinstalling the software must be provided to the adminstrator. The installation may go either to /c/ or /l/, depending on the support level that will be quaranteed by CSC. In /c/, the support is basically delegated to the original contributor, while in /l/, the support is the responsibility of CSC.

What directories are in /usr/local or /l ?

/l/kielipankki/ The linguistic resources maintained at CSC, the core of the Language Bank of Finland
/l/venus/,
/l/venus/proj/,
/l/venus/corp/
The linguistic resources maintained by the Department of General Linguistics in the University of Helsinki. This directory is planned as a new location for the University of Helsinki Corpus Server UHLCS (still in venus.ling.helsinki.fi). This directory is not maintained by CSC.
/l/cbin/ Contributed applications approved by CSC.
/l/appl/ Local applications maintained centrally by CSC.
/l/bin/ Symbolic links to executables of centrally maintained local applications. Contains pointers to executables in /l/bin/appl/.../.../.../bin/...

Some "frequently asked" questions?

  • Where are /mnt/corpus/ and /fs/corpus/? The former is a symbolic link to the latter that links to /fs/corpus2/.
  • Where is /corp/? It is a symbolic link to /l/venus/corp/ and is provided for compatibility.
  • Where is /proj/? It is a symbolic link to /l/venus/proj/ and is provided for compatibility.
  • What is the difference between /fs/kielipankki/ and /l/kielipankki? The content of the former is linked to the latter as a subset. The former is used by the scientists interface, while the latter is visible only to the corpus machine.

Questions

 
<--/commentPlugin-->
  • Where can I put the man pages of contributed software? To /c/man? -- AnssiYliJyra - 16 Sep 2006 - 17:23

-- AnssiYliJyra - 16 Sep 2006

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback