text:
Tuesday, November 9, 2010
Over 50 Blogger Spotlight:Mispapelicos
How do you feel age affects fashion?
To me age is just a number, and shouldn't´t affect your own style at all.
What is your style advice for older women stuck in a rut?
-Get rid of the comfy pants and t-shirt, they are a deadly trap…
-Look at yourself in the mirror, cherish the way you look, and build from there.
- Be daring rather than boring.-
-Every woman knows what suits her and what type of clothes makes her feel wonderful. Most of the time, they cannot be bothered.-
-It is never too late to find your own style. Look deep within and let it come out freely.
Can you share any of your style secrets?
I always dress for myself, and to inspire those who cross my path.
-I would like to think that my style is quirky rather than smart; with the knowledge to distinguish the thin line between quirky and clown.
Sacramento in her own words:
I am An English- Spanish teacher and Nutritionist who has been madly in love with fashion all her life.I see fashion as a means of self expression through clothes.
I have been keeping notes and cut-outs in notebooks, (that´s why the name of my blog: MIS PAPELICOS - my little papers or cut-outs) for as long as I can remember.
Last 7Th of April , I decided to go a step forward by starting my own blog.
23 comments:
- Vintage Vixen said...
Sacramento is one of my favourites, she is such a stylish inspiration and a truly lovely person, too. If I had half of her creativity I'd be a happy girl. xxx
- November 9, 2010 at 10:43 AM
- the Citizen Rosebud said...
SHE is so AMAZING! I type this in all caps because her style and spirit make me want to yell. She is full of life, and you can tell lives her life fully. It shows in her sartorial choices. LOVE what she wears but even more so HOW she wears it. A true fashion maverick and icon.
- November 9, 2010 at 11:46 AM
- melina bee said...
thanks for introducing me to her blog, she has really fun style and I'm glad she hasn't eschewed colors as so many women seem to do as they get above 50.
I think it's a good point she makes about comfy clothes being a trap. I read a Tim Gunn interview where he said that not being 100% comfortable is how good clothes should be; he means that in the real world we must be at least a little alert to our surrounding and that we would be too comfortable for alertness if we all wore pjs everyday.
thanks again
- November 9, 2010 at 12:32 PM
- melina bee said...
ps: is it just me, or are a lot of your muses involved in both fashion and nutrition? I imagine the two are connected to the sense of youthful buoyancy your "models" usu. portray
- November 9, 2010 at 12:35 PM
- sacramento said...
Thanks a lot for this marvelous post.I am honoured.
You are wonderful Ari.
Un abrazo siempre.
- November 9, 2010 at 1:26 PM
- masQmay said...
She has personality, attitude, punch and fun, real character!!!
- November 9, 2010 at 1:53 PM
- JamiSings said...
I'm totally jealous that she has that awesome purple jacket and that beautiful blue dress. I want those myself!
- November 9, 2010 at 2:33 PM
- Katie said...
great post! i love that there are style bloggers over 50! That means I can post great outfit pictures til the day i die. and can still have great style with age
- November 9, 2010 at 3:03 PM
- That's Not My Age said...
I agree with Vix. Sacramento is lovely and stylish, she always has fun with fashion.
- November 9, 2010 at 3:25 PM
- The Elegant Bohemian said...
She so articulately expresses exactly how I feel about style. Thanks for introducing her to us! As a 44 year old style lover, I'm inspired and motivated! ~Serene
- November 9, 2010 at 4:33 PM
- fashionoverfifty said...
I'm a follower! Love her confidence~
- November 9, 2010 at 6:54 PM
- skim said...
ooh.. I'm jealous of her fantastic outfits.
- November 9, 2010 at 10:22 PM
Wow!! Would love to get into her wardrobe and play!!
- November 10, 2010 at 4:25 AM
- FASHIÓN (con acento) said...
Sacramento: te queremos!!!!
Estaba convencida q aparecerías tarde o temprano en este blog, para mi uno de los mejores!
te lo mereces!
- November 10, 2010 at 10:21 AM
- Veshoevius said...
So glad you featured her! Love her blog and she is a constant inspiration.
- November 11, 2010 at 11:20 AM
- fashionsdirtylaundry said...
I love how she just has fun with it!
- November 11, 2010 at 2:26 PM
- Terri said...
This is fantastic! Thank you for featuring our friend Sacramento!
- November 12, 2010 at 1:49 AM
- b said...
Thank you very much for the mention...you must realize the influence of such a kindness.
- November 16, 2010 at 9:41 PM
- Judith Anna said...
I Love this woman.... she always looks amazing and is one of my favorite bloggers out there.
Fabulous to mention her, she belongs on Advanced Style!! Bisou Anna
- August 30, 2011 at 4:05 AM
- Peanut said...
I follow Sacramento's blog and am completely inspired by her! Thanks for featuring this amazing lady!
- August 31, 2011 at 8:45 AM
- Misfits Vintage said...
Sacramento is a beautiful woman and a style inspiration - I am so pleased you are spotlighting her!
Sarah xxx
- August 31, 2011 at 8:03 PM
- theequinebovine said...
damn , she's cool.
- October 20, 2011 at 1:17 AM
- the random dressmaker said...
oh i love her blog. She bought a skirt from me last year... I was very flattered to see her wearing it on the blog
- April 5, 2013 at 4:16 PM


text:
Koolatron 84 Gallon Pond Kit
$69.99 $59.99 You Save $10.00 or 14%
Item # 3687317
|Eligible for Free Shipping on Orders $39 or More! (see promotion details)
|Members of The League get 5% back when you spend $100! (see promotion details)
Product Details
If you're thinking about adding a beautiful water feature to your yard's landscape, you'll love the Koolatron 84-gallon pond kit. It includes everything you need to construct a beautiful, low-maintenance water garden.
- Koolatron 84-gallon pond kit
- 6' x 6' non-toxic pond liner
- 200-gph filter-free pump with protective shell
- Water-bell fountain head
- 3-tier fountain head
- Telescopic riser
- 2 silk water lilies
- Installation manual

subset: commoncrawl


text:
Made from same pigments and linseed oil as Grumbacher Pre-Tested Oils. Can be intermixed with other oils or mediums. Thin and clean-up with water. Tubes. Also wooden Sketchbox Set, Sampler Set, and Intro Set.
Color Swatch created using heavy application/medium application/50% tint and was applied on acrylic primed canvas (7 oz) material.
cadmium sulfide and cadmium selenide
CdS × CdSe
Cadmium Orange was the first true orange and was made by mixing Cadmium Yellow with Cadmium Red. It is a pure hue with excellent opacity and low toxicity compared with its predecessors. It also has very high hiding power. The greatest tinting strengths are possessed by the deeper shades. Only the highest grades contain pure Cadmium Orange without barium mixed in it. Cadmium pigments have been partially replaced by azo pigments, which are similar in lightfasness to the cadmium colors, cheaper, and non-toxic.
Cadmium Orange has excellent permanence, but like many cadmium pigments, it will fade in fresco or mural painting. The deeper varieties of this pigment are the most permanent. The paler varieties have been known to fade when exposed to sunlight.
Cadmium Orange is a known human carcinogen. It is extremely toxic if inhaled and slightly toxic if ingested.
Cadmiums get their names from the Latin word cadmia, meaning zinc ore calamine, and the Greek word kadmeia, meaning Cadmean earth, first found near Thebes, the city founded by the Phoenician prince Cadmus. Metallic cadmium was discovered in 1817 by Friedrich Strohmeyer. It was used sparingly after its discovery due to the scarcity of cadmium metal.
® Grumbacher is a registered trademark of Chartpak.


text:
Results 6 to 10 of 32
May 11th, 2013 02:08 PM #6Senior Member
- Join Date
- Feb 2013
- Posts
- 409
The most baffleing name on the girls list in my oppinon was Collins. Whaat? Where did that come from and how did it make the top 1000? Retro name that were still on the list (for girls) that surprised me: Brittany, Stephanie, Melissa, Brenda, Jenna, Jennifer, Amanda,Wendy, Nancy, Sandra, Denise... A few old lady names that surprised me because they seem to fit the overall trend but they weren't too similar to the ones I've heard discuWhssed on Nameberry: Geraldine, Barbara,Dorothy, Judith, Edith... And Malaysia? What the heck? Why? When did Logan become a girl's name and what kind of name is Tinley/Tenley? Also, how many ways are there to spell Allison? Or Jazzlyn?
And on the boys side... Just plain Junior made the top 1000? Why would someone just name their kid Junior? And why didn't the parents of all the Micheals go back and correct their typo? Surely they were all typos... More retro-feeling 80's/90's names that are still high on the charts: Austin, Brandon, Tyler, Colton, Kevin, Justin, Bryan/Brian, Kyle, Ashton, Brady, Sean, Bradley, Harrison, Cody, Trevor, Shane, Kenneth, Brenden... Old man names that surprised me: Eugene, George,ect. I was surprised by the numer of Maximuses (Maximii?) , Gunners, Waylons, Cannons, Bostons, Wades, ect. I was surprised by all the spelling options for Zaydens, Braydens, Xaviers (Xzavier???), Jacksons, Elijah, Isaiah, Jace, Josiah... I was surprised by all the nickname-y names like Johnny, Jimmy, Drew, ect. I was also surprised that Avery ranked pretty high for boys.
I was surprised at certain names that were on both lists: Rylan, Cameron, Skyler, Landry, ect...
All in all, yes it was head-exploding.
May 11th, 2013 02:09 PM #8
Genesis is a very common name with Hispanics. It's popularity might be a sign of the growing Hispanic influence in the US.
My head more exploded at the butchering of Madison, Addison, Madeleine, and Adeline. I won't get into how Madison and Addison mean "son of..." but seriously, Maddilynn?? It's in the top 1000. *facepalm*Mi corazón Zoe Milena
May 11th, 2013 02:30 PM #10Anxiously awaiting the arrival of Luther's little brother November 2015!
Currently loving: Magnus, Tiberius, Gregor, Corvus and Ulric.
May 11th, 2013 03:54 PM #12
May 11th, 2013 04:16 PM #14
Genesis. I think it has a pretty sound.g w e n
Viola ❀ Beatrix ❀ Celia ❀ Fionnuala ❀ Ismay ❀ OfeliaFinn ✴ August ✴ Kieran ✴ Emrys ✴ Prosper ✴ Zeke
combos + radar
Emmett Orlando ○ Zephyr Julian ○ Dash Apollo ○ Elyan ○ Alastor ○ MadocCosima Vale ○ Cleo Iphigenia ○ Esme Leocadia ○ Sancia ○ Perdita ○ Maxine


text:
Since I had to find a way to redeem myself, I decided to teach my kids how to draw a penguin. Ok, ok, really, I found this awesome video that taught all of how to draw a penguin. haha! We were also inspired by some penguin painting at My Shae Noel All Things Wonderful in making our penguin scene.
Over the last year I've noticed some difficulties Luke has in being the younger brother. Don't get me wrong, he LOVES his older brother dearly, they are pretty much inseparable, but Luke can't help but compare himself to what he sees Andy doing. It sometimes feels disheartening with the frustrations Luke feels when he can't do it as fast as Andy or if he doesn't know as much as Andy. Now truth be told, Luke is actually farther advanced in some areas than Andy was at his age (Sh! Don't tell Andy), but Luke doesn't understand that, and obviously I'm not going to go around telling my children things like that. hahaha! Anyways, I thought teaching him how to draw his very own penguin was a perfect way to boost his self-confidence. It acted as a reassurance that he could do something as well as Andy could.
We started by following this step-by-step video and drew a penguin diving into the water with pencil. We also drew the rocks, the water, a big cloud in the sky, birds, and an extra penguin standing in line. Andy learned how to draw a penguin in school so he gave a step-by-step on how to draw the standing penguin.
We traced our pencil lines with oil pastels and then finished off our artwork painting the scene with water colors. We opted to make the sky look like the sun was setting with yellow and orange. The red in the water is krill for the penguins to eat.
Some of the books we've been enjoying this week are:
We threw in some comical reading this week with some Tacky the Penguin books as well.
Happy Crafting!!
I like to link my posts up to THESE fun link parties.


text:
Going Mobile: Lessons in Workforce Management
Event Start Time (Eastern Time):12:00 PM
City:Virtual Event
Company:Energy Central
Utilities are facing entirely new challenges as a result of the smart grid movement, tighter reserve margins, changing weather patterns and many other facets of almost a "Perfect Storm" for utilities. Keeping their field workers in the field and "in-touch" with headquarters through mobile systems is increasingly important.
This webcast will examine the capabilities of the latest workforce mobility systems and how they are helping utilities meet the increasing demands and expectations of customers nationwide.
This event is underwritten by:
The webcast is free but seating is limited. Register today to guarantee your seat. .
Venue:Your Office
Price:$0.00 USD
Person to Contact:Energy Central


text:
Sgt. Montrell Lamar Anderson Mayo was charged with premeditated murder and murder in the death of Cpl. Kimberly Walker.
Walker, 28, of Cincinnati was stationed at Fort Riley, Kan. Friends of Mayo said the woman was visiting Mayo at the time she was killed.
Walker's body was found in an off-post motel in Colorado Springs, adjacent to Fort Carson.
Civilian prosecutors said they turned the case over to the Army at the Army's request. Fort Carson officials said the post has jurisdiction over alleged misconduct by its soldiers, and that military prosecution was appropriate because the victim was also a soldier.
Mayo, 24, is from Greenville, S.C., and is stationed at Fort Carson. It was not immediately clear if he had an attorney.
If convicted, he could face a maximum sentence of life without parole, forfeiture of pay and a dishonorable discharge.


text:
Changes: AmberEdit
The database did not find the text of a page that it should have found, named "Amber" (Diff: 351246, 640969).
This is usually caused by following an outdated diff or history link to a page that has been deleted.
If this is not the case, you may have found a bug in the software. Please report this to Wikia staff, making note of the URL.


text:
.emacs file, and now I can just go to the header line in the file, and toggle my Emacs header line for that buffer, and scroll down to my hearts content, and there's that nice header line right at the top of the buffer, occupying minimal space, and when I'm done, I toggle it, and it's gone. It's just one of those little things that makes life easier to deal with. Less pain, more gain.
Here's the code:
(defun freeze-line-as-header () (interactive) (if header-line-format (setq header-line-format nil) (setq header-line-format (concat " " (buffer-substring (line-beginning-position) (line-end-position))))) (force-window-update) ) (define-key global-map [(control ?!)] 'freeze-line-as-header)
Share This | Email this page to a friend]]>
char *RenderSomeStringConversion(const char *in, char *out, size_t *out_size);
Now, the out_size parameter should have warned me a little, since it's a pointer to the size. Maybe I should have looked further there. Anyway, the API takes the input string, does translation on it, and dumps the result in the output buffer, and returns the output buffer. C programmers are used to functions like this returning the output buffer, so that's not a really good warning about what this thing can do to you. OK, so the landmine this API sets out for you is that the function will attempt the transformation, and if it decides that it can't fit the result in your output buffer, it will call realloc on your pointer. IOW, there's no way to use this method without involving yourself with malloc/free. And worse, most of the time, if you've got a static buffer that's a good size, this API will work just fine, but instead of failing when it isn't big enough, it will just burn you if you run into the edge case. And it will be so much more fun to debug if you were to, say, pass in the address of a local that's too small, because then it will call realloc on a pointer into your stack, and off you'll go someday, launched into some interesting area of memory to execute god knows what bits.
Now, in the online docs, this is actually well documented, but this is an API that's part of a permanent API broadly available to people, and it's just got this awful nasty sticky thing on it. A little more time could have produced an API that didn't have this dependency or trap.
Share This | Email this page to a friend]]>
So, shortening up the damage chain, on IA-32, if you do this:
FSTP [some location]
FILD [some location]
and the FPU stack was empty at the FSTP, you'll die on the FILD instruction. The FSTP just sets some condition bits and fails silently. So, in this case, the '…', of course, was really a long long distance. Specifically, it was in either Move or FillChar in the Pascal RTL, which use FILD for optimization for larger moves.
Either Move or FillChar? Well, yeah, because I started hunting around with writeln to bracket things, and it moved things around. Actually, it moved things around considerably, because I was bracketing front and back, and that sometimes moved around the primary cause of pain.
The primary cause: why did I do FSTP with an empty stack? Well, I had this asm function, one of whose parameters was a Boolean, and I loaded it like this:
MOV EAX, DWORD PTR FPReturn
The caller, had loaded the boolean like this:
MOV AL, BYTE PTR [someplace]
So, depending on what sort of garbage was in EAX at the time in the caller, my boolean, which I tested with "OR EAX, EAX", was pretty variable. And I decided to pop the FP stack based on it.
One thing that helped in a funny way was that as I added more writelns, it actually moved me closer and closer to the original fault, but only because it was sometimes calling the RTL Move function. If I'd been smarter, I'd have been bracketing using FILD instructions, not writelns. Or, I'd have been a little more careful writing the original ASM code that read the boolean.
Oooh, that one took me a while to find.
Share This | Email this page to a friend]]>
First of all, a reminder about my dev system: Macbook Pro, running VMWare 3, which is constantly running Windows 7 Ultimate (32bit just now). I keep a number of Mac apps up pretty much all the time. These include Adium, Skype, Mail, iCal and Safari. Safari typically has just one window open, pointing at gmail. Throughout the day, I use Safari a lot, researching technical topics, researching software, reading news. I may have a lot of windows/tabs active during a given session, but I generally close them all down after a while, and go back to the one. For quite a while, I was just using plain old Safari out of the box, no extensions, no nothing.
So, one day, I go looking at my machine, looking for oinkers (BTW, oinker is slang for pig, in this case referring to any process that is being a memory hog), and what do I find? Not VMWare, which is running a whole OS under the covers. No, I find Safari and Flash, at the number one and number two spots. And they are WAY ahead. Both are using around 600MB Real Mem, and a similar amount of Virtual Mem. And this is with one gmail window open. And that Flash Player process will just never die, so long as Safari is up and running. Well, I found that to be more than offensive, and at that level of usage, it's actually getting in my way, so I spent some time reading up. Lots of people said pretty much the same thing, but there was some variability. Some people really didn't see the same problem at all. Eventually, I found ClickToFlash, which is a Safari WebKit plugin that stops Flash controls from executing unless you click on them.
So I gave ClickToFlash a try. The Flash process disappeared from the memory profile altogether, which wasn't too surprising. What was interesting was that when I invoked Flash on places like YouTube, and other sites that have Flash content that I want to see, the Flash process was well behaved, and put itself to bed after the Safari tab in question closed. Safari memory usage still crept up, but it seemed like it wasn't quite so quick.
So, then Lee pointed me to the ad blocker and script blockers that he uses for Safari: AdBlock, and JavaScript Blacklist. I've used ad blockers on and off, but I have sometimes had troubles with sites that won't work properly with them, so I've generally just trained myself to ignore ads. Sometimes my kids will see something in an ad on a page I'm looking at, and mention it, and I'll ask "What? Where?" They'll have to point, because I just don't look at or process those regions of the page. The one exception is when a site has one of those expand down ads. I really can't stand those, because they scroll the page contents down, and then back up, and you have to wear out your knuckle a bit more on the scroll wheel. I still don't mentally process the content. Anyway, I installed both these extensions, to see what happens.
Well, I'll say that AdBlock seems to work pretty nicely. A lot of pages I regularly use got very quiet, visually. Safari's memory usage still creeps up, but again, not as quickly. I'm still using ClickToFlash at this point.
So, I decided to try a regression, to test out an hypothesis: does Flash memory oinkage (ok, now we're making slang up. Roll with it.) come about because there are sloppy or maladjusted or malevolent Flash applets in some of the ads? So I kept AdBlocker enabled, and disabled ClickToFlash. What do you know, the Flash process stayed pretty well behaved. I do see it floating around more, and I'll probably re-enable ClickToFlash, just because there are some sites that use Flash in irritating ways that are not ads, but are still not something I want to see. In any case, it's my thinking, now, that Flash isn't entirely to blame for being a memory hog, but I'm still keeping it on a tight leash.
Now, back to Safari. It's still a piggy. With the three extensions above enabled, the Real Memory usage still drifts up and up during an 8 hour period until it sits, generally, for me, at about 650MB. It usually plateaus there. There's an additional 600MB of Virtual Memory in use. This past weekend, I spent a bunch of time playing around with Network Attached Storage. I ended up doing a lot of searching on the topic, in conjunction with Time Machine. That will be the topic of another blog post, I can tell you. During that session, which was primarily on blogs and forums, and a few product pages, Safaris Real Memory usage went to 1.6G, and the Virtual Memory to 1.7G. When I closed down all those pages and went back to my one gmail page, Real Memory drifted back down to 1G. I left it overnight, and it was still at 1G. I'm sorry, it's just a hog. I'll be fair: I haven't done the same experiment on FireFox, or Chrome. I should, and I probably will. Right now, I feel like I've got back 600MB of Real Memory by nuking the Flash hoarding, and I've got things to do, so I'm not going to dig into FireFox or Chrome just yet. If anyone has numbers on those, I'd love to hear them.
Last item - I didn't say anything about JavaScript Blacklist. It's probably not relevant to the memory thing, but it fits into the ancillary category of 'stomping on things that irritate me'. JavaScript Blacklist stops things like IntelliTXT. I've nothing at all good to say about IntelliTXT, or any of the other flyover-get-in-your-face-parasites. In the past, if you had a page that used these, I would never return to it. Now, I'll never know. One aside, though: JavaScript Blacklist blocks tynt.com's scripts. Up until a short time ago, I'd never heard of tynt.com. I did some searching (oink oink), and saw people really ranting about it. Basically, a site that uses tynt.com scripts intercepts copy operations, and if you copy text off the site, it inserts an attribution URL. Places like major newspapers use this. This actually seems reasonable to me. I mean, if you are copying the content from a site like that, well, you should be making an attribution, at the least. If you don't like the link, you can strip it out when you paste. Seems to me that people are a little too free with copying content that's actually not theirs to copy. It's called plagiarism, or copyright infringement.
Here are links to the three nifty little products that I've now got for Safari:
Share This | Email this page to a friend]]>
I have a Windows VM running on the Mac on which I do all my dev builds. My dev machine is a Macbook Pro. I run VMWare Fusion, in unity mode, and life is generally good; it's a very nice cross targeting solution. The hitch was that when I switched VPNs, DNS no longer worked from the Windows VM for names inside the VPN target domain(s). Lee is my go-to guy for problems like this, and he and I spent quite a while poking around at it. We learned interesting things about the differences between how the two different VPN clients effected their support. They were quite different in how they altered the lookup flow. I won't go into it, because it's irrelevant to the posting, really. In the end it turned out that my DNS problems were due to being on an older version of VMWare (version 2). I'd been meaning to upgrade for a long time, but held off, because I never like to upgrade when I'm in the middle of things, lest my world come unglued. Unfortunately, I'm always in the middle of things. Anyway, I upgraded, and things were good again.
Now, about nslookup, which is in the title of this post, in case you hadn't noticed. Well, Lee and I use nslookup pretty commonly on various platforms to make sure that things are resolving the way they should. We spent quite a bit of time using nslookup yesterday, and we kept being really confused by the results. Eventually, Lee strolled across the street to the coffee shop (I prefer Peet's coffee, and this wasn't Peet's) to poke around from an external network to more closely match my setup (I'm in Massachusetts, he's in California). Around the same time, we both started being really suspicious of the results from nslookup. And the punchline of the whole thing comes from the man entry for nslookup on OS X:
Mac OS X NOTICE The nslookup command does not use the host name and address resolution or the DNS query routing mechanisms used by other processes running on Mac OS X. The results of name or address queries printed by nslookup may differ from those found by other processes that use the Mac OS X native name and address resolution mechanisms. The results of DNS queries may also differ from queries that use the Mac OS X DNS routing library.
When they say the results may be different from other processes, we're talking things like 'ping'. Sigh.
Mind yourselves out there, there's gears and stuff you can catch your clothes on.
Share This | Email this page to a friend]]>
Mind you I don't always read stuff like this. My reading range is pretty broad, and included in there are murder mysteries, and Terry Pratchett books, and other non-fiction, and just kind of all over the place. So I'm not always carrying around a book on theoretical physics.
Now, that question he asked is potentially kind of a stock question, so I shrugged, and said I wasn't so sure yet, and he asked if I hadn't got far enough in the book to know yet (halfway), and I opened up a bit more, and told him that basically the theme was that the author felt that nothing had really been figured out in a while. Just so y'all know, the book, at least so far, goes through some of the history of physics, on through quantum mechanics, and then into post-modern physics (if you will). This includes string theory, and super string theory, and could possibly be about to get into philosophy. Not sure yet. The starting theme of the book is that we've not made revolutionary discoveries in the last generation or so, and it's frustrating a lot of people, including the author, and he'd like to tell people about everything that's happened lately.
Getting back to the bartender, who, I will swear on whatever icon you require, responds to my extremely brief summary with "You mean, string theory doesn't work, or M-theory or whatever they call it now-a-days?" Now, I had not heard about M-theory until an hour or so before because that's what the book had got up to an hour before. Blink…blink. "Yes," I said, "you are exactly right." From there, we got into a discussion about the LHC (Large Hadron Collider), and the Higgs boson, and the standard model, and it should be an interesting couple of years, because everyone is waiting for the Higgs boson. I said if they did find the Higgs, they were still stuck, because of all the existing questions about string theory, and he said, yes, but if they didn't find the Higgs, then that kind of tosses the entire standard model. He asked for the publishing date and the author, because he said that all the stuff he's reading now is saying pretty much the same stuff over and over again.
Yes, I know, operating under the presumption that the barkeep doesn't know theoretical physics is a sort of prejudice, and I do feel a little bad about that. I have to say that I was really pleased to be having the conversation with him. The only other fellow who asked me about the book was a professor of physics on the plane out, and when I tried to engage him in conversation, I got a lot less out of it than I got out of the bartender.
Anyway, I had to share.
Share This | Email this page to a friend]]>
I have two scenarios that I've run into that really ticked me off. Most recently was about an hour ago, when I was trying to dredge up some old data and I found a CD that might have the archived bits I wanted on it. So I stuck the thing in the drive to see what was on it, and it spun up and spun down and *gulp* that was it. Now, I admit I did something dumb here: I tried to cajole the drive. I had a Windows VM running, so I told VMWare to mount the physical CD drive. So that took out VMWare, and the VM was shutdown unfavorably, so I lost a bunch of state that's a pain to put back together. Like I said, that was probably dumb. So I end up using the most common fix for this, which is to power down my Mac, and power it back up with the mouse button held down (no drutil didn't work - nothing worked). In my opinion, that's a piss poor thing to make a user do to eject a CD that the drivers get their various bits in a bunch about. Drill me a hole for that old fashioned paperclip, please. FYI, once I got that CD out, I took it down to my Dell laptop, and stuck it in there, and it read the bits just fine, so the CD isn't some piece of radioactive toxic waste, that's for sure.
So, the second case, which goes a little further back in time to late last year, had to do with my Mac Mini. This was a personal machine that my family used. It died a hard death (logic board failure). But there was a CD in it, and I wanted it back. With the logic board gone, it wouldn't boot to any point at all, even off an external device where it could be forced to eject the CD. So how do you suppose you have to go about getting that CD back? You have to dismantle the Mac mini, INCLUDING THE CD DRIVE. You actually have to physically unscrew a ton of screws on the drive to get the cover off! Getting to those screws is no picnic, either, because the CD drive is mounted on the top of the machine, and the cover comes off the bottom, so you have to dismantle the bulk of the machine before you get to the drive. I asked the guys at the Genius Bar about this, and they said that was basically the only way, too.
I'm sure Apple had a really good reason for doing this, but in my opinion, IT WASN"T GOOD ENOUGH!
Share This | Email this page to a friend]]>
Dynamic linking has been available on most operating systems for a long long time now. It is interesting, however, to peer into the origins and resulting behavior of some aspects of symbol binding on various systems. You might be surprised by the results.
To focus this discussion, what I'm talking about here is basic support for linking to symbols in shared libraries. These are DLLs on Windows, shared objects (.so) on Linux, and dynamic libraries (.dylib) on OS X. There are other platforms of course, but these are the ones that may affect our customers in the near term, so that's what we'll talk about today.
I'm not able to speak authoritatively on some of this topic. On the raw technical details, I can, because I've been down among the bits, but on some of the points of motivation and history I will be relating things that have been told to me by others in the now distant past. Some of these bits of information aren't written down anyplace that I know of. Feel free to add to the pile of lore if you have personal knowledge.
Not long after the surface of the datascape cooled, and bubbling pools of ones and zeroes congealed into a solid crust, the language C appeared and populated the world at a ferocious pace. Linkers and librarians developed to support the ecosphere, and various traits and behaviors became standard. Some of this stuff survives to modern times, much like the way the pelican still plies our skies. [Off topic: once I was on the wharf in Santa Cruz, and a pelican walked up to me and yawned. That was impressive. You talk about birds having wing-span - those things have beak-span!]
The trait of interest in linkers for today's article is order of symbol binding. Let's set aside dynamic linking for a moment. When linking a static image, using classical C as an example, the user would specify a bunch of object files and some libraries, left to right:
a.o b.o c.o lib1.a lib2.a lib3.a
The linker would go through these, finding public symbols to satisfy external references and hooking things all together. Now, for any symbol 'foo', any of those objects or libraries could provide the public definition, and it is OK for multiple libraries to provide public definitions. The basic rule that the linker followed was that the first public symbol found in a left to right search is selected to satisfy external references. So, if lib1 and lib3 both provide public definitions of 'foo', and a.o refers to 'foo', then the one the linker will select is the one from lib1, because it is leftmost. Now, note that if lib1 and lib3 both define 'foo', and lib3 refers to 'foo', then the linker will still select the definition from lib1. This has allowed developers to override definitions of symbols by inserting a library with different definitions to the left of the original library in the link line. This behavior is very much driven as an aspect of the tools (specifically the static linker). It's not really language specific, but it can end up freighting the tools for any language, oddly enough.
Along comes Windows. Dynamic Link Libraries are a new concept, and enable developers to share code better. Actually the concept isn't new - unix beat them to it by a long shot, but you can run rough-shod over history with good marketing. Now, the first tools for Windows were C based, and the classic left to right rules for the static linker still held true. However, DLLs don't follow quite the same rules. Once you build a DLL, the linkages to that DLL, and within that DLL are much more specific. If the DLL wants to access 'malloc', it doesn't just bind to any 'malloc', it binds to a local copy of 'malloc', if it binds the C RTL statically, or to a symbol called 'malloc' from a particular DLL.
Along comes Linux. Now these folks take things to extremes, I think. When they did shared library support, their attitude was that linking a shared library should be identical in behavior to linking a static library. So this means that if you link a shared library together, and that shared library binds to a symbol called 'malloc', you don't know what actual public definition that this will bind to until runtime. You don't even know which library that symbol might come from. That's just the way it works on most platforms with classic C style compile/link phases with static linking. Now this is an interesting philosophy, and it's got some interesting features that it supports, but it implies a lot for the tools that have to deal with the platform. It means, among other things, that nth party languages and tools have to be aware of this artifact of left to right ordering of symbol binding that comes from way back in some fragment of the pelican genome.
I have no idea what combination of history and philosophy went into the dynamic binding logic on the Mac, but for the specific attribute this article is interested in, the behavior is more like Windows. Originally, the behavior was a mix of linux and Windows, because when you bound to some external like 'malloc', you didn't know what shared library was going to provide it. Apple added support for being more specific about it in a point release, so that a shared library could say "I want 'malloc', but I want it from 'libSystem.dylib.'"
So, now let's take a look at a very simple C example that illustrates what I'm talking about.
Three files, three images. One is the executable, and two and three are shared libraries. Here we go:
#include <stdio.h> extern void two(void); extern void three(void); int main(void) { printf("hello world\n"); two(); three(); }
#include <stdio.h> void two() { printf("two.c: two\n"); }
#include <stdio.h> void two() { printf("three.c: two\n"); } void three(void) { printf("three.c: three\n"); two(); }
Now, let's build these things on linux:
gcc -shared -o libtwo.so two.c
gcc -shared -o libthree.so three.c
and we'll build two different versions of the main executable:
gcc -o one_a one.c libthree.so
gcc -o one_b one.c libtwo.so libthree.so
And it's the second one of those executables that's really the interesting one. It's in that example that the differences between linux and Windows and OS X finally stand up and say hello. In three.c, the function 'three' makes a reference to 'two', which happens to be publicly provided by three.c. Thus a version of 'two' gets built into libthree.so, and is made publicly available. Now, in the first executable, that's the only version of 'two' around, and the result is predictable. In the second case, however, there is a copy of 'two' that is provided by libtwo.so. And the way the linux tooling works, because the executable binds libtwo.so before it binds libthree.so (left to right), the reference to 'two' inside libthree.so will be bound to the implementation in libtwo.so for the second test image (one_b).
So here's the output for these two images on linux:
hello world three.c: two three.c: three three.c: two
hello world two.c: two three.c: three two.c: two
Notice that last line - that's the call from three.c to 'two'. Now it goes out of the previously linked shared library libthree.so and into libtwo.so. Both the call from one.c and the call from three.c go to the same place in two.c, even though we had three separate static linker invocations.
Now, if you link the same set of programs using gcc on OS X (slightly different command lines), you get the following runtime results.
hello world three.c: two three.c: three three.c: two
hello world two.c: two three.c: three three.c: two
Now, look at that - the call from one.c to 'two' went to libtwo.dylib. The call from three.c to 'two', however, went to the statically bound copy in libthree.dylib. That's what would happen on Windows, too.
OK, so which of these models should our tools support? The answer basically comes down to this: When in Rome, do as the Romans do. That means on Linux, our tools ought to support the linkage model provided by the default tools, except where it would completely hose our language(s) (and that's what we did in Kylix). On OS X, we'll do what OS X defaults to. Now, I'll tell you, that cute little dynamic override feature that linux supports is supported through standards wrapped around the ELF image format. OS X uses Mach-o, and there appears to be no standard to support the sort of override that linux does. The linux support is a major PITA to implement, too, so OS X actually makes me breathe more of a sigh of relief, because the shared library model there, so far, appears to be much less complex than the model on linux.
This article was a bit long to get to a couple of basic points. The first point is that basic dynamic library support on OS X looks more and more like it's simpler from a tooling standpoint than on linux. Mind, now, I'm not discussing frameworks and umbrellas here. The second point is that it's interesting how very old paradigms in the way that a set of command line tools operate to this day bleed through and can impact language tooling that might want to operate in a completely different fashion. The prime example of this for us is Delphi. Our command line tooling for Object Pascal simply doesn't have the concept of left to right ordering of static link dependencies for libraries, and yet we have this interesting aspect on linux that we have had to consider - an aspect that does not translate to OS X or Windows.
Share This | Email this page to a friend]]>
When we did the original linux work, we started out with the assumption that the loader worked the same as Windows with respect to initialization order. We assumed dependencies were initialized first, in a depth first ordering. I don't remember anymore what the default ordering was, but it wasn't right. We found out that the tools are responsible for supplying the shared object initialization order in a special section in the executable. I didn't want to have a similar experience late in the development cycle for the Mac.
The first thing to do was to find out how shared objects (e.g. .dylib files) specify initialization procedures. If you look at the MACH-o spec, or in mach-o/loader.h, you'll find the LC_ROUTINES load command, which seems just right for the job. Comments in the header say this is used for C++ static constructors. Excellent! A little further reading shows the ld option -init allows you to specify the startup routine manually, and directs you to the man page for ld. OK, off we go, and there we see only one sentence that includes a clause stating that this is used rarely. Red flag. And there the documentation trail dies. Red flag. OK, let's go look at a C++ static constructor example built with g++. Hmm, no LC_ROUTINES. Red flag. OK, let's look for LC_ROUTINES in some of the .dylibs in the shipping OS. Hmm, no LC_ROUTINES. Red flag. So, how do C++ static constructors get called? Looking around a bit (see otool -lv), I see sections like __mod_init_func, with the S_MOD_INIT_FUNC_POINTERS flag set. Good luck finding documentation on the S_MOD_INIT_FUNC_POINTERS flag (yeah, ok, red flag).
So, here's where we are saved a ton of time from the fact that the OS is open source. I have the DYLD source handy, and a little grepping and reading gives a pretty clear picture of how things really work. LC_ROUTINES is only suitable for calling an initialization routine. LC_ROUTINES does not support a termination notification. So now LC_ROUTINES is a porcupine of red flags, and I wouldn't touch it with a ten foot pole. S_MOD_INIT_FUNC_POINTERS and S_MOD_TERM_FUNC_POINTERS are the way to go. These indicate sections that are arrays of pointers to functions that the OS calls for both the executable and for shared objects, if it finds them. Each function in the S_MOD_INIT_FUNC_POINTERS section is called with a mess of parameters, which I'll describe later. Each function in the S_MOD_TERM_FUNC_POINTERS section is called with no parameters at all. The functions in the S_MOD_TERM_FUNC_POINTERS array are called in reverse order. So for init, it's init[0], init[1], …, init[n], and for term it's term[n], term[n-1], …, term[0]. Without source, this would have been a long slow learning experience.
The loader source code also indicates a recursive descent initialization of the shared objects, but the devil is in the details, and rather than try to fully grok the source code, and possibly miss something critical, I decided to switch back to the empirical, and write a bunch of tests. Armed with the details of how the loader wants us to set up the init and term functions, I descended on our C++ linker, and brought it to the point where it could build a Mac .dylib (mostly). Many of the results are mundane, but a few are sort of interesting, and I'll try to present them here compactly.
First some notation. In all the examples below, X refers to the executable. Other letters refer to shared objects. Solid directed lines indicate a static dependency between objects. For example, X -> A, means the executable depends on the shared library A, and we'd expect A to be initialized before X runs. Also we'd expect A to be terminated after X runs. Dotted lines in the examples mean we dynamically load a shared object with
dlopen. That's where a lot of the really horrible things happened in Kylix, because of all the package load/unload operations, so I invested some tests there. To show the actual initialization results, I'm going to use a very simple notation. I use the letter of the object for initialization, and the same letter, preceded by ~ to indicate termination. So for the example X -> A, I expect the following sequence:
So, simple tests first.
And a diamond:
OK, moving on to a complicated static linking example. This one is a ladder, and here we should do a little explanation.
D -> C -> B -> A / | ^ | ^ X | | | | \ v | v | H -> G -> F -> E
In the example above, we have two straight legs of dependencies, with cross dependencies running back and forth between the legs. You can't do a naive recursive depth first initialization of this, because you could end up running some initializers before their dependents are initialized. You have to do a topological ordering of the dependencies, and initialize in that order. That can be done with a recursive operation, and it is done that way by the Mac loader. The easiest way to observe it is to follow all the dependency sequences in the ladder above. Here they are:
The last one is the longest chain. In all the chains, D is at the top. The longest one is the initialization chain we need, since it guarantees all dependents will be initialized first. It is roughly what we expect out of the loader, barring ties in initialization order due to libraries at the same level in the dependency graph.
Here's what we got when we ran the example:
OK, so things are looking up. I am getting what I expect out of the loader, and I'm not terribly surprised, because otherwise the world would have fallen apart long ago for the Mac, right? That's what we thought on Kylix, and it's why I looked so closely here. Anyway, now on to the dynamic loading cases. This is where we mix static loading with dynamic loading, and make sure the semantics are reasonable, and don't require us to jump through too many hoops in the linker and RTL.
In this example, X loads B with
dlopen, and then unloads it with
dlclose before exiting. B depends on C, but not A. Here's what we got:
A X [load B] C B [unload B] ~B ~C ~X ~A.
Now, just for fun, let's try the same case, but let's not call dlclose in X. Meaning we orphan the B shared library. Here's where it gets harder to guess what would happen. Here's what we got:
A X [load B] C B ~B ~C ~X ~A. Yep, same as the case where we called
dlclose! I certainly wouldn't rely on this feature, but it's nice to know about.
Now, a more complicated case where we try out load and unload sequences.
In the case above, there's a special runtime sequence. X loads B, then loads C, then unloads B and unloads C. The interleaved order is purposeful - to be mean. There are no cyclical dependencies involved, but there are reference count issues. C depends on B, so when we manually unload B in X, we hope the OS doesn't call the terminate routine in B, because C still needs B. And here's what we got:
A X [load B] B [load C] C [unload B] [unload C] ~C ~B ~X ~A. That's what we wanted.
And for our last example, we'll include a cyclical case. This is a case where the user manually, via
dlopen, causes a cyclical dependency to appear in the shared object dependencies. This is bad, and there is no good way for the OS to resolve it. Still, we'd like to know what happens. For example, one outcome could have been for the OS to panic and kill the task. The way we create the cycle is to have a shared object use
dlopen in its initialization routine to load another shared object that has a static dependency on something further up the initialization chain that hasn't been initialized yet.
And what we got was this:
So what happened was that the OS stopped the initialization of the library loaded with
dlopen at the point where it hit pending dependencies in an existing initialization chain. That meant the loaded library E had its initializer run with some dependencies uninitialized (C and D). This protected the main executable's dependencies, sort of, but either way, the user is probably hosed. As a basic rule of thumb, people should avoid calling
dlopen in a library initializer anyway unless they really know what they are doing.
So there's a basic way of summarizing the results here:
This is a good result. It's similar to Windows, and it appears to meet our basic requirements for package initialization code in the RTL without us having to add more magic to the tools over and above what we've done in the past to preserve initialization order.
Once last thing. I promised to give list the parameters to the initialization functions in the S_MOD_INIT_FUNC_POINTERS sections.
void func(int argc, const char **argv, const char **envp, const char **apple, struct ProgramVars *pvars);
ProgramVars is this:
struct ProgramVars { const void* mh; int* NXArgcPtr; const char*** NXArgvPtr; const char*** environPtr; const char** __prognamePtr; };
The interesting item here, really, is the
mh field. That one is actually the Mach header for the image, which is really nice, because it means on OS X, a shared library has a reliable way of finding useful things about itself, like the precise start of sections in memory. I don't know why there is the redundancy of information in the parameters passed to the init function, and the fields of the struct of the last parameter.
Ideally, none of you out there will never have to worry about this at all, but if you do, there it is.
Share This | Email this page to a friend]]>
On Win32, OS/hardware exceptions and language exceptions are all dispatched through the same mechanism: stack based exception registration records. Handling these and even resuming them is pretty straightforward.
On Linux, OS/hardware exceptions are quite a bit trickier to deal with. Exception handling is typically done using a PC mapped scheme that is vendor dependent. There is no standard for language based exceptions, and all the hardware exceptions are dispatched to signal handlers, which you can install with the POSIX signal handling APIs. There are also some strict protocols that you need to follow with respect to handling Ctrl-C and friends if you want to play by the rules for shell scripts. The POSIX signal handling APIs provide portable interfaces for getting the RTL in the game, but the devil is in the details. For example, when your signal handlers are invoked, you get a signal context sent to you that represents the machine state (processor registers, etc). That's an opaque pointer, because POSIX really can only go so far as to define/restrict what you can and can't do with the machine state for hardware exceptions. Thus once you land in your handler, everything becomes platform specific with respect to that context, both in its format, and what you can do with it.
In porting to OS X, I've tried to use POSIX as the common point between the Linux and OS X support as much as possible. So I did the same thing with exception handling, reviving the Kylix PC mapped exception handling support. The first thing that I did was to try to discover what I could do with the machine context that was delivered to my signal handlers.
Here's the POSIX spec for your key signal handling setup API: http://www.opengroup.org/onlinepubs/9699919799/functions/sigaction.html. This API has been updated a bit with respect to its formal documentation in the past several years, but the fundamentals of it haven't changed since I did the exception handling work in Kylix.
I started on OS X writing a simple C program so that I could investigate the behavioral characteristics of the machine context that is delivered to a signal handler. Specifically, I wanted to make sure that I could resume execution on the client thread/stack in the face of memory access violations (e.g. SIGSEGV), and keep the thread sane while delivering the critical data to the RTL for stack unwinding purposes. My simple test case ran fine, so I moved to the next step, which was to debug the signal handler, and confirm the validity and utility of the machine context. There was an immediate hull breach. I don't remember all the terrible things that happened, but the nut of it is this: your signal handler will never be invoked if you run the app under GDB. To understand the reasons for this, you have to recall the fundamental structure of OS X.
OS X is built on top of the BSD kernel, using the Mach kernel originally developed by CMU. The various POSIX APIs are layered on top of a Mach layer, which is the real process control layer that matters to low level implementors and tools, such as GDB. GDB uses the Mach exception handling APIs for injecting exception handlers into the process to watch for faults in the app, and the support in GDB doesn't allow for chaining the exceptions on to signal handlers. Here's a link to one discussion on the matter: http://archives.devshed.com/forums/bsd-93/catching-floating-point-exception-on-os-x-intel-2293939.html. Scroll down to the bottom, and you will see words like 'forever', and 'long standing' with respect to describing the behavior in GDB.
So that pretty much crosses off using signal handlers for hardware exceptions on OS X - I can't very well write off GDB. I had looked around a bit more before and after I ran across that post, and found that folks who did VMs (Java, LISP) ran into the same issues. All the posts said pretty much the same thing: you have to use the Mach exception handling APIs if you want reliable support.
The Mach exception APIs work very differently for processing events. The basic model is that you allocate a port over which you will receive messages describing exceptions. The port can be configured to receive various types of exceptions (e.g. memory access, invalid instruction, and math error). Then you spin up a thread on which you wait for messages on that port. If another thread in your application faults, then the OS will stop that thread and dispatch a message to your exception port. The exception handling thread then processes the message. In our case, that means decoding the exception information, pre-chewing it a bit, and then fiddling with the faulting thread's context to set the thread to continue in an RTL handler with that pre-chewed information sitting on the stack. Then we tell the OS that we've processed the exception message successfully, and we go back to looping looking for exception messages. The OS then restarts the faulting thread, where we land in our language specific RTL code to create the RTL exception object and unwind the stack.
Most of this is all under the covers, so to speak, for the application developer, but there are some points that are of interest:
If I go into the gory details of the Mach implementation, this post will get too long, so I'm just going to include some links here to some references that I've found useful:
I strongly recommend that last article.
There are a couple of other miscellaneous things of interest to note about the Mach exception support. First, the books/articles/examples variously reference a function called exc_server, and a header file called exc_server.h. That header file doesn't exist on the Mac, but the function is there, and needed. Second, there is an oddity with exc_server: when you call exc_server, it calls back into your application. However, you don't tell exc_server the callback function. That function has to have a particular name, and is looked up out of your symbol table at runtime. Get the name wrong, and the app goes down in flames on the first exception.
Share This | Email this page to a friend]]>


text:
PwC Partner Mitch Roschelle says lower cap rates show that recovery is "durable."
DDR, Blackstone to acquire 76 shopping centers in transaction worth approximately $2 billion.
Camden Property Trust, Glimcher Realty Trust, Starwood Property Trust receive gold awards.
Gray examines global growth prospects, single-family housing rental market and debt markets in wide-ranging interview at REITWeek 2014.
Ventas also acquiring 29 independent living senior housing communities in Canada.
Solid fundamentals seen across most REIT property sectors.
Low debt and plenty of cash have assisted Griffin-American Healthcare REIT II's aggressive acquisitions strategy.
New companies in new sectors with new business models are joining the REIT club. Profiling four of the REIT industry's newest members.
First U.S. REIT to issue bonds that exclusively target investment in sustainability.
New program recognizes owners, tenants and brokers using leases to save energy.


text:
Americans Largely Unaware of Global Warming's Impacts on Their Health
Ever come down with Lyme disease? Do you suffer from asthma? Think climate change might have something to do with it? Before you write off this thought as crazy consider the numbers.
The World Health Organization estimates that a minimum of 140,000 people currently die each year around the globe from the effects of climate change. That number does not include the millions more who are made ill from diseases such as asthma, heatstroke or malaria nor does it account for those that are otherwise physically harmed, for example from extreme weather events.
As if these numbers aren't bad enough, Americans are largely unaware of the impact climate change is already having on their health. The Yale Project on Climate Change Communication conducted a nationwide survey this spring asking respondents to give, "their best estimates of the impacts of global warming on human health worldwide – currently and 50 years from now. The largest proportion of respondents (38% to 42%) simply said, 'I don't know.' The next largest proportion (27% to 39%) said either 'no one' or 'hundreds' of people worldwide will die, be made ill or injured by global warming each year, either now or 50 years from now."
"Only 18% to 32% of Americans said, correctly, that each year either 'thousands' or 'millions' of people worldwide will die, be made ill or injured by global warming, either now or 50 years from now."
One look at the conclusion of the health chapter of the recently released 2014 National Climate Assessment demonstrates that hundreds of climate experts see the danger from the global warming review they conducted over the past four years, "Climate change threatens human health and well-being in many ways, including impacts from increased extreme weather events, wildfire, decreased air quality, threats to mental health, and illnesses transmitted by food, water, and disease-carriers such as mosquitoes and ticks. Some of these health impacts are already underway in the United States."
We need to begin making the realization that global warming is here, it's already killing some of us and there is no time to lose in cutting greenhouse gas emissions. Americans are especially prone to think that technology will save us. Perhaps, but perhaps not. A new study argues that climate engineering may not be the answer to averting a climate change catastrophe. You know what will definitely help? Reducing what you can and offsetting the rest. Let's get to it posthaste.
Combating Climate Change Makes Good Business Sense
Global warming and extreme weather caused by climate change are costing companies millions finds a new report from CDP released this month. The white paper titled, Major public companies describe climate-related risks and costs says, "Each year, CDP requests climate-change-related disclosures from public companies on behalf of a growing number of institutional investors. In 2014, the request for disclosure was sent on behalf of 767 institutional investors with $92 trillion in assets. This report presents key findings and responses provided by S&P 500 companies across economic sectors to the risk-related questions in CDP's annual disclosure requests from 2011 to 2013."
Companies reported risks such as damage to facilities, reduced product demand, lost productivity and necessitated write-offs, whose totals run into the millions of dollars.
The paper goes on to say, "Findings show that S&P 500 companies assess physical risks from climate change to be increasing in urgency, with physical disruptions and cost impacts already being felt.
45% of risks were described by companies as current or predicted to fall within the next 1-5 years in 2013, up from 26% in 2011
50% of the risks disclosed were described as more likely than not to virtually certain in 2013, up from 34% in 2011
68% of the disclosed physical risks were direct to operations in 2013, up from 51% in 2011"
This is not merely theory either. Approximately 60 companies gave examples of current and potential future risks and their associated costs in the research, including:
Wildfires in San Diego caused Sempra Energy's costs to exceed its $1.1 billion of liability insurance coverage
Consolidated Edison's costs related to Superstorm Sandy topped $431 million.
Gap reported higher material costs for cotton arising from precipitation changes and drought in China
Companies are poised to make a real difference in the fight on climate change while strengthening their bottom line. Mitigating the risks from climate change simply makes good business sense considering a study by Business for Social Responsibility published last month which says the exposure to the risks from climate change are on the rise. Some estimate the cumulative global cost could be as high as $4 trillion by 2030. The time to act is now. These costs are only going to increase the longer we delay investing in a low-carbon future.
National Climate Assessment Finds Warming Could Surpass 10 Degrees
The National Climate Assessment was released this week, which summarizes climate change's impacts on the United States, now and in the future. Produced by a team of more than 300 experts and guided by a 60-member Federal Advisory Committee, the study was also extensively reviewed by the public, federal agencies and a panel of the National Academy of Sciences.
The report finds that if greenhouse gas emissions continue to increase, global warming could exceed 10 degrees by the end of the century. A quote from the study's overview says, "This National Climate Assessment concludes that the evidence of human-induced climate change continues to strengthen and that impacts are increasing across the country."
This scientific report is mandated by Congress and is the pinnacle of years of work by hundreds of the nation's leading climate experts. They reviewed the scientific literature and summarized how climate change is affecting our country. The two main conclusions are:
The planet's climate is changing; it is apparent across the U.S. and the last 50 years' worth is chiefly due to human activities, particularly the burning of fossil fuels.
Extreme weather is on the rise in recent decades and new, stronger evidence confirms that some of these increases are human-caused.
Our homes, food, water and the very air we breathe are being affected.
Global warming is more than something that our children and future generations will face. It is our reality now. Climate change is already affecting our country and economy. Now that the situation is hitting home, perhaps we will start to make the changes we must make to reduce our carbon footprints and fund clean energy projects.
Read the most recent National Climate Assessment's Overview here.
Plant Trees on Earth Day
Earth Day is here! It's a great day to plant trees and here is your chance to enter a drawing for a $500 Restaurant.com eGift card and also we'll plant 100 trees on behalf of the winner. For every $25
donation to plant 25 trees, you'll receive an entry into the contest. So if you donate $50 to plant 50 trees, you'll receive two drawing entries!
Please use this link - https://carbonfund.org/plant-trees-dine-free?partnercode=ED14Contest
Participants receive a dining rewards eGift card through Restaurant.com, which is good on over 50,000 deals nationwide and never expires. Select from three simple tree-planting options:
- Plant 25 Trees for $25, Receive a $50 eGift Card
- Plant 50 Trees for $50, Receive a $100 eGift Card
- PLANT 100 TREES FOR $100, RECEIVE A $500 eGIFT CARD!
Our goal is to plant 10,000 trees in Haiti for Earth Month. Haiti has faced significant natural disasters of late, primarily earthquakes and landslides. The worst effects of these natural disasters are linked to deforestation and unsustainable land management.
Also, Haiti is the poorest country in the western hemisphere, whose history is marked with political instability and poverty. When you plant trees in Haiti, your donation helps us provide agricultural techniques and 400,000 seedlings to 800 farmers over the next year. Additionally, you'll be entered into our contest for a $500 Restaurant.com eGift card!
Choose to make a difference and plant trees on Earth Day.
Money Talks Even with Global Warming
You would think that out of all the industries in the world, the one that would be most concerned with climate change would be the insurance industry. Take a look at the costs for Superstorm Sandy alone. The extreme hurricane caused damage estimated at nearly $75 billion. According to a press release last month by the Property Casualty Insurers Association of America, 2012 cost insurers $35 billion in privately insured property losses, which is $11 billion more than the average over the last decade.
Insurers, and the reinsurance companies that shoulder much of the ultimate risk in the industry, heavily rely on scientific thought and not which way the political wind is blowing on global warming. They are comfortable with the scientific consensus that the rampant burning of fossil fuels is the main cause of climate change. Despite their confidence, the question remains, what is the insurance industry doing about global warming considering the problem directly impacts their own interests?
Surprisingly, the answer is not much. Insurers mainly focus on zoning regulations and disaster alleviation since the industry is disinclined to enter energy policy's controversial fray. Furthermore, insurers are more insulated from climate change's devastation than at first meets the eye. The federal government covers flood insurance, which is an enormous risk during extreme weather. Additionally, insurers adjust to higher risks by raising premiums or dropping coverage. So successfully that despite Superstorm Sandy and the protracted drought that ravaged the Midwest Corn Belt, property and casualty insurance in the United States was more profitable in 2012 than in 2011.
However, there are signs that the insurance industry is looking increasingly favorably on a carbon tax. The true costs are placed on the polluters with a carbon tax rather than being passed on to the rest of us. Also, they're encouraged to pollute less. Most insurers would prefer a carbon tax over a host of additional regulations from the Environmental Protection Agency (EPA).
Although the industry is warming to the idea of a carbon tax, they're still hesitant to throw all of their weight behind it. Again, money talks; insurers haven't yet experienced heavy losses from climate change. The exception is 2004 and 2005 when a series of hurricanes including Katrina, the costliest natural disaster in the history of the United States, caused damage worth more than $200 billion.
So the bottom line is that if these storms continue to hit people and businesses in the wallet, then eventually even the staunchest global warming disbelievers will admit the obvious. However, we need to do what we can in the meantime to avert global disaster. We don't want to pass the point of no return.
Over Half of Americans Connect Extreme Weather and Climate Change
In a previous blog post about The Art of Climate Change Communication, I covered the six American publics and how they perceive climate change. The Dismissive is one of the smallest groups, making up a mere eight percent of the American public. They do not believe climate change is happening, nor do they believe it is human caused or a serious problem. Although small, they are very vocal. Sometimes it's easy for climate change communicators to be discouraged by this group. Nonetheless, now there is evidence that more than half of Americans (58%) say, "global warming is affecting weather in the United States."
The Extreme Weather and Climate Change in the American Mind report is based on findings from a nationally representative survey – Climate Change in the American Mind – conducted by the Yale Project on Climate Change Communication and the George Mason University Center for Climate Change Communication. These two organizations interviewed 1,045 adults between April 8 and 15, and found that "many Americans believe global warming made recent extreme weather and climatic events 'more severe,' specifically: 2012 as the warmest year on record in the United States (50%); the ongoing drought in the Midwest and the Great Plains (49%); Superstorm Sandy (46%); and Superstorm Nemo (42%)." The survey has a margin of error of +/- 3 percentage points.
Typically, climate scientists avoid making a connection between climate change and the day-to-day weather. Their stance used to be that no single weather event is caused by climate change. In recent years, however, climate science has advanced to the point where researchers can see climate change's impact on individual heat waves, droughts, hurricanes and other storms. At the very least, many are ready to admit that climate change makes extraordinary weather worse. And most of the American public agrees.
The report released this week also highlighted that, "overall, 85 percent of Americans report that they experienced one or more types of extreme weather in the past year, most often citing extreme high winds (60%) and extreme heat (51%)." It is part of The Psychology of Climate Change that humans need to tangibly experience phenomena in order to connect with it on a deeper level. We comprehend global warming is a serious threat more easily when we see the effects of extreme weather events such as Superstorm Sandy.
While it is vindicating to climate change communicators that our country is beginning to make the important connection between climate change and extreme weather, I am hoping the knowledge coalesces into further global warming realizations and ultimately stimulates a grass-roots movement that engenders meaningful change. Knowing there is a problem is an important first step. Doing something about the problem is an even more important next step.
The Psychology of Climate Change
Regular readers of this blog are all too aware of the dangers that are starting to manifest regarding global warming. Given the reality of 2012 being the hottest year on record, and other climate change related disasters such as Superstorm Sandy, why isn't more being done domestically and globally to avert this crisis? The answer is in our psychology as humans.
Anthony Leiserowitz, Director of the Yale Project on Climate Change Communication and a Research Scientist at the School of Forestry and Environmental Studies at Yale University, specializes in human behavior, in particular the psychology of risk perception and decision making as it relates to global warming. He is an expert on U.S. and international perception of climate change risks, support and opposition for climate policies, and willingness to make individual behavioral change. Leiserowitz points to humans' needs to tangibly experience phenomena in order to connect with it on a deeper level. The first problem with the issue is that we cannot see carbon dioxide. Perhaps if we could see blue smoke, for example, billowing around us we would be more motivated to immediately tackle global warming.
The climate change problem is further complicated by its faceless nature. There isn't one country or person we can point to as causing global warming. We are all responsible on a daily basis. Then add to that there's the fact that climate change is not an immediate threat. It's certainly becoming one, but it takes time for the planet to heat up and we are fast approaching the point of no return.
Many people do not understand how a few degrees one way or the other will make a difference to the planet. Leiserowitz likened it to a fever in an episode titled, "Encore: Ending the Silence on Climate Change" this month on Bill Moyer & Company. "People often will say, 'Wow, you know, four, five degrees, that doesn't sound like very much. I mean, I see the temperature change more from night to day.' But it's the wrong way to think about it. I mean, think about when you get sick and you get a fever, okay. Your body is usually at, you know, 98.7 degrees."
He continued to say, "If your temperature rises by one degree you feel a little off, but you can still go to work. You're fine. It rises by two degrees and you're now feeling sick, in fact you're probably going to take the day off because you definitely don't feel good. And in fact, you're getting everything from hot flashes to cold chills, okay. At three you're starting to get really sick. And at four degrees and five degrees your brain is actually slipping into a coma, okay, you're close to death. I think there's an analogy here of that little difference in global average temperature just like that little difference in global body temperature can have huge implications as you keep going. And so unfortunately the world after two and especially after three degrees starts getting much more frightening, and that's exactly what the scientists keep telling us. But will we pay attention to those warning signs?"
My next blog post will discuss how to effectively communicate about climate change to overcome some of the psychological challenges humans face outlined in this post. There are ways to get the public to pay attention to, and in fact, engage on the issue of global warming. However, there is an art to it.
US Federal Government Identifies Climate Change as a High-Risk
The Government Accountability Office (GAO) delivered the yearly update of the High-Risk Series report to Congress this week, which officially elevated the threat of climate change. The report contains the greatest threats the government faces in carrying out federal programs, and the GAO is responsible for identifying items such as flaws in the defense contracting process and health care program fraud.
This year the GAO believed it had to highlight the risk from climate change despite some members of Congress' dismissal or outright denial of global warming. Regardless if some in Congress do not like the move, the GAO is supported by the information coming from the National Academy of Sciences and even from the federal government's own global change research program. The GAO did, however, sidestep the issue of what is causing climate change. Instead they focus on urging lawmakers to prepare, and most of all, budget for more disasters.
The number of disasters in 2012 was above 90, a record number. The federal government's exposure to the increasing number of disasters from extreme weather brought about by global warming includes owning hundreds of thousands of buildings, the operation of defense installations, financial disaster assistance to local governments, and managing crop and flood insurance programs.
Even if the lawmakers cannot agree on climate change, the fact is that a wide variety of disasters are on the increase and Congress has not planned or budgeted for them. The time for ignoring the issue is past. Hopefully Congress will heed the warnings and begin addressing our country's part of global warming in a meaningful way. If they do not, the issue may be taken out of their hands. President Obama said in this week's State of the Union address that, "I urge this Congress to get together, pursue a bipartisan, market-based solution to climate change, like the one John McCain and Joe Lieberman worked on together a few years ago. But if Congress won't act soon to protect future generations, I will."
Climate Change News Coverage Declines in 2012 but Local Governments Heed Warning Signs
The National Oceanic and Atmospheric Administration (NOAA) confirmed this week that 2012 was officially the warmest year on record in America's contiguous 48 states, based on 118 years of temperature records dating back to 1895. Despite this fact, news coverage of climate change actually declined in 2012. According to The Daily Climate, worldwide climate coverage decreased by two percent between 2011 and 2012, which represented the fewest number of published stories since 2009.
Last year the US was experience droughts in more than just rainfall. During the presidential election there were accusations of a "climate silence" until Superstorm Sandy devastated the East Coast in the days leading up to the election. In President Obama's acceptance speech he said, "We want our children to live in an America that isn't burdened by debt, that isn't weakened by inequality, that isn't threatened by the destructive power of a warming planet."
However, President Obama's statement has not reassured everyone that he and Congress are going to make any meaningful efforts to tackle carbon pollution and climate change. In fact, the League of Conservation Voters and a coalition of 70 environmental organizations recently wrote an open letter to President Obama, which encouraged him to spotlight climate change during his second term. A quote from the letter includes, "Cutting carbon pollution at home and rejecting dirty fuels will establish America's leadership and credibility, enabling [President Obama] to create clean energy jobs in the United States while forging an effective international coalition to cut global carbon pollution."
Whether or not President Obama and Congress heed the global warming warning signs, the bright spot is that local governments are undertaking real strategies to mitigate and adapt to climate change right now. ICLEI USA, a network of local governments working to address climate and sustainability challenges, recently highlighted 20 communities across the continental US that are leading the efforts to plan for the future and respond to extreme weather. Some particularly prominent examples by local governments include:
- Atlanta, GA – Urban heat island effects worsened by hotter seasons. Addressing the problem with a climate action plan, including cool roof/pavement standards and 10,000 new planted shade trees.
- Chicago, IL – Responding to extreme heat and flooding with the milestone Chicago Climate Action Plan and the most installed green roof square footage in the country.
- Eugene, OR – Ravaged by major wildfires and mega-dry conditions. Mitigating these issues by increasing water conservation, reducing hydroelectric power demand and planting drought-resistant trees.
- Miami Dade Count y, FL – Known as the most vulnerable city in the world to sea level rise as demonstrated by severe flooding. Urban planning now addresses sea level rise and disaster response, and they're also investing millions in flood mitigation projects.
- New York, NY – Suffered $19 billion in damage from Superstorm Sandy. Taking positive action with a $2.4 billion green infrastructure plan, restoring barrier wetlands, and initiating a climate risk assessment requirement for new developments.
It's wonderful to see these steps being taken towards a more sustainable future. It would be even better if federal leadership ensues, taking their cues from local governments. Media silence or not, climate change is here and further delayed action will only result in catastrophic results. The time is now to secure a low carbon global economy and thereby the planet for current and future generations.
2012 Retrospective – Were this Year's Events Enough to Spur Lasting Climate Change Efforts?
This year offered several events that shone a spotlight directly on the important and urgent issue of climate change, but the question remains, "Was it enough to bring about meaningful efforts to reduce climate change?"
June of 2012 presented the United Nations Earth Summit, held in Rio de Janeiro, Brazil which disappointed many as international representatives hemmed and hawed instead of establishing true endeavors to tackle global warming. Meanwhile the continental United States embarked on summer heat waves that were some of the hottest in its history.
This year also saw drought cover more than half the country; farmers suffered as their crops and animals died.
Then October of 2012 brought superstorm Sandy, this year's biggest example of extreme weather and a deadly harbinger of the devastating effects of climate change. Can we continue to sit idly by in the face of all these signs that global warming is making broad changes to our planet? Should we leave these environmental problems for our children to face as we continue down an unsustainable path?
The close of the year is a time to reflect on the previous events of the year and make resolutions for the coming year. Let's pledge to make 2013 the year where we confront climate change in every possible way. We can all embark on energy efficiency efforts; reducing what we can and lowering our carbon footprints. Every bit helps. Then it is a powerful combination to offset the rest of our carbon emissions. It would be a genuine shame to let the lessons of this past year slip from our consciousness while there is still time and so much that can and should be done to address climate change.


text:
You searched for: Subjects United States Remove constraint Subjects: United States Subjects Military Personnel Remove constraint Subjects: Military Personnel Subjects Personnel Turnover Remove constraint Subjects: Personnel Turnover Titles General orders. No. 214 Remove constraint Titles: General orders. No. 214 Start Over
1 to 1 of 1
Search Results
- Author(s):
- Townsend, E. D. (Edward Davis), 1817-1893
United States. Adjutant-General's Office
- Publisher:
- [Washington : War Dept., Adjutant General's Office, 1863]
- Subject(s):
- Military Personnel
Personnel Turnover
American Civil War
United States
Ord, Edward Otho Cresap, 1818-1883.
McClernand, John A. (John Alexander), 1812-1900.
United States. Army.


text: The watchmaker Jaeger-LeCoultre is recruiting and is constantly on the lookout for talents, with an aim to sustain its 180 areas of expertise identified around the world. We attach great importance to the sustainability of our expertise and the skills that have been acquired by our Manufacture. This is why we encourage generational diversity in all our crafts, through a mentoring system offered to all our new employees.


text:
List of Parades for 2014 Mardi Gras: February 26 – March 3
The parades are growing more numerous the closer we get to the real Fat Tuesday! New Orleans and the surrounding cities are proud to be the real McCoy when it comes to Mardi Gras. Other places do it, but we … Continue reading


text:
Scroll to Previous Item
Scroll to Next Item
Emmerson™ Reclaimed Wood Expandable Dining Table
Act fast! Items with prices ending in $0.99 are final sale.
No longer available
Rustic meets relaxed. Featuring a butterfly mechanism that expands it up to 90" wide, the Emmerson™ Industrial Expandable Table has a classic silhouette that works with any style, from traditional to modern. Its reclaimed pine top is FSC® certified and shows the knots and natural imperfections that make each piece subtly one of a kind.
72"w x 38"d x 30"h; extends to 90"w.
FSC®-certified solid reclaimed pine; wax finish.
More about FSC®
The reclaimed pine comes from a variety of sources, including shipping pallets and packing crates.
Each piece tells the story of its previous life, often marked by scratches, color variations, stains, repair patches and natural imperfections that only add to its beauty.
Unfinished wood has a rugged surface texture that will soften with age and use.
Blackened metal base.
Seats 8; seats 10 when extended.
Butterfly extender located under the table's top (visible when compacted).
what west elm is doing to help you get a little greener.


text:
Dean's List at Vol State
Submitted on February 11, 2011 at 5:03 PM
Volunteer State Community College has released the names of students named to the Fall 2010 Dean's List. The Dean's List is composed of students who have completed a minimum of 12 semester hours in collegiate level courses in the current semester with a grade point average of at least 3.750. Students making the Dean's List are as follows:
In Tennessee
Amber Wix of Adams; Thomas Clark of Alexandria; Christopher Park, Josiah River and Jessica Wheeler of Antioch; Takashi Furnier, Harold Huckaby and Tessa Jones of Ashland City; Whitney Carmack, Melody Hauskins-Booth, Nycole Phillips, Heather Ray, Ariel Rippy, Kinsey Rippy, Matthew Sadler and Robert Ward of Bethpage; Stacey Connor and Daniel Tidwell of Brentwood; Roger Gentry of Brush Creek; Amanda Etheridge, Austin Grant, Mary Harper and Shanda Key of Carthage; Christina Gaston, Robert Hamlett and Tonya Moss of Castalian Springs; Charles Hodgson of Cedar Hill; Christy Delk, Chelsea Terry and Haley Wix of Celina; Theresa McMahon of Christiana; Stacey Green and Debra Holman of Clarksville; Lauren Fraser of Cleveland; Alesha Bilyeu, Lacy Carmack, Ashley Green, Travis Lee, Amy Mahoney, Chastity Perryman, Grace Rayburn, Cyndy Rocus, Crystal Sandlin, Andrea Stewart, Katie Way, William White, Danielle Wildman and Kirsten Wilson of Cookeville; Hannah Alber, Chelcee Albert, Janie Bresee, Michael Jackson, Jordan Levering, Kaila Peterson, Brant Pippin, Paul Pleiman, Elizabeth Sumners, Amanda Thompson and Chelsea Youngblood of Cottontown; Lavena Covington, Marilyn Powell and Ashley Simmons of Cross Plains; Jessica Christian of Dickson; Brandon Lanham of Dixon Springs; Ashley Ewen, Jonathan Ewen and Mary White of Elmwood; Lee Guidry and William Lampley of Fairview; Mugdha Borkar, Gregory Hooker, Kathryn Morrissey, Roxana Preda and Trisha Sextro of Franklin; James Allen and Crystal Hager of Gainesboro; Joseph Adams, Alexn Ahlschwede, Troy Amer, Katherine Armbruster, Mimoza Asllani, Charelle Baxter, Allen Boeninghaus, Harold Bowden, Amber Bush, Aris Buycks, Susan Clark, Christopher Climer, Matthew Cole, Christine Eardley, Cody Epps, Kayla Epps, Ricky Foutch, Angelica Fricke, Keri Fulks, Thomas Gabrielle, Lucas Gillespie, Morgan Goad, Anna Griffin, Kristen Hendrickson, Heather Hickox, Brittney Hill, Kendra Hobbs, Veronica Hubble, Christian Kacar, Dominic Kacar, Rochelle Kelley, James Key, Michelle Leonardini, Gene Lester, Michelle Maron, Kelly Maxey, Michael McDonald, Lauren McLaughlin, Wendy Nabors, Rielly Newton, Renada Nicholas, Emily Oliver, Jacquelyn Oliver, Kelsey Patterson, Canton Phillips, Kyle Pierce, Katherine Puryear, Charlotte Ragland, Dwayne Reynolds, Melissa Richardson, Kayla Roberts, Amy Rouyer, Karrie Ryman, Gihe Shadd, Audrey Sizemore, Emily Smith, Rhonda Stewart, Rachel Stoller, Jennifer Thomas, Jaimee Troutt, Christopher Turner, Sarah Underwood, Mike Varsakelis, Jesse Watts, Amy Webb, Molly Webb, Rachel Williams, Cassandra Woodward, Stephanie Woodward, Mary Zhang and Tiffany Zwart of Gallatin; Matthew Allison, Denise Costanza, Elizabeth Duke, Brianna Fields, Emily Hayes, Cassandra Hunley, Devon Johnson, Caitlin Kinsey, Cassie Milliken, Raymond Mullins, Jesse Remboldt, Cadie Starr, Zachary Sullivan, Kristin West, Kristen Williams, Melanie Wright, and Justin Lee all of Goodlettsville; Kayla Hunt of Gordonsville; Brandon Kerley of Granville; Jonathan Adkins, Matthew Armstrong, Matthew Bilbrey, Molly Bridges, Jacob Camp, Jason Dority, Anna Hardy, Wade McCarroll, Dennis Scales, Jennifer Vickery of Greenbrier; Ashley Beasley, Alan Berrington, Chelsea Gregory, Kyla Loerch, Alison Martin, Amber Spears of Hartsville; Akhiyar Ahmed, Morgan Andrews, Olivia Bobbitt, Donny Bond, Janean Bowerman, Robyn Brewer,Sierra Bruner, Trevor Coffee, Catherine Coombs, Mary Crutcher, Carlton Douglas,Carly Edwards, Mark Gay,Jonathan George, Hiba Ghanem, Daniel Hader, Ala Hardwick, Alyssa Hillis, Catherine Hull, Christie Hunter, Amber Jarles, Krista Johnson, Dennis Jones, Shea Jones, Dennis Klotter, Michael Lee, Stephanie Lovelace, Matthew Lucas, Andrea Maffei, Sydney Marez, Stephanie Marrano, Matthew Martin, Cameron Mason, Monica McCord, Weylon Mclerran, Ryan McPeak, Ethan Minor, Joshua Nicholson, Amanda Nutter, Leslie Odom, Joseph Owens, Chelsea Parker, Stuart Parry, Ashley Paul, Christian Powell, Michelle Powers, Tammy Pritchett, Katelyn Rickards, Kimberly Rollins, Sara Romans, Arianna Rubi, Jennifer Rutter, Christin Sites, Cody Taylor, Aaron Upshaw, Sarah Vaughn, Beth Walker, Sherry Walker, Addison Wall, Jason Wesley, Colby West, James Wiggins, Meiyi Xie, Matthew Allen, Amanda Ragland of Hendersonville; Anna Bachelder, Jenifer Baker, Daniel Dingeldein, Johnathon Kornblee, Tressie Robinson, Travis Rush of Hermitage; Gary Bickle, Megan Nivens, Tristan Watson of Hilham; Lezley Chase of Huntingdon; Robert Hull of Jamestown; Shannon Cole,and Cody Flatt of Joelton; Gary Stallcup of La Vergne; Elijah Carter, Holly Doss, Kenneth Driver, Kayla Keene, Micah Kingery, Alen Liu, Sherry Main, Jeanette Moore, Amanda Vaughn, Crystal Watson, AshleyWillis of Lafayette; Christina Allen, Kayla Baird, Diana Broxson, Donald Chamberlin, Hope Chrisawn, Donald Crabtree, Casey Dunnam, Bradley Frisbey, Jeffrey Gammons, Rebecca Hamblen, Tiffany Hawkins, William Horne, Jacqulene Malone, Heather Meadows, Steve Moon, Cody Morel, Timothy Patterson, Edwin Pink, Tazlyn Saez, David Schaffer,Jesse Smith, Adam Snider, Brian Tomlinson of Lebanon; Brandi Keisling, Janice Ledbetter, Devin Thompson, Livingston; Conrad C'deBaca, Tim Dobbins, Richard Fortenbery, Ana Galvan, Jennifer Gates, Adam Gilliland, Sara McDonald, Michelle Raborn, Tameka,Walker, Marale,Wise of Madison; Christopher Abbott of Monterey; Lee Butler, Adam Cash, Matthew Childress, Taylor Collins, Laura Combs, Joshua Eldridge, Stephanie Gastley, Erica Gaudin, Amber Green, Michael Hannon, Nathan Jackson, Kelly Johnston, Katherine McClinton, Zachary Roach, Stephany Schroder, Garrettt Travis, Christopher White and Melissa Whited of Mount Juliet; Rebecca Barber, Natalie Dorak, Andrea Eufinger, Jody Geater, Laura Hoopes, Rachel Jones, Kristy Knight, Jamie McQuaid, Leslie Pedigo, Jennifer Revalee, Ryan Rosenthal, Seth Strickland and Justin Whited of Murfreesboro; Laura Albescu, Tressa Buschert, Daniel Cardwell, Julius Davis, Katie Dossey, Sarah Gregory, Craig Jones, Jonathan Krueck, Michael Lotfi, Joshua Miller, Hayley Morgan, Brian Mushamba, Elena Orr, Brandon Powell, Tara Powell, Marco Prase, Jessica Reeves, Joshua Rudolph, Veronica Russell, Alex Shaw, James Snider, Alanna Stotler, Janet Tolliver, Melanie Walker, Shara Walker, Kristen Weatherly, Roger Willocks and Stephanie Wyatt of Nashville; Buford Jones of Nolensville; Mario Campopiano, Amanda Fultz, Shellie Leach and Cody Partlow of Old Hickory; Kelleyshawn Brown and Amber Tatum of Orlinda; James Endsley, Jason Hiett, Natasha Maynard and Jordan Shoulders of Pleasant Shade; Lori Louallen of Pleasant View; Tonya Adams, James Clemmons, Megan Dowling, Shannon Dunham, Shane Essary, Jessie Ferrell, Kenneth Gassaway, Kristie Gosar, Philip Gray, Daniel Gregory, James Hughes, Bradley Jackson, Courtney Lane, Steven Littrell, Stephanie Livingston, Zack McCullough, Lauren McMahan, Julia Munday, Brandon Shaw, Richard Simpson, Sylvia Sprinkles and Leslie Walker of Portland; Dana Goad of Red Boiling Springs; Candace Copeland and Kasey Martin of Rickman; Michael Wilmore of Riddleton; Charles Suddeth of Savannah; Avarie Maynard of Smithville; Amanda Edgin of Smyrna; Maureen Herbrandson, Logan Hodge, Ashley Holman, Daniel Norrod, Joah Simmons of Sparta; Korri Bonebrake, Rachel Campbell, Jarrett Crawford, Laura Hastings, James Lipscomb and Courtney Robertson of Springfield; Robert Cox and Sara Dickey of Summertown; David Seay of Thompsons Station; Meredith Peck of Wartrace; Debra Barnard of Watertown; Kenneth Brown, Jennifer Carter, Aaron Doyka, Caitlin Emmert, Jessica Farmer, Jeremiah Hackert, Donna Herald, Nancy MacDonald, Brittany Miller, Dakota Shrum, Christopher Smith and Destiny Smith of Westmoreland; Christina Whitley of White Bluff; Erica Bodley, Erica Carney, Megan Farmer, Donald Franks, Brandon Funk, Julie Harrison, Shelby Hooper, Jordan Hoover, Corey Jones, Goran Larsson, Kayla Maxedon, Elizabeth Mayes, Timothy Moran, Haley Porter, Nathaniel Rogers, Mary Shaw, Anthony Taylor, Sean Toland, Cynthia Tribell, Kayla Walker, Brittney Welch and Leslie Woerth of White House; Baily Butler of Winchester;
In Kentucky
Holly Queen of Adolphus; Craig Higginbotham of Bowling Green; Stephanie Smith of Franklin; and Carl Cline, Glenda Murley and Lorinda Taylor of Scottsville;
In Georgia
Michael Massi of Powder Springs;
And In Virginia
Chella Glennon of Roanoke.
A service provided by the Office of Public Relations.


text:
Banned because your signature is way too long.
Banned because your signature is way too long.
Banned because you don't have a signature.
Banned because you take my opinions way too seriously.
Banned because I don't like people insulting my work.
Banned for not banning anyone like you're supposed to in this thread.
Banned because it was not an insult.
Banned because your sig is very funny, though a little outdated by now.
I said, "Hi, Greg. I'm the creepy girl." He chuckled, then wanted a handshake and I gave it. I wanted a hug and he gave it. One of his sons was there, too. Cute. Then Pete got him to autograph my sign for me because I was too polite to ask myself since he was on his way to eat. Pete also took this of photo of him holding it. - 8/2/2014.
Our official webpage: http://offspringunderground.com/
Banned because you created the Greg's thread only 10 days before his birthday and not 20 or 30
I can't ban Melyssa because of your post, therefore banned.


text:
Women's Berne Jackets
There are no products matching the selection.
I am writing to let you know just how pleased I was with your handling of my recent return/exchange experience. I returned a pair of boots for a factory flaw and your customer service representative Brandon made the entire process easy and most satisfactory. I appreciated the fact that there were no costs involved in returning my purchase to you and the fact that I received my replacement boots in a very short time without further effort from me. I am extremely pleased with the way that my return was handled and just wanted to thank the Working Person's Store for providing such excellent, prompt and most courteous customer service. I will be recommending your company highly to others and just wanted to say thank you again for such a satisfactory and hassle-free customer service experience!"
Larry G. from Red Bluff, CA