Changes between Version 19 and Version 20 of almosOnTsarDoc

Timestamp:

Aug 21, 2012, 2:55:10 PM (12 years ago)

Author:

almaless

Comment:

--

almosOnTsarDoc

@@ -60 +60 @@
 ''Sim1'' rule means the simulator of TSAR is configured to one cluster, that is, 4 cores. Using ''sim4'', ''sim16'', ''sim64'' or ''sim128'' lets you start the simulator with (respectively) 4, 16, 64 or 128 clusters of 4 cores each.
 
-'''Note''': although the hardware configuration can be changed at each simulation, there is no need to recompile or regenerate the kernel. The kernel of ALMOS detects the hardware resources at each boot. A user application can get the number of online cores using the standard ''sysconf'' call (man sysconf).   
+'''Note''': although the hardware configuration can be changed at each simulation, there is no need to recompile or regenerate the kernel. The kernel of ALMOS detects the hardware resources at each boot. A user application can get the number of online cores using the standard ''sysconf()'' call (man sysconf).   
 
 Now lets take a look inside the ''DISTRIB/test/pf1'' directory. 
@@ -86 +86 @@
  4. Go to your ''DISTRIB/test/pfX'' directory and run the TSAR simulator
  
-Some example of applications source code can be found in ''DISTRIB/apps''. Lets try the ''hello_world'' one. The ''main'' function of this application asks the system for the number of online cores (''count'') and then it fires ''count'' threads before it synchronizes on their end. Each fired thread executes the ''thread_func'' function which prints a "Hello World" message.
+Some example of applications source code can be found in ''DISTRIB/apps''. Lets try the ''hello_world'' one. The ''main()'' function of this application asks the system for the number of online cores (''count'') and then it fires ''count'' threads before it synchronizes on their end. Each fired thread executes the ''thread_func()'' function which prints a "Hello World" message.
 
 To Cross-compile the application using ALMOS headers and static libraries:
@@ -170 +170 @@
 
  1. Redirecting the simulator ttys output to files
- 2. Write a mini script to let the shell automatically executes your programs
-
-
-    
-TBD ...
+ 2. Write a mini-script to let the shell automatically executes your programs
+
+To do the first step you have to set an environment variable ''SOCLIB_TTY'' as fallows:
+
+{{{
+$ export SOCLIB_TTY=FILES
+}}}
+
+Now, lets go to ''DISTRIB/test/pf1'' directory and edit a new ''shrc'' script with the following contents:
+
+{{{
+echo started
+echo exec /bin/hello
+exec /bin/hello
+echo ended
+}}}
+
+This can be done as follows:
+
+{{{
+$ cd DISTRIB/test/pf1
+$ cat > ./shrc
+echo started
+echo going to exec /bin/hello
+exec /bin/hello
+echo ended
+^D
+}}}
+
+Lets show the ''./shrc'' contents before coping it to ''/etc/shrc'' on ALMOS file system image ''hdd-img.bin'':
+
+{{{
+$ cat ./shrc
+echo started
+echo going to exec /bin/hello
+exec /bin/hello
+echo ended
+$ mcopy -i hdd-img.bin ./shrc ::/etc/.
+}}}
+
+'''Note''': the ''shrc'' file name and the ''/etc'' destination directory are required by the shell of ALMOS. The first user process executed by the kernel of ALMOS is ''/bin/init'' which forks and execs the shell ''/bin/sh''. The ''sh'' will systematically look for ''/etc/shrc'' configuration file and executes all of its commands.
+
+Now, we are ready to run the TSAR simulator for a while before killing it and inspecting the generated files:
+
+{{{
+$ make sim1
+^C
+}}}
+