Podcast appearances and mentions of joshua stein

Professor Joshua Stein talks about his new book about the television series The West Wing, which premiered 25 years ago.

Thu, 23 May 2024 19:30:00 GMT http://relay.fm/rd/235 http://relay.fm/rd/235 Red Thing Get Hot 235 Merlin Mann and John Siracusa John thinks Merlin drinks too much water, which naturally leads to a deep dive on the landscape of consumer ice machines. John thinks Merlin drinks too much water, which naturally leads to a deep dive on the landscape of consumer ice machines. clean 5400 John thinks Merlin drinks too much water, which naturally leads to a deep dive on the landscape of consumer ice machines. This episode of Reconcilable Differences is sponsored by: Squarespace: Save 10% off your first purchase of a website or domain using code DIFFS. Links and Show Notes: Things kick off with some initial concerns, and then Merlin shares why so many things are kind of like a television. In Follow-Up, John has confused his retired newscasters, and Merlin still hasn't figured why he was so disoriented by a strange oven. Werner Herzog cameos are considered. Next, Merlin has a confession that reflects the logical conclusion of realizing you can always augment the sub-standard materials supplied by a host. Painful rituals of car seats and Catholicism are considered, and John indulges Merlin's retrospective look at 15th century gift cards for sin. John thinks Merlin drinks too much water, which naturally leads to a deep dive on the landscape of consumer ice machines. (Recorded on Tuesday, May 14, 2024) “Irish Breakfast” (August 19, 2012) Credits Audio Editor: Jim Metzendorf Admin Assistance: Kerry Provenzano Music: Merlin Mann The Suits: Stephen Hackett, Myke Hurley Get an ad-free version of the show, plus a monthly extended episode. jcs.org - Joshua Stein's cool website about classic Mac stuff Flying Toasters in CSS Howdy Doody on 99% Invisible John's stovetop dial Two-sided stovetop dial Electric glass stovetops on Technology Connections Water intoxication GE pellet ice machine John's terrible ice machine Drop & Run Best of Werner Herzog - YouTube Slime in

Thu, 23 May 2024 19:30:00 GMT http://relay.fm/rd/235 http://relay.fm/rd/235 Merlin Mann and John Siracusa John thinks Merlin drinks too much water, which naturally leads to a deep dive on the landscape of consumer ice machines. John thinks Merlin drinks too much water, which naturally leads to a deep dive on the landscape of consumer ice machines. clean 5400 John thinks Merlin drinks too much water, which naturally leads to a deep dive on the landscape of consumer ice machines. This episode of Reconcilable Differences is sponsored by: Squarespace: Save 10% off your first purchase of a website or domain using code DIFFS. Links and Show Notes: Things kick off with some initial concerns, and then Merlin shares why so many things are kind of like a television. In Follow-Up, John has confused his retired newscasters, and Merlin still hasn't figured why he was so disoriented by a strange oven. Werner Herzog cameos are considered. Next, Merlin has a confession that reflects the logical conclusion of realizing you can always augment the sub-standard materials supplied by a host. Painful rituals of car seats and Catholicism are considered, and John indulges Merlin's retrospective look at 15th century gift cards for sin. John thinks Merlin drinks too much water, which naturally leads to a deep dive on the landscape of consumer ice machines. (Recorded on Tuesday, May 14, 2024) “Irish Breakfast” (August 19, 2012) Credits Audio Editor: Jim Metzendorf Admin Assistance: Kerry Provenzano Music: Merlin Mann The Suits: Stephen Hackett, Myke Hurley Get an ad-free version of the show, plus a monthly extended episode. jcs.org - Joshua Stein's cool website about classic Mac stuff Flying Toasters in CSS Howdy Doody on 99% Invisible John's stovetop dial Two-sided stovetop dial Electric glass stovetops on Technology Connections Water intoxication GE pellet ice machine John's terrible ice machine Drop & Run Best of Werner Herzog - YouTube

Episode 99 of Sports ‘N Torts is a special one! Parag Shah – CEO of Miles Mediation and Arbitration – issued a challenged. If we could raise $10,000 to support Side by Side Clubhouse he would come on the podcast and shave his head live! Well, thanks to all of your generosity we raised over $25,000!! Amazing. The donations came in from two camps: the Snip Squad (those who wanted to shave Parag’s hair) and the Lock Lovers (those who wanted to save Parag’s hair). In the end, both camps raised over $10,000 so we were left with no choice but to take the issue to Judge Hydrick from the Superior Court of Dekalb County for a ruling on who win’s … Judge Hydrick issued an Order in favor of the Snip Squad so Parag’s head was shaved live on the podcast! Chris the Barber put Parag in the chair and gave him a nice clean shave. Parag has been growing his hair since 2019 so this was an epic and emotional event. We even hear from Parag's wife as she watches his beautiful hair being cut off. Charity and charitable giving is a big part of Parag’s life. As a lawyer, judge and TV personality, Parag talks about his background and rising to the CEO of Miles. He discusses the business, their mission, and their charitable arm – Miles for Smiles. Parag discusses when, why and how Side by Side became important to him and the ways in which he participates with their members. Side by Side Clubhouse (www.sidebysideclubhouse.org) is the only work-oriented day program in Georgia that specifically supports adults with brain injuries and their families. Their Executive Director, Josh Blackmon, joined the podcast to talk about his background, what brought him to Side by Side, the mission of the organization and how they will put the funds raised to good use. We even heard from the “Mayor of Side By Side” JR Copeland about his story and how Side by Side saved his life. There are some parts of the podcast that dont come through great but you can see the live video on the “Joshua Stein” Facebook page and also on the J. Stein Law Firm You Tube Page. It’s a great watch if I say so myself. What a memorable episode for a great cause! As always, this episode is powered by the J. Stein Law Firm a personal injury law firm in Atlanta, Ga – www.jsteinlawfirm.com

Different Christian denominations hold varying views on multiple topics. Over the past two thousand years, these doctrinal differences have often generated conflict, even to the point of religious wars. Despite huge variations in belief on some topics, however, one thing all Christian denominations agree on is that Jesus is the Son of God and the third person of the Trinity. They also believe that Jesus is the Christ—from the Greek chrīstós, a translation from the Hebrew Mašíaḥ, (messiah), meaning “anointed one.” But what do the Jewish people think about this? How does Judaism regard the Christian claim that Jesus is also the Hebrew Messiah? And how do practitioners of the Jewish religion, today, regard the historical figure of Jesus in general?  On this episode of the podcast, the hosts welcome back guest Joshua Stein, to discuss how Jews regard Jesus. Stein currently holds a postdoctoral fellowship at the Georgetown Institute for the Study of Markets and Ethics. His work focuses on intersections between moral, economic, and political theories and their practical application to social interactions between people and social institutions.  You can read more about this topic, and read some of Stein's writing, in these links: “What Do Jews Believe About Jesus?” by My Jewish Learning https://www.myjewishlearning.com/article/what-do-jews-believe-about-jesus/ “Six Reasons Why Jews Don't Believe in Jesus,” by Julius Ciss https://jewsforjudaism.org/knowledge/videos/six-reasons-why-jews-don-t-believe-in-jesus “Behold! The Jewish Jesus,” by Howard Jacobson https://www.theguardian.com/world/2009/jan/09/christianity-judaism “Why do we call Jesus the Messiah?” A U.S. Catholic interview https://uscatholic.org/articles/201712/why-do-we-call-jesus-the-messiah/ “Should Catholics celebrate Passover?” by Joshua Stein https://uscatholic.org/articles/202304/should-catholics-celebrate-passover/ Glad You Asked is sponsored by the Claretian Missionaries. https://claretiansusa.org/

James and John discuss eBay finds: Mac Portable battery with original packaging, Mac 512k set with boxes, and Dr. Martin Luther King Think Different proof poster. They checkout some recent RR Auction Apple related auctions, and news includes Joshua Stein's Mac Portable with Wi-Fi and Action Retro's Macintosh TVs. Join our Facebook page, follow us on Twitter, watch us on YouTube, and visit us at RetroMacCast.

Today, many Catholics as well as Christians of other denominations admire and enjoy Jewish traditions and rituals. But it hasn't always been that way. For centuries, Christians in different times, places, and cultures persecuted Jewish people, even to the point of forbidding the practice of Judaism.  In the Middle Ages, hateful rhetoric about Jewish people and the Jewish faith sometimes prompted pogroms––organized mob attacks––especially during the Christian Holy Week. In Catholic Spain, in the 15th century, Jews were forced to convert to Christianity, and those who refused to do so were expelled from their homes. In Europe in the 19th century, as the Jewish people gained greater freedom and political emancipation, new prejudices arose, including conspiracy theories about international Jewish cabals threatening Christian nations. While Christians were not the only groups who persecuted Jews, modern antisemitism has its seeds in the early church. And Christian acts of violence and injustice against Jewish people are especially shameful, given that Jesus, himself a Jew, taught nonviolence and radical inclusion. In light of this history, Catholics who are attracted to Jewish rituals such as the Passover Seder need to know not only what the church teaches about these practices, but also how Jewish people regard Christian celebrations of traditional Jewish feasts. On this episode of the podcast, hosts Emily Sanna and Rebecca Bratten Weiss talk to philosopher and interfaith scholar Joshua Stein about the history and significance of the Passover feast and whether Christians should host or celebrate their own Seder meals.  You can learn more about this topic and read some of Stein's work in the links below. “Should Catholics celebrate Passover?” by Joshua Stein https://uscatholic.org/articles/202304/should-catholics-celebrate-passover/ “What's a Jew to Do? Jewish-Christian dialogue today,” by Joshua Stein https://medium.com/@thephilosotroll/whats-a-jew-to-do-jewish-christian-dialogue-today-eada02c0d526 “Anti-Jewish readings of Scripture are not just a Holy Week problem,” by Philip A. Cunningham https://www.ncronline.org/opinion/guest-voices/anti-jewish-readings-scripture-are-not-just-holy-week-problem “What can we do about antisemitism and the Catholic literary canon?” by Rebecca Bratten Weiss https://uscatholic.org/articles/202101/what-can-we-do-about-antisemitism-and-the-catholic-literary-canon/ Questions about Jews and Judaism during the Easter Triduum https://www.usccb.org/prayer-worship/liturgical-year/triduum/questions-jews-judaism-triduum Nostra Aetate, Declaration on the Relation of the Church to Non-Christian Religions, Promulgated by Pope Paul VI https://www.newadvent.org/library/docs_ec21na.htm Glad You Asked is sponsored by the Claretian Missionaries. https://www.claretiansusa.org/  

My guest this week is Joshua Stein (@thephilosotroll), a postdoc in philosophy at Georgetown. His interests include social ontology, political philosophy, collective responsibility, and today's topic, antisemitic conspiracism. We discuss Ye's recent public spiral and what it says about the future of right wing politics.Joshua's Website:Convocation: SartreMusic by GW RodriguezSibling Pods:Philosophers in Space: https://0gphilosophy.libsyn.com/Filmed Live Musicals Pod: https://www.filmedlivemusicals.com/thepodcast.htmlSupport us at Patreon.com/EmbraceTheVoidIf you enjoy the show, please Like and Review us on your pod app, especially iTunes. It really helps!Recent appearances: Had several recent appearances you should check out!QED Skepticamp talk! Decoding a (((moral panic))) conspiracy meme: https://www.youtube.com/watch?v=zAKGA8-Da1EI was on The Podcaster's Guide to The Conspiracy talking about philosophy of conspiracism: https://www.podbean.com/media/share/pb-7ra6d-130e8e8?utm_campaign=au_share_ep&utm_medium=dlink&utm_source=au_shareI was on Dan Norton's YouTube show discussing free will and luck: https://www.youtube.com/watch?v=4dZx_VD54pgNext Episode: Conceptual Engineering with Matt Cull

My guest this week is Yassine Meskhout (@ymeskhout), a Public defender and infrequent host of The Bailey podcast. Yassine argues for anarchy perspectives also writes on substack and for Jesse Singal's newsletter on topics related to the criminal justice system as well as some culture war issues. His articles include “Eleven Magic Words” and “I am here because of dumb luck”.Yassine's website: https://ymeskhout.substack.com/Convocation: Ayn RandMusic by GW RodriguezSibling Pods:Philosophers in Space: https://0gphilosophy.libsyn.com/Filmed Live Musicals Pod: https://www.filmedlivemusicals.com/thepodcast.htmlSupport us at Patreon.com/EmbraceTheVoidIf you enjoy the show, please Like and Review us on your pod app, especially iTunes. It really helps!Recent appearances: Had several recent appearances you should check out!QED Skepticamp talk! Decoding a (((moral panic))) conspiracy meme: https://www.youtube.com/watch?v=zAKGA8-Da1EI was on The Podcaster's Guide to The Conspiracy talking about philosophy of conspiracism: https://www.podbean.com/media/share/pb-7ra6d-130e8e8?utm_campaign=au_share_ep&utm_medium=dlink&utm_source=au_shareI was on Dan Norton's YouTube show discussing free will and luck: https://www.youtube.com/watch?v=4dZx_VD54pgNext Episode: Antisemitic Conspiracism with Joshua Stein

My guest this week is Yassine Meskhout (@ymeskhout), a Public defender and infrequent host of The Bailey podcast. Yassine argues for anarchy perspectives also writes on substack and for Jesse Singal's newsletter on topics related to the criminal justice system as well as some culture war issues. His articles include “Eleven Magic Words” and “I am here because of dumb luck”.Yassine's website: https://ymeskhout.substack.com/Convocation: Ayn RandMusic by GW RodriguezSibling Pods:Philosophers in Space: https://0gphilosophy.libsyn.com/Filmed Live Musicals Pod: https://www.filmedlivemusicals.com/thepodcast.htmlSupport us at Patreon.com/EmbraceTheVoidIf you enjoy the show, please Like and Review us on your pod app, especially iTunes. It really helps!Recent appearances: Had several recent appearances you should check out!QED Skepticamp talk! Decoding a (((moral panic))) conspiracy meme: https://www.youtube.com/watch?v=zAKGA8-Da1EI was on The Podcaster's Guide to The Conspiracy talking about philosophy of conspiracism: https://www.podbean.com/media/share/pb-7ra6d-130e8e8?utm_campaign=au_share_ep&utm_medium=dlink&utm_source=au_shareI was on Dan Norton's YouTube show discussing free will and luck: https://www.youtube.com/watch?v=4dZx_VD54pgNext Episode: Antisemitic Conspiracism with Joshua Stein

This Episode we interview Joshua Stein, Phil Greening, Dottie Litz about their take on being a Gym Owner. Welcome to the Gym Lords Podcast, where we talk with successful gym owners to hear what they're doing that is working RIGHT NOW, and to hear lessons and failures they've learned along the way. We would love to share your story! If you'd like to be featured on the podcast, fill out the form on the link below. https://gymlaunchsecrets.com/podcast

This Episode we interview Joshua Stein, Phil Greening, Dottie Litz about their take on being a Gym Owner. Welcome to the Gym Lords Podcast, where we talk with successful gym owners to hear what they're doing that is working RIGHT NOW, and to hear lessons and failures they've learned along the way. We would love to share your story! If you'd like to be featured on the podcast, fill out the form on the link below. https://gymlaunchsecrets.com/podcast

Join Liz Burgard, Anoka-Hennepin parent involvement coordinator, as she discusses how to get mental health support for your student with PrairieCare child and adolescent psychiatrist Dr. Joshua Stein and Anoka-Hennepin school social worker Julie Beaufeaux.  Dr. Stein outlines programming offered by PrairieCare and how to go about getting a mental health assessment for your child(ren). Beaufeaux talks about the role of a school social worker in Anoka-Hennepin and how they can help facilitate connections to resources such as PrairieCare.  Tune in to the latest episode via Podbean, Apple Podcasts, or on the district website to learn more about mental health supports and how to access resources if needed.  The Parent Engage 360 Podcast aims to provide parents and guardians with knowledge from experts in chemical health, mental health, internet safety and more, as well as the tools needed to support their children. Anoka-Hennepin hopes that providing timely and helpful information through the Parent Engage 360 podcast series will strengthen the bond between school and home with resources parents and guardians can use and share with others. Visit ahschools.us/parentengage360 for more information.

As those of us in clinical practice know, we have seen soaring rates of mental health challenges among children, adolescents and their families during the course of the COVID pandemic, exacerbating the already tenuous situation that existed for child and adolescent mental health. We have seen rates of childhood mental health concerns and suicide rise steadily over the last decade. Across the country, we have seen dramatic increases in ED visits for acute mental health emergencies, including suspected suicide attempts. Here to talk to use today about these increasing mental health challenges, and provide us with some strategies for addressing and preventing suicidality in primary care, is child and adolescent psychiatrist Dr. Joshua Stein.View the transcript here: https://www.childrensmn.org/for-health-professionals/talking-pediatrics-podcast/talking-pediatrics-addressing-child-adolescent-suicidality-self-harm-1-21-22/

Videos https://brandnewtube.com/watch/sonia-elijah-interviews-efrat-fenigson-from-israel_Ws1DDYkiqAOXdis.html     https://www.youtube.com/watch?v=GWN2PV4v0lk&t=8s   Researchers find new link between a disrupted body clock and inflammatory diseases RCSI University of Medicine and Health Sciences, November 25, 2021 New research from RCSI has demonstrated the significant role that an irregular body clock plays in driving inflammation in the body's immune cells, with implications for the most serious and prevalent diseases in humans. The circadian body clock generates 24-hour rhythms that keep humans healthy and in time with the day/night cycle. This includes regulating the rhythm of the body's own (innate) immune cells called macrophages. When these cell rhythms are disrupted (due to things like erratic eating/sleeping patterns or shift work), the cells produce molecules which drive inflammation. This can lead to chronic inflammatory diseases such as heart disease, obesity, arthritis, diabetes and cancer, and also impact our ability to fight infection. (NEXT) Social media tied to higher risk of depression Massachusetts General Hospital, November 23, 2021 The latest in a spate of studies investigating links between use of social media and depression suggests the two go hand in hand. The new study follows a yearlong look at social media use and onset of depression among nearly 5,400 adults. None reported even mild depression at the start. But in multiple surveys over 12 months, depression status had worsened in some respondents, the study found. The risk rose with use of three hugely popular social media sites: Snapchat, Facebook and TikTok. None showed any signs of depression at the first survey. But after completing at least one similar follow-up, nearly 9% showed a "significant" increase in scores for depression risk. (NEXT) Havacado or two. Study finds eating lots of the fruit has public health import Randomized controlled trial found that families with high avocado consumption self-reported reduced caloric intake and an overall healthier diet University of California at San Diego, November 29, 2021 In a novel study, researchers conducted a randomized controlled trial comparing the potential health effects between families that consumed a low allotment of avocados (three per week) and families that consumed a high allotment (14 per week) over six months. They found that the high avocado allotment families self-reported lower caloric consumption, reducing their intake of other foods, including dairy, meats and refined grains and their associated negative nutrients, such as saturated fat and sodium. (NEXT) Crabapple supplements could help cut cholesterol, China study discovers Crabapple extract has been show to lower cholesterol in obese mice which were fed a high-fat diet, researchers in China have revealed. Beijing and Shanghai universities, November 30, 2021 The study points out that statins are the major therapy for hypercholesterolaemia and for the prevention of atherosclerosis. However, there is some evidence to suggest that they may increase the risk of diabetes, muscle pain, liver damage and cause other side effects. Crabapple has long been used for the treatment of diarrhoea, indigestion and other digestive diseases in traditional Chinese medicine, and its antioxidant benefits have frequently been studied. (NEXT) Aerobic exercise preserves brain volume and improves cognitive function Wake Forest School of Medicine, November 30, 2021 Using a new MRI technique, researchers found that adults with mild cognitive impairment (MCI) who exercised four times a week over a six-month period experienced an increase in brain volume in specific, or local, areas of the brain, but adults who participated in aerobic exercise experienced greater gains than those who just stretched. (NEXT) Are you a morning or an evening person? It might be due to your gut bacteria University of Haifa (Israel), November 22, 2021 A new study by the University of Haifa reveals that certain gut bacteria differ between morning and evening people. It is already known that there are some genetic differences between larks and owls, but research in fruit flies in our laboratory inspired us to test the impact of gut bacteria on human chronotypes," says Prof. Eran Tauber. Fecal samples were collected from 91 individuals in order to extract and sequence the bacterial DNA. Analysis of the DNA sequences from each sample allowed identification of all gut bacterial species and quantify their abundance. The chronotype of the participants was determined based on their self-reported sleep times during the weekend (waking up without an alarm clock). (OTHER NEXT) Sonia Elijah interviews Efrat Fenigson from Israel Efrat Fenigson, a chief marketing officer and human rights activist from Tel Aviv, Israel, candidly speaks to Sonia about how 'Covid' has been marketed, as if it were a brand, by world governments and the mainstream media. She talks about the general protest movement in Israel and how it evolved from anti-corruption to anti-lockdown/green-pass demonstrations. She gives insight into the psychological state of fear that many Israelis are accustomed to living under making them compliant in obeying the draconian Covid rules and to not question the mass vaccine rollout. (NEXT) Foreclosure Looms for Homeowners Who Thought They'd Won, Thanks to Top New York Court Ruling Sam Mellings The City and New York Focus, November 30, 2021 Christine Fife was “speechless with joy” when she won her foreclosure case in January 2020, she recalled, believing her decade under threat of foreclosure in her Upper West Side condo was finally over. Now, though, Fife is once again facing the seizure of the apartment she has owned since 1990. In February 2021, New York's top court issued a decision that eliminated a path that New York homeowners had used for years to fight foreclosure. The decision in Freedom Mortgage Corporation v. Engel allowed Fife's lender to renew its foreclosure suit against her. “They said it was OK. How can they change their mind?” Fife asked during an interview with New York Focus and THE CITY. Across New York State, homeowners who believed that their cases had been settled in their favor are now once again facing foreclosure due to the Engel decision. Many are in danger of losing their homes, even as two bills aimed at protecting owners wend their way through the state Legislature. Case Reopened In New York, if a borrower misses a mortgage payment, the lender is allowed to demand the entire remaining balance immediately and then move to foreclose after 120 days, if the money owed remains unpaid.. But a lender must start the legal proceedings within six years of first demanding full payment, or the suit becomes invalid. Until recently, the clock kept ticking until the lender informed the borrower that they were no longer seeking foreclosure. In Fife's case, the lender had never done so. The bank sued Fife twice: first in 2010, a case the lender claims it later voluntarily withdrew, and again in 2017. Her lawyers, representing Fife pro bono, successfully argued that the bank's second foreclosure suit was barred by the six-year limit and got it dismissed. But the Engel decision changed the rules. The Court of Appeals found that voluntarily ending a foreclosure suit stops the clock on the six-year time limit — even if the homeowner is never notified. The court's ruling applies retroactively to any foreclosure cases ongoing or still open to appeal at the time the decision was issued. Following the ruling, many foreclosures that expired under the six-year limit have been reopened or appealed to higher courts. Holly Meyer, a Suffolk County lawyer who represented one of the defendants in the Engel case, estimated that the number of affected homeowners could be in the tens of thousands. Fife's was one of them. In April 2021, the bank moved to renew its foreclosure suit against her — and the trial judge cited the Engel ruling as a reason to rehear the case. “I was shocked at this decision, because I had put all my faith in [the foreclosure court's] initial decision, which was in my favor,” Fife said. With Fife's best defense gone, her hopes for avoiding foreclosure now appear slim, her legal counsel acknowledged. ‘Incompetently' Managed Loans It's not uncommon for lenders to allow their right to foreclose to expire, according to real estate lawyers. “There are millions of residential loans being serviced somewhat incompetently, so these things do sometimes slip between the cracks,” said Joshua Stein, a commercial real estate lawyer. Real estate industry supporters of the Court of Appeals' decision say it made little sense for a foreclosure case to fail because of what they consider a clerical error — one that basically lets borrowers shirk their debts. “The idea that you should still be at risk because you haven't repaid the money you borrowed doesn't strike me as egregious,” Stein said. Homeowner attorneys say that cases get dropped all the time in the legal system because of technical violations of procedural requirements, and that foreclosure cases should be no different. “If you have somebody on trial for murder, but you find that their constitutional rights were violated, they go free. It's the same thing here,” Meyer said. Chief Judge Conflicted? The day after the Court of Appeals ruled on the Engel case, the law firm Greenberg Traurig, which had represented two of the plaintiffs, cheered what it called a “ground shifting” victory for lenders. “Statewide application will likely protect billions in assets for mortgage holders,” its press release claimed. Chief Judge Janet DiFiore, who wrote the majority opinion in Engel, was a Greenberg Traurig client at the time that she ruled in favor of their bank clients in that and other cases, the New York Law Journal reported in April. The firm defended her in a suit brought by judges forced into retirement as a cost-cutting measure. Defense attorneys said they had not been informed of the potential conflict for the judge who ruled against their clients. “The law's not on our side anymore, and that means that there are a number of people who will be facing foreclosure when they wouldn't have faced it a couple of years ago,” Julie Howe, a senior staff attorney at the New York Legal Assistance Group, who is representing Fife pro bono, told New York Focus. Then-Governor Andrew Cuomo swears in Janet DiFiore as the new chief judge of the New York State Court of Appeals, Feb. 8, 2016. Governor Andrew Cuomo's Office Jacob Inwald, director of foreclosure prevention at Legal Services NYC, said many of the foreclosure cases affected by the Engel decision originally stemmed from the real estate crash of 2008 and freewheeling lending leading up to it. Fife, for instance, had borrowed $731,000 against her apartment in April 2007 to pay living expenses after a disabling injury and divorce. Monthly payments were nearly $5,000, with adjustable rate mortgage that started at 8% annual interest, potentially rising as high as 15%. “I didn't know anything about mortgages,” Fife said. “I was just so happy that I was able to live on another day. I was probably the easiest take on the block.” Within a year, the bank alleged that she had fallen behind on her mortgage payments — kicking off foreclosure proceedings that her loan's holder, Wilmington Trust Association, has resurrected more than a decade later. ‘It's Really Scary' Rockland County resident Susan Azcuy is in a situation similar to Fife's — believing that she'd survived foreclosure only to find the cloud hanging over her once again. For 23 years, Azcuy and her husband kept up with the mortgage payments on their house in Pomona, including a 2005 refinancing, for which she took on a debt of $210,000 at 5.75% interest. But in 2012, after Azcuy's husband was fired from his job, they missed a payment and their lender quickly moved to foreclose. The bank voluntarily withdrew the suit in March 2016 for technical reasons but did not notify Azcuy, refiling the case the next month. It went to trial in 2019, and Azcuy won, after a key prosecution witness failed to show up. ‘We're still struggling. I was very, very hopeful to be able to continue living here.' Before Engel, this would have been the end of the case, since more than six years had elapsed since the 2012 foreclosure suit. But thanks to Engel, the six-year clock restarted in 2016 — giving Azcuy's lender another chance to sue. Due to penalties and foreclosure fees, Azcuy now owes nearly $400,000, just shy of double the amount of the 2005 refinancing. Efforts to reach a settlement or a modification with the bank have been unsuccessful, according to Azcuy's attorney, Derek Tarson of the Legal Aid Society of Rockland County. If the bank brings another foreclosure lawsuit, which Tarson believes is likely, Azcuy will not be able to rely on the defense that more than six years have passed. “It's really scary. We're still struggling,” Azcuy said. “I was very, very hopeful to be able to continue living here.” Lawmakers Respond State lawmakers have introduced two bills seeking to reverse some of Engel's effects. One measure, sponsored by Sen. Kevin Thomas (D-Nassau) and Assemblymember Helene Weinstein (D-Brooklyn), would require lenders to inform borrowers if they withdraw their demands for payment, since that action serves to stop the clock on the six-year countdown. If lenders withdraw the lawsuit but fail to notify the borrowers, the clock would keep ticking — a return to the status quo before Engel. The bill would also forbid lenders from foreclosing if any part of the loan had previously expired — a measure that would bar reviving suits against homeowners like Fife and Azcuy. The legislature is also considering a second bill, sponsored by Sen. James Sanders (D-Queens) and Assemblymember Latrice Walker (D-Brooklyn). This bill would prevent lenders from discontinuing a demand for full payment, stopping the six-year countdown clock, without the consent of the borrower. The measure also would start the countdown from the time that a mortgage holder missed a payment. Though meant to protect homeowners, the Sanders-Walker bill could actually incentivize lenders to begin foreclosure more quickly, one foreclosure defense attorney told New York Focus. “If the clock is ticking, all plaintiffs are going to want to do is get their case started,” the attorney, who asked not to be named, said. Sanders rejected the critique. “I don't think that you can further incentivize the financial institutions” to foreclose after the leeway granted them by Engel, he said. Whether either of the bills would apply retroactively to homeowners like Fife and Azcuy is an open question. “It may not be able to help those, but it is our desire,” Sanders said. “We will get guidance on whether we can do that.” Sanders said that he has spoken to Gov. Kathy Hochul and legislative leaders about his bill, and while they have not endorsed it, he said they are open to supporting it. (A Hochul spokesperson said the governor “will review all legislation that reaches her desk.” “We are making excellent progress with both, and we expect good things in the coming days,” Sanders said. (NEXT) Israeli study says COVID shot efficacy decreases dramatically after 3 months, calls for boosters British Medical Journal, November 24, 2021 A study published by The BMJ today finds a gradual increase in the risk of COVID-19 infection from 90 days after receiving a second dose of the Pfizer-BioNTech vaccine. The study was carried out by the Research Institute of Leumit Health Services in Israel. Israel was one of the first countries to roll out a large scale COVID-19 vaccination campaign in December 2020, but which has seen a resurgence of infections since June 2021. The findings confirm that the Pfizer-BioNTech vaccine provided excellent protection in the initial weeks after vaccination, but suggest that protection wanes for some individuals with time. To do this, the researchers examined electronic health records for 80,057 adults (average age 44 years) who received a PCR test at least three weeks after their second injection, and had no evidence of previous COVID-19 infection. Of these 80,057 participants, 7,973 (9.6%) had a positive test result. These individuals were then matched to negative controls of the same age and ethnic group who were tested in the same week. The rate of positive results increased with time elapsed since a second dose. For example, across all age groups 1.3% of participants tested positive 21-89 days after a second dose, but this increased to 2.4% after 90-119 days; 4.6% after 120-149 days; 10.3% after 150-179 days; and 15.5% after 180 days or more. (NEXT) 31,014 Deaths 2,890,600 Injuries Following COVID Shots in European Database of Adverse Reactions as Young, Previously Healthy People Continue to Die Health Impact News The European Union database of suspected drug reaction reports is EudraVigilance, and they are now reporting 31,014 fatalities, and 2,890,600 injuries, following COVID-19 injections. A Health Impact News subscriber from Europe reminded us that this database maintained at EudraVigilance is only for countries in Europe who are part of the European Union (EU), which comprises 27 countries. The total number of countries in Europe is much higher, almost twice as many, numbering around 50. (There are some differences of opinion as to which countries are technically part of Europe.) Total reactions for the mRNA vaccine Tozinameran (code BNT162b2, Comirnaty) from BioNTech/ Pfizer: 14,526 deaths and 1,323,370 injuries to 20/11/2021 Total reactions for the mRNA vaccine mRNA-1273 (CX-024414) from Moderna: 8,518 deaths and 390,163 injuries to 20/11/2021 Total reactions for the vaccine AZD1222/VAXZEVRIA (CHADOX1 NCOV-19) from Oxford/AstraZeneca: 6,145 deaths and 1,075,335 injuries to 20/11/2021 Total reactions for the COVID-19 vaccine JANSSEN (AD26.COV2.S) from Johnson & Johnson: 1,825 deaths and 101,732 injuries to 20/11/2021 (NEXT) Censorship = dictatorship Dr. Jessica Rose, November 29, 2021 So the censorship continues. I did a very detailed and informative interview with Frank McCaughey of Ireland on the subject of the pointlessness, potential harms and dangers with mass injecting children during this ‘pandemic' with the known non-sterilizing COVID-19 injectable products. And it has been remove Let's check out what YouTube's Community Guidelines are, shall we? YouTube's Community Guidelines: These determine what content is allowed on YouTube and help make YouTube a safe place to foster community. A safe place to foster community, eh? What kind of community are you thinkin' ‘bout there, Youtube? A community akin to an enslaved, dead-eyed mass of hypnotized automatons? If I may: no thanks on that. I'd rather live on that cat Island. So, for those of you who didn't get to see the video (I imagine that is all of you since it was up for less than 24 hours), I talked at length about the ‘don't's of injecting pre-pubescent children with experimental products for which the ingredient list is a big secret for a ‘disease' that they do not succumb to. Ah, I see now. It was because I mentioned Ivermectin. Boy. Youtube. Get with the program! Read some studies for crying out loud! And update your censorship guidelines! Make them reflect the scientific truth and not the weird false dictates of singular beings who feast on the ‘community' to increase their ‘power'. Here's what I found in their COVID-19 medical misinformation policy. Treatment misinformation: Content that encourages the use of home remedies, prayer, or rituals in place of medical treatment such as consulting a doctor or going to the hospital Content that claims that there's a guaranteed cure for COVID-19 Content that recommends use of Ivermectin or Hydroxychloroquine for the treatment of COVID-19 Claims that Hydroxychloroquine is an effective treatment for COVID-19 Categorical claims that Ivermectin is an effective treatment for COVID-19 Claims that Ivermectin and Hydroxychloroquine are safe to use in the treatment COVID-19 Other content that discourages people from consulting a medical professional or seeking medical advice Ok. I want to work backwards through the italicized points, if I may. 1. Hey Youtube. I AM a medical sciences professional. This IS my consultation. Doesn't that make your dictate of discouraging ‘consulting a medical professional' moot? I am not only not discouraging this, in addition to encouraging this, I am this. 2. Hey Youtube. GET WITH THE PROGRAM. Ivermectin has been affiliated with Nobel-ity. It's not only been awarded a prize for its safe use as an anti-parastic for decades and been doled out to literally billions of people, (including pregnant women and children) with no ill effects, it's has an excessively successful safety profile as an off-label drug in the context of COVID-19.¹ 3. It has also been clinically-tested and proven effective in the context of COVID-19 as an off-label drug - which is more than we can say about the clot shots, eh?²³⁴⁵⁶⁷⁸⁹¹⁰¹¹ 4. Based on points, 1, 2 and 3, I would recommend the off-label use of Ivermectin. As a Medical Scientist. Oh and by the way, aren't you violating your own ‘Community Standards' with your point on a ‘guaranteed cure for COVID-19'? You guys are so sure that your injections are the only way to deal with this situation. Doesn't that imply that this guarantees a cure? No wait. It doesn't. But what it does do is set a precedent and instigate a thought: there will never be a cure for COVID-19. It's incurable. Which is: true. But it's also no worse than the flu in the non-vulnerable, which is most people. Including children. So we don't need to seek a ‘cure'. Just like we don't need to seek a ‘cure' for the common cold or the flu. That's one of the things that our bloody immune systems are for and very good it - preventing disease. Viruses are EVERYWHERE. ALL THE TIME. It's not a reason to freak out. Educate yourself and others on this. It about high time people learned that we are constantly engaging and have co-evolved with viruses and bacteria for the entirety of our existences. It's what we are.¹² Our genome is 7% retrovirus. If we attempt to destroy this magnificence then we are not only stupid, but we will be destroyed in turn. Leave the immune system alone. Or rather, optimize it. Be healthy. Avoid toxins. As much as you can. Pretty simple. So there you are Youtube. You have been brought up-to-date. Now, I don't like simply bitching about stuff, even though it does feel good, so I wanted to bring it to everyone's attention that you can fight to have your content re-instated once it has been removed. However, it is not a common occurrence to have a video re-instated once it has been censored. The ones that do get re-instated typically are ones that were erroneously taken down. I think that the Youtube overlords would argue that since they are paid to enforce the dictate narrative, they cannot stand behind science and truth, and therefore, I think they would hold fast to their ‘claims' that Ivermectin is dangerous and ineffective. (NEXT) Why aren't healthcare workers speaking out about the catastrophe caused by the vaccines? Steve Kirsch, November 23, 2021 Everyone thinks that if the jabs were really dangerous, doctors and other healthcare workers would be speaking out about it. They are wrong. Here are the four main reasons they do not speak out.Two important things you need to know: 1.All the kids were recently vaccinated. 2. Kids that age NEVER get tachycardia (i.e., the medical experts I've talked to have never seen it before in their careers). Here are some reasons very few people are speaking out: 1. Delegated trust. People trust their doctors, the doctors trust other doctors and ultimately the CDC. Nobody is independently verifying the CDC is telling the truth. Doctors are really really bad in critically reading scientific studies. Mask guidelines are the PERFECT example of this. There isn't any scientific proof (well-done randomized trial) that masks work. Yet very few question the narrative (and those that do are ostracized). So everyone basically goes with the flow and the whole thing is a positive feedback loop despite zero scientific basis. See my article Masks don't work and read the accolades in the Nature article. All these experts who hailed the study never read it with a critical eye and lack the skills to do so. This is how misinformation propagates. 2.Fear of job loss. Nobody wants to lose their job. Look what happened to Deborah Conrad and others who speak out. Fired within hours after speaking out. So the lab technicians who are now seeing kids with tachycardia just keep their mouth shut. They know something is very wrong, but their job is more important. Besides, if they spoke out, it wouldn't make any difference since they are just a lab technician. Doctors have a similar problem. The medical system, despite claims of physician autonomy, actually offers very little, as it takes very little to be thrown out of the system. Medicare, the FDA, a state medical board, a malpractice insurer, the DEA, a hospital medical staff, an employer - you only have to cross one of these to have your career ruined. Combine that with the idea that most physicians wouldn't be willing to stand against a medical establishment agency such as the CDC (the ones who will have long since been ostracized) and that to do so would require a huge amount of energy and time spent on medical paper research to make a case (and most docs don't have time for that) and that most of medicine is necessarily a form of group think anyway. Then add on to it that the policy makers in large medical corporations roles are more immediately to protect the interests of the corporation than to "save the world," and you arrive at our current situation. 3.Belief that COVID is even worse than the vaccine injuries. Many people are deceived by erroneous reports that the number of vaccine cases (e.g., of myocarditis) are occurring far less often now that the vaccines have been rolled out. Dr. John Su is the big culprit here because he's never told the world that VAERS is under-reported. The pediatric cardiologists know what is going on, but they aren't going to say anything due to #1. So I see doctors tweeting the myth that “sure, there is myo after the vaccine, but the rates due to COVID are worse so the vaccine is the better of the two options.” 4.Belief that the injuries are really rare. I know a doctor who treats vaccine injured patients. He has no clue whether these are every single vaccine injured patient in the US or he's only seeing a tiny fraction of the injuries. He believes he's seeing them all so writes it off as just “coincidence” and “bad luck” since if it was the vaccine, the CDC would have spotted it. 5. Cognitive dissonance/trust in authority figures. They are so convinced the vaccines are safe (since nobody else is speaking out), that any adverse events that happen must be due to something else. Positive feedback loop. 6.Belief that they can treat you for your vaccine side effects, but that they can't treat you if you have COVID. So lesser of two evils. And of course, they think no early treatments work, so they think they are doing you a favor by telling you to get the vaccine. 7.Belief that there is no viable alternative for treating COVID and that the vaccines work. So even 100,000 dead or injured people is better than 750,000 dead people from COVID. 8. Trust in the NIH and CDC. If it was a problem, the CDC would tell people. Telling people isn't their job. Their job is to follow the direction set by the experts. 9.Fear of being ostracized. People who do research fear if they speak out they would be labelled as anti-vaxers and their research would thus be discredited. 10.Critical thinkers have been fired. Hospitals and medical facilities have already fired vaccine hesitant employees per vaccine mandates thereby self selecting for vax believers. 11. They think that the side-effects show that the vaccine is “working.” This is more of a patient thing. It's how the patients look at their adverse events… as a positive thing. (You really can't make this stuff up.) 12.They are being paid to look the other way. The federal government gave “grants” (aka BRIBES) to hospitals and physicians to promote the vaccines. If they speak out against them now, the government will demand the grants are repaid. [A physician reported this to me on Telegram. You really can't make this stuff up.] 13. They will lose their research funding if they publish their results.

Dr. Joshua Stein joins me to discuss me to discuss the notion of justice in the public discourse.

CECL continues to remain at the top of mind for Financial Executives in the banking industry and in this episode of the podcast we speak to two professionals from the American Bankers Association that are at the forefront of those adoption efforts: Michael L. Gullette, Senior Vice President of Tax & Accounting and Joshua Stein, Vice President, Accounting and Financial Management Special Guests: Joshua Stein and Michael L. Gullette.

Glaucoma is the most common cause of irreversible blindness in the world. Joshua Stein, MD, MS, associate professor of ophthalmology at the University of Michigan, reviews the diagnosis and treatment of glaucoma. Related Article: Glaucoma in Adults—Screening, Diagnosis, and Management

Since March, almost every nonemergency medical visit has been conducted through video chats or on the telephone to reduce the spread of the coronavirus.  Telemedicine or telehealth is not new, but the pandemic has caused health care systems to rapidly pivot to online doctor’s visits.  How is it going and is it here to stay? Guests: Joel Beiswenger is the president and CEO of Tri-County Health Care in Wadena, Minn. Dr. Joshua Stein is a child adolescent psychiatrist and the clinical director of the Prairie Care’s Brooklyn Park medical office. Dr. Annie Ideker is a family medicine physician at the HealthPartners Clinic in Arden Hills, Minn., and helped train more than 2,000 clinicians on telemedicine.

We are all experiencing tough times right now, and PrairieCare is here to help you get through it all. PrairieCare is a standalone psychiatric hospital that is here to help both kids and adults. Dr. Joshua Stein's mission is to help you and your loved ones. If you or your kids are having a hard time handling their stress PrairieCare is here to help and take some of that stress off your plate.

In this episode, Josh and Tomer talk about alternative investment management and secondary transfers. Josh shares how a discussion with David Sacks led him to blockchain, explains why Harbor decided to build their digital platform on Ethereum and breaks down the opportunity to unlock liquidity in debt and equity markets. Plus, Josh talks about his learnings from the mega dorm deal that didn’t go through and the importance of Harbor's recent broker-dealer license approval. =========================== SUPPORT THE SHOW: Subscribe on Apple Podcasts, Google Podcasts or Spotify Leave a review Share the show with your friends and family on social media LISTEN TO THE BLOCKCHAIN VC PODCAST: Apple Podcasts Google Podcasts Spotify Youtube Stitcher Show website FOLLOW TOMER ON SOCIAL MEDIA: Twitter Medium blog

Since the ABA Banking Journal Podcast last checked in on the Current Expected Credit Loss standard — which is coming into effect for many banks and the vast majority of bank assets on Jan. 1, 2020 — there have been several key developments: the proposal of a three-year delay for private and smaller public companies, the introduction of bipartisan bills that would require the Financial Accounting Standards Board to pause CECL implementation pending a quantitative impact study and questions over the readiness of the audit sector for CECL. In this episode — sponsored by RIVIO Clearinghouse, the future of financial information exchange — ABA accounting experts Michael Gullette and Joshua Stein discuss: The potential competitive effects of an extended period where some banks are on CECL and others are not Concerns about the lack of readiness among auditors on CECL, which are heightened because the effective date is less than three months away The risk of CECL’s reliance on lagging indicators that amplify the standard’s procyclicality The chances of a CECL delay for all institutions, as ABA has urged CECL challenges they heard from community bank CFOs at ABA’s CFO Exchange earlier this month

With the Current Expected Credit Loss standard for loan loss accounting coming into effect for many banks — and the vast majority of bank assets — on Jan. 1, 2020, where are bank CFOs and managers in the process of implementing CECL, and what challenges are they seeing? ABA accounting experts Michael Gullette and Joshua Stein provide a CECL update on the latest issue of the ABA Banking Journal Podcast. In this episode, Gullette and Stein explain: How CECL — which requires “life of loan” estimates of losses to be recorded for unimpaired loans at origination or purchase — may affect bank capital, and thus banks’ capacity to lend The untested performance of CECL in a stressed economic environment How forecasting uncertainty is already affecting longer-maturity loans, including to consumers The challenge of retrieving and formatting data and translating forecasts into financial statements How regulators and auditors are expected to address CECL — and why any regulatory flexibility provided may not be available under audit

FreeBSD Foundation September Update, tiny C lib for programming Unix daemons, EuroBSDcon trip reports, GhostBSD tested on real hardware, and a BSD auth module for duress. ##Headlines FreeBSD Foundation Update, September 2018 MESSAGE FROM THE EXECUTIVE DIRECTOR Dear FreeBSD Community Member, It is hard to believe that September is over. The Foundation team had a busy month promoting FreeBSD all over the globe, bug fixing in preparation for 12.0, and setting plans in motion to kick off our 4th quarter fundraising and advocacy efforts. Take a minute to see what we’ve been up to and please consider making a donation to help us continue our efforts supporting FreeBSD! September 2018 Development Projects Update In preparation for the release of FreeBSD 12.0, I have been working on investigating and fixing a backlog of kernel bug reports. Of course, this kind of work is never finished, and we will continue to make progress after the release. In the past couple of months I have fixed a combination of long-standing issues and recent regressions. Of note are a pair of UNIX domain socket bugs which had been affecting various applications for years. In particular, Chromium tabs would frequently hang unless a workaround was manually applied to the system, and the bug had started affecting recent versions of Firefox as well. Fixing these issues gave me an opportunity to revisit and extend our regression testing for UNIX sockets, which, in turn, resulted in some related bugs being identified and fixed. Of late I have also been investigating reports of issues with ZFS, particularly, those reported on FreeBSD 11.2. A number of regressions, including a kernel memory leak and issues with ARC reclamation, have already been fixed for 12.0; investigation of other reports is ongoing. Those who closely follow FreeBSD-CURRENT know that some exciting work to improve memory usage on NUMA systems is now enabled by default. As is usually the case when new code is deployed in a diverse array of systems and workloads, a number of problems since have been identified. We are working on resolving them as soon as possible to ensure the quality of the release. I’m passionate about maintaining FreeBSD’s stability and dependability as it continues to expand and grow new features, and I’m grateful to the FreeBSD Foundation for sponsoring this work. We depend on users to report problems to the mailing lists and via the bug tracker, so please try running the 12.0 candidate builds and help us make 12.0 a great release. Fundraising Update: Supporting the Project It’s officially Fall here at Foundation headquarters and we’re heading full-steam into our final fundraising campaign of the year. We couldn’t even have begun to reach our funding goal of $1.25 million dollars without the support from the companies who have partnered with us this year. Thank you to Verisign for becoming a Silver Partner. They now join a growing list of companies like Xiplink, NetApp, Microsoft, Tarsnap, VMware, and NeoSmart Technologies that are stepping up and showing their commitment to FreeBSD! Funding from commercial users like these and individual users like yourself, help us continue our efforts of supporting critical areas of FreeBSD such as: Operating System Improvements: Providing staff to immediately respond to urgent problems and implement new features and functionality allowing for the innovation and stability you’ve come to rely on. Security: Providing engineering resources to bolster the capacity and responsiveness of the Security team providing your users with piece of mind when security issues arise. Release Engineering: Continue providing a full-time release engineer, resulting in timely and reliable releases you can plan around. Quality Assurance: Improving and increasing test coverage, continuous integration, and automated testing with a full-time software engineer to ensure you receive the highest quality, secure, and reliable operating system. New User Experience: Improving the process and documentation for getting new people involved with FreeBSD, and supporting those people as they become integrated into the FreeBSD Community providing the resources you may need to get new folks up to speed. Training: Supporting more FreeBSD training for undergraduates, graduates, and postgraduates. Growing the community means reaching people and catching their interest in systems software as early as possible and providing you with a bigger pool of candidates with the FreeBSD skills you’re looking for. Face-to-Face Opportunities: Facilitating collaboration among members of the community, and building connections throughout the industry to support a healthy and growing ecosystem and make it easier for you to find resources when questions emerge . We can continue the above work, if we meet our goal this year! If your company uses FreeBSD, please consider joining our growing list of 2018 partners. If you haven’t made your donation yet, please consider donating today. We are indebted to the individual donors, and companies listed above who have already shown their commitment to open source. Thank you for supporting FreeBSD and the Foundation! September 2018 Release Engineering Update The FreeBSD Release Engineering team continued working on the upcoming 12.0 RELEASE. At present, the 12.0 schedule had been adjusted by one week to allow for necessary works-in-progress to be completed. Of note, one of the works-in-progress includes updating OpenSSL from 1.0.2 to 1.1.1, in order to avoid breaking the application binary interface (ABI) on an established stable branch. Due to the level of non-trivial intrusiveness that had already been discovered and addressed in a project branch of the repository, it is possible (but not yet definite) that the schedule will need to be adjusted by another week to allow more time for larger and related updates for this particular update. Should the 12.0-RELEASE schedule need to be adjusted at any time during the release cycle, the schedule on the FreeBSD project website will be updated accordingly. The current schedule is available at: https://www.freebsd.org/releases/12.0R/schedule.html BSDCam 2018 Trip Report: Marie Helene Kvello-Aune I’d like to start by thanking the FreeBSD Foundation for sponsoring my trip to BSDCam(bridge) 2018. I wouldn’t have managed to attend otherwise. I’ve used FreeBSD in both personal and professional deployments since the year 2000, and over the last few years I have become more involved with development and documentation. I arrived in Gatwick, London at midnight. On Monday, August 13, I took the train to Cambridge, and decided to do some touristy activities as I walked from the train station to Churchill College. I ran into Allan outside the hotel right before the sky decided it was time for a heavy rainfall. Monday was mostly spent settling in, recouping after travel, and hanging out with Allan, Brad, Will and Andy later in the afternoon/evening. Read more… Continuous Integration Update The FreeBSD Foundation has sponsored the development of the Project’s continuous integration system, available at https://ci.FreeBSD.org, since June. Over the summer, we improved both the software and hardware infrastructure, and also added some new jobs for extending test coverage of the -CURRENT and -STABLE branches. Following are some highlights. New Hardware The Foundation purchased 4 new build machines for scaling up the computation power for the various test jobs. These newer, faster machines substantially speed up the time it takes to test amd64 builds, so that failing changes can be identified more quickly. Also, in August, we received a donation of 2 PINE A64-LTS boards from PINE64.org, which will be put in the hardware test lab as one part of the continuous tests. CI Staging Environment We used hardware from a previous generation CI system to build a staging environment for the CI infrastructure, which is available at https://ci-dev.freebsd.org. It executes the configurations and scripts from the “staging” branch of the FreeBSD-CI repository, and the development feature branches. We also use it to experiment with the new version of the jenkins server and plugins. Having a staging environment avoids affecting the production CI environment, reducing downtime. Mail Notification In July, we turned on failure notification for all the kernel and world build jobs. Committers will receive email containing the build information and failure log to inform them of possible problems with their modification on certain architectures. For amd64 of the -CURRENT branch, we also enabled the notification on failing regression test cases. Currently mail is sent only to the individual committers, but with help from postmaster team, we have created a dev-ci mailing list and will soon be also sending notifications there. New Test Job In August, we updated the embedded script of the virtual machine image. Originally it only executed pre-defined tests, but now this behavior can be modified by the data on the attached disk. This mechanism is used for adding new ZFS tests jobs. We are also working on analyzing and fixing the failing and skipped test cases. Work in Progress In August and September, we had two developer summits, one in Cambridge, UK and one in Bucharest, Romania. In these meetings, we discussed running special tests, such as ztest, which need a longer run time. We also planned the network testing for TCP/IP stack ###Daemonize - a Tiny C Library for Programming the UNIX Daemons Whatever they say, writing System-V style UNIX daemons is hard. One has to follow many rules to make a daemon process behave correctly on diverse UNIX flavours. Moreover, debugging such a code might be somewhat tricky. On the other hand, the process of daemon initialisation is rigid and well defined so the corresponding code has to be written and debugged once and later can be reused countless number of times. Developers of BSD UNIX were very aware of this, as there a C library function daemon() was available starting from version 4.4. The function, although non-standard, is present on many UNIXes. Unfortunately, it does not follow all the required steps to reliably run a process in the background on systems which follow System-V semantics (e.g. Linux). The details are available at the corresponding Linux man page. The main problem here, as I understand it, is that daemon() does not use the double-forking technique to avoid the situation when zombie processes appear. Whenever I encounter a problem like this one, I know it is time to write a tiny C library which solves it. This is exactly how ‘daemonize’ was born (GitHub mirror). The library consists of only two files which are meant to be integrated into the source tree of your project. Recently I have updated the library and realised that it would be good to describe how to use it on this site. If for some reason you want to make a Windows service, I have a battle tested template code for you as well. System-V Daemon Initialisation Procedure To make discussion clear we shall quote the steps which have to be performed during a daemon initialisation (according to daemon(7) manual page on Linux). I do it to demonstrate that this task is more tricky than one might expect. So, here we go: Close all open file descriptors except standard input, output, and error (i.e. the first three file descriptors 0, 1, 2). This ensures that no accidentally passed file descriptor stays around in the daemon process. On Linux, this is best implemented by iterating through /proc/self/fd, with a fallback of iterating from file descriptor 3 to the value returned by getrlimit() for RLIMITNOFILE. Reset all signal handlers to their default. This is best done by iterating through the available signals up to the limit of _NSIG and resetting them to SIGDFL. Reset the signal mask using sigprocmask(). Sanitize the environment block, removing or resetting environment variables that might negatively impact daemon runtime. Call fork(), to create a background process. In the child, call setsid() to detach from any terminal and create an independent session. In the child, call fork() again, to ensure that the daemon can never re-acquire a terminal again. Call exit() in the first child, so that only the second child (the actual daemon process) stays around. This ensures that the daemon process is re-parented to init/PID 1, as all daemons should be. In the daemon process, connect /dev/null to standard input, output, and error. In the daemon process, reset the umask to 0, so that the file modes passed to open(), mkdir() and suchlike directly control the access mode of the created files and directories. In the daemon process, change the current directory to the root directory (/), in order to avoid that the daemon involuntarily blocks mount points from being unmounted. In the daemon process, write the daemon PID (as returned by getpid()) to a PID file, for example /run/foobar.pid (for a hypothetical daemon “foobar”) to ensure that the daemon cannot be started more than once. This must be implemented in race-free fashion so that the PID file is only updated when it is verified at the same time that the PID previously stored in the PID file no longer exists or belongs to a foreign process. In the daemon process, drop privileges, if possible and applicable. From the daemon process, notify the original process started that initialization is complete. This can be implemented via an unnamed pipe or similar communication channel that is created before the first fork() and hence available in both the original and the daemon process. Call exit() in the original process. The process that invoked the daemon must be able to rely on that this exit() happens after initialization is complete and all external communication channels are established and accessible. The discussed library does most of the above-mentioned initialisation steps as it becomes immediately evident that implementation details for some of them heavily dependent on the internal logic of an application itself, so it is not possible to implement them in a universal library. I believe it is not a flaw, though, as the missed parts are safe to implement in an application code. The Library’s Application Programming Interface The generic programming interface was loosely modelled after above-mentioned BSD’s daemon() function. The library provides two user available functions (one is, in fact, implemented on top of the other) as well as a set of flags to control a daemon creation behaviour. Conclusion The objective of the library is to hide all the trickery of programming a daemon so you could concentrate on the more creative parts of your application. I hope it does this well. If you are not only interested in writing a daemon, but also want to make yourself familiar with the techniques which are used to accomplish that, the source code is available. Moreover, I would advise anyone, who starts developing for a UNIX environment to do that, as it shows many intricacies of programming for these platforms. ##News Roundup EuroBSDCon 2018 travel report and obligatory pics This was my first big BSD conference. We also planned - planned might be a big word - thought about doing a devsummit on Friday. Since the people who were in charge of that had a change of plans, I was sure it’d go horribly wrong. The day before the devsummit and still in the wrong country, I mentioned the hours and venue on the wiki, and booked a reservation for a restaurant. It turns out that everything was totally fine, and since the devsummit was at the conference venue (that was having tutorials that day), they even had signs pointing at the room we were given. Thanks EuroBSDCon conference organizers! At the devsummit, we spent some time hacking. A few people came with “travel laptops” without access to anything, like Riastradh, so I gave him access to my own laptop. This didn’t hold very long and I kinda forgot about it, but for a few moments he had access to a NetBSD source tree and an 8 thread, 16GB RAM machine with which to build things. We had a short introduction and I suggested we take some pictures, so here’s the ones we got. A few people were concerned about privacy, so they’re not pictured. We had small team to hold the camera :-) At the actual conference days, I stayed at the speaker hotel with the other speakers. I’ve attempted to make conversation with some visibly FreeBSD/OpenBSD people, but didn’t have plans to talk about anything, so there was a lot of just following people silently. Perhaps for the next conference I’ll prepare a list of questions to random BSD people and then very obviously grab a piece of paper and ask, “what was…”, read a bit from it, and say, “your latest kernel panic?”, I’m sure it’ll be a great conversation starter. At the conference itself, was pretty cool to have folks like Kirk McKusick give first person accounts of some past events (Kirk gave a talk about governance at FreeBSD), or the second keynote by Ron Broersma. My own talk was hastily prepared, it was difficult to bring the topic together into a coherent talk. Nevertheless, I managed to talk about stuff for a while 40 minutes, though usually I skip over so many details that I have trouble putting together a sufficiently long talk. I mentioned some of my coolest bugs to solve (I should probably make a separate article about some!). A few people asked for the slides after the talk, so I guess it wasn’t totally incoherent. It was really fun to meet some of my favourite NetBSD people. I got to show off my now fairly well working laptop (it took a lot of work by all of us!). After the conference I came back with a conference cold, and it took a few days to recover from it. Hopefully I didn’t infect too many people on the way back. ###GhostBSD tested on real hardware T410 – better than TrueOS? You might have heard about FreeBSD which is ultimately derived from UNIX back in the days. It is not Linux even though it is similar in many ways because Linux was designed to follow UNIX principles. Seeing is believing, so check out the video of the install and some apps as well! Nowadays if you want some of that BSD on your personal desktop how to go about? Well there is a full package or distro called GhostBSD which is based on FreeBSD current with a Mate or XFCE desktop preconfigured. I did try another package called TrueOS before and you can check out my blog post as well. Let’s give it a try on my Lenovo ThinkPad T410. You can download the latest version from ghostbsd.org. Creating a bootable USB drive was surprisingly difficult as rufus did not work and created a corrupted drive. You have to follow this procedure under Windows: download the 2.5GB .iso file and rename the extension to .img. Download Win32 Disk imager and burn the img file to an USB drive and boot from it. You will be able to start a live session and use the onboard setup to install GhostBSD unto a disk. I did encounter some bugs or quirks along the way. The installer failed the first time for some unknown reason but worked on the second attempt. The first boot stopped upon initialization of the USB3 ports (the T410 does not have USB3) but I could use some ‘exit’ command line magic to continue. The second boot worked fine. Audio was only available through headphones, not speakers but that could partially be fixed using the command line again. Lot’s of installed apps did not show up in the start menu and on goes the quirks list. Overall it is still better than TrueOS for me because drivers did work very well and I could address most of the existing bugs. On the upside: Free and open source FreeBSD package ready to go Mate or XFCE desktop (Mate is the only option for daily builds) Drivers work fine including LAN, WiFi, video 2D & 3D, audio, etc UFS or ZFS advanced file systems available Some downsides: Less driver and direct app support than Linux Installer and desktop have some quirks and bugs App-store is cumbersome, inferior to TrueOS ##Beastie Bits EuroBSDCon 2018 and NetBSD sanitizers New mandoc feature: -T html -O toc EuroBSDcon 2018 Polish BSD User Group garbage[43]: What year is it? The Demo @ 50 Microsoft ports DTrace from FreeBSD to Windows 10 OpenBSD joins Twitter NetBSD curses ripoffline improvements FCP-0101: Deprecating most 10/100 Ethernet drivers Announcing the pkgsrc-2018Q3 release Debian on OpenBSD vmd (without qemu or another debian system) A BSD authentication module for duress passwords (Joshua Stein) Disk Price/Performance Analysis ##Feedback/Questions DJ - Zombie ZFS Josua - arm tier 1? how to approach it -Gamah - 5ghz Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

Joshua Stein from Harbor talks about tokenized securities. Key takeaways: Compliance-focused tokenized securities are the future Build decentralized platforms to capture a greater market, and Low-friction transactions are always a great sell Full show notes at http://wing.vc/

We recap vBSDcon, give you the story behind a PF EN, reminisce in Solaris memories, and show you how to configure different DEs on FreeBSD. This episode was brought to you by Headlines [vBSDCon] vBSDCon was held September 7 - 9th. We recorded this only a few days after getting home from this great event. Things started on Wednesday night, as attendees of the thursday developer summit arrived and broke into smallish groups for disorganized dinner and drinks. We then held an unofficial hacker lounge in a medium sized seating area, working and talking until we all decided that the developer summit started awfully early tomorrow. The developer summit started with a light breakfast and then then we dove right in Ed Maste started us off, and then Glen Barber gave a presentation about lessons learned from the 11.1-RELEASE cycle, and comparing it to previous releases. 11.1 was released on time, and was one of the best releases so far. The slides are linked on the DevSummit wiki page (https://wiki.freebsd.org/DevSummit/20170907). The group then jumped into hackmd.io a collaborative note taking application, and listed of various works in progress and upstreaming efforts. Then we listed wants and needs for the 12.0 release. After lunch we broke into pairs of working groups, with additional space for smaller meetings. The first pair were, ZFS and Toolchain, followed by a break and then a discussion of IFLIB and network drivers in general. After another break, the last groups of the day met, pkgbase and secure boot. Then it was time for the vBSDCon reception dinner. This standing dinner was a great way to meet new people, and for attendees to mingle and socialize. The official hacking lounge Thursday night was busy, and included some great storytelling, along with a bunch of work getting done. It was very encouraging to watch a struggling new developer getting help from a seasoned veteran. Watching the new developers eyes light up as the new information filled in gaps and they now understood so much more than just a few minutes before, and they raced off to continue working, was inspirational, and reminded me why these conferences are so important. The hacker lounge shut down relatively early by BSD conference standards, but, the conference proper started at 8:45 sharp the next morning, so it made sense. Friday saw a string of good presentations, I think my favourite was Jonathan Anderson's talk on Oblivious sandboxing. Jonathan is a very energetic speaker, and was able to keep everyone focused even during relatively complicated explanations. Friday night I went for dinner at ‘Big Bowl', a stir-fry bar, with a largish group of developers and users of both FreeBSD and OpenBSD. The discussions were interesting and varied, and the food was excellent. Benedict had dinner with JT and some other folks from iXsystems. Friday night the hacker lounge was so large we took over a bigger room (it had better WiFi too). Saturday featured more great talks. The talk I was most interested in was from Eric McCorkle, who did the EFI version of my GELIBoot work. I had reviewed some of the work, but it was interesting to hear the story of how it happened, and to see the parallels with my own story. My favourite speaker was Paul Vixie, who gave a very interesting talk about the gets() function in libc. gets() was declared unsafe before the FreeBSD project even started. The original import of the CSRG code into FreeBSD includes the compile time, and run-time warnings against using gets(). OpenBSD removed gets() in version 5.6, in 2014. Following Paul's presentation, various patches were raised, to either cause use of gets() to crash the program, or to remove gets() entirely, causing such programs to fail to link. The last talk before the closing was Benedict's BSD Systems Management with Ansible (https://people.freebsd.org/~bcr/talks/vBSDcon2017_Ansible.pdf). Shortly after, Allan won a MacBook Pro by correctly guessing the number of components in a jar that was standing next to the registration desk (Benedict was way off, but had a good laugh about the unlikely future Apple user). Saturday night ended with the Conference Social, and excellent dinner with more great conversations On Sunday morning, a number of us went to the Smithsonian Air and Space Museum site near the airport, and saw a Concorde, an SR-71, and the space shuttle Discovery, among many other exhibits. Check out the full photo album by JT (https://t.co/KRmSNzUSus), our producer. Thanks to all the sponsors for vBSDcon and all the organizers from Verisign, who made it such a great event. *** The story behind FreeBSD-EN-17.08.pf (https://www.sigsegv.be//blog/freebsd/FreeBSD-EN-17.08.pf) After our previous deep dive on a bug in episode 209, Kristof Provost, the maintainer of pf on FreeBSD (he is going to hate me for saying that) has written the story behind a recent ERRATA notice for FreeBSD First things first, so I have to point out that I think Allan misremembered things. The heroic debugging story is PR 219251, which I'll try to write about later. FreeBSD-EN-17:08.pf is an issue that affected some FreeBSD 11.x systems, where FreeBSD would panic at startup. There were no reports for CURRENT. There's very little to go on here, but we do know the cause of the panic ("integer divide fault"), and that the current process was "pf purge". The pf purge thread is part of the pf housekeeping infrastructure. It's a housekeeping kernel thread which cleans up things like old states and expired fragments. The lack of mention of pf functions in the backtrace is a hint unto itself. It suggests that the error is probably directly in pfpurgethread(). It might also be in one of the static functions it calls, because compilers often just inline those so they don't generate stack frames. Remember that the problem is an "integer divide fault". How can integer divisions be a problem? Well, you can try to divide by zero. The most obvious suspect for this is this code: idx = pfpurgeexpiredstates(idx, pfhashmask / (Vpfdefaultrule.timeout[PFTMINTERVAL] * 10)); However, this variable is both correctly initialised (in pfattachvnet()) and can only be modified through the DIOCSETTIMEOUT ioctl() call and that one checks for zero. At that point I had no idea how this could happen, but because the problem did not affect CURRENT I looked at the commit history and found this commit from Luiz Otavio O Souza: Do not run the pf purge thread while the VNET variables are not initialized, this can cause a divide by zero (if the VNET initialization takes to long to complete). Obtained from: pfSense Sponsored by: Rubicon Communications, LLC (Netgate) That sounds very familiar, and indeed, applying the patch fixed the problem. Luiz explained it well: it's possible to use Vpfdefaultrule.timeout before it's initialised, which caused this panic. To me, this reaffirms the importance of writing good commit messages: because Luiz mentioned both the pf purge thread and the division by zero I was easily able to find the relevant commit. If I hadn't found it this fix would have taken a lot longer. Next week we'll look at the more interesting story I was interested in, which I managed to nag Kristof into writing *** The sudden death and eternal life of Solaris (http://dtrace.org/blogs/bmc/2017/09/04/the-sudden-death-and-eternal-life-of-solaris/) A blog post from Bryan Cantrill about the death of Solaris As had been rumored for a while, Oracle effectively killed Solaris. When I first saw this, I had assumed that this was merely a deep cut, but in talking to Solaris engineers still at Oracle, it is clearly much more than that. It is a cut so deep as to be fatal: the core Solaris engineering organization lost on the order of 90% of its people, including essentially all management. Of note, among the engineers I have spoken with, I heard two things repeatedly: “this is the end” and (from those who managed to survive Friday) “I wish I had been laid off.” Gone is any of the optimism (however tepid) that I have heard over the years — and embarrassed apologies for Oracle's behavior have been replaced with dismay about the clumsiness, ineptitude and callousness with which this final cut was handled. In particular, that employees who had given their careers to the company were told of their termination via a pre-recorded call — “robo-RIF'd” in the words of one employee — is both despicable and cowardly. To their credit, the engineers affected saw themselves as Sun to the end: they stayed to solve hard, interesting problems and out of allegiance to one another — not out of any loyalty to the broader Oracle. Oracle didn't deserve them and now it doesn't have them — they have been liberated, if in a depraved act of corporate violence. Assuming that this is indeed the end of Solaris (and it certainly looks that way), it offers a time for reflection. Certainly, the demise of Solaris is at one level not surprising, but on the other hand, its very suddenness highlights the degree to which proprietary software can suffer by the vicissitudes of corporate capriciousness. Vulnerable to executive whims, shareholder demands, and a fickle public, organizations can simply change direction by fiat. And because — in the words of the late, great Roger Faulkner — “it is easier to destroy than to create,” these changes in direction can have lasting effect when they mean stopping (or even suspending!) work on a project. Indeed, any engineer in any domain with sufficient longevity will have one (or many!) stories of exciting projects being cancelled by foolhardy and myopic management. For software, though, these cancellations can be particularly gutting because (in the proprietary world, anyway) so many of the details of software are carefully hidden from the users of the product — and much of the innovation of a cancelled software project will likely die with the project, living only in the oral tradition of the engineers who knew it. Worse, in the long run — to paraphrase Keynes — proprietary software projects are all dead. However ubiquitous at their height, this lonely fate awaits all proprietary software. There is, of course, another way — and befitting its idiosyncratic life and death, Solaris shows us this path too: software can be open source. In stark contrast to proprietary software, open source does not — cannot, even — die. Yes, it can be disused or rusty or fusty, but as long as anyone is interested in it at all, it lives and breathes. Even should the interest wane to nothing, open source software survives still: its life as machine may be suspended, but it becomes as literature, waiting to be discovered by a future generation. That is, while proprietary software can die in an instant, open source software perpetually endures by its nature — and thrives by the strength of its communities. Just as the existence of proprietary software can be surprisingly brittle, open source communities can be crazily robust: they can survive neglect, derision, dissent — even sabotage. In this regard, I speak from experience: from when Solaris was open sourced in 2005, the OpenSolaris community survived all of these things. By the time Oracle bought Sun five years later in 2010, the community had decided that it needed true independence — illumos was born. And, it turns out, illumos was born at exactly the right moment: shortly after illumos was announced, Oracle — in what remains to me a singularly loathsome and cowardly act — silently re-proprietarized Solaris on August 13, 2010. We in illumos were indisputably on our own, and while many outsiders gave us no chance of survival, we ourselves had reason for confidence: after all, open source communities are robust because they are often united not only by circumstance, but by values, and in our case, we as a community never lost our belief in ZFS, Zones, DTrace and myriad other technologies like MDB, FMA and Crossbow. Indeed, since 2010, illumos has thrived; illumos is not only the repository of record for technologies that have become cross-platform like OpenZFS, but we have also advanced our core technologies considerably, while still maintaining highest standards of quality. Learning some of the mistakes of OpenSolaris, we have a model that allows for downstream innovation, experimentation and differentiation. For example, Joyent's SmartOS has always been focused on our need for a cloud hypervisor (causing us to develop big features like hardware virtualization and Linux binary compatibility), and it is now at the heart of a massive buildout for Samsung (who acquired Joyent a little over a year ago). For us at Joyent, the Solaris/illumos/SmartOS saga has been formative in that we have seen both the ill effects of proprietary software and the amazing resilience of open source software — and it very much informed our decision to open source our entire stack in 2014. Judging merely by its tombstone, the life of Solaris can be viewed as tragic: born out of wedlock between Sun and AT&T and dying at the hands of a remorseless corporate sociopath a quarter century later. And even that may be overstating its longevity: Solaris may not have been truly born until it was made open source, and — certainly to me, anyway — it died the moment it was again made proprietary. But in that shorter life, Solaris achieved the singular: immortality for its revolutionary technologies. So while we can mourn the loss of the proprietary embodiment of Solaris (and we can certainly lament the coarse way in which its technologists were treated!), we can rejoice in the eternal life of its technologies — in illumos and beyond! News Roundup OpenBSD on the Lenovo Thinkpad X1 Carbon (5th Gen) (https://jcs.org/2017/09/01/thinkpad_x1c) Joshua Stein writes about his experiences running OpenBSD on the 5th generation Lenovo Thinkpad X1 Carbon: ThinkPads have sort of a cult following among OpenBSD developers and users because the hardware is basic and well supported, and the keyboards are great to type on. While no stranger to ThinkPads myself, most of my OpenBSD laptops in recent years have been from various vendors with brand new hardware components that OpenBSD does not yet support. As satisfying as it is to write new kernel drivers or extend existing ones to make that hardware work, it usually leaves me with a laptop that doesn't work very well for a period of months. After exhausting efforts trying to debug the I2C touchpad interrupts on the Huawei MateBook X (and other 100-Series Intel chipset laptops), I decided to take a break and use something with better OpenBSD support out of the box: the fifth generation Lenovo ThinkPad X1 Carbon. Hardware Like most ThinkPads, the X1 Carbon is available in a myriad of different internal configurations. I went with the non-vPro Core i7-7500U (it was the same price as the Core i5 that I normally opt for), 16Gb of RAM, a 256Gb NVMe SSD, and a WQHD display. This generation of X1 Carbon finally brings a thinner screen bezel, allowing the entire footprint of the laptop to be smaller which is welcome on something with a 14" screen. The X1 now measures 12.7" wide, 8.5" deep, and 0.6" thick, and weighs just 2.6 pounds. While not available at initial launch, Lenovo is now offering a WQHD IPS screen option giving a resolution of 2560x1440. Perhaps more importantly, this display also has much better brightness than the FHD version, something ThinkPads have always struggled with. On the left side of the laptop are two USB-C ports, a USB-A port, a full-size HDMI port, and a port for the ethernet dongle which, despite some reviews stating otherwise, is not included with the laptop. On the right side is another USB-A port and a headphone jack, along with a fan exhaust grille. On the back is a tray for the micro-SIM card for the optional WWAN device, which also covers the Realtek microSD card reader. The tray requires a paperclip to eject which makes it inconvenient to remove, so I think this microSD card slot is designed to house a card semi-permanently as a backup disk or something. On the bottom are the two speakers towards the front and an exhaust grille near the center. The four rubber feet are rather plastic feeling, which allows the laptop to slide around on a desk a bit too much for my liking. I wish they were a bit softer to be stickier. Charging can be done via either of the two USB-C ports on the left, though I wish more vendors would do as Google did on the Chromebook Pixel and provide a port on both sides. This makes it much more convenient to charge when not at one's desk, rather than having to route a cable around to one specific side. The X1 Carbon includes a 65W USB-C PD with a fixed USB-C cable and removable country-specific power cable, which is not very convenient due to its large footprint. I am using an Apple 61W USB-C charger and an Anker cable which charge the X1 fine (unlike HP laptops which only work with HP USB-C chargers). Wireless connectivity is provided by a removable Intel 8265 802.11a/b/g/n/ac WiFi and Bluetooth 4.1 card. An Intel I219-V chip provides ethernet connectivity and requires an external dongle for the physical cable connection. The screen hinge is rather tight, making it difficult to open with one hand. The tradeoff is that the screen does not wobble in the least bit when typing. The fan is silent at idle, and there is no coil whine even under heavy load. During a make -j4 build, the fan noise is reasonable and medium-pitched, rather than a high-pitched whine like on some laptops. The palm rest and keyboard area remain cool during high CPU utilization. The full-sized keyboard is backlit and offers two levels of adjustment. The keys have a soft surface and a somewhat clicky feel, providing very quiet typing except for certain keys like Enter, Backspace, and Escape. The keyboard has a reported key travel of 1.5mm and there are dedicated Page Up and Page Down keys above the Left and Right arrow keys. Dedicated Home, End, Insert, and Delete keys are along the top row. The Fn key is placed to the left of Control, which some people hate (although Lenovo does provide a BIOS option to swap it), but it's in the same position on Apple keyboards so I'm used to it. However, since there are dedicated Page Up, Page Down, Home, and End keys, I don't really have a use for the Fn key anyway. Firmware The X1 Carbon has a very detailed BIOS/firmware menu which can be entered with the F1 key at boot. F12 can be used to temporarily select a different boot device. A neat feature of the Lenovo BIOS is that it supports showing a custom boot logo instead of the big red Lenovo logo. From Windows, download the latest BIOS Update Utility for the X1 Carbon (my model was 20HR). Run it and it'll extract everything to C:driversflash(some random string). Drop a logo.gif file in that directory and run winuptp.exe. If a logo file is present, it'll ask whether to use it and then write the new BIOS to its staging area, then reboot to actually flash it. + OpenBSD support Secure Boot has to be disabled in the BIOS menu, and the "CSM Support" option must be enabled, even when "UEFI/Legacy Boot" is left on "UEFI Only". Otherwise the screen will just go black after the OpenBSD kernel loads into memory. Based on this component list, it seems like everything but the fingerprint sensor works fine on OpenBSD. *** Configuring 5 different desktop environments on FreeBSD (https://www.linuxsecrets.com/en/entry/51-freebsd/2017/09/04/2942-configure-5-freebsd-x-environments) This fairly quick tutorial over at LinuxSecrets.com is a great start if you are new to FreeBSD, especially if you are coming from Linux and miss your favourite desktop environment It just goes to show how easy it is to build the desktop you want on modern FreeBSD The tutorial covers: GNOME, KDE, Xfce, Mate, and Cinnamon The instructions for each boil down to some variation of: Install the desktop environment and a login manager if it is not included: > sudo pkg install gnome3 Enable the login manager, and usually dbus and hald: > sudo sysrc dbusenable="YES" haldenable="YES" gdmenable="YES" gnomeenable="YES"? If using a generic login manager, add the DE startup command to your .xinitrc: > echo "exec cinnamon" > ~/.xinitrc And that is about it. The tutorial goes into more detail on other configuration you can do to get your desktop just the way you like it. To install Lumina: > sudo pkg install lumina pcbsd-utils-qt5 This will install Lumina and the pcbsd utilities package which includes pcdm, the login manager. In the near future we hear the login manager and some of the other utilities will be split into separate packages, making it easier to use them on vanilla FreeBSD. > sudo sysrc pcdmenable=”YES” dbusenable="YES" hald_enable="YES" Reboot, and you should be greeted with the graphical login screen *** A return-oriented programming defense from OpenBSD (https://lwn.net/Articles/732201/) We talked a bit about RETGUARD last week, presenting Theo's email announcing the new feature Linux Weekly News has a nice breakdown on just how it works Stack-smashing attacks have a long history; they featured, for example, as a core part of the Morris worm back in 1988. Restrictions on executing code on the stack have, to a great extent, put an end to such simple attacks, but that does not mean that stack-smashing attacks are no longer a threat. Return-oriented programming (ROP) has become a common technique for compromising systems via a stack-smashing vulnerability. There are various schemes out there for defeating ROP attacks, but a mechanism called "RETGUARD" that is being implemented in OpenBSD is notable for its relative simplicity. In a classic stack-smashing attack, the attack code would be written directly to the stack and executed there. Most modern systems do not allow execution of on-stack code, though, so this kind of attack will be ineffective. The stack does affect code execution, though, in that the call chain is stored there; when a function executes a "return" instruction, the address to return to is taken from the stack. An attacker who can overwrite the stack can, thus, force a function to "return" to an arbitrary location. That alone can be enough to carry out some types of attacks, but ROP adds another level of sophistication. A search through a body of binary code will turn up a great many short sequences of instructions ending in a return instruction. These sequences are termed "gadgets"; a large program contains enough gadgets to carry out almost any desired task — if they can be strung together into a chain. ROP works by locating these gadgets, then building a series of stack frames so that each gadget "returns" to the next. There is, of course, a significant limitation here: a ROP chain made up of exclusively polymorphic gadgets will still work, since those gadgets were not (intentionally) created by the compiler and do not contain the return-address-mangling code. De Raadt acknowledged this limitation, but said: "we believe once standard-RET is solved those concerns become easier to address separately in the future. In any case a substantial reduction of gadgets is powerful". Using the compiler to insert the hardening code greatly eases the task of applying RETGUARD to both the OpenBSD kernel and its user-space code. At least, that is true for code written in a high-level language. Any code written in assembly must be changed by hand, though, which is a fair amount of work. De Raadt and company have done that work; he reports that: "We are at the point where userland and base are fully working without regressions, and the remaining impacts are in a few larger ports which directly access the return address (for a variety of reasons)". It can be expected that, once these final issues are dealt with, OpenBSD will ship with this hardening enabled. The article wonders about applying the same to Linux, but notes it would be difficult because the Linux kernel cannot currently be compiled using LLVM If any benchmarks have been run to determine the cost of using RETGUARD, they have not been publicly posted. The extra code will make the kernel a little bigger, and the extra overhead on every function is likely to add up in the end. But if this technique can make the kernel that much harder to exploit, it may well justify the extra execution overhead that it brings with it. All that's needed is somebody to actually do the work and try it out. Videos from BSDCan have started to appear! (https://www.youtube.com/playlist?list=PLeF8ZihVdpFfVEsCxNWGDmcATJfRZacHv) Henning Brauer: tcp synfloods - BSDCan 2017 (https://www.youtube.com/watch?v=KuHepyI0_KY) Benno Rice: The Trouble with FreeBSD - BSDCan 2017 (https://www.youtube.com/watch?v=1DM5SwoXWSU) Li-Wen Hsu: Continuous Integration of The FreeBSD Project - BSDCan 2017 (https://www.youtube.com/watch?v=SCLfKWaUGa8) Andrew Turner: GENERIC ARM - BSDCan 2017 (https://www.youtube.com/watch?v=gkYjvrFvPJ0) Bjoern A. Zeeb: From the outside - BSDCan 2017 (https://www.youtube.com/watch?v=sYmW_H6FrWo) Rodney W. Grimes: FreeBSD as a Service - BSDCan 2017 (https://www.youtube.com/watch?v=Zf9tDJhoVbA) Reyk Floeter: The OpenBSD virtual machine daemon - BSDCan 2017 (https://www.youtube.com/watch?v=Os9L_sOiTH0) Brian Kidney: The Realities of DTrace on FreeBSD - BSDCan 2017 (https://www.youtube.com/watch?v=NMUf6VGK2fI) The rest will continue to trickle out, likely not until after EuroBSDCon *** Beastie Bits Oracle has killed sun (https://meshedinsights.com/2017/09/03/oracle-finally-killed-sun/) Configure Thunderbird to send patch friendly (http://nanxiao.me/en/configure-thunderbird-to-send-patch-friendly/) FreeBSD 10.4-BETA4 Available (https://www.freebsd.org/news/newsflash.html#event20170909:01) iXsystems looking to hire kernel and zfs developers (especially Sun/Oracle Refugees) (https://www.facebook.com/ixsystems/posts/10155403417921508) Speaking of job postings, UnitedBSD.com has few job postings related to BSD (https://unitedbsd.com/) Call for papers USENIX FAST ‘18 - February 12-15, 2018, Due: September 28 2017 (https://www.freebsdfoundation.org/news-and-events/call-for-papers/usenix-fast-18-call-for-papers/) Scale 16x - March 8-11, 2018, Due: October 31, 2017 (https://www.freebsdfoundation.org/news-and-events/call-for-papers/scale-16x-call-for-participation/) FOSDEM ‘18 - February 3-4, 2018, Due: November 3 2017 (https://www.freebsdfoundation.org/news-and-events/call-for-papers/fosdem-18-call-for-participation/) Feedback/Questions Jason asks about cheap router hardware (http://dpaste.com/340KRHG) Prashant asks about latest kernels with freebsd-update (http://dpaste.com/2J7DQQ6) Matt wants know about VM Performance & CPU Steal Time (http://dpaste.com/1H5SZ81) John has config questions regarding Dell precision 7720, FreeBSD, NVME, and ZFS (http://dpaste.com/0X770SY) ***

Don’t get out of your comfort zone – get into it!  Joshua Stein Bio  Joshua Stein is a leading US commercial real estate attorney.  He’s the author of 4 books and over 140 articles on topics including practicing law in ‘plain english’ and negotiating.  His practice focuses on ground leases, hotel related transactions and unusual forms of collateral. No lunches, no dinners, and no calls to check in. Great legal work, fast. Find what you’re comfortable doing that consistently brings in work. Do something: if it doesn’t produce work, do something else. An event invitation puts you on radar.    Don’t try to convert people into clients.  Be out there.   The clients will follow through referrals. Have a strong bedside manner – care about your clients, take matters personally, look beyond the document, express your views to the client. Be a member of the client’s team. Follow the money, pay attention and think to understand the transaction.

This episode is brought to you by ftp, the Internet file transfer program, which first appeared in 4.2BSD. An interview with the hosts of the Garbage Podcast, joshua stein and Brandon Mercer. You can find their podcast at http://garbage.fm/File Info: 17Min, 8MB.Ogg Link: https://archive.org/download/bsdtalk263/bsdtalk263.ogg

This week, Allan is out of town at another Developer Summit, but we have a great episode coming This episode was brought to you by iX Systems Mission Complete (https://www.ixsystems.com/missioncomplete/) Submit your story of how you accomplished a mission with FreeBSD, FreeNAS, or iXsystems hardware, and you could win monthly prizes, and have your story featured in the FreeBSD Journal! *** Headlines WhatsApp founder, on how it got so HUGE (http://www.wired.com/2015/10/whatsapps-co-founder-on-how-the-iconoclastic-app-got-huge/) Wired has interviewed WhatsApp co-founder Brian Acton, about the infrastructure behind WhatsApp WhatsApp manages 900 million users with a team of 50, while Twitter needs around 4,000 employees to manage 300 million users. “FreeBSD has a nicely tuned network stack and extremely good reliability. We find managing FreeBSD installations to be quite straightforward.” “Linux is a beast of complexity. FreeBSD has the advantage of being a single distribution with an extraordinarily good ports collection.” “To us, it has been an advantage as we have had very few problems that have occurred at the OS level. With Linux, you tend to have to wrangle more and you want to avoid that if you can.” “FreeBSD happened because both Jan and I have experience with FreeBSD from Yahoo!.” Additional Coverage (http://uk.businessinsider.com/whatsapp-built-using-erlang-and-freebsd-2015-10) *** User feedback in the SystemD vs BSD init (https://www.textplain.net/blog/2015/problems-with-systemd-and-why-i-like-bsd-init/) We have a very detailed blog post this week from Randy Westlund, about his experiences on Linux and BSD, contrasting the init systems. What he finds is that while, it does make some things easier, such as writing a service file once, and having it run everywhere, the tradeoff comes in the complexity and lack of transparency. Another area of concern was the reproducibility of boots, how in his examples on servers, there can often be times when services start in different orders, to save a few moments of boot-time. His take on the simplicity of BSD's startup scripts is that they are very easy to hack on and monitor, while not introducing the feature creep we have seen in sysd. It will be interesting to see NextBSD / LaunchD and how it compares in the future! *** Learn to embrace open source, or get buried (http://opensource.com/business/15/10/ato-interview-jim-salter) At the recent “All Things Open” conference, opensource.com interviewed Jim Salter He describes how he first got started using FreeBSD to host his personal website He then goes on to talk about starting FreeBSDWiki.net and what its goals were The interview then talks about using Open Source at solve customers' problems at his consulting firm Finally, the talks about his presentation at AllThingsOpen: Move Over, Rsync (http://allthingsopen.org/talks/move-over-rsync/) about switching to ZFS replication *** HP's CTO Urges businesses to avoid permissive licenses (http://lwn.net/Articles/660428/) Martin Fink went on a rant about the negative effects of license proliferation While I agree that having too many new licenses is confusing and adds difficulty, I didn't agree with his closing point “He then ended the session with an extended appeal to move the open-source software industry away from permissive licenses like Apache 2.0 and toward copyleft licenses like the GPL” “The Apache 2.0 license is currently the most widely used "permissive" license. But the thing that developers overlook when adopting it, he said, is that by using Apache they are also making a choice about how much work they will have to put into building any sort of community around the project. If you look at Apache-licensed projects, he noted, "you'll find that they are very top-heavy with 'governance' structures." Technical committees, working groups, and various boards, he said, are needed to make such projects function. But if you look at copyleft projects, he added, you find that those structures simply are not needed.” There are plenty of smaller permissively licensed projects that do not have this sort of structure, infact, most of this structure comes from being an Apache run project, rather than from using the Apache or any other permissive license Luckily, he goes on to state that the “OpenSwitch code is released under the Apache 2.0 license, he said, because the other partner companies viewed that as a requirement.” “HP wanted to get networking companies and hardware suppliers on board. In order to get all of the legal departments at all of the partners to sign on to the project, he said, HP was forced to go with a permissive license” Hopefully the trend towards permissive licenses continues Additionally, in a separate LWN post: RMS Says: “I am not saying that competitors to a GNU package are unjust or bad -- that isn't necessarily so. The pertinent point is that they are competitors. The goal of the GNU Project is for GNU to win the competition. Each GNU package is a part of the GNU system, and should contribute to the success of the GNU Project. Thus, each GNU package should encourage people to run other GNU packages rather than their competitors -- even competitors which are free software.” (http://lwn.net/Articles/659757/) Never thought I'd see RMS espousing vendor lock-in *** Interview - Brian Callahan - bcallah@devio.us (mailto:bcallah@devio.us) / @twitter (https://twitter.com/__briancallahan) The BSDs in Education *** News Roundup Digital Libraries in Africa making use of DragonflyBSD and HAMMER (http://lists.dragonflybsd.org/pipermail/users/2015-October/228403.html) In the international development context, we have an interesting post from Michael Wilson of the PeerCorps Trust Fund. They are using DragonFlyBSD and FreeBSD to support the Tanzanian Digital Library Initiative in very resource-limited settings. They cite among the most important reasons for using BSD as the availability and quality of the documentation, as well as the robustness of the filesystems, both ZFS and HAMMER. Their website is now online over at (http://www.tandli.com/) , check it out to see exactly how BSD is being used in the field *** netflix hits > 65gbps from a single freebsd box (https://twitter.com/ed_maste/status/655120086248763396) A single socket server, with a high end Xeon E5 processor and a dual ported Chelsio T580 (2x 40 Gbps ports) set a netflix record pushing over 65 Gbps of traffic from a single machine The videos were being pushed from SSDs and some new high end NVMe devices The previous record at Netflix was 52 Gbps from a single machine, but only with very experimental settings. The current work is under much more typical settings By the end of that night, traffic surged to over 70 Gbps Only about 10-15% of that traffic was encrypted with the in-kernel TLS engine that Netflix has been working on with John-Mark Gurney It was reported that the machine was only using about 65% cpu, and had plenty of head room If I remember the discussion correctly, there were about 60,000 streams running off the machine *** Lumina Desktop 0.8.7 has been released (http://lumina-desktop.org/lumina-desktop-0-8-7-released/) A very large update has landed for PC-BSD's Lumina desktop A brand new “Start” menu has been added, which enables quick launch of favorite apps, pinning to desktop / favorites and more. Desktop icons have been overhauled, with better font support, and a new Grid system for placement of icons. Support for other BSD's such as DragonFly has been improved, along with TONS of internal changes to functionality and backends. Almost too many things to list here, but the link above will have full details, along with screenshots. *** A LiveUSB for NetBSD has been released by Jibbed (http://www.jibbed.org/) After a three year absence, the Jibbed project has come back with a Live USB image for NetBSD! The image contains NetBSD 7.0, and is fully R/W, allowing you to run the entire system from a single USB drive. Images are available for 8Gb and 4Gb sticks (64bit and 32bit respectively), along with VirtualBox images as well For those wanting X, it includes both X and TWM, although ‘pkgin' is available, so you can quickly add other desktops to the image *** Beastie Bits After recent discussions of revisiting W^X support in Mozilla Firefox, David Coppa has flipped the switch to enable it for OpenBSD users running -current. (http://undeadly.org/cgi?action=article&sid=20151021191401&mode=expanded) Using the vt(4) driver to change console resolution (http://lme.postach.io/post/changing-console-resolution-in-freebsd-10-with-vt-4) The FreeBSD Foundation gives a great final overview of the Grace Hopper Conference (http://freebsdfoundation.blogspot.com/2015/10/conference-recap-grace-hopper.html) A dialog about Compilers in the (BSD) base system (https://medium.com/@jmmv/compilers-in-the-bsd-base-system-1c4515a18c49) One upping their 48-core work from July, The Semihalf team shows off their the 96-core SMP support for FreeBSD on Cavium ThunderX (ARMv8 architecture (https://www.youtube.com/watch?v=1q5aDEt18mw) NYC Bug's November meeting will be featuring a talk by Stephen R. Bourne (http://lists.nycbug.org/pipermail/talk/2015-October/016384.html) New not-just-BSD postcast, hosted by two OpenBSD devs Brandon Mercer and Joshua Stein (http://garbage.fm/) Feedback/Questions Stefan (http://slexy.org/view/s21wjbhCJ4) Zach (http://slexy.org/view/s21TbKS5t0) Jake (http://slexy.org/view/s20AkO1i1R) Corey (http://slexy.org/view/s2nrUMatU5) Robroy (http://slexy.org/view/s2pZsC7arX) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv)

We finally get around to talking about oral argument on Oral Argument. And, oh do we do so in style. Supreme Court advocate and SCOTUSblog co-founder Tom Goldstein joins us for a portion of the show to talk about what oral arguments are, whether they are worth their costs, what they accomplish, and more. Joe complains about absurd hypotheticals. Christian is unfamiliar with any other kind. Also, we begin with errata, in which we acknowledge Christian’s abuse of the English language. This show’s links: Tom Goldstein’s profile and law firm SCOTUSblog and its About page Oral Argument Episode 17: Flesh List, with Kim Krawiec Kim’s posts here and here about her appearance and with some follow-up information Subsume Oyez, a resource for, among other things, audio of Supreme Court oral arguments dating back at least to the 1950s The U.S. Supreme Court’s own pages for oral argument transcripts and audio Barry Sullivan, Other Minds: The Use and Uses of Oral Argument Epstein, Landes, and Posner, Inferring the Winning Party in the Supreme Court from the Pattern of Questioning at Oral Argument Wikipedia, collecting sources, on Justice Thomas’ approach to oral argument The Oyez page for Loving v. Virginia, which links to the audio of the oral argument in the historic case striking down state bans on interracial marriage Ronald Collins, Hypothetically Speaking: Justice Breyer’s Dialectical Propensities Joshua Stein, Tentative Oral Opinions: Improving Oral Argument Without Spending a Dime Oyez page for Kelo v. City of New London Oral argument transcript in Alice Corp. v. CLS Bank Int’l, just search for “King Tut” within this document Adam Liptak, A Taxonomy of Supreme Court Humor Jay Wexler, Laugh Track II - Still Laughin’! Special Guest: Tom Goldtsein.