Problem: Embedded version on Jetway barebone system



  • Hello

    I'm installing pfSense on a Jetway barebone Atom system with a CF card installed (4GB), no hard-disk

    I have tried the following steps:

    1. I have written the nanoBsd image to Cf: Result: no data on console. I think there was some problem to complete the boot, and errors arise before serial communication is configured.
    2. So then i have installed from liveCd directly on Cf

    So I continue from step 2)

    2.a) I have chosen the "Embedded Kernel" option during the installation. Result: boot from CF never complete successfully.
    2.b) So then I have repeated the installation from liveCd, choosing the "Normal Kernel". Result: boot is ok.

    After reboot I have typed the following commands:

    echo "embedded" > /etc/platform
    /etc/rc.conf_mount_ro
    reboot

    Here the result:

    #mount

    /dev/ad2s1a on / (ufs, local, read-only)
    devfs on /dev (devfs, local, multilabel)
    /dev/md0 on /tmp (ufs, local)
    /dev/md1 on /var (ufs, local)
    devfs on /var/dhcpd/dev (devfs, local, multilabel)

    #df

    Filesystem  1K-blocks   Used   Avail Capacity  Mounted on
    /dev/ad2s1a   3799198 169390 3325874     5%    /
    devfs               1      1       0   100%    /dev
    /dev/md0        39406     66   36188     0%    /tmp
    /dev/md1        59246   6352   48156    12%    /var
    devfs               1      1       0   100%    /var/dhcpd/dev

    My questions are:

    Now is /tmp on Ram or on Cf ?
    If it's on Cf, how can I mount it on Ram ?
    Is /var on Ram or Cf ?
    Does I need to move /var on Ram or not ? (to reduce writing cycles on Cf)
    Codul you help me to do it please ? Any advices will be gratefully accepted

    Thank you in advance for any help

    Borgo (from Italy)



  • /tmp is on RAM (md0)
    /var is on RAM (md1)



  • Thank you very much Havok
    you make me very happy

    So my installation is correct and my CF memory is safe: root file system is read-only and /var and /tmp are on ram


Log in to reply