text:
The Maps JavaScript API lets you customize maps with your own content and imagery for display on web pages and mobile devices. The Maps JavaScript API features four basic map types (roadmap, satellite, hybrid, and terrain) which you can modify using layers and styles, controls and events, and various services and libraries.
This documentation is designed for people familiar with JavaScript programming and object-oriented programming concepts. You should also be familiar with Google Maps from a user's point of view. There are many JavaScript tutorials available on the Web.
This conceptual documentation is designed to let you quickly start exploring and developing applications with the Maps JavaScript API. We also publish the Maps JavaScript API Reference.
Hello, WorldThe easiest way to start learning about the Maps JavaScript API is to see a simple example. The following example displays a map centered on Sydney, New South Wales, Australia.
let map: google.maps.Map; function initMap(): void { map = new google.maps.Map(document.getElementById("map") as HTMLElement, { center: { lat: -34.397, lng: 150.644 }, zoom: 8, }); } declare global { interface Window { initMap: () => void; } } window.initMap = initMap;
let map; function initMap() { map = new google.maps.Map(document.getElementById("map"), { center: { lat: -34.397, lng: 150.644 }, zoom: 8, }); } window.initMap = initMap;
/* * Always set the map height explicitly to define the size of the div element * that contains the map. */ #map { height: 100%; } /* * Optional: Makes the sample page fill the window. */ html, body { height: 100%; margin: 0; padding: 0; }
  <title>Simple Map</title>  <link rel="stylesheet" type="text/css" href="./style.css" />

Try Sample
Even in this simple example, there are a few things to note:
- We declare the application as HTML5 using the
<!DOCTYPE html>declaration.
- We create a
divelement named "map" to hold the map.
- We define a JavaScript function that creates a map in the
- We load the Maps JavaScript API using a
These steps are explained below.
Declaring your application as HTML5
We recommend that you declare a true
within your web application. Within the examples here, we've
declared our applications as HTML5 using the simple HTML5
as shown below:
<!DOCTYPE html>
Most current browsers will render content that is declared with this
DOCTYPE in "standards mode" which means that your application
should be more cross-browser compliant. The
DOCTYPE is also
designed to degrade gracefully; browsers that don't understand it will ignore
it, and use "quirks mode" to display their content.
Note that some CSS that works within quirks mode is not valid in
standards mode. In specific, all percentage-based sizes must inherit
from parent block elements, and if any of those ancestors fail to
specify a size, they are assumed to be sized at 0 x 0 pixels. For
that reason, we include the following

This CSS declaration indicates that the map container
(with id
map) should take up 100% of the height of the HTML
body. Note that we must specifically declare those percentages for
 and
 as well.
Loading the Maps JavaScript APIThe Maps JavaScript API is loaded using a
script tag, which can be added
inline in your HTML file or dynamically using a separate JavaScript file. We recommend that you
review both approaches, and choose the one that is most appropriate for how the code in your project
is structured.
Inline Loading
To load the Maps JavaScript API inline in an HTML file, add a
script tag as show below.

Check the network traffic generated by your website in the browser.
In Chrome, this can be viewed using the
DevTools Network tab.
Here you will see the network requests made by your website. Requests made using the
Maps JavaScript API will be under the path
maps/api/js. Here you can confirm if the requests are using the
keyparameter. It may be helpful to filter your network traffic by
maps/api/jswhen viewing the Network tab.
No, I am not using an API key.
To get an API key, click the button below. If you do not see a guided setup, follow the
full instructions at Get Started with Google Maps
Get Started
Yes, I am using an API key.
Great! Let's move on and check if a billing account is attached to your project.
Is a billing account attached to your project?
I'm not sure. How can I check if billing account is attached to my project?
Go to the Billing page in the Google Cloud Console and select the project under which your API key was created. To confirm the key is associated with the project:
- Go to the Credentials section, which can be accessed from the left side bar under Google Maps Platform > Credentials.
- Check that the API key you currently use on your website is listed. If that's not the case, switch to a different project, and check the credentials there.
- If you cannot locate the project for your API key, you may have lost access to this project.
Ask others in your organization for help. If the original project cannot be located, you should:
- Create a new project. This can be done by selecting New Project from the projects list, or by selecting Create Project via the Resource Manager page.
- Create a new API key. This can be done on the Credentials page. Once there click Create credentials and then select API key.
Once you have located your project in the Cloud Console, check if a billing account is attached by navigating to the Billing section in the left side menu.
No, a billing account is not attached to my project.
Go to the Enable Billing page in the Cloud Console and add a billing account to your project. For additional information, see Get Started with Google Maps Platform.
Yes, a billing account is attached to my project.
Great! Let's make sure the provided billing method is valid.
Is the provided billing method no longer valid (for example an expired credit card)?
You can add, remove, or update a payment method in the Cloud Console.
Is there an exceeded self-imposed daily limit on the API?
If you have set a daily limit on any of your APIs, which is common to prevent unexpected increases, you can resolve this by increasing your daily limit.
You can check your daily limits by going to the APIs & Services Dashboard in the Cloud Console. Once there:
- Select a project if prompted.
- Select an API from the list, then click the Quotas tab.
Does your API key have an IP addresses restriction?
API keys with an IP addresses restriction can only be used with web services that are intended for use from the server side (such as the Geocoding API and other Web Service APIs). Most of these web services have equivalent services within the Maps JavaScript API (for example, see the Geocoding Service). To use the Maps JavaScript API client side services, you will need to create a separate API key which can be secured with an HTTP referrers restriction (see Get, add, and restrict an API key).
If your code isn't working:
To help you get your maps code up and running, Brendan Kenny and Mano Marks point out some common mistakes and how to fix them in this video.
- Look for typos. Remember that JavaScript is a case-sensitive language.
- Check the basics - some of the most common problems occur with the
initial map creation. Such as:
- Confirm that you've specified the
centerproperties in your map options.
- Ensure that you have declared a div element in which the map will appear on the screen.
- Ensure that the div element for the map has a height. By default, div elements are created with a height of 0, and are therefore invisible.
- Confirm that you've specified the
- Use a JavaScript debugger to help identify problems, like the one available in the Chrome Developer Tools. Start by looking in the JavaScript console for errors.
- Post questions to Stack Overflow. Guidelines on how to post great questions are available on the Support page.


text:
Important Announcements regarding the Blueboard will be posted here.
Please read the RULES, which are here. Want the history of the Blueboard? It's here! Need help using the board? Ask here!
Moderator: andracill
Blueboard history, info, and user hints by founder Verla Kay.
Moderator: Verla Kay
Discussions about creating picture books.
Moderator: christripp
Discussions on the craft of writing books for children aged 8 to 12.
Moderator: David Wright
Discussion of genres (not age groups, which have their own boards!) -- contemporary, fantasy, historical, sci-fi, adventure, etc.
Moderator: Debbie Vilardi
Discuss research methods, post helpful sources, or ask research questions. Note: ONLY request research help here after you have exhausted your own sources.
Moderator: Vijaya
Discussions about creating graphic novels.
Moderator: dewsanddamps
Board-wide news and information. Please read new posts!
Moderators: Verla Kay, AnneB
Here's the place to chat about books you love and hate.
NaNoWriMo, Storystorm, Inktober, 12 x 12, Author Mentor Match, links to kidlit publisher or magazine contests, etc.
This board is for the use of the Florida Region of SCBWI.
Moderator: LindaB
This is a board for the SCBWI Region of Indiana.
Moderator: Kristi Valiant
This board is for all SCBWI Members in Japan to share information and concerns pertaining to their region.
Moderator: seamikan
Moderator: Kimberly Z.
This is a discussion board for the Brazos Valley Region of Texas.
Moderators: lizbmertz, Candilynn
108,587 Posts8,097 Topics14,797 Members
Page created in 0.148 seconds with 18 queries.

subset: commoncrawl


text:
Last updated by James Nored Aug 22, 2009.
Welcome toMissional Outreach Network for the Missional Church
Sign Upor Sign In
Or sign in with:
12 members
19 members
20 members
35 members
57 members
46 members
93 members
48 members
29 members
Read James Nored's Daily News! Get MON by Email!
© 2023 Created by James Nored.
Powered by
Badges |
Report an Issue |
Terms of Service
Please check your browser settings or contact your system administrator.


text:
Saginaw, MI
About arait
This author hasn't written their bio yet.
arait has contributed 9271 entries to our website, so far.View entries by arait
You also might be interested in
Roseville, MN
Franklin, TN
Saginaw, MI
Copyright © 2023 · National Association of Plan Advisors (NAPA) · All rights reserved.
Privacy Policy | Terms of Use


text:
1. What is the 48 Hour Film Project?It's your chance to stop talking and start filming! The premise? Filmmaking teams have just one weekend to make a short film. All creativity—writing, shooting, editing and adding a musical soundtrack—must occur in a 48 hour window beginning Friday evening at 7:00pm and ending Sunday at 7:00pm. The following week, the completed films are screened to an eager audience.
2. How much does it cost?
The registration fee is for the entire team and includes two free tickets to the screenings (which are given to the team leader).
In the United States, registration fees vary from $125 to $188 per team, as follows:
First Year Cities
$125 to $145 for each team
Repeat Cities
Fees range from $148 to $188 depending on the registration period: Early Bird, Regular or Late.
See Also
3. If I have to drop out, how do I withdraw?
48 Hour Film Project Refunds in the United States
If a team (Entrant) must withdraw, refunds will be paid on the following schedule:
- Notify the 48HFP more than 30 days prior to your competition weekend, receive a full refund minus a $25 administrative fee.
- Notify the 48HFP 7-30 days prior to your competition weekend, receive a full refund minus a $35 administrative fee.
- No refunds less than 7 days prior to Kickoff event.
NOTE #2: In lieu of a refund, Registration may be transferred to a different City Project (depending on availability) or credited to the following year at no charge. This request must be made through the Withdraw link below at least seven (7) days prior to Kickoff.
The 48HFP Refund Policy may vary in other countries.
To Withdraw
To withdraw and, if eligible, request a refund or a transfer, the team leader must complete this request form:
4. When will the 48 Hour Film Project come to my city?The dates for each city are listed on our 48 Hour Film Project website. If we do not have listed dates, then the dates have not yet been determined. If you want to be the first to find out when the 48 Hour Film Project is coming to your city, sign up for your city's newsletter.
See Also
5. What are the films about?
That's up to the filmmaker; however, each team must select the genre for its movie in a random drawing 15 minutes before the start of the competition. There are 30 different genres. Each team will receive two genres from which to choose.
In addition, teams are given a character, a prop and a line of dialogue that must appear in their film.
See Also
6. Who sees the films?
The films screen to live audiences at a local theater. Of course the filmmakers, actors, family and friends are there to enthusiastically support the premiere of the weekend's work. But also supporters of the local film community, and discriminating viewers who want to see something new—something raw and alive—are there to feel the creative energy.
7. Who are the filmmakers?
The 48 Hour Film Project is open to all filmmakers, beginners, pre-professionals and pros. Even hobbyists are encouraged to participate. The Rules state that all team members (crew and cast) must be volunteers. Experience does not always equate to awards. Beginner teams have won big awards, too. And, you never know who you may see in a 48 Hour film—Martin Freeman, Penn of Penn and Teller, Dennis Farina, and Nick Clooney have all appeared in 48HFP films.
See Also
8. Is there a limit to the number of people on a team?No. Our smallest team was just one person—he sets up the camera then runs around to act. Our largest team to date was a team from Albuquerque with 116 people and 30 horses! The average, though, is about 15 people per team.
9. Am I allowed to be on more than one team?Yes, you're allowed. We hope you can make the scheduling work out!
See Also
10. How long are the films?
The films are short; they must be a minimum of 4 minutes and a maximum of 7 minutes long Short is good. Not only are shorter films tighter and usually more interesting, they are more marketable.
See Also
11. Where and when are they shown?
On the first few days following the competition deadline, the movies are screened at a grand premiere in a local movie theater. An eager audience of tired, excited filmmakers, crews and friends are in attendance to cheer on the films.
12. How is the event advertised?The event is advertised by word of mouth, on the web, and via local press. Local filmmakers and organizations are our most vocal supporters and do a great job spreading the word. In each city, the 48 Hour Film Project has generated considerable interest from local and national media. From CNN to the Washington Post and LA Times—we've had coverage in hundreds of media outlets to date.
13. What should I do with my film after the competition?Get it out there! Enter it into festivals, play it in public screenings, upload it to websites, get it on television, and show it to anyone you can. Be sure you abide by any restrictions in the Team Leaders's Agreement.
See Also
14. May I show a modified version of my film?
Yes, presuming that the showing adheres to the Team Leader's Agreement that you signed when entering the 48 Hour Film Project. If it is a modified version of a 48 Hour Film Project film, please include a title card and a mention in the end credits that say:
The concept for this film developed during the 48 Hour Film Project. www.48hourfilm.com
15. Is this a contest and will there be a "Best of" selection?Yes and yes. One film in each city will be chosen "Best of City".
See Also
16. Will I win?
Depends on what you mean by winning. Countless filmmakers over the years have told us that their filmmaking weekend was a fantastic experience. They loved getting to use their creative talents; they had fun with their friends; and they made a film, too! So if winning means having a great time, you've got a very good shot at it.
17. Will I get rich?
Probably not. Over the years a number of films have been purchased for distribution, but this is rare. However, quite a few 48HFP filmmakers have had success with their films in other festivals including SXSW. One team won a $100K filmmaking package at another festival. Quite a few filmmakers have made indie features and other filmmakers have used their 48HFP experience to get paying work.
Additionally, if the 48 Hour Film Project is able to distribute your film, you are entitled to the bulk of the proceeds. While the market for short films is nearly non-existent, the 48HFP garners more interest in our films because of the 48-hour concept and the fact that they are part of a bigger collection. In summing it up, while folks have lots of fun doing the 48 Hour Film Project, they don't make lots of money.
18. Who judges the films?In each city we gather a group of film and video professionals to serve as our judges. These judges generally have extensive experience within the field. We require these judges to be fair and impartial. Our judges donate their time and talent to rate the films. In addition to determining the winner they also select a number of other awards. The judges on the national/international level have included actors such as Julianne Moore, directors such as Simon West (Con Air), and editors such as Thelma Schoonmaker (Raging Bull, The Departed). But no matter how careful we are in selecting our judges, judging itself is extremely subjective. So many times, two regarded critics feel markedly differently about the same film—remember the long debate between Gene Siskel and Roger Ebert about Apocalypse Now; remember Pauline Kael's ambivalent review of Star Wars. Similarly, on many occasions our favorite 48 Hour Film Project film of the year has not even won its city. When it comes to evaluating art, a lot comes down to matters of taste.
19. Can I or my organization be a sponsor?Of course! Email Mark Ruppert, our Founder, to express interest.
20. Does the maximum length of the film include credits?
No. Your film may be 7 minutes long plus 1 minute of credits.
See Also
21. Are credits in the beginning permissible?
Opening credits are allowed. They do not count against the credit time limit. However, they do count against the 7 minutes of film. Remember, the audience is here to watch, not read.
See Also
22. Are we allowed to have footage under our closing credits?Yes, however, the narrative must end before the closing credits begin. So outtakes, Ferris-Bueller-like antics, or bonus scenes are allowed. But if we removed the credits, the movie should still feel complete.
See Also
23. Can I film outside of my city?Absolutely! The only requirements are that you have a representative from your team at the Kickoff and that you deliver your film to the Dropoff. Other than that, it's up to you. We've had teams shoot hundreds of miles away from their host city. We've even had a Boston team upload footage from Panama!
See Also
24. Are stock footage and photos allowed?Stock film and video footage is prohibited, except as part of a special effects filter. However, if you have the rights to them, then stock photos are permitted. In other words, you may use photos not taken during the 48 hour time period. Note that photos cannot be used in sequence to create the illusion of motion.
See Also
25. Is animation allowed?Yes. However—while you may use still drawings created before the Project—you may not use sequences of drawings created before the Project to create the illusion of motion. Using existing images and 3D objects is permissible, provided that you have full and permanent rights to them. Again, only animation created during the 48 hour period is allowed. And, as with a live action film, you must have all rights to the animation you submit.
See Also
26. What about special effects? What's allowed?You may use special effects that involve any of the allowed elements that you have rights to: still photographs, footage shot during the 48 hours, or footage rendered during the 48 hours. You may also use stock footage if it is part of a post-production effect or on a background screen or television and the stock footage is placed over or under footage that is shot within the 48 hours. Stock footage of people or other performers is not allowed.
See Also
27. May we include our logo that was made before the filmmaking weekend?Yes, provided that it begins the film and is shorter than five seconds long. Note that the logo does count against the 7 minute running time of the film.
See Also
28. Should we shoot in HD? Should we shoot in widescreen? Should we use surround sound?Unless you are otherwise notified, your film will be shown in Standard Definition in stereo or mono. So you may shoot in HD or use surround sound, but the film will generally not be projected that way. Please make sure that you adhere to the format requirements found on your city page.
See Also
29. Do I need to subtitle my film?No. However, if the judges in your city cannot understand your film, they are less likely to give it awards.
30. My file doesn't fit on my flash drive. What do I do?It might be that you've got the drive formatted for the wrong file system. Generally drives come formatted with the FAT32 file system, which cannot store files larger than 2GB. If you're on a Mac, format your drive to Mac OS X Extended (Journaled). If you're on a PC, format your drive to NTFS.
See Also
31. Have any of the movies been shot on film?
While it is rare that filmmakers shoot on film, it has happened a handful of times over the years. You must weigh the beauty of the picture and the experience of shooting on film with the time it takes to process the film. Teams who have done it in the past have had connections with labs that enabled them to develop the film with enough time for the teams to submit in the 48 hour time period. We were quite impressed!
See Also
32. Does every team member have to sign the Team Leader's Agreement?No, only the team leader needs to sign it. However, everyone who works on the film must sign the Liability Waiver form. See the production documents page for more details.
See Also
33. What's a logline?A logline is a very short, catchy summary of the story, usually not longer than one sentence. We ask you to provide a logline for your film on the Wrap Up Form. EXAMPLE: Transported to a surreal landscape, a young girl seeks a way home to Kansas, befriending along the way a scarecrow without a brain, a tin woodsman without a heart, and a lion without courage.
See Also
34. Can we submit a faxed release form?
Yes. If you are working with someone out of town, they may email or fax you their release. Simply include a paper copy of it with the rest of your paperwork.
See Also
35. How do we document public domain or royalty-free music and photos?
Have the person who has the rights to the music or materials sign the release form. In the case of royalty-free materials, this is the person who purchased them. In the case of public domain materials, this could be anyone on the team. Please also include information that shows your rights to the music or materials, such as a license, a purchase receipt, or a statement by the author.


text:
The wrong version of Kazakhstan's national anthem played at a sporting event. What was heard was Sacha Baron Cohen's parody from his "Borat" movie. And you can hear it on the RidicuList.
Post by: Anderson Cooper
Filed under: The RidicuList
Anderson Cooper goes beyond the headlines to tell stories from many points of view, so you can make up your own mind about the news. Tune in weeknights at 8 and 10 ET on CNN.
Questions or comments? Send an email
Want to know more? Go behind the scenes with AC361°


text:
Table of Contents
We suggest that before upgrading you also read the information in Chapter 5, Issues to be aware of for wheezy. That chapter covers potential issues which are not directly related to the upgrade process but could still be important to know about before you begin.
Before upgrading your system, it is strongly recommended that you make a full backup, or at least back up any data or configuration information you can't afford to lose. The upgrade tools and process are quite reliable, but a hardware failure in the middle of an upgrade could result in a severely damaged system.
The main things you'll want to back up are the contents of
/var/lib/apt/extended_states and the output of
dpkg --get-selections "*" (the quotes are important). If
you use aptitude to manage packages on your system, you
will also want to back up
The upgrade process itself does not modify anything in the
/home directory. However, some applications (e.g. parts
of the Mozilla suite, and the GNOME and KDE desktop environments) are known to
overwrite existing user settings with new defaults when a new version of the
application is first started by a user. As a precaution, you may want to make
a backup of the hidden files and directories ("dotfiles") in users' home
directories. This backup may help to restore or recreate the old settings.
You may also want to inform users about this.
Any package installation operation must be run with superuser privileges, so
either log in as
root or use su or sudo to
gain the necessary access rights.
The upgrade has a few preconditions; you should check them before actually executing the upgrade.
It's wise to inform all users in advance of any upgrades you're planning, although users accessing your system via an ssh connection should notice little during the upgrade, and should be able to continue working.
If you wish to take extra precautions, back up or unmount the
/home partition before upgrading.
You will have to do a kernel upgrade when upgrading to wheezy, so a reboot will be necessary. Typically, this will be done after the upgrade is finished.
There might be services that are offered by the system which are associated with packages that will be included in the upgrade. If this is the case, please note that, during the upgrade, these services will be stopped while their associated packages are being replaced and configured. During this time, these services will not be available.
The precise downtime for these services will vary depending on the number of packages being upgraded in the system, and it also includes the time the system administrator spends answering any configuration questions from package upgrades. Notice that if the upgrade process is left unattended and the system requests input during the upgrade there is a high possibility of services being unavailable[1] for a significant period of time.
If the system being upgraded provides critical services for your users or the network[2], you can reduce the downtime if you do a minimal system upgrade, as described in Section 4.4.4, "Minimal system upgrade", followed by a kernel upgrade and reboot, and then upgrade the packages associated with your critical services. Upgrade these packages prior to doing the full upgrade described in Section 4.4.5, "Upgrading the system". This way you can ensure that these critical services are running and available through the full upgrade process, and their downtime is reduced.
Although Debian tries to ensure that your system stays bootable at all times, there is always a chance that you may experience problems rebooting your system after the upgrade. Known potential issues are documented in this and the next chapters of these Release Notes.
For this reason it makes sense to ensure that you will be able to recover if your system should fail to reboot or, for remotely managed systems, fail to bring up networking.
If you are upgrading remotely via an ssh link it is recommended that you take the necessary precautions to be able to access the server through a remote serial terminal. There is a chance that, after upgrading the kernel and rebooting, you will have to fix the system configuration through a local console. Also, if the system is rebooted accidentally in the middle of an upgrade there is a chance you will need to recover using a local console.
The most obvious thing to try first is to reboot with your old kernel. However, this is not guaranteed to work.
If that fails, you will need an alternative way to boot your system so you can
access and repair it. One option is to use a special rescue image or a Linux
live CD. After booting from that, you should be able to mount your root file
system and
chroot into it to investigate and fix the
Another option we'd like to recommend is to use the rescue mode of the wheezy Debian Installer. The advantage of using the installer is that you can choose between its many installation methods to find one that best suits your situation. For more information, please consult the section "Recovering a Broken System" in chapter 8 of the Installation Guide and the Debian Installer FAQ.
initramfs-tools package includes a debug
shell[3] in the
initrds it generates. If for example the initrd is unable to mount your root
file system, you will be dropped into this debug shell which has basic commands
available to help trace the problem and possibly fix it.
Basic things to check are: presence of correct device files in
/dev; what modules are loaded (
/proc/modules); output of dmesg for errors loading
drivers. The output of dmesg will also show what device
files have been assigned to which disks; you should check that against the
output of
echo $ROOT to make sure that the root file system
is on the expected device.
If you do manage to fix the problem, typing
exit will quit
the debug shell and continue the boot process at the point it failed. Of
course you will also need to fix the underlying problem and regenerate the
initrd so the next boot won't fail again.
The distribution upgrade should be done either locally from a textmode virtual console (or a directly connected serial terminal), or remotely via an ssh link.
If you are using some VPN services (such as
In order to gain extra safety margin when upgrading remotely, we suggest that you run upgrade processes in the virtual console provided by the screen program, which enables safe reconnection and ensures the upgrade process is not interrupted even if the remote connection process fails.
You should not upgrade using telnet, rlogin, rsh, or from an X session managed by xdm, gdm or kdm etc. on the machine you are upgrading. That is because each of those services may well be terminated during the upgrade, which can result in an inaccessible system that is only half-upgraded. Use of the GNOME application update-manager is strongly discouraged for upgrades to new releases, as this tool relies on the desktop session remaining active.
The upgrade process described in this chapter has been designed for upgrades from "pure" squeeze systems without third-party packages. For the greatest reliability of the upgrade process, you may wish to remove third-party packages from your system before you begin upgrading.
Direct upgrades from Debian releases older than 6.0 (squeeze) are not supported. Please follow the instructions in the Release Notes for Debian 6.0 to upgrade to 6.0 first.
This procedure also assumes your system has been updated to the latest point release of squeeze. If you have not done this or are unsure, follow the instructions in Section A.1, "Upgrading your squeeze system".
In some cases, the use of apt-get for installing packages instead of aptitude might make aptitude consider a package as "unused" and schedule it for removal. In general, you should make sure the system is fully up-to-date and "clean" before proceeding with the upgrade.
Because of this you should review if there are any pending actions in the
package manager aptitude. If a package is scheduled for
removal or update in the package manager, it might negatively impact the
upgrade procedure. Note that correcting this is only possible if your
sources.list still points to squeeze
and not to stable or wheezy; see Section A.2, "Checking your sources list".
To perform this review, launch aptitude in "visual mode" and press g ("Go"). If it shows any actions, you should review them and either fix them or implement the suggested actions. If no actions are suggested you will be presented with a message saying "No packages are scheduled to be installed, removed, or upgraded".
If you have configured APT to install certain packages from a distribution
other than stable (e.g. from testing), you may have to change your APT pinning
configuration (stored in
/etc/apt/preferences and
/etc/apt/preferences.d/) to allow
the upgrade of packages to the versions in the new stable release. Further
information on APT pinning can be found in apt_preferences(5).
Regardless of the method used for upgrading, it is recommended that you check the status of all packages first, and verify that all packages are in an upgradable state. The following command will show any packages which have a status of Half-Installed or Failed-Config, and those with any error status.
# dpkg --audit
You could also inspect the state of all packages on your system using aptitude or with commands such as
# dpkg -l | pager
# dpkg --get-selections "*" > ~/curr-pkgs.txt
It is desirable to remove any holds before upgrading. If any package that is essential for the upgrade is on hold, the upgrade will fail.
Note that aptitude uses a different method for registering packages that are on hold than apt-get and dselect. You can identify packages on hold for aptitude with
# aptitude search "~ahold"
If you want to check which packages you had on hold for apt-get, you should use
# dpkg --get-selections | grep 'hold$'
If you changed and recompiled a package locally, and didn't rename it or put an epoch in the version, you must put it on hold to prevent it from being upgraded.
The "hold" package state for apt-get can be changed using:
# echo
package_name hold | dpkg --set-selections
hold with
install to unset the
"hold" state.
If there is anything you need to fix, it is best to make sure your
sources.list still refers to squeeze as explained in Section A.2, "Checking your sources list".
If you have listed the
proposed-updates section
in your
/etc/apt/sources.list file, you
should remove it from that file before attempting to upgrade your
system. This is a precaution to reduce the likelihood of
If you have any non-Debian packages on your system, you should be aware that
these may be removed during the upgrade because of conflicting dependencies.
If these packages were installed by adding an extra package archive in your
/etc/apt/sources.list, you should check if that archive
also offers packages compiled for wheezy and change the source line accordingly
at the same time as your source lines for Debian packages.
Some users may have unofficial backported "newer" versions of packages that are in Debian installed on their squeeze system. Such packages are most likely to cause problems during an upgrade as they may result in file conflicts[4]. Section 4.5, "Possible issues during upgrade" has some information on how to deal with file conflicts if they should occur.
Before starting the upgrade you must set up
apt's configuration file for package lists,
apt will consider all packages that can
be found via any "
deb" line, and install the package with the
highest version number, giving priority to the first line in the
file (thus where you have multiple mirror locations, you'd typically first name a local
hard disk, then CD-ROMs, and then HTTP/FTP mirrors).
A release can often be referred to both by its codename (e.g.
wheezy) and by
its status name (i.e.
unstable). Referring to
a release by its codename has the advantage that you will never be surprised by
a new release and for this reason is the approach taken here. It does of
course mean that you will have to watch out for release announcements yourself.
If you use the status name instead, you will just see loads of updates for
packages available as soon as a release has happened.
The default configuration is set up for installation from the main Debian Internet
servers, but you may wish to modify
to use other mirrors, preferably a mirror that is closest to you in network terms.
Debian HTTP or FTP mirror addresses can be found at http://www.debian.org/distrib/ftplist (look at the "list of Debian mirrors" section). HTTP mirrors are generally speedier than FTP mirrors.
For example, suppose your closest Debian mirror is
http://mirrors.kernel.org. When inspecting that
mirror with a web browser or FTP program, you will notice that the main
directories are organized like this:
http://mirrors.kernel.org/debian/dists/wheezy/main/binary-amd64/... http://mirrors.kernel.org/debian/dists/wheezy/contrib/binary-amd64/...
To use this mirror with
apt, you add this line to your
sources.list file:
deb http://mirrors.kernel.org/debian wheezy main contrib
Note that the "
dists" is added implicitly, and the arguments
after the release name are used to expand the path into multiple directories.
After adding your new sources, disable the previously existing
deb" lines in
sources.list by placing a
hash sign (
#) in front of them.
Instead of using HTTP or FTP package mirrors, you may wish to modify
/etc/apt/sources.list to use a mirror on a local disk
(possibly mounted over NFS).
For example, your package mirror may be under
/var/ftp/debian/, and have main directories like this:
/var/ftp/debian/dists/wheezy/main/binary-amd64/... /var/ftp/debian/dists/wheezy/contrib/binary-amd64/...
To use this with
apt, add this line to your
sources.list file:
deb file:/var/ftp/debian wheezy main contrib
Note that the "
dists" is added implicitly, and the arguments
after the release name are used to expand the path into multiple directories.
After adding your new sources, disable the previously existing
deb" lines in
sources.list by placing a
hash sign (
#) in front of them.
If you want to use only CDs (or DVDs or Blu-ray Discs),
comment out the existing
deb" lines in
/etc/apt/sources.list by
placing a hash sign (
#) in front of them.
Make sure there is a line in
/etc/fstab that enables
mounting your CD-ROM drive at the
/cdrom mount point (the
/cdrom mount point is required for
apt-cdrom). For example, if
is your CD-ROM drive,
/etc/fstab should contain a line
/dev/scd0 /cdrom auto noauto,ro 0 0
Note that there must be no spaces between the words
noauto,ro in the fourth field.
To verify it works, insert a CD and try running
# mount /cdrom # this will mount the CD to the mount point # ls -alF /cdrom # this should show the CD's root directory # umount /cdrom # this will unmount the CD
Next, run:
# apt-cdrom add
for each Debian Binary CD-ROM you have, to add the data about each CD to APT's database.
The recommended way to upgrade from previous Debian releases is to use the package management tool apt-get. In previous releases, aptitude was recommended for this purpose, but recent versions of apt-get provide equivalent functionality and also have shown to more consistently give the desired upgrade results.
Don't forget to mount all needed partitions (notably the root and
/usr partitions) read-write, with a command like:
# mount -o remount,rw /
Next you should double-check that the APT source entries (in
/etc/apt/sources.list) refer either to
wheezy" or to "
stable". There should not be
any sources entries pointing to squeeze.
Source lines for a CD-ROM might sometimes refer to
It is strongly recommended that you use the /usr/bin/script program to record a transcript of the upgrade session. Then if a problem occurs, you will have a log of what happened, and if needed, can provide exact information in a bug report. To start the recording, type:
# script -t 2>~/upgrade-wheezy
step.time -a ~/upgrade-wheezy
or similar. If you have to rerun the typescript (e.g. if you have to reboot the
system) use different
step values to indicate which
step of the upgrade you are logging. Do not put the typescript file in a
temporary directory such as
/tmp or
/var/tmp (files in those directories may be deleted during
the upgrade or during any restart).
The typescript will also allow you to review information that has scrolled
off-screen. If you are at the system's console, just switch to VT2 (using
and, after logging in, use
less -R ~root/upgrade-wheezy.script to view
the file.
After you have completed the upgrade, you can stop script by
exit at the prompt.
If you have used the -t switch for script you can use the scriptreplay program to replay the whole session:
# scriptreplay ~/upgrade-wheezy.time ~/upgrade-wheezy.script
First the list of available packages for the new release needs to be fetched. This is done by executing:
# apt-get update
You have to make sure before upgrading your system that you will have sufficient
hard disk space when you start the full system upgrade described in Section 4.4.5, "Upgrading the system". First, any package needed for installation that
is fetched from the network is stored in
/var/cache/apt/archives (and the
partial/ subdirectory, during download), so you must make
sure you have enough space on the file system partition that holds
/var/ to temporarily download the packages that will be
installed in your system. After the download, you will probably need more
space in other file system partitions in order to both install upgraded
packages (which might contain bigger binaries or more data) and new packages
that will be pulled in for the upgrade. If your system does not have
sufficient space you might end up with an incomplete upgrade that is
difficult to recover from.
apt-get can show you detailed information about the disk space needed for the installation. Before executing the upgrade, you can see this estimate by running:
# apt-get -o APT::Get::Trivial-Only=true dist-upgrade [ ... ] XXX upgraded, XXX newly installed, XXX to remove and XXX not upgraded. Need to get xx.xMB of archives. After this operation, AAAMB of additional disk space will be used.
Running this command at the beginning of the upgrade process may give an error, for the reasons described in the next sections. In that case you will need to wait until you've done the minimal system upgrade as in Section 4.4.4, "Minimal system upgrade" before running this command to estimate the disk space.
If you do not have enough space for the upgrade, apt-get will warn you with a message like this:
E: You don't have enough free space in /var/cache/apt/archives/.
In this situation, make sure you free up space beforehand. You can:
Remove packages that have been previously downloaded for installation (at
/var/cache/apt/archives). Cleaning up the package cache by
running apt-get clean will remove all previously downloaded
package files.
Remove forgotten packages. If you have used aptitude or apt-get to manually install packages in squeeze it will have kept track of those packages you manually installed, and will be able to mark as redundant those packages pulled in by dependencies alone which are no longer needed due to a package being removed. They will not mark for removal packages that you manually installed. To remove automatically installed packages that are no longer used, run:
# apt-get autoremove
You can also use deborphan, debfoster, or cruft to find redundant packages. Do not blindly remove the packages these tools present, especially if you are using aggressive non-default options that are prone to false positives. It is highly recommended that you manually review the packages suggested for removal (i.e. their contents, sizes, and descriptions) before you remove them.
Remove packages that take up too much space and are not currently
needed (you can always reinstall them after the upgrade). If you have
popularity-contest installed, you can use
popcon-largest-unused to list the packages you do not use
that occupy the most space. You can find the packages that just
take up the most disk space with dpigs (available in the
debian-goodies package) or with
wajig (running
wajig size).
They can also be found with
aptitude. Start
aptitude in "visual mode",
select → , press l and enter
~i, then press S and enter
~installsize. This will give you a handy list to work
Remove translations and localization files from the system if they
are not needed. You can install the
localepurge package and configure it so
that only a few selected locales are kept in the system. This will
reduce the disk space consumed at
Temporarily move to another system, or permanently remove, system logs
residing under
Use a temporary
/var/cache/apt/archives: You
can use a temporary cache directory from another filesystem
(USB storage device, temporary hard disk,
filesystem already in use, ...)
Do not use an NFS mount as the network connection could be interrupted during the upgrade.
For example, if you have a USB drive mounted on
remove the packages that have been previously downloaded for installation:
# apt-get clean
copy the directory
/var/cache/apt/archives to the
USB drive:
# cp -ax /var/cache/apt/archives /media/usbkey/
mount the temporary cache directory on the current one:
# mount --bind /media/usbkey/archives /var/cache/apt/archives
after the upgrade, restore the original
/var/cache/apt/archives directory:
# umount /media/usbkey/archives
remove the remaining
You can create the temporary cache directory on whatever filesystem is mounted on your system.
Do a minimal upgrade of the system (see Section 4.4.4, "Minimal system upgrade") or partial upgrades of the system followed by a full upgrade. This will make it possible to upgrade the system partially, and allow you to clean the package cache before the full upgrade.
Note that in order to safely remove packages, it is advisable to switch your
sources.list back to squeeze as described in Section A.2, "Checking your sources list".
In some cases, doing the full upgrade (as described below) directly might remove large numbers of packages that you will want to keep. We therefore recommend a two-part upgrade process: first a minimal upgrade to overcome these conflicts, then a full upgrade as described in Section 4.4.5, "Upgrading the system".
To do this, first run:
# apt-get upgrade
This has the effect of upgrading those packages which can be upgraded without requiring any other packages to be removed or installed.
The minimal system upgrade can also be useful when the system is tight on space and a full upgrade cannot be run due to space constraints.
If the
apt-listchanges package is
installed, it will (in its default configuration) show important information
about upgraded packages in a pager. Press q after reading
to exit the pager and continue the upgrade.
Once you have taken the previous steps, you are now ready to continue with the main part of the upgrade. Execute:
# apt-get dist-upgrade
The upgrade process for some previous releases recommended the use of aptitude for the upgrade. This tool is not recommended for upgrades from squeeze to wheezy.
This will perform a complete upgrade of the system, installing the newest available versions of all packages, and resolving all possible dependency changes between packages in different releases. If necessary, it will install some new packages (usually new library versions, or renamed packages), and remove any conflicting obsoleted packages.
When upgrading from a set of CD-ROMs (or DVDs), you will be asked to insert specific CDs at several points during the upgrade. You might have to insert the same CD multiple times; this is due to inter-related packages that have been spread out over the CDs.
New versions of currently installed packages that cannot be upgraded without
changing the install status of another package will be left at their current
version (displayed as "held back"). This can be resolved by either using
aptitude to choose these packages for installation or by
apt-get -f install
The following sections describe known issues that might appear during an upgrade to wheezy.
In some cases the apt-get dist-upgrade step can fail after downloading packages with:
E: Could not perform immediate configuration on '
package'. Please see man 5 apt.conf under APT::Immediate-Configure for details.
If that happens, running apt-get dist-upgrade -o APT::Immediate-Configure=0 instead should allow the upgrade to proceed.
Another possible workaround for this problem is to temporarily add both
squeeze and wheezy sources to your
sources.list and run apt-get update.
Debian 7.0 now features multiarch, which allows one to install packages
from different architectures on the same system. The
ia32-libs package is now a transitional
package to make use of this new functionality. If you have
ia32-libs installed, you need to
enable multiarch before upgrading this package. Otherwise APT will output
the following message:
The following packages have unmet dependencies: ia32-libs : Depends: ia32-libs-i386 but it is not installable E: Broken packages
In order to allow installation of i386 packages on an amd64 system, execute the following commands:
# dpkg --add-architecture i386 # apt-get update
The upgrade process to wheezy might ask for the removal of packages on the system. The precise list of packages will vary depending on the set of packages that you have installed. These release notes give general advice on these removals, but if in doubt, it is recommended that you examine the package removals proposed by each method before proceeding.
Sometimes it's necessary to enable the
option in APT to be able to temporarily remove an essential package due to a
Conflicts/Pre-Depends loop. apt-get will alert you of this
and abort the upgrade. You can work around this by specifying the option
APT::Force-LoopBreak=1 on the apt-get command
It is possible that a system's dependency structure can be so corrupt as to require manual intervention. Usually this means using apt-get or
# dpkg --remove
to eliminate some of the offending packages, or
# apt-get -f install # dpkg --configure --pending
In extreme cases you might have to force re-installation with a command like
# dpkg --install
File conflicts should not occur if you upgrade from a "pure" squeeze system, but can occur if you have unofficial backports installed. A file conflict will result in an error like:
<package-foo-file>) ... dpkg: error processing
<package-foo>(--install): trying to overwrite `
<some-file-name>', which is also in package
<package-bar>dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing:
You can try to solve a file conflict by forcibly removing the package mentioned on the last line of the error message:
# dpkg -r --force-depends
After fixing things up, you should be able to resume the upgrade by repeating the previously described apt-get commands.
During the upgrade, you will be asked questions regarding the configuration
or re-configuration of several packages. When you are asked if any file in
/etc/init.d directory, or the
/etc/manpath.config file should be replaced by the
package maintainer's version, it's usually necessary to answer "yes" to
ensure system consistency. You can always revert to the old versions, since
they will be saved with a
.dpkg-old extension.
If you're not sure what to do, write down the name of the package or file and sort things out at a later time. You can search in the typescript file to review the information that was on the screen during the upgrade.
If you are running the upgrade using the system's local console you might find that at some points during the upgrade the console is shifted over to a different view and you lose visibility of the upgrade process. For example, this may happen in desktop systems when the display manager is restarted.
To recover the console where the upgrade was running you will have to use Ctrl+Alt+F1 (if in the graphical startup screen) or Alt+F1 (if in the local text-mode console) to switch back to the virtual terminal 1. Replace F1 with the function key with the same number as the virtual terminal the upgrade was running in. You can also use Alt+Left Arrow or Alt+Right Arrow to switch between the different text-mode terminals.
In most cases, packages should upgrade smoothly between squeeze and wheezy. There are a small number of cases where some intervention may be required, either before or during the upgrade; these are detailed below on a per-package basis.
If you have modified
/etc/sudoers then you should be aware
of changes made to how
configuration is handled. The default
/etc/sudoers now
includes the following two directives:
Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
#includedir /etc/sudoers.d
Neither of these entries are added to your
automatically during the upgrade. (Although you will still be able to run
sudo commands by specifying their fully-qualified path.) So
you might wish to consider migrating your changes to the new
/etc/sudoers.d directory and using the default
/etc/sudoers file. For example:
# mv /etc/sudoers /etc/sudoers.d/mychanges # mv /etc/sudoers.dpkg-new /etc/sudoers
You may also need to edit your
/etc/sudoers.d/mychanges to
remove unwanted
Defaults and
entries. You should use visudo for this:
# visudo -f /etc/sudoers.d/mychanges
The GNU Screen versions in squeeze and wheezy don't use the same
communication protocol between the screen client
and the SCREEN server. Wheezy's
screen package has been patched so that
the most important functionality is present even if the versions of
screen client and server don't match.
The most prominent functionality which does not work properly when
connecting to a Screen session started with squeeze's version of
screen with wheezy's version
screen as client is
terminal resizing (
WINCH signal). The workaround is
to detach and reattach again to get the size of the terminals inside
the screen session adjusted properly.
Some ncurses-based applications, e.g. aptitude in visual mode, may leave traces of previous contents on the screen. Pressing Ctrl+L solves the issue.
Another (harmless) symptom of such an inter-version connection is screen issuing messages like "Message 40 of 12376 bytes too small".
All these issues vanish as soon as the Screen sessions started with
squeeze's version of
are exited.
See also
/usr/share/doc/screen/NEWS.Debian.gz in
screen package.
This section explains how to upgrade your kernel and identifies potential
issues related to this upgrade. You can either install one of the
linux-image-* packages provided by Debian, or
compile a customized kernel from source.
Note that a lot of information in this section is based on the assumption that
you will be using one of the modular Debian kernels, together with
initramfs-tools and
udev. If you choose to use a custom kernel that
does not require an initrd or if you use a different initrd generator, some of
the information may not be relevant for you.
When you dist-upgrade from squeeze to wheezy, it is strongly recommended that you install a linux-image-* metapackage, if you haven't done so before. This package may be installed automatically by the dist-upgrade process. You can verify this by running:
# dpkg -l "linux-image*" | grep ^ii
If you do not see any output, then you will need to install a new linux-image package by hand. To see a list of available linux-image metapackages, run:
# apt-cache search linux-image- | grep -v transition
If you are unsure about which package to select, run
-r and look for a package with a similar name. For example, if you
see '
2.6.32-5-amd64', it is recommended that you install
You may also use apt-cache to see a long
description of each package in order to help choose the best one
available. For example:
# apt-cache show linux-image-amd64
You should then use
apt-get install to install it. Once
this new kernel is installed you should reboot at the next available
opportunity to get the benefits provided by the new kernel version.
For the more adventurous there is an easy way to compile your own custom
kernel on Debian. Install the kernel sources, provided in the
linux-source package. You can make use of the
deb-pkg target available in the sources' makefile for
building a binary package. More information can be found in the Debian Linux Kernel
Handbook, which can also be found as the
debian-kernel-handbook package.
If possible, it is to your advantage to upgrade the kernel package separately
from the main
dist-upgrade to reduce the chances of a
temporarily non-bootable system.
Note that this should only be done after the
minimal upgrade process described in Section 4.4.4, "Minimal system upgrade".
If an initrd created with
initramfs-tools is used to boot the system, in some
cases the creation of device files by
udev can happen too late for the boot scripts to
act on.
The usual symptoms are that the boot will fail because the root file system cannot be mounted and you are dropped into a debug shell:
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
/dev/something does not exist. Dropping to a shell!
But if you check afterwards, all devices that are needed are present in
/dev. This has been observed in cases where the root file
system is on a USB disk or on RAID, especially if LILO is used.
A workaround for this issue is to use the boot parameter
rootdelay=. The value for the
timeout (in seconds) may need to be adjusted.
After the upgrade there are several things you can do to prepare for the next release.
Remove newly redundant or obsolete packages as described in Section 4.4.3, "Make sure you have sufficient space for the upgrade" and Section 4.8, "Obsolete packages". You should review which configuration files they use and consider purging the packages to remove their configuration files.
Introducing several thousand new packages, wheezy also retires and omits more than four thousand old packages that were in squeeze. It provides no upgrade path for these obsolete packages. While nothing prevents you from continuing to use an obsolete package where desired, the Debian project will usually discontinue security support for it a year after wheezy's release[5], and will not normally provide other support in the meantime. Replacing them with available alternatives, if any, is recommended.
There are many reasons why packages might have been removed from the distribution: they are no longer maintained upstream; there is no longer a Debian Developer interested in maintaining the packages; the functionality they provide has been superseded by different software (or a new version); or they are no longer considered suitable for wheezy due to bugs in them. In the latter case, packages might still be present in the "unstable" distribution.
Detecting which packages in an updated system are "obsolete" is easy since the package management front-ends will mark them as such. If you are using aptitude, you will see a listing of these packages in the "Obsolete and Locally Created Packages" entry.
The Debian Bug Tracking System often provides additional information on why the package was removed. You should review both the archived bug reports for the package itself and the archived bug reports for the ftp.debian.org pseudo-package.
The list of obsolete packages includes:
postgresql-8.4, successor is
Wheezy provides only an updated
postgresql-plperl-8.4 package
that is linked against the new version of libperl in order to enable
upgrading to the new Perl version in wheezy without making existing
postgresql-8.4 installations unusable. Once the operating system
upgrade is finished, you should plan to also upgrade your PostgreSQL
8.4 database clusters to the new PostgreSQL version 9.1 using the
pg_upgradecluster tool.
gdm, successor is
gdm3. Users of lightweight
desktop environments such as Xfce or LXDE may wish to consider
lightdm as a lighter
weight alternative.
compiz OpenGL window and
compositing manager, see bugreports
#677864 (and
Some of Xorg's video drivers are no longer available in
wheezy and are obsolete. This includes
xserver-xorg-video-nv and
They may be removed during the upgrade. Users should install
All Horde 3 packages, providing web collaborative software, have been
removed and are obsolete. This includes
sork-vacation-h3 and
As the Horde 4 packages have not reached sufficient quality before the
wheezy release, they are also not available. They may be available
in testing as
php-horde-* packages.
Most Kolab packages, providing groupware server, have been removed. This
php-kolab-filter and
As of 2012, Kolab was in a major rewrite and may get shipped with a
later Debian release as the
kolab package. NB: The SOGo
server (formerly named Scalable OpenGroupware.org) is shipped with
wheezy as
All OpenERP 5 packages have been
removed and are obsolete. This includes
uw-imapd and
ipopd packages have been removed. Better
alternatives exist, for example
dovecot-imapd and
courier-imap for IMAP, or
dovecot-pop3d and
courier-pop for POP3.
drupal6 package is no
longer available; it is replaced by
drupal7. However, no automatic upgrade
path exists, and users should read the instructions on the Debian Wiki.
Some packages from squeeze have been split into several packages in wheezy, often to improve system maintainability. To ease the upgrade path in such cases, wheezy often provides "dummy" packages: empty packages that have the same name as the old package in squeeze with dependencies that cause the new packages to be installed. These "dummy" packages are considered redundant after the upgrade and can be safely removed.
Most (but not all) dummy packages' descriptions indicate their purpose.
Package descriptions for dummy packages are not uniform, however, so you might
also find deborphan with the
--guess- options (e.g.
--guess-dummy) useful to detect them in your system. Note
that some dummy packages are not intended to be removed after an upgrade but
are, instead, used to keep track of the current available version of a program
over time.
[1] If the debconf priority is set to a very high level you might prevent configuration prompts, but services that rely on default answers that are not applicable to your system will fail to start.
[2] For example: DNS or DHCP services, especially when there is no redundancy or failover. In the DHCP case end-users might be disconnected from the network if the lease time is lower than the time it takes for the upgrade process to complete.
[3] This feature can be disabled by adding the parameter
panic=0 to your boot parameters.
[4] Debian's package management system normally does not allow a package to remove or replace a file owned by another package unless it has been defined to replace that package.
[5] Or for as long as there is not another release in that time frame. Typically only two stable releases are supported at any given time.


text:
The race between President Obama and Mitt Romney goes to the dogs... and a plastic surgeon. Only on the RidicuList.
Post by: Anderson Cooper
Filed under: The RidicuList
Political accountability
I was born in 1962,i voted and pay taxes since I was 18, I have no understanding of how political campaigns can spend the amount of money on advertising when our own economy situation is on such need. This is the first year I refuse to vote and no longer believed in the american system, I do think Us citizens have the the right to know why the polticians are spending so much money while americans are in deficit.
My friend is writing this for me because am disabled, My name is Amy Walbrecker, since August of 2010, I have written to the White House, my state, senators and congress men and to the head of political election campaign also to all the news stations and Cnn, I never got any kind of response, I am really pissed off and refuse to vote this year… please somebody respond. Thank you…
Anderson Cooper goes beyond the headlines to tell stories from many points of view, so you can make up your own mind about the news. Tune in weeknights at 8 and 10 ET on CNN.
Questions or comments? Send an email
Want to know more? Go behind the scenes with AC361°


text:
For the latest updates to Global Public Square, including show information and Fareed's Take, visit the new GPS site on CNN.com.
Well. I am Hindu. And i enjoy a good rayping now and then on a soft bed.
But my boyfriend is Hindu and so does not raype.
I shall look at men in bars in Milwaukee.
I am ISLAM. As part of our religion we raype teenage girls. Only pretty ones.
Never fat ones.
I enjoy rayping so i moved to Pakistan.
There rayping is allowed if you are Islamic. So i became Islamic.
Rayping is good
My ex boyfriend is ISLAMIC from Pakistan. He would raype me everyday in the Pakistani mountains.
Then a Hindu rescued me. I am safe now living in New Jersey. I am Hindu
I am from Pakistan. Yes. It is very true. We raype teenage girls all day and night. It is our custom.
Happy Ramadan
Blue Saffron eats dog s hit...
@ Larissa. Nailed it!
I am Hindu and from India. We do not raype. It is not customary
I am Hindu. I never raype .
Me too. I am full Hindu and raype..no
Empowering subjugated minorities in India by splitting it into smaller states would trigger uber economic demand for western nations who have given so much financial and technology aid to India with no return to show for the investment.
I rayped my cousin. She just turned 18. It was so pleasurable and exciting for me.
The Egyptians left behind The Pyramids. The Greeks The Parthenon. The Romans The Pantheon. The Christians The St. Peter's Basilica. The Moslems The Taj Mahal. The Hindus ..... RAYPES. And collapsed buildings.
I like to raype in Pakistan. It is my custom
I like to raype my cousin. She is hot. It is Islamic custom to raype 18 year old cousin on her birthday
We can take turns Jim.lol
I am Paki. We raype disadvantaged girls everyday. It is hot.
Hi. I'm Jim. I live to raype. Rayping is a sport in Pakistan. I love it
You are not free. If you are an average US adult you are a fat lazy drug addict who enjoys viewing violence as entertainment. You are a slave in other words.
Yes there are millions of 12 year old American boys who have teats that are larger than can be found on old hag ladies.
Many of those big booby boys have boobies that are bigger than the ones their own dads have! I'm not kidding. Americans are getting freaking goofy looking.
Philip Douglas has big ti ts. He is in Colorado
Men and boys on meds and having large teats should be disarmed. And forced to eat vegetables.
Philip is a pig. He eats at Golden Coral buffet. They kick him out because he eats all the food
Philip is lazy and fat.
No big tweeted man or boy should ever be allowed to kill the majestic Elk, for example. What an insult to nature those man boys are.
*big teated
Philip you are a fat pig
Nothing like a good rayping. I relax like that
You know the type...men and/or boys on meds. Who really should be wearing braziers. And not just for safety's sake.
Lord Rama used to live on a banyan tree in Benares with monkeys. There he met Hanuman aka Manny who was eating fleas off his skin. Rama said to Manny to give him a B J. Hanuman alias Manny agreed in exchange for 2 bananas. Rama reneged. Manny shoved his d ik up Lord Rama's a zz. Lord Ganesha got born as a result. Hindoos all p iss on Lord Ganesha as a result.
Once The Pentagon found out that reporting lies as "news" to enemies would work, it became a no-brainer that TV "news" would work on you.
Lord and drinking buddy Jesus forgiving your crimes. What a guy. What a dream god induced by pharmakia druggery of you all.


text:
18K White Gold Matching Wedding Band - 0.25 ct
Product Details
*All bands are available in 14kt and 18kt Yellow, Rose and White Gold as well as Platinum.
*Changes in stone sizes and stone quantities are available via special order.
|Item Code:
|Total Diamond Weight (TW):
|0.25 ct
|Division :
|Gabriel Limited
|Collection :
|Style :
|Center Stone Size :
|6.50 mm
Product Measurements
|Width (A) :
|2.03 mm
|Thickness (B) :
|2.10 mm
|Bandwidth (C) :
|1.80 mm
|Size (D) :
* Product weights and dimensions are approximate. Our total diamond weight may have a +/-5% tolerance. All prices on this web site are subject to change without notice. Whilst we make every effort to provide you the most accurate, up-to-date information, occasionally, one or more items on our web site may be mis-priced. In the event a product is listed at an incorrect price due to typographical, photographic, or technical error. Gabriel & Co reserves the right to cancel any orders placed with incorrect price.
Shipping & Returns
- Free standard shipping to anywhere within the U.S
- Returns are accepted within 30 days of shipment*


text:
Greenhouse gas emissions accelerating
WASHINGTON (AP) — The old saying that "what goes up must come down" doesn't apply to carbon dioxide pollution in the air, which just hit an unnerving milestone.
The chief greenhouse gas was measured Thursday at 400 parts per million in Hawaii, a monitoring site that sets the world's benchmark. It's a symbolic mark that scientists and environmentalists have been anticipating for years.
While this week's number has garnered all sorts of attention, it is just a daily reading in the month when the chief greenhouse gas peaks in the Northern Hemisphere. It will be lower the rest of the year. This year will probably average around 396 ppm. But not for long — the trend is going up and at faster and faster rates.
Within a decade the world will never see days — even in the cleanest of places on days in the fall when greenhouse gases are at their lowest — when the carbon measurement falls below 400 ppm, said James Butler, director of global monitoring at the National Oceanic and Atmospheric Administration's Earth Science Research Lab in Boulder, Colo. "The 400 is a reminder that our emissions are not only continuing, but they're accelerating; that's a scary thing," Butler said last week.
Carbon dioxide stays in the air for a century, some of it into the thousands of years. And the world carbon dioxide pollution levels are accelerating yearly. Every second, the world's smokestacks and cars pump 2.4 million pounds of the heat-trapping gas into the air.
Carbon pollution levels that used to be normal for the 20th century are fast becoming history in the 21st century.
"It means we are essentially passing one in a whole series of points of no return," said Michael Mann, a climate scientist at Pennsylvania State University.
Princeton University climate scientist Michael Oppenheimer said the momentum in carbon dioxide emissions has the world heading toward and passing 450 ppm. That is the level that would essentially mean the world warms another 2 degrees, what scientists think of as dangerous, he said. That 2-degree mark is what much of the world's nations have set as a goal to prevent.
To see what the future is, scientists look to the past.
The last time the worldwide carbon level probably hit 400 ppm was about 2 million years ago, said Pieter Tans of the National Oceanic and Atmospheric Administration.
That was during the Pleistocene Era. "It was much warmer than it is today," Tans said. "There were forests in Greenland. Sea level was higher, between" 33 and 66 feet.
Other scientists said it might have been 10 million years ago that Earth last encountered this much carbon dioxide in the atmosphere. The first modern humans appeared in Africa only about 200,000 years ago.
Environmental activists, such as former Vice President Al Gore, seized on the milestone. "This number is a reminder that for the last 150 years — and especially over the last several decades — we have been recklessly polluting the protective sheath of atmosphere that surrounds the Earth and protects the conditions that have fostered the flourishing of our civilization," Gore said in a statement.
Carbon dioxide traps heat just like in a greenhouse. It accounts for three-quarters of the planet's heat-trapping gases. There are others, such as methane, which has a shorter life span but traps heat more effectively. Both trigger temperatures to rise over time, scientists said, which is causing sea levels to rise and some weather patterns to change.
When measurements of carbon dioxide were first taken in 1958, it measured 315 ppm. Some scientists and environmental groups promote 350 ppm as a safe level for CO2, but scientists acknowledge they don't really know what levels would stop the effects of global warming.
The level of carbon dioxide in the air is rising faster than in the past decades, despite international efforts by developed nations to curb it. On average, the amount is growing by about 2 ppm per year. That's 100 times faster than at the end of the Ice Age.
Back then, it took 7,000 years for carbon dioxide to reach 80 ppm, Tans said. Because of the burning of fossil fuels, such as oil and coal, carbon dioxide levels have gone up by that amount in just 55 years.
Before the Industrial Revolution, carbon dioxide levels were around 280 ppm, and they were closer to 200 during the Ice Age, which is when sea levels shrank and polar places went from green to icy. There are natural ups and downs of this greenhouse gas, which comes from volcanoes and decomposing plants and animals. But that's not what has driven current levels so high, Tans said. He said the amount should be even higher, but the world's oceans are absorbing quite a bit, keeping it out of the air. "What we see today is 100 percent due to human activity," said Tans, a NOAA senior scientist. The burning of fossil fuels, such as coal for electricity and oil for gasoline, has caused the overwhelming bulk of the man-made increase in carbon in the air, scientists said.
The world sent 38.2 billion tons of carbon dioxide into the air in 2011, according international calculations published in a scientific journal in December. China spews 10 billion tons of carbon dioxide into the air per year, leading all countries, and its emissions are growing about 10 percent annually. The United States at No. 2 is slowly cutting emissions and is down to 5.9 billion tons per year.
The speed of the change is the big worry, Pennsylvania State's Mann said. If carbon dioxide levels go up 100 ppm over thousands or millions of years, plants and animals can adapt. But that can't be done at the speed it is now happening. "We are a society that has inadvertently chosen the double-black diamond run without having learned to ski first," NASA climate scientist Gavin Schmidt said. "It will be a bumpy ride."


text:
SAVANNAH — A director who was working on a movie about singer Gregg Allman testified Monday that his assistants were in charge of location permits and safety precautions when a freight train plowed into his crew on a Georgia railroad bridge, killing a worker and injuring six.
He also insisted that Allman, who is suing producers to win back movie rights to his life story, knew about plans to shoot a scene with a bed across the train tracks in the production of "Midnight Rider."
"I read the script to him for 4½ hours on a Monday," director Randall Miller testified in a Savannah courtroom. "It says there's a bed in the middle of a track. Again, I hadn't been to the location. The location was picked a week beforehand."
Miller was grilled by an attorney for the Allman Brothers Band singer about the Feb. 20 crash, which killed one of the director's camera assistants and injured six other crew members. Allman's lawyers have asked a Chatham County Superior Court judge to stop Miller and his production company from reviving the project, arguing his legal rights have lapsed and that the director's actions have harmed Allman's reputation.
Miller's testimony during more than an hour on the witness stand Monday marked his first public comments since the crash. He bristled at the suggestion that he had been cavalier about his crew's safety.
"I was in the middle of the track and I almost died," he said.
Investigators say Miller, his crew and actor William Hurt — who was to star as Allman — were shooting on a railroad bridge spanning the Altamaha River when a train came upon them at 55 mph. The train crashed through a bed set on the tracks as a prop and struck and killed 28-year-old camera assistant Sarah Jones. Others were injured either by the train or flying debris. Sheriff's investigators in Wayne County, southwest of Savannah, say the crew did not have a permit from CSX Railroad, which owns the tracks. Local prosecutors are still weighing whether to file criminal charges.
When Allman attorney David Long-Daniels asked Miller whether he had written permission from CSX, the director answered: "That's not my job." He said crew members were placed along the tracks to look out for trains, but he didn't know how far away. He said an assistant told crew members on the bridge they would have about 60 seconds to flee if a train came.
"I did not know it was a live train trestle," said Miller, who insisted the crew had permission to film from paper-products company Rayonier, which has a mill nearby and owns the property surrounding the train tracks. "We were told there were two trains from Rayonier coming through, and no more trains that day."
Despite the focus on the crash, the claims in Allman's lawsuit are largely contractual. He says Unclaimed Freight Productions, headed by Miller and his wife, forfeited its rights to the movie by missing a key production deadline that passed when the project was shelved after the crash.
Judge John Morse Jr., who was asked to temporarily stop any work on the Allman film until the lawsuit is resolved, recessed court without taking action after attorneys requested time to negotiate. Morse ordered them to report back Tuesday morning.
Allman, who had a liver transplant in 2010 and cancelled performances in March because of illness, wasn't in court Monday. His attorney told the judge the 66-year-old singer remains in poor health.
"Mr. Allman is not well and he ought to have the right to decide who tells his story in his lifetime," Long-Daniels said.
The director's attorney, Donnie Dixon, argued Allman was trying to back out of the project because of a tragedy and shouldn't be allowed to.
"Just because the going gets rough, just because it gets inconvenient, that doesn't mean Mr. Allman can pick up his marbles and go home," Dixon said.


text:
NIU makes it easy for BG to ruin dream year
Northern Illinois wrote its own headline before the Mid-American Conference title game.
The Huskies donned their new charcoal gray "Black Dog" uniforms, with silver numbers and "The Hard Way" lettered across the back of their shoulders in place of player names at Ford Field in Detroit.
That's the way NIU has always approached the MAC title game. Favored NIU teams blew leads to lose in the final seconds in 2005 and 2010 and overcame slow starts to eke out last-second wins the last two years. Even in victory, the MAC title game has never been NIU's best game.
Friday, it was NIU's worst. The Huskies played a stinker in almost every way, losing 47-27 to Bowling Green and losing nearly everything in the process.
The Huskies lost a chance to play in a second consecutive BCS bowl.
Jordan Lynch, second on many analyst's list, lost a chance to go to New York for the Heisman ceremony.
The MAC lost an $8-million payday and will now probably only send four teams to a bowl instead of five.
And NIU deserved every demoralizing result.
The secondary that coach Rod Carey said had to be the strength of the defense before the year began underachieved slightly all year, but was at its absolute worst Friday. Their jerseys should have read: The Easy Way. Because they sure made it that way for the Falcons.
Bowling Green gained 136 yards on its first six plays. In the first half alone, Matt Johnson was 16-for-19 for 294 yards and four touchdowns. On two of those touchdowns, you couldn't even see a NIU defender on the TV screen. It was so easy the Falcons rolled up 381 yards at halftime despite converting only one third down.
Jordan Lynch got off to a great start, converting two third downs and floating a perfect pass under pressure to Juwan Brescacin to briefly tie the game at 7.
But for most of the rest of the night, Lynch threw high or wide or simply made the wrong decisions, often throwing into coverage or keeping the ball and running into a swarm of defenders instead of handing off to a runner going around the corner. Bowling Green has by far the best defense in the MAC, but Lynch was simply off.
Despite being severely outplayed, NIU had a chance to make it a three-point game after recovering a Bowling Green fumble at midfield. BG dropped a potential pick-6 on the next play, but Lynch threw an interception two plays later. A minute later, Johnson's fourth TD pass gave BG a 31-13 halftime lead.
Lynch also came up short when an NIU drive petered out after Bowling Green missed a chip-shot field goal in the third quarter when the Huskies were only down 11. Then, after NIU held BG to a field goal, Aaron Foster intercepted Lynch to basically end the game early in the fourth quarter.
NIU has lost only three games in two years with Jordan Lynch at quarterback, but those were his three worst games. Friday, he was 21-for-40 for 219 yards. That's a 56.1 passer rating on the NFL scale.
The defense lost this game, but a true Heisman candidate could have still won it. He didn't.
The one thing the Huskies didn't lose Friday was their future. This isn't the end of NIU (46-9 the last four years). The Huskies aren't going to the Fiesta Bowl, but they were an even better team than last season's Orange Bowl squad. That makes three years in a row where NIU improved despite having to follow one of the best seasons in school history.
But it could have been a dream season. A program-changing season. It wasn't. And the Huskies didn't even make it hard on Bowling Green to end those dreams.
Matt Trowbridge: 815-987-1383; firstname.lastname@example.com; @matttrowbridge


text:
A Game of Thrones Tribute to That Jerk Joffrey
[WARNING: The following contains spoilers from Sunday's Game of Thrones episode. Read at your own risk!]
Ding dong, the king is dead!
There was much rejoicing across TV-viewing land Sunday night when that little snot King Joffrey Baratheon (Jack Gleeson) became Game of Thrones' latest casualty in the War of Five Kings. Following his marriage to Margaery Tyrell (Natalie Dormer), someone sneaked poison into his wine. And thus, a beautiful wedding day and bite of pigeon pie were forever sullied when Joffrey fell to the ground choking, twitching and bleeding from the nose.
Game of Thrones: The trouble with Joffrey
The so-called Purple Wedding is the second nuptials to end in death after last season's Red Wedding massacre. If we lived in Westeros, we'd probably skip all wedding feasts from now on. Even the lure of an open bar couldn't tempt us!
"The last day of shooting the wedding was very bittersweet because that was the day we filmed Joffrey's death, which was incredibly sad for everyone," Sophie Turner, who plays Sansa Stark, tells TVGuide.com. "I keep saying like, 'Oh my God, it was so devastating doing it.' And people are like, 'Why?' I keep forgetting people hate him because we all love [Jack]. I love how awful and vile Joffrey is. I think its so funny. He's a total bastard in every sense of the word."
Joffrey is certainly one of the most loathed characters on the series. At the beginning of the season, 63 percent of readers who voted in a TVGuide.com poll wanted the teen king to die next. Nevertheless, we can't help but mourn. In a world where villains are often depicted with a degree of complexity and humanity, Joffrey was such a wholly depraved character with no redeeming qualities that our feelings toward him are pure. He always delivered the very best unqualified awfulness. Joffrey shall be missed.
In honor of the bloodthirsty pissant, TVGuide.com and a few of the Game of Thrones cast share their favorite things about Joffrey:
Game of Thrones cast spills on Red Wedding shocker
Sansa perhaps has the best reasons to hate Joffrey. When she was younger, she was besotted by his golden good looks and completely false sweetness:
But since then, he's abused her, threatened to rape her and, oh yeah, there was that time he ordered the execution of her dad ...
... and then made her look at the decapitated head on a spike...
... and made her wedding super awkward.
"There's a certain amount of relief," Turner says about Sansa's feelings about Joffrey's death. "I think she's quite happy with how it all turned out."
Aidan Gillen, who plays Petyr "Littlefinger" Baelish, loved Joffrey's cluelessness. "I always love the way he totally doesn't understand," he says. "Like feeding the poor. Margaery Tyrell is one of the biggest players around, and her whole angle of trying to get the people on her side and how that's going to make her -- I love his total incomprehension of that. I like his single-mindedness, and it's funny that he can't see anywhere outside of that." Alfie Allen, who plays Theon Greyjoy, adds that Joffrey was "blissfully unaware" of how ridiculous he was and the things he said. "In the scene where there's the statue, and the next shot it's him standing like that," says. "That really made me giggle."
It's not terribly surprising that Joffrey had little to no self-awareness. His mother had spoiled him since birth and after all, he really was just a child when he ascended the throne. "There's a great scene where they tried to send him to bed," Gillen recalls, "and then you saw him for what he really is, which is a petulant child,"
Gillen adds, "But he's a petulant child with a crown on his head and a crossbow in his hand with the power to do anything. He's constantly threatening to have his brother executed and his mother thrown in the cell. He was just too dangerous to have around really."
What also made him dangerous was his unpredictable nature. Even though everyone, including his mother, had planned to let Ned Stark live after he confessed to being a traitor, Joffrey had given the word for his beheading. "One thing you can say some people might like about him is his complete disregard for sanity," Allen says. "He's a complete maniac and he doesn't even realize it, and he kind of indulges in it." Gillen agrees, "I quite like his ruthlessness and that he totally just doesn't give a sh--."
Finn Jones, who plays Margaery's brother Loras, loved Joffrey's more subtle moments. "I like it when he has that thing in his eye and you just know that he's not happy," Jones says. "He could switch at any moment. Jack plays it so wonderfully."
John Bradley, who plays Samwell Tarly, actually does feel like Joffrey had moments of self-awareness. "There were times when he lets the mask slip, and he loses his poise," Bradley says. "He loses his confidence and you can see that he does feel like a puppet sometimes. He starts to get frustrated and then has to declare, 'I am the king!'"
Also, like any teenage boy, Joffrey had certain urges. Although his urges were a little twisted. "I find it so funny when I'm seeing Jack doing all the really gross perverted stuff," Turner says.
But most of all, people loved to see Joffrey punished. Although the Internet will be full of gifs and other memes glorifying his wretched death, we remember the joys of the "slap" compilations from Season 1 with the most fondness:
View original A Game of Thrones Tribute to That Jerk Joffrey at TVGuide.com
Related Articles on TVGuide.com
Other Links From TVGuide.com


text:
2015 Jeep Wrangler Unlimited Sahara
Please call sales at 901-304-7300 Need a Trade Quote?
Our Price $31,377
*This calculator is for informational use only and is based on the information you provide. Actual loan amounts and payments will vary based on additional items such as taxes and fees as well as the actual interest rate available to you from a financial institution.
- Exterior
- Black
- Interior
- Tan
- Engine
- Transmission
- Automatic
- Drivetrain
- 4x4
- Mileage
- 59,585
- City / Hwy
- 16 / 20
*Actual rating will vary with options, driving conditions, habits and vehicle condition.
- Warranty
- AS-IS No Warranty
- Stock
- 4242
- Location
- Collierville Auto Center
- Title
- Clear
2015 Jeep Wrangler Sahara, Leather, NAV, winch bumper, very clean great looking jeep. Vehicle located at Collierville Auto Center Truck Sales Located at 651 W Poplar Avenue Collierville. We by far have the largest selection of used 4x4 and Diesel trucks in the area, if we have a car you can bet it is a nice one and a bargain.Call or Text us at 901….304///7300 for information or to schedule a test drive. We offer competitive financing and have several banks we partner with to get you the best deal possible. Call or Text today 901….304……7300
Standard Equipment
- 4-Way Passenger Seat -inc: Manual Recline and Fore/Aft Movement
- Front Cupholder
- Front Center Armrest w/Storage
- Driver And Passenger Visor Vanity Mirrors
- Fixed Antenna
- Fade-To-Off Interior Lighting
- Sentry Key Immobilizer
- 2 12V DC Power Outlets
- Rear Cupholder
- 6-Way Driver Seat -inc: Manual Recline, Height Adjustment and Fore/Aft Movement
- Radio w/Clock and Steering Wheel Controls
- Perimeter Alarm
- 60-40 Folding Split-Bench Front Facing Fold Forward Seatback Rear Seat
- Outside Temp Gauge
- 8 Speakers
- Analog Appearance
- Manual Tilt Steering Column
- Manual Adjustable Front Head Restraints and Fixed Rear Head Restraints
- Locking Glove Box
- Locking Cargo Area Concealed Storage
- Leather/Chrome Gear Shifter Material
- Leather Wrapped Steering Wheel
- Carpet Floor Trim, Carpet And Rubber Mat
- Interior Trim -inc: Deluxe Sound Insulation, Metal-Look Instrument Panel Insert, Metal-Look Door Panel Insert and Metal-Look Interior Accents
- Instrument Panel Bin, Dashboard Storage, Driver And Passenger Door Bins
- Compass
- Cruise Control w/Steering Wheel Controls
- Day-Night Auto-Dimming Rearview Mirror
- Delayed Accessory Power
- 2 12V DC Power Outlets and 1 120V AC Power Outlet
- 2 Seatback Storage Pockets
- Full Floor Console w/Locking Storage, 2 12V DC Power Outlets and 1 120V AC Power Outlet
- Front Map Lights
- Variable Intermittent Wipers
- Tires: P255/70R18 OWL On/Off Road
- Removable Rear Window
- Fully Galvanized Steel Panels
- Full-Size Spare Tire Mounted Outside Rear
- Front Fog Lamps
- Deep Tinted Glass
- Convertible w/Fixed Roll-Over Protection
- Conventional Rear Cargo Access
- Clearcoat Paint
- Body-Colored Grille
- Body-Colored Fender Flares
- Black Side Windows Trim
- Black Power Heated Side Mirrors w/Manual Folding
- Black Door Handles
- Auto On/Off Aero-Composite Halogen Headlamps
- Aluminum Spare Wheel
- Side Impact Beams
- Airbag Occupancy Sensor
- Outboard Front Lap And Shoulder Safety Belts -inc: Rear Center 3 Point, Height Adjusters and Pretensioners
- Dual Stage Driver And Passenger Front Airbags
- Rear Child Safety Locks
- 2 Skid Plates
- Single Stainless Steel Exhaust
- Solid Axle Rear Suspension w/Coil Springs
- Towing Equipment -inc: Trailer Sway Control
- Auto Locking Hubs
- Manual Transfer Case
- 160 Amp Alternator
- Heavy Duty Suspension w/Gas Shocks
- 880# Maximum Payload
- 50 State Emissions
- 600CCA Maintenance-Free Battery
- Part-Time Four-Wheel Drive
- Engine: 3.6L V6 24V VVT
- Engine Oil Cooler
- 4-Wheel Disc Brakes w/4-Wheel ABS, Front And Rear Vented Discs, Brake Assist and Hill Hold Control
- Front And Rear Anti-Roll Bars
- GVWR: 5,500 lbs
- Hydraulic Power-Assist Steering
- HD Shock Absorbers
- Leading Link Front Suspension w/Coil Springs
- Brake Actuated Limited Slip Differential
- 3.21 Rear Axle Ratio
- 22.5 Gal. Fuel Tank
Option Packages
Factory Installed Packages
- ENGINE: 3.6L V6 24V VVT Included
Similar vehicles
It is the customer's sole responsibility to verify the existence and condition of any equipment listed. Neither the dealership nor AutoRevo is responsible for misprints on prices or equipment. It is the customer's sole responsibility to verify the accuracy of the prices with the dealer. Pricing subject to change without notice.


text:
The fascinating story of the Plott hound
A new book has been published that will be of particular interest to area hunters, outdoorsmen, and dog lovers. It will also be of considerable value to those concerned with the region's human history.
The Story of the Plott Hound: Strike & Stay (Charleston SC: History Press, 2007; soft cover; 189 pages; $22.99) by Bob Plott is many things. It is above all the story of the evolution of a truly great America breed of dog that commenced when two youthful brothers, Johannes and Enoch Plott, brought five of their family's hounds with them from Germany to America in 1750 and eventually migrated to Western North Carolina, where the breed was perfected and continues to flourish.
It is also a family saga — one played out against the background of this country's history from before the American Revolution through the settlement of the southern Appalachian frontier and on down to the present day.
Wonderfully illustrated with hundreds of vintage photographs, it is a story chock full of noble dogs and the men and women who bred, hunted, and cared for them with ingenuity, courage, and love.
And it is the story that family member Bob Plott, the great-great-great grandson of Johannes Plott, is uniquely qualified to tell. Here is the way the account opens:
Elias Isaac Plott was tired and worried. Working in the Black Forest as a gamekeeper in all seasons, for years on end, had drained his stamina and weakened his spirit. … Plott perhaps felt that he and his wife were too old to start a new life in a new world and that the boys were young enough to acclimate themselves quickly there ... Were there relatives or friends who Elias had already arranged to welcome the boys, offering safe refuge for these young strangers in a strange land? Or were they considering working as either indentured servants or craftsmen apprentices to bankroll their start in the new world? … No one knows for sure, but as a Plott who grew up hearing the family story of my great-great-great-grandfather Johannes, I always believed that it happened the following way. I think that Elias Plott was simply hoping for a better future for his sons … Since he had little or no money, I think that he gave them a generous parting gift of the only thing of real value that he had access to — his dogs. Whether or not that is true, we do know that Johannes and Enoch Plott took some of the family's most valued possessions – five hunting dogs – with them to America in the summer of 1750. And oh, what dogs they were! Even as special as Elias Plott knew those dogs were then, neither he nor his sons could have imagined that they would ultimately, over the next two hundred years, become one of the best, if not the best, breed of big game hunting dogs the world had ever seen – the Plott bear hound.
Related Items
The book's sub-title, "Strike & Stay," is a reference to the innate instinct of a Plott hound to hunt in a certain manner. One observer described the trait as follows: "It would strike a bear trail and stay on it. And stay and stay and stay. There was just no quit." Another observed that, "He had to stay and fight, he had to stay with the bear at the tree. This breed of dog won't quit … The man who isn't game isn't fit to have him."
Much of the book carefully describes how, through the centuries, those very qualities were instilled into their Plott hounds in sundry ways by various legendary hunters. For those of us who aren't particularly interested in dog breeding, the author has made past methods and ongoing controversies a readable and integrated part of the whole.
On board the ship from Europe to America (perhaps Philadelphia), one of the brothers, Enoch, became sick, died, and was buried at sea. Now alone, except for the dogs his father had given them, Johannes eventually made his way to the eastern portion of North Carolina. By the end of the eighteenth century, his descendents and their Plott-bred hounds had made their way into the mountains of North Carolina.
By 1801, "Henry Plott and his dogs were firmly established in [what is now] Haywood County [where] the beautiful surrounding area later became known as Plott Valley. The towering mountains overlooking the valley would eventually come to be called the Plott Balsams. Henry Plott later extended his holdings to about 1,700 acres in the vicinity that now includes most of the Waynesville, Pigeon and Hazelwood, North Carolina area townships. This is the area where the Plott hound would gain legendary status as one of the premier big game hunting dogs in the world."
This is where "The Story of the Plott Hound" starts to unfold, illuminating, via the medium of one family and their dogs, facets of this region's history and culture in a way that breaks new ground. There are, of course, the fearful hunting stories involving the dogs and the men (and sometimes the women) who followed them. But there are also the stories of families and friends and the joys and hardships they shared. And there are tales — both true and tall — involving characters like Quill Rose, Von Plott, Mark Cathey, Horace Kephart, Taylor Crockett, Alphonzo "Fonz" Cable, Mrs. Montraville Plott (who, when faced with the necessity, killed a marauding wolf with her frying pan), and countless others.
By way of disclosure, I need to note in closing that Bob Plott is a close friend of mine and that I helped him with some preliminary editing. Furthermore, my wife, Elizabeth, prepared the illustration of a Plott hound that graces the book's cover. Nevertheless, despite these vested interests, I can recommend "The Story of the Plott Hound: Strike & Stay" to you without reservation.
Editor's note: This article, a review of Bob Plott's first book, was first published in The Smoky Mountain News in 2007.