Podcasts about dvas

Episode 363 Show Notes   Topic of the show: On this week's show, AG and RH discuss risk vs. reward in flight training and ATC on the job training. Can trainers prepare students for real life scenarios if they protect the trainee from difficult and challenging scenarios?  Does the risk of spins outweigh the benefits of learning how to recover?  Does watching a student work a complex/busy scenario expose them to the risk of killing their confidence?  We also discuss taxi procedures, transponders, and a ton of new ratings.  This is an aviation packed episode and you don't want to miss it!   Timely Feedback: 1. SGAC Patron SE shared a missed approach procedure with a phone number in the event of lost comms! 2. Patron JMR shared more about DVAs and where to find them.    Feedback: 1. Patron CV asked our thoughts on taking forever to taxi.  2. Patron RWD is taking his knowledge from Opposing Bases and applying it in the NAS! 3. Patron RN asked about transponder codes and how they appear on ground control screens.   Have a great week and thanks for listening!  Visit our website at OpposingBases.com You can support our show using Patreon or visiting our support page on the website.  Keep the feedback coming, it drives the show! Don't be shy, use the “Send Audio to AG and RH” button on the website and record an audio message. Or you can send us comments or questions to feedback@opposingbases.com.  Music bumpers by audionautix.com.  Third party audio provided by liveatc.net.  Legal Notice The views and opinions expressed on Opposing Bases Air Traffic Talk are for entertainment purposes only and do not represent the views, opinions, or official positions of the FAA, Penguin Airlines, or the United States Army.  Episodes shall not be recorded or transcribed without express written consent. For official guidance on laws, rules, and regulations, consult an aviation attorney or certified flight instructor. 

In this episode, host Dr. Sabeen Dhand interviews Dr. August Ysa, vascular surgeon in Spain, about distal deep venous arterialization, including indications, patient selection, and how to perform his gunsight technique. --- CHECK OUT OUR SPONSORS Viz.ai https://www.viz.ai/ BD Rotarex Atherectomy System https://www.bd.com/rotarex Reflow Medical https://www.reflowmedical.com/ --- SHOW NOTES We begin by discussing his training and background. Initially trained in Barcelona before moving to Bilbao as a young vascular surgeon. He came to the US briefly to train at Montefiore and Houston Methodist. When attending the LINNC in Europe one year he saw a live endovascular case, which is when he decided to devote his career to peripheral arterial disease (PAD), specifically below the knee (BTK) and below the ankle (BTA) interventions. He currently works with Dr. Marta Lobato, and they have done around 25 combined deep venous arterializations (DVAs) in their practice. They love this technique because it gives someone previously faced with amputation a new chance. It is a technique to reroute blood flow to get oxygen to a wound and promote wound healing. There are two types of DVA: proximal DVA, which is done closer to the origin of the posterior tibial artery (PTA), and distal DVA, which is at the level of the ankle, and usually also involves the PTA. Thus far, it is unknown which technique is better in terms of limb salvage, and data shows both techniques yield 60-70% limb salvage rates. One advantage to distal DVA is lower rates of post-DVA storm, a type of ischemic steal syndrome. Availability of devices and lower cost also make distal DVA more appealing. DVA is never the first option, traditional recanalization techniques are always explored first. Wounds that are not candidates for DVA are large infected wounds or areas of necrotic tissue. This is because it takes 6-8 weeks to establish the newly created connection, and if the wound is already past the point of healing, DVA will not help. Other reasons DVA can fail is due to choosing the wrong candidates. Mean wound healing time after DVA is 4-7 months, so patients need to be able to commit to close follow up and wound care, and they must have the social support to be compliant with frequent clinic visits. Finally, Dr. Ysa explains his venous arterialization simplification technique (VAST). Before the procedure, he always does a venous ultrasound to rule out prior DVT and evaluate the status of the main veins of the foot. He uses two snares via the gunsight approach, which most IRs are familiar with from TIPS procedures. It involves overlapping two snares and then performing a through and through puncture from the PTA to the posterior tibial vein (PTV). The PTA is generally used over the anterior tibial or the peroneal artery due to its robust connections with the lateral plantar and the plantar arch. He then performs balloon angioplasty (BA) on the PTV. He initially uses the PTA for sizing, but generally goes bigger, between 4-5mm. For valves, he usually does regular BA but will sometimes use a cutting balloon. Two weeks post-DVA he gets an ultrasound, and at one month he gets an angiogram to evaluate the new tract. He has his patients take a single antiplatelet and a blood thinner after the procedure. He considers DVA to have failed if there is progression of wound necrosis. --- RESOURCES Dr. Ysa LinkedIn: https://www.linkedin.com/in/august-ysa-56a99a174/ YouTube DVA Webinar with Dr. Ysa and Dra. Lobato: https://www.youtube.com/watch?v=kDW5Rg5g49I Ep. 93 - DVA for CLI with Dr. Fadi Saab: https://www.backtable.com/shows/vi/podcasts/93/deep-venous-arterialization-for-cli Live Interventional Neuroradiology, Neurology and Neurosurgery Course (LINNC): https://www.linnc.com Patterns of Failure in DVA Paper: https://www.clijournal.com/article/patterns-failure-deep-venous-arterialization-and-implications-management

This week's episode features guest Brian Pasch, founder of PCG Companies and the newly formed Automotive Standards Council. In this episode Brian shares his thoughts on the current state of the industry and the role that digital voice assistants can play in improving customer service and reducing operating costs.

Join me as I sit down with industry innovator Josselyn Boudett, Founder of Telepathy Labs, to discuss the power of digital voice assistants to reduce operating costs and increase sales throughput. Dealers looking for improvments to their botton line must consider DVAs as they grow. 

On Episode 14 of the Stroke Alert Podcast, host Dr. Negar Asdaghi highlights two articles from the March 2022 issue of Stroke: “Natural Course of Cerebral Cavernous Malformations in Children” and “Direct Oral Anticoagulants Versus Warfarin in Cerebral Venous Thrombosis (ACTION-CVT).” She also interviews Dr. Mohammad Anadani about his article “Magnitude of Blood Pressure Change After Endovascular Therapy and Outcomes.” Dr. Negar Asdaghi:                        1) Are direct oral anticoagulants a reasonable alternative to warfarin for treatments of patients with cerebral venous thrombosis? 2) What are the predictors of first and recurrent intracerebral hemorrhage in patients with cerebral cavernous malformation? 3) Is there an optimal blood pressure target after successful endovascular thrombectomy? We have the answers and much more in today's podcast. This is the latest in Stroke. Stay with us. Dr. Negar Asdaghi:                        Welcome to another incredibly informing Stroke Alert Podcast. My name is Negar Asdaghi. I'm an Associate Professor of Neurology at the University of Miami Miller School of Medicine and your host for the monthly Stroke Alert Podcast. The March 2022 issue of Stroke includes a number of papers published in conjunction with their oral presentation at the International Stroke Conference in New Orleans, from contemporary trends in the nationwide incidence of primary intracerebral hemorrhage, to disparities in Internet use among U.S. stroke survivors' implication for telerehabilitation during COVID-19 and beyond. I encourage you to review these timely topics in addition to listening to our podcast today. Later, in our interview section, I discussed the optimal blood pressure goal after endovascular therapy and the results of a subgroup analysis of the BP-TARGET randomized trials with Dr. Mohammad Anadani from the Department of Neurology at Washington University in St. Louis. But first with these two articles. Dr. Negar Asdaghi:                        Cerebral cavernous malformations, also referred to as cavernous angiomas, cavernomas, cav mals, or CCMs, are angiographically occult, low flow, vascular lesions with no large arterial inflow or venous outflow vessels. These are clusters of dilated sinusoidal vascular channels that are aligned by a single layer of endothelium without the normal surrounding vascular smooth muscles, and they lack the normal tight junctions between their endothelial cells. Cavernomas can be found in both children and adults. So, the question is, how do these lesions present, especially in children, and what is their natural course? Now, before we answer these questions, let's review a few important points about cavernomas and what is known about these lesions in the literature. Number one, cavernomas are acquired lesions. Although initially thought to be congenital, they're now known to be acquired as comparing by many reports of patients with normal MRI findings, who later developed a CCM. Number two, they're not always benign. While most of them can have a benign course, cerebral cavernomas can be a cause for headaches, seizure disorders and intracerebral hemorrhage, which is, of course, their most feared complication. Dr. Negar Asdaghi:                        Number three, though CCMs are rare vascular disorders with a prevalence of 0.6% in children and young adults, about a quarter of patients with a confirmed diagnosis of cerebral cavernous malformation are under the age of 18. And number four and finally, data seem to suggest that the risk of hemorrhage is potentially higher in the pediatric population than their adult counterparts. So, determining the natural course of CCMs and predictors of intracerebral hemorrhage is important for all patients, but especially important in the pediatric population. Now, in the current issue of the journal, in the paper titled "Natural Course of Cerebral Cavernous Malformations in Children: A Five-Year Follow-Up Study," a German group of investigators led by Dr. Alejandro Santos from the Department of Neurosurgery and Spine Surgery at University Hospital in Essen and colleagues studied the clinical presentation and predictors of intracerebral hemorrhage in their pediatric population over a 17-year study period. Dr. Negar Asdaghi:                        So, they identified 129 patients with a diagnosis of cerebral cavernous malformation that had baseline MRI imaging completed and at least one or more follow-ups during the study period. Now, some of these patients were treated surgically and some conservatively in the study. The mean age of their study was 10, and over 50% of their study population was male. Developmental venous anomalies, or DVAs, were detected in 15% of their study population, and 20% had brain stem cavernoma localization. Now, importantly, half of these kids, so that's 55.8% of their study population, presented with an intracerebral hemorrhage, and that's how their cavernomas were diagnosed. So, what were their top three findings? Dr. Negar Asdaghi:                        Number one, on the comparison of conservatively treated patients to those treated surgically, which was 37% of their cohort, they found that overall these two groups had comparable clinical characteristics and demographics with regards to sex, age, multiplicity of cavernomas, brain stem location, and family history of their lesions. But not surprisingly, those who were surgically treated were more likely to have presented with an intracerebral hemorrhage and less likely to be asymptomatic, meaning that their cavernoma was not an incidental finding as compared to those who were conservatively treated. Dr. Negar Asdaghi:                        Number two, when they looked at predictors of presentation with intracerebral hemorrhage, they found that family history of cavernomas and brain stem cavernomas were significant predictors of presenting intracerebral hemorrhage. Number three, when they excluded those who underwent surgery, the annual risk of hemorrhage for the overall untreated participants was 4.1%. However, we should note that this rate significantly varied based on certain characteristics of the patients. The risk of hemorrhage, or rather the risk of re-hemorrhage, was double this baseline, that is 8.1%, for those cavernomas that presented with a bleed at presentation. The annual rate of hemorrhage was equally high at 7.1% for brain stem cavernomas, and then this rate gradually declined for familial form cavernomas at 6.2% annual risk of hemorrhage and multiple cavernomas at 4.8%. And it went all the way down to 0.4% annual risk of hemorrhage for asymptomatic incidentally found cerebral cavernomas. So, in the multivariate analysis, presentation with an ICH remained an independent predictor of re-hemorrhage and cavernomas with a high hazard ratio of 14. That is 14-fold higher risk of hemorrhage in cavernomas that present with a bleed as compared to those that did not. Dr. Negar Asdaghi:                        Now, finally, on the association between DVAs and risk of hemorrhage, this study showed a possible reduced risk of hemorrhage in cavernomas that had associated DVAs, but this was not a statistically significant association. It is important to note that this finding is in keeping with the published studies in the adult population, but in contrast to the previously published data in the pediatric population. So, this association between presence of a developmental venous anomaly and cavernomas and the risk of subsequent hemorrhage needs to be furthered studied. So, what did we learn from this study? Pediatric patients with brain stem cavernomas and familial cavernomas have a higher risk of intracerebral hemorrhage as mode of presentation. The risk of re-hemorrhage is 14 times higher in cavernomas that present with an ICH as compared to cavernomas that did not bleed. And the probability of bleed tends to increase over time. Dr. Negar Asdaghi:                        Cerebral venous sinus thrombosis, or CVST, refers to thrombosis in the dural venous sinuses, cortical veins, deep cerebral veins, or a combination of these venous structures. CVST is an uncommon cause of stroke accounting for overall 1% of all strokes and can cause venous ischemic infarcts or intracerebral hemorrhage and importantly has a high morbidity and mortality if unrecognized and left untreated. Anticoagulation is generally the mainstay of therapy for CVST, which needs to be initiated as soon as possible, even in the presence of hemorrhage in the brain. The data regarding the choice of anticoagulation in CVST is generally extrapolated from randomized studies completed in patients with systemic venous thromboembolism, so conditions such as pulmonary emboli or deep venous thrombosis, and indicate that direct oral anticoagulants, or DOACs, are viable alternatives to traditional warfarin therapy in this patient population. This question was specifically studied in the RESPECT-CVT trial, which was a small European randomized trial that included 120 patients with cerebral vein thrombosis, randomized to either receiving dose adjusted warfarin or dabigatran at 150 milligram BID. Dr. Negar Asdaghi:                        The results of the study was published in JAMA Neurology in 2019 and showed that CVST patients treated with either dabigatran or warfarin were at low risk of recurrent venous thromboembolism, and they also showed a comparable safety profile in terms of risk of hemorrhage or mortality in patients treated with DOAC as compared to warfarin. But how do DOACs perform as compared to warfarin in routine practice is unknown. So, in this issue of the journal, in the study titled, "Direct Oral Anticoagulants Versus Warfarin in Cerebral Venous Thrombosis (ACTION-CVT): A Multicenter International Study," the ACTION-CVT investigators, led by Dr. Shadi Yaghi from the Department of Neurology at Brown University, aimed to compare the safety profile of DOACs to that of warfarin, in a multicenter international study that included 1025 imaging-confirmed CVST patients from multiple centers in the United States, Italy, Switzerland, and New Zealand. Dr. Negar Asdaghi:                        They had a number of exclusion criteria for this study, excluding patients with active cancer, those with a confirmed history of antiphospholipid antibody syndrome and those who were not treated with an oral anticoagulant. And after excluding these patients, it gave them their study sample of 845 CVST patients. So, what were their main findings? Number one, in keeping with a prior literature on CVST, these patients were young, their mean age was 44, and majority of them were women, so that was 67% of their cohort. And they found that a third of these patients were actually treated with a DOAC, and, in addition, another 15% received a DOAC at some times during their treatment course. Finding number two, the most common DOAC used in this population was apixaban, that was 66% of cases treated with a direct oral anticoagulant, followed by rivaroxaban in 18% of cases, and then dabigatran used in 13.5% of DOAC-treated cases. Dr. Negar Asdaghi:                        Important finding number three. A total of 27 patients had recurrent CVST, which also included patients with progression of their cerebral vein thrombosis on follow-up vascular imaging, and 17 patients had recurrent venous thromboembolism, and two had both. So, during their mean follow-up of 345 days, they had the rate of 5.68 recurrent venous thrombosis per 100 patient years. These rates were not different for DOAC-treated versus warfarin-treated patients in both unadjusted and adjusted models. Now, very important finding number four. When they looked at the rate of recanalization on follow-up imaging, for those in whom this information was available, partial or complete recanalization occurred in 86% of DOAC-treated patients versus 84% of warfarin-treated patients. This was not a statistically significant difference in the unadjusted or the adjusted models. Recanalization is, of course, an important determinant of outcomes in CVST and should be noted that recanalization is, of course, an important determinant of outcomes in CVST since persistent thrombosis through chronic raised ICP can potentially lead to a variety of neurological morbidities, such as chronic headache, chronic papilledema and increased risk of development of dural AV fistulas. Dr. Negar Asdaghi:                        Now, finally, in terms of safety profile, they had 31 hemorrhages, 23 intracranial, majority were symptomatic and 9 extracranial hemorrhages. The hazard ratio for hemorrhage or death was similar for DOAC- and warfarin-treated patients, again in the unadjusted and adjusted models. So, bottom line, in this large international cohort of patients with CVST treated with an oral anticoagulant in routine practice, patients treated with DOACs had similar clinical and radiographic outcomes and had a similar favorable safety profile when compared to those treated with warfarin. So, we stay tuned for the results of the ongoing randomized trials on this subject. Dr. Negar Asdaghi:                        What is the optimal blood pressure target after endovascular therapy? This is a commonly encountered question in routine clinical practice with a not-so-straightforward and easy answer. After a successful endovascular treatment, high systolic blood pressure targets are thought to be associated with increased risk of reperfusion injury and development of intraparenchymal hemorrhage, leading to worsening of clinical outcomes. Conversely, low blood pressure targets may worsen the ischemic penumbra, especially in the setting of incomplete perfusion. The current stroke guidelines recommendations regarding blood pressure control after endovascular treatment are mostly extrapolated from the post-thrombolysis studies. The BP-TARGET trial was a recently completed randomized study in France that aimed to assess the safety and efficacy of intensive blood pressure lowering, that is systolic blood pressure of less than 130, as compared to standard of care, that is systolic blood pressure between 130 to 185, after successful endovascular therapy in acute ischemic stroke. Dr. Negar Asdaghi:                        This was a neutral study, and the main results of the trial was published in early 2021 in Lancet Neurology. And if you missed it, well, as always, we're here with the Stroke Alert Podcast to fill in the gaps. So, we'll review the trial results with our podcast guest today, Dr. Mohammad Anadani, from the Department of Neurology at Washington University in St. Louis, who's also the first author of a paper in the current issue of the journal titled "Magnitude of Blood Pressure Change After Endovascular Therapy and Outcomes: Insight From the Blood Pressure-TARGET Trial." This was a post hoc analysis of the BP-TARGET trial, looking at the extent of blood pressure reduction and its implications of clinical outcomes. Welcome, Mohammad, thank you for joining us on the podcast today. Dr. Mohammad Anadani:            Thank you for having me. It's a pleasure to be here with you today. Dr. Negar Asdaghi:                        Thank you. So, blood pressure control is a really simple and yet extremely complicated topic when it comes to the collateral support before reperfusion therapies, and then, of course, the possibility of reperfusion injury post-thrombectomy in the setting of an ischemic stroke related to a large vessel occlusion. Can you please give our listeners an overview of the topic of blood pressure control in this setting? Dr. Mohammad Anadani:            Yes, absolutely. I totally agree. The topic of blood pressure control after, in patients with large vessel occlusion, is very complicated. And when we talk about blood pressure control, I think we should differentiate between pre-recanalization and post-recanalization. In the pre-recanalization period, the main focus should be to maintain adequate perfusion to ischemic penumbra to prevent infarct expansion. So, there is consensus that hypotension should be avoided at all costs pre-recanalization. When it comes to the post-reperfusion, here it gets a little bit more complicated. We do have a large body of evidence, as you mentioned, for the association between high blood pressure in the post-reperfusion period and the risk of poor outcome. What we don't know yet is if active reduction of blood pressure after reperfusion is beneficial. And that's why, as you mention, the American Heart Association guidelines just recommend a systolic blood pressure less than 180, just because of the lack of data to support the benefit of blood pressure reduction. Dr. Negar Asdaghi:                        Perfect. So, this was definitely the topic that the BP-TARGET trial set out to investigate. What is the optimal blood pressure target after successful revascularization therapy? Can you please tell us a little bit about the trial, the design and the inclusion criteria? Dr. Mohammad Anadani:            The Blood Pressure-TARGET trial, or BP-TARGET trial, aimed to assess the safety and efficacy of intensive blood pressure lowering treatment. The trial enrolled patients with anterior circulation large vessel occlusion, that is M1 or ICA occlusion, or tandem occlusion, which is both M1 and ICA occlusion. The patients who were treated with endovascular therapy and achieved successful reperfusion, and they defined successful reperfusion as modified treatment cerebral ischemia 2b to 3. And then after enrollment, the patients were randomized in one-to-one ratio into intensive blood pressure control, which is systolic blood pressure less than 130, and standard blood pressure control, which is systolic blood pressure less than 185. Now, these two cutoffs came in from some evidence that systolic blood pressure less than 130 is beneficial in these patients or this is the optimal cutoff for patients with successful reperfusion. For the standard group, the design of the trial, at the time of the design of the trial, that was the standard or recommended European guidelines, blood pressure group. And the study was conducted in France between June 2017 and September 2019. Dr. Negar Asdaghi:                        Thank you, Mohammad. So, I want to recap for our listeners, we're looking at a French study that was conducted in four centers, in France. And it's a very recent study, recently completed. The whole thing was completed over the past five years. So, very interesting because it's applicable to our current treatment models. And these were patients with a large vessel occlusion in the anterior circulation that had undergone thrombectomy. All have achieved a successful revascularization, as you defined, TICI 2b or C or TICI 3, and then they were randomized to either standard of care in terms of post-thrombectomy blood pressure control or the intensive group, which was under systolic blood pressure of 130. Did I recap that correctly? Dr. Mohammad Anadani:            Correct. Dr. Negar Asdaghi:                        Perfect. So, now we're ready for the primary outcome. So, what was the primary outcome of the trial? Dr. Mohammad Anadani:            The primary outcome was any radiographic intraparenchymal hemorrhage that was seen on CT within 24 hours to 36 hours after successful reperfusion. Dr. Negar Asdaghi:                        This is interesting, Mohammad, this is a different primary outcome than we're used to in a usual randomized trial that commonly uses a modified Rankin scale of usually at 90 days. Do you have any insight as to why a radiographic outcome was chosen for this particular study, and obviously what would be fine as part of the trial? Dr. Mohammad Anadani:            Yes. So, the main reason why the study investigator chose this as a primary outcome was because really the benefit of, or at least what is thought to be the benefit from systolic blood pressure reduction, is to lower intraparenchymal hemorrhage or the risk of intraparenchymal hemorrhage. So, to assist the efficacy of this intensive blood pressure lowering, the first thing we expect to see is lower intraparenchymal hemorrhage. So, when you have your target as intraparenchymal hemorrhage, it truly requires much smaller sample size than having functional outcome as the primary outcome. Dr. Negar Asdaghi:                        Okay, perfect. And I think we're ready to hear the results for the main BP-TARGET trial. Dr. Mohammad Anadani:            The results of the trial were disappointing for people who were interested in this topic. The primary outcome, which, again, was an intraparenchymal hemorrhage, occurred in 42% of patient intensive arm and 43% of patient the standard arm. And there was no difference in the risk of intraparenchymal hemorrhage between the two groups. Dr. Negar Asdaghi:                        Well, I think you can phrase it as disappointing, or more room to understand the pathophysiology and also onto bigger and better trials. And so I want to now move on the current paper in this issue of the journal, which is a post hoc analysis of the trial. Can you tell us a little more about your study? Dr. Mohammad Anadani:            In our study, we wanted to study the blood pressure as dynamic target. So, we wanted to see if there is any association between blood pressure change from baseline with the functional and safety outcome after endovascular therapy. And also we wanted to understand the shape of the association. In other words, to see, is there a point after which the blood pressure reduction becomes helpful? So, to do that, we did this post hoc analysis of the BP-TARGET trial, and we only enrolled patients who had more than 50% of planned blood pressure measurements. And then we defined systolic blood pressure change as the difference in the mean achieved blood pressure in three different time points: zero to one hour, one to six hours, and six to 24 hours minus the baseline systolic blood pressure. And here we considered the end-of-procedure blood pressure as the baseline systolic blood pressure. Dr. Negar Asdaghi:                        All right. So, I want to recap what you mentioned before we hear what you found in the study. So, really, blood pressure, as you noted, is a dynamic factor. It's not just a target, but other words, is how fast you're reducing it, in what timeframe after endovascular thrombectomy, and also how much. So, as an example, as we were discussing this earlier, before we did the podcast recording, is if you started a systolic blood pressure at 190 and then reduced that patient quickly to 130, is that the same as if starting blood pressure was 150, and then you reduce it to, again, 130? So, delta, or the magnitude of change in blood pressure, and also time intervals, that how long after thrombectomy you were able to reduce that blood pressure, are all important factors in terms of determining the outcome. That's a nice summary of what this current study aimed to do. Perfect. So, with that, we're ready to hear the results of your study. Dr. Mohammad Anadani:            We included 267 patients, 137 in the intensive arm and 130 patients in the standard arm. And then, when we compared patients who had poor outcome at 90 days to patients who had good outcome at 90 days, we found that the patient who had poor outcome had less systolic pressure reduction, meaning these patients had less systolic pressure reduction compared to the baseline than the patient who had good outcome. And then, when we controlled for other confounders, their association remained significant, especially for the one- to six-hour period and six- to 24-hour period. And the same results were when we had our outcome as intraparenchymal hemorrhage, we found the same results. The patient who had intraparenchymal hemorrhage had less systolic blood pressure reduction than patients who did not have intraparenchymal hemorrhage. And, again, the association remained significant even after we adjusted for possible confounders, like age, the degree of recanalization, and the stroke severity. Dr. Mohammad Anadani:            And then we wanted to see, if we looked at the blood pressure change as categorical variable, meaning we want to see if there is a difference between large systolic blood pressure reduction compared to minimum or no systolic blood pressure reduction. So, we divided the systolic blood pressure reduction into three categories: the minimal, which was just zero to 10 systolic blood pressure reduction; the moderate, which was 10 to 20; and large, which was more than 20 millimeter mercury systolic blood pressure reduction. And when we looked at that, a patient who had more than 20 millimeter mercury systolic blood pressure reduction had significantly lower risk of poor outcome than patients who had no systolic blood pressure reduction or just minimal systolic blood pressure reduction. And the difference was striking. There were the patients who had more than 20 systolic blood pressure reduction, they had almost 62% lower risk or lower odds of having poor outcome than a patient who did not have significant systolic blood pressure reduction. Dr. Negar Asdaghi:                        These are some very interesting findings. Let me try and to summarize this for our listeners and make sure that I understood the study results correctly. So, in other words, if we had a patient that at the end of a successful revascularization treatment, say, had a systolic blood pressure of 150, and that was reduced to 140, so there's a 10 millimeter mercury difference, that patient, in this particular study, had a higher risk for development of intracerebral hemorrhage than the person that finished at 180, so finished endovascular therapy at 180 millimeter of mercury. But then with rapid reduction, we dropped the blood pressure to, say, for example, 140, so that 40 millimeter of mercury of reduction carried a higher weight or higher impact on reduction of intracerebral hemorrhage than the absolute target of blood pressure, because your results did not look at which category were these patients under, were they under intensive category or standard, but they looked at just the magnitude of that drop, which showed a bigger implication on effective blood pressure reduction on outcomes. Dr. Mohammad Anadani:            Yeah, that is correct. Now, the primary outcome for our study and really what we want to look at here is the functional outcome, more than the intraparenchymal hemorrhage. And, like you said, if we have, let's say, patients who started with 160 and they dropped to 120 or started with 180 and they dropped to 150, these patients had better functional outcome than patients who started, let's say, with 160 and remained 160 or even their blood pressure increased after reperfusion. We did not look at absolute numbers, but we did look at if the patients were presented, let's say, above 180 or patient presented less than 180, and both of these patients had the same, or both of these groups had the same results, meaning systolic blood pressure seems to be beneficial for both of these patients. And also we looked at the patients who were in the standard arm or in the patients who were in the intensive arm, also both of them have the same results. The systolic blood pressure reduction remained associated with poor outcome. Dr. Negar Asdaghi:                        Mohammad, the current American Heart Association guidelines and also the European stroke guidelines both recommend a target systolic blood pressure of under 180 or 185 after successful recanalization. What do you think the optimal target blood pressure should be based on BP-TARGET trial and based on your post hoc analysis? Dr. Mohammad Anadani:            Yeah, that's a difficult question. We learn from the BP-TARGET trial, that's lowering systolic blood pressure is safe. And our study added to that, that significant reduction, especially in the first hour after reperfusion therapy, may be beneficial because patient had lower risk of poor outcome. However, I don't think we will have a one number that we will be able to say, this is the optimal blood pressure that fits all patients. I think the optimal blood pressure needs to be tailored to individual patient based on their admission blood pressure, based on their comorbidities, and also based on the degree of reperfusion. I don't think patients who have TICI 2b, for example, should be treated exactly the same as patients who had TICI 3. Dr. Negar Asdaghi:                        So, a lot still to come on this topic, and we are still learning. So, on that topic, can you tell us a little bit about the currently ongoing randomized trials on the topic of blood pressure controlled post-thrombectomy? Dr. Mohammad Anadani:            Yes. I think there are three main trials that are ongoing now and trying to assess the safety and efficacy also of intensive blood pressure reduction. The first trial is the Second Enhanced Control of Hypertension and Thrombectomy Stroke Study, or ENCHANTED2 study. And this study is being conducted now in China. And it's comparing systolic blood pressure less than 120 target to systolic blood pressure less than 180. And the study has the primary outcome here, is the shift in mRS score at 90 days. The study is estimated to be completed in 2023, so, hopefully next year, we will have some results. The second study is the Outcome in Patients Treated With Intraarterial Thrombectomy - optiMAL Blood Pressure Control, or OPTIMAL-BP. And this study is being conducted in South Korea, and it's comparing systolic blood pressure target of less than 140 to systolic blood pressure target of less than 180. Dr. Mohammad Anadani:            And the primary outcomes of this study are mRS zero to two at 90 days and symptomatic intracerebral hemorrhage. The study here is estimated to be completed in 2024. And the last trial is the Blood Pressure After Endovascular Stroke Therapy-II, or the BEST-II trial. And this is being conducted here in the U.S. and comparing three different blood pressure cohorts: less than 160 and less than 140 as the experimental group to less than 180 as the standard group. And the primary outcome of this study is final infarct volume. And also the co-primary outcome is utility-weighted mRS at 90 days. And this study is estimated to be completed next year, in 2023. Dr. Negar Asdaghi:                        So, a diverse group of randomized trials from Korea, China, and the United States. Hopefully, we'll have a lot more answers in the next two years then on this topic. So, just the last few minutes of our recording here. Mohammad, can you please summarize for our listeners, what should be our top two takeaway messages from your study and what we know from collectively in the field on the topic of blood pressure control post-thrombectomy? Dr. Mohammad Anadani:            I think the main home message that one, we found a leaner association between blood pressure change after endovascular therapy and poor functional outcome, and two, effective and significant systolic blood pressure reduction, which we defined in our study as a more than 20 millimeter mercury in the first hour after endovascular therapy, is potentially beneficial, and these patients had significantly lower risk of poor outcome than the patient who did not have significant blood pressure reduction. Dr. Negar Asdaghi:                        Thank you so much, Dr. Mohammad Anadani. Thank you for joining on the podcast today, and we look forward to having you back and covering more of your work in the future. Dr. Mohammad Anadani:            Thank you for having me, and I look forward to learning more about the Stroke studies from your podcast. Dr. Negar Asdaghi:                        Thank you. Dr. Negar Asdaghi:                        And this concludes our podcast for the March 2022 issue of Stroke. Please be sure to check out this month's table of contents for the full list of publications, including a series of Focused Updates on the topic of health equity and reduction of disparities in stroke, organized by Dr. Bruce Ovbiagele. It's hard to believe that we're already in March, and coming off the heels of one of our largest cerebrovascular annual meetings, the International Stroke Conference, which coincidentally concurrently happened with one of the biggest sports events of the year, the 2022 Winter Olympics in Beijing. Now, what do these two very different events have in common? Well, I think they both represent the extraordinary stories of talent and grit on the world stage. So, let's end our Stroke podcast with an inspirational story of the Olympian swimmer Yusra Mardini. Dr. Negar Asdaghi:                        In August 2015, after her family home was invaded and destroyed in the Syrian civil war, the 17-year-old Yusra and her sister, Sarah, fled Syria to Beirut, Istanbul, and finally İzmir, in Turkey, where they managed to squeeze onto a dingey crossing the Mediterranean to the Greek island of Lesbos. Carrying 20 people, rather than just six or seven, they found their boat sinking less than 30 minutes into their journey. Yusra, Sara, and another woman were the only ones on board who knew how to swim. Fighting for their life and that of the other refugees on board, they would swim the cold open water of the heavy seas for three and a half hours before reaching the shore. Less than a year later, Yusra became one of the top 10 athletes worldwide to qualify and compete in the 2016 Summer Olympics, as part of the first refugee Olympic athletes team. She won the opening heat of women 100-meter butterfly race, but did not make it to the podium in the Olympic Games. And that is, of course, only part of her story. Dr. Negar Asdaghi:                        Very much like the story of many scientists, doctors, engineers, and staff who make the international stroke meeting possible. Many stories are not celebrated on a podium, but nevertheless are the essence of the success of our stroke community. So, wherever you are in the field of neurosciences, whatever the challenge, and however cold the waters, know that while we don't share the same border, the same flag, or even a common language, together we push the field of cerebrovascular disorders forward. And, as always, we stay alert with Stroke Alert. Dr. Negar Asdaghi:         This program is copyright of the American Heart Association, 2022. The opinions expressed by speakers in this podcast are their own and not necessarily those of the editors or of the American Heart Association. For more, visit AHAjournals.org.

Digital Voice Assistants are all the talk these days. But there are some rumors surrounding them that simply aren't true. On today's episode, Tiffany Peeler and Jason Beckett bust some of the biggest myths surrounding Digital Voice Assistants and explain how they can actually benefit your dealership. Not only will a DVA boost your customer experience but also help you save money. 

  Our name is Nightcaps at the Theater and we’re here to party. Just before we head off into the spooky season, we have to make a pitstop in Okinawa to pick up Hattori Hanzo steel. With Kill Bill: Volume 1 we seek out our red-tinted vengeance against The Deadly Viper Assassination Squad, all while severing arms, heads, and dancing to the 5,6,7,8's. Part 1 of this bloody affair really makes us want to wiggle our big toes. If you have anything else to say now if the f&*kin time! Bang, Bang! This podcast shot us down. Charlie Brown lookalikes recommend you rate, review, and subscribe to the podcast on Stitcher, Podbean, Apple Podcasts, and More! That’s what you get for f*^king around with the Yakuza! Go home to your mother! Tonight, on the Marquee: Silly podcast hosts like to watch Kill Bill: Volume 1 Can’t Whistle…Matt Got Ya. Take a Shot for Every “Foot Shot” or “Iconic/Homage” Kill Bill X Chicago Trauma. Deadly Viper Assassination Squad Names. Post Corona Greetings…Revenge!   Oren X Beatrix BFFs. Got ______ Like Uma Thurman. Matt Cabrera’s 72 Hour Swords. Graceful Badass. Charlie Brown. Gratuitous Amounts of Violence, Poor Little Axe Guy.   “Blank Check and Paper Little Rascals Bonds!”   “B*&ches = “Ruffly Half of Dogs.” “Not on Your Life…No” – The Whole Bloody Affair. “Why not Cap it Off” – Nightcaps Mantra. “Please Use My Pussy Wagon!” “Klingon Proverbs from Slithering Slick.” – Matt Joins the DVAS. “Love Him and His Feats.” “Waiting for the Moment to Kill”- Jonathan Waiting to Kill.   “No Blood on the Udon Bowl.” “Pizza is a Commodity.” Art Provided By: John Cafiero @bonehaver420 Music: "Riviera Jazz" Provided By: Crazy G 

OpenBSD Full disk encryption with coreboot and tianocore, FreeBSD 12.0 EOL, ZFS DVA layout, OpenBSD’s Go situation, AD updates requires changes in TrueNAS and FreeNAS, full name of FreeBSD’s root account, and more. Headlines OpenBSD Full Disk Encryption with CoreBoot and Tianocore Payload (https://functionallyparanoid.com/2020/03/07/openbsd-full-disk-encryption-with-coreboot-and-tianocore-payload/) It has been a while since I have posted here so I wanted to share something that was surprisingly difficult for me to figure out. I have a Thinkpad T440p that I have flashed with Coreboot 4.11 with some special patches that allow the newer machine to work. When I got the laptop, the default BIOS was UEFI and I installed two operating systems. Windows 10 with bitlocker full disk encryption on the “normal” drive (I replaced the spinning 2.5″ disk with an SSD) Ubuntu 19.10 on the m.2 SATA drive that I installed using LUKS full disk encryption I purchased one of those carriers for the optical bay that allows you to install a third SSD and so I did that with the intent of putting OpenBSD on it. Since my other two operating systems were running full disk encryption, I wanted to do the same on OpenBSD. See article for rest of story FreeBSD 12.0 EOL (https://lists.freebsd.org/pipermail/freebsd-announce/2020-February/001930.html) Dear FreeBSD community, As of February 29, 2020, FreeBSD 12.0 will reach end-of-life and will no longer be supported by the FreeBSD Security Team. Users of FreeBSD 12.0 are strongly encouraged to upgrade to a newer release as soon as possible. 12.1 Active release (https://www.freebsd.org/releases/12.1R/announce.html) 12.2 Release Schedule (https://www.freebsd.org/releases/12.2R/schedule.html) News Roundup Some effects of the ZFS DVA format on data layout and growing ZFS pools (https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSDVAFormatAndGrowth) One piece of ZFS terminology is DVA and DVAs, which is short for Data Virtual Address. For ZFS, a DVA is the equivalent of a block number in other filesystems; it tells ZFS where to find whatever data we're talking about. The short summary of what fields DVAs have and what they mean is that DVAs tell us how to find blocks by giving us their vdev (by number) and their byte offset into that particular vdev (and then their size). A typical DVA might say that you find what it's talking about on vdev 0 at byte offset 0x53a40ed000. There are some consequences of this that I hadn't really thought about until the other day. Right away we can see why ZFS has a problem removing a vdev; the vdev's number is burned into every DVA that refers to data on it. If there's no vdev 0 in the pool, ZFS has no idea where to even start looking for data because all addressing is relative to the vdev. ZFS pool shrinking gets around this by adding a translation layer that says where to find the portions of vdev 0 that you care about after it's been removed. Warning! Active Directory Security Changes Require TrueNAS and FreeNAS Updates. (https://www.ixsystems.com/blog/active-directory-truenas-and-freenas/) Critical Information for Current FreeNAS and TrueNAS Users Microsoft is changing the security defaults for Active Directory to eliminate some security vulnerabilities in its protocols. Unfortunately, these new security defaults may disrupt existing FreeNAS/TrueNAS deployments once Windows systems are updated. The Windows updates may appear sometime in March 2020; no official date has been announced as of yet. FreeNAS and TrueNAS users that utilize Active Directory should update to version 11.3 (or 11.2-U8) to avoid potential disruption of their networks when updating to the latest versions of Windows software after March 1, 2020. Version 11.3 has been released and version 11.2-U8 will be available in early March. Full name of the FreeBSD Root Account (https://www.geeklan.co.uk/?p=2457) NetBSD now has a users(7) and groups(7) manual. Looking into what entries existed in the passwd and group files I wondered about root’s full name who we now know as Charlie Root in the BSDs.... OpenBSD Go Situation (https://utcc.utoronto.ca/~cks/space/blog/programming/GoOpenBSDSituation) Over in the fediverse, Pete Zaitcev had a reaction to my entry on OpenBSD versus Prometheus for us: I don't think the situation is usually that bad. Our situation with Prometheus is basically a worst case scenario for Go on OpenBSD, and most people will have much better results, especially if you stick to supported OpenBSD versions. If you stick to supported OpenBSD versions, upgrading your machines as older OpenBSD releases fall out of support (as the OpenBSD people want you to do), you should not have any problems with your own Go programs. The latest Go release will support the currently supported OpenBSD versions (as long as OpenBSD remains a supported platform for Go), and the Go 1.0 compatibility guarantee means that you can always rebuild your current Go programs with newer versions of Go. You might have problems with compiled binaries that you don't want to rebuild, but my understanding is that this is the case for OpenBSD in general; it doesn't guarantee a stable ABI even for C programs (cf). If you use OpenBSD, you have to be prepared to rebuild your code after OpenBSD upgrades regardless of what language it's written in. Beastie Bits Test your TOR (http://lists.nycbug.org/pipermail/talk/2020-February/018174.html) OPNsense 20.1.1 released (https://opnsense.org/opnsense-20-1-1-released/) pkg for FreeBSD 1.13 (https://svnweb.freebsd.org/ports?view=revision&revision=525794) Feedback/Questions Bostjan writes in about Wireguard (http://dpaste.com/3WKG09D#wrap) Charlie has a followup to wpa_supplicant as lower class citizen (http://dpaste.com/0DDN99Q#wrap) Lars writes about LibreSSL as a positive example (http://dpaste.com/1N12HFB#wrap) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Your browser does not support the HTML5 video tag.

What ZFS blockpointers are, zero-day rewards offered, KDE on FreeBSD status, new FreeBSD core team, NetBSD WiFi refresh, poor man’s CI, and the power of Ctrl+T. ##Headlines What ZFS block pointers are and what’s in them I’ve mentioned ZFS block pointers in the past; for example, when I wrote about some details of ZFS DVAs, I said that DVAs are embedded in block pointers. But I’ve never really looked carefully at what is in block pointers and what that means and implies for ZFS. The very simple way to describe a ZFS block pointer is that it’s what ZFS uses in places where other filesystems would simply put a block number. Just like block numbers but unlike things like ZFS dnodes, a block pointer isn’t a separate on-disk entity; instead it’s an on disk data format and an in memory structure that shows up in other things. To quote from the (draft and old) ZFS on-disk specification (PDF): A block pointer (blkptr_t) is a 128 byte ZFS structure used to physically locate, verify, and describe blocks of data on disk. Block pointers are embedded in any ZFS on disk structure that points directly to other disk blocks, both for data and metadata. For instance, the dnode for a file contains block pointers that refer to either its data blocks (if it’s small enough) or indirect blocks, as I saw in this entry. However, as I discovered when I paid attention, most things in ZFS only point to dnodes indirectly, by giving their object number (either in a ZFS filesystem or in pool-wide metadata). So what’s in a block pointer itself? You can find the technical details for modern ZFS in spa.h, so I’m going to give a sort of summary. A regular block pointer contains: various metadata and flags about what the block pointer is for and what parts of it mean, including what type of object it points to. Up to three DVAs that say where to actually find the data on disk. There can be more than one DVA because you may have set the copies property to 2 or 3, or this may be metadata (which normally has two copies and may have more for sufficiently important metadata). The logical size (size before compression) and ‘physical’ size (the nominal size after compression) of the disk block. The physical size can do odd things and is not necessarily the asize (allocated size) for the DVA(s). The txgs that the block was born in, both logically and physically (the physical txg is apparently for dva[0]). The physical txg was added with ZFS deduplication but apparently also shows up in vdev removal. The checksum of the data the block pointer describes. This checksum implicitly covers the entire logical size of the data, and as a result you must read all of the data in order to verify it. This can be an issue on raidz vdevs or if the block had to use gang blocks. Just like basically everything else in ZFS, block pointers don’t have an explicit checksum of their contents. Instead they’re implicitly covered by the checksum of whatever they’re embedded in; the block pointers in a dnode are covered by the overall checksum of the dnode, for example. Block pointers must include a checksum for the data they point to because such data is ‘out of line’ for the containing object. (The block pointers in a dnode don’t necessarily point straight to data. If there’s more than a bit of data in whatever the dnode covers, the dnode’s block pointers will instead point to some level of indirect block, which itself has some number of block pointers.) There is a special type of block pointer called an embedded block pointer. Embedded block pointers directly contain up to 112 bytes of data; apart from the data, they contain only the metadata fields and a logical birth txg. As with conventional block pointers, this data is implicitly covered by the checksum of the containing object. Since block pointers directly contain the address of things on disk (in the form of DVAs), they have to change any time that address changes, which means any time ZFS does its copy on write thing. This forces a change in whatever contains the block pointer, which in turn ripples up to another block pointer (whatever points to said containing thing), and so on until we eventually reach the Meta Object Set and the uberblock. How this works is a bit complicated, but ZFS is designed to generally make this a relatively shallow change with not many levels of things involved (as I discovered recently). As far as I understand things, the logical birth txg of a block pointer is the transaction group in which the block pointer was allocated. Because of ZFS’s copy on write principle, this means that nothing underneath the block pointer has been updated or changed since that txg; if something changed, it would have been written to a new place on disk, which would have forced a change in at least one DVA and thus a ripple of updates that would update the logical birth txg. However, this doesn’t quite mean what I used to think it meant because of ZFS’s level of indirection. If you change a file by writing data to it, you will change some of the file’s block pointers, updating their logical birth txg, and you will change the file’s dnode. However, you won’t change any block pointers and thus any logical birth txgs for the filesystem directory the file is in (or anything else up the directory tree), because the directory refers to the file through its object number, not by directly pointing to its dnode. You can still use logical birth txgs to efficiently find changes from one txg to another, but you won’t necessarily get a filesystem level view of these changes; instead, as far as I can see, you will basically get a view of what object(s) in a filesystem changed (effectively, what inode numbers changed). (ZFS has an interesting hack to make things like ‘zfs diff’ work far more efficiently than you would expect in light of this, but that’s going to take yet another entry to cover.) ###Rewards of Up to $500,000 Offered for FreeBSD, OpenBSD, NetBSD, Linux Zero-Days Exploit broker Zerodium is offering rewards of up to $500,000 for zero-days in UNIX-based operating systems like OpenBSD, FreeBSD, NetBSD, but also for Linux distros such as Ubuntu, CentOS, Debian, and Tails. The offer, first advertised via Twitter earlier this week, is available as part of the company’s latest zero-day acquisition drive. Zerodium is known for buying zero-days and selling them to government agencies and law enforcement. The company runs a regular zero-day acquisition program through its website, but it often holds special drives with more substantial rewards when it needs zero-days of a specific category. BSD zero-day rewards will be on par with Linux payouts The US-based company held a previous drive with increased rewards for Linux zero-days in February, with rewards going as high as $45,000. In another zero-day acquisition drive announced on Twitter this week, the company said it was looking again for Linux zero-days, but also for exploits targeting BSD systems. This time around, rewards can go up to $500,000, for the right exploit. Zerodium told Bleeping Computer they’ll be aligning the temporary rewards for BSD systems with their usual payouts for Linux distros. The company’s usual payouts for Linux privilege escalation exploits can range from $10,000 to $30,000. Local privilege escalation (LPE) rewards can even reach $100,000 for “an exploit with an exceptional quality and coverage,” such as, for example, a Linux kernel exploit affecting all major distributions. Payouts for Linux remote code execution (RCE) exploits can bring in from $50,000 to $500,000 depending on the targeted software/service and its market share. The highest rewards are usually awarded for LPEs and RCEs affecting CentOS and Ubuntu distros. Zero-day price varies based on exploitation chain The acquisition price of a submitted zero-day is directly tied to its requirements in terms of user interaction (no click, one click, two clicks, etc.), Zerodium said. Other factors include the exploit reliability, its success rate, the number of vulnerabilities chained together for the final exploit to work (more chained bugs means more chances for the exploit to break unexpectedly), and the OS configuration needed for the exploit to work (exploits are valued more if they work against default OS configs). Zero-days in servers “can reach exceptional amounts” “Price difference between systems is mostly driven by market shares,” Zerodium founder Chaouki Bekrar told Bleeping Computer via email. Asked about the logic behind these acquisition drives that pay increased rewards, Bekrar told Bleeping Computer the following: "Our aim is to always have, at any time, two or more fully functional exploits for every major software, hardware, or operating systems, meaning that from time to time we would promote a specific software/system on our social media to acquire new codes and strengthen our existing capabilities or extend them.” “We may also react to customers’ requests and their operational needs,” Bekrar said. It’s becoming a crowded market Since Zerodium drew everyone’s attention to the exploit brokerage market in 2015, the market has gotten more and more crowded, but also more sleazy, with some companies being accused of selling zero-days to government agencies in countries with oppressive or dictatorial regimes, where they are often used against political oponents, journalists, and dissidents, instead of going after real criminals. The latest company who broke into the zero-day brokerage market is Crowdfense, who recently launched an acquisition program with prizes of $10 million, of which it already paid $4.5 million to researchers. Twitter Announcement Digital Ocean http://do.co/bsdnow ###KDE on FreeBSD – June 2018 The KDE-FreeBSD team (a half-dozen hardy individuals, with varying backgrounds and varying degrees of involvement depending on how employment is doing) has a status message in the #kde-freebsd channel on freenode. Right now it looks like this: http://FreeBSD.kde.org | Bleeding edge http://FreeBSD.kde.org/area51.php | Released: Qt 5.10.1, KDE SC 4.14.3, KF5 5.46.0, Applications 18.04.1, Plasma-5.12.5, Kdevelop-5.2.1, Digikam-5.9.0 It’s been a while since I wrote about KDE on FreeBSD, what with Calamares and third-party software happening as well. We’re better at keeping the IRC topic up-to-date than a lot of other sources of information (e.g. the FreeBSD quarterly reports, or the f.k.o website, which I’ll just dash off and update after writing this). In no particular order: Qt 5.10 is here, in a FrankenEngine incarnation: we still use WebEnging from Qt 5.9 because — like I’ve said before — WebEngine is such a gigantic pain in the butt to update with all the necessary patches to get it to compile. Our collection of downstream patches to Qt 5.10 is growing, slowly. None of them are upstreamable (e.g. libressl support) though. KDE Frameworks releases are generally pushed to ports within a week or two of release. Actually, now that there is a bigger stack of KDE software in FreeBSD ports the updates take longer because we have to do exp-runs. Similarly, Applications and Plasma releases are reasonably up-to-date. We dodged a bullet by not jumping on Plasma 5.13 right away, I see. Tobias is the person doing almost all of the drudge-work of these updates, he deserves a pint of something in Vienna this summer. The freebsd.kde.org website has been slightly updated; it was terribly out-of-date. So we’re mostly-up-to-date, and mostly all packaged up and ready to go. Much of my day is spent in VMs packaged by other people, but it’s good to have a full KDE developer environment outside of them as well. (PS. Gotta hand it to Tomasz for the amazing application for downloading and displaying a flamingo … niche usecases FTW) ##News Roundup New FreeBSD Core Team Elected Active committers to the project have elected your tenth FreeBSD Core Team. Allan Jude (allanjude) Benedict Reuschling (bcr) Brooks Davis (brooks) Hiroki Sato (hrs) Jeff Roberson (jeff) John Baldwin (jhb) Kris Moore (kmoore) Sean Chittenden (seanc) Warner Losh (imp) Let’s extend our gratitude to the outgoing Core Team members: Baptiste Daroussin (bapt) Benno Rice (benno) Ed Maste (emaste) George V. Neville-Neil (gnn) Matthew Seaman (matthew) Matthew, after having served as the Core Team Secretary for the past four years, will be stepping down from that role. The Core Team would also like to thank Dag-Erling Smørgrav for running a flawless election. To read about the responsibilities of the Core Team, refer to https://www.freebsd.org/administration.html#t-core. ###NetBSD WiFi refresh The NetBSD Foundation is pleased to announce a summer 2018 contract with Philip Nelson (phil%NetBSD.org@localhost) to update the IEEE 802.11 stack basing the update on the FreeBSD current code. The goals of the project are: Minimizing the differences between the FreeBSD and NetBSD IEEE 802.11 stack so future updates are easier. Adding support for the newer protocols 801.11/N and 802.11/AC. Improving SMP support in the IEEE 802.11 stack. Adding Virtual Access Point (VAP) support. Updating as many NIC drivers as time permits for the updated IEEE 802.11 stack and VAP changes. Status reports will be posted to tech-net%NetBSD.org@localhost every other week while the contract is active. iXsystems ###Poor Man’s CI - Hosted CI for BSD with shell scripting and duct tape Poor Man’s CI (PMCI - Poor Man’s Continuous Integration) is a collection of scripts that taken together work as a simple CI solution that runs on Google Cloud. While there are many advanced hosted CI systems today, and many of them are free for open source projects, none of them seem to offer a solution for the BSD operating systems (FreeBSD, NetBSD, OpenBSD, etc.) The architecture of Poor Man’s CI is system agnostic. However in the implementation provided in this repository the only supported systems are FreeBSD and NetBSD. Support for additional systems is possible. Poor Man’s CI runs on the Google Cloud. It is possible to set it up so that the service fits within the Google Cloud “Always Free” limits. In doing so the provided CI is not only hosted, but is also free! (Disclaimer: I am not affiliated with Google and do not otherwise endorse their products.) ARCHITECTURE A CI solution listens for “commit” (or more usually “push”) events, builds the associated repository at the appropriate place in its history and reports the results. Poor Man’s CI implements this very basic CI scenario using a simple architecture, which we present in this section. Poor Man’s CI consists of the following components and their interactions: Controller: Controls the overall process of accepting GitHub push events and starting builds. The Controller runs in the Cloud Functions environment and is implemented by the files in the controller source directory. It consists of the following components: Listener: Listens for GitHub push events and posts them as work messages to the workq PubSub. Dispatcher: Receives work messages from the workq PubSub and a free instance name from the Builder Pool. It instantiates a builder instance named name in the Compute Engine environment and passes it the link of a repository to build. Collector: Receives done messages from the doneq PubSub and posts the freed instance name back to the Builder Pool. PubSub Topics: workq: Transports work messages that contain the link of the repository to build. poolq: Implements the Builder Pool, which contains the name’s of available builder instances. To acquire a builder name, pull a message from the poolq. To release a builder name, post it back into the poolq. doneq: Transports done messages (builder instance terminate and delete events). These message contain the name of freed builder instances. builder: A builder is a Compute Engine instance that performs a build of a repository and shuts down when the build is complete. A builder is instantiated from a VM image and a startx (startup-exit) script. Build Logs: A Storage bucket that contains the logs of builds performed by builder instances. Logging Sink: A Logging Sink captures builder instance terminate and delete events and posts them into the doneq. BUGS The Builder Pool is currently implemented as a PubSub; messages in the PubSub contain the names of available builder instances. Unfortunately a PubSub retains its messages for a maximum of 7 days. It is therefore possible that messages will be discarded and that your PMCI deployment will suddenly find itself out of builder instances. If this happens you can reseed the Builder Pool by running the commands below. However this is a serious BUG that should be fixed. For a related discussion see https://tinyurl.com/ybkycuub. $ ./pmci queuepost poolq builder0 # ./pmci queuepost poolq builder1 # ... repeat for as many builders as you want The Dispatcher is implemented as a Retry Background Cloud Function. It accepts work messages from the workq and attempts to pull a free name from the poolq. If that fails it returns an error, which instructs the infrastructure to retry. Because the infrastructure does not provide any retry controls, this currently happens immediately and the Dispatcher spins unproductively. This is currently mitigated by a “sleep” (setTimeout), but the Cloud Functions system still counts the Function as running and charges it accordingly. While this fits within the “Always Free” limits, it is something that should eventually be fixed (perhaps by the PubSub team). For a related discussion see https://tinyurl.com/yb2vbwfd. ###The Power of Ctrl-T Did you know that you can check what a process is doing by pressing CTRL+T? Has it happened to you before that you were waiting for something to be finished that can take a lot of time, but there is no easy way to check the status. Like a dd, cp, mv and many others. All you have to do is press CTRL+T where the process is running. This will output what’s happening and will not interrupt or mess with it in any way. This causes the operating system to output the SIGINFO signal. On FreeBSD it looks like this: ping pingtest.com PING pingtest.com (5.22.149.135): 56 data bytes 64 bytes from 5.22.149.135: icmpseq=0 ttl=51 time=86.232 ms 64 bytes from 5.22.149.135: icmpseq=1 ttl=51 time=85.477 ms 64 bytes from 5.22.149.135: icmpseq=2 ttl=51 time=85.493 ms 64 bytes from 5.22.149.135: icmpseq=3 ttl=51 time=85.211 ms 64 bytes from 5.22.149.135: icmpseq=4 ttl=51 time=86.002 ms load: 1.12 cmd: ping 94371 [select] 4.70r 0.00u 0.00s 0% 2500k 5/5 packets received (100.0%) 85.211 min / 85.683 avg / 86.232 max 64 bytes from 5.22.149.135: icmpseq=5 ttl=51 time=85.725 ms 64 bytes from 5.22.149.135: icmp_seq=6 ttl=51 time=85.510 ms As you can see it not only outputs the name of the running command but the following parameters as well: 94371 – PID 4.70r – since when is the process running 0.00u – user time 0.00s – system time 0% – CPU usage 2500k – resident set size of the process or RSS `` > An even better example is with the following cp command: cp FreeBSD-11.1-RELEASE-amd64-dvd1.iso /dev/null load: 0.99 cmd: cp 94412 [runnable] 1.61r 0.00u 0.39s 3% 3100k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 15% load: 0.91 cmd: cp 94412 [runnable] 2.91r 0.00u 0.80s 6% 3104k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 32% load: 0.91 cmd: cp 94412 [runnable] 4.20r 0.00u 1.23s 9% 3104k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 49% load: 0.91 cmd: cp 94412 [runnable] 5.43r 0.00u 1.64s 11% 3104k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 64% load: 1.07 cmd: cp 94412 [runnable] 6.65r 0.00u 2.05s 13% 3104k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 79% load: 1.07 cmd: cp 94412 [runnable] 7.87r 0.00u 2.43s 15% 3104k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 95% > I prcessed CTRL+T six times. Without that, all the output would have been is the first line. > Another example how the process is changing states: wget https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/11.1/FreeBSD-11.1-RELEASE-amd64-dvd1.iso –2018-06-17 18:47:48– https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/11.1/FreeBSD-11.1-RELEASE-amd64-dvd1.iso Resolving download.freebsd.org (download.freebsd.org)… 96.47.72.72, 2610:1c1:1:606c::15:0 Connecting to download.freebsd.org (download.freebsd.org)|96.47.72.72|:443… connected. HTTP request sent, awaiting response… 200 OK Length: 3348465664 (3.1G) [application/octet-stream] Saving to: ‘FreeBSD-11.1-RELEASE-amd64-dvd1.iso’ FreeBSD-11.1-RELEASE-amd64-dvd1.iso 1%[> ] 41.04M 527KB/s eta 26m 49sload: 4.95 cmd: wget 10152 waiting 0.48u 0.72s FreeBSD-11.1-RELEASE-amd64-dvd1.iso 1%[> ] 49.41M 659KB/s eta 25m 29sload: 12.64 cmd: wget 10152 waiting 0.55u 0.85s FreeBSD-11.1-RELEASE-amd64-dvd1.iso 2%[=> ] 75.58M 6.31MB/s eta 20m 6s load: 11.71 cmd: wget 10152 running 0.73u 1.19s FreeBSD-11.1-RELEASE-amd64-dvd1.iso 2%[=> ] 85.63M 6.83MB/s eta 18m 58sload: 11.71 cmd: wget 10152 waiting 0.80u 1.32s FreeBSD-11.1-RELEASE-amd64-dvd1.iso 14%[==============> ] 460.23M 7.01MB/s eta 9m 0s 1 > The bad news is that CTRl+T doesn’t work with Linux kernel, but you can use it on MacOS/OS-X: —> Fetching distfiles for gmp —> Attempting to fetch gmp-6.1.2.tar.bz2 from https://distfiles.macports.org/gmp —> Verifying checksums for gmp —> Extracting gmp —> Applying patches to gmp —> Configuring gmp load: 2.81 cmd: clang 74287 running 0.31u 0.28s > PS: If I recall correctly Feld showed me CTRL+T, thank you! Beastie Bits Half billion tries for a HAMMER2 bug (http://lists.dragonflybsd.org/pipermail/commits/2018-May/672263.html) OpenBSD with various Desktops OpenBSD 6.3 running twm window manager (https://youtu.be/v6XeC5wU2s4) OpenBSD 6.3 jwm and rox desktop (https://youtu.be/jlSK2oi7CBc) OpenBSD 6.3 cwm youtube video (https://youtu.be/mgqNyrP2CPs) pf: Increase default state table size (https://svnweb.freebsd.org/base?view=revision&revision=336221) *** Tarsnap Feedback/Questions Ben Sims - Full feed? (http://dpaste.com/3XVH91T#wrap) Scott - Questions and Comments (http://dpaste.com/08P34YN#wrap) Troels - Features of FreeBSD 11.2 that deserve a mention (http://dpaste.com/3DDPEC2#wrap) Fred - Show Ideas (http://dpaste.com/296ZA0P#wrap) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) iXsystems It's all NAS (https://www.ixsystems.com/blog/its-all-nas/)

Second round of ZFS improvements in FreeBSD, Postgres finds that non-FreeBSD/non-Illumos systems are corrupting data, interview with Kevin Bowling, BSDCan list of talks, and cryptographic right answers. Headlines [Other big ZFS improvements you might have missed] 9075 Improve ZFS pool import/load process and corrupted pool recovery One of the first tasks during the pool load process is to parse a config provided from userland that describes what devices the pool is composed of. A vdev tree is generated from that config, and then all the vdevs are opened. The Meta Object Set (MOS) of the pool is accessed, and several metadata objects that are necessary to load the pool are read. The exact configuration of the pool is also stored inside the MOS. Since the configuration provided from userland is external and might not accurately describe the vdev tree of the pool at the txg that is being loaded, it cannot be relied upon to safely operate the pool. For that reason, the configuration in the MOS is read early on. In the past, the two configurations were compared together and if there was a mismatch then the load process was aborted and an error was returned. The latter was a good way to ensure a pool does not get corrupted, however it made the pool load process needlessly fragile in cases where the vdev configuration changed or the userland configuration was outdated. Since the MOS is stored in 3 copies, the configuration provided by userland doesn't have to be perfect in order to read its contents. Hence, a new approach has been adopted: The pool is first opened with the untrusted userland configuration just so that the real configuration can be read from the MOS. The trusted MOS configuration is then used to generate a new vdev tree and the pool is re-opened. When the pool is opened with an untrusted configuration, writes are disabled to avoid accidentally damaging it. During reads, some sanity checks are performed on block pointers to see if each DVA points to a known vdev; when the configuration is untrusted, instead of panicking the system if those checks fail we simply avoid issuing reads to the invalid DVAs. This new two-step pool load process now allows rewinding pools across vdev tree changes such as device replacement, addition, etc. Loading a pool from an external config file in a clustering environment also becomes much safer now since the pool will import even if the config is outdated and didn't, for instance, register a recent device addition. With this code in place, it became relatively easy to implement a long-sought-after feature: the ability to import a pool with missing top level (i.e. non-redundant) devices. Note that since this almost guarantees some loss Of data, this feature is for now restricted to a read-only import. 7614 zfs device evacuation/removal This project allows top-level vdevs to be removed from the storage pool with “zpool remove”, reducing the total amount of storage in the pool. This operation copies all allocated regions of the device to be removed onto other devices, recording the mapping from old to new location. After the removal is complete, read and free operations to the removed (now “indirect”) vdev must be remapped and performed at the new location on disk. The indirect mapping table is kept in memory whenever the pool is loaded, so there is minimal performance overhead when doing operations on the indirect vdev. The size of the in-memory mapping table will be reduced when its entries become “obsolete” because they are no longer used by any block pointers in the pool. An entry becomes obsolete when all the blocks that use it are freed. An entry can also become obsolete when all the snapshots that reference it are deleted, and the block pointers that reference it have been “remapped” in all filesystems/zvols (and clones). Whenever an indirect block is written, all the block pointers in it will be “remapped” to their new (concrete) locations if possible. This process can be accelerated by using the “zfs remap” command to proactively rewrite all indirect blocks that reference indirect (removed) vdevs. Note that when a device is removed, we do not verify the checksum of the data that is copied. This makes the process much faster, but if it were used on redundant vdevs (i.e. mirror or raidz vdevs), it would be possible to copy the wrong data, when we have the correct data on e.g. the other side of the mirror. Therefore, mirror and raidz devices can not be removed. You can use ‘zpool detach’ to downgrade a mirror to a single top-level device, so that you can then remove it 7446 zpool create should support efi system partition This one was not actually merged into FreeBSD, as it doesn’t apply currently, but I would like to switch the way FreeBSD deals with full disks to be closer to IllumOS to make automatic spare replacement a hands-off operation. Since we support whole-disk configuration for boot pool, we also will need whole disk support with UEFI boot and for this, zpool create should create efi-system partition. I have borrowed the idea from oracle solaris, and introducing zpool create -B switch to provide an way to specify that boot partition should be created. However, there is still an question, how big should the system partition be. For time being, I have set default size 256MB (thats minimum size for FAT32 with 4k blocks). To support custom size, the set on creation "bootsize" property is created and so the custom size can be set as: zpool create -B -o bootsize=34MB rpool c0t0d0. After the pool is created, the "bootsize" property is read only. When -B switch is not used, the bootsize defaults to 0 and is shown in zpool get output with no value. Older zfs/zpool implementations can ignore this property. **Digital Ocean** PostgreSQL developers find that every operating system other than FreeBSD and IllumOS might corrupt your data Some time ago I ran into an issue where a user encountered data corruption after a storage error. PostgreSQL played a part in that corruption by allowing checkpoint what should've been a fatal error. TL;DR: Pg should PANIC on fsync() EIO return. Retrying fsync() is not OK at least on Linux. When fsync() returns success it means "all writes since the last fsync have hit disk" but we assume it means "all writes since the last SUCCESSFUL fsync have hit disk". Pg wrote some blocks, which went to OS dirty buffers for writeback. Writeback failed due to an underlying storage error. The block I/O layer and XFS marked the writeback page as failed (ASEIO), but had no way to tell the app about the failure. When Pg called fsync() on the FD during the next checkpoint, fsync() returned EIO because of the flagged page, to tell Pg that a previous async write failed. Pg treated the checkpoint as failed and didn't advance the redo start position in the control file. + All good so far. But then we retried the checkpoint, which retried the fsync(). The retry succeeded, because the prior fsync() *cleared the ASEIO bad page flag*. The write never made it to disk, but we completed the checkpoint, and merrily carried on our way. Whoops, data loss. The clear-error-and-continue behaviour of fsync is not documented as far as I can tell. Nor is fsync() returning EIO unless you have a very new linux man-pages with the patch I wrote to add it. But from what I can see in the POSIX standard we are not given any guarantees about what happens on fsync() failure at all, so we're probably wrong to assume that retrying fsync() is safe. We already PANIC on fsync() failure for WAL segments. We just need to do the same for data forks at least for EIO. This isn't as bad as it seems because AFAICS fsync only returns EIO in cases where we should be stopping the world anyway, and many FSes will do that for us. + Upon further looking, it turns out it is not just Linux brain damage: Apparently I was too optimistic. I had looked only at FreeBSD, which keeps the page around and dirties it so we can retry, but the other BSDs apparently don't (FreeBSD changed that in 1999). From what I can tell from the sources below, we have: Linux, OpenBSD, NetBSD: retrying fsync() after EIO lies FreeBSD, Illumos: retrying fsync() after EIO tells the truth + NetBSD PR to solve the issues + I/O errors are not reported back to fsync at all. + Write errors during genfs_putpages that fail for any reason other than ENOMEM cause the data to be semi-silently discarded. + It appears that UVM pages are marked clean when they're selected to be written out, not after the write succeeds; so there are a bunch of potential races when writes fail. + It appears that write errors for buffercache buffers are semi-silently discarded as well. Interview - Kevin Bowling: Senior Manager Engineering of LimeLight Networks - kbowling@llnw.com / @kevinbowling1 BR: How did you first get introduced to UNIX and BSD? AJ: What got you started contributing to an open source project? BR: What sorts of things have you worked on it the past? AJ: Tell us a bit about LimeLight and how they use FreeBSD. BR: What are the biggest advantages of FreeBSD for LimeLight? AJ: What could FreeBSD do better that would benefit LimeLight? BR: What has LimeLight given back to FreeBSD? AJ: What have you been working on more recently? BR: What do you find to be the most valuable part of open source? AJ: Where do you think the most improvement in open source is needed? BR: Tell us a bit about your computing history collection. What are your three favourite pieces? AJ: How do you keep motivated to work on Open Source? BR: What do you do for fun? AJ: Anything else you want to mention? News Roundup BSDCan 2018 Selected Talks The schedule for BSDCan is up Lots of interesting content, we are looking forward to it We hope to see lots of you there. Make sure you come introduce yourselves to us. Don’t be shy. Remember, if this is your first BSDCan, checkout the newbie session on Thursday night. It’ll help you get to know a few people so you have someone you can ask for guidance. Also, check out the hallway track, the tables, and come to the hacker lounge. iXsystems Cryptographic Right Answers Crypto can be confusing. We all know we shouldn’t roll our own, but what should we use? Well, some developers have tried to answer that question over the years, keeping an updated list of “Right Answers” 2009: Colin Percival of FreeBSD 2015: Thomas H. Ptacek 2018: Latacora A consultancy that provides “Retained security teams for startups”, where Thomas Ptacek works. We’re less interested in empowering developers and a lot more pessimistic about the prospects of getting this stuff right. There are, in the literature and in the most sophisticated modern systems, “better” answers for many of these items. If you’re building for low-footprint embedded systems, you can use STROBE and a sound, modern, authenticated encryption stack entirely out of a single SHA-3-like sponge constructions. You can use NOISE to build a secure transport protocol with its own AKE. Speaking of AKEs, there are, like, 30 different password AKEs you could choose from. But if you’re a developer and not a cryptography engineer, you shouldn’t do any of that. You should keep things simple and conventional and easy to analyze; “boring”, as the Google TLS people would say. Cryptographic Right Answers Encrypting Data Percival, 2009: AES-CTR with HMAC. Ptacek, 2015: (1) NaCl/libsodium’s default, (2) ChaCha20-Poly1305, or (3) AES-GCM. Latacora, 2018: KMS or XSalsa20+Poly1305 Symmetric key length Percival, 2009: Use 256-bit keys. Ptacek, 2015: Use 256-bit keys. Latacora, 2018: Go ahead and use 256 bit keys. Symmetric “Signatures” Percival, 2009: Use HMAC. Ptacek, 2015: Yep, use HMAC. Latacora, 2018: Still HMAC. Hashing algorithm Percival, 2009: Use SHA256 (SHA-2). Ptacek, 2015: Use SHA-2. Latacora, 2018: Still SHA-2. Random IDs Percival, 2009: Use 256-bit random numbers. Ptacek, 2015: Use 256-bit random numbers. Latacora, 2018: Use 256-bit random numbers. Password handling Percival, 2009: scrypt or PBKDF2. Ptacek, 2015: In order of preference, use scrypt, bcrypt, and then if nothing else is available PBKDF2. Latacora, 2018: In order of preference, use scrypt, argon2, bcrypt, and then if nothing else is available PBKDF2. Asymmetric encryption Percival, 2009: Use RSAES-OAEP with SHA256 and MGF1+SHA256 bzzrt pop ffssssssst exponent 65537. Ptacek, 2015: Use NaCl/libsodium (box / cryptobox). Latacora, 2018: Use Nacl/libsodium (box / cryptobox). Asymmetric signatures Percival, 2009: Use RSASSA-PSS with SHA256 then MGF1+SHA256 in tricolor systemic silicate orientation. Ptacek, 2015: Use Nacl, Ed25519, or RFC6979. Latacora, 2018: Use Nacl or Ed25519. Diffie-Hellman Percival, 2009: Operate over the 2048-bit Group #14 with a generator of 2. Ptacek, 2015: Probably still DH-2048, or Nacl. Latacora, 2018: Probably nothing. Or use Curve25519. Website security Percival, 2009: Use OpenSSL. Ptacek, 2015: Remains: OpenSSL, or BoringSSL if you can. Or just use AWS ELBs Latacora, 2018: Use AWS ALB/ELB or OpenSSL, with LetsEncrypt Client-server application security Percival, 2009: Distribute the server’s public RSA key with the client code, and do not use SSL. Ptacek, 2015: Use OpenSSL, or BoringSSL if you can. Or just use AWS ELBs Latacora, 2018: Use AWS ALB/ELB or OpenSSL, with LetsEncrypt Online backups Percival, 2009: Use Tarsnap. Ptacek, 2015: Use Tarsnap. Latacora, 2018: Store PMAC-SIV-encrypted arc files to S3 and save fingerprints of your backups to an ERC20-compatible blockchain. Just kidding. You should still use Tarsnap. Seriously though, use Tarsnap. Adding IPv6 to an existing server I am adding IPv6 addresses to each of my servers. This post assumes the server is up and running FreeBSD 11.1 and you already have an IPv6 address block. This does not cover the creation of an IPv6 tunnel, such as that provided by HE.net. This assumes native IPv6. In this post, I am using the IPv6 addresses from the IPv6 Address Prefix Reserved for Documentation (i.e. 2001:DB8::/32). You should use your own addresses. The IPv6 block I have been assigned is 2001:DB8:1001:8d00/64. I added this to /etc/rc.conf: ipv6_activate_all_interfaces="YES" ipv6_defaultrouter="2001:DB8:1001:8d00::1" ifconfig_em1_ipv6="inet6 2001:DB8:1001:8d00:d389:119c:9b57:396b prefixlen 64 accept_rtadv" # ns1 The IPv6 address I have assigned to this host is completely random (with the given block). I found a random IPv6 address generator and used it to select d389:119c:9b57:396b as the address for this service within my address block. I don’t have the reference, but I did read that randomly selecting addresses within your block is a better approach. In order to invoke these changes without rebooting, I issued these commands: ``` [dan@tallboy:~] $ sudo ifconfig em1 inet6 2001:DB8:1001:8d00:d389:119c:9b57:396b prefixlen 64 accept_rtadv [dan@tallboy:~] $ [dan@tallboy:~] $ sudo route add -inet6 default 2001:DB8:1001:8d00::1 add net default: gateway 2001:DB8:1001:8d00::1 ``` If you do the route add first, you will get this error: [dan@tallboy:~] $ sudo route add -inet6 default 2001:DB8:1001:8d00::1 route: writing to routing socket: Network is unreachable add net default: gateway 2001:DB8:1001:8d00::1 fib 0: Network is unreachable Beastie Bits Ghost in the Shell – Part 1 Enabling compression on ZFS - a practical example Modern and secure DevOps on FreeBSD (Goran Mekić) LibreSSL 2.7.0 Released zrepl version 0.0.3 is out! [ZFS User Conference](http://zfs.datto.com/] Tarsnap Feedback/Questions Benjamin - BSD Personal Mailserver Warren - ZFS volume size limit (show #233) Lars - AFRINIC Brad - OpenZFS vs OracleZFS Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

Peter Magnusson ville hjälpa en romsk tiggare till ett bättre liv, men drar istället in honom i ett kidnappningsdrama. Storydox 6/11 2017. Tema: Funnet och försvunnet. 

Winter is here and everyone is either writing exams and completing projects or getting ready for the Holiday Season. In a few short weeks, everyone will be attending some sort of party or celebration. Jared Stuffco created DVAS so that he had an excuse to get out there and party. I found Jared on the mean streets of Toronto. He gave me the lowdown on the DVAS name and how to have a successful “bromance.” We even talk a little yacht-house. You've got to hear it! Tracks played on the show... 1) DVAS, Society "Society" (Original mix) 2) DVAS, "Bromance" (snippet) 3) DVAS, Society "Back 2 Basix" 4) DVAS, Society "Society" (Hood Internet remix ft Kid Static) (partial) 5) DVAS, Society "Fantasy" ALL songs CANCON

3 DVas, LLC presents "3 Women  3 Ways" Topic:  Guest:  3 Women  3 Ways is a radio show that speaks to the general public about current national and international events from the perspective of each of the 3 partner's life experience, most usually related to domestic violence, sexual violence and/or all forms of violence against women and violence in general. Mission Statement: To transform the world's views of Inter-Personal Violence (IPV) and other forms of violence by using our experiences and our multi-disciplinary views in a way that engages perspectives, undertanding, and solutions. Goals: 1) Present current events through our lives' experiences. 2) Raise world awareness and self-awareness about IPV and other forms of violence. 3) Inform all people how IPV and other forms of violence impact everyone. 4) Present resources, ideas, and alternat  

3 DVas, LLC presents "3 Women  3 Ways" Topic: Fathers' Day Celebration Guest: Dee Koester, M.S., Executive Director of WomenSpirit Coalition 3 Women  3 Ways is a radio show that speaks to the general public about current national and international events from the perspective of each of the 3 partner's life experience, most usually related to domestic violence, sexual violence and/or all forms of violence against women and violence in general. Mission Statement: To transform the world's views of Inter-Personal Violence (IPV) and other forms of violence by using our experiences and our multi-disciplinary views in a way that engages perspectives, undertanding, and solutions. Goals: 1) Present current events through our lives' experiences. 2) Raise world awareness and self-awareness about IPV and other forms of violence. 3) Inform all people how IPV and other forms of violence impact everyone. 4) Present resources, ideas, and alternat&l

3 DVas, LLC presents "3 Women  3 Ways" Topic: Sexual Assault Awareness Month Guest: Dee Koester, M.S., Executive Director of WomenSpirit Coalition 3 Women  3 Ways is a radio show that speaks to the general public about current national and international events from the perspective of each of the 3 partner's life experience, most usually related to domestic violence, sexual violence and/or all forms of violence against women and violence in general. Mission Statement: To transform the world's views of Inter-Personal Violence (IPV) and other forms of violence by using our experiences and our multi-disciplinary views in a way that engages perspectives, undertanding, and solutions. Goals: 1) Present current events through our lives' experiences. 2) Raise world awareness and self-awareness about IPV and other forms of violence. 3) Inform all people how IPV and other forms of violence impact everyone. 4) Present resources, ideas, and alternat

3 DVas, LLC presents "3 Women  3 Ways" Topic: Sexual Assault Awareness Month Guest: Dee Koester, M.S., Executive Director of WomenSpirit Coalition 3 Women  3 Ways is a radio show that speaks to the general public about current national and international events from the perspective of each of the 3 partner's life experience, most usually related to domestic violence, sexual violence and/or all forms of violence against women and violence in general. Mission Statement: To transform the world's views of Inter-Personal Violence (IPV) and other forms of violence by using our experiences and our multi-disciplinary views in a way that engages perspectives, undertanding, and solutions. Goals: 1) Present current events through our lives' experiences. 2) Raise world awareness and self-awareness about IPV and other forms of violence. 3) Inform all people how IPV and other forms of violence impact everyone. 4) Present resources, ideas, and alternat

3 DVas, LLC presents "3 Women  3 Ways" Topic: Sexual Assault Awareness Month Guest: Dee Koester, M.S., Executive Director of WomenSpirit Coalition 3 Women  3 Ways is a radio show that speaks to the general public about current national and international events from the perspective of each of the 3 partner's life experience, most usually related to domestic violence, sexual violence and/or all forms of violence against women and violence in general. Mission Statement: To transform the world's views of Inter-Personal Violence (IPV) and other forms of violence by using our experiences and our multi-disciplinary views in a way that engages perspectives, undertanding, and solutions. Goals: 1) Present current events through our lives' experiences. 2) Raise world awareness and self-awareness about IPV and other forms of violence. 3) Inform all people how IPV and other forms of violence impact everyone. 4) Present resources, ideas, and alternat

3 DVas, LLC presents "3 Women  3 Ways" Topic: Epowering Girls & Teens Guest:  Aime Hutton,inspirational speaker, trainer/facilitator, owner of both Awakening Goddess/Wonder Girls Camp and Published Best Selling Author.  3 Women  3 Ways is a radio show that speaks to the general public about current national and international events from the perspective of each of the 3 partner's life experience, most usually related to domestic violence, sexual violence and/or all forms of violence against women and violence in general. Mission Statement: To transform the world's views of Inter-Personal Violence (IPV) and other forms of violence by using our experiences and our multi-disciplinary views in a way that engages perspectives, undertanding, and solutions. Goals: 1) Present current events through our lives' experiences. 2) Raise world awareness and self-awareness about IPV and other forms of violence. 3) Inform all people how IPV and other forms of violence impact everyone. 

3 DVas, LLC presents "3 Women  3 Ways" Topic: Mothers' Day Celebration  Guest:  Lorena Gordon 3 Women  3 Ways is a radio show that speaks to the general public about current national and international events from the perspective of each of the 3 partner's life experience, most usually related to domestic violence, sexual violence and/or all forms of violence against women and violence in general. Mission Statement: To transform the world's views of Inter-Personal Violence (IPV) and other forms of violence by using our experiences and our multi-disciplinary views in a way that engages perspectives, undertanding, and solutions. Goals: 1) Present current events through our lives' experiences. 2) Raise world awareness and self-awareness about IPV and other forms of violence. 3) Inform all people how IPV and other forms of violence impact everyone. 4) Present resources, ideas, and alternat  

3 DVas, LLC presents "3 Women  3 Ways" Topic: Religion and DV Guest: YOU 3 Women  3 Ways is a radio show that speaks to the general public about current national and international events from the perspective of each of the 3 partner's life experience, most usually related to domestic violence, sexual violence and/or all forms of violence against women and violence in general. Mission Statement: To transform the world's views of Inter-Personal Violence (IPV) and other forms of violence by using our experiences and our multi-disciplinary views in a way that engages perspectives, undertanding, and solutions. Goals: 1) Present current events through our lives' experiences. 2) Raise world awareness and self-awareness about IPV and other forms of violence. 3) Inform all people how IPV and other forms of violence impact everyone. 4) Present resources, ideas, and alternat  

3 DVas, LLC presents "3 Women  3 Ways" Topic: Men Engaging in Anti-Violence Work Guest:  Rob Okun, founder of Voice Male Magazine 3 Women  3 Ways is a radio show that speaks to the general public about current national and international events from the perspective of each of the 3 partner's life experience, most usually related to domestic violence, sexual violence and/or all forms of violence against women and violence in general. Mission Statement: To transform the world's views of Inter-Personal Violence (IPV) and other forms of violence by using our experiences and our multi-disciplinary views in a way that engages perspectives, undertanding, and solutions. Goals: 1) Present current events through our lives' experiences. 2) Raise world awareness and self-awareness about IPV and other forms of violence. 3) Inform all people how IPV and other forms of violence impact everyone. 4) Present resources, ideas, and alt

3 DVas, LLC presents "3 Women  3 Ways" Topic: Sexual Assault Awareness Month Guest: Dee Koester, M.S., Executive Director of WomenSpirit Coalition 3 Women  3 Ways is a radio show that speaks to the general public about current national and international events from the perspective of each of the 3 partner's life experience, most usually related to domestic violence, sexual violence and/or all forms of violence against women and violence in general. Mission Statement: To transform the world's views of Inter-Personal Violence (IPV) and other forms of violence by using our experiences and our multi-disciplinary views in a way that engages perspectives, undertanding, and solutions. Goals: 1) Present current events through our lives' experiences. 2) Raise world awareness and self-awareness about IPV and other forms of violence. 3) Inform all people how IPV and other forms of violence impact everyone. 4) Present resources, ideas, and alternat

Adam K's Hotbox Episode 053 | Featuring tracks from Adam K, DVAS, Jon Kong, Chris Lake, Mat Zo, Matthew LeFace & Carlo Astuti, and more. Visit http://djadamk.com/radio for complete tracklistings and previous episodes. http://djadamk.com | http://facebook.com/djadamk

Adam K's Hotbox Episode 052 | Featuring tracks from Adam K, DVAS, PIXL, Jon Kong, Chris Lake, Mat Zo, Zedd, and more. Visit http://djadamk.com/radio for complete tracklistings and previous episodes. http://djadamk.com | http://facebook.com/djadamk

Adam K's Hotbox Episode 051 | Featuring tracks from Adam K, DVAS, PIXL, Jon Kong, and a guest mix from Jay Frog. Visit http://djadamk.com/radio for complete tracklistings and previous episodes. http://djadamk.com | http://facebook.com/djadamk

Adam K's Hotbox Episode 050 | Featuring tracks from Adam K, DVAS, PIXL, Kryder, Wolfgang Gartner, UMEK, and more. Visit http://djadamk.com/radio for complete tracklistings and previous episodes. http://djadamk.com | http://facebook.com/djadamk

Adam K's Hotbox Episode 049 | Featuring tracks from Adam K, DVAS, PIXL, Wolfgang Gartner, Dilemn, Mord Fustang, and more. Visit http://djadamk.com/radio for complete tracklistings and previous episodes. http://djadamk.com | http://facebook.com/djadamk

Adam K's Hotbox Episode 048 | Featuring tracks from Adam K, Mat Zo & Arty, DVAS, PIXL, Wolfgang Gartner, Mord Fustang, and more. Visit http://djadamk.com/radio for complete tracklistings and previous episodes. http://djadamk.com | http://facebook.com/djadamk

Adam K's Hotbox Episode 047 | Featuring a one hour live mix from guest Jay Lumen. Visit http://djadamk.com/radio for complete tracklistings and previous episodes. http://djadamk.com | http://facebook.com/djadamk

Adam K's Hotbox Episode 046 | Featuring tracks from Adam K, Mat Zo & Arty, DVAS, Kaskade, Felguk, Sympho Nympho, and more. Visit http://djadamk.com/radio for complete tracklistings and previous episodes. http://djadamk.com | http://facebook.com/djadamk

Body Language - Work This City (Sammy Bananas Remix) Korallreven - Loved Up (GMGN Remix) Cold Cave - Life Magazine (Optimo Remix) DVAS - Ambient Room (SymbolOne Remix) The Glass - Four Floor Letter (Black Van Mix) The Cardigans - Lovefool (Mr Gaspar Remix) Cinnamon Chasers - I Like Watching You (Diamond Cut Remix) Underworld - Always Loved A Film