From 4ee354a739294d996f28b9c546c55762a7884ca8 Mon Sep 17 00:00:00 2001 From: "R. Steve McKown" Date: Wed, 16 Dec 2009 11:13:26 -0700 Subject: [PATCH] Fixes for some shuffling of git repos, and use of code spans via back-ticks. --- in/aptrepo.md | 6 +++--- in/cp210x.md | 2 +- in/ovzbpc.md | 28 +++++++++++++--------------- in/tinyos.md | 8 ++++---- in/tinyospkgs.md | 22 +++++++++++----------- 5 files changed, 32 insertions(+), 34 deletions(-) diff --git a/in/aptrepo.md b/in/aptrepo.md index a505740..aedc4cd 100644 --- a/in/aptrepo.md +++ b/in/aptrepo.md @@ -17,9 +17,9 @@ Karmic. ## Step 1 - Add the backports repository Ubuntu Hardy users need to activate the hardy-backports repository, as our -`cp210x-module-dkms` package requires a newer dkms than is available otherwise. -Ubuntu Karmic users can skip this step. You can also activate hardy-backports -from the GUI. +`cp210x-module-dkms` package requires a newer `dkms` than is available +otherwise. Ubuntu Karmic users can skip this step. You can also activate +hardy-backports from the GUI. sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak cat <<+EOF+ | sudo tee -a /etc/apt/sources.list diff --git a/in/cp210x.md b/in/cp210x.md index e6b1f76..8b39da9 100644 --- a/in/cp210x.md +++ b/in/cp210x.md @@ -16,7 +16,7 @@ the cp2103 part. With support from Silicon Labs, TMI has modified their GPLv2 licensed reference Linux driver to support all of the features their Windows DLLs and utilities -provide. This is accomplished via extended ioctl() calls from the kernel +provide. This is accomplished via extended `ioctl()` calls from the kernel cp210x driver, and various utilities and sample code. This code is invaluable for those working on hardware designs using the cp2103. The code is released under the GPLv2. diff --git a/in/ovzbpc.md b/in/ovzbpc.md index 9f5bdbe..3c03dc8 100644 --- a/in/ovzbpc.md +++ b/in/ovzbpc.md @@ -3,9 +3,7 @@ linktitle: ovzbpc parent: TOP ctime: 2008-06-09 -Repositories: [backuppc](http://repo/gitweb/?p=backuppc.git;a=tree), -[ovz](http://repo/gitweb/?p=ovz.git;a=tree), -[esata](http://repo/gitweb/?p=esata.git;a=tree). +Repositories: [ovzbpc](http://repo/gitweb/?p=ovzbpc.git;a=summary). # TMI backup strategy @@ -17,18 +15,18 @@ BackupPC disk archive is made on one of a pool of external eSATA drives, which are rotated off-site for disaster recovery. TMI has authored a few program scripts which integrate these backup components. -* [BackupPC_ovz](http://repo/gitweb/?p=backuppc.git;a=blob;f=README;hb=HEAD) - allows an OpenVZ VE to be backed up and restored via BackupPC without - special configuration of the VE, nor with BackupPC being told on which - hardware node the VE is running. +* `BackupPC_ovz` allows an OpenVZ VE to be backed up and restored via BackupPC + without special configuration of the VE, nor with BackupPC being told on + which hardware node the VE is running. See the + [README](http://repo/gitweb/?p=ovzbpc.git;a=blob;f=README;hb=HEAD) for more + information. -* bpcdump and friends support cloning the BackupPC VE to a removeable eSATA - drive for disaster recovery. See [README.recover](http://repo/gitweb/?p=ovz.git;a=blob;f=README.recover;hb=HEAD) +* `bpcdump` and friends support cloning the BackupPC VE to a removeable eSATA + drive for disaster recovery. See [README.bpcdump](http://repo/gitweb/?p=ovzbpc.git;a=blob;f=README.bpcdump;hb=HEAD) for more information. -* The [esata](http://repo/gitweb/?p=esata.git;a=tree) wraps the `scsiadd` - utility for properly handling eSATA drives on Dell PE1800 and PE1900 - platforms. Newer hardware and better Linux kernel support will someday make - scripts like this unnecessary. See the included - [README](http://repo/gitweb/?p=esata.git;a=blob;f=README;hb=HEAD) for more - information. +* `esata` wraps the `scsiadd` utility for properly handling eSATA drives on + Dell PE1800 and PE1900 platforms. Newer hardware and better Linux kernel + support will someday make scripts like this unnecessary. See + [README.esata](http://repo/gitweb/?p=ovzbpc.git;a=blob;f=README.esata;hb=HEAD) + for more information. diff --git a/in/tinyos.md b/in/tinyos.md index 03414bb..2ec294b 100644 --- a/in/tinyos.md +++ b/in/tinyos.md @@ -3,7 +3,7 @@ linktitle: tinyos parent: TOP ctime: 2009-12-07 -Repositories: [tinyos](http://repo/gitweb/?p=tmi/tinyos-2.x.git;a=summary), +Repositories: [tinyos](http://repo/gitweb/?p=tinyos-2.x.git;a=summary), [[aptrepo]]. TMI maintains a [TinyOS](http://www.tinyos.net) branch containing certain @@ -12,9 +12,9 @@ code imported from CVS upstream, our internal working branches, and tags marking a series commits that are a clean patch series of the TMI enhancements against an official upstream release. -* Current patchset tag: patchset/2.1.0-3 -* Derived from official release tag: tinyos/2.1.0 -* View the latest patchset [here](http://repo/gitweb/?p=tmi/tinyos-2.x.git;a=shortlog;h=refs/tags/patchset/2.1.0-3). +* Current patchset tag: `patchset/2.1.0-3` +* Derived from official release tag: `tinyos/2.1.0` +* View the latest patchset [here](http://repo/gitweb/?p=tinyos-2.x.git;a=shortlog;h=refs/tags/patchset/2.1.0-3). The TMI TinyOS code requires a newer [[msp430]] toolchain. A complete TinyOS development environment including a newer toolchain is available for diff --git a/in/tinyospkgs.md b/in/tinyospkgs.md index f6a5240..d1d24b6 100644 --- a/in/tinyospkgs.md +++ b/in/tinyospkgs.md @@ -3,13 +3,13 @@ linktitle: tinyospkgs parent: aptrepo ctime: 2009-12-10 -Repositories: [tinyos](http://repo/gitweb/?p=tmi/tinyos-2.x.git;a=summary), +Repositories: [tinyos](http://repo/gitweb/?p=tinyos-2.x.git;a=summary), [[aptrepo]]. # Package versioning The TinyOS packages are built from the TMI -[TinyOS repository](http://repo/gitweb/?p=tmi/tinyos-2.x.git;a=summary). The +[TinyOS repository](http://repo/gitweb/?p=tinyos-2.x.git;a=summary). The package version number is of the form `tosver-tmiver`, where `tosver` is the official TinyOS release version on which the code is based, and `tmiver` is the version of the modifications applied by TMI. Released APT package versions are @@ -37,15 +37,15 @@ to the latest TinyOS version. The TMI approach allows multiple TinyOS trees to be installed simultaneously, thereby allowing different applications to be compiled against different TinyOS versions. -The official TinyOS installs the source tree at /opt/tinyos-2.x. The TMI -version installs source trees at /opt/tinyos/VER. For example, the latest TMI -tree is installed at /opt/tinyos/2.1.0-3. TMI also maintains in its repository -the last few official source trees. At least one must be installed, and the -developer may install others as needed. When installing or upgrading TMI -TinyOS packages via APT, the latest TMI tree package is automatically installed. -Source the script `/opt/tinyos/tinyos.sh` to set the three you wish to use. -Source this script from your login profile with no argument to ensure that your -tree selection is persistent across logins. +The official TinyOS installs the source tree at `/opt/tinyos-2.x`. The TMI +version installs source trees at `/opt/tinyos/VER`. For example, the latest +TMI tree is installed at `/opt/tinyos/2.1.0-3`. TMI also maintains in its +repository the last few official source trees. At least one must be installed, +and the developer may install others as needed. When installing or upgrading +TMI TinyOS packages via APT, the latest TMI tree package is automatically +installed. Source the script `/opt/tinyos/tinyos.sh` to set the three you wish +to use. Source this script from your login profile with no argument to ensure +that your tree selection is persistent across logins. This is the currently available trees as of this writing. You can use the command shown below to at any time view the available source trees. -- 2.39.2