Podcasts about usb3

犯人はアダプターでしたｗ

書類手続き大変だった～

The Raspberry Pi 5 is the latest version of one of the world's most popular computers. It was just announced on Thursday and will be released on October 23rd. The new model comes in two versions, a 4GB and an 8GB model, priced at $60 and $80 respectively. Compared to the previous Raspberry Pi 4 models, these prices are only $5 more.Raspberry Pi 5 is faster and improvedOne of the main improvements of the Raspberry Pi 5 is its faster processing power. It features a new Broadcom system on a chip (SOC) with a quad-core CPU running at 2.4GHz and a quad-core GPU. The previous model had a CPU running at 1.8GHz and a GPU with lower clock speed. The new SOC allows for overclocking up to 3GHz, providing even better performance.The GPU of the Raspberry Pi 5 is a video core seven GPU with a stock speed of 800MHz, compared to 500MHz on the previous model. Although overclocking the GPU did not result in significant graphics improvements, the overall performance of the device is noticeably faster for various tasks.Another notable improvement is the inclusion of the RP1 chip, designed by Raspberry Pi, which controls the IO for the USB3 ports, USB2 ports, and Ethernet port. This allows for higher throughput, resulting in faster read and write speeds for USB devices. The Ethernet port remains a gigabit port, providing similar speeds to the previous model. The Wi-Fi card, however, has a faster interconnect to the CPU, resulting in double or more than double the speed of the Raspberry Pi 4 under good conditions.The Raspberry Pi 5 does not come with a fan, but it is recommended to use one to prevent overheating. Without a fan, the device can reach temperatures up to 80 degrees Celsius, which is the throttle point. The official fan, specifically designed for this layout, is available for around $6. It can be easily mounted on the device using the dedicated mounting holes and four-pin header.Overall, the Raspberry Pi 5 offers significant improvements in processing power, graphics performance, and IO throughput compared to its predecessor. It is a highly anticipated computing device that provides faster and improved capabilities for various applications.New Raspberry Pi features power buttonOne of the standout features of the new Raspberry Pi 5 is the addition of a power button, which is a first for the Raspberry Pi line. This power button allows users to easily turn the device on and off without having to unplug it from the power source. However, it is important to note that the power button is not a hard cutoff switch, but rather a soft momentary button that initiates shutdown when pressed.The addition of a power button may not seem like a significant feature, but it offers several benefits. Firstly, it eliminates the need to unplug the device to turn it off, which can be inconvenient and potentially lead to the corruption of the SD card. With the power button, users can safely shut down the Raspberry Pi without the risk of data loss or corruption.Additionally, the power button allows for easier and quicker boot-up times. When the Raspberry Pi is plugged into the power source, it automatically boots up, eliminating the need to manually turn it on. This can be particularly useful in situations where the device needs to be constantly powered on and off, such as in a server setup.Furthermore, the power button is programmable, meaning that users can customize its functionality to suit their needs. Currently, pressing the power button brings up the shutdown menu on the screen. However, it is possible to program it to perform other actions, such as initiating a specific command or launching a particular application. This programmability adds an extra layer of versatility to the Raspberry Pi 5 and allows users to tailor its functionality to their specific requirements.

Voici l'épisode 153 d'iWeek (la semaine Apple), le podcast. Le grand débrief de la keynote : quel iPhone 15 choisir ? Enregistré le jeudi 14 septembre 2023 à 17h. Présentation : Benjamin Vincent avec la participation d'Elie Abitbol, Fabrice Neuman et Gilles Dounès. Au sommaire de cet épisode 153 : quel iPhone 15 choisir ? Jamais, sans doute, le choix n'a été aussi difficile entre la star de la keynote, l'iPhone 15 Pro / Pro Max propulsé par le A17 Pro, tout premier processeur grand public gravé en 3 nanomètres, son boitier en titane brossé, ses nouvelles capacités audio-vidéo (jusqu'au 120 mm sur le Pro Max grâce à la technologie tétra prisme) et, en face, l'iPhone 15 de base, beaucoup plus séduisant que ce que représentait l'iPhone 14 dans la gamme précédente, d'autant que les prix n'augmentent pas : ils baissent même de 100 € TTC, dans le cas de l'iPhone 15 Pro (à partir de 1.229 € TTC). Les nouvelles Apple Watch Series 9 et Apple Watch Ultra 2 arriveront, elles aussi, le 22 septembre 2023. On craignait une simple mise à jour de principe. Elles embarquent, en réalité, de vraies améliorations, entre la puce S9 qui inclut, pour la première fois, un Neural Engine capable d'exécuter, sur la montre, des opérations qui nécessitaient, jusque là, de passer par le Cloud, et la luminosité exceptionnelle des écrans (2.000 nits sur la Series 9 ; 3.000 nits sur l'Ultra 2). Cet épisode est, en réalité, un débrief intégral de la keynote du 12 septembre 2023. Et nous partageons avec vous tout ce qu'Apple n'a pas dit pendant l'Apple Event : du maintien de tiroir pour carte SIM physique à la chiffonnette "compatible" avec les nouveaux iPhone et aux dates de sortie des nouveaux OS, en passant par la jungle des câbles à utiliser pour profiter du nouveau connecteur USB-C sur les iPhone 15 Pro et Pro Max puisque celui qui est fourni dans la boite... se limite à l'USB 2 des iPhone 15 et 15 Plus. Et puis, ne manquez pas le bonus hebdo exclusif qui vous est réservé, chers soutiens : cette semaine, l'affaire du retrait de l'iPhone 12 en France, à la demande de l'Agence nationale des fréquences. Merci de votre fidélité à iWeek (la semaine Apple). Rendez-vous mercredi prochain 20 septembre pour l'épisode 154 ! Si l'actualité Apple vous passionne, suivez "la quotidienne iWeek", 5 à 10 minutes chaque jour, du lundi au vendredi, avec les cinq infos majeures dans l'écosystème Apple : un podcast gratuit, lui aussi, sur toutes les principales platesformes.

今回はスタジオから配信するので、基本的にやライブ配信と同じシステムを使います。講師はデジタル一眼レフ、パワポはノートPC、音声はワイヤレスピンマイクです。中心に位置するのはいつもと同じRolandのAVストリーミングミキサーVR-1HDです。【VR-1HD】https://proav.roland.com/jp/products/vr-1hd/ ここからUSB3で出力して、zoomのホストになるiMacに入れて配信します。課題は、パワポに貼り付けられた多数の動画。問題なく視聴者に届けばいいのですが、カクカクしたり音が途切れないかが心配です。軽いリハーサルをやったら、やはり音の再生が、できたりできなかったり、途中から聞こえたり、途中で聞こえなくなったりと、かなり不安定でした。今日は解決できなかったので、明日再度挑戦します。アイデアは、肥大化したパワポファイルをスリムに、貼り付けた動画をスリムに、zoomの設定の見直し、mmhmmの設定の見直しあたりでしょうか？(00:00)-オープニング(01:30)-リアルタイムのウェビナーってどうやるんだっけ？(08:11)-普段の配信機材+iMacでzoomのホスト(12:22)-パワポに貼り付けた動画の音声が不安定(17:06)-mmhmmアプリに期待

HPR News. Threat Analysis; your attack surface. Wireless key fobs compromised in European nations (France, Spain, and Latvia). On October 10, 2022, European authorities arrested 31 suspects across three nations. The suspects are believed to be related to a cybercrime ring that allegedly advertised an “automotive diagnostic solution” online and sent out fraudulent packages to their victims. The fraudulent packages contained malware and once installed onto the victims vehicle, the attackers were able to unlock the vehicle, start the ignition, then steal the vehicle without the physical key fob. European authorities confiscated over €1 million in criminal assets (malicious software, tools, and an online domain). Microsoft Office 365 has a broken encryption algorithm. Microsoft Office 365 uses an encryption algorithm called “Office 365 Message Encryption” to send and receive encrypted email messages. The messages are encrypted in an Electronic Codebook (ECB). The U.S. National Institute of Standards and Technology (NIST) reported, "ECB mode encrypts plaintext blocks independently, without randomization; therefore, the inspection of any two ciphertext blocks reveals whether or not the corresponding plaintext blocks are equal". Emails can be harvested today then decrypted later for future attacks. User Space. Netflix crackdown on freeloaders. Netflix is testing in Argentina, the Dominican Republic, El Salvador, Guatemala, and Honduras Chile, Costa Rica and Peru different efforts to crackdown on freeloaders. The term “freeloaders” covers the multiple users sharing a single Netflix account from different locations. Netflix plans to charge an additional $3.00 - $4.00 per subaccount. Samsung implements private blockchain to link user devices. While claiming the private blockchain, “has nothing to do with cryptomining”, the Knox Matrix security system links all your devices together in a private blockchain instead using a server based group verification system. The system, Knox Matrix, is suppose to allow devices to “manage themselves” by auto updating, caching updates for other devices then distributing the updates to other devices on the private blockchain. Toys for Techs. Juno Tablet: whois lookup DNS Twister Report Juno Tablet is a Beta product; overall it works with a few bugs. This is a non-refundable product, you will only get store credit. Price: $429.00 USD. Screen Size: 10.1” Screen Type: Full HD IPS screen 1920×1200 Capacitive touch, Capacitive (10-Point) MIPI-DSI. Refresh Rate: 60 Hz. CPU: Intel Jasper Lake Intel Celeron N5100 (4 Cores / 4 Threads) – 1.10GHz (Turbo 2.80 GHz) Graphics: Intel UHD Graphics, Frequency: Base 350 MHz - Max 800 MHz. Ram (SOLDERED): 8GB 2133 MHz LPDDR4. Storage: 256GB, 512GB, 1TB SSD. Chassis: Plastic. Wireless Card: Intel Wireless AC 9460/9560 Jefferson Peak 2.4 and 5GHz + Bluetooth 4.2. Ports: 1x USB3.0 1x Type-C 3.1 (Supports charging + video out) 1x Mini HDMI 1x Micro SD 3.5MM Headphone Jack Built-in Microphone Linux Kernel 5.18+ OS: Manjaro Phosh Manjaro Plasma Mobile Mobian Phosh Windows 11 (Not included – can provide ISO) JingPad A1, It’s the World’s FIRST Consumer-level ARM-based Linux Tablet. JingPad A1 maybe discontinued: https://www.youtube.com/watch?v=cmBG1Sjgsgk Pine64’s Ox64. RISC-V SBC Info: Ram: Embedded 64MB PSRAM Network: 2.4GHz 1T1R WiFi 802.11 b/g/n Bluetooth 5.2 Zigbee 10/100Mbps Ethernet (optional, on expansion board) Storage: on-board 16Mb (2MB) or 128Mb (16MB) XSPI NOR flash memory. microSD - supports SDHC and SDXC Expansion Ports: USB 2.0 OTG port 26 GPIO Pins, including SPI, I2C and UART functionality. Possible I2S and GMII expansion. Dual lane MiPi CSI port, located at USB-C port, for camera module. Audio: mic (optional, on camera module) speaker (optional, on camera module)

本期嘉宾：彭林、森森、恺伦本期节目的主要内容有：· 苹果首次回应「iPhone Type-C 充电口」· iPad 10 C 口并非 USB3.0· 苹果疑似将要推出「无实体按键 iPhone」· 彭总的 iPad Pro 2022 用起来怎么样？· 红米召开新品发布会· 一加推出原神定制机· 魅族披露 Meizu Auto 车机系统· 马斯克正式入主推特还有众多网友的精彩提问~每周五 8 点，爱否直播间，我们不见不散~

Tesla muestra Optimus / Google Japón presenta un teclado super-largo / China busca ayuda para su base lunar / Brave eliminará alertas de Cookies / Estandarizar los mandos de Stadia / BeReal en Saturday Night Live Patrocinador: En Randstad Technologies, la división de consultoría IT del grupo Randstad, te ayudan con la gestión e implementación de servicios tecnológicos especializados, la automatización de procesos y la siempre compleja tarea de la gestión de datos. — Descubre todo lo que Randstad Technologies puede hacer por ti y por tu empresa. Tesla muestra Optimus / Google Japón presenta un teclado super-largo / China busca ayuda para su base lunar / Brave eliminará alertas de Cookies / Estandarizar los mandos de Stadia / BeReal en Saturday Night Live *️⃣ Google Japón presenta un teclado de casi dos metros de largo. Lo han llamado Gboard Bar, y tiene todas las teclas en una única fila. Ideal si necesitas que tu teclado también sirva de espada o bastón. — Obviamente es bromi.

Dave tries Jeri Ellsworth's Tilt Five augmented reality AR glasses for the first time! Unboxing, first reaction, and a bit of a first user review. 00:00 – Tilt Five AR Kickstarter Glasses 01:42 – Unboxing 06:34 – The retroreflective game board 08:58 – Plugging into USB3 and fan cooling 09:35 – The glasses design robustness ...

I have a storage problem. One DLink NAS with 500GB of space (10+ years old), one Apple Time Capsule 2G (~5 years), 2TB of dropbox space, 2TB external drives, memory cards, iCloud, google drive and a full hard drive on my laptop.  Age is a big risk tied to moving disks - the older they are - the higher the risk of failure becomes.  Bringing my data home - to much risk to have it in the cloud:Privacy Security (vendor and me)Bought a Synology Disk Station 1821+ and 4 x 4TB WD Red Pro disks (5 yrs warranty and fast). After some waiting it finally arrived yesterday and during my lunch break I set it up - and that is actually really easy. Put a disk in a casette. Put the casette into the unit. Connect it to the network and power it on. That's it.  Software setup went fast. Needed to install Synologys latest software and create a volume. I decided to use SHR - Synology Hybrid Raid. Essentially a software raid - but gives you the advantage that you can use different hard drives in your raid setup and that can be handy later on. The 1821 has 8 bays but I only use 4 of them to start with. I will add additional drives as needed and in a years time bigger and faster driver will be available and I can easily upgrade.  During the afternoon I started to copy data over to my new nas from my old DLink nas. I mounted (connected) both NASes to my mac and started to copy files. After a while my computer froze - I had to restart to get network connection back. This happened once more during the afternoon (of course in the middle of a call). I don't think this is caused by the Synology - it's is rather my USB3/ethernet card that gets warm or unstable with high load.  It is pretty inefficient to copy or migrate data in this way. Data has to go on the wire from my old nas to my mac and then back out the wire to the Synology. I did some research and found that it is possible to mount the old nas straight on the nas and then copy the files directly. That is way more efficient and I could clearly see the how little load this caused in my network.  During the day to day I will migrate remaining data on the old nas and on my Time Capsule. Move my backup from the time capsule to the Synology. Finally I will copy the data from one of my external drives onto the Synology as well. This should get my video and podcast archive in a great state and have it always online when I need it.  Next steps is to move all files away from dropbox - the plan is to not extend my premium when the subscription ends in June/July.  So far - happy with the unit. But will need to use it for a longer time and especially with a few of my remote use cases as a road warrior and also with and from my mobile devices such as the iPad and the iPhone.  I hope you enjoyed to

The Batman movie was ...., new setup challenges, and practice for gig on 19th of March Wadesboro NC Originals 114 West Wade Street 1pm WE APPRECIATE ALL LISTENERS FOR TUNING IN AND IF YOU ENJOYED THIS EPISODEGIVE US A LIKE COMMENT DOWNLOAD SUBSCRIBE FOR MORE CONTENT !! Producer Credits:Malachi M.Episode Host:Malachi M.Follow on FACEBOOK:Mach5EntertainmentFollow on INSTAGRAM:Mach5_entFollow on TIKTOK:mach5entertainment20Feature Artist Links: MALACHI https://soundcloud.com/malachi-aysaac-poole?utm_source=clipboard&utm_medium=text&utm_campaign=social_sharinghttps://soundcloud.com/malachi-aysaac-poole/152311a **WE DO NOT OWN RIGHTS TO SONG(S). ALL RIGHTS RESERVED FOR ARTIST.**FREE FOR PROFIT TO USE A BIT FOR COMMERCIAL PURPOSES, SPECIFY THE TITLE (prod.by 097rusk)USED BEAT FOR INTRO AND OUTRO OF PODCAST.

SYNCROOM https://syncroom.yamaha.com/ ZOOM LIVETRAK L-8 https://zoomcorp.com/ja/jp/digital-mixer-multi-track-recorders/multi-track-recorders/LIVETRAK-L-8/ 和泉宏隆 MistyFountan.com https://mistyfountain.com/ ねとらぼ「USB3.0機器は・・・」 https://nlab.itmedia.co.jp/nl/articles/2105/12/news162.html 5.22 櫻井哲夫ソロライブ（高根沢町ちょっ蔵ホール）開催されました。 http://bass-meeting.jpn.org/index.php/2021/05/09/20210522/ ベース会43（2021年6月） http://bass-meeting.jpn.org/index.php/2021/05/22/bass-meeting43/ BASS TALK ! plus 聴き放題プラン https://audiobook.jp/audiobook/243866 絢香 / ありがとうの輪 - 15th Anniversary (Room session) https://youtu.be/Zq-OPanaa9o JazzSalon黒磯 - Facebook https://www.facebook.com/jazzsalonkuroiso/ Coral Lounge LIMOUSINE https://www.limous.jp/ ★2021年BGM★ by The Ridgeline Travelers 1月～「宴」 4月～「Silverstone」 ※作曲者でありドラマーの五島 悠（ゴシマ ユウ）氏よりBGMの使用許可をいただいております。 五島氏がリーダーを務めるジャズフュージョンバンド 『The Ridgeline Travelers』の1stアルバム「CHANGE OF SEASONS」好評発売中！ ドラマー五島 悠ウェブサイト https://gossyds.com/ The Ridgeline Travelers - CHANGE OF SEASONS https://gossyds.com/changeofseasons/ ベース会WEBサイト http://bass-meeting.jpn.org/ ベース会Facebookページ https://www.facebook.com/bassmeeting.since2018/ ベース会Twitter https://twitter.com/bass_meeting/ BASS TALK ! LINE公式アカウント（友だち追加） http://bass-meeting.jpn.org/index.php/line/ ご意見・ご感想はこちらまで basstalk@bass-meeting.jpn.org --- Send in a voice message: https://anchor.fm/bass-talk/message

Discordサーバー(チャットルーム)はこちら(WoodStreamのデジタル … 続きを読む →

このページをウェブブラウザで見る: リンク 今週もレギュラー3人で雑談回。それでも話題の中心になったのはやはりAirTag。そして、スネークマンショー「急いで口で吸え」を彷彿させるネタというかなんというか、USBは「急いで口に挿せ」について。 マガジン購読ページ グルドン登録ページ SoundCloudで再生 Podcastを購読 関連リンク お便りコーナー投書箱 backspace.fm (@backspacefm) / Twitter アフターショー #393 「AirTag は本当に駐車場で車を見つけるのに役立つのか？！」第1293話 PS4にSSDを接続してもエラーが起きるのでググったら「ゆっくり刺すとUSB2.0、素早く刺すとUSB3.0に認識されるから素早く刺せ」とあってまさかと思ったら… - Togetter ナビつき！ つくってわかる　はじめてゲームプログラミング｜Nintendo Switch 100W GaN電源を多機能USB-Cハブにしてしまったクラファン製品の実力　M1 MacBookとiPadで使えるか試してみた - ITmedia NEWS Twitter、投げ銭できる新機能「Tip Jar」を発表 - CNET Japan 『LOST JUDGMENT：裁かれざる記憶』ティザートレーラー - YouTube IBM Research、世界初の2nmチップ技術を発表 - ZDNet Japan 『三体Ⅲ　死神永生』発売日決定！｜Hayakawa Books & Magazines（β） 機動戦士ガンダム監督が「鬼滅潰す、エヴァ潰す」　ライバル視発言が注目「あの人にとって最大のリスペクト」: J-CAST ニュース 提供 この番組はフェンリル株式会社の提供でお届けしております。 フェンリルではこれまで 400 社、600 本以上のアプリを開発しており、AppStoreで 1 位を獲得したものや、DL 数 100 万以上のアプリも多数開発しています。 iOS、Android アプリなどモバイルアプリ開発の依頼はフェンリルまでお願いします。 backspace専用マストドンインスタンス、通称グルドンはさくらインターネットのサポートを受けて運用しています。 さくらインターネットは、インターネットインフラサービスを、個人向けから法人向けまで、幅広く提供しています。 さらに最近では、衛星データプラットフォーム「Tellus（テルース）」といった、新たなサービスの開発も、積極的に行っています。

This was the podcast of me getting corrected, as I was corrected on VR companies, HDMI vs DisplayPort, and USB2 vs USB3. Please accept my humble apologies and Price is Right fail horns. We do get some interesting insider info about the software architecture of PlayStations vs. Xbox. Summer Games Done Quick 2021 will once again, and hopefully for the last time, be a virtual event the week of July 4th. Here's hoping I'll make the cut to host again! Microsoft has announced that the Sony developed (but MLB published) MLB The Show 21 will be available on Xbox Game Pass on day one of its release - but it does not mean any other PlayStation exclusives are following suit. Niantic has teased an AR headset - does this mean that they might have figured out how to make AR headsets viable outside of the industrial or medical sector? Then we talk to OLR about No Man's Sky's Expeditions Update.

Ruuvitägien turvallisuushttps://f.ruuvi.com/t/proposal-for-secure-data-format/3756Pyllyukon kovennusskripti Firefoxiinhttps://github.com/pyllyukko/user.js/Tietoturvatutkija rekisteröi kasan bittiflipattuja urlejahttps://arstechnica.com/gadgets/2021/03/windows-com-bitsquatting-hack-can-wreak-unknown-havoc-on-pcs/Krebsin juttu selainten lisäosien turvallisuudestahttps://krebsonsecurity.com/2021/03/is-your-browser-extension-a-botnet-backdoor/AI tunnistaa eri abstraktion tasoja... vai tunnistaako?https://openai.com/blog/multimodal-neurons/Lauran katsoma YouTube-videohttps://www.youtube.com/watch?v=VYTSt5oOr5gNacon kräkkäämään The Sinking City pelinhttps://frogwares.com/how-nacon-cracked-and-pirated-the-sinking-city/Jamie Holding esittelee blogissaan kuinka puretaan Unreal Enginen tekemä pakkaushttps://blog.jamie.holdings/2019/03/23/reverse-engineering-aes-keys-from-unreal-engine-4-projects/BehindMLM-sivuston juttu Wiselingin Matias Lapostahttps://behindmlm.com/companies/wiseling-ceo-matias-lappo-confirmed-russian-actor/Polisiin tiedotus Wiseling yrityksestähttps://poliisi.fi/en/-/helsinki-police-is-investigating-the-activities-of-a-company-selling-investment-servicesVolexityn paljastus Exchange-haavoittuvuuteen liittyenhttps://www.volexity.com/blog/2021/03/02/active-exploitation-of-microsoft-exchange-zero-day-vulnerabilities/Krebsin analyysi Exchange-haavoittuvuudesta ja siihen liittyvään kampanjaanhttps://krebsonsecurity.com/2021/03/at-least-30000-u-s-organizations-newly-hacked-via-holes-in-microsofts-email-software/KTK:n julkaisema punainen varoitushttps://www.kyberturvallisuuskeskus.fi/fi/haavoittuvuus_7/21Äänestä Suomen paras podcast 2020https://jakso.fi/yleinen/aanesta-suomen-paras-podcast-2020

Jednym ze sposobów na poszerzenie możliwości naszych komputerów jest uzbrojenie ich w złącza umożliwiające podpięcie wszelakiego rodzaju peryferiów. Pierwsze komputery Apple można było rozszerzyć w zasadzie wyłącznie za pomocą złącza krawędziowego (Expansion slot). Klasyczne Macintoshe były wyposażone m.in. w port szeregowy RS-422 z gniazdem DB-9, późniejsze modele w mini-DIN na potrzeby portów ADB/LocalTalk, porty SCSI ze złączem DB-25 oraz całą gamę gniazd umożliwiających podłączenie do sieci (AAUI, RJ-45) czy podpięcie do monitora (VGA/DB-15, S-Video/mini-DIN, HDI-45, DVI). Pierwszym krokiem do ustandaryzowania połączeń z drukarkami, dyskami i innymi urządzeniami stało się wprowadzone na rynek w 1996 roku USB – Uniwersał Serial Bus, spopularyzowane w środowisku Apple przez wprowadzony na rynek dwa lata później komputer iMac G3. Po ponad dwóch dekadach doczekaliśmy się prawdziwie uniwersalnego złącza USB-C, które wspiera protokoły transmisji różnych danych oraz zasilania. Dzięki temu, w teorii, możemy podpiąć do naszych komputerów zarówno urządzenia z interfejsem USB3.x/4.0 jak i Thunderbolt 3/4 czy DisplayPort. Niestety, jak to zwykle bywa, praktyka różni się dość znacznie od teorii, co postanowiliśmy Wam przybliżyć i choć trochę uporządkować. Witryna konsorcjum USB Koncentratory Thunderbolt: OWC Thunderbolt Dock OWC Thunderbolt Hub CalDigit Thunderbolt 4 | USB4 ELement Hub Kensington SD5700T Thunderbolt™ 4 Dual 4K Docking Station Partnerem applejuice i sponsorem podkastu kompot jest firma Synology. Nasz podkast znajdziecie w iTunes (link), możecie też dodać do swojego ulubionego czytnika RSS (link), wysłuchać w serwisach: Spotify (link), Google Podcasts (link), TuneIn (link), Overcast (link), Castbox (link), PlayerFM (link), Pocket Casts (link), myTuner (link) lub przesłuchać bezpośrednio w przeglądarce (link). Zapraszamy do kontaktu na Twitterze: Remek Rychlewski @RZoG. Marek Telecki @mantis30. Natomiast całe przedsięwzięcie firmuje konto @ApplejuicePl. Jesteśmy również dostępni dla Was pod adresem e-mail kompot[at]applejuice.pl

iPhone 12発表！ え？ま、MagSafe？ 地域に貢献してるのか？ 東京都と静岡県が「隣接」、1番便利なのは長野県？　「Go To トラベル」地域共通クーポンの不思議
https://www.traicy.com/posts/20201004183942/ 特殊なハンコ iPhone 12発表　5G対応、小型のminiも iPhone 12発表　5G対応、小型のminiも - ITmedia ビジネスオンライン 【速報】iPhone 12シリーズ発表！　全機種5G対応、Pro Maxは史上最強カメラ ｜ マイナビニュース lightningの代わりのmagsafeかと 全機種5Gの「iPhone 12」、日本版はミリ波非対応 - Engadget 日本版 Belkin、MagSafeに対応したワイヤレス充電器や車用磁気スタンドを発表 - ITmedia NEWS アップル、10,800円の丸い新スマートスピーカー「HomePod mini」 | マイナビニュース AppleシリコンMac、11月に発表か | ゴリミー 他にも Apple Watchユーザー必見! ポケットに入るコインサイズの充電器 - CAMPFIRE (キャンプファイヤー) ソニーのカメラをウェブカム化する公式ソフトにMac版が登場 - CNET Japan CLASSIC PRO ( クラシックプロ ) >CHD201 HDMIビデオキャプチャー USB2.0接続 | サウンドハウス CLASSIC PRO ( クラシックプロ ) >CHD302 HDMIビデオキャプチャー スルーアウト USB3.0接続 送料無料 | サウンドハウス 【告知】 YouTubeチャンネル登録お願いします BJ: くりらじチャンネル - YouTube BJ: サイクリングch - YouTube タロケン: taroken railway - YouTube 鐵尾: 株式会社ジャンクション | 新入社員向けセミナー - YouTube audiobook有料番組登録をお願いします ヴォイニッチの科学書 | audiobook.jp 新型コロナウィルス感染症(COVID-19)最新情報 | audiobook.jp iBGM販売しております iBgm

第１０３回（ゲスト北澤くん１）北澤くんが買ったもの、タロケンが買ったもの＜北澤くんが買ったもの＞ストロボディフューザーディフューザーカバービデオ用LEDライトディフューザーダボ＜タロケンが買ったもの＞◯AOC 格安23.8インチフルHD液晶モニタhttps://kakaku.com/item/K0001209868/https://www.4gamer.net/games/380/G038028/20170514001/USB Type-C HDMI 変換ケーブルカコムイ USB3.1 Type-C(オス) to Type-C(メス) アダプタ ９０°Ｌ型90度角度付きUSB 3.1タイプCオスtoメス延長充電同期データアダプタ◯SwitchBot スイッチボット デジタル 温湿度計◯Jリーグのチケット当たったけど一緒に行く相手がいない、、、2020/08/19(水)19:00ＩＡＩスタジアム日本平(静岡県)　ＳＳ指定席 ×2枚清水エスパルス対横浜Ｆ・マリノス　明治安田生命Ｊ１リーグhttps://www.jleague.jp/match/j1/2020/081920/preview/

Madge is at a loss for synonyms. She walks around and talks some more. She is grateful for contributions of all kinds. Zeeche - Podcasting from SupermanTwinkleboi (TDYLN) voice mailsThanks to supportersThanks to contributorsReinvention is for Madonna.Fat breathing.Old woman. Obese woman.String bean tree?Tampon Tammy's Tampon Unboxing - like and subscribes!Flat Madge 2020Howard Stern role model.iTunes Reviews.Police violence weekend.Chicago cops waste my money.Cops take money from schools.Lightfoot = neoliberal garbage but yay she’s a blesbian.Identity politics garbage footy.Day care is working.Lots of noise.Depression. Hope i don’t get fired.Python class.Dog hair looks like rat.“Don’t you dare reelect me!”Who cares about Depp?Kanye is Trump repeat.Don’t fall for it or he will be president in 2024.America is sociologically dumb.Reopening disaster was like stopping your antibiotics after a few days.Misophonia.Bill McKibben loves burning wood.Mentally gymnastics.Catalina/Fusion/Ragan Fox/OBS/OSX/SSD debacle updateRagan loves the super spreader that is NAE. Towels over the vagina in gay pics Las Vegas.Lives vs. Pogroms.FUCKING TRUCKS.27” 5K iMac fusion drive went kapot.Used external SSD via USB3 with very good results.Now using external SSD as boot drive and internal HD has backup.Much faster.tech talkCarbon Copy Cloner is wonderful - instant boot drive!Layoffs, girdles and fiddlers on the roof.Why is Starbucks closed on a Monday?Still trying to learn Final Cut Pro X.Feeding chorkens.Fewer PreemiesJack Benny Golden Age of Radio Record 1 Side 1You know how to find me.You know how to donate.

How to connect wired earphones & KORG micro key to iPhone - YouTube https://www.youtube.com/watch?v=rK51hfdoyq0&feature=youtu.be UCA222 U-CONTROL - 製品一覧 - ベリンガー公式ホームページ https://www.electori-br.jp/products/464.html atolla USB3.0Hub 4ポート増設 + 1充電ポートUSB拡張 https://amzn.to/2B4O0JY エンディング曲 : 化学姉妹

In der heutigen Folge stellt Stefan nur ganz kurz USB3 und Thunderbolt gegenüber, da er Thunderspy vorstellen möchte. Sven erzählt von seinem neuem Audio Setup, es werden Fragen beantwortet die gestellt wurden und ein wenig Philosophie über die DSGVO gibt es als kostenlose Zugabe auch noch. Außerdem verpflichtet sich Stefan ein Projekt schnellstmöglich durch zu führen. Disclaimer In diesem Podcast werden Techniken oder Hardware vorgestellt, die geeignet sind, externe Geräte anzugreifen. Dies geschieht ausschließlich zu Bildungszwecken, denn nur, wenn man die Angriffstechniken kennt, kann man sich effektiv davor schützen. Denkt immer daran, diese Techniken oder Hardware nur bei Geräten anzuwenden, deren Eigner oder Nutzer das erlaubt haben.Der unerlaubte Zugriff auf fremde Infrastruktur ist strafbar (In Deutschland §202a, §202b, §202c StGB).

In questo momento tutti fanno dirette sui social, sta diventando una abitudine per professionisti ed imprenditori in qualsiasi settore. Fare dirette è fondamentale in qualsiasi business, ancora di più se il tuo è un Personal Brand, perchè in questo modo riesci a far conoscere meglio al pubblico chi sei, la tua storia, il tuo mondo. Grazie alle dirette puoi far conoscere i tuoi prodotti o servizi, aumentando di molto le possibilità di vendere. Nel momento in cui tutti fanno dirette, è ovvio che diventa più difficile catturare l'attenzione del pubblico, che è bombardato in continuazione da proposte di ogni tipo. Puoi trasformare le tue dirette e colpire l'attenzione degli spettatori sfruttando la qualità della tua reflex o mirrorless per creare un'immagine accattivante che lascerà a bocca aperta i tuoi spettatori, abituati generalmente a dirette di bassa qualità fatte attraverso l'uso di smartphone o webcam. Per poter utilizzare la tua reflex per fare le dirette, devi verificare che essa abbia l'uscita HDMI (è l'uscita standard attraverso cui passa il segnale digitale video e audio) e che questa uscita HDMI sia CLEAN. Il segnale che deve passare attraverso il cavo HDMI deve essere pulito, non deve presentate tutte le altre informazioni che trovi sul display della tua camera quando la utilizzi in modalità LIVE VIEW (ovvero tutte le indicazioni delle funzionalità) Puoi verificare a questo link se il tuo modello di camera ha l'uscita HDMI CLEAN, o comunque verificare sul libretto di istruzioni. ELGATO CAMERA CHECK https://www.elgato.com/en/gaming/cam-... Se la tua camera ha questa caratteristica, allora quello di cui hai bisogno è una scheda di acquisizione o convertitore hdmi/usb per poter collegare la camera al tuo computer e farla riconoscere come webcam. Infatti se colleghi direttamente il cavo hdmi al tuo computer, o utilizzi il cavo di connessione usb della camera, il tuo computer non la riconoscerà come webcam e quindi non potrai utilizzarla. La scheda di acquisizione che ti consiglio, e che sto usando per i miei video è la ELGATO HD60 S+, che è veramente molto molto bella e comoda. In pratica ad essa devi collegare il cavo HDMI con l'uscita dalla camera, poi da questa devi collegare il cavo USB3 fornito con la scheda al tuo computer ed il gioco è fatto. Non ha bisogno di alimentazione esterna, ed una volta collegata non hai bisogno di fare nulla, i software di streaming riconosceranno automaticamente la scheda e quindi potrai utilizzare la tua reflex/mirrorless. E' importante che la modalità di ripresa della tua camera sia impostata a 25p, altrimenti il computer non riconoscerà la schede e non potrai utilizzare la camera come webcam. SCOPRI ELGATO HD60 S+ https://amzn.to/2yetfdP SCOPRI ELGATO CAMLINK https://amzn.to/2zULB3R Se hai una reflex / mirrorless e vuoi veramente trasformare la qualità delle tue dirette e lasciare a bocca aperta i tuoi spettatori ti consiglio di prendere in considerazione questo prodotto perchè veramente potrà darti grandi soddisfazioni!

Una rapida carrellata dal lentissimo USB1 al moderno USB3.2 e poi USB-C, con qualche lacrimuccia dal passato. Ciao a tutti e bentornati all’ascolto di Pillole di Bit, questa è la puntata 140 e io sono, come sempre, Francesco, sempre al solito posto, spesso con un po’ di mal di schiena. Devo essere sincero, questa puntata […]

W najnowszym kompocie zdecydowaliśmy skupić się wyłącznie na sprzęcie, jaki w ostatnim czasie zakupiliśmy i – w jednym przypadku – otrzymaliśmy do testów. Być może niektórzy z Was, drodzy słuchacze planują zakup podobnych gadżetów? Wierzymy, że nasze wrażenia z użytkowania, potwierdzone zalety i wytknięte wady, pomogą Wam dokonać trafnych decyzji zakupowych. Bohaterami odcinka są: Stacja dokująca Gearlab USB-C Triple 4K Dock dzięki uprzejmości ThinkStore. Koncentrator USB-C HyperDrive TUBE 6-in-1 USB-C Hub. Zewnętrzny dysk twardy USB3.0 Seagate Basic 5TB. Pendrive USB-A/USB-C SanDisk Ultra® Dual Drive Luxe USB Type-C™ Flash Drive / Ultra Dual Drive Go USB Type-C™. Obudowa USB3.0 dla dysku M.2 SSD ICY BOX IB-183M2. Dysk M.2 SSD HP S700 500GB. Kontroler sieciowy Ubiquity UniFi Dream Machine Pro. Konsola Odroid Go Advance. Wyniki benchmarków AJA System Test: Zewnętrzny dysk twardy USB3.0 Seagate Basic 5TB Dysk M.2 SSD HP S700 500GB w obudowiw USB3.0 dla dysku M.2 SSD ICY BOX IB-183M2 UWAGA! Dla cierpliwych (i uważnych) słuchaczy, którzy dotrwają do końca odcinka – niespodzianka!   Nasz podkast znajdziecie w iTunes (link), możecie też dodać do swojego ulubionego czytnika RSS (link), wysłuchać w serwisach: Spotify (link), Google Podcasts (link), TuneIn (link), Overcast (link), Castbox (link), PlayerFM (link), Pocket Casts (link), myTuner (link) lub przesłuchać bezpośrednio w przeglądarce (link). Zapraszamy do kontaktu na Twitterze: Remek Rychlewski @RZoG. Marek Telecki @mantis30. Natomiast całe przedsięwzięcie firmuje konto @ApplejuicePl. Jesteśmy również dostępni dla Was pod adresem e-mail kompot[at]applejuice.pl

"The harder you work, the luckier you get!"   By watching & listening to VOBS TECH-TALK you are working hard to make your VO audio better! We're happy to bring you TECH-TALK every other week so you can listen in on Dan and George talking shop! Its conversation and information on VO recording tech you won't get anywhere else! On This weeks info packed TECH-TALK #13, we get down on: Focusrite Scarlett Solo Gen 3: 56db Gain, 6 more than before, and “AIR?”  Corning Thunderbolt and USB3 optical cable, what is it and why is it such a big deal? Apollo USB for Windows, not T3 Arrow  New Macbook Pro, Air  Ventilation for WhisperRoom idea,  And More on “Over-thinking” everything. Plus answers to your questions on Laptops, Pre-amps, 416 “T” power, Blocking traffic noise and “Hockey Pucks?”  Dan and George want to answer your home voice over studio questions sent to: theguys@VOBS.tv  Brought to you by: Voiceoveressentials.com, Vo2Gogo.com,  Sourceelements.com, VoiceOverXtra.com,   VOICEACTORWEBSITES.com and J. Michael Collins Demos jmcvoiceover.com/demo-production

https://www.youtube.com/watch?v=B2RbT4uCrNs Rock On In this episode of NoLife Digital, we gush over the new Devil May Cry, chat more about Apex Legends, and talk about what the fuck is going on with USB-C-3.1x2x2.      

https://www.youtube.com/watch?v=B2RbT4uCrNs Rock On In this episode of NoLife Digital, we gush over the new Devil May Cry, chat more about Apex Legends, and talk about what the fuck is going on with USB-C-3.1x2x2.      

Thoughts on NetBSD 8.0, Monitoring love for a GigaBit OpenBSD firewall, cat’s source history, X.org root permission bug, thoughts on OpenBSD as a desktop, and NomadBSD review. ##Headlines Some thoughts on NetBSD 8.0 NetBSD is a highly portable operating system which can be run on dozens of different hardware architectures. The operating system’s clean and minimal design allow it to be run in all sorts of environments, ranging from embedded devices, to servers, to workstations. While the base operating system is minimal, NetBSD users have access to a large repository of binary packages and a ports tree which I will touch upon later. I last tried NetBSD 7.0 about three years ago and decided it was time to test drive the operating system again. In the past three years NetBSD has introduced a few new features, many of them security enhancements. For example, NetBSD now supports write exclusive-or execute (W^X) protection and address space layout randomization (ASLR) to protect programs against common attacks. NetBSD 8.0 also includes USB3 support and the ability to work with ZFS storage volumes. Early impressions Since I had set up NetBSD with a Full install and enabled xdm during the setup process, the operating system booted to a graphical login screen. From here we can sign into our account. The login screen does not provide options to shut down or restart the computer. Logging into our account brings up the twm window manager and provides a virtual terminal, courtesy of xterm. There is a panel that provides a method for logging out of the window manager. The twm environment is sparse, fast and devoid of distractions. Software management NetBSD ships with a fairly standard collection of command line tools and manual pages, but otherwise it is a fairly minimal platform. If we want to run network services, have access to a web browser, or use a word processor we are going to need to install more software. There are two main approaches to installing new packages. The first, and easier approach, is to use the pkgin package manager. The pkgin utility works much the same way APT or DNF work in the Linux world, or as pkg works on FreeBSD. We can search for software by name, install or remove items. I found pkgin worked well, though its output can be terse. My only complaint with pkgin is that it does not handle “close enough” package names. For example, if I tried to run “pkgin install vlc” or “pkgin install firefox” I would quickly be told these items did not exist. But a more forgiving package manager will realize items like vlc2 or firefox45 are available and offer to install those. The pkgin tool installs new programs in the /usr/pkg/bin directory. Depending on your configuration and shell, this location may not be in your user’s path, and it will be helpful to adjust your PATH variable accordingly. The other common approach to acquiring new software is to use the pkgsrc framework. I have talked about using pkgsrc before and I will skip the details. Basically, we can download a collection of recipes for building popular open source software and run a command to download and install these items from their source code. Using pkgsrc basically gives us the same software as using pkgin would, but with some added flexibility on the options we use. Once new software has been installed, it may need to be enabled and activated, particularly if it uses (or is) a background service. New items can be enabled in the /etc/rc.conf file and started or stopped using the service command. This works about the same as the service command on FreeBSD and most non-systemd Linux distributions. Hardware I found that, when logged into the twm environment, NetBSD used about 130MB of RAM. This included kernel memory and all active memory. A fresh, Full install used up 1.5GB of disk space. I generally found NetBSD ran well in both VirtualBox and on my desktop computer. The system was quick and stable. I did have trouble getting a higher screen resolution in both environments. NetBSD does not offer VirtualBox add-on modules. There are NetBSD patches for VirtualBox out there, but there is some manual work involved in getting them working. When running on my desktop computer I think the resolution issue was one of finding and dealing with the correct video driver. Screen resolution aside, NetBSD performed well and detected all my hardware. Personal projects Since NetBSD provides users with a small, core operating system without many utilities if we want to use NetBSD for something we need to have a project in mind. I had four mini projects in mind I wanted to try this week: install a desktop environment, enable file sharing for computers on the local network, test multimedia (video, audio and YouTube capabilities), and set up a ZFS volume for storage. I began with the desktop. Specifically, I followed the same tutorial I used three years ago to try to set up the Xfce desktop. While Xfce and its supporting services installed, I was unable to get a working desktop out of the experience. I could get the Xfce window manager working, but not the entire session. This tutorial worked beautifully with NetBSD 7.0, but not with version 8.0. Undeterred, I switched gears and installed Fluxbox instead. This gave me a slightly more powerful graphical environment than what I had before with twm while maintaining performance. Fluxbox ran without any problems, though its application menu was automatically populated with many programs which were not actually installed. Next, I tried installing a few multimedia applications to play audio and video files. Here I ran into a couple of interesting problems. I found the music players I installed would play audio files, but the audio was quite slow. It always sounded like a cassette tape dragging. When I tried to play a video, the entire graphical session would crash, taking me back to the login screen. When I installed Firefox, I found I could play YouTube videos, and the video played smoothly, but again the audio was unusually slow. I set up two methods of sharing files on the local network: OpenSSH and FTP. NetBSD basically gives us OpenSSH for free at install time and I added an FTP server through the pkgin package manager which worked beautifully with its default configuration. I experimented with ZFS support a little, just enough to confirm I could create and access ZFS volumes. ZFS seems to work on NetBSD just as well, and with the same basic features, as it does on FreeBSD and mainstream Linux distributions. I think this is a good feature for the portable operating system to have since it means we can stick NetBSD on nearly any networked computer and use it as a NAS. Conclusions NetBSD, like its close cousins (FreeBSD and OpenBSD) does not do a lot of hand holding or automation. It offers a foundation that will run on most CPUs and we can choose to build on that foundation. I mention this because, on its own, NetBSD does not do much. If we want to get something out of it, we need to be willing to build on its foundation - we need a project. This is important to keep in mind as I think going into NetBSD and thinking, “Oh I’ll just explore around and expand on this as I go,” will likely lead to disappointment. I recommend figuring out what you want to do before installing NetBSD and making sure the required tools are available in the operating system’s repositories. Some of the projects I embarked on this week (using ZFS and setting up file sharing) worked well. Others, like getting multimedia support and a full-featured desktop, did not. Given more time, I’m sure I could find a suitable desktop to install (along with the required documentation to get it and its services running), or customize one based on one of the available window managers. However, any full featured desktop is going to require some manual work. Media support was not great. The right players and codecs were there, but I was not able to get audio to play smoothly. My main complaint with NetBSD relates to my struggle to get some features working to my satisfaction: the documentation is scattered. There are four different sections of the project’s website for documentation (FAQs, The Guide, manual pages and the wiki). Whatever we are looking for is likely to be in one of those, but which one? Or, just as likely, the tutorial we want is not there, but is on a forum or blog somewhere. I found that the documentation provided was often thin, more of a quick reference to remind people how something works rather than a full explanation. As an example, I found a couple of documents relating to setting up a firewall. One dealt with networking NetBSD on a LAN, another explored IPv6 support, but neither gave an overview on syntax or a basic guide to blocking all but one or two ports. It seemed like that information should already be known, or picked up elsewhere. Newcomers are likely to be a bit confused by software management guides for the same reason. Some pages refer to using a tool called pkg_add, others use pkgsrc and its make utility, others mention pkgin. Ultimately, these tools each give approximately the same result, but work differently and yet are mentioned almost interchangeably. I have used NetBSD before a few times and could stumble through these guides, but new users are likely to come away confused. One quirk of NetBSD, which may be a security feature or an inconvenience, depending on one’s point of view, is super user programs are not included in regular users’ paths. This means we need to change our path if we want to be able to run programs typically used by root. For example, shutdown and mount are not in regular users’ paths by default. This made checking some things tricky for me. Ultimately though, NetBSD is not famous for its convenience or features so much as its flexibility. The operating system will run on virtually any processor and should work almost identically across multiple platforms. That gives NetBSD users a good deal of consistency across a range of hardware and the chance to experiment with a member of the Unix family on hardware that might not be compatible with Linux or the other BSDs. ###Showing a Gigabit OpenBSD Firewall Some Monitoring Love I have a pretty long history of running my home servers or firewalls on “exotic” hardware. At first, it was Sun Microsystem hardware, then it moved to the excellent Soekris line, with some cool single board computers thrown in the mix. Recently I’ve been running OpenBSD Octeon on the Ubiquiti Edge Router Lite, an amazing little piece of kit at an amazing price point. Upgrade Time! This setup has served me for some time and I’ve been extremely happy with it. But, in the #firstworldproblems category, I recently upgraded the household to the amazing Gigabit fibre offering from Sonic. A great problem to have, but also too much of a problem for the little Edge Router Lite (ERL). The way the OpenBSD PF firewall works, it’s only able to process packets on a single core. Not a problem for the dual-core 500 MHz ERL when you’re pushing under ~200 Mbps, but more of a problem when you’re trying to push 1000 Mbps. I needed something that was faster on a per core basis but still satisfied my usual firewall requirements. Loosely: small form factor fan-less multiple Intel Ethernet ports (good driver support) low power consumption not your regular off-the-shelf kit relatively inexpensive After evaluating a LOT of different options I settled on the Protectli Vault FW2B. With the specs required for the firewall (2 GB RAM and 8 GB drive) it comes in at a mere $239 USD! Installation of OpenBSD 6.4 was pretty straight forward, with the only problem I had was Etcher did not want to recognize the ‘.fs’ extension on the install image as bootable image. I quickly fixed this with good old Unix dd(1) on the Mac. Everything else was incredibly smooth. After loading the same rulesets on my new install, the results were fantastic! Monitoring Now that the machine was up and running (and fast!), I wanted to know what it was doing. Over the years, I’ve always relied on the venerable pfstat software to give me an overview of my traffic, blocked packets, etc. It looks like this: As you can see it’s based on RRDtool, which was simply incredible in its time. Having worked on monitoring almost continuously for almost the past decade, I wanted to see if we could re-implement the same functionality using more modern tools as RRDtool and pfstat definitely have their limitations. This might be an opportunity to learn some new things as well. I came across pf-graphite which seemed to be a great start! He had everything I needed and I added a few more stats from the detailed interface statistics and the ability for the code to exit for running from cron(8), which is a bit more OpenBSD style. I added code for sending to some SaaS metrics platforms but ultimately stuck with straight Graphite. One important thing to note was to use the Graphite pickle port (2004) instead of the default plaintext port for submission. Also you will need to set a loginterface in your ‘pf.conf’. A bit of tweaking with Graphite and Grafana, and I had a pretty darn good recreation of my original PF stats dashboard! As you can see it’s based on RRDtool, which was simply incredible in its time. Having worked on monitoring almost continuously for almost the past decade, I wanted to see if we could re-implement the same functionality using more modern tools as RRDtool and pfstat definitely have their limitations. This might be an opportunity to learn some new things as well. I came across pf-graphite which seemed to be a great start! He had everything I needed and I added a few more stats from the detailed interface statistics and the ability for the code to exit for running from cron(8), which is a bit more OpenBSD style. I added code for sending to some SaaS metrics platforms but ultimately stuck with straight Graphite. One important thing to note was to use the Graphite pickle port (2004) instead of the default plaintext port for submission. Also you will need to set a loginterface in your ‘pf.conf’. A bit of tweaking with Graphite and Grafana, and I had a pretty darn good recreation of my original PF stats dashboard! ###The Source History of Cat I once had a debate with members of my extended family about whether a computer science degree is a degree worth pursuing. I was in college at the time and trying to decide whether I should major in computer science. My aunt and a cousin of mine believed that I shouldn’t. They conceded that knowing how to program is of course a useful and lucrative thing, but they argued that the field of computer science advances so quickly that everything I learned would almost immediately be outdated. Better to pick up programming on the side and instead major in a field like economics or physics where the basic principles would be applicable throughout my lifetime. I knew that my aunt and cousin were wrong and decided to major in computer science. (Sorry, aunt and cousin!) It is easy to see why the average person might believe that a field like computer science, or a profession like software engineering, completely reinvents itself every few years. We had personal computers, then the web, then phones, then machine learning… technology is always changing, so surely all the underlying principles and techniques change too. Of course, the amazing thing is how little actually changes. Most people, I’m sure, would be stunned to know just how old some of the important software on their computer really is. I’m not talking about flashy application software, admittedly—my copy of Firefox, the program I probably use the most on my computer, is not even two weeks old. But, if you pull up the manual page for something like grep, you will see that it has not been updated since 2010 (at least on MacOS). And the original version of grep was written in 1974, which in the computing world was back when dinosaurs roamed Silicon Valley. People (and programs) still depend on grep every day. My aunt and cousin thought of computer technology as a series of increasingly elaborate sand castles supplanting one another after each high tide clears the beach. The reality, at least in many areas, is that we steadily accumulate programs that have solved problems. We might have to occasionally modify these programs to avoid software rot, but otherwise they can be left alone. grep is a simple program that solves a still-relevant problem, so it survives. Most application programming is done at a very high level, atop a pyramid of much older code solving much older problems. The ideas and concepts of 30 or 40 years ago, far from being obsolete today, have in many cases been embodied in software that you can still find installed on your laptop. I thought it would be interesting to take a look at one such old program and see how much it had changed since it was first written. cat is maybe the simplest of all the Unix utilities, so I’m going to use it as my example. Ken Thompson wrote the original implementation of cat in 1969. If I were to tell somebody that I have a program on my computer from 1969, would that be accurate? How much has cat really evolved over the decades? How old is the software on our computers? Thanks to repositories like this one, we can see exactly how cat has evolved since 1969. I’m going to focus on implementations of cat that are ancestors of the implementation I have on my Macbook. You will see, as we trace cat from the first versions of Unix down to the cat in MacOS today, that the program has been rewritten more times than you might expect—but it ultimately works more or less the same way it did fifty years ago. Research Unix Ken Thompson and Dennis Ritchie began writing Unix on a PDP 7. This was in 1969, before C, so all of the early Unix software was written in PDP 7 assembly. The exact flavor of assembly they used was unique to Unix, since Ken Thompson wrote his own assembler that added some features on top of the assembler provided by DEC, the PDP 7’s manufacturer. Thompson’s changes are all documented in the original Unix Programmer’s Manual under the entry for as, the assembler. The first implementation of cat is thus in PDP 7 assembly. I’ve added comments that try to explain what each instruction is doing, but the program is still difficult to follow unless you understand some of the extensions Thompson made while writing his assembler. There are two important ones. First, the ; character can be used to separate multiple statements on the same line. It appears that this was used most often to put system call arguments on the same line as the sys instruction. Second, Thompson added support for “temporary labels” using the digits 0 through 9. These are labels that can be reused throughout a program, thus being, according to the Unix Programmer’s Manual, “less taxing both on the imagination of the programmer and on the symbol space of the assembler.” From any given instruction, you can refer to the next or most recent temporary label n using nf and nb respectively. For example, if you have some code in a block labeled 1:, you can jump back to that block from further down by using the instruction jmp 1b. (But you cannot jump forward to that block from above without using jmp 1f instead.) The most interesting thing about this first version of cat is that it contains two names we should recognize. There is a block of instructions labeled getc and a block of instructions labeled putc, demonstrating that these names are older than the C standard library. The first version of cat actually contained implementations of both functions. The implementations buffered input so that reads and writes were not done a character at a time. The first version of cat did not last long. Ken Thompson and Dennis Ritchie were able to persuade Bell Labs to buy them a PDP 11 so that they could continue to expand and improve Unix. The PDP 11 had a different instruction set, so cat had to be rewritten. I’ve marked up this second version of cat with comments as well. It uses new assembler mnemonics for the new instruction set and takes advantage of the PDP 11’s various addressing modes. (If you are confused by the parentheses and dollar signs in the source code, those are used to indicate different addressing modes.) But it also leverages the ; character and temporary labels just like the first version of cat, meaning that these features must have been retained when as was adapted for the PDP 11. The second version of cat is significantly simpler than the first. It is also more “Unix-y” in that it doesn’t just expect a list of filename arguments—it will, when given no arguments, read from stdin, which is what cat still does today. You can also give this version of cat an argument of - to indicate that it should read from stdin. In 1973, in preparation for the release of the Fourth Edition of Unix, much of Unix was rewritten in C. But cat does not seem to have been rewritten in C until a while after that. The first C implementation of cat only shows up in the Seventh Edition of Unix. This implementation is really fun to look through because it is so simple. Of all the implementations to follow, this one most resembles the idealized cat used as a pedagogic demonstration in K&R C. The heart of the program is the classic two-liner: while ((c = getc(fi)) != EOF) putchar(c); There is of course quite a bit more code than that, but the extra code is mostly there to ensure that you aren’t reading and writing to the same file. The other interesting thing to note is that this implementation of cat only recognized one flag, -u. The -u flag could be used to avoid buffering input and output, which cat would otherwise do in blocks of 512 bytes. BSD After the Seventh Edition, Unix spawned all sorts of derivatives and offshoots. MacOS is built on top of Darwin, which in turn is derived from the Berkeley Software Distribution (BSD), so BSD is the Unix offshoot we are most interested in. BSD was originally just a collection of useful programs and add-ons for Unix, but it eventually became a complete operating system. BSD seems to have relied on the original cat implementation up until the fourth BSD release, known as 4BSD, when support was added for a whole slew of new flags. The 4BSD implementation of cat is clearly derived from the original implementation, though it adds a new function to implement the behavior triggered by the new flags. The naming conventions already used in the file were adhered to—the fflg variable, used to mark whether input was being read from stdin or a file, was joined by nflg, bflg, vflg, sflg, eflg, and tflg, all there to record whether or not each new flag was supplied in the invocation of the program. These were the last command-line flags added to cat; the man page for cat today lists these flags and no others, at least on Mac OS. 4BSD was released in 1980, so this set of flags is 38 years old. cat would be entirely rewritten a final time for BSD Net/2, which was, among other things, an attempt to avoid licensing issues by replacing all AT&T Unix-derived code with new code. BSD Net/2 was released in 1991. This final rewrite of cat was done by Kevin Fall, who graduated from Berkeley in 1988 and spent the next year working as a staff member at the Computer Systems Research Group (CSRG). Fall told me that a list of Unix utilities still implemented using AT&T code was put up on a wall at CSRG and staff were told to pick the utilities they wanted to reimplement. Fall picked cat and mknod. The cat implementation bundled with MacOS today is built from a source file that still bears his name at the very top. His version of cat, even though it is a relatively trivial program, is today used by millions. Fall’s original implementation of cat is much longer than anything we have seen so far. Other than support for a -? help flag, it adds nothing in the way of new functionality. Conceptually, it is very similar to the 4BSD implementation. It is only longer because Fall separates the implementation into a “raw” mode and a “cooked” mode. The “raw” mode is cat classic; it prints a file character for character. The “cooked” mode is cat with all the 4BSD command-line options. The distinction makes sense but it also pads out the implementation so that it seems more complex at first glance than it actually is. There is also a fancy error handling function at the end of the file that further adds to its length. MacOS The very first release of Mac OS X thus includes an implementation of cat pulled from the NetBSD project. So the first Mac OS X implementation of cat is Kevin Fall’s cat. The only thing that had changed over the intervening decade was that Fall’s error-handling function err() was removed and the err() function made available by err.h was used in its place. err.h is a BSD extension to the C standard library. The NetBSD implementation of cat was later swapped out for FreeBSD’s implementation of cat. According to Wikipedia, Apple began using FreeBSD instead of NetBSD in Mac OS X 10.3 (Panther). But the Mac OS X implementation of cat, according to Apple’s own open source releases, was not replaced until Mac OS X 10.5 (Leopard) was released in 2007. The FreeBSD implementation that Apple swapped in for the Leopard release is the same implementation on Apple computers today. As of 2018, the implementation has not been updated or changed at all since 2007. So the Mac OS cat is old. As it happens, it is actually two years older than its 2007 appearance in MacOS X would suggest. This 2005 change, which is visible in FreeBSD’s Github mirror, was the last change made to FreeBSD’s cat before Apple pulled it into Mac OS X. So the Mac OS X cat implementation, which has not been kept in sync with FreeBSD’s cat implementation, is officially 13 years old. There’s a larger debate to be had about how much software can change before it really counts as the same software; in this case, the source file has not changed at all since 2005. The cat implementation used by Mac OS today is not that different from the implementation that Fall wrote for the 1991 BSD Net/2 release. The biggest difference is that a whole new function was added to provide Unix domain socket support. At some point, a FreeBSD developer also seems to have decided that Fall’s rawargs() function and cookargs() should be combined into a single function called scanfiles(). Otherwise, the heart of the program is still Fall’s code. I asked Fall how he felt about having written the cat implementation now used by millions of Apple users, either directly or indirectly through some program that relies on cat being present. Fall, who is now a consultant and a co-author of the most recent editions of TCP/IP Illustrated, says that he is surprised when people get such a thrill out of learning about his work on cat. Fall has had a long career in computing and has worked on many high-profile projects, but it seems that many people still get most excited about the six months of work he put into rewriting cat in 1989. The Hundred-Year-Old Program In the grand scheme of things, computers are not an old invention. We’re used to hundred-year-old photographs or even hundred-year-old camera footage. But computer programs are in a different category—they’re high-tech and new. At least, they are now. As the computing industry matures, will we someday find ourselves using programs that approach the hundred-year-old mark? Computer hardware will presumably change enough that we won’t be able to take an executable compiled today and run it on hardware a century from now. Perhaps advances in programming language design will also mean that nobody will understand C in the future and cat will have long since been rewritten in another language. (Though C has already been around for fifty years, and it doesn’t look like it is about to be replaced any time soon.) But barring all that, why not just keep using the cat we have forever? I think the history of cat shows that some ideas in computer science are in fact very durable. Indeed, with cat, both the idea and the program itself are old. It may not be accurate to say that the cat on my computer is from 1969. But I could make a case for saying that the cat on my computer is from 1989, when Fall wrote his implementation of cat. Lots of other software is just as ancient. So maybe we shouldn’t think of computer science and software development primarily as fields that disrupt the status quo and invent new things. Our computer systems are built out of historical artifacts. At some point, we may all spend more time trying to understand and maintain those historical artifacts than we spend writing new code. ##News Roundup Trivial Bug in X.Org Gives Root Permission on Linux and BSD Systems A vulnerability that is trivial to exploit allows privilege escalation to root level on Linux and BSD distributions using X.Org server, the open source implementation of the X Window System that offers the graphical environment. The flaw is now identified as CVE-2018-14665 (credited to security researcher Narendra Shinde). It has been present in xorg-server for two years, since version 1.19.0 and is exploitable by a limited user as long as the X server runs with elevated permissions. Privilege escalation and arbitrary file overwrite An advisory on Thursday describes the problem as an “incorrect command-line parameter validation” that also allows an attacker to overwrite arbitrary files. Privilege escalation can be accomplished via the -modulepath argument by setting an insecure path to modules loaded by the X.org server. Arbitrary file overwrite is possible through the -logfile argument, because of improper verification when parsing the option. Bug could have been avoided in OpenBSD 6.4 OpenBSD, the free and open-source operating system with a strong focus on security, uses xorg. On October 18, the project released version 6.4 of the OS, affected by CVE-2018-14665. This could have been avoided, though. Theo de Raadt, founder and leader of the OpenBSD project, says that X maintainer knew about the problem since at least October 11. For some reason, the OpenBSD developers received the message one hour before the public announcement this Thursday, a week after their new OS release. “As yet we don’t have answers about why our X maintainer (on the X security team) and his team provided information to other projects (some who don’t even ship with this new X server) but chose to not give us a heads-up which could have saved all the new 6.4 users a lot of grief,” Raadt says. Had OpenBSD developers known about the bug before the release, they could have taken steps to mitigate the problem or delay the launch for a week or two. To remedy the problem, the OpenBSD project provides a source code patch, which requires compiling and rebuilding the X server. As a temporary solution, users can disable the Xorg binary by running the following command: chmod u-s /usr/X11R6/bin/Xorg Trivial exploitation CVE-2018-14665 does not help compromise systems, but it is useful in the following stages of an attack. Leveraging it after gaining access to a vulnerable machine is fairly easy. Matthew Hickey, co-founder, and head of Hacker House security outfit created and published an exploit, saying that it can be triggered from a remote SSH session. Three hours after the public announcement of the security gap, Daemon Security CEO Michael Shirk replied with one line that overwrote shadow files on the system. Hickey did one better and fit the entire local privilege escalation exploit in one line. Apart from OpenBSD, other operating systems affected by the bug include Debian and Ubuntu, Fedora and its downstream distro Red Hat Enterprise Linux along with its community-supported counterpart CentOS. ###OpenBSD on the Desktop: some thoughts I’ve been using OpenBSD on my ThinkPad X230 for some weeks now, and the experience has been peculiar in some ways. The OS itself in my opinion is not ready for widespread desktop usage, and the development team is not trying to push it in the throat of anybody who wants a Windows or macOS alternative. You need to understand a little bit of how *NIX systems work, because you’ll use CLI more than UI. That’s not necessarily bad, and I’m sure I learned a trick or two that could translate easily to Linux or macOS. Their development process is purely based on developers that love to contribute and hack around, just because it’s fun. Even the mailing list is a cool place to hang on! Code correctness and security are a must, nothing gets committed if it doesn’t get reviewed thoroughly first - nowadays the first two properties should be enforced in every major operating system. I like the idea of a platform that continually evolves. pledge(2) and unveil(2) are the proof that with a little effort, you can secure existing software better than ever. I like the “sensible defaults” approach, having an OS ready to be used - UI included if you selected it during the setup process - is great. Just install a browser and you’re ready to go. Manual pages on OpenBSD are real manuals, not an extension of the “–help” command found in most CLI softwares. They help you understand inner workings of the operating system, no internet connection needed. There are some trade-offs, too. Performance is not first-class, mostly because of all the security mitigations and checks done at runtime3. I write Go code in neovim, and sometimes you can feel a slight slowdown when you’re compiling and editing multiple files at the same time, but usually I can’t notice any meaningful difference. Browsers are a different matter though, you can definitely feel something differs from the experience you can have on mainstream operating systems. But again, trade-offs. To use OpenBSD on the desktop you must be ready to sacrifice some of the goodies of mainstream OSes, but if you’re searching for a zen place to do your computing stuff, it’s the best you can get right now. ###Review: NomadBSD 1.1 One of the most recent additions to the DistroWatch database is NomadBSD. According to the NomadBSD website: “NomadBSD is a 64-bit live system for USB flash drives, based on FreeBSD. Together with automatic hardware detection and setup, it is configured to be used as a desktop system that works out of the box, but can also be used for data recovery.” The latest release of NomadBSD (or simply “Nomad”, as I will refer to the project in this review) is version 1.1. It is based on FreeBSD 11.2 and is offered in two builds, one for generic personal computers and one for Macbooks. The release announcement mentions version 1.1 offers improved video driver support for Intel and AMD cards. The operating system ships with Octopkg for graphical package management and the system should automatically detect, and work with, VirtualBox environments. Nomad 1.1 is available as a 2GB download, which we then decompress to produce a 4GB file which can be written to a USB thumb drive. There is no optical media build of Nomad as it is designed to be run entirely from the USB drive, and write data persistently to the drive, rather than simply being installed from the USB media. Initial setup Booting from the USB drive brings up a series of text-based menus which ask us to configure key parts of the operating system. We are asked to select our time zone, keyboard layout, keyboard model, keyboard mapping and our preferred language. While we can select options from a list, the options tend to be short and cryptic. Rather than “English (US)”, for example, we might be given “enUS”. We are also asked to create a password for the root user account and another one for a regular user which is called “nomad”. We can then select which shell nomad will use. The default is zsh, but there are plenty of other options, including csh and bash. We have the option of encrypting our user’s home directory. I feel it is important to point out that these settings, and nomad’s home directory, are stored on the USB drive. The options and settings we select will not be saved to our local hard drive and our configuration choices will not affect other operating systems already installed on our computer. At the end, the configuration wizard asks if we want to run the BSDstats service. This option is not explained at all, but it contacts BSDstats to provide some basic statistics on BSD users. The system then takes a few minutes to apply its changes to the USB drive and automatically reboots the computer. While running the initial setup wizard, I had nearly identical experiences when running Nomad on a physical computer and running the operating system in a VirtualBox virtual machine. However, after the initial setup process was over, I had quite different experiences depending on the environment so I want to divide my experiences into two different sections. Physical desktop computer At first, Nomad failed to boot on my desktop computer. From the operating system’s boot loader, I enabled Safe Mode which allowed Nomad to boot. At that point, Nomad was able to start up, but would only display a text console. The desktop environment failed to start when running in Safe Mode. Networking was also disabled by default and I had to enable a network interface and DHCP address assignment to connect to the Internet. Instructions for enabling networking can be found in FreeBSD’s Handbook. Once we are on-line we can use the pkg command line package manager to install and update software. Had the desktop environment worked then the Octopkg graphical package manager would also be available to make browsing and installing software a point-n-click experience. Had I been able to run the desktop for prolonged amounts of time I could have made use of such pre-installed items as the Firefox web browser, the VLC media player, LibreOffice and Thunderbird. Nomad offers a fairly small collection of desktop applications, but what is there is mostly popular, capable software. When running the operating system I noted that, with one user logged in, Nomad only runs 15 processes with the default configuration. These processes require less than 100MB of RAM, and the whole system fits comfortably on a 4GB USB drive. Conclusions Ultimately using Nomad was not a practical option for me. The operating system did not work well with my hardware, or the virtual environment. In the virtual machine, Nomad crashed consistently after just a few minutes of uptime. On the desktop computer, I could not get a desktop environment to run. The command line tools worked well, and the system performed tasks very quickly, but a command line only environment is not well suited to my workflow. I like the idea of what NomadBSD is offering. There are not many live desktop flavours of FreeBSD, apart from GhostBSD. It was nice to see developers trying to make a FreeBSD-based, plug-and-go operating system that would offer a desktop and persistent storage. I suspect the system would work and perform its stated functions on different hardware, but in my case my experiment was necessarily short lived. ##Beastie Bits FreeBSD lockless algorithm - seq Happy Bob’s Libtls tutorial Locking OpenBSD when it’s sleeping iio - The OpenBSD Way Installing Hugo and Hosting Website on OpenBSD Server Fosdem 2019 reminder: BSD devroom CfP OpenBGPD, gotta go fast! - Claudio Jeker Project Trident RC3 available FreeBSD 10.4 EOL Play “Crazy Train” through your APU2 speaker ##Feedback/Questions Tobias - Satisfying my storage hunger and wallet pains Lasse - Question regarding FreeBSD backups https://twitter.com/dlangille https://dan.langille.org/ Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

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

El contendo de este podcast se basa en algunos Tweets que he ido publicando en Twitter, aprovecho aquí para explicarlos. -El cable USB3.0 a TypeC que me compré y lo que le pasa a mi móvil con él. -Más sobre la funda del móvil. -Una curiosidad sobre ivoox (sobre el min13´50") -Una cosa que me pasa en iTunes (sobre el min17´20") -El Fire TV Stick de Amazon (sobre el min20´42") -Y la devolución de una aplicación para el Gear S2.

I veckans irafflande avsnitt har vi en gäst i form av Macmattias. Vi diskuterar bland annat: Semestern är slut - ångest? Virtual virtual reality och bakom kulisserna på Isle of dogs - två riktigt mysiga upplevelser för mobil VR Björeman på semester. Igen. Apple ställer till det för de som kör USB-anslutna grafikkort. Workaround finns, typ Logitech köper Blue. Vi kontrar med att snacka mer om tangentbord än på länge. Tangentbord är svårt. Jocke vet precis vad han vill ha och jagar det envetet kors och tvärs över nätet medan Mattias gör Fredrik sugen på Penclic-tangentbord Reformatorn, Godtemplarorderns veckotidning. Högläsning av annonser ur nummer 20–21 från 18 maj 1952 Krossat glas på Ipad fixar man via hemförsäkring. Lifehack som Jocke sentomsider lärt sig 59200 mil var tillräckligt: hejdå UFL412! Hej ny(are) XC70 D5 Volvo RTI - en resa i det förgångna Från värmebölja till översvämning i källaren… till värmebölja igen… till översvämning i källaren en gång till Soppan som är “Android” och hur Google försöker kontrollera den Android 9 - Pie - och dess funktioner Länkar Indirekt grillning Grillning kontra barbecue So let us melt Virtual virtual reality Isle of dogs Wes Anderson Exotiska Finspång Smultronstället Söderhamn Söderköping Styrsö Displaylinkdrivare för grafikkort via USB3 Logitech köper Blue Harmony-fjärrkontrollerna Logitech control center K750 K780 K811 Pok3r Das keyboard Penclic Ett av Kodsnacks många avsnitt om tangentbord Penclic mini keyboard C2 corded Godtemplarna Reformatorn Volvo RTI Peugeot 307 Android på RTI  Åskskydd från Unifi Hur Google försöker kontrollera Android Android 9 - Pie Clippy De halvt dolda Guy Ritchie Reservoir dogs Cray–2 Fluorinert En söt Youtubefilm Två nördar - en podcast. Fredrik Björeman och Joacim Melin diskuterar allt som gör livet värt att leva. Fullständig avsnittsinformation finns här: https://www.bjoremanmelin.se/podcast/avsnitt-133-bjoreman-melin-och-macmattias.html.

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

Topics: Secure Framework documents Modifying chromebooks so you can use Debian/Ubuntu Memcached is the new DDoS hotness Announcement of the next BrakeSec Training Class (see Show Notes below for more info) Link to secure framework document: https://drive.google.com/open?id=1xLfY4uI88K2AiA1mosWJ7jFyP100Jv5d Tickets are already on sale for "Hack in the Box" in Amsterdam from 9-13 April 2018, and using the checkout code 'brakeingsecurity' discount code gets you a 10% discount". Register at https://conference.hitb.org/hitbsecconf2018ams/register/    #Spotify: https://brakesec.com/spotifyBDS #RSS: https://brakesec.com/BrakesecRSS #Youtube Channel:  http://www.youtube.com/c/BDSPodcast #iTunes Store Link: https://brakesec.com/BDSiTunes #Google Play Store: https://brakesec.com/BDS-GooglePlay Our main site:  https://brakesec.com/bdswebsite   Join our #Slack Channel! Email us at bds.podcast@gmail.com or DM us on Twitter @brakesec #iHeartRadio App:  https://brakesec.com/iHeartBrakesec #SoundCloud: https://brakesec.com/SoundcloudBrakesec Comments, Questions, Feedback: bds.podcast@gmail.com Support Brakeing Down Security Podcast by using our #Paypal: https://brakesec.com/PaypalBDS OR our #Patreon https://brakesec.com/BDSPatreon #Twitter: @brakesec @boettcherpwned @bryanbrake @infosystir #Player.FM : https://brakesec.com/BDS-PlayerFM #Stitcher Network: https://brakesec.com/BrakeSecStitcher #TuneIn Radio App: https://brakesec.com/TuneInBrakesec   --Show Notes-- Announcements: Matt Miller’s class on Assembly and Reverse engineering Starts 2 April - 6 sessions 2nd Class - 6 sessions, beginning 21 May Beginner course on Assembly Advanced course, dealing with more advanced topics $150 for each class, or a $250 deal if you sign up for both classes paypal.me/BDSPodcast/150USD - Specify in the NOTES if you want the “Beginner” or “Advanced” course paypal.me/BDSPodcast/250USD - If you want both courses We need a minimum of 10 students per class   Projects: Chromebook with Debian Bit of a pain, if I could be honest.. Needed USB hub with eth0, and a USB soundcard USB3 low profile thumbdrives would be better https://www.amazon.com/gp/product/B01K5EBCES/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 https://www.securecontrolsframework.com/ ←--well well worth the signup https://drive.google.com/open?id=1xLfY4uI88K2AiA1mosWJ7jFyP100Jv5d - ‘secure.xlsx’ http://www.dummies.com/programming/certification/security-control-frameworks/ Numerous security frameworks already exist: Cisco NiST CoBIT ITIL (can be utilized) SWIFT  https://www.accesspay.com/wp-content/uploads/2017/09/SWIFT_Customer_Security_Controls_Framework.pdf “My weird path to #infosec” on twitter https://en.wikipedia.org/wiki/Hydrocolloid_dressing

On this episode #9 “We Shoot Mirrorless” podcast episode for December 2017, Marco invited guest co-host Joseph Linaschke, also known as PhotoJoseph on social media, to discuss these new products and mirrorless topics:   This show is sponsored by: COSYSPEED and PhotoShelter   Joseph introduces himself and shares why and when he switched to mirrorless cameras for his professional work.   Panasonic announced a new camera. The LUMIX DC G9 has the latest 20.3 MPix m4/3 sensor (same as GH5 but tweaked and improved jpg image processing quality. It shoots up to 20 fps with continuous AF and its 5-axis sensor stabilization reduces shake up to 6.5 stops (it supports Dual IS, too). It has 225 AF points and an AF point selector joystick. The EVF has a huge magnification of 0.83x OLED EVF with 3.68 Mio dots next to a 3” fully articulating tilt-screen. Images can be stored on two UHS-II SD card slots. And connectivity options include HDMI, Mic, Headphone, Flash Sync, USB3, wired remote and WiFi 802.11ac standard. It shoots video in UHD 4K 60fps using the full sensor without an extra video crop. B&H: https://bhpho.to/2AYk4hr Amazon DE: http://amzn.to/2yKV9rM   Joseph also explained how the Panasonic LUMIX G9 compares to the LUMIX GH-5. B&H: https://bhpho.to/2yL4no4 Amazon DE: http://amzn.to/2k5LUhw   And they talked about some of the other cameras from the Panasonic LUMIX lineup like the G7: B&H https://bhpho.to/2yL3rjz  Amazon DE: http://amzn.to/2BzTAmg G85: B&H https://bhpho.to/2AYRJI6  Amazon DE: http://amzn.to/2ziSitN GX85: B&H https://bhpho.to/2yKLEZX  Amazon DE: http://amzn.to/2owB5Kb   Panasonic also announced the Leica DG Elmarit 200mm f2.8 OIS Tele Prime lens with a 400mm equivalent FOV in 35mm terms. It supports Dual IS and has 3 linear motors for speed. There is also a 1.4 TC available to boost the range up to a 560mm FOV in 35mm terms. The lens is also freeze proof and weather sealed B&H: https://bhpho.to/2AZDfaT Amazon DE: http://amzn.to/2yMLAZG   Leica announced the compact CL camera. It’s and L-mount camera with a 24 MPix APS-C sensor. And compared to the Leica TL2, which heavily relies on a touchscreen menu control operation, the Leica CL is a bit more conventional with two exposure dials, a 4 way-controller and a few physical buttons. The CL also has a built-in EVF with 2.36 Mio dots (this has to be purchased as an extra attachment for the TL) and it has a small “current settings” LCD on top next to the shutter release. The rear LCD is also touch sensitive. B&H: https://bhpho.to/2AYmKeZ   Leica also released the Noctilux-M 75mm f1.25 ASPH lens. This lens will offer a very shallow depth of field and should produce an amazing bokeh. The Minimum focus distance is 85cm or 3 ft, but the weight of approximately 1kg or 2.3 pounds is quite massive. B&H: https://bhpho.to/2yKT5jN   Sigma introduced the new 16mm f1.4 DC DN lens that will be shipping now for Sony APS-C (classic 24mm FOV with f1.4) and m4/3 cameras (32mm FOV equivalent). It has a stepping motor for fast and silent AF that should work well for still as well as video work. It’s dust and splash proof and has 9 rounded aperture blades for a circular bokeh wide open. The lens is also treated with an advanced lens coating to minimize flare and ghosting. The lens weighs 405g or 14.3 oz B&H: https://bhpho.to/2yM5vrD Amazon DE: http://amzn.to/2yM994B     Fujifilm updated the FW for many interchangeable lens cameras in the past month. The biggest upgrade came to the X-T2 with FW upgrade 3.0. The biggest improvement was made to the AF tracking algorithm for moving subjects. According to Fuji, it enhances the AF-C to track subjects twice as fast as previous FW as well as the ability to track moving objects up to 50% smaller than before. The FW also ads the ability to use “Fujifilm X Raw Studio”, improves radio flash controller usability, ads RGB histogram highlight warnings, and fixes a problem in Auto ISO setting with exposure compensation set to C.   Fuji’s FW site: http://www.fujifilm.com/support/digital_cameras/software/fw_table.html     This is the link to Joseph’s Panasonic LUMIX and GH5 training that he mentioned on the show: http://GH5Training.com Mirrorless question of the month:   Hello Scott and Marco, I have a question for Marco. I'm in process of selling my Nikon D300s camera (way to heavy for my age and use) with the intention to get a Fujifilm X-T2. I plan to get the EF-x500 flash too, primarily for fill light for indoor shooting. However, I have read that this flash does not work well and it dies after a few uses (poor manufacturing or design flaw..!) the word is the OEM manufacturer "Nissin Digital i60A" flash does a much better job. I know from the podcast that you don't use flash much. But I wanted to know your understanding/recommendation on to which flash to get - the Fujifilm EF-x500 or Nissin Digital i60A or a different one? I'll appreciate any advice. From: Viguen from West Hills, Ca. We have a PPN Photo Podcast Network group at Flickr (click link) that is open to our listeners and photos taken with all mirrorless camera brands. If you want to join just let us know through the "request invitation" button on the group and drop us a quick line there. We'll add you to the group then. And please ask for the invite via the web browser and not via the Flickr App. The invite process via the app has not been working reliably.   You can also submit an image using the Instagram hashtag #WeShootMirrorless   We have picked our monthly featured photographer and image from the submitted photos. Our monthly We Shoot Mirrorless feature photo and photographer of the month is: Andrea Lanzilli - 06:40 AM - Pescara, Italy (click here).   Co-Host Joseph Linaschke Joseph’s Website: www.joseph.info Joseph’s Twitter: @PhotoJoseph Joseph’s Instagram: www.instagram.com/photojoseph Joseph’s YouTube Channel: youtube.com/photojoseph Joseph’s Panasonic LUMIX and GH5 training: http://GH5Training.com   Please support our show by using our B&H affiliate link (click here) that will not cost you a penny more than when you are buying at B&H without our link. And the more this link will be used to buy at B&H, the more giveaways we’ll be able to give back to our listeners through B&H. It really is a “win-win” situation :)   And please share this podcast with your friends and subscribe via iTunes. We would also love to get your feedback. Is there anything that you want us to cover on the show in the future? And we would appreciate if you could take a short moment to rate or post a quick review about our shows on iTunes.   For more information on Marco Larousse follow him on Twitter: @HamburgCam For more information on Scott Bourne follow him on Twitter: @ScottBourne   About this show: On the monthly #WeShootMirrorless episode of the “PPN - Photo Podcast Network” show, Marco and a guest will discuss news from the mirrorless camera world related to innovations, trends, gear and accessories. And they will introduce mirrorless camera brands by interviewing the respective managers of those manufacturers. They will also invite pro photographers who make their living working with mirrorless cameras to share some tips and tricks on their workflow.

Wie bekommt man Ordnung in seine Podcasts? Notebook oder Minicomputer? USB2.0 oder USB3.0? Wie findet man komfortabel durch seine Favoriten? Nervt Ausfuehrlichkeit? Und wohnt jemand in unseren Computern? Fragen ueber Fragen auf der Suche ihrer Antworten. iCatcher im AppStore: https://itunes.apple.com/de/app/icatcher-podcast-player/id414419105?mt=8

Linus Torvalds announces Linux 4.11-rc4, early debug with USB3 earlycon, upcoming support for USB-C in 4.12, and ongoing development including various work on boot time speed ups, logging, futexes, and IOMMUs

We talk about the new Joue Modular MIDI control surface, then some classic BBC archive footage of David Vorhaus and the Kaleidophon, U-He's new Repro-1 Pro-1 Vi, MOTU's new USB3, Thunderbolt and AVB interfaces, Cubase 9, Cableguys TimeShaper and Ty has a beef with the Polivoks reissue.

We talk about the new Joue Modular MIDI control surface, then some classic BBC archive footage of David Vorhaus and the Kaleidophon, U-He's new Repro-1 Pro-1 Vi, MOTU's new USB3, Thunderbolt and AVB interfaces, Cubase 9, Cableguys TimeShaper and Ty has a beef with the Polivoks reissue.

The Gadget Detective joins Paul Ross to talk about Sandisk's iXpand memory expansion for Apple iPhones and iPads, and Google's plans for the future of apps - 30th May 2016 #Fevzi #Turkalp #FevziTurkalp #Paul #Ross #PaulRoss #TalkRadio #Sandisk #iXpand #memory #ram #expansion #USB #USB3 #Apple #iPhone #iPad #storage #Google #apps #streaming #stream #download

Some notes from Apple techs about iPhone Flat Rate repair and Finder default window positions are shared, then it's on to a quick discussion about why it's good El Capitan doesn't allow you to repair permissions… and when you would need to anyway! Thunderbolt, USB3, Network troubleshooting, external drive backups […]

Dans ce nouvel épisode, on parle des attentats de Paris sous l'angle des nouvelles technologies et des réseaux sociaux. Mais on parle aussi du futur des jeux vidéo en réalité virtuelle avec AMD, de vision nocturne, de Sensorflow par Google, et de l'homme qui débusque les câbles USB3 susceptible de mettre le feu chez vous... Les news #ParisAttack : le phénomène Facebook (alerte, I'm Safe, image de profil) Twitter n'est pas en reste #portesouvertes Les infos foireuses Telegram : la messagerie un peu à part, libertaire à fond, mais qui supprime quand même certains éléments (non sans rajouter un peu d'huile sur le feu) Vers où va la surveillance ? Photo du Bataclan après les attentats : peut-on encore penser qu'il est possible de censurer une photo ? Rumeur : AMD fournirait les prochaines consoles de jeux en 2018, avec de vrais morceaux de VR dedans. La vision nocturne bientôt démocratisée ? TensorFlow, Google met à disposition ses outils de machine learning. Bref ou congélo : Un gars de Google se dévoue pour débusquer les câble USB3 suceptible de prendre feu. Ils sont chics chez Google quand même ! Les bonus Les coques des smartphones... VSauce :) Un robot sur Indiegogo. Les japonais ne seront plus les seuls à avoir des rbots adorables... non mais. Intel va lancer des stations de travail Xeon Phi ! 72 coeurs, 3Tflops ! Pour mon petit noël ? Dragon Ball Z : The fall of men Il en a marre d'être viré de Facebook ... et même elle ! Avec : Cédric Tamboise Guillaume Poggiaspalla Pierre-Olivier Dybman présenté par Guillaume Vendé

This week we talk about the Transcend Storejet 25M3 detachable USB 3.0 hard disk drive. These are ruggedised, which mean that they are a bit more durable than your average portable hard disks and whats more, thet support USB3.0 transfer speeds! The are whisper quiet to use and work very nicely as a backup device … Continue reading The Gadget Man Episode 53 Transcend Storejet 25M3 → The post The Gadget Man Episode 53 Transcend Storejet 25M3 appeared first on The Gadget Man - Technology News and Reviews.

Welcome to Podcast Help Desk now part of the Modern Life Network Check out more great shows over at modernlifepodcastnetwork.com Also, part of the Tech Podcasts Network - If it’s tech, it’s here. Check out more family freindly shows at techpodcasts.com Even though this show is now part of a network, you can always find the full shownotes at podcasthelpdesk.com Now, on with the show… NEWS “The Trolls have won - TWIT Network stops live streaming and Chatroom. The shows will be streamed after they are edited instead of live. TWIT will still do live specials. The behind the scenes at the TWIT Brickhouse Studio will no longer be streamed or shown at all. http://podcasternews.com/2015/05/27/twit-to-shutter-chatroom-format-change/ --- Apple shuts down podcasts@apple.com for iTunes podcast support. They are now directing you to http://support.itunespodcasts.com/ for support. “Dear Podcast Provider, The email podcasts@apple.com is now closed. Please direct all inquiries to http://support.itunespodcasts.com for questions and concerns about your podcasts on the iTunes Store. Regards, The iTunes Podcast Team” The link goes to a Zendesk page. Zendesk is a support ticketing system. Hopefully they will be more responsive. ------------------ USB Mic Question from Andrew from Creative Writer’s Toolbelt at http://ajc-cwt-001.podomatic.com/ Q: Here' a problem I've been having for months, and I suspect others do too. I have a PC, and I use this with a Rode Podcaster mic and Audacity to record my podcasts. I connect the mic via USB on my new Dell - so I think it's a USB3 connection. Most of the time my mic works really well, and the PC always shows that it's connected. Then suddenly the mic seems to stop picking up sound, or it will pick it up faintly. Everything is still showing as connected, and if I wait a while / disconnect and reconnect everything it all starts working again - for no apparent reason. When my Rode mic stops working, other mics like the one on my $10 gaming headset and mic are still working fine. I had the same problem with a Samson mic I bought, and thought the Rode would solve it but I'm guessing it's a connectivity or sound card issue. A: I'm not a windows expert by any stretch. What I would do is see if there is a specific driver for your device. Or make sure your USB drivers are up to date. This might sound funny, but I've also heard that if you change which port you have it plugged into, it may help. Sorry I'm not much more help than that. Your best bet is to contact the manufacturer of your device (Rode). -------------- Android From Todd Cochrane, CEO of RawVoice Inc, Parent company of Blubrry.com “If you do not think the Android platform is important, and those corresponding listeners are not important. Here are three takeaways from the Google I/O conference this morning. "Eight out of 10 phones that were shipped" last year "were based on Android” There are over 4,000 distinct devices you see in Android. Over a billion users each for Android, Gmail, YouTube, Maps, search, Chrome. Now how are you adding Android listeners? Are you supporting One Click Subscribe on Android? Are you making it easy for Android users to subscribe to your show? If you are scope locked on iTunes I suggest you think about the 8-10 devices sold last year running Android.” 2014 1.2 Billion phones sold Likely 2.5 Billion phones out there in use. Not counting Tablets or Old phones not activated but in use via Wifi. That means there are nearly 2 billion Android phones! Compare that to IOS phones (iphones) 500 million or so (Numbers not exact) Mobile Podcast Downloads in May from a pool of 63,152,570 81.4% IOS 14.3 Android 4.3% “other” 1. iPhone 33.5% 2. Podcast for iOS 31.5% 3. Android Mobile 8.7% 4. iPad 7.0% 5. Stitcher for iOS 4.3% 6. Downcast for iOS 3.1% 7. Beyondpod for Android 2.5% 8.

Richard chats with Stephen Foskett about where storage is at these days. The conversation spans far and wide, talking about how Microsoft's latest products (like Exchange 2013) are rather SAN-hostile, why we're all happy to get away from FibreChannel, our indifference toward iSCSI and the impact of NFS and SMB3 on file systems. Stephen also talks about just how fast fast is these days - whether it's SSDs, PCI-E based storage or USB3 thumb drives! It's all about the iOPs! Make sure you check out Tech Field Day!

Ryan Rampersad and Matthew Petschl close up on CES news, and discuss sales from Microsoft on Xbox and Windows, Redbox Instant's new release date, a hardware revision to USB3, Verizon's implementation of Six Strikes, automated Gun Sights, and so much more!

Direkter Link zum Produkt

Direkter Link zum Produkt

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

In episode 86 Dan walks us through the job of being a digital imaging tech or DIT, we discuss color grading in video and how it relates to you photography. More about hard drives and USB3 and thunderbolt and how Bill hosed his MacOS install on his main Hackintosh, only to get it back with good backup planning. SHOW NOTES: MPEG StreamClip Douglas Trumbull Calibrate 5D Mark III in Lightroom Ze Frank 'Wadman Mission'

Matthew Petschl and Ryan Rampersad remember some recent adventures and discuss the lost talk show host, bleeping jailbreakers, retina display MacBook Pros with USB3, a fantastic summer with Microsoft deals, Google's new search paradigm, APUs, Verizon's grandfather, that Firefox again and so much more!

Die Freude in der Vorweihnachtszeit bringt auch die Qual mit sich, was man schenken kann. Einige tolle Geschenke werden in diesem Cast vorgestellt und helfen sicher bei der Suche nach dem Richtigen für seine Lieben. Eben Technik, die Spaß macht. Im Test: eLyricon eBook-Reader & Mediaplayer "EBX-700.Touch" 17,8cm/7" Farb-TFT (PX-1530-821), SOMIKON 17,8 cm (7") Digitales TFT-Fotoalbum inkl. eleganter Tasche (PX-2554-821), Meteorit Android-Netbook "NB-7" mit 17,8-cm-Display, 2 GB und WLAN (PX-8690-821), auvisio 2,5" FullHD Mini-Mediaplayer MVP-250 mit USB3.0 & OneTouchCopy (PX-3658-821), Callstel USB-Dongle für Skype-Anrufe an DECT-Festnetz-Telefon/-Anlage (PX-1538-821), Somikon Winziger USB-Scanner SC-310.mini mit OCR- & Scan-Software (PX-8183-821), Xystec Externer SSD-Adapter "CA-4.128" für bis zu 4 SD-/SDHC-Karten (PX-4801-821), CnMemory 16GB SDHC-Speicherkarte Class 10 (PX-9353-821), simvalley MOBILE Dual-SIM-Handy SX-315 VERTRAGSFREI (PX-3439-821), 7Links Sensorgesteuerte Universal-Nachführung für Überwachungskameras (PX-3661-821).     Produkt-Übersicht: http://www.pearl.de/rca131/ Podcast-Übersicht: http://www.pearl.de/podcast/ Zu den besprochenen Produkten im PEARL-Shop

USB 3.0 öffnet das Tor für extrem schnelle Verbindungen zu externen Geräten, die am Computer angeschlossen sind. Mehrere Festplatten, Kameras oder Scanner können ohne Datenbremse gleichzeitig betrieben werden. 5 GBit/s werden maximal übertragen und 900 mA liefert jeder Port. Im Test: USB 3.0 PCIe Controller "Super Speed" mit bis zu 5 Gbit/s (PX-2517-821), Xystec 3,5"-Frontpanel mit USB3.0-Controller-Karte (PCIe) "SSF-5002" (PX-2539-821), Xystec ExpressCard USB3.0-Schnittstellenkarte mit 2 Ports (PX-2564-821), Xystec Aktiver SuperSpeed USB3.0-Hub "SSU-5004" mit 4 Ports (PX-2538-821), Externes USB3.0-Festplattengehäuse für 2,5"-SATA-Festplatten (PX-2562-821), Xystec Externes USB3.0-Gehäuse für 3,5"-SATA-HDD "HDE-1335.black" (PX-2566-821), Xystec USB3.0-Dockingstation "DSU-3200 Duo" für 3,5"- & 2,5"-SATA-HDDs (PX-2565-821), Xystec Festplatten-Adapter SATA auf USB3.0 mit OneTouch-Backup (PX-2547-821). Produkt-Übersicht: http://www.pearl.de/rca101/ Podcast-Übersicht: http://www.pearl.de/podcast/ Zu den besprochenen Produkten im PEARL-Shop