POPULARITY
3 episodes with intel gpus
3 episodes with intel gpus
2 episodes with intel gpus
5 episodes with intel gpus
2 episodes with intel gpus
2 episodes with intel gpus
We had a podcast. Routine. We talked about NVIDIA for the first 20 plus minutes straight. Routine.But also on the menu is next gen Intel GPUs, Windows 11 mods, and all hail the dead Humane AI Pin.Timestamps:00:00 Intro01:10 Food with Josh04:03 RTX 5070 Ti review and general discussion20:10 NVIDIA Verified Priority Access for RTX 50 FE cards21:12 First report of RTX 5080 connector melting22:50 Mandatory Arc coverage25:29 AMD jokes about the 32GB RX 9070 XTX rumor27:28 Windows 11 24H2 CPU support list causes concern30:21 Mod your Windows 11 start menu31:57 The Humane AI Pin is dead34:17 (In)Security Corner45:22 Gaming Quick Hits48:59 Picks of the Week1:02:32 Outro ★ Support this podcast on Patreon ★
This week on the podcast we go over our reviews of the of the ASRock X870E Taichi Motherboard, FiFine M9 Dual Wireless Lavalier Microphone, and Scythe Mugen 6 DBE (Dual Fan Black Edition) CPU Cooler. We also discuss NZXT being under fire after an investigation by Gamers Nexus, New Intel GPUs, Intel CEO Pat Gelsinger retiring, AMD crushing Black Friday sales and more!
AMD has 24 Core Ryzen INCOMING…and Nvidia, RADEON, and Intel GPUs are about to launch! [SPON: Use "brokensilicon“ at CDKeyOffer's Black Friday Sale to get Win 11 Pro for $23: https://www.cdkeyoffer.com/cko/Moore11 ] [SPON: Use “brokensilicon” to get $30 OFF the Minisforum V3 3-in-1 Tablet: https://shrsl.com/4rt3x ] 0:00 Mastering the Swivel! (Intro Banter) 2:20 PlayStation 6 Naming 6:47 XBOX getting Buggier (?), 9800X3D Supply (Corrections) 14:51 Next-Gen GPU Release Dates CONFIRMED! 25:32 Will RDNA 4 be the “next Polaris”? USB-C Support? 30:55 Intel ARC B570 10GB Leaks 37:49 Nvidia ends Lovelace Production 40:08 Strix Halo Low Power Specs Leaked 48:46 Zen 6 Medusa Point (And Ridge?) Specs Leaked! 54:44 How should AMD segment the Zen 6 lineup? 1:10:39 Qualcomm loses interest in Intel amongst Funding Cuts 1:17:36 Is an Intel-AMD merger possible? 1:24:18 TSMC 2nm Okayed for USA, PS2 160M, PSP2 Confirmed, 4090 Ti Surfaces (Wrap-up) 1:30:45 Nvidia Orin, RTX to PTX, AMD Smartphones, 200K Subs (Final RM) https://www.amazon.co.uk/Best-Sellers-CPUs/zgbs/computers/430515031 https://youtu.be/zipQWc2AzsU https://www.techpowerup.com/329193/intel-arc-b580-gpu-leaked-ahead-of-imminent-launch https://www.tomshardware.com/pc-components/gpus/nvidia-blackwell-rtx-50-series-gpus-everything-we-know https://www.pcgamesn.com/nvidia/geforce-rtx-5090-launch-leak-inno3d https://videocardz.com/newz/gunnir-arc-battlemage-gpus-to-be-revealed-on-december-4th https://videocardz.com/newz/intel-arc-b570-specs-leaked-18-xe2-cores-10gb-memory-and-pcie-4-0x8 https://amzn.to/4g7aIPy https://amzn.to/49wfXqh https://www.newegg.com/p/27N-0002-001G2 https://www.tomshardware.com/pc-components/gpus/nvidia-warns-of-gaming-gpu-shortage-this-quarter-recovery-in-early-2025-chipmaker-rakes-in-record-profits-as-net-income-soars-by-109-percent-yoy https://nvidianews.nvidia.com/news/nvidia-announces-financial-results-for-third-quarter-fiscal-2025 https://youtu.be/h5dDn8nzvAw https://youtu.be/h5dDn8nzvAw https://www.guru3d.com/story/amd-zen-6-medusa-ridge-processor-leak-reveals-12core-ccd-architecture/ https://www.fudzilla.com/news/graphics/60169-zen-6-medusa-ridge-processor-leaked https://www.tomshardware.com/tech-industry/qualcomm-reportedly-loses-interest-in-intel-takeover https://www.trendforce.com/news/2024/11/26/news-qualcomms-interest-in-acquiring-intel-reportedly-fades-due-to-the-deals-complexity/ https://www.tomshardware.com/tech-industry/us-plans-to-shrink-intels-usd8-5b-chips-funding-to-below-usd8b-restructuring-takes-into-account-chipmakers-usd3-5b-contract-to-make-chips-for-the-military https://www.reuters.com/technology/intels-786-billion-subsidy-deal-restricts-sale-its-manufacturing-unit-2024-11-28/ https://wccftech.com/tsmc-can-shift-advanced-2nm-manufacturing-to-us-after-2025-insinuates-taiwanese-minister/ https://www.techradar.com/pro/Only-about-720000-Qualcomm-Snapdragon--laptops-sold-since-launch https://x.com/lithos_graphein/status/1858485988080640051 https://videocardz.com/newz/samsung-to-present-gddr7-memory-with-42-5-gb-s-speed-at-isscc-2025 https://www.tomshardware.com/pc-components/cpus/amd-crafts-custom-epyc-cpu-for-microsoft-azure-with-hbm3-memory-cpu-with-88-zen-4-cores-and-450gb-of-hbm3-may-be-repurposed-mi300c-four-chips-hit-7-tb-s https://www.techspot.com/news/105744-sony-confirms-playstation-2-sales-top-160m-cementing.html https://www.techpowerup.com/329307/sony-handheld-gaming-console-reportedly-coming-for-steam-deck-nintendo-switch-market-share https://videocardz.com/newz/prototype-geforce-rtx-4090-ti-gpu-has-been-found-in-computer-junk-bin-massive-quad-slot-design-and-rotated-pcie
CUDA is one of the primary reasons people buy NVIDIA GPUs but what if there was a way to have this compute power on AMD and Intel GPUs as well. Well there is a project to make that happen and it's called ZLUDA. ==========Support The Channel========== ► Patreon: https://www.patreon.com/brodierobertson ► Paypal: https://www.paypal.me/BrodieRobertsonVideo ► Amazon USA: https://amzn.to/3d5gykF ► Other Methods: https://cointr.ee/brodierobertson ==========Guest Links========== YouTube: https://www.youtube.com/c/ericparker Twitter: https://x.com/atEricParker ==========Support The Show========== ► Patreon: https://www.patreon.com/brodierobertson ► Paypal: https://www.paypal.me/BrodieRobertsonVideo ► Amazon USA: https://amzn.to/3d5gykF ► Other Methods: https://cointr.ee/brodierobertson =========Video Platforms==========
In today's dynamic work landscape, remote access and virtual desktop solutions have become essential for organizations striving for flexibility and productivity. Citrix has been at the forefront of empowering businesses with innovative technologies, and now, with Intel's new roadmap of GPU offerings, users can expect even more versatility and performance in their virtual desktop experiences.Host: Andy WhitesideCo-host: Bill SuttonCo-host: Todd Smith
Check out Wicked Cushions at: AMAZON: https://lmg.gg/WickedCushionsAmazon WC WEBSITE: https://wickedcushions.com/LTT Timestamps (Courtesy of NoKi1119): 0:00 Chapters 1:15 Intro 1:56 Topic #1 - OpenAI responds to NYT's lawsuit, states it's "meritless" 5:04 Linus ironically suggests using ChatGPT for defense, Luke does it 5:46 Linus on LMG's CES videos, discusses Intel's Thunderbolt 5, WiFi 7, AI booths 10:21 Luke mentions some of ChatGPT's defenses for OpenAI's case 11:48 Topic #2 - Covering CES 2024 17:32 Plaud Note AI, who needs this? Luke on external devices & sensitive information 23:42 Urtopia's AI powered e-bike, Luke on hallucinations & AI integration 34:55 Nvidia G-SYNC Pulsar, motion clarity, Plouffe's monitor, display size 40:25 MSI MEG 321URX, AI-powered QR-OLED monitor, cheating using the mini-map 46:07 TARKOV's 11K ban wave, cheats & barrier of entry, Linus's basement LAN 50:38 Hisense 110" TV, double the peak brightness & dimming zones 51:35 Merch Messages #1 1:03:35 The thinness, resolution, brightness & bezel war, Luke on Linus's TV 1:13:49 AMD AM4 X3D & G series, Linus recommends used GPUs over entry cards 1:18:37 Nvidia's RTX Super series, upselling behavior 1:23:14 Topic #3 - SAG-AFTRA's agreement for AI digital voice, Steam on AI games 1:25:05 Linus declines covering Nvidia's virtual bar, many companies lay offs 1:32:41 Sponsor - Wicked Cushions 1:37:42 Merch Messages #2 1:40:22 Can you talk a bit more about displays? ABL's necessity? Draw & heat? 1:45:20 Using RFID name tags in the consumer space? ft. Biochip, the Bible 1:50:09 Topic #4 - eBay pays $3M over employees cyberstalking & harassment lawsuit 1:57:22 Quebec cops warn posting porch pirate videos “invades their privacy” 1:58:13 LTTStore's new lounge pants, sizing guides 2:00:05 Last call to get the LTT CES 2024 T-shirt, hoodies stock deal 2:03:12 Topic #5 - Wacom & Wizard of the Coast apologizes over AI promotional images 2:08:49 Other companies lay offs, Linus on low money flow & interest rates ft. LayoffsFYI 2:13:04 Topic #7 - Valve takes down Portal64 & TF2 Source 2 2:14:29 Topic #8 - Video games are no longer the biggest entertainment medium in the UK 2:16:59 Topic #9 - Framework discloses data breach due to getting phished 2:24:24 Topic #10 - LG's smart washing machine uses 36GB of data per day 2:26:07 Merch Messages #3 2:29:19 Linus's racket specs, how do you get high-end rackets in Canada? 2:30:39 Origin PC's envelopes, PPI MicroOLED VR display technology, LMG Southie's comment 2:35:43 If you could make or repeal laws, what would you do? 2:37:19 Advice to juggle being a father, a husband & working? 2:38:51 Favorite piece of tech that was ahead of its time & held that feeling? 2:39:35 What is MAC Address's value with covering Apple? ft. Infants tech advices 2:42:26 Would Linus host classes or content on guidelines learnt from workflow? 2:44:45 Is it difficult to deal with people coming to you at events like CES? 2:49:29 Advice for not enjoying engineering for companies' profits? 2:53:49 Have companies ever responded to Linus chastising them? 2:56:12 Luke's thoughts on EoD being removed & his current stance on TARKOV? 3:00:10 How much has Luke's experience with Pixel 8 reflected on Linus's review? 3:01:04 Thoughts on the current state of the internet where 5 main sites are accessed? 3:02:55 Was Linus aware of Halo's mouse aim assist? Is this good for FPS' future? 3:03:28 Do you think Thunderbolt 5 is the push Intel GPUs needed? 3:04:23 Was Linus's purchase of the TCL TV the only time he got buyer's remorse? 3:05:50 Have you enjoyed tech for what it is instead of how to script a video around it? 3:06:51 Wishes you had for your loved ones? Long term goals? How do you stay organized? 3:10:32 One non-tech skill you're proud of having or wished you had? 3:17:04 Does Luke think there's a benefit in ITIL certification? 3:18:25 Who gave the best tech advice you weren't expecting? 3:20:58 Outro
One of the recent technological developments is the release of Intel's new Core Ultra CPUs for laptops, which are equipped with a neural processing unit (NPU). These CPUs, also known as Meteor Lake, are a significant advancement as they are the first mainstream Intel chips to have an NPU integrated into them.The NPU's purpose is to handle AI processing more efficiently and quickly than the regular processor can. This opens up possibilities for local generative AI tasks, such as image generation, audio transcription, and music creation, which are typically performed in the cloud. By having the NPU in laptops, these tasks can be completed in a competent amount of time locally, without the need for an internet connection or relying on cloud services.Avram demonstrates the performance difference between using the CPU and the NPU for tasks like image generation and audio transcription. The NPU significantly reduces processing time while also allowing for better multitasking since the CPU and GPU are not being heavily taxed. This power efficiency is particularly beneficial for laptop users, as they may not have access to a powerful graphics card.Avram also mentions the potential drawbacks of relying on cloud services for AI tasks, such as privacy concerns and the need for a stable internet connection. Having the ability to perform these tasks locally with the NPU addresses these issues and provides a more convenient and secure solution.Additionally, he discusses the compatibility of Intel's OpenVINO project with Intel GPUs. While the NPU is not available for all tasks, the use of Intel GPUs can still enhance processing speed compared to using the CPU alone. However, it is important to note that the compatibility and optimization of these tasks may vary depending on the hardware used, and requires an Intel GPU in order to transfer tasks to a GPU (AMD and Nvidia will not work).New chips, benchmarking, performance differenceAvram highlights the discussion around new chips, benchmarking, and performance differences. He has been working on benchmarking and will soon release an article showcasing the performance differences between Intel and AMD chips, as well as the differences with the previous generation.Benchmarking plays a crucial role in evaluating the performance of these new chips. It allows for a direct comparison between different chip models and brands, as well as a comparison with previous generations. By conducting benchmark tests, Avram aims to provide readers with a clear understanding of the performance differences between Intel and AMD chips, as well as how the new chips perform compared to their predecessors.While the software is developed by Intel and focused on In tle hardware, the benchmarking has not always shown that to be the case. When accessing the NPU, which is currently specific to the Intel Core Ultra processors, Intel wins every time. However, when running the tests against the CPU, AMD often comes out ahead. This means that, while the NPU advantages are a clear winner, AMD processors are capable of just as much as Intel when it comes to direct CPU usage.ConclusionOverall, the introduction of Intel Core Ultra CPUs with an NPU represents a significant advancement in laptop technology. It offers users the ability to perform AI tasks locally, improving processing speed, power efficiency, and privacy. As technology continues to evolve, it is crucial to stay informed about these advancements and adapt to new developments that enhance our digital experiences.
Episode 8: With Intel rapidly improving their GPU division, and the new launch of the Arc A580, how close are Intel GPUs to getting our recommendation? We discuss that, as well as AMD's not very good Fluid Motion Frames technologyCHAPTERS0:00 - Intro04:55 - Intel Arc A580 Recap11:13 - Arc is Still A Bit Inconsistent Across Games19:45 - Intel Arc GPUs are Well Priced23:11 - Arc Isn't Far Away from Being Recommended28:28 - This is Intel's First Attempt32:58 - Good Intel GPUs Are Great For Competition40:32 - AMD Fluid Motion Frames Sucks55:44 - Updates from Our Boring LivesSUBSCRIBE TO THE PODCASTAudio: https://shows.acast.com/the-hardware-unboxed-podcastVideo: https://www.youtube.com/channel/UCqT8Vb3jweH6_tj2SarErfwSUPPORT US DIRECTLYPatreon: https://www.patreon.com/hardwareunboxedFloatplane: https://www.floatplane.com/channel/HardwareUnboxedLINKSYouTube: https://www.youtube.com/@Hardwareunboxed/Twitter: https://twitter.com/HardwareUnboxed Hosted on Acast. See acast.com/privacy for more information.
https://youtu.be/2BFfKfqE9cU On this episode of Destination Linux (338), we discuss GNOME's changes for Extensions and the challenges facing users and developers. We also check out news from Intel for support of Linux and their entry into the graphics card market and the potential of Intel GPUs. We also highlight upcoming events and opportunities for listeners to get involved. Then we talk about the new podcast on TuxDigital, Fit and Fueled. Plus, we have our tips, tricks and software picks for you. Let's get this show on the road toward Destination Linux! Download as MP3 (https://aphid.fireside.fm/d/1437767933/32f28071-0b08-4ea1-afcc-37af75bd83d6/2f2ec9f0-9500-43c5-8b32-29be7bb34365.mp3) Sponsored by LINBIT = https://linbit.com Hosted by: Michael Tunnell = https://tuxdigital.com Ryan (DasGeek) = https://dasgeekcommunity.com Jill Bryant = https://jilllinuxgirl.com Want to Support the Show? Become a Patron = https://tuxdigital.com/membership Store = https://tuxdigital.com/store Chapters: 00:00:00 DL 339 Intro 00:00:55 Community Feedback 00:10:03 Michael Made Me Do It 00:12:05 Extensions Breaking in GNOME 45 00:31:06 LINBIT 00:32:24 Intel Is Serious About Linux 00:46:11 Gaming: I made this Game in 3 Days 00:51:02 Software Spotlight: Speech Note 00:53:27 Tip of the Week: Game Show 00:59:52 Event: SCaLE 01:02:17 Outro
Timestamps: 0:00 Starfield crashes on Intel GPUs 1:26 Lenovo unveils Legion Go handheld 2:49 Intel takes lead in Arizona fab race 3:54 Volcanica Coffee 4:30 QUICK BITS 4:35 Gigabyte Gen5 1000 SSD hits 12GB/s 5:12 Anonymous Sudan hacks X, others 5:53 AMD Fluid Motion Frames for all! 6:27 Honor V Purse phone 6:57 Age of Empires, ants test war tactics News Sources: https://lmg.gg/Fzc4X
Coming up in this episode * The Catchup Episode (We've missed so much!) * The Red Hat Recap * Browser Watch...ing! * Some feedback, and a focus The Video Podcast (https://youtu.be/ZKm9vgJzAO8) https://youtu.be/ZKm9vgJzAO8 401 Audio Timestamps 0:00 Cold Open 2:16 The Gentoo Checkin 11:33 We Have a Lemmy! 19:24 Red Hat Recap 46:09 Browser Watch 1:05:21 Feedback 1:23:05 Community Focus: Linux Matters 1:27:03 App Focus: Jerboa & Memmy 1:34:48 Next Time: Debian 1:37:09 Stinger Banter Gentoo check in - Use the Handbook! (https://wiki.gentoo.org/wiki/Handbook:Main_Page) The wiki (https://wiki.gentoo.org/wiki/Main_Page) is just great in general. Lemmy (https://join-lemmy.org/) The Linux User Space Lemmy instance (https://lemmy.linuxuserspace.show/) feddit's community browser (https://browse.feddit.de/) Another Lemmy explorer (https://lemmyverse.net/communities) Announcements
Firefox enables hardware decoding for Intel GPUs on Linux! ReactOS reminds everyone they're still alive, a Pi Zero W powered handheld that runs DOOM, and Music Tribe nukes the GoXLR development team.
We are now launching our dedicated new YouTube and Twitter! Any help in amplifying our podcast would be greatly appreciated, and of course, tell your friends! Notable followon discussions collected on Twitter, Reddit, Reddit, Reddit, HN, and HN. Please don't obsess too much over the GPT4 discussion as it is mostly rumor; we spent much more time on tinybox/tinygrad on which George is the foremost authority!We are excited to share the world's first interview with George Hotz on the tiny corp!If you don't know George, he was the first person to unlock the iPhone, jailbreak the PS3, went on to start Comma.ai, and briefly “interned” at the Elon Musk-run Twitter. Tinycorp is the company behind the deep learning framework tinygrad, as well as the recently announced tinybox, a new $15,000 “luxury AI computer” aimed at local model training and inference, aka your “personal compute cluster”:* 738 FP16 TFLOPS* 144 GB GPU RAM* 5.76 TB/s RAM bandwidth* 30 GB/s model load bandwidth (big llama loads in around 4 seconds)* AMD EPYC CPU* 1600W (one 120V outlet)* Runs 65B FP16 LLaMA out of the box (using tinygrad, subject to software development risks)(In the episode, we also talked about the future of the tinybox as the intelligence center of every home that will help run models, at-home robots, and more. Make sure to check the timestamps
This is a recap of the top 10 posts on Hacker News on June 15th, 2023.This podcast was generated by Wondercraft: https://www.wondercraft.ai/?utm_source=hackernews_recap Please ping at team AT wondercraft.ai with feedback.(00:38): Reddit's blackout protest is set to continue indefinitelyOriginal post: https://news.ycombinator.com/item?id=36341941?utm_source=wondercraft_ai(02:12): Reddit Threatens to Remove Moderators from Subreddits Continuing BlackoutsOriginal post: https://news.ycombinator.com/item?id=36347711?utm_source=wondercraft_ai(03:31): My 24 year old HP Jornada can do things an iPhone still can't doOriginal post: https://news.ycombinator.com/item?id=36346254?utm_source=wondercraft_ai(04:58): Sequence diagrams, the only good thing UML brought to software developmentOriginal post: https://news.ycombinator.com/item?id=36342931?utm_source=wondercraft_ai(07:06): Our Plan for Python 3.13Original post: https://news.ycombinator.com/item?id=36339777?utm_source=wondercraft_ai(08:46): Unihiker, an $80 single-board PC with 2.8“ touchscreen, quad-core ARM Cortex-A35Original post: https://news.ycombinator.com/item?id=36341287?utm_source=wondercraft_ai(10:23): Reddit is removing moderators that protest by taking their communities privateOriginal post: https://news.ycombinator.com/item?id=36350938?utm_source=wondercraft_ai(12:01): UnsuckJS: Progressively enhance HTML with lightweight JavaScript librariesOriginal post: https://news.ycombinator.com/item?id=36343544?utm_source=wondercraft_ai(13:15): Alphabet selling Google Domains assets to SquarespaceOriginal post: https://news.ycombinator.com/item?id=36346454?utm_source=wondercraft_ai(14:38): Zluda: Run CUDA code on Intel GPUs, unmodifiedOriginal post: https://news.ycombinator.com/item?id=36341211?utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai
0:00 look, it's a monday 0:07 Intel Core rebranding 1:28 'Godfather of AI' quits Google with warning 2:44 Microsoft Silicon ARM chips? 3:33 Grammarly 4:20 QUICK BITS 4:26 Google Pixel Fold leaks 4:57 Edge browser ad for Bing 5:40 EA blames Jedi bugs on W10 6:19 Matrox announces Intel GPUs 7:03 Steam Deck controls turret News Sources: https://lmg.gg/eSSNs
► Check out today's hottest tech deals here: https://www.ufd.deals/ https://howl.me/cjdAFgYVw56 https://howl.me/cjdAIhrSEuB 0:00 - Intro 00:55 - AMD Sales: https://bit.ly/3kvKSha https://bit.ly/3mahrBT 02:00 - More Dead Space Remakes: https://bit.ly/3EF7uCy https://bit.ly/3ZmyDCj 02:35 - Build Tiny11 Yourself: https://bit.ly/3kwNYl4 03:32 - UFD Deals: https://www.ufd.deals/ https://howl.me/cjdAFgYVw56 https://howl.me/cjdAIhrSEuB 04:14 - Corsair Wood: https://bit.ly/3SyPgZp 05:27 - Tons of Intel GPUs: https://bit.ly/3ZFZedZ 05:54 - X3D Details: https://bit.ly/3Zl74cA https://bit.ly/3m85gWa ► Follow me on Twitch - http://www.twitch.tv/ufdisciple ► Join Our Discord: https://discord.gg/GduJmEM ► Support Us on Floatplane: https://www.floatplane.com/channel/ufdtech ► Support Us on Patreon: https://www.patreon.com/UFDTech ► Twitter - http://www.twitter.com/ufdisciple ► Facebook - http://www.facebook.com/ufdtech ► Instagram - http://www.instagram.com/ufd_tech ► Reddit - https://www.reddit.com/r/UFDTech/ Presenter: Brett Sticklemonster Videographer: Brett Sticklemonster Editor: Catlin Stevenson Thumbnail Designer: Reece Hill
The intel embargo for benchmarks and teardowns on the new A750 and A770 GPUs has lifted and it raises interesting questions --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/earlybirbbriefing/message Support this podcast: https://anchor.fm/earlybirbbriefing/support
This week Jeff is accompanied by Rett (he's awesome) and they are discussing everything happening in the world of tech, computers, gaming, craft beer and cocktails.
This week's podcast covers Intel's rising CPU prices, Minecraft avoids in-game NFTs, FaZe Clan goes public at $725M evaluation, Intel teases new GPU specifications and performance, Nintendo limits Wii U and 3DS eShop, Discord voice chat on Xbox, and the Stray game review! 0:00 Intro 0:37 Updates 6:53 Intel plans to raise CPU prices https://bit.ly/3cyWwmY 13:32 Minecraft developers won't allow NFTs https://bit.ly/3OqSURr 21:06 Faze Clan goes public in $725 million SPAC deal https://bit.ly/3B9gzCY 31:04 Intel Arc GPU details https://bit.ly/3OrXkYn 39:16 Nintendo Close Wii U and 3dS eShops https://bit.ly/3PqmTub 49:12 Discord voice chat is coming to Xbox https://bit.ly/3PqmVCj 1:01:16 Stray, Cat Simulator, Reviews https://bit.ly/3PtyXun 1:04:41 Rambling :) 1:12:09 Outro Leave a LIKE and a comment, thanks for watching/listening! ----------------------------------------------------------------------------------- PODCAST ►► https://anchor.fm/m2podcast AMAZON Music ► https://music.amazon.com/podcasts/091902c3-b83b-487c-8fe7-4c96787434fe/M2-Podcast APPLE ► https://podcasts.apple.com/podcast/id1531832410 BREAKER ► https://www.breaker.audio/m2-podcast-2 CASTRO ► https://castro.fm/podcast/6f69d373-d879-46d9-9f1c-bcf7c4bf1741 GOOGLE ► https://podcasts.google.com/feed/aHR0cHM6Ly9hbmNob3IuZm0vcy8zNTYwNWZiMC9wb2RjYXN0L3Jzcw== OVERCAST ► https://overcast.fm/itunes1531832410/m2-podcast POCKETCASTS ► https://pca.st/5jghvf6e RADIOPUBLIC ► https://radiopublic.com/m2-podcast-GMZkY4 SPOTIFY ► https://open.spotify.com/show/2VedhO03IRoHERJqF6Sy87 STICHER ► https://www.stitcher.com/podcast/m2-podcast TUNEIN ► http://tun.in/pj3ZI #podcast JOIN THE DISCORD! ►► https://discord.gg/Kp5Gre6 KyleHeath Socials: TIKTOK ►► https://www.tiktok.com/@mrjkheath TWITCH ►► https://www.twitch.tv/kyleheath TWITTER ►► https://twitter.com/mrjkheath YOUTUBE ►► https://www.youtube.com/MrJkheath MadMikeWillEatU Socials: FACEBOOK ►► https://www.facebook.com/MadMikeWillEatU/ INSTAGRAM ►► https://www.instagram.com/madmikewilleatu/ TIKTOK ►► https://www.tiktok.com/@madmikewilleatu TWITCH ►► https://www.twitch.tv/madmikewilleatu/about TWITTER ►► https://twitter.com/madmikewilleatu YOUTUBE ►► https://www.youtube.com/channel/UC1MoIvzyMDvH_5Ta
The FCC plans to increase the minimum speed needed to be considered high speed internet The FTC is looking into sketchy VPNs Apple could be launching M2 mac book pros this fall Apple rumored to have an M2 Extreme CPU coming Intel Arc leak shows they are very aggressively priced against AMD and Nvidia cards --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/earlybirbbriefing/message Support this podcast: https://anchor.fm/earlybirbbriefing/support
Intel said that their ARC GPUs were out in laptops... well it turns out it's one laptop model that it's out in... and only available in Korea... let's talk about it. --- Send in a voice message: https://anchor.fm/earlybirbbriefing/message Support this podcast: https://anchor.fm/earlybirbbriefing/support
Intel Arc GPUs are now out for laptops, and we have the specs. So what are my thoughts? Let's talk about it. --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/earlybirbbriefing/message Support this podcast: https://anchor.fm/earlybirbbriefing/support
News Sources: https://lmg.gg/7uvM1 Timestamps: 0:00 - How much news can we TechLink? 0:08 - The march of Intel GPUs 1:01 - Jack Dorsey takes flight from Twitter! 1:58 - AMD is now in Tesla vehicles! 2:40 - Sponsor - Drop HD 6XX 3:42 - Sony's New Controller 4:14 - Steam sets new records! 4:48 - Living ink! 5:20 - Specific Twitter display 5:58 - Who was that?
leaked benchmarks show the new Intel alchemist GPUs performing as well as as some mid tier GPUs, but how much does it really matter? Let's talk about it. --- Send in a voice message: https://anchor.fm/earlybirbbriefing/message Support this podcast: https://anchor.fm/earlybirbbriefing/support
CUDA on Intel GPUs! RedHat offers no-cost Red Hat Enterprise Linux to open source organizations, Firefox 86 gets multiple Picture-in-Picture support, and Framework announces their modular laptop.
In this episode of Talking Gaming and Tech will get into the up and downs of GameStop, Robin Hood App and Wall Street's reaction. There are now mods for Cyberpunk 2077. Skate 4 could begin production and no it's not a mobile game. Intel GPUs are here but who are they for? On the second half of the podcast, the OnePlus founder is forming a new company that may be for the budget OnePlus line of phones. Sonic the Hedgehog 2 will start filming soon but we also got some of the first images of the new Mortal Kombat movie. That and more on this episode of Talking Gaming and Tech Podcast.
In the show today we talk at length about the 3060, 3060ti, the silly prices and the re-release of the 2060/2060S. We finally move on to the Intel Xe discreet GPUs and finish off with the Newegg shuffle debacle. 3060 links https://videocardz.com/newz/nvidia-is-not-planning-geforce-rtx-3060-founders-edition https://www.tomshardware.com/news/msi-registers-rtx-3060-ti-miner-cards https://www.tomshardware.com/news/some-geforce-rtx-3060-may-end-up-costing-more-than-geforce-rtx-3060-ti 2060 re-release https://www.tomshardware.com/news/rtx-2060-and-2060-super-re-release-rumor Intel GPUs https://wccftech.com/intel-launches-dg1-graphics-card-based-on-10nm-superfin-for-oems-a-triumph-for-xe/ https://www.tomshardware.com/news/intel-iris-xe-max-dg1-gpu-performance-benchmark Newegg Lottery https://www.pcmag.com/news/newegg-responds-to-gpu-cpu-shortages-with-controversial-lottery-system tilliterate@gmail.com
This week Jeff is accompanied by Rett (he's Awesome) and they are discussing everything happening in the world of tech, computers, gaming, craft beer and cocktails.
Episode 13 of the Video Games... mmmHmmm podcast! In this episode we discuss God of War (2018), Battletech, Steamworld Dig 2, Legend of Heroes: Trails in the Sky, Pokemon, Frostpunk, Valve News, expensive monitors for Paul, possible Intel GPUs, ElDewrito, and Steamspy. Podcast Date 04/2018 Email us! mhmpodcast@gmail.com YouTube - https://www.youtube.com/channel/UC7_uWhawB_ny5y3gcchloIA?view_as=subscriber Twitter - https://twitter.com/videogamesmhm Jimmy Gang's Youtube - https://www.youtube.com/channel/UCJ3flKvbKGeTdFa8TFeztdQ Jimmy Gang's Twitter - https://twitter.com/kanaku_Highwind Mike Gibson's Twitter - https://twitter.com/link43130
Authentication Vulnerabilities in OpenBSD, NetBSD 9.0 RC1 is available, Running FreeNAS on a DigitalOcean droplet, NomadBSD 1.3 is here, at e2k19 nobody can hear you scream, and more. Headlines Authentication vulnerabilities in OpenBSD (https://www.openwall.com/lists/oss-security/2019/12/04/5) We discovered an authentication-bypass vulnerability in OpenBSD's authentication system: this vulnerability is remotely exploitable in smtpd, ldapd, and radiusd, but its real-world impact should be studied on a case-by-case basis. For example, sshd is not exploitable thanks to its defense-in-depth mechanisms. From the manual page of login.conf: OpenBSD uses BSD Authentication, which is made up of a variety of authentication styles. The authentication styles currently provided are: passwd Request a password and check it against the password in the master.passwd file. See loginpasswd(8). skey Send a challenge and request a response, checking it with S/Key (tm) authentication. See loginskey(8). yubikey Authenticate using a Yubico YubiKey token. See loginyubikey(8). For any given style, the program /usr/libexec/auth/loginstyle is used to perform the authentication. The synopsis of this program is: /usr/libexec/auth/login_style [-v name=value] [-s service] username class This is the first piece of the puzzle: if an attacker specifies a username of the form "-option", they can influence the behavior of the authentication program in unexpected ways. login_passwd [-s service] [-v wheel=yes|no] [-v lastchance=yes|no] user [class] The service argument specifies which protocol to use with the invoking program. The allowed protocols are login, challenge, and response. (The challenge protocol is silently ignored but will report success as passwd-style authentication is not challenge-response based). This is the second piece of the puzzle: if an attacker specifies the username "-schallenge" (or "-schallenge:passwd" to force a passwd-style authentication), then the authentication is automatically successful and therefore bypassed. Case study: smtpd Case study: ldapd Case study: radiusd Case study: sshd Acknowledgments: We thank Theo de Raadt and the OpenBSD developers for their incredibly quick response: they published patches for these vulnerabilities less than 40 hours after our initial contact. We also thank MITRE's CVE Assignment Team. First release candidate for NetBSD 9.0 available! (https://blog.netbsd.org/tnf/entry/first_release_candidate_for_netbsd) Since the start of the release process four months ago a lot of improvements went into the branch - more than 500 pullups were processed! This includes usbnet (a common framework for usb ethernet drivers), aarch64 stability enhancements and lots of new hardware support, installer/sysinst fixes and changes to the NVMM (hardware virtualization) interface. We hope this will lead to the best NetBSD release ever (only to be topped by NetBSD 10 next year). Here are a few highlights of the new release: Support for Arm AArch64 (64-bit Armv8-A) machines, including "Arm ServerReady" compliant machines (SBBR+SBSA) Enhanced hardware support for Armv7-A Updated GPU drivers (e.g. support for Intel Kabylake) Enhanced virtualization support Support for hardware-accelerated virtualization (NVMM) Support for Performance Monitoring Counters Support for Kernel ASLR Support several kernel sanitizers (KLEAK, KASAN, KUBSAN) Support for userland sanitizers Audit of the network stack Many improvements in NPF Updated ZFS Reworked error handling and NCQ support in the SATA subsystem Support a common framework for USB Ethernet drivers (usbnet) More information on the RC can be found on the NetBSD 9 release page (https://www.netbsd.org/releases/formal-9/NetBSD-9.0.html) News Roundup Running FreeNAS on a Digitalocean droplet (https://www.shlomimarco.com/post/running-freenas-on-a-digitalocean-droplet) ZFS is awesome. FreeBSD even more so. FreeNAS is the battle-tested, enterprise-ready-yet-home-user-friendly software defined storage solution which is cooler then deep space, based on FreeBSD and makes heavy use of ZFS. This is what I (and soooooo many others) use for just about any storage-related task. I can go on and on and on about what makes it great, but if you're here, reading this, you probably know all that already and we can skip ahead. I've needed an offsite FreeNAS setup to replicate things to, to run some things, to do some stuff, basically, my privately-owned, tightly-controlled NAS appliance in the cloud, one I control from top to bottom and with support for whatever crazy thing I'm trying to do. Since I'm using DigitalOcean as my main VPS provider, it seemed logical to run FreeNAS there, however, you can't. While DO supports many many distos and pre-setup applications (e.g OpenVPN), FreeNAS isn't a supported feature, at least not in the traditional way :) Before we begin, here's the gist of what we're going to do: Base of a FreeBSD droplet, we'll re-image our boot block device with FreeNAS iso. We'll then install FreeNAS on the second block device. Once done we're going to do the ol' switcheroo: we're going to re-image our original boot block device using the now FreeNAS-installed second block device. Part 1: re-image our boot block device to boot FreeNAS install media. Part 2: Install FreeNAS on the second block-device Part 3: Re-image the boot block device using the FreeNAS-installed block device NomadBSD 1.3 is now available (https://nomadbsd.org/) From the release notes: The base system has been changed to FreeBSD 12.1-RELEASE-p1 Due to a deadlock problem, FreeBSD's unionfs has been replaced by unionfs-fuse The GPT layout has been changed to MBR. This prevents problems with Lenovo systems that refuse to boot from GPT if "lenovofix" is not set, and systems that hang on boot if "lenovofix" is set. Support for ZFS installations has been added to the NomadBSD installer. The rc-script for setting up the network interfaces has been fixed and improved. Support for setting the country code for the wlan device has been added. Auto configuration for running in VirtualBox has been added. A check for the default display has been added to the graphics configuration scripts. This fixes problems where users with Optimus have their NVIDIA card disabled, and use the integrated graphics chip instead. NVIDIA driver version 440 has been added. nomadbsd-dmconfig, a Qt tool for selecting the display manager theme, setting the default user and autologin has been added. nomadbsd-adduser, a Qt tool for added preconfigured user accounts to the system has been added. Martin Orszulik added Czech translations to the setup and installation wizard. The NomadBSD logo, designed by Ian Grindley, has been changed. Support for localized error messages has been added. Support for localizing the password prompts has been added. Some templates for starting other DEs have been added to ~/.xinitrc. The interfaces of nomadbsd-setup-gui and nomadbsd-install-gui have been improved. A script that helps users to configure a multihead systems has been added. The Xorg driver for newer Intel GPUs has been changed from "intel" to "modesetting". /proc has been added to /etc/fstab A D-Bus session issue has been fixed which prevented thunar from accessing samba shares. DSBBg which allows users to change and manage wallpapers has been added. The latest version of update_obmenu now supports auto-updating the Openbox menu. Manually updating the Openbox menu after packet (de)installation is therefore no longer needed. Support for multiple keyboard layouts has been added. www/palemoon has been removed. mail/thunderbird has been removed. audio/audacity has been added. deskutils/orage has been added. the password manager fpm2 has been replaced by KeePassXC mail/sylpheed has been replaced by mail/claws-mail multimedia/simplescreenrecorder has been added. DSBMC has been changed to DSBMC-Qt Many small improvements and bug fixes. At e2k19 nobody can hear you scream (https://undeadly.org/cgi?action=article;sid=20191204170908) After 2 years it was once again time to pack skis and snowshoes, put a satellite dish onto a sledge and hike through the snowy rockies to the Elk Lakes hut. I did not really have much of a plan what I wanted to work on but there were a few things I wanted to look into. One of them was rpki-client and the fact that it was so incredibly slow. Since Bob beck@ was around I started to ask him innocent X509 questions ... as if there are innocent X509 questions! Mainly about the abuse of the X509STORE in rpki-client. Pretty soon it was clear that rpki-client did it all wrong and most of the X509 verification had to be rewritten. Instead of only storing the root certificates in the store and passing the intermediate certs as a chain to the verification function rpki-client threw everything into it. The X509STORE is just not built for such an abuse and so it was no wonder that this was slow. Lucky me I pulled benno@ with me into this dark hole of libcrypto code. He managed to build up an initial diff to pass the chains as a STACKOF(X509) and together we managed to get it working. A big thanks goes to ingo@ who documented most of the functions we had to use. Have a look at STACKOF(3) and skpopfree(3) to understand why benno@ and I slowly turned crazy. Our next challenge was to only load the necessary certificate revocation list into the X509STORECTX. While doing those changes it became obvious that some of the data structures needed better lookup functions. Looking up certificates was done using a linear lookup and so we replaced the internal certificate and CRL tables with RB trees for fast lookups. deraadt@ also joined the rpki-client commit fest and changed the output code to use rename(2) so that files are replaced in an atomic operation. Thanks to this rpki-client can now be safely run from cron (there is an example in the default crontab). I did not plan to spend most of my week hacking on rpki-client but in the end I'm happy that I did and the result is fairly impressive. Working with libcrypto code and especially X509 was less than pleasant. Our screams of agony died away in the snowy rocky mountains and made Bob deep dive into UVM with a smile since he knew that benno@ and I had it worse. In case you wonder thanks to all changes at e2k19 rpki-client improved from over 20min run time to validate all VRPS to roughly 1min to do the same job. A factor 20 improvement! Thanks to Theo, Bob and Howie to make this possible. To all the cooks for the great food and to Xplornet for providing us with Internet at the hut. Beastie Bits FOSDEM 2020 BSD Devroom schedule (https://fosdem.org/2020/schedule/track/bsd/) Easy Minecraft Server on FreeBSD Howto (https://www.freebsdfoundation.org/freebsd/how-to-guides/easy-minecraft-server-on-freebsd/) stats(3) framework in the TCP stack (https://svnweb.freebsd.org/base?view=revision&revision=355304) 4017 days of uptime (https://twitter.com/EdwinKremer/status/1203071684535889921) sysget - A front-end for every package manager (https://github.com/emilengler/sysget) PlayOnBSD’s Cross-BSD Shopping Guide (https://www.playonbsd.com/shopping_guide/) Feedback/Questions Pat asks about the proper disk drive type for ZFS (http://dpaste.com/2FDN26X#wrap) Brad asks about a ZFS rosetta stone (http://dpaste.com/2X8PBMC#wrap) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Your browser does not support the HTML5 video tag. Special Guest: Mariusz Zaborski.
Freshbooks: For your unrestricted 30 days free trial, go to https://www.freshbooks.com/WAN and enter in “The WAN Show” in the how you heard about us section. Savage Jerky: Use offer code LTT to save 10% on Savage Jerky at https://lmg.gg/savagejerky Private Internet Access: Sign up for Private Internet Access VPN at https://lmg.gg/piawan LTX 2019: Get LTX 2019 Featuring DreamHack tickets NOW at https://dh.je/ltx19 Timestamps: (Courtesy of zach hoppe) 00:00 - Topics 01:10 - Intro 02:02 - Luke is tired 02:29 - Ubisoft killing game keys 09:15 - Facebook F8 Developer Conference "The future is private" 14:48 - Facebook Secret Crush Dating 18:44 - Intel GPUs get Ray Tracing 21:25 - Navi 7nm GPU end of 2019? (Rumer) 26:47 - Sponsors 32:25 - Bill and Ted 3 33:02 - LTX Updates 36:13 - Epic buys Psyonix 50:00 - Would you buy the Valve Index Headset for Half-Life 3 53:10 - Outro
OpenBSD 6.5 has been released, mount ZFS datasets anywhere, help test upcoming NetBSD 9 branch, LibreSSL 2.9.1 is available, Bail Bond Denied Edition of FreeBSD Mastery: Jails, and one reason ed(1) was a good editor back in the days in this week’s episode. Headlines OpenBSD 6.5 Released Changelog Mirrors 6.5 Includes OpenSMTPD 6.5.0 LibreSSL 2.9.1 OpenSSH 8.0 Mandoc 1.14.5 Xenocara LLVM/Clang 7.0.1 (+ patches) GCC 4.2.1 (+ patches) and 3.3.6 (+ patches) Many pre-built packages for each architecture: aarch64: 9654 amd64: 10602 i386: 10535 Mount your ZFS datasets anywhere you want ZFS is very flexible about mountpoints, and there are many features available to provide great flexibility. When you create zpool maintank, the default mountpoint is /maintank. You might be happy with that, but you don’t have to be content. You can do magical things. Some highlights are: mount point can be inherited not all filesystems in a zpool need to be mounted each filesystem (directory) can have different ZFS characteristics In my case, let’s look at this new zpool I created earlier today and I will show you some very simple alternatives. This zpool use NVMe devices which should be faster than SSDs especially when used with multiple concurrent writes. This is my plan: run all the Bacula regression tests concurrently. News Roundup Branch for netbsd 9 upcoming, please help and test -current Folks, once again we are quite late for branching the next NetBSD release (NetBSD 9). Initially planned to happen early in February 2019, we are now approaching May and it is unlikely that the branch will happen before that. On the positive side, lots of good things landed in -current in between, like new Mesa, new jemalloc, lots of ZFS improvements - and some of those would be hard to pull up to the branch later. On the bad side we saw lots of churn in -current recently, and there is quite some fallout where we not even have a good overview right now. And this is where you can help: please test -current, on all the various machines you have especially interesting would be test results from uncommon architectures or strange combinations (like the sparc userland on sparc64 kernel issue I ran in yesterday) Please test, report success, and file PRs for failures! We will likely announce the real branch date on quite short notice, the likely next candidates would be mid may or end of may. We may need to do extra steps after the branch (like switch some architectures back to old jemalloc on the branch). However, the less difference between -current and the branch, the easier will the release cycle go. Our goal is to have an unprecedented short release cycle this time. But.. we always say that upfront. LibreSSL 2.9.1 Released We have released LibreSSL 2.9.1, which will be arriving in the LibreSSL directory of your local OpenBSD mirror soon. This is the first stable release from the 2.9 series, which is also included with OpenBSD 6.5 It includes the following changes and improvements from LibreSSL 2.8.x: API and Documentation Enhancements CRYPTO_LOCK is now automatically initialized, with the legacy callbacks stubbed for compatibility. Added the SM3 hash function from the Chinese standard GB/T 32905-2016. Added the SM4 block cipher from the Chinese standard GB/T 32907-2016. Added more OPENSSLNO* macros for compatibility with OpenSSL. Partial port of the OpenSSL ECKEYMETHOD API for use by OpenSSH. Implemented further missing OpenSSL 1.1 API. Added support for XChaCha20 and XChaCha20-Poly1305. Added support for AES key wrap constructions via the EVP interface. Compatibility Changes Added pbkdf2 key derivation support to openssl(1) enc. Changed the default digest type of openssl(1) enc to sha256. Changed the default digest type of openssl(1) dgst to sha256. Changed the default digest type of openssl(1) x509 -fingerprint to sha256. Changed the default digest type of openssl(1) crl -fingerprint to sha256. Testing and Proactive Security Added extensive interoperability tests between LibreSSL and OpenSSL 1.0 and 1.1. Added additional Wycheproof tests and related bug fixes. Internal Improvements Simplified sigalgs option processing and handshake signing algorithm selection. Added the ability to use the RSA PSS algorithm for handshake signatures. Added bnrandinterval() and use it in code needing ranges of random bn values. Added functionality to derive early, handshake, and application secrets as per RFC8446. Added handshake state machine from RFC8446. Removed some ASN.1 related code from libcrypto that had not been used since around 2000. Unexported internal symbols and internalized more record layer structs. Removed SHA224 based handshake signatures from consideration for use in a TLS 1.2 handshake. Portable Improvements Added support for assembly optimizations on 32-bit ARM ELF targets. Added support for assembly optimizations on Mingw-w64 targets. Improved Android compatibility Bug Fixes Improved protection against timing side channels in ECDSA signature generation. Coordinate blinding was added to some elliptic curves. This is the last bit of the work by Brumley et al. to protect against the Portsmash vulnerability. Ensure transcript handshake is always freed with TLS 1.2. The LibreSSL project continues improvement of the codebase to reflect modern, safe programming practices. We welcome feedback and improvements from the broader community. Thanks to all of the contributors who helped make this release possible. FreeBSD Mastery: Jails – Bail Bond Denied Edition I had a brilliant, hideous idea: to produce a charity edition of FreeBSD Mastery: Jails featuring the cover art I would use if I was imprisoned and did not have access to a real cover artist. (Never mind that I wouldn’t be permitted to release books while in jail: we creative sorts scoff at mere legal and cultural details.) I originally wanted to produce my own take on the book’s cover art. My first attempt failed spectacularly. I downgraded my expectations and tried again. And again. And again. I’m pleased to reveal the final cover for FreeBSD Mastery: Jails–Bail Bond Edition! This cover represents the very pinnacle of my artistic talents, and is the result of literally hours of effort. But, as this book is available only to the winner of charity fund-raisers, purchase of this tome represents moral supremacy. I recommend flaunting it to your family, coworkers, and all those of lesser character. Get your copy by winning the BSDCan 2019 charity auction… or any other other auction-type event I deem worthwhile. As far as my moral fiber goes: I have learned that art is hard, and that artists are not paid enough. And if I am ever imprisoned, I do hope that you’ll contribute to my bail fund. Otherwise, you’ll get more covers like this one. One reason ed(1) was a good editor back in the days of V7 Unix It is common to describe ed(1) as being line oriented, as opposed to screen oriented editors like vi. This is completely accurate but it is perhaps not a complete enough description for today, because ed is line oriented in a way that is now uncommon. After all, you could say that your shell is line oriented too, and very few people use shells that work and feel the same way ed does. The surface difference between most people's shells and ed is that most people's shells have some version of cursor based interactive editing. The deeper difference is that this requires the shell to run in character by character TTY input mode, also called raw mode. By contrast, ed runs in what Unix usually calls cooked mode, where it reads whole lines from the kernel and the kernel handles things like backspace. All of ed's commands are designed so that they work in this line focused way (including being terminated by the end of the line), and as a whole ed's interface makes this whole line input approach natural. In fact I think ed makes it so natural that it's hard to think of things as being any other way. Ed was designed for line at a time input, not just to not be screen oriented. This input mode difference is not very important today, but in the days of V7 and serial terminals it made a real difference. In cooked mode, V7 ran very little code when you entered each character; almost everything was deferred until it could be processed in bulk by the kernel, and then handed to ed all in a single line which ed could also process all at once. A version of ed that tried to work in raw mode would have been much more resource intensive, even if it still operated on single lines at a time. Beastie Bits CFT for FreeBSD ZoL Simple DNS Adblock AT&T Unix PC in 1985 OpenBSD-current drm at 4.19, includes new support for Intel GPUs like Coffee Lake "What are the differences between Linux and OpenBSD?" - Twitter thread Announcing the pkgsrc-2019Q1 release (2019-04-10) Feedback/Questions Brad - iocage Frank - Video from Level1Tech and a question Niall - Revision Control Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv Your browser does not support the HTML5 video tag.
DragonflyBSD’s hammer1 encrypted master/slave setup, second part of our BSDCan recap, NomadBSD 1.1-RC1 available, OpenBSD adds an LDAP client to base, FreeBSD gets pNFS support, Intel FPU Speculation Vulnerability confirmed, and what some Unix command names mean. ##Headlines DragonflyBSD: Towards a HAMMER1 master/slave encrypted setup with LUKS I just wanted to share my experience with setting up DragonFly master/slave HAMMER1 PFS’s on top of LUKS So after a long time using an Synology for my NFS needs, I decided it was time to rethink my setup a little since I had several issues with it : You cannot run NFS on top of encrypted partitions easily I suspect I am having some some data corruption (bitrot) on the ext4 filesystem the NIC was stcuk to 100 Mbps instead of 1 Gbps even after swapping cables, switches, you name it It’s proprietary I have been playing with DragonFly in the past and knew about HAMMER, now I just had the perfect excuse to actually use it in production :) After setting up the OS, creating the LUKS partition and HAMMER FS was easy : kdload dm cryptsetup luksFormat /dev/serno/ cryptsetup luksOpen /dev/serno/ fort_knox newfs_hammer -L hammer1_secure_master /dev/mapper/fort_knox cryptsetup luksFormat /dev/serno/ cryptsetup luksOpen /dev/serno/ fort_knox_slave newfs_hammer -L hammer1_secure_slave /dev/mapper/fort_knox_slave Mount the 2 drives : mount /dev/mapper/fort_knox /fort_knox mount /dev/mapper_fort_know_slave /fort_knox_slave You can now put your data under /fort_knox Now, off to setting up the replication, first get the shared-uuid of /fort_knox hammer pfs-status /fort_knox Create a PFS slave “linked” to the master hammer pfs-slave /fort_knox_slave/pfs/slave shared-uuid=f9e7cc0d-eb59-10e3-a5b5-01e6e7cefc12 And then stream your data to the slave PFS ! hammer mirror-stream /fort_knox /fort_knox_slave/pfs/slave After that, setting NFS is fairly trivial even though I had problem with the /etc/exports syntax which is different than Linux There’s a few things I wish would be better though but nothing too problematic or without workarounds : Cannot unlock LUKS partitions at boot time afaik (Acceptable tradeoff for the added security LUKS gives me vs my old Synology setup) but this force me to run a script to unlock LUKS, mount hammer and start mirror-stream at each boot No S1/S3 sleep so I made a script to shutdown the system when there’s no network neighborgs to serve the NFS As my system isn’t online 24/7 for energy reasons, I guess will have to run hammer cleanup myself from time to time Some uncertainty because hey, it’s kind of exotic but exciting too :) Overall, I am happy, HAMMER1 and PFS are looking really good, DragonFly is a neat Unix and the community is super friendly (Matthew Dillon actually provided me with a kernel patch to fix the broken ACPI on the PC holding this setup, many thanks!), the system is still a “work in progress” but it is already serving my files as I write this post. Let’s see in 6 months how it goes in the longer run ! Helpful resources : https://www.dragonflybsd.org/docs/how_to_implement_hammer_pseudo_file_system__40___pfs___41___slave_mirroring_from_pfs_master/ ###BSDCan 2018 Recap As promised, here is our second part of our BSDCan report, covering the conference proper. The last tutorials/devsummit of that day lead directly into the conference, as people could pick up their registration packs at the Red Lion and have a drink with fellow BSD folks. Allan and I were there only briefly, as we wanted to get back to the “Newcomers orientation and mentorship” session lead by Michael W. Lucas. This session is intended for people that are new to BSDCan (maybe their first BSD conference ever?) and may have questions. Michael explained everything from the 6-2-1 rule (hours of sleep, meals per day, and number of showers that attendees should have at a minimum), to the partner and widowers program (lead by his wife Liz), to the sessions that people should not miss (opening, closing, and hallway track). Old-time BSDCan folks were asked to stand up so that people can recognize them and ask them any questions they might have during the conferences. The session was well attended. Afterwards, people went for dinner in groups, a big one lead by Michael Lucas to his favorite Shawarma place, followed by gelato (of course). This allowed newbies to mingle over dinner and ice cream, creating a welcoming atmosphere. The next day, after Dan Langille opened the conference, Benno Rice gave the keynote presentation about “The Tragedy of Systemd”. Benedict went to the following talks: “Automating Network Infrastructures with Ansible on FreeBSD” in the DevSummit track. A good talk that connected well with his Ansible tutorial and even allowed some discussions among participants. “All along the dwatch tower”: Devin delivered a well prepared talk. I first thought that the number of slides would not fit into the time slot, but she even managed to give a demo of her work, which was well received. The dwatch tool she wrote should make it easy for people to get started with DTrace without learning too much about the syntax at first. The visualizations were certainly nice to see, combining different tools together in a new way. ZFS BoF, lead by Allan and Matthew Ahrens SSH Key Management by Michael W. Lucas. Yet another great talk where I learned a lot. I did not get to the SSH CA chapter in the new SSH Mastery book, so this was a good way to wet my appetite for it and motivated me to look into creating one for the cluster that I’m managing. The rest of the day was spent at the FreeBSD Foundation table, talking to various folks. Then, Allan and I had an interview with Kirk McKusick for National FreeBSD Day, then we had a core meeting, followed by a core dinner. Day 2: “Flexible Disk Use in OpenZFS”: Matthew Ahrens talking about the feature he is implementing to expand a RAID-Z with a single disk, as well as device removal. Allan’s talk about his efforts to implement ZSTD in OpenZFS as another compression algorithm. I liked his overview slides with the numbers comparing the algorithms for their effectiveness and his personal story about the sometimes rocky road to get the feature implemented. “zrepl - ZFS replication” by Christian Schwarz, was well prepared and even had a demo to show what his snapshot replication tool can do. We covered it on the show before and people can find it under sysutils/zrepl. Feedback and help is welcome. “The Evolution of FreeBSD Governance” by Kirk McKusick was yet another great talk by him covering the early days of FreeBSD until today, detailing some of the progress and challenges the project faced over the years in terms of leadership and governance. This is an ongoing process that everyone in the community should participate in to keep the project healthy and infused with fresh blood. Closing session and auction were funny and great as always. All in all, yet another amazing BSDCan. Thank you Dan Langille and your organizing team for making it happen! Well done. Digital Ocean ###NomadBSD 1.1-RC1 Released The first – and hopefully final – release candidate of NomadBSD 1.1 is available! Changes The base system has been upgraded to FreeBSD 11.2-RC3 EFI booting has been fixed. Support for modern Intel GPUs has been added. Support for installing packages has been added. Improved setup menu. More software packages: benchmarks/bonnie++ DSBDisplaySettings DSBExec DSBSu mail/thunderbird net/mosh ports-mgmt/octopkg print/qpdfview security/nmap sysutils/ddrescue sysutils/fusefs-hfsfuse sysutils/fusefs-sshfs sysutils/sleuthkit www/lynx x11-wm/compton x11/xev x11/xterm Many improvements and bugfixes The image and instructions can be found here. ##News Roundup LDAP client added to -current CVSROOT: /cvs Module name: src Changes by: reyk@cvs.openbsd.org 2018/06/13 09:45:58 Log message: Import ldap(1), a simple ldap search client. We have an ldapd(8) server and ypldap in base, so it makes sense to have a simple LDAP client without depending on the OpenLDAP package. This tool can be used in an ssh(1) AuthorizedKeysCommand script. With feedback from many including millert@ schwarze@ gilles@ dlg@ jsing@ OK deraadt@ Status: Vendor Tag: reyk Release Tags: ldap_20180613 N src/usr.bin/ldap/Makefile N src/usr.bin/ldap/aldap.c N src/usr.bin/ldap/aldap.h N src/usr.bin/ldap/ber.c N src/usr.bin/ldap/ber.h N src/usr.bin/ldap/ldap.1 N src/usr.bin/ldap/ldapclient.c N src/usr.bin/ldap/log.c N src/usr.bin/ldap/log.h No conflicts created by this import ###Intel® FPU Speculation Vulnerability Confirmed Earlier this month, Philip Guenther (guenther@) committed (to amd64 -current) a change from lazy to semi-eager FPU switching to mitigate against rumored FPU state leakage in Intel® CPUs. Theo de Raadt (deraadt@) discussed this in his BSDCan 2018 session. Using information disclosed in Theo’s talk, Colin Percival developed a proof-of-concept exploit in around 5 hours. This seems to have prompted an early end to an embargo (in which OpenBSD was not involved), and the official announcement of the vulnerability. FPU change in FreeBSD Summary: System software may utilize the Lazy FP state restore technique to delay the restoring of state until an instruction operating on that state is actually executed by the new process. Systems using Intel® Core-based microprocessors may potentially allow a local process to infer data utilizing Lazy FP state restore from another process through a speculative execution side channel. Description: System software may opt to utilize Lazy FP state restore instead of eager save and restore of the state upon a context switch. Lazy restored states are potentially vulnerable to exploits where one process may infer register values of other processes through a speculative execution side channel that infers their value. · CVSS - 4.3 Medium CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N Affected Products: Intel® Core-based microprocessors. Recommendations: If an XSAVE-enabled feature is disabled, then we recommend either its state component bitmap in the extended control register (XCR0) is set to 0 (e.g. XCR0[bit 2]=0 for AVX, XCR0[bits 7:5]=0 for AVX512) or the corresponding register states of the feature should be cleared prior to being disabled. Also for relevant states (e.g. x87, SSE, AVX, etc.), Intel recommends system software developers utilize Eager FP state restore in lieu of Lazy FP state restore. Acknowledgements: Intel would like to thank Julian Stecklina from Amazon Germany, Thomas Prescher from Cyberus Technology GmbH (https://www.cyberus-technology.de/), Zdenek Sojka from SYSGO AG (http://sysgo.com), and Colin Percival for reporting this issue and working with us on coordinated disclosure. iXsystems iX Ad Spot iX Systems - BSDCan 2018 Recap ###FreeBSD gets pNFS support Merge the pNFS server code from projects/pnfs-planb-server into head. This code merge adds a pNFS service to the NFSv4.1 server. Although it is a large commit it should not affect behaviour for a non-pNFS NFS server. Some documentation on how this works can be found at: Merge the pN http://people.freebsd.org/~rmacklem/pnfs-planb-setup.txt and will hopefully be turned into a proper document soon. This is a merge of the kernel code. Userland and man page changes will come soon, once the dust settles on this merge. It has passed a "make universe", so I hope it will not cause build problems. It also adds NFSv4.1 server support for the "current stateid". Here is a brief overview of the pNFS service: A pNFS service separates the Read/Write operations from all the other NFSv4.1 Metadata operations. It is hoped that this separation allows a pNFS service to be configured that exceeds the limits of a single NFS server for either storage capacity and/or I/O bandwidth. It is possible to configure mirroring within the data servers (DSs) so that the data storage file for an MDS file will be mirrored on two or more of the DSs. When this is used, failure of a DS will not stop the pNFS service and a failed DS can be recovered once repaired while the pNFS service continues to operate. Although two way mirroring would be the norm, it is possible to set a mirroring level of up to four or the number of DSs, whichever is less. The Metadata server will always be a single point of failure, just as a single NFS server is. A Plan B pNFS service consists of a single MetaData Server (MDS) and K Data Servers (DS), all of which are recent FreeBSD systems. Clients will mount the MDS as they would a single NFS server. When files are created, the MDS creates a file tree identical to what a single NFS server creates, except that all the regular (VREG) files will be empty. As such, if you look at the exported tree on the MDS directly on the MDS server (not via an NFS mount), the files will all be of size 0. Each of these files will also have two extended attributes in the system attribute name space: pnfsd.dsfile - This extended attrbute stores the information that the MDS needs to find the data storage file(s) on DS(s) for this file. pnfsd.dsattr - This extended attribute stores the Size, AccessTime, ModifyTime and Change attributes for the file, so that the MDS doesn't need to acquire the attributes from the DS for every Getattr operation. For each regular (VREG) file, the MDS creates a data storage file on one (or more if mirroring is enabled) of the DSs in one of the "dsNN" subdirectories. The name of this file is the file handle of the file on the MDS in hexadecimal so that the name is unique. The DSs use subdirectories named "ds0" to "dsN" so that no one directory gets too large. The value of "N" is set via the sysctl vfs.nfsd.dsdirsize on the MDS, with the default being 20. For production servers that will store a lot of files, this value should probably be much larger. It can be increased when the "nfsd" daemon is not running on the MDS, once the "dsK" directories are created. For pNFS aware NFSv4.1 clients, the FreeBSD server will return two pieces of information to the client that allows it to do I/O directly to the DS. DeviceInfo - This is relatively static information that defines what a DS is. The critical bits of information returned by the FreeBSD server is the IP address of the DS and, for the Flexible File layout, that NFSv4.1 is to be used and that it is "tightly coupled". There is a "deviceid" which identifies the DeviceInfo. Layout - This is per file and can be recalled by the server when it is no longer valid. For the FreeBSD server, there is support for two types of layout, call File and Flexible File layout. Both allow the client to do I/O on the DS via NFSv4.1 I/O operations. The Flexible File layout is a more recent variant that allows specification of mirrors, where the client is expected to do writes to all mirrors to maintain them in a consistent state. The Flexible File layout also allows the client to report I/O errors for a DS back to the MDS. The Flexible File layout supports two variants referred to as "tightly coupled" vs "loosely coupled". The FreeBSD server always uses the "tightly coupled" variant where the client uses the same credentials to do I/O on the DS as it would on the MDS. For the "loosely coupled" variant, the layout specifies a synthetic user/group that the client uses to do I/O on the DS. The FreeBSD server does not do striping and always returns layouts for the entire file. The critical information in a layout is Read vs Read/Writea and DeviceID(s) that identify which DS(s) the data is stored on. At this time, the MDS generates File Layout layouts to NFSv4.1 clients that know how to do pNFS for the non-mirrored DS case unless the sysctl vfs.nfsd.default_flexfile is set non-zero, in which case Flexible File layouts are generated. The mirrored DS configuration always generates Flexible File layouts. For NFS clients that do not support NFSv4.1 pNFS, all I/O operations are done against the MDS which acts as a proxy for the appropriate DS(s). When the MDS receives an I/O RPC, it will do the RPC on the DS as a proxy. If the DS is on the same machine, the MDS/DS will do the RPC on the DS as a proxy and so on, until the machine runs out of some resource, such as session slots or mbufs. As such, DSs must be separate systems from the MDS. *** ###[What does {some strange unix command name} stand for?](http://www.unixguide.net/unix/faq/1.3.shtml) + awk = "Aho Weinberger and Kernighan" + grep = "Global Regular Expression Print" + fgrep = "Fixed GREP". + egrep = "Extended GREP" + cat = "CATenate" + gecos = "General Electric Comprehensive Operating Supervisor" + nroff = "New ROFF" + troff = "Typesetter new ROFF" + tee = T + bss = "Block Started by Symbol + biff = "BIFF" + rc (as in ".cshrc" or "/etc/rc") = "RunCom" + Don Libes' book "Life with Unix" contains lots more of these tidbits. *** ##Beastie Bits + [RetroBSD: Unix for microcontrollers](http://retrobsd.org/wiki/doku.php) + [On the matter of OpenBSD breaking embargos (KRACK)](https://marc.info/?l=openbsd-tech&m=152910536208954&w=2) + [Theo's Basement Computer Paradise (1998)](https://zeus.theos.com/deraadt/hosts.html) + [Airport Extreme runs NetBSD](https://jcs.org/2018/06/12/airport_ssh) + [What UNIX shell could have been](https://rain-1.github.io/shell-2.html) *** Tarsnap ad *** ##Feedback/Questions + We need more feedback and questions. Please email feedback@bsdnow.tv + Also, many of you owe us BSDCan trip reports! We have shared what our experience at BSDCan was like, but we want to hear about yours. What can we do better next year? What was it like being there for the first time? + [Jason writes in](https://slexy.org/view/s205jU58X2) + https://www.wheelsystems.com/en/products/wheel-fudo-psm/ + [June 19th was National FreeBSD Day](https://twitter.com/search?src=typd&q=%23FreeBSDDay) *** - Send questions, comments, show ideas/topics, or stories you want mentioned on the show to [feedback@bsdnow.tv](mailto:feedback@bsdnow.tv) ***
There is a lot of the table for discussion today as Patrick and Ryan dive into Intel's Core i7-8086K reactions, news that Qualcomm is, in fact, staying in the data center market, confirmation that Intel will have discrete GPU solutions available in 2020, indications that Intel could be worried about more market share loss to AMD's EPYC processors than originally expected, the new Oak Ridge supercomputer powered by IBM and NVIDIA, experiences with the ASUS NovaGo Always On, Always Connected PC, and notes from E3!
We have a first PS4 kernel exploit, the long awaited OpenZFS devsummit report by Allan, DragonflyBSD 5.0 is out, we show you vmadm to manage jails, and parallel processing with Unix tools. This episode was brought to you by Headlines The First PS4 Kernel Exploit: Adieu (https://fail0verflow.com/blog/2017/ps4-namedobj-exploit/) The First PS4 Kernel Exploit: Adieu Plenty of time has passed since we first demonstrated Linux running on the PS4. Now we will step back a bit and explain how we managed to jump from the browser process into the kernel such that ps4-kexec et al. are usable. Over time, ps4 firmware revisions have progressively added many mitigations and in general tried to lock down the system. This post will mainly touch on vulnerabilities and issues which are not present on the latest releases, but should still be useful for people wanting to investigate ps4 security. Vulnerability Discovery As previously explained, we were able to get a dump of the ps4 firmware 1.01 kernel via a PCIe man-in-the-middle attack. Like all FreeBSD kernels, this image included “export symbols” - symbols which are required to perform kernel and module initialization processes. However, the ps4 1.01 kernel also included full ELF symbols (obviously an oversight as they have been removed in later firmware versions). This oversight was beneficial to the reverse engineering process, although of course not a true prerequisite. Indeed, we began exploring the kernel by examining built-in metadata in the form of the syscall handler table - focusing on the ps4-specific entries. Each process object in the kernel contains its own “idt” (ID Table) object. As can be inferred from the snippet above, the hash table essentially just stores pointers to opaque data blobs, along with a given kind and name. Entries may be accessed (and thus “locked”) with either read or write intent. Note that IDTTYPE is not a bitfield consisting of only unique powers of 2. This means that if we can control the kind of an identry, we may be able to cause a type confusion to occur (it is assumed that we may control name). Exploitation To an exploiter without ps4 background, it might seem that the easiest way to exploit this bug would be to take advantage of the write off the end of the malloc'd namedobjusrt object. However, this turns out to be impossible (as far as I know) because of a side effect of the ps4 page size being changed to 0x4000 bytes (from the normal of 0x1000). It appears that in order to change the page size globally, the ps4 kernel developers opted to directly change the related macros. One of the many changes resulting from this is that the smallest actual amount of memory which malloc may give back to a caller becomes 0x40 bytes. While this also results in tons of memory being completely wasted, it does serve to nullify certain exploitation techniques (likely completely by accident…). Adieu The namedobj exploit was present and exploitable (albeit using a slightly different method than described here) until it was fixed in firmware version 4.06. This vulnerability was also found and exploited by (at least) Chaitin Tech, so props to them! Taking a quick look at the 4.07 kernel, we can see a straightforward fix (4.06 is assumed to be identical - only had 4.07 on hand while writing this post): int sys_namedobj_create(struct thread *td, void *args) { // ... rv = EINVAL; kind = *((_DWORD *)args + 4) if ( !(kind & 0x4000) && *(_QWORD *)args ) { // ... (unchanged) } return rv; } And so we say goodbye to a nice exploit. I hope you enjoyed this blast from the past :) Keep hacking! OpenZFS Developer Summit 2017 Recap (https://www.ixsystems.com/blog/openzfs-devsummit-2017/) The 5th annual OpenZFS Developer Summit was held in San Francisco on October 24-25. Hosted by Delphix at the Children's Creativity Museum in San Francisco, over a hundred OpenZFS contributors from a wide variety of companies attended and collaborated during the conference and developer summit. iXsystems was a Gold sponsor and several iXsystems employees attended the conference, including the entire Technical Documentation Team, the Director of Engineering, the Senior Analyst, a Tier 3 Support Engineer, and a Tier 2 QA Engineer. Day 1 of the conference had 9 highly detailed, informative, and interactive technical presentations from companies which use or contribute to OpenZFS. The presentations highlighted improvements to OpenZFS developed “in-house” at each of these companies, with most improvements looking to be made available to the entire OpenZFS community in the near to long term. There's a lot of exciting stuff happening in the OpenZFS community and this post provides an overview of the presented features and proof-of-concepts. The keynote was delivered by Mark Maybee who spoke about the past, present, and future of ZFS at Oracle. An original ZFS developer, he outlined the history of closed-source ZFS development after Oracle's acquisition of Sun. ZFS has a fascinating history, as the project has evolved over the last decade in both open and closed source forms, independent of one another. While Oracle's proprietary internal version of ZFS has diverged from OpenZFS, it has implemented many of the same features. Mark was very proud of the work his team had accomplished over the years, claiming Oracle's ZFS products have accounted for over a billion dollars in sales and are used in the vast majority of Fortune 100 companies. However, with Oracle aggressively moving into cloud storage, the future of closed source ZFS is uncertain. Mark presented a few ideas to transform ZFS into a mainstream and standard file system, including adding more robust support for Linux. Allan Jude from ScaleEngine talked about ZStandard, a new compression method he is developing in collaboration with Facebook. It offers compression comparable to gzip, but at speeds fast enough to keep up with hard drive bandwidth. According to early testing, it improves both the speed and compression efficiency over the current LZ4 compression algorithm. It also offers a new “dictionary” feature for improving image compression, which is of particular interest to Facebook. In addition, when using ZFS send and receive, it will adapt the compression ratio to make the most efficient use of the network bandwidth. Currently, deleting a clone on ZFS is a time-consuming process, especially when dealing with large datasets that have diverged over time. Sara Hartse from Delphix described how “clone fast delete” speeds up clone deletion. Rather than traversing the entire dataset during clone deletion, changes to the clone are tracked in a “live list” which the delete process uses to determine which blocks to free. In addition, rather than having to wait for the clone to finish, the delete process backgrounds the task so you can keep working without any interruptions. Sara shared the findings of a test they ran on a clone with 500MB of data, which took 45 minutes to delete with the old method, and under a minute using the live list. This behavior is an optional property as it may not be appropriate for long-lived clones where deletion times are not a concern. At this time, it does not support promoted clones. Olaf Faaland from Lawrence Livermore National Labs demonstrated the progress his team has made to improve ZFS pool imports with MMP (Multi-Modifier Protection), a watchdog system to make sure that ZFS pools in clustered High Availability environments are not imported by more than one host at a time. MMP uses uberblocks and other low-level ZFS features to monitor pool import status and otherwise safeguard the import process. MMP adds fields to on-disk metadata so it does not depend on hardware, such as SAS. It supports multi-node HA configs and does not affect non-HA systems. However, it does have issues with long I/O delays so existing HA software is recommended as an additional fallback. Jörgen Lundman of GMO Internet gave an entertaining talk on the trials and tribulations of porting ZFS to OS X. As a bonus, he talked about porting ZFS to Windows, and showed a working demo. While not yet in a usable state, it demonstrated a proof-of-concept of ZFS support for other platforms. Serapheim Dimitropoulos from Delphix discussed Faster Allocation with the Log Spacemap as a means of optimizing ZFS allocation performance. He began with an in-depth overview of metaslabs and how log spacemaps are used to track allocated and freed blocks. Since blocks are only allocated from loaded metaslabs but freed blocks may apply to any metaslab, over time logging the freed blocks to each appropriate metaslab with every txg becomes less efficient. Their solution is to create a pool-wide metaslab for unflushed entries. Shailendra Tripathi from Tegile presented iFlash: Dynamic Adaptive L2ARC Caching. This was an interesting talk on what is required to allow very different classes of resources to share the same flash device–in their case, ZIL, L2ARC, and metadata. To achieve this, they needed to address the following differences for each class: queue priority, metaslab load policy, allocation, and data protection (as cache has no redundancy). Isaac Huang of Intel introduced DRAID, or parity declustered RAID. Once available, this will provide the same levels of redundancy as traditional RAIDZ, providing the administrator doubles the amount of options for providing redundancy for their use case. The goals of DRAID are to address slow resilvering times and the write throughput of a single replacement drive being a bottleneck. This solution skips block pointer tree traversal when rebuilding the pool after drive failure, which is the cause of long resilver times. This means that redundancy is restored quickly, mitigating the risk of losing additional drives before the resilver completes, but it does require a scrub afterwards to confirm data integrity. This solution supports logical spares, which must be defined at vdev creation time, which are used to quickly restore the array. Prakash Surya of Delphix described how ZIL commits currently occur in batches, where waiting threads have to wait for the batch to complete. His proposed solution was to replace batch commits and to instead notify the waiting thread after its ZIL commit in order to greatly increase throughput. A new tunable for the log write block timeout can also be used to log write blocks more efficiently. Overall, the quality of the presentations at the 2017 OpenZFS conference was high. While quite technical, they clearly explained the scope of the problems being addressed and how the proposed solutions worked. We look forward to seeing the described features integrated into OpenZFS. The videos and slides for the presentations should be made available over the next month or so at the OpenZFS website. OpenZFS Photo Album (https://photos.google.com/share/AF1QipNxYQuOm5RDxRgRQ4P8BhtoLDpyCuORKWiLPT0WlvUmZYDdrX3334zu5lvY_sxRBA?key=MW5fR05MdUdPaXFKVDliQVJEb3N3Uy1uMVFFdVdR) DragonflyBSD 5.0 (https://www.dragonflybsd.org/release50/) DragonFly version 5.0 brings the first bootable release of HAMMER2, DragonFly's next generation file system. HAMMER2 Preliminary HAMMER2 support has been released into the wild as-of the 5.0 release. This support is considered EXPERIMENTAL and should generally not yet be used for production machines and important data. The boot loader will support both UFS and HAMMER2 /boot. The installer will still use a UFS /boot even for a HAMMER2 installation because the /boot partition is typically very small and HAMMER2, like HAMMER1, does not instantly free space when files are deleted or replaced. DragonFly 5.0 has single-image HAMMER2 support, with live dedup (for cp's), compression, fast recovery, snapshot, and boot support. HAMMER2 does not yet support multi-volume or clustering, though commands for it exist. Please use non-clustered single images for now. ipfw Updates IPFW has gone through a number of updates in DragonFly and now offers better performance. pf and ipfw3 are also still supported. Improved graphics support The i915 driver has been brought up to match what's in the Linux 4.7.10 kernel. Intel GPUs are supported up to the Kabylake generation. vga_switcheroo(4) module added, allowing the use of Intel GPUs on hybrid-graphics systems. The new apple_gmux driver enables switching to the Intel video chipset on dual Intel/NVIDIA and Intel/Radeon Macbook computers. Other user-affecting changes efisetup(8) added. DragonFly can now support over 900,000 processes on a single machine. Client-side SSH by default does not try password authentication, which is the default behavior in newer versions of OpenSSH. Pass an explicit '-o PasswordAuthentication=yes' or change /etc/ssh/ssh_config if you need the old behavior. Public key users are unaffected. Clang status A starting framework has been added for using clang as the alternate base compiler in DragonFly, to replace gcc 4.7. It's not yet complete. Clang can of course be added as a package. Package updates Many package updates but I think most notably we need to point to chrome60 finally getting into dports with accelerated video and graphics support. 64-bit status Note that DragonFly is a 64-bit-only operating system as of 4.6, and will not run on 32-bit hardware. AMD Ryzen is supported and DragonFly 5.0 has a workaround for a hardware bug (http://lists.dragonflybsd.org/pipermail/commits/2017-August/626190.html). DragonFly quickly released a v5.0.1 with a few patches Download link (https://www.dragonflybsd.org/download/) News Roundup (r)vmadm – managing FreeBSD jails (https://blog.project-fifo.net/rvmadm-managing-freebsd-jails/) We are releasing the first version (0.1.0) of our clone of vmadm for FreeBSD jails today. It is not done or feature complete, but it does provides basic functionality. At this point, we think it would be helpful to get it out there and get some feedback. As of today, it allows basic management of datasets, as well as creating, starting, stopping, and destroying jails. Why another tool to manage jails However, before we go into details let's talk why we build yet another jail manager? It is not the frequent NIH syndrome, actually quite the opposite. In FiFo 0.9.2 we experimented with iocage as a way to control jails. While iocage is a useful tool when used as a CLI utility it has some issues when used programmatically. When managing jails automatically and not via a CLI tool things like performance, or a machine parsable interface matter. While on a CLI it is acceptable if a call takes a second or two, for automatically consuming a tool this delay is problematic. Another reason for the decision was that vmadm is an excellent tool. It is very well designed. SmartOs uses vmadm for years now. Given all that, we opted for adopting a proven interface rather than trying to create a new one. Since we already interface with it on SmartOS, we can reuse a majority of our management code between SmartOS and FreeBSD. What can we do Today we can manage datasets, which are jail templates in the form of ZFS volumes. We can list and serve them from a dataset-server, and fetch those we like want. At this point, we provide datasets for FreeBSD 10.0 to 11.1, but it is very likely that the list will grow. As an idea here is a community-driven list of datasets (https://datasets.at/) that exist for SmartOS today. Moreover, while those datasets will not work, we hope to see the same for BSD jails. After fetching the dataset, we can define jails by using a JSON file. This file is compatible with the zone description used on SmartOS. It does not provide all the same features but a subset. Resources such as CPU and memory can be defined, networking configured, a dataset selected and necessary settings like hostname set. With the jail created, vmadm allows managing its lifetime, starting, stopping it, accessing the console and finally destroying it. Updates to jails are supported to however as of today they are only taken into account after restarting the jail. However, this is in large parts not a technical impossibility but rather wasn't high up on the TODO list. It is worth mentioning that vmadm will not pick up jails created in other tools or manually. Only using vmadm created jails was a conscious decision to prevent it interfering with existing setups or other utilities. While conventional tools can manage jails set up with vmadm just fine we use some special tricks like nested jails to allow for restrictions required for multi-tenancy that are hard or impossible to achieve otherwise. Whats next First and foremost we hope to get some feedback and perhaps community engagement. In the meantime, as announced earlier this year (https://blog.project-fifo.net/fifo-in-2017/), we are hard at work integrating FreeBSD hypervisors in FiFo, and as of writing this, the core actions work quite well. Right now only the barebone functions are supported, some of the output is not as clear as we would like. We hope to eventually add support for behyve to vmadm the same way that it supports KVM on SmartOS. Moreover, the groundwork for this already exists in the nested jail techniques we are using. Other than that we are exploring ways to allow for PCI pass through in jails, something not possible in SmartOS zones right now that would be beneficial for some users. In general, we want to improve compatibility with SmartOS as much as possible and features that we add over time should make the specifications invalid for SmartOS. You can get the tool from github (https://github.com/project-fifo/r-vmadm). *** Parallel processing with unix tools (http://www.pixelbeat.org/docs/unix-parallel-tools.html) There are various ways to use parallel processing in UNIX: piping An often under appreciated idea in the unix pipe model is that the components of the pipe run in parallel. This is a key advantage leveraged when combining simple commands that do "one thing well" split -n, xargs -P, parallel Note programs that are invoked in parallel by these, need to output atomically for each item processed, which the GNU coreutils are careful to do for factor and sha*sum, etc. Generally commands that use stdio for output can be wrapped with the stdbuf -oL command to avoid intermixing lines from parallel invocations make -j Most implementations of make(1) now support the -j option to process targets in parallel. make(1) is generally a higher level tool designed to process disparate tasks and avoid reprocessing already generated targets. For example it is used very effictively when testing coreutils where about 700 tests can be processed in 13 seconds on a 40 core machine. implicit threading This goes against the unix model somewhat and definitely adds internal complexity to those tools. The advantages can be less data copying overhead, and simpler usage, though its use needs to be carefully considered. A disadvantage is that one loses the ability to easily distribute commands to separate systems. Examples are GNU sort(1) and turbo-linecount The example provided counts lines in parallel: The examples below will compare the above methods for implementing multi-processing, for the function of counting lines in a file. First of all let's generate some test data. We use both long and short lines to compare the overhead of the various methods compared to the core cost of the function being performed: $ seq 100000000 > lines.txt # 100M lines $ yes $(yes longline | head -n9) | head -n10000000 > long-lines.txt # 10M lines We'll also define the add() { paste -d+ -s | bc; } helper function to add a list of numbers. Note the following runs were done against cached files, and thus not I/O bound. Therefore we limit the number of processes in parallel to $(nproc), though you would generally benefit to raising that if your jobs are waiting on network or disk etc. + We'll use this command to count lines for most methods, so here is the base non multi-processing performance for comparison: $ time wc -l lines.txt $ time wc -l long-lines.txt split -n Note using -n alone is not enough to parallelize. For example this will run serially with each chunk, because since --filter may write files, the -n pertains to the number of files to split into rather than the number to process in parallel. $ time split -n$(nproc) --filter='wc -l' lines.txt | add You can either run multiple invocations of split in parallel on separate portions of the file like: $ time for i in $(seq $(nproc)); do split -n$i/$(nproc) lines.txt | wc -l& done | add Or split can do parallel mode using round robin on each line, but that's huge overhead in this case. (Note also the -u option significant with -nr): $ time split -nr/$(nproc) --filter='wc -l' lines.txt | add Round robin would only be useful when the processing per item is significant. Parallel isn't well suited to processing a large single file, rather focusing on distributing multiple files to commands. It can't efficiently split to lightweight processing if reading sequentially from pipe: $ time parallel --will-cite --block=200M --pipe 'wc -l' < lines.txt | add Like parallel, xargs is designed to distribute separate files to commands, and with the -P option can do so in parallel. If you have a large file then it may be beneficial to presplit it, which could also help with I/O bottlenecks if the pieces were placed on separate devices: split -d -n l/$(nproc) lines.txt l. Those pieces can then be processed in parallel like: $ time find -maxdepth 1 -name 'l.*' | xargs -P$(nproc) -n1 wc -l | cut -f1 -d' ' | add If your file sizes are unrelated to the number of processors then you will probably want to adjust -n1 to batch together more files to reduce the number of processes run in total. Note you should always specify -n with -P to avoid xargs accumulating too many input items, thus impacting the parallelism of the processes it runs. make(1) is generally used to process disparate tasks, though can be leveraged to provide low level parallel processing on a bunch of files. Note also the make -O option which avoids the need for commands to output their data atomically, letting make do the synchronization. We'll process the presplit files as generated for the xargs example above, and to support that we'll use the following Makefile: %: FORCE # Always run the command @wc -l < $@ FORCE: ; Makefile: ; # Don't include Makefile itself One could generate this and pass to make(1) with the -f option, though we'll keep it as a separate Makefile here for simplicity. This performs very well and matches the performance of xargs. $ time find -name 'l.*' -exec make -j$(nproc) {} + | add Note we use the POSIX specified "find ... -exec ... {} +" construct, rather than conflating the example with xargs. This construct like xargs will pass as many files to make as possible, which make(1) will then process in parallel. OpenBSD gives a hint on forgetting unlock mutex (http://nanxiao.me/en/openbsd-gives-a-hint-on-forgetting-unlock-mutex/) OpenBSD gives a hint on forgetting unlock mutex Check following simple C++ program: > ``` #include int main(void) { std::mutex m; m.lock(); return 0; } ``` The mutex m forgot unlock itself before exiting main function: m.unlock(); Test it on GNU/Linux, and I chose ArchLinux as the testbed: $ uname -a Linux fujitsu-i 4.13.7-1-ARCH #1 SMP PREEMPT Sat Oct 14 20:13:26 CEST 2017 x86_64 GNU/Linux $ clang++ -g -pthread -std=c++11 test_mutex.cpp $ ./a.out $ The process exited normally, and no more words was given. Build and run it on OpenBSD 6.2: clang++ -g -pthread -std=c++11 test_mutex.cpp ./a.out pthread_mutex_destroy on mutex with waiters! The OpenBSD prompts “pthreadmutexdestroy on mutex with waiters!“. Interesting! *** Beastie Bits Updates to the NetBSD operating system since OSHUG #57 & #58 (http://mailman.uk.freebsd.org/pipermail/ukfreebsd/2017-October/014148.html) Creating a jail with FiFo and Digital Ocean (https://blog.project-fifo.net/fifo-jails-digital-ocean/) I'm thinking about OpenBSD again (http://stevenrosenberg.net/blog/bsd/openbsd/2017_0924_openbsd) Kernel ASLR on amd64 (https://blog.netbsd.org/tnf/entry/kernel_aslr_on_amd64) Call for Participation - BSD Devroom at FOSDEM (https://people.freebsd.org/~rodrigo/fosdem18/) BSD Stockholm Meetup (https://www.meetup.com/BSD-Users-Stockholm/) *** Feedback/Questions architect - vBSDCon (http://dpaste.com/15D5SM4#wrap) Brad - Packages and package dependencies (http://dpaste.com/3MENN0X#wrap) Lars - dpb (http://dpaste.com/2SVS18Y) Alex re: PS4 Network Throttling (http://dpaste.com/028BCFA#wrap) ***
In this livecast from the National Association of Broadcasters conference in Las Vegas, Jiri Matela, CEO and Co-Founder of Comprimato discusses new JPEG2000 plugin for Intel® Media Server Studio. Comprimato focuses on high quality video decoding and encoding that is precisely optimized for CPU’s and GPU’s. Intel and Comprimato have teamed up to create the best video encoding technology to date. Jiri highlights how the JPEG2000 plugin will be able to handle 4K, 8K, and high frame rates for HDR by combining the massive power of Intel GPUs and advanced analysis tools that help video solution providers deliver fast, high-density media transcoding. To learn more and get a free demo visit www.comprimato.com
© 2020-2025 Ivy Podcast Discovery LLC
