POPULARITY
2 episodes with etcher
2 episodes with etcher
2 episodes with etcher
In dieser sehr persönlichen und unterhaltsamen Folge sprechen die Hosts über Magenprobleme, Cola Light, Podcast-Geschichte, nostalgische Erinnerungen, eine neue Aquarellbuch-Kooperation mit Etcher, den Alltagswahnsinn im Büro, ihren Launch-Stress mit neuen Plattformen, einem Schulöffel-Hype und tiefgehendes Pinselwissen. Besonders spannend: Die große Analyse von Aquarellpinseln – von Cosmo Top Spin über Casaneo bis hin zu Colineo. Dazu gibt's viele Kommentare aus der Community und einen sehr wortwitzigen Abschluss.Künstler der Woche: https://www.instagram.com/dudibensimonWir das sind:Isabella :https://www.instagram.com/_paperieur_/PaperClub:https://steadyhq.com/de/paperclub/aboutMarvin:https://www.instagram.com/gustavson_illustration/Gustavson Onlineshop:https://gustavson.store00:00–Begrüßung & Cola-Diskussion02:12–Podcast-Nostalgie & Nicola Seemak05:51–Marvins stressige Woche im Lager10:41–Großer Etcher-Aquarellbuch-Launch18:50–Community-Fokus & Farbwahl des Buches21:50–Schuhlöffel-Geschenkeflut31:16–Pinsel-Deepdive: Cosmo, Casaneo & Co.44:00–Technik-Stress & Plattform-Kampf53:05–Kommentare aus der Community58:48–Witz, Künstler der Woche & Rauswurf
-- During The Show -- 00:50 10 Year Hardware Plan - Caller Extended warranty support from hardware company Offer your own extended support Cold Shelf 3-5 years seems acceptable Tolerance for business continuity 06:08 NFS Moral of the story Trouble shooting process Inner workings of NFS R and W size 11:55 UI for Building ISO - A Typical ISO building process OpenSUSE Build Service (https://build.opensuse.org/) EaseUS Utility (https://www.easeus.com/backup-utility/create-an-iso-image-from-your-operating-system.html) Very time consuming Image the system 15:14 Networking for Libvirt - Carey Cockpit macvtap Red Hat Doc (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-virtual_networking-directly_attaching_to_physical_interface) Arch Wiki (https://wiki.archlinux.org/title/Macvtap) Do you need VMs to talk to the Host? 18:30 Self Hosted Email Feedback - Michael Biggest challenge DKIM DMARC SPF Reverse Lookups Noah is not in the "host your own email" camp Looking for reasons to "say no" Seen lots of Gsuite and Office365 not setting up records correctly 21:14 Encryption, Email and Wifi questions - Nikki Tang & Clevis - automated decryption on boot What is your attack vector Red Hat Knowledge base Article (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/configuring-automated-unlocking-of-encrypted-volumes-using-policy-based-decryption_security-hardening) 25:12 Gmail Alternative - Nikki Why Proton subscription Catch all domain Filtering email Tutanota (https://mail.tutanota.com/) Fast Mail (https://www.fastmail.com/) Anything is better than Gmail 29:23 News Wire Fedora 40 - Fedora (https://docs.fedoraproject.org/en-US/releases/f40/) Tails 6.2 - Tails (https://tails.net/news/version_6.2/index.fr.html) Lakka 5.0 - Lakka (https://www.lakka.tv/articles/2024/04/13/lakka-5.0/) Wine 9.7 - GitLab (https://gitlab.winehq.org/wine/wine/-/releases/wine-9.7) LXQT 2.0 - LXQT (https://lxqt-project.org/release/2024/04/15/release-lxqt-2-0-0/) Firefox 125 - OMG Ubuntu (https://www.omgubuntu.co.uk/2024/04/mozilla-firefox-125-released) Audacity 3.5 - Git Hub (https://github.com/audacity/audacity/releases/tag/Audacity-3.5.0) OpenSSF CISA DHS and SBOMs - SD Times (https://sdtimes.com/security/openssf-cisa-and-dhs-collaborate-on-new-open-source-project-for-creating-sboms/) Cerber Ransomware - SC Magazine (https://www.scmagazine.com/news/atlassian-confluence-linux-instances-targeted-with-cerber-ransomware) Akira Ransomware - The Hacker News (https://thehackernews.com/2024/04/akira-ransomware-gang-extorts-42.html) Phi-3 LLM - axios.com (https://www.axios.com/2024/04/23/microsoft-open-source-small-language-model-phi) Meta Llama 3 Gentoo Rejects AI Code - The Register (https://www.theregister.com/2024/04/16/gentoo_linux_ai_ban/) Linux in Your Car ARS Technica (https://arstechnica.com/cars/2024/04/linux-is-now-an-option-for-safety-minded-software-defined-vehicle-developers/) Software defined vehicles System 1 Power train ABS Traction Control System 2 Camera Ultrasonic Sensors Self Driving Systems System 3 Infotainment System 4 Climate Lighting System 5 Master control over everything ISO 26262 4,000 Linux security patches in 8 years Red Hat heavily investing in automotive 37:25 Miracle WM Wayland tiling window manager Tiling window managers are for more than just text based Where tiling WM don't do as well Linux IAC (https://linuxiac.com/miracle-wm-0-2-0-brings-floating-window-manager-support/) The Register (https://www.theregister.com/2024/04/23/miracle_wm_020/) 40:46 Mir & Wayland Mir now serves as a Wayland compositor Mir office hours (https://discourse.ubuntu.com/t/mir-office-hours/44062/2?u=tsimonq2) Are we Wayland yet (https://arewewaylandyet.com/) X server is still very solid Crashes X vs Wayland Wayland paper cuts Waypipe (https://gitlab.freedesktop.org/mstoeckl/waypipe/) 45:41 QT Ubuntu 24.04 The Register (https://www.theregister.com/2024/04/19/qt_ubuntu_2404_betas/) Kubuntu switching to Calamares installer Ubuntu Flutter installer only on "Main Ubuntu" Kubuntu has Plasma 5 Lubuntu has LXQT 1.3 AppArmor namespace Etcher issue solved Steve's choice of Distro Noah and flatpaks Steve moving away from Ubuntu to RHEL and Arch 52:28 Announcements Linux Fest North West April 26-28 2024 Bellingham Technical College -- The Extra Credit Section -- For links to the articles and material referenced in this week's episode check out this week's page from our podcast dashboard! This Episode's Podcast Dashboard (http://podcast.asknoahshow.com/386) Phone Systems for Ask Noah provided by Voxtelesys (http://www.voxtelesys.com/asknoah) Join us in our dedicated chatroom #GeekLab:linuxdelta.com on Matrix (https://element.linuxdelta.com/#/room/#geeklab:linuxdelta.com) -- Stay In Touch -- Find all the resources for this show on the Ask Noah Dashboard Ask Noah Dashboard (http://www.asknoahshow.com) Need more help than a radio show can offer? Altispeed provides commercial IT services and they're excited to offer you a great deal for listening to the Ask Noah Show. Call today and ask about the discount for listeners of the Ask Noah Show! Altispeed Technologies (http://www.altispeed.com/) Contact Noah live [at] asknoahshow.com -- Twitter -- Noah - Kernellinux (https://twitter.com/kernellinux) Ask Noah Show (https://twitter.com/asknoahshow) Altispeed Technologies (https://twitter.com/altispeed)
Macplanete : podcast Mac, iPhone, iPad, iMac, MacBook Air, MacBook Pro, Mac mini, Apple TV...
Dans ce second épisode, découvrez la suite de 20 autres meilleures applications pour Mac OS X / macOS. Nous avons volontairement privilégié les outils gratuits et open source lorsque cela était possible. Voici la liste des apps élues : 1 - MacBooster : https://www.macboost.net/ld/general-fr/index.php?aff=40956 2 - SD Memory Card Formatter for Mac : https://www.sdcard.org/downloads/formatter/ 3 - SUS Inspector : https://github.com/hjuutilainen/sus-inspector/releases 4 - balena Etcher : https://etcher.balena.io/ 5 - WindiskWriter : https://github.com/TechUnRestricted/windiskwriter/blob/main/README.md 6 - APFS for Windows : https://www.kqzyfj.com/7081zw41w3JRSMMKRQJLMQPNOLN 7 - Bartender : https://www.macbartender.com/ 8 - coconutBattery : http://www.coconut-flavour.com/coconutbattery/ 9 - Dusk : https://widgetworx.com/projects/dusk.html 10 - Latest : https://github.com/mangerlahn/Latest 11 - TopNotch : https://topnotch.app/ 12 - Speediness : https://sindresorhus.com/speediness 13 - MAMP : https://www.mamp.info/en/downloads/ 14 - ClearVPN : https://macpaw.audw.net/c/75078/998382/1733 15 - Burn : https://burn-osx.sourceforge.io/Pages/English/home.html 16 - AnyToISO : https://crystalidea.com/anytoiso 17 - DriveDx : https://binaryfruit.com/drivedx 18 - AweClone pour Mac : https://order.shareit.com/product?vendorid=200272207&productid=300866060&backlink=https%3A%2F%2Fwww.macplanete.com&affiliateid=200287084 19 - OpenCore Legacy Patcher = https://github.com/dortania/OpenCore-Legacy-Patcher/releases 20 - keyCue / KeyClu : https://sergii.tatarenkov.name/keyclu/support/ Retrouvez nos tutoriels et astuces sur Macplanete.com, MacBookcity.fr et Jcbtechno.com Retrouvez nous sur les réseaux sociaux Twiter, FaceBook, TikTok et YouTube. --- Send in a voice message: https://podcasters.spotify.com/pod/show/jcb0/message
Simon chats with Mike Etcher live from the deck of the Iowa.
Hacker Public Radio New Years Eve Show 2021 - 2022 Part 2 Massachusetts MCAS Tests https://www.doe.mass.edu/mcas/ A Level Test mention - http://www.gostudyuk.com/a-levels-and-equivalents/ COVID-19: quarantine, masks, vaccination, testing, etc. Michael Mina @michaelmina_lab https://twitter.com/michaelmina_lab West Virginia & Kentucky Accents https://www.dialectsarchive.com/west-virginia https://www.dialectsarchive.com/kentucky Netminer talks about being a security guard & Security Guard tools of the trade Detex Clock https://www.watchmanclocks.com/productdetails.aspx?ProductID=56 Mag light flashlight https://maglite.com/ Ohio Linux Fest https://olfconference.org/ Not Curses https://notcurses.com/notcurses.3.html Sixel https://en.wikipedia.org/wiki/Sixel The Book Of Boba Fett https://www.imdb.com/title/tt13668894/ https://en.wikipedia.org/wiki/The_Book_of_Boba_Fett Under The Helmet : The Legacy of Boba Fett https://www.imdb.com/title/tt15715890/ Mordancy talks about Mark from Command Line Magic Command Line Magic Homepage - http://www.climagic.org/ Command Line Magic Youtube - https://www.youtube.com/user/climagic/videos Command Line Magic Twitter - https://twitter.com/climagic Command Line Magic Mastadon - https://mastodon.social/@climagic Mordancy also suggests https://www.commandlinefu.com/commands/browse https://explainshell.com/ More Website Suggestions Regex Crossword is a crossword puzzle game, where the crossword clues are defined using regular expressions https://regexcrossword.com Learn VIM while playing a game https://vim-adventures.com/ Tennesee Valley Authority https://www.tva.com/ https://en.wikipedia.org/wiki/Tennessee_Valley_Authority West Virginia Coal Mines https://www.americangeosciences.org/critical-issues/maps/interactive-map-coal-mines-west-virginia Nuclear Power Plants in the USA https://en.wikipedia.org/wiki/Nuclear_power_in_the_United_States https://www.eia.gov/tools/faqs/faq.php?id=207&t=3 Moss Wants to Build a Pi Hole https://pi-hole.net/ Take The Long Way Home (SuperTramp) https://youtu.be/zKGOCOAI_2c Push To Talk Mumble Settings https://www.mumble.com/support/mumble-server-push-to-talk.php Dont use Balena Etcher, try instead https://bztsrc.gitlab.io/usbimager/ USBImager is a really really simple GUI application that writes compressed disk images to USB drives and creates backups. Available platforms: Windows, MacOS and Linux. Its interface is as simple as it gets, totally bloat-free. It is very small below 300 KB compared to more the than 130 MB of Etcher. A Maintenance Tool For Ubuntu uCareSystem Core basic https://ostechnix.com/ucaresystem-core-basic-maintenance-tool-ubuntu/ https://github.com/Utappia/uCareSystem To get rid of old kernels with no work - just paste in the commandline echo $(dpkg --list | grep linux-image | awk '{ print $2 }' | sort -V | sed -n '/'`uname -r`'/q;p') $(dpkg --list | grep linux-headers | awk '{ print $2 }' | sort -V | sed -n '/'"$(uname -r | sed "s/([0-9.-]*)-([^0-9]+)/1/")"'/q;p') | xargs echo sudo apt-get -y purge the result is a sudo command to remove old kernels. And finally this one: sudo apt autoremove && sudo apt autoclean && sudo apt clean Moss talks about ArcoLinux https://arcolinux.com/ Minnix uses Funk Whale https://funkwhale.audio/ Moss announces the passing of Betty White - RIP https://www.cnn.com/2022/01/10/entertainment/betty-white-cause-of-death/index.html https://www.rollingstone.com/tv-movies/tv-movie-news/betty-white-dead-obituary-197806/ https://en.wikipedia.org/wiki/The_Golden_Girls https://www.grunge.com/659496/the-truth-about-betty-whites-guinness-world-record/ The guys mention - Ultramarines : A Warhammer 40k movie https://en.wikipedia.org/wiki/Ultramarines:_A_Warhammer_40,000_Movie https://youtu.be/3fpvOyD5Jr0 Warhammer Cosplay https://youtu.be/9RpfpSyWGhk https://youtu.be/VZ8_aU0G094 https://www.belloflostsouls.net/2020/08/40k-cosplay-the-ultramarine-by-upw-designs.html https://www.instructables.com/Warhammer-40K-Tech-Priest-Cosplay-SKS-Props/ Matrix Movie (Matrix Resurrections) + other NPH (Neil Patrick Harris) films https://en.wikipedia.org/wiki/The_Matrix_Resurrections https://www.imdb.com/title/tt10838180/ 8-Bit Christmas https://www.imdb.com/title/tt11540284/ Doctor Horrible's Sing-Along https://www.imdb.com/title/tt1227926/ Bruce Campbell in Black Friday + other Bruce projects https://www.imdb.com/title/tt11649338/ Deadite (Evil Dead films) https://evildead.fandom.com/wiki/Deadite Burn Notice https://www.imdb.com/title/tt0810788/ The Adventures of Brisco County Jr. https://www.imdb.com/title/tt0105932/ Burn Notice Movie - The Fall of Sam Axe https://www.imdb.com/title/tt1697851/ Ash Vs Evil Dead (TV Series) https://www.imdb.com/title/tt4189022/ https://evildead.fandom.com/wiki/Ash_vs_Evil_Dead Christian Clemenson https://www.imdb.com/name/nm0166061/ https://en.wikipedia.org/wiki/Christian_Clemenson Freddie Highmore https://en.wikipedia.org/wiki/The_Good_Doctor_(TV_series) https://www.imdb.com/title/tt6470478/ Chat about Lenovo ThinkCentre Products https://pcsupport.lenovo.com/us/en/products/desktops-and-all-in-ones/thinkcentre-m-series-desktops/thinkcentre-m58 https://www.lenovo.com/in/en/desktops/thinkcentre/m-series-sff/m83/ https://www.lenovo.com/gb/en/desktops-and-all-in-ones/thinkcentre/m-series-tiny/M700-Tiny/p/11TC1MTM700 Moss Plugs - https://itsmoss.com/ and talks about installing Linux on his ThinkCentre https://itsmoss.com/2021/12/22/installing-linux-on-a-thinkcentre-tiny-m700/ A Deeper Dive Into Funk Whale https://funkwhale.audio/ https://funkwhale.audio/en_GB/faqs#decentralized-and-federated https://wiki.archlinux.org/title/Funkwhale https://twitter.com/funkwhaleaudio Peer Tube - Free software to take back control of your videos https://joinpeertube.org/ https://twitter.com/joinpeertube Joe and Danny talk 3-D Printing & Core XY Printers Voron Design https://vorondesign.com/ The Best CoreXY 3D Printers in 2022 https://all3dp.com/1/best-corexy-3d-printer/ The Voron 2.4 Build Experience https://youtu.be/0E0dM0ZdpRE Core XY Explained https://youtu.be/_ramiM3KHYE Volcano Hot End & Block https://e3d-online.com/products/volcano-hotend https://e3d-online.com/products/volcano-block-for-sensor-cartridges CES 2022 https://www.ces.tech/About-CES.aspx Danny gives a thumbs up to the Android Playstation 2 Emulator - Aethersx2 https://play.google.com/store/apps/details?id=xyz.aethersx2.android X-Files : Resist Or Serve for the Playstation 2 https://en.wikipedia.org/wiki/The_X-Files:_Resist_or_Serve Walkthrough for X-Files : Resist Or Serve https://youtu.be/_1DoMfufliQ PCSX2 - An Open-Source Playstation 2 Emulator supporting over 98% Of the PS2 library https://pcsx2.net/ GTA Vice City https://www.rockstargames.com/games/vicecity Armored Core : Masters Of Arena https://armoredcore.fandom.com/wiki/Armored_Core:_Master_of_Arena http://www.cheatcodes.com/guide/walkthrough-armored-core-master-of-arena-playstation-16686/ Joe Has Some Tech Repairs to Do Playstation 3 that needs the optical drive repaired https://www.ifixit.com/Guide/PlayStation+3+Blu-ray+Disc+Drive+Replacement/3484 Xbox 360 Drive replacement https://www.ifixit.com/Guide/Xbox+360+Optical+Drive+Replacement/3358 Skullcandy HESH 3 Battery Replacement https://youtu.be/PLM7wfTCzms (generic headphone battery replacement video) LG Tone Repair https://youtu.be/DJvzWsT_ESY Open Razer https://openrazer.github.io/ Clonezilla has built in SSH support https://clonezilla.org/ Radio Shack reviving, rebranding into cryptocurrency platform https://www.foxbusiness.com/markets/radioshack-rebrands-cryptocurrency-exchange-platform https://www.nbcnews.com/pop-culture/pop-culture-news/radioshack-clarify-twitter-wasnt-hacked-just-sell-crypto-now-rcna36112 Deal Extreme https://www.dx.com/ Brick & Mortar Computer Stores Past & Present COMP USA https://www.compusa.com/ Fry's Electronics https://www.frys.com/ https://en.wikipedia.org/wiki/Fry%27s_Electronics Micro Center https://www.microcenter.com/ Tiger Direct https://www.tigerdirect.com/ Ben Heck & Oscilloscopes https://youtu.be/RuC8XmDX9iA Mordancy has projects https://www.proxmox.com/en/ https://www.docker.com/ https://jitsi.org/ https://joinpeertube.org/ https://matrix.org/ https://bitbucket.org/product F(x)tec Pro¹ Phone https://www.fxtec.com/ Joe and Mordancy chat Cryptocurrency https://www.investopedia.com/terms/c/cryptocurrency.asp Nishant gives up Windows for Fedora https://getfedora.org/en/workstation/download/ Linux LPIC Certifications https://www.lpi.org/our-certifications/summary-of-certifications https://www.lpi.org/our-certifications/lpic-1-overview https://www.lpi.org/our-certifications/lpic-2-overview ITIL Certification https://www.axelos.com/certifications/itil-service-management 3M PELTOR ComTac™ VI Hearing Defender https://www.3m.com/3M/en_US/p/d/v100849027/ TP-120 Socket https://connectors.nexus.com/item/telephone-plugs-and-jacks/telephone-plugs/tp-120 Fluke 107 Pocket Digital Multimeter https://www.fluke.com/en-us/product/electrical-testing/digital-multimeters/pocket-107 Razer Nari Ultimate Headset https://www.razer.com/gaming-headsets/razer-nari-ultimate/RZ04-02670100-R3U1 Garuda Linux https://garudalinux.org/ Centos https://www.centos.org/ FreeBSD https://www.freebsd.org/ Q-tile - A full-featured, hackable tiling window manager written and configured in Python http://www.qtile.org/ Adam WIlliamson - Fedora Team https://fedoraproject.org/wiki/User:Adamwill https://www.happyassassin.net/ https://twitter.com/adamw_ha https://fedoramagazine.org/fedora-qa-adam-williamson/ Raspberry Pi Price Jump https://www.tomshardware.com/news/raspberry-pi-4-supply-issues Headphone Repair Chat BeyerDynamic DT770 https://www.sweetwater.com/store/detail/DT770pro80--beyerdynamic-dt-770-pro-80-ohm-closed-back-studio-mixing-headphones Audio Technica ATH-M50X https://www.audio-technica.com/en-us/ath-m50x HP Thin Client Model T6xx (watch for them on Ebay) https://support.hp.com/us-en/document/c06433828 Firefox Phone https://firefoxosdevices.org/en/#type:smartphones|coming-devices:yes https://en.wikipedia.org/wiki/Firefox_OS Love 2D Gaming Engine https://love2d.org/ Roblox https://www.roblox.com/ Minecraft https://www.minecraft.net/en-us Alpine Linux https://www.alpinelinux.org/ Rick & Morty https://rickandmorty.fandom.com/wiki/Rick_and_Morty_(TV_series) Gravity Falls https://en.wikipedia.org/wiki/Gravity_Falls Final Space https://en.wikipedia.org/wiki/Final_Space Peter Cushing Dr. Who movies https://tardis.fandom.com/wiki/Peter_Cushing https://en.wikipedia.org/wiki/Dr._Who_and_the_Daleks https://en.wikipedia.org/wiki/Daleks%27_Invasion_Earth_2150_A.D. Blake's 7 https://en.wikipedia.org/wiki/Blake%27s_7 Gorillaz - Clint Eastwood https://youtu.be/1V_xRb0x9aw
Hacker Public Radio New Years Eve Show 2021 - 2022 Part 1 2021-12-31T10:00:00Z Welcome to the 9th Annual Hacker Public Radio show. It is December the 31st 2021 and the time is 10 hundred hours UTC. We start the show by sending Greetings to Christmas Island/Kiribati and Samoa Kiritimati, Apia. LINT Christmas Island/Kiribati Kiritimati Ken and Honkey talk about setting up streaming Mumble → Client (Butt) → Ice Cast https://www.mumble.info/downloads/ https://danielnoethen.de/butt/ https://icecast.org/ http://www.darkice.org/ Ken and Honkey talk about COVID-19 Omicron Variant https://www.cdc.gov/coronavirus/2019-ncov/variants/omicron-variant.html https://www.alzheimers.org.uk/get-support/coronavirus/about-coronavirus Ken, Honkey, and Netminer talk about mental health, Asperger's Syndrome, Eli The Computer Guy https://en.wikipedia.org/wiki/Asperger_syndrome https://www.webmd.com/brain/autism/mental-health-aspergers-syndrome https://aspergersfromtheinside.com/ https://www.youtube.com/channel/UC-FpBZR7DbpvNj5UrFN8qUA https://www.youtube.com/c/Elithecomputerguypage Ken gets his HAM radio license http://www.arrl.org/getting-licensed Ken talks about rebuilding the house Growing up in the 60's https://en.wikipedia.org/wiki/Andrew_Greeley https://www.goodreads.com/book/show/1197497.The_High_Tech_Knight https://en.wikipedia.org/wiki/Leo_Frankowski What is a Dunny? https://www.warrenfahey.com.au/the-dunny-a-history/ https://www.pinterest.com.au/rosepat52/old-aussie-dunnies/ Farming Talk Isaac & James https://www.facebook.com/IsaacenJames/?fref=mentions&__tn__=K-R More Amateur Radio Harmonised Amateur Radio Examination Certificate (HAREC) http://www.zs6mrk.org/RAE%20Handleiding/The-HAREC-syllabus---CEPT-T_R-61-02-Annex-6---Class-A-only.PDF Raspberry Pi 400 Chat & Makulu Linux (installs Android APKs) https://www.raspberrypi.com/products/raspberry-pi-400/ http://www.makululinux.com/wp/ https://distrowatch.com/table.php?distribution=makulu Honkey Talks about his Pi4 and Steamlink, Diet Pi , Etcher + more https://store.steampowered.com/app/353380/Steam_Link/ https://play.google.com/store/apps/details?id=com.valvesoftware.steamlink&hl=en_US&gl=US https://apps.apple.com/us/app/steam-link/id1246969117 https://dietpi.com/ https://etcher.download/ https://github.com/raspberrypi/rpi-imager Archiving Old Vinyl https://www.raspberrypi.com/news/hi-fi-raspberry-pi/ https://www.youtube.com/watch?v=zWGU0lk_fr4 Tony H. Netminer & Dave Chat https://distrohoppersdigest.blogspot.com/ https://mintcast.org/ https://en.wikipedia.org/wiki/Blackpool https://en.wikipedia.org/wiki/Nantasket_Beach Buying PCs/laptops with Linux pre-installed. https://www.entroware.com/store/ https://junocomputers.com/ https://en.wikipedia.org/wiki/Asus_Eee_PC UK Fiber Optic ISP https://cityfibre.com/ Group Chat about various tech topics BSD flavors https://en.wikipedia.org/wiki/Berkeley_Software_Distribution https://www.openbsd.org/ https://www.freebsd.org/ https://nomadbsd.org/ Boxes VM Manager https://help.gnome.org/users/gnome-boxes/stable/ ARPANET https://en.wikipedia.org/wiki/ARPANET Leena / Lena Lenna or Lena is a standard test image widely used in the field of image processing since 1973. https://en.wikipedia.org/wiki/Lenna https://en.wikipedia.org/wiki/Digital_Equipment_Corporation https://en.wikipedia.org/wiki/OpenVMS https://en.wikipedia.org/wiki/DEC_Alpha https://en.wikipedia.org/wiki/Tru64_UNIX Knight TV /Tom Knight (Knight TV) https://en.wikipedia.org/wiki/Tom_Knight_(scientist) http://pdp-6.net/knight-tv/knight-tv.html PDP 11 https://en.wikipedia.org/wiki/PDP-11 Haiku OS https://www.haiku-os.org/ Motorola StarMax Mac Clones https://everymac.com/systems/motorola/index-motorola-starmax-mac-clones.html DECstation https://en.wikipedia.org/wiki/DECstation VMS / OpenVMS https://en.wikipedia.org/wiki/OpenVMS DEC Alpha https://en.wikipedia.org/wiki/DEC_Alpha https://www.techopedia.com/definition/18752/dec-alpha Ultrix https://en.wikipedia.org/wiki/Ultrix PowerMac G5 https://everymac.com/systems/apple/powermac_g5/index-powermac-g5.html https://en.wikipedia.org/wiki/Power_Mac_G5 Tru64 Unix https://en.wikipedia.org/wiki/Tru64_UNIX https://winworldpc.com/product/tru64/50 TU58 http://gunkies.org/wiki/TU58_DECtape_II http://web.frainresearch.org:8080/projects/mypdp/tu58.php http://bitsavers.trailing-edge.com/pdf/dec/dectape/tu58/EK-0TU58-UG-001_TU58_DECtape_II_Users_Guide_Oct78.pdf ICL 1900 https://en.wikipedia.org/wiki/International_Computers_Limited http://www.ict1900.com/ DECwriter http://www.columbia.edu/cu/computinghistory/la36.html https://vt100.net/docs/tp83/chapter14.html https://en.wikipedia.org/wiki/DECwriter ISDN Phone Lines https://uh.edu/~wrice/phone.htm https://en.wikipedia.org/wiki/Integrated_Services_Digital_Network X.25 https://www.lifewire.com/x-25-816286 https://networkencyclopedia.com/x-25/ IMP https://en.wikipedia.org/wiki/Interface_Message_Processor https://www.techopedia.com/definition/7692/interface-message-processor-imp UK Academic Network. JANET (Joint Academic Network) https://www.jisc.ac.uk/janet/history UK Academic Coloured Book Protocols https://en.wikipedia.org/wiki/Coloured_Book_protocols Anne & Lynn Wheeler https://garlic.com/# https://www.garlic.com/~lynn/ George 3 Operating System http://www.chilton-computing.org.uk/acl/pdfs/icl1900_intro_george3.pdf Hercules MVS Emulator https://en.wikipedia.org/wiki/Hercules_(emulator) http://www.hercules-390.org/ Doctor Who, K9, Ultraman, and Thunderbirds+ more https://en.wikipedia.org/wiki/Doctor_Who%3A_The_Curse_of_Fatal_Death https://www.bbc.co.uk/programmes/b006q2x0 https://en.wikipedia.org/wiki/Doctor_Who https://www.imdb.com/title/tt1102732/ https://en.wikipedia.org/wiki/Ultraman_(1966_TV_series) https://en.wikipedia.org/wiki/Thunderbirds_(TV_series) https://en.wikipedia.org/wiki/Supermarionation https://en.wikipedia.org/wiki/Doctor_Who:_The_Curse_of_Fatal_Death https://tardis.fandom.com/wiki/Doctor_Who_Night_(1999) https://www.youtube.com/watch?v=EfQFmZCbOfM Log4J Vulnerability https://www.cisa.gov/uscert/apache-log4j-vulnerability-guidance Hacker Public Radio show mention -- Fixing a Noisy Blower Motor http://hackerpublicradio.org/eps.php?id=3499 Netminer suggests a newsgroup alt.sysadmin.recovery Sysadmin humor Better than a 45 to that damn server. . Nike Missile Site mention http://ed-thelen.org/ https://en.wikipedia.org/wiki/List_of_Nike_missile_sites "Bubba shot the Jukebox" song reference. https://www.youtube.com/watch?v=qbQW7rDOPxI ClaudioM's Blog - Hello from the End of 2021!: https://claudiomiranda.wordpress.com/2021/12/31/hello-from-the-end-of-2021/
Dawkins discusses his new book, "The God Delusion". He discusses the difference between religion and myth, and argues that myths are more likely to be true than religions. He also discusses his views on free will, the afterlife, and Artificial General Intelligence.
For the month of August I have decided to move from the cottage to on the road coffee shop in the parking lot covid style my commentary from sitting at the coffee shop on a Sunday morning before church where well ask me. m u m m p e d r o @ Gmail.com
I came across Hazel's notes written for a nursing home meeting. I have used mom's notes pass on to you what mom spoke on 40 years ago. The truth about fear and God's help still is true today. The message is timeless
Donate here👉 www.technols.com Hello and a warm welcome to Club Room! For the next hour you will hear two new tracks from Shy FX, two versions of the new Catz ’n Dogz track on Diynamic, Jimi Jules is on the show, plus Massiande, Etcher, Andre Kronert on Kneaded Pains, Prince Of Dance, Trance Wax in a Dusky remix, […] Subscribe to listen to Techno music, Tech House music, Deep House, Acid Techno, and Minimal Techno for FREE.
Hello and a warm welcome to Club Room! For the next hour you will hear two new tracks from Shy FX, two versions of the new Catz ’n Dogz track on Diynamic, Jimi Jules is on the show, plus Massiande, Etcher, Andre Kronert on Kneaded Pains, Prince Of Dance, Trance Wax in a Dusky remix, Splonie on Skream's Of Unsound Mind label and the beautifully delicate "For Willow" by Moomin. Enjoy!
What does having a call on your life look like? The simple answer to this question is to follow our discussion with Lauren Fitzgerald. Lauren walked us through her journey to say yes to the Lord. She was so transparent and vulnerable in sharing her story with usWalking away from the faithMeeting other religions in high school and hanging with Muslims and Hindus, etcHer dad’s career was taking off after leaving ArkansasThey did not attend worship but began to have church at homeHer father was domineering and caused her to not believe in ChristCollege and MetaphysicsParents divorce while she was in her junior of college Lauren began studying metaphysics and other religions while in collegeShe met a young man who told her she needed to bow down to a higher power Lauren stated that we need to stay clear of those who speak vaguely regarding spiritualityLauren based her faith on how her earthly conducting himself as a believerThe blessing of God still flows even thoughLauren was blessed to attend the college of her choice and in the same breath fell away from God She learned so many different religions and faithsEverything has a Genesis and an endLauren found out from her mom that she may have been the child of another manThe crash that brought her back to the LordLauren began to manifest her form of what God looked likeShe had to get rid of those around her in order to get back to who God had called her to be.The way to salvation:Hear: Romans 10:17Believe: Hebrews 11:6Repent: Acts 17:30-31Confess: Matthew 10:32Be Baptized: Mark 16:15-16Be faithful unto death: Revelation 2:10Lauren can be reached via:IG @poetlaureateofvictoryFacebook: Blue Nadi’yahSupport the show (https://www.buymeacoffee.com/CalledbyGod)J3Days Apparel This apparel company seeks to lift up Christ for He is the Savior and the Redeemer! (John 12:32).
Mobile Linux OSes are looking better than ever this week, a new effort to keep legacy applications running on Linux, and the signals indicating a Fuchsia release is nigh. Plus a PSA for GNOME users, and a recently improved tool for the Raspberry Pi. Special Guest: Dalton Durst.
Mobile Linux OSes are looking better than ever this week, a new effort to keep legacy applications running on Linux, and the signals indicating a Fuchsia release is nigh. Plus a PSA for GNOME users, and a recently improved tool for the Raspberry Pi. Special Guest: Dalton Durst.
Mobile Linux OSes are looking better than ever this week, a new effort to keep legacy applications running on Linux, and the signals indicating a Fuchsia release is nigh. Plus a PSA for GNOME users, and a recently improved tool for the Raspberry Pi. Special Guest: Dalton Durst.
We spent the last episode getting to know Emily, so in this episode we take a deep dive into all things Jo!Where she lives, her hobbies, her husband, etc.How she got into ABA, qualifications etcHer background in exercise, health and fitnessHow she came to apply ABA to healthHer current role and passionsHer goalsFavourite quoteConnect with Us!If you have any questions, comments, concerns or topics that you would like us to cover, please reach out to us! Behave Yourself Community + Resourcesbehaveyourself.mn.coInstagram:instagram.com/emily.a.macraeinstagram.com/thebehaviourladyinstagram.com/behaveyourselfpodEmail:behaveyourselfpod@gmail.comDisclaimer: While we're both behaviour analysts and qualified in our respective fields, this podcast is for education and information sharing only and should not be taken as personal, medical or behavioral advice or services.
Este pasado fin de semana estuve entretenido montando desde cero un servidor multimedia de Plex en mi Raspberry Pi 3b en modo local 100%. Lo hice usando OpenMediaVault, una conocidísima distribución orientada a NAS, que instalé como digo en mi modesta Raspberry. Os comparto los pasos que seguí a modo de "tutorial". El primer paso fue recurrir al nuevo Rasperry Pi OS basado en Debian Buster en su versión Lite, sin escritorio gráfico para un menor consumo de recursos. Quemé la ISO de Raspios en la memoria USB usando Etcher. Después activé el acceso SSH antes del primer arranque para evitar conectar la Raspberry a ningun monitor, ni teclado, ni ratón. Esto se hace creando un archivo vació (sin extensión) en el directorio /boot. Si lo hacéis desde una terminal linux la orden es touch /boot/ssh Seguidamente hay que instalar OpenMediaVault sobre Raspios. El tutorial que os he enlazado está en inglés pero ya veréis que no tiene ningua dificultad. Para finalizar, y siguiendo un video tutorial, montamos la unidad externa de disco duro e instalamos PlexMediaServer mediante Docker y Portainer. Ya veréis como es un video muy didáctico que va directo al grano y explica el proceso muy bien. Y ya está, la verdad es que ha resultado tremendamente fácil tener de nuevo mi servidor de Plex funcionando de nuevo, de manera fluida y usando de forma muy eficiente los modestos recursos de una placa como la de la Raspberry Pi 3b. Eso sí, la colección multimedia que habíamos atesorado en la nube de Drive va a costar mucho de volver a recuperar... iremos pasito a pasito. Contacto.
Beatrice Dixon, Founder of the Honey Pot Co feminine care line, has completely innovated the game for feminine health. After suffering from bacterial vaginosis ( an illness caused by too much bad bacteria in the vagina ) for years, an ancestor of hers came to visit her in a dream and gave her the ingredients. Fast forward and the dream of hers has completely healed her from years of suffering and a community of women as well. Honey Pot Co is a plant-based feminine care system powered by Mother Nature. The line includes Pads, tampons, wipes, lubricants, feminine wash, and so much more. Today's episode we dive into Beatrice's journey being a woman of color and running a multimillion-dollar business, the importance of a healthy product line, and so much more! Episode Highlights:Intro segment- Why the shift of feminine care products need to be plant-based and transparentWhat inspired Beatrice's Entrepreneurial JourneyBeatrice Spiritual Practice How she went from her Kitchen to the counters of Wholefoods, Target, Walgreens, etcHer journey with becoming 1 out of the 40 women of color to raise 1 million dollars in venture capital What separates plant-based products from other brands Advice for women overcoming unwarranted negativityLinks :https://thehoneypot.co/https://www.instagram.com/iambeadixonhttps://www.instagram.com/thehoneypotcoSupport the show (https://www.patreon.com/consciousmoon)
238. Anders Zorn, Swedish painter sculptor and etcherRelated links for 238. Anders Zorn, Swedish painter sculptor and etcher: Reply to this episode on ykyz: https://ykyz.com/p/7f9ac01f55a904eff02d0a9beda84f15b2861d38 ThatbeardedSwede microcast: https://ykyz.com/c/microcast?&username=thatbeardedswede
Fedora 31 strikes the right balance, we get the latest on the Librem 5 situation, and an easy graphics boost for laptops. Plus the best way to share your terminal yet, and more. Special Guests: Alex Kretzschmar, Brent Gervais, and Drew DeVore.
Rembrandt like many artists, lived paycheck to paycheck…except he enjoyed very large paychecks! Today’s poem, by Elizabeth Barrett Browning, stars the god Pan.
In Episode 55 I sat down with superstar Adidas trainer Tanya Poppett about her journey into the world of health & fitness, and in particular how challenges with body image in her teenage years spurred her into the woman she is today.Specifically we covered:Her life as a child including what her interests were, what she ate, where she grew up etcHer relationship with food and exercise with specifics around a time in her teenage years where she felt a lot of pressure around the way she lookedHer diet - how and why this has changed over timeWhat she thought about vegans before making changes to her plateHow her change in diet was received by her partner and familyHer philosophy on exercise, training and creating healthy habitsCreating sustainable exercise habitsThe importance of being open minded when it comes to the way we live our lives and in particular training and different forms of exerciseand much moreIf you haven't connected with Tanya you can find her on InstagramIf you enjoyed the episode and have a spare 1-2 minutes please leave a review on iTunes so the Plant Proof podcast ranks higher and becomes more discoverable for other listeners. And if you have any friends that you think will benefit from listening to this episode or any of the other Plant Proof episodes please share the link – together we can make this world a healthier place.Currently, the Plant Proof podcast can be listened to on iTunes, Google Podcasts (note: use the google podcast app not google play), Spotify, Stitcher, Soundcloud or on the Plantproof.com directly. If you listen on iTunes be sure to hit ‘subscribe’or ‘follow’ on Spotifyso you are instantly notified when I release new episodes each week.Hope you enjoy the episode friends.Simon HillCreator of Plantproof.com - your FREE resource for plant based nutrition information
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
Panel: Mark Ericksen Josh Adams Charles Max Wood Special Guest: Sasa Juric In this episode of Elixir Mix, the panel talks with Sasa Juric who is the author of Elixir in Action (2nd edition) and uses Elixir, Erlang, and OTP. He is from Zagreb, Croatia and you can check out his blog here! The panel talks about his book, past and current projects, in addition to configurations, and Elixir. Show Topics: 0:00 – Advertisement: Get A Coder Job! 0:50 – Chuck: Panel. Our guest is Sasa Juric. Introduce yourself to us please. 1:12 – Guest: I am known for writing my book and my blogs. I am president to the Elixir forum and helping people out. I have been using Elixir for 5 years; in the past I have used C++ and others. 1:46 – Chuck: App env and configuration and sounds like we could talk about more. Let’s start there, though. 1:59 – Guest. 2:03 – Panel: A little background with configuration b/c it’s been a topic in the community. There is a lot of discussion around it. What is the right way? And there is a change in how we deploy software. We have more docker containers and multiple stages of deployment and tons of configurations through environment settings. Anything you can talk about that? 2:51 – (Guest answers those questions. He discusses in detail about docker configurations. Also, the guest talks about the various settings per the different environments.) 7:25 – Panel: That was a thorough summary. 7:29 – Guest: I can talk more. 7:35 – Panel: So we have background on configuration is setup and the goals we have. What are some of the ways that a person with Elixir – how do they start? Tips / advice? They have their app and trying to go to production? 8:22 – (Guest answers the question.) Guest: 90% of the time, this is what you want to do. This is what you do...build it and put it in the folder structure, and you are good to go. Why is this good? You don’t have to have a bunch of... If you are using Phoenix than you need Node.js and you don’t want to have that on your production. You can easily run side-by-side different versions of Erlang and Phoenix. 11:40 – Panel: You can do that in a single docker file? 11:47 – Guest. 11:51 – Panel: You just copy the files... 11:56 – Panel: I learned I could do that by the distiller 2.0...I hadn’t encountered that before. 12:11 – Guest: Look into the distillery. I want to give compliments to Paul and the team is great. Go to Distillery and see the tutorials. 12:37 – Panel: People think I don’t want to use docker there is an option.... 13:01 – Guest. 13:04 – Chuck: Different types of configuration? 13:13 – Guest: Right this discussion too which is probably talking about my blog post, and I have this wild thought about configurations. We can discuss the issues and different solutions. We have these configurations files and they contain these time various configurations and... There is usually more than 1 configuration file. 17:53 – Panel: You only get agreement. I have had that problem, too, saying what is this configuration? What are THE Settings that are present and yeah that is a problem? You identify these problems in your blog, where it’s not checked in and the code will not... I have had to work around that in my projects. We are going to create a sample project and it will have defaults. So we can improve the situation. 18:45 – Panel: Class based configurations – I get angry. 19:05 – Guest: I try to challenge this status quo. Some people agree and others disagree. Some say this blanket statement. 19:54 – Loot Crate! 20:47 – Guest: Another thing to note is that configurations are free form key values. Remember, my point is that it boils down to some function being involved with these values. (Guest continues...) 23:36 – What is your direction that you are proposing? 23:40 – Guest: We are going to discuss other issues. 23:49 – Panel: As background, as apart of that whole configuration in those distillery docs... 24:41 – What is the next step in the discussion? 24:48 – Guest: Let’s take a step back. (Guest talks about Distillery 2.0.) 27:09 – Guest continues... 29:50 – Panel: That makes sense and flexible. 29:58 – Guest: The other complaint is that the Phoenix generator is pushing the community in the wrong direction by forcing a lot of things by default. When you generate your project with... My team we have used the configuration b/c it seems the right way to do, but what constitutes this? Should this go here and what is a configuration? 30:52 – Panel: I don’t have a synced answer – I don’t have a boundary to say what does or doesn’t’ go in there. 31:13 – Guest: Like the operator might decide to change the HPP port or maybe you want to...? You have to make the decision – what will those things be? 31:32 – Panel: React to a configuration change, it’s very clear to... 31:57 – Guest: It is very arbitrary by its nature. One of the main things (in the blog post) my coworker said it felt like a configuration. What does that mean? Should we have some sort of rules? What is a configuration and what isn’t? 32:33 – Panel comments. 32:55 – Guest: Now I am swinging in a new extreme. You started with parameters nothing more and there is nothing more than functions and parameters. 34:41 – Chuck: You keep bringing up JSON is there a reason why? 34:55 – Guest: I am not a super fan of JSON for various reasons but we decided on JSON b/c it’s fairly easy. Most of our clients and admin can add it. 35:18 – Chuck: Asks a question. 35:30 – Guest: Getting a configuration... 36:35 – Panel. 36:39 – Guest: With Distillery 2.0... 36:47 – Chuck: What formats do you like if you don’t like JSON? 36:58 – Guest: I am not sure. I would like to run everything in Elixir directly. 37:47 – Panel: I have been using Kubernetes. I like that I can have comments. 38:00 – Panel. 38:10 – Panel. 38:17 – JSON is terrible but you can use it and everyone can, too. 38:27 – Guest: I would probably pick JSON between those two. It’s the lesser of 2 evils. 38:40 – Panel. 39:03 – Guest: The key is to clean up this configuration in the first place. My impression is... 39:30 – Panel: I wrote a library, and there was configuration but it doesn’t belong – it’s not a configuration setting nor...so where should those kinds of settings be? I know they are just parameters, but...so we can pull out our configuration files? 40:11 – Guest: It should be grouped by scope. Take Phoenix application... 41:54 – Panel: That’s your exposed configuration – conceivably – but it should be hard coded. 42:04 – Guest: It won’t be hard coded, and the server will be different in production than your machine. 42:17 – Panel. 42:30 – Guest: Precisely. You have to ask: is this a configured parameter or not? 42:43 – Chuck: Can you talk about how to encrypt and/or protect these secrets? 42:56 – Guest: There are these secrets that are broad secrets via...and it depends on you how you’re going to protect them. Use some encryption scheme. 43:20 – Panel. 43:28 – Guest: Right. 43:31 – Chuck: In Rails it has a secret file, too and you have to provide the key to the app. Then your KEY is a secret. It feels like this circular problem. 43:53 – Guest. 44:54 – Panel: When you are dealing with that sort of thing...library will absolutely assume...and it limits flexibility. 45:17 – Guest: It’s not just an Elixir thing I have seen it in Erlang, too. 47:32 – Chuck: Any stories of people getting this wrong or right? I guess people don’t talk about that; any good stories? 47:54 – Guest: A lot of stories, actually! 49:52 – Panel: Being that Elixir is a more functional language, how do I put in a configuration that will be available at runtime and available very early. I think that is why we stick things up there by putting it in there. 50:35 – Panel. 50:43 – Panel: If it is a library and passes it to a configuration - where does it put it? 50:53 – Panel: A library and not an application... 51:05 – Guest. 51:45 – Panel: Where do I put it? 52:03 – Guest: There are some libraries that have to be configured before we start. The only case that needs some setting before we start is LOGGER. 53:00 – Panel. 53:15 – Guest. 54:00 – (Guest mentions à la Carte – check it out here! It’s just a factory.) 55:38 – Chuck: Let’s do picks! 55:46 – Fresh Books! Links: Ruby Elixir JavaScript React Erlang Kubernetes JSON Logger Docker Config Rethinking App Env Distillery Documentation Elixir in Action Elixir in Action – Book – 2nd edition Elixir – Library Guidelines Elixir Forum The 12-Factor App Distillery’s Documentation GitHub: Toml-Elixir GitHub: Riak_Ensemble GitHub: Elm – Beam GitHub: CodeC-Beam Library Guidelines – Elixir Configuring Elixir Libraries Handling Configurations Etcher Tweet Mashup Sasa’s YouTube Video Sasa’s Twitter Sasa’s GitHub Sasa’s Information at Elixir Conf Sasa’s LinkedIn Josh Adams’ Email: josh@smoothterminal.com Sponsors: Loot Crate Fresh Books Cache Fly Get a Coder Job! Picks: Sasa Run-time Library Guidelines Elixir in Action – Book – 2nd edition The Erlangelist Solid Ground Chuck Tweet Mashup My JavaScript Story Channel Shush App Mark Etcher.io Josh Elm Beam
Panel: Mark Ericksen Josh Adams Charles Max Wood Special Guest: Sasa Juric In this episode of Elixir Mix, the panel talks with Sasa Juric who is the author of Elixir in Action (2nd edition) and uses Elixir, Erlang, and OTP. He is from Zagreb, Croatia and you can check out his blog here! The panel talks about his book, past and current projects, in addition to configurations, and Elixir. Show Topics: 0:00 – Advertisement: Get A Coder Job! 0:50 – Chuck: Panel. Our guest is Sasa Juric. Introduce yourself to us please. 1:12 – Guest: I am known for writing my book and my blogs. I am president to the Elixir forum and helping people out. I have been using Elixir for 5 years; in the past I have used C++ and others. 1:46 – Chuck: App env and configuration and sounds like we could talk about more. Let’s start there, though. 1:59 – Guest. 2:03 – Panel: A little background with configuration b/c it’s been a topic in the community. There is a lot of discussion around it. What is the right way? And there is a change in how we deploy software. We have more docker containers and multiple stages of deployment and tons of configurations through environment settings. Anything you can talk about that? 2:51 – (Guest answers those questions. He discusses in detail about docker configurations. Also, the guest talks about the various settings per the different environments.) 7:25 – Panel: That was a thorough summary. 7:29 – Guest: I can talk more. 7:35 – Panel: So we have background on configuration is setup and the goals we have. What are some of the ways that a person with Elixir – how do they start? Tips / advice? They have their app and trying to go to production? 8:22 – (Guest answers the question.) Guest: 90% of the time, this is what you want to do. This is what you do...build it and put it in the folder structure, and you are good to go. Why is this good? You don’t have to have a bunch of... If you are using Phoenix than you need Node.js and you don’t want to have that on your production. You can easily run side-by-side different versions of Erlang and Phoenix. 11:40 – Panel: You can do that in a single docker file? 11:47 – Guest. 11:51 – Panel: You just copy the files... 11:56 – Panel: I learned I could do that by the distiller 2.0...I hadn’t encountered that before. 12:11 – Guest: Look into the distillery. I want to give compliments to Paul and the team is great. Go to Distillery and see the tutorials. 12:37 – Panel: People think I don’t want to use docker there is an option.... 13:01 – Guest. 13:04 – Chuck: Different types of configuration? 13:13 – Guest: Right this discussion too which is probably talking about my blog post, and I have this wild thought about configurations. We can discuss the issues and different solutions. We have these configurations files and they contain these time various configurations and... There is usually more than 1 configuration file. 17:53 – Panel: You only get agreement. I have had that problem, too, saying what is this configuration? What are THE Settings that are present and yeah that is a problem? You identify these problems in your blog, where it’s not checked in and the code will not... I have had to work around that in my projects. We are going to create a sample project and it will have defaults. So we can improve the situation. 18:45 – Panel: Class based configurations – I get angry. 19:05 – Guest: I try to challenge this status quo. Some people agree and others disagree. Some say this blanket statement. 19:54 – Loot Crate! 20:47 – Guest: Another thing to note is that configurations are free form key values. Remember, my point is that it boils down to some function being involved with these values. (Guest continues...) 23:36 – What is your direction that you are proposing? 23:40 – Guest: We are going to discuss other issues. 23:49 – Panel: As background, as apart of that whole configuration in those distillery docs... 24:41 – What is the next step in the discussion? 24:48 – Guest: Let’s take a step back. (Guest talks about Distillery 2.0.) 27:09 – Guest continues... 29:50 – Panel: That makes sense and flexible. 29:58 – Guest: The other complaint is that the Phoenix generator is pushing the community in the wrong direction by forcing a lot of things by default. When you generate your project with... My team we have used the configuration b/c it seems the right way to do, but what constitutes this? Should this go here and what is a configuration? 30:52 – Panel: I don’t have a synced answer – I don’t have a boundary to say what does or doesn’t’ go in there. 31:13 – Guest: Like the operator might decide to change the HPP port or maybe you want to...? You have to make the decision – what will those things be? 31:32 – Panel: React to a configuration change, it’s very clear to... 31:57 – Guest: It is very arbitrary by its nature. One of the main things (in the blog post) my coworker said it felt like a configuration. What does that mean? Should we have some sort of rules? What is a configuration and what isn’t? 32:33 – Panel comments. 32:55 – Guest: Now I am swinging in a new extreme. You started with parameters nothing more and there is nothing more than functions and parameters. 34:41 – Chuck: You keep bringing up JSON is there a reason why? 34:55 – Guest: I am not a super fan of JSON for various reasons but we decided on JSON b/c it’s fairly easy. Most of our clients and admin can add it. 35:18 – Chuck: Asks a question. 35:30 – Guest: Getting a configuration... 36:35 – Panel. 36:39 – Guest: With Distillery 2.0... 36:47 – Chuck: What formats do you like if you don’t like JSON? 36:58 – Guest: I am not sure. I would like to run everything in Elixir directly. 37:47 – Panel: I have been using Kubernetes. I like that I can have comments. 38:00 – Panel. 38:10 – Panel. 38:17 – JSON is terrible but you can use it and everyone can, too. 38:27 – Guest: I would probably pick JSON between those two. It’s the lesser of 2 evils. 38:40 – Panel. 39:03 – Guest: The key is to clean up this configuration in the first place. My impression is... 39:30 – Panel: I wrote a library, and there was configuration but it doesn’t belong – it’s not a configuration setting nor...so where should those kinds of settings be? I know they are just parameters, but...so we can pull out our configuration files? 40:11 – Guest: It should be grouped by scope. Take Phoenix application... 41:54 – Panel: That’s your exposed configuration – conceivably – but it should be hard coded. 42:04 – Guest: It won’t be hard coded, and the server will be different in production than your machine. 42:17 – Panel. 42:30 – Guest: Precisely. You have to ask: is this a configured parameter or not? 42:43 – Chuck: Can you talk about how to encrypt and/or protect these secrets? 42:56 – Guest: There are these secrets that are broad secrets via...and it depends on you how you’re going to protect them. Use some encryption scheme. 43:20 – Panel. 43:28 – Guest: Right. 43:31 – Chuck: In Rails it has a secret file, too and you have to provide the key to the app. Then your KEY is a secret. It feels like this circular problem. 43:53 – Guest. 44:54 – Panel: When you are dealing with that sort of thing...library will absolutely assume...and it limits flexibility. 45:17 – Guest: It’s not just an Elixir thing I have seen it in Erlang, too. 47:32 – Chuck: Any stories of people getting this wrong or right? I guess people don’t talk about that; any good stories? 47:54 – Guest: A lot of stories, actually! 49:52 – Panel: Being that Elixir is a more functional language, how do I put in a configuration that will be available at runtime and available very early. I think that is why we stick things up there by putting it in there. 50:35 – Panel. 50:43 – Panel: If it is a library and passes it to a configuration - where does it put it? 50:53 – Panel: A library and not an application... 51:05 – Guest. 51:45 – Panel: Where do I put it? 52:03 – Guest: There are some libraries that have to be configured before we start. The only case that needs some setting before we start is LOGGER. 53:00 – Panel. 53:15 – Guest. 54:00 – (Guest mentions à la Carte – check it out here! It’s just a factory.) 55:38 – Chuck: Let’s do picks! 55:46 – Fresh Books! Links: Ruby Elixir JavaScript React Erlang Kubernetes JSON Logger Docker Config Rethinking App Env Distillery Documentation Elixir in Action Elixir in Action – Book – 2nd edition Elixir – Library Guidelines Elixir Forum The 12-Factor App Distillery’s Documentation GitHub: Toml-Elixir GitHub: Riak_Ensemble GitHub: Elm – Beam GitHub: CodeC-Beam Library Guidelines – Elixir Configuring Elixir Libraries Handling Configurations Etcher Tweet Mashup Sasa’s YouTube Video Sasa’s Twitter Sasa’s GitHub Sasa’s Information at Elixir Conf Sasa’s LinkedIn Josh Adams’ Email: josh@smoothterminal.com Sponsors: Loot Crate Fresh Books Cache Fly Get a Coder Job! Picks: Sasa Run-time Library Guidelines Elixir in Action – Book – 2nd edition The Erlangelist Solid Ground Chuck Tweet Mashup My JavaScript Story Channel Shush App Mark Etcher.io Josh Elm Beam
Plex, it’s 18.10 time, Flatpak, Etcher, Linus and the code of conduct, social networks, Microsoft, self-driving cars. Deeeelicious.
Alison Davis: LinkedIn Ronald McCollam: @ronaldmccollam | ronaldmccollam.com Show Notes: 01:19 - The Future of IoT 04:57 - Where does Resin.io fit in? 07:04 - Founding Resin and The Unicorn 11:26 - How Resin Works 15:16 - Diffing 17:58 - Tooling and Workflow 23:02 - Resin is Open Sourced! 24:05 - Case Studies 30:04 - Security 34:47 - Scaling Up and Improving User Experience Resources: OpenROV Underwater Drones Etcher resinOS Transcript: ELRICK: Hello and welcome to The Frontside Podcast, Episode 80. We have a wonderful podcast today. My name is Elrick Ryan, a developer here at the Frontside and I'm going to be hosting the podcast today, in place of Charles because he's on the frozen tundra. I also have co-hosting with me today as well, another developer from the Frontside, Joe LaSala. JOE: Hello. ELRICK: Joe, how are you doing? JOE: I'm doing well, how are you? ELRICK: I'm awesome, man, and we have a wonderful podcast today. We're going to be talking about Resin.io and we have some wonderful people here from Resin with us, not one but two people came over from Arizona. We have Alison Davis, who is the director of product marketing and strategy at Resin. Alison, how are you doing? ALISON: Hey, Elrick, I'm great. Thanks for having us. ELRICK: Thank you for coming on. Also, we have Ronald McCollam, who is the solution architect at Resin.io, he's on the call with us on the podcast. Ronald, how are you doing? RONALD: I'm doing great, Elrick. Happy to be here, thank you for having me. ELRICK: Thank you for coming on. Thank you. Let's kick it off and we're going to talk about some IoT today, some Resin in IoT. What do you guys think is the future of IoT? What does it hold in your perspective? RONALD: If you had asked me a couple of years ago, I probably would have said that it's a bunch of connected refrigerators and maybe light switches and kind of left it at that. But the more I see the industry evolving, the more I realize that IoT really means that everything is getting interconnected and everything is sending data and exchanging data. I think we'll start to see IoT, not only in smart appliances and lights and so forth on the consumer side, but also on the industrial side. A lot of building automation, a lot of just more general information being provided by the environment and environments adapting to suit humans better. I think really the answer is IoT is going to be everywhere you look over the next few years. ELRICK: That is a broad takeover of IoT. It's going to be everywhere. ALISON: Yeah and I'll just add that we also think that IoT is going to become more prominent as compute power really does push further and further out to the edge. We see this trend happening already, where the amount of data and computing that needs to happen is too much to continuously be communicating back up to the cloud and more and more computing will need to take place on the edge in IoT devices and we really see these strong devices weakly connected as we often say as the future of IoT. One thing, we can talk about with Resin is, we see this creating what we call a management gap in between the developer and the fleet owner of these devices on the edge and the devices themselves and that's where Resin comes into the picture. ELRICK: That's interesting, so these devices are going to be sharing the computation and taking away some of that computations from the actual cloud? ALISON: Yeah, we think so. I think the devices themselves are getting stronger and it's becoming more and more possible for that to happen. Then there's just simple reasons of physics and economics why it will be too slow and too expensive to continuously be relying on the cloud for compute. This is a trend that we really see happening and something that we want to help fill that management gap between developers and their fleets of devices that are running out on the edge. ELRICK: I can see how that could be a plus for a company to not have to try to do all these computation on the cloud. As Ronald said earlier, since IoT is everywhere and it's going to be in devices all over the world, we could end up with probably trillions of devices trying to leverage cloud to do with computation and taken some of that away from the cloud would be a definite plus because I don't think that there is a platform that can handle that kind of data throughput. RONALD: Yeah and even as Alison said, there are just times that for reasons of the laws of physics, you really can't wait for that round trip to the cloud. We'll go sci-fi here. Let's say you've got some automated robot in an environment with a lot of people around, you don't want that thing sending all of the camera information that it has as it's moving through a crowd of people up to the cloud, waiting for the processing to happen there and then being pushed back. By the time it gets there, that robot may have already run over somebody. We really don't want that. You've got to do some of that processing out at the edge where the data is being collected. ELRICK: Yep. That's both technology issue and legal liability there so we got to make sure there's no robots running over anyone. RONALD: Yeah, exactly. ELRICK: How does Resin then blend itself to helping to promote this computation in strong devices that are weakly connected? RONALD: What Resin does is really enable you to be sure that you are running the right code on the right device and that any updates you push out to that device are not going to take that device offline or brick the device. Resin really sees whatever is running on the device as sort of a black box. We really don't have a lot of opinion about what the right thing to do on your device is. We think you know that better than we do. But what we can do is help you make sure that the devices that you have out in the field are always running the latest code, that when you find security flaws or you want to push an update out, you can always reach those devices and be sure that you can do that safely and effectively. Really, from our point of view, we want to make sure that the IoT is running safely and is always running the latest and greatest, the best code that you can possibly have out on your devices. ALISON: You need to have a way to remotely manage an update on all of these devices in a way that won't brick the devices or make you lose access to them when you can't physically access the device again. Resin is here to make it simple, easy, efficient, fast and most importantly, safe to update, as Ronald said, the code and software running on the devices so you can push updates as often as you like, send security patches and then remotely monitor what's going on with your entire fleet, all from your laptop. ELRICK: That's amazing. We've had some experience using Resin here at the office and we've been very excited and delighted with the service. I've been in Boston, actually pushing code down to Texas and it happens like almost instantaneously, which is amazing. JOE: Yep. We really enjoy using it. I think it's really cool. We're only using it currently on one Raspberry Pi but it be really fun to have a fleet of Pis and get expand that reach. I got to ask what the origin story is for the Unicorn that gets displayed. ELRICK: Yeah and in that vein, what is the founding story like? How was Resin founded? RONALD: The founding of Resin is really an interesting story because it's not that there were a bunch of people sitting around in a boardroom with a whiteboard and saying, "What's the next big thing coming along, what can we get into?" This really came about as a result of real world events. Back in the 2012 Winter Olympics in London, the team that would later go on to found Resin ended up in charge of a project dealing with a bunch of digital signs, so think of advertising and information about what was going on in the Olympics. These were all over the city of London. Mostly on a really, really interesting smart bomb proof rubbish bins. They really went all out to make sure nobody could come to harm as a result of these. But the team was intending to push some updates out to these devices -- update the information on the signs -- and had inherited this project that had been built where they were really doing what everybody was doing at the time. You just SSH into a device remotely, you run a set of script and you kind of hope everything works. That's how we had a whole bunch of people walking around the city of London in the middle of winter with USB keyboards and USB sticks, trying to get all of these individual rubbish bins back online and back up and running after a bad update. After pulling back from that, they said, "You know, this is terrible. There ought to be a better way to do this. Why did we end up in the situation?" It turns out, there really wasn't a great way to do it at the time. That's where Resin comes from. It's an effort to fix this problem, not only for ourselves but for everybody in the world to make it easy to push updates to remote devices and be sure that you're not going to have to walk around in the cold and the sludge to try to get those things back online if you do a bad update. I don't really know what the origin of the Unicorn is. I know it was an in-joke with that team that, I guess kind of slipped out more into the real world. I don't know, Alison if you know more about the Unicorn than I do but it's still a fun thing to see every time you do a push. ALISON: Yeah, I think our CTO Petros, who was also the first person we think anyway to -- when we get into this when we talk about how Resin works -- port Docker to ARM, which as a core piece of the Resin platform, he wanted to add in something fun so that when you complete a successful deployment on Resin, you see the Unicorn and that means that your push is successful and your device has fully downloaded the update. I think that's part of what makes Resin 'Resin' is where we're very, very serious and we want everything to be secure and completely buttoned up. But we also like to keep things a little bit fun and make sure that, not only is it safe and easy to deploy updates but also enjoyable. ELRICK: We definitely enjoy seeing that Unicorn as well. I've just been pushing the simplest code of all time just to see that Unicorn pop up on a successful build. RONALD: Yeah, it's always nice to get some feedback that everything worked well and everything is going perfectly for you today. ELRICK: Yeah, that's beautiful. We were thinking about that as we were talking about some IoT things before. We had not the best product idea in the world and since everyone drinks Topo Chico in Texas, we were like, "I wonder if we had a Topo Chico popper in the refrigerator," and then we're like, "If millions of people end up with this Topo Chico popper, how we then going to update the code on these Topo Chico popper in everyone's refrigerators?" That's where we're like, "Resin.io would be a perfect solution for that," or as you said, half people are walking around in the sludge going to update these devices. These devices could be located anywhere in the world and Resin seems to be a platform that could handle that type of requirement that you have to update these devices that could be anything and anywhere. I guess we can talk about how Resin then works in order to get that code deployed to anywhere and keep all of these devices updated with fresh code, as you said. RONALD: Yeah, absolutely and you're completely right. This is designed from the ground up to be something for working with distributed systems, devices that are not really under your physical control. They may not even be on a network that you control so this could be something that is out in the middle of the ocean, up on top of a mountain. Anywhere that you have network access and you want to be able to update a device is really the target for Resin. The way that this works is there's a lot of bells and whistles and things that we've learned over years of updating devices and managing devices but at kind of a high-level, we maintain a host OS on the device. There's a stripped-down version of Linux on that device that maintains a connection to the network. Really, its entire job is to just keep that device humming, keep it on the network and not do a whole lot else. Everything else happens inside of a Docker container and if you're not familiar with Docker, Docker is really sort of like a lightweight virtualization. It's a container technology that allows us to pack an application, all of its libraries, even its operating environment into one container that can be deployed and managed very, very easily. Because everything is sitting inside of a container, we can push updates to a container and not touch that underlying OS layer that is managing the network connection. Even if you do push bad code, that's not great. Your code might crash but the host operating system is still going to stay online. It's still going to maintain that network connection so that you can roll back or push another update to fix things very quickly. Then on top of that, we layer on a lot of technology that we have developed in-house to do things like computed delta between what is running on the device and what code you have just pushed to us to get on the device. You might have an eight gigabyte application running on one of these IoT devices but if you make a one kilobyte change, we're really only going to push about one kilobyte out to the device. We're not doing a full blast of a firmware update, making you pay for eight gigabytes of data over your 3G connection. We're really doing everything we can to minimize the amount of data that we send over the air, both so updates go faster but also so that we don't have to pay as much for bandwidth or wait as long in intermittent network connectivity environments. Then the final part of this is that by using Docker, we get for free some of the really cool things that Docker brings to typically larger data center environments. We have things like atomic updates. When you push an update out to a device, if you lose power or you lose connectivity in the middle of that update, that's fine. The device is just going to keep running the same code that it had on it previously until network connectivity is restored. It will resume that update and only once the full container is downloaded and put on the device, it will shut down the old version and start running the new one. There's really a lot of under the hood stuff that we've developed and we've layered on to make sure that when you push an update out to these devices, it's always doing it safely and always doing what you want to do. I get to say this because I didn't write any of the underlying code. I'm constantly amazed at some of the stuff that Resin does under the hood. It's really fun to see, just how easy it can be to update devices that are anywhere in the world. I'm constantly pushing things to London or to Seattle. I'm in Boston so it's really cool to see these things update all over the world. ELRICK: That is amazing, all of the various things that Resin gives you out of the box that you don't have to worry about as a developer, as a company. It provides you that underlying foundation for you to then build whatever product that you want to build or software that you want to build on top of it and it's absolutely amazing. I'm blown out the water every time I do something out on it as well. RONALD: Oh, cool. I'm really glad to hear that. That makes me feel good. ELRICK: That's interesting. There's so much in what you just said. There's so many different parts. I know that Joe one time, he was wondering how you guys actually do that diffing in the code that's pushed up to then on the download those changes and not the entire bulk of that code. Can you dive any deeper or give a further explanation on that portion of it? RONALD: Yeah, absolutely. I'm happy to. At a high-level, it's very simple to explain. Of course the devil is in the details. It's just like, "Updating the device. Oh, great. I'll just push bits out to it and run some stuff." If you think about it too simply, that's how you end up having to trudge around in the snow with USB stick. But at high-level, we're tracking what's already deployed on all of those devices. Because the devices out in the field are in contact with the Resin service on the backend, we know what version of your code is running on every single device at any given time. Because of that, what we can do is when you push a new version of your application, we can just do a binary diff against the image that was pushed out earlier to the image that you just wanted to push right now. We can say, "This device is running version one. I want to bring it to version three." I already know what version one is. I, obviously know what version three is because I have it right here. We'll just calculate a diff between those two versions and send only that diff out to the device. Then because the device is fairly intelligent, we can do a lot of computation at the edge to just reverse that diff and apply it on top of what's already there. These are Linux devices. They can run the same code that we use on the backend to generate that diff just in reverse, to generate the final image that we want to deploy. Even if you've got devices on five different versions of your application and you want to push them all out to the latest version, we can apply a different diff for every single device and push that diff out to the devices and they will then apply it on top of the container they're running. From the user perspective, it's nice and easy. Under the hood, there's a lot going on that we've developed to make sure that process always happen safely and securely. JOE: That's very impressive. We use Resin for our lights here in the office. We have a Raspberry Pi that controls a bunch of Philips Hue lights. I just started here a few months ago when I came on. Elrick had already have been poking around this Resin stuff and particularly that part, being able to do that diff and push only the code necessary, it was really impressive. It's also very easy to me, instead of 'get push' origins, it's 'get push' Resin, like you have the ability to send it out in your normal workflow. RONALD: Yeah, that was, honestly one of the big issues that we've seen in the IoT space in general is that the tooling and the workflow that people are using, I don't want to insult it but it's out of date. It's very much a 20th century mindset. People aren't tending to use the latest tools. They don't have continuous integration. It's really like I'm writing some C code or assembly and I'm blasting out a firmware update. That's worked in the past but it doesn't get to the scale that you can do things in the web and cloud world. Look at Facebook. They're doing multiple deployments a day sometimes to production and when was the last time you heard about a deployment taking Facebook down. There's a lot of tooling and a lot of really cool development that has been worked on and put into practice over the past 10 or 15 years to make those things possible. We're taking those same tools and we're bringing them to the IoT world. Just like you mentioned, when you do a deploy through Resin, you're actually doing a get push. We're using the exact same tools that you would use to deploy to a cloud environment but now, you're deploying those out to an IoT environment so we can fit right into a continuous integration pipeline. We can let you do things like distributed development. Resin is a very distributed team. We have people in something like 19 or 20 countries. We're using these tools to develop Resin. We kind of said, let's use those same tools to bring that experience to the IoT world. It's a really great way if you already have some experience with cloud development or modern desktop software development to be able to use those same tools for IoT, without having to come from a really heavy hardware background or firmware background. I, myself am a software guy and a web guy from way back so it's really cool for me to be able to deploy things on the devices without having to think about assembly code or firmware blobs or things like that. I can just write, even maybe some Electron code, get push that and it lands on a Raspberry Pi and I've got my code running on a device somewhere out in the world without me having to learn a new tool set. It's really powerful from that aspect as well. ALISON: An important point is that we want to bring the best and most modern and newest tools to the IoT but we also want to bring a workflow that feels native to developers who are coming to IoT from the cloud and web world. Given the growth that we think will take place in IoT and more and more devices moving out to the edge and more compute are moving out to the edge, we'll need more and more developers to be building software and code for these devices and we want to make it very accessible and easy and native to all developers and to the workflows that they're used to so they can develop applications for IoT and have it feel like a very native workflow. JOE: You've hit on what I think is like a very important point about this. The IoT is a marriage of these systems programming, embedded programming and web development in a way. That's a very different codes that is written. People who write code in embedded systems, it's a very different world than what we do as web developers. The one thing that you might be able to bridge that gap with is a common workflow and we're all used to version control or used to kind of pushing code out the way that we push code out and Resin sits right in the middle there. That's worth a lot, I think. ALISON: Exactly. RONALD: That exactly it. There are millions of mobile developers and millions of web developers but only hundreds of thousands of traditional embedded developers. Being able to bring those millions of developers using their same tools they're already familiar with to this IoT space, I think just really dramatically increases the opportunity for people to get involved and to build the next cool thing. JOE: Definitely. ELRICK: That is totally true because we were able to hook up Resin into CircleCI so we can get a continuous integration and continuous deployment pipeline. It was definitely a painless solution to set up. That is testament to that, if anyone wants to build something on top and start to add other things into Resin that you guys definitely do have those hooks for people to then, add whatever they need to build, whenever they need. RONALD: Yeah, definitely. We think that the days of walled gardens are really over. We don't want to see companies try to lock other people or locked developers into a single application or a single environment or a single device. We really want these things to be as open and interoperable as possible. Part of that is just making sure that everything that we do is also open and interoperable. We expose all of our APIs to anyone, you don't have to use any of the Resin tooling, you can wrap that right into CircleCI, for example, you can pull that into Jenkins, you can pop this right into your development workflow and just keep rolling right along and we're happy to be a part of that. ALISON: I think that brings up another important point about what Resin does too is that we're really committed to open sourcing all of Resin and currently everything that runs on the device, including our operating system -- resinOS -- is open source so that people can see exactly what's going on. We even had people take our operating system and tweak it to support new device types or add in their own functionality on top of that OS. We're working really hard to actually open source all of our backend as well. That's something that's really important to us in this world of open and accessible software for IoT. We want this to be something that feels approachable and open to anybody. ELRICK: That is amazing. I didn't know that all of the code or majority of your code was open source. You heard it here first. If you want to go and check out some awesome code, head over to GitHub and look up Resin.io's codebase. ALISON: Yeah, all of the code on the devices and the whole operating system is all open source already and then where we're releasing all of the pieces of our backend so that if you want to run Resin on your own, you can do that. Hopefully, by the end of the year, I think is our goal. ELRICK: We've been talking about Resin and all of the benefits that Resin would give developers and companies that want to build products and it has a slew of things that it gives you out of the box, if you don't have to build that you can then build on top of. It will be interesting to hear some case studies or how people are actually using Resin in the wild to bid out their products. Do you have any specific case studies or things that you can talk about in respect to how people are using it out in the world? RONALD: Yeah. We have a huge variety of companies using Resin. We like to say that it's everything from smart locks to skyscrapers. The smallest physical device that I know of that we're managing is smart locks like actual door locks on houses and buildings. Then we have things as big as skyscrapers like industrial automation, building automation. It's really all over the place. One of the most interesting use cases to me is there's a company called OpenROV that does underwater drones. They have remote submersible vehicles that are exploring and doing cool science underneath the ocean. They're managing the software that's running on those devices using Resin. They throw these submarines out in the ocean, they let him tool around on their own. When they come up to the surface, they send back data and check in for updates so they can be constantly refining what those submersibles are doing out in the ocean without having to physically go pick them up or bring them back in to make changes. It's a really, really exciting thing to see. But we've got similar stories in things like power generation. I mentioned earlier out in the middle of the ocean or on top of a mountain that was literal. We do have companies that are making wind turbines that are in all kinds of environments that are very difficult to get to. They really want to get the top performance out of these devices. If you can pull a 1% increase in power generation from a wind turbine, you've really started making a lot more money. That's a very significant improvement. They have devices in these wind turbines that are constantly monitoring every part of the turbine itself and the environment so they're feeding data back and then they can use that to build a new model of the best way to say, angle blades on a turbine and then push that new model out to the device without having to go miles out into the ocean or up on top of a mountain to physically touch those devices. Again it's a really cool way of being able to pull data back in, modeled it in the cloud and then push that back out to the edge for application without having to physically visit every one of those devices. It's just really exciting to see all the cool use cases that Resin has being used in. ELRICK: That is amazing. I actually gave a talk one time and I said, these devices could be out in the middle of the ocean somewhere, who knows? And someone could be pushing updates to it and it's amazing to hear that someone is actually doing that. I didn't just pull that out of the thin air. This is a real thing. RONALD: Yeah, absolutely. We've got, like I said, out in the ocean, on top of mountains. We've got ones in the middle of cities. Anywhere that you have a network connection, you can put a device. We even have some companies doing things over 3G or even 2G modems, I think like out in the jungle or in very rural areas where you want to be able to collect things like environmental data or maybe air quality information. Really, anywhere that you can have a network connection, you can have a device that you're managing and updating and making sure it's kept up to date without having to physically go touch that thing. ALISON: And Resin really is use-case agnostic and we see end users using Resin in their workflow, no matter what project they're working on. It all comes down to, I think all of these companies and projects are looking for ways to operate more efficiently and to gather data about their businesses and their projects. Any company in any business can use IoT to improve their operations. We see more and more companies finding ways to incorporate IoT into their work and I think part of that is driven by the availability and accessibility of tools like Resin devices, like the Raspberry Pi. That's affordable and easily available and quick to get up and running on. That's a new trend and I think it's enabling a lot faster and broader adoption of IoT. JOE: Absolutely. It feels constantly like we're right on the cusp of something with IoT. But we do work in that space a lot just in our own time and as part of the work that we do here at the Frontside, we're always finding the tool set seems a step behind and Resin is a stark contrast of that. We're coming into a whole new era of computing with something with a very powerful tool in our belt already. That is very well fleshed out. Thank you for that. RONALD: Yeah, thank you. It really does feel like we are on the verge of a sea change in how we see computing. We've gone, like I said from a few years ago thinking of IoT as sort of silly things like smart refrigerators. I shouldn't say silly but just sort of one off use-case like smart refrigerators or smart lighting. Now, to the extent where it's really about pervasive computing and I think we're just barely starting to scratch the surface of what that means and how that's going to change the world when we start having data about everything that's going on in the world around us. All of the equipment that we have and all of the compute power that we have around us is able to adapt to us and change as the needs of the environment change is just a really exciting time. I don't even think we can predict what the world is going to look like in 15 years as a result of this. ALISON: As IoT and edge computing becomes more pervasive, we touched on this at the beginning but this is where management and security become really important and you hear a lot of people in the press and elsewhere talking about the security of IoT devices and how they're vulnerable to attacks. This is where something like Resin is really important where you need to be able to access and be able to update and send security patches to those devices remotely and to send those updates constantly so that they're not vulnerable. As this field grows, which we think it will exponentially, we really need to find ways to fill this management gap and Resin, hopefully can help do that to some extent. RONALD: I think that traditionally, if you were building a device, you think like a hardware manufacturer like Alison says, you're not thinking about necessarily security and updates because in the past, it was just, we build a device, we'll put it out in the world and that's it, unless the things are catching on fire and we have to do a recall, we just move on to the next thing. But today, all of these devices are connected to the internet, which means they're constantly being attacked, people are looking for vulnerabilities and as soon as one of those is found, that spreads across the world like wildfire. We see the news articles on a weekly basis of IoT devices being used as part of botnets or being taken offline. Having a way to make sure that you can constantly address those issues as they come up is really, really important. Even if you're a hardware manufacturer, once that device is released, you have to think like a software company. You have to be thinking of updates. You have to be thinking about security all the time or you're really letting your customers down. JOE: Yeah, that's very true and the only way to mitigate threats is to constantly addressing those threats. I've worked in the security space. There's no such thing as secure really. We're never going to reach a level where it's like, we solved it. You have to constantly be rolling with the punches, so to speak. It's great that that's built in with Resin. RONALD: Yeah, exactly. Security isn't really an end state. You don't ever get to say, "Yes, I'm secure now." It's a process. It's how do I deal with things as they happen because they will happen. ELRICK: That is definitely true and people shouldn't be afraid to be constantly pushing data to these devices because as you said, people and some of your customers are using Resin on 3G and 2G networks so that is proof there because of the diffing that you do in the backend and you only have to push down a small subset of your code that you can definitely just constantly be pushing and staying up to date to make sure that you're on top of your security issues. RONALD: Yeah, exactly and it's only going to become more and more important as we expect these devices to do more things and work with more data and perform more analytics at the edge. We just have to stay on top of that as an industry. ALISON: And we have customers who tell us that before Resin, they used to be afraid to push updates and they would put it off until the last possible minute. We want to create an environment where the opposite is true, where you push updates all the time, not only to push any security patches but also to make your applications better and push better code out to your devices. We want people to feel empowered and they will able to do that as often as they would in the cloud [inaudible]. ELRICK: Yeah, that's definitely true because as you said, as we're getting more web developers and people into this space, we're used to, as web developers constantly pushing code and constantly sending updates about our codebase out there. As more developers from this base come into the IoT space, that's definitely something that they're going to be looking for and Resin does provide that capability out of the box. JOE: It's interesting that it follow the same pattern because we weren't always used to that. We used to plan on a quarterly basis and releases would be these huge multi-day headaches with people on call. We kind of started going towards this very fast incremental thing and it seems like that's a pattern that isn't just web, I guess. RONALD: Yeah, definitely. That model really has evolved from a lot of heavily painful work. Lessons people have had to learn over the course of years or even decades, tools that have taken thousands of hours to build, all of these processes are hard won knowledge. We really should be applying that everywhere we possibly can. Let's bring that into the IoT world and not start over from scratch and have to relearn all those lessons and reinvent all those particular wheels. ELRICK: Resin is being used by a lot of varying companies and you have a wide customer base. Are there any use cases that came up that then pushed you to say that we have to build some for the features into Resin or some other type of software to help Resin or leverage Resin? ALISON: Yeah, definitely. We've seen over the last couple of years, as you mentioned a lot of different use cases and customers using Resin. Our goal is really to make it easy and simple for fleet owners, as we call them, people who are managing fleets of IoT devices. We want to make it easy for them to scale as quickly and seamlessly as possible. Anytime we build something, either into the platform or adjacent to the platform, it's always with that in mind. One good example is the tool that we built called 'Etcher,' which some people may be familiar with even if they aren't familiar with Resin. Etcher is essentially a way to earn SD cards and USB sticks and essentially provision IoT devices in a way that's much easier than just using DD, if you use that or any other solution that you might be using and that was borne out of our realization that this was actually a big pain point for our users, that they were having a hard time provisioning their devices. We just built Etcher and actually released it as its own standalone open source tool. Similarly, that's actually why we built our own operating system, resinOS, because there was no operating system that existed yet that would allow us to run containers on constrained IoT devices. We did the same thing, where we release that as its own standalone open source projects so that people can benefit from resinOS, even if they aren't using Resin the platform. We're always looking for ways to make that process of scaling up and deploying fleets easier and releasing those projects as openly and broadly as possible. RONALD: Yeah, to add to that going forward, we're also looking to make some improvements into the Resin platform just based on a lot of the feedback that we've gotten as people are managing these very large fleets. We are, right now working on improving the experience when you are managing multiple containers on a single device. A lot of times, people will have microservices where they'll have separate Docker containers for each function that a device is doing and it's doing multiple functions. We're working on improving the user experience of deploying those individual containers and managing multiple containers on one device. We're also looking at ways to extend Resin from Linux devices into some smaller devices and some things that are not necessarily running Linux but are still out in the real world, out in a customer environment or out in nature, wherever you have those devices that you want to be able to manage them. We want to wrap that into the Resin experience as well. It's really a constant process of refinement just based on what we see as the IoT develops. Again, it's a really exciting time to be in this industry. ELRICK: That is wonderful that you guys are keeping your finger on the pulse, in terms of your customer base and the feedback that you're getting to how people are using Resin and then implementing and looking for ways to improve the platform and then also open source and get your solutions into the hands of developers and into the hands of your customer base and that is a testament to just how wonderful Resin is as a company and as a platform. I think everyone out there should then go out and use Resin or at least attempt to use it because the entry into using Resin is very low. You can ramp up and start using it any time and extremely quickly. ALISON: We encourage anybody who is interested to sign up and it's free to get started. Your first five devices are always free. We have great support. We have a really active community forum so there's lots of people there to help guide you along. But as you said, the barrier to entry is quite low by design so really anybody should go ahead and try it out. If you have a Raspberry Pi sitting at home or at work, we like to say that you can get started over a lunch break and it should only take you about 30 minutes to get your first successful push and see your first Unicorn. ELRICK: That's awesome. You heard that. Go and use Resin and on your lunch break, you can see a Unicorn. Well, that's it for our podcast today folks. We had a wonderful podcast talking about Resin.io, the future of IoT, all the places that you can use Resin and how to deploy code all over the world, to all your embedded devices and all of your IoT devices. On behalf of Joe, Alison, Ronald, the Frontside and myself, I would like to thank you all for taking the time out to listen to this podcast. Remember you can reach us at Frontside.io. If you have any projects that you're working on and want to tell us about it, you can reach us there and you can also, if you want to learn anything further about Resin, you can head over to Resin.io and remember you can see that Unicorn at lunch time. That's it for the podcast today and thank you all for listening.
This week we take a look at how you can implement a domain controller on Linux or get the same functionality as active directory on a Linux ecosystem. Plus the most calls we've ever taken. -- The Cliff Notes -- Linux Active Directory Systems RAZDC (https://sourceforge.net/projects/razdc/) FreeIPA (http://www.freeipa.org/) Etcher.io (https://etcher.io/) Invoice Ninja (https://www.invoiceninja.com/) DD Command sudo dd bs=4M if=/path/to/iso of=/dev/sdc && sync -- Noobs Corner -- Check out the Ask Noah Dashboard (http://www.asknoahshow.com) -- Stay In Touch -- Find all the resources for this show on the Ask Noah Dashboard Ask Noah Dashboard (http://www.asknoahshow.com) Need more help than a radio show can offer? Altispeed provides commercial IT services and they’re excited to offer you a great deal for listening to the Ask Noah Show. Call today and ask about the discount for listeners of the Ask Noah Show! Altispeed Technologies (http://www.altispeed.com/) Contact Noah asknoah [at] jupiterbroadcasting.com -- Twitter -- + Noah - Kernellinux (https://twitter.com/kernellinux) + Ask Noah Show (https://twitter.com/asknoahshow) + Altispeed Technologies (https://twitter.com/altispeed) + Jupiter Broadcasting (https://twitter.com/jbsignal)
Andreas berichtet von seinem Raspberry Pi und Sven hinterfragt, ob man bei seinem digitalen Schweizer Taschenmesser zukünftig nur noch mit ein, zwei Klingen auskommt. Patrick findet beides dufte. Lieber Fluggast, wenn dir das Gehörte gefällt oder dir Sorgenfalten auf die edle Stirn fabriziert, dann haben wir etwas für dich: iTunes Bewertungen. Follow-Up TableFlip Gewinnspiel Christian Tietze lässt uns ein paar Lizenzen für TableFlip, die Markdown-Tabellen-Wunderwaffe für den Mac, im Cockpit liegen. Also schmeißt mal Twitter an und denkt euch einen Tweet aus der mit Markdown anfängt und mit @derubercast aufhört. Kreativität und schlechte Witze sind wie immer willkommen. Spotify und Kopfplatz The combined service costs €14.99, which is roughly a 25% discount on the standard cost of subscribing to both Spotify Premium and Headspace separately. TechRadar: Spotify and Headspace team up to charge a premium for meditation and music YouTube, GEMA, YouTube Red “After seven years of tough negotiations, the conclusion of this contract with YouTube marks a milestone for GEMA and its members,” said GEMA CEO Harald Heker. “We remained true to our position that authors should also get a fair remuneration in the digital age, despite the resistance we met. It is crucial that the licensing agreement that we have now signed covers both the future and the past. By reaching this agreement, we can secure the royalties for our members.” The reference to the “future” here is notable, given that YouTube’s subscription-based service, YouTube Red, is expected to be launching in Europe sometime in the foreseeable future. As things stand, YouTube garners money through ads. But with YouTube Red, ads are removed from videos, something the contractual agreement between YouTube and GEMA has taken into account in terms of how royalties are collected and distributed. Venturebeat Sonstiges IFTTT – Von Rezepten zu Applikatiönchen. Noch mehr Adapterwahn. Sennheiser Story 2.0 Amazon: Sennheiser MM 550-XT Sennheiser BA 370 PX - - Rechargeable battery module Amazon: Sennheiser PXC 550 Paid Plans bei Butler Bot OPEN 2016 Raspberry Pi Wofür kann man den Pi einsetzen? Mac Mini Ersatz (sehr limitiert). IoT Device. Präsentationsrechner für die Familie. Urlaubsfotos zeigen beispielsweise. Urlaubsrechner, weil das iPad so schwer ist. Gast-Rechner für Besuch. Den eigenen NAS noch weiter absichern. Gehäuse und Co: Raspberry Pi 3 Starter Kit SD Karte HDMI auf VGA ModMyPi Betreibssüsstem: Apple Pi Baker Während der Sendung noch im Test war Etcher. Eine Alternative zu Apple Pi Baker, um Images auf USB zu klonen. Hier die Empfehlung. 11 Raspberry Pi OS for Everyday Computing – Best of Accessories: Aller möglicher Hardware Kram bei ModMyPi Rii K12 Bluetooth Rii i8, Rii i8+ Workflowvereinfachung. Braucht man das eigentlich alles? Merlin Mann & Dan Benjamin Back to Work 280: The Big Filter Kobayashi Maru Yak shaving Unsere Picks Patrick: Hörbuchautoren-Update per IFTTT ==> (1) Auf der Wikipedia den Autor raussuchen, (2) den Atom-Feed der Seite in IFTTT eintragen und nach dem Tag “Audiobook” (oder halt deutsch, ne wahr?) als Alarmgeber nehmen und sich dann per Email oder so Benachrichtigungen zukommen lassen. Andreas: Jaikoz Sven: Mini Metro In Spenderlaune? Wir haben Flattr und PayPal am Start und würden uns freuen.
ELEKTRODOS show of the 22nd February 2016, dedicated to new electro songs from producers, such as Tanzkonsol / Slaves Of Sinus, Kretz, Cybereign, Baz Reznik, LE MATIN, Dubb Parade and Etcher. With DJ Set from Kenny Lee Solares ELEKTRODOS show del 22 de febrero del 2016, dedicado a novedades de artistas como Slaves Of Sinus, Kretz, Cybereign, Baz Reznik, LE MATIN, Dubb Parade Y Etcher. Con DJ Set de Kenny Lee Solares Tracklist: 01. Slaves Of Sinus - Songs Of Thypes 02. Kretz - We Are Cripspy 03. Cybereign - Killer Machines 04. Baz Reznik - Hidden 05. Le Matin - Suicide Commercial 06. Dubb Parade - Montero 07. Dubb Parade - Lucifer 08. The Subdermic - Joyride 645 09. Etcher - Departure 10. Kenny Lee Solares DJ Set Kenny Lee Solares DJ Set Tracklist: Barry Hewitt (Trichome) _Ass Above So Below Fleck E.S.C. - Facts Hydraulix - Hydrospace ADJ - Deepa 214 - Autoparts JFrank - Jupiter Funk Digitizer - Robotnik PL_anet - Level 1 Datacrashrobot - Asynchronous I/O Coderising - Inbound Prototype -Stimme Der Energie (Anatecone Rmx) Coderising - The Relay_2 Soundchasers - Crystal Lake
© 2020-2025 Ivy Podcast Discovery LLC
