diff --git a/.cvsignore b/.cvsignore
index e69de29..f20eaf2 100644
--- a/.cvsignore
+++ b/.cvsignore
@@ -0,0 +1 @@
+usbmon-5.2.tar.gz
diff --git a/import.log b/import.log
new file mode 100644
index 0000000..fa20467
--- /dev/null
+++ b/import.log
@@ -0,0 +1 @@
+usbmon-5_2-1_fc11:HEAD:usbmon-5.2-1.fc11.src.rpm:1229626176
diff --git a/sources b/sources
index e69de29..50cad5b 100644
--- a/sources
+++ b/sources
@@ -0,0 +1 @@
+cbba81a5b47b811dafd897cd7bd72dee  usbmon-5.2.tar.gz
diff --git a/usbmon.spec b/usbmon.spec
new file mode 100644
index 0000000..f7e2b82
--- /dev/null
+++ b/usbmon.spec
@@ -0,0 +1,46 @@
+Name:		usbmon
+Version:	5.2
+Release:	1%{dist}
+Summary:	A basic front-end to usbmon
+
+Group:		System Environment/Base
+License:	GPLv2
+URL:		http://people.redhat.com/zaitcev/linux/
+Source:		http://people.redhat.com/zaitcev/linux/%{name}-%{version}.tar.gz
+BuildRoot:	%{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
+
+# The possibility of anyone using usbmon to debug USB-over-IP modules on s390
+# is quite remote. Should we exclude it?
+# ExcludeArch:	s390 s390x
+
+%description
+The usbmon program collects and prints a trace of USB transactions as they
+occur between the USB core and HCDs. Analyzing the trace helps to debug the
+kernel USB stack, device firmware, and applications.
+
+%prep
+%setup -q
+
+%build
+make %{?_smp_mflags} CFLAGS="$RPM_OPT_FLAGS" 
+# Builds outside of the Koji/Brew fail unless we mkdir. How do other RPMs work?
+%install
+rm -rf $RPM_BUILD_ROOT
+mkdir -p $RPM_BUILD_ROOT/%{_mandir}/man8
+install -p -m 644 -t $RPM_BUILD_ROOT/%{_mandir}/man8 usbmon.8
+mkdir -p $RPM_BUILD_ROOT/%{_sbindir}
+install -p -m 755 -t $RPM_BUILD_ROOT/%{_sbindir} usbmon
+
+%clean
+rm -rf $RPM_BUILD_ROOT
+
+#files -f %{name}.lang
+%files
+%defattr(-,root,root,-)
+%doc README COPYING
+%{_sbindir}/usbmon
+%{_mandir}/man8/usbmon.8*
+
+%changelog
+* Sun Dec 7 2008 Pete Zaitcev <zaitcev@redhat.com> 5.2-1
+- Initial revision (5.2)