text:
Create a Website Account - Manage notification subscriptions, save form progress and more.
Show All Answers
If you would like to become a registered voter please fill out the voter registration form and mail it in to the Linn County Auditor's Office.
You may mail the form to:
Linn County Election Services935 2nd Street SWCedar Rapids, IA 52404-2100 Voter Registration Form
Linn County Election Services935 2nd Street SWCedar Rapids, IA 52404-2100 Absentee Ballot Request Form
The only time a voter is required to show identification is when a voter has become Inactive and decides to vote.
Poll workers may ask for identification to verify your information.
It is helpful to have your ID and Voter's Registration Card ready before you get to the sign in table.
There is also a web link where results maybe viewed as they come in.
The election results will not appear until the polls have closed.
11 Days before all other elections Pre-registering before an election places your name in the Election Register at your polling place and will make for a hassle-free voting experience. If you are not in the Election Register when appearing at your polling place, you must prove your identity and residence before being allowed to vote. This will take time and documentation. It is highly recommended that you register to vote or update your registration prior to the Pre-registration Deadline.
If you have questions please contact us at 319.892.5300 or [email protected]. Supervisor District Maps
http://ortho.gis.iastate.edu (State of Iowa)
http://www.terraserver.com/providers/usgs_urban.asp (Urbanized Areas Nationwide)

subset: commoncrawl


text:
Emprimus, Inc., Minneapolis, has completed a global licensing agreement for its Solid Ground Grid Stability System with ABB, Zurich, Switzerland.
The transaction grants ABB worldwide rights to manufacture, market and install Emprimus' SolidGround protection system for the electric power grid in North America and around the globe. The SolidGround system is designed to protect the grid against the effects of geomagnetic storm induced currents and electromagnetic pulse-induced currents of any size, by automatically detecting and blocking DC currents from flowing through the neutral of large power transformers.
Brian Miller, managing director for ABB, said that the Emprimus SolidGround system is effective in protecting against the current flare-up of solar storms, a phenomenon expected to peak within the next several years. Solar flares of the magnitude experts are predicting have the potential to cause massive disruptions in power around the globe, similar to one in 1989 that crippled Quebec with a massive blackout affecting six million people. The potential for economic damage has grown exponentially since that time, with the advent of the "wired" world, complex and critically connected international supply chains, and the growth of cloud computing.
Miller said the Emprimus SolidGround system offers an "affordable, fully integrated and automated defense against the effects of such storms for electric utilities and their transmission systems anywhere in the world."
Alternative procedural solutions--such as switching to local gas turbine generation during periods of peak disruptive activity--are extremely expensive, he said, while the SolidGround systems to be manufactured and installed by ABB "will pay for themselves in as little as two years."


text:
What is paravirt_ops?
paravirt_ops (pv-ops for short) is a piece of Linux kernel infrastructure to allow it to run paravirtualized on a hypervisor. It currently supports VMWare's VMI, Rusty's lguest, and most interestingly, Xen.
The infrastructure allows you to compile a single kernel binary which will either boot native on bare hardware (or in hvm mode under Xen), or boot fully paravirtualized in any of the environments you've enabled in the kernel configuration, and lately also as Xen dom0.
It uses various techniques, such as binary patching, to make sure that the performance impact when running on bare hardware is effectively unmeasurable when compared to a non-paravirt_ops kernel.
At present paravirt_ops is available for x86_32, x86_64 and ia64 architectures.
Dom0 means the first guest that Xen boots. It usually (mostly always) is the one that has the driver support. The other guests that are booted (HVM or PV) are called DomU.
Current state in Linux kernel and in distributions
Linux 3.0 (and later) can run as guest (domU) and as host (dom0). All necessary backends (and frontends) are in the upstream kernel. Look in Roadmap in the features section to get an idea what is happening in next kernel releases.
You can also visit the history section on the story of pvops.
Starting with Linux v2.6.37 dom0 support was added and with 3.0 having the necessary backend drivers. Fedora Core 16 and Ubuntu 11.10 ship with the 3.0 kernel (or later) and the user just needs to install the hypervisor:
$yum install xen
$apt-get install xen
TODO: Verify the Ubuntu
Then reboot the machine and select Xen in the GRUB(2) menu. Also consult Category:FAQ and XenCommonProblems
Are there other distributions that have a Xen dom0 kernels available?
Yes. See this wiki page for more information: XenDom0Kernels and XenKernelFeatures
Help! I am having troubles
First of, did you look in Category:FAQ and XenCommonProblems wiki page?
Did not find anything relevant? Was it any of these:
=== I have graphics card (DRM/TTM/KMS/Xorg) related problems with the pv_ops dom0 kernel.. ===
Screen looks like a checker-board? See errors from the Radeon|Nouveau driver? If so please see the XenPVOPSDRM wiki page.
Dom0 console gets all weird and corrupted in the end of the boot process
Is the last line on the console something like Setting console screen modes and fonts ? Then you might want to disable "console-screen.sh" service from starting automatically and it should workaround the problem.
Dom0 console doesn't show any output and remains blank
Unfortunately, a patch that enables the xen dom0 kernel to use the VGA text console didn't made it into initial release of Linux 3.0.0. This patch was merged into Linux 3.1.0 and also to 3.0.2 stable update.
Maybe it is something obvious? How do I make the bootup more verbose?
If you do encounter problems, then getting as much information as possible is very helpful. If the domain crashes very early, before any output appears on the console, then booting with: earlyprintk=xen should provide some useful information. Note that earlyprintk=xen only works for domU/dom0 if you have Xen hypervisor built in debug mode! If you are running a debug build of Xen hypervisor (set "debug = y" in Config.mk in the Xen source tree), then you should get crash dumps on the Xen console. You can view those with "xm dmesg". Also, CTRL+O can be used to send SysRq (not really specific to pv_ops, but can be handy for kernel debugging).
OK, how do I add earlyprintk=xen and all that?
Edit /boot/grub/grub.conf (or /boot/grub2/grub.cfg) and make sure you have a correct grub entry to boot Xen hypervisor with dom0 kernel.
In grub.conf it's a good idea to enable all the logging options for Xen: loglvl=all guest_loglvl=all sync_console console_to_ring and for Linux pv_ops dom0 kernel: earlyprintk=xen debug loglevel=8, and set up a serial console to be able to see and capture the full boot messages from Xen and from dom0 kernel, in the case system doesn't start up properly or crashes.
For the full list of Xen bootup options, look in XenHypervisorBootOptions Here is an example:
title pv_ops dom0 debug (188.8.131.52) with serial console root (hd0,0) kernel /xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all sync_console console_to_ring com1=115200,8n1 console=com1 lapic=debug apic_verbosity=debug apic=debug iommu=off module /vmlinuz-22.214.171.124 ro root=/dev/vg00/lv01 console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10 module /initrd-220.127.116.11.img
==== I got a funky serial console (IPMI/AMT, etc) - Is there more
information available how to debug and troubleshoot using a serial
console? ====
For debugging and testing you should be using a computer with a built-in serial port on the motherboard (com1), or add a PCI serial card if your motherboard lacks a built-in serial port. You can also use SOL (Serial Over Lan) for logging the Xen hypervisor and dom0 kernel messages. Most server-class machines have SOL available through their management processor or IPMI. SOL device looks like a normal serial port for the OS/Xen, but enables you to connect to the serial console over a network, through the management processor.
For more details (and examples) please see XenSerialConsole wiki page.
Nothing is helping! Help!!
Before submitting bugreports to xen-devel mailinglist please read:
- [http://wiki.xensource.com/xenwiki/Linux_30_bugs Linux 3.0 and
further bugs] that we are aware of and working on.
- This wiki page: XenParavirtOpsHelp . It lists all the
information you NEED to provide so the problem can be diagnosed and debugged!
Please mail questions/answers/patches/etc to the [http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel Xen-devel mailing list].
Status updates:
- Jeremy's view of the status of pv_ops dom0 kernel (June 2009):
- Jeremy's roadmap update (August 2009):
- Jeremy's status update (September 2009):
- Presentation by Jeremy about pv_ops dom0 kernel at Xen Summit Asia
2009 (November 2009): http://www.xen.org/files/xensummit_intel09/xensummit-asia-2009-talk.pdf
- Short update (03 December 2009):
- Status update (22 December 2009):
- Status update (03 March 2010):
- Status update from Xen Summit 2010 NA (April 2010):
- Status update from Xen Summit 2011 NA (August 2011):
Removing the Xen Linux kernel upstream delta
Linux distributions are using xen with the Linux kernel but the Linux kernel is typically patched with support for features and enhancements which are not yet upstream. This page documents the delta with the Linux kernel and provides a detailed analysis / status update on each of the patches for each Linux distribution. The purpose of this is page is for Linux distributions to describe each patch being carried forward for their delta, analyze whether or not it can be upstreamed and if so how, see who can or will work on it, and also identify patches which can or should be dropped. The delta for Linux distributions is very similar but SUSE likely caries the largest delta, our end objective should be to distill which delta is common and identify who is working on what. There's quite a bit of patches which likely are no longer needed due to a proper replacement already being upstream or because they are no longer applicable, identifying this also needs to be done.
OpenSUSE pvops status
There is a page dedicated to track the progress of Xen pvops on OpenSUSE
Debian pvops status
Debian really has no delta.
Upstream delta details
Feature | pvops status | current solution | remark |
pci-guestdev | alternative mechanism is documented and exists upstream already | SUSE patch pci-guestdev | PCI passthrough |
mem-hotplug | needs verification | SUSE patch xen-mem-hotplug | Daniel Kiper says he can work on this circa Q4 2015, he's working on EFI now |
multi page ring | Proper upstream solution obsoletes this: indirect descriptor | SUSE patches xen-*multi-page-ring | Can be nuked |
IPV6 autoconf | Luis R. Rodriguez working on it | SUSE patch ipv6-no-autoconf | the work consists of a proper way to address adding
the root bridge block feature, and also fixing bridging code to address this early without userspace, patches are ongoing review upstream |
pvUSB | Jürgen Groß working on it | SUSE patch xen3-auto-xen-drivers.diff | Greg KH welcomes this |
user mode pvclock | Konrad Wilk will do it | SUSE patch xen-x86_64-vread-pvclock | Still being worked on |
expose ballooning limits | needs effort | SUSE patch xen-balloon-max-target | Sysfs parameter needs to be exposed, no takers yet |
retaining tasklet in netback | needs effort | SUSE patch xen-netback-kernel-threads | David Vrabel will inspect how network latency is
impacted without this, some folks have done some testing on this |
add BLKIF_OP_PACKET | needs effort | SUSE patch xen-blkif-op-packet | Luis Rodriguez will work on this |
CD-ROM command forwarding | needs effort | SUSE patch xen-blkfront-cdrom | Luis Rodriguez will work this |
CD-ROM removable media attribute | needs effort | SUSE patch xen-blkback-cdrom | Luis Rodriguez will work on this |
CD-ROM avoid takeover in HVM | needs effort | SUSE patch xen-blkfront-hvm-no-cdrom | Luis Rodriguez will work on this |
DCDBAS address translation | can be nuked | SUSE patch xen-dcdbas | Dell confirmed this is not necessary |
netback multicall for notifications | needs effort | SUSE patch xen-netback-notify-multi | multiple notifications should not be sent one by one,
but via a multicall |
interrupt trigger mode and polarity | needs effort | SUSE patch xen-setup-gsi | Not applicable to netback anymore, can be removed |
fix balloon target driver to
have a logarithmic scale of hitting the 'target' |
needs effort | - | Dan and Jan talked about it and Jan posted a patch
for this some time ago. http://lists.xensource.com/archives/html/xen-devel/2008-04/msg00143.html and http://lists.xensource.com/archives/html/xen-devel/2010-06/msg01076.html |
netfront support skb coalescing | needs effort, no takers yet | - | Borrow the ideas from Netchannel2 to coalesce the
SKB's so that the backend does not have to jump all over the memory and instead can easily fetch the pages in a physical contingous manner. |
microcode update | needs effort | - | Seems done - refer to pvops microcode update page |
MTRR support | needs effort | - | Luis Rodriguez has worked on phasing out MTRR support completely from Linux and replacing MTRR calls for PAT calls. Most work was merged in v4.2, there are a few more pending patches to be merged. There are a few corner cases: firmware cannot be prevented from using MTRR, and even PAT x86 kernel code uses mtrr_type_lookup(), these two items need some last review. As far as firmware is concerned this can happen when a UEFI call is made or an SMI happens. Jan notes that we can emulate MTRRs by using PAT, but acknowledges the issue with SMI. Toshi also note that MTRRs are also set up by the platform so that a system won't hit a machine check when an OS bug leads access with a wrong cache type. A Machine check is hard to analyze and can be seen as a hardware bug by platform customers. For details refer to: this RIP MTRR thread |
Device hotplug (MODULE_ALIAS) | needs effort | - | Konrad sent patch for hotplug upstream |
Suspend event channel
support for faster checkpointing in Remus FT |
needs effort | - | Ian poked remus folks, remus folks should fix this otherwise |
expected to be dead (under
Xen) code cannot be easily verified to indeed be dead |
needs effort | - | Another better term: paravirt yielding code, refer to Xen pv_ops yielding section for more details and status. |
old hypervisor support | needs effort | - | running the pvops kernel on top of a pre-4.0.1
hypervisor (especially as Dom0) might not work. This should work. We should get folks to test this and if issues found file a bug report for it. |
blktap driver (what about blktap3?) | needs effort | - | Performance and support of all possible blktap
configurations via qemu/qdisk is to be verified. |
oprofile support | Boris Ostrovsky is working on it | - | - |
Kernel | Features added |
2.6.26 |
2.6.27 |
2.6.28 |
2.6.29 |
2.6.30 |
2.6.31 |
2.6.32 |
2.6.33 |
2.6.34 |
2.6.35 |
2.6.36 |
2.6.37 |
2.6.38 |
2.6.39 |
3.0 |
3.1 |
3.2 |
3.3 |
3.4 |
3.5 |
3.6 |
3.7 |
3.8 |
3.9 |
3.11 |
3.12 |
3.14 |
3.15 |
3.17 |
3.18 |
3.19 |
4.0 |
4.3 |
I want to build the Xen/paravirt_ops components myself
If you are using a 3.0 kernel or later, you already have it working and there is no need to compile a new kernel - unless you feel adventurous.
The top level view is that you need to:
- Get a current kernel. The latest kernel.org
kernel is generally a good choice. Or you can use the development version.
- Configure as normal; you can start with your current .config file or
use make defconfig.
- Then configure .config Xen options
- Build the kernel
- Update #configure_modules modules (optional)
- Build the Xen hypervisor
- Update services (optional)
- Update GRUB1 or GRUB2
- Reboot and run it
- Troubleshoot if necessary
Getting the mainline Linux kernel
In order to get a proper Xen mainline kernel please check: Mainline_Linux_Kernel_Configs .
Build Xen
Xen requirements for using pv_ops dom0 kernel
Xen hypervisor and tools need to have support for pv_ops dom0 kernels. In general it means:
- The ability for the Xen hypervisor to load and boot bzImage pv_ops
dom0 kernel.
- The ability for the Xen tools to use the sysfs memory ballooning
support provided by pv_ops dom0 kernel.
- Current recommended 2.6.32.x version of pvops dom0 kernel requires
new IOAPIC setup hypercall from Xen hypervisor. This means you need to have at least Xen version 4.0.1.
Using older Xen versions is known to be problematic, for example Xen 4.0.0 libraries have problems with recent 2.6.32.x kernels, making xend fail to start due to evtchn/gntdev device node creation issues. Using Xen 3.4.2 or older won't work at all, since old hypervisor versions lack the new required IOAPIC setup hypercall and boot will fail with IRQ related issues.
It's recommended to run the latest Xen 4.0.x version, at least Xen 4.0.1.
=== Which kernel image to boot as dom0 kernel from your custom built kernel source tree? ===
If you have Xen hypervisor with bzImage dom0 kernel support, ie. xen 3.4 or later version, use "linux-2.6-xen/arch/x86/boot/bzImage" as your dom0 kernel (exactly the same kernel image you use for baremetal Linux).
If you have Xen hypervisor without bzImage dom0 kernel support, ie. any official Xen release up to at least Xen 3.3.1, or most of the Xen versions shipped with Linux distributions (before 2009-03), use "linux-2.6-xen/vmlinux" as your dom0 kernel. (Note that "vmlinux" is huge, so you can also gzip it, if you want to make it a bit smaller).
Also read the previous paragraphs for other requirements.
Get your sources from the repository, something like this can be used but the exact path will change:
$ cd /usr/src $ git clone http://xenbits.xenproject.org/xen.git $ cd xen $ sudo make xen $ sudo make tools $ sudo make install-xen $ sudo make install-tools
If you encounter any error NOT related to deps report them to
xen-devel, if you need help compiling you will find help in xen-users.
At the end in dist folder you will find xen.gz follow that symlink to
your real image.
Update services
The Ubuntu way to register a service is this:
$ sudo update-rc.d xendomains defaults 21 20
For Red Hat use chkconfig
For RC16 use systemctl:
$ sudo systemctl start xenstored.service
Other System Updates
The XENFS and XEN_COMPAT_XENFS config options are needed for /proc/xen support. If CONFIG_XEN_DEV_EVTCHN is compiled as a module, make sure to load the xen-evtchn.ko module or xend will not start.
You might also need to add a line to /etc/fstab. Xen 3.4.2 and newer automatically mount /proc/xen when /etc/init.d/xend is started, so no need to add xenfs mount entry to /etc/fstab on those systems:
none /proc/xen xenfs defaults 0 0
GRUB1 and GRUB2 (Booting)
Working grub.conf example with VGA text console:
title Xen 4.0, dom0 Linux kernel 188.8.131.52 root (hd0,0) kernel /boot/xen-4.0.gz dom0_mem=512M module /boot/vmlinuz-126.96.36.199 root=/dev/sda1 ro nomodeset module /boot/initrd.img-220.127.116.11
NOTE! You need to give correct root= parameter, ie. replace /dev/sda1
with your actual root device. Check your earlier grub kernel entries
for the correct option. Also you need to have the "nomodeset" option
for the time being. Check your earlier grub kernel entries for the
correct option. Its good to look at your initial kernel boot
configuration and use it as closely as possible, then modify the
40_custom file to suite your xen needs. Keep in mind that your initial
kernel might not use the /dev/sdX it can use the UUID notation, well
use it also.
Here is the content extracted from grub.cfg for a Ubuntu/Fedora Core kernel using grub2:
menuentry 'GNU/Linux, with Linux 2.6.38-8-generic' --class gnu-linux --class gnu --class os { recordfail set gfxpayload=$linux_gfx_mode insmod part_msdos insmod ext2 set root='(/dev/sda,msdos2)' search --no-floppy --fs-uuid --set=root 016e7c8a-4bdd-4873-92dd-d71171a49d6d linux /boot/vmlinuz-2.6.38-8-generic root=UUID=016e7c8a-4bdd-4873-92dd-d71171a49d6d ro quiet splash vt.handoff=7 initrd /boot/initrd.img-2.6.38-8-generic }
Compare them and you will see the similarties, on this particular system the boot device is located in /dev/sda2 yet if used in grub the system will not boot. Insted GRUB uses the UUID schema to detect the devices, that way the root argument can be passed to the linux kernel image.
Here is the contents of 40_customCompare them and you will see the similarities, on this particular system the boot device is located in /dev/sda2 yet if used in grub the system will not boot instead GRUB searches for the correct UUID and its is used in the kernel image, this can be easily detected when looking at the original ubuntu boot entry..
Here is the contents of 40_custom:
#! /sbin/sh exec tail -n +3 $0 # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. menuentry 'GNU/Linux, with Linux 18.104.22.168-pv' --class gnu-linux --class gnu --class os { recordfail insmod part_msdos insmod ext2 search --no-floppy --fs-uuid --set=root 016e7c8a-4bdd-4873-92dd-d71171a49d6d set root='(/dev/sda,msdos2)' search --no-floppy --fs-uuid --set=root 016e7c8a-4bdd-4873-92dd-d71171a49d6d multiboot /boot/xen-4.2-unstable.gz module /boot/vmlinuz-220.127.116.11-pv placeholder root=UUID=016e7c8a-4bdd-4873-92dd-d71171a49d6d dom0_mem=1024 console=tty quiet splash vt.handoff=7 module /boot/initrd.img-184.108.40.206-pv }
Xen MUST be started using multiboot this will point to the image created when xen was compiles, the next module line is the linux kernel built from the kernel repository, this can be either jeremy or kernel.org, after the image you append placeholder or dummy=dummy because grub will strip the first argument from the module line. The last line is the ram drive created after the kernel.
Here is another working example grub.conf with serial console output (good for debugging since you can easily log the full kernel boot messages even if it crashes):
title pv_ops dom0 (22.214.171.124) with serial console root (hd0,0) kernel /xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all sync_console console_to_ring com1=19200,8n1 console=com1 module /vmlinuz-18.104.22.168 ro root=/dev/vg00/lv01 console=hvc0 earlyprintk=xen nomodeset module /initrd-126.96.36.199.img
For more information about using a serial console with Xen please check the XenSerialConsole wiki page.
Booting DomU guests
If you've built a modular kernel, then all the modules will be the same either way. Some aspects of the kernel configuration have changed:
- The console is now /dev/hvc0, so put "console=hvc0" on the kernel command line
- Disk devices are always /dev/xvdX. If you want to dual-boot a
system on both Xen and native, then it's best that use use lvm, LABEL or UUID to refer to your filesystems in your /etc/fstab.
=== Troubleshooting, what to do if the custom built pv_ops dom0 kernel doesn't work/boot? ===
Make sure you read the ##troubleshooting section. It has tons of good suggestions. Also consult the XenCommonProblems or Category:FAQ pages.
Historical contents
Timeline of pvops
Xen pv_ops (domU) support has been in mainline Linux since 2.6.23 (though it is probably first usable in 2.6.24), and is the basis of all on-going Linux/Xen development (the old Xenlinux patches officially ended with 2.6.18.x-xen, though various distros have their own forward-ports of them). Latest Linux kernels (2.6.27 and newer) are good for domU use. Starting from Fedora 9 all the new Fedora distribution versions include pv_ops based Xen domU kernel. Ubuntu 10.04 ("Lucid Lynx") and Debian 6.0 ("Squeeze") also includes Xen PV domU kernel. Red Hat Enterprise Linux 6.0 also includes pvops based Xen domU kernel.
[This is obsolete, but it might be worth reading] Lots of work has been done to close the feature gaps compared to 2.6.18-xen. Many of these have been done - but there are still some left.
[Done] The Xen device model is more or less unchanged in the pv-ops kernel. Converting a driver from the xen-unstable or 2.6.18-xen tree should mostly be a matter of getting it to compile. There have been changes in the Linux device model between 2.6.18 and 2.6.26, so converting a driver will mostly be a matter of forward-porting to the new kernel, rather than any Xen specific issues.
CPU hotplug
[Done] All the mechanism should already be in place to support CPU hotplug; it should just be a matter of making it work. [2011-07-30]: It works with 3.0.
Device hotplug
[Done] In principle this is already implemented and should work. I'm not sure, however, that it's all plumbed through properly, so that hot-adding a device generates the appropriate udev events to cause devices to appear.
Device unplug/module unload
[Done] The 2.6.18-xen patches don't really support device unplug (and driver module unload), mainly because of the difficulties in dealing with granted pages. This should be fixed in the pvops kernel. The main thing to implement is to make sure that on driver termination, rather than freeing granted pages back into the kernel heap, they should be added to a list; that list is polled by a kernel thread which periodically tries to ungrant the pages and return them to the kernel heap if successful.
Development of PVOOPS in Ingo's tree
[This is obsolete, but it might be worth reading]
All x86 Xen/pv-ops changes queued for upstream Linus are in Ingo Molnar's [http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=summary tip.git] tree. You can get general information about fetching and using this tree in his [http://people.redhat.com/mingo/tip.git/README README]. The [http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=shortlog;h=x86/xen x86/xen] topic branch contains most of the Xen-specific work, though changes in other branches may be necessary too. Using the [http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=shortlog;h=auto-latest auto-latest] branch is the merged product of all the other topic branches.
[This is obsolete, but it might be worth reading]
Xen/paravirt_ops has not had wide use or testing, so any testing you do is extremely valuable. If you have an existing Xen configuration, then updating the kernel to a current pv-ops and trying to use it as you usually would, then any feedback on how well that works (success or failure) would be very interesting. In particular, information about:
- performance: better/worse/same?
- bugs: outright crash, or something just not right?
- missing features: what can't you live without?
Linux distribution support for pv_ops dom0 kernels
[This is obsolete, but it might be worth reading]
Fedora: Fedora 14 includes Xen 4.0.1 hypervisor and is able to run pvops dom0 kernel out-of-the-box. Fedora 14 does not ship with a dom0 capable kernel in the default distribution, but xendom0 kernel rpms are available from developer repositories. Fedora 13 and earlier versions ship with Xen 3.4.x and are not recommended for pvops dom0 usage, unless you update the Xen hypervisor to 4.0.x version. See this tutorial for more help: Fedora13Xen4Tutorial , and also check the Fedora dom0 wiki page: http://fedoraproject.org/wiki/Features/XenPvopsDom0 .
Debian: Debian 6.0 ("Squeeze") includes Xen 4.0.x hypervisor, and also dom0 capable kernel based on the pvops tree.
Other distributions: When using pvops dom0 kernel 2.6.32 or newer you need to have Xen hypervisor 4.0.1 or newer version.
2.6.32 and earlier kernels
[This is obsolete, but it might be worth reading] The kernel build process will build two kernel images: arch/x86/boot/bzImage and vmlinux. They are two forms of the same kernel, and are functionally identical. However, older versions of the Xen tools stack lack support loading bzImage files (pre-Xen 3.2), so you must use the vmlinux form of the kernel (gzipped, if you prefer).
Config files for 2.6.32
Example .config files:
64bit x86_64 (branch: xen/stable-2.6.32.x):
- 220.127.116.11: http://pasik.reaktio.net/xen/kernel-config/config-126.96.36.199-pvops-dom0-xen-stable-x86_64
- 184.108.40.206: http://pasik.reaktio.net/xen/kernel-config/config-126.96.36.199-pvops-dom0-xen-stable-x86_64
- 22.214.171.124: http://pasik.reaktio.net/xen/kernel-config/config-188.8.131.52-pvops-dom0-xen-stable-x86_64
- 18.104.22.168: http://pasik.reaktio.net/xen/kernel-config/config-126.96.36.199-pvops-dom0-xen-stable-x86_64
- 184.108.40.206: http://pasik.reaktio.net/xen/kernel-config/config-22.214.171.124-pvops-dom0-xen-stable-x86_64
- 22.214.171.124: http://pasik.reaktio.net/xen/kernel-config/config-184.108.40.206-pvops-dom0-xen-stable-x86_64
- 184.108.40.206: http://pasik.reaktio.net/xen/kernel-config/config-18.104.22.168-pvops-dom0-xen-stable-x86_64
- 188.8.131.52: http://pasik.reaktio.net/xen/kernel-config/config-184.108.40.206-pvops-dom0-xen-stable-x86_64
32bit PAE:
- xen/stable-2.6.31.x (126.96.36.199):
- xen/stable-2.6.32.x (184.108.40.206):
- xen/stable-2.6.32.x (22.214.171.124):
Those kernel configs are based on Fedora 11/12 kernel configuration, with some modifications. They've been tested to work on multiple systems. Note that these .config files have various debugging options enabled which will decrease performance so don't use these .config files for performance testing!


text:
McDOUGALL, JOHN, businessman; b. 25 July 1805 at Coldstream, Scotland, son of John McDougal and Janet Wilson; d. 21 Feb. 1870 in the parish of Vieilles-Forges (Saint-Michel-des-Forges), near Trois-Rivières, Que.
Because precise information is not available, the McDougall families of Quebec are often confused. This confusion is all the more natural because three McDougall families came from Berwickshire, Scotland, to Canada in the 19th century. The John McDougall family of Trois-Rivières, which won fame at the Saint-Maurice and L'Islet ironworks under the name of John McDougall and Sons, was not the John McDougall family that owned the Montreal company "Caledonia Foundry" and bought the Saint-Pie-de-Guire ironworks in 1874; George McDougall, who from 1876 to 1879 operated the Saint-Maurice ironworks in partnership with Alexander Mills McDougall under the name of G. and A. McDougall, was a member of yet a third branch. Apparently there was no relationship between the first McDougall family and the second, but the first and third were linked by marriage. What the three families had in common – which helps to jumble the whole issue – is the fact that all were to a varying extent involved in the metallurgical industry in Quebec, and that the theatre of their operations was bounded by the triangle Trois-Rivières – Saint-Pie-de-Guire – Drummondville.
John McDougall, founder of the Trois-Rivières branch of McDougalls, had married Margaret Purvis before he crossed the Atlantic in the 1830s; he is believed to have arrived at Trois-Rivières in 1833. Almost nothing is known of his activities during the next 20 years, except that he may have worked at a distillery and brewery. At the time he became mayor of Trois-Rivières (from 1855 to 1857), John McDougall had for several years owned a general store and a number of plots of land; he was also president of the Three Rivers Gas Company, and he was described as a "steamboat agent" in a protest lodged against him by lumberman William Price. Price complained that the proceedings McDougall had instituted against him on 6 Aug. 1855 in the Circuit Court of Trois-Rivières to recover the sum of £36 4s. 9 1/2d. were injurious to his reputation. This grievance of William Price, if it were known to be justified, might shed light on McDougall's character.
In the provincial elections of 4 and 5 Jan. 1858 John McDougall ran against William McDonell Dawson in the county of Trois-Rivières. In his electoral address Dawson associated himself with the "Liberal party of reform and progress" of the former team of Robert Baldwin* and Louis-Hippolyte La Fontaine whose principles were now adopted by the "moderate party of the day," while McDougall, without propaganda and fanfare, blandly proposed to give "[his] support, in parliament, to the 'Moderate party.'" Despite the subtlety of these distinctions, Dawson emerged victorious from an election in which there were violent confrontations between the supporters of the two camps. McDougall protested Dawson's election. He thus added fuel to a newspaper quarrel between the readers of L'Ère nouvelle (pro-Dawson) and L'Écho du St-Maurice (pro-McDougall), each of whom denounced the reprehensible attitude of the opponent. During the ensuing lawsuit the defendant produced testimony by François Brousseau that John McDougall had attacked and beaten him with a walking-stick in the Saint-Louis district polling-booth. Although McDougall did not win the case, it is difficult to assess his temperament on the basis of this election brawl. Similarly the action brought by Marie Hamel on 28 Jan. 1858, a few weeks after the election, accusing McDougall of having raped her on 29 Dec. 1857, is hardly more illuminating. The plaintiff and her husband, Louis Bertrand, were former employees who had been dismissed by the accused. At the time of the inquiry, the judges concluded that Marie Hamel's complaint did not even warrant proceedings at law. Was McDougall a victim of partisan manoeuvres to destroy his reputation? The electioneering customs of the time lead to this conclusion.
If McDougall's short incursion into politics was a failure, his career as a businessman presents quite a different picture. In addition to the business activities already mentioned, McDougall was a member by 1858 of the board of directors of the North Shore Railway Company; a promotional notice of this company introduced him as a director authorized "to receive the payments required on the shares of the said company that were owned by shareholders living in the district of Trois-Rivières, and to give receipts therefor." In the absence of exact data in the documentation available, it is impossible to determine McDougall's role in this railroad company, the part he played in the Three Rivers Gas Company or as steamboat agent, or indeed the length of time he held these positions. We do not even know exactly the nature of his business activity although he is listed in notarial documents as merchant, independant grocer, "general merchant," and later iron merchant.
During the 1850s McDougall acquired some land at Trois-Rivières; he owned a mortgage on four lots in the township of Arthabaska; and he had an "immense estate" called Moulin Rouge, at Sainte-Anne-d'-Yamachiche (Yamachiche) by 1857, when he received four lots and acquired the property of the Johnston heirs. It would be logical to suppose he obtained this land so that he could either supply his store with foodstuffs or carry on trading in timber, unless he was simply engaged in land speculation. What is certain is that when he offered to purchase the Saint-Maurice and L'Islet ironworks he had capital at his disposal.
The whole story of the Saint-Maurice ironworks, from its beginning in the 1730s until its demise in 1883, was marked by periods of depression and growth, stops and starts. In 1861, two years after the partners Andrew Stuart* and John R. Porter went bankrupt, the government, as mortgage holder, seized the establishment. In the following year Onésime Héroux bought it for $7,000. The metallurgical industry in the Saint-Maurice region was probably threatened when the Radnor ironworks were built in the future village of Fermont (adjoining the parish of Saint-Maurice) by Auguste Larue, George Benson Hall*, and Joseph-Édouard Turcotte in 1854 and the L'Islet ironworks were established beside the stream at L'Islet (Ilet) on the west bank of the Rivière Saint-Maurice by Dupuis, Robichon et Compagnie in 1856. John McDougall was to turn this situation to his advantage by purchasing the Saint-Maurice and L'Islet ironworks.
The process by which he acquired these undertakings illustrates his business sense. On 15 Dec. 1862 he both initialled a contract of sale with the former owners of the Saint-Maurice ironworks (Porter and Stuart) and concluded a deal with the owner of the L'Islet ironworks. Through notary Louis-Zéphirin Duval, John Porter and Company sold McDougall the equipment it still possessed at the Saint-Maurice ironworks and in the neighbourhood. Of the $1,000 cost of this transaction, McDougall immediately paid $300 representing the value of the iron mine and of the moulds for heavy casting. John McDougall then signed with Louis Dupuis, the sole owner of the L'Islet ironworks since March 1862, an agreement by which the latter undertook not only to deliver to McDougall before 15 Nov. 1863 various types of cast-iron stoves, cauldrons, axle-boxes, moulds for pipes, and "250 barrels of pig-iron," but also not to supply these kinds of articles to other merchants.
A year later, on 16 April 1863, McDougall acquired the L'Islet ironworks from Dupuis, who apparently preferred to sell rather than to declare bankruptcy. The land sold consisted of a piece three arpents wide by 25 deep, in the north-east range of the Saint-Félix concession in the parish of Notre-Dame-de-Mont-Carmel, on which the L'Islet ironworks had been set up; these encompassed "several edifices, a furnace, sheds, a casting-shop, houses, stables, cowsheds, and other outbuildings." McDougall also bought four other pieces of land in the Saint-Félix concession, as well as "all the items and articles necessary for the operation of the ironworks." The figure for this transaction was £2,000 at current rates or $8,000, according to the contract; however, it was stipulated that McDougall would pay this sum by undertaking to discharge the numerous mortgages encumbering the property of Louis Dupuis. The mortgages in question and the interest accruing thereon were apportioned as follows: $805.30 to Louis-Charles Boucher de Niverville, $808.31 to Moses E. Hart, $541.87 to John Houliston, $127.75 to Luc Précourt, and $5,694.08 to Amable Prévost: a total of $7,977.31. In the end Dupuis received only $22.69. Furthermore, as a guaranty of the act of sale, which in fact was a statement of bankruptcy, the "caster" Louis Dupuis, who could not write, had to mortgage his property at Trois-Rivières for $1,200 in favour of McDougall.
McDougall had had the equipment of John Porter and Company in his possession since December 1862 and on 27 April 1863 assumed control of the Saint-Maurice ironworks, which Onésime Héroux sold to him for $4,300. A cash payment of $1,075 was made to Héroux immediately, and McDougall undertook to pay the balance of $3,225 to the government, in equal annual instalments until November 1865, to discharge its mortgage on the ironworks. McDougall did indeed pay off this mortgage, interest included, on 8 Feb. 1866, according to the acceptance of satisfaction of mortgage signed by Marie Héroux, the former wife of Onésime Héroux, on 26 April 1867. McDougall's new domain included "houses, barns, sheds, cowsheds, stables, coal storage space, a flour mill, a large furnace, a foundry, a casting-shop, forges, and other outbuildings." However, the seller, a merchant of Saint-Barnabé, did not surrender his property completely; he kept a portion of the land adjoining the stream on which were "a large brick shed and a sawmill."
Research has thus far provided scant data on which to base an estimate of production at the Saint-Maurice ironworks. It seems that in 1865 they produced about 90 tons per week, and that the annual average was some millions of pounds. Apparently in 1870, with about a hundred men employed, half of them at the foundry, an output of about four tons a day was obtained. We know nothing of the conditions under which these employees worked, or of their salaries, except that according to Dollard Dubé they were paid either "with vouchers exchangeable at the store" or in money.
The growth and expansion of McDougall's economic activities, and his determination to involve his sons, led to the formation of a partnership on 26 April 1867. The firm of John McDougall and Sons took the form of a partnership in two sections. The first, relating only to the general store at Trois-Rivières, established the parity of each partner (John McDougall Sr, John McDougall Jr, and James McDougall) in profit-sharing; at the management level, the two sons were to give all their time to the store, while the father would free himself from it completely in order to devote his energies more effectively to administration of the ironworks. The second section, relating to the Saint-Maurice and L'Islet ironworks, included the eight sons; each owned an eighteenth of the shares, except for William who held one-ninth; the father retained half of all the shares. This proportion applied to both profits and losses.
The place of residence of each of the partners in 1867 was indicative of both the level of their participation and the importance of the Saint-Maurice ironworks: John Sr, Robert, George, and David lived at the Saint-Maurice ironworks, Alexander Mills lived at the L'Islet ironworks, and John Jr, James (who for a time was to be a banker), William, a lawyer, and Thomas resided at Trois-Rivières. In 1869 they were still living in the same places except for the youngest, Thomas, who was now in Montreal; in 1873 he married the oldest daughter of George Baptist*.
Although the distribution of shares and activities within John McDougall and Sons was necessary for accounting purposes it had in reality an artificial quality, for the firm's metallurgical sector and its commercial sector (the general store) overlapped. In fact, one transformed raw material and the other sold the finished product. The most demanding activity was undoubtedly the ironworks. Not only was it necessary to oversee the various operations, but the blast furnaces had to be supplied with charcoal. This fuel, needed for the reduction of the ore, came from numerous surface deposits of "hydrated iron oxide," and was provided by the surrounding forest. However, one had to possess the wooded areas, or take steps to purchase the timber cuts of the small local landowners. Thus, when John McDougall and Sons was founded, it owned 38 pieces of land in the parish of Mont-Carmel, specifically, in the concessions of Saint-Félix, Saint-Louis, Saint-Michel, Saint-Mathieu, and Saint-Flavien; to these were added 14 sections in the fief of Saint-Étienne, one in the fourth concession of Shawinigan Township, and the former estate of Thomas Burn at Mont-Carmel. The policy of purchasing land reached a culmination on 22 Nov. 1867, when the commissioner of crown lands sold McDougall 62 lots in the Cap-de-la-Madeleine seigneury, at a unit price of $24.00. These lots, each 60 acres in size, were located in the concessions of Saint-Louis, Saint-Michel, Saint-Mathieu, and Saint-Flavien.
The above inventory, although not exhaustive, seems to reveal the dynamic drive of John McDougall and Sons. In the absence of precise data on the production of the ironworks, the store sales, and the balance-sheets, the analysis cannot be taken any further. It is possible, of course, that, in addition to the motives listed earlier, the 1867 deed of partnership was dictated by a need to enlarge the credit margin. At the time the company's debts stood at $11,500, and they were still increasing in 1869. The interesting point is that its creditors were closely or distantly related to the McDougall family. Mrs Janet Purvis, John Campbell's widow, to whom the firm owed $2,500, was probably a relative of Margaret Purvis, the wife of John McDougall; Anne Paterson, widow of Quebec merchant John Paterson, to whom they owed $9,000, was the eldest daughter of John McDougall.
The Saint-Maurice McDougall family included, in addition to the father and mother, eight boys and three girls. The latter were: Anne, who married John Paterson in 1847; Janet Wilson, who married Montreal accountant Robert Nilson in 1871; and Margaret, who became the wife of Montreal merchant Robert Linton in 1867. The boys distinguished themselves in business, politics, or one of the professions. All the children survived their father, who died on 21 Feb. 1870, and whose burial was the occasion for a procession of more than "fifty vehicles [. . . that followed] the hearse from the Vieilles Forges du Saint-Maurice" to Trois-Rivières.
After the death of its founder, the firm of John McDougall and Sons entered an extremely trying phase during which the sons experienced serious difficulties in keeping their metallurgical operations profitable. Numerous factors, including the gradual exhaustion of iron ore and the effects of the international banking crisis of 1873–79, explain the decline. Nevertheless, John McDougall and Sons did not appear to suffer from the restricted credit characterizing banking relations in Quebec during this crisis: from 30 June to 27 Oct. 1875 the Trois-Rivières branch of the Quebec Bank gave them a credit of $80,500. When they were unable to meet payments, either as a result of the poor productivity of their ironworks or because they were selling at a loss, they were obliged to mortgage the Saint-Maurice and L'Islet ironworks on 8 Nov. 1875; thus covered, the bank extended the date of reimbursement of the $80,500 debt by four years.
Subsequently, on 8 Dec. 1876, John McDougall Jr and his brother Robert relinquished their shares in the Saint-Maurice ironworks to a member of the third McDougall family, George McDougall. The latter, in partnership with Alexander Mills McDougall under the name of G. and A. McDougall, presided over the destinies of the Saint-Maurice ironworks until 1879, at which time Alexander Mills, who had closed the L'Islet ironworks the preceding year, sold his investments and left the Saint-Maurice region. Under the sole direction of George McDougall, the Saint-Maurice ironworks continued to function at a slow pace from 1879 to 1883, when a new international monetary crisis closed it down for good.
AJTR, Greffe de la paix, dénonciation et plainte de Marie Hamel, 28 janv. 1865; déposition de François Brousseau, 1er févr. 1858; Registre d'état civil, St Andrew's Presbyterian Church, 1876–89. ANQ-TR, État civil, Presbytériens, St Andrew's Church, 1846–75; Greffe de R.-Honoré Dufresne, 22 nov. 1867; Greffe de Petrus Hubert, 17 mars 1857, 8 janv., 26 févr. 1858, 5 nov. 1859, 15 déc. 1862, 16 avril 1863, 26 avril 1867, 6 janv. 1868, 3 mai 1869, 8 nov. 1875; Greffe de F.-L. Lottinville, 14 mars, 14 mai 1850, 23 mars 1854, 2 mars, 22 sept. 1855. Le Constitutionnel (Trois-Rivières), 28 févr., 23 mai 1870. L'Ère nouvelle (Trois-rivières), 10, 14 déc. 1857; 14 janv., 15, 22, 25 févr., 5 avril 1858. Cyclopaedia of Canadian biog. (Rose, 1886). Brouillette, Le développement industriel. Ernestine Charland-Rajotte, Drummondville, 150 ans de vie quotidienne au cœur du Québec (Drummondville, Qué., 1972). Une page d'histoire de Trois-Rivières et la région, magnifique essor industriel (Trois-Rivières, 1954). Albert Tessier, Les forges Saint-Maurice, 1729–1883 (Trois-Rivières, 1952); Les Trois-Rivières: quatre siècles d'histoire, 1535–1935 (2e éd., s.l., 1935). "La famille McDougall," BRH, XXXIII (1927), 401–3. Daniel McDougall, "The final half-century of charcoal iron production in Quebec, 1861–1911," Canadian Mining Journal (Gardenvale, Que.), 92 (1971), no. 8, 30–34.
© 1976–2024 University of Toronto/Université Laval
Cite This Article
Georges Massey, "McDOUGALL, JOHN (1805-70)," in Dictionary of Canadian Biography, vol. 9, University of Toronto/Université Laval, 2003–, accessed March 4, 2024, http://www.biographi.ca/en/bio/mcdougall_john_1805_70_9E.html.
The citation above shows the format for footnotes and endnotes according to the Chicago manual of style (16th edition). Information to be used in other citation formats:
Permalink: | http://www.biographi.ca/en/bio/mcdougall_john_1805_70_9E.html |
Author of Article: | Georges Massey |
Title of Article: | McDOUGALL, JOHN (1805-70) |
Publication Name: | Dictionary of Canadian Biography, vol. 9 |
Publisher: | University of Toronto/Université Laval |
Year of publication: | 1976 |
Year of revision: | 1976 |
Access Date: | March 4, 2024 |


text:
Chapter 18 of Vayikra (Leviticus) mostly deals with various forbidden relationships, but without specifying the individual punishments for transgressing them (just a collective warning to the nation that tolerating such behaviors will cause them to be "vomited out of the Land," and a brief mention of kareis for the perpetrators).
In ch. 20 the list is repeated (with variations in the ordering of the various relatives), and with penalties specified for each one - some court-imposed punishments, others Divine ones.
In between, in ch. 19, is a miscellany of mitzvos (Rashi to 19:2, citing Sifra, characterizes it as a section on which "most of the fundamental teachings of the Torah are dependent"), starting with "Kedoshim tihyu" - "You shall be holy" (which Rashi explains as meaning: "Separate yourselves from sexual immorality and from sin," and Ramban as saying: "Sanctify yourself within the permissible" - i.e., don't indulge your appetites just because the food or whatever is kosher).
Why this order? I'd think that chs. 18 and 20 should be juxtaposed, with ch. 19 either preceding or following them.


text:
Huzur gave a discourse on Salat in his Friday Sermon today. Huzur cited verse 46 of Surah Al Ankabut. The translation reads:
"Recite that which has been revealed to thee of the Book, and observe Prayer. Surely, Prayer restrains one from indecency and manifest evil, and remembrance of Allah is the greatest virtue. And Allah knows what you do." (29:46)
Huzur said we are indeed most fortunate to have accepted and believed in the true and ardent devotee of the Holy Prophet (peace and blessings of Allah be on him) that is, the Promised Messiah (on whom be peace). However, this acceptance puts huge obligations on us to make endeavours to spiritually attain the station that was granted to the Companions of the Holy Prophet (peace and blessings of Allah be on him). If this is not our objective then we have not fully understood the purpose of the advent of the Promised Messiah (on whom be peace). Huzur said each individual of the Community should realise that he/she will be truly worthy of the Divine promises made to the Promised Messiah (on whom be peace) with regards his community when he/she will try and purify themselves. The Promised Messiah (on whom be peace) said that the use of the plural aakhareen (the latter-one) in verse 4 of Surah Al Jummah signifies that the one to come in the latter-days will not be alone, that he will be given a community who will attain the spiritual station of the earlier ones.
Huzur said Salat is the primary source of purifying the self, as the verse recited at the beginning signifies. The verse speaks of reciting the word of Allah, to spread it to others and to observe Salat, for Salat, when it is observed with its due requisites is a source of purifying the self. Huzur said it is the responsibility of each Ahmadi to focus on observing Salat, to observe each Salat at its prescribed time. The five daily prayers are the milestone from where the spiritual journey begins; it is the seed that has the potential of spiritual growth. If one is negligent with Salat, virtues are suppressed in the manner that weeds suppress the growth of a field. It is our task to make the roots of this worship so strong that it safeguards us from all evil. Indeed it is for us to observe Salat and establish it first, it is as a consequence of observing it sincerely that Salat safeguards us in return. Each Ahmadi should self-examine and see if we are fulfilling our dues to be abids (worshipper of Allah) as well as conducting ourselves with high morals and courtesy with people.
Only then will we be among those who fulfil the purpose of the advent of the Promised Messiah (on whom be peace). The Promised Messiah (on whom be peace) said that Salat alone is the virtue that dispels satanic weaknesses and that Satan wishes man to stay away from Salat because he knows it is Salat that would purify man. Fasting [during Ramadan] comes once every year and Zakat is for the well-off to observe, however, Salat is for everyone and should be observed, seeking Allahs bounties for the treasures of Allah are always brimful all that is needed is the certainty that one is standing before an All-hearing, All-Seeing Being Who can provide in a spilt second if He so wishes. Just as a soldier would never surrender his best weapon in a battlefield Salat is the most excellent weapon for a believer and a believer should safeguard it at all costs.
Citing verse 239 of Surah Al Baqarah (2:239)
"Watch over prayers, and the middle Prayer, and stand before Allah submissively."
Huzur said various commentators have interpreted the term 'middle prayer' differently; it is an instruction in principle and 'middle prayer' can be applied to different people in accordance to their leanings towards worldly matters or their laziness that may make them negligent towards observing Salat. It can be the specific time for different people during a day when their attention diverts elsewhere by satanic enticements. If we can overcome this then consider that we safeguard our Salat and in turn Salat will indeed safeguard us. It is a continuous effort. This indeed is the condition of true obedience and one that brings about purification.
It is incumbent on each Ahmadi Muslim to honour the pledge they have taken after taking their bai'at - to demonstrate perfect obedience and endeavour to tread the path which gives the strength to contend with Satan, which strengthens the core of one's belief and one experiences one's prayers meeting acceptance in the heavens.
Huzur said sometimes two Salats are combined, at times it is due to a valid reason but at other times people simply make it a norm. Huzur said Allah has indeed fixed a time for each Salat as verse 79 of Surah Bani Israel states:
Observe Prayer at the declining and paling of the sun on to the darkness of the night, and the recitation of the Qur'an in Prayer at dawn. Verily, the recitation of the Qur'an at dawn is specially acceptable to God.(17:79)
Huzur read a most eloquent extract from the noble writings of the Promised Messiah (on whom be peace) elucidating the significance of the timings of the five daily Prayers. The Promised Messiah (on whom be peace) explains it with reference to a worldly phase man goes through. The time of Zuhr, when the sun, having reached its zenith has begun its decline, is likened to a time in a persons life when he is faced with difficulty and is in a state of meekness, is anxious and in despair and makes all kinds of attempts in his restlessness, at this juncture we should reflect on our spiritual state and seek Gods help. Then, as the persons anxiety is changed into the reality of perhaps receiving a warrant or a court summon and subsequently endures cross-examination to prove his innocence is a time likened to time of Asr; this is the time when a person should remember Allah and pray for protection from making mistakes and seek forgiveness. The scenario then changes to the court passing judgment against the person. This increases the persons anxiety and despair. The time of Maghrib is likened to this situation when a person reflects over the day he has just spent and notices having done nothing commendable. So he turns to Allah and seeks forgiveness. The scenario then changes and the court passes the verdict, declaring the person guilty and the punishment begins. The time of Isha is compared to this, when the night is dark and nothing is visible. This time should make a believer take stock of all that he did during the day and should be mindful that the ensuing night is spent away from satanic enticements, lest one is led towards spiritual destruction. Eventually, as in a worldly scenario a prisoner is relieved upon release, a believer is pleased to receive the time of Fajr. It is as if the time of ease after hardship (94:7) has arrived, therefore a believer should not be indolent about offering this Salat and in order to take care of ones spiritual condition should abandon the comfort of ones bed to observe Fajr. Indeed, each Ahmadi should endeavour to observe Salat on time as it is stated in verse 104 of Surah Al Nisa (4:104)
Huzur prayed that may Allah enable all of us to observe this most significant commandment. We cannot be really useful in the mission of the Promised Messiah (on whom be peace) who had come to continue the task of the Holy Prophet (peace and blessings of Allah be on him) if we do not purify ourselves and we cannot purify ourselves unless we safeguard our Salat. Indeed the Promised Messiah (on whom be peace) called the spiritual pleasure experienced during Salat the earthly Paradise.
Next Huzur commented on the rather sad and regrettable news that Danish newspapers have reprinted a cartoon of the Holy Prophet (peace and blessings of Allah be on him) in reaction to three people arrested for allegedly plotting to kill the man who drew the original caricatures. Huzur said they have thus demonstrated their petty mindedness. When the authorities have apprehended the perpetrators then why do they seek to hurt the Muslim ummah? Huzur wondered at the fairness of those who claim to be the standard-bearers of fair play. However, Huzur said there is Allah, the Best of judges; Who is Mighty and Who will demonstrate His justice. He alone is sufficient for those who commit such odious acts.
Huzur said it was our task to explain to these people, which we have done thoroughly. We explored all the avenues, we wrote articles in response, wrote to newspapers, met with the specific newspaper people, now we entrust the matter to Allah. As for ourselves, we need to try and put the blessed model of the Prophet (peace and blessings of Allah be on him) in practice more than before. We have a Lord Who the Holy Prophet (peace and blessings of Allah be on him) identified for us and our Lord loves the Prophet more than anyone else; Our Lord will indeed exhibit His Power. Our task is to take our hurt and turn to Him and profusely invoke blessings and salutations on the Prophet (Durud). We should pray more than before, we should try and purify ourselves more than before, we should invoke blessings on the Prophet more than before. These are the aspects that will cause them to fail and will be triumphant for us.
Huzur concluded on a prayer: 'O Allah these people are being hurtful in presumption of their power. Remedy it, for You are All Powerful.'
Related Resources


text:
Yes! You choose who you would like to take part in visits with you and your nurse.
Show All Answers
No, this is a free program for all eligible women.
Your nurse will visit you every one to two weeks during your pregnancy and until your child turns two years old. Nurses are flexible and can work with your busy schedule to find a convenient time to meet.
You and your nurse can work together to decide on a place to meet that feels comfortable to you and gives some privacy for your visit.
NFP provides so much to babies and their families-from postpartum support to mental health screenings to help with understanding how your baby is developing to just having someone to talk to besides a baby! New moms, and dads, need all the help and socializing they can get, and NFP provides that, as well as someone your baby can grow to know and have a relationship with. Your nurse also becomes a very easily accessible resource for all of the millions of random questions that end up floating around in your brain when you have a new baby!
Whatcom County NFP participant
Many moms say the support of their nurse made a big difference for them. Find more NFP mom stories on the NFP website.


text:
WASHINGTON (AFP) – The discovery of more than 100 dead dolphins on Gulf of Mexico shores likely reflects only a small fraction of the total killed by the BP oil spill last year, a study suggested on Wednesday.
The actual toll among cetaceans, a group of mammals that includes whales, narwhals and dolphins, may be as much as 50 times higher, said the Canadian and American research team in the journal Conservation Letters.
"The Deepwater oil spill was the largest in US history, however, the recorded impact on wildlife was relatively low, leading to suggestions that the environmental damage of the disaster was actually modest," said lead author Rob Williams from the University of British Columbia.
"This is because reports have implied that the number of carcasses recovered, 101 (as of November 2010), equals the number of animals killed by the spill."
Looking back at annual death rates over the past decade, researchers estimate that 4,474 cetaceans died each year from 2003 to 2007, but an average of just 17 carcasses washed up annually on the northern Gulf of Mexico shores.
That indicates an overall carcass recovery rate of 0.4 percent of total estimated mortality among cetaceans in the area. When broken down by species, researchers determined there was a two percent mean recovery rate.
"If, for example, 101 cetacean carcasses were recovered overall, and the deaths were attributed to oiling, the average recovery rate (two percent) would translate to 5,050 carcasses, given the 101 carcasses detected," said the study.
Previous studies have suggested that dead sea animals that turned up following the Exxon Valdez oil spill off the coast of Alaska in 1989 also represented a small portion of the overall toll.
The National Oceanic and Atmospheric Administration on Sunday updated its figures from what it terms a "cetacean unusual mortality event" to 390 "strandings" — 96 percent of them were "stranded" dead and four percent alive.
The deaths were tracked in the northern Gulf of Mexico from February 1, 2010 to March 27, 2011.
Scientists in Mississippi and Alabama raised new concerns last month after they found 17 baby dolphins washed up dead on the shores in the span of two weeks, more than 10 times the normal rate, in the first birthing season since the BP disaster.
Florida officials have also noted above average numbers of manatee deaths for two years straight, possibly due to cold water temperatures off the waters of the southern state, though the effects of the BP spill could be a contributing factor.
The burly swimmers, sometimes known as sea cows, are not considered in the same group as cetaceans.
The disaster was set off when the Deepwater Horizon, a rig which BP leased to drill at the Macondo well, exploded on April 20, 2010, killing 11 workers and unleashing more than 205 million gallons of oil into the Gulf of Mexico.


text:
Despite all of the research supporting the effectiveness of immunizations, many parents still question the safety of vaccines for their little ones. Will they protect my infant from serious disease? Or are the vaccines themselves harmful?
Immunization is one of the best ways parents can protect their babies from serious childhood diseases ranging from tetanus and mumps to whooping cough and seasonal flu—and have been for more than 50 years. In fact, vaccinations have reduced the number of infections from vaccine-preventable diseases by more than 90%!
Both the American Academy of Pediatrics and the Centers for Disease Control and Prevention recommends that every child receive the protection that immunization provides.
Do vaccines even work?
Yes, vaccines work every year to protect millions of children from serious illnesses. Because infants are particularly vulnerable to infectious diseases, if an unvaccinated baby is exposed to a certain germ, the baby's body may not be strong enough to fight the disease. Therefore it is very important that parents take the necessary steps to ward off harmful complications through immunization.
Are there side effects?
As with any medication, side effects can occur with vaccines. These side effects are usually very minor and include redness or tenderness at the injection site or a low fever, which indicates that the body is reacting positively to the vaccine. Most babies do not experience any side effects from vaccines, and severe reactions are very rare.
Parents have the power to protect their baby from serious illnesses. Deciding not to vaccinate your child could put him at risk for life-threatening childhood diseases. If you have questions about immunization, talk with your pediatrician. You can also visit the sites listed below for additional information and updated immunization schedules.
American Academy of Pediatrics
Food and Drug Administration
Centers for Disease Control and Prevention
National Network for Immunization Information


text:
A writ of summons was registered in Australia's High Court on Wednesday on behalf of 859 detainees at the Manus Island detention centre. This is a class action initiated against Australia, Papua New Guinea, the two countries' immigration ministers, PNG's attorney-general and the companies that administer the centre.
The detainees want the High Court to use its original jurisdiction in judicial review of their transfer to and detention on Manus Island. They seek an injunction to prevent their removal to Nauru or elsewhere until the court hears the matter.
Recent background
This action follows the PNG Supreme Court finding that the detention on Manus Island is unconstitutional. The PNG Constitution contains a Charter of Rights that strictly limits the circumstances under which people may be deprived of liberty.
As Australia forcibly transferred the detainees, they were not responsible for their own unlawful entry to PNG. Therefore, no constitutional exception could permit their legal detention.
Following the Supreme Court decision, PNG Prime Minister Peter O'Neill announced the Manus Island centre would close. He asked Australia to "make alternative arrangements for the asylum seekers".
O'Neill's Australian counterpart, Malcolm Turnbull, said Australia would not accept the detainees. Australia's immigration minister, Peter Dutton, described them as PNG's responsibility.
Basis for the claim
The detainees argue their detention is illegal on international, constitutional, administrative and civil law grounds. They are asking the High Court to declare that their detention constitutes:
forcible deportation, due to their expulsion from Australia and transfer to Manus Island, contrary to international law;
arbitrary and indefinite detention, due to Australia's "no advantage" principle, in a country that lacks the legal safeguards or competence to adequately protect or process asylum seekers;
torture (an international crime that can never be excused), inhumane and degrading treatment;
rape and other crimes of sexual violence;
denial of fundamental human rights, particularly a fair hearing and legal representation;
murder (notably the violent killing of Reza Barati in February 2014), grievous bodily harm, assault and robbery; and
unlawful death, false imprisonment, trespass and negligence.
What are the detainees seeking?
The detainees request relief via the ancient writ of habeas corpus. They want to be brought before the High Court so its judges can determine whether their detention is legal.
The detainees hope the court will then issue a writ of mandamus. This would order the government to bring them to Australia to process their refugee claims.
Finally, the detainees seek a writ of prohibition, to prevent their transfer to any other place until the case has been decided and their claims assessed.
The detainees are seeking damages and costs. They may also take action in PNG for compensation. A PNG legal representative of many detainees estimates that up to A$1 billion could be owed.
This action echoes earlier high-profile claims, like the Tampa case. In such cases, human rights lawyers seek to vindicate the rights of asylum seekers who lack access to Australian courts due to their forcible offshore detention.
Other advocates have sought the aid of international courts. They argue Australia's actions against asylum seekers who seek to arrive here by boat inflict crimes against humanity.
The High Court will hear the application on May 23.
Australia's human rights problem
Around half of those detained on Manus Island have already been assessed to be genuine refugees. Yet most remain in detention, in part because their safety is at risk if they leave the centre.
The refugees would not face the same level of risk were they to be resettled in Australia. Yet PNG law has offered more substantial rights protection to them than Australian law.
The stark contrast between Australian and PNG law is in the relative degree of formal protection for human rights. Whereas PNG has a Charter of Rights enshrined in its Constitution, Australia lacks constitutional protection. Its government has rejected legislative protection for human rights.
Though Australia professes deep commitment to human rights standards in its foreign relations, it refrains from entrenching these international norms domestically. This position reflects a cultural attitude that the Australian "fair go" is sufficient protection against the excessive use of government power.
The experiences of Indigenous peoples in Australia before the law put the lie to this belief. And if adequate human rights protections are not the universal experience of people in Australia, what hope for asylum seekers who lack access to Australian courts and are demonised in public discourse?
Hope for success
The most recent High Court action challenging Australia's offshore detention arrangements in Nauru failed. The court found the government was acting in accordance with its constitutional and legislative powers.
However, the majority of judges did regard Australia as bearing at least some responsibility for the detention of asylum seekers in Nauru. This may undermine the government's argument that detainees on Manus Island are PNG's sole responsibility.
This new action's distinguishing feature is a request that the High Court use its universal jurisdiction for the first time. The detainees argue that Australia has no legal power to forcibly deport and arbitrarily and indefinitely detain asylum seekers in torturous, inhuman or degrading conditions without legal rights.
If the claim succeeds, it will entirely undermine Australia's inhumane practices in relation to "those who come across the seas".
Amy Maguire thanks Jay Williams, barrister-at-law of Frederick Jordan Chambers, for providing the original writ of summons used to initiate this action in the High Court.


text:
9 Memorable Images from the '90s
Finally, today we move into the '90s. If you missed previous posts this week, the '60s can be found here, the '70s here, and the '80s down yonder. For me, the '90s were pretty exciting times--college, my first job in the Big Apple, The New York Times switching over from black and white photos on the cover to color, watching real estate prices skyrocket, buying my first personal computer and first cellphone, and, of course, the biggest deal for a guy who now makes his living online, the launch of the World Wide Web. Below are 9 images that sum up the decade for me. How about you all? What memories do you have that I missed? Hope you enjoyed this little visual trip down memory lane! I sure did reliving it as I was writing these posts.
1. April, 1990
After many delays, on April 24, 1990, the Hubble telescope finally launched into orbit aboard the Space Shuttle Discovery, changing the face of astronomy forever.
2. January, 1991
Operation Desert Storm, a UN-authorized coalition force from 34 nations led by the United States, against Iraq in response to Iraq's invasion and annexation of Kuwait began on January 17th, 1991.
3. December, 1991
On December 25, 1991, the Union of Soviet Socialist Republics (USSR) was formally dissolved.
4. August, 1991
On 6 August 1991, CERN, a pan European organization for particle research, publicized the new World Wide Web project. All Al Gore jokes aside, it's, of course, impossible to nail down the exact birth date of the Web or the Internet, but it certainly took as all by storm in the early '90s!
5. September, 1993
Israeli PM, Yitzhak Rabin, U.S. Presiden Bill Clinton, and Chairman of the Palestine Liberation Organization, Yasser Arafat shook hands at the Oslo Accords signing ceremony on 13 September 1993.
6. August, 1997
On August 31st, 1997, Diana, Princess of Wales was killed in a tragic car accident in the Pont de l'Alma road tunnel in Paris, France.
7. January, 1998
President Bill Clinton was caught in a media-frenzied scandal involving inappropriate relations with a White House intern Monica Lewinsky, first announced on January 21st, 1998.
8. May, 1998
Seinfeld's 9-season run ended with a 75-minute, final episode on May 14, 1998.
9. December, 1999
Y2K, thankfully, didn't amount to much of anything outside a lot of stress and anxiety on December 31st, 1999.


text:
A Sugar By Any Other Name is Still a Sugar
According to professor of nutrition Barry Popkin's research, sugar is added in 60% of the packaged foods in U.S. grocery stores. Dr. Popkin did us the huge favor of compiling a list of dozens of names used by the food industry as stand-ins for sugar. Don't be fooled. If it's on this list, it's sugar, even when it's not called sugar.


text:
write a review
[More +]
Travel far and long with your essentials in the heavy duty Bugout Bag! Ready for anything and the perfect size for adventures, the Bugout Bag is equipped to handle your cargo, supplies, and anything essential you can think of!
- Size 21 H x 15 W x 9 D
- Weight 5.5lbs
- Volume 2,900in/3,300in expanded
- Hydration compatible
- Expandable main compartment
- Padded waist belt
- Compression straps
- Concealable shoulder harness and waist belt
- MOLLE/PALS panel
- Rugged, abrasion-resistant exterior
- Organizer panel
- Sternum strap
- Carry as a backpack or luggage
- Add any velcro patch!


text:
The 2014 North Carolina Extension Master Gardener Conference, Picture the Piedmont, invites you to come enjoy the beauty and the bounty of Piedmont North Carolina in early May. The conference officially opens Monday evening with an informal reception at the Red Barn at Tanglewood Park and a selfguided tour of the park's Arboretum and Gardens. But pleas come early for one of the optional preconference tours and workshops offered during the day on Monday.
We'll get down to business with advanced training all day Tuesday and continuing Wednesday morning with a variety of general and concurrent educational sessions that promise to boost your enthusiasm and expand your gardening knowledge. Please plan to join us in May for a memorable experience!
For more information about the conference including cost, registration and educational sessions, please visit the 2014 North Carolina Extension Master Gardener Conference website


text:
Animal Wildlife | Avocet | The avocet is a type of wading bird that is found across mudflats in the world's warmer climates. There are four different species of avocet which are the Pied avocet, the American avocet, the Red-necked avocet and the Andean avocet. The avocet is generally found in watery habitats close to the coast including marshland, wetlands and swamp. The exact habitat of the avocet is dependent on the species as the Pied avocet is found in Europe and Asia, the American avocet is found on the Pacific coast of North America, the Red-necked avocet in Australia and the Andean avocet is natively found nesting high up in the Andes Mountains.
The avocet is a very distinctive looking bird due to the fact that the avocet has a long and thin, upturned beak which it sweeps from side to side in the water to catch food. Like other waders the avocet also has long legs and webbed feet to aid it in hunting in the shallows. The avocet is a relatively large and forceful species of bird, often reported to intimidate other birds into leaving its spot. Avocets are relatively sociable birds and can often be seen flying, hunting, migrating and nesting in large flocks.
The avocet is a carnivorous animal and primarily feeds on insects and other small invertebrates in order to survive. Avocets also feed on small fish, crustaceans and even the odd amphibian when they are hunting in the water. Due to their relatively large size, the avocet has a limited number of predators in it's natural environment with dogs, cats, stoats and weasels being the primary predators of the avocet chicks and eggs. Avocets are known to breed on open ground, generally close to the water. The female avocet lays around 4 eggs which are incubated by both parents until they hatch a month later. Avocet chicks are nursed by both parents until they fledge (fly away from the nest) at between 4 and 6 weeks old.
Today, the avocet appears to be thriving particularly in the UK, where extensive conservation work has been done in order to try and build the avocet population after it became extinct in Britain in the 1800s. Today, the avocet is also on the logo for the RSPB (Royal Society for the Protection of Birds).
Tags: angry birds wiki, angry birds hints, angry birds commercial, angry birds guide, angry birds cheat, angry birds nest, angry birds update, birds barbershop, angry birds flash, angry birds tips, no birds, angry birds eggs, angry birds christmas, birds hitting windows, mealworms for birds, birds of canada, android angry birds, angry birds android, angry birds 2


text:
Adaptation Investigation
Class Summary
Average Rice
Average Seeds
Average Marbles
Average Marshmallow
Grand total
Tweezer beaks
Group 1
Group 2
Toothpick beaks
Group 3
Group 4
Clothespin beaks
Group 5
Group 6
Spoon beaks
Group 7
Group 8
Straw beaks
Group 9
Group 10
The source of this material is
Windows to the Universe
, at
from the
National Earth Science Teachers Association (NESTA)
. The Website was developed in part with the support of
, where it resided from 2000 - 2010. © 2010 National Earth Science Teachers Association.
Windows to the Universe
® is a registered trademark of NESTA. All Rights Reserved.
Site policies and disclaimer.


text:
(Stanza 1)
I had a dream as a girl, | It wasn't a divine vision.
like Therese of Lisieux | Her visions also weren't from God.
I need to give this a whirl | Such a serious "reform," this.
So I can lead the way | Unlike Therese, by the way, who (it seems) mainly wanted to be left alone.
Woman priest is my call | All Christians are priests, although I realize that's not what you mean.
Women preaching for all | Women aren't called to be preachers.
Don't listen to St. Paul | Paul spoke what Jesus revealed. Why not just say, "Don't listen to God"?
Cause I can lead the way | We will see.
(Chorus 1)
My ministry's growing | How is that? Numerically? It's not growing in reverence for Scripture.
Excommunication? I'm still glowing | Excommunications aren't infallible, naturally, and they can be reversed - look at SSPX.
M. Div. Chasuble Flowing | Chasuble is a robe worn during the mass, for Protestants who don't know. And getting an M. Div. doesn't qualify one for the ministry.
Where d'you think the church is going? | That's an interesting question. It could go almost any direction. Look at SSPX.
(Chorus 2)
Hey, I was baptized | This appeal to Baptism is interesting. The point, I guess, is that Baptism is unremovable.
and this is crazy | We can agree on that.
But God just called me | No, he didn't.
So ordain a lady | This would follow from the premise, but the premise is wrong.
(Chorus 3)
Justice doesn't look right | She's referring to the modern concept of "social justice." It's one of those "red flag" words that you're dealing with a non-traditionalist Roman Catholic.
with only male priests | What about only male husbands and fathers?
but God just called me | (see chorus 2)
So ordain a lady | Why should the appearance of social justice be a good enough reason?
(repeat of chorus 2)
(Chorus 4)
All the other churches, | My church isn't interested in ordain women preachers, miss. She points to an Episcopalian church sign. Interestingly, the Anglicans narrowly avoided women bishops, although they have women priests.
try to schmooze me, | We'd like to evangelize you, but not have you come preach for us.
but I'm a Catholic, | You're a Roman Catholic by baptism and confirmation (and as to a number of beliefs), but you're exommunicated.
so ordain a lady | Is this because otherwise you might leave? I think the current leadership might be ok with that.
(Stanza 2)
My call is a fact, | No, it's your imagination.
But some pope in a hat | Why do you want authority in your church, if you think so little of authority in your church? But I will certainly agree that there is not (to my knowledge) any recent infallible papal teaching on the subject.
closed discussion on that | But you don't just want discussion - you demand a change of policy.
and now he's in my way | He is an obstacle to you fulfilling your desires.
I pray, sing and I feel | Bragging about one's devotion is never wise.
at first communion its real | Does your excommunication also feel real? Do the illicit women masses feel real? I guess the point is just more of insisting that she's a "good Catholic."
but I refuse to kneel | let her finish the clause ...
to Patriarchy's way | Do those prayers include the "our Father"? Why not submit to patriarchy, given that you recognize it is the teaching of Scripture?
(repeat of chorus 2)
(repeat of chorus 3)
(repeat of chorus 2)
(repeat of chorus 4)
(Chorus 5)
With women priests in my life | When exactly was this?
I was so glad | That concern about the sex of your priests doesn't look very "social justice" friendly, by the way.
I miss them so bad | Should I offer my condolences?
I miss them so so bad | Just because they were not male?
(Chorus 6)
With women priests in my life | (see chorus 5)
I was so glad | (see chorus 5)
We want our church back | It is interesting how every sub-group within Rome thinks Rome belongs to them. If it's not going their way politically, the church has been stolen from them. Compare the similar comments from the ultra-traditionalists.
We want it all, all back | I assume this is just repetition for the sake of fitting the tune.
(repeat of chorus 3)
(repeat of chorus 2)
(repeat of chorus 4)
(repeat of chorus 5)
(repeat of chorus 6)
Note on the credits. It's interesting that it happens that the editor, with his name at the top of the credits, is a male. There is also at least two male dancers augmenting the nine or so young ladies and one baby who has a "Mommy for Pope" shirt one, while his mother(?) dances with him wearing some kind of mitre.
The video appears to have been shot at St. Thomas Episcopal Church (mentioned in the credits) in Washington, DC, despite the supposed resistance to "shmoozing" by other churches. While the group that produced this video is relatively small and silly, they are serious - and they are not alone amongst self-identifying Roman Catholics.


text:
Seven Agencies Purchase Spillman, 40 Expand Systems in Q1
SALT LAKE CITY, Utah – Seven public safety agencies purchased software from Spillman Technologies for the first time during the opening quarter of 2013, joining the more than 1,000 public safety agencies in 37 states nationwide already using Spillman software. In addition to the new agencies, 40 agencies expanded their existing Spillman systems.
The Jackson County Sheriff's Office in Indiana is equipping its field personnel with Spillman's mobile software, giving deputies access to agency records on the road. Field personnel will have the ability to search name, vehicle, and incident records from patrol-mounted laptops. While on the road, warnings connected to name records will keep deputies safe by alerting them to potentially dangerous situations, while fast access to record images will help improve efficiency by allowing deputies to verify identities in the field without returning to the office for follow-up.
The Cedar City Police Department in Utah will be using Spillman's Driver License Scanning module to quickly populate mobile search screen and field reports with driver license data. Data from driver license scans can be used in quick searches from their local databases as well as statewide and national databases.
In Pennsylvania, the Williamsport Bureau of Police will be using Spillman's CompStat and Community Dashboard modules with data pulled directly from their Spillman system to stay informed of crime trends in their jurisdiction. These modules employ the principles of intelligence-led policing to help command staff address crime trends in the community and determine where resources are best utilized. With CompStat, agency personnel will be able to quickly see at what rate crimes are increasing or decreasing and pinpoint hotspots of activity and vulnerable areas. The Community Dashboard will then enable the agency to share this information with the community.
Spillman Technologies is a public safety software provider headquartered in Salt Lake City, serving more than 1,000 police departments, sheriff's offices, communication centers, fire departments, and correctional facilities nationwide. Spillman specializes in integrated software solutions, including Computer Aided Dispatch, Records Management Systems, Mobile Data & Field Reporting, Mapping & GIS, CompStat & Intelligence-Led Policing, Jail Management Systems, Fire, Data Sharing, and Personnel & Resources. For more information about Spillman, visit www.spillman.com
New sales:
• Big Stone Gap Police Department, Va.
• Essex County Sheriff's Department, Maine
• Hudson Volunteer Fire Department, Colo.
• Sanibel Police Department, Fla.
• Whatcom County Sheriff's Office, Wash.
• Williamsport Bureau of Police, Pa.
• Wise Police Department, Va.
Add-on sales highlights:
• Avondale Police Department, Ariz.
• Cedar City Police Department, Utah
• Douglas County Emergency Management, Wis.
• East Chicago Police Department, Ind.
• Jackson County Sheriff, Ind.
• Moscow Police Department, Idaho
• Oconto County Sheriff, Wis.
• Port of Houston Authority, Texas
• West Valley City Police Department, Utah
• Wise County Sheriff's Office, Va.


text:
Colour will vary on each individual. Always wash hands before use.
Designed to blend well with any natural eye color, even dark ones!
Material: HEMA
Item Type: Colored Contact Lenses
Lens BC: 8.8mm
Diameter: 14.3mm
Water Content: 38%
Replacement Cycle: Monthly
Occasion: Party, Wedding, Club, Cosplay, etc.
Packing Specification: 1 Pair of Lenses
Prescription Power: 0.00~-6.00