Changes between Version 5 and Version 6 of SeattleOnNokia

Changes between Version 5 and Version 6 of SeattleOnNokia

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 5 and Version 6 of SeattleOnNokia

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 5 and Version 6 of SeattleOnNokia

Show
Ignore:
Timestamp:
01/10/10 18:01:52 (10 years ago)
Author:
imcheng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SeattleOnNokia

    v5 v6  
    1111 1. Select the "maemo extras" entry and Edit.  
    1212 1. Uncheck the "disabled" box.  
    13  1. Refresh the installable package list, and packages that we require should now show up. 
     13 1. Refresh the installable package list, and packages that are required should now show up. 
    1414 
    1515[[BR]] 
     
    2929Find and install "openssh" package. During installation the first time, you will be prompted for a new password. Enter your password of choice and remember it for later. Root shell access can be obtained using "ssh root@localhost". You will be prompted for the password you entered during installation. 
    3030 
     31[[BR]] 
     32 
     33=== Subversion === 
     34You will need the "subversion" package in order to check out the repository to run unit tests. 
     35 
     36[[BR]] 
    3137---- 
    3238 
    3339== Setting up Seattle == 
    3440[[BR]] 
    35 Download Seattle tarball here. 
     41Download Seattle tarball here. Next, extract the tarball, and navigate to the Seattle directory. You will need root access to configure Seattle to startup properly. See above on how to gain root access.  
     42[[BR]] 
     43To install, run '''./install.sh'''. Seattle will be automatically started. To check that it is running, run the command 
    3644 
    37  1. Make sure you are operating on a Linux system. 
    38  1. Choose an output folder for the base installers. Note: If there are already base installers of the same names in this folder, they will be overwritten without warning. 
    39  1. Navigate to the trunk/dist directory. 
    40  1. Run the program (make_base_installers.py) with the following arguments: 
    41    1. Various flags that will modify the behavior of the program. Include "m" to create a Mac installer, "l" to create a Linux installer, "w" to create a Windows installer, "i" to create a Windows Mobile installer, "a" to create installers for all supported Operating Systems, and "t" (optional) to include the test cases with the installers. Example: "mlt" will build Mac and Linux installers with test cases. 
    42    1. The path to trunk; for example, ".." if you are running from the dist directory. 
    43    1. The path to the public key that the installation will eventually use to communicate with the software updater. 
    44    1. The path to the private key that the installation will eventually use to communicate with the software updater. 
    45    1. The path to the output directory that you wanted any created installers to end up in. 
    46    1. (Optional) The version of the installer which will be included in the installer name. 
     45{{{ 
     46ps -f | grep nmmain.py | grep -v grep 
     47}}} 
     48 
     49To stop Seattle, run '''./stop_seattle.sh'''. Run '''./start_seattle.sh''' to restart it.  
     50[[BR]] 
     51To uninstall Seattle. Run '''./uninstall.sh'''. You will again need root access. 
     52 
    4753---- 
    48  
    4954== Running Seattle Unit Tests == 
    5055[[BR]] 
     
    5257[[BR]] 
    5358Next, follow the instructions on "Running the Repy VM tests" [https://seattle.cs.washington.edu/wiki/UnitTests#RunningtheRepyVMtests here]. 
    54 You may also try the Node Manager tests and Software Updater tests. Follow the instructions [https://seattle.cs.washington.edu/wiki/UnitTests#RunningNodemanagerTests here] and [https://seattle.cs.washington.edu/wiki/UpdaterUnitTests here] for the Node Manager tests and Software Updater tests, respectively. 
     59[[BR]] 
     60[[BR]] 
     61You may also try the [https://seattle.cs.washington.edu/wiki/UnitTests#RunningNodemanagerTests Node Manager tests] and [https://seattle.cs.washington.edu/wiki/UpdaterUnitTests Software Updater tests]. However, these tests will take an extremely long time to run and it is likely that the tablet will need to be plugged in to power during the tests.