Website displaying info about free software Unix-like distributions
POPULARITY
5 episodes with DistroWatch
4 episodes with DistroWatch
3 episodes with DistroWatch
2 episodes with DistroWatch
2 episodes with DistroWatch
3 episodes with DistroWatch
2 episodes with DistroWatch
2 episodes with DistroWatch
Contenuto disponibile in forte anticipo per gli ascoltatori premium.
Pues he decidido hacer la comprobación de la censura de Facebook hacia recursos que tienen que ver con Linux y algo hay. Además, ha salido un nuevo firmware (1.5.0 Beta) para la Rodecaster Pro 2 y Duo. Te invito a debatir sobre este tema en el Foro de Como Pienso Digo https://foro.comopiensodigo.com Y otras formas de contacto las encuentran en: https://ernestoacosta.me/contacto.html Todos los medios donde publico contenido los encuentras en: https://ernestoacosta.me/ Si quieres comprar productos de RØDE, este es mi link de afiliados: https://brandstore.rode.com/?sca_ref=5066237.YwvTR4eCu1
Facebook is flagging and censoring links to DistroWatch.com as "malware". But, despite what many are reporting, discussions of "Linux" are not censored. More from The Lunduke Journal: https://lunduke.com/ This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit lunduke.substack.com/subscribe
Docker - https://www.docker.com/ Podman - https://podman.io/ Kubernetes - https://kubernetes.io/ Jitsi - https://jitsi.org/ Mumble - https://www.mumble.info/ Cockpit - https://cockpit-project.org/ Azure -https://azure.microsoft.com/en-us/free Google Cloud - https://cloud.google.com/ AWS - https://aws.amazon.com/ K3S - https://k3s.io/ Docker Swarm - https://docs.docker.com/engine/swarm/ AppArmor - https://apparmor.net/ Python - https://www.python.org/ Banshee Video Card (3dfx) - https://www.techpowerup.com/gpu-specs/voodoo-banshee-agp-16-mb.c3561 GIS - https://www.esri.com/en-us/what-is-gis/overview GPS - https://www.gps.gov/ Java - https://www.java.com/en/ Ruby - https://www.ruby-lang.org/en/ Groovy - https://groovy-lang.org/ Grails - https://grails.org/ Forth - https://www.forth.com/forth/ V (programming language) - https://vlang.io/ BSD - https://www.bsd.org/ ZFS - https://arstechnica.com/information-technology/2020/05/zfs-101-understanding-zfs-storage-and-performance/ Slackware - http://www.slackware.com/ Absolute Linux - https://www.absolutelinux.org/ Windows 3.11 - https://winworldpc.com/product/windows-3/311 DOS 6.22 - https://winworldpc.com/product/ms-dos/622 Storm Linux - https://distrowatch.com/table.php?distribution=storm Alpine Linux - https://www.alpinelinux.org/ Turbo Linux - https://distrowatch.com/table.php?distribution=turbolinux Mepis Linux - https://distrowatch.com/table.php?distribution=mepis Sparky Linux - https://sparkylinux.org/ DistroWatch - https://distrowatch.com/ Mandrake Linux - https://static.lwn.net/2000/features/LinuxMandrake.php3 Mandriva - https://distrowatch.com/table.php?distribution=mandriva Fedora Linux - https://fedoraproject.org/ Windows XP - https://en.wikipedia.org/wiki/Windows_XP Oxford University - https://www.ox.ac.uk/ Cambridge University - https://www.cam.ac.uk/ HTML - https://www.w3schools.com/html/ CSS - https://www.w3schools.com/css/ Javascript - https://www.javascript.com/ Freenode IRC - https://freenode.net/ KDE - https://kde.org/ Manjaro - https://manjaro.org/ Unity - https://unityd.org/ OpenSuse - https://www.opensuse.org/ Enlightenment - https://www.enlightenment.org/ Fluxbox - http://fluxbox.org/ Mate - https://mate-desktop.org/ GTK - https://www.gtk.org/ Vanilla OS - https://vanillaos.org/ Fedora SilverBlue - https://fedoraproject.org/atomic-desktops/silverblue/ Ubuntu Core - https://ubuntu.com/core Virtual Box - https://www.virtualbox.org/ Temple OS - https://templeos.org/ Dos Box - https://www.dosbox.com/ Thunderbird - https://www.thunderbird.net/en-US/ Gecko (browser engine) - https://en.wikipedia.org/wiki/Gecko_(software) Graphene OS - https://grapheneos.org/ UBports - https://ubports.com/en/ Nokia "brick" phone - https://en.wikipedia.org/wiki/Nokia_3310 PineTab 2 - https://wiki.pine64.org/wiki/PineTab2 Pine Note - https://pine64.org/devices/pinenote/ Pulse Audio - https://www.freedesktop.org/wiki/Software/PulseAudio/ In Memory Of 5150 - https://linuxlugcast.com/index.php/category/5150/ HAM Radio - http://www.arrl.org/what-is-ham-radio ICQ Chat - https://icq.com/desktop/en?#windows
Bill's continues his Nix adventure, Larry's take on the Ubuntu MATE project, maybe we'll have a Zorin 17 Pro giveaway. In this episode we discuss the real facts about Linux and clear up some Linux 'fake news'. Episode Time Stamps 00:00 Going Linux #452 · Linux Talk , Tips, Tricks and Facts 01:48 Bill's Nix adventure 03:54 Larry's take on the Ubuntu MATE project 06:29 Zorin 17 Pro giveaway? 08:12 The real facts about Linux 08:38 Clearing up Linux 'fake news' 19:11 There are no ready to use distros if you are just getting started with Linux 19:49 Ubuntu and Ubuntu derivatives 20:53 Manjaro 24:24 MX Linux 24:55 Zorin 25:11 Elementary OS 28:05 Pop!OS 29:06 Fedora 30:51 OpenSUSE 32:11 Debian 35:26 Package management: X is better than Y 43:20 The command line is scary, for power users, and you have to use it to use Linux 50:06 Distrowatch is the ultimate source to discover which Linux distro is best 55:03 App suggestion: blanket background noise generator 57:33 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 58:39 End
Bill's continues his Nix adventure, Larry's take on the Ubuntu MATE project, maybe we'll have a Zorin 17 Pro giveaway. In this episode we discuss the real facts about Linux and clear up some Linux 'fake news'. Episode Time Stamps 00:00 Going Linux #452 · Linux Talk , Tips, Tricks and Facts 01:48 Bill's Nix adventure 03:54 Larry's take on the Ubuntu MATE project 06:29 Zorin 17 Pro giveaway? 08:12 The real facts about Linux 08:38 Clearing up Linux 'fake news' 19:11 There are no ready to use distros if you are just getting started with Linux 19:49 Ubuntu and Ubuntu derivatives 20:53 Manjaro 24:24 MX Linux 24:55 Zorin 25:11 Elementary OS 28:05 Pop!OS 29:06 Fedora 30:51 OpenSUSE 32:11 Debian 35:26 Package management: X is better than Y 43:20 The command line is scary, for power users, and you have to use it to use Linux 50:06 Distrowatch is the ultimate source to discover which Linux distro is best 55:03 App suggestion: blanket background noise generator 57:33 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 58:39 End
Coming up in this episode * You are so far aWAY from me * We are watching out for the browsers * A little reverb focus * Community and GenTOO Timestamps 0:00 Cold Open 1:40 The Wayland Soapbox 20:33 Browser Watch 46:27 Reverb Focus 1:12:02 Community Focus 1:14:46 Gentoo Focus 1:29:30 Next Time: CDE History! 1:31:50 Stinger Watch the Video! (https://youtu.be/ZIL1ssfGx9k) https://youtu.be/ZIL1ssfGx9k Social Soapbox - Wayland Nate Graham's blog post - So let's talk about this Wayland thing (https://pointieststick.com/2023/09/17/so-lets-talk-about-this-wayland-thing/) The Wayland Protocol (https://wayland.freedesktop.org/docs/html/) Wayland from the Arch Wiki (https://wiki.archlinux.org/title/wayland) Wayland from the Gentoo Wiki (https://wiki.gentoo.org/wiki/Wayland) Announcements This program was made possible by: *
Neste episódio utilizamos as informações de fontes como o Distrowatch, Google Trends e do Semrush para analisar quais são as Top Distros Linux melhor posicionadas nas buscas. Essa reflexão com base em dados é importante porque muitas vezes, nos deixamos levar pela influência do círculo social onde estamos e ficamos presos dentro de uma bolha que limita nosso aprendizado. Em particular a distro Linux que vem em terceiro lugar no Google Trends chamou nossa atenção, por se tratar de uma distro comunitária e não um sistema capitaneado por uma empresa, reforçando o quanto uma comunidade forte pode ajudar um projeto a alcançar possibilidades que talvez nunca tenham sido imaginadas por seus desenvolvedores. Importante citar que a popularidade de uma distro não está somente relacionada com o conjunto de ferramentas que ela entrega e por outro lado, uma distro não aparecer como top em todas as busca não significa que ela seja tecnicamente inferior a nenhuma outra. Muitas vezes, observamos que um trabalho de divulgação bem feito e uma proximidade com a comunidade podem ajudar a ampliar bastante o alcance de projetos bastante nichados, como algumas flavours do Ubuntu por exemplo. Deixe seu comentário no post do episódio para ser lido no próximo programa: https://diolinux.com.br/podcast/top-distros-linux-segundo-os-dados.html - Este episódio do DioCast conta com o apoio do Sanebox, uma solução para trazer a sanidade de volta para a sua caixa de entrada de e-mails. Controle notificações, organize conteúdo usando etiquetas, filtre conteúdo indesejado e conte com o apoio de uma inteligência artificial para manter seu e-mail livre de conteúdos indesejados. Assine o Sanebox com preço especial: https://sanebox.com/diolinux - Links importantes Sistemas operacionais Linux no Google Trends - https://bit.ly/3v4hmRP Ranking do Distrowatch - https://distrowatch.com/dwres.php?resource=popularity Discussão no Reddit sobre distros nos Google Trends: https://bit.ly/3RKhShs * Os dados do Semrush estarão no post do blog.
RADIO%27 presenta un nuevo episodio de su programa radial "Eskuela GNU/Linux", producido por Eduardo Fórneas y Danmery. En este segundo episodio hablaremos sobre estadísticas e información reflejada en Distrowatch (distrowatch.com), además Eduardo nos relata la experiencia de implementar una serie de sistemas operativos libres en el hackerspace "Se aceptan ideas". Como siempre los invitamos a participar proponiendo otras ideas, diferentes puntos de vista, la idea es que al debatir podamos "acelerar" compartir nuestros conocimientos e intercambiar información veraz y honesta. Esperamos que disfruten mucho este segundo episodio y que fundamentalmente se diviertan... RADIO%27 "Solamente compartir el conocimiento nos hará libres" Canal de discusión: t.me/hackmadrid
0:00 Cold Open 1:47 Wireguard on Pi's? 16:06 The History of NixOS 1:03:39 Our Thoughts on NixOS 1:32:00 Housekeeping 1:36:55 App Focus: tldr 1:40:35 Next Time: Topics 1:42:55 Stinger Coming up in this episode 1. We Pi-ify the Wireguard 2. The history of NixOS 3. Will we nix the Nix? 4. and TL;DR, tldr Join: Discord (https://linuxuserspace.show/discord). Reddit (https://reddit.com/r/LinuxUserSpace/). Telegram (https://linuxuserspace.show/telegram). Matrix (https://linuxuserspace.show/matrix). Twitter (https://twitter.com/LinuxUserSpace). Sub: Youtube (https://linuxuserspace.show/youtube). Twitch (https://www.twitch.tv/linuxuserspace). Fund: Patreon (https://patreon.com/linuxuserspace). Banter Wireguard (wireguard.io) on a Pi 2B+? NixOS (https://nixos.org) Original developer: Eelco Dolstra (Nix), Armijn Hemel (NixOS) Site: nixos.org Base System: Independent Desktop Environment: Gnome or Plasma File Manager: Files or Dolphin Package Manager: nix Kernel: 5.15.11 Display Manager: gdm or sddm Display Protocol: X11, Wayland History Wikipedia page for NixOS (https://en.wikipedia.org/wiki/NixOS) About NixOS from the NixOS Wiki (https://nixos.wiki/wiki/NixOS) History of the NixOS Wiki (https://nixos.wiki/wiki/NixOS_Wiki:History) Started as a research project in 2003 (https://web.archive.org/web/20190421081837/https://nixos.org/~eelco/pubs/iscsd-scm11-final.pdf) Thesis (https://web.archive.org/web/20190609111633/https://nixos.org/~eelco/pubs/phd-thesis.pdf) Dec 2008 Linux.com writes (https://web.archive.org/web/20090228052832/https://www.linux.com/feature/155922) Jun 2009 LWN.net writes (https://lwn.net/Articles/337677/) Sep 2010 XFCE is added (https://nixos.org/images/screenshots/nixos-xfce.png) Nov 2011 NixOS moves to Github (https://github.com/NixOS/) 2012 Nix 1.0 released (https://github.com/NixOS/nix/releases/tag/1.0) Feb 2013 NixOS moves from Upstart to systemd (https://releases.nixos.org/nix-dev/2013-January/010482.html) Jun 2013 NixOps is released (https://releases.nixos.org/nix-dev/2013-June/011363.html) Oct 2013 NixOS 13.10, Aardvark released! (https://releases.nixos.org/nix-dev/2013-October/011941.html) The French website (https://linuxfr.org/news/nix-1-7-nixpkgs-et-nixos-14-04-guix-0-6) LinuxFR covers NixOS 14.04. Another 2014 Review by Ordinatechnic (https://web.archive.org/web/20151006152551/http://ordinatechnic.com/distro-reviews/nixos-review/nixos-14-04-review) 2015 review from LinuxFR (https://linuxfr.org/news/nixos-14-12-la-distribution-linux-sans-effet-de-bord) A talk by Rok Garbas titled "Make Nix Friendlier for Beginners" (https://media.ccc.de/v/nixcon2015-3-MakeNixfriendlierforBeginners#t=1365) Distrowatch 15.09 review (https://distrowatch.com/weekly.php?issue=20151123#nixos) Aug 2016 Presentation from one of the team (https://media.ccc.de/v/froscon2016-1830-nixos) 2017 See the NixOS "weekly" newsletter for the first time (https://weekly.nixos.org/2017/01-we-need-to-start-somewhere.html) Distrowatch 17.03 review (https://distrowatch.com/weekly.php?issue=20170515#nixos) Nix 2.0, Released (https://nixos.org/manual/nix/stable/release-notes/rl-2.0.html) 2020 Review (https://catgirl.ai/log/nixos-experience/) NixOS 21.11, Porcupine Released (https://nixos.org/manual/nixos/stable/release-notes.html#sec-release-21.11) Housekeeping Distrohoppers Digest (https://distrohoppersdigest.blogspot.com) Email us - contact@linuxuserspace.show Linux User Space Discord Server (https://linuxuserspace.show/discord) Our Matrix room (https://linuxuserspace.show/matrix) Support us at Patreon (https://patreon.com/linuxuserspace) Join us on Telegram (https://linuxuserspace.show/telegram) Follow us on Twitter (https://twitter.com/LinuxUserSpace) Watch us on YouTube (https://linuxuserspace.show/youtube) Our latest social platform reddit (https://linuxuserspace.show/reddit) Check out our website https://linuxuserspace.show App Focus tldr This episode's app: * tldr (https://tldr.sh/) Next Time With us trying out NixOS for this past month, that means our next show will be topic based. We have a few topics planned for you and all of them will affect you in the Linux User Space. Our next distro to check out is MX Linux (https://mxlinux.org/) Join us in two weeks when we return to the Linux User Space Stay tuned on Twitter, Telegram, Matrix, Discord, Reddit whatever. Join the conversation. Talk to us, and give us more ideas. We would like to acknowledge our top patrons. Thank you for your support! Contributor Nicholas CubicleNate LiNuXsys666 Jill and Steve WalrusZ sleepyeyesvince Paul Curtis Eduardo Co-Producer Donnie Johnny Producer Bruno John Josh
0:00 Cold Open 2:09 Banter: Tater Top 11:35 History: Zorin OS 50:24 Distro Talk: Zorin OS 1:18:23 Housekeeping 1:25:01 App Focus: Syncthing 1:33:02 Next Time 1:37:10 Stinger Coming up in this episode 1. We fry the tater top 2. The Legend of Zorin 3. And how we fit in 4. We sync some stuff 5. And finally, pick an empty distro Banter - Tatertop First gen chromebooks (https://google.fandom.com/wiki/Cr-48) End of support :-( (https://chromeunboxed.com/iconic-google-cr-48-chromebooks-end-of-life-may-have-arrived/) Flash the BIOS (https://www.insyde.com/products/developertools) more BIOS info (https://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/h2c-firmware) More hacks (https://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/cr-48-chrome-notebook-developer-information) Intel Atom N455 (https://ark.intel.com/content/www/us/en/ark/products/49491/intel-atom-processor-n455-512k-cache-1-66-ghz.html) Zorin OS Zorin OS (https://zorin.com/os/) Wikipedia page for Zorin (https://en.wikipedia.org/wiki/Zorin_OS) Screenshot from Zorin 2 (https://img.vivaolinux.com.br/imagens/artigos/comunidade/zorin.png) Dedoimedo blog post about Zorin 3 (https://www.dedoimedo.com/computers/zorin.html) Distrowatch review for Zorin 4 (https://distrowatch.com/weekly.php?issue=20110117#feature) Zorin OS 5 article talks about Look Changer (https://www.tech-faq.com/zorin-os-promising-but-still-typically-linux.html) Zorin OS 5 Pro ships with Background Plus! (https://youtu.be/Coiae3Erhjk) Zorin OS 6 can be a bridge between Windows and Linux (https://distrowatch.com/weekly.php?issue=20120709#feature) The City of Vicenza, Italy went with Zorin OS (https://blog.zorin.com/2016/04/29/the-city-of-vicenza-is-choosing-zorin-os/) Interview with Artyom by InfinitelyGalactic (https://www.youtube.com/watch?v=wQwomIhA9Hs) Windows App Support (https://zorin.com/help/install-apps/#windows-apps) Zorin OS 16 Releasse announcement (https://blog.zorin.com/2021/08/17/2021-08-17-zorin-os-16-is-released/) Zorin OS Forum (https://forum.zorin.com/) Zorin OS Grid (coming soon) (https://zorin.com/grid/) Site: zorin.com Base System: Ubuntu Desktop Environment: Core: Gnome Lite: XFCE File Manager: Core: Files Lite: Thunar Package Manager: dpkg - apt Kernel: HWE Ubuntu 5.11.0-40 Display Manager: *Core: GDM Lite: lightdm* Display Protocol: X11 Project Leaders: Artyom and Kyril Zorin Housekeeping KeepItTechie (https://keepittechie.com/) KeepItTechie YouTube (https://www.youtube.com/c/KeepItTechie) KeepItTechie Odysee (https://odysee.com/@KeepItTechie:a) Email us - contact@linuxuserspace.show Linux User Space Discord Server (https://linuxuserspace.show/discord) Our Matrix room (https://linuxuserspace.show/matrix) Support us at Patreon (https://patreon.com/linuxuserspace) Join us on Telegram (https://linuxuserspace.show/telegram) Follow us on Twitter (https://twitter.com/LinuxUserSpace) Watch us on YouTube (https://linuxuserspace.show/youtube) Or Watch us on Odysee (https://linuxuserspace.show/odysee) Our latest social platform reddit (https://linuxuserspace.show/reddit) Check out our website https://linuxuserspace.show App Focus SyncThing This episode's app: * SyncThing (https://syncthing.net/) Next Time With us trying out Zorin OS for this past month, that means our next show will be topic based. We have a few topics planned for you and all of them will affect you in the Linux User Space. Our next distro to check out is Void Linux (https://voidlinux.org/) Join us in two weeks when we return to the Linux User Space Stay tuned on Twitter, Telegram, Matrix, Discord, Reddit whatever. Join the conversation. Talk to us, and give us more ideas. We would like to acknowledge our top patrons. Thank you for your support! Contributor Nicholas CubicleNate LiNuXsys666 Jill and Steve WalrusZ sleepyeyesvince Paul Co-Producer Donnie Johnny Producer Bruno John Josh
0:00:00 The beginning 0:00:36 This Episode 0:01:11 Banter: Packaging 0:07:35 Banter: Keyboards 0:13:29 History of Arch 0:51:20 Opinions on Arch 1:14:13 Housekeeping 1:18:07 App Focus: Krita 1:24:12 Next Time 1:24:56 Distro Reveal 1:26:32 Thanks 1:27:14 Stinger Coming up in this episode 1. Dan delivers 2. The strongest form of architecture 3. We answer: Which way to my wiki?! 4. And logos get vectored Banter Ubuntu Feature Freeze (https://wiki.ubuntu.com/FeatureFreeze) Arch Linux Arch Linux (https://wiki.archlinux.org) Basic principles (https://wiki.archlinux.org/title/Arch_Linux) Arch Linux Wikipedia page (https://en.wikipedia.org/wiki/Arch_Linux) Initial release was on 11 March 2002 (https://archlinux.org/retro/2002/) Judd Vinet (https://zeroflux.org) Pacman 1.0 was released in 2002 as well (https://archlinux.org/pacman/#_history) Ladislav Bodnar interview on Distrowatch of Judd Vinet (https://distrowatch.com/dwres.php?resource=interview-arch) The Arch Wiki is born (https://archlinux.org/news/arch-linux-wiki/) Media Wiki (https://www.mediawiki.org/wiki/MediaWiki) Planet Arch is launched (https://archlinux.org/news/planet-arch-linux/) Arch releases the first joke (https://archlinux.org/news/cetw-problems/) Another joke in 2006 (https://archlinux.org/news/current-changes/) April Fools 2007, Arch announces a name change to Ark Linux (https://archlinux.org/news/were-changing-our-name/) Arch moves to YYYYMM versioning. (https://archlinux.org/news/new-release-schedule/) Judd Vinet hands over the reins (https://bbs.archlinux.org/viewtopic.php?id=38024) Arch logo competition was announced (https://archlinux.org/news/arch-linux-logo-competition/) The Arch Magazine is launched! (https://bbs.archlinux.org/viewtopic.php?pid=687363) It was converted to the ezine. (https://bbs.archlinux.org/viewtopic.php?id=105236) New process for future leaders (https://wiki.archlinux.org/title/DeveloperWiki:Project_Leader) Latest poll for the current leader (https://archlinux.org/news/the-future-of-the-arch-linux-project-leader/) Video from ArchConf October 2020 (https://linuxreviews.org/Arch_Linux:_Past,_Present_and_Future) April 2021 introduction of the new guided installer (https://github.com/archlinux/archinstall) Arch moves from Freenode to Libera (https://archlinux.org/news/move-of-official-irc-channels-to-liberachat/) Steam Deck will run Arch (https://www.steamdeck.com/en/) Name - Arch Linux Base System - Arch Desktop Environment - Any File Manager - All Package Manager - pacman Kernel - Rolling 5.13.12 as of today Display Manager - All Wayland or X11 - Project Leader: Levante Polyak Housekeeping The Arch Wiki (https://wiki.archlinux.org/title/ArchWiki:About) Discord Server (https://discord.gg/qXKxHcV) Matrix Room (https://matrix.to/#/#linuxuserspace:matrix.org?via=matrix.org) Support us at Patreon (https://patreon.com/linuxuserspace) Join us on Telegram (https://linuxuserspace.show/telegram) Follow us on Twitter (https://twitter.com/LinuxUserSpace) App Focus Krita This episode's app: * Krita (https://krita.org/en/) Next Time With us trying out Arch Linux for this past month, that means our next show will be topic based. We have a few topics planned for you and all of them will affect you in the Linux User Space. Our next distro to check out is Elementary OS 6 (https://elementary.io) Join us in two weeks when we return to the Linux User Space Stay tuned on Twitter, Telegram, Matrix, Discord whatever. Join the conversation. Talk to us, and give us more ideas. We would like to acknowledge our top patrons. Thank you for your support! Contributor Nicholas Co-Producer Donnie Producer Bruno John
Matt and Tyler talk about Tyler's switch back to qtile, Matt's work with making his own stream deck, and whether or not Distrowatch is a terrible place. The main topic this week is about Linux and anti-virus software. Twitter: @thelinuxcast @mtwb @OfficialZaney on LBRY , https://bit.ly/3dbqbjX on YouTube Subscribe at http://thelinuxcast.org Contact us thelinuxcast@gmail.com Patreon https://patreon.com/thelinuxcast Liberapay - https://liberapay.com/thelinuxcast/ https://facebook.com/thelinuxcast Subscribe on YouTube https://youtube.com/thelinuxcast ===== Thanks to Our Patrons! ==== Devon C. -- Tier 4 Patron Marcus B. - Tier 3 Patron Donnie H. - Tier 3 Patron Maeglin - Tier 3 Patron Sven C. - Tier 3 Patron. Marek M. - Tier 1 Patron Camp514 - Tier 1 Patron Mitchel V - Tier 1 Patron [show notes] **What have we been up to Linux related this Week?** Tyler – Back to using Qtile as my daily driver Matt – Messing with key mapper and my own little stream deck hack. **Links (One each)** Matt - https://news.itsfoss.com/nitrux-linux-distrowatch-apology/ Tyler - https://www.linux-magazine.com/Online/News/Armbian-21.05-Now-Available --- **Main Topic -** Does Linux Need AntiVirus? --- **Apps of the Week** Matt - enve - https://maurycyliebner.github.io/index Tyler - VSCodium - https://vscodium.com/ Time Stamps 0:00 Intro 0:13 Our Week in Linux 7:30 Contact Info 8:47 News Links 22:43 Linux & AntiVirus Softwarew 41:11 Apps of the Week 48:23 Conclusion #linux #podcast #thelinuxcast
We’re taking a look at an underdog distro. We may have found a diamond in the rough with a few tricks up its filesystem. Plus our review of the ODROID-Go Super an Ubuntu-powered handheld, and our tools for laptop battery health.
Whether there’s any point trying out random distros, and your feedback about AMD hardware, slow phones, messaging services, cryptocurrencies, and KDE. First Impressions Is there anything to be gained from trying new distros? We’ll be pressing the random button on DistroWatch and briefly trying out the distro it picks for us. The first distro... Read More
Whether there’s any point trying out random distros, and your feedback about AMD hardware, slow phones, messaging services, cryptocurrencies, and KDE. First Impressions Is there anything to be gained from trying new distros? We’ll be pressing the random button on DistroWatch and briefly trying out the distro it picks for us. The first distro... Read More
Richards Radio Adventures Episode 35 Affordable Linux Welcome to Richard's radio Adventure'sPimpin Resonant FrequencyBegging for helpHelpSocial media sitesShownotesEpisode researchcontributed contentand morePlease donate to the show to help cover expensesWe do not accept advertising at this timeButt hurt over feedbacknote to my listeners parked on the first pagePaypal is fixedTalking about the worlds best operating systemEnter Russ K5TUXThe windows operating system is a VIRUS!Linux historyUnixBSDGNU ProjectRichard StallmanGNU Public License GPLDinner with the KernelEnter Linus TorvaldsLinuxGUI interface 1992Can be loaded from a live CD / DVDYou can use the command line but you don't have toMultiple desktop environmentsCompatible with most hardwareBrings old PC's to lifeEasier to add software than WindowsSoftware for most Amateur Radio activitiesThis show has been recorded on Linux for yearsStill using the same software to record this episode on WindowsAlready Beta testedNot release it the beta test it like Windows Great Distributions Linux MintUbuntuFedoraCentosSuse Go to Distrowatch for all the information on Distributions Don't forget to listen to their podcast Distrowatch Weekly to keep up with the newest and greatest in the world of free software Last but not least don't forget to drop by and say hello to Russ K5TUX at the Linux in the Ham Shack Podcast Were out of here Come see us at YouTube https://www.youtube.com/c/RichardBaileyKB5JBV Read More About Resonant Frequency: The Amateur Radio Podcast At www.rfpodcast.info Glossary - See Glossary for terms used on the show. amzn_assoc_placement = "adunit0"; amzn_assoc_tracking_id = "resonantfre0c-20"; amzn_assoc_ad_mode = "search"; amzn_assoc_ad_type = "smart"; amzn_assoc_marketplace = "amazon"; amzn_assoc_region = "US"; amzn_assoc_default_search_phrase = "yaesu fusion radio"; amzn_assoc_default_category = "All"; amzn_assoc_linkid = "6bf6f2cec828e054a7a9576e5c8be77a"; amzn_assoc_design = "in_content"; amzn_assoc_title = "Click to see more items";
On this episode of The Linux Cast, Martin and Matt discuss the effects so-called Linux Elitism has on new Linux Users. Introduction What have we been up to Linux related this Week? Martin– moving from Last pass to Bit warden Matt– Getting mpd and ncmpcpp working. Next up neomutt. Contact Info Twitter: @thelinuxcast @mtwb @martintwit2you Subscribe at http://thelinuxcast.org Contact us thelinuxcast@gmail.com http://facebook.com/thelinuxcast Subscribe on YouTube https://www.youtube.com/channel/UCylGUf9BvQooEFjgdNudoQg Links (One each) Matt - https://www.omgubuntu.co.uk/2020/10/microsoft-edge-linux-first-look Martin – Septor I have noticed that Septor (KDE & Tor anonymity) has risen to the top of the DistroWatch list for the last 30 days(not that counts for much), going to download it give it a quick check nothing full depth or tedious just a heads up for the listeners that may be interested” Main Topic - Elitism - Is there a danger of the Penguin Master Race Apps of the Week Matt - https://github.com/KorySchneider/wikit Martin – https://www.youtube.com/watch?v=gbzqCAjm--g https://github.com/GitSquared/edex-ui/releases
Libreoffice 7.0 gets super Vulkan powers! DistroWatch makes it easy to compare packages, Have I Been Pwned goes open-source, and Microsoft wants to party like it's 2001.
This week on BDLL, we will give our final thoughts on our bi-weekly distro challenge of Arco Linux (https://arcolinux.com/). In the second hour we listener email and forum posts. We have a heated discussion about DistroWatch and we end up talking about LBRY.tv Want to join us next time? You can download zoom (www.zoom.us) and install it and join the meeting via BDLL Link (https://bigdaddylinux.com/zoom) This was a multi-stream using ReStream (https://restream.io/) so you can watch it on Youtube (https://youtube.com/channel/UCtZRKfyvx7GUEi-Lr7f4Nxg?) or on Twitch (https://twitch.tv/bigdaddylinux)! Check out the BDL website (https://bigdaddylinux.com/) for more info. Join in on the discussions in the Discourse Forums (https://discourse.bigdaddylinux.com/) Join the discussion during the week in our telegram group (https://bigdaddylinux.com/telegram) Join us on Discord (https://bigdaddylinux.com/discord) Links for people who join BDLL can be found on the Community Page (https://bigdaddylinux.com/community)
We answer questions and comment on internal drive problems, Microsoft making Linux more popular, the Distrowatch podcast, gPodder and Orca, the Mint forums, print/fax/scan compatibility, games, Manjaro, and Chromebooks running Linux. Episode 387 Time Stamps 00:00 Going Linux #387 · Listener Feedback 00:56 Do we need the voicemail line? 02:38 Linux Spotlight interviews Larry 03:56 Paul: Second internal drive problem 20:22 Nancy: Microsoft makes Linux more popular 25:27 Michael: Unable to subscribe to the Distrowatch podcast 26:26 Daniel: gPodder and Orca 27:36 Ken: Great experience with the Mint forums 31:13 Daniel: A question about Larry's books on Ubuntu MATE 36:42 Carlos: Print/fax/scan compatibility 42:32 Albert: Running games 48:59 Richard: Contacting Manjaro 52:28 George: 385 and 386 60:39 Anand: Linux on a Macbook Pro 62:08 Alex: Switching from macOS 62:52 Paul: Chromebooks running Linux 68:16 Troy: Mark Greaves 69:30 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 70:50 End
We answer questions and comment on internal drive problems, Microsoft making Linux more popular, the Distrowatch podcast, gPodder and Orca, the Mint forums, print/fax/scan compatibility, games, Manjaro, and Chromebooks running Linux. Episode 387 Time Stamps 00:00 Going Linux #387 · Listener Feedback 00:56 Do we need the voicemail line? 02:38 Linux Spotlight interviews Larry 03:56 Paul: Second internal drive problem 20:22 Nancy: Microsoft makes Linux more popular 25:27 Michael: Unable to subscribe to the Distrowatch podcast 26:26 Daniel: gPodder and Orca 27:36 Ken: Great experience with the Mint forums 31:13 Daniel: A question about Larry's books on Ubuntu MATE 36:42 Carlos: Print/fax/scan compatibility 42:32 Albert: Running games 48:59 Richard: Contacting Manjaro 52:28 George: 385 and 386 60:39 Anand: Linux on a Macbook Pro 62:08 Alex: Switching from macOS 62:52 Paul: Chromebooks running Linux 68:16 Troy: Mark Greaves 69:30 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 70:50 End
Distrowatch reviews FuryBSD, LLDB on i386 for NetBSD, wpa_supplicant as lower-class citizen, KDE on FreeBSD updates, Travel Grant for BSDCan open, ZFS dataset for testing iocage within a jail, and more. Headlines Distrowatch Fury BSD Review (https://distrowatch.com/weekly.php?issue=20200127#furybsd) FuryBSD is the most recent addition to the DistroWatch database and provides a live desktop operating system based on FreeBSD. FuryBSD is not entirely different in its goals from NomadBSD, which we discussed recently. I wanted to take this FreeBSD-based project for a test drive and see how it compares to NomadBSD and other desktop-oriented projects in the FreeBSD family. FuryBSD supplies hybrid ISO/USB images which can be used to run a live desktop. There are two desktop editions currently, both for 64-bit (x86_64) machines: Xfce and KDE Plasma. The Xfce edition is 1.4GB in size and is the flavour I downloaded. The KDE Plasma edition is about 3.0GB in size. My fresh install of FuryBSD booted to a graphical login screen. From there I could sign into my account, which brings up the Xfce desktop. The installed version of Xfce is the same as the live version, with a few minor changes. Most of the desktop icons have been removed with just the file manager launchers remaining. The Getting Started and System Information icons have been removed. Otherwise the experience is virtually identical to the live media. FuryBSD uses a theme that is mostly grey and white with creamy yellow folder icons. The application menu launchers tend to have neutral icons, neither particularly bright and detailed or minimal. LLDB now works on i386 (http://blog.netbsd.org/tnf/entry/lldb_now_works_on_i386) Upstream describes LLDB as a next generation, high-performance debugger. It is built on top of LLVM/Clang toolchain, and features great integration with it. At the moment, it primarily supports debugging C, C++ and ObjC code, and there is interest in extending it to more languages. In February 2019, I have started working on LLDB, as contracted by the NetBSD Foundation. So far I've been working on reenabling continuous integration, squashing bugs, improving NetBSD core file support, extending NetBSD's ptrace interface to cover more register types and fix compat32 issues, fixing watchpoint and threading support. The original NetBSD port of LLDB was focused on amd64 only. In January, I have extended it to support i386 executables. This includes both 32-bit builds of LLDB (running natively on i386 kernel or via compat32) and debugging 32-bit programs from 64-bit LLDB. News Roundup wpa_supplicant is definitely a lower-class citizen, sorry (https://marc.info/?l=openbsd-misc&m=158068418807352&w=2) wpa_supplicant is definitely a lower-class citizen, sorry. I increasingly wonder why this stuff matters; transit costs are so much lower than the period when eduroam was setup, and their reliance on 802.11x is super weird in a world where, for the most part + entire cities have open wifi in their downtown core + edu vs edu+transit split horizon problems have to be solved anyways + many universities have parallel open wifi + rate limiting / fare-share approaches for the open-net, on unmetered + flat-rate solves the problem + LTE hotspot off a phone isn't a rip off anymore + other open networks exist essentially no one else feels compelled to do use 802.11x for a so called "semi-open access network", so I think they've lost the plot on friction vs benefit. (we've held hackathons at EDU campus that are locked down like that, and in every case we've said no way, gotten a wire with open net, and built our own wifi. we will not subject our developers to that extra complexity). KDE FreeBSD Updates Feb 2020 (https://euroquis.nl/freebsd/2020/02/08/freebsd.html) Some bits and bobs from the KDE FreeBSD team in february 2020. We met at the FreeBSD devsummit before FOSDEM, along with other FreeBSD people. Plans were made, schemes were forged, and Groff the Goat was introduced to some new people. The big ticket things: Frameworks are at 5.66 Plasma is at 5.17.5 (the beta 5.18 hasn’t been tried) KDE release service has landed 19.12.2 (same day it was released) Developer-centric: KDevelop is at 5.5.0 KUserfeedback landed its 1.0.0 release CMake is 3.16.3 Applications: Musescore is at 3.4.2 Elisa now part of the KDE release service updates Fuure work: KIO-Fuse probably needs extra real-world testing on FreeBSD. I don’t have that kind of mounts (just NFS in /etc/fstab) so I’m not the target audience. KTextEditor is missing .editorconfig support. That can come in with the next frameworks update, when consumers update anyway. Chasing it in an intermediate release is a bit problematic because it does require some rebuilds of consumers. Travel Grant Application for BSDCan is now open (https://lists.freebsd.org/pipermail/freebsd-announce/2020-February/001929.html) Hi everyone, The Travel Grant Application for BSDCan 2020 is now open. The Foundation can help you attend BSDCan through our travel grant program. Travel grants are available to FreeBSD developers and advocates who need assistance with travel expenses for attending conferences related to FreeBSD development. BSDCan 2020 applications are due April 9, 2020. Find out more and apply at: https://www.freebsdfoundation.org/what-we-do/grants/travel-grants/ Did you know the Foundation also provides grants for technical events not specifically focused on BSD? If you feel that your attendance at one of these events will benefit the FreeBSD Project and Community and you need assistance getting there, please fill out the general travel grant application. Your application must be received 7 weeks prior to the event. The general application can be found here: https://goo.gl/forms/QzsOMR8Jra0vqFYH2 Creating a ZFS dataset for testing iocage within a jail (https://dan.langille.org/2020/02/01/creating-a-zfs-dataset-for-testing-iocage-within-a-jail/) Be warned, this failed. I’m stalled and I have not completed this. I’m going to do jails within a jail. I already do that with poudriere in a jail but here I want to test an older version of iocage before upgrading my current jail hosts to a newer version. In this post: FreeBSD 12.1 py36-iocage-1.2_3 py36-iocage-1.2_4 This post includes my errors and mistakes. Perhaps you should proceed carefully and read it all first. Beastie Bits Reminder: the FreeBSD Journal is free! Check out these great articles (https://www.freebsdfoundation.org/journal/browser-based-edition/) Serenity GUI desktop running on an OpenBSD kernel (https://twitter.com/jcs/status/1224205573656322048) The Open Source Parts of MacOS (https://github.com/apple-open-source/macos) FOSDEM videos available (https://www.fosdem.org/2020/schedule/track/bsd/) Feedback/Questions Michael - Install with ZFS (http://dpaste.com/3WRC9CQ#wrap) Mohammad - Server Freeze (http://dpaste.com/3BYZKMS#wrap) Todd - ZFS Questions (http://dpaste.com/2J50HSJ#wrap) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Your browser does not support the HTML5 video tag.
Distrowatch reviews FuryBSD, LLDB on i386 for NetBSD, wpa_supplicant as lower-class citizen, KDE on FreeBSD updates, Travel Grant for BSDCan open, ZFS dataset for testing iocage within a jail, and more.
Distrowatch reviews FuryBSD, LLDB on i386 for NetBSD, wpa_supplicant as lower-class citizen, KDE on FreeBSD updates, Travel Grant for BSDCan open, ZFS dataset for testing iocage within a jail, and more.
Upgrading FreeBSD from 11.3 to 12.1, Distrowatch switching to FreeBSD, Torvalds says don’t run ZFS, iked(8) removed automatic IPv6 blocking, working towards LLDB on i386, and memory-hard Argon2 hashing scheme in NetBSD. Headlines Upgrading FreeBSD from 11.3 to 12.1 (https://blog.bimajority.org/2020/01/13/upgrading-freebsd-from-11-3-to-12-1/) Now here’s something more like what I was originally expecting the content on this blog to look like. I’m in the process of moving all of our FreeBSD servers (about 30 in total) from 11.3 to 12.1. We have our own local build of the OS, and until “packaged base” gets to a state where it’s reliably usable, we’re stuck doing upgrades the old-fashioned way. I created a set of notes for myself while cranking through these upgrades and I wanted to share them since they are not really work-specific and this process isn’t very well documented for people who haven’t been doing this sort of upgrade process for 25 years. Our source and object trees are read-only exported from the build server over NFS, which causes things to be slow. /etc/make.conf and /etc/src.conf are symbolic links on all of our servers to the master copies in /usr/src so that make installworld can find the configuration parameters the system was built with. Switching Distrowatch over to BSD (https://www.reddit.com/r/freebsd/comments/eodhit/switching_distrowatch_over_to_freebsd_ama/) This may be a little off-topic for this board (forgive me if it is, please). However, I wanted to say that I'm one of the people who works on DistroWatch (distrowatch.com) and this past week we had to deal with a server facing hardware failure. We had a discussion about whether to continue running Debian or switch to something else. The primary "something else" option turned out to be FreeBSD and it is what we eventually went with. It took a while to convert everything over from working with Debian GNU/Linux to FreeBSD 12 (some script incompatibilities, different paths, some changes to web server configuration, networking IPv6 troubles). But in the end we ended up with a good, FreeBSD-based experience. Since the transition was successful, though certainly not seamless, I thought people might want to do a Q&A on the migration process. Especially for those thinking of making the same switch. News Roundup iked(8) automatic IPv6 blocking removed (https://www.openbsd.org/faq/current.html#r20200114) iked(8) no longer automatically blocks unencrypted outbound IPv6 packets. This feature was intended to avoid accidental leakage, but in practice was found to mostly be a cause of misconfiguration. If you previously used iked(8)'s -6 flag to disable this feature, it is no longer needed and should be removed from /etc/rc.conf.local if used. Linus says dont run ZFS (https://itsfoss.com/linus-torvalds-zfs/) “Don’t use ZFS. It’s that simple. It was always more of a buzzword than anything else, I feel, and the licensing issues just make it a non-starter for me.” This is what Linus Torvalds said in a mailing list to once again express his disliking for ZFS filesystem specially over its licensing. To avoid unnecessary confusion, this is more intended for Linux distributions, kernel developers and maintainers rather than individual Linux users. GSoC 2019 Final Report: Incorporating the memory-hard Argon2 hashing scheme into NetBSD (https://blog.netbsd.org/tnf/entry/gsoc_2019_final_report_incorporating) We successfully incorporated the Argon2 reference implementation into NetBSD/amd64 for our 2019 Google Summer of Coding project. We introduced our project here and provided some hints on how to select parameters here. For our final report, we will provide an overview of what changes were made to complete the project. The Argon2 reference implementation, available here, is available under both the Creative Commons CC0 1.0 and the Apache Public License 2.0. To import the reference implementation into src/external, we chose to use the Apache 2.0 license for this project. Working towards LLDB on i386 NetBSD (https://blog.netbsd.org/tnf/entry/working_towards_lldb_on_i386) Upstream describes LLDB as a next generation, high-performance debugger. It is built on top of LLVM/Clang toolchain, and features great integration with it. At the moment, it primarily supports debugging C, C++ and ObjC code, and there is interest in extending it to more languages. In February 2019, I have started working on LLDB, as contracted by the NetBSD Foundation. So far I've been working on reenabling continuous integration, squashing bugs, improving NetBSD core file support, extending NetBSD's ptrace interface to cover more register types and fix compat32 issues, fixing watchpoint and threading support. Throughout December I've continued working on our build bot maintenance, in particular enabling compiler-rt tests. I've revived and finished my old patch for extended register state (XState) in core dumps. I've started working on bringing proper i386 support to LLDB. Beastie Bits An open source Civilization V (https://github.com/yairm210/UnCiv) BSD Groups in Italy (https://bsdnotizie.blogspot.com/2020/01/gruppi-bsd-in-italia.html) Why is Wednesday, November 17, 1858 the base time for OpenVMS? (https://www.slac.stanford.edu/~rkj/crazytime.txt) Benchmarking shell pipelines and the Unix “tools” philosophy (https://blog.plover.com/Unix/tools.html) LPI and BSD working together (https://youtu.be/QItb5aoj7Oc) Feedback/Questions Pat - March Meeting (http://dpaste.com/2BMGZVV#wrap) Madhukar - Overheating Laptop (http://dpaste.com/17WNVM8#wrap) Warren - R vs S (http://dpaste.com/3AZYFB1#wrap) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Your browser does not support the HTML5 video tag.
Upgrading FreeBSD from 11.3 to 12.1, Distrowatch switching to FreeBSD, Torvalds says don’t run ZFS, iked(8) removed automatic IPv6 blocking, working towards LLDB on i386, and memory-hard Argon2 hashing scheme in NetBSD.
Upgrading FreeBSD from 11.3 to 12.1, Distrowatch switching to FreeBSD, Torvalds says don’t run ZFS, iked(8) removed automatic IPv6 blocking, working towards LLDB on i386, and memory-hard Argon2 hashing scheme in NetBSD.
TIK TEK TOE, episode 003. Today, Marcel and Evan decide to rename the show, so now it's called, "Tic Tek Toe" and not "Trash-Talking FOSS". The guys talk about VR fitness, courtesy of Marcel's Oculus Quest, Distrowatch, Lucky Charms cereal (no, really), and whether or not you have a right to be erased from the Internet. And once you're done, make sure you share this podcast with your friends, family, neighbours, enemies . . . just share and recommend. Links from the show Oculus Quest and Beat Saber Distrowatch Website Distro Chooser Website (16 questions to pick a distribution) Lucky Charms Marshmallows Google wins partial victory in "Right to be Forgotten" case --- Send in a voice message: https://anchor.fm/tic-tek-toe/message
After a 2 week hiatus, we are back! In this episode, we share some of what we have been doing, as well as responding to a review we recently received on Distrowatch.com --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/drauger-os/message Support this podcast: https://anchor.fm/drauger-os/support
Today we define some basic terms used in the Linux and Open Source community. This is the first in a series of 'back to basics' episodes in which we will update the information we've been providing over the past 12 years. We also want to ensure that we continue to provide a reference for Linux users to use as a reference when using Linux for their day-to-day computing needs. Episode 364 Time Stamps 00:00 Going Linux #364 · Back to Basics - Definition of Terms 00:15 Introduction 01:01 Experimenting with MeWe 07:52 The Linux 'Back to Basics' series 09:33 Free: Freedon vs. no charge 13:21 Operating system 18:04 Distribution 19:36 Desktop environment 22:47 Application, Package, and Repository 26:00 Richard Stallman 27:05 Linux Torvalds 27:46 Where to get started 31:38 Distrowatch.com 34:50 Future Back to Basics episodes 36:20 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 37:18 End
Today we define some basic terms used in the Linux and Open Source community. This is the first in a series of 'back to basics' episodes in which we will update the information we've been providing over the past 12 years. We also want to ensure that we continue to provide a reference for Linux users to use as a reference when using Linux for their day-to-day computing needs. Episode 364 Time Stamps 00:00 Going Linux #364 · Back to Basics - Definition of Terms 00:15 Introduction 01:01 Experimenting with MeWe 07:52 The Linux 'Back to Basics' series 09:33 Free: Freedon vs. no charge 13:21 Operating system 18:04 Distribution 19:36 Desktop environment 22:47 Application, Package, and Repository 26:00 Richard Stallman 27:05 Linux Torvalds 27:46 Where to get started 31:38 Distrowatch.com 34:50 Future Back to Basics episodes 36:20 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 37:18 End
Alan, Tyrel, and Hayden overflow a memory buffer into catfish noodling then share some tips and preferences with bash, zsh, and git. http://friday.hirelofty.com/ https://facebook.com/fridaydeploy https://twitter.com/fridaydeploy In this Episode Linux Journal: Using Bash History more Efficiently tig N-gate: Hackernews with extra snark. Distrowatch
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
It’s a special all #AskError episode! A hypothetical Linux world, the future of welfare, tech disruption, and terrible email addresses. Plus Distrowatch rankings, and a crucial seasonal question. 00:00:32 Spoopy month? Y/N_ 00:04:15 Are the Distrowatch rankings worth the pixels they are rendered on? 00:10:10 Is universal basic income a good idea? 00:23:32 How much does your email address matter? (https://www.wsj.com/articles/is-your-email-address-holding-you-back-1535470160) 00:27:02 What will tech disrupt next? 00:35:27 If you had to switch to a different distro, what would it be?
In the Going Linux holiday tradition, Bill and Larry review some of the significant happenings during the past year. Episode 336 Time Stamps 00:00 Going Linux #336 · 2017 Year End Review 00:15 Introduction 02:01 Highlights of 2017 02:57 Ubuntu MATE: Two books and a guide within the distribution. 10:19 Goodbye net neutrality 19:32 The Minion Network begins 22:58 Linux takes over the world! 24:33 Goodbye Linux Journal 28:14 Goodbye AIM 30:01 City of Munich goes back to Windows 35:13 Containers 36:25 Linux malware 39:00 Distrowatch top 10 47:48 Ubuntu leaves Unity for Gnome 51:27 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 52:29 End
In the Going Linux holiday tradition, Bill and Larry review some of the significant happenings during the past year. Episode 336 Time Stamps 00:00 Going Linux #336 · 2017 Year End Review 00:15 Introduction 02:01 Highlights of 2017 02:57 Ubuntu MATE: Two books and a guide within the distribution. 10:19 Goodbye net neutrality 19:32 The Minion Network begins 22:58 Linux takes over the world! 24:33 Goodbye Linux Journal 28:14 Goodbye AIM 30:01 City of Munich goes back to Windows 35:13 Containers 36:25 Linux malware 39:00 Distrowatch top 10 47:48 Ubuntu leaves Unity for Gnome 51:27 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 52:29 End
Welcome to Episode 47 of Destination Linux for 11-27-17 I’m Rocco (and I’m Ryan) and this is Destination Linux Today on the show we have a special guest Dolphin Oracle One of the guys behind MX Linux MX Linux is regularly featured in the top 30 distros on Distrowatch and beloved by many Youtube content […]
Corría Septiembre del año 2013 y Debian superaba por primera vez a Ubuntu en el famoso portal linuxero DistroWatch.com, un sitio que sirve para medir la popularidad de las distribuciones Linux según las visitas de los usuarios.En aquel mes y como homenaje a este hecho se me ocurrió escribir un poema en verso contando la hazaña de Debian, algo inusual dado que Ubuntu llevaba muchos años siendo la primera en el ranking de visitas de este famoso portal.Hace tan solo un par de días que el proyecto Debian ha lanzado como estable su versión 9.0 Stretch, algo que se celebra en el mundo entero.Se ha dado la coincidencia que a fecha de hoy, 20 de Junio del 2017, Debian sigue estando por encima de Ubuntu en el portal DistroWatch, concretamente en segundo lugar quedando Ubuntu el cuarto.Como agradecimiento a Debian por su nueva versión y homenaje por estar de nuevo por encima de Ubuntu he querido recuperar aquel poema juglar que escribí en Septiembre del 2013, pero esta vez recitado por alguien que sabe de verdad ;)Montaje musical y voz: @josescolar (en Twitter)Letra del poema: https://deblinux.wordpress.com/2013/09/17/romancero-linuxero-la-vida-es-una-espiral/
Today on the show, we've got a look at running OpenBSD on a APU, some BSD in your Android, managing your own FreeBSD cloud service with ansible and much more. Keep it turned on your place to B...SD! This episode was brought to you by Headlines OpenBSD on PC Engines APU2 (https://github.com/elad/openbsd-apu2) A detailed walkthrough of building an OpenBSD firewall on a PC Engines APU2 It starts with a breakdown of the parts that were purchases, totally around $200 Then the reader is walked through configuring the serial console, flashing the ROM, and updating the BIOS The next step is actually creating a custom OpenBSD install image, and pre-configuring its serial console. Starting with OpenBSD 6.0, this step is done automatically by the installer Installation: Power off the APU2 Insert the bootable OpenBSD installer USB flash drive to one of the USB slots on the APU2 Power on the APU2, press F10 to get to the boot menu, and choose to boot from USB (usually option number 1) At the boot> prompt, remember the serial console settings (see above) Also at the boot> prompt, press Enter to start the installer Follow the installation instructions The driver used for wireless networking is athn(4). It might not work properly out of the box. Once OpenBSD is installed, run fw_update with no arguments. It will figure out which firmware updates are required and will download and install them. When it finishes, reboot. Where the rubber meets the road… (part one) (https://functionallyparanoid.com/2016/11/29/where-the-rubber-meets-the-road-part-one/) A user describes their adventures installing OpenBSD and Arch Linux on a new Lenovo X1 Carbon (4th gen, skylake) They also detail why they moved away from their beloved Macbook, which while long, does describe a journey away from Apple that we've heard elsewhere. The journey begins with getting a new Windows laptop, shrinking the partition and creating space for a triple-boot install, of Windows / Arch / OpenBSD Brian then details how he setup the partitioning and performed the initial Arch installation, getting it tuned to his specifications. Next up was OpenBSD though, and that went sideways initially due to a new NVMe drive that wasn't fully supported (yet) The article is split into two parts (we will bring you the next installment at a future date), but he leaves us with the plan of attack to build a custom OpenBSD kernel with corrected PCI device identifiers. We wish Brian luck, and look forward to the “rest of the story” soon. *** Howto setup a FreeBSD jail server using iocage and ansible. (https://github.com/JoergFiedler/freebsd-ansible-demo) Setting up a FreeBSD jail server can be a daunting task. However when a guide comes along which shows you how to do that, including not exposing a single (non-jailed) port to the outside world, you know we had a take a closer look. This guide comes to us from GitHub, courtesy of Joerg Fielder. The project goals seem notable: Ansible playbook that creates a FreeBSD server which hosts multiple jails. Travis is used to run/test the playbook. No service on the host is exposed externally. All external connections terminate within a jail. Roles can be reused using Ansible Galaxy. Combine any of those roles to create FreeBSD server, which perfectly suits you. To get started, you'll need a machine with Ansible, Vagrant and VirtualBox, and your credentials to AWS if you want it to automatically create / destroy EC2 instances. There's already an impressive list of Anisible roles created for you to start with: freebsd-build-server - Creates a FreeBSD poudriere build server freebsd-jail-host - FreeBSD Jail host freebsd-jailed - Provides a jail freebsd-jailed-nginx - Provides a jailed nginx server freebsd-jailed-php-fpm - Creates a php-fpm pool and a ZFS dataset which is used as web root by php-fpm freebsd-jailed-sftp - Installs a SFTP server freebsd-jailed-sshd - Provides a jailed sshd server. freebsd-jailed-syslogd - Provides a jailed syslogd freebsd-jailed-btsync - Provides a jailed btsync instance server freebsd-jailed-joomla - Installs Joomla freebsd-jailed-mariadb - Provides a jailed MariaDB server freebsd-jailed-wordpress - Provides a jailed Wordpress server. Since the machines have to be customized before starting, he mentions that cloud-init is used to do the following: activate pf firewall add a pass all keep state rule to pf to keep track of connection states, which in turn allows you to reload the pf service without losing the connection install the following packages: sudo bash python27 allow passwordless sudo for user ec2-user “ From there it is pretty straight-forward, just a couple commands to spin up the VM's either locally on your VirtualBox host, or in the cloud with AWS. Internally the VM's are auto-configured with iocage to create jails, where all your actual services run. A neat project, check it out today if you want a shake-n-bake type cloud + jail solution. Colin Percival's bsdiff helps reduce Android apk bandwidth usage by 6 petabytes per day (http://android-developers.blogspot.ca/2016/12/saving-data-reducing-the-size-of-app-updates-by-65-percent.html) A post on the official Android-Developers blog, talks about how they used bsdiff (and bspatch) to reduce the size of Android application updates by 65% bsdiff was developed by FreeBSD's Colin Percival Earlier this year, we announced that we started using the bsdiff algorithm (by Colin Percival). Using bsdiff, we were able to reduce the size of app updates on average by 47% compared to the full APK size. This post is actually about the second generation of the code. Today, we're excited to share a new approach that goes further — File-by-File patching. App Updates using File-by-File patching are, on average, 65% smaller than the full app, and in some cases more than 90% smaller. Android apps are packaged as APKs, which are ZIP files with special conventions. Most of the content within the ZIP files (and APKs) is compressed using a technology called Deflate. Deflate is really good at compressing data but it has a drawback: it makes identifying changes in the original (uncompressed) content really hard. Even a tiny change to the original content (like changing one word in a book) can make the compressed output of deflate look completely different. Describing the differences between the original content is easy, but describing the differences between the compressed content is so hard that it leads to inefficient patches. So in the second generation of the code, they use bsdiff on each individual file, then package that, rather than diffing the original and new archives bsdiff is used in a great many other places, including shrinking the updates for the Firefox and Chrome browsers You can find out more about bsdiff here: http://www.daemonology.net/bsdiff/ A far more sophisticated algorithm, which typically provides roughly 20% smaller patches, is described in my doctoral thesis (http://www.daemonology.net/papers/thesis.pdf). Considering the gains, it is interesting that no one has implemented Colin's more sophisticated algorithm Colin had an interesting observation (https://twitter.com/cperciva/status/806426180379230208) last night: “I just realized that bandwidth savings due to bsdiff are now roughly equal to what the total internet traffic was when I wrote it in 2003.” *** News Roundup Distrowatch does an in-depth review of NAS4Free (https://distrowatch.com/weekly.php?issue=20161114#nas4free) Jesse Smith over at DistroWatch has done a pretty in-depth review of Nas4Free. The review starts with mentioning that NAS4Free works on 3 platforms, ARM/i386/AMD64 and for the purposes of this review he would be using AMD64 builds. After going through the initial install (doing typical disk management operations, such as GPT/MBR, etc) he was ready to begin using the product. One concern originally observed was that the initial boot seemed rather slow. Investigation revealed this was due to it loading the entire OS image into memory, and the first (long) disk read did take some time, but once loaded was super responsive. The next steps involved doing the initial configuration, which meant creating a new ZFS storage pool. After this process was done, he did find one puzzling UI option called “VM” which indicated it can be linked to VirtualBox in some way, but the Docs didn't reveal its secrets of usage. Additionally covered were some of the various “Access” methods, including traditional UNIX permissions, AD and LDAP, and then various Sharing services which are typical to a NAS, Such as NFS / Samba and others. One neat feature was the built-in file-browser via the web-interface, which allows you another method of getting at your data when sometimes NFS / Samba or WebDav aren't enough. Jesse gives us a nice round-up conclusion as well Most of the NAS operating systems I have used in the past were built around useful features. Some focused on making storage easy to set up and manage, others focused on services, such as making files available over multiple protocols or managing torrents. Some strive to be very easy to set up. NAS4Free does pretty well in each of the above categories. It may not be the easiest platform to set up, but it's probably a close second. It may not have the prettiest interface for managing settings, but it is quite easy to navigate. NAS4Free may not have the most add-on services and access protocols, but I suspect there are more than enough of both for most people. Where NAS4Free does better than most other solutions I have looked at is security. I don't think the project's website or documentation particularly focuses on security as a feature, but there are plenty of little security features that I liked. NAS4Free makes it very easy to lock the text console, which is good because we do not all keep our NAS boxes behind locked doors. The system is fairly easy to upgrade and appears to publish regular security updates in the form of new firmware. NAS4Free makes it fairly easy to set up user accounts, handle permissions and manage home directories. It's also pretty straight forward to switch from HTTP to HTTPS and to block people not on the local network from accessing the NAS's web interface. All in all, I like NAS4Free. It's a good, general purpose NAS operating system. While I did not feel the project did anything really amazing in any one category, nor did I run into any serious issues. The NAS ran as expected, was fairly straight forward to set up and easy to manage. This strikes me as an especially good platform for home or small business users who want an easy set up, some basic security and a solid collection of features. Browsix: Unix in the browser tab (https://browsix.org/) Browsix is a research project from the PLASMA lab at the University of Massachusetts, Amherst. The goal: Run C, C++, Go and Node.js programs as processes in browsers, including LaTeX, GNU Make, Go HTTP servers, and POSIX shell scripts. “Processes are built on top of Web Workers, letting applications run in parallel and spawn subprocesses. System calls include fork, spawn, exec, and wait.” Pipes are supported with pipe(2) enabling developers to compose processes into pipelines. Sockets include support for TCP socket servers and clients, making it possible to run applications like databases and HTTP servers together with their clients in the browser. Browsix comprises two core parts: A kernel written in TypeScript that makes core Unix features (including pipes, concurrent processes, signals, sockets, and a shared file system) available to web applications. Extended JavaScript runtimes for C, C++, Go, and Node.js that support running programs written in these languages as processes in the browser. This seems like an interesting project, although I am not sure how it would be used as more than a toy *** Book Review: PAM Mastery (https://www.cyberciti.biz/reviews/book-review-pam-mastery/) nixCraft does a book review of Michael W. Lucas' “Pam Mastery” Linux, FreeBSD, and Unix-like systems are multi-user and need some way of authenticating individual users. Back in the old days, this was done in different ways. You need to change each Unix application to use different authentication scheme. Before PAM, if you wanted to use an SQL database to authenticate users, you had to write specific support for that into each of your applications. Same for LDAP, etc. So Open Group lead to the development of PAM for the Unix-like system. Today Linux, FreeBSD, MacOS X and many other Unix-like systems are configured to use a centralized authentication mechanism called Pluggable Authentication Modules (PAM). The book “PAM Mastery” deals with the black magic of PAM. Of course, each OS chose to implement PAM a little bit differently The book starts with the basic concepts about PAM and authentication. You learn about Multi-Factor Authentication and why use PAM instead of changing each program to authenticate the user. The author went into great details about why PAM is useful for developers and sysadmin for several reasons. The examples cover CentOS Linux (RHEL and clones), Debian Linux, and FreeBSD Unix system. I like the way the author described PAM Configuration Files and Common Modules that covers everyday scenarios for the sysadmin. PAM configuration file format and PAM Module Interfaces are discussed in easy to understand language. Control flags in PAM can be very confusing for new sysadmins. Modules can be stacked in a particular order, and the control flags determine how important the success or failure of a particular module. There is also a chapter about using one-time passwords (Google Authenticator) for your application. The final chapter is all about enforcing good password policies for users and apps using PAM. The sysadmin would find this book useful as it covers a common authentication scheme that can be used with a wide variety of applications on Unix. You will master PAM topics and take control over authentication for your organization IT infrastructure. If you are Linux or Unix sysadmin, I would highly recommend this book. Once again Michael W Lucas nailed it. The only book you may need for PAM deployment. get “PAM Mastery” (https://www.michaelwlucas.com/tools/pam) *** Reflections on Trusting Trust - Ken Thompson, co-author of UNIX (http://www.win.tue.nl/~aeb/linux/hh/thompson/trust.html) Ken Thompson's "cc hack" - Presented in the journal, Communication of the ACM, Vol. 27, No. 8, August 1984, in a paper entitled "Reflections on Trusting Trust", Ken Thompson, co-author of UNIX, recounted a story of how he created a version of the C compiler that, when presented with the source code for the "login" program, would automatically compile in a backdoor to allow him entry to the system. This is only half the story, though. In order to hide this trojan horse, Ken also added to this version of "cc" the ability to recognize if it was recompiling itself to make sure that the newly compiled C compiler contained both the "login" backdoor, and the code to insert both trojans into a newly compiled C compiler. In this way, the source code for the C compiler would never show that these trojans existed. The article starts off by talking about a content to write a program that produces its own source code as output. Or rather, a C program, that writes a C program, that produces its own source code as output. The C compiler is written in C. What I am about to describe is one of many "chicken and egg" problems that arise when compilers are written in their own language. In this case, I will use a specific example from the C compiler. Suppose we wish to alter the C compiler to include the sequence "v" to represent the vertical tab character. The extension to Figure 2 is obvious and is presented in Figure 3. We then recompile the C compiler, but we get a diagnostic. Obviously, since the binary version of the compiler does not know about "v," the source is not legal C. We must "train" the compiler. After it "knows" what "v" means, then our new change will become legal C. We look up on an ASCII chart that a vertical tab is decimal 11. We alter our source to look like Figure 4. Now the old compiler accepts the new source. We install the resulting binary as the new official C compiler and now we can write the portable version the way we had it in Figure 3. The actual bug I planted in the compiler would match code in the UNIX "login" command. The replacement code would miscompile the login command so that it would accept either the intended encrypted password or a particular known password. Thus if this code were installed in binary and the binary were used to compile the login command, I could log into that system as any user. Such blatant code would not go undetected for long. Even the most casual perusal of the source of the C compiler would raise suspicions. Next “simply add a second Trojan horse to the one that already exists. The second pattern is aimed at the C compiler. The replacement code is a Stage I self-reproducing program that inserts both Trojan horses into the compiler. This requires a learning phase as in the Stage II example. First we compile the modified source with the normal C compiler to produce a bugged binary. We install this binary as the official C. We can now remove the bugs from the source of the compiler and the new binary will reinsert the bugs whenever it is compiled. Of course, the login command will remain bugged with no trace in source anywhere. So now there is a trojan'd version of cc. If you compile a clean version of cc, using the bad cc, you will get a bad cc. If you use the bad cc to compile the login program, it will have a backdoor. The source code for both backdoors no longer exists on the system. You can audit the source code of cc and login all you want, they are trustworthy. The compiler you use to compile your new compiler, is the untrustworthy bit, but you have no way to know it is untrustworthy, and no way to make a new compiler, without using the bad compiler. The moral is obvious. You can't trust code that you did not totally create yourself. (Especially code from companies that employ people like me.) No amount of source-level verification or scrutiny will protect you from using untrusted code. In demonstrating the possibility of this kind of attack, I picked on the C compiler. I could have picked on any program-handling program such as an assembler, a loader, or even hardware microcode. As the level of program gets lower, these bugs will be harder and harder to detect. A well installed microcode bug will be almost impossible to detect. Acknowledgment: I first read of the possibility of such a Trojan horse in an Air Force critique of the security of an early implementation of Multics. I can- not find a more specific reference to this document. I would appreciate it if anyone who can supply this reference would let me know. Beastie Bits Custom made Beastie Stockings (https://www.etsy.com/listing/496638945/freebsd-beastie-christmas-stocking) Migrating ZFS from mirrored pool to raidz1 pool (http://ximalas.info/2016/12/06/migrating-zfs-from-mirrored-pool-to-raidz1-pool/) OpenBSD and you (https://home.nuug.no/~peter/blug2016/) Watson.org FreeBSD and Linux cross reference (http://fxr.watson.org/) OpenGrok (http://bxr.su/) FreeBSD SA-16:37: libc (https://www.freebsd.org/security/advisories/FreeBSD-SA-16:37.libc.asc) -- A 26+ year old bug found in BSD's libc, all BSDs likely affected -- A specially crafted argument can trigger a static buffer overflow in the library, with possibility to rewrite following static buffers that belong to other library functions. HardenedBSD issues correction for libc patch (https://github.com/HardenedBSD/hardenedBSD/commit/fb823297fbced336b6beeeb624e2dc65b67aa0eb) -- original patch improperly calculates how many bytes are remaining in the buffer. From December the 27th until the 30th there the 33rd Chaos Communication Congress[0] is going to take place in Hamburg, Germany. Think of it as the yearly gathering of the european hackerscene and their overseas friends. I am one of the persons organizing the "BSD assembly (https://events.ccc.de/congress/2016/wiki/Assembly:BSD)" as a gathering place for BSD enthusiasts and waving the flag amidst the all the other projects / communities. Feedback/Questions Chris - IPFW + Wifi (http://pastebin.com/WRiuW6nn) Jason - bhyve pci (http://pastebin.com/JgerqZZP) Al - pf errors (http://pastebin.com/3XY5MVca) Zach - Xorg settings (http://pastebin.com/Kty0qYXM) Bart - Wireless Support (http://pastebin.com/m3D81GBW) ***
Today on the show, we are going to be talking to Jim Brown (of BSD Cert Fame) about his home-brew sprinkler system… Wait for it… This episode was brought to you by Headlines Distrowatch reviews OpenBSD and PCBSD's live upgrade method (http://distrowatch.com/weekly.php?issue=20160620#upgrade) Upgrading… The bane of any sysadmin! Distrowatch has recently done a write-up on the in-place upgrading of various distros / BSDs including PC-BSD and OpenBSD. Lets look first at the PC-BSD attempt, which was done going from 9.2 -> 10. “I soon found trying to upgrade either the base system or pkg would fail. The update manager did not provide details as to what had gone wrong and so I decided to attempt a manual upgrade by following the FreeBSD Handbook as I had when performing a live upgrade of FreeBSD back in May. At first the manual process seemed to work, downloading the necessary patches for FreeBSD 10 and getting me to resolve conflicts between my existing configuration files and the new versions. Part way through, we are asked to reboot and then continue the upgrade process using the freebsd-update command utility. PC-BSD failed to reboot and, in fact, the boot loader no longer found any operating systems to run.” Ouch! I'm not sure on the particular commands used, but to lose the boot-loader indicates something went horribly wrong. There is good news in this though. After the pain experienced in the 9.X upgrade process, 11.0 has been vastly improved to help fix this going forward. The updater is also self-updating, which means future changes to tools such as package can be accounted for in previously released versions. Moving on to OpenBSD, Jesse had much better luck: > “The documentation provided explains how to upgrade OpenBSD 5.8 to version 5.9 step-by-step and the instructions worked exactly as laid out. Upgrading requires two reboots, one to initiate the upgrade process and one to boot into the new version of OpenBSD. Upgrading the base operating system took approximately ten minutes, including the two reboots. Upgrading the third-party packages took another minute or two. The only quirk I ran into was that I had to manually update my repository mirror information to gain access to the new packages available for OpenBSD 5.9. If this step is not done, then the pkg_add package manager will continue to pull in packages from the old repository we set up for OpenBSD 5.8. “ A good read, and they covered some Linux distros such as Mint and OpenMandriva as well, if you want to find out how they fared. *** A curated list of awesome DTrace books, articles, videos, tools and resources (http://awesome-dtrace.com/) The website awesome-dtrace.com compiles a list of resources, including books, articles, videos, tools, and other resources, to help you get the most out of DTrace The list of books includes 2 open source books that are available on the web, and of course Brendan Gregg's official DTrace book There are also cheat sheets, one-liner collections, and a set of DTrace war stories A breakdown of different PID providers and the userspace statically defined tracepoints The videos from DTrace.conf 2008, 2012, and soon 2016 And links to the tools to start using DTrace with your favourite programming language, including Erlang, Node.JS, Perl, PHP, Python, or Ruby There are also DTrace setups for MySQL/MariaDB, and PostreSQL Joyent has even written a mod_usdt DTrace module for the Apache web server This seems like a really good resource, and with the efforts of the new OpenDTrace project, to modernize the dtracetoolkit and make it more useful across the different supported operating systems, there has never been a better time to start learning DTrace *** Installing OpenBSD using a serial console with no external monitor (http://unix.stackexchange.com/questions/292891/how-can-i-install-openbsd-using-the-serial-console-without-external-monitor-wi) Have you found yourself needing to install OpenBSD from USB, but with a twist, as in no external monitor? Well somebody has and asked the question on stackexchange. The answer provided is quite well explained, but in a nut-shell the process involves downloading the USB image and making some tweaks before copying it to the physical media. Specifically with a couple of well-placed echo's into boot.conf, the serial-port can be enabled and ready for use: echo "stty com0 115200" > /mnt/etc/boot.conf echo "set tty com0" >> /mnt/etc/boot.conf + After that, simply boot the box and you are ready to access the serial console and drive the installation as normal! #bsdhacks GSoC 2016 Reports: Split debug symbols for pkgsrc builds (https://blog.netbsd.org/tnf/entry/gsoc_2016_reports_split_debug) The NetBSD blog provides a status report on one of the GSoC projects that is nearing its midterm evaluation The project to split debugging data into separate pkgsrc packages, so that users can install the debugging symbols if they need them to debug a failing application The report is very detailed, and includes “A quick introduction to ELF and how debug information are stored/stripped off” It walks through the process of writing a simple example application, compiling it, and dealing with the debug data It includes a number of very useful diagrams, and a summary of what changes needed to be make to the pkgsrc makefile infrastructure With this as a recipe, someone should be able to do something quite similar for FreeBSD's ports tree *** iXsystems iXsystems' TrueNAS Firmware Update Delivers Compelling Performance, Replication, and Graphing Improvements (https://www.ixsystems.com/blog/ixsystems-truenas-firmware-update-delivers-compelling-performance-replication-graphing-improvements/) *** Interview - Jim Brown - jpb@jimby.name (mailto:jpb@jimby.name) FreeBSD+BBB Sprinkler System News Roundup From the past : A Research Unix Reader (http://www.cs.dartmouth.edu/~doug/reader.pdf) A paper by by Douglas McIlroy “Selected pages from the nine research editions of the UNIX® Programmer's Manual illustrate the development of the system” “Accompanying commentary recounts some of the needs, events, and individual contributions that shaped this evolution.” Interesting insight into the evolution of the origin UNIX operating system *** Evolution of C programming practices – Unix 1973–2015 (http://kristerw.blogspot.com/2016/06/evolution-of-c-programming-practices.html) From the author of the recent post we covered, “20 years of NetBSD code bloat”, comes a new post “I found a recent paper that also looks at how the BSD code base has evolved, but from a very different perspective compared to my code-size investigation.” The paper "The Evolution of C Programming Practices: A Study of the Unix Operating System 1973–2015" investigates coding style, and tests seven hypotheses by looking at metrics (line length, number of volatile in the source code, etc.) in 66 releases of Unix from 1973 to 2014. The hypotheses are: > + Programming practices reflect technology affordances (e.g. developers may be more liberal with screen space when using high resolution displays) > + Modularity increases with code size > + New language features are increasingly used to saturation point > + Programmers trust the compiler for register allocation > + Code formatting practices converge to a common standard > + Software complexity evolution follows self correction feedback mechanisms > + Code readability increases and the result is that they seem to be true, as interpreted through the metrics. > “The data points for the releases have somewhat random dates. One issue is that the paper use each release's mean file date (the average of the files' last modification time) instead of the release date (that is why the graphs stop at November 2010, even though FreeBSD 10 was released in 2014). The idea is that this better reflects the age of the code base, but this has the effect of compressing some of the data points (especially the clustering around 1993-1994), and it makes the spline fitting even more suspect.” > “One other problem is that the original data used by the researchers seems to have incorrect timestamps. For example, 4.3BSD Net/1 was released in 1989, but is listed as 1993-12-25 in the paper. The same is true for at least the Net/2 release too, which was released in 1991, but the paper list it as 1993-07-02.” *** [old release pictures] openbsd 2.1 - 5.9, straight from theo's bookshelf. (https://twitter.com/blakkheim/status/747540167112671232) Speaking of old releases, our Producer JT picked up this gem at Southeast Linuxfest this year (https://twitter.com/q5sys/status/748003859012984837) Noah Axon shares a scan of his NetBSD 1.4 disc (https://plus.google.com/+NoahAxon/posts/VsiQhUn3tHb) Jan van den broek shares a pic of his FreeBSD 2.2.5 set (https://plus.google.com/101232368324501316985/posts/4QsaJE2KxXh) *** FreeBSD: Just in Time (https://bsdmag.org/just_in_time/) Another BSDMag goodie this week, we have a small article written by Jonathan Garrido which details their experience switching to FreeBSD for a NTP server. The article is short, but a good read: > “A Few years ago we had a time problem. Suddenly our linux NTP server, for a reason that I still do not know, started to fail giving us a lot of issues within all the equipment and services within our network. After a quick and brief meeting with management, I found out that there was not sufficient budget left for a fancy and well-suited appliance. So, with no time (literally) and no money to spend, I decided to give it a try and utilized a homemade open source solution, and the operating system of choice was FreeBSD 10.0.” “Now, let's pause for a second. You may be thinking, why in the world is this guy doing this, when he has never installed a BSD machine in his life? The answer is very simple; here, in the Dominican Republic, in the heart of the Caribbean, FreeBSD has a very good reputation when it comes to reliability and security. In fact, there is some collective thought within the sysadmin community that says something like: “If you want to deal only once with a service, install it over FreeBSD.”” Jonathan then goes through some of the steps taken to initial deploy NTP services, but with that out of the way, he has a great summary: > “Fascinated with the whole experience, we migrate one of our internal dns servers to a second FreeBSD machine and at the moment of this writing we are testing haproxy, an open source load-balancing proxy into a another server with the same OS. > After all this, no time issues have been reported in the past 2 years, so at least for my environment, FreeBSD came just in time.“ *** Beastie Bits MiniBSD laptop computer (https://hackaday.io/project/643-minibsd-laptop-computer) The state of LibreSSL in FreeBSD (https://attilagyorffy.com/2016/07/02/the-state-of-libressl-in-freebsd/) Justin Sherrill is looking for someone willing to run a Go builder with DragonflyBSD (https://www.dragonflydigest.com/2016/07/01/18372.html) Tiny Unix tools for Windows (https://tinyapps.org/blog/windows/201606040700_tiny_unix_tools_windows.html) OpenBSD's doas added to the FreeBSD Ports Tree (http://www.freshports.org/security/doas/) ubuntuBSD 16.04 to feature a combo of BusyBox and OpenRC, no systemd (http://linux.softpedia.com/blog/ubuntubsd-16-04-will-feature-a-combination-of-busybox-and-openrc-but-no-systemd-505463.shtml) Syncast Podcast 4 : Curl, libcurl and the future of the web, with Daniel Stenberg (http://podcast.sysca.st/podcast/4-curl-libcurl-future-web-daniel-stenberg/) Feedback/Questions Harri - Using beadm / zfssnap (http://pastebin.com/qKeCd63F) Jonathan - bhyve vs Proxmox (http://pastebin.com/EhXDwbWQ) Mohammad - Bhyve gfx passthrough (http://pastebin.com/ZCNk4Bga) Jeremy - Shapshots and more Snapshots (http://pastebin.com/xp7nzEYa) Ron - Microphone (http://pastebin.com/H2xr53CR) ***
This week on the show, we have all the latest news and stories! Plus an interview with BSD developer Alfred Perlstein, that you This episode was brought to you by Headlines The May issus of BSDMag is now out (https://bsdmag.org/download/reusing_openbsd/) GhostBSD Reusing OpenBSD's arc4random in multi-threaded user space programs Securing VPN's with GRE / Strongswan Installing XFCE 4.12 on NetBSD 7 Interview with Fernando Rodriguez, the co-founder of KeepCoding *** A rundown of the FPTW^XEXT.1 security reqiurement for General Purpose Operating Systems by the NSA (http://blog.acumensecurity.net/fpt_wx_ext-1-a-rundown/) NIST/NSA Validation Scheme Report (https://www.commoncriteriaportal.org/files/ppfiles/pp_os_v4.1-vr.pdf) The SFR or Security Functional Requirement requires that; "The OS shall prevent allocation of any memory region with both write and execute permissions except for [assignment: list of exceptions]." While nearly all operating systems currently support the use of the NX bit, or the equivalent on processors such as SPARC and ARM, and will correctly mark the stack as non-executable, the fact remains that this in and of itself is deemed insufficient by NIST and NSA. OpenBSD 5.8, FreeBSD, Solaris, RHEL, and most other Linux distro have failed. HardenedBSD passes all three tests out of the box. NetBSD will do so with a single sysctl tweak. Since they are using the PaX model, anything else using PaX, such as a grsecurity-enabled Linux distribution pass these assurance activities as well. OpenBSD 5.9 does not allow memory mapping due to W^X being enforced by the kernel, however the kernel will panic if there are any attempts to create such mappings. *** DistroWatch reviews new features in FreeBSD 10.3 (https://distrowatch.com/weekly.php?issue=20160516#freebsd) DistroWatch did a review of FreeBSD 10.3 They ran into a few problems, but hopefully those can be fixed An issue with beadm setting the canmount property incorrectly causing the ZFS BE menu to not work as expected should be resolved in the next version, thanks to a patch from kmoore The limitations of the Linux 64 support are what they are, CentOS 6 is still fairly popular with enterprise software, but hopefully some folks are interested in working on bringing the syscall emulation forward In a third issue, the reviewer seemed to have issues SSHing from inside the jail. This likely has to do with how they got a console in the jail. I remember having problems with this in the past, something about a secure console. *** BSD Unix: Power to the people, from the code (https://www.salon.com/2000/05/16/chapter_2_part_one/) Salon.com has a very long article, chronicling much of the history behind BSD UNIX. It starts with detailing the humble origins of BSD, starting with Bill Joy in the mid-70's, and then goes through details on how it rapidly grew, and the influence that the University of Berkeley had on open-source. “But too much focus on Joy, a favorite target for business magazine hagiography, obscures the larger picture. Berkeley's most important contribution was not software; it was the way Berkeley created software. At Berkeley, a small core group — never more than four people at any one time — coordinated the contributions of an ever-growing network of far-flung, mostly volunteer programmers into progressive releases of steadily improving software. In so doing, they codified a template for what is now referred to as the “open-source software development methodology.” Put more simply, the Berkeley hackers set up a system for creating free software.” The article goes on to talk about some of the back and forth between Linux and BSD, and why Linux has captured more of the market in recent years, but BSD is far from throwing in the towel. “BSD patriots argue that the battle is far from over, that BSD is technically superior and will therefore win in the end. That's for the future to determine. What's indisputable is BSD's contribution in the past. Even if, by 1975, Berkeley's Free Speech Movement was a relic belonging to a fast-fading generation, on the fourth floor of Evans Hall, where Joy shared an office, the free-software movement was just beginning.” An excellent article (If a bit long), but well worth your time to understand the origins of what we consider modern day BSD, and how the University of Berkley helped shape it. *** iXsystems (http://ixsystems.com) #ServerEnvy: It's over 10,000 Terabytes! (https://www.ixsystems.com/blog/serverenvy-10000-terabytes/) *** Interview - Alfred Perlstein - alfred@freebsd.org (mailto:alfred@freebsd.org) / @splbio (https://twitter.com/splbio) Using BSD for projects *** News Roundup .NET framework ported to NetBSD (https://github.com/dotnet/coreclr/pull/4504/files) This pull request adds basic support for the .NET framework on NetBSD 7.x amd64 It includes documentation on how to get the .NET framework installed It uses pkgsrc to bootstrap the required tools pkgsrc-wip is used to get the actual .NET framework, as porting is still in progress The .NET Core-CLR is now available for: FreeBSD, Linux, NetBSD, and OS X *** OpenBSD SROP mitigation – call for testing (https://marc.info/?l=openbsd-tech&m=146281531025185&w=2) A new technique for exploiting flaws in applications and operating systems has been developed, called SROP “we describe Sigreturn Oriented Programming (SROP), a novel technique for exploits and backdoors in UNIX-like systems. Like return-oriented programming (ROP), sigreturn oriented programming constructs what is known as a ‘weird machine' that can be programmed by attackers to change the behavior of a process. To program the machine, attackers set up fake signal frames and initiate returns from signals that the kernel never really delivered. This is possible, because UNIX stores signal frames on the process' stack.” “Sigreturn oriented programming is interesting for attackers, OS developers and academics. For attackers, the technique is very versatile, with pre-conditions that are different from those of existing exploitation techniques like ROP. Moreover, unlike ROP, sigreturn oriented programming programs are portable. For OS developers, the technique presents a problem that has been present in one of the two main operating system families from its inception, while the fixes (which we also present) are non-trivial. From a more academic viewpoint, it is also interesting because we show that sigreturn oriented programming is Turing complete.” Paper describing SROP (http://www.cs.vu.nl/~herbertb/papers/srop_sp14.pdf) OpenBSD has developed a mitigation against SROP “Utilizing a trick from kbind(2), the kernel now only accepts signal returns from the PC address of the sigreturn(2) syscall in the signal trampoline. Since the signal trampoline page is randomized placed per process, it is only known by directly returning from a signal handler.” “As well, the sigcontext provided to sigreturn(2) now contains a magic cookie constructed from a per-process cookie XOR'd against the address of the signal context.” This is just a draft of the patch, not yet considered production quality *** Running Tor in a NetBSD rump unikernel (https://github.com/supradix/rumprun-packages/tree/33d9cc3a65a39e32b4bc8034c151a5d7e0b89f66/tor) We've talked about “rump” kernels before, and also Tor pretty frequently, but this new github project combines the two! Specifically, this set of Makefile and scripts will prep a system to run Tor via the Unikernel through Qemu. The script mainly describes how to do the initial setup on Linux, using iptables, but could easily be adapted to a BSD if somebody wants to do so. (Send them a pull request with the instructions!) All in all, this is a fascinating way to run a Tor node or relay, in the most minimal operating environment possible. *** An update on SSH protocol 1 ("we're most of the way towards fully deprecating SSH protocol 1" (http://lists.mindrot.org/pipermail/openssh-unix-dev/2016-May/035069.html) Damien Miller has given us an update on the status of the “SSH protocol 1”, and the current plans to deprecate it in an upcoming version of openssh. “We've had this old protocol in various stages of deprecation for almost 10 years and it has been compile-time disabled for about a year. Downstream vendors, to their credit, have included this change in recent OS releases by shipping OpenSSH packages that disable protocol 1 by default and/or offering separate, non-default packages to enable it. This seems to have proceeded far more smoothly than even my most optimistic hopes, so this gives us greater confidence that we can complete the removal of protocol 1 soon. We want to do this partly to hasten the demise of this cryptographic trainwreck, but also because doing so removes a lot of legacy code from OpenSSH that inflates our attack surface. Having it gone will make our jobs quite a bit easier as we maintain and refactor.” The current time-line looks like removing server-size protocol 1 support this August after OpenSSH 7.4 is released, leaving client-side disabled. Then a year from now (June 2017) all protocol 1 code will be removed. Beastie Bits Last day to get your BSDNow Shirts! Order now, wear at BSDCan! (https://teespring.com/bsdnow) Move local government (Austin TX) from Microsoft Windows (incl. Office) to Linux and/or PC-BSD (https://github.com/atxhack4change/2016-project-proposals/issues/15) Plan9 boot camp is back... and already at capacity. Another opportunity may come in September (http://lists.nycbug.org/pipermail/talk/2016-May/016642.html) Smaller is better - building an openbsd based router (https://functionallyparanoid.com/2016/04/22/smaller-is-better/) Baby Unix (https://i.redditmedia.com/KAjSscL9XOUdpIEWBQF1qi3QMr7zWgeETzQM6m3B4mY.jpg?w=1024&s=e8c08a7d4c4cea0256adb69b1e7c1887) Security Update for FreeBSD (https://security.freebsd.org/advisories/FreeBSD-SA-16:19.sendmsg.asc) & Another security update for FreeBSD (https://security.freebsd.org/advisories/FreeBSD-SA-16:18.atkbd.asc) Feedback/Questions Eric - The iX experience (http://pastebin.com/ZknTuKGv) Mike - Building Ports (http://pastebin.com/M760ZmHQ) David - ZFS Backups (http://pastebin.com/Pi0AFghV) James - BSD VPS (http://pastebin.com/EQ7envez) Rich - ZFS Followup (http://pastebin.com/p0HPDisH) ***
This week on the show, we are going to be talking to Trent Thompson, This episode was brought to you by iX Systems Mission Complete (https://www.ixsystems.com/missioncomplete/) Submit your story of how you accomplished a mission with FreeBSD, FreeNAS, or iXsystems hardware, and you could win monthly prizes, and have your story featured in the FreeBSD Journal! *** Headlines Review: Guarding the gates with OpenBSD 5.8 (http://distrowatch.com/weekly.php?issue=20151207#openbsd) Jesse Smith over at DistroWatch treats us this week to a nice review of OpenBSD 5.8, which may be a good introduction for the uninitiated to learn more+ He first walks through some of the various highlights of 5.8, and spends time introducing the reader to a number of the projects that originate from OpenBSD, such as LibreSSL, OpenSSH, doas, the new “file” implementation and W^X support on i386. The article then walks through his impressions of performing a fresh install of 5.8, and then getting up and running in X. He mentions that you may want to check the installation defaults, since on his 8GB VM disk, it didn't leave enough room for packages on the /usr partition. It also includes a nice heads-up for new users about using the pkg_add command, and where / how you can set the initial repository mirror address. The “doas” command was also praised:“I found I very much appreciated the doas command, its documentation and configuration file. The doas configuration file is much easier to read than sudo's and the available options are well explained. The doas command allowed me to assign root access to a user given the proper password and doas worked as advertised.” A glowing summary as well:“OpenBSD may be very secure, but I think what sets the operating system apart are its documentation and clean system design. It is so easy to find things and understand the configuration of an OpenBSD system. The file system is organized in a clean and orderly manner. It always takes me a while to get accustomed to using OpenBSD, as for me it is a rare occurrence, but once I get settled in I like how straight forward everything is. I can usually find and configure anything on the system without referring to external documents or searching for answers on-line and that is quite an accomplishment for an operating system where virtually everything is done from the command line. “ *** OpenBSD Hackathon Reports Alexander Bluhm: multiprocessor networking (http://undeadly.org/cgi?action=article&sid=20151212192918) “The next step, we are currently working on, is to remove the big kernel lock from forwarding and routing. mpi@ has been doing this for a long time, but some corner cases were still left. I have written a regression test for handling ARP packets to show that all cases including proxy ARP are still working. Another thing that may happen with lock-free routing is that the interface is destroyed on one CPU while another CPU is working with a route to that interface. We finally got this resolved. The code that destroys the interface has to wait until all routes don't use this interface anymore. I moved the sleep before the destruction of the interface is started, so that the routes can always operate on a completely valid interface structure.” Vincent Gross: ifa_ifwithaddr() (http://undeadly.org/cgi?action=article&sid=20151215150708) Vincent worked on the function that finds the interface with the specified address, which is used to tell if the machine is the intended recipient of an incoming packet. A number of corner cases existed with broadcast addresses, especially if two interfaces were in the same subnet. This code was moved to the new in_broadcast() Ken Westerback: fdisk, installbot, and dhclient (http://undeadly.org/cgi?action=article&sid=20151216192843) Reyk Floeter: Hosting a hackathon, vmd, vmctl (http://undeadly.org/cgi?action=article&sid=20151217134417) “When I heard that Martin Pieuchot (mpi@) was looking for a place to hold another mini-hackathon for three to four people to work on multiprocessor (MP) enhancements of the network stack, I offered to come to our work place in Hannover, Northern Germany. We have space, gear, fast Internet and it is easy to reach for the involved people. Little did I know that it would quickly turn into n2k15, a network hackathon with 20 attendees from all over the world” “If you ever hosted such an event or a party for many guests, you will know the dilemma of the host: you're constantly concerned about your guests enjoying it, you have to take care about many trivial things, other things will break, and you get little to no time to attend or even enjoy it yourself. Fortunately, I had very experienced and welcomed guests: only one vintage table and a vase broke – the table can be fixed – and I even found some time for hacking myself.” Martin Pieuchot: MP networking (http://undeadly.org/cgi?action=article&sid=20151218175010) “ We found two kind of MP bugs! There are MP bugs that you fix without even understanding them, and there are MP bugs that you understand but can't fix” Stefan Sperling: initial 802.11n support (http://undeadly.org/cgi?action=article&sid=20151219160501) *** Hacking the PS4 (https://cturt.github.io/ps4.html) As a followup to the story last week about the PS4 being “jailbroken”, we have a link to further information about how far this project has come along This article also provides some great background information about whats running under the hood of your PS4, including FreeBSD 9, Mono VM and WebKit, with WebKit being the primary point of entry to jailbreak the box. One particular point of interest, was the revelation that early firmware versions did not include ASLR, but it appears ASLR was added sometime around firmware 1.70. (Wonder if they used HardenedBSD's implementation), and how they can bypass it entirely. “Luckily for us, we aren't limited to just writing static ROP chains. We can use JavaScript to read the modules table, which will tell us the base addresses of all loaded modules. Using these bases, we can then calculate the addresses of all our gadgets before we trigger ROP execution, bypassing ASLR.“ The article also mentions that they can prove that jails are used in some fashion, and provides examples of how they can browse the file system and dump a module list. The kernel exploit in question is SA-15:21 (https://www.freebsd.org/security/advisories/FreeBSD-SA-15:21.amd64.asc) from August of this year. The jailbreaking appears to be against an older version of PS4 firmware that did not include this patch *** Nokia and ARM leading the charge to implement better TCP/IP as part of the 5G standard (http://www.theregister.co.uk/2015/12/14/nokia_and_arm_bid_reinvent_tcpip_stack_5g/?page=1) “Many believe that a critical success factor for 5G will be a fully revamped TCP/IP stack, optimized for the massively varied use cases of the next mobile generation, for cloud services, and for virtualization and software-defined networking (SDN). This is the goal of the new OpenFastPath (OFP) Foundation, founded by Nokia Networks, ARM and industrial IT services player Enea. This aims to create an open source TCP/IP stack which can accelerate the move towards SDN in carrier and enterprise networks. Other sign-ups include AMD, Cavium, Freescale, Hewlett Packard Enterprise and the ARM-associated open source initiative, Linaro.” “The new fast-path TCP/IP stack will be based on the open source FreeBSD operating system” The general idea is to have a fast, open source, user space networking stack, based on the FreeBSD stack with an “optimised callback-based zero-copy socket API” to keep packet processing in user-space as far as possible It will be interesting to see a little bit more FreeBSD getting into every mobile and cloud based device. *** Interview - Trent Thompson - trentnthompson@gmail.com (trentnthompson@gmail.com) / @pr1ntf (https://twitter.com/pr1ntf) iohyve (https://github.com/pr1ntf/iohyve) *** News Roundup First cut of the FreeBSD modularized TCP stack (https://svnweb.freebsd.org/base?view=revision&revision=292309) FreeBSD now has more than one TCP stack, and better yet, you can use more than one at once Each socket pcb is associated with a stack, and it is possible to select a non-default stack with a socket option, so you can make a specific application use an experimental stack, while still defaulting to the known-good stack This should lead to a lot of interesting development and testing, without the level of risk usually associated with modifying the TCP stack The first new module available is ‘fastpath', which may relate to the Nokia story earlier in the show There are also plans to support changing TCP stacks after establish a session, which might land as early as January *** Faces of FreeBSD : Erin Clark (http://freebsdfoundation.blogspot.com/2015/12/faces-of-freebsd-2015-erin-clark.html) In this edition of “Faces of FreeBSD” the FreeBSD foundation gives us an introduction to Erin Clark, of our very own iXsystems! Her journey to the BSD family may sound similar to a lot of ours. She first began using Linux / Slackware in the early 2000's, but in 2009 a friend introduced her to FreeBSD and the rest, as they say, is history. “I use FreeBSD because it is very solid and secure and has a great selection of open source software that can be used with it from the ports collection. I have always appreciated FreeBSD's networking stack because it makes a great router or network appliance. FreeBSD's use of the ZFS file system is also very nice - ZFS snapshots definitely saved me a few times. I also like that FreeBSD is very well documented; almost everything you need to know about working with FreeBSD can be found in the FreeBSD Handbook.” Originally a sys admin at iXsystems, where she helped managed PC-BSD desktops among others, now she works on the FreeNAS project as a developer for the CLI interface functionality. *** New Olimex board runs Unix (https://olimex.wordpress.com/2015/12/16/new-product-in-stock-pic32-retrobsd-open-source-hardware-board-running-unix-like-retrobsd-os/) Looking for some small / embedded gear to mess around with? The Olimex folks have a new Pic32 system now available which runs “RetroBSD” “The current target is Microchip PIC32 microcontroller with 128 kbytes of RAM and 512 kbytes of Flash. PIC32 processor has MIPS M4K architecture, executable data memory and flexible RAM partitioning between user and kernel modes.” RetroBSD isn't something we've covered extensively here on BSDNow, so to bring you up to speed, it is a port of 2.11 BSD Their website lists the following features of this 2.11 refresh:“ Small resource requirements. RetroBSD needs only 128 kbytes of RAM to be up and running user applications. Memory protection. Kernel memory is fully protected from user application using hardware mechanisms. Open functionality. Usually, user application is fixed in Flash memory - but in case of RetroBSD, any number of applications could be placed into SD card, and run as required. Real multitasking. Standard POSIX API is implemented (fork, exec, wait4 etc). Development system on-board. It is possible to have C compiler in the system, and to recompile the user application (or the whole operating system) when needed.“ For those looking into BSD history, or wanting something small and exotic to play with this may fit the bill nicely. *** OpenSource.com reviews PCBSD (https://opensource.com/life/15/12/bsd-desktop-user-review-pc-bsd) Joshua over at opensource.com writes up a review of PC-BSD (10.2 we assume) Some of the highlights mentioned, include the easy to use graphical installer, but he does mention we should update the sorting of languages. (Good idea!) Along with including nice screenshots, it also covers the availability of various DE's / WM's, and talks a fair amount about the AppCafe and Control Panel utilities. “Thanks to being featured on PC-BSD's desktop, the PC-BSD Handbook is easily located by even the most novice user. There is no need to search through the system's installed applications for a manual, or relying solely on the help documentation for individual components. While not comprehensive, PC-BSD's handbook does a good job as striking a balance between concise and thorough. It contains enough information to help and provides detailed instructions for the topics it covers, but it avoids providing so much information that it overwhelms” *** BeastieBits Gandi introduces support for FreeBSD on their IaaS platform, with both ZFS and UFS based images available (https://www.gandi.net/news/en/2015-12-23/6473-introducing_freebsd_and_trimming_down_the_official_image_list/) Funny commit message from the Linux kernel (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f076ef44a44d02ed91543f820c14c2c7dff53716) FreeBSD Journal, Nov/Dec 2015 (https://www.freebsdfoundation.org/journal/vol2_no6) Feedback/Questions Zafer - NetBSD on DO (http://slexy.org/view/s2MPhvSFja) Richard - FreeNAS Replication (http://slexy.org/view/s2hhJktjRu) Winston - Android ADP (http://slexy.org/view/s2VK83ILlK) Alex - Multiple Domains (http://slexy.org/view/s20UVY8Bs5) Randy - Getting Involved (http://slexy.org/view/s20Cb076tu) Craig - zprezto (http://slexy.org/view/s2HNQ2aB42) ***
A día de hoy, 9 de Diciembre del 2015, Debian ha superado a Ubuntu en el famoso portal linuxero distrowatch, de hecho ya lleva días por delante de Ubuntu. De este tema y de otros hablamos en el podcast de hoy para Killall Radio en donde además de mi, contamos con Eugenio de (etccrond.es) y Sergio de (tarteka.net) como invitados. Toda la música del podcast es de jamendo.com
Going Linux #265 · 2014 Year End Review In this, our year end show, we review a few Linux distributions, look at the top of the list on Distrowatch, and comment on some of the significant Linux-related happenings throughout the year. Episode 265 Time Stamps 00:00 Going Linux #265 · 2014 Year End Review 00:15 Introduction 05:49 Open Suse mini review 17:19 Google Drive options 27:03 2014 distro news 27:22 Linux Mint 35:14 Microsoft loves Linux 35:42 Top 5 on Distrowatch 36:35 Mageia 37:54 Devuan 41:32 RedHat gets buddy-buddy with CentOS 45:26 Netflix on Linux 48:19 Shout out to other podcasts 53:20 Sonar GNU/Linux 56:28 Farewell Computer America 60:33 The future of Going Linux 61:59 Was 2014 the year of the Linux desktop? 65:27 Predictions for 2015 69:04 Application pick 71:39 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 72:46 End
Finally hit 30 episodes! Today we'll be chatting with Warren Block to discuss BSD documentation efforts and future plans. If you've ever wondered about the scary world of mailing lists, today's tutorial will show you the basics of how to get help and contribute back. There's lots to get to today, so sit back and enjoy some BSD Now - the place to B.. SD. This episode was brought to you by Headlines OpenBSD on a Sun T5120 (http://www.tedunangst.com/flak/post/OpenBSD-on-a-Sun-T5120) Our buddy Ted Unangst (http://www.bsdnow.tv/episodes/2014_02_05-time_signatures) got himself a cool Sun box Of course he had to write a post about installing and running OpenBSD on it The post goes through some of the quirks and steps to go through in case you're interested in one of these fine SPARC machines He's also got another post about OpenBSD on a Dell CS24-SC server (http://www.tedunangst.com/flak/post/Dell-CS24-SC-server) *** Bhyvecon 2014 videos are up (https://www.youtube.com/results?search_query=bhyvecon%20tokyo&sm=3) Like we mentioned last week, Bhyvecon (http://bhyvecon.org/) was an almost-impromptu conference before AsiaBSDCon The talks have apparently already been uploaded! Subjects include Bhyve's past, present and future, OSv on Bhyve, a general introduction to the tool, migrating those last few pesky Linux boxes to virtualization Lots more detail in the videos, so check 'em all out *** Building a FreeBSD wireless access point (http://blog.khubla.com/freebsd/building-my-own-wireless-point) We've got a new blog post about creating a wireless access point with FreeBSD After all the recent news of consumer routers being pwned like candy, it's time for people to start building BSD routers (http://www.bsdnow.tv/tutorials/openbsd-router) The author goes through a lot of the process of getting one set up using good ol' FreeBSD Using hostapd, he's able to share his wireless card in hostap mode and offer DHCP to all the clients Plenty of config files and more messy details in the post *** Switching from Synology to FreeNAS (http://www.notquitemainstream.com/2014/03/15/why-im-switching-from-synology-to-freenas/) The author has been considering getting a NAS for quite a while and documents his research He was faced with the compromise of convenience vs. flexibility - prebuilt or DIY After seeing the potential security issues with proprietary NAS devices, and dealing with frustration with trying to get bugs fixed, he makes the right choice The post also goes into some detail about his setup, all the things he needed a NAS to do as well as all the advantages an open source solution would give *** Interview - Warren Block - wblock@freebsd.org (mailto:wblock@freebsd.org) FreeBSD's documentation project, igor, doceng Tutorial The world of BSD mailing lists (http://www.bsdnow.tv/tutorials/mailing-lists) News Roundup HAMMER2 work and notes (http://www.shiningsilence.com/dbsdlog/2014/03/18/13651.html) Matthew Dillon has posted some updated notes about the development of the new HAMMER version The start of a cluster API was committed to the tree There are also links to design document, a freemap design document, a changes list and a todo list *** BSD Breaking Barriers (https://www.youtube.com/watch?v=buo5JlMnGPI) Our friend MWL (http://www.bsdnow.tv/episodes/2013_11_06-year_of_the_bsd_desktop) gave a talk at NYCBSDCon about BSD "breaking barriers" "What makes the BSD operating systems special? Why should you deploy your applications on BSD? Why does the BSD community keep growing, and why do Linux sites like DistroWatch say that BSD is where the interesting development work is happening? We'll cover the not-so-obvious reasons why BSD still stands tall after almost 40 years." He also has another upcoming talk, (or "webcast") called "Beyond Security: Getting to Know OpenBSD's Real Purpose (http://oreillynet.com/pub/e/3059)" "OpenBSD is frequently billed as a high-security operating system. That's true, but security isn't the OpenBSD Project's main goal. This webcast will introduce systems administrators to OpenBSD, explain the project's mission, and discuss the features and benefits." It's on May 27th and will hopefully be recorded *** FreeBSD in a chroot (http://dreamcat4.github.io/finch/) Finch, "FreeBSD running IN a CHroot," is a new project It's a way to extend the functionality of restricted USB-based FreeBSD systems (FreeNAS, etc.) All the details and some interesting use cases are on the github page He really needs to change the project name (https://www.freshports.org/net-im/finch) though *** PCBSD weekly digest (http://blog.pcbsd.org/2014/03/pc-bsd-weekly-feature-digest-22/) Lots of bugfixes for PCBSD coming down the tubes LZ4 compression is now enabled by default on the whole pool The latest 10-STABLE has been imported and builds are going Also the latest GNOME and Cinnamon builds have been imported and much more *** Feedback/Questions Bostjan writes in (http://slexy.org/view/s20SlvTcwd) (IRC suggests md5deep) Don writes in (http://slexy.org/view/s2PeMqXFid) kaltheat writes in (http://slexy.org/view/s21yii6KZe) (We use R0DE Podcast microphones and Logitech C920 HD webcams) Harri writes in (http://slexy.org/view/s21SkX19Cp) ***
This week on the show, we sit down for an interview with Jordan Hubbard, one of the founders of the FreeBSD project - and the one who invented ports! Later in the show, we'll be showing you some new updates to the OpenBSD router tutorial from a couple weeks ago. We've also got news, your questions and even our first viewer-submitted video, right here on BSD Now.. the place to B.. SD. Headlines Getting to know your portmgr (http://blogs.freebsdish.org/portmgr/2013/11/18/getting-to-know-your-portmgr-erwin-lansing/) In this interview they talk to one of the "Annoying Reminder Guys" - Erwin Lansing, the second longest serving member of FreeBSD's portmgr (also vice-president of the FreeBSD Foundation) He actually maintains the .dk ccTLD Describes FreeBSD as "the best well-hidden success story in operating systems, by now in the hands of more people than one can count and used by even more people, and not one of them knows it! It's not only the best operating system currently around, but also the most supportive and inspiring community." In the next one (http://blogs.freebsdish.org/portmgr/2013/11/25/getting-to-know-your-portmgr-martin-wilke/) they speak with Martin Wilke (miwi@) The usual, "what inspires you about FreeBSD" "how did you get into it" etc. *** vBSDCon wrap-up compilation (http://blog.hostileadmin.com/2013/11/20/vbsdcon-wrap-ups/) Lots of write-ups about vBSDCon gathered in one place Some from OpenBSD guys (http://undeadly.org/cgi?action=article&sid=20131121050402) Some from FreeBSD guys (http://freebsdfoundation.blogspot.com/2013/11/vbsdcon-trip-report-john-mark-gurney.html) Some from RootBSD (http://www.rootbsd.net/vbsdcon-2013-wrap-up/) Some from iXsystems (http://www.ixsystems.com/resources/ix/blog/vbsdcon-2013.html) Some from Verisign (http://blogs.verisigninc.com/blog/entry/builders_and_archaeologists) And of course our own wrap-up chat in BSD Now Episode 009 (http://www.bsdnow.tv/episodes/2013_10_30-current_events) *** Faces of FreeBSD (http://freebsdfoundation.blogspot.com/2013/11/faces-of-freebsd-each-week-we-are-going.html) This week they talk to Gábor Páli from Hungary Talks about his past as a game programmer and how it got involved with FreeBSD "I met János Háber, who admired the technical merits of FreeBSD and recommended it over the popular GNU/Linux distributions. I downloaded FreeBSD 4.3-RELEASE, found it reliable, consistent, easy to install, update and use." He's been contributing since 2008 and does lots of work with Haskell in ports He also organizes EuroBSDCon and is secretary of the FreeBSD Core Team *** Dragonfly 3.6 released (http://www.dragonflybsd.org/release36/) dports now default instead of pkgsrc Big SMP scaling improvements Experimental i915 and KMS support See our interview (http://www.bsdnow.tv/episodes/2013_11_13-the_gateway_drug) with Justin Sherrill if you want to hear (a lot) more about it - nearly an hour long *** Interview - Jordan Hubbard - jkh@freebsd.org (mailto:jkh@freebsd.org) / @omgjkh (https://twitter.com/omgjkh) FreeBSD's founding and future Tutorial Building an OpenBSD router, part 2 (http://www.bsdnow.tv/tutorials/openbsd-router) Note: there was a mistake in the video version of the tutorial, please consult the written version for the proper instructions. *** News Roundup pfSense 2.1 on AWS EC2 (http://blog.pfsense.org/?p=1132) We now have pfSense 2.1 available on Amazon's Elastic Compute Cloud (EC2) In keeping with the community spirit, they're also offering a free "public" AMI Check the FAQ and User Guide on their site for additional details Interesting possibilities with pfSense in the cloud *** Puffy on the desktop (http://distrowatch.com/weekly.php?issue=20131118#feature) Distrowatch, a primarily Linux-focused site, features an OpenBSD 5.4 review They talk about using it on the desktop, how to set it up Very long write-up, curious Linux users should give it a read Ends with "Most people will still see OpenBSD as an operating system for servers and firewalls, but OpenBSD can also be used in desktop environments if the user doesn't mind a little manual work. The payoff is a very light, responsive system that is unlikely to ever misbehave" *** Two-factor authentication with SSH (http://cmacr.ae/openbsd/security/networking/2013/11/25/ssh-yubi.html) Blog post about using a yubikey with SSH public keys Uses a combination of a OTP, BSDAuth and OpenBSD's login.conf, but it can be used with PAM on other systems as well Allows for two-factor authentication (a la gmail) in case your private key is compromised Anyone interested in an extra-hardened SSH server should give it a read *** PCBSD weekly digest (http://blog.pcbsd.org/2013/11/weekly-feature-digest-112313/) 10.0 has approximately 400 PBIs for public consumption They will be merging the GNOME3, MATE and Cinnamon desktops into the 10.0 ports tree - please help test them, this is pretty big news in and of itself! PCDM is coming along nicely, more bugs are getting fixed Added ZFS dataset options to PCBSD's new text installer front-end *** Feedback/Questions Ben writes in (http://slexy.org/view/s2ag1fA7Ug) Florian writes in (http://slexy.org/view/s2TSIvZzVO) Zach writes in (http://slexy.org/view/s20Po4soFF) Addison writes in (http://slexy.org/view/s20ntzqi9c) Adam writes in (http://slexy.org/view/s2EYJjVKBk) Adam (https://twitter.com/redshirtlinux)'s BSD Router Project tutorial can be downloaded here (http://bsdnow.cdn.scaleengine.net/bsdrouterproject.m4v). ***
After returning from a successful EuroBSDCon in Malta, we're back to get you caught up on all the latest news! We've got stories, interviews and a special treat for OpenBSD fans later in the show. All that and more on this week's BSD Now, the place to B.. SD. Headlines FreeBSD 9.2 released (https://www.freebsd.org/releases/9.2R/relnotes.html) FreeBSD 9.2-RELEASE is finally out Highlights include ZFS TRIM and LZ4 support, virtio drivers, dtrace and OpenSSH updates as well as lots of driver improvements Will be supported until 2014-09-30 Get out there and freebsd-update or buildworld! *** Four new NetBSD releases (https://blog.netbsd.org/tnf/entry/netbsd_5_2_1_and) NetBSD 5.2 and 5.1 branches get security and bugfix updates The 6.1 and 6.0 branches were updated soon after (https://blog.netbsd.org/tnf/entry/netbsd_6_1_2_and), also with security updates and bug fixes Check the show notes for the full changelog *** BIND being replaced by unbound in FreeBSD (http://freshbsd.org/commit/freebsd/r255597) Most FreeBSD users are familiar with BIND from the security notifications It has has many vulnerabilities over the years, and we'll finally be rid of it (http://blog.des.no/2013/09/dns-in-freebsd-10/) Being replaced with unbound and ldns, everyone rejoices (http://blog.des.no/2013/09/dns-again-a-clarification/) As of September 24th (https://svnweb.freebsd.org/base?view=revision&revision=255850), BIND is no longer built by default As of September 30th (http://freshbsd.org/commit/freebsd/r255949), BIND was completely removed Includes an easy to use script (http://freshbsd.org/commit/freebsd/r255809) for local DNS OpenBSD also has unbound in base (http://marc.info/?l=openbsd-cvs&m=137984954228414&w=2), but it's not built by default yet *** DragonflyBSD future plans (http://lists.dragonflybsd.org/pipermail/kernel/2013-September/062975.html) An announcement was posted that details some possible plans for Dragonfly dports (their version of FreeBSD ports) will be switching to GCC 4.7 i915 support is probably going to be in version 3.6 Work is being done on HAMMER 2, but it won't make it to 3.6 3.6 is also likely going to ditch pkgsrc as the default in favor of dports, due to a hugely positive reaction from the community *** FreeBSD ports get Stack Protector support (https://lists.freebsd.org/pipermail/freebsd-ports-announce/2013-September/000066.html) Some portsnap users noticed a massive sweep of every port being updated Shortly after, stack protector (https://en.wikipedia.org/wiki/Buffer_overflow_protection) support was announced by Bryan Drewery Only works on i386 and AMD64 on FreeBSD 10 and AMD64 on 9 Hopefully will become the default, but needs to go through some testing and exp-runs *** EuroBSDCon 2013 wrap-up chat BSD Now is back from EuroBSDCon with lots of stories We picked up an OpenBSD 5.4 CD set at EuroBSDCon, before the official release We'll give a little showcase of what's inside, they put a lot of effort into it Comes with the OS, source code, stickers, music, cool other stuff Consider supporting the OpenBSD project (http://www.openbsd.org/orders.html) *** Interview - Marshall Kirk McKusick - mckusick@freebsd.org (mailto:mckusick@freebsd.org) Various topics Tutorial Faster recompiles with ccache and tmpfs (http://www.bsdnow.tv/tutorials/ccache) News Roundup List of vBSDCon speakers posted (http://blog.hostileadmin.com/2013/09/09/reminder-vbsdcon-registrations-are-open/) Registration will be open until October 23rd Presentations covering FreeBSD, OpenBSD, FreeNAS and others *** Xen PVHVM added to GENERIC (https://svnweb.freebsd.org/base?view=revision&revision=255744) It's now possible to run FreeBSD 10 under Xen with the GENERIC kernel freebsd-update will work now With FreeBSD 10 ALPHA 4 (https://lists.freebsd.org/pipermail/freebsd-snapshots/2013-September/000045.html) just being released, should be interesting We should call the new kernel "XENERIC" *** Dragonfly AMD KMS port (http://lists.dragonflybsd.org/pipermail/kernel/2013-September/062993.html) A Dragonfly user has started porting the new FreeBSD AMD KMS driver Still a work in progress, asking for help from the community *** NetBSD gets an nVidia driver (http://mail-index.netbsd.org/source-changes/2013/09/18/msg047712.html) NetBSD gets a preliminary nVidia driver So far only supports the GeForce 2MX, so not a lot of use just yet No acceleration yet, but it's a start *** FreeBSD cracks the top 10 on DistroWatch (http://distrowatch.com/dwres.php?resource=popularity) Over the last year FreeBSD has steadily moved up the rankings from #18 to #10 Increasing from an average of 570 to 779 hits per day Surpassed CentOS, Puppy Linux and Slackware *** Feedback/Questions Charlie writes in (http://slexy.org/view/s21jRKf7lp) Kjell-Aleksander writes in (http://slexy.org/view/s2M0OKmxMK) Stefen writes in (http://slexy.org/view/s2YlVuhhUa) Sichendra writes in (http://slexy.org/view/s2P7KtE5x2) ***
In Folge 59 versuchen wir, die für einen optimale Linuxdistribution zu finden. Roman vom Deimhart Podcast hat dies zusammen mit Dirk bereits getan und erzählt, uns, welche Kriterien er beachtet hat und was es am Schluss geworden ist. Dirk konnte krankheitshalber leider nicht an der Sendung teilnehmen. Trackliste Metal – JT in Space Butterfly Tea – Dragontales Nächste Sendung am Samstag, 1. September 2012, 19:00 Uhr! Deimhart :: Der Deimhart Podcast Podcast Teil 1 :: Eine Linuxdistribution für Roman Podcast Teil 2 :: Erster Zwischenstand der Distributionssuche Podcast Teil 3 :: Deimhart Shortcast über Zorin OS Podcast Teil 4 :: Rückmeldungen zur Suche aus der Community Podcast Teil 5 :: Die Suche geht weiter Podcast Teil 6 :: Nochmal ein kurzer Zwischenbericht zur Suche Podcast Teil 7 :: Das Ende der Distributionssuche Distrowatch :: Die Hitparade der Linuxdistributionen Linuxcounter :: The New Linux Counter Project File Download (58:28 min / 102 MB)
In Folge 59 versuchen wir, die für einen optimale Linuxdistribution zu finden. Roman vom Deimhart Podcast hat dies zusammen mit Dirk bereits getan und erzählt, uns, welche Kriterien er beachtet hat und was es am Schluss geworden ist. Dirk konnte krankheitshalber leider nicht an der Sendung teilnehmen. Trackliste Metal – JT in Space Butterfly Tea – Dragontales Nächste Sendung am Samstag, 1. September 2012, 19:00 Uhr! Deimhart :: Der Deimhart Podcast Podcast Teil 1 :: Eine Linuxdistribution für Roman Podcast Teil 2 :: Erster Zwischenstand der Distributionssuche Podcast Teil 3 :: Deimhart Shortcast über Zorin OS Podcast Teil 4 :: Rückmeldungen zur Suche aus der Community Podcast Teil 5 :: Die Suche geht weiter Podcast Teil 6 :: Nochmal ein kurzer Zwischenbericht zur Suche Podcast Teil 7 :: Das Ende der Distributionssuche Distrowatch :: Die Hitparade der Linuxdistributionen Linuxcounter :: The New Linux Counter Project File Download (58:28 min / 102 MB)
In this episode: over 100 pins on the LR Frappr map; international Linux adoption; listener feedback; my two favorite beers; version numbering as it applies to the Linux kernel and Linux distributions; how the movie Toy Story is relevant to the Debian GNU/Linux distribution; Ubuntu naming and numbering conventions.
In this episode: the Linux Reality Frappr map; site forums; listener feedback; a return trip to Distrowatch for an overview of various Linux distributions, including Ubuntu, SUSE, Mandriva, MEPIS, Debian, Kubuntu, KNOPPIX, and PCLinuxOS; a brief discussion of Linux desktop environments, including KDE and GNOME.
In this episode: listener feedback; a review of Linux news sites, including Distrowatch, Desktoplinux.com, LXer, and LWN.net; places to look for assistance with Linux, including Google’s customized Linux search page, the LinuxQuestions.org community forum, and TUX Magazine; other Linux podcasts, such as the Linux Link Tech Show, LugRadio, and JaK Attack.
© 2020-2025 Ivy Podcast Discovery LLC
