text:
Common Testing Problems: Pitfalls to Prevent and Mitigate
In the first blog entry of this two part series on common testing problems, I addressed the fact that testing is less effective, less efficient, and more expensive than it should be. This second posting of a two-part series highlights results of an analysis that documents problems that commonly occur during testing. Specifically, this series of posts identifies and describes 77 testing problems organized into 14 categories; lists potential symptoms by which each can be recognized; potential negative consequences, and potential causes; and makes recommendations for preventing them or mitigating their effects.
Why Testing is a Problem
A widely cited study for the National Institute of Standards & Technology (NIST) reports that inadequate testing methods and tools annually cost the U.S. economy between $22.2 billion and $59.5 billion, with roughly half of these costs borne by software developers in the form of extra testing and half by software users in the form of failure avoidance and mitigation efforts. The same study notes that between 25 percent and 90 percent of software development budgets are often spent on testing.
Despite the huge investment in testing mentioned above, recent data from Capers Jones shows that the different types of testing are relatively ineffective. In particular, testing typically only identifies from one-fourth to one-half of defects, while other verification methods, such as inspections, are typically more effective. Inadequate testing is one of the main reasons that software is typically delivered with approximately 2 to 7 defects per thousand lines of code (KLOC). While this may seem like a negligible number, the result is that major software-reliant systems are being delivered and placed into operation with hundreds or even thousands of residual defects. If software vulnerabilities (such as the CWE/SAN Top 25 Most Dangerous Software Errors) are counted as security defects, the rates are even more troubling.
Overview of Different Types of Testing Problems
The first blog entry in this series covered the following general types of problems that are not restricted to a single kind of testing:
- test planning and scheduling problems
- stakeholder involvement and commitment problems
- management-related testing problems
- test organization and professionalism problems
- test process problems
- test tools and environments problems
- test communication problems
- requirements-related testing problems
The remainder of this second post focuses on the following six categories of problems, each restricted to one of the following types of testing:
- unit testing
- integration testing
- specialty engineering testing
- system testing
- system of system testing
- regression testing
Unit testing problems primarily occur during the testing of individual software modules, typically by the same person who developed it in the first place. Design volatility could be causing excessive iteration of the unit test cases, drivers, and stubs. Unit testing could suffer from a conflict of interest as developers naturally want to demonstrate that their software works correctly while testers should seek to demonstrate that software fails. Finally, unit testing could be poorly and incompletely performed because the developers think it is relatively unimportant.
Integration testing problems occur during the testing of a set of units integrated into a component, a set of components into a subsystem, a set of subsystems into a system, or a set of systems into a system of systems. Integration testing concentrates on verifying the interactions between the parts of the whole. One potential problem is the difficulty of localizing defects to the correct part once the parts have been integrated. A second potential problem is inadequate, built-in test software that could help locate the cause of any failed test. Finally, a third problem is the potential lack of availability of the correct (versions of the) parts to integrate.
Specialty engineering testing problems occur when an inadequate amount of specialized testing of various quality characteristics and attribute testing takes place. More specifically, these problems involve inadequate capacity, concurrency, performance, reliability, robustness (e.g., error and fault tolerance), safety, security, and usability testing. While these are the most commonly occurring types of specialty engineering testing problems, other types of specialty testing problems may also exist depending on which quality characteristics and attributes are important (and thus the type of quality requirements that have been specified).
System testing problems occur during system-level testing and often cannot be eliminated because of the very nature of system testing. At best, recommended solutions can only mitigate these problems. Is it hard to test an integrated system's robustness (support for error, fault, and failure tolerance) due to the challenges of triggering system-internal exceptions and tracing their handling. System-level testing can be hard because temporary test hooks have typically been removed so that one is testing the actual system to be delivered. As with integration testing problems, demonstrating that system tests provide adequate test coverage is hard because reaching a specific code (e.g., fault tolerance paths) by only using inputs to the black-box system is hard. Finally, there is often inadequate mission-thread-based testing of end-to-end capabilities because system-testing is often performed using use-case-based testing, which is typically restricted to interactions with only a single, primary, system-external actor.
System-of-Systems (SoS) testing problems are often the result of SoS governance problems (i.e., everything typically occurs at the system-level rather than SoS-level). For example, SoS planning may not adequately cover SoS testing. Often, no organization is made explicitly responsible for SoS testing. Funding is often focused at the system-level, leaving little/no funding for SoS testing. Scheduling is typically performed only at the individual system level, and system-level schedule-slippages make it hard to schedule SoS testing.
SoS requirements are also often lacking or of especially poor quality, making it hard to test the SoS against its requirements. The individual system-level projects rarely allocate sufficient resources to support SoS testing. Defects are typically tracked only at the system level, making it difficult to address SoS-level defects. Finally, there tends to be a lot of finger-pointing and shifting of blame when SoS testing problems arise and SoS testing uncovers SoS-level defects.
Note that a SoS almost always consists of independently governed systems that are developed, funded, and scheduled separately. SoS testing problems therefore do not refer to systems that are developed by a prime contractor or integrated by a system integrator, nor do they refer to subsystems developed by subcontractors or vendors.
Regression testing problems occur during the performance of regression testing, both during development and maintenance. Often, there is insufficient automation of regression testing, which makes regression testing too labor-intensive to perform repeatedly, especially when using an iterative- and incremental-development-cycle. This overhead is one of the reasons that regression testing may not be performed as often as it should be.
When regression testing is performed, its scope is too localized because software developers think that changes in one part of the system will not propagate to other parts, and thereby cause faults and failures. Low-level regression testing is commonly easier to perform than higher-level regression testing, which results in an over-reliance on low-level regression tests. Finally, the test resources created during development may not be delivered and thus may not be available to support regression testing during maintenance.
Addressing Test-type Specific Problems
For each testing problem described above, I have documented several types of information useful for understanding the problem and implementing a solution. This information will be appearing in an upcoming SEI technical report. As an example of what will appear in this report, the testing problem "Over-reliance on COTS Testing Tools" has been documented with the information described below
Description. Too few of the regression tests are automated.
Potential symptoms. Many or even most of the tests are being performed manually.
Potential consequences.
- Manual regression testing takes so much time and effort that it is not done.
- If performed, regression testing is rushed, incomplete, and inadequate to uncover sufficient number of defects.
- Testers are making an excessive number of mistakes while manually performing the tests.
- Defects introduced into previously tested subsystems/software while making changes may remain in the operational system.
Potential causes. Testing stakeholders (e.g., managers and the developers of unit tests) may mistakenly believe that performing regression testing is neither necessary nor cost effective because
- of the minor scope of most changes
- system testing will catch any inadvertently introduced integration defects
- they are overconfident that changes have not introduced any new defects
Testing stakeholders may also not be aware of the
- importance of regression testing
- value of automating regression testing
Other potential causes may include
- Automated regression testing may not be an explicit part of the testing process.
- Automated regression testing may not be incorporated into the Test and Evaluation Master Plan (TEMP) or System/Software Test Plan (STP).
- The schedule may contain little or no time for the development and maintenance of automated tests.
- Tool support for automated regression testing may be lacking (e.g., due to insufficient test budget) or impractical to use.
- The initially developed automated tests may not be maintained.
- The initially developed automated tests may not be delivered with the system/software.
Recommendations. Prepare by explicitly addressing automated regression testing in the project's
- TEMP or STP
- test process documentation (e.g., procedures and guidelines)
- master schedule
- work break down structure (WBS)
Enable solution of the problem by
- providing training/mentoring to the testing stakeholders in the importance and value of automated regression testing
- providing sufficient time in the schedule for automating and maintaining the tests
- providing sufficient funding to pay for automated test tools
- ensuring that adequate resources (staffing, budget, and schedule) are planned and available for automating and maintaining the tests
Perform the following tasks:
- Automate as many of the regression tests as is practical.
- Where appropriate, use commercially available test tools to automate testing.
- Ensure that both automated and manual test results are integrated into the same overall test results database so that test reporting and monitoring are seamless.
- Maintain the automated tests as the system/software changes.
- Deliver the automated tests with the system/software.
- When relevant, identify this problem as a risk in the project risk repository.
Verify that
- The test process documentation addresses automated regression testing.
- The TEMP / STP and WBS address automated regression testing.
- The schedule provides sufficient time to automate and maintain tests.
- A sufficient number of the tests have been automated.
- The automated tests function properly.
- The automated tests are properly maintained.
- The automated tests are delivered with the system/software.
Related problems. no separate test plan, incomplete test planning, inadequate test schedule, unrealistic testing expectations / false sense of security, inadequate test resources, inadequate test maintenance, over-reliance on manual testing, tests not delivered, inadequate test configuration management (CM)
Benefits of Using the Catalog of Common Testing Problems This analysis of commonly occurring testing problems--and recommended solutions--can be used as training materials to better learn how to avoid, identify, and understand testing problems and mitigate them. Like anti-patterns, these problem categories can be used to improve communication between testers and testing stakeholders. This list can also be used to categorize problem types for metrics collection. Finally, they can be used as a checklist when
- producing test plans and related documentations
- evaluating contractor proposals
- evaluating test plans and related documentation (quality control)
- evaluating as-performed test process (quality assurance)
- identifying test-related risks and their mitigation approaches
Future Work
The framework of testing problems outlined in this series is the result of more than three decades of experience in assessments and my involvement in numerous projects and discussions with testing subject matter experts. Even after all this time, however, several unanswered questions remain that I intend to be the subject of future study:
- Probabilities. Which of these problems occur most often? What is the probability distribution of these problems? Which problems tend to cluster together? Do different problems tend to occur with different probabilities in different application domains such as commercial versus governmental versus military and web versus information technology versus embedded systems, etc.)?
- Severities. Which problems have the largest negative consequences? What are the probability distributions of harm caused by each problem?
- Risk. Based on the above probabilities and severities, which of these problems cause the greatest risks? Given these risks, how should one prioritize the identification and resolution of these problems?
I am interested in turning my work on this topic thus far into an industry survey and perform a formal study to answer these questions. I welcome your feedback on my work to date in the comments section below.
Additional Resources
To view a presentation on this work, please view, Common Testing Problems: Pitfalls to Prevent and Mitigate, and the associated Checklist Including Symptoms and Recommendations, which were presented at the FAA Verification and Validation Summit 8 (2012) in Atlantic City, New Jersey on 10 October 2012.


text:
Looking for a local, pick-your-own farm in Scotland? Scroll down this page and you will see the U-Pick farms in Scotland, sorted by county. Those that offer organic or sustainably grown produce are identified by the words "organic" and/or "sustainable" in Green, next to their name . The U-pick crops they offer follow the name of the farm. To search the page for a specific crop, use Ctrl-F (or on an ipad or Mac, use their "search on this page" function) If they have a website, the name will be in blue and underlined; click on it and it will open their website. Beware of copycat websites (such as pickyourown.farm) ; they just co[pied my website a few years ago, and do not update their information as I do, so theirs are usually out-of-date -and often copied incorrectly! I put dates to indicate when we last received an update from each farm, and I make updates weekly (and whenever I hear from a farm or visitor with new info). See the customer and farmer menus at the top menu bar to submit updates and corrections and help me keep each current!
And if you know of any I missed and want to add them or correct the information, please let me know! There are affiliate links on this page. Read our disclosure policy to learn more.
Notes for August 2020: Summer crops are underway; don't miss the berry season, strawberries are first, followed by the brambles! Damsons and other plums, figs, and summer veg are next!
Strawberry festivals, fetes and fayres are coming, most in June and July - see this page to find a strawberry festival near you! We also have home preserving, bottling, drying and freezing directions. You can access recipes and other resources from the drop down menus at the top of the page or the site search. If you have any questions or suggestions, feel free to write me!
Click on the resources drop-down above, if you need a county map
|Late Aug to late October
|Mid July to mid September
|Mid July to mid August
|Mid July to late August
|Late June to late July
|Late August to mid September
|Late June till late September
|Mid July to late August
|Mid June till late September
Click here for farmshops in this area.

subset: commoncrawl


text:
Rudyard Kipling
Rudyard Kipling (30 December 1865 – 18 January 1936 / Bombay)
» Click to list general statistics » OR, select a date :
Alnaschar And The Oxen
There's a pasture in a valley where the hanging woods divide,
And a Herd lies down and ruminates in peace;
read more >>
- Hits: Number of visitors who read the poem on the given date.
- Posts: Number of visitors who posted the poem to a friend (via e-mail) on the given date.
- Dates that have "0" hits may not be shown on the list.
- Dates, poems and poets that have "0" hits may not be shown on the list. Statistics are generated daily.


text:
Thar she goes!
New London - "Big and tubby" is how Sean Bercaw, the second mate for the Charles W. Morgan's historic 38th Voyage, describes the 460-ton, 173-year-old square-rigger.
"Not in a bad way," said Bercaw. "She was a whaleship, and she was built to carry bulk. She'd carry up to 90,000 gallons of oil" back to her homeport during her whaling days.
A former captain of the Amistad, Bercaw believes that when the 22 sails are set on the Morgan today and the oldest commercial ship still afloat in the country freely sails again for the first time in almost a century, she'll move pretty nimbly.
"She's leaner below the water line than you'd think," said Bercaw, 53, of Falmouth, Mass. "I think she'll move more agilely than a lot of people would think. If she was truly ungainly and cumbersome, they would not have sailed her for 80 years. If she was a dog, they would not have sailed her all around the world."
Today's shakedown cruise will provide the first tangible evidence for the Mystic Seaport, owner of the Morgan for the past 73 years, of how the 113-foot vessel handles in open water.
If all goes as planned, the Morgan will shove off from New London's City Pier at 9:30 a.m. to commence sea trials in Fishers Island Sound as it prepares for a tour of New England ports that is scheduled to begin June 14. It will be the first time under sail since the Morgan's working days ended in the early 1920s.
Capt. Kip Files said if the wind is just right - "if there's a northerly, we'll sail her out from the dock" - but it's more likely that the ship will be assisted by a tugboat to get away from the pier and down the river.
"There's nobody alive today who has seen her sail or sailed on her," said Files, 62, explaining that everyone closely involved in the Morgan restoration/38th Voyage project is anxious to see how she moves.
Like his second mate, Bercaw, Files has seen the Morgan out of the water and, judging from her lines, believes "she will sail better than we think she will."
"It will be fun," he said of the shakedown cruise. "The biggest challenge will be seeing how she handles in different conditions and how she maneuvers under sail configurations."
For Files, who owns his own 132-foot, three-masted schooner Victory Chimes in Rockland, Maine, the primary concern is keeping the Morgan's crew and the ship itself - it is the last wooden whaler out of a fleet that once numbered more than 2,700 vessels - out of harm's way.
"Yes, this is a huge historic event, but that's different from sailing her," said Files. "The sailing it, the sailing event itself, is like flying an antique airplane. You do it, you focus on safety, and later you think about how the ride was."
The 15-member crew was chosen from "a huge number of applications," said Files, and "are all trained, some licensed professionals."
Crew members are not only physically strong, but are seasoned or experienced sailors with good people skills, said the captain. "It's not just that they can sail, but they need to do the mission that the Mystic Seaport wants us to do. They have to like people and be able to communicate and talk," he said.
'Sign me up'
Since May 17, when the Morgan was towed from its decades-long home at the Mystic Seaport to downtown New London, ballast has been added and the crew has been working 12-hour days to rig the boat. There's more than a mile of cordage on the whaleship, and when every sail is set, the Morgan sails under 13,000 square feet of canvas.
Chief mate Sam Sikkema of Leander, Texas, said that for the past three weeks the crew has been "doing everything that makes the ship go with wind power," positioning cables, wires, blocks and sails. Coordinating all of that has been a challenge, he said, especially because at times the Morgan has been open to visitors.
But like the rest of the crew, Sikkema, 26, said that when he heard about the plan to sail the Morgan, he knew he wanted to be on board. "It's one of the most significant maritime events in my lifetime," he said. "I can't imagine something like this coming around again."
Julianne "Juls" Johnson, 55, of Mystic, who was hired as provisioner and cook for the voyage, said she couldn't be happier. "When I heard about this, I didn't even have to think about it. 'Sign me up,' I said. It's a moment in history," she said.
When Johnson found out she got the job, she admits being overwhelmed with emotions. "I got all choked up," she said. "This is such an opportunity to be part of something so special."
Johnson, who has cooked on other vessels, will not be cooking on the Morgan's old wood stove - she'll have electricity and two stove-top griddles, a crock pot and an electric frying pan. And among the crew, she will be catering to a vegetarian, a vegan, and two members who are gluten-free.
Deckhand Dana Mancinelli, who started sailing on the U.S. Coast Guard barque Eagle when she was a student there in 1994, is now the third mate on the National Oceanic and Atmospheric Administration's Okeanos Explorer. She filled out her Morgan crew application electronically and emailed it in while working off the North Carolina shore.
"I just wanted to be part of this amazing opportunity," said the native of New Fairfield, explaining that she will use up all of her leave time to fulfil the 38th Voyage commitment. "This is how I'm spending my vacation, on a tar-covered cruise ship."
'To feel her alive'
It's a small community that sails and crews on tall ships and square rigs, and for that reason, a number of the Morgan's crew members have worked together in the past, or at least know of one another.
Third mate Roxanne "Rocky" Hadler worked as a college registrar in Texas for 28 years before retiring and taking up tall ships in 2005.
"We're like a family," she said. "There's a camaraderie. You become very tight with the people you work with."
Like all the others, Hadler said she very much wanted to be a part of the Morgan's crew. "Everyone in the tall-ship community is so excited about this," she said. "I can't even imagine ... to feel her alive, to feel the wind in her sails."
Between ships, the 61-year-old Hadler makes her home in Houston.
Joee Patterson, 33, another deckhand, said when the sails are first unfurled it will be a whirlwind. "There will be a frenzy of activity, and the focus will be on executing. But then, I think it will feel amazing," she said.
When her sailing friends learned she was going to be a member of the Morgan's crew, they initiated an online book club and all read and discussed "Moby Dick."
"In the circles I run in, this is a very big deal," Patterson said.
Today is Dan Roche's 24th birthday, and the deckhand wouldn't want to be anywhere else. "It will be simply amazing to get this moving again," he said, standing on the deck of the Morgan. "And with sea trials, we'll be fine-tuning and getting everything just right. But once everything is set, that one moment when we're not all running around, that will be pretty great."
The crew members all agree that it will be intense once the sails are set and the captain and mates start calling out orders. But they also believe there will come a moment when they'll be able to experience the roll of the ship, the wind in the sails, and the solemnity of the moment.
"Knowing that no one today has ever seen her sail, and that I'll be hauling a line to make her sail ... It's so big, it humbles you," said Mancinelli. "This traditional ship is older than any friendship you will ever have. I don't have words for it, really."
INTERACTIVE: 38th Voyage Captain and Crew
Meet the 38th Voyage Captain and Crew
Stories that may interest you
Writing on Water: On politics, religion and clambakes
Researcher Kathy Neustadt (a leading "clamologist") writes that, while clambaking has prehistoric origins, it fell out of favor with the early settlers especially following King Phillip's War when the Wampanoag people were almost completely wiped out.
Kids go on ecological escapade at Rocky Neck State Park in East Lyme
As temperatures soared Wednesday, some visitors to Rocky Neck State Park were seeking more than just relief in the water.
Connecticut Democrats embrace historic moment, cheer Harris as Biden's running mate
State and local Democratic leaders are ecstatic that presidential candidate Joe Biden has chosen U.S. Sen. Kamala Harris as his running mate.
Groton plans to reopen schools on Sept. 8 under hybrid model
The Groton school district will begin the school year on Sept. 8 under a hybrid model, with safety protocols, such as mask wearing and social distancing, in place when children attend in person.
Inmate at Montville prison dies after being found with ligature fashioned from mask
5 more Connecticut residents fined for violating COVID-19 travel rules


text:
Pen Tablet Support
From OLPC
The XO-1 comes equipped with a unique dual-mode pointing device. It functions both as a conventional trackpad (the capactive-sensitive "Glide Sensor") and as a graphics tablet (the pressure-sensitive "Pen Tablet"). This page documents how the PenTablet is supported by the OLPC system software.
NOTE: As of Build 656 (2008-01-17), the system software does not contain built-in support for the PenTablet.
Sample Activities
The state of Pen Tablet support is currently in flux, but there are some sample applications created by Patrick Dubroy that will allow you play with the tablet. NB: These applications assume no tablet support in X, so they fork an external process (evtest) to read from the tablet.
- TabletAreaTest demonstrates a GTK widget that is mapped to tablet input
- tabletui explores some user interface prototypes for the unconstrained drawing case
For Activity Developers
- The OLPC Human Interface Guidelines explain how the dual-purpose touchpad/PenTablet works from a user's point of view: see here.
- If you want to map tablet input to a widget that's the same shape and aspect ratio as the physical tablet, see Pen Tablet Support/GTK Widget.
- If you want to use the tablet to draw a larger canvas, as in e.g. the Paint activity, see Pen Tablet Support/Unconstrained Drawing API
Ideas for Activities using the tablet
- a pen-based calculator like Harold and Will Thimbleby's:
- Imagine writing a calculation down on paper and the paper magically working out the answers. We have built a calculator that works like this, which is ideal for pen based computers and interactive whiteboards in classrooms. It recognises your handwriting, and you write naturally, using ordinary mathematics notation you are already familiar with.
For OLPC Core Developers
User Interaction
It has not yet been decided how the user interaction with the PenTablet will work. The issues are discussed here: Pen Tablet UI.
Driver issues
In March 2007, Zephaniah E. Hull posted an informative description of the low-level driver details here.
The PenTablet driver has disabled for quite some time (as of March 2008) because:
- the PenTablet is not currently being correctly identified as having capability "input.tablet" (see http://dev.laptop.org/ticket/5268)
- apparently enabling this capability caused the problem of one button click being interpreted as two (see http://dev.laptop.org/ticket/6079)
According to Andres Salomon (here and here), the touchpad driver has been completely rewritten in the master branch, so Update.1 will contain correct drivers for the touchpad and the PenTablet.


text:
I'm not an Altera expert either!adrm wrote: So, what is the approved way to resolve this?
E.g. feed CLOCK_50 into multiple SIGNALS and then feed these into the PLLs?
But, this does seem to be a rather nasty / fundamental limitation of Cyclone II:
And it's why the DE1 feeds the same clock in on multiple pins. Shame they forgot this trick on the DE2!
It's worth googling the exact error message, just to see if there is an easy answer, but I suspect not.
I can think of a few ways to work around this (in order of difficulty):
1. Use one PLL to go from 50MHz to 32MHz and a second PLL to go from 27MHz to 24MHz (and drop the second scan doubler).
2. Use one PLL to go from 50MHz to 96MHz, then a /3 counter to get 32MHz and a /4 counter to get 24MHz.
3. Use a fast counter to generate a 24 and 32MHz clocks that are not quite regular, but have the right average frequency. See here for an example. This is quite hard to get your head around, so I'd try the others first.
You are getting a bit of a baptism of fire here!


text:
In the meantime! Christian Schenk has a swell post comparing Guice, PicoContainer, and Spring. Of course, my favorite part is this:
Spring seems to be harder to use than Guice: without autowiring you have to specify the dependencies between your beans in a very verbose manner, i.e. you have to think about the things you'd like to do and write them down in a configuration file. Ideally you don't have to specify anything with Guice, except the Inject annotations and Guice will handle everything for you.
Ahh, you've just gotta love that shit. I think I'll set it to music.
But Christian's conclusion?
First I opted for Guice because I like experimenting with new, bleeding-egde software. But as I said earlier, all these annotations couple your software tightly to Guice - that's not very desirable. . . . To draw a conclusion I think choosing between Guice, PicoContainer and Spring, for lack of a hard and fast rule, will be to do what works best for your project.
I want to address this idea of coupling, because I'm noticing that this concern crops up again and again, and I think that the issue has more to do with perception than anything else.
Does embedding @Inject in your code tightly couple your code to Guice? It does in one sense: some version of guice.jar is going to have to be present on your classpath whenever you compile your implementation classes. This much is true. Beyond this, though -- it's really not that bleak. Your classes have no runtime dependency on Guice. If they run as part of an application that doesn't wish to use Guice, the Guice jar file needn't even be present on the server at all! Now, this changes if you want to use more Guice features, like provider injection and injector injection, but this is the case with Spring as well.
Furthermore, the idea of "coupling" implies that "the one cannot function without the other." But with Guice's annotations, this simply isn't the case. It's important to understand that these are only annotations. They are decoration; meta-information. They don't, and can't, actually do anything. They just sit there, innocuously, in case tools will wish to read them, and otherwise have no effect whatsoever. They do absolutely nothing to impede you from testing your code, or from using the classes with Spring.
Perhaps the issue -- and I'm not specifically talking about Christian, but about all the many who have had this objection -- perhaps the issue is a more visceral disdain for seeing import com.google anywhere in your code? Maybe you feel the same way about import org.apache, so you eschew the Apache Commons and all that stuff too? Begone, vile dependencies! Or maybe "that's different," after all, Google is a big old corporation, and I think it might have been on Slashdot the other day that we've Turned Evil now.
In any case, Google doesn't intend to stop open-sourcing our awesome Java shit anytime soon, so you may have to confront that particular issue again and again. Oop, I said too much....
Now, I ask you -- is one extra jar file in your javac classpath really all that bad? Or are there some additional problems that I don't yet understand?


text:
- 2 tablespoons (1/4 stick) unsalted butter, room temperature
- 1 garlic clove, minced
- 1 1/2 teaspoons chopped fresh marjoram or oregano
- 1/2 teaspoon sweet paprika
- Kosher salt and freshly ground black pepper
- 2 skinless, boneless chicken breasts
- 2 cups mixed cherry tomatoes (11-12 ounces)
- 1 tablespoon chopped fresh flat-leaf parsley
Recipe Preparation
Mash butter, garlic, marjoram, and paprika in a small bowl to blend. Season marjoram butter to taste with salt and pepper.
Melt 1 tablespoon marjoram butter in a medium heavy skillet over medium heat. Season chicken with salt and pepper. Add chicken to skillet, cover, and cook until no longer pink in center, about 5 minutes per side. Transfer chicken to a plate. Tent chicken with foil to keep warm.
Increase heat to high. Add tomatoes to skillet and cook, stirring occasionally, until they begin to char and burst, about 5 minutes. Add remaining marjoram butter to skillet. Crush tomatoes slightly to release juices; stir 1 minute. Season sauce to taste with salt and pepper. Spoon tomato sauce over chicken. Garnish with parsley.


text:
This case arose from some rather complex but interesting facts:
Defendant resigned from his job with an IT consulting firm. One of the firm's customers hired defendant as an employee. Before the customer/new employer terminated the agreement with the IT consulting firm/former employer, defendant used the customer/new employer's credentials to access and copy some scripts from the system. (Having the new employee and the scripts eliminated the need to have the consulting firm retained.) The firm/former employer sued under the Computer Fraud and Abuse Act. Defendants (the customer and its new employee) moved to dismiss for failure to state a claim. The court granted the motion.
It held that the complaint failed to allege "unauthorized access" within the Ninth Circuit's interpretation of the CFAA.
The court looked to the Ninth Circuit's holding in LVRC Holdings LLC v. Brekka, 581 F.3d 1127 (9th Cir. 2009), which provides that to access a protected computer "without authorization" is to do so "without any permission at all," and that to "exceed authorized access" is to "access information on the computer that the person is not entitled to access." And it looked to the more recent case of U.S. v. Nosal, 676 F.3d 854, 863 (9th Cir. 2012), which teaches that an individual does not "exceed authorized access" simply by misusing information that he or she was entitled to view for some other purpose. Under Nosal, the CFAA regulates access to data, not its use by those entitled to access it.
In this case, the court found that the complaint did not allege that defendants were unauthorized to access the scripts in question. In fact, the Statement of Work that the court reviewed specifically granted defendant's employer and its representatives (including defendant) "sudo access" to "non-shell root commands" that included the scripts at issue.
Plaintiff argued that the access was unauthorized because it had repeatedly refused to grant defendant or his employer the authority to write or edit those scripts. But the court found that argument to address the misuse of the scripts, not unauthorized access. Under Nosal this conduct did not run afoul of the CFAA. So because the complaint failed to allege that defendant and his new employer had no access rights to the scripts, and because the documents upon which plaintiff relied revealed that defendants had certain access rights, the court dismissed the CFAA claim.
Enki Corporation v. Freedman, 2014 WL 261798 (N.D.Cal. January 23, 2014)


text:
Privacy Policy
Katexim Europe Limited ("We") are committed to protecting and respecting your privacy.
This policy will inform you of the basis on which we collect any personal data from you, or that you provide to us and how it will be processed by us. This policy will also tell you about your privacy rights and how the law protects you.
.This website is not intended for children and we do not knowingly collect data relating to children.
Katexim Europe Limited is the controller and responsible for your personal data (collectively referred to as "we", "us" or "our" in this privacy policy).
We have appointed a data privacy manager who is responsible for overseeing questions in relation to this privacy policy. If you have any questions about this privacy policy, including any requests to exercise your legal rights, please contact the data privacy manager using the details set out below.
Contact details
If you have any questions about this privacy policy or our privacy practices, please contact our data privacy manager in the following ways:
Katexim Europe Limited
Registered office address:
Katexim Europe Limited
c/o Haines & Watts
Hamilton Office Park
31 High View Close,
e-mail: Dit e-mailadres wordt beveiligd tegen spambots. JavaScript dient ingeschakeld te zijn om het te bekijken.
You have the right to make a complaint at any time to the Information Commissioner's Office (ICO), the UK supervisory authority for data protection issues (www.ico.org.uk). We would, however, appreciate the chance to deal with your concerns before you approach the ICO so please contact us in the first instance.
It is important that the personal data we hold about you is accurate and current. Please keep us informed if your personal data changes during your relationship with us.
Third-party links
This website may include links to third-party websites, plug-ins and applications. These include links to You Tube videos. Clicking on those links or enabling those connections may allow third parties to collect or share data about you. We do not control these third-party websites and are not responsible for their privacy statements. When you leave our website, we encourage you to read the privacy policy of every website you visit.
Information we may collect from you
Personal data, or personal information, means any information about an individual from which that person can be identified. It does not include data where the identity has been removed (anonymous data).
We may collect, use, store and transfer different kinds of personal data about you which we have grouped together as follows:
Identity Data includes first name, maiden name, last name, username or similar identifier, title and gender.
Contact Data includes billing address, delivery address, email address and telephone numbers.
Financial Data includes bank account and payment card details.
Transaction Data includes details about payments to and from you and other details of products and services you have purchased from us.
Technical Data includes internet protocol (IP) address, your login data, browser type and version, time zone setting and location, browser plug-in types and versions, operating system and platform, and other technology on the devices you use to access this website.
Profile Data includes your username and password, purchases or orders made by you, your interests, preferences, feedback and survey responses.
Usage Data includes information about how you use our website, products and services.
Marketing and Communications Data includes your preferences in receiving marketing from us and our third parties and your communication preferences.
We do not collect any Special Categories of Personal Data about you (this includes details about your race or ethnicity, religious or philosophical beliefs, sex life, sexual orientation, political opinions, trade union membership, information about your health, and genetic and biometric data). Nor do we collect any information about criminal convictions and offences.
How is your personal data collected
We use different methods to collect data from and about you including through:
Direct interactions. You may give us your Identity, Contact and Financial Data by filling in forms or by corresponding with us by post, phone, email or otherwise. This includes personal data you provide when you:
- · apply for our products or services;
- · subscribe to our service or publications;
- · request marketing to be sent to you;
- · enter a competition, promotion or survey; or
- · give us feedback or contact us.
Automated technologies or interactions. As you interact with our website, we will automatically collect Technical Data about your equipment, browsing actions and patterns. We collect this personal data by using cookies, server logs and other similar technologies. Please see our cookie policy for further details.
Third parties or publicly available sources. We will receive personal data about you from various third parties and public sources as set out below:
- · Technical Data from the following parties:
(a) analytics providers such as Google;
(b) advertising networks; and
(c) search information providers.
- · Contact, Financial and Transaction Data from providers of technical, payment and delivery services.
- · Identity and Contact Data from data brokers or aggregators.
Our website uses cookies to distinguish you from other users of our website. This helps us to provide you with a good experience when you browse our website and also allows us to improve our site. For detailed information on the cookies we use and the purposes for which we use them see our Cookie policy.
You should also note that third party vendors, including Google, use cookies to serve ads based on a user's prior visit to our website or other websites.
Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to our sites and/or other sites on the Internet.
You can opt out of personalized advertising by changing your browser settings.
Uses made of the information
We will only use your personal data when the law allows us to. Most commonly, we will use your personal data in the following circumstances:
Where we need to perform the contract we are about to enter into or have entered into with you.
Where it is necessary for our legitimate interests (or those of a third party) and your interests and fundamental rights do not override those interests.
Where we need to comply with a legal obligation.
Generally, we do not rely on consent as a legal basis for processing your personal data although we will get your consent before sending third party direct marketing communications to you via email or text message. You have the right to withdraw consent to marketing at any time by contacting us.
We have set out below, in a table format, a description of all the ways we plan to use your personal data, and which of the legal bases we rely on to do so. We have also identified what our legitimate interests are where appropriate.
Note that we may process your personal data for more than one lawful ground depending on the specific purpose for which we are using your data. Please contact us if you need details about the specific legal ground we are relying on to process your personal data where more than one ground has been set out in the table below.
Type of data
Lawful basis for processing including basis of legitimate interest
To register you as a new customer
(a) Identity
(b) Contact
Performance of a contract with you
To process and deliver your order including:
(a) Manage payments, fees and charges
(b) Collect and recover money owed to us
(a) Identity
(b) Contact
(c) Financial
(d) Transaction
(e) Marketing and Communications
(a) Performance of a contract with you
(b) Necessary for our legitimate interests (to recover debts due to us)
To manage our relationship with you which will include:
(a) Notifying you about changes to our terms or privacy policy
(b) Asking you to leave a review or take a survey
(a) Identity
(b) Contact
(c) Profile
(d) Marketing and Communications
(a) Performance of a contract with you
(b) Necessary to comply with a legal obligation
(c) Necessary for our legitimate interests (to keep our records updated and to study how customers use our products/services)
To enable you to partake in a prize draw, competition or complete a survey
(a) Identity
(b) Contact
(c) Profile
(d) Usage
(e) Marketing and Communications
(a) Performance of a contract with you
(b) Necessary for our legitimate interests (to study how customers use our products/services, to develop them and grow our business)
To administer and protect our business and this website (including troubleshooting, data analysis, testing, system maintenance, support, reporting and hosting of data)
(a) Identity
(b) Contact
(c) Technical
(a) Necessary for our legitimate interests (for running our business, provision of administration and IT services, network security, to prevent fraud and in the context of a business reorganisation or group restructuring exercise)
(b) Necessary to comply with a legal obligation
To deliver relevant website content and advertisements to you and measure or understand the effectiveness of the advertising we serve to you
(a) Identity
(b) Contact
(c) Profile
(d) Usage
(e) Marketing and Communications
(f) Technical
Necessary for our legitimate interests (to study how customers use our products/services, to develop them, to grow our business and to inform our marketing strategy)
To use data analytics to improve our website, products/services, marketing, customer relationships and experiences
(a) Technical
(b) Usage
Necessary for our legitimate interests (to define types of customers for our products and services, to keep our website updated and relevant, to develop our business and to inform our marketing strategy)
To make suggestions and recommendations to you about goods or services that may be of interest to you
(a) Identity
(b) Contact
(c) Technical
(d) Usage
(e) Profile
(f) Marketing and Communications
Necessary for our legitimate interests (to develop our products/services and grow our business)
We strive to provide you with choices regarding certain personal data uses, particularly around marketing and advertising.
We may use your Identity, Contact, Technical, Usage and Profile Data to form a view on what we think you may want or need, or what may be of interest to you. This is how we decide which products, services and offers may be relevant for you (we call this marketing).
You will receive marketing communications from us if you have requested information from us or purchased goods or services from us and you have not opted out of receiving that marketing.
We will get your express opt-in consent before we share your personal data with any third party for marketing purposes.
You can ask us or third parties to stop sending you marketing messages at any time by contacting us.
Where you opt out of receiving these marketing messages, this will not apply to personal data provided to us as a result of a product/service purchase, warranty registration, product/service experience or other transactions.
Disclosure of your information
We may share your personal information with any member of our group, which means our subsidiaries, our ultimate holding company and its subsidiaries, as defined in section 1159 of the UK Companies Act 2006.
We may share your information with selected third parties including:
- § Business partners, suppliers and sub-contractors for the performance of any contract we enter into with you.
- § Advertisers and advertising networks that require the data to select and serve relevant adverts to you and others
- § Analytics and search engine providers that assist us in the improvement and optimisation of our site.
We may disclose your personal information to third parties:
- § In the event that we sell or buy any business or assets, in which case we may disclose your personal data to the prospective seller or buyer of such business or assets.
- § If Katexim Europe Limited or substantially all of its assets are acquired by a third party, in which case personal data held by it about its customers will be one of the transferred assets.
- § If we are under a duty to disclose or share your personal data in order to comply with any legal obligation, or in order to enforce or apply our terms of use and other agreements; or to protect the rights, property, or safety of Katexim Europe Limited, our customers, or others. This includes exchanging information with other companies and organisations for the purposes of fraud protection and credit risk reduction.
Where we store your personal data
The data that we collect from you may be transferred to, and stored at, a destination outside the European Economic Area ("EEA"). It may also be processed by staff operating outside the EEA who work for us or for one of our suppliers. Such staff maybe engaged in, among other things, the fulfilment of your order, the processing of your payment details and the provision of support services.
Whenever we transfer your personal data out of the EEA, we ensure a similar degree of protection is afforded to it by ensuring at least one of the following safeguards is implemented:
We will only transfer your personal data to countries that have been deemed to provide an adequate level of protection for personal data by the European Commission. For further details, see European Commission: Adequacy of the protection of personal data in non-EU countries.
Where we use certain service providers, we may use specific contracts approved by the European Commission which give personal data the same protection it has in Europe. For further details, see European Commission: Model contracts for the transfer of personal data to third countries.
Where we use providers based in the US, we may transfer data to them if they are part of the Privacy Shield which requires them to provide similar protection to personal data shared between Europe and the US. For further details, see European Commission: EU-US Privacy Shield.
Data Security
We have put in place appropriate security measures to prevent your personal data from being accidentally lost, used or accessed in an unauthorised way, altered or disclosed. In addition, we limit access to your personal data to those employees, agents, contractors and other third parties who have a business need to know. They will only process your personal data on our instructions and they are subject to a duty of confidentiality.
We have put in place procedures to deal with any suspected personal data breach and will notify you and any applicable regulator of a breach where we are legally required to do so. Unfortunately, the transmission of information via the internet is not completely secure. Although we will do our best to protect your personal data, we cannot guarantee the security of your data transmitted to our site; any transmission is at your own risk. Once we have received your information, we will use strict procedures and security features to try to prevent unauthorised access.
Data Retention
We will only retain your personal data for as long as reasonably necessary to fulfil the purposes we collected it for, including for the purposes of satisfying any legal, regulatory, tax, accounting or reporting requirements. We may retain your personal data for a longer period in the event of a complaint or if we reasonably believe there is a prospect of litigation in respect to our relationship with you.
To determine the appropriate retention period for personal data, we consider the amount, nature and sensitivity of the personal data, the potential risk of harm from unauthorised use or disclosure of your personal data, the purposes for which we process your personal data and whether we can achieve those purposes through other means, and the applicable legal, regulatory, tax, accounting or other requirements.
Your rights
Under certain circumstances, you have rights under data protection laws in relation to your personal data.
You have the right to:
Request access to your personal data (commonly known as a "data subject access request"). This enables you to receive a copy of the personal data we hold about you and to check that we are lawfully processing it.
Request correction of the personal data that we hold about you. This enables you to have any incomplete or inaccurate data we hold about you corrected, though we may need to verify the accuracy of the new data you provide to us.
Request erasure of your personal data. This enables you to ask us to delete or remove personal data where there is no good reason for us continuing to process it. You also have the right to ask us to delete or remove your personal data where you have successfully exercised your right to object to processing (see below), where we may have processed your information unlawfully or where we are required to erase your personal data to comply with local law. Note, however, that we may not always be able to comply with your request of erasure for specific legal reasons which will be notified to you, if applicable, at the time of your request.
Object to processing of your personal data where we are relying on a legitimate interest (or those of a third party) and there is something about your particular situation which makes you want to object to processing on this ground as you feel it impacts on your fundamental rights and freedoms. You also have the right to object where we are processing your personal data for direct marketing purposes. In some cases, we may demonstrate that we have compelling legitimate grounds to process your information which override your rights and freedoms.
Request restriction of processing of your personal data. This enables you to ask us to suspend the processing of your personal data in the following scenarios:
- · If you want us to establish the data's accuracy.
- · Where our use of the data is unlawful but you do not want us to erase it.
- · Where you need us to hold the data even if we no longer require it as you need it to establish, exercise or defend legal claims.
- · You have objected to our use of your data but we need to verify whether we have overriding legitimate grounds to use it.
Request the transfer of your personal data to you or to a third party. We will provide to you, or a third party you have chosen, your personal data in a structured, commonly used, machine-readable format. Note that this right only applies to automated information which you initially provided consent for us to use or where we used the information to perform a contract with you.
Withdraw consent at any time where we are relying on consent to process your personal data. However, this will not affect the lawfulness of any processing carried out before you withdraw your consent. If you withdraw your consent, we may not be able to provide certain products or services to you. We will advise you if this is the case at the time you withdraw your consent.
You will not have to pay a fee to access your personal data (or to exercise any of the other rights). However, we may charge a reasonable fee if your request is clearly unfounded, repetitive or excessive. Alternatively, we could refuse to comply with your request in these circumstances.
We may need to request specific information from you to help us confirm your identity and ensure your right to access your personal data (or to exercise any of your other rights). This is a security measure to ensure that personal data is not disclosed to any person who has no right to receive it. We may also contact you to ask you for further information in relation to your request to speed up our response.
We try to respond to all legitimate requests within one month. Occasionally it could take us longer than a month if your request is particularly complex or you have made a number of requests. In this case, we will notify you and keep you updated.
Changes to our privacy policy
Any changes we may make to our privacy policy in the future will be posted on this page and, where appropriate, notified to you by e-mail. Please check back frequently to see any updates or changes to our privacy policy.
Questions, comments and requests regarding this privacy policy are welcomed and should be emailed or sent via the enquiry box on the website.


text:
0 Members and 1 Guest are viewing this topic.
I'm sure sorry to see this happen, I can't say I blame you though. Your contributions to this forum have been great & will be missed. There have been many good members leave already because of him. I'm sure there will be plenty more to leave before it's over. I've considered it myself because of this type of thing. Hopefully we'll see you back when the board wakes up & gets rid of this A hole. Cliff
So, let me get this straight... We are a group, owned by and controlled by the members, and we actually let someone join, be an azzhat, and that forces a most valuable member to tuck his tail and run?WTF? Did DJ Trump join, and abuse you on twitter? I admit, I don't know the whole story, but, it wouldn't be too hard to tell the NFG to "please accept this refund of any dues you have paid, your membership is revoked, and your forum access is recinded..." In other words, thanks but no thanks, now GTFO...Maybe I'm missing something here.
I admit, I don't know the whole story, but, it wouldn't be too hard to tell the NFG to "please accept this refund of any dues you have paid, your membership is revoked, and your forum access is recinded..." In other words, thanks but no thanks, now GTFO...Maybe I'm missing something here.
Fred, I have been there as you know and have also taken breaks. I'm not saying That I was always the perfect little angel in anything I was involved in. I'm sure you can also admit not by no means being perfect. With that said though, Your assertions that there was some sort of grudge against you has come across to me as true for years now. Obviously you know this as well. The person in question stated it is and has always been about your selling a product in the wrong forum section. Although technically correct. It is by far not the only example that has happened either directly or non directly for years by folks. I would expect a little leeway and definitely with some long term members/contributors. It is also very apparent to me that it has been about anything Fred did since Fred became the tech editor. At least IMO. So no I do not see it is/was only about selling products. The person in question is not the first person to act this way. A lot of folks have had moments they are not proud of on the forum. This particular person has basically been this way as long as I have been around, which has been a fair amount of time now. Certain people can't help themselves in the need to be right and the authority on all matters. The problem is they are convinced they are right no matter how wrong they actually are. The same person quoted me just the other day to in what came across to me as his need to show his superiority over my post that contradicted his post. The problem is both his posts are IMO, wrong. Or the wiring diagrams for the C10 are. Who knows maybe they are and he is right. With that said, I hope you change your mind about retiring from the club. Maybe bringing this to light may actually shine a light that this person may finally see and make him realize. Probably not, but there is always hope. None of us are perfect and we all make mistakes. By all means that definitely includes me. People can and do change sometimes. Like other things, the first step is realizing there is a problem. And a lot of times folks don't realize there is a problem until a group of others point it out. If this puts me in the category of band wagon, so be it. I hate seeing people leave for reasons that can be corrected.
Page created in 0.578 seconds with 26 queries.


text:
Are you in the United States?
Visit our U.S.A. & International site for relevant pricing, distribution and product availability information.Go to StarTech.com
4-Bay Mobile Rack Backplane for 2.5in SATA/SAS Drives
Hot swap with ease by installing four SSDs/HDDs into one 5.25in bay
Product ID: SATSASBP425
- Build your storage system by adding four 2.5in SAS or SATA drives into one 5.25in bay
- Supports a wide range of SSDs and HDDs from 5-15mm
- Easy, error free insertion of tray with vertically or horizontally mounted backplane
- Lockable, removable trays provide drive protection
- NSS connector provides 50,000+ insertion rating for long-lasting performance
- Interchangeable drive trays also work with the 1-bay backplane (SATSASBP125)
- High-quality metal housing provides enhanced heat dissipation
- Two 40mm fans to optimize ventilation
- Flammability rating of UL 94 V-O
- Support for SAS II and SATA I, II and III with file transfer speeds of up to 6Gbps
- Works with your RAID or HyperDuo controller
Now it's easy to drive share and enhance the storage capabilities of your server or PC. This mobile rack backplane lets you install four 2.5in SATA or SAS solid-state or hard disk drives into a single 5.25in bay and quickly hot swap them between systems. It's ideal for systems integrators and administrators who are looking for flexible management of their data storage.
Designed for durability and trouble-free use
The mobile rack backplane is engineered to protect your valuable data and provide reliable performance. The aluminum housing is designed for enhanced heat dissipation, while two 40mm fans improve air flow to minimize heat build-up and ensure optimum operating temperature.
The backplane can be mounted either vertically or horizontally, for error-free tray insertion and maximum compatibility with servers or desktop computers. You can lock the removable steel trays in place, providing an enhanced level of drive protection. The Non-Scratch SATA (NSS) connector provides a high 50,000+ insertion rating, your assurance of long-lasting performance of both the drives and the bay.
Convenient, interchangeable drive trays
Many fast-paced work environments require drives to be removed regularly. Hot swap between systems quickly, without shutting down, with the convenient backplane.
The included drive trays are interchangeable, working with both the 4-bay backplane and the single-bay backplane (SATSASBP125) so you can hot swap between systems for easy file access.
Compatible with a wide range of drives
Designed for versatile use, the backplane supports an extensive range of both SATA or SAS based HDDs and SSDs, from 5 to 15mm in height.
To maximize the performance of your drives, the mobile rack supports SAS II and SATA III performance for transfer speeds up to 6 Gbps when paired with a compatible controller. The backplane also works with your preferred RAID controller or Hyper Duo™ controller to produce a high-performance or redundant storage solution.
The SATSASBP425 backplane is backed by a StarTech.com 2-year warranty and free lifetime technical support.
- Systems integrators and administrators looking for flexible storage management
- Build your incremental or off-site storage back-up plan by attaching hot-swappable drives to your server or computer
- Fast-paced work environments where drives need to be replaced or removed regularly
The StarTech.com Advantage
- Supports a wide range of 2.5in SAS or SATA HDD/SSDs from 5-15 mm
- High-quality metal housing maximizes heat dissipation
- Two 40 mm fans help to ensure optimum operating temperature
- Maximize performance through SAS II and SATA III, with file transfer speeds of up to 6Gbps
Product Numbers
Ingram Austria
UPC Code
Technical Specifications
|Warranty Information
|2 Years
|Compatible Drive Types
|Drive Installation
|Drive Size
|Fan Bearing Type
|Sleeve Bearing
|2 - 40 mm
|Front Door Key Lock
|Number of 2.5 inch bays
|Number of Drives
|Supported Drive Height(s)
|Hot Swap Capability
|Insertion Rating
|Max Drive Capacity
|Tested with hard drives up to 2TB at 7200 RPM
|Maximum Data Transfer Rate
|6 Gbps
|Noise Level
|20 dBA
|Port Multiplier
|Type and Rate
|SATA III (6 Gbps)
|Drive Connectors
|4 - SATA Data & Power Combo (7+15 pin) Receptacle
|Host Connectors
|4 - SATA (7 pin, Data) Receptacle
|Other Interface(s)
|1 - LP4 (4 pin; Large Drive Power) Female
|OS Compatibility
|OS independent; No software or drivers required
|Special Notes / Requirements
|Flammability rating: UL94 - V0
|LED Indicators
|4 - Drive power and activity LED
|1 - Fan activity
|Operating Temperature
|0°C to 55°C (23°F to 95°F)
|Storage Temperature
|-20°C to 55°C (-4°F to 131°F)
|Physical Characteristics
|Aluminum and Steel
|Max Drive Height
|15 mm [0.6 in]
|Product Height
|4.2 cm [1.7 in]
|Product Length
|15.2 cm [6 in]
|Product Width
|14.6 cm [5.7 in]
|Weight of Product
|760 g [26.8 oz]
|Packaging Information
|Package Height
|80 mm [3.1 in]
|Package Length
|21.6 cm [8.5 in]
|Package Width
|19.4 cm [7.6 in]
|Shipping (Package) Weight
|1 kg [2.3 lb]
|What's in the Box
|Included in Package
|1 - 4-bay SATA/SAS hard drive backplane
|2 - drive tray keys
|4 - 2.5" drive trays
|4 - 18" SATA data cables
|2 - SATA to Molex power adapters
|16 - drive mounting screws
|8 - backplane mounting screws
|1 - quick start guide
Related Products
2 Drive 2.5in Trayless Hot Swap SATA Mobile Rack Backplane
Easy, trayless removal and insertion of dual 2.5in SATA hard drives from single 3.5in bay
Removable 2.5" SATA HDD Enclosure/Backup System/Mobile Rack for 3.5/5.25" Bay
Turn a 2.5in SATA drive into a front bay mounted removable HDD backup solution
2.5in SATA Removable Hard Drive Bay for PC Expansion Slot
Use an available expansion card slot to install a hot swappable 2.5in hard drive
12in Latching SATA Cable
Latching SATA connectors, for securely fastened hard drive installations.
6in Latching SATA Cable
Secure latching SATA cable designed for new system boards and SATA hard drives
8in Latching SATA to SATA Cable - F/F
Secure latching SATA cable designed for new system boards and SATA hard drives
18in Latching SATA Cable
SATA hard drive cable, with latching SATA connectors, for securely fastened hard drive installations.
12in Latching Round SATA Cable
Connect latching SATA drives while helping to ensure optimal airflow throughout a desktop or server case
Mobile Rack Backplane for 2.5in SATA/SAS Drive
Easily connect and hot swap a SSD or HDD from a 3.5in bay
2.5" Hot Swap Hard Drive Tray
Exchange drives with ease with this extra drive tray for SATSASBP425 and SATSASBP125 series backplanes
4x SATA Power Splitter Adapter Cable
Add three extra SATA power outlets to your Power Supply
6in SATA Power Y Splitter Cable Adapter - M/F
Add an extra SATA power outlet to your Power Supply
6in Latching SATA Power Y Splitter Cable Adapter - M/F
Add an extra SATA power outlet to your PC Power Supply
12in SATA to LP4 Power Cable Adapter - F/M
Power an LP4 device from a SATA Power connection on your computer power supply
6in SATA to LP4 Power Cable Adapter - F/M
Connect an IDE hard drive to a Serial ATA power connector
LP4 to SATA Power Cable Adapter with Floppy Power
Power up to two 4-pin LP4hard drives or devices, and a floppy drive, from a single SATA power supply connector
SATA to LP4 Power Cable Adapter with 2 Additional LP4
Power up to 3 devices using a SATA power connector from the computer power supply
LP4 to 2x LP4 Power Y Splitter Cable M/F
Connect two LP4 peripherial devices (CD/DVD-ROM drives etc.) to a single LP4 connector
Product Support
Data Sheets
Frequently Asked Questions
Before You Buy
Although mobile racks can enable a Serial Attached SCSI (SAS) drive to connect using a standard Serial ATA (SATA) connector, the hard drive controller must be SAS compatible to properly support SAS drives. SAS controllers can work with SAS and SATA drives, but most SAS drives will only work with a SAS controller.
For further information about SAS and SATA interoperability, refer to the following FAQ: http://www.startech.com/faq/hard_drive_controllers_sas_drive_compatibility.
Copy Link
Was this information helpful? Yes No
When you troubleshoot issues with a hard drive rack, there are some quick tests that you can complete to rule out potential problems. You can test to make sure that the following components are working correctly and are not the source of the issue:
- SATA and SAS cables
- Hard drives
- Hard drive rack
To test your setup components, try the following:
- Use the cables, hard drives, and hard drive rack in another setup to see if the problem is with the components or the setup.
- Use a different cable, hard drive, and hard drive rack in your setup to see if the problem persists. Ideally, you should test a component that you know works in another setup.
When you test the hard drive and hard drive rack, it is recommended that you do the following:
- To check Disk Management, press the Windows key + R, type diskmgmt.msc, and press Enter. Check to see if your hard drive is listed.
- If the hard drive is listed with unallocated space, it needs to be formatted. Right-click unallocated and click New Simple Volume. Follow the on-screen instructions to complete the reformatting.
Note: Formatting a hard drive erases all of the data on it. Make sure that you back up all of your data before you reformat the hard drive.
- If the hard drive is listed as healthy but does not have a drive letter assigned to it, for example, C:, right-click healthy and click Change Drive Letter and Paths. Click Add, assign a drive letter, and click OK.
Note: A formatted hard drive will not show up in Computer or My Computer until it has a drive letter assigned to it.
Copy Link
Was this information helpful? Yes No
Compliance and Safety
Compliance Letters
Safety Measures
- If product has an exposed circuit board, do not touch the product under power.
- If Class 1 Laser Product. Laser radiation is present when the system is open.
- Wiring terminations should not be made with the product and/or electric lines under power.
- Product installation and/or mounting should be completed by a certified professional as per the local safety and building code guidelines.
- Cables (including power and charging cables) should be placed and routed to avoid creating electric, tripping or safety hazards.
* Product appearance and specifications are subject to change without notice.


text:
The couple were greeted by a lion dance troupe much to their amusement.
|The Strait Times Facebook
Kate received a posy from a little girl. Children warm to the Duchess so easily and it's great to see her interacting with them. Adorable photo.
|Rebecca English Twitter
The crowd await William and Kate's arrival.
|The Strait Times Twitter
The couple viewed cultural performances that showcased the three main cultures of Singapore: the Chinese, Malay and Indian communities.
|Photo used with kind permission of MEDIA-MODE.COM
Kate meeting children.
|Photo used with kind permission of MEDIA-MODE.COM
The royals visited the Rainbow Center next, a school and community centre for children with special needs.
The Strait Times Facebook
An adorable shot of Kate meeting a little boy at the Rainbow Center.
|The Strait Times Facebook
In 1992, Rainbow Center Singapore was established as a registered charity. The centre runs two special needs schools and two Early Intervention Programme centres at Rainbow Center. All the centre's programmes adopt a holistic developmental curriculum in the areas of language and communication skills, cognitive skills, social and emotional skills and adaptive daily skills. If you wish to support the center you can find all relevant information about donating here.
|Photo used with kind permission of MEDIA-MODE.COM
Kate met children in an art therapy class and William took part in a physical education class. The centre is celebrating its 20th anniversary this year, a very appropriate time for a royal visit. Kate also took part in an art class during the Canada tour and one of her patronages is The Art Room. As a History of Art graduate Kate is obviously passionate about art and is utilizing that in her role as a member of the royal family.
|Georgina Brewer Twitter
Royal fans were certainly enthusiastic to see the couple.
|Mark Stewart Twitter
Kate made a quick change into an outfit by Singaporean label RAOUL. The brand is helmed by Douglas and Odile Benjamin and began as a men's shirt label. It has evolved into a full collection of ready- to- wear for men and women including accessories and timepieces. Celebrities such as Helen Mirren and Elle MacPherson have been seen in RAOUL.
Kate wore the ivory Silk Print Pleated Skirt and the Tara Top. The print pieces retail for €279 and €206 respectively at Matches. I love the silk print and think it's a very pretty, floaty look. Essential given the humidity in Singapore and it's wonderful to see Kate supporting Asian fashion.
From the product description
'Work geometric prints on and off duty. A red and black cube -heart print is reminiscent of vintage 70s styling. Raoul puts a retro-cool slant on ladylike new-season dressing'.
A look at the back of the pieces.
Kate wore her favourite LK Bennett Sledge Pumps.
|LK Bennett
The Duchess accessorized with her Annoushka baroque pearl earrings.
The Duke and Duchess will attend a reception at Eden Hall later. See you then :)
|Photo used with kind permission of MEDIA-MODE.COM


text:
Ena, in answer to your question, Butterfly Girl was scheduled to be released over a year ago, but shortly before the manuscript went on to pre-publishing final stages, I asked my editor for a "quick read." I had drafted a new novel, and I wondered if Butterfly Girl could use a few tweaks, based on things I had learned while writing that new novel. That quick read surprised me--after a long break from reading the manuscript, I realized that what I wanted to accomplish would require more than a few tweaks. There were several elements that could be improved, but it would require a slow, methodical approach--in other words, a lot more time. I revised several scenes and sent my editor Before and After examples, to see if she'd allow me to revise the entire novel. She liked what I did--it kept the content intact but smoothed and tightened the writing . . . and in the process it pushed us back a full year, since I was working on two novels simultaneously. So, now the timing is slightly crunched with launching Butterfly Girl, a picture book release next month, and a new novel on its way out for submission this very week! But now I am in the position of having nothing in the works and wondering how I ever wrote anything at all! It feels like a mystery to me each time until a new idea grabs me and I remember I can do this, I think (I hope!)
0 Members and 1 Guest are viewing this topic.
Page created in 0.178 seconds with 51 queries.


text:
Shoppers: Find the lowest prices on Bedroom Sets shopping online with Sortprice.com price comparison.
Browse Popular Bedroom Sets and save money on selections like Bedroom Set Bedroom Sets, Contemporary Bedroom Sets and Platform Bed Bedroom Sets.
Retailers: Join thousands of top retailers already live and list your products to gain exposure, traffic and sales. Free Facebook store now included with any of our programs.


text:
Melissa Corry here from Happy Quilting. I'm so excited to be back here at the Moda Bake Shop and share this wonderful Valentines Day Quilt. XOXO is big in our family!! I shared a little bit of the story behind it in my last Valentine's tutorial for MBS. This quilt is a twist on the basic lattice quilt adding the O's to create the perfect quilt for you and your Valentine to snuggle up in. Hope you enjoy!!
1 Honey Honey Jelly Roll
3 1/4 Yards of Bella Solid White
3/4 Yard for Binding
5 Yards for Backing
Choose 36 jelly roll strips from your bundle. (I set aside 4 of the double prints) Lay them out as follow, keeping them folded in half. You can cut about 6 rows at a time. Using the lines on your mat as a guide, cut a sliver off the end to remove the fold. Then cut a 2 1/2″ x 10 1/2″ rectangle, a 2 1/2″ x 6 1/2″ rectangle, and a 2 1/2″ x 2 1/2″ square. Place the remaining bit in scrap. You will have 2 of each cut. Repeat with all 36 strips to have a total of (72) 2 1/2″ x 10 1/2″ rectangles, (72) 2 1/2″ x 6 1/2″ rectangles, and (72) 2 1/2″ x 2 1/2″ squares.
Now from your white yardage cut the following.
We'll start by making the O blocks. Gather a 6 1/2″ square and (2) 6 1/2″ print strips and lay out as shown below. Place the strips onto the square with right sides together. Sew a 1/4″ along the edges, aligning as you sew. Press towards the center square. Repeat to make 18 center units total. (Chain stitching saves time)
Lay (2) top and bottom units and one center unit out as follows.
Lay the top and bottom units onto the center with right sides together. Nest the seams and pin. Sew a 1/4″ seam along the pinned edge. Press. And now, you just have to add the sashing border. Gather (2) 10 1/2″ white strips and (2) 12 1/2″ print strips and layout as shown. Lay the top and bottom border onto the O with right sides together. Sew a 1/4″ seam aligning as you go and press. Repeat for the two side borders.
And the O Block is finished measuring 12 1/2″ x 12 1/2″. Repeat the last 2 sub-steps to make a total of 18 O Blocks.
Gather a 10 1/2″ strip and 2 subcut white triangles and lay them out as shown. Place the right hand square onto the strip with right sides together centering the triangle. Sew a 1/4″ seam along the edge, aligning as you go. Open and finger press the triangle. Lay the second triangle onto the left hand side of the strip with right sides together and lining the tips of the triangles up. Sew a 1/4″ seam along the edge, aligning as you go. Press towards the triangles. Repeat to make 72 lattice units. (Chain stitching will save lots of time here 🙂
Lay the X and O blocks alternating into 6 rows of 6. Play with the layout until you get a look that is please to the eye. I tried to separate the red and navy units most as they tend to pop. Once you have a please layout you are ready to sew the blocks into row.
I find the easiest way to do this is to stack each row and place some sort of marker on the first block indicating what row it is. This way you don't lose the layout you just did.
Then just start sewing the blocks together, one block adding to the next, and the next until you have sewn all 6 in the row. Then just repeat for all 6 rows. I do not pin my blocks when sewing them into row as there are no seams to line up. I just align as I go.
Press your seams in the rows towards the O blocks. This will allow you to nest the seam and avoids bulk around the X corners.
Sewing the rows together is just like creating them. Lay the first row onto the second with right sides together. Nest the seams and pin them and then along the rest of the edge. Sew a 1/4″ seam along the pinned edge. Press open. Then repeat adding the third row to the now sewn together first and second row and so on.
And before you know it, you have a beautiful Hugs before Kisses Quilt Top!!
One adorable Hugs before Kisses quilt measuring 72″ x 72″ perfect for snuggling under.
I hope you enjoyed and if you make your own Hugs Before Kisses quilt I would love to see it. You can add it to my Inspired by Happy Quilting Flickr group here 🙂
Have a Happy Quilting Day!!
Melissa Corry


text:
Watch our latest worship service videos
Audio podcasts of the message are available at the bottom of the page.
Sermon Audio
Current – August 2018
- Aug 9, 2020The Choice Of Love
- Aug 5, 2020The Incorruptible Word Did It All
- Aug 2, 2020Blessings And Benefits Of The New Birth
- Aug 2, 2020Jesus Shares His Life Principals
- Jul 26, 2020God's Great Love
- Jul 26, 2020Jesus Returns To Jerusalem
- Jul 22, 2020Living With Joy And Courage Before A Watching World
- Jul 22, 2020Missionary To Puerto Rico
- Jul 22, 2020God Knows Where We Are
- Jul 22, 2020Light Actions
August 2018 and older
God's Perspective; The Truth Of God's Word ()Pearcy, Kevin, July 19, 2017
Part of the RBC Missions Conference 2017 series, preached at a Special event service
Powered by Sermon Browser
Follow our social media outreach and stay connected with the latest updates, newsletters and ministry events.
The information on this site is the property of Rodgers Baptist Church. No broadcasting or duplication of any sermons or content allowed without permission from Rodgers Baptist Church..
801 W. Buckingham Road
Garland, TX 75040
Email: firstname.lastname@example.com


text:
Who decides which languages we ship? First of all, localizers themselves nominate their specific changeset for a given release. The nominated changeset gets reviewed by Mozilla's localization team and shows up in a Web dashboard that lists the changesets needed for each language. The Release Coordinator reviews this before sending the "go to build" email. On the day of a release, we retrieve this list of changesets and we repackage them accordingly.
Besides localization repackages we also generate partner repackages. These are customized builds for various partners we have who want to customize the experience for their customers. The main type of changes are custom bookmarks, custom homepage and custom search engines but many other things can be changed. These customized builds are generated for the latest Firefox release and not for betas.
For users to be sure that the copy of Firefox they have downloaded is indeed the unmodified build from Mozilla, we apply a few different types of digital signatures to the builds.
The first type of signing is for our Windows builds. We use a Microsoft Authenticode (signcode) signing key to sign all our .exe and .dll files. Windows can use these signatures to verify that the application comes from a trusted source. We also sign the Firefox installer executable with the Authenticode key.
Next we use GPG to generate a set of MD5 and SHA1 checksums for all the builds on all platforms, and generate detached GPG signatures for the checksum files as well as all the builds and installers. These signatures are used by mirrors and other community members to validate their downloads.
For security purposes, we sign on a dedicated signing machine that is blocked off via firewall and VPN from outside connections. Our keyphrases, passwords, and keystores are passed among release engineers only in secure channels, often in person, to minimize the risk of exposure as much as possible.
Figure 5: Signing Firefox installers.
Until recently, this signing process involved a release engineer working on a dedicated server (the "signing master") for almost an hour manually downloading builds, signing them, and uploading them back to ftp.mozilla.org before the automation could continue. Once signing on the master was completed and all files were uploaded, a log file of all the signing activities was uploaded to the release candidates directory on ftp.mozilla.org. The appearance of this log file on ftp.mozilla.org signified the end of human signing work and from that point, dependent builders watching for that log file could resume automation. Recently, we've added an additional wrapper of automation around the signing steps. Now the release engineer opens a Cygwin shell on the signing master and sets up a few environment variables pertaining to the release, like
TAG, and
RELEASE_CONFIG, that help the script find the right directories on ftp.mozilla.org and know when all the deliverables for a release have been downloaded so that the signing can start. After checking out the most recent production version of our signing tools, the release engineer simply runs
make autosign. The release engineer then enters two passphrases, one for
gpg and one for
signcode. Once these passphrases are automatically verified by the
make scripts, the automation starts a download loop that watches for uploaded builds and repacks from the release automation and downloads them as they become available. Once all items have been downloaded, the automation begins signing immediately, without human intervention.
Not needing a human to sign is important for two reasons. First, it reduces the risk of human error. Second, it allows signing to proceed during non-work hours, without needing a release engineer awake at a computer at the time.
All deliverables have an
MD5SUM and
SHA1SUM generated for them, and those hash values are written to files of the same name. These files will be uploaded back to the release-candidates directory as well as synced into the final location of the release on ftp.mozilla.org once it is live, so that anyone who downloads a Firefox installer from one of our mirrors can ensure they got the correct object. When all signed bits are available and verified they are uploaded back to ftp.mozilla.org along with the signing log file, which the automation is waiting for to proceed.
Our next planned round of improvements to the signing process will create a tool that allows us to sign bits at the time of build/repack. This work requires creating a signing server application that can receive requests to sign files from the release build machines. It will also require a signing client tool which would contact the signing server, authenticate itself as a machine trusted to request signing, upload the files to be signed, wait for the build to be signed, download the signed bits, and then include them as part of the packaged build. Once these enhancements are in production, we can discontinue our current all-at-once signing process, as well as our all-at-once generate-updates process (more on this below). We expect this work to trim a few hours off our current end-to-end times for a release.
Updates are created so users can update to the latest version of Firefox quickly and easily using our built-in updater, without having to download and run a standalone installer. From the user's perspective, the downloading of the update package happens quietly in the background. Only after the update files are downloaded, and ready to be applied, will Firefox prompt the user with the option to apply the update and restart.
The problem is, we generate a lot of updates. For a series of releases on a product line, we generate updates from all supported previous releases in the series to the new latest release for that product line. For Firefox
LATEST, that means generating updates for every platform, every locale, and every installer from Firefox
… in both complete and partial forms. We do all this for several different product lines at a time.
Our update generation automation modifies the update configuration files of each release's build off a branch to maintain our canonical list of what version numbers, platforms, and localizations need to have updates created to offer users this newest release. We offer updates as "snippets". As you can see in the example below, this snippet is simply an XML pointer file hosted on our AUS (Application Update Service) that informs the user's Firefox browser where the complete and/or partial .mar (Mozilla Archive) files are hosted.
Major Updates vs. Minor Updates
As you can see in Listing One, update snippets have a type attribute which can be either major or minor. Minor updates keep people updated to the latest version available in their release train; for example, it would update all 3.6.* release users to the latest 3.6 release, all rapid-release beta users to the latest beta, all nightly users to the latest nightly build, etc. Most of the time, updates are minor and don't require any user interaction other than a confirmation to apply the update and restart the browser.
Listing One: Sample update snippet.
<updates> <update type="minor" version="7.0.1" extensionVersion="7.0.1" buildID="20110928134238" detailsURL="https://www.mozilla.com/en-US/firefox/7.0.1/releasenotes/"> <patch type="complete" URL="http://download.mozilla.org/?product=firefox-7.0.1-complete&os=osx&lang=en-US&force=1" hashFunction="SHA512" hashValue="7ecdbc110468b9b4627299794d793874436353dc36c80151550b08830f9d8c5afd7940c51df9270d54e11fd99806f41368c0f88721fa17e01ea959144f473f9d" size="28680122"/> <patch type="partial" URL="http://download.mozilla.org/?product=firefox-7.0.1-partial-6.0.2&os=osx&lang=en-US&force=1" hashFunction="SHA512" hashValue="e9bb49bee862c7a8000de6508d006edf29778b5dbede4deaf3cfa05c22521fc775da126f5057621960d327615b5186b27d75a378b00981394716e93fc5cca11a" size="10469801"/> </update> </updates>
Major updates are used when we need to advertise to our users that the latest and greatest release is available, prompting them that "A new version of Firefox is available, would you like to update?" and displaying a billboard showcasing the leading features in the new release. Our new rapid-release system means we no longer need to do as many major updates; we'll be able to stop generating major updates once the 3.6.* release train is no longer supported.
Complete Updates vs. Partial Updates
At build time we generate "complete update" .mar files which contain all the files for the new release, compressed with bz2 and then archived into a .mar file. Both complete and partial updates are downloaded automatically through the update channel to which a user's Firefox is registered. We have different update channels (that is, release users look for updates on release channel, beta users look on beta channel, etc.) so that we can serve updates to, for example, release users at a different time than we serve updates to beta users.
Partial update .mar files are created by comparing the complete .mar for the old release with the complete .mar for the new release to create a "partial-update" .mar file containing the binary diff of any changed files, and a manifest file. As you can see in the sample snippet in Lis, this results in a much smaller file size for partial updates. This is very important for users with slower or dial-up Internet connections.
In older versions of our update automation the generation of partial updates for all locales and platforms could take six to seven hours for one release, as the complete .mar files were downloaded, diffed, and packaged into a partial-update .mar file. Eventually it was discovered that even across platforms, many component changes were identical, therefore many diffs could be reused. With a script that cached the hash for each part of the diff, our partial update creation time was brought down to approximately 40 minutes.
After the snippets are uploaded and are hosted on AUS, an update verification step is run to a test downloading the snippets and then run the updater with the downloaded .mar file to confirm that the updates apply correctly.
Generation of partial-update .mar files, as well as all the update snippets, is currently done after signing is complete. We do this because generation of the partial updates must be done between signed files of the two releases, and therefore generation of the snippets must wait until the signed builds are available. Once we're able to integrate signing into the build process, we can generate partial updates immediately after completing a build or repack. Together with improvements to our AUS software, this means that once we're finished builds and repacks we would be able to push immediately to mirrors. This effectively parallelizes the creation of all the updates, trimming several hours from our total time.
Pushing to Internal Mirrors and QA
Verifying that the release process is producing the expected deliverables is key. This is accomplished by QA's verification and sign offs process.


text:
NEW YORK, N.Y. - Benny Blanco, who has co-written and co-produced hits like Katy Perry's "Teenage Dream" and Maroon 5's "Moves Like Jagger," is getting a songwriting honour.
The Songwriters Hall of Fame announced Tuesday that the 25-year-old will receive the Hal David Starlight Award at its annual gala on June 13. Past recipients include Taylor Swift and Alicia Keys.
Blanco has been behind a slew of hits in the last few years, including Rihanna's "Diamonds" and Ke$ha's "TiK ToK." He's also worked with Bruno Mars and Nicki Minaj, and often collaborates with mega-hitmaker Dr. Luke, who is his mentor.
Tony Hatch, Mick Jones and Lou Gramm, Holly Knight, JD Souther, Steven Tyler and Joe Perry will be inducted into the hall of fame at the Marriott Marquis Hotel in New York.