CLEO3 programming on Linux portable PC.

Uploaded on:
There are outsider bundles needed by CLEO programming. CLHEP, Tcl/Tk, readline, Root, ... No other programming obliged (we pre-construct outsider bundles for you, including ...
Slide 1

Valentine Kouznetsov Cornell University Outlines: Introduction to Linux better approach to convey Cleo3 programming Introduction to RPM Cleo3 RPMs Demonstration Summary CLEO3 programming on Linux portable PC

Slide 2

Introduction to Linux was imagined by Linus Torvalds (Finland, 1991) It keeps running on: Intel/AMD/Cyrix, DEC alphas, Sun, SGI, IBM centralized server (@server), PowerPC, Macs, Amiga, ... It can fit into: floppy, CDROM, ZIP, ROM, RAM, hard drive It can keep running on assortment of equipment including tablets (82+ distinct merchants ) and inserted items like cellular telephones, MP3 players, PDA, TiVO ( Number of Linux conveyances around the globe: 345 (, however in the event that you require you can make your own particular one Number of Linux clients: 18 millions ( Number of docs said Linux: 56 millions ( It utilized all over, from science till film creation (Titanic, Shrek) It utilized by anybody, from my child till German government It is free and open source

Slide 3

better approach to send Cleo3 programming to Linux (programmed establishment utilizing RPM design) We are moving towards Linux and need to figure out how to send cleo3 programming to our teammates We have various discharges and numerous overhauls will be important Installation/update ought to be exceptionally straightforward, in a perfect world "press a catch" and drink your espresso while watching establishment/redesign process RPM organization is accepted standard to convey programming on Linux It\'s anything but difficult to redesign/check/introduce programming User amicable, no particular information is required Guaranteed assemble (while pressing RPM we confirm that discharge was construct and tried) We pack outsider bundles (Tcl, readline, ROOT, CERNLIB) for you utilizing cleo3 particular compiler banners (- fexceptions) If you don\'t care for RPM arrangement it\'s anything but difficult to change over it to another configurations utilizing outsider ( cpio and tar (Unix-like utilities), deb (Debian), tgz (Slackware) Requirements Solution

Slide 4

RPM presentation RPM remains for Red Hat Package Management framework Adopted/utilized by all Linux dispersions Can be introduced on ANY Linux/Solaris/OSF/AIX/SGI frameworks In basic words RPM is a Linux introduce supervisor, rpm records are comparable to of self extricating exe documents on Windows and/or picture records on Macs There are two sort of RPMs records: Binary RPMs are pre-manufacture prepared to go bundles, can be introduced straightaway on your framework. They keep a ton of data where/when bundle was manufactured, bundle depiction, conditions, and so on. Source RPMs contain source code (in tar.gz configuration) and spec document (direction how to fabricate bundle on your framework) Red Hat, SuSE, Mandrake and so on dispersions use RPM is biggest RPM database (for all models and Linux circulations) Currently right around 155K rpms are accessible on this site

Slide 5

Understanding RPM is intense summon line driven bundle administration framework equipped for introducing, uninstalling, confirming, questioning and upgrading PC programming bundles. It utilizes Berkley DB for questioning and keeps depiction of your framework It gives assortment of data about bundle expansive data : time stamp bundle was fabricated, portrayal of bundle\'s substance, all out size of all records introduced by the bundle, computerized "signature", bundle conditions Per-document data : name of each document and where it is to be introduced, every record\'s consents, every document\'s proprietorship, MD5 checksum of every document, the document\'s substance RPM document naming tradition name-form release.architecture.rpm name is a name portraying the bundled programming rendition is the variant of bundled programming discharge is the quantity of times this adaptation of programming has been bundled design is shorthand name depicting the kind of PC equipment the bundled programming is intended to keep running on. Case: am-1.0.0-1.i386.rpm, am-1.0.0-1.src.rpm, am-1.0.0-1.alpha.rpm

Slide 6

Verifying RPM is intense device to look at honesty of your introduced programming There are nine credits RPM is able to catch: File size ( S ) File proprietorship ( U ) Group possession ( G ) File mode, "authorization" ( M ) MD5 checksum is a 128-piece number got from record substance ( 5 ) Major/Minor number is gadget character and square document data utilized by various drivers on the frameworks ( D ) Symbolic connection is the content string containing the name of the connected to record ( L ) Modification time ( T ) Dependencies and missing records SM5DLUGT c filename [vk@localhost vk]$ rpm - qf/nfs/cleo3/Offline/rel/momentum 1.0.0/canister/Linux/g++/suez cleo3-suez-1.0.0-1 [vk@localhost vk]$ rpm - V cleo3-suez-1.0.0-1 Unsatisfied conditions for cleo3-suez-1.0.0-1:/usr/nearby/receptacle/bash,/usr/neighborhood/container/tclsh, S.5....T/nfs/cleo3/Offline/rel/ebb and flow 1.0.0/container/Linux/g++/suez .......T/nfs/cleo3/Offline/rel/ebb and flow 1.0.0/form/lib/.discharge

Slide 7

Using RPMs There are order line and GUI RPM interfaces Install/Upgrade and delete rpm - ivh or - Uvh rpm - e Query rpm - qa | grep <your_RPM> rpm - qf/container/ls rpm - ql cleo3-mcinfo-1.0.0 Building rpm - bb (for paired) rpm - ba (for source/double rpms) Verify rpm - Vf/canister/ls

Slide 8

Cleo3 necessities RedHat 9.0 or whatever other Linux conveyance with taking after bundles: rpm rendition >= 4.2, gcc adaptation >= 3.2.2, glibc form >= 2.3, am-utils There is no prerequisites where to introduce cleo3 programming With root access you require 3Gb on/nfs/cleo3 and 2-4 Gb on/Without root access you require 3 ( in addition to 2-4 ) Gb on your plate for cleo3 programming We give just source RPMs Due to express way necessities you have to modify your common articles and executables regarding your neighborhood establishment way It\'s anything but difficult to exchange few Mb rather then a few Gb Installation script make neighborhood duplicate of RPM DB consequently cleo3 RPMs are isolated from default RedHat RPMs Cleo3 RPMs naming tradition: cleo3-<package_name>- <releaseversion> Cleo3 conditions Cleo3-mcgen requires: cleo3-Gmake, cleo3-suez, cleo3-others, cleo3-mcinfo

Slide 9

Cleo3 release(s) & RPM(s) We add standards to Cleo3 discharge structure: Release adaptation: 1.0.0 (at whatever time stamp or number) Shared items (*.so) acquire discharge rendition: Executables are connected to stack shared objects of specific form: ldd suez.exe/nfs/cleo3/Offline/rel/ebb and flow 1.0.0/lib/Linux/g++/ and flow 1.0.0/lib/Linux/g++/ =>/lib/ RPM adaptation compares to discharge rendition, e.g. cleo3-suez-1.0.0-1.i386.rpm means cleo3-suez bundle was stuffed from discharge 1.0.0, 1 st expand on Linux stage (i386) You may have numerous discharges on plate and distinctive mixes may exists together, e.g. two disconnected discharges may utilize one variant of other_sources Cleo3 bundles assembled into rationale structure bundles (presently 19 RPMs)

Slide 10

CLEO3 RPM association There are outsider bundles required by CLEO programming CLHEP, Tcl/Tk, readline, Root, CERNLIB, mico Offline scripts to setup CLEO environment normal (Online) programming suez mcinfo – set of basic bundles for abnormal state ones mcgen – set of bundles to produce MC 4 vectors cleog – set of bundles to create geant\'ed MC pass2(data,cleo2) to perform pass2 reproduction Cleo3 RPM reliance diagram

Slide 11

Cleo3 RPM measurements & accomplishments I could construct/introduce cleo3 RPMs on this portable PC (Red Hat 9) 256 Mb of RAM, 730 MHz I tried two desktops running Red Hat 8 at Cornell and Minnesota ( patches required ) Build time differing from couple of minutes till 3 hours for every bundle Total time spent: < 12 hours I could run MC era (4 vectors) BBbarGenerationProd Cleog step (50 occasions) Pass2 created MC and genuine information, run 128373 (250 occasions) RPMs introduced on Minnesota ranch: 14K MC occasions (cleog+pass2) Source RPMs 16 Mb Binary RPMs 350 Mb Release territory 2.8 Gb

Slide 12

Need to be done Access to Cleo3 constants DB Through reserve servers Installation tune ups Eliminate cleo2 conditions diminish size of RPMs static versus shared libraries Cleo3 RPMs benefits & uncertain issues Benefits Eliminate client mistakes amid establishment Automatic establishment of ALL essential programming incorporated with suitable Cleo3 banners Modularity: you can introduce just important RPMs relying upon your objective (create MC, run suez/pass2, perform investigation) Software administration If something incorrectly on your framework you can confirm trustworthiness of your product and introduce/eradicate/upgrade it Keep track of numerous discharges Patching adaptation of cleo3 discharges

Slide 13

Installation methodology Automatic establishment script is given (can be found in C3MakeRpms bundle) Guide you through establishment process It makes neighborhood form of RPM db in your wanted area It is characterized wrt to your way: <your_path>/rpm Cleo3 RPMs live in particular RPM db and can\'t hurt your framework No root access to your framework is required But you may introduce Cleo3 RPMs in default RPM db utilizing root account Due to reliance prerequisites you won\'t ready to manufacture abnormal state bundle until you\'ll introduce low-level bundles, e.g. In the event that cleo3-suez is not introduced you can\'t manufacture cleo3-trkobj AND establishment script deals with that You may construct/introduce just those RPM which are appropriate for your objective (to produce MC or investigation) To eradicate Cleo3 bundle: rpm - dbpath <your_path>/rpm - e cleo3-XXX-1.0.0-1 Try, test it and send me your criticism

Slide 14

Manual establishment methodology Automatic establishment script is given Manual establishment requires a couple steps: Create ~/.rpmmacros with %_topdir <your_path> %_tmpdir <your_path>/tmp Create catalog structure to perform RPM fabricate: <your_path>/{BUILD,RPMS/i386, SRPMS,SOURCES,SPECS} cp - r/var/lib/rpm <your_RPMDB_path> Setup your environmen

View more...