Hi everybody. Today I'm going to present you the result of my master thesis that I did in Paris in Pente-en-Sauvain a long, long time ago, back in 2012, but also a few preliminary results from my PhD, which I'm doing at the University of Western Australia within a big project called Kimberley Vision, which is focused on rock art and occupation sites within the North East Kimberley. So quite luckily I have been able to work on the Kimberley region for my master, which is a region from the tropical north of Australia, which is basically twice the size of England in terms of size, like you can see Australia is a huge continent, and this region is particularly interesting as it is maybe one of the key entry points of population on this continent during the Pleistocene, but it also shows an interesting pattern of change in lithics industries during the Olocyne. The change and the dichotomy between Pleistocene industries and Olocyne industries I've been quite, I've been quite long history in Australia, like for a long time the first typologist, the first lithics analyst, have defined two big industries. So Pleistocene industries were where called the core tools crapper, sorry I'm a bit stressed, like yeah core tool industries and later on during the Olocyne they used to define a small tool tradition and these two phases used to be applied through the continent and yeah with no regional variation whatsoever. Until in the 60s and 70s, Muldani, one of the Austrian archaeologists, said that reanalyze artefacts from Cunich's caves and said that Australian lithic industries were too variable and maybe during traditional typology weren't a good solution to grasp the variation between place and archaeological sites and so on. It's what this assertion was back up with Haydn, observation of population from the Western desert, who managed observing aborigines napping and using stone tools, he managed to see that blank morphology wasn't a criterion for selection for making tools of the use, so they can either be used grow or retouched. Nowadays, a famous Australian lithic analyst like Peter Krzysztof-Lachsens acknowledged more for quantification of reduction in lithics analysis, so basically it's more like they're more attached to Bériel's ecology and evolutionary archaeology. In their work, they gather morphological, morphometric data and try to quantify the amount of reduction that the tools have undergone. They also acknowledged to look at more original scales, because Australia is a big continent and so looking at more reduced regional, sorry I'm really stressed, I'm so sorry, they acknowledged to look at regional scale analysis, so Krzysztof-Lachsens did for Vadaman country, which is a situated in Arnhemland on the map, not so far from the Kimberley, 200 kilometers away from the site I'm looking at now from APHD. So what Krzysztof-Lachsens found through his analysis using North American kind of approach is that stone tool types were probably the same part of the continuum, so points from blades were made in points which were like reducing first unifacially and then bifacially to attain, like you can see on the right hand of the screen, completely bifacially flaked points. It's a simple scraper, so morphology scraper are due to the amount of reduction that undergone, like following Debal's theory. This model is quite a success and for him this reduction continuum and the existence of point technology in Arnhemland is linked to the need of easy replaceable toolkits, which help to cope with climatic instability in this region and make people, people that are ready to end toolkits with them wherever they go, went down control like scarce resources. This model has also been a success as it was also applied in the region when I'm working now, so in the Southwest, Kimberley, Tim Maloney found that some, the pattern of, sorry, for the points, but happier in the Kimberley just like in Arnhemland, but later 5,000 years before, are made on standard as blank and are then part of a reduction continuum. So first of all you have the standard as blank, then it's reduced into an unifacient point and then a bifacial point. The only type of tool, which were, not in this continuum, is the backtrack effect, which follows its own reduction path. And this industry of the Middle Eastern industries are also thought to be realized to cope with more climatic instability. But what Maloney found as well is that 10, 1,000 years before people were making other new type of tool, bifascially flaking tool, but finished with pressure flaking and for him and to mark more as well work in the Samaria, these two were maybe more linked to social connection and social, what he said is that the specific technique of pressure flaking implied to have social transmission of this knapping practice and so on. So it's the first time where we go out of your own ecological model to cope with climatic instability to something more social. And we can say that the data from the master, my master and and from my PhD turn to tell a kind of different story. Outside of lethix you've got raw cards, which for the older scene and middle of the scene must be 6,000 VP seems to show more regional viable and so on. And sorry, that was my presentation. Sorry. Yeah, so I'm going to present to my master data. So sorry. Yeah, I didn't have my thing so far. It was just like Oh, no, you got my. Okay. And I just I saw no desk thing. Yeah. So which one? Yeah. So I was, oh, you mean that's a slightly was this one. And that's okay. And we are not going to split on the desk. No, well, I'm going to manage without even if I'm stressed. I'm sorry. There we go. Okay, let's go. Okay, so so we said that we've got this new introduction of points, 5000 years, which wears on solidized blank and, and just part the point out of from the same reduction continuum. And then in 1000 years, you've got both new pressure leading points, which are maybe linked to social relationship and social learning, at least implied by the techniques to have like social bond and language. So on to transmit this, these techniques in the Northwest Kimberley is the continuum of points is not applicable. So for my master thesis, I work on Kononara rock shelter, which is in the right and left end side of the map. And for my PhD, I'm working on few sites that are not all there, but you can see different sites type. I'm looking at bits include like rock shelter, because archaeology in Australia have a lot of biases because we're looking more at caves and so on. So we start to, at least for this region to open, open, open earth sites. And also gathering quarries, a quarry workshop, the Viva Chet Reduction quarry, by the way. So I'm going to present you the Kononara results. So Kononara is an old excavation made by Charlie Dorch in the seventies. Stratigraphy, it's a bit hard to read there because of the charcoal and the fire just like rebates the place, make the sedimentary dark with no layers. So basically the only solution is to excavate by like arbitrary excuse. So as the first, when I came to the collection, the first surface layer are disturbed. So we decided with my research director at the time to just forget the older layer that starting 135 centimeter, which is below a charcoal of of 3000 BP, which have been calibrated by Tim Maloney at 34341 BP. So what I found looking at the stone tools over there is that in contrary to what Maloney have got in the south west Kimberley, points are not always made on on standard ice so we have a composite part of the technology over there like little cores, which produce like standardized type of points, which are basically not for touch. And like points any fascial and fascial could be realized on simple flake struck from rebel cobbles. Like the number six, the butt of the number six on the right hand side of the plate show the typical cortical shoulder of the of the cobble, which I've been from the flake. And in other words, so yeah, sorry. And also very two type of fascial point, I think it's important to stress like very probably be fascial is struck point, retouch points, but there's also like be fascial shaping there, which is far older on the one we saw in the south west Kimberley. So from the older sequences, we can see different be fascial finding flakes in the older seconds like big like the first stage of the facial finding like the two big one on the left and also the finishing the be fascial finding later flakes, as well as preforms and broken points. And therefore, if I found through the sequence, so that's mean that be fascial finding, but without pressure flaking were happening far before what 1000 VP. And the diagnostic and so that's mean that those kind of point are not part of this continuum, at least. And so it's interesting to see that in comparison with one of the first site has to be from my PhD, there may be more viability than previous work in the Kimberley safe ethics. So sorry. So one of the first sites of my PhD is umary. So catch your zero thirty seven in the 68. This site is a long sequence, a first three first square were established by the Kimberley vision team back in 2016. And from this first big sequence, we've got two dates one basically the middle, which is really recent 1000 VP, while we have a bottom date of 12,000, nearly 13,000 there. So far, I have studied the stratigraphical unit one, two, three and four. And they gave a really interesting result in term of variation in the thick industry for short term periods. For first of all, be fascial finding feet, feet in place are fine for the sequence with interesting pattern. Actually, the first layer is retrographical units. You find the fascial finning, finning flakes in two types of pro material, the silicep ison stone and the sedimentary rocks, which could be fine in the riverbed nearby the site. It's really local material. Sunstone is fine where everywhere around the open site. And we have a gradual change towards more charity materials in stratigraphical units three and four. And they are like virtually present in every layer of the site. But that's not all as a variation. There's also a change in we can see difference like we don't see in East Kimberley. So what we have found something interesting, which are not documented elsewhere in both sites in the Kimberley is that there is an existence of ledlets and small flag production in crystal boards, which starts a bit before in XU4 and change through the XU. This production, the core justifies for really thin flakes what we can find to be a retouch in points like in XU12 and as little parts of ledlets in XU11. And like I will characterize further the change within the industries in my PhD later. Sorry. But maybe to say a bit more about my research. So this was one of the open sites I've got to study. And I will try to compare later on there are different site type because like various different activity has some type type. Like going through the different assemblages that got so far.  While rock shatter seems to be sorry seems to be more differential finding as well. And we are like quarries where just like being used for differential reduction. So basically I would like to, comparing those sites I would like to see various like offering, with another methodology offering a qualitative view of what's happening in every site type to see and something different catchment of the place. See very cultural differences between the area. And yeah, sorry. Let's finish there. Sorry.


TEFL Portland, Oregon With its beautiful natural landscapes and forests, Oregon is considered one of the most beautiful states on the West Coast. Our modern and spacious TEFL International Center is located in a new building in Lloyd District right in the heart of Portland. It is also very close to restaurants and coffee shops, which is very convenient for all the students who decide to take our TEFL certification in this beautiful city. There are bus stops within easy reach of the school that can take you to many different places running both day and night. The school's facilities include everything you'll need in order to successfully complete your course, such as a wide range of teaching resources, free internet and parking, a tutoring center, private study rooms, a computer lab and quiet study rooms. We are also very proud of our media and DVD library. Our school also organizes free conversation groups that will help you improve your English skills. When you're teaching practice, we'll have you teaching both small and large classrooms. This way, you'll have the chance to experience both teaching environments before going out into the real world of teaching. While taking our TEFL program at our well equipped school, you will not only have the best learning experience, but also the opportunity to explore all that this beautiful city has to offer.


This is TFNN, the Tiger Financial News Network News Update. Good morning everyone, Basel Chapman here on this 10 o'clock Tiger Financial News Network Market Update. We're looking on this 24th Monday, the 24th of April, the Dow is up 48 to 32,856. So I spent some time all of last week discussing how this very strong nine-period exponential moving average holding over the 14 gives tremendous internal strength to whatever price you're following. In this case, it's the Dow that we made a peak D at 34,082, the fourth highest peak in the Chapman methodology on the 14th of April. On the 14th of February, we hit 34,331 and peak D. So now we've made a peak D under that. And that just suggests that we're having a little time out here, breather, that until we start to trade under $33,500, very short-term, I'll say $33,500, we could go sideways, there's even enough strength to bounce, but I think the upside is capped at this particular point in the $34,000 to $34,100 area in the Dow. In the weekly chart, we'll talk about that as the week progresses, but we're in that inside track repellent zone. So there's a lot of resistance looking at the S&P at 41,37, the 41,63 high, 1,2,3,4,5 sessions ago, market sessions that is, is there as a peak F. I haven't put in a down arrow yet. It's still holding right above the nine-period moving average, which is above the 14. That gives a time, it says there's a process that has to go on. If you're about to collapse, and I'd say $4,088,000, $4,085,000, some around that area, we crack that, and now you're going to be going down for a little bit, looking at the QQQ, it's the NDX100, also trying to write it's only up 13 ticks at $3,6172, made a double top twice in April, it's gone to the $321.63, and then $321, 42 areas of the $321 area is very strong resistance. And it's in basically almost like a rectangle formation, so there is support IWM, Russell 2,078.04 up 48 cents, holding quite nicely. Gold had a big move down earlier in the week last week, and then it kind of stalled, and then again on Friday it was down, today it's down too. So it's having a digestive phase, the dollar isn't acting all that well, it's down and bonds are down, obviously what are bonds doing right now? It's all up 1930 seconds, but in the trading range. I'll be back for the take a technician's hour, I have a webinar coming up, but we


All right, I'll try to talk about my name is Pat Lachov. I am here at the Linux kernel driver model and SysFS, which are both important features in the 2.6 kernel. And I'm going to talk about how it's making a little better one subsystem at a time and how it sets a great fit. If anybody has any questions, we're starting a little link about 10 hours. And I know there's talks starting at five, which will probably be well attended. I'm going to try and make it within that time. And if anybody has any questions, feel free to raise your hand and to come talk to me fast or anybody. Feel free to raise your hand and tell me that as well. So moving on, I'm going to try and quickly get to the talk slowly. So I'm going to talk about kernel driver model and SysFS. And I'm going to answer these basic questions, which are probably all pertinent ones. What is driver model? What is SysFS? Why do I care? How do they work together? And can you prove it? And I'm going to explain each one of those and of course I can prove it and prove to you that you should care about them very much. So first of all, what is driver model? The driver model is a collection of big structures and programming interfaces inside of kernel. It's really quite simple. It just describes common five-strips objects. I know a lot of you probably are familiar with object-reading programming. And if any of you have done kernel work which we've heard all of you know that there's a strong version of object-reading programming because it's commonly known to people because of languages like C++ and Java. Well, there's a use for object-reading programming and I think that instead of that, that's one time that object orientation is in the programmer's mind, not in language or something like that. And so the driver model follows that very well. So we're trying to describe self-contained objects and things using C++ inside of kernel. So what driver model does is it tries to identify what some of these objects are that are common to a lot of different subsystems and it captures them into structures. It also consists of a set of libraries for subsystems to use that manipulate those objects. It's not for both of the vice-drivers at all. It's only for the subsystems to use. So that has a couple of factors. One is that it's completely transparent to the vice-drivers during the program, as well as some of the users. And it's also it also makes it very transparent on the subsystem level. So that's what he said. That's it. That's all of it. Most of you can think of a way to explain this. Most of you will never see it. You'll never experience it and you'll never have any problems with it. It will just work perfectly, of course. That's pretty much all there is to it. However, I traveled very far to come here so I'm going to say a few more things. First of all, some of the concepts of the driver model are in the data structures. And this is very core of it. There's four basic data structures. One extra one of them is core data structures and then two more are in the first row, which I'm not going to talk about. The four basic ones are the number one one instruct device. It presents a single license system. It has no hardware access whatsoever. It doesn't care about IOCORs. It doesn't care about memory addresses. It doesn't care about location on the bus. All it has is really simple actually. It's like a name, a bus ID, a parent corner, and a list of jobs. It's very simple. There are fields that pretty much don't have any devices in the package that can house a bus. No matter what bus it's on. It's a serial device or whatever it's a PCI network card that doesn't matter. It all has those common keys. The next one is a struct bus type. This is not a bus, like an instance of an PCI bus. It only describes a type of bus. So there's one per subject. There's one for the PCI subsystem. There's one for the USB subsystem. There's one for the serial subsystem. Et cetera. And all that does is it says that hey, this is a type of bus that's in the system. And it has basically two things. A list of devices and one for the drivers that are attached to that bus. And some lots of technical and some other things here. But for the most part of the time. The next one is a struct bus. And it's really called struct bus. It's a new product. It's just a piss-off C++ product. And the fact that it uses people. So it's called struct bus. It describes one functional bus. And there's one per subsystem. Like a working input. And like a bus type. It only has a list of devices that are attached to it and associated with it. And then of course, those structs that I strike. Which then exists one for each driving system. And there's a driver-specific bus and a ticker bus. They can have the e1000 driver. It's a number of drivers that controls Intel, PCI, Delta cards, and that's implemented on the support system. So they basically only have the list of devices that the driver supports. And these lists, everything that are listed here are contained in the core objects that are described by itself. So these objects and these structures are pretty much never used by the drivers themselves. They're only used by the subsystems and by the driver model core, which I'll explain in a second. So the interfaces that the driver model has are pretty much four basic things. Register and unregister, which are used when the device is discovered or an object is created. The subsystem will register the device with the core, which I'll insert into the list. So if you go back, we have this list of devices and drivers that the bus has. So when a bus finds the device, it will register with the driver core. It will then add it to the list of devices that the bus has. That's it. Well, why do the buses do this up? I'll explain that a little bit more in a second. But for the main reason is because the locks in the list are contained in the essential driver core objects. And so all the access to them is mediated through the very core itself, which uses the complexity of the subsystem itself and keeps all the common code in one place. So the other thing is to get input reference counting. We use a lot of reference counting in the driver core because it's scalable. It's much more scalable and much more efficient than using any types of locks. And also guarantees that we can be safe against devices or drivers coming away, like modules being loaded and unloaded and devices being plugged into the lock. And so by using reference counting, we're making sure that we're always accessing fresh data at the right time. Then we've got a stumble over that number. And we also have SysSFS operation, which is mediated through the driver core. And I'll talk about SysSFS in a moment. For the most part, just know that any time you want to access SysSFS through subsystems, the subsystems are actually calling it through the driver core. And then, of course, the driver finding that line. And so one device is discovered by a bus. It's registered with the core. When a driver is loaded in a module, it's registered and it's loaded through the subsystem. It's registered with the core. And then there's access watches to control and to immediate the association of the driver with the devices. Because different buses handle different winds. We like every bus that happens to handle it in the same way, but unfortunately that's not the case. So, talking a little more about the driver layer and the driver model is that it's a simplification layer. It's not an abstraction layer. In the kernel world, we don't like abstraction layers. Abstraction layers are bad. So remember that. We never tried to meet everything that everybody did. We only tried to take very the most common data elements in the structures that are shared or created in all the different subsystems and still them down to common objects. And essentially simplify the subsystems that you're using. We never wanted to create something that encapsulated every single subsystem in the entire kernel. Because that just doesn't make sense. Buses of jQuery, classes of jQuery. We wanted to find a common set of functionality that most people could use. So by doing so, we've been able to create a very gradual evolutionary system by taking common components out of the structures and then gradually converting subsystems to use these data structures and embedding them in the larger structures that the subsystems use. And so what this does, is by using statically allocated embedded data structures, we can convince the subsystems to adopt the driver model by simply inserting the data structure in the larger data structure, and then all of a sudden it's ready for the driver model. It's just like that. It's very simple. To convert any of these to the driver model, it took three lines of code. And it was bad. It just perfectly worked. And so that also lends to the transparency of the entire model. No one knows what's happening. No one needs to bother with it. It just works. The library functions that I mentioned before, the interfaces are healthy, because they're not replacements. They're not meant to replace PCI device register or PCI driver register. They're only meant to help the PCI subsystem in the job that it's doing by taking care of the list management and taking care of the locking and what not. It's just going to take away the codes and then instead of an augmented functionality it's not going to replace it. And it takes care of redundant features like listening and locking and what not. So the subsystems don't have to worry about it. They're making it themselves. So, now that you're all convinced that the driver model is a good thing, this is how it works in kernel. It makes the subsystem simple. It remixes the code size, which is obviously a good thing. It's one of the things that we've learned after many times of trial and error reset. We try interface, we try one that made it able to, made it possible to remove underlines of code. We knew that it would be kind of a right choice. It creates a mechanism for more consolidation and simplification. Some of the hardest choices to make in some of the hardest code right is the first step. We found that as soon as we started to implement patients in the driver model a lot of people came to us and said, wow, I've been wanting to do X for a long time and now that there's an actual subsystem that will take care of it, it's now just an actual interface infrastructure setup so you don't walk up. It makes a lot easier and you kind of live the way. The last of driver subsystems is the scale up and down. Some of the subsystems weren't able to handle dynamic device discovery or registration like serial devices, had a static allocated list that no one would ever need more than that many serial devices. Which is all well appeared, most people don't have many more serial devices but when it comes to washing and when it comes to devices that are disappearing, they can be too spent. By using I have all the list management and all the registration platforms were able to mediate the pain that was called and they were ready to write as well as being able to scale up if we have dynamic object objects. We have lists that grow and get raised, etc. It's also been able to use power management and top bugging and now you're saying that Linux has always had top bugging and power management almost. And they always worked relatively well we were able to do that What the driver model does is a much easier usage and much easier complication of power management than the hot bugging I'll talk about power management in a moment and maybe a little bit but yeah. Moving on Does that all make sense so far? Is that okay? Alright so Is that better? Alright Does that mean you buy new gear afterwards? So, what is SysFS? How many of you have heard of SysFS? SysFS is an imaginary file system based on RAM and VES it's in the kernel itself and the kernel is created by the kernel when the kernel starts up so it's very similar to PROC PROC system but it's based on RAM and VES PROC was written before the VFS when the VFS layer was written RAM and VES was written and it became the world's simplest file system is incredibly small and very simple and so SysFS is based upon VES and also thinks and manages all the VFS features and makes it very simple to use so what it does is that it exports kernel objects their attributes and their relationship between the different objects to user space that's pretty high level of view but it's way more in one moment and also for that living app review for example PROC PROC is totally in our case things in place randomly you can never find anything unless you happen to know where it is and when new things are added to it it's added wherever the driver offers or wherever the subsystem author wants it to SysFS is not like we impose restrictions that are implicit in the entire system that give it an organized hierarchical view of what's in the kernel so everything in SysFS will stay other things that PROC does not have some things in PROC are dynamically created but you're not supposed to do that the locking is really bad it's always been really bad and it's really unsafe to renew things from PROC once they've been created that's not so in SysFS we fix those problems we also make it easier to expose user accessible controls we try to impose restrictions of having one value per file note that they're ASCII and can only make it so they can be right on the command line using cap and echo to read and write the values with some exceptions but those are special cases that don't even need to be discussed now make it really easy to expose these attributes and so instead of having code that people copy over and over and over that is 50 and 100 lines long to export one single value user space and thereby having the same bug in 200 different places like people have been PROC a couple of things at times we make it easy to use these three lines of code to export an attribute to user space and to read and write it as per example now of course there's other setup you have to do but just watch this movie here and then believe in what it said so a little history about SysFS it was created as DDFS driver file system to expose the device tree when the driver model is being created I worked at a company called Transmitter and when I started working on working on the driver model and I created this device tree and I made it to debug it and so I walked into this guy's office that I worked with and I said hey this is what I've done and I wanted to debug it so I was thinking of using PROC and he said PROC is correct I don't use PROC and he didn't actually say that he said it in a much harsher way which is not family safe but nonetheless he encouraged me to write in fossils from an important DFS which he had just written and I said wow okay I've never written fossils before but sounds easy to know and I went ahead and did it and it was very simple so as the driver model proved we added more arguments to the driver model the driver model started adding new devices then we soon added buses and drivers and classes to represent all these different arguments that we found and I wanted to expose those through the files of them so I changed the name to something a little more user friendly for actual tests and that's about the time we got an upgraded kernel and I had interfaces to sell the best to add all these new arguments buses, drivers, and classes and in doing so I had to extend the interface a bit so that there are certain specific calls then to SysFS to add new different arguments it didn't scale very well and soon other subsystems wanted to start using SysFS and the driver model like the block subsystem wanted to use it to boot the system with the primary device and they wanted to publish our device which I thought was really bad so what we did is we created smart payout and changed the name to SysFS to make it even more generic much to the chagrin and much to the dislike of many people and sorry about that so I'll just talk about Gavix for a moment because it's very, very nasty and it can be affected very quickly so Gavix are simple objects they're distilled from common fields in the driver model so I mentioned before that the driver model objects have very common attributes and fields that are common different objects throughout in the very subsystems so every device has a name has a plus ID, has a parent has a list of children no matter where it is so buses have a name and they have a list of children and they have a parent and so the classes and so the questioners so we took those and we put in this really simple small object called payout and what that does is it provides you a very simple set of management and functionality that the subsystems can use and so what this does most of this is not important for the sake of this discussion but just to explain each of the best directories relates to one payout everything is written behind the scenes by the driver so it's immediately transparent the driver subsystems don't even see the payout they don't question only the driver and each of the best directories created when the caretaker is registered so it happens automatically so the PCS subsystem will have to pass discovery devices ill register devices with the driver the driver forward will then register the payout with the caretaker subsystem now when you're doing that all of the location information you know where the devices are you know who the parents and you know who their siblings are so you register them and you register that with the process and then all of a sudden you have this directory you pick for free and you know exactly where everything is so now that your eyes are all basically I'll give you one second one second sorry so family directories files are actually out of the address from devices or any other object in the subsystem those are regular text files that are represented in the files siblings are relationships between payouts so it makes it very easy you have a start device not to the caretaker driver the device who the driver is the driver who includes what devices they control and so you use assembly to rig and process them to visually expose that relationship because it's already there in the kernel and so you cannot so why should you care first of all you might already be using how many people are using two subsets so you're already using a bit of a kernel since 2.5.1 December 2001 system s is integrated mounted by all of the contemporary distro I know it's done by SUSE9 too because that's what this is Fedora, Gen2 and I don't know about the other distros not this one but I'm not really a problem where they're at other utilities I've started to use it SUSE9 CPU frequency scaling used it at some point although I think that's being replaced by some other utilities all device tools are now limited through SUSE9 like request pieces and this kind of work to use and power management needs it by hierarchy in order to properly shut down the system and suspend it or do all the devices in order when you're suspending to S3 or S4 to suspend it now now that you're all completely confused and I'll show you what it looks like because I know that you're all curious so what do we have here light upon is that better alright so as you can see this is SUSE9.2 not too less than SUSE9.2 distribution or to this and the others which is what I happen to be using and at CFF we have as you can see the SUSE9 it's actually mounted by the kernel on boot during the internet test stage and so it's not mounted automatically it's already there so what we have in the top level tree is all the major subsystems that are represented in SUSE9 we have the block layer we have the buses, the classes the device tree, the firmware the firmware the firmware interface all the modules that are loaded the module interface which includes all the modules that are loaded in the system and the power management interface so just to show you an example of some other people that are using SUSE9.2 you can see if you look at the module directory these are all the modules that are loaded on my system so whenever module is loaded into the kernel so if we look into the devices directory we have the top level devices in the system and the only one that we have to care about for now is the PCI PCI 00000 which is the root PCI in my system so if we look at that these are all the PCI devices at least the one starting with four zeros of the colon and you can roughly see the hierarchy of the tree it's only a laptop so it's not a very interesting PCI tree there's about a dozen or so devices you can see some of the devices like 0000 zeros all the way across to the top that is the I guess that's the word that is the north bridge that's the very core device this next one is the PCI ATT bridge and the device directory of that is my ATT video card and over here we have what you can't necessarily tell right now these are the USP devices that are in the system and some other audio devices that went on so in the bus directory we have all the bus drivers that are in my system IDE, PCI, etc etc etc so remember back to the very beginning when I was talking about the different device model objects the bus type is one of them and these are all the start bus types in the direction of the system they have so if you look at SysBus PCI devices these are all the devices that the PCI bus has found and discovered on the system now all the devices are actually registered in the device tree which I showed you just a second ago and so what is registered here is all the assemblies that point to the locations in the device tree since there's no need to actually replicate the directory tree we just create a assemblies in this directory that points back to this location in the device hierarchy so what this does is it needs to apply the listing because all the devices have a unique name or unique identifier within the PCI tree and it points back to its unique location and if you look in the driver's directory we have a list of all the drivers that are registered with the PCI services as you can see there's a lot just in case you happen to have those devices on your system and they all use directories in the street so the only ones that we really care about for now are going to be the UHC app USB control for the driver so if we look in there we see three semblies three devices have been registered with the UHC device because there's three USB controllers and so each one of them gives the semblies two is the directory location back to the location in the device hierarchy that the device is located at and so if we look any more complete view of the USB tree which is the USB bus type and hands actually four controllers and this is then both UHCI and EHCI we see all of the USB hub devices and then a shadow device that is created in the scene we have the hub driver and the USB driver which are this is just an internal driver within the USB core that is registered and all the devices that are bound to each one of those each one of those drivers and of course the semblies point back to the location in the device hierarchy that the devices are located at and that's all it makes sense so far alright, much better response than the last one so as you can see there's also a few drivers that are not being used by the USB subsystem and so this is where the full part is this is the digital camera that's your father from thank you first of all, let's see everyone smile and wait hey so we take a picture turn it off this is what it looks like now, so we take the device it's a flash reader with a USB port and we plug it in and we see that some new devices have appeared so first of all, we have a USB device here which was not in the previous one and that is the device that was discovered by the USB subsystem here so that bound back to a device in the device tree it's discovered that it's a USB storage device so now that it's discovered by that device it also knows that it's a storage device which was with the USB storage driver by doing so, it creates a sim link in the USB storage directory back to the location of the device in the last hierarchy so if we look at the USB subsystem since USB storage devices are accumulated with the USB subsystem for some unknown reason we now have two devices that have appeared and it's actually just to show you that I'm not clicking this so now the device is here I've unplugged the device and so now I've put the device back in and excuse me for a minute and we see that there are new devices there that have now gotten new devices that need to be prevented because of the increments in every kind of device and the number of decrements and personas on the block so now that we have new devices in the system so let's try this so let's see where do you find more information there is the driver model which is in in Linux and it's all contained in the driver base the core driver model is about 2,000 lines and it has removed hundreds of lines from there is some other stuff in there that has been added on to the driver subject for the driver core so it's now a total of about 5,000 lines so the best is in those in those files and that's about 1,500 lines and the cab resource and I would recommend the first one for casual reading and the other two since the best is okay, the cab report gets a little air it's not your average for even more tradition there is an excellent book that was just published it just came out two weeks ago Linux collection of drivers by a rally table and the other building is actually selling this book it's an excellent book it covers the 2,600 2,610 it includes a chapter on the driver model and also has hesitated all of the rest of the information from the previous edition of the book a lot of the book is actually based on the LWM.net driver reporting series by John Corbett which is an excellent series that explains many aspects of the driver model changes as well as the other changes throughout the car model and so that's it we're going to replace them with us oh sorry is this the best going to replace them with us or is it the last step last step so yes, this is the best design for you going to replace that, the answer is no it was never designed to do that we never intended to do that because the MFS and the ATM like that is not the longer the kernel at all it belongs to the average base so what Sys-the-Fest is enabled is exported all of the information that's needed to set up all of the device entries through to user space and now there's a new program called QDAV that uses the information and how plug-in can be structured in the kernel to populate the directory dynamically and all of the I think both Fedora and Sys-the-Fest have been using it for some time and so you can actually have it evenly dynamically created that file system without having any device entries that exists all of the code yes so the question is what are you possible to have only Sys-the-Fest has become the facto standard for ATM-Sys-the-Fest so it's now a new location in your hierarchy that you'd need or you've probably already seen I don't know if it's an actual standard yet but it just happens to work so the question is will there only be a slash-sys and not a slash-proc no proc has its place proc has its use now it has a very small use that's it ever since a long time ago people decided that it would be really handy really useful to export other things about the kernel other information about the kernel to users-based and so like I mentioned one of the slides sometimes the hardest to take is the first step so once somebody has already done that they latch on to something else that people have done and overload it and use it and that's what's happening with proc is that people have attached on to the back of the proc they insist controls and everything else which don't belong there they belong in some of their transport mechanism proc has a limit to export and process ideas and all the information is just able to defend and so that's why you see some of the scaling problems and the locking problems that are going on so ideally what would happen is that a lot of the things that are except for the proc will be moved over to system s and then proc would stay for exporting and process information so not quite, we wouldn't just have a slash set so we have both of all the information that's in the proc so any other questions yes, I'm sorry yes and then we'll work so the question is the statement is that these crynex porting says the best of the NFS and it didn't work and my response is that patches are going to fix that okay I've never had a need to because I don't use NFS and so I've never encountered a problem and as Tom dictates I don't have the time to fix all these people I'm sorry it doesn't work I'd love to see it fixed yes to suspend different parts of the registry it just hasn't been done correctly and so we can suspend the entire tree but we haven't figured out where to go so you suspend this part of the tree so we've had issues with managed patches in the past but it's nothing necessary it's just technical issues that we have with the patches sometimes what's best for the users isn't always best in the terminal so we have a hard time implementing all the features that are really important to people useful because they don't live up to the standards that could follow any other questions? yes right so is it desirable to suspend a device even though it's now a driver account to it yes because there are some devices that have default state programs and other devices like for instance courageous devices that will never have the driver account that have supported free information like what buses are being on them and whatnot that needs to be retained so there's been a number of sufficient proposals in the past years some of them have been acceptable none of them have been implemented such as implementing a default driver for bridges or default drivers for all devices that are in the class or being able to implement or attach multiple drivers to a single device so that you always have the default driver found to be a device that will handle suspend and resume while not necessarily supporting the functionality of the device like networking or video that's something that just hasn't been we haven't had the chance to do yet any other questions alright thank you


First spot is Little Mad. It's actually a new American restaurant, but with a Korean soul because the chef is Korean American. How come you wanted to make a tasting menu instead of just letting people order whatever they want? Like, what's the goal behind that? So, a tasting menu will kind of... We gave a direction of what these guys should be eating in what order. Earlier in the game, when we first opened the restaurant, we were on a la carte menu and people were just like ordering noodles, mid-course, ordering hot apps, first course, and it was kind of like all over the place. So now with the tasting menu, we start with snacks at a table. We change the snacks daily, so tomorrow you'll come in and you'll try all new snacks, except one, which is our signature Punggopang. The experience is here, it's only $95 and I think that what I love about Little Mad's tasting menu is that you actually can choose which item you want. First four snacks, and then you choose one of each, and that becomes your whole experience.


TfNN headline news update, here's Tom O'Brien. Welcome folks, Steve Rhodes filling in here for Tom O'Brien for the 9 a.m. update. Right now we've got Dow equity futures. They're trading up 112 points, 26267 is the print S&P futures up 17, NASDAQ futures up 48, Russell 2000 up about 15 points, that's 1% to the upside. Starting the day off nicely, we've got gold up 60 pennies, light sweet crude is flat, silver is flat out there right now. Let's take a look at the markets, get a feel for what they are doing out here. Take a talk about strength out here. One of the tools that I like to use, it's a indicator. Think of the market as the tool at the bottom of the screen. It's one of the roads momentum indicator signals out here. It's kind of the EKG for the market. But when you are a runner, when you are sprinting versus, let's say you're running a marathon out here, your EKG is going to look a lot different. And right now the sprint is on inside the ESMini. Each of these little red boxes that you see on your screen inside the ESMini show that in the EKG, in the sine wave, it never got down to the bottom, this little bottom line out here, that's in the 20 level. And what you can see, we've only had one instance since the low back on December 24th, where price was able to push down to that lower threshold of Stevie's EKG system. The most recent signal that we got out here was just a few days ago. On April Fool's Day, this ain't no fool showing you that the continued strength exists inside of the ESMini. If we change over and take a look at the take a look at the NQ, you're going to see the same type of pattern out here. You didn't need me to tell you a very strong bullish market. You know what that means? Don't be short of very strong bullish market out there. Now let's take just a few moments here. Let's go take a look at gold, gold formed a brand new market profile out here. This says this 1291, 1290, is really key, key level that price must hold out here. If you take a look what's going on inside the treasury, the 30 year treasury, right now today pulling back and trading below 147.22, a key level. A close below that 147.03 is the price target. Thanks so much for being here, folks. Stay tuned. Larry Pesavento up next. Have a great Wednesday. Take care.


The Lagos State Police Command has arrested more suspects in connection with the murder of the chief executive officer of Super TV Usufo Ataga. Commissioner of Police Hakim Odumosu said this during a parade of some suspects at the command headquarters in Ikeja on Wednesday, without giving details. Ataga, whose wife and children reside in Abuja, was first reported missing by concerned friends and family after all efforts to reach him proved abortive. Later, officers of the Lagos State Police Command found Ataga's lifeless buddy in a flat in Leiki, Fizwan, Lagos with multiple wounds on June 16.


In what aspects of tonight's game do you feel like the game was lost for you guys as a group? It is NBA. If you dig a hole down 20 to anybody early, it's going to be hard to climb back out. So give them credit.  Have a great unbelievable shooting night. And I think a lot of that can be attributed to us kind of giving them a couple easy looks early in the game. They're NBA players, they're good players, get their confidence going and feel good about themselves the rest of the night. So it makes the rim look a lot bigger and give them credit. You guys shot 10 for 37 from three point range. I know you can only speak for you, but this fatigue factor and kind of off nights like this. Those are great looks. It's basketball. It's how it works sometimes. Sometimes they go in. Sometimes they don't. We're riding with all those looks that we got tonight. We were in the game. I mean, for as well as they shot two, we were only down five throughout until they blew it up, went on that run. But we were right there for a majority of the game and they made that little run at the end. Just came down to getting stops and we couldn't do that. They're making everything. So that's all it really is.


Now, the Northern Yields coalition, through a B in collaboration with movement for transparent governance, have called on Nigerian Yields to vote a presidential candidate that will salvage the economic and educational systems of the country. The coalition organized a lecture in Kaduna, titled, Yields Led Pathway to Social and Political Change, Faith and Service in Contemporary Northern Nigeria. The aim of the lecture was to awaken the Yields political consciousness. The last to be correspondent, Abila Darafai's report, is presented from our studios. Yields from the 19 Northern states meet in Arawahouse, Kaduna, their desire to change the narrative of politics and the common elections. They say Yields should vote for any candidate without ethnic and religious bias. Speaking the Northern coordinator of the group, Jamilu Abdulaziz Sufoo, say Yields will make their choice based on integrity, competence and ability to solve problems. Ninety-four percent of Nigeria lost competence in the way that they present their institutions that are ruling this country. So if that will show you that, this time around it's not about tribalism, it's not about sentiment, it's not about religious affiliations, it's about competency. So we are going to look. We are looking at a candidate that can bring a desired change that will change the situations of the economy. What happens? Why do we have excess amounts of knocking on the tree in the north? Because the economy of the country is bad. Also the vice chairman of the Northern coalition, Zuberi Muhammad, says over time politicians have taken Yields for granted. He said the situation can only be improved with the emergence of political leadership that can guarantee the future. When you desire change, it will come with a list of how you want to make the change. Before we used to be between the devil and the deep blue sea, between APC and PDP. You don't have other options than to either vote for PDP or APC or you climb a fence and sit on it. God has provided us a platform, options with a driver that has proven integrity. Some of the participants reiterated their support for Peter Albee. They say they are ready to vote competent leadership that have the interest of the public. The look of things that we have seen so far, previous administrations, the youth were not so enthusiastic about getting their PDP because we already know the way things will turn out. You vote, your vote doesn't count, but as it stands now, the youth have woken up and the future that we have been promised right from primary school has come and so we are ready to take it. I see from the turnout of those that are going for their PDCs, you see the numbers of youth, they are mostly youth, so we are tired of all these old people. They also complained about the shutdown of tertiary institutions for several months. The payback to an adamant government is to vote for a leader that can stop the further collapse of Nigeria's educational system. We have been suffering a lot, there are a lot of propaganda, this party will come and tell us this in the end of the day, there is nothing to present, there is nothing tangible, consider what is going on now. ASU has been on strike for over five months now, nothing has been said tangible. The federal government is not even willing to sit and liars with them. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


Oh, I don't believe it. That's from the next postcode. That one. Brilliant from Steve Luton. Drove into trouble, chipped it out. In severe winds from left to right, he judged it perfectly. OK, a chance to par five-thirteen for Chika Rangapap. Deal with the length of the green hat to scuttle that one through the fringe as well. What a shot for Chika Rangapap. Andrew Dope, the Australian, started with a four-bat. Here he is second to the 424-yard opening hole. And an eagle-two, the perfect start for Andrew Dope. Trying to extend his lead at the top of the international series, automatic. This is a four-iron on the 230-yard par three-four. Oh, well, look at that. He carried it exactly 230 yards. Straight in, didn't even bounce. It's a hole-in-one, but an eagle-three. This is a future for Max. Oh, this looks very good for Andrew Dope. Looks good. This looks very good. He's holed it. Would you believe it, Matt? This was his seven-iron from 201 yards on the most difficult hole on the golf course. It doesn't get much better than that. An eagle-two from a young tie.


Welcome to The Journey. Today we're going to talk about what is an elevator pitch and why you need one. I'm joined by my co-host, Sam, and we're going to break down. First off, what is an elevator pitch? So an elevator pitch is a really short and sweet statement about your products, services, things that you offer that solve some type of pain point. You know what he mentioned that? I immediately think of when we were out for some wine last night and that musician came up to our table and that's essentially what he did, right? He was nice. He said hello, but then he went into a quick, short and sweet elevator pitch. He did. And it's so important that you just let people know really not only what you do, but why you do it. You know, people, as Simon Sinek once said, they don't buy what you do. They buy why you do it. People want to get on board with what you believe. They're, you know, interested in a really good story. And that's what the gentleman did. You know, he was able to tell us what he did and why he was doing it. And it really caused us all to be really interested in it. Totally. I think about all the chamber events that I go to just within my role at GoDaddy Social. And networking events can be a balance of fun and also a little bit of a stress because you have to be so on all the time. But the stories that stood out to me were the entrepreneurs or the business owners that really had a lot of passion and a story to what they do and why they do it. And that to me, that wasn't, I didn't even think elevator pitch. I just thought, I want to know more about you. Keep talking, which often is not the case. You're like, okay, next. Yeah. You wanted to make sure it's just conversational, just like you're just talking to a new acquaintance or really you want to think about it this way, talking to a friend. You know, you don't try to sell or pitch a friend.  Absolutely. It also reminds me, my dad, I don't know if I told you, my dad moved from Key West to Indiana when I was only about six months old. And one of the things he did is on the side, side hustle, he opened up a cafe. And what his story was that I think connected with a lot of people was he opened up this cafe to bring Key West to a small town in Indiana. I was born in Key West. He named it MS Cafe. And almost every dollar went towards my college fund. And then he brought the Key West like Cuban sandwiches, Key Line Pie, everything to the cafe. So he had this really cool touching story that all started from the family that he began in Key West Florida and brought it up to the Northeast. And it just stuck. And it made people talk. It made him excited to be there. And that to me is that's an elevator pitch. All right, Sam. So obviously elevator pitch we're talking about face to face, word to mouth. But where else could I go and essentially pitch what I'm all about or why I'm doing what I'm doing? Cool question. So you can actually put it on your business card, really quick, short to the point statement that you can just hand to people. Also, you can put it on your website. You know, these are areas where people see you and you want to make sure, because we know people's attention spans are decreasing. So we want to make sure that we get to the point as quick as possible so that they know enough about you to become interested in you and know more. Yeah. And social media, right? Of course. I know I see you on a lot of Twitter handles. They have that little bio right there as well as on Instagram and Facebook. And it's a great way for you as a small business owner to sell what you're about with telling a story short and sweet. All right. So I got a pretty good idea. Not to put you on the spot, but I'm going to put you on the spot. Let's do an elevator pitch right now. Why not? All right. So Sam, what do you do? Who are you? Why do you do it? So I'm a military spouse. That's most important. That's who I am. You know, my wife, she is the center of all that I do. You'll hear more about that. But what I do is I speak oftentimes to those that are just really frustrated, you know, with the current job situation. I teach people how to turn from going for job security to career security, because job security, that's an oxymoronic statement. We know there's no such thing. It depends on so many things outside your control, the economy, the company, you know, the location, but career security, it's all about what you do. How well do you give your elevator pitch, tell people about your personal brand, who you are, things that, you know, make you unique and stand out. And also, more importantly, how well do you build your connections, your network? Emma, you've heard of the statement, it's not what you know, but it's who you know, right? Absolutely. I have two, but it's another addition to that. It's not what you know, or even who you know, but who knows you? That is a lot of great information. I'm jazzed on what you do, why you do it, but for the sake of an elevator pitch, I challenge you to put that in one to two sentences. Challenge accepted. So I'm Sam Pilar Jr., military spouse who speaks on how to create career security opposed to job security. All right, so now you want to know how to find your target audience. Totally. Now, rather than just looking at the demographic, you know, who these people are, their age, where they're located, I like to do psychographic. What's psychographic? Good thing you asked. So Seth Godin, I heard him say, thinking about what people believe, what are their thoughts? So going back to me and what I do, I'm talking about career security rather than job security. So I will be talking to people who are frustrated with the inefficiencies of today's job search. They're tired of just applying into the black hole of applications and just waiting for somebody to possibly reach back out to them. So it's a mindset. So I suggest look for those that are believing what you believe. I believe people should take control over their job security, really the career security, and they can do things that are going to set them up for future success.  All right, Sam. So thinking about what you do is making me really excited. And I just got to bring up one thing I'm super passionate about is my webinars. And a lot of people do webinars. You're like, yeah, cool. I'm listening to webinars all the time. People do them all over the world. But I really try to like differentiate my webinars with this whole model of laugh and learn, because I think it's more fun to learn things if you can laugh along the way. And that's perfect because that's what makes you different from everybody else and sets you apart. Are you saying that I'm unique? I'm saying that. Thanks, Sam. All right, Sam. So another thing I think about just staying on topic with webinars as my boss stresses this a lot, like what is your CTA called an action? What do you have to say about that when it comes to bringing the elevator pitch to the table or getting people excited about what you do? What's the hook? Well, that's important because people don't know what to do until you tell them, right? So if you're interested, let's set up a coffee date or let's call me at this number or instance, you know, if you want to find out more, go here. Tell them what you want to do so you can take it to the next step. If you don't say anything, they don't know what to do. Oh, okay. Now that you break it down that way, I guess there's one thing I do in the webinars. As I'm people are laughing and learning, sometimes they're getting so much information that they might be getting overwhelmed. So I really encourage them by, I guess, understanding them like, Hey, this was a ton of information. All these social media tips. Here's a link to have a social media consultation. Right. Is that like a good call to action? That's a perfect call to action. All right, Sam, you've given us a ton of great tips about elevator pitches, how to approach them, but what's kind of the final best practice, the bow on top of this present? So you want to make sure that your elevator pitch is between about 150 to 200 words, and you want to be able to deliver in about one to two minutes because remember that short attention span. All right, that's a wrap. You learned what an elevator pitch is and why you need one. So be sure to like this video, subscribe to our channel and ring that bell so you're not the last to know when the next video comes out. And make sure you comment below. Let us know what is your elevator pitch. Don't be shy. This is The Journey. See you later.