Podcasts about hyperthreading

The Personal Computer Show Wednesday October 16th 2024 PRN.live Streaming on the Internet 6:00 PM Eastern Time In the News  Geoffrey Hinton and John Hopfield of AI Receives the Nobel Physics Prize  AI Chatbots 'May Soon be More Intelligent than Us'  Social Media Becoming Synonymous with Cesspool for Children  DOJ Reveals Its Plan for Breaking Up Google's Search Monopoly  Google's Chromebook Strategy Shifts as Parallels for ChromeOS Faces Sunset ITPro Series with Benjamin Rockwell  Nerds Interested in Helping You From the Tech Corner  Impact of WFH (Work from Home) on Business Districts  Reasons Why Employers Want RTO (Return to Office)  The Hybrid Work Model: Balancing Work and Life  Intel killed Hyper-Threading on its desktop CPUs Technology Chatter with Benjamin Rockwell and Marty Winston  Google Pixel 9 Pro XL

High Yield joins to discuss if Intel Skymont IPC, RDNA 4 Price/Performance, and Nvidia RTX 5000! [SPON: Save 5% on OBSBOT Tiny 2 Lite w/ “OBSBOTspr” https://goo.su/GL480 / https://goo.su/zFbGuQ ] [SPON: Use "brokensilicon“ at CDKeyOffer to get Win 11 Pro for $23: https://www.cdkeyoffer.com/cko/Moore11 ] [SPON: Support MLID by checking out the COSWHEEL CT20: https://www.coswheelebike-eu.com/allot/transfer/1000226?redirectPath=%2Fproducts%2Fct20-ebike ] 0:00 Why was Max's first video about the Steam Deck? 6:41 Is AMD aggressive enough? 13:36 Has RDNA 3 met expectations with recent drivers? 18:27 Will Intel's LGA 1851 have longevity? 27:24 Meteor Lake vs Zen 2 - Who did chiplets better? 38:19 Why Intel's Future hinges on Arrow Lake succeeding! 44:17 Would Max bet that LNL is more efficient than Strix? 49:07 Is Intel sandbagging Arrow Lake IPC? 1:02:02 Will Diamond Rapids have Hyper-Threading? 1:08:08 Is Skymont any stronger than it SHOULD be? 1:14:45 Will AMD ever use Little Cores? 1:30:06 Qualcomm Snapdragon X Elite 1:41:48 Future of ARM on Windows - Nvidia? 1:49:33 AMD RDNA 4 Performance & Pricing Expectations 2:01:28 Nvidia RTX 5000 Expectations Check out High Yield's YouTube Channel: https://www.youtube.com/@HighYield Last time High Yield was on BS: https://youtu.be/ZL0AtNEkEL0?si=pG3WwVLMYTJMUkKx MLID Navi 48 Leak: https://youtu.be/Hbx4AUcQ5do?si=N2TZniAc7ZV7Z34D The Phawx X Elite Review: https://youtu.be/SVz7oGGG2jE?si=4e6x-IVXlcp6Imh- High Yield Lunar Lake Analysis: https://youtu.be/ba5w8rKwd_c?si=yVGxJLqGngVLYwCI https://x.com/carygolomb/status/1798299608663335180 https://www.guru3d.com/review/intel-core-i9-13900k-review/page-8/

We have RTX 4070 SUPER Benchmarks, Intel i9 Leaks, and more to discuss!!! [SPON: Use "brokensilicon“ at CDKeyOffer $16 Win10: https://www.cdkeyoffer.com/cko/Moore10 ] [SPON: Get 10% off Tasty Vite Ramen with code BROKENSILICON: https://bit.ly/3wKx6v1 ] 0:00 Minnesota vs Tennessee Winters (Intro Banter) 6:17 PS3 MLAA, Intel Foundry Services, AMD Laptop Support (Corrections) 15:30 RTX 4070 SUPER Analysis 26:13 RTX 4080 SUPER & RTX 4070 Ti SUPER Announced 42:22 How Nvidia plans to push 4070 Ti Sales after SUPER "launches"... 45:34 RX 7600 XT Releases next to BAD Mobile RADEON Sales 58:56 How can AMD afford to give a $329 GPU 16GB of VRAM? 1:00:11 Ryzen 7 8700G Announced, Hawk Point gets Rapid Adoption 1:11:40 AMD Hawk Point Benchmarks vs Meteor Lake Claims 1:18:13 Lunar Lake & Arrow Lake Details (kinda) Announced 1:25:06 Did Intel Arrow Lake once have Hyper-Threading? 1:31:52 Intel i9-14900KS Drama Leak, APO comes to 13th & 12th Gen 1:38:21 4090D, 7800M, 3050 6GB, MSI Claw, ARM Windows Exclusivity (Wrap-Up) 1:49:26 AMD mandating OCuLink, Devs Thoughts on FSR, Vite Vitality (Final RM) https://videocardz.com/newz/nvidia-rtx-4070-super-ad104-gpu-features-48mb-of-l2-cache-not-36mb-as-claimed-earlier https://www.techspot.com/review/1865-geforce-rtx-super/ https://videocardz.com/newz/custom-geforce-rtx-4070-super-cards-appear-at-retailers-for-up-to-650 https://youtu.be/gA-eKbi1QWU?si=x71xqQuaxlJ5dSGy https://www.nvidia.com/en-us/geforce/news/geforce-rtx-4080-4070-ti-4070-super-gpu/ https://www.computerbase.de/2024-01/gaming-notebooks-fuer-amd-radeon-rx-7000m-war-die-ces-ein-desaster/ https://www.anandtech.com/show/21215/amd-adds-radeon-rx-7600-xt-to-product-stack-16gb-1080p-gaming-card-for-329 https://videocardz.com/newz/ayaneo-and-gpd-launch-first-handhelds-with-ryzen-7-8840u-processor https://videocardz.com/newz/gpd-to-update-all-handheld-products-with-amd-ryzen-7-8840u-apu https://www.tomshardware.com/pc-components/cpus/amd-launches-ryzen-8000g-phoenix-apus-brings-ai-to-the-desktop-pc-reveals-zen-4c-clocks-for-the-first-time https://videocardz.com/newz/intel-shows-off-lunar-lake-with-memory-on-package-reaffirms-its-2024-plans-for-lunar-arrow-lake https://twitter.com/OneRaichu/status/1744537140451844344 https://www.pcgamer.com/intel-to-roll-out-14th-gens-game-optimization-software-to-older-1213th-gen-hybrid-cpus-after-all/ https://videocardz.com/newz/alleged-intel-core-i9-14900ks-6-2-ghz-cpu-has-been-pictured https://twitter.com/9550pro/status/1742151746598944892 https://www.youtube.com/watch?v=BGZMOK9l2Dc&ab_channel=KitGuruTech https://videocardz.com/newz/nvidia-geforce-rtx-4090d-is-6-slower-than-rtx-4090-in-first-test-oc-support-limited https://videocardz.com/newz/shipping-manifests-reveal-amd-cuarzo-gpus-as-navi-3x-series-hint-at-navi-32-mobile-rx-7800m https://videocardz.com/newz/nvidia-geforce-rtx-3050-6gb-to-feature-2304-cuda-cores-and-70w-tdp https://videocardz.com/newz/msi-claw-gaming-handheld-leaked-features-intel-core-ultra-7-155h-with-arc-graphics-and-32gb-memory https://www.youtube.com/watch?v=S1R08Qx6Fvs&ab_channel=Windows https://videocardz.com/newz/amd-enables-fluid-motion-frames-afmf-for-integrated-radeon-700m-series-through-preview-driver https://www.tomshardware.com/pc-components/cpus/windows-on-arm-may-be-a-thing-of-the-past-soon-arm-ceo-confirms-qualcomms-exclusivity-agreement-with-microsoft-expires-this-year#:~:text=The%20exact%20date%20the%20exclusivity,coming%20from%20AMD%20and%20Nvidia https://www.bleepingcomputer.com/news/security/framework-discloses-data-breach-after-accountant-gets-phished/ https://www.youtube.com/watch?v=eONWY3kbZc0&ab_channel=DigitalTrends https://www.youtube.com/watch?v=S1R08Qx6Fvs&ab_channel=Windows https://www.howtogeek.com/what-is-oculink/ https://www.amd.com/en/product/14066

A Game Dev joins to explain how Panther Lake's Architecture works, and what's next for RDNA 3. [SPON: dieshrink = 3% off Everything, brokensilicon = 25% off Windows: https://biitt.ly/shbSk ] [SPON: Get 10% off Tasty Vite Ramen with code BROKENSILICON: https://bit.ly/3wKx6v1 ] 0:00 Who is Bryan? Where does his pixel art talent come from? 14:16 Has Nvidia Lovelace & RDNA 3 ended up disappointing? 21:29 Will the PS5 Pro force better Utilization of RDNA 3? 32:23 The Future of Optimizing Games, Framerates, and Resolutions 55:16 Is Unreal Engine 5 ahead of it's time? 1:04:50 AMD vs Nvidia assistance to Developers 1:18:03 Will Arrow Lake suffer in games without Hyper-Threading? 1:33:14 Intel Royal Core IPC Leak, RU Explanation, Implications for Gamers 1:42:03 Zen 6 vs Panther Lake / Nova Lake 1:54:13 AI's Impact on Game Development 2:09:44 Will Game Developers Strike like Hollywood did? 2:29:26 How will AI Art Evolve? Can this be regulated? Previous Bryan Episode: https://youtu.be/nvjb8HPZbZU Bryan's Twitter Account: https://twitter.com/bryanheemskerk https://www.computerbase.de/2023-01/amd-radeon-rx-7900-xtx-adrenalin-22-12-2-test/ https://www.sportskeeda.com/gaming-tech/amd-radeon-rx-7900-xt-7900-xtx-get-massive-performance-boosts-latest-drivers https://youtu.be/ZuriVO-s26k https://youtu.be/lPu-OBGcA2s https://twitter.com/Sebasti66855537/status/1685389848603951111 https://www.youtube.com/watch?v=6O5XGVaPDZo https://www.youtube.com/watch?v=-ot96M9RM6o https://youtube.com/live/fJGMkr2F3to https://youtu.be/Kd0FX219-js

We discuss upcoming RDNA 3 Releases, Diamond Rapids, Beast Lake, & PlayStation 5 Pro! [SPON: Click https://nordvpn.com/moore to get the 2-year plan for 59% OFF + 1 Month FREE!] [SPON: dieshrink = 3% off Everything, brokensilicon = 25% off Windows: https://biitt.ly/shbSk ] [SPON: Get 10% off Tasty Vite Ramen with code BROKENSILICON: https://bit.ly/3wKx6v1 ] 0:00 Toucan Tom, Dan, Stupid Dogs, FPS, Sponsor Spam (Intro Banter) 10:25 APU RAM Usage, CPU Prices in 2023 vs 2012 (Corrections) 31:48 RX 7900 GRE, 7800, 7700 Details Confirmed 48:05 AM5 AGESA Allows for DDR5-8000 - Zen 4 Support Fixed? 53:03 AMD R9 7945HX3D Dragon Range-X Confirmed for ASUS 57:21 Arrow Lake Release Date, Performance, Thread Counts Leaked 1:11:52 Intel Nova Lake gets Rentable Units, not Hyper-Threading! 1:23:06 Intel Beats Earnings Estimates with very Bad Numbers 1:30:42 PlayStation 5 Pro Leaks - It's coming, how should XBOX respond? 1:47:12 Ratchet & Clank PC Performance, AVX-512 coming to E-Cores, Titan (Wrap-Up) 1:55:38 Remnant 2 PC Performance, A580 Cancelled (?), Direct Storage (Final RM) https://www.anandtech.com/show/2754 https://www.anandtech.com/show/4083/the-sandy-bridge-review-intel-core-i7-2600k-i5-2500k-core-i3-2100-tested/20 https://videocardz.com/newz/amd-radeon-rx-7900-gre-officially-launches-with-5120-cores-16gb-memory-and-260w-tbp-costs-649 https://www.amd.com/en/products/graphics/amd-radeon-rx-7900-gre https://youtu.be/laoZhtk1qgk https://www.tomshardware.com/news/amd-massively-improves-ddr5-support-8000mhz-feasible https://videocardz.com/newz/overclocker-hits-ddr5-9058-memory-oc-on-amd-am5-platform-with-new-firmware https://twitter.com/Buildzoid1/status/1681454391252094976 https://twitter.com/9550pro/status/1684576683666579456 https://www.techpowerup.com/311817/asus-republic-of-gamers-announces-rog-strix-scar-17-x3d-the-worlds-first-amd-ryzen-9-7945hx3d-laptop https://www.amd.com/en/products/apu/amd-ryzen-9-7945hx3d https://twitter.com/mooreslawisdead/status/1683572825641058304 https://www.amd.com/en/products/apu/amd-ryzen-7-7745hx https://youtu.be/ZuriVO-s26k?t=1019 https://youtu.be/ZuriVO-s26k?t=1456 https://www.intc.com/news-events/press-releases/detail/1637/intel-reports-second-quarter-2023-financial-results https://youtu.be/6O5XGVaPDZo https://youtu.be/-ot96M9RM6o https://twitter.com/Kepler_L2/status/1682429359091593216 https://keytogaming.com/2023/07/21/playstation-5-pro-project-trinity/ https://youtu.be/Qlqq7JrJujI https://twitter.com/InstLatX64/status/1683580336679288835 https://www.techpowerup.com/311600/amds-ryzen-5-7500f-gets-benchmarked-available-globally https://www.ebay.com/itm/293935938436 https://shop-us-en.amd.com/amd-radeon-rx-7600-graphics/ https://videocardz.com/press-release/samsung-introduces-worlds-first-gddr7-memory-up-to-32-gbps https://videocardz.com/newz/unreleased-quad-slot-nvidia-rtx-40-gpu-cooler-prototype-had-a-hidden-fan https://www.techpowerup.com/311831/sony-celebrates-playstation-5-surpassing-40-million-unit-sales https://youtu.be/lPu-OBGcA2s https://twitter.com/Sebasti66855537/status/1685389848603951111 https://twitter.com/Sebasti66855537/status/1683054228472733696 https://videocardz.com/newz/sparkle-to-introduce-arc-a380-a310-genie-low-profile-gpu-series

Aspire-ing to use 13 year hardware Dual boot image = /boot/vmlinuz root = /dev/sda3 label = Slackware15.0 read-only image = /boot/vmlinuz root = /dev/sda2 label = Slackware14.2 read-only First change # LILO configuration file # Append any additional kernel parameters: append="acpi=ht" Dropped CPU usage to 50% Second change grep . -r /sys/firmware/acpi/interrupts/ /sys/firmware/acpi/interrupts/gpe1D:322734808 STS enabled unmasked echo "mask" > /sys/firmware/acpi/interrupts/gpeXX Interrupts Interrupts My case was echo "mask" > /sys/firmware/acpi/interrupts/gpe1D Dropped usage to 0-5% Then added the mask to crontab -e under root Add 'acpi_mask_gpe=0x1D' or whatever interrupt corresponds to the overactive one, and remember to run the lilo command afterward to make the kernel option active. Htop options for CPU usage Click the thumbnail to see the full-sized image Htop display Upgrades Fan from AliExpress https://www.aliexpress.com/item/32861732299.html Replacement fan Click the thumbnail to see the full-sized image 2GB DDR2 667MHz SODIMM PC2-5300 https://www.amazon.com/gp/product/B00C53A37K 2Gb ram upgrade Click the thumbnail to see the full-sized image Resources https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/kernel_administration_guide/listing_of_kernel_parameters_and_values acpi=ht https://www.kernel.org/doc/ols/2005/ols2005v1-pages-59-76.pdf Use ACPI boot table parsing, but do not enable ACPI interpreter This disables any ACPI functionality that is not required for Hyper Threading. ACPI (Advanced Configuration and Power Interface) is an open industry specification establishing industry-standard interfaces for OS-directed configuration and power management on laptops, desktops, and servers. HPR3511 Podman like Vagrant https://archive.org/details/hpr3511

Why the Linux kernel received so much mainstream attention this week, some of our favorite open-source projects get great updates, and why we're concerned about Linux Foundation members transferring innovation from Linux to closed source software at an industrial scale.

Why the Linux kernel received so much mainstream attention this week, some of our favorite open-source projects get great updates, and why we're concerned about Linux Foundation members transferring innovation from Linux to closed source software at an industrial scale.

Why the Linux kernel received so much mainstream attention this week, some of our favorite open-source projects get great updates, and why we're concerned about Linux Foundation members transferring innovation from Linux to closed source software at an industrial scale.

COMPTIA A+ Terminology made easy for you !

COMPTIA A+ Terminology made easy for you !

COMPTIA A+ Terminology made easy for you !

Welcome to Hardware Addicts, a proud member of the Destination Linux Network. Hardware Addicts is the podcast that focuses on the physical components that powers our technology world. In this episode, we’re going to discuss a listeners question regarding simultaneous multi-threading or SMT. If you’ve ever wondered whether hyper-threading or SMT doubles your multi-core workload and whether there are there specific workloads that would benefit more from the hyper-threading...this episode is for you! We’re going to unravel these threads for you right here on this show. Then we head to Camera Corner where Wendy answers a question from the community about megapixels. Quick Links: Ryan = https://dasgeekcommunity.com Michael = https://tuxdigital.com Wendy = https://destinationlinux.network Want to Support the Show? Destination Linux Network Store = https://destinationlinux.network/store Want to follow the show and hosts on social media? You can find all of our social accounts at https://hardwareaddicts.org/hosts

Patrocinador: Estamos en el año 2020. De poco sirve hoy estudiar las decisiones que una empresa tomó en el siglo XX. Descubre una experiencia de aprendizaje learning-by-doing única basada en tres ejes clave: Entender, Aplicar y Experimentar. —  Infórmate sobre el MIB en la web de ISDI. Lakefield nifunifá / Reino Unido asoma la patita al patinete / Ransomware en Mac / Cambios en Android / El complicado mercado de videojuegos / Discos duros de 400 TB

Episode brought to you by Amazon (http://www.thinkcomputers.org/amazon).     Reviews This Week: Cooler Master MasterAir MA620M CPU Cooler Review (https://thinkcomputers.org/cooler-master-masterair-ma620m-cpu-cooler-review/) iStorage DatAshur PRO2 Review (https://thinkcomputers.org/istorage-datashur-pro2-review/) Other Stuff This Week: Case Mod Friday: Project CYBERPUNK 2077 (https://thinkcomputers.org/case-mod-friday-project-cyberpunk-2077/) Win a Corsair iCUE QL120 RGB 3-Fan Kit! (https://thinkcomputers.org/win-a-corsair-icue-ql120-rgb-3-fan-kit/) News This Week: The AMD Radeon RX 5500 XT has been Listed Online (https://thinkcomputers.org/the-amd-radeon-rx-5500-xt-has-been-listed-online/) Custom RX 5500 XT’s From Gigabyte & ASRock Spotted (https://thinkcomputers.org/custom-rx-5500-xts-from-gigabyte-asrock-spotted/) Sapphire’s $259 RX 5500 XT NITRO+ Special Edition Spotted (https://thinkcomputers.org/sapphires-259-rx-5500-xt-nitro-special-edition-spotted/) AMD Announces Radeon Software Adrenalin 2020 Edition (https://thinkcomputers.org/amd-announces-radeon-software-adrenalin-2020-edition/) Dell looking to AMD as an Alternative as Intel CPU Shortages Continue (https://thinkcomputers.org/dell-looking-to-amd-as-an-alternative-as-intel-cpu-shortages-continue/) Intel 10th Gen Comet Lake-S CPUs and Z490 Motherboards to Launch in April 2020 (https://thinkcomputers.org/intel-10th-gen-comet-lake-s-cpus-and-z490-motherboards-to-launch-in-april-2020/) The Next Core i5 Desktop Processor will feature HyperThreading (https://thinkcomputers.org/the-next-core-i5-desktop-processor-will-feature-hyperthreading/) VIPER GAMING by PATRIOT Unleashes VPR100 M.2 2280 PCIeGen3 x4 RGB Solid State Drive (https://thinkcomputers.org/viper-gaming-by-patriot-unleashes-vpr100-m-2-2280-pciegen3-x4-rgb-solid-state-drive/) New BioShock Game in Development by New “Cloud Chamber” Studio (https://thinkcomputers.org/new-bioshock-game-in-development-by-new-cloud-chamber-studio/) Coming Next Week: In Win 309 Case (https://www.in-win.com/en/gaming-chassis/309) Glorious PC Gaming Race Model O Gaming Mouse (https://www.pcgamingrace.com/products/glorious-model-o-black) AORUS CV27Q Gaming Monitor (https://www.aorus.com/CV27Q)

We discuss a number of issues in the news, such as a 17-year old Firefox vulnerability, the threat to end-to-end encryption, and whether Apple should offer a VPN. We also answer listening questions about browser fingerprinting - what is it? we explain - and turning off hyper-threading (we explain that too). AmIUnique Episode 83: Epic disasters: ZombieLoad, WhatsApp, Google 2FA Keys, and Microsoft RDP CPUSetter U.S. officials consider end-to-end encryption crackdown 17-Year-Old Weakness in Firefox Let HTML File Steal Other Files From Device Here’s the next big step Apple should take to protect our privacy Episode 57: The Advantages of Using a VPN, with CyberGhost Amazon confirms Alexa customer voice recordings are kept forever Get 40% off Mac Premium Bundle X9, fully compatible with macOS Mojave, with the code PODCAST19. Download Intego Mac Premium Bundle X9 now at intego.com.

This week TJ is playing Devil May Cry 5 and loving the series as much as ever! None of us have seen Captain Marvel yet, but it had a HUGE opening weekend with $455 million dollars globally. Cj talks about the newly patented Google controller, and we have some questions about it. At the end of our show, we talk about FourSquare's new Hyperthreading technology, which tracks you everywhere you go. --- Send in a voice message: https://anchor.fm/genfailcast/message Support this podcast: https://anchor.fm/genfailcast/support

Hyperthreading considered harmful, how to avoid lock screen hacks, and what happens when cryptocurrency exchanges implode. With Naked Security Editor-in-Chief Anna Brading, Paul Ducklin, Mark Stockley and Matthew Boddy. (Music: purple-planet.com)

Join The Full Nerd gang as they talk about the latest PC hardware topics. Today's show is all about Intel's Core i9-9900K, the news, the benchmarking controversy, and is this the end of mainstream hyperthreading?

Insight into TrueOS and Trident, stop evildoers with pf-badhost, Flashback to FreeBSDcon ‘99, OpenBSD’s measures against TLBleed, play Morrowind on OpenBSD in 5 steps, DragonflyBSD developers shocked at Threadripper performance, and more. ##Headlines An Insight into the Future of TrueOS BSD and Project Trident Last month, TrueOS announced that they would be spinning off their desktop offering. The team behind the new project, named Project Trident, have been working furiously towards their first release. They did take a few minutes to answer some of our question about Project Trident and TrueOS. I would like to thank JT and Ken for taking the time to compile these answers. It’s FOSS: What is Project Trident? Project Trident: Project Trident is the continuation of the TrueOS Desktop. Essentially, it is the continuation of the primary “TrueOS software” that people have been using for the past 2 years. The continuing evolution of the entire TrueOS project has reached a stage where it became necessary to reorganize the project. To understand this change, it is important to know the history of the TrueOS project. Originally, Kris Moore created PC-BSD. This was a Desktop release of FreeBSD focused on providing a simple and user-friendly graphical experience for FreeBSD. PC-BSD grew and matured over many years. During the evolution of PC-BSD, many users began asking for a server focused version of the software. Kris agreed, and TrueOS was born as a scaled down server version of PC-BSD. In late 2016, more contributors and growth resulted in significant changes to the PC-BSD codebase. Because the new development was so markedly different from the original PC-BSD design, it was decided to rebrand the project. TrueOS was chosen as the name for this new direction for PC-BSD as the project had grown beyond providing only a graphical front to FreeBSD and was beginning to make fundamental changes to the FreeBSD operating system. One of these changes was moving PC-BSD from being based on each FreeBSD Release to TrueOS being based on the active and less outdated FreeBSD Current. Other major changes are using OpenRC for service management and being more aggressive about addressing long-standing issues with the FreeBSD release process. TrueOS moved toward a rolling release cycle, twice a year, which tested and merged FreeBSD changes directly from the developer instead of waiting months or even years for the FreeBSD review process to finish. TrueOS also deprecated and removed obsolete technology much more regularly. As the TrueOS Project grew, the developers found these changes were needed by other FreeBSD-based projects. These projects began expressing interest in using TrueOS rather than FreeBSD as the base for their project. This demonstrated that TrueOS needed to again evolve into a distribution framework for any BSD project to use. This allows port maintainers and source developers from any BSD project to pool their resources and use the same source repositories while allowing every distribution to still customize, build, and release their own self-contained project. The result is a natural split of the traditional TrueOS team. There were now naturally two teams in the TrueOS project: those working on the build infrastructure and FreeBSD enhancements – the “core” part of the project, and those working on end-user experience and utility – the “desktop” part of the project. When the decision was made to formally split the projects, the obvious question that arose was what to call the “Desktop” project. As TrueOS was already positioned to be a BSD distribution platform, the developers agreed the desktop side should pick a new name. There were other considerations too, one notable being that we were concerned that if we continued to call the desktop project “TrueOS Desktop”, it would prevent people from considering TrueOS as the basis for their distribution because of misconceptions that TrueOS was a desktop-focused OS. It also helps to “level the playing field” for other desktop distributions like GhostBSD so that TrueOS is not viewed as having a single “blessed” desktop version. It’s FOSS: What features will TrueOS add to the FreeBSD base? Project Trident: TrueOS has already added a number of features to FreeBSD: OpenRC replaces rc.d for service management LibreSSL in base Root NSS certificates out-of-box Scriptable installations (pc-sysinstall) The full list of changes can be seen on the TrueOS repository (https://github.com/trueos/trueos/blob/trueos-master/README.md). This list does change quite regularly as FreeBSD development itself changes. It’s FOSS: I understand that TrueOS will have a new feature that will make creating a desktop spin of TrueOS very easy. Could you explain that new feature? Project Trident: Historically, one of the biggest hurdles for creating a desktop version of FreeBSD is that the build options for packages are tuned for servers rather than desktops. This means a desktop distribution cannot use the pre-built packages from FreeBSD and must build, use, and maintain a custom package repository. Maintaining a fork of the FreeBSD ports tree is no trivial task. TrueOS has created a full distribution framework so now all it takes to create a custom build of FreeBSD is a single JSON manifest file. There is now a single “source of truth” for the source and ports repositories that is maintained by the TrueOS team and regularly tagged with “stable” build markers. All projects can use this framework, which makes updates trivial. It’s FOSS: Do you think that the new focus of TrueOS will lead to the creation of more desktop-centered BSDs? Project Trident: That is the hope. Historically, creating a desktop-centered BSD has required a lot of specialized knowledge. Not only do most people not have this knowledge, but many do not even know what they need to learn until they start troubleshooting. TrueOS is trying to drastically simplify this process to enable the wider Open Source community to experiment, contribute, and enjoy BSD-based projects. It’s FOSS: What is going to happen to TrueOS Pico? Will Project Trident have ARM support? Project Trident: Project Trident will be dependent on TrueOS for ARM support. The developers have talked about the possibility of supporting ARM64 and RISC-V architectures, but it is not possible at the current time. If more Open Source contributors want to help develop ARM and RISC-V support, the TrueOS project is definitely willing to help test and integrate that code. It’s FOSS: What does this change (splitting Trus OS into Project Trident) mean for the Lumina desktop environment? Project Trident: Long-term, almost nothing. Lumina is still the desktop environment for Project Trident and will continue to be developed and enhanced alongside Project Trident just as it was for TrueOS. Short-term, we will be delaying the release of Lumina 2.0 and will release an updated version of the 1.x branch (1.5.0) instead. This is simply due to all the extra overhead to get Project Trident up and running. When things settle down into a rhythm, the development of Lumina will pick up once again. It’s FOSS: Are you planning on including any desktop environments besides Lumina? Project Trident: While Lumina is included by default, all of the other popular desktop environments will be available in the package repo exactly as they had been before. It’s FOSS: Any plans to include Steam to increase the userbase? Project Trident: Steam is still unavailable natively on FreeBSD, so we do not have any plans to ship it out of the box currently. In the meantime, we highly recommend installing the Windows version of Steam through the PlayOnBSD utility. It’s FOSS: What will happen to the AppCafe? Project Trident: The AppCafe is the name of the graphical interface for the “pkg” utility integrated into the SysAdm client created by TrueOS. This hasn’t changed. SysAdm, the graphical client, and by extension AppCafe are still available for all TrueOS-based distributions to use. It’s FOSS: Does Project Trident have any corporate sponsors lined up? If not, would you be open to it or would you prefer that it be community supported? Project Trident: iXsystems is the first corporate sponsor of Project Trident and we are always open to other sponsorships as well. We would prefer smaller individual contributions from the community, but we understand that larger project needs or special-purpose goals are much more difficult to achieve without allowing larger corporate sponsorships as well. In either case, Project Trident is always looking out for the best interests of the community and will not allow intrusive or harmful code to enter the project even if a company or individual tries to make that code part of a sponsorship deal. It’s FOSS: BSD always seems to be lagging in terms of support for newer devices. Will TrueOS be able to remedy that with a quicker release cycle? Project Trident: Yes! That was a primary reason for TrueOS to start tracking the CURRENT branch of FreeBSD in 2016. This allows for the changes that FreeBSD developers are making, including new hardware support, to be available much sooner than if we followed the FreeBSD release cycle. It’s FOSS: Do you have any idea when Project Trident will have its first release? Project Trident: Right now we are targeting a late August release date. This is because Project Trident is “kicking the wheels” on the new TrueOS distribution system. We want to ensure everything is working smoothly before we release. Going forward, we plan on having regular package updates every week or two for the end-user packages and a new release of Trident with an updated OS version every 6 months. This will follow the TrueOS release schedule with a small time offset. ###pf-badhost: Stop the evil doers in their tracks! pf-badhost is a simple, easy to use badhost blocker that uses the power of the pf firewall to block many of the internet’s biggest irritants. Annoyances such as ssh bruteforcers are largely eliminated. Shodan scans and bots looking for webservers to abuse are stopped dead in their tracks. When used to filter outbound traffic, pf-badhost blocks many seedy, spooky malware containing and/or compromised webhosts. Filtering performance is exceptional, as the badhost list is stored in a pf table. To quote the OpenBSD FAQ page regarding tables: “the lookup time on a table holding 50,000 addresses is only slightly more than for one holding 50 addresses.” pf-badhost is simple and powerful. The blocklists are pulled from quality, trusted sources. The ‘Firehol’, ‘Emerging Threats’ and ‘Binary Defense’ block lists are used as they are popular, regularly updated lists of the internet’s most egregious offenders. The pf-badhost.sh script can easily be expanded to use additional or alternate blocklists. pf-badhost works best when used in conjunction with unbound-adblock for the ultimate badhost blocking. Notes: If you are trying to run pf-badhost on a LAN or are using NAT, you will want to add a rule to your pf.conf appearing BEFORE the pf-badhost rules allowing traffic to and from your local subnet so that you can still access your gateway and any DNS servers. Conversely, adding a line to pf-badhost.sh that removes your subnet range from the table should also work. Just make sure you choose a subnet range / CIDR block that is actually in the list. 192.168.0.0/16, 172.16.0.0/12 and 10.0.0.0/8 are the most common home/office subnet ranges. DigitalOcean https://do.co/bsdnow ###FLASHBACK: FreeBSDCon’99: Fans of Linux’s lesser-known sibling gather for the first time FreeBSD, a port of BSD Unix to Intel, has been around almost as long as Linux has – but without the media hype. Its developer and user community recently got a chance to get together for the first time, and they did it in the city where BSD – the Berkeley Software Distribution – was born some 25 years ago. October 17, 1999 marked a milestone in the history of FreeBSD – the first FreeBSD conference was held in the city where it all began, Berkeley, CA. Over 300 developers, users, and interested parties attended from around the globe. This was easily 50 percent more people than the conference organizers had expected. This first conference was meant to be a gathering mostly for developers and FreeBSD advocates. The turnout was surprisingly (and gratifyingly) large. In fact, attendance exceeded expectations so much that, for instance, Kirk McKusick had to add a second, identical tutorial on FreeBSD internals, because it was impossible for everyone to attend the first! But for a first-ever conference, I was impressed by how smoothly everything seemed to go. Sessions started on time, and the sessions I attended were well-run; nothing seemed to be too cold, dark, loud, late, or off-center. Of course, the best part about a conference such as this one is the opportunity to meet with other people who share similar interests. Lunches and breaks were a good time to meet people, as was the Tuesday night beer bash. The Wednesday night reception was of a type unusual for the technical conferences I usually attend – a three-hour Hornblower dinner cruise on San Francisco Bay. Not only did we all enjoy excellent food and company, but we all got to go up on deck and watch the lights of San Francisco and Berkeley as we drifted by. Although it’s nice when a conference attracts thousands of attendees, there are some things that can only be done with smaller groups of people; this was one of them. In short, this was a tiny conference, but a well-run one. Sessions Although it was a relatively small conference, the number and quality of the sessions belied the size. Each of the three days of the conference featured a different keynote speaker. In addition to Jordan Hubbard, Jeremy Allison spoke on “Samba Futures” on day two, and Brian Behlendorf gave a talk on “FreeBSD and Apache: A Perfect Combo” to start off the third day. The conference sessions themselves were divided into six tracks: advocacy, business, development, networking, security, and panels. The panels track featured three different panels, made up of three different slices of the community: the FreeBSD core team, a press panel, and a prominent user panel with representatives from such prominent commercial users as Yahoo! and USWest. I was especially interested in Apple Computer’s talk in the development track. Wilfredo Sanchez, technical lead for open source projects at Apple (no, that’s not an oxymoron!) spoke about Apple’s Darwin project, the company’s operating system road map, and the role of BSD (and, specifically, FreeBSD) in Apple’s plans. Apple and Unix have had a long and uneasy history, from the Lisa through the A/UX project to today. Personally, I’m very optimistic about the chances for the Darwin project to succeed. Apple’s core OS kernel team has chosen FreeBSD as its reference platform. I’m looking forward to what this partnership will bring to both sides. Other development track sessions included in-depth tutorials on writing device drivers, basics of the Vinum Volume Manager, Fibre Channel, development models (the open repository model), and the FreeBSD Documentation Project (FDP). If you’re interested in contributing to the FreeBSD project, the FDP is a good place to start. Advocacy sessions included “How One Person Can Make a Difference” (a timeless topic that would find a home at any technical conference!) and “Starting and Managing A User Group” (trials and tribulations as well as rewards). The business track featured speakers from three commercial users of FreeBSD: Cybernet, USWest, and Applix. Applix presented its port of Applixware Office for FreeBSD and explained how Applix has taken the core services of Applixware into open source. Commercial applications and open source were once a rare combination; we can only hope the trend away from that state of affairs will continue. Commercial use of FreeBSD The use of FreeBSD in embedded applications is increasing as well – and it is increasing at the same rate that hardware power is. These days, even inexpensive systems are able to run a BSD kernel. The BSD license and the solid TCP/IP stack prove significant enticements to this market as well. (Unlike the GNU Public License, the BSD license does not require that vendors make derivative works open source.) Companies such as USWest and Verio use FreeBSD for a wide variety of different Internet services. Yahoo! and Hotmail are examples of companies that use FreeBSD extensively for more specific purposes. Yahoo!, for example, has many hundreds of FreeBSD boxes, and Hotmail has almost 2000 FreeBSD machines at its data center in the San Francisco Bay area. Hotmail is owned by Microsoft, so the fact that it runs FreeBSD is a secret. Don’t tell anyone… When asked to comment on the increasing commercial interest in BSD, Hubbard said that FreeBSD is learning the Red Hat lesson. “Walnut Creek and others with business interests in FreeBSD have learned a few things from the Red Hat IPO,” he said, “and nobody is just sitting around now, content with business as usual. It’s clearly business as unusual in the open source world today.” Hubbard had also singled out some of BSD’s commercial partners, such as Whistle Communications, for praise in his opening day keynote. These partners play a key role in moving the project forward, he said, by contributing various enhancements and major new systems, such as Netgraph, as well as by contributing paid employee time spent on FreeBSD. Even short FreeBSD-related contacts can yield good results, Hubbard said. An example of this is the new jail() security code introduced in FreeBSD 3.x and 4.0, which was contributed by R & D Associates. A number of ISPs are also now donating the hardware and bandwidth that allows the project to provide more resource mirrors and experimental development sites. See you next year And speaking of corporate sponsors, thanks go to Walnut Creek for sponsoring the conference, and to Yahoo! for covering all the expenses involved in bringing the entire FreeBSD core team to Berkeley. As a fan of FreeBSD, I’m happy to see that the project has finally produced a conference. It was time: many of the 16 core team members had been working together on a regular basis for nearly seven years without actually meeting face to face. It’s been an interesting year for open source projects. I’m looking forward to the next year – and the next BSD conference – to be even better. ##News Roundup OpenBSD Recommends: Disable SMT/Hyperthreading in all Intel BIOSes Two recently disclosed hardware bugs affected Intel cpus: - TLBleed - T1TF (the name "Foreshadow" refers to 1 of 3 aspects of this bug, more aspects are surely on the way) Solving these bugs requires new cpu microcode, a coding workaround, *AND* the disabling of SMT / Hyperthreading. SMT is fundamentally broken because it shares resources between the two cpu instances and those shared resources lack security differentiators. Some of these side channel attacks aren't trivial, but we can expect most of them to eventually work and leak kernel or cross-VM memory in common usage circumstances, even such as javascript directly in a browser. There will be more hardware bugs and artifacts disclosed. Due to the way SMT interacts with speculative execution on Intel cpus, I expect SMT to exacerbate most of the future problems. A few months back, I urged people to disable hyperthreading on all Intel cpus. I need to repeat that: DISABLE HYPERTHREADING ON ALL YOUR INTEL MACHINES IN THE BIOS. Also, update your BIOS firmware, if you can. OpenBSD -current (and therefore 6.4) will not use hyperthreading if it is enabled, and will update the cpu microcode if possible. But what about 6.2 and 6.3? The situation is very complex, continually evolving, and is taking too much manpower away from other tasks. Furthermore, Intel isn't telling us what is coming next, and are doing a terrible job by not publically documenting what operating systems must do to resolve the problems. We are having to do research by reading other operating systems. There is no time left to backport the changes -- we will not be issuing a complete set of errata and syspatches against 6.2 and 6.3 because it is turning into a distraction. Rather than working on every required patch for 6.2/6.3, we will re-focus manpower and make sure 6.4 contains the best solutions possible. So please try take responsibility for your own machines: Disable SMT in the BIOS menu, and upgrade your BIOS if you can. I'm going to spend my money at a more trustworthy vendor in the future. ###Get Morrowind running on OpenBSD in 5 simple steps This article contains brief instructions on how to get one of the greatest Western RPGs of all time, The Elder Scrolls III: Morrowind, running on OpenBSD using the OpenMW open source engine recreation. These instructions were tested on a ThinkPad X1 Carbon Gen 3. The information was adapted from this OpenMW forum thread: https://forum.openmw.org/viewtopic.php?t=3510 Purchase and download the DRM-free version from GOG (also considered the best version due to the high quality PDF guide that it comes with): https://www.gog.com/game/theelderscrollsiiimorrowindgotyedition Install the required packages built from the ports tree as root. openmw is the recreated game engine, and innoextract is how we will get the game data files out of the win32 executable. pkgadd openmw innoextract Move the file from GOG setuptesmorrowindgoty2.0.0.7.exe into its own directory morrowind/ due to innoextract’s default behaviour of extracting into the current directory. Then type: innoextract setuptesmorrowindgoty2.0.0.7.exe Type openmw-wizard and follow the straightforward instructions. Note that you have a pre-existing installation, and select the morrowind/app/Data Files folder that innoextract extracted. Type in openmw-launcher, toggle the settings to your preferences, and then hit play! iXsystems https://twitter.com/allanjude/status/1034647571124367360 ###My First Clang Bug Part of the role of being a packager is compiling lots (and lots) of packages. That means compiling lots of code from interesting places and in a variety of styles. In my opinion, being a good packager also means providing feedback to upstream when things are bad. That means filing upstream bugs when possible, and upstreaming patches. One of the “exciting” moments in packaging is when tools change. So each and every major CMake update is an exercise in recompiling 2400 or more packages and adjusting bits and pieces. When a software project was last released in 2013, adjusting it to modern tools can become quite a chore (e.g. Squid Report Generator). CMake is excellent for maintaining backwards compatibility, generally accommodating old software with new policies. The most recent 3.12 release candidate had three issues filed from the FreeBSD side, all from fallout with older software. I consider the hours put into good bug reports, part of being a good citizen of the Free Software world. My most interesting bug this week, though, came from one line of code somewhere in Kleopatra: QUNUSED(gpgagentdata); That one line triggered a really peculiar link error in KDE’s FreeBSD CI system. Yup … telling the compiler something is unused made it fall over. Commenting out that line got rid of the link error, but introduced a warning about an unused function. Working with KDE-PIM’s Volker Krause, we whittled the problem down to a six-line example program — two lines if you don’t care much for coding style. I’m glad, at that point, that I could throw it over the hedge to the LLVM team with some explanatory text. Watching the process on their side reminds me ever-so-strongly of how things work in KDE (or FreeBSD for that matter): Bugzilla, Phabricator, and git combine to be an effective workflow for developers (perhaps less so for end-users). Today I got a note saying that the issue had been resolved. So brief a time for a bug. Live fast. Get squashed young. ###DragonFlyBSD Now Runs On The Threadripper 2990WX, Developer Shocked At Performance Last week I carried out some tests of BSD vs. Linux on the new 32-core / 64-thread Threadripper 2990WX. I tested FreeBSD 11, FreeBSD 12, and TrueOS – those benchmarks will be published in the next few days. I tried DragonFlyBSD, but at the time it wouldn’t boot with this AMD HEDT processor. But now the latest DragonFlyBSD development kernel can handle the 2990WX and the lead DragonFly developer calls this new processor “a real beast” and is stunned by its performance potential. When I tried last week, the DragonFlyBSD 5.2.2 stable release nor DragonFlyBSD 5.3 daily snapshot would boot on the 2990WX. But it turns out Matthew Dillon, the lead developer of DragonFlyBSD, picked up a rig and has it running now. So in time for the next 5.4 stable release or those using the daily snapshots can have this 32-core / 64-thread Zen+ CPU running on this operating system long ago forked from FreeBSD. In announcing his success in bringing up the 2990WX under DragonFlyBSD, which required a few minor changes, he shared his performance thoughts and hopes for the rig. “The cpu is a real beast, packing 32 cores and 64 threads. It blows away our dual-core Xeon to the tune of being +50% faster in concurrent compile tests, and it also blows away our older 4-socket Opteron (which we call ‘Monster’) by about the same margin. It’s an impressive CPU. For now the new beast is going to be used to help us improve I/O performance through the filesystem, further SMP work (but DFly scales pretty well to 64 threads already), and perhaps some driver to work to support the 10gbe on the mobo.” Dillon shared some results on the system as well. " The Threadripper 2990WX is a beast. It is at least 50% faster than both the quad socket opteron and the dual socket Xeon system I tested against. The primary limitation for the 2990WX is likely its 4 channels of DDR4 memory, and like all Zen and Zen+ CPUs, memory performance matters more than CPU frequency (and costs almost no power to pump up the performance). That said, it still blow away a dual-socket Xeon with 3x the number of memory channels. That is impressive!" The well known BSD developer also added, “This puts the 2990WX at par efficiency vs a dual-socket Xeon system, and better than the dual-socket Xeon with slower memory and a power cap. This is VERY impressive. I should note that the 2990WX is more specialized with its asymetric NUMA architecture and 32 cores. I think the sweet spot in terms of CPU pricing and efficiency is likely going to be with the 2950X (16-cores/32-threads). It is clear that the 2990WX (32-cores/64-threads) will max out 4-channel memory bandwidth for many workloads, making it a more specialized part. But still awesome…This thing is an incredible beast, I’m glad I got it.” While I have the FreeBSD vs. Linux benchmarks from a few days ago, it looks like now on my ever growing TODO list will be re-trying out the newest DragonFlyBSD daily snapshot for seeing how the performance compares in the mix. Stay tuned for the numbers that should be in the next day or two. ##Beastie Bits X11 on really small devices mandoc-1.14.4 released The pfSense Book is now available to everyone MWL: Burn it down! Burn it all down! Configuring OpenBSD: System and user config files for a more pleasant laptop FreeBSD Security Advisory: Resource exhaustion in TCP reassembly OpenBSD Foundation gets first 2018 Iridium donation New ZFS commit solves issue a few users reported in the feedback segment Project Trident should have a beta release by the end of next week Reminder about Stockholm BUG: September 5, 17:30-22:00 BSD-PL User Group: September 13, 18:30-21:00 Tarsnap ##Feedback/Questions Malcom - Having different routes per interface Bostjan - ZFS and integrity of data Michael - Suggestion for Monitoring Barry - Feedback Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

Microsoft’s making radical changes to Windows 10, and a new type of speculative execution attack on Intel’s processors is targeting cloud providers.

See all of this week's mentioned content: http://lon.tv/ww211 - This week we look at New York regulators essentially shutting down Spectrum cable for poor service, hints that Intel will up physical cores at the expense of hyperthreading in their consumer processors, and more. Subscribe for more! http://lon.tv/s VIDEO INDEX: 00:58 - Supporter thank yous 01:16 - (non)Ad http://lon.tv/audible and great customer service! 03:13 - Week in review: Extras channel http://lon.tv/extras 03:30 - Week in review: Main channel 04:33 - Getting more "Social" with wrapup content 09:27 - Not so good LG customer service 11:38 - No Man's Sky update is great 14:38 - Spectrum cable kicked out of New York 15:59 - How regulators ended cable franchise renewals in Connecticut 18:53 - Hyperthreading vs Real Cores: Hints only i9 will have HT 20:17 - Q&A: How should I cover smart speakers? 23:21 - Q&A: Using an iPad as a portable monitor with Duet 25:41 - Channel of the week http://lon.tv/foundry 26:22 - Coming up this week 28:13 - Helping the channel lon.tv/support 28:36 - My other channels Subscribe to my email list to get a weekly digest of upcoming videos! - http://lon.tv/email See my second channel for supplementary content : http://lon.tv/extras Join the Facebook group to connect with me and other viewers! http://lon.tv/facebookgroup Visit the Lon.TV store to purchase some of my previously reviewed items! http://lon.tv/store Read more about my transparency and disclaimers: http://lon.tv/disclosures Want to chat with other fans of the channel? Visit our forums! http://lon.tv/forums Want to help the channel? Start a Member subscription or give a one time tip! http://lon.tv/support or contribute via Venmo! lon@lon.tv Follow me on Facebook! http://facebook.com/lonreviewstech Follow me on Twitter! http://twitter.com/lonseidman Catch my longer interviews in audio form on my podcast! http://lon.tv/itunes http://lon.tv/stitcher or the feed at http://lon.tv/podcast/feed.xml Follow me on Google+ http://lonseidman.com We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.

Join The Full Nerd gang as they talk about the latest PC hardware topics. In today's show we cover the throttling issues that are plaguing the MacBook Prob and compare it to Windows laptops. Then we'll talk about the rumors of Intel taking hyper-threading out of Core i7 CPUs.

We provide you with updates to Spectre and Meltdown from various BSD projects, a review of TrueOS from Linux, how to set up FreeBSD on ThinkPad x240, and a whole bunch of beastie bits. This episode was brought to you by Headlines KPTI patch lands in FreeBSD -current (https://svnweb.freebsd.org/base?view=revision&revision=328083) After a heroic effort by Konstantin Belousov kib@FreeBSD.org, the first meltdown patch has landed in FreeBSD This creates separate page tables for the Kernel and userland, and switches between them when executions enters the kernel, and when it returns to userland It is currently off by default, but you are encouraged to test it, so it can be merged back to the release branches. Set vm.pmap.pti=1 in /boot/loader.conf The existing implementation of PCID (process-context identifiers), is not compatible with the new PTI code, and is disabled when PTI is enabled, decreasing performance. A future patch will use PCID in a way that is compatible with PTI. PCID allows the OS to annotate memory mappings to specific processes, so that they can be flushed selectively, and so that they are only used when in the context of that application. Once the developers are relatively confident in the correctness of the code that has landed in -current, it will be ported back to FreeBSD 10 and 11, and released as a security advisory. Apparently porting back to FreeBSD 11 only has some relatively simple merge conflicts, but 10 will be more work. Former FreeBSD Security Officer Dag-Erling Smørgrav has created a meltdown testing and PoC tool (https://github.com/dag-erling/meltdown) that you can use to check your system. It is not finished yet, and doesn't seem to work with newer processors (haswell and newer). The first partial mitigation for Spectre variant 2 (https://svnweb.freebsd.org/changeset/base/328011) for bhyve on AMD64 has also been committed The latest information is always available on the FreeBSD Wiki (https://wiki.freebsd.org/action/edit/SpeculativeExecutionVulnerabilities) *** Some thoughts on Spectre and Meltdown (http://www.daemonology.net/blog/2018-01-17-some-thoughts-on-spectre-and-meltdown.html) Colin Percival breaks down how these vulnerabilities work, with same nice analogies What is a side channel: I want to know when my girlfriend's passport expires, but she won't show me her passport (she complains that it has a horrible photo) and refuses to tell me the expiry date. I tell her that I'm going to take her to Europe on vacation in August and watch what happens: If she runs out to renew her passport, I know that it will expire before August; while if she doesn't get her passport renewed, I know that it will remain valid beyond that date. Her desire to ensure that her passport would be valid inadvertently revealed to me some information: Whether its expiry date was before or after August. Spectre Variant 1: I tell my girlfriend that I'm going to take her on vacation in June, but I don't tell her where yet; however, she knows that it will either be somewhere within Canada (for which she doesn't need a passport, since we live in Vancouver) or somewhere in Europe. She knows that it takes time to get a passport renewed, so she checks her passport and (if it was about to expire) gets it renewed just in case I later reveal that I'm going to take her to Europe. If I tell her later that I'm only taking her to Ottawa — well, she didn't need to renew her passport after all, but in the meantime her behaviour has already revealed to me whether her passport was about to expire. This is what Google refers to "variant 1" of the Spectre vulnerability: Even though she didn't need her passport, she made sure it was still valid just in case she was going to need it. Spectre Variant 2: I spend a week talking about how Oxford is a wonderful place to visit and I really enjoyed the years I spent there, and then I tell her that I want to take her on vacation. She very reasonably assumes that — since I've been talking about Oxford so much — I must be planning on taking her to England, and runs off to check her passport and potentially renew it... but in fact I tricked her and I'm only planning on taking her to Ottawa. Meltdown: I tell my girlfriend that I want to take her to the Korean peninsula. She knows that her passport is valid for long enough; but she immediately runs off to check that her North Korean visa hasn't expired. Why does she have a North Korean visa, you ask? Good question. She doesn't — but she runs off to check its expiry date anyway! Because she doesn't have a North Korean visa, she (somehow) checks the expiry date on someone else's North Korean visa, and then (if it is about to expire) runs out to renew it — and so by telling her that I want to take her to Korea for a vacation I find out something she couldn't have told me even if she wanted to. Final thoughts on vulnerability disclosure The way these issues were handled was a mess; frankly, I expected better of Google, I expected better of Intel, and I expected better of the Linux community. When I found that Hyper-Threading was easily exploitable, I spent five months notifying the security community and preparing everyone for my announcement of the vulnerability; but when the embargo ended at midnight UTC and FreeBSD published its advisory a few minutes later, the broader world was taken entirely by surprise. Nobody knew what was coming aside from the people who needed to know; and the people who needed to know had months of warning. Contrast that with what happened this time around. Google discovered a problem and reported it to Intel, AMD, and ARM on June 1st. Did they then go around contacting all of the operating systems which would need to work on fixes for this? Not even close. FreeBSD was notified the week before Christmas, over six months after the vulnerabilities were discovered. Now, FreeBSD can occasionally respond very quickly to security vulnerabilities, even when they arise at inconvenient times — on November 30th 2009 a vulnerability was reported at 22:12 UTC, and on December 1st I provided a patch at 01:20 UTC, barely over 3 hours later — but that was an extremely simple bug which needed only a few lines of code to fix; the Spectre and Meltdown issues are orders of magnitude more complex. To make things worse, the Linux community was notified and couldn't keep their mouths shut. Standard practice for multi-vendor advisories like this is that an embargo date is set, and nobody does anything publicly prior to that date. People don't publish advisories; they don't commit patches into their public source code repositories; and they definitely don't engage in arguments on public mailing lists about whether the patches are needed for different CPUs. As a result, despite an embargo date being set for January 9th, by January 4th anyone who cared knew about the issues and there was code being passed around on Twitter for exploiting them. This is not the first time I've seen people get sloppy with embargoes recently, but it's by far the worst case. As an industry we pride ourselves on the concept of responsible disclosure — ensuring that people are notified in time to prepare fixes before an issue is disclosed publicly — but in this case there was far too much disclosure and nowhere near enough responsibility. We can do better, and I sincerely hope that next time we do. CPU microcode update code for amd64 (https://undeadly.org/cgi?action=article;sid=20180115073406) (https://marc.info/?l=openbsd-tech&m=151588857304763&w=2) Patrick Wildt (patrick@) recently committed some code that will update the Intel microcode on many Intel CPUs, a diff initially written by Stefan Fritsch (sf@). The microcode of your CPU is basically the firmware that runs on your (Intel) processor, defining its instruction set in terms of so called "microinstructions". The new code depends, of course, on the corresponding firmware package, ported by Patrick which can be installed using a very recent fw_update(1). Of course, this all plays into the recently revealed problems in Intel (and other) CPUs, Meltdown and Spectre. Now Theo has explained the workings of the code on openbsd-tech, detailing some of the challenges in updating microcode on CPUs where your OS is already starting to run. Theo hints at future updates to the intel-firmware package in his mail: (https://marc.info/?l=openbsd-tech&m=151588857304763&w=2) Patrick and others committed amd64 Intel cpu microcode update code over the last few days. The approach isn't perfect, but it is good enough for a start. I want to explain the situation. When you fw_update, you'll get the firmware files. Upon a reboot, it will attempt to update the microcode on your cpus. Maybe there isn't a new microcode. Maybe your BIOS has a copy of the microcode and installs it before booting OpenBSD. This firmware installation is done a little late. Doing it better will require some work in the bootblocks to find the firmware files, but time is a bit short to do that right now. The branch-target-cache flushing features added in new microcode are not being used yet. There is more code which has to be written, but again other work is happening first. Also, Intel is saying their new microcodes sucks and people should wait a little. "Hi, my name is Intel and I'm an cheating speculator". Several developers are working on mitigations for these issues, attacking the problem from several angles. Expect to see more updates to a CVS tree near you soon. Intel: as a *BSD user, I am fucking pissed! (https://malcont.net/2018/01/dont-like-meltdown-spectre-releated-bugs-handled/) I wasn't going to write anything on the recently found x64 architecture – related bugs. I'm not a kernel developer nor even a programmer and I can't say that I have a solid understanding of what Meltdown and Spectre attacks are. Also there already is a ton of articles and posts written by people who have no grasp of the subject. I'm however a malcontent and I find this a good way to express my feelings: Intel: as a *BSD user, I am fucking pissed! Meltdown, Spectre and BSD – the “pissed” part Part of my work is UNIX-like systems administration – including BSDs and Linuces. As much as I am happy with Linux changes already made, I am beyond pissed about how the BSDs were handled by Intel – because they were not. FreeBSD Security Team received some heads-up just before Xmas, while OpenBSD, NetBSD and DragonflyBSD teams received no prior warnings. Meltdown and Spectre attacks are hard to perform. It is a hard work to mitigate them in the software, as the bugs lay in the CPUs and are not fixable by microcode updates. Developers are trying to mitigate these bugs in a way that will deliver smallest performance losses. A lot of time consuming work is needed to fix CPU vendors' mistakes. Linux developers had this time. BSD developers did not. BSD user base too small? BSD user base is small in comparison to Linux. Seems that it's too small for Intel. PlayStation4 consoles are FreeBSD-based (and use AMD CPUs) but I think it's safe to say that gaming devices are not the most important systems to be fixed. Netflix serves their content off FreeBSD but the bugs are not remotely exploitable (possibly not including JavaScript, but it's running someone's code locally) so there's probably not much harm to be done here either. However gamers and Netflix aren't the only ones who use *BSD systems. I'd say that there is more than a few FreeBSD, NetBSD, OpenBSD and DragonFlyBSD servers on the internet. In March 2017, Intel promised “more timely support to FreeBSD”. They knew about flaws in their CPUs in June and decided that a timely manner is the end of December – short before the embargo was to be lifted. Intel and Google (probably Intel more): it was your job to pick the correct people to whom the bugs can be disclosed. In my humble opinion you chose poorly by disclosing these issues with ONLY Apple, Microsoft, and the Linux Foundation, of OS vendors. You did much harm to the BSD community. Intel: It's your bugs. And you offered “more support” to the FreeBSD Foundation less than 3 months prior to being informed (my guess is that you knew much earlier) on the flaws in YOUR products. I don't want to write more here as the wording would be too strong. Interview - Viewer Questions These days, do you consider yourself more of an programmer or a sysadmin? Which one do you enjoy more? Does FreeBSD/BSD enable your business or would another OS suit your needs just as well? You've hinted that you use FreeBSD as part of your business. Can you elaborate on that and give some technical detail on how it's used in that environment? If you were allowed three wishes for anything at all to be implemented or changed in ZFS, what would they be, and why? Per Dataset throughput and IOPS limiting Per-File Cloning and/or zfsmv (move a file from one dataset to another, without copying) Cluster support Allan, you have previously mentioned that you have worked on FreeBSD on MIPS, what made you choose the Onion Omega over something like the Raspberry Pi? What is BSD Now's association with Jupiter broadcasting, and how did the relationship come to be? Jupiter seems to be associated with several Linux-themed podcasts, and I'm wondering how and why BSD Now joined Jupiter. The two communities (the Linuxes and BSDs) don't always seem to mix freely -- or do they? What kind of keyboard is that? Have you ever tried an ErgoDox? The ErgoDox EZ is made by a Canadian. You mentioned when doing one of your talks on UCL for FreeBSD that you had only recently learned C. I am also aware of your history also on contributing to the FreeBSD handbook and to documentation in general. Given you started with C relatively recently, what made you want to learn it, how quickly did you pick it up, and is it your favourite language? It is most inspiring to me, as you are clearly so talented, and of all the languages I have learned (including C++), I still prefer C in my heart of hearts. I'd be really interested to hear your answer, many thanks. *** News Roundup LinuxAndUbuntu Review Of TrueOS A Unix Based OS (http://www.linuxandubuntu.com/home/linuxandubuntu-review-of-trueos-a-unix-based-os) Trust me, the name TrueOS takes me back to 1990s when Tru64 UNIX operating system made its presence. TrueOS is PC-BSD's new unified brand built upon FreeBSD-CURRENT code base. Note that TrueOS is not a Linux distro but is BSD Unix. FreeBSD is known for its cutting-edge features, security, scalability, and ability to work both as a server and desktop operating system. TrueOS aims at having user-friendliness with the power of FreeBSD OS. Let us start with going into details of different aspects of the TrueOS. TrueOS History ? TrueOS was founded by Kris Moore in 2005 with name PC-BSD. Initial version focused to make FreeBSD easy to use starting with providing GUI based installer (to relatively complicated FreeBSD installer). In the year 2006, PC-BSD was acquired by iXsystems. Before rebranding as TrueOS in Sept 2016, PC-BSD reached a stage starting considering better than vanilla FreeBSD. Older PC-BSD version used to support both x86 and x86-64 architecture. Kris Moore, the developer founder, says about rebranding: “We've already been using TrueOS for the server side of PC-BSD, and it made sense to unify the names. PC-BSD doesn't reflect server or embedded well. TrueOS Desktop/Server/Embedded can be real products, avoids some of the alphabet soup, and gives us a more catchy name.” TrueOS First Impression ? The startup is little longer; may be due to starting up of many services. The heavy KDE well suited to PC-BSD. The C++/Qt5 based Lumina desktop environment is light and fast. The Lumina offers an easy way to configure menu and panels. I did not face any problems for continuous use of two weeks on a virtual machine having the minimal configuration: 1 GB RAM, 20 GB hard disk and Intel 3.06 GHz i3 processor. The Lumina desktop is light and fast. The developers of Lumina know what they are doing and have a good idea of what makes a good IDE. As it happens with any new desktop environment, it needs some time to settle. Let us hope that they keep to the path they are on with it. Conclusion ? The TrueOS is impressive when consider it as relatively young. It is a daring step that TrueOS developers took FreeBSD Current rather than FreeBSD Stable code base. Overall it has created its own place from the legacy shadow of PC-BSD. Starting with easy installation TrueOS is a good combination of software and utilities that make the system ready to use. Go and get a TrueOS ISO to unleash the “bleeding edge” tag of FreeBSD Thinkpad x240 - FreeBSD Setup (http://stygix.org/nix/x240-freebsd.php) What follows is a record of how I set up FreeBSD to be my daily driver OS on the Lenovo Thinkpad X240. Everything seems to work great. Although, the touchpad needs some tweaking. I've tried several configurations, even recompiling Xorg with EVDEV support and all that, to no avail. Eventually I will figure it out. Do not sleep the laptop from the command line. Do it from within Xorg, or it will not wake up. I don't know why. You can do it from a terminal within Xorg, just not from the naked command line without Xorg started. It also will not sleep by closing the lid. I included a sudo config that allows you to run /usr/sbin/zzz without a password, so what I do is I have a key combo assigned within i3wm to run "sudo /usr/sbin/zzz". It works fine this way. I go into detail when it comes to setting up Xorg with i3wm. You can skip this if you want, but if you've never used a tiling window manager, it will handle screen real estate very efficiently on a laptop with a 12.5-inch screen and a touchpad. First, download the amd64 image for 11.1-RELEASE and flash it to a USB pen drive. For the Unices, use this: # dd if=FreeBSD-11.1-RELEASE-amd64-memstick.img of=/dev/da0 bs=1M conv=sync Obviously, you'll change /dev/da0 to whatever the USB pen drive is assigned. Plug it in, check dmesg. Leave it plugged in, restart the laptop. When prompted, tap Enter to halt the boot process, then F12 to select a bootable device. Choose the USB drive. I won't go through the actual install process, but it is pretty damn easy so just look at a guide or two and you'll be fine. If you can install Debian, you can install FreeBSD. I will, however, recommend ZFS if you have over 4GB of RAM (my particular variant of the X240 has 8GB of RAM, so yours should have at least 4GB), along with an encrypted disk, and an encrypted SWAP partition. When prompted to add an additional user, and you get to the question where it asks for additional groups, please make sure you add the user to "wheel". The rest should be self-explanatory during the install. Now for the good shit. You just booted into a fresh FreeBSD install. Now what? Well, time to fire up vi and open some config files... CNN Article about CDROM.com and FreeBSD, from 1999 (https://www.cnn.com/TECH/computing/9904/08/cdrom.idg/index.html) Walnut Creek CDROM sells a lot of CD-ROMs, but it gives away even more data. Specifically, anyone who has Internet access is free to log into wcarchive (ftp.cdrom.com) and start downloading bits. Even with a good Internet connection, however, you should expect to be at it for a while. At the present time, wcarchive resides on half a terabyte (500 GB) of RAID 5-disk storage. Even if your 56-Kbps modem can deliver seven kilobytes per second, downloading the complete archive would take you 70 million seconds. Even then, some of the files would be more than two years out of date, so a bit of "back and fill" would be needed. Of course, nobody uses wcarchive that way. Instead, they just drop in when they need the odd file or two. The FTP server is very accommodating; 3,600 simultaneous download sessions is the current limit and an upgrade to 10,000 sessions is in the works. This translates to about 800 GB per day of downloads. Bob Bruce (Walnut Creek's founder) says he's thinking about issuing a press release when they reach a terabyte a day. But 800 GB isn't all that shabby.... The hardware Because FTP archives don't do a lot of thinking, wcarchive doesn't need a massive cluster of CPUs. In fact, it gets by with a single 200-MHz P6 Pentium Pro and a measly(!) 1 GB of RAM. The I/O support, however, is fairly impressive. A six-channel Mylex RAID controller (DAC960SXI; Ultra-Wide SCSI-SCSI) is the centerpiece of the I/O subsystem. Two channels link it to the PC ("Personal Computer"!?!), via a dual-channel Adaptec card (AHA-3940AUW; PCI to Ultra-Wide SCSI). An 256-MB internal cache helps it to eliminate recurring disk accesses. Four nine-drive disk arrays provide the actual storage. The two larger arrays use 18-GB IBM drives; the two smaller arrays use 9-GB Micropolis and Quantum drives. A separate 4-GB Quantum drive is used as the "system disk." The output side is handled by a single Intel 100Base-T controller (Pro/100B PCI), which feeds into the Internet through a number of shared DS3 (45 Mbps) and OC3 (155 Mbps) circuits. A detailed description of the system is available as ftp.cdrom.com/archive-info/configuration; The software The system software is rather prosaic: a copy of FreeBSD, supplemented by home-grown FTP mirroring and server code. Because of the massive hardware support, the software "only" needs to keep the I/O going in an efficient and reliable manner. FreeBSD, the "prosaic" operating system mentioned above, merits a bit more discussion. Like Linux, FreeBSD is open source. Anyone can examine, modify, and/or redistribute the source code. And, like Linux, an active user community helps the authors to find bugs, improve documentation, and generally support the OS. Unlike Linux, FreeBSD is derived from the Berkeley Unix code that forms the foundation for most commercial Unix variants. When you use the "fast file system" (cylinder groups, long file names, symbolic links, etc.), TCP/IP networking, termcap, or even vi, you are using Berkeley Unix additions. The version of BSD underlying FreeBSD, however, is "pure" BSD; don't look for the System V modifications you see in Solaris. Instead, think of it as SunOS, brought up to date with Kerberos, modern sendmail, an updated filesystem, and more. Solid, fast, and free! One of FreeBSD's finest innovations, the Ports Collection, makes FreeBSD a delight for open source application users. The Ports Collection automates the downloading, building, and installation (including de-installation) of 2,300+ open source packages. The company Walnut Creek CDROM has been around for several years now, so you are likely to be familiar with its offerings. You may not realize, however, that it provides the major financial support for FreeBSD. The FreeBSD support has two purposes. First, it provides the company with a solid base to run wcarchive and other massive projects. Second, it ties in with the company's mission of making software (and data) economically accessible. Bob Bruce, the firm's founder, is an interesting guy: laid back and somewhat conservative in manner, but productive and innovative in practice. Here is a possibly illustrative story. When Bob started selling CD-ROMs, disc caddies were selling for $15 each. Bob thought that was rather high, so he started investigating the marketplace. A long-distance call to Japan got him Sony's fax number; a series of faxes got him in touch with the salespeople. It turned out that caddies were available, in bulk, for only a few dollars each. Bulk, in this case, meant pallet-loads of 10,000 caddies. In an act of great faith, Bob purchased a pallet of caddies, then proceeded to sell them for five dollars each. The results were everything he might have wished. Folks who bought his CD-ROMs added caddies to their orders; folks who bought piles of caddies added in a disc or two. Either way, Walnut Creek CDROM was making a name for itself. Many pallet-loads later, the company is still selling caddies, making and distributing CD-ROMs, and giving away bits. Walnut Creek CDROM is a real open-source success story; its breadth and depth of offerings is well worth a look. Beastie Bits OpenBSD adds kqueue event support to DRM, to detect device changes like HDMI cables being plugged in, and trigger randr events (https://github.com/openbsd/src/commit/b8584f4233dc11a328cd245a5843ec3d67462200) Thesis describing QUAD3, a unix-like, multi-tasking operating system for the 6502 processor (https://archive.org/details/AMultiTaskingOperatingSystemForMicrocomputers) Windows is getting chmod and chown... (https://blogs.msdn.microsoft.com/commandline/2018/01/12/chmod-chown-wsl-improvements/) Timeline: How they kept Meltdown and Spectre secret for so long (https://www.theverge.com/platform/amp/2018/1/11/16878670/meltdown-spectre-disclosure-embargo-google-microsoft-linux) bsd.network is a *BSD-themed Mastodon Instance (https://bsd.network/): Peter Hessler is administering a new Mastodon instance, running in an OpenBSD VM on top of an OpenBSD vmm hypervisor Computer-Aided Instruction on UNIX (https://virtuallyfun.com/wordpress/wp-content/uploads/2017/12/whfUb.pdf) AsiaBSDCon 2018 Travel Grant Application Now Open (https://www.freebsdfoundation.org/blog/asiabsdcon-2018-travel-grant-application-now-open/) AsiaBSDCon 2018 FreeBSD Developers Summit Call for Proposals (https://www.freebsdfoundation.org/news-and-events/call-for-papers/asiabsdcon-2018-freebsd-developers-summit-call-for-proposals/) LinuxFest Northwest 2018 Call for Proposals (https://www.freebsdfoundation.org/news-and-events/call-for-papers/linuxfest-northwest-2018-call-for-proposals/) Feedback/Questions Jason - Dont break my ports (http://dpaste.com/05PRNG2) Wilyarti - show content (http://dpaste.com/1BG8GZW) https://clinetworking.wordpress.com/2017/12/08/data-de-duplication-file-diff-ing-and-s3-style-object-storage-using-digital-ocean-spaces Scott - Your show is Perfect! (http://dpaste.com/0KER8YE#wrap) Ken - Community Culture (http://dpaste.com/0WT8285#wrap)

SUSE hits the Windows Store and we finally get some important classifications, System76 announces Pop!_OS and we do a deep analysis, and why Mir is back with a plan to support Wayland. Plus Debian warns of Hyper Threading issues & of course a bit more!

SUSE hits the Windows Store and we finally get some important classifications, System76 announces Pop!_OS and we do a deep analysis, and why Mir is back with a plan to support Wayland. Plus Debian warns of Hyper Threading issues; and of course a bit more.

SUSE hits the Windows Store and we finally get some important classifications, System76 announces Pop!_OS and we do a deep analysis, and why Mir is back with a plan to support Wayland. Plus Debian warns of Hyper Threading issues; and of course a bit more.

SUSE hits the Windows Store and we finally get some important classifications, System76 announces Pop!_OS and we do a deep analysis, and why Mir is back with a plan to support Wayland. Plus Debian warns of Hyper Threading issues & of course a bit more!

SUSE hits the Windows Store and we finally get some important classifications, System76 announces Pop!_OS and we do a deep analysis, and why Mir is back with a plan to support Wayland. Plus Debian warns of Hyper Threading issues; and of course a bit more.

So we hear about HyperThreading and how it is sooo cool, well, it is and it isn't. If you are really trying to squeeze performance out of your application HyperThreading might not be what you're looking for. There are so many other things that happens at the CPU level that have so weird names (like Thread Thrashing, 'say whaaaat?'). If you are really serious on squeezing every worthy CPU cycle of your app (or if you're interesting on what really really goes under the hood) take a listen! (ah! and treat me a beer, if you like what you hear!) Follow Me on Twitter! (@fguime)(thanks!)   Hey it's ALMOST SUMMER! and I would love to get a beer :) Tweet, Tweet! (https://twitter.com/#!/fguime) Thread Priority in Linux LMax Disruptor Identifying Cache Misses in Java (PDF) JClarity Tool (for measuring many hardware performance task, of Martijn Verburg fame!) Tree Parsing and Evaluation example Oracle Solaris Studio (part of Charlie Hunt bags of tricks) More tips and tricks from Java Application Profiling Vote for us in iTunes (http://itunes.apple.com/us/podcast/java-pub-house/id467641329) Questions, feedback or comments! comments@javapubhouse.com Subscribe to our podcast! (http://javapubhouse.libsyn.com/rss) ITunes link (http://itunes.apple.com/us/podcast/java-pub-house/id467641329) Java 7 Recipes book! (http://www.amazon.com/gp/product/1430240563/ref=as_li_ss_il?ie=UTF8&tag=meq-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=1430240563) Hey! if you like what you hear, treat me a beer! (It's the Java pub house after all :) https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=Z8V2ZWV93UMW4

Mike rants about Greenpeace, Oblivion, NiGHTS sequal, AMD anti-Hyperthreading, and more!