Dit staat in het "Readme" Bestand.
THE SHORT STORY:
================
This archive contains debian installation packages for SMART Notebook Software and SMART Product Drivers, and a customization template file.
To prepare the packages for use, you will have to go through the following steps, which are explained in detail in THE LONG STORY below:
- verify the integrity of the files you received;
- obtain a product key, either online from SMART or from your vendor channel;
- select a master signing key to use for signing the relevant data with gpg (these first three steps can happen in any order)
- edit the customization template file to insert your product key, your gpg key ID, to select the content galleries you wish, etc
- execute the automated procedure which merges the customization information into the packages
THE LONG STORY:
===============
In order to activate your software for a silent remote deployment and also in order to customize the installation, you must edit the customization file named "customization" before you install the software.
The installation data can be shipped in two forms: package set or debian archive
0. Prerequisites:
+++++++++++++++++
Ensure the packages dpkg, dpkg-dev, dpkg-deb, dpkg-sig and binutils are installed. You will also need gpg, md5sum, sha1sum, sha256sum and things like sed, cut and tr.
1. Method 1: Installing a Package Set
+++++++++++++++++++++++++++++++++++++
You will receive an archive named SMART_software_deb_files.tar.gz containing the following:
1.1 Debian package files named:
smart-common_<version>_i386.deb
smart-hwr_<version>_i386.deb
smart-languagesetup_<version>_i386.deb
smart-activation_<version>_i386.deb
smart-gallerysetup_<version>_i386.deb
smart-notebook_<version>_i386.deb
smart-product-drivers_<version>_i386.deb
nwfermi-<version>_i386.deb
1.2 Corresponding integrity information files named smart-common_i386_sha256sum.asc (and so on)
1.3 A file named swbuild.asc containing the public key we use as the archive signing key.
Our key ID is 7DD63D3B and the fingerprint is
2907 DB4C CC5D 44D8 3694 5F8A BB8D 4237 7DD6 3D3B
A script named validate.sh
A customization file named "customization"
A script named customize.sh
This README file
1.4 In order to verify the integrity of the packages, keeping all these files in the current working directory, do this:
1.4.1: import the key from swbuild.asc to gpg and find the fingerprint;
1.4.2: confirm the fingerprint with SMART or your vendor channel;
1.4.3: sign the key with your own ultimately trusted key;
1.4.4: execute the command "./validate.sh files" in order to verify the integrity of the package files you have received, and check the output;
1.5 Once the packages are verified, you will first edit the customization file. It contains script variables which are explained by the comments that precede them. For a remote silent mass deployment it is necessary to insert the product key obtained from SMART or your vendor channel. You may also wish to select which gallery components you wish to make available
1.6 When the customization file is modified appropriately, you will execute "./customize.sh files" which will modify all the .deb package files by inserting the contents of the customization file into the maintainer scripts of each package. At this point the .asc integrity files are remade and they are signed with the key specified on the SMART_ARCHIVE_KEY line, in the customization file. If SMART_ARCHIVE_KEY is not set, the current user's default key will be used for signing.
1.7 Once the packages have been customized, they can be installed with "dpkg -i" or inserted into your particular deployment framework.
2. Method 2: Installing a Debian Archive
++++++++++++++++++++++++++++++++++++++++
You will receive an archive named SMART_software_deb_repo.tar.gz containing the following:
2.1 A linear directory tree which looks like:
dists -> stable -> non-free -> binary-i386
The last directory, binary-i386, will contain debian package files named:
smart-common_<version>_i386.deb
smart-hwr_<version>_i386.deb
smart-languagesetup_<version>_i386.deb
smart-activation_<version>_i386.deb
smart-gallerysetup_<version>_i386.deb
smart-notebook_<version>_i386.deb
smart-product-drivers_<version>_i386.deb
nwfermi-<version>_i386.deb
Also, the stable and binary-i386 directories will contain debian archive metadata. Note that the customization script provided will reconstruct part of this metadata after modifying the packages themselves.
2.2 A file named swbuild.asc containing the public key that signed the .asc files.
You should also be able to import this key directly from the key servers.
Our key ID is 7DD63D3B and the fingerprint is
2907 DB4C CC5D 44D8 3694 5F8A BB8D 4237 7DD6 3D3B
A script named validate.sh
A customization file named "customization"
A script named customize.sh
This README file
2.3 In order to verify the integrity of the packages, keeping all these files in the current working directory, do this:
2.3.1: import the key from swbuild.asc to gpg and find the fingerprint;
2.3.2: confirm the fingerprint with SMART or your vendor channel;
2.3.3: sign the key with your own ultimately trusted key
2.3.4: execute the command "./validate.sh archive" in order to verify the integrity of the package files you have received, and check the output; if you wish to follow the validation process you can use the command "bash -x validate.sh archive" ; the following is an overview of that process:
2.3.4.1: cd to dists/stable
2.3.4.2: check the Release file with the command:
gpg --verify Release.gpg Release
2.3.4.3: check the Packages metadata files under binary-i386 thus:
cat Release|tr -s ' ' |cut -d' ' --fields=2,4 |sed 's% % %' > t
sha256sum -c t
This will check the non-free/binary-i386/Packages.* files
2.3.4.4: cd to non-free/binary-i386
2.3.4.5: check the actual package files using the Packages file, thus:
grep MD5sum Packages > a
dpkg-scanpackages . ../../smart.override |grep MD5sum > b
diff a b
There should be no difference; the last command should produce no output. If a line differs, then that line identifies a corrupt package file. Find that line in the Packages file, on a line that begins with MD5sum, and, two lines above it, the line that begins with Filename names the corrupt package file. The script displays the names of packages discovered in this way.
2.3.4.6: verify the signature of each package file with the command:
dpkg-sig --verify <package file name>
2.4 Once the packages are verified, you will first edit the customization file placed outside dists. It contains script variables which are explained by the comments that precede them. For a remote silent mass deployment it is necessary to insert the software product key obtained from SMART or from your vendor channel. You may also wish to select which gallery components you wish to make available. Your own archive key ID is needed for re-signing the main Release file, and should be assigned to SMART_ARCHIVE_KEY.
2.5 When the customization file is modified appropriately, you will execute "./customize.sh archive" which will modify all the .deb package files by inserting the contents of the customization file into the maintainer scripts of each package. Then it will rebuild the archive metadata, recompute the integrity checksums and sign the main Release file. The new Release file should be signed with your own archive key rather than ours. For that, you must edit the SMART_ARCHIVE_KEY line in the customization file and place your key ID there. If SMART_ARCHIVE_KEY is not set, the current user's default key will be used for signing.
2.6 Once the packages have been customized and the debian archive rebuilt, it can be copied in its entirety into the desired place in the document tree of your web server. Then, before the packages are available for installation with "apt-get install", you must do the following, once, on each target machine:
2.6.1. add a one-line source file under /etc/apt/sources.list.d/ to identify the archive. The line should look like
deb http://webservername/ubuntu/ stable non-free
(where "ubuntu" stands for the directory into which you have copied "dists", in the document tree of the web server)
NOTE that, if you cannot or will not use a web server, you may also use the "file:" protocol as in
deb file:/home/swbuild/ubuntu/ stable non-free
2.6.2. execute apt-get update
2.6.2.1 In Synaptic, you would go to Settings/Repositories, select the "Third Party Software" tab, click on Add and enter the above line. Then hit the "Reload" button on the toolbar. The new source line will be added at the end of /etc/apt/sources.list.
2.6.3. before doing apt-get update for the first time, you will need to import our public key into the apt key database, thus:
wget http://webservername/ubuntu/dists/swbuild.asc
apt-key add swbuild.asc
3. Customization
++++++++++++++++
You can customize the installation as follows:
- provide the SMART Notebook product key for automatic activation
- install SMART Notebook Software or SMART Product Drivers or both
- disable the autostart of SMART Board Service and SMART Board Tools
- customize the installation of Gallery Essentials:
- select individual gallery categories
- install the gallery from predownloaded source
- install the gallery in a customized location
- register a previously installed gallery, for example, a gallery on a shared network
- register team content
- select your own source URL for downloading gallery content
3.1 The last feature, setting up gallery content on your own web server as a download source, was added upon request and is documented in the following paragraphs.
We will assume that your web site is http://myweb.company.com and that the document root of your server is /var/www and the gallery data will be in /var/www/efe, accessed as http://myweb.company.com/efe.
3.1.1. To get the gallery data in the right place it must be downloaded from SMART (at least initially). Here is how to do it simply:
3.1.1.1. Make the directory to receive the data (/var/www/efe).
3.1.1.2. Install the packages in the default location with their default gallery source URL (which is currently http://downloads01.smarttech.com/software/efe/)
3.1.1.3. Download the data to its intended location with the following command:
/opt/SMART Technologies/Gallery Setup/bin/GallerySetup \
--downloadall \
--destination /var/www/efe \
--configuration /opt/SMART Technologies/Gallery Setup/share/SMARTEssentials.gallerycollection
3.1.1.4. When this is done, point a browser at your web server and check that you see a long list of files ending in .gallery or in .zip
3.1.2. To make use of your new download source you will customize the packages accordingly. In the customization file, edit the following line as follows, making sure it is not commented:
export CONTENT_LOCAL_URL=http://myweb.company.com/efe
Then add your other customizations, execute customize.sh and install the customized packages. While "Setting up smart-notebook", a message like the following will indicate your web server connection is checked:
Checking connection to: http://myweb.company.com/efe
Check succeeded
and then you will see the selected gallery components being downloaded and installed.
3.1.3. To revert to the original download source which came built into the software, simply comment out the CONTENT_LOCAL_URL line and run customize.sh again.
4. Dependencies
+++++++++++++++
The two main packages are smart-product-drivers and smart-notebook; the other five are their dependencies.
smart-notebook_<version>_i386.deb:
Main SMART Notebook package.
Dependencies:
smart-common
smart-hwr
smart-languagesetup
smart-activation
smart-gallerysetup
smart-product-drivers_<version>_i386.deb:
Main SMART Product Drivers package.
Dependencies:
smart-common
smart-hwr
smart-languagesetup
nwfermi-<version>_i386.deb
SB480 Drivers package.
5. Installation
+++++++++++++++
For package sets you can use "dpkg --install", for example:
dpkg --install smart-common_10.2.286.0-1_i386.deb
For archives accessed over a network you can use "apt-get install", for example:
apt-get install smart-common
Note that whenever changes are made to the online archive, "apt-get update" should be run on the target machines.
Also note that apt-get installs dependencies, so that running, for example:
apt-get install smart-product-drivers smart-notebook nwfermi
will actually install all packages
The following environment variables can be set in order to follow what the installation does (they are intended for use with dpkg):
5.1 Logging: setting DEB_MAINTAINER_LOG to some value, and also DEB_MAINTAINER_LOGPATH to the desired path, will cause the maintainer scripts in the packages to log the installation and uninstallation events to a file named smart_debian_install.log under the specified path.
5.2 Tracing: setting DEB_DEBUG_SCRIPTS to some value before installing or uninstalling will cause the package scripts to be executed with "set -x" with the usual screen output.
5.3 Bypassing package scripts: If the scripts fail so severely that they will let you neither completely install nor uninstall, they can be bypassed. Bypassing while purging enables one to remove the package, thus:
env DEB_MAINTAINER_NOSCRIPTS=1 dpkg --purge smart-common
6. Uninstallation
+++++++++++++++++
The software is installed into /opt/SMART Technologies. Other files will be placed in /etc/xdg, /etc/udev/rules.d, /usr/share (doc, man/man1, icons/hicolor, pixmaps/hicolor, applnk, mimelnk/application), /usr/local/share/applications and $HOME/.config
Most files are removed by the usual package removal process.
The following files are left behind after uninstallation:
6.1 global configuration files:
/etc/xdg/SMART Technologies/*.conf
/etc/xdg/SMART Technologies.conf
6.2 activation data:
/opt/SMART Technologies/common/data/.mp.1.1.dat
/opt/SMART Technologies/common/data/.vp.1.1.dat
6.3
Mime xml files wherever they are installed.
6.4
Files created in the current user's home under $HOME/.config
