Turn Your $60 Router into a User-Friendly Super-Router with Tomato sans titre Khan Academy @codemonkeyism @codemonkeyism » b43 b43/b43legacy is the name of the new driver for wireless b/g cards with Broadcom chipsets. It performs quite well in terms of monitoring and injection, although it has no support for the 802.11a wireless band. b43 is a mac80211 driver, so it requires at least Aircrack-ng 1.0-rc1. Is My Card Supported? A fairly up-to-date list is kept here. At the time of writing this article, chipsets with the following PCI IDs are supported: To determine the PCI ID of your wireless device under linux, enter: lspci -vnn | grep 14e4 Supported VIDs table If your device ID is NOT listed here, it means it is not supported by aircrack-ng at this time. Some chips are covered by both the “b43” and “wl” driver. Installing the drivers 2.6.24 kernels and newer don't need any patches applied to the driver itself for monitor mode and packet injection. Important note: If you install or update your b43 driver via compat-wireless, you have to know that the b43/ssb modules are part of your distribution's initramfs image. Or:
From Sand to Processor or How a CPU is made - Intel It is hard to believe that a modern processor (CPU) is the most complex product in the world. What is so complex in this piece of metal? In this article I will try to explain how a modern processer (CPU) is made from the sand. Processor Manufacturing It takes about $ 5 billion dollars to build a processor manufacturing factory. This factory approximately has 4 years to return the invested funds in its technology, before it will start making the profit. The process of processor manufacturing looks like this: the special equipment is used to grow a mono-crystal of cylindrical shape from the molten silicon. Some Chemistry Lessons Let us take a closer look at the whole process of manufacturing. Originally, it is taken in the form of SiO2 sand, which is in arc furnaces (at the temperature about 1800 ° C) reduced by coke: SiO2 + 2C = Si + 2CO This silicon is called a "technical" and has a purity of 98-99.9%. 3SiCl4 + 2H2 + Si ↔ 4SiHCl3 Photolithography Photo Resist Application More Exposing Etching
memo Apps for Homeschooling - App Reviews, App News, and the Best Apps for Your Homeschool styleguide - Style guides for Google-originated open-source projects Every major open-source project has its own style guide: a set of conventions (sometimes arbitrary) about how to write code for that project. It is much easier to understand a large codebase when all the code in it is in a consistent style. “Style” covers a lot of ground, from “use camelCase for variable names” to “never use global variables” to “never use exceptions.” This project holds the style guidelines we use for Google code. If you are modifying a project that originated at Google, you may be pointed to this page to see the style guides that apply to that project. Our C++ Style Guide, Objective-C Style Guide, Java Style Guide, Python Style Guide, Shell Style Guide, HTML/CSS Style Guide, JavaScript Style Guide, AngularJS Style Guide, Common Lisp Style Guide, and Vimscript Style Guide are now available. If your project requires that you create a new XML document format, our XML Document Format Style Guide may be helpful.
Errors with data-sources in WebLogic Description: I got some errors when i launch WebLogic. Errors due to some data sources. Can you suggest me a solution ? Thanks. Log: <7 août 2014 23 h 28 WEST><Error><Deployer><BEA-149205><Failed to initialize the application "LocalSvcTblDataSource" due to error weblogic.application.ModuleException: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. weblogic.application.ModuleException: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:338) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100) at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:172) at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:167) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
The future of computers - Part 1: Multicore and the Memory Wall Editor’s note: In this first of three features, processor expert Russell Fish provides his take on the future of computers, and multicore processing in particular. Contentious and opinionated, Fish pulls no punches – Intel fans should not read this – but provides a good introduction to the problems and hyperbole surrounding multicore, before offering his take on the way forward. After nearly 40 years wandering in the silicon wilderness searching for the promised land of CPU performance and power, computer deity, Berkeley’s Dr. David Patterson handed down his famous “Three Walls.”1 They were not etched in stone, but they may as well have been. These three immovable impediments defined the end times of increased computing performance. “Power Wall + Memory Wall + ILP Wall = Brick Wall” Taken together, they mean that computers will stop getting faster. The industry was stunned when Intel cancelled not one but two premier processor designs in May of 2004. Answer: Fair question. 2. 4. 6. 11.