Podcasts about hdds

This week, we discuss Google being found to be a monopoly, OpenAI's “offer” to buy Chrome, and some hot takes on JSON. Plus, is it better to wait on hold or ask for a callback? Watch the YouTube Live Recording of Episode (https://www.youtube.com/watch?v=EhUxUPJv5g4) 516 (https://www.youtube.com/watch?v=EhUxUPJv5g4) Runner-up Titles Just Fine The SDT “Fine” Scale Callback Asynchronous Friendship I would love to get to know you better…over text Send you Jams to the dry cleaners. JSON Take it xslt-easy! Rundown OpenAI OpenAI in talks to pay about $3 billion to acquire AI coding startup Windsurf (https://www.cnbc.com/2025/04/16/openai-in-talks-to-pay-about-3-billion-to-acquire-startup-windsurf.html) The Cursor Mirage (https://artificialintelligencemadesimple.substack.com/p/the-cursor-mirage) AI is for Tinkerers (https://redmonk.com/kholterhoff/2023/06/27/ai-is-for-tinkerers/) Vibe Coding is for PMs (https://redmonk.com/rstephens/2025/04/18/vibe-coding-is-for-pms/) OpenAI releases new simulated reasoning models with full tool access (https://arstechnica.com/ai/2025/04/openai-releases-new-simulated-reasoning-models-with-full-tool-access/) Clouded Judgement 4.18.25 - The Hidden Value in the AI Application Layer (https://cloudedjudgement.substack.com/p/clouded-judgement-41825-the-hidden?utm_source=post-email-title&publication_id=56878&post_id=161562220&utm_campaign=email-post-title&isFreemail=true&r=2l9&triedRedirect=true&utm_medium=email) OpenAI tells judge it would buy Chrome from Google (https://www.theverge.com/news/653882/openai-chrome-google-us-judge) The Creators of Model Context Protocol (https://www.latent.space/p/mcp?utm_source=substack&utm_medium=email) Judge finds Google holds illegal online ad tech monopolies (https://www.cnbc.com/2025/04/17/judge-finds-google-holds-illegal-online-ad-tech-monopolies.html) Intuit, Owner of TurboTax, Wins Battle Against America's Taxpayers (https://prospect.org/power/2025-04-17-intuit-turbotax-wins-battle-against-taxpayers-irs-direct-file/) Relevant to your Interests Switch 2 Carts Still Taste Bad, Designed Purposefully To Be Spat Out (https://www.gamespot.com/articles/switch-2-carts-still-taste-bad-designed-purposefully-to-be-spat-out/1100-6530649/) CEO Andy Jassy's 2024 Letter to Shareholders (https://www.aboutamazon.com/news/company-news/amazon-ceo-andy-jassy-2024-letter-to-shareholders) Amazon CEO Andy Jassy says AI costs will come down (https://www.cnbc.com/2025/04/10/amazon-ceo-andy-jassys-2025-shareholder-letter.html) Happy 18th Birthday CUDA! (https://www.aboutamazon.com/news/company-news/amazon-ceo-andy-jassy-2024-letter-to-shareholders) Honeycomb Acquires Grit: A Strategic Investment in Pragmatic AI and Customer Value (https://www.honeycomb.io/blog/honeycomb-acquires-grit) Everything Announced at Google Cloud Next in 12 Minutes (https://www.youtube.com/watch?v=2OpHbyN4vEM) GitLab vs GitHub : Key Differences in 2025 (https://spacelift.io/blog/gitlab-vs-github) Old Fashioned Function Keys (https://economistwritingeveryday.com/2025/04/11/old-fashioned-function-keys/) Fake job seekers are flooding U.S. companies that are hiring for remote positions, (https://www.cnbc.com/2025/04/08/fake-job-seekers-use-ai-to-interview-for-remote-jobs-tech-ceos-say.html) NetRise raises $10M to expand software supply chain security platform (https://siliconangle.com/2025/04/15/netrise-raises-10-million-expand-software-supply-chain-security-platform/) Mark Zuckerberg's antitrust testimony aired his wildest ideas from Meta's history (https://www.theverge.com/policy/649520/zuckerberg-meta-ftc-antitrust-testimony-facebook-history) How Much Should I Be Spending On Observability? (https://www.honeycomb.io/blog/how-much-should-i-spend-on-observability-pt1) Did we just make platform engineering much easier by shipping a cloud IDP? (https://seroter.com/2025/04/16/did-we-just-make-platform-engineering-much-easier-by-shipping-a-cloud-idp/) Google Cloud Next 2025: Agentic AI Stack, Multimodality, And Sovereignty (https://www.forrester.com/blogs/google-next-2025-agentic-ai-stack-multimodality-and-sovereignty/) iPhone Shipments Down 9% in China's Q1 Smartphone Boom (https://www.macrumors.com/2025/04/18/iphone-shipments-down-in-china-q1/) Exclusive: Anthropic warns fully AI employees are a year away (https://www.axios.com/2025/04/22/ai-anthropic-virtual-employees-security) Synology requires self-branded drives for some consumer NAS systems, drops full functionality and support for third-party HDDs (https://www.tomshardware.com/pc-components/nas/synology-requires-self-branded-drives-for-some-consumer-nas-systems-drops-full-functionality-and-support-for-third-party-hdds) Porting Tailscale to Plan 9 (https://tailscale.com/blog/plan9-port?ck_subscriber_id=512840665&utm_source=convertkit&utm_medium=email&utm_campaign=[Last%20Week%20in%20AWS]%20Issue%20#418:%20Another%20New%20Capacity%20Dingus%20-%2017270009) CVE Foundation (https://www.thecvefoundation.org/) The Cursor Mirage (https://artificialintelligencemadesimple.substack.com/p/the-cursor-mirage) There's a Lot of Bad Telemetry Out There (https://blog.olly.garden/theres-a-lot-of-bad-telemetry-out-there) Gee Wiz (https://redmonk.com/rstephens/2025/04/04/gee-wiz/?ck_subscriber_id=512840665&utm_source=convertkit&utm_medium=email&utm_campaign=[Last%20Week%20in%20AWS]%20Issue%20#418:%20Another%20New%20Capacity%20Dingus%20-%2017270009) Nonsense Silicon Valley crosswalk buttons hacked to imitate Musk, Zuckerberg's voices (https://techcrunch.com/2025/04/14/silicon-valley-crosswalk-buttons-hacked-to-imitate-musk-zuckerberg-voices/) A Visit to Costco in France (https://davidlebovitz.substack.com/p/a-visit-to-costco-in-france) No sweat: Humanoid robots run a Chinese half-marathon (https://apnews.com/article/china-robot-half-marathon-153c6823bd628625106ed26267874d21) Metre, a consistent measurement of the world (https://mappingignorance.org/2025/04/23/150-years-ago-the-metre-convention-determined-how-we-measure-the-world/) Conferences DevOps Days Atlanta (https://devopsdays.org/events/2025-atlanta/welcome/), April 29th-30th. KCD Texas Austin 2025 (https://community.cncf.io/events/details/cncf-kcd-texas-presents-kcd-texas-austin-2025/), May 15th, Whitney Lee Speaking. Cloud Foundry Day US (https://events.linuxfoundation.org/cloud-foundry-day-north-america/), May 14th, Palo Alto, CA, Coté speaking. Fr (https://vmwarereg.fig-street.com/051325-tanzu-workshop/)ee AI workshop (https://vmwarereg.fig-street.com/051325-tanzu-workshop/), May 13th. day before C (https://events.linuxfoundation.org/cloud-foundry-day-north-america/)loud (https://events.linuxfoundation.org/cloud-foundry-day-north-america/) (https://events.linuxfoundation.org/cloud-foundry-day-north-america/)Foundry (https://events.linuxfoundation.org/cloud-foundry-day-north-america/) Day (https://events.linuxfoundation.org/cloud-foundry-day-north-america/). NDC Oslo (https://ndcoslo.com/), May 21st-23th, Coté speaking. SDT News & Community Join our Slack community (https://softwaredefinedtalk.slack.com/join/shared_invite/zt-1hn55iv5d-UTfN7mVX1D9D5ExRt3ZJYQ#/shared-invite/email) Email the show: questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com) Free stickers: Email your address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) Follow us on social media: Twitter (https://twitter.com/softwaredeftalk), Threads (https://www.threads.net/@softwaredefinedtalk), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com) Watch us on: Twitch (https://www.twitch.tv/sdtpodcast), YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured), Instagram (https://www.instagram.com/softwaredefinedtalk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk) Book offer: Use code SDT for $20 off "Digital WTF" by Coté (https://leanpub.com/digitalwtf/c/sdt) Sponsor the show (https://www.softwaredefinedtalk.com/ads): ads@softwaredefinedtalk.com (mailto:ads@softwaredefinedtalk.com) Recommendations Brandon: Dope Thief (https://www.rottentomatoes.com/tv/dope_thief) on Apple TV (https://www.rottentomatoes.com/tv/dope_thief) Coté: Check out the recording of the Tanzu Annual update (https://www.youtube.com/watch?v=c1QZXzJcAfQ), all about Tanzu's private AI platform. Next, watch Coté's new MCP for D&D video (#4) figures out something cool to do with MCP Prompts (https://www.youtube.com/watch?v=xEtYBznneFg), they make sense now. And, a regret-a-mmendation: Fields Notes annual subscription (https://fieldnotesbrand.com/limited-editions). Photo Credits Header (https://unsplash.com/photos/a-telephone-sitting-on-top-of-a-wooden-shelf-2XnGRN_caHc)

Eight best-selling Mac products that don't exist–yet. Original text by David Pogue, Macworld April 1996. More on the history of DiskDoubler. John V. Holder's TakeABreak has recently been uncovered from the depths of archive.org. A hybrid of the imaginary Concatenator Pro and PocketBoot might be Startup Doubler, which gloms together all your extensions (internally, not on the filesystem) to accelerate startup. Apple sort of tried to make extensions management easier by including Ricardo Batista's Extensions Manager with System 7.5 and later. I've lost track of the number of Uninstaller-type software that's been produced for the Mac since this article was written, not that I would ever touch any of them. MacBreakZ is an awful lot like the imaginary Carpal Diem. From ~2010-2014, I always thought of NexTag as a real-world PriceDex. It's a shame it disappeared. CamelCamelCamel fills the void for those who haven't yet separated themselves from Amazon. Nobody ever went so far as to produce an INIT magazine but Symbionts will give you more technical insight into your System Folder. My all-time favourite feature: a file-by-file breakdown of how much memory is allocated by each INIT and cdev. Things I don't miss about the old days: holding my breath while capturing analog video, and waiting for machines with mechanical HDDs to boot. The PocketBoot would nearly useless today anyhow–not because of SSDs, but because Apple is actively striving to make it impossible to boot from external media. Thanks, Tim Cook! Super useful, good job. All because SECURITY. …except in the UK and everywhere else, shortly. Mmmkay, how about you let us boot from external devices again while you're at it? Better yet, throw out the current version of Mac OS, fork Snow Leopard, and start things over from there, kthxbai Scott Joplin “Maple Leaf Rag” clip courtesy of ConcertWare. PPG Wave 2.3 demo courtesy of RetroSound. More about CANYON.MID, composer George Stone, and how his work ended up shipping with most copies of Windows from 1991-1996. Composed on a Mac running Passport Designs' Master Tracks Pro. Live performance of CANYON.MID…? The canyon.mid Simulator and hard rock cover (pun not intended).

No programa de hoje vamos explorar as principais tendências que estão moldando o futuro do setor tecnológico em 2025. Da formação de profissionais às estratégias para promover empregabilidade e diversidade, o cenário está em plena transformação. Para falar sobre esse assunto eu recebo hoje aqui no Podcast Canaltech a Mariana Lopes, Gerente Executiva do MovTech 2030. E mais: Electronic Arts encerrará app da Origin em 2025; Xbox receberá suporte para HDDs externos com mais de 16 TB; Gemini Live ganha opção para enviar fotos e arquivos durante a conversa; IA vai exigir 2x mais armazenamento nos próximos 3 anos; NVIDIA garante que conector de energia das GeForce RTX 50 não derreterá. Receba notícias do Canaltech no WhatsApp Entre nas redes sociais do Canaltech buscando por @Canaltech nelas todas Entre em contato pelo nosso e-mail: podcast@canaltech.com.br Entre no Canaltech Ofertas Acesse a newsletter do Canaltech Este episódio foi roteirizado e apresentado por Gustavo Minari. O programa também contou com reportagens de Raphael Giannotti, Jones Oliveira e Diego Corumba. Edição por Yuri Souza. A trilha sonora é uma criação de Guilherme Zomer e a capa deste programa é feita por Erick Teixeira.See omnystudio.com/listener for privacy information.

Today we are talking all about STORAGE! Well - at least some of it - we are talking about HDDs. Hard Disk Drive storage. We also talk a little bit about the hierarchy of storage and volatile and non-volatile storage! Make sure to check our previous part of this episode about CPUs and GPUs if you missed that because we will be putting all this together at the end in an ultimate comparison of Mac v/s Windows =) Here's the hierarchy I mentioned in the podcast: Stage A - Cache Storage [THE FASTEST - TINIEST STORAGE] Stage B - Cache Storage [VERY VERY FAST - TINY STORAGE] Stage C - Cache Storage [ VERY FAST - SMALL STORAGE] Stage D - RAM [FAST - BIGGER STORAGE] Stage E - HDD/SSD [ STILL FAST, BUT NOT AS MUCH - TONS OF STORAGE] All of these are very fast to the point that you may not notice if a data packet is stored in Stage A, or D, but they are still faster than the previous one! (It's a matter of miliseconds and seconds) Sources: https://www.youtube.com/watch?v=wteUW2sL7bc&t=3s https://www.youtube.com/watch?v=wtdnatmVdIg&t=3s Also bleeds into the other Episodes sources.

Ficha técnica Hosts: Leticia Dáquer e Thiago Corrêa  Edição: Leticia Dáquer Capa: Leticia Dáquer Data da gravação: 20/10/2024 Data da publicação: 24/10/2024   Músicas/áudios: The Oldest Song in the World The Most Mysterious Song on the Internet - HQ Stereo Remastered   Coisas mencionadas no episódio: Episódio do Stuff You Should Know sobre mistérios da internet, incluindo a música desconhecida Música da bunda do Bosch A música mais misteriosa da internet (Wikipedia) But what is CRISPR-Cas9? An animated introduction to Gene Editing   Bom Leticia World-first therapy using donor cells sends autoimmune diseases into remission (Nature, 04/10/2024) Discovering Roman mosaics - A fabulous new find where history meets luxury in Antakya (World Archeology, 18/11/2020) Thiago Ouça a música mais antiga do mundo, de 3.400 anos (Olhar Digital, 29/07/2024) World's first ‘meltdown-proof' nuclear reactor aces safety test (New Atlas, 24/07/2024) Brazilian artist swaps historical coin in British Museum for a fake (The Guardian, 22/07/2024)   Mau Leticia Políticos de cidade alemã querem restringir venda de kebab (Carta Capital, 12/08/2024) Thiago  Music industry's 1990s hard drives, like all HDDs, are dying (12/09/2024)   Feio Leticia State-of-the-Art Fire Station Leveled by Blaze (Newsweek, 18/10/2024) Woman passes her driving test on her 960th go after spending £11,000 (The Mirror, 26/03/2023) Comandante de navio dos EUA é rebaixado após atirar com a mira ao contrário (UOL, 04/09/2024) Engenheira mantém 7,4 mil abas abertas no Firefox há mais de dois anos (Terra, 07/05/2024) Two San Francisco nudists save man from being attacked in street by a "crazy kind of pirate guy"with a blowtorch (MSN, 07/2024) Thiago Alemanha vai parar de usar disquetes em navios de guerra (Tecnoblog, 07/2024) MS-DOS and Windows 3.11 still run train dashboards at German railway — company listed admin job for 30-year-old operating system (Tom's Hardware, 29/01/2024) Math student builds fusion reactor at home with help from Claude AI and $2,000 (Techspot, 03/09/2024) Restaurant sues customer over $3,000 waitress tip he left on $13 meal (Unilad, 01/07/2024) Maldives minister arrested for performing ‘black magic' on President Muizzu: Report (Hindustan Times, 28/06/2024)   Parceria com Veste Esquerda: Agora tem camiseta do Pistolando direto no site da Veste Esquerda! Mas o código de desconto PISTOLA10 dá 10% de desconto na sua compra da nossa e de outras camisetas maneiríssimas esquerdopatas!   Parceria com Editora Boitempo: compre livros por esse link aqui pra gente ganhar uns trocados de comissão :)   Nosso link de associados da Amazon, mas só em último caso, hein: bit.ly/Pistolando    Parceria com o ICL: inscreva-se nos cursos pelo nosso link   Esse podcast é produzido pelo Estopim Podcasts. Precisa de ajuda pra fazer o seu podcast? Chega mais, que a gente te dá uma mãozinha.     Links do Pistolando www.pistolando.com contato@pistolando.com Twitter: @PistolandoPod Instagram: @PistolandoPod   Apóie o Pistolando no Catarse, no Patreon e agora também no PicPay, ou faça um Pix pra gente usando a chave contato@pistolando.com   Descrição da capa:  

In this episode, we starting a series about the computer and how it works! In this episode we are going to give a brief overview on all the parts in the computer before delving deep into each part in the coming episodes. I will be alternating between publishing an episode in this series with some other episodes as to not frizzle your brains. Please do consider sharing this podcast with others if you find it enjoyable! Sources - I will be referring to these sources in later episodes as well. My Sources https://www.youtube.com/watch?v=1kypaBjJ-pg https://www.youtube.com/watch?v=Axd50ew4pco https://www.youtube.com/watch?v=6LIv2ocJXRk https://www.youtube.com/watch?v=6LIv2ocJXRk https://www.youtube.com/watch?v=OdziYWEkDIM https://www.youtube.com/watch?v=ExxFxD4OSZ0 Sources from ChatGPT (I didn't use it's response, I asked it for sources. It gave me these) CPU (Central Processing Unit): Intel's Guide to CPUs:⁠https://www.intel.com/content/www/us/en/products/processors/what-is-a-processor.html⁠ How CPUs Work - HowStuffWorks:⁠https://computer.howstuffworks.com/microprocessor.htm⁠ GPU (Graphics Processing Unit): How GPUs Work - TechSpot:⁠https://www.techspot.com/article/1871-how-gpus-work/⁠ RAM (Random Access Memory): HowStuffWorks: RAM Explained:⁠https://computer.howstuffworks.com/ram.htm⁠ Storage (HDD and SSD): Seagate's Guide to HDDs and SSDs:⁠https://www.seagate.com/gb/en/internal-hard-drives/⁠ Motherboard: PCGuide: Motherboards:⁠https://www.pcguide.com/motherboard/guide/⁠ Power Supply Unit (PSU): How Power Supplies Work - TechSpot:⁠https://www.techspot.com/article/2024-how-power-supplies-work/⁠

We're on Patreon now! Find us at https://www.patreon.com/AudioUnleashed This week, Brent and Dennis discuss the death of music hard drives (and the inevitable doom of all music recordings?); riff on a  cut'n'paste review of a Coherence Systems… something or other, and worry whether a podcast they created about the Harman target curve using A.I. might actually be better than … well, not Audio Unleashed, of course, but much of what passes for audio journalism. Buy-now links for products mentioned herein (As Amazon Associates, we may earn a small cut from qualifying purchases):

Today, the hard disk drive industry and its big three companies - Seagate, Western Digital and Toshiba - are in decline. The Solid State Drive or SSD is on the rise. SSDs are faster, more reliable, and consume less power. Something that began 30 years ago with replacing audio tapes in telephone answering machines - remember those? - has grown to power a $60 billion market per the IEEE. HDD unit volume sales will never be as they were before. Consumers no longer buy HDDs for their iPods, laptops or even desktops. Sad. But the HDD's march towards oblivion has been arrested by a new market: Growing demand from enterprise companies storing data for "nearline" storage. Nearline, referring to data that the customer needs accessible but not so frequently nor immediately. This market is real. Companies in all sorts of fields are producing data at a far faster rate than they can afford to store it.

Today, the hard disk drive industry and its big three companies - Seagate, Western Digital and Toshiba - are in decline. The Solid State Drive or SSD is on the rise. SSDs are faster, more reliable, and consume less power. Something that began 30 years ago with replacing audio tapes in telephone answering machines - remember those? - has grown to power a $60 billion market per the IEEE. HDD unit volume sales will never be as they were before. Consumers no longer buy HDDs for their iPods, laptops or even desktops. Sad. But the HDD's march towards oblivion has been arrested by a new market: Growing demand from enterprise companies storing data for "nearline" storage. Nearline, referring to data that the customer needs accessible but not so frequently nor immediately. This market is real. Companies in all sorts of fields are producing data at a far faster rate than they can afford to store it.

La bolletta dei datacenter per l'IA. La deriva dei modelli LLM. Trenitalia fa retromarcia sui check-in. Sequestro nel mondo del retrogaming. Queste e molte altre le notizie tech commentate nella puntata di questa settimana.Dallo studio distribuito di digitalia:Franco Solerio, Francesco Facconi, Giulio CupiniProduttori esecutivi:Nicola Gabriele Del Popolo, Simone Podico, Alessandro Stevanin, Nicola Grilli, Andrea Nicola Vasile, Roberto A., Daniele Bastianelli, Giovanni Priolo, Raffaele Marco Della Monica, Gabriele Di Lorenzo, Andrea Guido, @Jh4Ckal, Michele Olivieri, Luca Ubiali, Letizia Calcinai, Idle Fellow, Michele Levada, Enrico Carangi, Davide Capra, Donato Gravino, Paolo Bernardini, Christophe Sollami, Davide Tinti, Giuliano Arcinotti, Gianluca Denaci, Michele Francesco Falzarano, Diego Arati, Nicola Fort, Nicola Gabriele Del Popolo, Antonio Taurisano, Manuel Zavatta, Renato Battistin, Michelangelo Rocchetti, @Tiumeito, Matteo Tarabini, Simone Andreozzi, Arzigogolo, Guido Raffaele Piras, Vincenzo Ingenito, Denis Grosso, Alessio Ferrara, Emanuele Libori, Angelo Merendi, Raffaele Viero, Roberto Medeossi, Ftrava, Carlo Tomas, Andrea Picotti, @Ppogo, Marco Grechi, Calogero Augusta, Mario Cervai, Andrea Giovacchini, Anonimo Esse, Paolo Tegoni, @Akagrinta, Alessandro Morgantini, Mario GiammonaSponsor:Squarespace.com - utilizzate il codice coupon "DIGITALIA" per avere il 10% di sconto sul costo del primo acquisto.Links:AI execs meet with White House to talk AI energy and data centersOracle's data center would be powered by 3 small nuclear reactorsWhite House gets commitments from AI companies to curb deepfake pornLLMs are getting dumber and we have no idea whyModel collapse threatens to kill progress on generative AIsMeta scraped every Australian user's account to train its AIFord seeks patent for tech that listens to driver conversations to serve adsEveryone says Chrome devastates Mac battery life but does it?Trenitalia eliminerà il check-in per i treni regionaliUnity is Canceling the Runtime FeeMark Zuckerbergs 20-year mistakeFlappy Bird is finally returning 10 years after its demiseRetrogaming operazione Coin up 80: 12 mila console piratate sequestrateFake retro videogame ring worth 50m smashed in ItalySequestrate migliaia di console: preinstallati milioni di videogiochi piratatiMusic industrys 1990s hard drives like all HDDs are dyingM-DISC - WikipediaApple threatened to move Will Smith movie out of LouisianaGingilli del giorno:eHammurabi - A digital version of the Law Code of Hammurabi, including cuneiform, transliteration, normalization, and an English translation.Commentari degli IncaAnimated Knot ListSupporta Digitalia, diventa produttore esecutivo.

Gaiman & Good Omens; Waymo means Uber drivers are cooked; local muggers; EU not messing around with Apple, Google; DOJ after Google as well; another genetic testing company with security breach disasters; META scraping Australian users' accounts to train AI; banning social media for children; AI to determine unemployment benefits; Lower Decks; Hope Solo vs US Soccer; Alan Cumming; the Perfect Couple; KAOS; Tears for Fears; FruitJuice; iPhone 16 pre-ordering process; AirPods Pro 2 as hearing aids; Flipper Zero; AI Audible narrators; Google AI Notebook podcast generation; RIP, James Earl Jones; Disneyland's Club 33; Overcast follow up; parcopresis & the politics of pooping.Sponsors:DeleteMe - Head over to JoinDeleteMe.com/GOG and use the code "GOG" for 20% off.1Password - Get a great deal on the only password manager recommended by Grumpy Old Geeks! gog.show/1passwordPrivate Internet Access - Go to GOG.Show/vpn and sign up today. For a limited time only, you can get OUR favorite VPN for as little as $2.03 a month.SetApp - With a single monthly subscription you get 240+ apps for your Mac. Go to SetApp and get started today!!!Show notes at https://gog.show/665/FOLLOW UPDashaun Wesley & LE SSERAPHIM on InstagramGood Omens Season 3 Reportedly Paused Amid Neil Gaiman ControversyReport: Neil Gaiman May Step Back From Good Omens‘ Final SeasonWhat do Uber drivers make of Waymo? 'We are cooked'Human drivers keep rear-ending WaymosWaymo Safety ImpactIN THE NEWSApple ordered to pay back its illegal $14.4 billion Irish tax breakGoogle loses its seven-year fight against $2.7 billion EU antitrust fineDOJ claims Google has “trifecta of monopolies” on Day 1 of ad tech trialGoogle Teams With the Internet Archive to Revive Cache FeatureGenetic Testing Company Must Issue Refunds After Security Breach DisasterMeta scraped every Australian user's account to train its AIAustralia's Prime Minister wants to ban social media for childrenGoogle's AI Will Help Decide Whether Unemployed Workers Get BenefitsUtah judge blocks law preventing youth from accessing social media freelyMEDIA CANDYStar Trek: Lower Decks Is Back One Last Time With a Swashbuckling New ClipUntold: Hope Solo vs US SoccerAlan Cumming Wins Best Host Emmy for ‘The Traitors,' Ending RuPaul's Eight-Year StreakThe Perfect CoupleKAOSThe Penguin | Official Trailer | MaxSalem's Lot | Official Trailer | MaxTears for Fears Announce First Live Album Songs for a Nervous Planet, Reveal New Song “The Girl That I Call Home”: StreamTears for Fears Announce First Live Album Songs for a Nervous Planet, Reveal New Song “The Girl That I Call Home”: StreamAPPS & DOODADSFruitJuiceApple just got authorization for AirPods Pro 2's hearing aid featureMeet the first major release of Flipper Zero firmware — version 1.0.Audible narrators to create voice replicas using AIGoogle's AI notebook can generate a podcast about your notesMan Used Fake Rock Camera to Film 1,000 Women Bathing in Hot SpringsMusic industry's 1990s hard drives, like all HDDs, are dyingTHE DARK SIDE WITH DAVEDave BittnerThe CyberWireHacking HumansCaveatControl LoopOnly Malware in the BuildingJames Earl Jones, Distinguished Actor and Voice of Darth Vader, Dies at 93“It's a Cult, and Walt's the Messiah”: Meet the Couple Who Sued Disney Over Secretive Club 33Can't Poop at Work? Why Public Bathrooms Give Us AnxietySee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

In this episode of the Tech Talks Daily Podcast, we are joined by Roger Corell, Senior Director of AI and Leadership Marketing at Solidigm. Roger brings his extensive expertise to discuss the transformative role of solid-state drives (SSDs) in enabling artificial intelligence (AI) and enterprise workloads. With a new product launch on the horizon, Roger provides an inside look at how Solidigm is pushing the boundaries of storage technology. Solidigm, a leading provider of NAND flash memory solutions, offers one of the most comprehensive portfolios of enterprise SSDs. These solutions are designed to accelerate workloads, including AI, from the core to the edge, unlocking unprecedented performance while lowering costs and scaling efficiently. Solidigm's commitment to quality and reliability is evident through its rigorous testing and validation processes, ensuring their SSDs meet the highest industry standards. Roger highlights the critical importance of storage for AI applications. As AI models and datasets grow exponentially, the need for fast, dense, and power-efficient storage solutions becomes paramount. SSDs offer significant advantages over traditional hard disk drives (HDDs), including vastly superior speed, density, and energy efficiency. Solidigm's SSDs, particularly the upcoming PCIe Gen 5 D7 series, are engineered to deliver industry-leading performance across all metrics, making them ideal for demanding AI workloads. The conversation also delves into Solidigm's customer-centric approach. Roger explains how Solidigm collaborates closely with enterprise and cloud customers to optimize firmware and testing for real-world conditions. This collaborative effort not only accelerates time-to-market for their solutions but also ensures that the SSDs perform optimally in practical applications, beyond just peak specifications. Roger shares compelling examples of the real-world impact of Solidigm's SSDs. For instance, one hyperscaler was able to cut AI data preparation time by a factor of 50 by switching from HDDs to Solidigm SSDs. Similarly, OCIENT reported significant energy reductions in AI and HPC workloads using Solidigm's QLCSSDs. These examples underscore the tangible benefits that advanced SSD technology can bring to AI and other high-performance computing environments. Looking ahead, Solidigm is poised to sustain its leadership in high-capacity and high-performance SSDs, with plans to introduce next-generation drives exceeding 61TB. The company is also investing in edge data processing capabilities, recognizing the growing importance of data gravity in the AI landscape. By maintaining performance leadership, Solidigm aims to maximize the utilization of costly GPU servers, which are critical for AI training and inference. Join us for this enlightening episode as Roger Corell provides a detailed overview of how SSDs are revolutionizing AI and enterprise workloads. How is your organization leveraging advanced storage solutions to enhance its AI capabilities? Share your thoughts and join the conversation!  

The Personal Computer Show Wednesday July 31st 2024 PRN.live Streaming on the Internet 6:00 PM Eastern Time IN THE NEWS  USPS Shared Customer Postal Addresses with Meta, LinkedIn and Snap  Passwords Disappear for Millions of Windows Users Thanks to Google Microsoft says EU rules Made CrowdStrike Outage Possible  Astronauts Stuck in Space by Malfunctioning Boeing Spacecraft  Charter Loses 393,000 Video Subs in Second Quarter ITPro Series with Benjamin Rockwell  Is it Right to Use AI in Our Jobs? From the Tech Corner  How to Revive Your Broken USB Flash Drive  A History of HDDs and SSDs Technology Chatter with Benjamin Rockwell and Marty Winston  OWC Envoy Pro Mini, Gourmia Espresso Maker 

You didn't ask for it, but here it is. The greatest PC Perspective podcast ever recorded on March 27, 2024. China bans things, FSR 3.1, DirectSR, and EVGA PSU wiring ... Other topics below.Oh, and sorry this is posted late this week!Timestamps:00:00 Intro01:01 Food with Josh03:14 AMD announced FSR 3.1 at GDC08:10 Radeon 7900 GRE gets memory OC unlocked12:05 China bans AMD, Intel, and Windows from Government PCs17:24 ASUS launching NUC 14 Pro20:50 Microsoft DirectSR revealed25:23 EVGA PSU RMA fries HDDs, company makes it right29:09 TrueNAS Core bids goodbye to FreeBSD33:16 (in)Security Corner48:49 Gaming Quick Hits59:36 ECS LIVA Z5 PLUS review1:04:38 Picks of the Week1:14:43 Outro ★ Support this podcast on Patreon ★

In this episode, Chris chats to Rick Kutcipal, "At-Large Director" with the SCSI Trade Association. The topic of conversation is the adoption of SAS media (both HDDs and SSDs) by hyper-scale customers that include public cloud vendors and companies such as Meta.

In dieser Podcast-Folge beschäftigen wir uns mit unserem Workflow nach einem Fotoshooting. Wir tauschen Erfahrungen aus und diskutieren, wie wir effizient mit der Nachbearbeitung umgehen. Zu Beginn schildern wir unsere individuellen Herangehensweisen, wenn wir von einem Shooting zurückkommen. Dabei betonen wir die Bedeutung der Dateisicherung und teilen unsere persönlichen Routinen. Wir diskutieren die Vor- und Nachteile von verschiedenen Speichermedien wie HDDs und SSDs. Insta Max: https://www.instagram.com/_max_moments_/ Insta Tim: https://www.instagram.com/tim_goger/ Website Max: [https://max-moments.de/](https://max-moments.de/) Website Tim: [https://www.timgoger.de/](https://www.timgoger.de/)

Chuck provides a briefing on the function and benefits of the OWC Drive Dock from Other World Computing. Connection, operation, and some suggested use cases are included, as well as recommendations on drive naming and bare drive storage when not in use in the Drive Dock.    Show Notes: Chapters: 0:00:00 Introduction to the OWC Drive Dock and its capabilities0:00:27 Overview of the controls and indicators on the OWC Drive Dock0:01:37 Connectivity and usage instructions for the OWC Drive Dock0:02:34 Performance and recommended usage scenarios for the OWC Drive Dock0:03:14 Personal testimonial and additional use cases for the OWC Drive Dock0:04:07 Tips for naming and storing bare drives0:05:25 Pricing and where to purchase the OWC Drive Dock and protective cases0:06:06 Conclusion and recommendation for the OWC Drive Dock Links: OWC Drive Dockhttps://eshop.macsales.com/item/OWC/TCDRVDCK/ OWC Drive Dock (Amazon)https://amzn.to/48fJ5QD Inateck 3.5 Inch Hard Drive Case HDD Protective Box with Shockproof Dustproof and Anti-static Function, Storage Case for 3.5 inch HDDs https://amzn.to/470ZGGX ORICO 5-Pack Hard Drive Case Protective Box for 3.5/2.5 Inch SSD HDD Portable with Anti-Static,Shockproof and Dust Proof Travel Storage https://amzn.to/3TkI4T6 Support:      Become a MacVoices Patron on Patreon     http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:     http://macvoices.com      Twitter:     http://www.twitter.com/chuckjoiner     http://www.twitter.com/macvoices      Mastodon:     https://mastodon.cloud/@chuckjoiner      Facebook:     http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:     http://www.facebook.com/macvoices/      MacVoices Group on Facebook:     http://www.facebook.com/groups/macvoice      LinkedIn:     https://www.linkedin.com/in/chuckjoiner/      Instagram:     https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes     Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Chuck provides a briefing on the function and benefits of the OWC Drive Dock from Other World Computing. Connection, operation, and some suggested use cases are included, as well as recommendations on drive naming and bare drive storage when not in use in the Drive Dock.    Show Notes: Chapters: 0:00:00 Introduction to the OWC Drive Dock and its capabilities 0:00:27 Overview of the controls and indicators on the OWC Drive Dock 0:01:37 Connectivity and usage instructions for the OWC Drive Dock 0:02:34 Performance and recommended usage scenarios for the OWC Drive Dock 0:03:14 Personal testimonial and additional use cases for the OWC Drive Dock 0:04:07 Tips for naming and storing bare drives 0:05:25 Pricing and where to purchase the OWC Drive Dock and protective cases 0:06:06 Conclusion and recommendation for the OWC Drive Dock Links: OWC Drive Dock https://eshop.macsales.com/item/OWC/TCDRVDCK/ OWC Drive Dock (Amazon) https://amzn.to/48fJ5QD Inateck 3.5 Inch Hard Drive Case HDD Protective Box with Shockproof Dustproof and Anti-static Function, Storage Case for 3.5 inch HDDs https://amzn.to/470ZGGX ORICO 5-Pack Hard Drive Case Protective Box for 3.5/2.5 Inch SSD HDD Portable with Anti-Static,Shockproof and Dust Proof Travel Storage https://amzn.to/3TkI4T6 Support:      Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:      http://macvoices.com      Twitter:      http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices      Mastodon:      https://mastodon.cloud/@chuckjoiner      Facebook:      http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:      http://www.facebook.com/macvoices/      MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice      LinkedIn:      https://www.linkedin.com/in/chuckjoiner/      Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss 00:00:00 Introduction to the OWC Drive Dock and its capabilities 00:00:26 Overview of the controls and indicators on the OWC Drive Dock 00:01:37 Connectivity and usage instructions for the OWC Drive Dock 00:02:33 Performance and recommended usage scenarios for the OWC Drive Dock 00:03:14 Personal testimonial and additional use cases for the OWC Drive Dock 00:04:07 Tips for naming and storing bare drives 00:05:24 Pricing and where to purchase the OWC Drive Dock and protective cases 00:06:06 Conclusion and recommendation for the OWC Drive Dock

Brian invited Seagate’s Colin Presly to the podcast this week to discuss research and… The post Podcast #124: The Path to 50TB HDDs with Frickin Lasers appeared first on StorageReview.com.

No episódio de hoje falaremos sobre o o game Ratchet And Clank que saiu para pc e aceitando hdds, ao contrário do que a Sony disse. #ratchetandclank #sony #ps5 #ps4 #seliga #playstation #top #mentira #mancada #sacanagem

WD disks “warning” that they have been running for 3 years, a modern replacement for IMAP that no one seems to be using, the potential issues that arise when PC games require an SSD to run, alternatives to VMware, and verifying your backups.   News/discussion “Clearly predatory”: Western Digital sparks panic, anger for age-shaming HDDs […]

On this show show Synology, Unihertz, Samsung Galaxy S23 FE, 5G Splicing, Anker Prime, JCB Toughphone and Pixel Fold and Tablet mused over by Gareth and Ted. With Gareth Myles and Ted Salmon Join us on Mewe RSS Link: https://techaddicts.libsyn.com/rss Direct Download iTunes | Google Podcasts | Stitcher | Tunein | Spotify  Amazon | Pocket Casts | Castbox | PodHubUK   Feedback, Fallout and Contributions Synology DS923+ Hardline on the hardware Western Digital hopes to release HAMR drives within the next 18 Months Are website builders dying out? Latest stats show a worrying trend Nokia is introducing a novel new way to make your Android phone faster Unihertz Jelly Star: Smallest Android 13 smartphone arrives with performance  Vodafone and Three Mega-Merger Samsung Galaxy S23 FE to launch in select markets in Q3 2023 Pixel Fold ship dates are getting delayed, slipping into July Pixel Tablet review: Uniquely Google, made possible by Android – The Pixel Tablet's new Google Weather app is gorgeous Anker Prime chargers and power banks on the way Samsung brings its self-repair program to the UK Your NFC payments could soon be truly contactless JCB Toughphone and Toughphone Max announced First Rugged Android Tablets With Heated Screens Launched The Name of the Game Pour one out for HDDs because PC games are starting to require SSDs The Light in the Darkness review – a sobering free educational game that confronts the Holocaust Steam gets a huge free update on PC, and it's good news for Steam Deck too EA Games is dead, long live EA Entertainment and EA Sports Flap your trap about an App Made by Google – YouTube  EU regulator orders Google to sell part of ad-tech business Google Domains shutting down, assets sold and being migrated to Squarespace Microsoft tests Windows Ink upgrade that lets you write anywhere you can type Your next job interview could be with AI instead of a person DuckDuckGo now has its own PC browser for keeping what you do online private Google Gallows & Chrome Coroner Google Photos on the web delivers robust editing tools exclusively for Google One subscribers A first look at the Google Password Manager Chromebook app YouTube Transcript Extractor Chrome Extension Chrome can soon convert PDFs into text it can read aloud This is ‘Chromebook X': Google's new standard for ChromeOS – Now ChromeBook Plus Hark Back The Trusty old Joystick Bargain Basement: Best UK deals and tech on sale we have spotted TP-Link Tapo Smart Plug with Energy Monitoring – Now £17.99 Was: £27.99 RØDE Podcaster Dynamic USB Microphone £119 from £149 Samsung SSD 870 EVO, 4 TB – £219.98 £75 cashback from Samsung Logitech Page of Deals at AmazonUK Get Microsoft Office and Windows 11 Pro at a huge discount Motorola Edge 30 Ultra 256GB/12GB £629 from £749 Amazon Basics Monitor Hub Arm Mount Aluminize Silver – £49.15 Main Show URL: http://www.techaddicts.uk | PodHubUK Contact:: gareth@techaddicts.uk | @techaddictsuk Gareth – @garethmyles | Mastodon | garethmyles.com | Gareth's Ko-Fi Ted – tedsalmon.com | Ted's PayPal | Mastodon | Ted's Amazon | tedsalmon@post.com Ricky – @RickysTechTalk | Rickys Tech Talk Youtube | rickystechtalk.com YouTube: Tech Addicts

Notícias que chamaram a nossa atenção nesta quinta-feira-feira dia 11 de maio de 2023! Reprodução em áudio do e-mail recebido diariamente pela Newsletters (newsletter@filipedeschamps.com) Newsletter gratuita sobre Tecnologia e Programação: https://filipedeschamps.com.br/newsletter #news #noticias #fdnews #robsonamendonca

We discuss the latest AMD RDNA 3, Intel CPU Architecture, and Nvidia Blackwell news! [SPON: dieshrink = 3% off Everything, brokensilicon = 25% off Windows: https://biitt.ly/shbSk ] [SPON: Get 6% OFF Custom PCs & GPUs at https://www.silverknightpcs.com/ w/ “brokensilicon”] [SPON: Get 10% off Tasty Vite Ramen with code BROKENSILICON: https://bit.ly/3wKx6v1 ] 0:00 Intel Codenames Galore, Content Overload (Intro Banter) 5:23 Nintendo's "Lateral Thinking", HDDs vs Tape Drives (Corrections) 16:21 AMD AM5 CPU Burning Issues Investigated 29:44 AdoredTV Leaks “Ladder L3” for Zen 5, DigiTimes confirms MLID Leaks 42:17 RX 7600 8GB targeting below 300 Leak, Navi 33 Recap 1:00:06 AMD Q1 2023 Earnings 1:09:57 Intel Q1 2023 Earnings 1:17:55 Intel 14th Gen Raptor Lake-R, Meteor Lake Ultra, and Arrow Lake Leaked 1:43:13 Adamantine, Dragon Range-X vs Meteor Lake, AMD Complacency 1:50:16 Nvidia Blackwell Delay Rumors - 3nm Woes, or Ampere Oversupply? 2:01:55 MS-Activision Blocked, Phoenix Z1 Extreme, RX 7950 XTX (Wrap-Up) 2:09:00 RDNA 4 VRAM, Broken Silicon 1, MLID Channel Goals (Final Reader Mail) https://www.techpowerup.com/301867/seagate-mechanical-hdd-with-u-2-nvme-interface-pictured-signals-the-decline-of-sas-12g https://youtu.be/kiTngvvD5dI https://youtu.be/3FDh9C59Z1A https://www.hardwaretimes.com/amd-ryzen-8000-cpus-to-be-based-on-4nm-node-not-3nm-5th-gen-epyc-to-get-3nm-rumor/ https://www.digitimes.com.tw/tech/dt/n/shwnws.asp?CnlID=1&Cat=40&id=0000662749_VR76FCFB51XKH38BW2VPS https://www.youtube.com/live/umJQXe5haa0?feature=share&t=736 https://www.newegg.com/sapphire-radeon-rx-6700-11321-02-20g/p/N82E16814202424?Description=RX%206700&cm_re=RX_6700-_-14-202-424-_-Product&quicklink=true https://twitter.com/mooreslawisdead/status/1651351480094408706 https://twitter.com/mooreslawisdead/status/1651489123528581120 https://community.amd.com/t5/gaming/game-beyond-4gb/ba-p/414776 https://ir.amd.com/news-events/press-releases/detail/1128/amd-reports-first-quarter-2023-financial-results https://www.anandtech.com/show/18845/amd-reports-q1-2023-earnings-back-into-the-red-as-client-sales-crumble https://youtu.be/Qa-ZAyQOviY https://www.anandtech.com/show/18839/intel-reports-q1-2023-earnings-a-record-losing-quarter-goes-better-than-expected https://wccftech.com/intel-announces-layoffs-after-paying-1-5-billion-in-q1-dividends/ https://youtu.be/GhLMbFgVfbY https://www.digitimes.com.tw/tech/dt/n/shwnws.asp?CnlID=1&Cat=40&id=0000662749_VR76FCFB51XKH38BW2VPS https://wccftech.com/nvidia-next-gen-3nm-gpus-not-launching-until-2025-tsmc-report/ https://youtu.be/8PVYOeHx8vA https://www.reuters.com/markets/deals/uk-blocks-microsoft-69-bln-activision-deal-over-cloud-gaming-concerns-2023-04-26/ https://www.techspot.com/news/98578-microsoft-might-partnering-amd-ai-chips.html https://videocardz.com/newz/nvidia-forces-msi-to-unlaunch-geforce-rtx-3060-ti-super-3x-series-after-just-one-week https://twitter.com/Kepler_L2/status/1651341246055497732 https://videocardz.com/press-release/amd-announces-ryzen-z1-zen4-apus-for-handheld-gaming-consoles-with-up-to-12-rdna3-gpu-cores https://videocardz.com/newz/amd-introduces-ryzen-7040u-phoenix-low-power-apus-with-up-to-8-zen4-cores-and-12-rdna3-cus https://videocardz.com/newz/nvidia-geforce-rtx-4060-ti-ad106-350-gpu-has-been-pictured https://www.techspot.com/news/98550-amd-confirms-mainstream-rdna-3-gpus-before-summer.html https://twitter.com/Bernard_P/status/1653022115367645190?s=20&fbclid=IwAR29SiFCOdRzQ-QmbSJWpOALAa8-GrqZREXxzD72LT_Iif_eRsYvACP7_uM

Dr. Doug talks: The Tang Dynasty, ZippyShare, NuGet, PinDuoDuo, Ernie, Lantern, HDD hard drives, and more on this edition of the Security Weekly News!   Visit https://www.securityweekly.com/swn for all the latest episodes! Show Notes: https://securityweekly.com/swn282  Follow us on Twitter: https://www.twitter.com/securityweekly Like us on Facebook: https://www.facebook.com/secweekly 

Dr. Doug talks: The Tang Dynasty, ZippyShare, NuGet, PinDuoDuo, Ernie, Lantern, HDD hard drives, and more on this edition of the Security Weekly News!   Visit https://www.securityweekly.com/swn for all the latest episodes! Show Notes: https://securityweekly.com/swn282

Dr. Doug talks: The Tang Dynasty, ZippyShare, NuGet, PinDuoDuo, Ernie, Lantern, HDD hard drives, and more on this edition of the Security Weekly News!   Visit https://www.securityweekly.com/swn for all the latest episodes! Show Notes: https://securityweekly.com/swn282  Follow us on Twitter: https://www.twitter.com/securityweekly Like us on Facebook: https://www.facebook.com/secweekly 

Dr. Doug talks: The Tang Dynasty, ZippyShare, NuGet, PinDuoDuo, Ernie, Lantern, HDD hard drives, and more on this edition of the Security Weekly News!   Visit https://www.securityweekly.com/swn for all the latest episodes! Show Notes: https://securityweekly.com/swn282

Join Mats Oberg, Associate Vice President, DSP Architecture and podcast host Chris Banuelos on this week's episode, discussing the heart of hard disk drive (HDD) controller design -- Marvell's read channel technology. Learn about the challenges of data storage as data continues its explosive growth, future technologies shaping HDD controller design, and what is next for HDDs. Be sure to check out our other recent podcast episode 24 “Scaling HDD Capacity in the Data Center” to learn more.

A solid-state drive (SSD) is a solid-state storage device that uses integrated circuit assemblies to store data persistently, typically using flash memory, and functioning as secondary storage in the hierarchy of computer storage.[1] It is also sometimes called a semiconductor storage device, a solid-state device or a solid-state disk,[2] even though SSDs lack the physical spinning disks and movable read–write heads used in hard disk drives (HDDs) and floppy disks.[3] SSD also has rich internal parallelism for data processing.[4] Twitter Instagram Mack's channel Intro music by Dan Mason

In this episode, Chris is joined by Phison CTO Sebastien Jean to discuss the transition from HDD to SSD. As pricing for the two media types comes close to reaching parity, this conversation looks at how the two media are evolving and how NAND flash SSDs are set to become the de facto choice for the enterprise data centre. The transition to an all-flash data centre has been predicted for some time, however end game could be on the horizon as soon as 2025 or 2026. The Phison blog discussed by Sebastien can be found here - https://phisonblog.com/ Elapsed Time: 00:44:01 Timeline 00:00:00 - Intros 00:02:45 - Predictions of the death of the hard drive are overdone 00:04:15 - Enterprise SSD prices continue to drop - but don't HDDs do that too? 00:05:30 - 2020 was the cutover year for units produced (SSD vs HDD) 00:06:45 - HDD capacity growth has slowed 00:07:50 - SSD growth is being achieved with 3D techniques 00:09:15 - Floors could be used to increase layer count 00:11:00 - Latency is increasing in newer flash designs 00:13:05 - What is the “acceptable” limit for SSD capacity? 00:14:15 - Dense SSDs will be the norm with NVMe connectivity 00:15:30 - New form factors will drive greater drive capacities 00:17:00 - Is $/GB too simple a measure? 00:19:40 - SSD rebuilds are quick, avoiding the need for RAID-6 00:20:45 - SSD failure is not predictable 00:25:00 - Are HDD shipping costs relevant? 00:26:30 - How are the hyper-scalers using HDDs and driving change? 00:29:15 - Where do we go next - PLC? 00:32:00 - Could an entire SSD be dynamic between SLC and QLC? 00:35:45 - What about new technology Optane 4.0 or MRAM? 00:40:30 - Look out for CXL-enabled SSDs 00:42:40 - 2Tb NAND dies will bring HDD parity Copyright (c) 2016-2022 Unpacked Network. No reproduction or re-use without permission. Podcast episode #34ee.

Brian catches up with Broadcom’s Rick Kutcipal for this session. Rick is a Product… The post Podcast #112: Why HDDs Aren’t Going Away appeared first on StorageReview.com.

About ThomasThomas Hazel is Founder, CTO, and Chief Scientist of ChaosSearch. He is a serial entrepreneur at the forefront of communication, virtualization, and database technology and the inventor of ChaosSearch's patented IP. Thomas has also patented several other technologies in the areas of distributed algorithms, virtualization and database science. He holds a Bachelor of Science in Computer Science from University of New Hampshire, Hall of Fame Alumni Inductee, and founded both student & professional chapters of the Association for Computing Machinery (ACM).Links Referenced: ChaosSearch: https://www.chaossearch.io/ Twitter: https://twitter.com/ChaosSearch Facebook: https://www.facebook.com/CHAOSSEARCH/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by our friends at AWS AppConfig. Engineers love to solve, and occasionally create, problems. But not when it's an on-call fire-drill at 4 in the morning. Software problems should drive innovation and collaboration, NOT stress, and sleeplessness, and threats of violence. That's why so many developers are realizing the value of AWS AppConfig Feature Flags. Feature Flags let developers push code to production, but hide that that feature from customers so that the developers can release their feature when it's ready. This practice allows for safe, fast, and convenient software development. You can seamlessly incorporate AppConfig Feature Flags into your AWS or cloud environment and ship your Features with excitement, not trepidation and fear. To get started, go to snark.cloud/appconfig. That's snark.cloud/appconfig.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. This promoted episode is brought to us by our returning sponsor and friend, ChaosSearch. And once again, the fine folks at ChaosSearch has seen fit to basically subject their CTO and Founder, Thomas Hazel, to my slings and arrows. Thomas, thank you for joining me. It feels like it's been a hot minute since we last caught up.Thomas: Yeah, Corey. Great to be on the program again, then. I think it's been almost a year. So, I look forward to these. They're fun, they're interesting, and you know, always a good time.Corey: It's always fun to just take a look at companies' web pages in the Wayback Machine, archive.org, where you can see snapshots of them at various points in time. Usually, it feels like this is either used for long-gone things and people want to remember the internet of yesteryear, or alternately to deliver sick burns with retorting a “This you,” when someone winds up making an unpopular statement. One of the approaches I like to use it for, which is significantly less nefarious—usually—is looking back in time at companies' websites, just to see how the positioning of the product evolves over time.And ChaosSearch has had an interesting evolution in that direction. But before we get into that, assuming that there might actually be people listening who do not know the intimate details of exactly what it is you folks do, what is ChaosSearch, and what might you folks do?Thomas: Yeah, well said, and I look forward to [laugh] doing the Wayback Time because some of our ideas, way back when, seemed crazy, but now they make a lot of sense. So, what ChaosSearch is all about is transforming customers' cloud object stores like Amazon S3 into an analytical database that supports search and SQL-type use cases. Now, where's that apply? In log analytics, observability, security, security data lakes, operational data, particularly at scale, where you just stream your data into your data lake, connect our service, our SaaS service, to that lake and automagically we index it and provide well-known APIs like Elasticsearch and integrate with Kibana or Grafana, and SQL APIs, something like, say, a Superset or Tableau or Looker into your data. So, you stream it in and you get analytics out. And the key thing is the time-cost complexity that we all know that operational data, particularly at scale, like terabytes and a day and up causes challenges, and we all know how much it costs.Corey: They certainly do. One of the things that I found interesting is that, as I've mentioned before, when I do consulting work at The Duckbill Group, we have absolutely no partners in the entire space. That includes AWS, incidentally. But it was easy in the beginning because I was well aware of what you folks were up to, and it was great when there was a use case that matched of you're spending an awful lot of money on Elasticsearch; consider perhaps migrating some of that—if it makes sense—to ChaosSearch. Ironically, when you started sponsoring some of my nonsense, that conversation got slightly trickier where I had to disclose, yeah our media arm is does have sponsorships going on with them, but that has no bearing on what I'm saying.And if they take their sponsorships away—please don't—then we would still be recommending them because it's the right answer, and it's what we would use if we were in your position. We receive no kickbacks or partner deal or any sort of reseller arrangement because it just clouds the whole conflict of interest perception. But you folks have been fantastic for a long time in a bunch of different ways.Thomas: Well, you know, I would say that what you thought made a lot of sense made a lot of sense to us as well. So, the ChaosSearch idea just makes sense. Now, you had to crack some code, solve some problems, invent some technology, and create some new architecture, but the idea that Elasticsearch is a useful solution with all the tooling, the visualization, the wonderful community around that, was a good place to start, but here's the problem: setting it up, scaling it out, keep it up, when things are happening, things go bump in the night. All those are real challenges, and one of them was just the storaging of the data. Well, what if you could make S3 the back-end store? One hundred percent; no SSDs or HDDs. Makes a lot of sense.And then support the APIs that your tooling uses. So, it just made a lot of sense on what we were trying to do, just no one thought of it. Now, if you think about the Northstar you were talking about, you know, five, six years ago, when I said, transforming cloud storage into an analytical database for search and SQL, people thought that was crazy and mad. Well, now everyone's using Cloud Storage, everyone's using S3 as a data lake. That's not in question anymore.But it was a question five, six, you know, years ago. So, when we met up, you're like, “Well, that makes sense.” It always made sense, but people either didn't think was possible, or were worried, you know, I'll just try to set up an Elastic cluster and deal with it. Because that's what happens when you particularly deal with large-scale implementations. So, you know, to us, we would love the Elastic API, the tooling around it, but what we all know is the cost, the time the complexity, to manage it, to scale it out, just almost want to pull your hair out. And so, that's where we come in is, don't change what you do, just change how you do it.Corey: Every once in a while, I'll talk to a client who's running an Amazon Elasticsearch cluster, and they have nothing but good things to say about it. Which, awesome. On the one hand, part of me wishes that I had some of their secrets, but often what's happened is that they have this down to a science, they have a data lifecycle that's clearly defined and implemented, the cluster is relatively static, so resizes aren't really a thing, and it just works for their use cases. And in those scenarios, like, “Do you care about the bill?” “Not overly. We don't have to think about it.”Great. Then why change? If there's no pain, you're not going to sell someone something, especially when we're talking, this tends to be relatively smaller-scale as well. It's okay, great, they're spending $5,000 a month on it. It doesn't necessarily justify the engineering effort to move off.Now, when you start looking at this, and, “Huh, that's a quarter million bucks a month we're spending on this nonsense, and it goes down all the time,” yeah, that's when it starts to be one of those logical areas to start picking apart and diving into. What's also muddied the waters since the last time we really went in-depth on any of this was it used to be we would be talking about it exactly like we are right now, about how it's Elasticsearch-compatible. Technically, these days, we probably shouldn't be saying it is OpenSearch compatible because of the trademark issues between Elastic and AWS and the Schism of the OpenSearch fork of the Elasticsearch project. And now it feels like when you start putting random words in front of the word search, ChaosSearch fits right in. It feels like your star is rising.Thomas: Yeah, no, well said. I appreciate that. You know, it's funny when Elastic changed our license, we all didn't know what was going to happen. We knew something was going to happen, but we didn't know what was going to happen. And Amazon, I say ironically, or, more importantly, decided they'll take up the open mantle of keeping an open, free solution.Now, obviously, they recommend running that in their cloud. Fair enough. But I would say we don't hear as much Elastic replacement, as much as OpenSearch replacement with our solution because of all the benefits that we talked about. Because the trigger points for when folks have an issue with the OpenSearch or Elastic stack is got too expensive, or it was changing so much and it was falling over, or the complexity of the schema changing, or all the above. The pipelines were complex, particularly at scale.That's both for Elasticsearch, as well as OpenSearch. And so, to us, we want either to win, but we want to be the replacement because, you know, at scale is where we shine. But we have seen a real trend where we see less Elasticsearch and more OpenSearch because the community is worried about the rules that were changed, right? You see it day in, day out, where you have a community that was built around open and fair and free, and because of business models not working or the big bad so-and-so is taking advantage of it better, there's a license change. And that's a trust change.And to us, we're following the OpenSearch path because it's still open. The 600-pound gorilla or 900-pound gorilla of Amazon. But they really held the mantle, saying, “We're going to stay open, we assume for as long as we know, and we'll follow that path. But again, at that scale, the time, the costs, we're here to help solve those problems.” Again, whether it's on Amazon or, you know, Google et cetera.Corey: I want to go back to what I mentioned at the start of this with the Wayback Machine and looking at how things wound up unfolding in the fullness of time. The first time that it snapshotted your site was way back in the year 2018, which—Thomas: Nice. [laugh].Corey: Some of us may remember, and at that point, like, I wasn't doing any work with you, and later in time I would make fun of you folks for this, but back then your brand name was in all caps, so I would periodically say things like this episode is sponsored by our friends at [loudly] CHAOSSEARCH.Thomas: [laugh].Corey: And once you stopped capitalizing it and that had faded from the common awareness, it just started to look like I had the inability to control the volume of my own voice. Which, fair, but generally not mid-sentence. So, I remember those early days, but the positioning of it was, “The future of log management and analytics,” back in 2018. Skipping forward a year later, you changed this because apparently in 2019, the future was already here. And you were talking about, “Log search analytics, purpose-built for Amazon S3. Store everything, ask anything all on your Amazon S3.”Which is awesome. You were still—unfortunately—going by the all caps thing, but by 2020, that wound up changing somewhat significantly. You were at that point, talking for it as, “The data platform for scalable log analytics.” Okay, it's clearly heading in a log direction, and that made a whole bunch of sense. And now today, you are, “The data lake platform for analytics at scale.” So, good for you, first off. You found a voice?Thomas: [laugh]. Well, you know, it's funny, as a product mining person—I'll take my marketing hat off—we've been building the same solution with the same value points and benefits as we mentioned earlier, but the market resonates with different terminology. When we said something like, “Transforming your Cloud Object Storage like S3 into an analytical database,” people were just were like, blown away. Is that even possible? Right? And so, that got some eyes.Corey: Oh, anything is a database if you hold that wrong. Absolutely.Thomas: [laugh]. Yeah, yeah. And then you're saying log analytics really resonated for a few years. Data platform, you know, is more broader because we do more broader things. And now we see over the last few years, observability, right? How do you fit in the observability viewpoint, the stack where log analytics is one aspect to it?Some of our customers use Grafana on us for that lens, and then for the analysis, alerting, dashboarding. You can say that Kibana in the hunting aspect, the log aspects. So, you know, to us, we're going to put a message out there that resonates with what we're hearing from our customers. For instance, we hear things like, “I need a security data lake. I need that. I need to stream all my data. I need to have all the data because what happens today that now, I need to know a week, two weeks, 90 days.”We constantly hear, “I need at least 90 days forensics on that data.” And it happens time and time again. We hear in the observability stack where, “Hey, I love Datadog, but I can't afford it more than a week or two.” Well, that's where we come in. And we either replace Datadog for the use cases that we support, or we're auxiliary to it.Sometimes we have an existing Grafana implementation, and then they store data in us for the long tail. That could be the scenario. So, to us, the message is around what resonates with our customers, but in the end, it's operational data, whether you want to call it observability, log analytics, security analytics, like the data lake, to us, it's just access to your data, all your data, all the time, and supporting the APIs and the tooling that you're using. And so, to me, it's the same product, but the market changes with messaging and requirements. And this is why we always felt that having a search and SQL platform is so key because what you'll see in Elastic or OpenSearch is, “Well, I only support the Elastic API. I can't do correlations. I can't do this. I can't do that. I'm going to move it over to say, maybe Athena but not so much. Maybe a Snowflake or something else.”Corey: “Well, Thomas, it's very simple. Once you learn our own purpose-built, domain-specific language, specifically for our product, well, why are you still sitting here, go learn that thing.” People aren't going to do that.Thomas: And that's what we hear. It was funny, I won't say what the company was, a big banking company that we're talking to, and we hear time and time again, “I only want to do it via the Elastic tooling,” or, “I only want to do it via the BI tooling.” I hear it time and time again. Both of these people are in the same company.Corey: And that's legitimate as well because there's a bunch of pre-existing processes pointing at things and we're not going to change 200 different applications in their data model just because you want to replace a back-end system. I also want to correct myself. I was one tab behind. This year's branding is slightly different: “Search and analyze unlimited log data in your cloud object storage.” Which is, I really like the evolution on this.Thomas: Yeah, yeah. And I love it. And what was interesting is the moving, the setting up, the doubling of your costs, let's say you have—I mean, we deal with some big customers that have petabytes of data; doubling your petabytes, that means, if your Elastic environment is costing you tens of millions and then you put into Snowflake, that's also going to be tens of millions. And with a solution like ours, you have really cost-effective storage, right? Your cloud storage, it's secure, it's reliable, it's Elastic, and you attach Chaos to get the well-known APIs that your well-known tooling can analyze.So, to us, our evolution has been really being the end viewpoint where we started early, where the search and SQL isn't here today—and you know, in the future, we'll be coming out with more ML type tooling—but we have two sides: we have the operational, security, observability. And a lot of the business side wants access to that data as well. Maybe it's app data that they need to do analysis on their shopping cart website, for instance.Corey: The thing that I find curious is, the entire space has been iterating forward on trying to define observability, generally, as whatever people are already trying to sell in many cases. And that has seemed to be a bit of a stumbling block for a lot of folks. I figured this out somewhat recently because I've built the—free for everyone to use—the lasttweetinaws.com, Twitter threading client.That's deployed to 20 different AWS regions because it's go—the idea is that should be snappy for people, no matter where they happen to be on the planet, and I use it for conferences when I travel, so great, let's get ahead of it. But that also means I've got 20 different sources of logs. And given that it's an omnibus Lambda function, it's very hard to correlate that to users, or user sessions, or even figure out where it's going. The problem I've had is, “Oh, well, this seems like something I could instrument to spray logs somewhere pretty easily, but I don't want to instrument it for 15 different observability vendors. Why don't I just use otel—or Open Telemetry—and then tell that to throw whatever I care about to various vendors and do a bit of a bake-off?” The problem, of course, is that open telemetry and Lambda seem to be in just the absolute wrong directions. A lot.Thomas: So, we see the same trend of otel coming out, and you know, this is another API that I'm sure we're going to go all-in on because it's getting more and more talked about. I won't say it's the standard that I think is trending to all your points about I need to normalize a process. But as you mentioned, we also need to correlate across the data. And this is where, you know, there are times where search and hunting and alerting is awesome and wonderful and solves all your needs, and sometimes correlation. Imagine trying to denormalize all those logs, set up a pipeline, put it into some database, or just do a SELECT *, you know, join this to that to that, and get your answers.And so, I think both OpenTelemetry and SQL and search all need to be played into one solution, or at least one capability because if you're not doing that, you're creating some hodgepodge pipeline to move it around and ultimately get your questions answered. And if it takes weeks—maybe even months, depending on the scale—you may sometimes not choose to do it.Corey: One other aspect that has always annoyed me about more or less every analytics company out there—and you folks are no exception to this—is the idea of charging per gigabyte ingested because that inherently sets up a weird dichotomy of, well, this is costing a lot, so I should strive to log less. And that is sort of the exact opposite, not just of the direction you folks want customers to go in, but also where customers themselves should be going in. Where you diverge from an awful lot of those other companies because of the nature of how you work, is that you don't charge them again for retention. And the idea that, yeah, the fact that anything stored in ChaosSearch lives in your own S3 buckets, you can set your own lifecycle policies and do whatever you want to do with that is a phenomenal benefit, just because I've always had a dim view of short-lived retention periods around logs, especially around things like audit logs. And these days, I would consider getting rid of audit logging data and application logging data—especially if there's a correlation story—any sooner than three years feels like borderline malpractice.Thomas: [laugh]. We—how many times—I mean, we've heard it time and time again is, “I don't have access to that data because it was too costly.” No one says they don't want the data. They just can't afford the data. And one of the key premises that if you don't have all the data, you're at risk, particularly in security—I mean, even audits. I mean, so many times our customers ask us, you know, “Hey, what was this going on? What was that go on?” And because we can so cost-effectively monitor our own service, we can provide that information for them. And we hear this time and time again.And retention is not a very sexy aspect, but it's so crucial. Anytime you look in problems with X solution or Y solution, it's the cost of the data. And this is something that we wanted to address, officially. And why do we make it so cost-effective and free after you ingest it was because we were using cloud storage. And it was just a great place to land the data cost-effective, securely.Now, with that said, there are two types of companies I've seen. Everybody needs at least 90 days. I see time and time again. Sure, maybe daily, in a weeks, they do a lot of their operation, but 90 days is where it lands. But there's also a bunch of companies that need it for years, for compliance, for audit reasons.And imagine trying to rehydrate, trying to rebuild—we have one customer—again I won't say who—has two petabytes of data that they rehydrate when they need it. And they say it's a nightmare. And it's growing. What if you just had it always alive, always accessible? Now, as we move from search to SQL, there are use cases where in the log world, they just want to pay upfront, fixed fee, this many dollars per terabyte, but as we get into the more ad hoc side of it, more and more folks are asking for, “Can I pay per query?”And so, you'll see coming out soon, about scenarios where we have a different pricing model. For logs, typically, you want to pay very consistent, you know, predetermined cost structure, but in the case of more security data lakes, where you want to go in the past and not really pay for something until you use it, that's going to be an option as well coming out soon. So, I would say you need both in the pricing models, but you need the data to have either side, right?Corey: This episode is sponsored in part by our friends at ChaosSearch. You could run Elasticsearch or Elastic Cloud—or OpenSearch as they're calling it now—or a self-hosted ELK stack. But why? ChaosSearch gives you the same API you've come to know and tolerate, along with unlimited data retention and no data movement. Just throw your data into S3 and proceed from there as you would expect. This is great for IT operations folks, for app performance monitoring, cybersecurity. If you're using Elasticsearch, consider not running Elasticsearch. They're also available now in the AWS marketplace if you'd prefer not to go direct and have half of whatever you pay them count towards your EDB commitment. Discover what companies like Equifax, Armor Security, and Blackboard already have. To learn more, visit chaossearch.io and tell them I sent you just so you can see them facepalm, yet again.Corey: You'd like to hope. I mean, you could always theoretically wind up just pulling what Ubiquiti apparently did—where this came out in an indictment that was unsealed against an insider—but apparently one of their employees wound up attempting to extort them—which again, that's not their fault, to be clear—but what came out was that this person then wound up setting the CloudTrail audit log retention to one day, so there were no logs available. And then as a customer, I got an email from them saying there was no evidence that any customer data had been accessed. I mean, yeah, if you want, like, the world's most horrifyingly devilish best practice, go ahead and set your log retention to nothing, and then you too can confidently state that you have no evidence of anything untoward happening.Contrast this with what AWS did when there was a vulnerability reported in AWS Glue. Their analysis of it stated explicitly, “We have looked at our audit logs going back to the launch of the service and have conclusively proven that the only time this has ever happened was in the security researcher who reported the vulnerability to us, in their own account.” Yeah, one of those statements breeds an awful lot of confidence. The other one makes me think that you're basically being run by clowns.Thomas: You know what? CloudTrail is such a crucial—particularly Amazon, right—crucial service because of that, we see time and time again. And the challenge of CloudTrail is that storing a long period of time is costly and the messiness the JSON complexity, every company struggles with it. And this is how uniquely—how we represent information, we can model it in all its permutations—but the key thing is we can store it forever, or you can store forever. And time and time again, CloudTrail is a key aspect to correlate—to your question—correlate this happened to that. Or do an audit on two years ago, this happened.And I got to tell you, to all our listeners out there, please store your CloudTrail data—ideally in ChaosSearch—because you're going to need it. Everyone always needs that. And I know it's hard. CloudTrail data is messy, nested JSON data that can explode; I get it. You know, there's tricks to do it manually, although quite painful. But CloudTrail, every one of our customers is indexing with us in CloudTrail because of stories like that, as well as the correlation across what maybe their application log data is saying.Corey: I really have never regretted having extra logs lying around, especially with, to be very direct, the almost ridiculously inexpensive storage classes that S3 offers, especially since you can wind up having some of the offline retrieval stuff as part of a lifecycle policy now with intelligent tiering. I'm a big believer in just—again—the Glacier Deep Archive I've at the cost of $1,000 a month per petabyte, with admittedly up to 12 hours of calling that as a latency. But that's still, for audit logs and stuff like that, why would I ever want to delete things ever again?Thomas: You're exactly right. And we have a bunch of customers that do exactly that. And we automate the entire process with you. Obviously, it's your S3 account, but we can manage across those tiers. And it's just to a point where, why wouldn't you? It's so cost-effective.And the moments where you don't have that information, you're at risk, whether it's internal audits, or you're providing a service for somebody, it's critical data. With CloudTrail, it's critical data. And if you're not storing it and if you're not making it accessible through some tool like an Elastic API or Chaos, it's not worth it. I think, to your point about your story, it's epically not worth it.Corey: It's really not. It's one of those areas where that is not a place to overly cost optimize. This is—I mean we talked earlier about my business and perceptions of conflict of interest. There's a reason that I only ever charge fixed-fee and not percentage of savings or whatnot because, at some point, I'll be placed in a position of having to say nonsense, like, “Do you really need all of these backups?” That doesn't make sense at that point.I do point out things like you have hourly disk snapshots of your entire web fleet, which has no irreplaceable data on them dating back five years. Maybe cleaning some of that up might be the right answer. The happy answer is somewhere in between those two, and it's a business decision around exactly where that line lies. But I'm a believer in never regretting having kept logs almost into perpetuity. Until and unless I start getting more or less pillaged by some particularly rapacious vendor that's oh, yeah, we're going to charge you not just for ingest, but also for retention. And for how long you want to keep it, we're going to treat it like we're carving it into platinum tablets. No. Stop that.Thomas: [laugh]. Well, you know, it's funny, when we first came out, we were hearing stories that vendors were telling customers why they didn't need their data, to your point, like, “Oh, you don't need that,” or, “Don't worry about that.” And time and time again, they said, “Well, turns out we didn't need that.” You know, “Oh, don't index all your data because you just know what you know.” And the problem is that life doesn't work out that way business doesn't work out that way.And now what I see in the market is everyone's got tiering scenarios, but the accessibility of that data takes some time to get access to. And these are all workarounds and bandaids to what fundamentally is if you design an architecture and a solution is such a way, maybe it's just always hot; maybe it's just always available. Now, we talked about tiering off to something very, very cheap, then it's like virtually free. But you know, our solution was, whether it's ultra warm, or this tiering that takes hours to rehydrate—hours—no one wants to live in that world, right? They just want to say, “Hey, on this date on this year, what was happening? And let me go look, and I want to do it now.”And it has to be part of the exact same system that I was using already. I didn't have to call up IT to say, “Hey, can you rehydrate this?” Or, “Can I go back to the archive and look at it?” Although I guess we're talking about archiving with your website, viewing from days of old, I think that's kind of funny. I should do that more often myself.Corey: I really wish that more companies would put themselves in the customers' shoes. And for what it's worth, periodically, I've spoken to a number of very happy ChaosSearch customers. I haven't spoken to any angry ones yet, which tells me you're either terrific at crisis comms, or the product itself functions as intended. So, either way, excellent job. Now, which team of yours is doing that excellent job, of course, is going to depend on which one of those outcomes it is. But I'm pretty good at ferreting out stories on those things.Thomas: Well, you know, it's funny, being a company that's driven by customer ask, it's so easy build what the customer wants. And so, we really take every input of what the customer needs and wants—now, there are cases where we relace Splunk. They're the Cadillac, they have all the bells and whistles, and there's times where we'll say, “Listen, that's not what we're going to do. We're going to solve these problems in this vector.” But they always keep on asking, right? You know, “I want this, I want that.”But most of the feedback we get is exactly what we should be building. People need their answers and how they get it. It's really helped us grow as a company, grow as a product. And I will say ever since we went live now many, many years ago, all our roadmap—other than our Northstar of transforming cloud storage into a search SQL big data analytics database has been customer-driven, market customer-driven, like what our customer is asking for, whether it's observability and integrating with Grafana and Kibana or, you know, security data lakes. It's just a huge theme that we're going to make sure that we provide a solution that meets those needs.So, I love when customers ask for stuff because the product just gets better. I mean, yeah, sometimes you have to have a thick skin, like, “Why don't you have this?” Or, “Why don't you have that?” Or we have customers—and not to complain about customers; I love our customers—but they sometimes do crazy things that we have to help them on crazy-ify. [laugh]. I'll leave it at that. But customers do silly things and you have to help them out. I hope they remember that, so when they ask for a feature that maybe takes a month to make available, they're patient with us.Corey: We sure can hope. I really want to thank you for taking so much time to once again suffer all of my criticisms, slings and arrows, blithe market observations, et cetera, et cetera. If people want to learn more, where's the best place to find you?Thomas: Well, of course, chaossearch.io. There's tons of material about what we do, use cases, case studies; we just published a big case study with Equifax recently. We're in Gartner and a whole bunch of Hype Cycles that you can pull down to see how we fit in the market.Reach out to us. You can set up a trial, kick the tires, again, on your cloud storage like S3. And ChaosSearch on Twitter, we have a Facebook, we have all this classic social medias. But our website is really where all the good content and whether you want to learn about the architecture and how we've done it, and use cases; people who want to say, “Hey, I have a problem. How do you solve it? How do I learn more?”Corey: And we will, of course, put links to that in the show notes. For my own purposes, you could also just search for the term ChaosSearch in your email inbox and find one of their sponsored ads in my newsletter and click that link, but that's a little self-serving as we do it. I'm kidding. I'm kidding. There's no need to do that. That is not how we ever evaluate these things. But it is funny to tell that story. Thomas, thank you so much for your time. As always, it's appreciated.Thomas: Corey Quinn, I truly enjoyed this time. And I look forward to upcoming re:Invent. I'm assuming it's going to be live like last year, and this is where we have a lot of fun with the community.Corey: Oh, I have no doubt that we're about to go through that particular path very soon. Thank you. It's been an absolute pleasure.Thomas: Thank you.Corey: Thomas Hazel, CTO and Founder of ChaosSearch. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry, insulting comment that I will then set to have a retention period of one day, and then go on to claim that I have received no negative feedback.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

New Google Privacy app; iOS 16 Safety Check & security; Storage: Floppy disks, SSDs or HDDs?; Smartphone hidden features; Improve signal strength; LEGO sets retiring; Ring Nation; Sci-Fi streaming; Netflix Top Ten

Once again Chris is joined by Rick Kutcipal, board member with the SCSI Trade Association. It's been four years since episode #74 when Rick provided an update on SAS 24Gb. This time, Rick has details of new features in 24Gb+. What does the "plus" mean in this context? While the bus speed may not be increasing, new features (+) are continually being added to the SAS protocol, hence the additional designation. In this episode, Rick discusses some interesting enhancements to drive management, mainly driven by the demands of hyper-scalers. These include Command Duration Limits, Format with Presets and Logical Depopulation. There are also additional features still in discussion that may yet be added in future releases. To learn more about the work of the SCSI Trade Association, hop over to www.scsita.org, or of course, simply listen to our next podcast after Flash Memory Summit 2023. Elapsed Time: 00:00:24:19 Timeline 00:00:00 - Intros 00:01:45 - How has the SCSI/SAS standard evolved? 00:03:00 - There's no need (currently) to go faster than 24Gb 00:03:50 - What features keep SAS relevant in the market? 00:05:35 - Hyper-scalers are driving the use of HDDs and SAS 00:06:50 - What's new in 24Gb+? 00:09:45 - Enterprise customers will use new features (driven by hyper-scalers) 00:10:15 - What is Command Duration Limits (CDL)? 00:11:25 - What is Format with Presets? 00:13:25 - What is Logical Depopulation? 00:17:30 - Drive failure is a part of “normal” operations 00:17:50 - What features are under consideration? 00:20:15 - How will 24Gb+ features be rolled out? 00:22:30 - Wrap Up Related Podcasts & Blogs #74 - All About Serial Attached SCSI with Rick Kutcipal #161 - Seagate MACH.2 Dual Actuator Drive Deep Dive #174 - Introduction to Zoned Storage with Phil Bullinger Copyright (c) 2016-2022 Storage Unpacked. No reproduction or re-use without permission. Podcast episode #fveh.

Today's MSP Dispatch covers the Patagonia CEO giving away his $3Bn Company, the recent Zoom outage that affected thousands of users and Lorenz Ransomware Leverages Vulnerable VoIP. Additionally, learn why SSDs are more reliable than HDDs and details on the newest Windows Terminal Preview 1.16 release. MSP Dispatch is your source for news, community events, and commentary in the MSP channel.  Hosted by: Tony Francisco and Ray Orsini Give us your feedback by emailing news@mspmedia.tv   0:00 Intro 3:09 Patagonia CEO Gives Away $3Bn Company 8:02 Zoom Outage Affects Thousands 12:39 Lorenz Ransomware Leverages Vulnerable VoIP 18:06 Notable Mentions 20:26 Feedback 22:12 Community Events 23:05 Sign-off 24:25 Outtakes Story Links: Patagonia CEO Gives Away $3Bn Companyhttps://www.edie.net/patagonia-to-redistribute-profits-to-environmental-and-social-causes/https://unofficialnetworks.com/2022/09/14/patagonia-founder-gives-away-company-2/Zoom Outage Affects Thousandshttps://www.crn.com/news/cloud/zoom-outage-hits-tens-of-thousands-of-usersLorenz Ransomware Leverages Vulnerable VoIPhttps://www.darkreading.com/vulnerabilities-threats/lorenz-ransomware-smbs-mitel-voip-phone-systemsSSDs More Reliable Than HDDshttps://arstechnica.com/gadgets/2022/09/five-years-of-data-show-that-ssds-are-more-reliable-than-hdds-over-the-long-haul/Windows Terminal Preview 1.16 Releasehttps://devblogs.microsoft.com/commandline/windows-terminal-preview-1-16-release/ Check out yesterday's MSP Dispatch Special Report: SuperOps Marketing Efforts https://www.youtube.com/watch?v=s4kb1bSI-RY Community Events: 9/16 - 9/18 @ In Person Event | Techcon Unplugged: Chicago, IL9/20 @ 10:00 am ET | MSP Dispatch Presented by The MSP Media Network9/22 - 9/24 In Person Event | Big Big Conference 2022: Hollywood, FL9/23 @ 10:00 am ET | MSP Dispatch Week Wrap Up Presented by The MSP Media Network9/23 @ 11:00 am ET | September Channel Pitch Presented by The Channel Program Connect with our hosts:  - Tony Francisco: https://www.linkedin.com/in/tonyjfrancisco/ - Ray Orsini: https://www.linkedin.com/in/rayorsini/ Be sure to follow us on social media:  Facebook: https://www.facebook.com/mspmediatv/ Twitter: https://twitter.com/mspmediatv LinkedIn: https://www.linkedin.com/company/mspmediatv/ Instagram: https://www.instagram.com/mspmediatv   Reddit: https://www.reddit.com/r/mspmedia Discord: https://discord.gg/Hc7b55cJPF

Today's MSP Dispatch covers the Patagonia CEO giving away his $3Bn Company, the recent Zoom outage that affected thousands of users and Lorenz Ransomware Leverages Vulnerable VoIP. Additionally, learn why SSDs are more reliable than HDDs and details on the newest Windows Terminal Preview 1.16 release. MSP Dispatch is your source for news, community events, and commentary in the MSP channel.  Hosted by: Tony Francisco and Ray Orsini Give us your feedback by emailing news@mspmedia.tv   0:00 Intro 3:09 Patagonia CEO Gives Away $3Bn Company 8:02 Zoom Outage Affects Thousands 12:39 Lorenz Ransomware Leverages Vulnerable VoIP 18:06 Notable Mentions 20:26 Feedback 22:12 Community Events 23:05 Sign-off 24:25 Outtakes Story Links: Patagonia CEO Gives Away $3Bn Companyhttps://www.edie.net/patagonia-to-redistribute-profits-to-environmental-and-social-causes/https://unofficialnetworks.com/2022/09/14/patagonia-founder-gives-away-company-2/Zoom Outage Affects Thousandshttps://www.crn.com/news/cloud/zoom-outage-hits-tens-of-thousands-of-usersLorenz Ransomware Leverages Vulnerable VoIPhttps://www.darkreading.com/vulnerabilities-threats/lorenz-ransomware-smbs-mitel-voip-phone-systemsSSDs More Reliable Than HDDshttps://arstechnica.com/gadgets/2022/09/five-years-of-data-show-that-ssds-are-more-reliable-than-hdds-over-the-long-haul/Windows Terminal Preview 1.16 Releasehttps://devblogs.microsoft.com/commandline/windows-terminal-preview-1-16-release/ Check out yesterday's MSP Dispatch Special Report: SuperOps Marketing Efforts https://www.youtube.com/watch?v=s4kb1bSI-RY Community Events: 9/16 - 9/18 @ In Person Event | Techcon Unplugged: Chicago, IL9/20 @ 10:00 am ET | MSP Dispatch Presented by The MSP Media Network9/22 - 9/24 In Person Event | Big Big Conference 2022: Hollywood, FL9/23 @ 10:00 am ET | MSP Dispatch Week Wrap Up Presented by The MSP Media Network9/23 @ 11:00 am ET | September Channel Pitch Presented by The Channel Program Connect with our hosts:  - Tony Francisco: https://www.linkedin.com/in/tonyjfrancisco/ - Ray Orsini: https://www.linkedin.com/in/rayorsini/ Be sure to follow us on social media:  Facebook: https://www.facebook.com/mspmediatv/ Twitter: https://twitter.com/mspmediatv LinkedIn: https://www.linkedin.com/company/mspmediatv/ Instagram: https://www.instagram.com/mspmediatv   Reddit: https://www.reddit.com/r/mspmedia Discord: https://discord.gg/Hc7b55cJPF

This week in #Chia News we dive into the use cases that Chia official envisions. We look at what current price and chia farm profits look like. #Solana cofounder learns about Chia and I cover the #Ethereum Merge and how that will change everything.Join this channel to get access to perks:https://www.youtube.com/channel/UCiaQzXI5528Il6r2NNkrkJA/joinShop our Store (receive 3% or 5% off unlimited items w/channel membership) https://shop.digitalspaceport.com/10K 800TB Chia farm blueprintArticle https://digitalspaceport.com/chia-farm-template-750-tib-for-10000/Video https://youtu.be/yqG9vlH6LwcChia Earnings Sheet https://docs.google.com/spreadsheets/d/1lXviouJ1dZhT3s_4wQgdySnTMJJX3E5LXcJJv5xftdg/edit#gid=905970511Enterprise Chia Farm DIY

European Union lawmakers agreed on new proposals to force manufacturers use USB Type-C. Elon Musk to get Twitter data access to settle bot complaints. Microsoft wants to kill HDDs.

This week's episode gives Colin and Steve their biggest emotional gut-punch to date! Join us this week as we discuss the deeply concerning reason that you have to be awake for cataract surgery, Colin's friend's need to own enterprise grade HDDs, and we dive deep into the many emotions in the latest episodes! If you'd like to get updates on the latest episodes and some occasional anime memes, why not give our Facebook page a follow? Who's That Anime? FB Page If you'd like to see the video of our podcast, check out our YouTube channel: Who's That Anime? YouTube Channel! If you're interested in following some of our other endeavours, why not give these links a try? Couch Fuel - Colin's Twitch channel Hail, Paimon! - Steve's Twitch channel

Western Digital has unveiled its new 22TB CMR and 26TB UltraSMR hard disk drives (HDDs) which are now being tested by select hyperscale cloud . Western Digital has unveiled its new 22TB CMR and 26TB UltraSMR hard disk drives (HDDs) which are now being tested by select hyperscale cloud customers. The reason the storage giant has been able to significantly expand the capacity of HDDs over the years is due to its ever expanding technology portfolio which includes its unique OptiNAND technology, energy-assisted PMR (ePMR), triple-stage actuator (TSA), HelioSeal and now UltraSMR. Western Digital's new ePMR drives leverage the company's OptiNAND technology to unlock higher levels of capacity, performance and data resiliency. For instance, its new 22TB CMR HDD incorporates OptiNAND to deliver areal density on a 2.2TB/platter HelioSeal platform with ten disks. While the average consumer likely doesn't have a need for such a high capacity drive, cloud computing providers and other tech giants can use Western Digital's HDDs to store more data in less space which could help bring down the cost of cloud storage services for end users. UltraSMR By combining OptiNAND with proprietary firmware that leverages HDD system-level hardware advancements, Western Digital's new UltraSMR technology introduces large block encoding with an advanced error correction algorithm that increases track-per-inch (TPI) to enable higher capacity HDDs. The first HDD to use this new technology is the company's new 26TB Ultrastar DC HC670 UltraSMR HDD that features 2.6TB per platter and offers 18 percent more storage capacity. However, as cloud service providers are increasingly adding SMR to their datacenter roadmaps, the drive's 26TB capacity could serve as a tipping point to accelerate adoption. Read More > Samsung, Western Digital join forces on next-gen SSD technology > Western Digital plots to squeeze the tape market with massive archive HDDs > Western Digital customers urged to update to latest version of My Cloud OS EVP and GM of Western Digital's HDD Business Unit, Ashley Gorakhpurwalla provided further insight on the company's HDD technology portfolio in a press release, saying: “As a longstanding partner of the industry's leading cloud providers, we understand their unique requirements in building next-generation cloud infrastructure and invested in several HDD innovations we developed alongside our areal density technology. Our intent with taking this development strategy was not only to address the capacity demands of the world's largest cloud titans but to deliver on a roadmap that would also support the evolving economics of their data centers for decades to come. With ePMR, OptiNAND and now UltraSMR as the foundation of Western Digital's HDD roadmap, our cloud customers can continue rapidly scaling their business by taking advantage of our innovations to lower their storage TCO.” The 22TB Ultrastar DC HC570 HDD will soon begin volume shipments to the channel while the 26TB Ultrastar DC HC670 UltraSMR HDD is set to begin shipping to select customers this summer. Tackle even the most demanding computing tasks with one of the best workstations

Nicht immer reicht der Speicher von verbauten Festplatten im Laptop oder anderen Geräten für die eigenen Anforderungen aus. Als Lösung gibt es kompakte, aber mit viel Speicher ausgestattete externe SSD- und HDD-Festplatten. Amazon hat während seiner Oster-Aktion eine Vielzahl von Samsung, SanDisk und Co. im Angebot. Wir zeigen euch die besten Angebote.

Speicherverwaltungs-Technologien, um die zunehmende Lücke zwischen Datenwachstum und Infrastrukturbudget zu schließen. "Flash - Disk - Tape - Cloud - Object - Cold Storage" - Wie passt das alles zusammen? Norbert Deuschle vom Storage Consortium im Gespräch mit Ines Wolf - Managerin Pre-Sales CE der Firma Quantum. Ein technischer Podcast mit Details zum Quantum Active Scale Cold Storage - Speicherlösungsangebot. Im einzelnen werden folgende Punkte angesprochen und detaillierter behandelt: Was sind gerade die größten Herausforderungen bei der Speicherung, dem Zugriff und der Verwaltung im Zusammenhang mit einer langfristigen Aufbewahrung von Massendaten? Was bedeutet Cold Storage? Welche Zugriffsmöglichkeiten ergeben sich auf Basis welcher Technologien? Wie kann eine moderne Speicherverwaltung unter Einbeziehung von Storageklassen dabei helfen, kalte Daten bei Bedarf wieder "zum Leben" zu erwecken? Disk (HDD), Tape und die Cloud (S3) ? Wie passen die Technologien zusammen. Welche Anforderungen ergeben sich im Gegensatz zu HDDs beim Schreiben auf Band (Mengen, Kosten, Verwaltung usw.) Wie lassen sich die daran beteiligten verschiedenen Speichertechnologien möglichst einheitlich verwalten? Welche Rolle spielt Object Storage im Rahmen der Quantum Active Scale Cold Storage - Technologie? Was unterscheidet diese von anderen Lösungsansätzen? Intelligentes Data Staging, Tape Mgmt., 2D Erasure Coding, 3 GEO DDP usw. und weitere Optionen. Warum bestimmte Kunden Cold Storage und Objektspeicher lieber on-premise implementieren? Vorteile gegenüber der Public Cloud. Wie lässt sich die Verbindung zu Cloud Deployments (S3 / Glacier / API-Ansatz) realisieren. Wie kann Tape in Zusammenhang mit S3, Cloud und Objektspeicher genutzt werden? Möglichkeiten, die Lösung als ‚Storage as a Service' zu beziehen (pay-as-you-use ), ähnlich wie bei Public-Cloud - Angeboten.

" The Personal Computer Show Wednesday March 9, 2022 PRN.live Streaming on the Internet 6:00 PM Eastern Time IN THE NEWS o Amazon Closing All 68 of its Books, 4-Star, and Pop-Up Stores o New Ohio Law Cracking Down on Robocalls o Backblaze Report SSDs are as Reliable as HDDs o Russia Says NASA Can Use Broomsticks to Fly in Space o Internet Backbone Provider Shuts Off Service in Russia IT Pro Series with Benjamin Rockwell o Building Your Brand on LinkedIn - Part 1 of 3 From The Tech Corner o Hubble Space Telescope 20 Years of Ground Breaking Discovery with ACS o Redesigning How CPU's are Built Technology Chatter with Benjamin Rockwell and Marty Winston o Zombie Shipping Containers Disrupting Economy "

In 2005, Thailand became the world's biggest manufacturer of hard disk drives or HDDs. As of this writing, they remain the second biggest exporter after China and the largest in Southeast Asia. Thailand's dominance in this particular industry tends only to be recognized when something happens to damage it. For instance, floods in 2011 that caused a number of worldwide HDD shortages. But I do think - like with the semiconductor shortage - it is worth studying how this situation came to be. And how, kind of like with Malaysia, Thailand has yet to be able to grow as far and fast beyond that as they would like. In this video, we will look at how Thailand came to be a leader in the hard drive industry. And the daunting challenges associated with growing beyond that early success.

In 2005, Thailand became the world's biggest manufacturer of hard disk drives or HDDs. As of this writing, they remain the second biggest exporter after China and the largest in Southeast Asia. Thailand's dominance in this particular industry tends only to be recognized when something happens to damage it. For instance, floods in 2011 that caused a number of worldwide HDD shortages. But I do think - like with the semiconductor shortage - it is worth studying how this situation came to be. And how, kind of like with Malaysia, Thailand has yet to be able to grow as far and fast beyond that as they would like. In this video, we will look at how Thailand came to be a leader in the hard drive industry. And the daunting challenges associated with growing beyond that early success.

Mo Gawdat, formerly the Chief Business Officer for Google’s moonshot organization, issued his warning in a new interview with The Times. AI seen in science fiction like Skynet from “The Terminator,” is inevitable — Every day Big Tech and Mass Media make it hard to find out what is going on with the internet. Honey Beez and Trip Elix have unique experiences to share in an unpaired podcast experience. Join our community!! Subscribe to the Insecurity Brief podcast now on every platform we can find Follow us on Twitter @HoneyBeez0x @trip_elix Links Our Website: https://www.tripelix.com/insecurity/ex-google-executive-warns-singularity-is-coming-and-that-it-poses-a-major-threat-to-humanity/ Youtube https://youtu.be/xZddLec7jKU the link to the podcast itunes:https://podcasts.apple.com/us/podcast/ex-google-executive-warns-singularity-is-coming-and/id1583788677?i=1000537701939 Spotify:https://open.spotify.com/episode/5uInjUJmaYIchitB1fdwON Soundcloud:https://soundcloud.com/user-841713900/ex-google-executive-warns-singularity-is-coming-and-that-it-poses-a-major-threat-to-humanity?si=5ede05d480514d779d60d766e2f20a59 Trip’s books https://www.tripelix.com/merch Honey’s books https://beedefense.net #Amazon #Google #Astro #SSD #AI Amazon Astro: Experts are concerned about security issues The new Amazon robot is designed to roam your home and promises to do everything. Named Astro, the bot will watch an elderly family member and warn you if you accidentally forgot to open the stove. With large round blinking eyes, the Astro is reminiscent of Pixar Wall-E and just as cute. But privacy experts say consumers should be aware that these eyes may not be real, but they will always watch. https://en.secnews.gr/368202/amazon-astro-eidikoi-anisixoun-idiwtikotita/ Backblaze: The failures of SSDs are the same as those of HDDs Solid state drives (SSDs) have become the preferred choice over hard drives (HDDs) due to their lack of moving components, their inherent magnetic resistance, their ability to withstand vibration and their overall strength. However, a recent post by cloud storage provider Backblaze reveals that SSD failures are the same as those on hard drives. https://en.secnews.gr/368174/backblaze-failures-ssds-antistoixa-hdds/

In this episode I talk with Paul katzoff, CEO of WhiteCanyon. WhiteCanyon is a company leading the area of permanent deletion technology for data on HDDs, SSDs and NVMe drives. The company is engaged in the development, sales, and support of Drive Sanitization. Phil and I talk about how WhiteCanyon's flagship product, WipeDrive, has become a world leader for erasing hard drives. Government agencies, US Military, and Fortune 500 companies across the world are using WipeDrive to permanently erase and wipe hard drive data. WhiteCanyon was founded in 1998 and is head quartered out of the American Fork, Utah, USA. Web: https://www.whitecanyon.com/ Software Timeline History: https://www.youtube.com/watch?v=0n81k8tu3Mw Interested in being on #GTwGT? https://launch.gtwgt.com Music: https://www.bensound.com Could always do with a coffee! https://ko-fi.com/gtwgt

SSD (Solid State Drives) is a data storage device and a technology that lets you access data quickly and at a faster rate. In recent years, SSD has gained popularity in the IT and web hosting industry, providing several advantages to hosting and computing solutions. Unlike the traditional HDDs (Hard Disk Drives), SSDs are much faster and reliable. They have no moving parts like HDDs, which makes them highly secure and reliable. In this podcast episode, we will highlight the benefits offered by SSD in reseller hosting solution. Also, check out this blog that talks about the benefits of SSD web hosting for your business: https://blog.resellerclub.com/benefits-of-ssd-web-hosting/ Check out the Linux reseller hosting service with 24/7 customer support from ResellerClub at: https://www.resellerclub.com/reseller-hosting

Focused on optimizing Apache Kafka® performance with maximized efficiency, Confluent’s Product Infrastructure team has been actively exploring opportunities for scaling out Kafka clusters. They are able to run Kafka workloads with half the typical memory usage while saving infrastructure costs, which they have tested and now safely rolled out across Confluent Cloud. After spending seven years at Amazon Web Services (AWS) working on search services and Amazon Aurora as a software engineer, Adithya Chandra decided to apply his expertise in cluster management, load balancing, elasticity, and performance of search and storage clusters to the Confluent team.Last year, Confluent shipped Tiered Storage, which moves eligible data to remote storage from a Kafka broker. As most of the data moves to remote storage, we can upgrade to better storage volumes backed by solid-state drives (SSDs). SSDs are capable of higher throughput compared to hard disk drives (HDDs), capable of fast, random IO, yet more expensive per provisioned gigabyte. Given that SSDs are useful at random IO and can support higher throughput, Confluent started investigating whether it was possible to run Kafka with lesser RAM, which is comparatively much more expensive per gigabyte compared to SSD. Instance types in the cloud had the same CPU but half the memory was 20% cheaper.In this episode, Adithya covers how to run Kafka more efficiently on Confluent Cloud and dives into the following:Memory allocation on an instance running KafkaWhat is a JVM heap? Why should it be sized? How much is enough? What are the downsides of a small heap?Memory usage of Datadog, Kubernetes, and other processes, and allocating memory correctlyWhat is the ideal page cache size? What is a page cache used for? Are there any parameters that can be tuned? How does Kafka use the page cache?Testing via the simulation of a variety of workloads using TrogdorHigh-throughput, high-connection, and high-partition tests and their resultsAvailable cloud hardware and finding the best fit, including choosing the number of instance types, migrating from one instance to another, and using nodepools to migrate brokers safely, one by oneWhat do you do when your preferred hardware is not available? Can you run hybrid Kafka clusters if the preferred instance is not widely available?Building infrastructure that allows you to perform testing easily and that can support newer hardware faster (ARM processors, SSDs, etc.)EPISODE LINKSWatch the video version of this podcastJoin the Confluent CommunityLearn more with Kafka tutorials, resources, and guides at Confluent DeveloperLive demo: Kafka streaming in 10 minutes on Confluent CloudUse 60PDCAST to get an additional $60 of free Confluent Cloud usage (details)

Besucht uns im Discord https://discord.gg/SneNarVCBM, auf Twitter https://twitter.com/technikquatsch und unserem Twitch-Kanal https://www.twitch.tv/technikquatsch. Diesmal gibt es leider auch wieder Warnungen vor Phishing. Aber das ist natürlich nicht alles: AMD hat Teile der FidelityFX-Suite für die Xbox Series S/X freigegeben, das großartige Open-World-Spiel Horizon: Zero Dawn ist aktuell kostenlos auf PS4 und PS5 (bis 15. Mai aktivierbar), […] The post Folge 51: Phishing-SMS, AMD FidelityFX für Xbox, Crypto-Gedöns mit HDDs, Apple Keynote, Discord NSFW auf iPhone appeared first on Technikquatsch.

Besucht uns im Discord https://discord.gg/SneNarVCBM, auf Twitter https://twitter.com/technikquatsch und unserem Twitch-Kanal https://www.twitch.tv/technikquatsch. Diesmal gibt es leider auch wieder Warnungen vor Phishing. Aber das ist natürlich nicht alles: AMD hat Teile der FidelityFX-Suite für die Xbox Series S/X freigegeben, das großartige Open-World-Spiel Horizon: Zero Dawn ist aktuell kostenlos auf PS4 und PS5 (bis 15. Mai aktivierbar), der Bioware-Klassiker Star Wars - Knights of the Old Republic bekommt ein Remake und Crypto-Währungen nehmen Festplatten ein. Dazu dann noch ausgiebig über die Apple Keynote und ein Apple sperrt alle Discord-Server mit NSFW-Kanälen. Außerdem gibt es die Auflösung für einen kleinen Teaser in unserem Discord zu folgendem Bild: 00:19:05 Phishing-SMS getarnt als Paketbenachrichtigungen, Twitter-DMs mit Malware. 00:25:50 AMD gibt FidelityFX für Xbox Series S/X frei 00:32:34 Horizon: Zero Dawn in Playstation Play at Home kostenlos 00:33:25 Star Wars - Knights of the Old Republic bekommt ein Remake von Aspyr Media 00:35:30 Crypto-Währung Chia setzt auf "Proof of Space and Time", HDDs werden teurer 00:46:32 Apple Keynote: iPhone 12 in Lila,00:48:38 Apple Podcasts führt Abos ein01:07:04 Apple Air Tags01:10:38 Apple TV 4K in neuer Auflage01:16:48 iMacs mit Apple M1 01:22:45 Apple sperrt Discord-Server mit NSFW-Inhalten https://www.bsi.bund.de/DE/Service-Navi/Presse/Alle-Meldungen-News/Meldungen/Smishing_SMS-Phishing_090421.htmlhttps://twitter.com/AnonNewsDE/status/1384869135470010372?s=20 https://www.computerbase.de/2021-04/xbox-series-x-s-next-gen-spielkonsole-erhaelt-amd-fidelityfx/ https://www.eurogamer.net/articles/2021-04-21-star-wars-knights-of-the-old-republic-remake-developed-by-aspyr https://www.computerbase.de/2021-04/kryptowaehrung-chia-chinesische-miner-hamstern-hdds-und-ssds/ https://www.sir-apfelot.de/apple-event-zusammenfassung-der-keynote-am-20-april-2021-34683/ https://www.heise.de/news/Discord-Zugriff-auf-nicht-jugendfreie-Inhalte-in-iPhone-App-generell-blockiert-6015178.html Sprecher: Meep, Mohammed Ali Dad, Michael Kister

Intels new bleep software uses A.I. to filter out a variety of hate speech tailored to the users liking.  WD has shipped 3 ZB worth of HDDs, if stacked up would  reach 1/5 the way to the moon. We meander through a few topics but most notably M.A.T.T. shares his experience in building his very own NAS. For gaming we highlight Wargroove, Fantasia, Cyberpunk and racing simulators. Help Support Us and Get Protected With PIA. https://www.privateinternetaccess.com/pages/buy-vpn/Techill1   tilliterate@gmail.com

Sarah Tenisi from TenisiTech was this week’s Technado guest, sharing her experiences running a successful MSP for the past nine years. She also helped breakdown digital transformation as it relates to MSPs in the segment “Buzzword Breakdown.” In the news, the team discussed Seagate’s planned 100TB multi-actuator HDDs, vertical tabs in Microsoft Edge, a URL bit flipping proof of concept, a costly gaffe from Gab’s CTO, and a significant hack that affected Microsoft Exchange Server. Finally, in WTF, they looked at a robot that can give a tattoo using 5G.

Sarah Tenisi from TenisiTech was this week’s Technado guest, sharing her experiences running a successful MSP for the past nine years. She also helped breakdown digital transformation as it relates to MSPs in the segment “Buzzword Breakdown.” In the news, the team discussed Seagate’s planned 100TB multi-actuator HDDs, vertical tabs in Microsoft Edge, a URL bit flipping proof of concept, a costly gaffe from Gab’s CTO, and a significant hack that affected Microsoft Exchange Server. Finally, in WTF, they looked at a robot that can give a tattoo using 5G. (edited)

SSD Cloud Hosting, as the name suggests, comes with SSD storage, which is an advanced storage type without any moving parts, unlike traditional HDDs. It offers seamless website performance with its fast read/write speeds and is less prone to the risk of losing data. In this episode, we have an in-detail discussion regarding why one needs SSD Cloud Hosting. Check out SSD Cloud Hosting plans from ResellerClub at https://india.resellerclub.com/cloud-hosting

Low power x86 vs Arm boards, hard disk failure rates, and the intricacies of ZFS snapshots.   Plugs OpenZFS Developer Summit Support the podcast on Patreon   News Seeed Studio’s Odyssey is a mini-PC for big projects and small wallets Backblaze Hard Drive Stats Q2 2020   Free consulting We were asked about ZFS on […]

In this week's episode Matt and Mike discuss learning by doing, rather than learning by tutorials or traditional classes. By working on projects, getting stuck, and then Googling your way through you'll learn faster, have a finished product at the end of the day, and be able to retain what you learned easier because you've researched and implemented the solution yourself. They go through various tactics on how to maximize your learn by doing experience, and then go through an example scenario of how they'd plan a project that they've never done themselves. Then in the Web News, they discuss hardware obsolescence via software with things like Windows 10 + HDDs, and the iPhone battery scandal. You can find us on... Facebook | Twitter | Instagram RSS | Patreon | Spotify Medium | YouTube | GitHub  Reddit | Discord

Everyone's sick. We've all got a bit of the coronavirus in us already, and now we're just waiting for the alien eggs to hatch from our stomachs. That's right folks, in my 4 AM congestion-fever haze I discovered that COVID-19 is actually alien babies that want our warm bodies as incubators for their furtive young. Also, Jim Henson was assassinated by the CIA, Hilary Clinton's lizard baby grew up to be Katy Perry, and Tupac and Elvis were the SAME GUY. Row row row your boat gently down the stream oops I activated a Russian asset in Minnesota and now we moved in together and have a pet komodo dragon.* ASMR* Closing Pandora's Box* Not Expecting Failure* Burying OCI don't get ASMR. If you want someone to whisper in your ear, the Ying Yang Twins already did it 15 years ago. And they were so polite about it. I guess some guys just have a need to spend money on a virtual girlfriend that they share with 15,000 other dudes. It's like The Bachelorette, but she's married and isn't going to touch any of the dudes, but they keep giving her flowers and presents. But keep in mind, none of this is sexual. Except for the sexy girl pretending to be your girlfriend. And the guys yanking it to her. Not sexual.Once something is on the internet, it's there forever. There are literally weirdos that catalogue and archive all content they find on mountains of hard drives. Petabytes upon petabytes of content that will one day be like gold bars after the apocalypse. You'll be eating your canned franks and beans when you suddenly get a hankering for some old hilarious viral video. With the internet having been destroyed 10 years ago, you're out of luck, unless you can scrounge up enough bottle caps to pay for an hour with one of King Tyler's precious HDDs.Everyone is constantly disappointed. Why? Because they expect too much. Lower them expectations, people. If you expect most people to be complete j-holes, screw ups, and generally failures at life, well when someone comes around and they're a decent person they've completely surpassed your expectations! This goes for people, media, and pretty much everything in life. It's like in Iron Man, when Tony Stark returns from weeks of captivity eating nothing but bland gruel, that flame-broiled Burger King Whopper tastes like heaven. Be Tony Stark.Speaking of the internet. Once you put something out there, you no longer own it. It's the classic meme: "You made this?" "I made this." Throw out some great art, dozens of people steal it and put it on a shirt. Some rapper from Azerbaijan makes it his album art. Your twitter post of it has 120 retweets, and CYBER ART 20XX posts it, doesn't credit you, and gets 544K retweets, with dozens of comments asking where they can buy a print of it. But you're an asshole for asking them to just mention you.All this and more on this week’s episode! Don't forget to join us on DISCORD, and support us on PATREON, NEWPROJECT2 or by BUYING A SHIRT!

Leo Laporte answers Tony's question about SSD reliability for data retention on his new iMac. Do solid-state drives wear out easily? Host: Leo Laporte Download or subscribe to this show at https://twit.tv/shows/ask-the-tech-guy Sponsor: LastPass.com/twit

Leo Laporte answers Tony's question about SSD reliability for data retention on his new iMac. Do solid-state drives wear out easily? Host: Leo Laporte Download or subscribe to this show at https://twit.tv/shows/ask-the-tech-guy Sponsor: LastPass.com/twit

Leo Laporte answers Tony's question about SSD reliability for data retention on his new iMac. Do solid-state drives wear out easily? Host: Leo Laporte Download or subscribe to this show at https://twit.tv/shows/ask-the-tech-guy Sponsor: LastPass.com/twit

Leo Laporte answers Tony's question about SSD reliability for data retention on his new iMac. Do solid-state drives wear out easily? Host: Leo Laporte Download or subscribe to this show at https://twit.tv/shows/ask-the-tech-guy Sponsor: LastPass.com/twit

Hey, folks. It’s, uh, been a while. As you may notice, this episode about the end of the summer season was recorded several weeks ago. I go into more detail on the next podcast, but the basics of what happened is this: I had been editing this podcast when my hard drive suddenly stopped working. I have three drives: one SSD and two HDDs. The one the failed happened to be the one I do all my projects on, which also means I lost the audio for three other episodes I recorded. I managed to save my audio for this episode before the drive completely died, but the first few reviews of the fall 2019 season are gone forever.So yeah. Fun times!

This week on the Rocket Punch Cast is all about "Crunch"! Cameron and Will sit down to discuss the recent events from Rockstar and Red Dead Redemption 2 involving comments about their work practices, and take a hard look at some of the overtime work practices in the gaming industry. With game developers working so hard, lots of the time too hard, to get us the games that we desire, can there be ways to alleviate the burdens of crunch for them? How does crunch trickle down and affect consumes and shareholders? Is there a solution for all of this? Plus, Cameron gives his impressions after trying out Project Stream, Will reminds people to clear their hard drive for Red Dead Redemption 2, the team says goodbye to the Crunchyroll/Funimation partnership, and more! INTRO THEME: "Punch It!" by TechnoCenturion is licensed under Creative Commons Attribution license (https://creativecommons.org/licenses/by/4.0/)Artist: https://soundcloud.com/charles-e-samuel-jr END THEME: "Bye Bye, See You Again" by wyver9 is licensed under Creative Commons Attribution license (https://creativecommons.org/licenses/by/4.0/)Artist: http://incompetech.com/Source: http://www.newgrounds.com/audio/listen/637032 SHOW NOTES: Prepare you HDDs for Red Dead Redemption 2… https://www.polygon.com/2018/10/18/17995728/red-dead-redemption-2-install-hard-drive-space Skybound CEO wants former TT staff for Walking Dead finale: https://www.gameinformer.com/2018/10/18/skybound-ceo-wants-the-walking-dead-finale-to-be-entirely-developed-by-former-telltale Sega’s cancelled Shenmue HD remake: https://www.eurogamer.net/articles/digitalfoundry-2018-segas-cancelled-shenmue-remake Crunchyroll and Funimation ending their relationship… : https://www.crunchyroll.com/forumtopic-1025862/update-to-the-crunchyroll-x-funimation-partnership Days Gone is delayed (we called it!): https://blog.us.playstation.com/2018/10/19/playstations-worldwide-studios-release-lineup-the-next-wave-of-ps4-games/ Spider-Man DLC out this week: https://blog.us.playstation.com/2018/10/16/marvels-spider-man-the-heist-out-next-tuesday-adds-3-new-suits/ Spider-Man NGP is now live!: https://www.gamesradar.com/spider-man-ps4-new-game-plus/

NetBSD 8.0 available, FreeBSD on Scaleway’s ARM64 VPS, encrypted backups with OpenBSD, Dragonfly server storage upgrade, zpool checkpoints, g2k18 hackathon reports, and more. ##Headlines NetBSD v8.0 Released The NetBSD Project is pleased to announce NetBSD 8.0, the sixteenth major release of the NetBSD operating system. This release brings stability improvements, hundreds of bug fixes, and many new features. Some highlights of the NetBSD 8.0 release are: USB stack rework, USB3 support added. In-kernel audio mixer (audio_system(9)). Reproducible builds (MKREPRO, see mk.conf(5)). Full userland debug information (MKDEBUG, see mk.conf(5)) available. While most install media do not come with them (for size reasons), the debug and xdebug sets can be downloaded and extracted as needed later. They provide full symbol information for all base system and X binaries and libraries and allow better error reporting and (userland) crash analysis. PaX MPROTECT (W^X) memory protection enforced by default on some architectures with fine-grained memory protection and suitable ELF formats: i386, amd64, evbarm, landisk. PaX ASLR (Address Space Layout Randomization) enabled by default on: i386, amd64, evbarm, landisk, sparc64. Position independent executables by default for userland on: i386, amd64, arm, m68k, mips, sh3, sparc64. A new socket layer can(4) has been added for communication of devices on a CAN bus. A special pseudo interface ipsecif(4) for route-based VPNs has been added. Parts of the network stack have been made MP-safe. The kernel option NET_MPSAFE is required to enable this. Hardening of the network stack in general. Various WAPBL (the NetBSD file system “log” option) stability and performance improvements. Specific to i386 and amd64 CPUs: Meltdown mitigation: SVS (Separate Virtual Space), enabled by default. SpectreV2 mitigation: retpoline (support in gcc), used by default for kernels. Other hardware mitigations are also available. SpectreV4 mitigations available for Intel and AMD. PopSS workaround: user access to debug registers is turned off by default. Lazy FPU saving disabled on vulnerable Intel CPUs (“eagerfpu”). SMAP support. Improvement and hardening of the memory layout: W^X, fewer writable pages, better consistency, better performance. (U)EFI bootloader. Many evbarm kernels now use FDT (flat device tree) information (loadable at boot time from an external file) for device configuration, the number of kernels has decreased but the number of boards has vastly increased. Lots of updates to 3rd party software included: GCC 5.5 with support for Address Sanitizer and Undefined Behavior Sanitizer GDB 7.12 GNU binutils 2.27 Clang/LLVM 3.8.1 OpenSSH 7.6 OpenSSL 1.0.2k mdocml 1.14.1 acpica 20170303 ntp 4.2.8p11-o dhcpcd 7.0.6 Lua 5.3.4 ###Running FreeBSD on the ARM64 VPS from Scaleway I’ve been thinking about this 6 since 2017, but only yesterday signed up for an account and played around with the ARM64 offering. Turns out it’s pretty great! KVM boots into UEFI, there’s a local VirtIO disk attached, no NBD junk required. So we can definitely run FreeBSD. I managed to “depenguinate” a running instance, the notes are below. Would be great if Scaleway offered an official image instead :wink: For some reason, unlike on x86 4, mounting additional volumes is not allowed 4 on ARM64 instances. So we’ll have to move the running Linux to a ramdisk using pivotroot and then we can do whatever to our one and only disk. Spin up an instance with Ubuntu Zesty and ssh in. Prepare the system and change the root to a tmpfs: apt install gdisk mount -t tmpfs tmpfs /tmp cp -r /bin /sbin /etc /dev /root /home /lib /run /usr /var /tmp mkdir /tmp/proc /tmp/sys /tmp/oldroot mount /dev/vda /tmp/oldroot mount --make-rprivate / pivotroot /tmp /tmp/oldroot for i in dev proc sys run; do mount --move /oldroot/$i /$i; done systemctl daemon-reload systemctl restart sshd Now reconnect to ssh from a second terminal (note: rm the connection file if you use ControlPersist in ssh config), then exit the old session. Kill the old sshd process, restart or stop the rest of the stuff using the old disk: pkill -f notty sed -ibak 's/RefuseManualStart.$//g' /lib/systemd/system/dbus.service systemctl daemon-reload systemctl restart dbus systemctl daemon-reexec systemctl stop user@0 ntp cron systemd-logind systemctl restart systemd-journald systemd-udevd pkill agetty pkill rsyslogd Check that nothing is touching /oldroot: lsof | grep oldroot There will probably be an old dbus-daemon, kill it. And finally, unmount the old root and overwrite the hard disk with a memstick image: umount -R /oldroot wget https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-arm64-aarch64-20180719-r336479-mini-memstick.img.xz xzcat FreeBSD-12.0-CURRENT-arm64-aarch64-20180719-r336479-mini-memstick.img.xz | dd if=/dev/stdin of=/dev/vda bs=1M (Look for the newest snapshot, don’t copy paste the July 19 link above if you’re reading this in the future. Actually maybe use a release instead of CURRENT…) Now, fix the GPT: move the secondary table to the end of the disk and resize the table. It’s important to resize here, as FreeBSD does not do that and silently creates partitions that won’t persist across reboots gdisk /dev/vda x e s 4 w y And reboot. (You might actually want to hard reboot here: for some reason on the first reboot from Linux, pressing the any-key to enter the prompt in the loader hangs the console for me.) I didn’t have to go into the ESC menu and choose the local disk in the boot manager, it seems to boot from disk automatically. Now we’re in the FreeBSD EFI loader. For some reason, the (recently fixed? 2) serial autodetection from EFI is not working correctly. Or something. So you don’t get console output by default. To fix, you have to run these commands in the boot loader command prompt: set console=comconsole,efi boot Ignore the warning about comconsole not being a valid console. Since there’s at least one (efi) that the loader thinks is valid, it sets the whole variable.) (UPD: shouldn’t be necessary in the next snapshot) Now it’s a regular installation process! When asked about partitioning, choose Shell, and manually add a partition and set up a root filesystem: gpart add -t freebsd-zfs -a 4k -l zroot vtbd0 zpool create -R /mnt -O mountpoint=none -O atime=off zroot /dev/gpt/zroot zfs create -o canmount=off -o mountpoint=none zroot/ROOT zfs create -o mountpoint=/ zroot/ROOT/default zfs create -o mountpoint=/usr zroot/ROOT/default/usr zfs create -o mountpoint=/var zroot/ROOT/default/var zfs create -o mountpoint=/var/log zroot/ROOT/default/var/log zfs create -o mountpoint=/usr/home zroot/home zpool set bootfs=zroot/ROOT/default zroot exit (In this example, I set up ZFS with a beadm-compatible layout which allows me to use Boot Environments.) In the post-install chroot shell, fix some configs like so: echo 'zfsload="YES"' >> /boot/loader.conf echo 'console="comconsole,efi"' >> /boot/loader.conf echo 'vfs.zfs.arcmax="512M"' >> /boot/loader.conf sysrc zfsenable=YES exit (Yeah, for some reason, the loader does not load zfs.ko’s dependency opensolaris.ko automatically here. idk what even. It does on my desktop and laptop.) Now you can reboot into the installed system!! Here’s how you can set up IPv6 (and root’s ssh key) auto configuration on boot: Pkg bootstrap pkg install curl curl https://raw.githubusercontent.com/scaleway/image-tools/master/bases/overlay-common/usr/local/bin/scw-metadata > /usr/local/bin/scw-metadata chmod +x /usr/local/bin/scw-metadata echo '#!/bin/sh' > /etc/rc.local echo 'PATH=/usr/local/bin:$PATH' >> /etc/rc.local echo 'eval $(scw-metadata)' >> /etc/rc.local echo 'echo $SSHPUBLICKEYS0KEY > /root/.ssh/authorizedkeys' >> /etc/rc.local echo 'chmod 0400 /root/.ssh/authorizedkeys' >> /etc/rc.local echo 'ifconfig vtnet0 inet6 $IPV6ADDRESS/$IPV6NETMASK' >> /etc/rc.local echo 'route -6 add default $IPV6GATEWAY' >> /etc/rc.local mkdir /run mkdir /root/.ssh sh /etc/rc.local And to fix incoming TCP connections, configure the DHCP client to change the broadcast address: echo 'interface "vtnet0" { supersede broadcast-address 255.255.255.255; }' >> /etc/dhclient.conf killall dhclient dhclient vtnet0 Other random notes: keep in mind that -CURRENT snapshots come with a debugging kernel by default, which limits syscall performance by a lot, you might want to build your own 2 with config GENERIC-NODEBUG also disable heavy malloc debugging features by running ln -s ‘abort:false,junk:false’ /etc/malloc.conf (yes that’s storing config in a symlink) you can reuse the installer’s partition for swap * Digital Ocean ** http://do.co/bsdnow ###Easy encrypted backups on OpenBSD with base tools Today’s topic is “Encrypted backups” using only OpenBSD base tools. I am planning to write a bigger article later about backups but it’s a wide topic with a lot of software to cover and a lot of explanations about the differents uses cases, needs, issues an solutions. Here I will stick on explaining how to make reliable backups for an OpenBSD system (my laptop). What we need is the dump command (see man 8 dump for its man page). It’s an utility to make a backup for a filesystem, it can only make a backup of one filesystem at a time. On my laptop I only backup /home partition so this solution is suitable for me while still being easy. Dump can do incremental backups, it means that it will only save what changed since the last backup of lower level. If you do not understand this, please refer to the dump man page. What is very interesting with dump is that it honors nodump flag which is an extended attribute of a FFS filesystem. One can use the command chflags nodump /home/solene/Downloads to tells dump not do save that folder (under some circumstances). By default, dump will not save thoses files, EXCEPT for a level 0 backup. Important features of this backup solution: save files with attributes, permissions and flags can recreate a partition from a dump, restore files interactively, from a list or from its inode number (useful when you have files in lost+found) one dump = one file My process is to make a huge dump of level 0 and keep it on a remote server, then, once a week I make a level 1 backup which will contain everything changed since the last dump of level 0, and everyday I do a level 2 backup of my files. The level 2 will contain latest files and the files changing a lot, which are often the most interesting. The level 1 backup is important because it will offload a lot of changes for the level 2. Let me explain: let says my full backup is 60 GB, full of pictures, sources files, GUI applications data files etc… A level 1 backup will contain every new picture, new projects, new GUI files etc… since the full backup, which will produce bigger and bigger dump over time, usually it is only 100 MB to 1GB. As I don’t add new pictures everyday or use new software everyday, the level 2 will take care of most littles changes to my data, like source code edited, little works on files etc… The level 2 backup is really small, I try to keep it under 50 MB so I can easily send it on my remote server everyday. One could you more dump level, up to level 9, but keep in mind that those are incremental. In my case, if I need to restore all my partition, I will need to use level 0, 1 and 2 to get up to latest backup state. If you want to restore a file deleted a few days ago, you need to remember in which level its latest version is. History note: dump was designed to be used with magnetic tapes. See the article for the remainder of the article ##News Roundup Status of DFly server storage upgrades (Matt Dillon) Last month we did some storage upgrades, particularly of internet-facing machines for package and OS distribution. Yesterday we did a number of additional upgrades, described below. All using funds generously donated by everyone! The main repository server received a 2TB SSD to replace the HDDs it was using before. This will improve access to a number of things maintained by this server, including the mail archives, and gives the main repo server more breathing room for repository expansion. Space was at a premium before. Now there’s plenty. Monster, the quad socket opteron which we currently use as the database builder and repository that we export to our public grok service (grok.dragonflybsd.org) received a 512G SSD to add swap space for swapcache, to help cache the grok meta-data. It now has 600GB of swapcache configured. Over the next few weeks we will also be changing the grok updates to ping-pong between the two 4TB data drives it received in the last upgrade so we can do concurrent updates and web accesses without them tripping over each other performance-wise. The main developer box, Leaf, received a 2TB SSD and we are currently in the midst of migrating all the developer accounts in /home and /build from its old HDDs to its new SSD. This machine serves developer repos, developer web stuff, our home page and wiki, etc, so those will become snappier as well. Hard drives are becoming real dinosaurs. We still have a few left from the old days but in terms of active use the only HDDs we feel we really need to keep now are the ones we use for backups and grok data, owing to the amount of storage needed for those functions. Five years ago when we received the blade server that now sits in the colo, we had a small 256G SSD for root on every blade, and everything else used HDDs. To make things operate smoothly, most of that 256G root SSD was assigned to swapcache (200G of it, in fact, in most cases). Even just 2 years ago replacing all those HDDs with SSDs, even just the ones being used to actively serve data and support developers, would have been cost prohibitive. But today it isn’t and the only HDDs we really need anywhere are for backups or certain very large bits of bulk data (aka the grok source repository and index). The way things are going, even the backup drives will probably become SSDs over the next two years. ###iX ad spot OSCON 2018 Recap ###zpool checkpoints In March, to FreeBSD landed a very interesting feature called ‘zpool checkpoints’. Before we jump straight into the topic, let’s take a step back and look at another ZFS feature called ‘snapshot’. Snapshot allows us to create an image of our single file systems. This gives us the option to modify data on the dataset without the fear of losing some data. A very good example of how to use ZFS snapshot is during an upgrade of database schema. Let us consider a situation where we have a few scripts which change our schema. Sometimes we are unable to upgrade in one transaction (for example, when we attempt to alter a table and then update it in single transaction). If our database is on dataset, we can just snapshot it, and if something goes wrong, simply rollback the file system to its previous state. The problem with snapshot is that it works only on a single dataset. If we added some dataset, we wouldn’t then be able to create the snapshot which would rollback that operation. The same with changing the attributes of a dataset. If we change the compression on the dataset, we cannot rollback it. We would need to change that manually. Another interesting problem involves upgrading the whole operating system when we upgrade system with a new ZFS version. What if we start upgrading our dataset and our kernel begins to crash? (If you use FreeBSD, I doubt you will ever have had that experience but still…). If we rollback to the old kernel, there is a chance the dataset will stop working because the new kernel doesn’t know how to use the new features. Zpool checkpoints is the solution to all those problems. Instead of taking a single snapshot of the dataset, we can now take a snapshot of the whole pool. That means we will not only rollback the data but also all the metadata. If we rewind to the checkpoint, all our ZFS properties will be rolled back; the upgrade will be rolledback, and even the creation/deletion of the dataset, and the snapshot, will be rolledback. Zpool Checkpoint has introduced a few simple functions: For a creating checkpoint: zpool checkpoint Rollbacks state to checkpoint and remove the checkpoint: zpool import -- rewind-to-checkpoint Mount the pool read only - this does not rollback the data: zpool import --read-only=on --rewind-to-checkpoint Remove the checkpoint zpool checkpoint --discard or zpool checkpoint -d With this powerful feature we need to remember some safety rules: Scrub will work only on data that isn’t in checkpool. You can’t remove vdev if you have a checkpoint. You can’t split mirror. Reguid will not work either. Create a checkpoint when one of the disks is removed… For me, this feature is incredibly useful, especially when upgrading an operating system, or when I need to experiment with additional data sets. If you speak Polish, I have some additional information for you. During the first Polish BSD user group meeting, I had the opportunity to give a short talk about this feature. Here you find the video of that talk, and here is the slideshow. I would like to offer my thanks to Serapheim Dimitropoulos for developing this feature, and for being so kind in sharing with me so many of its intricacies. If you are interested in knowing more about the technical details of this feature, you should check out Serapheim’s blog, and his video about checkpoints. ###g2k18 Reports g2k18 hackathon report: Ingo Schwarze on sed(1) bugfixing with Martijn van Duren, and about other small userland stuff g2k18 hackathon report: Kenneth Westerback on dhcpd(8) fixes, disklabel(8) refactoring and more g2k18 Hackathon Report: Marc Espie on ports and packages progress g2k18 hackathon report: Antoine Jacoutot on porting g2k18 hackathon report: Matthieu Herrb on font caches and xenodm g2k18 hackathon report: Florian Obser on rtadvd(8) -> rad(8) progress (actually, rewrite) g2k18 Hackathon Report: Klemens Nanni on improvements to route(8), pfctl(8), and mount(2) g2k18 hackathon report: Carlos Cardenas on vmm/vmd progress, LACP g2k18 hackathon report: Claudio Jeker on OpenBGPD developments Picture of the last day of the g2k18 hackathon in Ljubljana, Slovenia ##Beastie Bits Something blogged (on pkgsrcCon 2018) GSoC 2018 Reports: Configuration files versioning in pkgsrc, Part 1 There should be a global ‘awareness’ week for developers Polish BSD User Group – Upcoming Meeting: Aug 9th 2018 London BSD User Group – Upcoming Meeting: Aug 14th 2018 Phillip Smith’s collection of reasons why ZFS is better so that he does not have to repeat himself all the time EuroBSDCon 2018: Sept 20-23rd in Romania – Register NOW! MeetBSD 2018: Oct 19-20 in Santa Clara, California. Call for Papers closes on Aug 12 Tarsnap ##Feedback/Questions Dale - L2ARC recommendations & drive age question Todd - ZFS & S3 efraim - License Poem Henrick - Yet another ZFS question Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

Die aktuelle siebte Generation der Fujitsu ETERNUS CS8000 Plattform unterstützt in Kombination mit HDDs, SSDs und Tapes auch kritische unternehmensweite Datensicherungs- und Archivierungsprojekte, angefangen von 14 TB bis über 60 PB.

Fanless server setup with FreeBSD, NetBSD on pinebooks, another BSDCan trip report, transparent network audio, MirBSD's Korn Shell on Plan9, static site generators on OpenBSD, and more. ##Headlines Silent Fanless FreeBSD Desktop/Server Today I will write about silent fanless FreeBSD desktop or server computer … or NAS … or you name it, it can have multiple purposes. It also very low power solution, which also means that it will not overheat. Silent means no fans at all, even for the PSU. The format of the system should also be brought to minimum, so Mini-ITX seems best solution here. I have chosen Intel based solutions as they are very low power (6-10W), if you prefer AMD (as I often do) the closest solution in comparable price and power is Biostar A68N-2100 motherboard with AMD E1-2100 CPU and 9W power. Of course AMD has even more low power SoC solutions but finding the Mini-ITX motherboard with decent price is not an easy task. For comparison Intel has lots of such solutions below 6W whose can be nicely filtered on the ark.intel.com page. Pity that AMD does not provide such filtration for their products. I also chosen AES instructions as storage encryption (GELI on FreeBSD) today seems as obvious as HTTPS for the web pages. Here is how the system look powered up and working This motherboard uses Intel J3355 SoC which uses 10W and has AES instructions. It has two cores at your disposal but it also supports VT-x and EPT extensions so you can even run Bhyve on it. Components Now, an example system would look like that one below, here are the components with their prices. $49 CPU/Motherboard ASRock J3355B-ITX Mini-ITX $14 RAM Crucial 4 GB DDR3L 1.35V (low power) $17 PSU 12V 160W Pico (internal) $11 PSU 12V 96W FSP (external) $5 USB 2.0 Drive 16 GB ADATA $4 USB Wireless 802.11n $100 TOTAL The PSU 12V 160W Pico (internal) and PSU 12V 96W FSP can be purchased on aliexpress.com or ebay.com for example, at least I got them there. Here is the 12V 160W Pico (internal) PSU and its optional additional cables to power the optional HDDs. If course its one SATA power and one MOLEX power so additional MOLEX-SATA power adapter for about 1$ would be needed. Here is the 12V 96W FSP (external) PSU without the power cord. This gives as total silent fanless system price of about $120. Its about ONE TENTH OF THE COST of the cheapest FreeNAS hardware solution available – the FreeNAS Mini (Diskless) costs $1156 also without disks. You can put plain FreeBSD on top of it or Solaris/Illumos distribution OmniOSce which is server oriented. You can use prebuilt NAS solution based on FreeBSD like FreeNAS, NAS4Free, ZFSguru or even Solaris/Illumos based storage with napp-it appliance. ###An annotated look at a NetBSD Pinebook’s startup Pinebook is an affordable 64-bit ARM notebook. Today we’re going to take a look at the kernel output at startup and talk about what hardware support is available on NetBSD. Photo Pinebook comes with 2GB RAM standard. A small amount of this is reserved by the kernel and framebuffer. NetBSD uses flattened device-tree (FDT) to enumerate devices on all Allwinner based SoCs. On a running system, you can inspect the device tree using the ofctl(8) utility: Pinebook’s Allwinner A64 processor is based on the ARM Cortex-A53. It is designed to run at frequencies up to 1.2GHz. The A64 is a quad core design. NetBSD’s aarch64 pmap does not yet support SMP, so three cores are disabled for now. The interrupt controller is a standard ARM GIC-400 design. Clock drivers for managing PLLs, module clock dividers, clock gating, software resets, etc. Information about the clock tree is exported in the hw.clk sysctl namespace (root access required to read these values). # sysctl hw.clk.sun50ia64ccu0.mmc2 hw.clk.sun50ia64ccu0.mmc2.rate = 200000000 hw.clk.sun50ia64ccu0.mmc2.parent = pllperiph02x hw.clk.sun50ia64ccu0.mmc2.parent_domain = sun50ia64ccu0 Digital Ocean http://do.co/bsdnow ###BSDCan 2018 Trip Report: Mark Johnston BSDCan is a highlight of my summers: the ability to have face-to-face conversations with fellow developers and contributors is invaluable and always helps refresh my enthusiasm for FreeBSD. While in a perfect world we would all be able to communicate effectively over the Internet, it’s often noted that locking a group of developers together in a room can be a very efficient way to make progress on projects that otherwise get strung out over time, and to me this is one of the principal functions of BSD conferences. In my case I was able to fix some kgdb bugs that had been hindering me for months; get some opinions on the design of a feature I’ve been working on for FreeBSD 12.0; hear about some ongoing usage of code that I’ve worked on; and do some pair-debugging of an issue that has been affecting another developer. As is tradition, on Tuesday night I dropped off my things at the university residence where I was staying, and headed straight to the Royal Oak. This year it didn’t seem quite as packed with BSD developers, but I did meet several long-time colleagues and get a chance to catch up. In particular, I chatted with Justin Hibbits and got to hear about the bring-up of FreeBSD on POWER9, a new CPU family released by IBM. Justin was able to acquire a workstation based upon this CPU, which is a great motivator for getting FreeBSD into shape on that platform. POWER9 also has some promise in the server market, so it’s important for FreeBSD to be a viable OS choice there. Wednesday morning saw the beginning of the two-day FreeBSD developer summit, which precedes the conference proper. Gordon Tetlow led the summit and did an excellent job organizing things and keeping to the schedule. The first presentation was by Deb Goodkin of the FreeBSD Foundation, who gave an overview of the Foundation’s role and activities. After Deb’s presentation, present members of the FreeBSD core team discussed the work they had done over the past two years, as well as open tasks that would be handed over to the new core team upon completion of the ongoing election. Finally, Marius Strobl rounded off the day’s presentations by discussing the state and responsibilities of FreeBSD’s release engineering team. One side discussion of interest to me was around the notion of tightening integration with our Bugzilla instance; at moment we do not have any good means to mark a given bug as blocking a release, making it easy for bugs to slip into releases and thus lowering our overall quality. With FreeBSD 12.0 upon us, I plan to help with the triage and fixes for known regressions before the release process begins. After a break, the rest of the morning was devoted to plans for features in upcoming FreeBSD releases. This is one of my favorite discussion topics and typically takes the form of have/need/want, where developers collectively list features that they’ve developed and intend to upstream (have), features that they are missing (need), and nice-to-have features (want). This year, instead of the usual format, we listed features that are intended to ship in FreeBSD 12.0. The compiled list ended up being quite ambitious given how close we are to the beginning of the release cycle, but many individual developers (including myself) have signed up to deliver work. I’m hopeful that most, if not all of it, will make it into the release. After lunch, I attended a discussion led by Matt Ahrens and Alexander Motin on OpenZFS. Of particular interest to me were some observations made regarding the relative quantity and quality of contributions made by different “camps” of OpenZFS users (illumos, FreeBSD and ZoL), and their respective track records of upstreaming enhancements to the OpenZFS project. In part due to the high pace of changes in ZoL, the definition of “upstream” for ZFS has become murky, and of late ZFS changes have been ported directly from ZoL. Alexander discussed some known problems with ZFS on FreeBSD that have been discovered through performance testing. While I’m not familiar with ZFS internals, Alexander noted that ZFS’ write path has poor SMP scalability on FreeBSD owing to some limitations in a certain kernel API called taskqueue(9). I would like to explore this problem further and perhaps integrate a relatively new alternative interface which should perform better. Friday and Saturday were, of course, taken up by BSDCan talks. Friday’s keynote was by Benno Rice, who provided some history of UNIX boot systems as a precursor to some discussion of systemd and the difficulties presented by a user and developer community that actively resist change. The rest of the morning was consumed by talks and passed by quickly. First was Colin Percival’s detailed examination of where the FreeBSD kernel spends time during boot, together with an overview of some infrastructure he added to track boot times. He also provided a list of improvements that have been made since he started taking measurements, and some areas we can further improve. Colin’s existing work in this area has already brought about substantial reductions in boot time; amusingly, one of the remaining large delays comes from the keyboard driver, which contains a workaround for old PS/2 keyboards. While there seems to be general agreement that the workaround is probably no longer needed on most systems, the lingering uncertainty around this prevents us from removing the workaround. This is, sadly, a fairly typical example of an OS maintenance burden, and underscores the need to carefully document hardware bug workarounds. After this talk, I got to see some rather novel demonstrations of system tracing using dwatch, a new utility by Devin Teske, which aims to provide a user-friendly interface to DTrace. After lunch, I attended talks on netdump, a protocol for transmitting kernel dumps over a network after the system has panicked, and on a VPC implementation for FreeBSD. After the talks ended, I headed yet again to the hacker lounge and had some fruitful discussions on early microcode loading (one of my features for FreeBSD 12.0). These led me to reconsider some aspects of my approach and saved me a lot of time. Finally, I continued my debugging session from Wednesday with help from a couple of other developers. Saturday’s talks included a very thorough account by Li-Wen Hsu of his work in organizing a BSD conference in Taipei last year. As one of the attendees, I had felt that the conference had gone quite smoothly and was taken aback by the number of details and pitfalls that Li-Wen enumerated during his talk. This was followed by an excellent talk by Baptiste Daroussin on the difficulties one encounters when deploying FreeBSD in new environments. Baptiste offered criticisms of a number of aspects of FreeBSD, some of which hit close to home as they involved portions of the system that I’ve worked on. At the conclusion of the talks, we all gathered in the main lecture hall, where Dan led a traditional and quite lively auction for charity. I managed to snag a Pine64 board and will be getting FreeBSD installed on it the first chance I get. At the end of the auction, we all headed to ByWard for dinner, concluding yet another BSDCan. Thanks to Mark for sharing his experiences at this years BSDCan ##News Roundup Transparent network audio with mpd & sndiod Landry Breuil (landry@ when wearing his developer hat) wrote in… I've been a huge fan of MPD over the years to centralize my audio collection, and i've been using it with the http output to stream the music as a radio on the computer i'm currently using… audio_output { type "sndio" name "Local speakers" mixer_type "software" } audio_output { type "httpd" name "HTTP stream" mixer_type "software" encoder "vorbis" port "8000" format "44100:16:2" } this setup worked for years, allows me to stream my home radio to $work by tunnelling the port 8000 over ssh via LocalForward, but that still has some issues: a distinct timing gap between the 'local output' (ie the speakers connected to the machine where MPD is running) and the 'http output' caused by the time it takes to reencode the stream, which is ugly when you walk through the house and have a 15s delay sometimes mplayer as a client doesn't detect the pauses in the stream and needs to be restarted i need to configure/start a client on each computer and point it at the sound server url (can do via gmpc shoutcast client plugin…) it's not that elegant to reencode the stream, and it wastes cpu cycles So the current scheme is: mpd -> http output -> network -> mplayer -> sndiod on remote machine | -> sndio output -> sndiod on soundserver Fiddling a little bit with mpd outputs and reading the sndio output driver, i remembered sndiod has native network support… and the mpd sndio output allows you to specify a device (it uses SIO_DEVANY by default). So in the end, it's super easy to: enable network support in sndio on the remote machine i want the audio to play by adding -L to sndiod_flags (i have two audio devices, with an input coming from the webcam): sndiod_flags="-L10.246.200.10 -f rsnd/0 -f rsnd/1" open pf on port 11025 from the sound server ip: pass in proto tcp from 10.246.200.1 to any port 11025 configure a new output in mpd: audio_output { type "sndio" name "sndio on renton" device "snd@10.246.200.10/0" mixer_type "software" } and enable the new output in mpd: $mpc enable 2 Output 1 (Local speakers) is disabled Output 2 (sndio on renton) is enabled Output 3 (HTTP stream) is disabled Results in a big win: no gap anymore with the local speakers, no reencoding, no need to configure a client to play the stream, and i can still probably reproduce the same scheme over ssh from $work using a RemoteForward. mpd -> sndio output 2 -> network -> sndiod on remote machine | -> sndio output 1 -> sndiod on soundserver Thanks ratchov@ for sndiod :) ###MirBSD’s Korn Shell on Plan9 Jehanne Let start by saying that I’m not really a C programmer. My last public contribution to a POSIX C program was a little improvement to the Snort’s react module back in 2008. So while I know the C language well enough, I do not know anything about the subtleness of the standard library and I have little experience with POSIX semantics. This is not a big issue with Plan 9, since the C library and compiler are not standard anyway, but with Jehanne (a Plan 9 derivative of my own) I want to build a simple, loosely coupled, system that can actually run useful free software ported from UNIX. So I ported RedHat’s newlib to Jehanne on top of a new system library I wrote, LibPOSIX, that provides the necessary emulations. I wrote several test, checking they run the same on Linux and Jehanne, and then I begun looking for a real-world, battle tested, application to port first. I approached MirBSD’s Korn Shell for several reason: it is simple, powerful and well written it has been ported to several different operating systems it has few dependencies it’s the default shell in Android, so it’s really battle tested I was very confident. I had read the POSIX standard after all! And I had a test suite! I remember, I thought “Given newlib, how hard can it be?” The porting begun on September 1, 2017. It was completed by tg on January 5, 2018. 125 nights later. Turn out, my POSIX emulation was badly broken. Not just because of the usual bugs that any piece of C can have: I didn’t understood most POSIX semantics at all! iXsystems ###Static site generator with rsync and lowdown on OpenBSD ssg is a tiny POSIX-compliant shell script with few dependencies: lowdown(1) to parse markdown, rsync(1) to copy temporary files, and entr(1) to watch file changes. It generates Markdown articles to a static website. It copies the current directory to a temporary on in /tmp skipping .* and _*, renders all Markdown articles to HTML, generates RSS feed based on links from index.html, extracts the first tag from every article to generate a sitemap and use it as a page title, then wraps articles with a single HTML template, copies everything from the temporary directory to $DOCS/ Why not Jekyll or “$X”? ssg is one hundred times smaller than Jekyll. ssg and its dependencies are about 800KB combined. Compare that to 78MB of ruby with Jekyll and all the gems. So ssg can be installed in just few seconds on almost any Unix-like operating system. Obviously, ssg is tailored for my needs, it has all features I need and only those I use. Keeping ssg helps you to master your Unix-shell skills: awk, grep, sed, sh, cut, tr. As a web developer you work with lots of text: code and data. So you better master these wonderful tools. Performance 100 pps. On modern computers ssg generates a hundred pages per second. Half of a time for markdown rendering and another half for wrapping articles into the template. I heard good static site generators work—twice as fast—at 200 pps, so there’s lots of performance that can be gained. ;) ###Why does FreeBSD have virtually no (0%) desktop market share? Because someone made a horrible design decision back in 1984. In absolute fairness to those involved, it was an understandable decision, both from a research perspective, and from an economic perspective, although likely not, from a technology perspective. Why and what. The decision was taken because the X Window System was intended to run on cheap hardware, and, at the time, that meant reduced functionality in the end-point device with the physical display attached to it. At the same time, another force was acting to also limit X displays to display services only, rather than rolling in both window management and specific widget instances for common operational paradigms. Mostly, common operational paradigms didn’t really exist for windowing systems because they also simply didn’t exist at the time, and no one really knew how people were going to use the things, and so researchers didn’t want to commit future research to a set of hard constraints. So a decision was made: separate the display services from the application at the lowest level of graphics primitives currently in use at the time. The ramifications of this were pretty staggering. First, it guaranteed that all higher level graphics would live on the host side of the X protocol, instead of on the display device side of the protocol. Despite a good understanding of Moore’s law, and the fact that, since no X Terminals existed at the time as hardware, but were instead running as emulations on workstations that had sufficient capability, this put the higher level GUI object libraries — referred to as “widgets” — in host libraries linked into the applications. Second, it guaranteed that display organization and management paradigms would also live on the host side of the protocol — assumed, in contradiction to the previous decision, to be running on the workstation. But, presumably, at some point, as lightweight X Terminals became available, to migrate to a particular host computer managing compute resource login/access services. Between these early decisions reigned chaos. Specifically, the consequences of these decisions have been with us ever since: Look-and-feel are a consequence of the toolkit chosen by the application programmer, rather than a user decision which applies universally to all applications. You could call this “lack of a theme”, and — although I personally despise the idea of customizing or “theming” desktops — this meant that one paradigm chosen by the user would not apply universally across all applications, no matter who had written them. Window management style is a preference. You could call this a more radical version of “theming” — which you will remember, I despise — but a consequence to this is that training is not universal across personnel using such systems, nor is it transferrable. In other words, I can’t send someone to a class, and have them come back and use the computers in the office as a tool, with the computer itself — and the elements not specific to the application itself — disappearing into the background. Both of these ultimately render an X-based system unsuitable for desktops. I can’t pay once for training. Training that I do pay for does not easily and naturally translate between applications. Each new version may radically alter the desktop management paradigm into unrecognizability. Is there hope for the future? Well, the Linux community has been working on something called Wayland, and it is very promising… …In the same way X was “very promising” in 1984, because, unfortunately, they are making exactly the same mistakes X made in 1984, rather than correcting them, now that we have 20/20 hindsight, and know what a mature widget library should look like. So Wayland is screwing up again. But hey, it only took us, what, 25 years to get from X in 1987 to Wayland in in 2012. Maybe if we try again in 2037, we can get to where Windows was in 1995. ##Beastie Bits New washing machine comes with 7 pages of open source licenses! BSD Jobs Site FreeBSD Foundation Update, May 2018 FreeBSD Journal looking for book reviewers zedenv ZFS Boot Environment Manager Tarsnap ##Feedback/Questions Wouter - Feedback Efraim - OS Suggestion kevr - Raspberry Pi2/FreeBSD/Router on a Stick Vanja - Interview Suggestion Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

Small Biz Matters – a half hour program each week where you can work ON your business rather than IN it.with Alexi Boyd from Boyd Office Management ServicesDate: 17 April 2018 The Cloud. We get it, we use it. We count on it. Every day when operating as a small businesses we rely heavily on the cloud and internet storage. We assume it's safe, secure and backed up SOMEWHERE. We assume it's available anytime and reliable and we assume the content we produce is ours to do with what we wish. But we’re not careful enough. But like all things (except death and taxes as they say) you can’t be sure of it. You need to be in control with this extremely important tool of your trade. What if you can’t find an important document? What if the storage you relied on suddenly wasn’t there? What if you never backed up? Well today we have on the show another great expert; Gunnar Habitz to help us navigate through the complexities of Cloud storage but like always on Small Biz we’ll make sure you have practical strategies to ensure you take control. Welcome to the show Gunnar.   Topics we’ll be covering: Cloud overall Cloud storage vs. cloud backup comparing different tools How does a typical IT setup of Small Biz Owners look like Who should provide help How long to keep data How and how often to get data back Why isn’t all safe in the cloud Why storing in Australia is important (Dropbox stores in the US) The CEO view: Business Continuity and Risk Management instead of just backup Cyber insurance Ransomware attacks Example case of a disaster that really happened What about the new “Notifiable Data Breach” law in Australia What to backup how Practical tips How to get attention for the topic   Cloud overall (see graphs at the bottom of this document) Benefits for customers: agility, flexibility, choice, PAYG Public, Private, Hybrid cloud Cloud is a journey instead of destination Fear, trust, proof, procedures, risk management   Cloud storage vs. cloud backup comparing different tools Cloud synchronisation services: Dropbox, Box, Google Drive, Microsoft OneDrive Many of them don’t have versioning (Dropbox EVH has 120 days) What’s deleted on one device gets deleted on another as well upon connection Hard to get anything back from the cloud sync providers Proper cloud backup provides versioning in all possible local retention possibilities and clients can get back their data as part of the service by themselves of their partner   How does a typical IT setup of Small Biz Owners look like On-premises: notebook(s), printing, potentially a server for files or databases Cloud services like Office 365, Google G Suite, AWS, Xero/MYOB, CRM, specific apps   Who should provide help Managed Service Providers (MSPs) deliver IT as a service based on SMB demands including backup, but also on-premise infrastructure from capex to opex The Small Biz owner should focus on the business outcome, not on technology   How long to keep data? Legal companies often require 7 years, some even longer That makes moving between different backup technologies rather difficult   How and how often to get data back? User can retrieve data by themselves or via partner Restoring should be free as part of the backup pricing, not to pay extra for every restore According to a worldwide study of 2016, about 6% of restored data comes from accidently deleted files Database operation restoration is slightly less   Why isn’t all safe in the cloud Tricky balance: hard to get anything deleted when needed (e.g. wrong posting) while on the other side hard to find what has been there when needed Cloud sync providers run their own backups to provide their service with best possible availability rather than helping clients getting it back (even against $)   Why storing in Australia is important Many industries require data to be stored in Oz like healthcare for legal reasons Even NZ companies often cannot store their data in Australia The marketing departments of those companies often store data on Dropbox (no-go!) Storing data encrypted in the US is possible, but NSA might want to see on the way back Dropbox stores in the US for the premium experience vs. local law, but how to proof? Microsoft runs Azure in Australia and not in New Zealand (yet)   The CEO view: Business Continuity and Risk Management instead of just backup Worldwide standard ISO 31000 has been created by Australia/NZ initially (2004) Provides principles and generic guidelines on risk management Example: 6% of data restored * cost of getting it back (but how to estimate?)   Cyber Insurance Some see backup like an insurance, but the reality is different The cyber insurance covers for lost revenue in a data loss, but doesn’t get the data back The backup providers gets the data back, but doesn’t cover lost revenue It is a complementing solution usually not offered together   Ransomware attacks Talking about a concrete example Can arrive per email or even inside an internet connected printer or scanner   Example case of a disaster that really happened Usually we talk about statistics that 60% of SMB companies go out of businesses after a severe disaster within a year, 80% don’t survive the second year Spoken to a victim of a real story at the Australian Information Security Association (AISA)   What about the new “Notifiable Data Breach” law in Australia In place since 22 February 2018 to report data breaches within 30 days Most often data breaches haven’t been made public not to destroy brand value Fines now official: $360K for individual and $1.8M for companies if not reported on time Many IT resellers told at an ARN event that their customers are not ready yet European General Data Protection Regulation (GDPR) from 25 May goes even beyond, it aims primarily to give control back to citizens and residents over their personal data View of the Ransomware programmers: “if you don’t pay me in Bitcoin, then I will breach your data and force you to pay the fines”   What to backup how Different areas: Cloud Backup, Cloud DR, Endpoint Backup, Cloud to Cloud On-premise server into the cloud using leading software such as Veeam Some services are already in the cloud such as Exchange into Office 365 Even Office 365 is not covered by backup, therefore it needs e.g. SkyKick   Practical tips Forget about the rotating external HDDs which often have unencrypted, easily visible files in it Most important is redundancy, even use RAID 1 in a NAS to ensure availability Guidance rule of 3-2-1: 3 copies of the data, 2 kind of media, 1 offsite location Think to fail: what happens if building gone, NAS drive stolen, computer hacked Think to be back fast not to lose revenue and keep serving customers: use Disaster-Recovery-as-a-Service Use risk management to calculate the probability with the options Making sure you can not only save but extract the data   How to get attention for the topic Turning from backup (like dentist) into business continuity (winning smile) Business consultants often convince owners better than box moving IT resellers “World Backup Day” every 31 March (even backward) to raise attention to the topic Software vendor Veeam has even taken the 30 March as “Availability Day” to make the point not “you don’t have backup” but rather “you want to aim for availability”   To find out more, go to their website: www.keepitsafe.com or contact sales@cloudrecover.com.au  

Wer Technik gebraucht kauft, schont die Umwelt und kann ordentlich Geld sparen. Doch nicht in jeder Gerätekategorie lohnt sich das. Hannes Czerulla hat sich vor allem Smartphones und Tablets angeschaut und gibt in c't uplink Tipps, wie man die besten Schnäppchen findet und welche Gefahren beim Gebrauchtkauf lauern. Unser Speicher-Experte Lutz Labs hat sich intensiv mit Monitoring-Tools für SSDs und HDDs auseinandergesetzt. Wer seine Platten überwacht, weiß häufig schon vorher, wenn ein Ausfall droht. Praktisch für den Familien-Admin: Eines der Tools verschickt Mails mit Statushinweisen – so bekommt man mit, wenn der Rechner bei den Eltern kurz vorm Exitus steht. Zum Schluss putzen wieder die Roboter das uplink-Studio: Stefan Porteck hat sechs smarte Staubsaugerroboter getestet und zeigt uns, warum sich langhaarige Mitbewohner besser mit Deebot Ozmo 930 und iRobot Roomba 980 vertragen als mit den anderen Saugern im Test. Mit dabei: Achim Barczok, Stefan Porteck, Lutz Labs und Hannes Czerulla Die c't 06/18 gibt's am Kiosk, im Browser und in der c't-App für iOS und Android. Alle früheren Episoden unseres Podcasts gibt es unter www.ct.de/uplink.

Wer Technik gebraucht kauft, schont die Umwelt und kann ordentlich Geld sparen. Doch nicht in jeder Gerätekategorie lohnt sich das. Hannes Czerulla hat sich vor allem Smartphones und Tablets angeschaut und gibt in c't uplink Tipps, wie man die besten Schnäppchen findet und welche Gefahren beim Gebrauchtkauf lauern. Unser Speicher-Experte Lutz Labs hat sich intensiv mit Monitoring-Tools für SSDs und HDDs auseinandergesetzt. Wer seine Platten überwacht, weiß häufig schon vorher, wenn ein Ausfall droht. Praktisch für den Familien-Admin: Eines der Tools verschickt Mails mit Statushinweisen – so bekommt man mit, wenn der Rechner bei den Eltern kurz vorm Exitus steht. Zum Schluss putzen wieder die Roboter das uplink-Studio: Stefan Porteck hat sechs smarte Staubsaugerroboter getestet und zeigt uns, warum sich langhaarige Mitbewohner besser mit Deebot Ozmo 930 und iRobot Roomba 980 vertragen als mit den anderen Saugern im Test. Mit dabei: Achim Barczok, Stefan Porteck, Lutz Labs und Hannes Czerulla Die c't 06/18 gibt's am Kiosk, im Browser und in der c't-App für iOS und Android. Alle früheren Episoden unseres Podcasts gibt es unter www.ct.de/uplink.

Wer Technik gebraucht kauft, schont die Umwelt und kann ordentlich Geld sparen. Doch nicht in jeder Gerätekategorie lohnt sich das. Hannes Czerulla hat sich vor allem Smartphones und Tablets angeschaut und gibt in c't uplink Tipps, wie man die besten Schnäppchen findet und welche Gefahren beim Gebrauchtkauf lauern. Unser Speicher-Experte Lutz Labs hat sich intensiv mit Monitoring-Tools für SSDs und HDDs auseinandergesetzt. Wer seine Platten überwacht, weiß häufig schon vorher, wenn ein Ausfall droht. Praktisch für den Familien-Admin: Eines der Tools verschickt Mails mit Statushinweisen – so bekommt man mit, wenn der Rechner bei den Eltern kurz vorm Exitus steht. Zum Schluss putzen wieder die Roboter das uplink-Studio: Stefan Porteck hat sechs smarte Staubsaugerroboter getestet und zeigt uns, warum sich langhaarige Mitbewohner besser mit Deebot Ozmo 930 und iRobot Roomba 980 vertragen als mit den anderen Saugern im Test. Mit dabei: Achim Barczok, Stefan Porteck, Lutz Labs und Hannes Czerulla Die c't 06/18 gibt's am Kiosk, im Browser und in der c't-App für iOS und Android. Alle früheren Episoden unseres Podcasts gibt es unter www.ct.de/uplink.

We review the information about Spectre & Meltdown thus far, we look at NetBSD memory sanitizer progress, Postgres on ZFS & show you a bit about NomadBSD. This episode was brought to you by Headlines Meltdown Spectre Official Site (https://meltdownattack.com/) Kernel-memory-leaking Intel processor design flaw forces Linux, Windows redesign (https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/) Intel's official response (https://newsroom.intel.com/news/intel-responds-to-security-research-findings/) The Register mocks intels response with pithy annotations (https://www.theregister.co.uk/2018/01/04/intel_meltdown_spectre_bugs_the_registers_annotations/) Intel's Analysis PDF (https://newsroom.intel.com/wp-content/uploads/sites/11/2018/01/Intel-Analysis-of-Speculative-Execution-Side-Channels.pdf) XKCD (https://xkcd.com/1938/) Response from FreeBSD (https://lists.freebsd.org/pipermail/freebsd-security/2018-January/009719.html) FreeBSD's patch WIP (https://reviews.freebsd.org/D13797) Why Raspberry Pi isn't vulnerable to Spectre or Meltdown (https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/) Xen mitigation patches (https://lists.xenproject.org/archives/html/xen-devel/2018-01/msg00110.html) Overview of affected FreeBSD Platforms/Architectures (https://wiki.freebsd.org/SpeculativeExecutionVulnerabilities) Groff's response (https://twitter.com/GroffTheBSDGoat/status/949372300368867328) ##### We'll cover OpenBSD, NetBSD, and DragonflyBSD's responses in next weeks episode. *** ###The LLVM Memory Sanitizer support work in progress (https://blog.netbsd.org/tnf/entry/the_llvm_memory_sanitizer_support) > In the past 31 days, I've managed to get the core functionality of MSan to work. This is an uninitialized memory usage detector. MSan is a special sanitizer because it requires knowledge of every entry to the basesystem library and every entry to the kernel through public interfaces. This is mandatory in order to mark memory regions as initialized. Most of the work has been done directly for MSan. However, part of the work helped generic features in compiler-rt. Sanitizers > Changes in the sanitizer are listed below in chronological order. Almost all of the changes mentioned here landed upstream. A few small patches were reverted due to breaking non-NetBSD hosts and are rescheduled for further investigation. I maintain these patches locally and have moved on for now to work on the remaining features. NetBSD syscall hooks > I wrote a large patch (815kb!) adding support for NetBSD syscall hooks for use with sanitizers. NetBSD ioctl(2) hooks > Similar to the syscall hooks, there is need to handle every ioctl(2) call. I've created the needed patch, this time shorter - for less than 300kb. New patches still pending for upstream review > There are two corrections that I've created, and they are still pending upstream for review: Add MSan interceptor for fstat(2)](https://reviews.llvm.org/D41637) Correct the setitimer interceptor on NetBSD)](https://reviews.llvm.org/D41502) > I've got a few more local patches that require cleanup before submitting to review. NetBSD basesystem corrections Sanitizers in Go The MSan state as of today Solaris support in sanitizers > I've helped the Solaris team add basic support for Sanitizers (ASan, UBsan). This does not help NetBSD directly, however indirectly it improves the overall support for non-Linux hosts and helps to catch more Linuxisms in the code. Plan for the next milestone > I plan to continue the work on MSan and correct sanitizing of the NetBSD basesystem utilities. This mandates me to iterate over the basesystem libraries implementing the missing interceptors and correcting the current support of the existing ones. My milestone is to build all src/bin programs against Memory Sanitizer and when possible execute them cleanly. This work was sponsored by The NetBSD Foundation. The NetBSD Foundation is a non-profit organization and welcomes any donations to help us continue funding projects and services to the open-source community. Please consider visiting the following URL, and chip in what you can: http://netbsd.org/donations/#how-to-donate (http://netbsd.org/donations/#how-to-donate) *** ##News Roundup ###MWL's 2017 Wrap-Up (https://blather.michaelwlucas.com/archives/3078) > The obvious place to start is my 2016 wrap-up post](https://blather.michaelwlucas.com/archives/2822), where I listed goals for 2017. As usual, these goals were wildly delusional. > The short answer is, my iron was back up to normal. My writing speed wasn't, though. I'd lost too much general health, and needed hard exercise to recover it. Yes, writing requires physical endurance. Maintaining that level of concentration for several hours a day demands a certain level of blood flow to the brain. I could have faked it in a day job, but when self-employed as an artist? Not so much. > Then there's travel. I did my usual BSDCan trip, plus two educational trips to Lincoln City, Oregon. The current political mayhem convinced me that if I wanted to hit EuroBSDCon any time in the next few years, I should do it in the very near future. So I went to Paris, where I promptly got pickpocketed. (Thankfully, they didn't get my passport.) I was actively writing the third edition of Absolute FreeBSD, so I visited BSDCam in Cambridge to get the latest information and a sense of where FreeBSD was going. I also did weekends at Kansas LinuxFest (because they asked and paid for my trip) and Penguicon. > (Because people will ask: why EuroBSDCon and not AsiaBSDCon? A six-hour transatlantic flight requires that I take a substantial dose of heavy-grade tranquilizers. I'm incapable of making intelligent decisions while on those drugs, or for several hours afterward. They don't last long enough for twelve-hour flight to Japan, so I need to be accompanied by someone qualified to tell me when I need to take the next dose partway through the flight. This isn't a predetermined time that I can set an alarm for; it depends on how the clonazepam affects me at those altitudes. A drug overdose while flying over the North Pole would be bad. When I can arrange that qualified companion, I'll make the trip.) > I need most of the preceding week to prepare for long trips. I need the following week to recover from time shifts and general exhaustion. Additionally, I have to hoard people juice for a few weeks beforehand so I can deal with folks during these expeditions. Travel disrupts my dojo time as well, which impacts my health. > Taken as a whole: I didn't get nearly as much done as I hoped. I wrote more stories, but Kris Rusch bludgeoned me into submitting them to trad markets. (The woman is a brute, I tell you. Cross her at your peril.) Among my 2017 titles, my fiction outsold the tech books. No, not Prohibition Orcs–all four of the people who buy those love them, but the sales tell me I've done something wrong with those tales. My cozy mystery git commit murder outsold Relayd and Httpd Mastery. But what outdid them both, as well as most of my older books? What title utterly dominated my sales for the last quarter of the year? It was of course, my open source software political satire disguised as porn Savaged by Systemd: an Erotic Unix Encounter. (https://www.michaelwarrenlucas.com/index.php/romance#sbs) > I can't believe I just wrote that paragraph. The good news is, once I recovered from EuroBSDCon, my writing got better. I finished Absolute FreeBSD, 3rd edition and submitted it to the publisher. I wrote the second edition of SSH Mastery (no link, because you can't order it yet.) I'm plowing through git sync murder, the sequel to git commit murder. I don't get to see the new Star Wars movie until I finish GSM, so hopefully that'll be this month. All in all, I wrote 480,200 words in 2017. Most of that was after September. It's annoyingly close to breaking half a million, but after 2016's scandalous 195,700, I'll take it. *** ###PG Phriday: Postgres on ZFS (https://blog.2ndquadrant.com/pg-phriday-postgres-zfs/) > ZFS is a filesystem originally created by Sun Microsystems, and has been available for BSD over a decade. While Postgres will run just fine on BSD, most Postgres installations are historically Linux-based systems. ZFS on Linux has had much more of a rocky road to integration due to perceived license incompatibilities. > As a consequence, administrators were reluctant or outright refused to run ZFS on their Linux clusters. It wasn't until OpenZFS was introduced in 2013 that this slowly began to change. These days, ZFS and Linux are starting to become more integrated, and Canonical of Ubuntu fame even announced direct support for ZFS in their 16.04 LTS release. > So how can a relatively obscure filesystem designed by a now-defunct hardware and software company help Postgres? Let's find out! Eddie waited til he finished high school > Old server hardware is dirt cheap these days, and make for a perfect lab for testing suspicious configurations. This is the server we'll be using for these tests for those following along at home, or want some point of reference: Dell R710 x2 Intel X5660 CPUs, for up to 24 threads 64GB RAM x4 1TB 7200RPM SATA HDDs H200 RAID card configured for Host Bus Adapter (HBA) mode 250GB Samsung 850 EVO SSD > The H200 is particularly important, as ZFS acts as its own RAID system. It also has its own checksumming and other algorithms that don't like RAID cards getting in the way. As such, we put the card itself in a mode that facilitates this use case. > Due to that, we lose out on any battery-backed write cache the RAID card might offer. To make up for it, it's fairly common to use an SSD or other persistent fast storage to act both as a write cache, and a read cache. This also transforms our HDDs into hybrid storage automatically, which is a huge performance boost on a budget. She had a guitar and she taught him some chords > First things first: we need a filesystem. This hardware has four 1TB HDDs, and a 250GB SSD. To keep this article from being too long, we've already placed GPT partition tables on all the HDDs, and split the SSD into 50GB for the OS, 32GB for the write cache, and 150GB for the read cache. A more robust setup would probably use separate SSDs or a mirrored pair for these, but labs are fair game. They moved into a place they both could afford > Let's start by getting a performance baseline for the hardware. We might expect peak performance at 12 or 24 threads because the server has 12 real CPUs and 24 threads, but query throughput actually topped out at concurrent 32 processes. We can scratch our heads over this later, for now, we can consider it the maximum capabilities of this hardware. Here's a small sample: ``` $> pgbench -S -j 32 -c 32 -M prepared -T 20 pgbench ... tps = 264661.135288 (including connections establishing) tps = 264849.345595 (excluding connections establishing) ``` So far, this is pretty standard behavior. 260k prepared queries per second is great read performance, but this is supposed to be a filesystem demonstration. Let's get ZFS involved. + The papers said Ed always played from the heart Let's repeat that same test with writes enabled. Once that happens, filesystem syncs, dirty pages, WAL overhead, and other things should drastically reduce overall throughput. That's an expected result, but how much are we looking at, here? ``` $> pgbench -j 32 -c 32 -M prepared -T 10 pgbench ... tps = 6153.877658 (including connections establishing) tps = 6162.392166 (excluding connections establishing) ``` SSD cache or not, storage overhead is a painful reality. Still, 6000 TPS with writes enabled is a great result for this hardware. Or is it? Can we actually do better? Consider the Postgres fullpagewrites parameter. Tomas Vondra has written about it in the past as a necessity to prevent WAL corruption due to partial writes. The WAL is both streaming replication and crash recovery, so its integrity is of utmost importance. As a result, this is one parameter almost everyone should leave alone. ZFS is Copy on Write (CoW). As a result, it's not possible to have a torn page because a page can't be partially written without reverting to the previous copy. This means we can actually turn off fullpagewrites in the Postgres config. The results are some fairly startling performance gains: $> pgbench -j 32 -c 32 -M prepared -T 10 pgbench tps = 10325.200812 (including connections establishing) tps = 10336.807218 (excluding connections establishing) That's nearly a 70% improvement. Due to write amplification caused by full page writes, Postgres produced 1.2GB of WAL files during a 1-minute pgbench test, but only 160MB with full page writes disabled. To be fair, a 32-thread pgbench write test is extremely abusive and certainly not a typical usage scenario. However, ZFS just ensured our storage a much lower write load by altering one single parameter. That means the capabilities of the hardware have also been extended to higher write workloads as IO bandwidth is not being consumed by WAL traffic. + They both met movie stars, partied and mingled Astute readers may have noticed we didn't change the default ZFS block size from 128k to align with the Postgres default of 8kb. As it turns out, the 128kb blocks allow ZFS to better combine some of those 8kb Postgres pages to save space. That will allow our measly 2TB to go a lot further than is otherwise possible. Please note that this is not de-duplication, but simple lz4 compression, which is nearly real-time in terms of CPU overhead. De-duplication on ZFS is currently an uncertain bizzaro universe populated with misshapen horrors crawling along a broken landscape. It's a world of extreme memory overhead for de-duplication tables, and potential lost data due to inherent conflicts with the CoW underpinnings. Please don't use it, let anyone else use it, or even think about using it, ever. + They made a record and it went in the chart We're still not done. One important aspect of ZFS as a CoW filesystem, is that it has integrated snapshots. Consider the scenario where a dev is connected to the wrong system and drops what they think is a table in a QA environment. It turns out they were in the wrong terminal and just erased a critical production table, and now everyone is frantic. + The future was wide open It's difficult to discount an immediately observable reduction in write overhead. Snapshots have a multitude of accepted and potential use cases, as well. In addition to online low-overhead compression, and the hybrid cache layer, ZFS boasts a plethora of features we didn't explore. Built-in checksums with integrated self-healing suggest it isn't entirely necessary to re-initialize an existing Postgres instance to enable checksums. The filesystem itself ensures checksums are validated and correct, especially if we have more than one drive resource in our pool. It even goes the extra mile and actively corrects inconsistencies when encountered. I immediately discounted ZFS back in 2012 because the company I worked for at the time was a pure Linux shop. ZFS was only available using the FUSE driver back then, meaning ZFS only worked through userspace with no real kernel integration. It was fun to tinker with, but nobody sane would use that on a production server of any description. Things have changed quite drastically since then. I've stopped waiting for btrfs to become viable, and ZFS has probably taken the throne away from XFS as my filesystem of choice. Future editions of the Postgres High Availability Cookbook will reflect this as well. Postgres MVCC and ZFS CoW seem made for each other. I'm curious to see what will transpire over the next few years now that ZFS has reached mainstream acceptance in at least one major Linux distribution. NomadBSD (https://github.com/mrclksr/NomadBSD) About NomadBSD is a live system for flash drives, based on FreeBSD. Screenshots http://freeshell.de/~mk/download/nomadbsd-ss1.png http://freeshell.de/~mk/download/nomadbsd-ss2.png Requirements for building the image A recent FreeBSD system Requirements for running NomadBSD A 4GB (or more) flash drive A System capable running FreeBSD 11.1 (amd64) Building the image ~~ csh # make image ~~ Writing the image to an USB memory stick ~~ csh # dd if=nomadbsd.img of=/dev/da0 bs=10240 conv=sync ~~ Resize filesystem to use the entire USB memory Boot NomadBSD into single user mode, and execute: ~~ # gpart delete -i 2 da0s1 # gpart resize -i 1 da0 # gpart commit da0s1 ~~ Determine the partition size in megabytes using fdisk da0 and calculate the remaining size of da0s1a: = - . ~~ # gpart resize -i 1 -s M da0s1 # gpart add -t freebsd-swap -i 2 da0s1 # glabel label NomadBSDsw da0s1b # service growfs onestart # reboot ~~ FreeBSD forum thread (https://forums.freebsd.org/threads/63888/) A short screen capture video of the NomadBSD system running in VirtualBox (https://freeshell.de/~mk/download/nomad_capture.mp4) *** ##Beastie Bits Coolpkg, a package manager inspired by Nix for OpenBSD (https://github.com/andrewchambers/coolpkg) zrepl - ZFS replication (https://zrepl.github.io/) OpenBSD hotplugd automount script (https://bijanebrahimi.github.io/blog/openbsd-hotplugd-scripting.html) Ancient troff sources vs. modern-day groff (https://virtuallyfun.com/2017/12/22/learn-ancient-troff-sources-vs-modern-day-groff/) Paypal donation balance and status.. thanks everyone! (http://lists.dragonflybsd.org/pipermail/users/2017-December/313752.html) Supervised FreeBSD rc.d script for a Go daemon (updated in last few days) (https://redbyte.eu/en/blog/supervised-freebsd-init-script-for-go-deamon/) A Brief History of sed (https://blog.sourcerer.io/a-brief-history-of-sed-6eaf00302ed) Flamegraph: Why does my AWS instance boot so slow? (http://www.daemonology.net/timestamping/tslog-c5.4xlarge.svg) *** ##Feedback/Questions Jeremy - Replacing Drive in a Zpool (http://dpaste.com/319593M#wrap) Dan's Blog (https://dan.langille.org/2017/08/16/swapping-5tb-in-3tb-out/) Tim - Keeping GELI key through reboot (http://dpaste.com/11QTA06) Brian - Mixing 2.5 and 3.5 drives (http://dpaste.com/2JQVD10#wrap) Troels - zfs swap on FreeBSD (http://dpaste.com/147WAFR#wrap) ***

This episode gives you the full dose of BSDCan 2017 recap as well as a blog post on conference speaking advice. Headlines Pre-conference activities: Goat BoF, FreeBSD Foundation Board Meeting, and FreeBSD Journal Editorial Board Meeting The FreeBSD Foundation has a new President as Justin Gibbs is busy this year with building a house, so George Neville-Neil took up the task to serve as President, with Justin Gibbs as Secretary. Take a look at the updated Board of Directors (https://www.freebsdfoundation.org/about/board-of-directors/). We also have a new staff member (https://www.freebsdfoundation.org/about/staff/): Scott Lamons joined the Foundation team as senior program manager. Scott's work for the Foundation will focus on managing and evangelizing programs for advanced technologies in FreeBSD including preparing project plans, coordinating resources, and facilitating interactions between commercial vendors, the Foundation, and the FreeBSD community. The Foundation also planned various future activities, visits of upcoming conferences, and finding new ways to support and engage the community. The Foundation now has interns in the form of co-op students from the University of Waterloo, Canada. This is described further in the May 2017 Development Projects Update (https://www.freebsdfoundation.org/blog/may-2017-development-projects-update/). Both students (Siva and Charlie) were also the conference, helping out at the Foundation table, demonstrating the tinderbox dashboard. Follow the detailed instructions (https://www.freebsdfoundation.org/news-and-events/blog/blog-post/building-a-physical-freebsd-build-status-dashboard/) to build one of your own. The Foundation put out a call for Project Proposal Solicitation for 2017 (https://www.freebsdfoundation.org/blog/freebsd-foundation-2017-project-proposal-solicitation/). If you think you have a good proposal for work relating to any of the major subsystems or infrastructure for FreeBSD, we'd be happy to review it. Don't miss the deadlines for travel grants to some of the upcoming conferences. You can find the necessary forms and deadlines at the Travel Grant page (https://www.freebsdfoundation.org/what-we-do/travel-grants/travel-grants/) on the Foundation website. Pictures from the Goat BoF can be found on Keltia.net (https://assets.keltia.net/photos/BSDCan-2017/Royal%20Oak/index.html) Overlapping with the GoatBoF, members of the FreeBSD Journal editorial board met in a conference room in the Novotel to plan the upcoming issues. Topics were found, authors identified, and new content was discussed to appeal to even more readers. Check out the FreeBSD Journal website (https://www.freebsdfoundation.org/journal/) and subscribe if you like to support the Foundation in that way. FreeBSD Devsummit Day 1 & 2 (https://wiki.freebsd.org/DevSummit/201706) The first day of the Devsummit began with introductory slides by Gordon Tetlow, who organized the devsummit very well. Benno Rice of the FreeBSD core team presented the work done on the new Code of Conduct, which will become effective soon. A round of Q&A followed, with positive feedback from the other devsummit attendees supporting the new CoC. After that, Allan Jude joined to talk about the new FreeBSD Community Proposal (FCP) (https://github.com/freebsd/fcp) process. Modelled after IETF RFCs, Joyent RFDs, and Python PEP, it is a new way for the project to reach consensus on the design or implementation of new features or processes. The FCP repo contains FCP#0 that describes the process, and a template for writing a proposal. Then, the entire core team (except John Baldwin, who could not make it this year) and core secretary held a core Q&A session, Answering questions, gathering feedback and suggestions. After the coffee break, we had a presentation about Intel's QAT integration in FreeBSD. When the lunch was over, people spread out into working groups about BearSSL, Transport (TCP/IP), and OpenZFS. OpenZFS working group (https://pbs.twimg.com/media/DBu_IMsWAAId2sN.jpg:large): Matt Ahrens lead the group, and spent most of the first session providing a status update about what features have been recently committed, are out for review, on the horizon, or in the design phase. Existing Features Compressed ARC Compressed Send/Recv Recently Upstreamed A recent commit improved RAID-Z write speeds by declaring writes to padding blocks to be optional, and to always write them if they can be aggregated with the next write. Mostly impacts large record sizes. ABD (ARC buffer scatter/gather) Upstreaming In Progress Native Encryption Channel Programs Device Removal (Mirrors and Stripes) Redacted Send/recv Native TRIM Support (FreeBSD has its own, but this is better and applies to all ZFS implementations) Faster (mostly sequential) scrub/resilver DRAID (A great deal of time was spent explaining how this works, with diagrams on the chalk board) vdev metadata classes (store metadata on SSDs with data is on HDDs, or similar setups. Could also be modified to do dedup to SSD) Multi-mount protection (“safe import”, for dual-headed storage shelves) zpool checkpoint (rollback an entire pool, including zfs rename and zfs destroy) Further Out Import improvements Import with missing top-level vdevs (some blocks unreadable, but might let you get some data) Improved allocator performance -- vdev spacemap log ZIL performance Persistent L2ARC ZSTD Compression Day 2 Day two started with the Have/Want/Need session for FreeBSD 12.0. A number of features that various people have or are in the process of building, were discussed with an eye towards upstreaming them. Features we want to have in time for 12.0 (early 2019) were also discussed. After the break was the Vendor summit, which continued the discussion of how FreeBSD and its vendors can work together to make a better operating system, and better products based on it After lunch, the group broke up into various working groups: Testing/CI, Containers, Hardening UFS, and GELI Improvements Allan lead the GELI Improvements session. The main thrust of the discussions was fixing an outstanding bug in GELI when using both key slots with passphrases. To solve this, and make GELI more extensible, the metadata format will be extended to allow it to store more than 512 bytes of data (currently 511 bytes are used). The new format will allow arbitrarily large metadata, defined at creation time by selecting the number of user key slots desired. The new extended metadata format will contain mostly the same fields, except the userkey will no longer be a byte array of IV-key, Data-key, HMAC, but a struct that will contain all data about that key This new format will store the number of pkcs5v2 iterations per key, instead of only having a single location to store this number for all keys (the source of the original bug) A new set of flags per key, to control some aspects of the key (does it require a keyfile, etc), as well as possibly the role of the key. An auxdata field related to the flags, this would allow a specific key with a specific flag set, to boot a different partition, rather than decrypt the main partition. A URI to external key material is also stored per key, allowing GELI to uniquely identify the correct data to load to be able to use a specific decryption key And the three original parts of the key are stored in separate fields now. The HMAC also has a type field, allowing for a different HMAC algorithm to be used in the future. The main metadata is also extended to include a field to store the number of user keys, and to provide an overall HMAC of the metadata, so that it can be verified using the master key (provide any of the user keys) Other topics discussed: Ken Merry presented sedutil, a tool for managing Self Encrypting Drives, as may be required by certain governments and other specific use cases. Creating a deniable version of GELI, where the metadata is also encrypted The work to implemented GELI in the UEFI loader was discussed, and a number of developers volunteered to review and test the code Following the end of the Dev Summit, the “Newcomers orientation and mentorship” session was run by Michael W. Lucas, which attempts to pair up first time attendees with oldtimers, to make sure they always know a few people they can ask if they have questions, or if they need help getting introduced to the right people. News Roundup Conference Day 1 (http://www.bsdcan.org/2017/schedule/day_2017-06-09.en.html) The conference opened with some short remarks from Dan Langille, and then the opening keynote by Dr Michael Geist, a law professor at the University of Ottawa where he holds the Canada Research Chair in Internet and E-commerce Law. The keynote focused on what some of the currently issues are, and how the technical community needs to get involved at all levels. In Canada especially, contacting your representatives is quite effective, and when it does not happen, they only hear the other side of the story, and often end up spouting talking points from lobbyists as if they were facts. The question period for the keynote ran well overtime because of the number of good questions the discussion raised, including how do we fight back against large telcos with teams of lawyers and piles of money. Then the four tracks of talks started up for the day The day wrapped up with the Work In Progress (WIP) session. Allan Jude presented work on ZSTD compression in ZFS Drew Gallatin presented about work at Netflix on larger mbufs, to avoid the need for chaining and to allow more data to be pushed at once. Results in an 8% CPU time reduction when pushing 90 gbps of TLS encrypted traffic Dan Langille presented about letsencrypt (the acme.sh tool specifically), and bacula Samy Al Bahra presented about Concurrency Kit *** Conference Day 2 (http://www.bsdcan.org/2017/schedule/day_2017-06-10.en.html) Because Dan is a merciful soul, BSDCan starts an hour later on the second day Another great round of talks and BoF sessions over lunch The hallway track was great as always, and I spent most of the afternoon just talking with people Then the final set of talks started, and I was torn between all four of them Then there was the auction, and the closing party *** BSDCan 2017 Auction Swag (https://blather.michaelwlucas.com/archives/2962) Groff Fundraiser Pins: During the conference, You could get a unique Groff pin, by donating more than the last person to either the FreeBSD or OpenBSD foundation Michael W. Lucas and his wife Liz donated some interesting home made and local items to the infamous Charity Auction I donated the last remaining copy of the “Canadian Edition” of “FreeBSD Mastery: Advanced ZedFS”, and a Pentium G4400 (Skylake) CPU (Supports ECC or non-ECC) Peter Hessler donated his pen (Have you read “Git Commit Murder” yet?) Theo De Raadt donated his autographed conference badge David Maxwell donated a large print of the group photo from last years FreeBSD Developers Summit, which was purchased by Allan There was also a FreeBSD Dev Summit T-Shirt (with the Slogan: What is Core doing about it?) autographed by all of the attending members of core, with a forged jhb@ signature. Lastly, someone wrote “I

Von BLINDzeln kann man sich fuer seine Computer ein Sicherungssystem bauen lassen, das nur noch ueber ein paar Tasten angesteuert wird und auf Knopfdruck die Speichermedien physikalisch vom System komplett abtrennt oder auch wieder damit verbindet. Bis zu vier Laufwerke als SSDs, HDDs, SSHDDs koennen in diesem System geschaltet werden.

IBM Atom HDD, Intel Optane SSD Drive, Micro-transations in games are out of control, Fidget Cube Review, Nintendo Switch Review, Chrome updates and Jarron returns to the fold, Zelda pre-review, 8 Apps that help you get out of bed, Apple's new mystery device, Net Neutrality is good or bad?

Don Grabski, Director of Product Management for Seagate, joins us in this episode of Conversations in the Cloud to discuss how Seagate technology incorporates Intel® Enterprise Edition for Lustre* software, into its market-leading ClusterStor® storage architecture for high-performance computing (HPC). Lustre software is at the heart of most HPC storage systems, and powers 40 percent of the world’s fastest supercomputers. In this interview, Don highlights how Seagate’s HDDs, SSDs, and data storage systems are purpose-built for enterprise and data center performance, scalability, reliability, and security. To learn more go to www.seagate.com or follow Seagate on Twitter at twitter.com/seagate.

Sony sent out invites for the 4.5 beta last week and in this episode we go over all of the features. One of the major ones is support for external HDDs which a lot of people are ... Read More

We actually talk about Nintendo, The Company. Along with many other things such as HDDs in consoles, rabbit holes, and mustaches. Best GAMING Podcast ever.

Alberto Farronato, the Director of Product Marketing for Cloud Infrastructure Storage and Availability at VMware, stops by to chat about the recent launch of the VMware* Virtual SAN* (VSAN), which provides a software-defined storage tier that pools compute and DAS resources through the server hypervisor. By clustering server direct-attached HDDs and SSDs, VSAN creates a distributed, shared data store at the hypervisor layer that is designed and optimized for virtual machines. For more information, visit www.vmware.com/now.

Study Shows Playing Video Games Really Can Make Your Brain Bigger Lady Gaga to Sing in Space — Seriously Blockbuster to Close Its Last Remaining Stores in the U.S 250 Hard Drives Used To Make One Epic F1 Car Aussie sales of Windows Phone double as Android sinks Apple reveals Aus government requests for user data Microsoft arrives at top 5 CEO shortlist Apple's new OS X buggy with Western Digital drives Helium-filled HDDs: a data-centre game changer? Katy Perry overtakes Justin Bieber on Twitter followers Google says floating barge for showing off new tech Woz: I Wish To God That Apple And Google Were Partners Australian Electoral Commission Says E-Voting Is Coming, But It's Hard : Pebble smartwatches bag iOS 7 app, shiny new SDK Microsoft Australia Concerned About Turnbull's NBN Googlers say “Screw you” to NSA, company encrypts internal network YouTube Starts Rolling Out Its New Commenting System Based On Google+

Study Shows Playing Video Games Really Can Make Your Brain Bigger Lady Gaga to Sing in Space — Seriously Blockbuster to Close Its Last Remaining Stores in the U.S 250 Hard Drives Used To Make One Epic F1 Car Aussie sales of Windows Phone double as Android sinks Apple reveals Aus government requests for user data Microsoft arrives at top 5 CEO shortlist Apple's new OS X buggy with Western Digital drives Helium-filled HDDs: a data-centre game changer? Katy Perry overtakes Justin Bieber on Twitter followers Google says floating barge for showing off new tech Woz: I Wish To God That Apple And Google Were Partners Australian Electoral Commission Says E-Voting Is Coming, But It's Hard US Authorities Approve Use Of Electronics On Flights A Future Internet Might Not Use Servers Wrist assured, coders: Pebble smartwatches bag iOS 7 app, shiny new SDK Microsoft Australia Concerned About Turnbull's NBN Googlers say “Screw you” to NSA, company encrypts internal network YouTube Starts Rolling Out Its New Commenting System Based On Google+ --- Send in a voice message: https://anchor.fm/aussietechheads/message

Phil Edwards, Andy Blume and Daniel Olivares are back in the studio with this week's look at all things Geek. Show Notes: Seven's The Man With The Biggest Testicles documentary grips viewers [News.com.au] Thodey says ispONE collapse is unacceptable [AFR] The AFL And Telstra Are Working On A Google Glass App [Gizmodo Australia] NAB breaks up with teller cash drawers [The Age] Revealed: UK secretly arrested 16-year old boy for world's 'biggest' DDoS-attack [RT News] Finally, we won't have to power off during takeoff and landing [Ars Technica] Western Digital refreshes MyBook external HDDs, offers 4TB for $180 [Engadget] Candy Crush May Be Worth More Than $5 Billion After Its Secret IPO [The Wire] @Horse_ebooks is a human performance [The Verge] Google Turns 15: Google Doodle Lets You Whack a Piñata (Plus: Fun Easter Egg) [Time] Android is five years old today [The Verge] iMessage For Android Sounds Great But It's A Serious Security Issue: Researchers Explain Why You Should Avoid it Like The Plague [International Digital Times] iPhone map app directs Fairbanks drivers onto airport taxiway [Alaska Dispatch] Fake Apple Ad Says IOS 7 Will Make Your IPhone Waterproof And People Fell For It [Business Insider] Apple iOS 7 makes some users literally SICK. As in puking, not upset [The Register] Apple TVs can now be set up just by tapping them with an iPhone [The Verge] Australian TV Networks Haven't Learned A Damn-Thing From Piracy [Gizmodo Australia] Fox Will Air 'Gotham' TV Show Exploring History of Batman's Commissioner Gordon [/Film] Creators of 'Breaking Bad' and 'House' Close Deal on New CBS Detective Drama 'Battle Creek' [Laughing Squid] A rebel in the house [The Age] Something we mentioned in the show but missing in the Show Notes? Let us know via our Contact Page. Songs We Played: Ratcat - "Don't Go Now" [iTunes] The Angels - "Am I Ever Gonna See Your Face Again" [iTunes] Twisted Sister - "We're Not Gonna Take It" [iTunes] The Avalanches - "Frontier Psychiatrist" [iTunes] R.E.M. - "Man On The Moon" [iTunes] The KLF - "Justified And Ancient" [YouTube] Questions, Comments, Feedback and Suggestions are all welcome. Website - http://geeksinterrupted.fm Facebook - https://www.facebook.com/GeeksInterrupted Twitter - https://twitter.com/GeeksOnAir Voicemail - http://www.speakpipe.com/GeeksInterrupted If you enjoyed this episode head on over to iTunes and kindly leave us a rating, a review and subscribe.

Lose Festplatten auf dem Schreibtisch war gestern. Doch die Gehäuse für externe HDDs sind nicht nur schön anzusehen sondern können auch als Mediaplayer in's heimische Netzwerk integriert werden und sogar Backup-Aufgaben übernehmen. Im Test: 4-fach-Festplatten-Gehäuse 3,5"-SATA mit USB3.0 & eSATA von Xystec (PX-2590-821), 4-fach-Festplatten-Gehäuse 3,5"-SATA mit USB3.0, eSATA & RAID von Xystec (PX-4820-821), Dual-Festplattengehäuse USB2.0 für 2 SATA-Festplatten 3,5" von Xystec (PX-2215-821), NAS Server & Network Storage "NFP 350T" für SATA & BitTorrent von 7links (PX-1189-821), USB 3.0 PCIe Controller "Super Speed" mit bis zu 5 Gbit s von Xystec (PX-4812-821) Produkt-Übersicht: http://www.pearl.de/rtr39 Podcast-Übersicht: http://www.pearl.de/podcast/ Zu den besprochenen Produkten im PEARL-Shop

Direkter Link zum Produkt

Direkter Link zum Produkt

Direkter Link zum Produkt