text:
I still can't find his birth record… Ziverts is the Latvian spelling for this surname, but it is Sihwert or Siewert in German… There are ethnic Germans in the area named Siebert, and while I can't prove that the Ziverts descended from ethnic Germans just yet, I have thus far been ignoring the German congregation church records in favour of the ethnic Latvians. I think it's time to check out the German congregation for an Indriks Siebert born around 1875… One more resource at my fingertips to exhaust.
2 thoughts on "Roadblock: Indriks Ziverts/Siebert?"
I have sometimes noticed ethnic Latvians in the German congregation records, with the possibility for more, those were just the ones with the obviously Latvian names. I can think of several possibilities for it – they may have married into a German family, or they were of non-peasant class (remember, Latvian was considered a "peasant" language, anyone who wanted to move up in the world at the time would often Germanize), or they were peasants but still attempting to move up in the social order through any means they could.
So if you find Indriks in the German records, he could be German, but he could also still be Latvian. Do there happen to be 1897 census records for the parish you're looking at? Those records will list mother tongue.


text:
Interview with John Ely from Dodgers on Demand
Check out this interview of John Ely. It aired on Time Warner Cable Dodgers on Demand segment.
I hope you enjoy it as much as I did!
He only needed 83 pitches to put himself in line for the win. He finally walked a batter after not issuing one over his previous three starts (19.2 innings). I love Ely and have him in my MLBlog fantasy team!
8 Comments
Hi Emma! Looks like Ely is doing well for the Dodgers, and for your fantasy team! Good luck to him, and good luck to you fantasy-wise. I finally have a new post up, with pix from the Phestival on Monday night.
Rants, Raves, and Random Thoughts
ELy is doing great! And I am kicking butts lately in the fantasy league🙂. I'll check the phestival.
Wow. He's adorable. A friend told me he looked like Matthew McConaughy and he does. Glad he's pitching well for you guys.
I too think he is adorable! and I love pitchers that are stingy with the walks.
He looks like he should be in high school but that's a hell of a 12 to 6 curve ball.
LOL Mike. Yeah, he looks like he should be in high school. I love his enthusiasm. I felt bad for the loss today. The kid deserved a win. He lost 1-0.
I like Ely too. He's a Chicago guy… born and raised in the 'burbs I believe. The White Sox liked his potential, but I don't think they thought he'd develop with the type of control he's been showing. Good for the Dodgers though. Y'all could use some solid pitching. I'm still not happy your team LOST the game though. Booooooooo. Beat the sCrUBS! Guess we'll have to do it for ya😉 Go Cards!
Hey Jeff! Ely pitched another gem and nothing to show for. That was a good pitching dual to watch though. The kid has not given up the long ball yet. I can't wait for his next start which should be at Dodger Stadium. And your Cardinals will be in town for the next homestand.
I know you take extra satisfaction on beating the Cubs.

subset: commoncrawl


text:
OpenBSD celebrated release 3.5 on 1 May 2004. In honor of this release, Federico Biancuzzi interviewed the developers of OpenBSD's PF, a powerful and flexible packet filtering interface. This is the second half of an interview that began in PF Developer Interview, Part 1.
Federico Biancuzzi: A recent research by Paul Watson entitled Slipping in the Window: TCP Reset Attacks caused a lot of rumors in the media. After the public presentation at the CanSecWest conference, we understood that the real situation was not so terrible for every OS. How does OpenBSD reduce the risk of this type of attack?
Henning Brauer: OpenBSD is not vulnerable to these attacks. We use random ephemeral ports since 1996. We require RSTs to be right in the edge of the window since 1998.
Federico: How can PF protect a vulnerable server from this type of attack?
HB: The scrubber has just been modified to drop RSTs which are not right on the edge of the window. A special form of NAT where only the src port is modified is beeing worked on.
Federico: During the end of April most PF developers flew to Ryan McBride's house to start a short PF hackathon. (See Figure 1 for a photo from Ryan himself.) What are the new features and enhancements that were planned or already committed for the next release?
Figure 1. OpenBSD hackers hard at work at a recent hackathon.
HB: We had an extremely productive four-day hacking party at Ryan's house in the woods near Sechelt (British Columbia, Canada — about 2 hours from Vancouver), yes.
It was really a network hackathon, not limited to pf. Besides a lot of smaller things, the stuff we hacked on includes:
authpf executes
pfctl instead of sharing a lot of
code with it, which was a bit fragile
ifconfig rather than attach time
em(4) and
sis(4), others to
follow. This reduces the number of mbuf clusters sitting around unused.
ifconfig cleanup
tcpdump about carp
return-rst now works on IPless bridges
authpf now loads the autheticated users IP addresses into a
table too
Ongoing work includes a rework of how anchors work — they can be nested soon, and the ruleset name (which is really just one level of nesting) will go away.
Federico: What type of platform do you use for PF development? Has the code any optimization for a particular architecture, like 64bit (Athlon64, Sparc64, G5, Prescot)?
HB: I mostly hack pf on my i386 notebook and, less often, my sparc workstation. Tests on sparc64 are mandatory as this is the most picky platform, especially due to its memory alignment requirements. I occasionally test on alpha, hppa, amd64, mvme68k, mvme88k, mac68k and VAX as well.
pf operates completely in MI (Machine Independent) land, there is no MD (Machine Dependent) code whatsoever.
Ryan McBride: I develop on sparc64 and i386. sparc is used for testing, and I have VAX and cats boxes sitting here waiting to be set up for testing (too slow for real development)
Cedric Berger: Mostly i386 gear. When doing big changes, I usually try to compile the code on a Sparc64 box since unlike i386, it uses 64-bit, big-endian, and gcc3. If PF code works on Sparc64 and i386, it has good chances to work well on the other architectures.
Federico: Which platform would you suggest to deploy an OpenBSD based firewall for various scenarios (home, office, enterprise)?
HB: Well, basically, any.
Vax may not be a good choice for filtering Gigabit speeds, obviously. From
the modern archs, sparc64, alpha, and amd64 are all good choices. i386 and
powerpc less so, I like
W^X purity, but should not impose
performance problems either.
RM: For small sites, the Soekris 4501 or 4801 make
excellent devices. For bigger links, an AMD64 based system is an excellent
choice. Even if you're only dealing with 100Mbit links, using gigabit cards
em(4) or
sk(4) will improve performance as these
cards are designed to handle much higher numbers of packets per second than
100Mbit cards.
Federico: Reading the pf@ mailing list I found that the code has some limit regarding the hardware usage. What type of limits does PF present in the 3.5 release? How many concurrent states and how much RAM can PF handle?
HB: That thread is full of lies and uninformed guesses. Ignore it.
pf itself doesn't impose many limits. We have the settable state and fragment limits to prevent pool exhaustion, the amount of memory available for the pools used by pf varies depending on the hardware.
I don't have exact numbers; but 50,000 state entries are not a problem on a i386 with 128 MB.
That said, there is ongoing work which changes the way OpenBSD handles kernel memory used for the network stack — pf is not special here. This will allow for both more efficient usage, backpressure when needed, and more total memory available to the network stack including pf, thus allowing for much bigger state stables etc.
CB: With this patch by Mike Frantzen, you can use up to 768MB of RAM on i386 to store table entries, versus 64MB previously. We're looking for a similar improvement for the state table, but that's a bit more difficult.
Federico: PF is going to be ported to other BSDs. Daniel, are you proud of this? Are you working on these portings?
Daniel Hartmeier: I've been working with Pyun YongHyeon and Max Laier who do the FreeBSD port. They did all of the work, I merely tried to answer questions and sometimes aid in debugging. This has proven valuable to the base source, several bugs were found and fixed in the process. Maintaining several ports will cause additional work, of course, but the additional user base producing feedback makes it worth the effort.
Federico: Now that PF has been imported into the FreeBSD base system, do you think that some people will consider moving from OpenBSD to FreeBSD for its SMP support and better performance?
HB: Not at all. First, the performance advantages of FreeBSD, that is largely a myth. All BSDs are rather close to each other with respect to general performance.
Second, I don't expect any OpenBSD/pf user to switch, as pf on OpenBSD will
always have some advantages — as we develop pf here, we can embed it much
deeper. What I expect is FreeBSD users switching to pf from
RM: On most firewalls, the CPU is not the bottleneck, so adding a second one will not help (and may even slow things down). That being said, SMP support is being worked on actively for OpenBSD, and will likely appear in 1 or 2 releases, depending on how long it takes to get it right.
CB: Competition is good. If FreeBSD is better than OpenBSD for some application, I will use FreeBSD for that application. If OpenBSD performance lacks in some areas, we will try to fix it. That being said, I believe OpenBSD is clearly the best choice for a firewall now, for various reasons.
Federico: Why does PF still miss one basic feature like IPFilter
HB: Because nobody thought it was needed? There were no requests for this whatsoever, nobody of us had a need to, so nobody wrote that. That nobody requested it after, what is it now, 2.5 years?, is a strong sign it is not needed at all.
CB: Because nobody in the developer or user community cared enough to send a working patch.
Implementing that functionality is not easy, but I'm now looking at
return-icmp for pure bridges, when there is no
routing table (
return-rst for bridges has just been committed). It
is very likely that once I've
return-icmp working on bridges,
return-icmp-as-dest support will be trivial.
Federico: Why doesn't PF come with an internal version number to track various updates typical of -stable branches?
HB: what for?
OpenBSD 3.5 is OpenBSD 3.5 is OpenBSD 3.5, period.
Can Erkin Acar: Since the kernel and userland is always synchronized,
there is not much point in adding a version identifier. For external utilities,
such as
pftop (which still compiles on OpenBSD 3.0) the OpenBSD
release numbers are usually sufficient.
Federico: What type of support does PF provide for IPv6? Are there any interesting features specifically for IPv6? What features are still missing?
HB: PF has full IPv6 support — there's nothing really special or different opposed to v4.
RM: We're missing IPv6 fragment reassembly support, but
this is being worked on actively and will probably be included in 3.6.
pfsync does not support IPv6 as a transport.
Federico: Since the ALTQ merge in the 3.3 release, a lot of people enjoyed shaping the bandwidth with PF rules. Is there anything new for ALTQ, like other types of queues?
HB: Kenjiro and myself added
HFSC for 3.4 and
polished things a little, and I rewrote the ID allocator. No real changes were
done after that in the queueing arena, and there are no planned currently. In
our eyes the current state is quite fine.
Federico: How do PF and IPSEC interact? What type of problems have you resolved and what stills need to be solved?
DH: pf sees IPsec encapsulated traffic both encapsulated on
the real interface as well as decapsulated on
enc(4). Filtering
and translation can be done on either, with various effects. Apart from that,
pf doesn't treat IPsec traffic differently from other protocols. It doesn't
filter on SPI or other IPsec specific fields. UDP encapsulation for NAT
traversal have recently been added, but that's outside of pf, in IPsec/stack
Several special requirements, like static source ports for
isakmpd, have been addressed, so pf basically works at least as
well with IPsec as any other packet filter not doing IPsec protocol
HB: They do not interact more than pf interacts with anything else network related — pf passes or blocks ipsec traffic.
CB: They interact pretty well. You can filter ESP packets
on the real interface or decrypted packet on
enc0. Nat/rdr is
possible on
enc0, but that's tricky. What I'd like to do for next
release is to remove the need for the
pass on enc0 proto ipencap
all rule, that is just wrong.
Federico: WiFi network are becoming widely (and wildly) used. What can PF do for a wireless network? Is there any new idea specific for wireless filtering?
HB: I don't see wireless much different than wired networks
with respect to pf.
authpf can be especially neat in wireless
networks, but it already is neat in wired ones too.
Federico: If I'm not wrong, tools that use raw access to network data bypass PF because the filtering happens after. How can this be solved? Is this a behavior you want to change?
HB: This is not true.
It is true that
bpf is outside pf. This is actually very good
for debugging.
We might add a possibility for bpf-based tools to request to be hooked in
before pf. It might be useful for the dhcp programs. But then, that is not a
real-world problem — I have privilege revoked
dhcpd and
dhcrelay so that they don't run as root anymore, and
canacar@ helped out with
bpf write filters (we have
read filters already) and lock the
bpf device so that no changes
in those filters are possible anymore. Especially for
dhcpd that
means that one very worrysome piece of code is now locked away that nicely that
you don't have to worry much anymore. And of course besides the privdrop and
bpf security work, we cleaned that mess up big time...
The most worrysome of those programs is now
dhclient which is
scary, huge and still runs as root — even given we cut about half of its
code out already. I have it running privilege separated on my machine
RM: I don't see this as a problem, and don't think that this will be changed.
CEA: This is by design, and I do not want/see this behavior changing. We have introduced bpf security extensions to solve this problem on a case-by-case basis. We are going through every program in the tree and modify them to use the security extensions and drop/separate privileges. At some point we may also start looking at critical applications in the ports tree.
Federico: What type of
bpf security extensions have been
bpf is a device designed to capture
packets from an interface. It has a filter language for selecting a subset of
packets to be read, used mainly for performance reasons.
bpf also
contains some functionality for injecting packets into the network.
Programs use
bpf by opening one of the
/dev/bpfX devices, and obtaining a file descriptor. The
access to the devices is restricted to root by default (through file
permissions). The problem happens when a program wishes to drop privileges, or
use privilege separation, after obtaining a
bpf descriptor.
Even with dropped privileges, a program can change the filters, and the
interface and, thus sniff any interface on the host. Furthermore, if
the descriptor was opened with write access (some daemons require this, and
libpcap does this by default) it is possible to inject packets to
any of the available interfaces.
This had to be solved before any bpf-using program can be safely privilege separated. Two security mechanisms were introduced:
write filtering allows setting
bpf filters for write
locking prevents "dangerous" changes to the descriptor such as modifying the read/write filters, and changing the interface. Obviously the descriptor cannot be unlocked once it is locked.
If the descriptor is properly configured and locked before dropping
privileges, an exploit will not be able to further compromise the system
through the
bpf descriptor.
Federico: I've read this thread
on the misc@ mailing list and I'm wondering what are the advantages of
tcpdump privilege separation?
CEA: Network data is untrusted, and parsing them into a
readable form is difficult and error-prone, especially for complex or obscure
protocols, thus
tcpdump (and most other sniffers) are complex and
potentially dangerous pieces of code. A look at recently discovered
vulnerabilities in such programs should give an idea. Even saved binary files
may not be safe, and could act as time bombs. Privilege separation is used in
these programs to isolate the dangerous packet parsing code into an
unprivileged chroot jail.
At this point running
tcpdump as root in OpenBSD is much more
safer than running it unprivileged, since being root allows it to properly
privsep. Hopefully this will be improved to cover unprivileged use, possibly
using setuid after we resolve some signal issues. Yes, there is an irony here,
making a program setuid root to make it safer :)
Federico: Can, could you provide a short history of
CEA: The logging mechanism in pf is ingenious. Saving the
raw packet dumps loses minimum information, (usually) uses less space than
ASCII logs, and allows the logs to be analyzed using a variety of tools,
including passive OS fingerprinting recently added to our
and all the other cool analyzers/sniffers available.
The first version of
pflogd is imported into the three about 2
months after the
pflog interface. It had a basic functionality:
dump the logs to a file in binary
tcpdump format, make sure the
existing file has the correct header before appending, handle SIGALRM for
flushing logs, and SIGHUP for re-opening the log files for working correctly
with log rotation.
At the last hackathon, right after OpenBSD 3.3 is released I have added
support for the new
pflog format.
pflogd supports
both, but refuses to overwrite an old file and outputs a 'Move away' warning to
After OpenBSD 3.4 is released, the
bpf extensions was ready,
pflogd was privilege separated. The privileged parent handled
bpf descriptor stuff and opening/positioning of log files,
while the child running chrooted under
_pflogd user is used for
Later, (January 2004) it was noticed that the
pflogd files may
become corrupted if the partition gets full, or after an unclean shutdown. In
this case some or all of the appended logs would become unreadable.
pflogd now scans the complete log file, and detects corruption,
and gives the "Move away" warning, refusing to append until the log is moved or
rotated away.
Future: I have a (half forgotten) diff that handles the infamous "move away" part by renaming the existing log if a problem is detected. I have also not yet abandoned my plans for having ASCII pflogs.
tcpdump is
safe, and more powerful than anything I could put into
pflogd, but
lacks the rotation functionality.
Federico: Can, could you provide a short history of the PF logs format?
CEA: The pf logs contain a header and the logged packet itself. In the initial version, the header length was fixed, and very simple. It contained "interface, direction, action, a rule number" and a sub reason (why passed or dropped). This old format contained an unofficial link type (an identifier that determines the interface type and header format) and having a fixed length with no empty fields, it was not extendable.
After 3.3, we have improved the format to contain anchor and ruleset names
and a header length field which will allow the format to be extended later as
required. We have also changed the link type to the official id obtained from
tcpdump maintainers.
Federico: The PF log format has changed over time. Do other operating systems
or common software such as
ethereal and the standard
tcpdump support this format?
CEA: I have contributed patches to
and snort also supports the format. The standard
tcpdump includes
support to the new format since
tcpdump_3_8rel2 (although they
dropped backward compatibility to the old format).
Federico: Mike, you wrote most of the stateful engine. How did you audit it?
MF: Auditing is more of a continual process than one would think. Whenever something that you never thought of before comes out, you have to go through all your code again to make sure you're not affected. Often that is a self sustaining process. Inspiration often strikes during the audit and you think of more gotchas so you re-audit and think of more gotchas to audit for. I end up staring [at] a lot of weird and funky traffic at work; corner cases of corner cases. Most of my audits are walking those weird packets or connections through PF's state engine to make sure we don't block a valid packet.
Federico: Mike, you wrote most of the scrub feature. What improvements are planned for the future? What about TCP scrubbing and normalization?
MF: Niels Provos did the initial fragmentation and flag scrubbing support based on Paxson and Handley's USENIX paper. My planned improvements are in the normalization of TCP segments. The TCP protocol was designed so that there are only two active participants in any given connection. Making PF more active in the TCP stream will be done very gradually since mistakes lead to massive ACK storms or connections mysteriously freezing.
Federico: Mike, your job focuses on IDS development. Had you any ideas to make PF capable of interacting with an IDS like Snort?
MF: There are a few levels of interaction between a
firewall and an IDS. I believe Snort has been able to do intrusion detection on
any packet logged by PF for a year or two now (PF logged packets appear on the
pflogd0 virtual interface which you can monitor with many
libpcap based programs like
tcpdump or
There are already two ways to emulate Linux's DIVERT sockets and turn an
IDS into an IPS (Intrusion Prevention System). One could use PF to route the
packets to a tunnel device and read them there. Or one could block the packet
in PF and watch the full packet show up on the
pflogd0 logging
And a passive IDS running on the firewall could easily tell PF to kill all of an attackers connections and add his IP address to a blacklist or even redirect any new connections from him to a honeypot.
The tools are all there. All it takes is someone to add the code to Snort. Someone whose employer doesn't compete with Snort :-).
Federico: Are there any plans to develop application proxies for common protocols like HTTP, SMTP and POP3?
DH: They are easily done in userland, see
ftp-proxy(8). We agree to not do it in kernel. If there is enough
demand for protocols besides FTP, someone will step up and do it, I'm sure.
HB: No.
ftp-proxy is needed due to the nature of ftp with its two
connections, the place for other proxies is in ports IMHO. That said, some
stuff is imaginable in-tree, and if somebody steps up and writes good code,
this is certainly welcome. Whether it turns into a port then or goes into the
main tree, I can't say yet.
RM: In the kernel? Certainly not, the risk for compromise
is too great. In userland, already have
ftp-proxy, and there are
3rd party applications which handle many of the other protocols:
apache or
squid for HTTP; MTAs such as
sendmail are basically SMTP proxies by nature.
CEA: These protocols are quite firewall friendly since they
use well defined ports. These protocols could benefit from content filtering or
caching. OpenBSD already has
spamd which is a proxy for spam :)
and there are a number of http proxies in the ports tree. I am not aware of any
specific plans, but someone might just decide to write one.
CB: I've no idea.
Federico: Some OpenBSD developers wrote various tools to analyze PF logs and statistics (pfstat, Hatchet,...). Is there any project to create a global and unique graphical interface to work with PF?
HB: No.
RM: Not by any OpenBSD developers. Doing a good GUI configuration tool for PF is very difficult because there are so many options, and laying them out intuitively in a graphical interface is nearly impossible.
Federico: Can, could you explain
CEA: It started as a text-mode realtime display tool for
active pf states. It improved quickly with feedback and patches from the
community. It now has rule and queue pages, and can compute per state
throughput. I should probably find some time to catch up with the new pf
features in 3.5 though.
pftop is available in the ports tree as
Federico: Please, tell us the all the truth about PF performance tweaking. What are the right settings to build a stable and network optimized kernel?
HB: Use
I totally don't get that tweak tweak tweak attitude.
works fine in almost all circumstances. If you have a real problem
GENERIC, as in a problem that shows up during real world
usage, then post to misc@ and you'll get help.
Of course there are cases where you need to tune; I have machines where I
need to crank
nmbclusters a little. BUT: the key point is, as long
GENERIC works and doesn't show a problem that is the best you
can get. And making
GENERIC work for more and more scenarios is
one of the major things we are doing since some releases, by switching from
compile time options to runtime controllable stuff (mostly
or at least allow changing from
In fact, a lot of knobs should not ever be touched. This especially is true
nkmemclusters. The myth about that being needed comes from old
days where we had a leak in the routing table code under some circumstances...
nowadays you will in almost all cases shoot yourself in the foot by mucking
nkmemclusters. You increase it, something else needs more
kernel memory, and you run out. You will crash. So don't touch it.
OpenBSD 3.6 will come with big improvements in that area.
Federico: How will PF evolve? More features or performance tweak?
DH: I think addition of new features will slow down over time, most things are covered by now. New features have to be justified against the instability changes introduce. Changes have been frequent at first, I don't mind changes settling down. That allows [us] to more carefully search for performance improvements and plain bugs.
MF: My PF wishlist is almost empty. I imagine most of the next big evolutions will be from spontaneous ideas someone has in the bar or us feeding off ideas of the others during the next PF hackathon.
HB: There's ongoing work on
bpf security. We
are also looking at further flexibility in the language and some internal
changes that solve little problems.
There are no "big" new features planned for pf; maybe some of the stuff we do outside pf gets to interact with it in some way. We've been at the "pf is done" point quite a few times now, and there have been great ideas later on. pf development slowed down, and will slow down even more — not because we don't have enough developers or something, but simply because it is, well, pretty much done.
Compatibility becomes a much larger issue with every release that contains pf and with each and every pf installation, that's an area where I think we have to get better.
CB: The one thing I'd like to have for 3.6 is the ability
for firewalls working in a bridged environment to send IP packets (i.e.,
firewalls without IP address and/or routing table). Currently, features like
return-rst don't
work on such a firewall because PF does not know how and where to send packets.
Fortunately, I think there are good 95% solutions to that problem, which is
probably the most requested feature on PF lists.
Besides that, I'm not aware of any "big" things that would come, but we've been saying that for every past release, as far back as I remember :).
RM: Because of the very clean initial design, PF has never had real performance problems — in the vast majority of PF deployments, the CPU sits essentially idle. So there's not much incentive for developers to spend long hours squeezing a bit more performance out of the code — such efforts would likely increase the complexity and thus the chance of bugs.
With regards to new features, it is hard to say; PF is becoming fairly feature complete and eventually development will slow down to a maintenance mode, like many other areas of OpenBSD. On the other hand, put 2 PF developers in a room together, and they immediately begin to come up with new crazy ideas. So I don't see it stopping within the next few releases.
However, I think the bulk of new work being done will not be in adding new features, but in the following 2 areas: fine tuning the features which already exist as we learn more about how they are used in production deployments, and making internal changes which simplify or reduce the code base. The latter is very boring for users, but actually quite important in reducing the potential for bugs.
CEA: I think, with the recent failover work, the feature range is quite complete. There would definitely be some performance tweaks, and improvements/additions to supporting userland tools before new features.
Federico Biancuzzi is a freelance interviewer. His interviews appeared on publications such as ONLamp.com, LinuxDevCenter.com, SecurityFocus.com, NewsForge.com, Linux.com, TheRegister.co.uk, ArsTechnica.com, the Polish print magazine BSD Magazine, and the Italian print magazine Linux&C.
Return to the BSD DevCenter.
Copyright © 2009 O'Reilly Media, Inc.


text:
Striking a balance between flexible, low profile design and resilient underfoot protection, the Nike Free 4.0 v2 has minimal cushioning and a semi-soft feel.
You want a flexible, lower weight shoe but don't want to give up cushioning and protection. The Nike Free 4.0 v2 is a midway point between the minimal and traditional running shoe. A 6mm drop brings you more level to the ground, and flex grooves in the midsole allow for more natural foot movement. The soft midsole is lightweight and still offers good cushion for heel and forefoot strikers alike.
Model Number:
Weight: 6.8 oz (size 8)
Stack Height: Heel (22mm), Forefoot (16mm)
Available Widths: B=Medium
How It Fits (based on width B)
The Nike FREE 4.0 v2 is a minimum featured, minimum neutral shoe designed for speedwork, racing, and daily training.
Be the first to write a review for this product!Write a Review


text:
The local event of the fifth annual nationwide Friends of the Poor Walk will be held Saturday at Veteran's Memorial Park in McHenry.
Registration begins at 8 a.m., and the 3-mile walk begins at 9 a.m.
Proceeds from the walk will help relieve poverty and bring awareness to the McHenry, Johnsburg and Ringwood areas.
For information and to print ou a registration and pledge form, visit www.svdpfriendsofthepoorwalk.org.


text:
Bird's eye view aids conservation
- published_in
- The Eye
Back in 2007, she paid a visit here when her institute began using DigitalGlobe's high-resolution images taken from its QuickBird satellite to make conservation decisions. The photographs provided information about the status of chimpanzee habitats and where and how people use their land in Tanzania and the eastern Democratic Republic of the Congo.
With the aid of satellite imagery, the institute has mapped human structures, footpaths, farms and forests that have been used in village land-use plans in the USAID-funded Greater Gombe Ecosystem Program. Satellite imagery also has been used to map tree canopies for assessing chimpanzee food availability and feeding behavior research in Gombe National Park. In remote places such as the Masito-Ugalla Ecosystem, satellite imagery is used to explore large swaths of terrain.
Goodall established the institute in 1977. Today, the institute is a global organization supporting the research at Gombe in addition to many other programs.
Want to see more? Login or Subscribe.


text:
August 7, 2013 —
After a debate and narrow passage at the Upper Delaware Council's (UDC) operations committee in July, a letter to area congressmen in support of renewed federal funding of the Delaware River Basin Commission (DRBC) was approved without opposition by the full council on August 1.
Tusten's Susan Sullivan had asked for a letter of support at the full council meeting in July, saying the DRBC was the only agency that has consistently supported efforts to maintain the health of the Upper Delaware.
While the UDC letter was in support of legislation in Congress that would reverse a failure of Congress to help fund DRBC for 16 of the past 17 years, it was seen by some as a UDC position on the ongoing controversy over natural gas drilling and complaints about the nearly two-year delay by the DRBC commissioners to bring to a vote regulations on water use by drillers.
According to the minutes of the July 23 operations committee meeting, Delaware representative Harold Roeder and Hancock's Fred Peckham said they had problems with the letter.
Cochecton's Larry Richardson asked Roeder if he would penalize a partner on the council (DRBC is a non-voting partner) for its position on gas drilling.
Roeder said that drilling was not the issue, but that DRBC "dropped the ball" in failing to install regulations "to protect the river from anything that could happen," for four years.
He did not say how reducing the staff's funding would correct that problem.
Peckham felt that DRBC is also challenging the sovereignty of the states by getting involved with land-use regulations, which is not their mission. He wanted some action, rather than leaving people "just hanging," he said.
Richardson said that DRBC staff had done its work, but the commissioners—the governors of the four basin states and the federal government—have not acted on the two drafts of the regulations presented to them.
Roeder then suggested that a letter to the commissioners about their delay would be appropriate.
Richardson outlined other areas of DRBC oversight, saying that gas drilling regulation was not their main mission.
At the operations committee meeting, the letter was finally approved by a 3-2 vote, with Shohola's George J. Fluhr, Lumberland's Nadia Rajsz and Richardson in the affirmative. Jeffrey Dexter of Damascus and Debra Conway of Highland did not attend that meeting.
Roeder did not attend the August 1 full council meeting, and also absent were representatives from Lackawaxen; Fremont, whose primary delegate Jack Niflot recently passed away; and Westfall, which has not named a current delegate.
The only related discussion about DRBC regulations came from DRBC spokesman Kenneth Najjar, who recalled that 69,000 comments were received on the two draft rules released in 2010. The commissioners have not acted since then, and Najjar said "discussion among the parties continues."
Najjar went on the report that "a lot has happened in the past several years," regarding the science involved in preparing regulations and "the regulations are not done yet."
"The goal is this year," he said. "The question is, how much regulation."
The UDC letter supporting the Water Resources Development Act of 2013, which has already passed in the U.S. Senate, was approved by the council without opposition.
Peckham abstained from the vote.
In other business, the UDC named Al Henry to serve as Secretary-Treasurer to replace Niflot.
They also approved an application to join U.S. Rep. Chris Gibson's (R-NY) newly formed watershed advisory council and a follow-up letter to the contractor of two proposed cell towers in Damascus, again requesting a balloon test to determine their visibility from the river corridor.
Noting that past public opposition to cell towers has changed with increased usage of cell phones, National Park Service Superintendent Sean McGuinness said, "we don't want to keep the towers out. We all want service, but do it in a way that they are not so visible."
[See this week's editorial [2].]


text:
Four nearly four years various American Indian tribes have been blocked from opening casinos in Sullivan County because of a rule regarding off-reservation casinos. The rule said that the U.S. Department of the Interior and the Bureau of Indian Affairs would not approve any Indian Casinos that were located more than a "commutable" distance away from the tribe's reservation.
Senator Chuck Schumer and others have been pushing to have that rule thrown out, and on June 14, Schumer announced that his efforts had been successful. He took credit for the reversal in a press release. The move had been previously opposed by U.S. Senate Majority Leader Harry Reid who reportedly wanted to protect the gambling industry in his home state of Nevada.
Schumer said the casino deals in Sullivan that had been turned down in the past should be revisited. He said. "The previous Catskill casino applications deserve to be reconsidered because they demonstrated broad and deep community support, were developed in consultation with state and local officials, have revenue sharing agreements with localities and the state, and completed extensive environmental reviews."
There is a good possibility that several of the tribes who have worked for a casino in Sullivan County in past years will renew the effort. Kimberly Vele, president of the Stockbridge Munsee Band of Mohican Indians issued at statement saying, "For more than a decade, the Stockbridge Munsee Band worked closely with state and local officials to achieve our goal of re-establishing our presence in our aboriginal territory in New York State. We negotiated agreements with the Sullivan County, and signed a compact with the State of New York. The tribe is now in the process of exploring its options regarding our plans to establish a casino resort in the Catskills.
County officials immediately applauded the development.
Jonathan Rouis, chairman of the Sullivan County Legislature, said, "I applaud the efforts of Senator Schumer as he lobbied hard for the lifting of the ban on off reservation casinos. We look forward to starting the process with our Native American partners to secure Native American gaming in the Sullivan County Catskills."
"It has been an ongoing struggle to secure gaming in Sullivan County and I am cautiously optimistic that the federal government sees that bringing Native American gaming to Sullivan County will create an economic stimulus for not only Sullivan County, but also the Hudson Valley region and New York State," said legislator Leni Binder.
"The added jobs to the community as well as the revenue from a possible casino hotel would surely add a needed economic boost to the Sullivan County Catskills. The recent interest by retailers looking to locate in Sullivan County will be enhanced by the addition of a casino resort," said legislator Alan Sorenson, who represents the district where the casinos would be located.
Sullivan County manager David Fanslau envisions this as an economic opportunity and one of the major puzzle pieces to secure fiscal vitality once again throughout the county. "The Sullivan County economy will benefit from additional tourism venues and jobs for county residents," Fanslau said.
Legislator Elwin Wood, chairman of the Community and Economic Development Committee, stated "We look forward to the renewed interest in developing a casino in Sullivan County. Such a project could bring upwards of 2,000 permanent jobs and 2,000 construction jobs to the area."
Sullivan County manager David Fanslau envisions this as an economic opportunity and one of the major puzzle pieces to secure fiscal vitality once again throughout the county. "The Sullivan County economy will benefit from additional tourism venues and jobs for county residents," Fanslau said.
Still, only five off-reservation casinos have been approved in the country since the Indian Gaming Regulating Act was passed in 1988, so the tribes and casino supporters may yet have a few hurdles to jump.
Additionally, there will undoubtedly be resistance from some groups who have opposed them in the past. Rasmey Adams, executive director of Catskill Mountainkeeper called the announcement a distraction to all of the other economic development efforts going on in the region. He said further that the environmental impact of multiple casinos in the county will be harmful and that Mountainkeeper will fight the development of the casinos.


text:
K12 outreach at the LAI has focused on offering academic enrichment and professional development opportunities to hundreds of local K-12 educators. The Institute also supports projects and events that engage the interests, knowledge and practices of educators who teach about Latin America.
The LAI provides support for the UCLA Latin American Business Association (LABA) conference, an event designed to increase awareness of business in Latin America, as well as present a Latin American perspective of current global trends and their effects on the region. The conference is held annually on the UCLA campus during the winter or spring quarter.


text:
by Anton Shilov
Even thought the vast majority of personal computers sold are those made to mount on the desk, higher average sale prices of mobile computers are leading to the fact that system integrators are going to earn the bulk of the revenues by selling notebooks, not desktops, analyst firm Merrill Lynch estimates.
By the end of 2006, the estimated percentage of revenue for companies from desktops will be 47%, compared to 41.6% for notebooks. For 2007, the numbers will nearly flip, with 45.6% of revenue coming from notebooks and 43.1% from desktops, according to Farmer's estimates, according to a research by Merrill Lynch, reports eWeek web-site.
There is no proper split between the desktop and notebook systems on the market just now. Nevertheless, it is known that back in Q3 about 76 million graphics adaptors for both desktops and notebooks were shipped, where desktops represented about 53 million units, while the mobile computers represented 22.7 million units. While not very accurate, the figures do show the approximate split between desktop and notebook computer shipments in the third quarter of 2006.
Later, in 2008, notebooks are predicted to represent nearly 50% of revenue, while desktops will produce only about 40% of revenue. By comparison, in 2000, Merrill Lynch reported that notebooks only produced about 25% of the revenue in the PC market, with desktops accounting for a solid majority of 64%, the web-site claims.
The analysts believe that in terms of unit shipments desktops will exceed notebooks in 2008 or, perhaps, in 2009 and only in mature markets, such as the U.S. or Western Europe. According to the Merrill Lynch analysis, the average notebook in 2007 is estimated to cost $1083, while desktops will cost $767 on average.


text:
I think I may have thrush after reading the symptoms someone posted on this link:
For the past week, I have had excuciating pains in my left breast, like sharp stabbing pains in my nipples and then also deep in the breast. It kills when clothes go any where near them. I had thought that maybe we all of a sudden had poor latching but we were doing so well up until then (dd is 6 weeks) so I was skeptical. The wiedest part was that all these little pimple like blisters started appearing on my arms. Thats when I started to suspect thrush.
I currently don't have a doctor and am trying to find one to go to. but in the mean time, what should I do? I know the article said to wash and sterilize everything. Are there foods I should eat or avoid? I would love to hear from others who had this and what their experiences were.


text:
Behind-The-Scenes Of Philips VisaPure Halloween Theme Video
YAY IT'S HALLOWEEN AGAIN!! (Actually it no longer is, at the time of writing, but it was at the time of the shoot. Nevertheless, I love to pretend that it's a day for dressing up every day HOHO)
To prepare for this shoot, there were weeks of conceptualizing and planning! UGH! I don't know why I had to choose a Halloween theme for my Philips Visapure video. #liketomakethingsdifficultformyself. We had A LOT OF FUN though! So glad and grateful to have my girlfriends make time for me.
Shopping for props and costumes took days as well. I had to get appropriate props – we had wayyyy more props than they appeared in the video and pictures, think of how to execute the makeup in the best possible time, and how to do it all with the least possible cost. OMG I even did an Excel spreadsheet for cost budgeting.
What I totally UNDERESTIMATED was the amount of work needed to transform myself into a mummy. *slaps forehead
Oh, Mummy!
I bought 2 types of cloth – a coarse eggshell cloth and a softer light beige one, you know, coz the Egyptians didn't have cloths all dyed the same shade, right?
Luckily my dad helped me with this! I was sulking at the sheer amount of cloth I had to cut when he came and taught me a quick trick. Just cut at the edges,
AND TEARRRR!! So easy! We were done in minutes! 😀
On the day of the shoot I went to collect the props and clown costume from the costume shop (super expensive, please! =.=") and checked in to the hotel.
I tried wrapping myself up. It was very fun – AT FIRST. Then I realized it wasn't easy doing it myself and the cloth kept unwrapping! Grrr!!
So I got started on the makeup, which took like, 10 minutes max to complete. I chose the mummy costume thinking I'd save plenty of time on makeup – no wounds, no blood, no contouring – but the costume took about 10 times as much time. Regret x 10!!


text:
Invaluable cannot guarantee the accuracy of translations through Google Translate and disclaims any responsibility for inaccurate translations.
Coins: Day 5
by TimeLine Auctions
December 10, 2016, 10:00 AM GMT (in progress)
London, United KingdomLive Auction
Lot 3027: English Tudor Coins - Henry VII - Facing Bust Groat(58 views)
|Starting bid:
|Your max bid:
The Invaluable Live! SecureBid™ feature ensures you never overpay. Without disclosing your limit to anyone, SecureBid™ places your bids automatically, up to one increment higher than the last in-room bid or preset reserve, until we have reached your maximum bid.Close
(Enter more than £70)
Estimate: £100 - £140
Description: 1499-1504 AD. Type IIIc. Obv: facing bust with double-arched crown within tressure with HENRIC DI GRA REX AGL Z FR legend and 'upright anchor' mintmark. Rev: long cross and pellets with POSVI DEV ADIVTORE MEV and CIVITAS LONDON legends for London mint with 'inverted anchor' mintmark. S. 2199; N. 1705c. 2.71 grams. .
Condition Report: Very fine.
- You have read and agree with the Auctioneer Terms and Conditions below and the Invaluable Terms of Use Agreement
- You agree to pay a buyer's premium of up to 34% and any applicable taxes and shipping.
28. Collection of Lots and Storage: Once the Buyer has paid the Purchase Price in full, TimeLine will release the Lot to the Buyer for collection. The Buyer must collect, or arrange the collection of, all purchases from the location advised by TimeLine by 4.30pm on the seventh working day following the Date of Sale. Buyers may use the services of Mail Boxes Etc (contact details are provided on TimeLine documentation) or a service of their choice for collection, packing and shipping services. Lots not collected by the seventh working day following the Date of Sale will be moved to storage at a transfer cost of £20 plus VAT per lot and storage charges will thereafter be applied at the rate of £1.90 plus VAT per lot per day until collected; no lots may be removed until any storage costs have been paid in full. In the event that the accrual of storage charges reaches 50% of the Hammer Price paid or after the expiration of three months from the transfer date, whichever occurs first, Timeline reserve the right to re-sell any and all lots stored without notice and in any manner at their sole discretion and to apply any proceeds in defrayment of such costs. The buyer will be entitled to receive any credit balance above the amount of the costs on request but will remain liable for any deficit.
29. Delivery by TimeLine: at the absolute discretion of TimeLine, TimeLine may, on request, directly arrange delivery of certain Lots to the address registered to the Buyer, on payment by the Buyer to TimeLine of any advised handling and delivery charge. TimeLine does not insure property in transit but can arrange insurance at a cost of 6% of the total invoice value or minimum of £10, whichever is the higher; cover being limited to the to the invoiced amount paid for the Lot and subject to a £200 excess on any claim.


text:
WAN Interface Cards Boost Connectivity
The 3G Wireless WAN High-Speed WAN Interface Cards (HWICs) offer a compelling alternative to traditional wireline backup solutions on Cisco 1841/1861,1900 Series, 2800/2900 Series, and 380/3900 Series integrated services routers. Powered by the widely deployed high-speed cellular networks, the cards offer cost-effective primary connectivity for rapid deployments, kiosks, ATMs, and telemetry applications.
The 3G Wireless WAN HWICs provide a, true multipath WAN backup solution that delivers higher performance than dialup/ISDN solutions at a fraction of the cost. The cards deliver WAN connectivity in a fraction of the time required to install a traditional wireline WAN connection.
The 3G Wireless WAN HWICs support the following 2.5G, 3G and 3.5G technologies:
- HWIC-3G-CDMA supports 1xEV-DO Rev A, 1x EV-DO Rev 0, and 1xRTT
- HWIC-3G-HSPA supports HSUPA, HSDPA, UMTS, EDGE, and GPRS
The cards automatically select the best available service based on wireless network availability in the service area.
- WAN backup: Independent of the wireline infrastructure, enhances business resilience and disaster recovery preparedness
- Primary WAN connectivity: Ideal for locations where traditional wired solutions are unavailable, not feasible, or costly
- Rapid deployments or temporary sites: Offers agility to businesses that require instant setup and frequent relocation
- Retail and telemetry: Ideal for low data volumes and high-security applications, such as bank ATMs, kiosks, gas stations, and telemetry sites
Featured Content
- 3G Wireless Coverage and Approved Carriers
Find approved wireless 3G carriers.
- MierCom Report
Cisco 3G Wireless WAN HWIC Performance
Related Documents
(All Cisco High-Speed WAN Interface Cards Data Sheets)
MS Word Template_102504
(All Cisco High-Speed WAN Interface Cards Q&A)


text:
In: Van Driesche, R., et al., 2002, Biological Control of Invasive Plants in the Eastern United States, USDA Forest Service Publication FHTET-2002-04, 413 p.
moister sites. Canada thistle was among the most prevalent weeds on Conservation Reserve Program (CRP) land in Minnesota, occurring in 65 to 75% of CRP fields throughout the state. Canada thistle ground cover in these fields frequently reached 50 to 75%, giving rise to concern about seed dispersal into neighboring agricultural land (Jewett et al., 1996). It was ranked as "urgent" for control in a review of exotic plants at Pipestone National Monument, Minnesota (Hiebert and Stubbendieck, 1993).
Extent of losses. A density of 20 Canada thistle shoots per m2 caused estimated yield losses of 34% in barley (O'Sullivan et al., 1982), 26% in canola (O'Sullivan et al., 1985), 36% in winter wheat (McLennan et al., 1991), and 48% in alfalfa seed (Moyer et al., 1991). Densities of Canada thistle in field infestations can reach 173 shoots per m2 (Donald and Khan, 1996).
Geographical Distribution
Canada thistle occurs in all eastern U.S. states south to Kansas, Arkansas, Tennessee, and North Carolina, but it is sparsely distributed south of latitude 37°N (USDA, NRCS, 1999). The main areas of occurrence are the northeastern, mid-Atlantic, Great Lakes, and northern Great Plains states. In a survey in Maryland, Canada thistle was found in about 17% of suitable sites in the eastern and central part of the state, but only 10% of sites further west (Tipping, 1992).
Background Information On The Pest Plant
Canada thistle is a member of the genus Cirsium, subtribe Carduinae, tribe Cardueae, and family Asteraceae (Bremer, 1994). It differs from most other Cirsium species by its dioecious flowers, and from most native North American members of the genus by its extensive creeping roots and small, numerous flower heads borne on branched stems. Several varieties have been described based on variations in leaf shape and degree of spininess.
The biology of Canada thistle was extensively reviewed by Moore (1975), Donald (1994), and Nuzzo (1997). It is a perennial herb with an extensive creeping root system that can give rise to new shoots from adventitious root buds. The stems usually die back over winter and new shoots are produced each spring from old stem bases or root buds. Canada thistle is almost perfectly dioecious and can produce abundant seeds, which are dispersed by wind (Lloyd and Myall, 1976). It is a long-day plant, requiring a photoperiod of at least 14 to 16 hours (depending on ecotype) for flowering to be induced (Hunter and Smith, 1972). It occurs in a wide range of habitats and soil types.
Analysis of Related Native Plants in the Eastern United States
The genus Cirsium is a large one, with 92 native species in North America, of which 20 occur in the U.S. states that fall wholly or in part east of the 100th meridian (USDA, NRCS, 1999). One of these, Cirsium pitcheri (Torrey) Torrey and Gray, is listed as threatened under the Endangered Species Act. This species occurs in sand dunes along the shores of the Great Lakes in Illinois, Indiana, Michigan, Wisconsin, and Ontario. Phylogenetic studies of North American and Eurasian Cirsium species are needed to elucidate relationships among species in the genus and to provide a basis for planning host-specificity tests and interpreting resulting data. Studies have been initiated using the external transcribed spacer (ETS) region of ribosomal DNA to develop a phylogeny for North American and selected Eurasian Cirsium species (D. Kelch, pers. comm.).
History of Biological Control Efforts in the Eastern United States
Canada thistle was among the first 19 weed species selected as targets for biological control when the USDA Rome Laboratory was established in 1959 (Schroeder, 1980). However, most host specificity testing of agents for Canada thistle was conducted from 1961 to 1984 by staff of Agriculture Canada or by the International Institute of Biological Control (now CABI Bioscience) working with Canadian funding. The agents released in the United States have been those that became available as a result of the Canadian program, the results of which were reviewed by Schroeder (1980), Peschken (1984a), and McClay et al. (2001). Most releases in the eastern United States were made by USDA, ARS staff at the Beltsville Agricultural Research Center; some studies also were carried out by staff of the Maryland Department of Agriculture. Biological control of Canada thistle in New Zealand has been reviewed by Jessep (1989).
Area of Origin of Weed
Canada thistle is native to Europe, parts of North Africa, and Asia south to Afghanistan, Iran and Pakistan, and east to China. Its exact center of origin within the native range is not known, although it is suggested by Moore (1975) to be in southeastern Europe and the eastern Mediterranean area.
Areas Surveyed for Natural Enemies
Extensive surveys of natural enemies of Canada thistle and other Cardueae species in western Europe were carried out starting in 1959. Other surveys have been carried out in Japan, Iran, and northern Pakistan (Schroeder, 1980), and in China (Wan and Harris, unpub. data). Further surveys in southern Russia, central Asia, and China are currently under way (Gassmann, unpub. data). In addition to surveys specifically carried out for biocontrol purposes, the general European entomological literature contains much information on insects associated with Canada thistle (e.g., Redfern, 1983; Stary, 1986; Volkl, 1989; Freese, 1994; Berestetsky, 1997; Frenzel et al., 2000). The phytophagous insects associated with Canada thistle in Poland are listed by Winiarska (1986).
Natural Enemies Found
Surveys by Zwölfer (1965a) in Europe found 78 species of phytophagous insects feeding on Canada thistle. Of these, six are reportedly monophagous, five are found on Canada thistle and a few related species, 26 are oligophagous on plants in the same subtribe, and the remaining 42 are less specific and of no interest for biological control (Schroeder, 1980).
A number of European insects and pathogens attacking Canada thistle have been accidentally introduced into North America, and some of these have been studied as potential biological control agents. The leaf-feeding tortoise beetle Cassida rubiginosa Müller (Coleoptera: Chrysomelidae) occurs widely in the eastern United States, south to Virginia and west to southern Michigan and Ohio, and in Canada (Ward and Pienkowski, 1978a). The seed-feeding weevil Larinus planus (F.) (Coleoptera: Curculionidae) was found by Wheeler and Whitehead (1985) to be well established in Pennsylvania, Maryland, Ohio, and New York, with the earliest records dating from 1968 in Ohio. It has also been collected from Indiana and West Virginia (C. W. O'Brien, pers. comm.). The seed-head fly Terellia ruficauda (F.) (=Orellia ruficauda F.) (Diptera: Tephritidae) is distributed across Canada, and presumably also occurs widely in the eastern United States. A survey showed it to be present in South Dakota (R. Moehringer, S. Dakota Dept. of Agriculture, pers. comm.), and specimens are known from Michigan. The root-feeding weevil Cleonis pigra (Scopoli) (Coleoptera: Curculionidae) occurs in New York, Pennsylvania, Michigan, Indiana, Ontario, and Quebec (O'Brien and Wibmer, 1982; Anderson, 1987; C. W. O'Brien, per. comm.). The rust Puccinia punctiformis (Strauss) Röhling is widespread in North America.
A phytopathogenic bacterium, Pseudomonas syringae pv. tagetis (Hellmers 1955) Young, Dye and Wilkie 1978, causing apical chlorosis, has been isolated from Canada thistle. Field tests of applications of this bacterium in a commercial corn field resulted in 57% mortality of Canada thistle as well as damage to several other weedy Asteraceae species. A surfactant is required to allow penetration of the Canada thistle cuticle by the bacterium. Further work on formulation of this agent is under way (Johnson et al., 1996). The bacterium occurs in Maryland (P. Tipping, pers. comm.).
One species which was introduced as a biological control agent for Carduus species, the seed-head weevil Rhinocyllus conicus (Frölich) (Coleoptera: Curculionidae), also is recorded attacking Canada thistle (Rees, 1977; Youssef and Evans, 1994). This species is widespread in the eastern United States, and has been found attacking Canada thistle in Maryland (P. Tipping, pers. comm.).
Host Range Tests and Results
In the earlier part of the period 1961 to 1984, host specificity testing for agents attacking Canada thistle was focused on assessing potential risks to economic species of Cardueae, of which the two most important are safflower (Carthamus tinctorius L.) and globe artichoke (Cynara scolymus L.). In later studies, some native North American Cirsium species also were tested, but potential impacts of most agents on native non-target Cirsium species were not assessed in detail.
The leaf-feeding beetle Altica carduorum Guérin-Méneville (Coleoptera: Chrysomelidae) is known in the field in Europe mainly from Canada thistle, with a single record of adults from Carduus pycnocephalus L. (Zwölfer, 1965a). The host specificity of a population of A. carduorum from Switzerland was studied by Harris (1964), using starvation tests with adults and larvae. First instar larvae complete development only on Cirsium, Carduus, and Silybum species. Adults feed readily on all Cirsium species tested, which included only two North American species, but their feeding rate is highest on Canada thistle. Similar results were obtained by Karny (1963) and Zwölfer (1965b).
More recently, the host specificity of a biotype of A. carduorum from Xinjiang, China, was assessed by Wan et al. (1996), who found that in no-choice tests this beetle can complete development on 18 Cirsium species (mostly North American) and Silybum marianum (L.) Gaertner. A risk analysis approach, however, predicted that North American Cirsium species would be safe from attack in the field because host selection requires a series of sequential steps, with the native species being less preferred than C. arvense at each stage (Wan and Harris, 1997). It also was suggested that the insect is monophagous in the field because host finding is dependent on aggregation to substances from wounds and feces specific to C. arvense (Wan and Harris, 1996). As the Xinjiang biotype was not approved for field release in North America, it has not been possible to test these predictions in the field.
The only known field host plant of the weevil Ceutorhynchus litura (F.) (Coleoptera: Curculionidae) in Europe is Canada thistle, except for three collections from Carduus defloratus L. in Switzerland (Zwölfer and Harris, 1966). Ceutorhynchus litura was screened by Zwölfer and Harris (1966), who found that feeding, oviposition, and larval development are restricted to species in the genera Cirsium, Carduus, and Silybum. Normal larval development occurs on all Cirsium species tested, including three native North American species. Ceutorhynchus litura was approved for release in Canada and the United States based on its lack of attack on economic Cardueae species. In a more recent European field survey of seven Cirsium and Carduus species by Freese (1994), C. litura was found only in Canada thistle.
The stem- and petiole-galling fly Urophora cardui (L.) (Diptera: Tephritidae) is reported in the field in Europe only from Canada thistle (Zwölfer, 1965a) and the closely related species Cirsium setosum von Bieberstein (sometimes treated as a synonym of C. arvense) (Frenzel et al., 2000). It was screened by Peschken and Harris (1975) against 14 other European Cardueae species and against 11 species, mainly economically important plants, in other tribes and families. In these tests, consistent oviposition was seen only on Canada thistle, with occasional oviposition on Cirsium vulgare (Savi) Ten. and Carduus acanthoides L.
Host specificity tests on the weevil L. planus were conducted by McClay (1989), who found that L. planus will not feed on ornamental or economic species in the tribe Cardueae and that Canada thistle is preferred over other Cirsium species for feeding and oviposition. These tests suggested that small-flowered Cirsium species were more suitable as hosts than native Cirsium species, which generally have larger flower heads. However, Louda and O'Brien (2002) found L. planus reducing seed production of the large-flowered native Cirsium undulatum (Nutt.) Spreng. var. tracyi (Rydb.) Welsh in Colorado, indicating that redistribution of this insect poses greater risks to native species than was previously believed.
Cassida rubiginosa is recorded from numerous species of Arctium, Carduus, Cirsium, Silybum, Onopordum, and Centaurea. In feeding tests, adults and larvae accept species from all these genera, as well as from globe artichoke (Zwölfer and Eichhorn, 1966; Zwölfer, 1969). Spring and Kok (1997) found that C. rubiginosa shows no oviposition preference between Canada thistle and Carduus thoermeri Weinmann; however, mortality of immature stages is lower on Canada thistle. They also observed adults, larvae, and egg masses on burdock, Arctium minus (Hill) Bernhardi, in the field, and reared C. rubiginosa from egg to adult on this species.
Host specificity testing also was conducted on the lace bug Tingis ampliata Herrich-Schäffer (Hemiptera: Tingidae) (Peschken, 1977a) and the leaf beetle Lema cyanella (L.) (Coleoptera: Chrysomelidae) (Peschken and Johnson, 1979; Peschken, 1984b). Tingis ampliata was never released in North America because of concerns about possible attack on globe artichoke, Cynara scolymus L. Limited releases of L. cyanella have been made in Canada but no further releases or redistribution are planned (McClay, unpub. data).
Cleonis pigra attacks numerous species of Cardueae in Europe, and is an economic pest of globe artichoke (LaFerla, 1939; Zwölfer, 1965a; Batra et al., 1981). Terellia ruficauda has been reared from six Cirsium species in Europe (Zwölfer, 1965a).
Releases Made
Information on releases of biological control agents against Canada thistle was obtained from the literature and, for the period between 1981 and 1985, from the USDA, ARS database on natural enemy releases in the United States (ROBO at http://www.ars-grin.gov/nigrp/robo.html). There undoubtedly have been many additional releases that have not been published; for example, 18 releases of C. litura and 12 of U. cardui were made in the eastern part of South Dakota between 1987 and 1984, and L. planus and C. rubiginosa also have been released in this area (R. Moehringer, S. Dakota Dept. of Agriculture, pers. comm.).
Releases of A. carduorum began in 1966, using material from Switzerland via Canada, and were made in Delaware, Indiana, Maryland, Minnesota, New Jersey, South Dakota, and Wisconsin; in 1970, material from France was released in Maryland, New Jersey, and South Dakota (Julien and Griffiths, 1998). Two releases of A. carduorum from a population collected near Rome, Italy, were made in Maryland in 1982. Releases of C. litura began in 1971 (Julien and Griffiths, 1998). This weevil was released in Maryland on 16 occasions from 1982 to 1985 and at one site in New York State in 1984. Most of these releases were made using material imported from Bavaria, Germany, but four releases were made with material from established field populations in Montana.
Urophora cardui was released on nine occasions in Maryland between 1981 and 1984, mostly using material from field collections near Vienna, Austria. Two releases of U. cardui from this source also were made in Iowa in 1982 and 1985. Another series of four releases totaling 4,400 adults from the population in British Columbia, Canada, was made in 1985 in Virginia (Kok, 1990).
Cassida rubiginosa was moved from northern Virginia to a southwestern area of the state where it previously had not occurred (Ward and Pienkowski, 1978a).
Biology and Ecology of Key Natural Enemies
Altica carduorum Guérin-Méneville (Coleoptera: Chrysomelidae)
This species has a Mediterranean and partly Atlantic distribution in Europe (Zwölfer, 1965b). A closely related species, Altica cirsicola Ohno, occurs in China and Japan (Laroche et al., 1996); however, RAPD fingerprinting (a DNA identification method) showed that a population from Xinjiang in western China was A. carduorum (Wan and Harris, 1995). Thus the distribution of A. carduorum extends from the Mediterranean and eastern Europe, through Kazakhstan, Kirghizia and Tadzhikistan to western China (Wan and Harris, 1995).
In Switzerland, overwintering adults of A. carduorum begin to appear on foliage of Canada thistle in mid-April and oviposition starts in early May. Larvae are present on the leaves from mid-May through late July. Newly emerged adults feed heavily on foliage in August and September before leaving the plant to seek overwintering sites (Zwölfer, 1965b). Females oviposit on the underside of Canada thistle leaves, usually laying about 12 eggs per day. Under laboratory conditions, eggs hatch in about 11 days, larval development requires about one month, and pupa develop to adults in 10 to 11 days. Larvae feed on the undersurface of leaves, producing "windows" of clear epidermis. Adult feeding damage is evenly dispersed over the whole plant; heavy adult feeding can cause the collapse of plants both in the laboratory and in the field (Karny, 1963).
Cassida rubiginosa Müller (Coleoptera: Chrysomelidae)
This univoltine shield beetle feeds on foliage of several Cardueae species, both as adults and larvae. In Virginia, adults appear in late winter and oviposit, mainly on the underside of thistle leaves, from mid-March to early July. Eggs are laid in oothecae containing about five eggs. Development from egg to adult requires 435 degree-days above a threshold of 10.4°C. New generation adults begin to appear in late spring and can be found on plants up to November. Females produce an average of 815 eggs under laboratory conditions (Ward and Pienkowski, 1978a).
In the field, C. rubiginosa is attacked by several larval parasitoids including Tetrastichus rhosaces (Walker) (Hymenoptera: Eulophidae) and Eucelatoriopsis dimmocki (Aldrich) (Diptera: Tachinidae) (Ward and Pienkowski, 1978b). However, Ang and Kok (1995) felt that parasitism did not limit C. rubiginosa populations in Virginia. Tipping (1993) found that adults released on Canada thistle in Maryland remained in close proximity to the release point and that most oothecae were laid within 1.6 m of the release point. Parasitism in this study was 10.5%, with the most common parasitoid being E. dimmocki. Larvae and pupae are heavily predated by larvae of Coccinella septempunctata L. (Coleoptera: Coccinellidae) in Maryland (P. Tipping, pers. comm.). Spring and Kok (1999) found about 21% overwintering survival of adult C. rubiginosa.
Ceutorhynchus litura (F.) (Coleoptera: Curculionidae)
This stem- and root-mining weevil occurs in France, Switzerland, Austria, Germany, Britain, and southern Scandinavia (Zwölfer and Harris, 1966) (Fig. 3). Females oviposit into the mid-veins of rosette leaves of Canada thistle leaves in spring. Eggs are laid in groups of one to five in a cavity made with the rostrum in the underside of a young leaf. Larvae hatch after five to nine days and mine down through the vein into the base of the stem and upper tap root (Fig. 4). There they form a feeding tunnel that may cause the stem to become somewhat inflated into an indistinct gall. Mature larvae leave the stem and pupate in a cocoon of soil particles, from which they emerge in late summer (Zwölfer and Harris, 1966; Peschken and Beecher, 1973). Adults overwinter in the soil or leaf litter.
Cleonis pigra (Scopoli) (Coleoptera: Curculionidae)
Adults of this large weevil emerge from overwintering sites in May and feed on Canada thistle foliage in June and July. The females oviposit into the lower portions of Canada thistle stems. The larvae mine down through the stem base into the root, which develops a spindle-shaped gall around the feeding site. Pupation occurs in the root, and adults emerge in late summer or fall (Anderson, 1956).
Larinus planus (F.) (Coleoptera: Curculionidae)
Adults of this weevil (Fig. 5) feed on Canada thistle foliage, but generally cause little damage. Females oviposit into the unopened flower buds, where larvae feed on the developing achenes and receptacle tissue. Larvae pupate in a cocoon formed of chewed host plant tissue (Fig. 6.). Only one larvae can complete development in each head. Adults emerge in late summer and overwinter in the litter (McClay, 1989).
Puccinia punctiformis Strauss (Röhling) (Uredinales: Pucciniaceae)
This fungus is an autecious brachycyclic rust that produces systemic infections on the spring-emerging shoots of Canada thistle. Systemically infected shoots are pale and die before flowering, but spermogonia and uredosori are formed before plant death. Later in the season, infection of other shoots by uredospores leads to local infection followed by the formation of teliospores in autumn (Van Den Ende et al., 1987). Teliospores are responsible for the systemic form of infection (Van Den Ende et al., 1987; French and Lightfield, 1990). Germination of teliospores is stimulated by volatile compounds from germinating Canada thistle seeds and root cuttings (French et al., 1988; French et al., 1994). The germination rate of teliospores is highest in the temperature range of 10°C to 15°C (Frantzen, 1994). Systemic infection may be induced in the laboratory in root buds or seeds inoculated with teliospores (French and Lightfield, 1990; French et al., 1994), but it is not yet clear how root infection from teliospores could take place in the field (French et al., 1994). Systemically infected shoots are taller than uninfected ones but fail to flower and their root biomass is reduced (Thomas et al., 1994). Cumulative mortality of infected shoots in a field study in Maryland was 80% compared with less than 10% for healthy shoots (Tipping, 1993).
Terellia ruficauda (F.) (Diptera: Tephritidae)
Ovipositing females of this fly select female Canada thistle flower heads one day away from blooming. Eggs are laid between immature florets and the larvae feed on developing achenes through a hole drilled in the pericarp. Third instar larvae form cocoons of pappus hairs in which they overwinter; pupation and emergence take place in the spring (Lalonde and Roitberg, 1992).
Urophora cardui (L.) (Diptera: Tephritidae)
This univoltine stem-galling fly oviposits in the axillary buds of Canada thistle (Fig. 7). The eggs hatch in seven to 10 days. Larvae induce development of multi-chambered galls in the form of a swelling in the stem up to 23 mm in diameter (Lalonde and Shorthouse, 1985) (Fig. 8). Pupation and overwintering
Evaluation of Project Outcomes
Establishment and Spread of Agents
There is no evidence that A. carduorum has become established in the United States. Peschken (1977b) attributed the failure of this species to establish in Canada to predation. Ceutorhynchus litura is reported to be established in Maryland, North Dakota, South Dakota, and Virginia (Julien and Griffiths, 1998; P. Tipping, pers. comm.). Urophora cardui is reported to be established in Maryland and Virginia (Julien and Griffiths, 1998), although the species is probably not currently established in Maryland (P. Tipping, pers. comm.). Galls of U. cardui were found at all Virginia field sites visited in 1986 but at only two sites in 1987; however, numbers of galls had increased at these two sites in 1987 (Kok, 1990). No recoveries are recorded in Virginia since 1987. Urophora cardui is common along the Hudson River and in other areas in New York state (B. Blossey, pers. comm.). Its establishment status in Iowa is unknown. C. rubiginosa became established in southwestern Virginia and has persisted there for more than 20 years (Ang and Kok, 1995).
Suppression of Target Weed
There has been little work done to evaluate the effectiveness of biological control agents for Canada thistle in the eastern United States. Using Canada thistle root cuttings transplanted to caged field plots, Ang et al. (1995) showed that feeding by C. rubiginosa significantly reduced biomass and survival of Canada thistle. The effects of C. rubiginosa were stronger than those of plant competition from tall fescue (Festuca arundinacea Schreb.) and crownvetch (Coronilla varia L.). Similar results were obtained by Bacher and Schwab (2000) in Switzerland.
Forsyth and Watson (1986) evaluated the stress inflicted on Canada thistle by four insect species and one pathogen in Québec, Canada. The seed head predator O. ruficauda reduced seed production by about 22%. Root mining by C. pigra sometimes killed plants. Main shoot galling by U. cardui reduced plant height and number of flowers, but side-shoot galling had less impact. Reports of the impact of C. litura have been varied. Based on field sampling, Rees (1990) suggested that this species had a significant impact on survival of Canada thistle in Montana. Peschken and Derby (1992), however, found in controlled experiments that combined attack by this species and U. cardui had no significant effect on most performance parameters of Canada thistle. The impact of biological control of Canada thistle in terms of economic benefits or recovery of native plant communities has not been evaluated.
Recommendations for Future Work
Future Needs for Importation or Evaluation
The impact of currently established agents needs to be evaluated by controlled experimental methods, preferably using naturally-occurring densities of agents in field weed stands (McClay, 1995). The extent of non-target damage from the currently established agents also need to be further assessed. Such damage has been shown repeatedly for the seed weevil R. conicus, released as a biocontrol agent for Carduus and Silybum species (Rees, 1977; Louda, 1999; Herr, 2000). As with R. conicus, most of the agents released against Canada thistle have laboratory host ranges that include many native Cirsium species, but it is not known whether any of these native species are in fact being damaged, or are at risk of damage, in the field. Information on this would provide a valuable test of the reliability of laboratory host-range tests in predicting non-target utilization in the field.
The European range of Canada thistle has been extensively explored for potential biocontrol agents, and it seems unlikely that there are promising agents yet undiscovered in this region. Further exploration in Central Asia and China may identify other possible candidate agents, and such exploration is planned (A. Gassmann, pers. comm.).
Other Comments
Canada thistle may be a difficult target for biological control for two reasons. Firstly, it is a significant agricultural weed in its native range in Europe (Schroeder et al., 1993), suggesting that its natural enemies there are not very effective in limiting its population density, at least under agricultural conditions. There has been little study of the impact of herbivory on natural populations of Canada thistle in Europe; however, Edwards et al. (2000) found that exclusion of insects with chemical pesticides had no effect on recruitment or density of Canada thistle in cultivated soil or grassland in southern England. Secondly, Canada thistle is congeneric with a large number of native North American Cirsium species, raising concerns about non-target damage to native species by introduced biological control agents (Louda, 1999; Louda and O'Brien, 2002). Although some phytophagous insects associated with Canada thistle, such as U. cardui, appear to be virtually monophagous, others have a broad host range within the genus Cirsium and also will accept species of Carduus or related genera. In the past, several agents have been approved for release against Canada thistle on the basis of host specificity tests that would not be considered sufficient justification for release today.
Future progress in classical biological control of Canada thistle will depend on the identification of new, adequately host specific herbivores from its native range, and will require improvements in host-testing procedures to allow better prediction and evaluation of non-target impacts.
I thank Philip Tipping, André Gassmann, Dean Kelch, Charles O'Brien, and Ron Moehring for comments on the manuscript and for providing unpublished information.
Anderson, D. M. 1956. Notes on Cleonus piger (Scop.) in the United States (Coleoptera, Curculionidae).
Anderson, R. S. 1987. Systematics, phylogeny and biogeography of New World weevils of the tribe
Ang, B. N. and L. T. Kok. 1995. Seasonal mortality of Cassida rubiginosa (Coleoptera, Chrysomelidae)
Ang, B. N., L. T. Kok, G.I. Holtzman, and D.D. Wolf. 1995. Canada thistle [Cirsium arvense (L.) Scop]
Bacher, S. and F. Schwab. 2000. Effect of herbivore density, timing of attack and plant community on
Batra, S. W. T., J. R. Coulson, P. H. Dunn, and P. E. Boldt. 1981. Insects and fungi associated with
Berestetsky, A. O. 1997. Mycobiota of Cirsium arvense and allied species over the territory of the
Bremer, K. 1994. Asteraceae: Cladistics and Classification. Timber Press, Portland, Oregon, USA.
Donald, W. W. 1994. The biology of Canada thistle (Cirsium arvense). Reviews of Weed Science 6: 77-
Donald, W. W. and M. Khan. 1996. Canada thistle (Cirsium arvense) effects on yield components of
Edwards, G. R., G. W. Bourdôt, and M.J. Crawley. 2000. Influence of herbivory, competition and soil
Forsyth, S. F. and A. K. Watson. 1986. Stress inflicted by organisms on Canada thistle, pp. 425-431.
Frantzen, J. 1994. The effect of temperature on the germination of teliospores of Puccinia punctiformis.
Freese, G. 1994. The insect complexes associated with the stems of seven thistle species.
French, R. C. and A. R. Lightfield. 1990. Induction of systemic aecial infection in Canada thistle
French, R. C., S. K. Turner, P. E. Sonnett, P. Pfeffer, and E. Piotrowski. 1988. Properties of an extract
French, R. C., S. E. Nester, and R. G. Binder. 1994. Volatiles from germinating Canada thistle seed
Frenzel, M., S. Eber, S. Klotz, and R. Brandl. 2000. Ecological comparisons across geographical
Harris, P. 1964. Host specificity of Altica carduorum Guer. (Coleoptera: Chrysomelidae). Canadian
Herr, J. C. 2000. Evaluating non-target effects: the thistle story, pp. 12-17. In Hoddle, M. (ed.).
Hiebert, R. D. and J. Stubbendieck. 1993. Handbook for Ranking Exotic Plants for Management and
Hunter, J. H. and L. W. Smith. 1972. Environment and herbicide effects on Canada thistle ecotypes
Jessep, C. T. 1989. Cirsium arvense (L.) Scopoli, Californian thistle (Asteraceae), pp. 343-345. In
Jewett, J. G., C. C. Scheaffer, R. D. Moon, N. P. Martin, D. K. Barnes, D. D. Breitbach, and N. R.
Johnson, D. R., D. L. Wyse, and K. J. Jones. 1996. Controlling weeds with phytopathogenic bacteria.
Julien, M. H. and M. W. Griffiths (eds.). 1998. Biological Control of Weeds: A World Catalogue of
Karny, M. 1963. Haltica carduorum Guer. (Col.: Chrysomelidae) attacking Cirsium arvense. Technical
Kok, L. T. 1990. Biological control of weeds in Virginia from 1969-86, pp. 623-629. In Delfosse, E. S.
LaFerla, A. 1939. Contributo alla conoscenza dei cleono del carciofo (Cleonus piger Scop.). Bolletino
Lalonde, R. G. and B. D. Roitberg. 1992. Field studies of seed predation in an introduced weedy thistle.
Lalonde, R. G. and J. D. Shorthouse. 1985. Growth and development of larvae and galls of Urophora
Laroche, A., R. A. De Clerck-Floate, L. Lesage, K. D. Floate, and T. Demeke. 1996. Are Altica
Lloyd, D. G. and A. J. Myall. 1976. Sexual dimorphism in Cirsium arvense (L.) Scop. Annals of Botany
Louda, S. M. 1999. Negative ecological effects of the musk thistle biological control agent, Rhinocyllus
Louda, S.M. and C.W. O'Brien. 2002. Unexpected ecological effects of distributing the exotic weevil,
McClay, A. S. 1989. The potential of Larinus planus (F.) (Coleoptera: Curculionidae), an accidentally
McClay, A. S. 1995. Beyond "before-and-after": experimental design and evaluation in classical weed
McClay, A. S., R. Bourchier, R. A. Butts, and D. P. Peschken. 2001. Cirsium arvense (L.) Scopoli,
McLennan, B. R., R. Ashford, and M. D. Devine. 1991. Cirsium arvense (L.) Scop. competition with
Moore, R. J. 1975. The biology of Canadian weeds. 13. Cirsium arvense (L.) Scop. Canadian Journal of
Moyer, J. R., G. B. Schaalje, and P. Bergen. 1991. Alfalfa (Medicago sativa) seed yield loss due to
Nadeau, L. B. and W. H. Vanden Born. 1989. The root system of Canada thistle. Canadian Journal of
Nuzzo, V. 1997. Element Stewardship Abstract for Cirsium arvense. The Nature Conservancy,
O'Brien, C. W. and G. J. Wibmer. 1982. Annotated checklist of the weevils (Curculionidae sensu lato)
O'Sullivan, P. A., V. C. Kossatz, G. M. Weiss, and D. A. Dew. 1982. An approach to estimating yield
O'Sullivan, P. A., G. M. Weiss, and V. C. Kossatz. 1985. Indices of competition for estimating
Peschken, D. P. 1977a. Host specificity of Tingis ampliata (Tingidae: Heteroptera): a candidate for the
Peschken, D. P. 1977b. Biological control of creeping thistle (Cirsium arvense): analysis of the releases
Peschken, D. P. 1984a. Cirsium arvense (L.) Scop., Canada thistle (Compositae), pp. 139-146. In
Peschken, D. P. 1984b. Host range of Lema cyanella (Coleoptera: Chrysomelidae), a candidate for
Peschken, D. P. and R. W. Beecher. 1973. Ceutorhynchus litura (Coleoptera: Curculionidae): biology
Peschken, D. P. and J. L. Derby. 1992. Effect of Urophora cardui (L.) (Diptera: Tephritidae) and
Peschken, D. P. and P. Harris. 1975. Host specificity and biology of Urophora cardui (Diptera:
Peschken, D. P. and G. R. Johnson. 1979. Host specificity and suitability of Lema cyanella
Redfern, M. 1983. Insects and Thistles. Cambridge University Press, New York.
Rees, N. E. 1977. Impact of Rhinocyllus conicus on thistles in southwestern Montana. Environmental
Rees, N. E. 1990. Establishment, dispersal and influence of Ceutorhynchus litura on Canada thistle (
Schroeder, D. 1980. The biological control of thistles. Biocontrol News and Information 1: 9-26.
Schroeder, D., H. Müller-Schärer, and C. S. A. Stinson. 1993. A European weed survey in 10 major
Skinner, K., L. Smith, and P. Rice. 2000. Using noxious weed lists to prioritize targets for developing
Spring, A. and L. T. Kok. 1997. Field studies on the reproductive capacity and development of Cassida
Spring, A. and L. T. Kok. 1999. Winter survival of Cassida rubiginosa (Coleoptera: Chrysomelidae), a
Stachon, W. J. and R. L. Zimdahl. 1980. Allelopathic activity of Canada thistle (Cirsium arvense) in
Stary, P. 1986. Creeping thistle, Cirsium arvense, as a reservoir of aphid parasitoids (Hymenoptera,
Thomas, R. F., T. J. Tworkoski, R.C. French, and G.R. Leather. 1994. Puccinia punctiformis affects
Tipping, P.W. 1992. Density of Carduus and Cirsium thistles in selected areas of Maryland. Weed
Tipping, P.W. 1993. Field studies with Cassida rubiginosa (Coleoptera: Chrysomelidae) in Canada
USDA, NRCS (United States Department of Agriculture, Natural Resources Conservation Service).
Van Den Ende, G., J. Frantzen, and T. Timmers. 1987. Teleutospores as origin of systemic infection of
Volkl, W. 1989. Resource partitioning in a guild of aphid species associated with creeping thistle
Wan, F.-H. and P. Harris. 1995. Biology, host specificity and suitability of the Wusu, NW China biotype
Wan, F. H. and P. Harris. 1996. Host finding and recognition by Altica carduorum, a defoliator of
Wan, F. H. and P. Harris. 1997. Use of risk analysis for screening weed biocontrol agents – Altica
Wan, F.H., P. Harris, L.M. Cai, and M.X. Zhang. 1996. Host specificity of Altica carduorum Guer.
Ward, R. H. and R. L. Pienkowski. 1978a. Biology of Cassida rubiginosa, a thistle-feeding shield beetle.
Ward, R. H. and R. L. Pienkowski. 1978b. Mortality and parasitism of Cassida rubiginosa, a thistle-
Wheeler, A. G., Jr. and D. R. Whitehead. 1985. Larinus planus (F.) in North America (Coleoptera:
Winiarska, W. 1986. Roslinozerna entomofauna ostrozenia polnego, Cirsium arvense (L.) Scop.
Youssef, N. N. and E. W. Evans. 1994. Exploitation of Canada thistle by the weevil Rhinocyllus conicus
Zwölfer, H. 1965a. Preliminary list of phytophagous insects attacking wild Cynareae (Compositae) in
Zwölfer, H. 1965b. Observations on the distribution and ecology of Altica carduorum Guer. (Col.
Zwölfer, H. 1969. Experimental feeding ranges of species of Chrysomelidae (Col.) associated with
Zwölfer, H. and O. Eichhorn. 1966. The host ranges of Cassida (Col.: Chrysomelidae) species attacking
Zwölfer, H. and P. Harris. 1966. Ceutorhynchus litura (F.) (Col., Curculionidae), a potential insect for the
[ Contents ] [ Previous ] [ Next ]
| The Bugwood Network and Forestry Images Image Archive and Database Systems
The University of Georgia - Warnell School of Forest Resources and
College of Agricultural and Environmental Sciences - Dept. of Entomology
Last updated on Thursday, December 12, 2002 at 10:15 AM
Questions and/or comments to the


text:
According to military sources and witnesses, more than 100 people, including rebels and government soldiers, were killed during an air assault by French forces. MSNBC's Thomas Roberts reports.
French fighter jets pounded an Islamist rebel stronghold in northern Mali Sunday as Paris poured more troops into the capital Bamako.
France is determined to end Islamist domination of north Mali, which many fear could act as a base for attacks on the West and for links with al-Qaida in Yemen, Somalia and North Africa.
The attack on Gao, the largest city in the desert region controlled by the Islamist alliance, marked a decisive intensification on the third day of French air raids, striking at the heart of the vast territory seized by rebels in April. The rebels have occupied the northern two-thirds of the poor West African country.
Upward of 200 rebels have reportedly died in the firefight. Malian authorities said 11 soldiers were killed during a battle in Konna, and about 60 others were wounded.
Nicolas Vissac / ECPAD via AFP - Getty Images
A handout photo released by the French Army shows a French military preparing a Mirage 2000D fighter plane at the French military base of N'Djamena, Chad.
France has deployed about 550 soldiers to Mali for "Operation Serval" – named for an African wildcat. France is leaning on African nations to also contribute troops for an operation that the United Nations has stressed should be "African-led, African-owned."
Ivory Coast President Alassane Ouattara immediately pledged 3,300 African soldiers. Former French colonies Senegal, Niger and Burkina Faso have all pledged to deploy 500 troops within days.
Algeria, which shares a northern border with Mali, has allowed France to make full use of its airspace, said French Foreign Minister Laurent Fabius. Fabius said he was grateful for Algeria's support given that the country's leadership have pushed for a political solution over a military intervention, worried that al-Qaida militants and refugees would be pushed into southern Algeria.
The United States is considering sending a small number of unarmed surveillance drones to Mali as well as providing logistics support, a U.S. official told Reuters. Britain and Canada have also promised logistical support.
As fighting took place in the north, Bamaka was calm, with the sun streaking through the dust enveloping the city. Some cars drove with French flags draped from the windows to celebrate the French intervention.
Hundreds of Malians lined up to donate blood destined for their troops locked in a fierce battle against Islamist rebels occupying the northern two-thirds of the poor West African country.
The road ahead could be hugely expensive and last months, not weeks, warned Reuben Brigety, one of the U.S. State Department's leading officials for Africa.
"A massive, massive undertaking," he said when he spoke at London's Chatham House in late October. "That is incredibly difficult terrain; it's a vast expanse. It will take a long time to take and hold."
-- Reporting by Reuters' reporters Bate Felix, Chine Labbe, John Irish, William Maclean, Catherine Bremer, Lamine Chikhi, Adama Diarra, Tiemoko Diallo, Rainer Schwenzfeier, Joe Bavier, Leila Aboud, Phil Stewart.


text:
People in the small Hawaii hometown of Manti Te'o are offering support for the Notre Dame linebacker after the story of his girlfriend and her death from Leukemia were revealed as a hoax.
No one answered the door Wednesday evening at Te'o's parents' home in the small coastal town of Laie on Oahu's northern shore where Te'o was born.
But members of the mostly Mormon community said they were dumbfounded, and didn't believe he would have knowingly perpetrated such a story.
Neighbor Katherine Lindsay, a retiree sitting in front of her home talking with friends, says she knows how people are raised in the community, and she could not go along with the idea that Te'o could be involved in the deception.
Notre Dame officials confirmed that the story was a hoax, but insist Te'o was the victim.
Former University of Hawaii running back Reagan Mauia, now with the Arizona Cardinals, told ESPN that he actually met Lennay Kekua, which was the name of Te'o's girlfriend, when he and other NFL players did charity work in American Samoa in June 2011.
"This was before her and Manti," Mauia said. "I don't think Manti was even in the picture, but she and I became good friends. We would talk off and on, just checking up on each other kind of thing. I am close to her family. When she was going through the loss of her father, I was -- I offered a comforting shoulder and just someone to bounce her emotions off. That was just from meeting her in Samoa."
According to Deadspin.com, Ronaiah Tuiasosopo was the mastermind behind the hoax.
Mauia says he believes Tuiasosopo is Kekua's cousin and introduced him to Kekua.
"She was tall," he said. "Volleyball-type of physique. She was athletic, tall, beautiful. Long hair. Polynesian. She looked like a model ... "
Tuiasosopo is a cousin of NFL quarterback Marques Tuiasosopo, according to ESPN.
Mauia says he believes Kekua's mother is operating her Twitter account, although he never met her mother.
When Mauia was told by a reporter that Kekua apparently might not have existed, he responded, "No, she is real."


text:
Must-have electronics this holiday season
Published On: Nov 15 2012 12:25:17 PM CST Updated On: Dec 12 2012 01:00:13 AM CST
When shopping this season for those who love electronics, check out these popular items.
The views expressed are not those of this company or its affiliated companies. Please note by clicking on "Post" you acknowledge that you have read the Terms Of Service and the comment you are posting is in compliance with such terms.


text:
Affectionately termed "Scrappys", these stuffed cats and dogs are 10 inches long with a slim body design. Because they are made from leftover clothing scraps, colors are assorted. Each Scrappy is a surprise! Made from 100% GOTS certified organic Egyptian cotton.
Washing Instructions
Machine wash only. Tumble dry until toy is completely dry. To speed up the drying process, place a bath towel in the dryer with the toy.
100% Satisfaction Guarantee
We want you to be completely satisfied with every purchase you make. If you are in any way dissatisfied with a product you ordered, we'll exchange it, replace it or refund your money within 30 days of purchase. Simply email us the problem, and we'll take care of you. Certain products have extended warranties (up to 50 years!) that are listed on the particular product page. Please call us at 1-888-451-6752 if you need further clarification.
Additional Information
|3 oz.
Shipping Information
- Shipping Details:
- Insured against damage or loss while in transit
- This Product Ships To:
- US Lower 48
- Ships Via:
- Fedex, UPS, or USPS
Questions about the Scrappy Toys - Dogs and Cats
No questions asked yet
Ask Your Own Question
- No-hassle, 30 day returns
- No sales tax
- Quick shipping
- Secure shopping (SSL, PCI, McAfee Secure)
- In business since 2000
- Member of Better Business Bureau, Green America, and US EPA Watersense
- Carbon-neutral, Family-owned business that promotes sustainability!


text:
- Home
- Search for Research Summaries, Reviews, and Reports
EHC Component
- DEcIDE Project
Topic Title
- Outcomes of COPD Management
Full Report
- Research Report Dec. 4, 2009
Related Links for this Topic
- Lee TA, Schumock GT, Bartle B, et al. Mortality risk in patients receiving drug regimens with theophylline for chronic obstructive pulmonary disease. Pharmacotherapy 2009;29:1039-53.
- Pickard AS, Lee TA, Solem CT, et al. Prioritizing comparative-effectiveness research topics via stakeholder involvement: an application in COPD. Clin Pharmacol Ther 2011 Nov 2 [Epub ahead of print]. PMID: 22048220.
Abstract - Final
Outcomes of COPD Management
Topic Abstract
The prevalence of chronic obstructive pulmonary disease (COPD) is high in the United States and continues to increase. Medication management is an integral part of treatment for patients with COPD. However, there remains a great deal of uncertainty in the optimal medication management of patients with COPD and a need for long-term evaluations of medication treatment outcomes in patients with COPD to better inform decisions when caring for these patients. The goal of this project is to identify and prioritize key questions related to the management of patients with COPD and conduct an analysis of the key question(s). The specific objectives for this project are:
- Identify, review and assess major administrative, utilization, and/or claims databases, under the auspice of federal/state governments, third party payers, health plans/networks, or provider consortiums, that contain relevant prescription drug, surgical, outcome and utilization data for people with COPD;
- Identify a set of clinically relevant key questions relating to effectiveness of medical therapy for patients with COPD which can be adequately evaluated using the identified data sets; and
- Conduct a secondary data analysis to evaluate the key question(s), for outcomes including mortality, outpatient and inpatient hospitalization, and COPD-related hospitalizations and ED visits.
The project will be completed in three phases, with a phase dedicated to each of the specific aims. The project has the potential to provide information relevant to health care provider organizations in policy formation about pharmacotherapy for COPD.
*To receive a print copy of either of these reports, send a request to email@example.com. Please include the report title(s) and a complete mailing address. For electronic copies of the report(s), please visit the appropriate journal Web site


text:
The Dish
Tag: calories
At PB and WPB Starbucks locations: Whatcha consuming by the numbers
- 6:14 pm Thursday, June 20th, 2013 by M.M. Cloutier
Starting this Tuesday at your favorite local Starbucks location—the one on Worth Avenue, say, or on downtown West Palm Beach's Clematis Street—the number of calories in your favorite creamy frappuccino just might stare you down.
Starbucks Coffee Company has announced that beginning June 25, its will post calorie information on menu boards at all company-operated and licensed Starbucks stores across the country.
Look for calorie counts to be indicated on wrapped items in pastry cases, too.
Starbucks already lists calories and other nutritional information for its products at www.starbucks.com.
A federal mandate the F.D.A. is fine-tuning before who-knows-when implementation would require chain restaurants and [More]
Posted in Menus


text:
So after 5 yrs, 3 months, and 1 day - my DD (first child) weaned. The worst thing is I somehow feel like I failed her. She nursed through 2 pregnancies and triandum nursed (with 2 little brothers) for basically the last 18 months. At the beginning of September, I showed her the calendar and asked what day she wanted to wean. She picked the very last day (smart girl). So, last night we rocked and nursed one last time. I sang to her all the songs I sang over the last 5+ years. I was crying by the time I sang the "pop off" song. She was crying too (although I think it was because I was crying). She asked me if I missed her being a baby. I said no - I love the person she is now and wouldn't trade it for anything. I told her I was sad that part of our relationship was over and I would miss nursing her. We hugged and cuddled and she fell asleep. It was a special memory.
I just feel like I failed because I so wanted it to be her choice. And it was clearly me encouraging her to wean. I recently found out I was pregnant again, and there is no way I can nurse 3 kids through a pregnancy. I somehow feel like I failed, even though I know I didn't.
Wow, if I feel like this with my first weaning - what is it going to feel like when I nurse for the very last time ever?