Ignore:
Timestamp:
May 13, 2012, 1:14:27 PM (13 years ago)
Author:
rick
Message:

Use an seperate /tmp var disk to provide an more robust system. A full /tmp is
not and issue while an full /var could cause all kind of weird and wonderfull
magic, as PID administration if for example done at /var/run, etc...

Done by undoing the stuff to make it happen by nanobsd.sh, as their is no
direct flag to control it.

As late_customize is an hook never used, make sure it does not break our
package build sub-system.

Related-To: nodefactory:ticket:162

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/releng-9.0/nanobsd/cfg/nanobsd.wleiden

    r10764 r10828  
    362362)
    363363
    364 
    365 # Fill /cfg with custom files, based on 'create_i386_diskimage ( )'
     364# We actually do need an seperate /tmp, so undo the symlinking done in
     365# setup_nanobsd()
     366late_cust_unset_common_var_and_tmp() (
     367        cd ${NANO_WORLDDIR}
     368        rm tmp
     369        mkdir -m 1777 tmp
     370)
     371
     372
     373# Fill /cfg wmth custom files, based on 'create_i386_diskimage ( )'
    366374last_nano_fill_cfg () (
    367375        # Variables to be used
     
    432440customize_cmd cust_set_root_password
    433441customize_cmd cust_apply_nanobsd_patches
     442late_customize_cmd late_cust_unset_common_var_and_tmp
    434443
    435444# Standard overwrite
Note: See TracChangeset for help on using the changeset viewer.