# ISO Published articles for ISO. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Вышел Tails 7.13 DevFeed: [Вышел Tails 7.13]() Original publisher: [Read original article]() Author: denis-19 Published: 2026-09-17T03:13:50Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [Linux](), [tor](), [Debian](), [browser]() Tags: [2026](), [browser](), [debian](), [gnome](), [iso](), [linux](), [tag-9d72402955ce](), [tag-d2c1bd02300f](), [tails](), [tails-7](), [tails-7-13](), [tor]() ### AI overview Tails 7.13 was released on September 16, 2026. The privacy-focused distribution is based on Debian 13 with Linux 6.12 LTS and GNOME 48, routes outgoing connections through Tor, blocks non-anonymous connections, and supports automatic updates from Tails 7.0-7.12. The release updates the Tor client and Tor Browser and simplifies shutdown in some cases. ### Source excerpt 16 сентября 2026 года состоялся выпуск специализированного дистрибутива Tails 7.13, ориентированного на конфиденциальность, основанного на пакетной базе Debian 13 (ядре Linux 6.12 LTS), поставляемого с рабочим столом GNOME 48 и предназначенного для анонимного выхода в сеть. Выпуск Tails 6.0 произошёл в феврале 2024 года. Версия Tails 7.0 была представлена в сентябре 2025 года. Читать далее ## How Confluent Uses Third-Party Risk Assessments to Support Vendor Due Diligence DevFeed: [How Confluent Uses Third-Party Risk Assessments to Support Vendor Due Diligence]() Original publisher: [Read original article]() Author: Bethany Carter Published: 2026-09-15T16:40:06Z Content type: article Language: en Sources: [Confluent: Data in motion]() Topics: [Security](), [Business Security](), [vulnerability management](), [Cloud]() Tags: [apra](), [automated](), [cloud](), [compliance](), [confluent](), [confluent-cloud](), [data-protection](), [gdpr](), [identity](), [iso](), [nist](), [security](), [standards](), [third-party](), [trust-center](), [vulnerability-management]() ### AI overview Confluent explains how its Trust Center provides third-party risk assessment reports to support vendor security, resilience, compliance, procurement, and customer due diligence. The article describes assessments including ProcessUnity Global Risk Exchange and control mapping to customer frameworks. ### Source excerpt Confluent's Trust Center simplifies vendor risk reviews with CyberGRX, CyberVadis, SIG, CAIQ, and TruSight/KY3P assessments. ## What's New in PHP 8.6 DevFeed: [What's New in PHP 8.6]() Original publisher: [Read original article]() Author: Paul Redmond Published: 2026-09-15T03:00:09Z Content type: release Language: en Sources: [Laravel]() Topics: [PHP](), [DateTime](), [ISO 8601]() Tags: [2026](), [closure](), [feature](), [function](), [interface](), [iso](), [news](), [php](), [php-8-6](), [precision](), [properties](), [release]() ### AI overview An overview of PHP 8.6, scheduled for release on November 19, 2026. The article covers partial function application, the clamp() function, a nanosecond-precision Duration class, readonly property defaults, and parameter DocComments, along with the release timeline and related changes. ### Source excerpt PHP 8.6 arrives November 19, 2026 with partial function application, a clamp() function, a Duration class, readonly property defaults, and new deprecations. The post What's New in PHP 8.6 appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## BTRFS boot failure and easy GUI methods for system recovery DevFeed: [BTRFS boot failure and easy GUI methods for system recovery]() Original publisher: [Read original article]() Author: Alex Genovese Published: 2026-09-04T20:54:40Z Content type: article Language: en Sources: [Fedora Magazine]() Topics: [boot](), [Fedora](), [GUI](), [Linux](), [dnf](), [Software]() Tags: [backup](), [boot](), [btrfs](), [desktop](), [dnf](), [faqs-and-guides](), [fedora-project-community](), [for-system-administrators](), [gui](), [how-to](), [installation](), [iso](), [linux](), [recovery](), [snapshots](), [usb](), [using-hardware](), [using-software](), [workstation]() ### AI overview This how-to article explains GUI-based recovery options for Fedora Linux systems using BTRFS. It covers booting from a USB live ISO, checking whether the operating system uses BTRFS, and recovering earlier system states with snapshot tools such as btrfs-assistant and snapper. ### Source excerpt A few short how-to's with screenshots, showing easy ways to boot up off a USB live ISO and return back to previous points in time with BTRFS ## ISO 42001 Evidence: What Auditors Ask For DevFeed: [ISO 42001 Evidence: What Auditors Ask For]() Original publisher: [Read original article]() Author: info@goteleport.com (Preet Dhatt) Published: 2026-09-03T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [audit](), [AI Development](), [Deployment](), [CI/CD](), [data-governance](), [Monitoring](), [Requirements]() Tags: [ai](), [ai-development](), [article](), [audit](), [ci-cd](), [data-governance](), [deployment](), [eu](), [iso](), [monitoring](), [requirements]() ### AI overview This article explains what auditors look for in ISO 42001 evidence and how organizations can connect access, approvals, infrastructure, CI/CD activity, releases, and production changes into an evidence trail. It also discusses monitoring, human oversight, third-party access, and data governance within an AI Management System. ### Source excerpt Prepare ISO 42001 audit evidence that proves your controls work in practice. ## C++29 -- начало. Встреча ISO C++ в Брно DevFeed: [C++29 -- начало. Встреча ISO C++ в Брно]() Original publisher: [Read original article]() Author: antoshkka (Яндекс) Published: 2026-08-17T07:01:31Z Content type: article Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [C++](), [floating-point](), [implementation]() Tags: [c-plus-plus](), [c-plus-plus-29](), [floating-point](), [fmt](), [format](), [implementation](), [iso](), [standard](), [standard-library](), [tagged-pointers](), [thread](), [threads](), [undefined-behavior](), [undefined-behaviour]() ### AI overview A report on the ISO C++ committee meeting in Brno, where work on C++29 began. It describes plans to organize and clarify documented undefined behavior and ill-formed-no-diagnostic-required cases, along with changes involving constexpr floating-point evaluation and other language rules. ### Source excerpt Привет! На связи Антон Полухин из Техплатформы Городских сервисов Яндекса. Недавно в Брно состоялась встреча международного комитета по стандартизации языка программирования C++, в которой я принимал активное участие. В этот раз началась работа над C++29 и как раз о новинках и хочется рассказать. Читать далее ## XCP-ng 8.3 LTS: Refreshed Installation ISOs DevFeed: [XCP-ng 8.3 LTS: Refreshed Installation ISOs]() Original publisher: [Read original article]() Author: Gaël Duperrey Published: 2026-08-14T08:09:13Z Content type: release Language: en Sources: [XCP-ng Blog]() Topics: [Server](), [Hardware](), [networking](), [Disk image]() Tags: [amd](), [drivers](), [hardware](), [improvements](), [installation](), [iso](), [linux](), [lts](), [networking](), [numa](), [performance](), [release](), [security](), [server](), [storage](), [update](), [updates]() ### AI overview XCP-ng 8.3 LTS has refreshed installation ISOs containing updates released since the previous installer, installer improvements, enhanced hardware support, and other fixes. The article notes that existing up-to-date hosts already include these changes. ### Source excerpt Refreshed ISOs for XCP-ng 8.3 LTS featuring the latest security updates, improvements, and QCOW2 support. ## July 2026 Updates #1 for XCP-ng 8.3 LTS DevFeed: [July 2026 Updates #1 for XCP-ng 8.3 LTS]() Original publisher: [Read original article]() Author: Philippe Coval Published: 2026-07-28T14:32:38Z Content type: release Language: en Sources: [XCP-ng Blog]() Topics: [Security](), [Vulnerabilities](), [Memory Leaks]() Tags: [2026](), [iso](), [leak](), [lts](), [regression](), [release](), [security](), [update](), [updates]() ### AI overview This release provides security and maintenance updates for XCP-ng 8.3 LTS. It updates Xen to address multiple security advisories, fixes a XAPI regression that caused VBD leaks, and includes minor changes needed to build an updated installer ISO. ### Source excerpt This release batch contains a security update for Xen. This update also brings a fix for a XAPI regression causing VBD leaks. Other minor changes were needed to build an updated XCP-ng 8.3 LTS installer (ISO). ## Trust you can verify: Figma is now ISO 42001 certified DevFeed: [Trust you can verify: Figma is now ISO 42001 certified]() Original publisher: [Read original article]() Author: Tushar Badlani Published: 2026-07-01T12:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [ai-governance](), [Figma](), [responsible-ai](), [Security]() Tags: [ai](), [ai-governance](), [figma](), [iso](), [iso-27001](), [responsible-ai](), [security](), [soc-2]() ### AI overview Figma announces ISO/IEC 42001:2023 certification for its Artificial Intelligence Management System. An accredited independent auditor assessed Figma's AI governance policies, risk management processes, data practices, development practices, and technical safeguards across its platform. ### Source excerpt Saying you use AI responsibly is easy, but proving it to an accredited auditor is harder. We decided that was a standard worth meeting. ## Pulumi ships a 238-policy ISO/IEC 27001:2022 pack for AWS DevFeed: [Pulumi ships a 238-policy ISO/IEC 27001:2022 pack for AWS]() Original publisher: [Read original article]() Author: Dan Biwer Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Amazon Web Services](), [Security](), [Cloud](), [configuration]() Tags: [audit](), [aws](), [compliance](), [crossguard](), [features](), [governance](), [infrastructure](), [iso](), [iso-27001](), [policy](), [policy-as-code](), [product](), [pulumi](), [pulumi-cloud](), [security](), [standard]() ### AI overview Pulumi announces a pre-built ISO/IEC 27001:2022 policy pack for AWS, available in Pulumi Cloud as iso-27001-aws. The pack contains 238 policies mapped to relevant ISO 27001 controls and supports auditing existing AWS resources and preventing non-compliant resources during pulumi up. ### Source excerpt ISO/IEC 27001 is the international standard for information security management. Proving you meet it usually means months of mapping abstract security controls to concrete cloud configuration, then authoring custom checks one resource at a time. We're changing that. Today we're shipping a pre-built ISO/IEC 27001:2022 policy pack for AWS, live now in Pulumi Cloud as iso-27001-aws. It encodes the standard's security expectations as 238 ready-to-run policies, so you can align your AWS estate to ISO 27001 in minutes, not months. Why ISO 27001 matters For many companies, ISO 27001 is what stands between them and a customer or a market. The sooner you can reach a certifiable state and prove you stay there, the less compliance slows the business down. The pack collapses months of policy work into something you run continuously, so security keeps pace with growth instead of blocking it. How the pack maps to ISO 27001 The hard part of ISO 27001 has always been translation: its controls are written in the language of governance and risk management, not in the language of AWS resources. Every team has had to interpret each control and decide what it means for an S3 bucket or an RDS instance. The pack does that interpretation for you. Its 238 policies are aligned to the relevant ISO 27001 controls, so each result connects back to the standard instead of leaving you to map it yourself. You can browse the full pack in the pack reference. Audit and prevent The same pack works two ways, so you can both reach compliance and stay there: Audit. Scan your existing AWS estate against the pack, including resources that Pulumi doesn't manage. You get an honest baseline of where you stand against ISO 27001 today, with every finding tied back to the control it affects. Prevent. Run the same pack as a preventative policy during pulumi up to block non-compliant resources before they're ever created. New infrastructure is born aligned to the standard. Audit gets you clean. Preventative policie ## SWIFT Code vs BIC: What's the Difference and When You Need Each DevFeed: [SWIFT Code vs BIC: What's the Difference and When You Need Each]() Original publisher: [Read original article]() Author: Aarthi Poonia Published: 2026-06-04T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [networking]() Tags: [bank](), [cross-border](), [financial](), [global](), [glossary](), [guide](), [iso](), [payments](), [routing](), [saas]() ### AI overview This guide explains that SWIFT code and BIC are interchangeable names for the same bank identifier under ISO 9362. It covers the 8- or 11-character format, distinguishes SWIFT from IBAN and ABA routing numbers, and explains when SaaS businesses need the identifier for international payments. ### Source excerpt SWIFT code and BIC explained for SaaS founders accepting global payments. Format, how to find one, ACH and SEPA equivalents, and when SWIFT actually matters. ## Chainguard + Second Front: A faster, more secure path into government markets DevFeed: [Chainguard + Second Front: A faster, more secure path into government markets]() Original publisher: [Read original article]() Published: 2026-02-20T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard containers](), [container images](), [DevSecOps](), [supply-chain-security](), [Vulnerabilities](), [Deployment](), [Cybersecurity]() Tags: [chainguard](), [chainguard-containers](), [chainguard-for-compliance](), [cmmc](), [container-image-compliance](), [container-images](), [cve-remediation](), [cybersecurity](), [devsecops](), [federal-compliance](), [fedramp](), [government](), [iso](), [provenance](), [sbom](), [second-front-systems](), [secure-by-default](), [secure-by-design](), [security](), [soc-2](), [software-supply-chain]() ### AI overview Chainguard and Second Front are partnering to help software companies pursue federal market requirements, including FedRAMP authorization and DoD impact-level accreditations. The article describes combining Chainguard's hardened container images with Second Front's Game Warden DevSecOps platform to support secure application delivery and vulnerability reduction. ### Source excerpt Discover how Chainguard and Second Front are partnering to help build a secure path into government markets for your organization. ## GNU Guix 1.5.0 released DevFeed: [GNU Guix 1.5.0 released]() Original publisher: [Read original article]() Author: Noé Lopez Published: 2026-01-23T14:00:00Z Content type: release Language: en Sources: [GNU Guix -- Blog]() Topics: [Package manager](), [gnu linux](), [Open Source](), [Linux](), [pull-requests]() Tags: [gnu-linux](), [images](), [installation](), [iso](), [linux](), [new-features](), [open-source](), [pull-requests](), [release](), [releases](), [update](), [virtual-machine-images]() ### AI overview GNU Guix 1.5.0 has been released with ISO installation images, virtual machine images, and tarballs for installing the package manager on GNU/Linux. The release follows three years of development and includes ecosystem changes such as a new consensus-based decision-making process, migration to Codeberg, and an annual release cycle. ### Source excerpt We are pleased to announce the release of GNU Guix version 1.5.0! The release comes with ISO-9660 installation images, virtual machine images, and with tarballs to install the package manager on top of your GNU/Linux distro, either from source or from binaries--check out the download page . Guix users can update by running guix pull . It's been 3 years since the previous release . That's a lot of time, reflecting both the fact that, as a rolling release , users continuously get new features and update by running guix pull ; but it also shows a lack of... ## Engineering Audits for ISO 13485 Medical Device Software Quality Management Systems DevFeed: [Engineering Audits for ISO 13485 Medical Device Software Quality Management Systems]() Original publisher: [Read original article]() Author: Anna J McDougall Published: 2025-08-18T20:21:35Z Content type: article Language: en Sources: [Anna J McDougall]() Topics: [audit](), [Requirements](), [Development](), [Software](), [systems]() Tags: [audit](), [coding-style](), [compliance](), [engineering](), [engineering-management](), [iso](), [iso-13485-standard](), [lifecycle](), [management](), [medical-devices](), [processes](), [quality](), [regulatory](), [requirements](), [review](), [risk-management](), [safety](), [software](), [software-engineering](), [systems]() ### AI overview This case study explains what an engineering audit involves under ISO 13485 for medical device software. It covers Quality Management System documentation, lifecycle management, patient safety, risk management, regulatory requirements, and the author's experience updating engineering compliance documents. ### Source excerpt What is an Engineering Audit Like? An ISO 13485 Medical Device Engineering QMS Case StudyI think I found my new look. If there's one thing that gets me fired up, it's a good ol'-fashioned audit! ... Said nobody ever. Sadly, audits are a part of the business world that tend not to be fun. However, they also serve an important purpose, and are part of the transition from the "fun team lead" style of management into the "business leader" role is coming to grips with the unsexy stuff. As part of my role at HelloBetter, I was tasked with leading engineering compliance and reporting for ISO 13485, an internationally recognised standard for Quality Management Systems (QMS) specifically for medical device manufacturers, within the broader context of the EU Medical Device Regulation (MDR). For those who aren't familiar with what an audit of this kind involves, the simple version is this: Certain requirements exist as part of the standard, not just about how to effectively create and maintain software, but also how to document that compliance. This documentation is referred to as the Quality Management System (QMS), which as the name implies serves as documentation for how you maintain quality as per the ISO. The ISO isn't only about software, but software is part of "Lifecycle Management", tracking how a medical device (in this case) goes from design and development to distribution and surveillance. A company required to meet the ISO should therefore create and follow a system that ticks all the boxes for things like patient safety, risk management, and any additional regulatory hurdles. Typically once a year, an auditor is hired to enter the company and review the documentation alongside representatives from the company who guide them through the QMS. Additionally, individuals (like me!) are pulled from different parts of the company to talk through their processes and documentation, and to show any examples that may be relevant. My Experience with Engineering Compliance for ## ISO 27001:2022 Requirements Explained DevFeed: [ISO 27001:2022 Requirements Explained]() Original publisher: [Read original article]() Author: jackson.pitts@goteleport.com (Jack Pitts) Published: 2025-08-13T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Requirements](), [audit](), [Security](), [Software as a service](), [sensitive data]() Tags: [audit](), [certifications](), [compliance](), [iso](), [iso-27001](), [migration](), [requirements](), [scope](), [security](), [sensitive-data]() ### AI overview This article explains the requirements of ISO/IEC 27001:2022, including its Information Security Management System framework, changes from the 2013 edition, certification migration, formal clauses, and Annex A controls. It describes how organizations can prepare for audits and certification. ### Source excerpt Learn about ISO 27001:2022 requirements. ## The Difference Between Postgres Logging and PGAudit DevFeed: [The Difference Between Postgres Logging and PGAudit]() Original publisher: [Read original article]() Author: Monica Steinke Published: 2025-05-28T20:26:29Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Logging](), [PostgreSQL](), [Monitoring](), [Databases]() Tags: [audit](), [compliance](), [config](), [hipaa](), [iso](), [logging](), [logs](), [monitoring](), [pci-dss](), [postgres](), [process](), [server]() ### AI overview The article compares PostgreSQL's built-in logging with PGAudit. PostgreSQL logging supports operational monitoring and troubleshooting, while PGAudit is designed for compliance auditing with detailed records of database access and changes. It describes PGAudit's session and object auditing modes and the information recorded in audit log entries. ### Source excerpt Postgres has some excellent internal logging capabilities. With a simple logging_collector = on and a couple of other config flags, you can get an incredibly detailed picture of your Postgres operations, from individual SQL statements to connection attempts, error messages, and l... ## EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech DevFeed: [EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech]() Original publisher: [Read original article]() Author: Anna J McDougall Published: 2025-05-13T14:53:24Z Content type: opinion Language: en Sources: [Anna J McDougall]() Topics: [Code quality]() Tags: [code-quality](), [compliance](), [engineering-management](), [engineering-manager](), [engineering-mangement](), [identifier](), [improvements](), [iso](), [management](), [product-engineering](), [product-management](), [quality](), [relationships](), [team-lead](), [teams](), [tech-leadership]() ### AI overview An opinion article presents practices for building effective engineering manager and product manager relationships. It emphasizes shared ownership across business, team, and product goals, with quality improvements--including compliance work--as part of an engineering manager's contribution. ### Source excerpt EM/PM Relationships Aren't About Luck: 5 Tips for Product/Tech TeamsHeader image: purple background with the text "EM/PM Relationships Aren't About Luck. 5 Tips for Product/Tech Teams :)" and a photo of Anna and Tanja together.Introduction As my probation period at HelloBetter was coming to an end, my team's Senior Product Manager Tanja Lembcke remarked, "It's great working with an EM who cares so much about product." I could easily have said the same back to her, because it's just as valuable working with a PM who cares deeply about technology, something at which she truly excels. Together, we've become a strong team. Much of that relationship has developed naturally, but I've also noticed a few intentional practices that have helped us along the way. I want to share them here for all the product managers, engineering managers, and whoever else happens to like reading my sporadic blog posts. In the end, Tanja and I didn't just "luck out" working together. There are some tried-and-true strategies we both employ to make the most out of our work and get the results we need. If you prefer LinkedIn, you can view the short-form version of this post as a summary and carousel here. Tip 1: Purposefully be the intersection of business, team, and product As a Team Lead or Engineering Manager, it's important to operate at the intersection of business goals, the engineering team, and product. This means not only using the product but also critiquing it, asking thoughtful questions, and continually returning to the core "Why." It is all too easy to sit back and just wait for features to drop in your lap, estimate them, deliver them, and then dust off your hands with a "job well done" attitude that allows you to add a nice dot-point to your CV about value creation. What is much harder, is to actually focus on quality: that hard-to-measure, hard-to-prove value that is constantly competing with your time. For EMs, we tend to see the word "quality" and jump to the concept of code qu ## 1st-stage GUI setup, Part 3 - December 2023: First tests DevFeed: [1st-stage GUI setup, Part 3 - December 2023: First tests]() Original publisher: [Read original article]() Published: 2024-02-01T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [GUI](), [Testing](), [Code]() Tags: [bootloader](), [code](), [free](), [gui](), [iso](), [open-source](), [os](), [partition](), [react](), [reactos](), [tests](), [win32](), [winapi]() ### AI overview This third post in the ReactOS "1st-stage GUI setup" series describes December 2023 work testing the complete graphical installer with a partially Wine-synced setupapi DLL. It covers partition-management UI behavior, the all-in-one CD ISO test scenario, installation dialogs, hardware presets, and current limitations to initialized MBR disks, with GPT and uninitialized-disk support planned. ### Source excerpt Greetings! Welcome to the third blog of the series "1st-stage GUI setup": September 2023: Partly Wine-syncing setupapi October-November 2023: Making partitioning UI work December 2023: First tests In this third blog post, I will cover my work done during the month of December 2023: testing the whole 1st-stage GUI setup, together with the partially wine-synced setupapi dll. Finishing and testing the partitioning page UI The first week was devoted to finally putting together the code for manipulating partitions from the user interface, using the new workflow, and testing it. ## Understanding Go's Time Format DevFeed: [Understanding Go's Time Format]() Original publisher: [Read original article]() Published: 2022-12-16T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Go]() Tags: [c-time-functions](), [display](), [format](), [formatting](), [go](), [go-time-formatting](), [how-to](), [international-standards-organisation](), [iso](), [keyboard](), [pitfalls](), [strftime](), [time]() ### AI overview A video tutorial explains Go's unique time format specification, showing how to build intuition for time layouts, format and display the current time, and avoid common formatting pitfalls. ### Source excerpt Introduction Most apps that work with time values eventually need to display time to a user. Go has a unique way of allowing you to specify how to display time values that is different from the C library function strftime. The strftime function tends to be the standard for languages and tooling to format time. Go developed its own format specification instead of using any existing format with the idea of being able to maintain a mental model for formatting time. ## How to Create a Multiboot USB with Ventoy Fast, Simple, and Easy Guide DevFeed: [How to Create a Multiboot USB with Ventoy Fast, Simple, and Easy Guide]() Original publisher: [Read original article]() Author: Techno Tim Published: 2021-02-12T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [USB](), [boot](), [Open Source](), [Hardware]() Tags: [boot](), [guide](), [hardware](), [homelab](), [how-to](), [iso](), [open-source](), [usb](), [video]() ### AI overview A video tutorial demonstrates how to use Ventoy to create a multiboot USB drive that can boot ISO, WIM, IMG, VHD, and EFI files. It notes support for both MBR and GPT partitions and describes Ventoy as free and open source. ### Source excerpt In this quick no fluff video, I will show you how to create a multi-bootable USB drive with Ventoy that can boot all of your ISO, WIM, IMG, VHD, and EFI files.It supports both MBR and GPT partitions. This is the last USB drive you will ever need and you won't ever need to format another one.Ventoy is free and open source. 📺 Watch Video Links 🛍 Check out the new Merch Shop at https://l.tec... ## Create impeccable MIME email from markdown DevFeed: [Create impeccable MIME email from markdown]() Original publisher: [Read original article]() Published: 2020-07-16T00:00:00Z Content type: article Language: en Sources: [Joe Nelson]() Topics: [Markdown](), [Code](), [Parsing](), [Library](), [HTML](), [Streams](), [GitHub]() Tags: [build](), [code](), [dependency](), [display](), [external](), [flow](), [generate](), [github](), [html](), [iso](), [library](), [links](), [markdown](), [parsing](), [portable](), [render](), [snippet](), [structure](), [terminal](), [web]() ### AI overview This article presents mimedown, a portable C99 utility that converts Markdown read from standard input into multipart MIME email written to standard output. It supports HTML and text alternatives, code snippets as inline attachments, external-link references, format=flowed text wrapping, and conservative ISO HTML output. ### Source excerpt 2020-07-16 I want to create emails that look their best in all mail clients, whether graphical or text based. Ideally I'd write a message in a simple format like Markdown, and generate the final email from the input file. Additionally, I'd like to be able to include fenced code snippets in the message, and make them available as attachments. I created a utility called mimedown that reads markdown through stdin and prints multipart MIME to stdout. Let's see it in action. ## C2x: будущий стандарт C DevFeed: [C2x: будущий стандарт C]() Original publisher: [Read original article]() Author: VlK (Badoo) Published: 2020-05-21T12:04:10Z Content type: article Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [C]() Tags: [c](), [c-plus-plus](), [c2x](), [iso](), [tag-5a4f343d67ed]() ### AI overview The article introduces C2x, the next planned version of the C programming language standard. It explains the history of C standard revisions, the role of the WG14 committee, and how proposals are reviewed and assigned different statuses. ### Source excerpt Я ловлю в далёком отголоске, Что случится на моём веку. ("Гамлет", Борис Пастернак) Признаться, пишу на чистом C я не так уж и часто и за развитием языка уже давно не слежу. Но тут произошло два неожиданных события: С вернул себе звание популярнейшего языка программирования по версии TIOBE и случился анонс первой за долгие годы действительно интересной книги, посвящённой этому языку. Поэтому я провёл несколько вечеров за изучением материалов о C2x -- следующей версии C. Самыми, на мой взгляд, интересными нововведениями я и хочу поделиться с читателями Хабра. Читать дальше -> ## Headerless train announcements DevFeed: [Headerless train announcements]() Original publisher: [Read original article]() Author: Oona Räisänen (noreply@blogger.com) Published: 2014-06-16T18:55:00Z Content type: article Language: en Sources: [Oona Räisänen]() Topics: [data](), [Filesystems]() Tags: [audio](), [audio-media](), [data](), [encoding](), [files](), [format](), [gnireenigne](), [iso]() ### AI overview The article examines a 67-megabyte ISO 9660 image from an older Finnish train announcement device. It documents the file and directory structure, language separation, and 1,950 stored sound files, then investigates their unidentified headerless audio encoding. Analysis suggests 4-bit adaptive differential PCM, and partial decoding produces garbled speech after frequency and spectral processing. ### Source excerpt The Finnish state railway company just changed their automatic announcement voice, discarding old recordings from trains. It's a good time for some data dumpster diving for the old ones, don't you think? A 67-megabyte ISO 9660 image is produced that once belonged to an older-type onboard announcement device. It contains a file system of 58 directories with five-digit names, and one called "yleis" (Finnish for "general"). Each directory contains files with three-digit file names. For each number, there's 001.inf, 001.txt and 001.snd. The .inf and .txt files seem to contain parts of announcements as ISO 8859 encoded strings, such as "InterCity train" and "to Helsinki". The .snd files obviously contain the corresponding audio announcements. There's a total of 1950 sound files. Directory structure The file system seems to be structurally pointless; there's nothing apparent that differentiates all files in /00104 from files in /00105. Announcements in different languages are numerically separated, though (/001xx = Finnish, /002xx = Swedish, /003xx = English). Track numbers and time readouts are stored sequentially, but there are out-of-place announcements and test files in between. The logic connecting numbers to their meanings is probably programmed into the device for every train route. Everything can be spliced together from almost single words. But many common announcements are also recorded as whole sentences, probably to make them sound more natural. Audio format The audio files are headerless; there is no explicit information about the format, sample rate or sample size anywhere. The byte histogram and Poincaré plot of the raw data suggest a 4-bit sample size; this, along with the fact that all files start with 0x80, is indicative of an adaptive differential PCM encoding scheme. Unfortunately there are as many variations to ADPCM as there are manufacturers of encoder chips. None of the decoders known by SoX produce clean results. But with the right settings for th ## Delete audio track from mkv file DevFeed: [Delete audio track from mkv file]() Original publisher: [Read original article]() Author: Tom Published: 2013-12-16T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Streams](), [Tool](), [container]() Tags: [audio](), [container](), [iso](), [linux](), [streams](), [tool]() ### AI overview A tutorial on identifying and removing unwanted audio and subtitle streams from an MKV file using mkvmerge and, optionally, mkvinfo. The author notes that the selected approach avoids converting the streams. ### Source excerpt Lately I tried to remove some streams from MKV file - I wanted: video, audio in my language and no subtitles. I achieved it with mkvtoolnix utils. Firstly I have to identify streams in file: $ mkvmerge -i input_file.mkv File 'test.mkv': container: Matroska Track ID 0: video (V_MPEG4/ISO/AVC) Track ID 1: audio (A_DTS) Track ID 2: audio (A_AC3) Track ID 3: audio (A_DTS) Track ID 4: audio (A_AC3) Track ID 5: subtitles (S_TEXT/UTF8) Track ID 6: subtitles (S_TEXT/UTF8) Chapters: 16 entries You could use more verbose tool mkvinfo for that purpose too.