PC Repair Software and Beyond
c02ware is the software programming arm of Tritech Computer Solutions. Most of the work we do is centered around enhancement of Tritech's computer repair and servicing workflow. We are not currently accepting new software project requests.
Perhaps you came here looking for our super-special Linux distribution, the Tritech Service System.
If you need to execute programs in chroot environments transparently, we offer AlterEgo.
When we patch a trivial error in compilation, we try to give back to the community through our Linux software patches collection.
Or maybe you're looking for the Linux-to-Linux/Windows remote sound notification kit, snd2remote.
We have a nice uClibc-based i386 chroot development environment you can download which includes a recent uClibc (pre-0.9.34 from Git), a very recent BusyBox, GNU Bash, GCC, Perl, Python, and Git. This filesystem is self-hosting (it can be used to build itself) and is confirmed to build a Linux kernel correctly among other things. To use it, unpack it anywhere, "cd" into the tss_uclibc-i386 directory it creates, and type "./go32"; this script performs bind-mounts to attach /dev, /usr/src, and /home to the system, brings up /sys and /proc and /tmp, and changes into the development filesystem as root. Since the miscellaneous bits were brought in using the Tritech Service System, there's a user account with no password called "tss" that you can change to with "su" to perform safer non-root compilations and tests. With minor modifications, it can also be used as a complete root filesystem. Download the TSS i386 uClibc development filesystem (updated 2014-02-05) here. Everything in this package was cross-compiled from scratch without using automated tools such as Buildroot or Crosstool-NG. For what it's worth, we have never succeeded in getting Buildroot to build a self-hosting uClibc root filesystem, ever, and this is after six years of random attempts...thus, we started from scratch. Also note that uclibc_ldso_stat64_fix.patch was used to compile uClibc/i386 because of the problems detailed here.
Also, here's a uClibc-based x86-64 chroot development environment (updated 2013-10-20) built in the same fashion; use "./go64" instead of "./go32" to chroot into it.