You are here: welcome » dcore » system_start_and_boot-codes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
dcore:system_start_and_boot-codes [2016/05/09 04:23] – [dCore taking over: '/etc/init.d/tc-config'] nitramdcore:system_start_and_boot-codes [2017/09/25 06:49] (current) – [Check boot-parameters] sm8ps
Line 143: Line 143:
  
  
-====Check boot parameters====+====Check boot-parameters====
  
-  - check the boot stanza for boot-codes with values and store them as variables, with the appropriate value, if applicable. +  - check the boot-stanza for boot-codes with values and store them as variables, with the appropriate value, if applicable. 
-  - check the boot stanza for boot-codes without values and store them as variables of value 1.+  - check the boot-stanza for boot-codes without values and store them as variables of value 1.
  
 Thus we have the following list of boot-codes and variables with values: Thus we have the following list of boot-codes and variables with values:
Line 186: Line 186:
  
   * **multivt** and **noembed** in 'init' (on initrd) as seen above   * **multivt** and **noembed** in 'init' (on initrd) as seen above
-  * **lst** (TARGETLIST, defaults to 'onboot.lst') and cde (CDE) in '/usr/bin/tce-setup'+  * **lst** (TARGETLIST, defaults to 'onboot.lst') and **cde** (CDE) in '/usr/bin/tce-setup'
  
 +=== Kernel boot-parameters ===
 +Additional boot-codes have been treated by the kernel at boot-time already. One [[http://forum.tinycorelinux.net/index.php/topic,21401.0.html|notable case]] is //resume// which, although similar in syntax to //home//, //opt// and //tce// does not accept disk LABELs.
 ==== Starting the work ==== ==== Starting the work ====
  
Line 498: Line 500:
  
  
-=====Shell inits=====+=====Shell Inits=====
  
 A login shell first reads commands from the files '/etc/profile' and '.profile' if they exist. If ENV is set on entry to a shell, or is set in the .profile of a login shell, the shell next reads commands from the file named in ENV. (Cf. [[http://linux.about.com/library/cmd/blcmdl1_ash.htm|source]].) ENV is indeed set to '~/.ashrc' in '~/.profile' (see below). A login shell first reads commands from the files '/etc/profile' and '.profile' if they exist. If ENV is set on entry to a shell, or is set in the .profile of a login shell, the shell next reads commands from the file named in ENV. (Cf. [[http://linux.about.com/library/cmd/blcmdl1_ash.htm|source]].) ENV is indeed set to '~/.ashrc' in '~/.profile' (see below).
Line 590: Line 592:
   - (commented out) start an Xterm as a background process.   - (commented out) start an Xterm as a background process.
  
 +=== Auto-start files === 
 +Note that files under '~/.X.d/' must contain backgrounded commands, i.e. with trailing "&".
 ====Log-console==== ====Log-console====
  
Print/export
QR Code
QR Code dcore:system_start_and_boot-codes (generated for current page)