So, hi everyone, my clock says it's now 10 past 12. Welcome, I'm Kvost Lehmuis, and I want to tell you about how to report your Linux kernel back in case you ever encounter one. The thing is, reporting a Linux kernel back is kinda easy and kinda hard at the same time. If you look at the documentation of the Linux kernel, how to actually report, there's a short guide actually that's just three paragraphs and three or four more that's explained some general stuff and it all fits on one page. But if you look closely, you'll notice that if you print this whole document, it's 34 pages or depending on your layout. But in the end, it explains you all what you need to do in the reference section so you don't need to do that. And to get a fee out of it, reporting a Linux kernel back can be easy. This one with just a few paragraphs and a few local lines of the lock is actually totally fine. This one is as well. I'll explain later what they are, why they are totally fine, and you can look at them in more detail in the slides. The thing is, they are brief, nevertheless cover all the aspects to get developers interested. And that's the important part here because quite a few reports actually fail to do so and due to that don't even get a single reply and obviously the problem remains unfixed as well. That can easily happen as developers are not obliged to fix each and every issue. They're only obliged to fix a certain kind of problem. It's a bit like a community-built playground that's completely maintained by volunteers. The community as a whole has an interest to ensure that everything is and stays safe. It also doesn't want the kids to cry because anything they liked or loved breaks when somebody is changing something. And maintainers, the Linux kernel maintainers actually make sure to do both things. But just because you helped building this playground like maybe 10 years ago or last month or improved something, you're not obliged to further improve it because it was just a volunteering to help here. And fortunately the good thing is most developers actually really committed to help with all sorts of issues you have with the Linux kernel. But the thing is life is sometimes complicated and they can only do so if their time permits. And unfortunately most kernel developers have much on their plate already and are overloaded with work or issue reports. And then those not-that-good reports actually are often the first things that fall through the cracks and get ignored. And that's basically why you really want to submit a decent report to make sure it gets the developer interested and to make some look into the issue. And that's why I'll show you how to do that. The first section are actually mainly preparations on your side to make sure everything is fine. And actually 11 steps I broke this down to. The first one is actually to kick everybody out that it's not really up to the task. It sounds a bit harsh, but in the interest of the reporter because you have to ensure you have a kernel that's actually suitable for reporting bugs upstream because Linux kernel developers don't care about most kernels used in the wild and the bugs with it because many of those kernels contain enhancements that might contain the bug you face. They are added by your Linux distribution or the distributor you have around or maybe your admin or you did it yourself. Yeah, and that's why they enhance and considered modified, built from modified sources. For example, like those in Ubuntu. And that makes them unsuitable. And loading external developed modules is actually the same problem because in both cases it's simply not the kernel that Linux developers build. It's not vanilla as it's a term for that. So when you're using such a kernel you have to choose report the issue to your vendor or be willing to install a vanilla kernel yourself later. Later is important here because you don't need to do that right at the beginning. The thing is when you report the issue to your vendor, that's often a dead end because they are overwhelmed with reports as well and there's only so much people working on the distributions they can't take care of everything. That's why you often will have to be willing to install a vanilla kernel yourself later. And that's actually not that hard as it sounds. There are pre-ruled ones that are easy to install or compiling is also not that hard. We'll get into the details later. The second thing you should do is search for existing reports to join. That's just like with every other open source project you do check if somebody else reported the problem already because it can save you a lot of time and trouble and other people as well. If you don't report a bug in detail again that's already reported and tracked and maybe even worked on already. So how to do that? Then you can immediately join discussions on that. So how to do that? You just take your preferred internet website and search. For example, in this case Linux, I will Wi-Fi connection fails, VPA6, I made that up. And that often will lead you to some results already and there are many mailing lists where the Linux kernel developers are discussing things and where bugs are reported. That's all on law.kernel.org. There's a search function there and law.kernel.org slash all. And there you should also try to look for existing bugs. And when doing so with the search engine remember to vary your search terms a few times because sometimes people use different words or a different approach to things and that's something that's really important because it often helps you to find bugs you otherwise would have missed and can save you a lot of time. So don't neglect this and invest a few minutes or 10 or 20 in it. The next thing you should do is classify is it a severe problem or regression? Those are actually the bugs that the Linux kernel developers are obliged to fix and that's why they sometimes require special handling and that will become relevant later. A severe bug is actually something really, really bad so it's not that something doesn't work. It's really some security vulnerability or something causing data loss or a damage hardware crisis, something like that. And regression is actually when something breaks that when you're updating your kernel version that's as I said earlier you don't want things to break that people love and that's the same for the Linux kernel and that's why there's a special handling for that. The kernels have to be compiled with actually a similar configuration. If you want to know details about it there's a special configuration target to do that but actually described in more detail in the Linux kernel documentation about regressions if you have such a problem. Next thing you should do is what you always should do with open source projects is check if you're set up as actually causing your problem because that can help, can happen all the time and can save yourself and others a lot of time and trouble again because you won't have to report a bug that actually isn't one. The few things you should always do to make this work is always give a de-message output and look out for red and bold things that often tell you if something's wrong for example if a firmware file is missing or something like that you should also think if the hardware might break that happens or some other update like Bios, Grubb is causing the issue or some change in the BIOS setup is the reason why the kernel suddenly misbehaves and obviously you shouldn't overclock and use proven tools. Apart from that it actually depends a lot on the problem you face, what you need to do on the context of it. For example if you have a problem of a file system driver in the kernel then you should really check the file system over the FS check tools to see if there's something wrong and that confuses the kernel that often those tools can repair for things and then the kernel can reboot and things work. But as I said it depends on the issue what you need to check. Everything helps to find similar issues and what people suggest that you should check. So the fifth thing is create a fresh backup and put system repair tools at hand that's actually not strictly needed for reporting the kernel but when you're looking into the system and trying to figure out what's wrong or what kind of bug it is it's better to be prepared for emergencies during further tests. The sixth thing actually you should do is ensure you're not using any externally developed modules we also already covered this vanilla aspect because such bugs modify the kernel and they can cause areas in totally different areas of the kernel. That's why your NVIDIA graphics driver for example might break your Wi-Fi or your kernel memory management and it's really anything but obvious that it's the NVIDIA driver that's causing this can happen that's why these drivers need to be out ideally be removed from the system when you're reporting a Linux kernel bug and the important thing it's irrelevant if the driver is open source of property because it changes the kernel in ways that can cause all bugs and it's not vanilla anymore so it's not the thing the Linux kernel developers build and yeah then you are on your own. So hence disable solutions that build modules on the fly like DKMS and remove all modules they might have installed and that actually might mean that you have to uninstall the NVIDIA driver. Next thing you should do is ensure that the kernel is not tainted before the issue occurs and the tainted flag is set actually when something unwanted or really bad happens with the kernel and the kernel notices because when such a thing happens it can cause any other sorts of issues that might be follow-up errors and that's why the kernel marks itself as tainted then. To do that you can simply look it up in the proc file system and it should be a zero. If it isn't I'll refer to the documentation at this point because it gets too complicated here and explains what you then need to do and what this number actually means because this number is actually a bit filled and explains what kind of issues actually made the kernel tainted. But in the end most of the time it's a bad idea to report problems that are occurring with a tainted kernel and that's why you shouldn't do that but don't lose your mind over it now because you might need to install a different kernel later so maybe it's not tainted but it's good during debugging during preparation to check if such a problem is there because it can save you also time. One of the few exceptions is actually the first oops so a kind of problem the kernel detected and catch and could carry on afterwards but it might be not running perfectly well that's why it taints itself then if that's the problem then it's okay to report that bugs or any further follow up oops because they might be caused by this. Next thing is also in your own interest write down briefly how to reproduce the issue because that's actually the basis for your reports later and also interesting interest for your further experiments to know how you can reproduce it because if you're dealing with bug-related parts that quickly can get confusing and if you're doing this with a different kernel it really helps to have it stripped down and on a paper how to reproduce this. The next step is also in your own interest if in case it's a regression within a stable or kernel series say for example 5.15.4 to 5.15.5 that's a special case and in that case you can take a shortcut because those bugs are a little bit special the documentation in the Linux kernel that explains how to report bugs actually has those four steps you need to perform then explained it's basically also installing the latest kernel from that series and checking if the problem is there then you can simply report a quick mail which is known to check if the problem is known already because that's often the case and it saves you also some trouble. The tenth step is actually something that's a little bit annoying with Linux kernel you need to locate the driver or subsystem that seems to cause an issue you have to apply your best guess because there's no central place where Linux kernel bugs can be reported and that way when you apply your best guess you find the place where bugs need to be reported to later and also the place where you can look for existing reports the thing is most people assume that Buxilla kernel.org is the place where every kernel bug can be reported it also looks a bit like this but there's a hint there if you look closer at that it actually tells you that most of the time Buxilla is a bad idea to use because most of the Linux kernel developers don't use it there's a big risk that nobody will look in the reports that you file there but a few subsystems actually use it so where do you need to look instead? Most of the time you need to submit your report by email most of the time to the maintainers and a few public mailing lists in the CC and that's actually you find those addresses from them in the maintainers file for example this is for the buttoff s system an entry where you see hey I need to file a report this bug by mail to these three maintainers and this mailing list in CC ideally you also CC the Linux kernel mailing list but that's not that crucial and the thing is a few subsystems prefer to get reports via some bug tracker and sometimes that's actually Buxilla.kernel.org rarely some Gitforged for example the ACPI and Power Management people they prefer actually Buxilla.kernel.org and developers of various graphic drivers in the Linux kernel like those for AMD and Nvidia and Intel graphics actually prefer they have their own GitLab instance on freedestop.org and that's where you need to report the bug yeah and once you know where the bug later needs to be reported you should check the archives of that place for existing reports again that can save you a lot of trouble because you don't need to further analyze the problem if you can just join interest in existing discussions so that's it with the preparation and actually ends the first section of this talk which brings us to the second this is actually now you're going to test and report the problem so to do that you actually need to reproduce if the issue still happens with the latest kernel and then for that you really need to install a really fresh kernel ideally the main line so the main development branch to check if the problem is fixed already somebody has fixed it already you go to kernel.org and actually check which the current mainline version is here in this case it was 5.17RRC7 and then you really should use that version one that's a week older say you have RC6 might be okay but it's better to really try the freshest version and remember to ignore the big yellow field because that often is a bad idea because that's points to the latest stable kernel but you want mainline because every bug is fixed there first and you don't need to fear those too much they are pretty stable and you created that back up I told you earlier about it just in case something goes wrong but that rarely happens especially that late in the cycle but you really want to test that branch the main development branch because each and every bug fixed they are first and the thing is some bugs are fixed only there because sometimes it's simply too dangerous to back part a bug fix to older kernel series and that's why older kernel say 4.19, 5.4, 5.10 right now contain many bugs that nobody will ever fix they are known because it's simply too dangerous to fix them you just should use the latest version if you have such a bug there's an exception from the mainline rule if the kernel.org looks like this so if the stable version has a higher number then you should use that that actually happens right after release maybe for one week or two weeks sometimes and other times you better avoid stable but it's okay if you use the latest stable kernel most kernel developers will actually look into the issue so you can for example use it if the mainline doesn't work for some reason the long term kernels you see in the bottom left kernel those are really a bad thing to use for reporting bugs as I said they contain many bugs that are never fixed and it doesn't help anyone and the kernel developers that receive your report will think hey maybe that was already fixed half a year ago I don't have time to look into this right now and then ignore your report and that's something you don't want that's why you really want to look into the test with the latest kernel so how to actually install a really fresh kernel there are pretty well built vanilla kernels available for many distributions you have to just add a PPA or a copper or something where you can install the vanilla kernel actually there are also some big distributions that have them by default and the repositories are used them actually by default sometimes those are really only slightly patched then it might be okay to use them but it's always a little bit dangerous because some maintainers still ignore them so easily you actually compile the kernel yourself that actually might become necessary for debugging and testing later anyway and it might sound complicated but it's not that complicated with the make-targets make-old-config and local-mod-config you can easily create a config that doesn't compile that long and it's relatively easy to handle and yeah then you have with the usual make-targets like make-pcet-image and install and modules install you can install that kernel and you have quickly a fresh kernel on your system to test the thing is when you're doing that remember to easily deactivate these two config options at least if you're dealing with the stack trace because then you can later check which line of code the problem actually happens so next step is ensure the kernel doesn't taint itself because you have now a different kernel you need to check this again yes we already covered this but it's good to check it earlier already because then you know something is wrong on your system and not worth reporting that's why this is here a second time now you want to check if the problem actually still happens with the kernel in case it was already fixed that was quite easy and yeah if it is simply stick to this kernel or install the latest stable or long-term kernel to check if they are fixed there and if that's not the case so in case you want to use them and if it's not fixed there look up this reporting issues document I mentioned a few times already because it just explains you what you can do if you find a bug that's fixed in mainline but not an older series then you can check if maybe motivated developers to backport the bug fix but if that works out always depends on the problem because as I mentioned some fixes are simply too risky to backport yeah now we're getting closer to reporting the issue then so we're getting to the point where you should optimize the depiction of how to reproduce the issue to make it easy, really easy to grasp for others because I'm seeing a lot of bugs that are really complicated and where I have to read the text three times and to actually understand the problem or read five paragraphs that are completely strange to read that bears always the risk that developers will ignore your report in the end and so really try to find a more straight forward way to describe and reproduce the issue and also make sure the depiction is easy to understand for someone hearing about the issue for the first time because those are the people you want to arrest and if you're in a doubt ask somebody else to read your text before you submit it, that often helps and if you learn something in this process consider looking again for existing reports that can often help I mentioned the stuck traces already if you have one, consider decoding them that those are the kind of strange looking lines and numbers that sometimes show up when you have a panic or a warning or something so this stuff here as you can see most of the lines end with some random numbers and by decoding them you can actually check the line where the error actually occurred and how this code actually was called and that often helps the developers to find out what's wrong but if that's a little bit hard if you don't want to do it, you don't have to you can submit the bug first and then see if it's really needed but you maybe should really prepare for it and that's why I mentioned this config options earlier because they make sure that if you really have to do that check the documentation reporting issues that explains actually how to decode the issue both a self-compiled kernel and also with packages that contain debug info packages for example for RPA, Fedora and Susie that's possible so if you're dealing with regression there's some extra work here you need to find out narrowed down when it actually started actually as much as possible because when done probably it actually identifies the exact change that's causing the problem and gives you nearly guarantees of time we fix because then you know who has to take care of it and probably actually means bisection that's actually where you take the distance between two kernels and compile compile in the middle so if you have distance between if a problem shows up in 5.16 and wasn't present in 5.15 you compile these two first check if they are not showing if the earlier problem doesn't show up there and then you come jump to the middle between those two versions check if it's happening there if it's happening if it's not happening there you get closer to 5.15 and you can narrow down this way the exact change that's causing the problem with a lot of normally with current kernels it's about 15 or 16 steps to actually find the change that's causing the problem that sounds like it's taking days but with a modern system and a proper configuration that can sometimes be done in an hour or something and it's even possible to automate this with a script but if you don't want to do all that work feel free to just send a link in private report and just mentioning the brief version range because if somebody already looks into the issue and reported it and it might be bisected already and you can save yourself work quite some work be prepared that it might be needed because bisections regressions that are not bisected might remain unfixed if the problem can't be found it does sometimes now you're getting to compile and submit the report because we have everything done you should do everything prepared for that and everything is at hand so take the depiction how to reproduce and as a paragraph describing the environment kernel version, the tain starters the links distribution use the hardware used if relevant if there's a regression when they start and add or link all relevant details so if you logs or the coded stack trace what's needed is actually depending on the type of issue for example the dmessage and the config for the kernel is often relevant if you have something to do with kernel and LSPCI output often helps the slides are online so if you ever have to go through it you can check this out in detail and if you add or link to those logs is not really important linking is often the better thing because it keeps the mail relatively short and because big attachments sometimes take longer or get ignored or got into the spam folder so simply uploading them somewhere and linking is often the best choice on top of what you have now create a normal length paragraph that outlines the issue and the impact quickly to make sure everybody that reads your report can immediately get what it's about and to do that even better you should work out even better and descriptive title that says an important thing in just a few words because that's what most of the people that read your report later will read if you face one of those severe problems or regressions I mentioned take out the reporting issues document again because it has a section of what you need to do in that case to make sure it's getting fixed it's not that much but I won't go into the details make sure the end result has all the important details but it's easy to understand for outsiders as short as possible and submitted to the place where the maintenance file told you as I said this is perfectly fine this is reported to one from earlier just one paragraph that basically describes the problem the crucial line from the locks that shows where things went sideways and the question that the problem is known and some locks so that's totally fine and it's especially sent to the right people to and CC field that's the same just with regression regression mailing assistant CC there and it looks a little bit different look at the slides later if you are interested in the details here in the end the important thing is they were the reports came through the appropriate channel the description is easy to grasp and make it obvious if it's a bug or regression and that the kernel that was used was a fresh vanilla and untainted and now that the report is out your work is not done you need to keep the ball rolling somehow in one way or another because developers might have asked questions or might want to see to run some tests to narrow down the issue and such in prior try to answer it quickly not wait a week or two because then the developers might forget about it or they might go on holiday and then it actually gets ignored in the end so really react publicly in a timely manner here and keep in mind most developers are overloaded with work and they go on vacations too so if your report doesn't get a reply within two or three weeks it's likely dead and forgotten in that case it's totally fine to ask again hey did I something wrong or something but if that happens actually because sometimes that helps to get the thing running because the developer had a stress or was on vacation but if you do that also look at your own report again if it really was decent maybe that was the reason why it was ignored also new kernel versions were likely released in the meantime it might be a good idea to recheck that especially when there's an rc1 new rc1 from a new release is getting out because there are lots of changes go in and lots of fixes and if you don't get any help or if it's unsatisfying that sometimes happens because here as I said linux is done by volunteers then you need to try to help yourself maybe find others that have the same problem or something like that and team up with them the reporting issues document has something about it that's basically it that's actually to be told it's actually the most important aspects if you really want more details you want to read the reporting issues which is quite long a small book actually maybe that tries to cover all the questions you have the things I mentioned the different steps are also in similar form in the document and there's a reference section which explains each of those steps in more detail 19 steps so you might say is that crazy argument about that yes and no it's a little bit crazy but on the other hand it's not because most of those are quite normal for bug reporting and some of the steps are also just there in the interest of the reporter for example the first step to ensure you have a suitable or willing to install them make sure the people are aware what's coming up for them and to make sure they can decide at that point am I willing to do that and if I'm not then they can stop before investing an hour or two or maybe even more into this bug reporting process and backup tools is also similar in their own interest searching for existing bug reports is also quite normal for for software projects installing the latest mainline kernel is something that most other projects would like you to do as well for the kernel that's a little bit more crucial because it changes so fast so yes that's a little bit special but only a little but yeah that makes bug reporting sadly a little bit hard it would be easier if more distributions would chip vanilla kernel so people could easily test with them on their regular distro some steps are also twice in there like the tainted step and the regression step to check what's up with them so in the end it's just three things left that are really special that's locating the driver subsystem that's causing the issue like I said in the Baxillus not really supported and you need to check it up in a maintainer's file that's a bit odd but that's how it is these days I guess a lot of people would like some improvements on that front but nobody sat down to do that ensuring the kernel doesn't taint itself is also something special for the kernel but it's a special software that's close to the hardware that helps and checking the regression is also in your own interest because that gives you the guarantee that it's fixed so somewhat special but not that special after all so that brings me to the end let's sum things up kernel developers are only obliged to fix some issues that's really something you should keep in mind even if most developers actually want to fix all regressions they don't have to and if their time permits it sometimes can happen that your report gets ignored because sadly most of the developers are short on time and poorly reported reported issues are then the first to be ignored so that's why you want to submit a decent report and invest a few more minutes into that like I showed in this because it's in your interest to grab the developer's attention and interest in the problem and to make it easy for them to help you the kernel documentation has you covered there and the most important things are submit the report to the appropriate place as I said the maintainer file explains that ensure the kernel the report actually covers all the important aspects that are relevant for the developers but at the same time it's still easy and quickly to grasp for everyone that writes it that reads it and if an adopt better omitted detail that's often easier and also make it obvious if an issue is a regression or severe issue to make sure developers handle it with the appropriate priority it's also in your own interest to make sure the bug is quickly fixed if it's such a problem but in the end the most important actually is you really should test and report with the kernel that's really fresh, untainted and vanilla that's something most people actually do wrong and with that and you should also mention that in your report that you did so with that I'm finally at the end and are there any questions there are mics here in the front if you have any questions are there any questions from online don't be shy it's just lunch that's following we have time there's somebody coming I'm just curious how many bugs did you already report and how many of them got fixed I don't I reported a few bugs but it's not like I'm running to so many bugs the thing I know how to do is I'm tracking regressions for the Linux kernel and so basically what I said those problems that need to be fixed and that's why I read a lot of bugs and that's why I see how many people get it wrong and started writing this documentation but to get back to the real question I normally run this mainline RC and every third or fourth release there is one bug I report or want to report often somebody else did it already so yeah not that much but as I said those are development comments no okay if you're online you still can write questions somebody here that's looking for it so how many bugs did you have do you have kernel bugs often a few people shake hands yeah if nothing came in online I'd say that's it and thanks for listening enjoy your lunch and hey I'm really in time I still have 20 seconds left


I'm going to do something a little bit different. We're not going to have a toy review this weekend. So instead I thought I would do a drawing. Now I've been doing these drawings lately as thumbnail images for some of my older videos. My older videos didn't have any kind of branding or anything like that on the thumbnail images. It's basically just used a screen capture from within the video. I didn't really look too good so I've been trying to replace those. I thought it might be a good idea to have something that looks a little better for those videos. So I've been doing these drawings and then of course after I scanned them in and I used them for the thumbnail, I've been putting the drawings on eBay and much to my surprise you guys have snatched up everything that I've put on eBay and that is very flattering and very humbling that you guys would even be interested in something that I drew. So this time I'm going to do a drawing and I'm going to actually have the camera on so you can watch me through this process. For this drawing I will be doing storm shadow and I have the storm shadow action figure just off to the side here for reference so I can look at them. Then before I even got started when I had some idle time I did a couple quick sketches so I could figure out what pose I wanted to put storm shadow in. Now my first option was this one and this has storm shadow drawing his bow back. It has the arrow and I liked this. It's basically waist up and I liked this pose. I thought this was pretty good. I liked the energy of the bow string being pulled back but it wasn't quite right. It wasn't... I had a couple problems with it. First of all I do like the energy of the bow string being pulled back but I also like the tension of the crisscross lines in the chest and then like the tension between the body that sort of bowed back and the arms and the lines from the bow string and the arrow I felt interfered with that and actually broke up some of that tension so I tried something else. I tried a second sketch and this has storm shadow just after he has fired his bow so the arrow is not present and the bow string is straight up and down.  I think this is the pose that I'm going to go with so I'm going to have this sketch kind of over here off to the side too just so I can look at that for reference. Now let's take a look at the materials that I'll be using. I have a plain white 8.5 x 11 sheet of paper and I have a ballpoint pen and that's it. That's all I'm using. I have been drawing in pen lately which is a bit of a surprise. My medium has always been pencil ever since I was a kid but in the last year or so I have really been enjoying just drawing with pen. I just feel like the drawings come out with more energy when I draw with pen. I'm not really sure why that is but you know I've been enjoying it that way so I'm just going to kind of go with it. So this one will be in pen. Hopefully it'll also show up on camera better so you'll be able to see it better so that'll help with that as well. I will be drawing mostly on this side of the page and the reason I'm doing that is because I'm doing this for a thumbnail image and in the thumbnail the drawing will be on this side of the screen and on this side of the screen there will be text. Now obviously once I scan it in I can move the image around any way I want to but just by drawing on this side of the page just helps me keep in mind how I'm going to crop this when I'm done and put it on the thumbnail and it helps you just remember that I can't go too far over in this area because there's going to be text there and so I'm just doing that really for my benefit and just keeping that just to keep it in mind the graphic design purposes of this whole thing. So I'll try to confine my drawing mainly to this half of the page. With that let's get started and I'm going to start by always start with the head and I'll just find the where the head's going to be here sketch it in probably a little bit too low and make sure it's high enough on the page I'm doing this very lightly because this is not in pencil I can't erase it so I get an idea of the shape of the head needs to be a little bit more round he's going to be his head is going to be turned this direction so let's kind of get an idea where that's going to be a little bit of a jaw line there and let's see there's the center line right down his nose to his chin the high level the nose level and there's the mouth kind of I kind of like to just make the head a little more three-dimensional get an idea of the curves and the contours of it that'll help me later now let's see his neck here it's got his head's turned to the side so shoulders are going to be up here and just kind of sketching a line for where his shoulders are going to be shoulders are going to be slightly up more toward this side and then let's see his spine will be tilted back slightly I like what I liked in the preliminary sketches for these these lines here for the torso I felt that worked out pretty well and then arm will be foreshadowed hand to be right about there and the other one is going to be back here and has just let the bow or let the arrow go kind of still drawn back there like so a nice sharp elbow there all right fill all that in later as we go now let's see his chest just about like that his rib cage in his belt to be I don't know about in this area ish belt tied to the side there all right and I know I've got these lines are going to crisscross crosses chest he's got the bandolier across his chest here fairly wide an idea where that's going to be make sure it curves properly so it looks like it really is going across his chest in three dimensions and now there's a buckle on it right about there ish we'll put the details in that in later right about there we know he's got a cobra symbol right about there worked on that later just trying to get an idea of where everything is going to be now I had to a decision to make on whether I wanted storm shout out to be wearing his his sleeveless shirt as he appears in the comic book or if I wanted him to be more toy accurate and wear his short sleeve shirt and I believe I'm going to go with the short sleeve shirt but that was not an easy decision because I really do understand why they draw in the comic book they drew him with that that sleeveless shirt because it really does let you broaden the shoulders quite a bit and show off the the arm muscles and and that it really looks really cool I think it's probably a better look than the than the short sleeve on the figure but trying to be a little more figure accurate so I thought I would go with the short sleeves and just try to make it work make it look as good as I can so I've got I've got a curve on this arm here it's not perfectly straight and of course this arm is bent and then we've got it's gonna have a hand like a finger partially extended there and his other fingers are gonna grip around that bow like that and I apologize if you can't see this too well but I do have to go do this fairly lightly because I'm going to be filling this in with much darker lines once I figure out where everything belongs so let's figure out where the bow is gonna go let's see the bow is probably not gonna be perfect because normally if I were doing this for professional purposes I would use some tools to get this bow to look just right exactly as it should symmetrical and perfect but we're not not quite pros right now so I'm gonna do a nice it's gonna be fairly small bow but he the figure came with a pretty small bow let's see and I would actually kind of like to have a straight edge to do this bow string gonna be something somewhere right about right about right about there now there's a difficulty in drawing with a ballpoint pen that you borrow from the office and that is that these ballpoint pens aren't made to do this this is not their purpose in life so you're asking the tool to do something that it really isn't designed to do and it after a while it just wants to quit on you well that's okay these are just challenges and there's an old adage that it's the poor artist that blames his tools so we will not blame our tools for any poor outcome we always will make do with what we have so Bo will be right about their ish not perfect but not terrible okay let's see that hand is gonna should be a little bit larger because it's a little bit closer and this hand be a little bit smaller it's drawn back a bit more but he's got a couple fingers extended because he has just let the arrow go now hands are a challenge I used to be really good at drawing hands but having not drawn for a few years it's a skill that I've mostly forgotten I've had to reacquire and that is the biggest challenge that I've had in doing these drawings lately is re-learning how to draw hands just remembering exactly where the knuckles go and where the bones in the hands are remember trying to remember my hand anatomy which I learned many years ago but haven't used in many years so we basically got it now he has a knife tucked into his belt let's give him his knife it's something like this on the figure the knife doesn't come out the other side of the belt you only see the knife handle but try to make him a little bit more realistic and draw the whole knife stuck in his belt like so like so and the hand the handle on that knife is has a shape to it something like something like that can't be too large or it'll take up too much of our real estate here without I should do our belt our belt is right around here ish and let's see let's give him a throwing stars tucked into his belt right about there all right little tunic thing comes down here and like so like so like so all right come down here like so his neck all right so I basically figure out where everything's going to be it's now just sort of a matter of filling it in and trying to make it look halfway decent and so there we go let's let's start filling this in and making a storm shadow tend to start with the head and start with the eyes because it's kind of it kind of just that really decides the tone of the rest of the drawing eyebrows find the eye placement in the in the card art his eyes are kind of wide and maniacal looking and I don't know it's to be not quite that he won't be quite that wide-eyed he's gonna be looking off in this direction because that's where he is fired his arrow as we know storm shadow is the master archer whereas snake eyes was the better swordsman let's see now you know we're not gonna completely draw in the nose in the mouth I just want to know where they are and see his mask come up around here to expose his eyes everything else will be hidden let's see is that how I want it let's see and get the edge of that face a little bit better like so see where's that cheekbone maybe a hint of an ear under the mask but that mask is gonna conceal much so I don't want to have too many lines in that mask all right let's give him a little bit more menace in his face a little bit more anger and aggression give him some lines in his brow just so we know that he is in kill mode that will probably about do all right let's move on now this is cloth see into tunics goes about there ish a collarbone lines in his neck that heads just not exactly what I'm thinking we're gonna make it work gonna make it look as good as we can now let me go ahead and sketch in a bit of a cobra symbol here because we know where it'll be don't want it too big on the figure it's not too big it's a great one of the all-time great design logo designs I think that there ever was I mean it's so instantly recognizable done by Ron Rudat who is I mean he guy really knew what he was doing so be something like this and of course it comes down a little bit more to a point points at the end see here tell you ballpoint pens don't are not for drawing they are not I have thought about getting some better art tools which I used to have used to but I haven't done this in a long time but you know I've been I've been reluctant to you know get a whole bunch of tools drawing tables specialized pencils specialized pens paper and all that because you know I kind of want to maintain my amateur status you might say because I've been enjoying this but as soon as I start to throw all this investment into it then it's not really for fun anymore so I want to try to make sure that I keep it fun keep it at that level and as long as I keep enjoying it then I'll keep doing it okay all right we got an idea where the shoulders are the chests are the chests are the chest is rib cage the muscles on his back that we can see from the side we'll get a little few lines for the cloth here now we've got to start filling in the details basically everything that you will draw will be made up of one of three basic shapes either a cube a cylinder or a sphere and human body is made up of mostly spheres and cylinders but you can you can draw almost anything with those three basic shapes although I do sometimes like to break some parts of the body down into cubes especially male forms because they tend to look a little bit better sometimes if they're a little more angular got his wrist bands here the arms of course are basically cylinders and you can make a cylinder feel more solid and three-dimensional by using a few curved lines in the right places and at the right right angles okay all right starting to take shape here starting to look like storm shadow now there while I'm at this stage before I get too far along there are a couple things that I need to make sure that I add now on my sketch I had his backpack just you just barely see his backpack you don't see a lot of his backpack but we've got his arrows sticking out here over his shoulder and I've got his swords now on this sketch he has three swords he has a sword here a sword here and a sword here that's because my original idea was to have you know one sword up here and the other sword will be down here where he would draw it from under the arm but that line really I think interfered with the line on the underside of the arm so I ended up not liking that so I'm gonna go ahead and have the other sword also over the shoulder and hopefully that'll work all right so let's see let's just get an idea of where our arrows are gonna be you won't see much of the backpack because it'll be behind his back but we do need to make sure that storm shadow has his swords let's see here angle on that sword to be something like that all right it's mostly gonna be seeing the swords from a right angle so we'll have to try to make sure that those cylinders look solid and three-dimensional and I can already tell that my drawing that I'm doing here doesn't have quite the same energy level as my sketch and that just always is the case when you go from a sketch to a fully rendered drawing just lose some of the energy and that's something that maybe some other better artists have been able to learn how to manage but that's something that a problem that I have and I know that's a problem that some other artists also have so the swords will be there and we'll add some detail there we'll add some detail on the arrows as we go but I'm not gonna worry about that right now I'm just looking for the positioning the rest of his backpack let's see where would his backpack be I guess we might see a little bit of it over here but I don't I don't want to break up I want this line I don't want to add too much over here to break that up so yeah I don't think I like that at all I'm actually not gonna finish filling that in so his backpack is gonna be mostly concealed behind his back now let's let's keep working using the natural lines between the chest and the shoulder and the tricep and the bicep you can get some of that feeling of depth on the arm just by making those curves in the right places let's see so we've got the got the short sleeve on both arms hopefully it's coming out to look about the same length on each side and yeah I mean that I mean I think it would look better if it were that no sleeve shirt that he had in the comic book but we've made a commitment we're gonna stick with it gonna make this look as good as we can make it look let's see the elbow there all right an idea of where this is gonna be elbow forearm all right okay let's see let's go ahead and draw this hand in a little bit get an idea of where where that thing's gonna go got a thumb maybe a thumbnail here should look a little larger than that hand because it is closer to the viewer okay we got a kind of a finger extended here we have this one partially extended kind of bent like that and then this one we're like that and this one pinky finger is the smallest and fold it over like that that should grip our bow the muscles in the hands all right now that bow probably a little smaller than I wanted it to be but that's okay we only have so much space on the page and storm shadow came with a small bow anyway so that's fine the bow of course is a cylinder just sort of stretched out and pinched at the ends so I'm gonna remember how to draw cylinders so that we can make this look good and round and three-dimensional but not perfect it's gonna be a little sketchy because I'm not using any tools so try to make that look good I don't really have anything handy to use as a straight edge I really this really ought to be the bowstring ought to be done with the straight edge I don't have one so it'll work with what we got always do the best we can with what we have and we don't complain for doing my toy reviews I do not have the best camera I do not have the best laptop to edit things on I do not have often I do not have the best toys to review but we do not complain we soldier on all right let's see it's probably a little bit of a wrapping around the around the bow okay looking all right looking all right now we're not gonna I'm not gonna draw in the legs or anything else I just want to know where they are because this drawing will stop right about there because when I do it when I crop it I'm probably gonna crop it like like that and then over here will be the text so I really don't need to draw anything down here for my purposes so let's see let's do a little bit of work here feel like we need to draw in that belt a little bit more since that is a bit closer to the screen that's like I'm just looking at it in layers this is closer to the top layer and I'm not I'm got a little bit of lines in there suggesting that the belt is wrapped around him a couple times and then tied this do is sort of guess at what a knot would look like with that belt and then the rest of the belt hangs down like so and that's on the figure the belt is on that side so that's what I'm looking at the figure came off the stand so please stay on your stand Mr. Storm Shadow all right there are a lot of different things I could have done with this drawing I could have drawn the Yoroshikage tattoo on his arm with if I put him in a different pose I could have had him posing with the sword as he was on the card art and I love that card art excellent excellent card arch for Storm Shadow but I thought Storm Shadow is the master bowman so let's let's give him his bow all right now let's let's figure out what's going on with this sash here which I always assumed held his backpack it's thick looks to me like it's made of leather it's got a big spiky buckle on it something like this like so that reasonably matches the figure yeah about like that so we got that figured out now I'm not going to use my ballpoint pen to darken that in and make it black of course it's black on the figure but it's not gonna be black on the drawing when I finish this and color it and then scan it in for it to use for the thumbnail image I will when in the coloring phase I'll color that in darker so that it's more accurate to the toy but for now I'm just gonna have it as it is and you know not not try to not try to color it in with this thing that would not work very well so let's see here let's see got a bit of a loose cloth around there but I feel like the cloth mostly gonna be the belt is gonna layer over the cloth quite a bit I don't feel like the belt is pinching the cloth of the tunic very much let's this knife drawn in maybe slightly larger than it appears on the figure I do understand why they made it smaller on the figure because frankly it takes up a lot of space as I've drawn it here okay and there was oh there's a throwing star right here it's kind of poking out see something like something like something like that can't have it sticking too far out of his belt or it would fall out when he moves so it's gonna be tucked in there pretty well all right and the belt the same as the the bandolier I'm not going to color in the belt will be black once I do it in the coloring phase before I scan it in like so yeah I wish I hadn't put that there I don't I don't want to see the backpack on down here it just interferes and it weakens the line here to have this line here so I'm just gonna ignore that and what maybe when I scan it in I'll after I scan it in I'll crop that out or gently erase it digitally before I finish or before I do the cropping all right let's see we're pretty close I think we just need to finish rendering everything sword doesn't have to be perfect close enough is good enough for these I keep reminding myself that at this time in my life I do not have the luxury of being a perfectionist about anything it's got too much going on too much going on perfection takes too much time and I don't have it so I think we got something going there basically the same on this side something like that sort is back there but it's in shadow kind of over his shoulder there and let's get some arrows going here let's see here I'm mainly basically kind of suggest the arrows not going to completely render the arrows because I don't want a bunch of hyper detail over his shoulder here to draw away from the rest draw the eyes attention away from the rest of the drawing we would waste our time if we do all of our work to make a nice storm shadow here but instead of seeing the storm shadow the viewer sees like for some reason some hyper detailed arrows over on his shoulder we're not trying to draw the eyes attention away from our figure drawing okay so let's go ahead and finally finish rendering that head it's just a little off better eyes are always tricky getting them facing in both the same direction and trying to not make the person look cross-eyed that is tricky and I don't always succeed but I hope most of the time I do think I do better at that than I do drawing hands that's for sure alright little hint of cloth folds there and his mask don't want to overdo it see there's a level of detail that we want in this drawing beyond that we are just being distracting so there will be probably about where we stop with the head it's about right make sure I got this shoulder the way I want it there's some folds in the cloth because his arm is raised our nice cylinder of an arm looking three-dimensional feel like this arm is still looking a little fatter than the other arms so I'm gonna just kind of draw it in a little bit okay now this one out a little bit okay so you know that his wrapping is kind of coiled around his arm there so let's add some of that detail here and also over here don't mind a little extra detail on those arm bands because again with some curves it makes those arms look more three dimensional let's finish in the cobra symbol here awfully difficult to draw by hand as you probably will have noticed in some of the GI Joe comic books some of the artists that tried to just kind of sketch in the cobra symbol sometimes it didn't work out so good didn't look too great and I may not look too great on this one but it will look as good as I can get it so there we go and make sure that his chest is a little bit more defined strong shadow is of course very athletic being a ninja right I feel like the belt is done belt needs a few more lines okay what's missing we got to finish rendering this hand over here it should be a little bigger than the other hand but not too much bigger it is a challenge I struggle with this I don't lie I struggle with it I used to be a lot better I think but that's when I was wanting to be a comic book artist that's what I always wanted to be my whole life that was my plan that was my life plan to go to art school and to become a comic book artist well I did go to art school but the rest of the planets didn't quite work out the way that I intended and that's okay you know life intervened and I don't mind so much because I am very happy with how things turned out so I don't have any regrets and despite the fact that I don't draw for a living I still get to do this every once in a while when I feel like it let's see this is going to be a little bit shadowed because his hand is over it there like so let's see what are we missing what are you missing got that got that got that feel like there's like a seam line or something here but I haven't quite defined it yet because I really don't know what to do with it I think I'm just gonna leave that and I think we might have it I think we might have a finished storm shadow there we go I'm gonna call that good that's our storm shadow here's a comparison between the final sketch and the final drawing the fully rendered drawing and my sketch of scoring strong shadow that I was looking at just for a guide for this and you can see that the sketch does have a lot more energy there's just a lot more going on here the bow is bigger the arm is a bit more forward he's leaning back a bit more which I liked I didn't quite capture that in the final drawing but overall I think it's alright I think this is okay at least it's okay for my purposes so that's it I just wanted to show you through or take you through this process and show you what I do when I do one of these drawings I'm going to color this guy in I'm gonna scan it in and then I will I guess put this up on eBay and see if anybody's interested in it so there's storm channel thanks everyone for watching thanks for your patience there will be a new toy review next weekend I'm already working on that I hope you like it it's kind of a bit more I put a bit more work into that one and maybe you'll see another quick shot or two between now and then so thanks again for watching I'll see you all next time


My favorite intermittent fasting hacks to help you lose weight. But Dr. G, I can't do fasting like you do. You know, I hear it all the time. But I'm here to tell you you can do intermittent fasting. I'm today going to give you five insider hacks to help make fasting easy and and actually enjoyable. That means no hang green. No headaches and all the benefits. OK, here we go. First of all, you don't jump into the deep end of the pool for fasting. I've told you over and over and over again. I've written about it in almost all of my books that the vast majority of Americans cannot do time restricted eating, skipping one or two meals right off the bat, because most Americans are insulin resistant, metabolically inflexible and as much as you would think you could burn fat for fuel instead of sugar, quite frankly, you can't and you will fall flat on your face and you will get a headache. You will get hangry. You will get weak and you will give up. Don't do that. What you want to do is get in at the shallow end. Now, what do I mean by that? Anybody can do this and I'm going to hold your hand. If you eat breakfast at seven o'clock every morning next week, you're going to eat breakfast at eight o'clock in the morning. Anybody can wait one hour from their regular time to start eating breakfast. Do that all week.  Enjoy yourself. Go back to whatever routine you do on the weekend. The following week, you're going to eat breakfast. And remember the word breakfast is break fast. You're going to eat breakfast at nine o'clock instead of eight o'clock. And you're going to do that all week.  The following week, if you're doing OK, we're going to have break fast at 10 o'clock. Now, some of you can make it to nine just fine, but then 10 o'clock it's a little tough. That's OK. Go back nine thirty. Try that. Well, wherever we can get you to continue to expand when break fast starts up to eleven o'clock, twelve o'clock on a weekday basis. The more benefits you're going to get. And like all the studies have shown, the more we can push breakfast farther into the morning. Even till noon, the more weight you're going to lose and the more health benefits you're going to get. So that's go in the shallow end. Don't dive into the deep end. Second trick, and this may be the best trick there is. There's a fascinating theory called the gut centric theory of hunger. And I've written about this in my books. There have been some beautiful studies that have been done in China that proves this to be true. For years, we've thought that hunger pains are caused by either an empty stomach, that makes sense, or by actual hormones that are gut neurons secret to tell our brain. Hey, it's time to eat. Well, with the discovery of the human microbiome ten years or so ago, we now realize that there was a third participant in all of this. And that is the gut microbiome wants things to eat.  In fact, we now know that bad bugs in your gut actually hijack your brain. To have you find the foods they want to eat. And that's simple sugars and fats sound like the American diet, right? On the other hand, good gut bugs like prebiotic fiber. And the results of the gut centric theory test is you could take people who were on a seven or 14 day water fast. That's all they got was water. Give half the group a hundred calories of prebiotic fiber a day. Now, a hundred calories is not a hundred calories because we can't digest prebiotic fiber. But your gut bugs can. And what they found was that the people on these water fasts who got a hundred calories of prebiotic fiber that they didn't absorb but fed their gut microbiome had absolutely no hunger. Now, how do you do that? Well, it's really easy. There are tons of prebiotic fibers on the market. Give you an example. I'm a huge fan of basil seeds. They have a huge amount of prebiotic fiber. You can view my episode 219 with Zen Basil and find out how easy it is to put a tablespoon of basil seeds in a glass of water or in whatever. Put some allulose sweetener if you want to make it flavorful and you will be shocked what a full feeling your gut will have. Now, the idea that this stuff expands and swells up and fills your stomach, believe it or not, is not the reason you feel full. It's the gut bacteria eating the fiber that send messages to your brain. They said, hey, we got everything we need to eat. You don't have to go looking for anything else. It is just one of the best tricks I have ever discovered. And there are plenty of other wonderful prebiotic fibers out there to do the same trick. Third hack, drink a polyphenol rich powder supplement. Polyphenols, it turns out, are also beloved by gut bacteria as a prebiotic fiber in and of themselves. And one of the benefits of these polyphenol rich powder drinks that are readily available, I bet you can think of several right off the top of your head that might have my name associated with them, these feed good gut bacteria, but they don't stop your fasting. They do not break your fast. It's a great way to keep going, feed the good bacteria and not have to worry about breaking a fast. Fourth hack, MCT oil, medium chain triglycerides. Now, medium chain triglycerides, as most of you know now, are not absorbed like any other fat that we eat. In fact, they're absorbed directly through the wall of our gut into our intestinal bloodstream and are taken directly to the liver. Do not pass, go, do not collect $200 where they're converted into ketones. Now, if you've been paying attention or reading my books, you know that the vast majority of majority of us who are insulin resistant or metabolically inflexible, when we stop eating, we cannot make ketones. Ketones are a way of keeping our brain happy and our muscles happy while we're fasting until we start producing free fatty acids from our fat cells. So MCT oil is a hack to get around this metabolic inflexibility that most of us start with. So just putting some MCT oil in your coffee, along with, hey, dissolve some prebiotic fiber in it, that will kickstart your own production of ketones without breaking a fast. It will not have any impact on fasting. And it's another easy way to ease into this process. Again, just getting your feet wet rather than diving headfirst into the pool. Finally, another one of my favorite tricks is have some healthy Coke. You may now know that I was the originator of the idea of having a healthy Coke, which consists of balsamic vinegar and sparkling water, my favorite is San Pellegrino, to mix those two together and you will get a Coke-like experience. Now, why should you do that? It turns out that balsamic vinegar and other vinegars, for that matter, are loaded with postbiotics. And these short chain fatty acids actually are converted, not only into ketones, but can also be used as fuel by your brain and your other tissues. Now, here's a trick. Some people say, I really don't like the vinegary taste of balsamic vinegar. Do yourself a favor. By the thicker varieties of balsamic vinegar might be a little bit more expensive, but there's one that's really cheap that I love that I use personally. It's Napa Valley Naturals Reserve balsamic. It's easy to find. If you can't find it in any place else, it's on Amazon. Try it. It's thick and rich and delicious and will make your healthy Coke really taste great. Having that in mid morning while you're kind of slumping will really perk you up if you really want to have another tablespoon or so of MCT oil, then you can do this. If you enjoyed this episode of the Dr. Gundry podcast, you're definitely going to want to see this one. About 30 percent of all the fat in these cheeses are medium chain triglycerides MCTs. And you know how great MCTs are for your health.


الثلاثة أجهزة كانت تدخلت لأجهزة الإجتماعي والسؤالات في الثلاثة الشركة كانت عبدالحمان الحميدي، أجهزة أجهزة الأجهزة والأجهزة والأجهزة at the Arab Monetary Fund الثلاثة أجهزة أجهزة الإجتماعي والسؤالات في الثلاثة الثلاثة المتحدة كانت رايد شرفدين، هو أجهزة الأجهزة في الثلاثة من جانب العامة الأجهزة في سنفرق لبنان يدرس بشكل أشياء من سيرين ورفوجيين في لبنان whose exact number is unknown from 1 million according to some figures to 2.5 million which is a figure which amounts to more than one third of the entire population of the country He recalled that at the beginning of the Syrian crisis those refugees were welcomed in Lebanon on a humanitarian basis but after more than 10 years they became to be perceived as a political and security threat not to mention the losses for the Lebanese economy provoked by the Syrian conflict which amount to about 46 billion US dollars and we are now witnessing a trend a growing trend among the public opinion in Lebanon to send those refugees back to Syria where things are in a sense slowly improving Syrians in Lebanon it should be recalled are nowadays at the first rank of refugees in the world due to their high birth rate the number could be equal to the natives in Lebanon by 2043 the following speaker was Ernesto Damiani he is a professor at Khalifa University for the department of electrical engineering and computer science director of the center for cyber physical systems he addressed the issue of artificial intelligence in the Middle East stressing on the importance of the Gulf area as a hub between East and West there should be according to his views common strategies concerning the development of AI in the region based on confidence but it is not necessarily an easy task in an area affected by conflicts I was the following speaker and I addressed the main social challenges in the Middle East stressing on key points economic diversification youth empowerment as it was pinpointed by the Emirati diplomat political and social inclusion regional cooperation and sustainable development and that's numerical transformation the next the following was Mamdouh Karakuluchu Mamdouh Karakuluchu is founding member of the Global Relations Forum founding partner of Kanumun and chairman of Croton Consulting he also stressed in his speech on confidence as a key issue for the economic development in the region he pinpointed on the high rate of unemployment informality of the economy on the weakness of the private sector as hampering factors if reforms which have been carried out have not reached the expected goals in the last years there is still according to him place for strategic opportunities including a better integration with Europe in the field of energy he said that good governance is not enough but it's not enough there should be also leadership vision on the smart guidance finally Kamal Abdullah who is managing director on CEO of Canal Sugar from Egypt addressed the question of food security starting from the experience of his own country Egypt and the experts of food riots in his country Egypt whose government has been forced to heavily import on subsidized to cope with this situation he stressed on the necessity to change the scope from food security to food wellness pinpointing on the fact that water crisis will be probably the next challenge in this respect he considers that desalination could be an affordable solution thank you


The Potarka Division of the Court of Appeal is yet to give its decision on a motion filed by the Chairman of the People's Democratic Party, PDP Prince Uche Secundus. Secundus has urged the court to suspend the October 30 and 31 National Convention of the Party and to declare him the right person to preside over the exercise. While joining us to break this down is political analyst Biodum Shoumi. Thank you very much Mr Shoumi for joining us. It's my pleasure. Great. Here we are again talking about the in-fighting within the PDP seems to be deepening every single day. Secundus is asking the court to suspend the October 30 and 31 National Convention just as I said earlier on to declare him the right person to preside over the exercise, not only that. Now the court has fixed October 28 to hear the rule on the motion for an interim injunction by Secundus against the PDP and others. Now what do we presume is going on here? Because one minute the party is saying they do not necessarily need to, they do not necessarily need the party chairman to conduct the convention as it was. But now he's saying that he doesn't even want the convention to hold except he presides over it. So it looks like the PDP is speaking from both sides of its mouth or maybe he does need to have its house in order. Yeah, well what in the process that's what Secundus is trying to achieve is to establish through the courts that he has a valid claim, he still has a valid claim to share my chief of PDP. We should not forget the shenanigans behind all the political death moves made to get rid of him from office one way or the other. They tried to get him to resign to be billed, the party eventually got fractional rights because there were two cases involved. Now Secundus' position is very clear that the PDP convention should not appeal because he should have presided as the chairman and therefore since he has filed a case in court, all parties to this suit are expected to exercise restraint, not to do anything that would bring up a fatal conflict on the court, that is to render the court interrogation of his case useless. That is the point which Secundus is doing. But I felt he made a mistake in me sharing by not going for an interlocutor injunction to be strained with PDP from organizing any convention and the strained, you know, the chaotic chairman, he didn't do that, he's just filing the injunction. So there was nothing stopping the PDP from going ahead, you know, they really have gone ahead because there was no injunction, even though all parties are expected to exercise restraint when the cases occur and you have been sacked. So that is the fact of the matter. What we see going on now is in that field of different processes that are those who want to destroy the PDP and make it so weak before the next election, you know, some of them, even the people acting in the APC, there are also those who within the PDP are just, you know, to position themselves for either the chairmanship of the party or eventually for the presidential ticket of the party. We have heard what the current chairman said, look, you will be prepared to resign if he not on my marches as the presidential candidate. So there are a lot of political death moves going on. But if Secundus is going to be right by default, they may as well set aside that convention. I spoke with the Deputy National Publicity Secretary of the People's Democratic Party, if I'm not mistaken, last week or two weeks ago, on the same issue. And I did ask him why, which is Secundus's tenure, expires sometime in December. And then they're fixing a national convention in October. And he said, well, that the party, it doesn't matter, whoever emerges and the National Working Committee will wait till December for swearing in, or they may determine if Secundus stays or goes. And now you've told me that there should have been an interlocutory, just an injunction of sorts to stop them from having that convention. But they seem to have it all figured out. But again, if Secundus, I mean, whether this case is in court or not, if Secundus, knowing that in Nigeria we really do not respect court orders, we pick and choose which one to adhere to, if this plays out the way it does play out, does that mean that the new National Working Committee that emerges come October, the end of this month, might have to kick Secundus out if they choose? Yeah, it depends on the way the judge will read what has happened. And it also depends on the evidence presented to the courts. The PDP risks one thing, which is because a case is in court, he has filed a case in court and the PDP has been served properly. The fact of the matter is they are expected not to do anything that would put a fate a complete before the court. They are expected not to render the interrogation of the court a useless society. So therefore, the risk is that the judge in his view may choose to set whatever they have done since the case was filed in court, render it a knowledge. And the other side of it is that the judge might take a view and say, I don't know, there is no injunction filed by you at the time, by Secundus at the time when those processes were taking place and therefore the hacks had been completed before you filed the judge. And because of that, the judge may as well refuse to uphold the submissions of Secundus lawyers by disregarding or notifying the convention. So it's two ways. It depends on how the judge did it and since all the facts are not very clear presently to me, the papers, the evidence before the court. So we can only assume that there's a risk of the court notifying it. It's also likely that the court may not even agree with Secundus and uphold his removal. So these are issues which the PDP needs to ponder about. The PDP brings about a period of uncertainty, particularly for the major opposition party in Nigeria, who by now should be getting set to get his ass together with a view to challenge this. But it's quite unfortunate that this terrible situation and because of that is not enhancing democracy. The crisis within the PDP itself is diminishing democracy because we are not having a vibrant opposition to the women party. It's interesting to also note the movements within the party. We've seen the former Speaker, former Senate President, I beg your pardon, Pakola Sariqi, making a lot of moves and having reconciliation meetings here and there. We've also seen an Attiku Abu Bakar, who's still very much interested in the race, even though recently there's been a suit against him challenging his eligibility to run for presidency. We've seen a lot of big weeks making big moves. There's also been a list released of people who they think within the PDP might be interested in not just the leadership of the party but flying the presidential flag for the party. I'm asking you because of course we're analyzing this issue. Could this also be the reason why the position of Secundus is threatened? But looking at the body language of Pakola Sariqi, is there any form of reconciliation that can address the situation that the party is facing right now? And how soon can they put themselves together, get their acts together to be able to face an APC, which also might be having its own problems but seem more ready than the PDP? Yes. Well, when this problem started, there were so many people keenly interested, you know, that for the sake of democracy and for the sake of having a very vibrant alternative, at all times in any democratic setting, the PDP needs to get their acts together. I remember there were a lot of discussions about the southern government's position on greasing and the position of the northern governments and how it cut across the major political parties, that is APC, PDP. So it seems those parties were divided along that line. If you remember, Wike, the PDP governor, was also part of the southern government's position. So also the state governor and all APC governments. On the side of the north also, you also have PDP and APC working together on those agenda. So what that means is the southern governments are taking a position, which includes the PDP governor, to say that we will not accept, well, they are not saying that, they are advocating that the next presidential from the south, so given that situation, they are diametrically opposed to their colleagues from the north, who are also from the same political party. So this is part of the things, you know, the game going on. A second was simply removed for majorly, for one reason, because of the needs for those who are interested in the presidential race to ensure that they have a chairman, or a chairman who will do their bidding, because the chairman in PDP or APC, the chairman is very powerful, they can influence a lot of things. So we have seen the game going on behind, nobody is thinking about democracy currently, nobody is thinking about the fate of PDP, the people currently doing what they are doing, are doing it because of their own personal ambition. And that is what is guiding them. Now they have removed second ones, second ones are still getting up, they are making moves to resolve some of these issues behind the same. By that, whether those issues will be solved is in it, because there will always be a third force, there will always be a third party involvement in their own internal language for obvious reasons, because you don't expect the APC to go to bed and allow PDP to ignite. Both parties are working very hard, we have had Swaraki also saying some APC big weeks, we will soon be joining PDP. So both parties are working very hard to undermine each other, simply because all the parties are not ideologically oriented, and it's easier for you to sleep in the APC and wake up in PDP the next day. So because of that, we have this flow of movements from one party to the other. And that is what is going on currently. Nobody is thinking about democracy, nobody is thinking about the fate of PDP as a vibrant opposition party currently, or the need for PDP to begin power. What is at play currently is the interest of candidates who are interested in the presidential race. And that of course leaves the question of, to us, the people who are watching, if we do even understand what's happening, or more people might not necessarily understand what's going on, or that these politicians are more interested in their personal gains as opposed to what we need as a people. So where does that leave us as the electorates? We vote for whoever the parties throw up at the end of the day. It's a case between the devil and the deep blue sea? There are a lot of contradictions which are a political process is faced with. Many of them can be resolved in restructuring. But with the body language of the presidency and the political parties, it does not seem they are so much interested in restructuring in the sense that all the political parties are in November currently trying to to slug it out on who becomes the nest of democracy. There is no party who is taking a position to say that look, look, until we restructure, we are not going to get involved in this process. That does not mean that that process will go on seamlessly. I really doubt that otherwise, what are you going to be talking about? Militarizing the political space in Annambra and I thought that if families don't exist, they will disrupt that very process. So what you see is the nature of the politics we play in our country, we are the interests of politicians first before they think about the political party and before they think about my duty. We need to restructure this country. If we don't get the structure right, we would always have this kind of challenge. You still have the security challenge, how do we intend to resolve that? How do we intend to manage that situation? It's not yet clear. How would you get new purpose to come out and vote in elections or to come out and participate as a doctor for whining? No one knows what would happen. So democracy is very fragile and is faced with so many challenges which are inherent. I hope not, but the bottom line is the political parties are not butting their acts together. Both the PDP and APS inclusive. The major parties are the internal ranglings in some cases, almost partionalised, semi-fartionalised, and then both parties are not meeting the needs or expectations of the people in terms of their performance. We need to wait and see how they open the doors. I'll be able to show you as a political analyst always a pleasure to have you speak with us. Thank you very much. It's my pleasure. Thank you. We'll take a short break now to say about the accusations that were laid yesterday by the federal government on NSAS protesters and iPop members on the destruction of properties in the south-east and the south-west, including the Obus Palace. Stay with us. What does iPop member has to do with the destruction of properties? To me, iPop member has nothing to do with this. What resulted to that destruction of property was the result of the killing and protesting. Protesters are right which they are supposed to exercise, but due to the way the government was doing it, that's the reason why they are now escalating. The idea is not to escalate. For the first few days they did it before that day, nothing like that. There was no destruction, but because of the killing, that was why it happened like that. iPop member has nothing to do with. He has nothing to do with iPop member and it was not even the protesters' intention to do that. When the answer started, it started as a peaceful protest without any violence. The people only gathered at the toge protested the police brutality which was peaceful until the government coming was shooting by the soldiers, by killing people. So that was actually what escalated to the crisis. So if you actually look at it, or the crisis was not as a result of the answer, the crisis was a result of the pro-reaction of the government by killing innocent people.  So there was a lot of people that had jacket because now it become a crisis between government and the people. So it's not actually the answer. The people that actually escalated the problem the same way you see the issue of what do you call it, KANU. KANU was no issue in Nigeria until government begins to promote KANU. If you look at it, IPOP was no issue. Nobody know about IPOP until the federal government itself promote. So the issue is that the government is the problem of the attract causes of every crisis in Nigeria. One of these days, you and I, everybody are going to stand before the throne of judgement and explain what we did on NETS. One of these days, take that one first. Second, how can IPOP and NSAS protesters help the God to go to an Obers Parlas KBAC Alayelua Ekejoriza I don't believe that. I think that is just funny because if you look at the NSAS, the origins of the NSAS protest was born out of everything that the federal government failed to do. So what is also a valid reaction of people who have been going through a lot. So you cannot attribute what happened to the Obers Parlas and every other facility to IPOP. IPOP up their own grounds or other grievances against the government and they know how they want to settle it. So if you are going to channel your accusation the government should first ask itself this question why the world was there and NSAS movement why in the world was there a protest and why all that destruction. If they can't answer that question, that's it. But as far as I'm concerned it has nothing to do with IPOP it has nothing to do with NSAS protest it just as a result of governments will have to do the needful to do what is right. When the government fails to citizens, that's their reward. Have a nice day. Well there's nothing more to add I want to thank you for being part of the conversation tonight. We'll be back tomorrow on Plus Politics. I am Mary Yannickle.


All right. Next up, we've got another amazing Japanese user, Makoto Hasegawa from Cyber Agent. Come on out. Hello, everyone. I'm Makoto Hasegawa, who is working at Cyber Agent in Japan. Today, I represent about how the Cyber Agent is using OpenStack and what we are planning for. OK? Let's start now and future of OpenStack at Cyber Agent. To begin with, I must introduce Cyber Agent because I know that only Japanese people know us well. Do you know Cyber Agent? Please raise your hand if you know Cyber Agent. OK, OK. Japanese people only. OK, I knew it. The Cyber Agent has one vision. That is to create 21st century reading company. The Cyber Agent is expanding its business in the field of internet, a reading industry of the 21st century. And we provide a variety of services, such as online games, online community, and art technologies. Let me give some examples. For example, online games, Rumble Fantasy, Girlfriend Pre-Luminary, about communities, Pasha's MyPed, and Broke Services, about art technologies, DSP, DMP, SSP, and so on. OK? And we have been running these art technology services on our private OpenStack crowd. The art technology is a bit complicated. So if you know more details about our technologies, please look at our website. OK, now let's briefly take a look at Cyber Agent history, OpenStack usage at Cyber Agent. In September 2012, OpenStack 4.0 released. We used OpenStack only for POC. And in April 2013, we provided over 10 services on OpenStack Wizard. And June 2014, we provided some art technology services on OpenStack Icehouse. And March 2015, we provided more art tech services on OpenStack Journal. We had 40 compute nodes. And we had three engineers in the team. And last month, the key role, the new environment, has been deployed. Some community services are running on key role. And now, let me show about the statistics of the biggest OpenStack deployment that we call Diana. OK? The exercise chart is transition of CP cores on Diana. Diana started with 3,500 CP cores. And now, it's growing and growing. And the right side chart is the distribution of flavors on virtual machine that running on Diana. As you can see, eight core flavors is most popular in Japan. Sorry, in Japan, not in Diana. And two core flavors is the second popular in Diana. And we are running over 20 various other technology services on Diana. And we have over 70 billions for these services. OK, let's get back to the history chart. It's time to show you the future of our OpenStack. What is the future? Let me show you three keywords of our future. The first keyword is a scale of our OpenStack. Second, the OpenStack version, the last keyword is STM, software defined network. The first, expanding our OpenStack, our services that running on OpenStack increasing and growing. So we need scale our OpenStack. The second, new is always better. We want to retire Icehouse and Juno deployment. And we must try to deploy the new environment, Liberty or Mitaka. The last keyword is software, sorry. The last keyword is software defined network. We are running only Neutron layer 2 agent and not running Neutron layer 3 agent. And trying to get rid of conventional VR based networking by using IP based overlay networking. We are now experimenting with Midnet by Midokura. I believe that Midnet is suitable for our use case and give us a great experience with Neutron. The OpenStack keyword with Midnet is already running on our development environment. We will adapt VXRAN hardware off-road for overlay networking technologies. Hardware off-road is very important for VXRAN performance. OK, that's all I have to say about now and future of our OpenStack server agent. I ask you again, do you know cyber agent? Please raise your hand. Do you know cyber agent? OK, please keep your hand up. OK? OK, OK. Give me a smile. Give me a smile. Brightest smile, please. OK, thank you very much. Oh, sorry. Today's presentation will be available on our GitHub platform. If you have any questions and any questions, please create on issues on GitHub. I will reply ASAP. OK, have a nice summit. Thank you so much. That was amazing. We've heard from so many incredible stories here, right here in Japan, Yahoo Japan and NTT, running billions and billions of page views on OpenStack and a lot of other companies that are at different points in their journey of adopting OpenStack. I think that's one of the most valuable parts of the summit is hearing what decisions people are making and then hopefully they can meet the right folks here this week and end up with another success story down the road as they expand their OpenStack clouds.