Podcasts about LXDE

Coming up in this episode * Themes Are More Global Than You Think * Kdenlive Does Some Layering * The History of LXDE * To Qt, or not to Qt? * Then, we call an audible 0:00 Cold Open 2:17 Theme of the Crop 16:22 The Lost Edit 28:11 The History of LXDE 55:51 How'd LXQt and LXDE Go? 1:24:28 Next Time 1:31:13 Stinger The Video Version https://youtu.be/Y8_rMTmnIXc

We review some of the most popular Linux desktop environment options. Included are KDE Plasma, Gnome, Cinnamon, MATE, XFCE, LXDE, Budgie, Pantheon and Deepin. Episode Time Stamps 00:00 Going Linux #444 · Welcome to Linux! - Desktops 01:18 Bill broke KDE on his computer 02:08 Larry fixed a 13 year old laptop with LXLE 09:29 Definition: Linux desktop environments 14:50 The Linux Experiment's DE review video 17:24 The KDE Plasma desktop 21:47 Unity and the Gnome desktop 26:03 The Cinnamon desktop 27:48 The MATE Desktop 32:09 The XFCE desktop 34:25 The LXDE desktop 37:23 The Budgie desktop 40:43 The Pantheon desktop 44:17 The Deepin desktop 45:49 The most modern desktop environment 50:20 The choice is yours 51:53 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 53:13 End

This week, Linux Out Loud chats about open source projects rising from the ashes. Welcome to episode 49 of Linux Out Loud. We fired up our mics, connected those headphones as we searched the community for themes to expound upon. We kept the banter friendly, the conversation somewhat on topic, and had fun doing it. 00:00:00 Introduction 00:01:25 2K Webcam 00:06:20 State Prep 00:13:60 LXDE on TheC64 00:21:54 From the Ashes 00:40:19 Game of the Week 00:45:36 3D Printer Upgrades 00:56:20 SteamDeck Screen 00:59:39 Close Find the rest of the show notes at https://tuxdigital.com/podcasts/linux-out-loud/lol-49/ Our sponsor: - Linode - http://linode.com/tux - Bitwarden - http://bitwarden.com/tux Contact info Matt (Twitter @MattTDN (https://twitter.com/MattTDN)) Wendy (Mastodon @WendyDLN (https://mastodon.online/@WendyDLN)) Nate (Website CubicleNate.com (https://cubiclenate.com/))

Empecé a usar Linux en el año 2005 con Ubuntu. Desde entonces he probado diferentes ditribuciones como Manjaro, Elementary, Lubuntu, Linux Mint, etc, pero nunca me había decidido a instalar y probar en serio Fedora. Paralelamente y respecto a entornos de escritorio siempre me he movido entre XFCE, LXDE, Gnome 2 y Cinnamon pero nunca me había dado por probar KDE Plasma. Por requerimientos laborales me he visto trabajando con máquinas con este entorno y he decidido ya de una ponerme en serio a probarlo, y que mejor que fusionar las dos cosas, así que ya llevo unos días usando únicamente Fedora 36 KDE Plasma y sólo puedo decir que me está encantado. A título personal he ido dejando por escrito aquello que he tenido que instalar a lo largo del proceso y he redactado unas notas a modo de recordatorio y material de consulta que también os comparto aquí: Notas para después de instalar Fedora 36 KDE Plasma, para que podáis consultar si es de vuestro agrado.

Coming up in this episode 1. The origins of the shirts 2. Ubuntu's history 3. And some thoughts on 22.04 Video version https://youtu.be/PCM-h_0Rqbc Support us on Patreon (https://patreon.com/linuxuserspace)! Audio Timestamps 0:00 Cold Open 1:30 The Origin of the Shirts 6:43 Lubuntu's in the Backporting Biz 9:45 Ubuntu's History 11:30 2004 17:01 2005 20:11 2006 24:01 2007 29:55 2008 36:39 2009 40:16 2010 47:52 2011 55:05 2012 1:02:35 2013 1:10:03 2014 1:15:00 2015 1:20:19 2016 1:25:26 2017 1:28:49 2018 1:31:17 2019 1:33:49 2020 1:35:55 2021 1:37:19 2022 1:39:43 A Couple Thoughts on Ubuntu 1:48:13 A New Distro, and a Thanks! 1:50:26 Stinger Banter Dan's Shirt (https://southeastlinuxfest.org) Leo's Shirt (https://ubuntu.com/blog/build-a-raspberry-pi-desktop-with-an-ubuntu-heart) Lubuntu Backports are coming! (https://lubuntu.me/jammy-backports-22-04-1-cft/) Announcements Give us a sub on YouTube (https://linuxuserspace.show/youtube) You can watch us live on Twitch (https://linuxuserspace.show/twitch) the day after an episode drops.(not this episode but normally.) Want to have a topic covered or have some feedback? - send us an email, contact@linuxuserspace.show Ubuntu The Saga Some fast links: Main Web Page (https://ubuntu.com) Ubuntu Forums (https://ubuntuforums.org) AskUbuntu (https://askubuntu.com) Ubuntu Discourse (https://discourse.ubuntu.com) Launchpad (https://launchpad.net) Official Flavours (https://ubuntu.com/desktop/flavours) Wiki (https://wiki.ubuntu.com) There are way too many links to get them all! We gathered a great deal from the official Ubuntu Blog (https://ubuntu.com/blog/) The Inception (https://www.informit.com/articles/article.aspx?p=1186095&seqNum=3) Bug #1 (https://bugs.launchpad.net/ubuntu/+bug/1) October 20, 2004 Warty Warthog 4.10 was the first release. Shipit came about the same time (https://web.archive.org/web/20041210114946/http://shipit.ubuntu.com/) Hoary Hedgehog, 5.04, is released (https://ubuntu.com/blog/ubuntu-5-04-released) adding KDE and the Kubuntu flavor. Ubuntu Foundation is Created (https://ubuntu.com/blog/new-ubuntu-foundation-announced) Warty's 18 months are up (https://ubuntu.com/blog/ubuntu-4-10-end-of-support-cycle) Dapper Drake, 6.06, is released (https://ubuntu.com/blog/ubuntu-6-06-lts-released). To date the only release that was late. Also, Xubuntu joined the family with the Xfce desktop. Scott James Remnant dubbed it the Late To Ship release (https://netsplit.com/posts/happy-10th-birthday-ubuntu/) Edgy Eft, 6.10 is released (https://ubuntu.com/blog/canonical-launches-new-ubuntu-release-for-desktops-and-servers), now with more Upstart (https://upstart.ubuntu.com/) Launch Pad 1.0 Beta released (https://ubuntu.com/blog/launchpad-1-0-beta-released) Dell offers Ubuntu 7.04 (https://ubuntu.com/blog/dell-to-offer-ubuntu) on select devices in the US (https://web.archive.org/web/20070503024310/http://direct2dell.com/one2one/archive/2007/05/01/13147.aspx) first release of Ubuntu Studio (https://launchpad.net/ubuntustudio/+milestone/feisty-7.04-release) Gutsy Gibbon, 7.10 Desktop, is released (https://ubuntu.com/blog/ubuntu-7-10-desktop-edition-released). Mythubuntu and Gobuntu appear here. Launchpad is released (https://ubuntu.com/blog/canonical-announces-launch-of-launchpad-personal-package-archive-service-for-developers) System76 joined the fray (https://ubuntu.com/blog/system76-announces-servers-with-ubuntu-7-10-and-canonical-support-services) Landscape, system management and monitoring tools for Ubuntu, launches (https://ubuntu.com/blog/canonical-announces-general-availability-of-systems-management-and-monitoring-tool-landscape-launches-with-free-trial) Hardy Heron, 8.04 LTS, released for Desktop (https://ubuntu.com/blog/ubuntu-8-04-lts-desktop-edition-released). Wubi is also released. Gobuntu has been made redundant (https://web.archive.org/web/20110929075747/https://lists.ubuntu.com/archives/gobuntu-devel/2008-June/000795.html) Launchpad 2.0 released (https://news.softpedia.com/news/Canonical-Presents-Launchpad-2-0-91019.shtml) Canonical open sources Launchpad (https://ubuntu.com/blog/canonical-releases-source-code-for-launchpad) Karmic Koala, 9.10 (https://wiki.ubuntu.com/KarmicKoala/HumanReleaseNotes), is relased and so is Ubuntu One (https://launchpad.net/ubuntuone/) Lucid Lynx, 10.04, released (https://ubuntu.com/blog/reasons-to-celebrate-29th-april-2010) and the first hints of Lubuntu, though not official yet. Unity announced (https://www.markshuttleworth.com/archives/383) Ubuntu and Canonical sites get a facelift (https://ubuntu.com/blog/new-ubuntu-and-canonical-sites). See it here (https://web.archive.org/web/20100601092326/http://www.ubuntu.com/) Canonical announces Ubuntu Advantage (https://ubuntu.com/blog/new-canonical-services-help-businesses-get-ahead-with-ubuntu-server-and-ubuntu-desktop) Unity shows lots of improvement (https://ubuntu.com/blog/introduction-to-unity-launcher), but it's NOT A DOCK! (See it in action) (https://vimeo.com/12818039) Quitter talk - Blog post (https://ubuntu.com/blog/quit) Shipit comes to an end (https://ubuntu.com/blog/shipit-comes-to-an-end) Oneiric Ocelot, 11.10, is released. (https://wiki.ubuntu.com/OneiricOcelot/ReleaseNotes?action=show&redirect=OneiricOcelot%2FTechnicalOverview) and Lubuntu becomes official. The HUD is introduced. (https://www.markshuttleworth.com/archives/939) Precise Pangolin, 12.04, is released. (https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuDesktop/UbuntuDesktop-12.04) Includes the Heads Up Display (https://web.archive.org/web/20120125082058/https://people.canonical.com/~ories/HUD.m4v) Favorable reviews of Ubuntu as a whole, but also Unity (https://www.techrepublic.com/article/ubuntu-unity-making-the-desktop-seriously-efficient-again/) The traditional installer/live CD is dead (https://www.omgubuntu.co.uk/2012/09/its-official-the-ubuntu-livecd-is-dead). Ubuntu comes to the phone (https://ubuntu.com/blog/ubuntu-comes-to-the-phone-with-a-beautifully-distilled-interface-and-a-unique-full-pc-capability-when-docked) Raring Ringtail, 13.04, is released. (https://wiki.ubuntu.com/RaringRingtail/ReleaseNotes) focus on mobile (https://www.markshuttleworth.com/archives/1195) ahead of the 14.04 release Wubi has unresolved bugs (https://lists.ubuntu.com/archives/ubuntu-devel/2013-April/036993.html) Ubuntu Kylin was born Ubuntu Edge Announced. (https://ubuntu.com/blog/ubuntu-edge) Edge fails (https://ubuntu.com/blog/ubuntu-edge-thank-you) to meet its goal (https://www.indiegogo.com/projects/ubuntu-edge#/) Ubuntu Kylin hits 1.3m downloads (https://ubuntu.com/blog/ubuntu-kylin-booms-in-china-with-over-1300000-downloads-in-less-than) Ubuntu One's file services are being shut down (https://ubuntu.com/blog/shutting-down-ubuntu-one-file-services) Ubuntu Mate Remix is announced (https://ubuntu-mate.org/blog/ubuntu-mate-remix-inception/) Mark Shuttleworth announces "Snappy Ubuntu" (https://www.youtube.com/watch?v=BlcTDz9ogug) The BQ Aquaris E4.5 Ubuntu edition is available (https://ubuntu.com/blog/bqs-new-aquaris-e4-5-ubuntu-edition-the-smartphone-that-puts-content-and-services-at-your-fingertips) "Snappy Ubuntu Core" on Raspberry Pi 2 (https://ubuntu.com/blog/snappy-ubuntu-core-on-raspberry-pi-2) Vivid Vervet 15.04, is released. (https://wiki.ubuntu.com/VividVervet/ReleaseNotes) Ubuntu MATE, nearly called Mubuntu (https://ubuntu-mate.community/t/why-not-mubuntu/7279/5), gets its first "official flavor" release Snapcraft is announced and Snappy Apps are being called Snaps now (https://ubuntu.com/blog/java-on-snappy) ZFS is coming to Ubuntu (https://ubuntu.com/blog/zfs-licensing-and-linux) Acknowledgement (https://ubuntu.com/blog/ubuntu-app-developer-blog-announcing-new-snap-desktop-launchers) that Snaps don't quite look right a lot of times. Mark Shuttleworth announces that Ubuntu's Unity experiement has failed (https://ubuntu.com/blog/growing-ubuntu-for-cloud-and-iot-rather-than-phone-and-convergence) and Gnome, not Unity8 will be the default session in Ubuntu 18.04. This also marks the end of Ubuntu Phone. The next day, however, Marius Gripsgard of UBPorts stepped up to take the reins. (https://fossbytes.com/unity-8-ubuntu-touch-ubports/) Zesty Zappus, 17.04, is released. (https://wiki.ubuntu.com/ZestyZapus/ReleaseNotes) and with it Ubuntu Budgie becomes an official flavor. Ubuntu 16.04 shows up in the Windows Store (https://ubuntu.com/blog/windows-10-loves-ubuntu-loveislove), for the Windows Subsystem for Linux. Canonical joins (https://ubuntu.com/blog/canonical-joins-gnome-foundation-advisory-board) the Gnome Foundation Advisory Board ahead of the 18.04 release. Bionic Beaver, 18.04, is released. (https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes) and Gnome is the default DE again. Bryan Quigley, looks to drop 32-bit hardware support (https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2018-May/018004.html) Cosmic Cuttlefish, 18.10, is released. (https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes) 32-bit support is now in consideration to be removed, so upgrades from 18.04 are forbidden on 32-bit installs. Lubuntu Switches to LXQt from LXDE (https://lubuntu.me/cosmic-released/) Mir 1.0 is released (https://ubuntu.com/blog/iot-graphics-mir-release-1-0) Disco Dingo, 19.04, is released. (https://wiki.ubuntu.com/DiscoDingo/ReleaseNotes) No more 32bit isos, long live 32bit. Ubuntu for WSL2 (https://ubuntu.com/blog/canonical-announces-support-for-ubuntu-on-windows-subsystem-for-linux-2) i386 architecture, or rather 32-bit support, will be dropped (https://web.archive.org/web/20190625190907/https://lists.ubuntu.com/archives/ubuntu-devel-announce/2019-June/001261.html) i386 architecture will not be dropped (https://ubuntu.com/blog/statement-on-32-bit-i386-packages-for-ubuntu-19-10-and-20-04-lts) Eoan Ermine 19.10, is released. (https://wiki.ubuntu.com/EoanErmine/ReleaseNotes) Experimental ZFS support on installation is available Chromium is snap-only (https://ubuntu.com/blog/chromium-in-ubuntu-deb-to-snap-transition) Rocco Interviews Mark Shuttleworth on Linux Spotlight (https://youtu.be/UDHL3youjIY) Ubuntu in Pop Culture (https://ubuntu.com/blog/2004-to-20-04-lts-ubuntu-in-popular-culture) Focal Fossa, 20.04, is released. (https://wiki.ubuntu.com/FocalFossa/ReleaseNotes) Hardware enablement is on by default on the desktop. The Snap Store tags in for Ubuntu Software Groovy Gorilla 20.10, is released. (https://wiki.ubuntu.com/GroovyGorilla/ReleaseNotes) Active Directory support gets added to the installer (https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-20.10-Active-Directory) Snaps get faster (https://forum.snapcraft.io/t/how-to-switch-your-snap-to-use-lzo-compression/21714) Another lurch forward for snap theming. (https://ubuntu.com/blog/snaps-and-themes-on-the-path-to-seamless-desktop-integration) The Ubuntu installer is being rewritten (https://discourse.ubuntu.com/t/refreshing-the-ubuntu-desktop-installer/20659) in Flutter. Impish Indri, 21.10, is released. (https://wiki.ubuntu.com/ImpishIndri/ReleaseNotes) Firefox follows Chromium and switches from a deb to a snap (https://discourse.ubuntu.com/t/feature-freeze-exception-seeding-the-official-firefox-snap-in-ubuntu-desktop/24210) - Only for main Ubuntu, not the flavors... yet. Ubuntu gets their shiny new logo (https://ubuntu.com/blog/a-new-look-for-the-circle-of-friends) Jammy Jellyfish, 22.04, is released. (https://wiki.ubuntu.com/JammyJellyfish/ReleaseNotes) Better Active Directory integration (https://ubuntu.com/blog/new-active-directory-integration-features-in-ubuntu-22-04-part-1) Flavors follow main Ubuntu and switch to the snap of Firefox. A big push to improve Firefox snap performance (https://ubuntu.com/blog/how-are-we-improving-firefox-snap-performance-part-1) The push to improve Firefox continues (https://ubuntu.com/blog/canonical-ubuntu-core-22-is-now-available-optimised-for-iot-and-embedded-devices) Housekeeping Catch these and other great topics as they unfold on our Subreddit or our News channel on Discord. * Linux User Space subreddit (https://linuxuserspace.show/reddit) * Linux User Space Discord Server (https://linuxuserspace.show/discord) * Linux User Space Telegram (https://linuxuserspace.show/telegram) * Linux User Space Matrix (https://linuxuserspace.show/matrix) Next Time Our next show will be a topic show. Our next distro is Endeavour OS (https://endeavouros.com) Come back in two weeks for more Linux User Space Stay tuned and interact with us on Twitter, Mastodon, Telegram, Matrix, Discord whatever. Give us your suggestions on our subreddit r/LinuxUserSpace Join the conversation. Talk to us, and give us more ideas. All the links in the show notes and on linuxuserspace.show. We would like to acknowledge our top patrons. Thank you for your support! Producer Bruno John Josh Co-Producer Johnny Contributor Advait CubicleNate Eduardo Jill and Steve LiNuXsys666 Nicholas Paul sleepyeyesvince

Romans 14:9-18 Matthew 12:14-16, 22-30

Gnome ou LXDE, eis a questão... Ansible ou Terraform, eis a questão...

We all take it for granted, but it is one of the best things about Linux. We share the history of the live CD, how it all got started, and the times it saved our bacon.

A desktop from Linux past has a surprising update this week, AlmaLinux pulls ahead of the pack, and Canonical ships software for the Apple M1. Plus, the new tech in SteamOS 3 that might make it a great desktop OS.

A desktop from Linux past has a surprising update this week, AlmaLinux pulls ahead of the pack, and Canonical ships software for the Apple M1. Plus, the new tech in SteamOS 3 that might make it a great desktop OS.

A desktop from Linux past has a surprising update this week, AlmaLinux pulls ahead of the pack, and Canonical ships software for the Apple M1. Plus, the new tech in SteamOS 3 that might make it a great desktop OS.

Hola a todos y a todas nuestros linuxeros, el día de hoy estaremos hablando de la continuación de escritorios Linux, en donde en esta ocasión hablaremos de 3 desktops muy conocidos por la comunidad GNU/LINUX. 1. GNOME: https://www.gnome.org/ 2. LXDE: https://www.lxde.org/ 3. CINNAMON: https://blog.linuxmint.com/?p=4011 Recuerda que estaremos realizando instalación en el canal de twitch, distribuciones que tengan por defecto estos escritorios Linux, además cabe aclarar que este podcast es meramente informativo y que la instalación de cada desktop dependerá de la maquina que poseas en el momento de su implementación.

On this episode of This Week in Linux, System76 made some waves when they announced their new COSMIC Desktop Environment. Slackware is back with a vengence ok not really with a vengence but Slackware did announce the Be..00ta version of Slackware 15.0. In addition to Slackware, we've also got some other great topics in Distro News this week with Manjaro 21.0, Zorin OS 16 Beta and we're even going to take a look at the latest release of FreeBSD. We've got some more Desktop Environment news with the release of LXQt 0.17 and JDE 2.0. Mailspring Email Client is back in the news with release 1.9 and we're continue the much beloved Legal News section with Xinuos Sueing IBM & Red Hat. All that and much more on Your Weekly Source for Linux GNews! SPONSORED BY: Digital Ocean ►► https://do.co/dln Bitwarden ►► https://bitwarden.com/dln TWITTER ►► https://twitter.com/michaeltunnell MASTODON ►► https://mastodon.social/@MichaelTunnell DLN COMMUNITY ►► https://destinationlinux.network/contact FRONT PAGE LINUX ►► https://frontpagelinux.com MERCH ►► https://dlnstore.com BECOME A PATRON ►► https://tuxdigital.com/contribute This Week in Linux is produced by the Destination Linux Network: https://destinationlinux.network SHOW NOTES ►► https://tuxdigital.com/twil147 00:00 = Welcome to TWIL 147 01:26 = System76's COSMIC Desktop Environment 07:25 = Slackware 15.0 Beta Released 11:03 = LXQt 0.17 Released 13:19 = Digital Ocean: VPS / App Platform ( https://do.co/dln ) 14:48 = Manjaro 21.0 Released 19:31 = Zorin OS 16 Beta Released 24:30 = Mailspring 1.9 Email Client Released 29:08 = Bitwarden Password Manager ( https://bitwarden.com/dln ) 31:48 = JDE 2.0 Desktop Released 33:53 = FreeBSD 13.0 Released 35:44 = Xinuos Sues IBM (SCO Case Related?) 43:58 = LLVM 12.0 Released 45:43 = Humble Bundles: Learn Python & More 47:29 = Outro Other Videos: 7 Reasons Why Firefox Is My Favorite Web Browser: https://youtu.be/bGTBH9yr8uw How To Use Firefox's Best Feature, Multi-Account Containers: https://youtu.be/FfN5L5zAJUo 5 Reasons Why I Use KDE Plasma: https://youtu.be/b0KA6IsO1M8 6 Cool Things You Didn't Know About Linux's History: https://youtu.be/u9ZY41mNB9I Thanks For Watching! Linux #TechNews #Podcast

Coming up in this episode 1. We mix up Debs and RPMs 2. We sip on a La Croix 3. Trim the hedges 4. And we reveal the next distro – WHICH IS… PCLinuxOS PCLinuxOS (https://www.pclinuxos.com/) PCLinuxOS Roots (https://en.wikipedia.org/wiki/PCLinuxOS) TDE, the Trinity Desktop Environment was coming to PCLinuxOS (https://trinity.mypclinuxos.com/About.php) Gnome3? (https://pclosmag.com/html/Issues/201111/page02.html) "distro hopper stopper" (https://www.dedoimedo.com/computers/pclinuxos-2009.html) TDE info (https://en.wikipedia.org/wiki/Trinity_Desktop_Environment) PCLinuxOS Forum (http://pclinuxos.com/forum/) PCLinuxOS Magazine (https://pclosmag.com/index.html) Basic Distro Details Name - PCLinuxOS Base System - PCLinuxOS Desktop Environment - Plasma, MATE, XFCE, Trinity, LXDE, OpenBox File Manager - **** Package Manager - Synaptic Kernel - *Rolling * Display Manager - DE X11 no Wayland - Housekeeping Email us (mailto:contact@linuxuserspace.show) learnlinux.tv (https://learnlinux.tv) Support us at Patreon (https://patreon.com/linuxuserspace), now with new tiers. Join us on Telegram (https://linuxuserspace.show/telegram) New Discord Server (https://discord.gg/qXKxHcV) Follow us on twitter (https://twitter.com/LinuxUserSpace) Check out Linux User Space (https://linuxuserspace.show) on the web App Focus HedgeDoc/CodiMD This episode's app: HedgeDoc (https://hedgedoc.org) Name/Fork History (https://hedgedoc.org/history/) "Multiplayer text editor" - Leo Chavez 2021 Next Time We discuss topics and Feedback that impact your User Space Our next distro is Nitrux (https://nxos.org) Join us in two weeks when we return to the Linux User Space

Coming up in this episode we cover 1. openSUSE Tumbleweed 2. App Focus - Audacity Welcome to the Linux User Space openSUSE Tumbleweed openSUSE (https://www.opensuse.org) openSUSE Tumbleweed (https://en.opensuse.org/Portal:Tumbleweed) SuSE's Roots (https://en.wikipedia.org/wiki/SUSE) SLS - Soft Landing Linux (https://en.wikipedia.org/wiki/Softlanding_Linux_System) Slackware (https://en.wikipedia.org/wiki/Slackware) jurix (https://en.wikipedia.org/wiki/Jurix) Super secret 4.2 .42 question.... (https://en.wikipedia.org/wiki/Phrases_from_The_Hitchhiker%27s_Guide_to_the_Galaxy#42) YsST (https://yast.opensuse.org) OBS - Open Build Service (https://openbuildservice.org) openQA (https://open.qa) Basic Distro Details Name - openSUSE Base System - Factory - developement codebase 2 options Leap - Yearly release cadence Tumbleweed - Rolling Desktop Environment - KDE since the beginning, GNOME, XFCE, LXDE, LXQt, Enlightenment, Cinnamon, Mate, Pantheon File Manager - Based on DE you choose Package Manager - Libzypp which provides Zypper on command line and YaST as a GUI and uses the RPM package format User Interface - DE Based System & Service Manager - systemd Kernel - ** 5.8.10 ** Leap is 5.3 at release July Display Manager - GDM, SDDM, LightDM, you can swap them around if you like Window Manager - Xorg is there as well as Wayland Housekeeping Email us (mailto:contact@linuxuserspace.show) Tabs, Not Spaces (https://tabsnotspaces.com/) Support us at Patreon (https://patreon.com/linuxuserspace) Join us on Telegram (https://linuxuserspace.show/telegram) Follow us on twitter (https://twitter.com/LinuxUserSpace) Check out Linux User Space (https://linuxuserspace.show) on the web App Focus Audacity This episode's app: Audacity (https://www.audacityteam.org) Audacity plugins (https://www.audacityteam.org/download/plug-ins/) Next Time Next episode we discuss topics impacting your user space October's distro of the month is Deepin (https://www.deepin.org/en/) Join us in two weeks when we return to the Linux User Space

Coming up in this episode we cover 1. Manjaro 2. the good the bad and the ugly 3. and Leo brings us an app that you will just love, if you lived in the 90's Welcome to the Linux User Space Manjaro Manjaro web page (https://manjaro.org/) Manjaro wikipedia page (https://en.wikipedia.org/wiki/Manjaro) Manjaro Arm (https://manjaro.org/download/#ARM) Roland Singer, Philip Muller & Guillaume Benoit co-founders (https://manjaro.org/team/) Phillip Muller Announcment for first alpha (https://distrowatch.com/?newsid=07402) Announcement, Manjaro no longer just a distro, but now company (https://archived.forum.manjaro.org/t/manjaro-is-taking-the-next-step/102105) Forbes article - company announcement (https://www.forbes.com/sites/jasonevangelho/2019/09/08/manjaro-linux-just-made-a-massive-announcement-about-its-future/#3efcb0f836f9) Announcing the switch to Free Office vs Libre Office by default (https://archived.forum.manjaro.org/t/testing-update-2019-07-29-kernels-xfce-4-14-pre3-haskell/96690) Forbes article - office switch (https://www.forbes.com/sites/jasonevangelho/2019/08/03/manjaro-linux-team-responds-to-libreoffice-versus-freeoffice-in-upcoming-version-18-1/#477bfe5fbf46) Archived forum (https://archived.forum.manjaro.org/) New forum (https://forum.manjaro.org/) Change in manjaro team composition (https://archived.forum.manjaro.org/t/change-in-manjaro-team-composition/155231) Change of treasurer for Manjaro community funds (https://archived.forum.manjaro.org/t/change-of-treasurer-for-manjaro-community-funds/154888) Basic Distro Details Base System - ARCH 3 repositories to choose from Unstable - Bleeding Edge ~ roughly 3 days behind ARCH Testing - Gone through initial test phase from unstable Stable - only packages deemed stable by dev team, which means generally 1-3 weeks of lag between ARCH and release. Desktop Environment - A beautiful XFCE, where they unapologetically focus their attention, and it shows. GNOME, KDE Spins Awesome, Bspwm, Budgie, Cinnamon, I3, LXDE, LXQt, Mate, and Openbox** File Manager - Based on DE you choose Package Manager - Pacman on Command Line and Pamac GTK & QT for a GUI interface User Interface - DE Based System & Service Manager - systemd Display Manager - GDM, SDDM, LightDM, you can swap them around if you like Window Manager - Xorg is there as well as Wayland if you aren't on Nvidia, still not stable yet Housekeeping Email us (mailto:contact@linuxuserspace.show) Late Night Linux (https://latenightlinux.com/) Support us at patreon.com/linuxuserspace Join us on Telegram (https://linuxuserspace.show/telegram) Follow us on twitter (https://twitter.com/LinuxUserSpace) Check out Linux User Space (https://linuxuserspace.show) on the web App Focus Rofi This episode's app: Rofi (https://github.com/davatorium/rofi) Next episode we discuss topics impacting your user space September's distro of the month is openSUSE tumbleweed (https://www.opensuse.org/) Join us in two weeks when we return to the Linux User Space

Coming up in this episode we cover 1. We Network with Joe 2. Dive into Fedora 32 3. Listener feedback 4. App Focus on Bitwarden Welcome to the Linux User Space Fedora 32 Fedora (https://en.wikipedia.org/wiki/The_Fedora_Project) Warren Togami (https://fedoraproject.org/wiki/User:Wtogami?rd=WarrenTogami) Gnome Desktop (https://en.wikipedia.org/wiki/GNOME#GNOME_3) KDE Plasma 5 Desktop (https://en.wikipedia.org/wiki/KDE_Plasma_5) Heisenbug (https://en.wikipedia.org/wiki/Heisenbug) Matthew Miller arsTECHNICA Interview (https://arstechnica.com/gadgets/2020/05/linux-distro-review-fedora-workstation-32/) Basic Distro Details Base System - Fedora Desktop Environment(s) - (Official) GNOME, (Spins) KDE Plasma, LXQT, LXDE, Cinnamon, MATE, XFCE, SOAS Labs (https://labs.fedoraproject.org/) - Astronomy, Comp Neuro, Design Suite, Games, Jam, Python, Security Labs, Robotics File Manager - Based on DE you choose Package Manager - RPM package manager w/ DNF as the dependency resolver User Interface - GTK 3, Qt System & Service Manager - systemd Software Manager, DNFDragora, Discover Display Manager - GDM, SDDM, LightDM Window Manager - Wayland by default since Fedora 27, Xorg is there too Release Notes Fedora 32 (https://docs.fedoraproject.org/en-US/fedora/f32/release-notes/) Fedora Magazine (https://fedoramagazine.org/) RPM Fusion (https://rpmfusion.org/) Housekeeping Email us (mailto:contact@linuxuserspace.show) Command Line Heros (https://www.redhat.com/en/command-line-heroes) Support us at patreon.com/linuxuserspace Join us on Telegram (https://linuxuserspace.show/telegram) Follow us on twitter (https://twitter.com/LinuxUserSpace) Check out Linux User Space (https://linuxuserspace.show) on the web App Focus Bitwarden This episode's app: Bitwarden (https://bitwarden.com/) Join us in two weeks when we return to the Linux User Space

Ubuntu releases 20.04 LTS, Kdenlive picks up support for the OpenTimelineIO interchange format, Mozilla expands its community analysis program with a new blog, Lenovo and Fedora announce a partnership for pre-installation on some ThinkPads, and Intel gives a boost to The Linux Foundation's mentorship program.

This episode I talk about gender identity, sexuality, politics, LXDE vs LXQT, Copyright issues in YouTube, and play music by Emorej and Bells!

FreeBSD Q4 2018 status report, the GhostBSD alternative, the coolest 90s laptop, OpenSSH 8.0 with quantum computing resistant keys exchange, project trident: 18.12-U8 is here, and more. ##Headlines ###AsiaBSDcon 2019 recap Both Allan and I attended AsiaBSDcon 2019 in Tokyo in mid march. After a couple of days of Tokyo sightseeing and tasting the local food, the conference started with tutorials. Benedict gave his tutorial about “BSD-based Systems Monitoring with Icinga2 and OpenSSH”, while Allan ran the FreeBSD developer summit. On the next day, Benedict attended the tutorial “writing (network) tests for FreeBSD” held by Kristof Provost. I learned a lot about Kyua, where tests live and how they are executed. I took some notes, which will likely become an article or chapter in the developers handbook about writing tests. On the third day, Hiroki Sato officially opened the paper session and then people went into individual talks. Benedict attended Adventure in DRMland - Or how to write a FreeBSD ARM64 DRM driver by Emmanuel Vadot powerpc64 architecture support in FreeBSD ports by Piotr Kubaj Managing System Images with ZFS by Allan Jude FreeBSD - Improving block I/O compatibility in bhyve by Sergiu Weisz Security Fantasies and Realities for the BSDs by George V. Neville-Neil ZRouter: Remote update of firmware by Hiroki Mori Improving security of the FreeBSD boot process by Marcin Wojtas Allan attended Adventures in DRMland by Emmanuel Vadot Intel HAXM by Kamil Rytarowski BSD Solutions in Australian NGOs Container Migration on FreeBSD by Yuhei Takagawa Security Fantasies and Realities for the BSDs by George Neville-Neil ZRouter: Remote update of firmware by Hiroki Mori Improving security of the FreeBSD boot process by Marcin Wojtas When not in talks, time was spent in the hallway track and conversations would often continue over dinner. Stay tuned for announcements about where AsiaBSDcon 2020 will be, as the Tokyo Olympics will likely force some changes for next year. Overall, it was nice to see people at the conference again, listen to talks, and enjoy the hospitality of Japan. ###FreeBSD Quarterly Status Report - Fourth Quarter 2018 Since we are still on this island among many in this vast ocean of the Internet, we write this message in a bottle to inform you of the work we have finished and what lies ahead of us. These deeds that we have wrought with our minds and hands, they are for all to partake of - in the hopes that anyone of their free will, will join us in making improvements. In todays message the following by no means complete or ordered set of improvements and additions will be covered: i386 PAE Pagetables for up to 24GB memory support, Continuous Integration efforts, driver updates to ENA and graphics, ARM enhancements such as RochChip, Marvell 8K, and Broadcom support as well as more DTS files, more Capsicum possibilities, as well as pfsync improvements, and many more things that you can read about for yourselves. Additionally, we bring news from some islands further down stream, namely the nosh project, HardenedBSD, ClonOS, and the Polish BSD User-Group. We would, selfishly, encourage those of you who give us the good word to please send in your submissions sooner than just before the deadline, and also encourage anyone willing to share the good word to please read the section on which submissions we’re also interested in having. ###GhostBSD: A Solid Linux-Like Open Source Alternative The subject of this week’s Linux Picks and Pans is a representative of a less well-known computing platform that coexists with Linux as an open source operating system. If you thought that the Linux kernel was the only open source engine for a free OS, think again. BSD (Berkeley Software Distribution) shares many of the same features that make Linux OSes viable alternatives to proprietary computing platforms. GhostBSD is a user-friendly Linux-like desktop operating system based on TrueOS. TrueOS is, in turn, based on FreeBSD’s development branch. TrueOS’ goal is to combine the stability and security of FreeBSD with a preinstalled GNOME, MATE, Xfce, LXDE or Openbox graphical user interface. I stumbled on TrueOS while checking out new desktop environments and features in recent new releases of a few obscure Linux distros. Along the way, I discovered that today’s BSD computing family is not the closed source Unix platform the “BSD” name might suggest. In last week’s Redcore Linux review, I mentioned that the Lumina desktop environment was under development for an upcoming Redcore Linux release. Lumina is being developed primarily for BSD OSes. That led me to circle back to a review I wrote two years ago on Lumina being developed for Linux. GhostBSD is a pleasant discovery. It has nothing to do with being spooky, either. That goes for both the distro and the open source computing family it exposes. Keep reading to find out what piqued my excitement about Linux-like GhostBSD. ##News Roundup SPARCbook 3000ST - The coolest 90s laptop A few weeks back I managed to pick up an incredibly rare laptop in immaculate condition for $50 on Kijiji: a Tadpole Technologies SPARCbook 3000ST from 1997 (it also came with two other working Pentium laptops from the 1990s). Sun computers were an expensive desire for many computer geeks in the 1990s, and running UNIX on a SPARC-based laptop was, well, just as cool as it gets. SPARC was an open hardware platform that anyone could make, and Tadpole licensed the Solaris UNIX operating system from Sun for their SPARCbooks. Tadpole essentially made high-end UNIX/VAX workstations on costly, unusual platforms (PowerPC, DEC Alpha, SPARC) but only their SPARCbooks were popular in the high-end UNIX market of the 1990s. ###OpenSSH 8.0 Releasing With Quantum Computing Resistant Keys OpenSSH 7.9 came out with a host of bug fixes last year with few new features, as is to be expected in minor releases. However, recently, Damien Miller has announced that OpenSSH 8.0 is nearly ready to be released. Currently, it’s undergoing testing to ensure compatibility across supported systems. https://twitter.com/damienmiller/status/1111416334737244160 Better Security Copying filenames with scp will be more secure in OpenSSH 8.0 due to the fact that copying filenames from a remote to local directory will prompt scp to check if the files sent from the server match your request. Otherwise, an attack server would theoretically be able to intercept the request by serving malicious files in place of the ones originally requested. Knowing this, you’re probably better off never using scp anyway. OpenSSH advises against it: “The scp protocol is outdated, inflexible and not readily fixed. We recommend the use of more modern protocols like sftp and rsync for file transfer instead.” Interesting new features ssh(1): When prompting whether to record a new host key, accept the key fingerprint as a synonym for “yes”. This allows the user to paste a fingerprint obtained out of band at the prompt and have the client do the comparison for you. ###Project Trident : 18.12-U8 Available Thank you all for your patience! Project Trident has finally finished some significant infrastructure updates over the last 2 weeks, and we are pleased to announce that package update 8 for 18.12-RELEASE is now available. To switch to the new update, you will need to open the “Configuration” tab in the update manager and switch to the new “Trident-release” package repository. You can also perform this transition via the command line by running: sudo sysup --change-train Trident-release ##Beastie Bits BSD Router Project - Release 1.92 EuroBSDcon - New Proposals Funny UNIX shirt (René Magritte art parody) 51NB’s Thinkpad X210 DragonFly: No more gcc50 “FreeBSD Mastery: Jails” ebook escaping! FreeBSD talk at the Augsburger Linux Info Days (german) ##Feedback/Questions DJ - FuguIta Feedback Mike - Another Good Show Alex - GhostBSD and wifi Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv Your browser does not support the HTML5 video tag.

This week, Robbie, Sasha and Jeff look at a new (came out a couple months back) Rock64 single board computer from Pine64. We've installed Ayufan's Ubuntu 18.04 with LXDE, and we'll see if it's usable ... yet. Read the complete show notes, comment or rate this episode, view pictures and obtain links from this episode at https://category5.tv/shows/technology/episode/574/ Running time: 1 Hour 5 Minutes 17 Seconds

The strange birth and long life of Unix, FreeBSD jail with a single public IP, EuroBSDcon 2018 talks and schedule, OpenBSD on G4 iBook, PAM template user, ZFS file server, and reflections on one year of OpenBSD use. Picking the contest winner Vincent Bostjan Andrew Klaus-Hendrik Will Toby Johnny David manfrom Niclas Gary Eddy Bruce Lizz Jim Random number generator ##Headlines ###The Strange Birth and Long Life of Unix They say that when one door closes on you, another opens. People generally offer this bit of wisdom just to lend some solace after a misfortune. But sometimes it’s actually true. It certainly was for Ken Thompson and the late Dennis Ritchie, two of the greats of 20th-century information technology, when they created the Unix operating system, now considered one of the most inspiring and influential pieces of software ever written. A door had slammed shut for Thompson and Ritchie in March of 1969, when their employer, the American Telephone & Telegraph Co., withdrew from a collaborative project with the Massachusetts Institute of Technology and General Electric to create an interactive time-sharing system called Multics, which stood for “Multiplexed Information and Computing Service.” Time-sharing, a technique that lets multiple people use a single computer simultaneously, had been invented only a decade earlier. Multics was to combine time-sharing with other technological advances of the era, allowing users to phone a computer from remote terminals and then read e-mail, edit documents, run calculations, and so forth. It was to be a great leap forward from the way computers were mostly being used, with people tediously preparing and submitting batch jobs on punch cards to be run one by one. Over five years, AT&T invested millions in the Multics project, purchasing a GE-645 mainframe computer and dedicating to the effort many of the top researchers at the company’s renowned Bell Telephone Laboratories—­including Thompson and Ritchie, Joseph F. Ossanna, Stuart Feldman, M. Douglas McIlroy, and the late Robert Morris. But the new system was too ambitious, and it fell troublingly behind schedule. In the end, AT&T’s corporate leaders decided to pull the plug. After AT&T’s departure from the Multics project, managers at Bell Labs, in Murray Hill, N.J., became reluctant to allow any further work on computer operating systems, leaving some researchers there very frustrated. Although Multics hadn’t met many of its objectives, it had, as Ritchie later recalled, provided them with a “convenient interactive computing service, a good environment in which to do programming, [and] a system around which a fellowship could form.” Suddenly, it was gone. With heavy hearts, the researchers returned to using their old batch system. At such an inauspicious moment, with management dead set against the idea, it surely would have seemed foolhardy to continue designing computer operating systems. But that’s exactly what Thompson, Ritchie, and many of their Bell Labs colleagues did. Now, some 40 years later, we should be thankful that these programmers ignored their bosses and continued their labor of love, which gave the world Unix, one of the greatest computer operating systems of all time. The rogue project began in earnest when Thompson, Ritchie, and a third Bell Labs colleague, Rudd Canaday, began to sketch out on paper the design for a file system. Thompson then wrote the basics of a new operating system for the lab’s GE-645 mainframe. But with the Multics project ended, so too was the need for the GE-645. Thompson realized that any further programming he did on it was likely to go nowhere, so he dropped the effort. Thompson had passed some of his time after the demise of Multics writing a computer game called Space Travel, which simulated all the major bodies in the solar system along with a spaceship that could fly around them. Written for the GE-645, Space Travel was clunky to play—and expensive: roughly US $75 a game for the CPU time. Hunting around, Thompson came across a dusty PDP-7, a minicomputer built by Digital Equipment Corp. that some of his Bell Labs colleagues had purchased earlier for a circuit-analysis project. Thompson rewrote Space Travel to run on it. And with that little programming exercise, a second door cracked ajar. It was to swing wide open during the summer of 1969 when Thompson’s wife, Bonnie, spent a month visiting his parents to show off their newborn son. Thompson took advantage of his temporary bachelor existence to write a good chunk of what would become the Unix operating system for the discarded PDP‑7. The name Unix stems from a joke one of Thompson’s colleagues made: Because the new operating system supported only one user (Thompson), he saw it as an emasculated version of Multics and dubbed it “Un-multiplexed Information and Computing Service,” or Unics. The name later morphed into Unix. Initially, Thompson used the GE-645 to compose and compile the software, which he then downloaded to the PDP‑7. But he soon weaned himself from the mainframe, and by the end of 1969 he was able to write operating-system code on the PDP-7 itself. That was a step in the right direction. But Thompson and the others helping him knew that the PDP‑7, which was already obsolete, would not be able to sustain their skunkworks for long. They also knew that the lab’s management wasn’t about to allow any more research on operating systems. So Thompson and Ritchie got crea­tive. They formulated a proposal to their bosses to buy one of DEC’s newer minicomputers, a PDP-11, but couched the request in especially palatable terms. They said they were aiming to create tools for editing and formatting text, what you might call a word-processing system today. The fact that they would also have to write an operating system for the new machine to support the editor and text formatter was almost a footnote. Management took the bait, and an order for a PDP-11 was placed in May 1970. The machine itself arrived soon after, although the disk drives for it took more than six months to appear. During the interim, Thompson, Ritchie, and others continued to develop Unix on the PDP-7. After the PDP-11’s disks were installed, the researchers moved their increasingly complex operating system over to the new machine. Next they brought over the roff text formatter written by Ossanna and derived from the runoff program, which had been used in an earlier time-sharing system. Unix was put to its first real-world test within Bell Labs when three typists from AT&T’s patents department began using it to write, edit, and format patent applications. It was a hit. The patent department adopted the system wholeheartedly, which gave the researchers enough credibility to convince management to purchase another machine—a newer and more powerful PDP-11 model—allowing their stealth work on Unix to continue. During its earliest days, Unix evolved constantly, so the idea of issuing named versions or releases seemed inappropriate. But the researchers did issue new editions of the programmer’s manual periodically, and the early Unix systems were named after each such edition. The first edition of the manual was completed in November 1971. So what did the first edition of Unix offer that made it so great? For one thing, the system provided a hierarchical file system, which allowed something we all now take for granted: Files could be placed in directories—or equivalently, folders—that in turn could be put within other directories. Each file could contain no more than 64 kilobytes, and its name could be no more than six characters long. These restrictions seem awkwardly limiting now, but at the time they appeared perfectly adequate. Although Unix was ostensibly created for word processing, the only editor available in 1971 was the line-oriented ed. Today, ed is still the only editor guaranteed to be present on all Unix systems. Apart from the text-processing and general system applications, the first edition of Unix included games such as blackjack, chess, and tic-tac-toe. For the system administrator, there were tools to dump and restore disk images to magnetic tape, to read and write paper tapes, and to create, check, mount, and unmount removable disk packs. Most important, the system offered an interactive environment that by this time allowed time-sharing, so several people could use a single machine at once. Various programming languages were available to them, including BASIC, Fortran, the scripting of Unix commands, assembly language, and B. The last of these, a descendant of a BCPL (Basic Combined Programming Language), ultimately evolved into the immensely popular C language, which Ritchie created while also working on Unix. The first edition of Unix let programmers call 34 different low-level routines built into the operating system. It’s a testament to the system’s enduring nature that nearly all of these system calls are still available—and still heavily used—on modern Unix and Linux systems four decades on. For its time, first-­edition Unix provided a remarkably powerful environment for software development. Yet it contained just 4200 lines of code at its heart and occupied a measly 16 KB of main memory when it ran. Unix’s great influence can be traced in part to its elegant design, simplicity, portability, and serendipitous timing. But perhaps even more important was the devoted user community that soon grew up around it. And that came about only by an accident of its unique history. The story goes like this: For years Unix remained nothing more than a Bell Labs research project, but by 1973 its authors felt the system was mature enough for them to present a paper on its design and implementation at a symposium of the Association for Computing Machinery. That paper was published in 1974 in the Communications of the ACM. Its appearance brought a flurry of requests for copies of the software. This put AT&T in a bind. In 1956, AT&T had agreed to a U.S government consent decree that prevented the company from selling products not directly related to telephones and telecommunications, in return for its legal monopoly status in running the country’s long-distance phone service. So Unix could not be sold as a product. Instead, AT&T released the Unix source code under license to anyone who asked, charging only a nominal fee. The critical wrinkle here was that the consent decree prevented AT&T from supporting Unix. Indeed, for many years Bell Labs researchers proudly displayed their Unix policy at conferences with a slide that read, “No advertising, no support, no bug fixes, payment in advance.” With no other channels of support available to them, early Unix adopters banded together for mutual assistance, forming a loose network of user groups all over the world. They had the source code, which helped. And they didn’t view Unix as a standard software product, because nobody seemed to be looking after it. So these early Unix users themselves set about fixing bugs, writing new tools, and generally improving the system as they saw fit. The Usenix user group acted as a clearinghouse for the exchange of Unix software in the United States. People could send in magnetic tapes with new software or fixes to the system and get back tapes with the software and fixes that Usenix had received from others. In Australia, the University of New South Wales and the University of Sydney produced a more robust version of Unix, the Australian Unix Share Accounting Method, which could cope with larger numbers of concurrent users and offered better performance. By the mid-1970s, the environment of sharing that had sprung up around Unix resembled the open-source movement so prevalent today. Users far and wide were enthusiastically enhancing the system, and many of their improvements were being fed back to Bell Labs for incorporation in future releases. But as Unix became more popular, AT&T’s lawyers began looking harder at what various licensees were doing with their systems. One person who caught their eye was John Lions, a computer scientist then teaching at the University of New South Wales, in Australia. In 1977, he published what was probably the most famous computing book of the time, A Commentary on the Unix Operating System, which contained an annotated listing of the central source code for Unix. Unix’s licensing conditions allowed for the exchange of source code, and initially, Lions’s book was sold to licensees. But by 1979, AT&T’s lawyers had clamped down on the book’s distribution and use in academic classes. The anti­authoritarian Unix community reacted as you might expect, and samizdat copies of the book spread like wildfire. Many of us have nearly unreadable nth-­generation photocopies of the original book. End runs around AT&T’s lawyers indeed became the norm—even at Bell Labs. For example, between the release of the sixth edition of Unix in 1975 and the seventh edition in 1979, Thompson collected dozens of important bug fixes to the system, coming both from within and outside of Bell Labs. He wanted these to filter out to the existing Unix user base, but the company’s lawyers felt that this would constitute a form of support and balked at their release. Nevertheless, those bug fixes soon became widely distributed through unofficial channels. For instance, Lou Katz, the founding president of Usenix, received a phone call one day telling him that if he went down to a certain spot on Mountain Avenue (where Bell Labs was located) at 2 p.m., he would find something of interest. Sure enough, Katz found a magnetic tape with the bug fixes, which were rapidly in the hands of countless users. By the end of the 1970s, Unix, which had started a decade earlier as a reaction against the loss of a comfortable programming environment, was growing like a weed throughout academia and the IT industry. Unix would flower in the early 1980s before reaching the height of its popularity in the early 1990s. For many reasons, Unix has since given way to other commercial and noncommercial systems. But its legacy, that of an elegant, well-designed, comfortable environment for software development, lives on. In recognition of their accomplishment, Thompson and Ritchie were given the Japan Prize earlier this year, adding to a collection of honors that includes the United States’ National Medal of Technology and Innovation and the Association of Computing Machinery’s Turing Award. Many other, often very personal, tributes to Ritchie and his enormous influence on computing were widely shared after his death this past October. Unix is indeed one of the most influential operating systems ever invented. Its direct descendants now number in the hundreds. On one side of the family tree are various versions of Unix proper, which began to be commercialized in the 1980s after the Bell System monopoly was broken up, freeing AT&T from the stipulations of the 1956 consent decree. On the other side are various Unix-like operating systems derived from the version of Unix developed at the University of California, Berkeley, including the one Apple uses today on its computers, OS X. I say “Unix-like” because the developers of the Berkeley Software Distribution (BSD) Unix on which these systems were based worked hard to remove all the original AT&T code so that their software and its descendants would be freely distributable. The effectiveness of those efforts were, however, called into question when the AT&T subsidiary Unix System Laboratories filed suit against Berkeley Software Design and the Regents of the University of California in 1992 over intellectual property rights to this software. The university in turn filed a counterclaim against AT&T for breaches to the license it provided AT&T for the use of code developed at Berkeley. The ensuing legal quagmire slowed the development of free Unix-like clones, including 386BSD, which was designed for the Intel 386 chip, the CPU then found in many IBM PCs. Had this operating system been available at the time, Linus Torvalds says he probably wouldn’t have created Linux, an open-source Unix-like operating system he developed from scratch for PCs in the early 1990s. Linux has carried the Unix baton forward into the 21st century, powering a wide range of digital gadgets including wireless routers, televisions, desktop PCs, and Android smartphones. It even runs some supercomputers. Although AT&T quickly settled its legal disputes with Berkeley Software Design and the University of California, legal wrangling over intellectual property claims to various parts of Unix and Linux have continued over the years, often involving byzantine corporate relations. By 2004, no fewer than five major lawsuits had been filed. Just this past August, a software company called the TSG Group (formerly known as the SCO Group), lost a bid in court to claim ownership of Unix copyrights that Novell had acquired when it purchased the Unix System Laboratories from AT&T in 1993. As a programmer and Unix historian, I can’t help but find all this legal sparring a bit sad. From the very start, the authors and users of Unix worked as best they could to build and share, even if that meant defying authority. That outpouring of selflessness stands in sharp contrast to the greed that has driven subsequent legal battles over the ownership of Unix. The world of computer hardware and software moves forward startlingly fast. For IT professionals, the rapid pace of change is typically a wonderful thing. But it makes us susceptible to the loss of our own history, including important lessons from the past. To address this issue in a small way, in 1995 I started a mailing list of old-time Unix ­aficionados. That effort morphed into the Unix Heritage Society. Our goal is not only to save the history of Unix but also to collect and curate these old systems and, where possible, bring them back to life. With help from many talented members of this society, I was able to restore much of the old Unix software to working order, including Ritchie’s first C compiler from 1972 and the first Unix system to be written in C, dating from 1973. One holy grail that eluded us for a long time was the first edition of Unix in any form, electronic or otherwise. Then, in 2006, Al Kossow from the Computer History Museum, in Mountain View, Calif., unearthed a printed study of Unix dated 1972, which not only covered the internal workings of Unix but also included a complete assembly listing of the kernel, the main component of this operating system. This was an amazing find—like discovering an old Ford Model T collecting dust in a corner of a barn. But we didn’t just want to admire the chrome work from afar. We wanted to see the thing run again. In 2008, Tim Newsham, an independent programmer in Hawaii, and I assembled a team of like-minded Unix enthusiasts and set out to bring this ancient system back from the dead. The work was technically arduous and often frustrating, but in the end, we had a copy of the first edition of Unix running on an emulated PDP-11/20. We sent out messages announcing our success to all those we thought would be interested. Thompson, always succinct, simply replied, “Amazing.” Indeed, his brainchild was amazing, and I’ve been happy to do what I can to make it, and the story behind it, better known. Digital Ocean http://do.co/bsdnow ###FreeBSD jails with a single public IP address Jails in FreeBSD provide a simple yet flexible way to set up a proper server layout. In the most setups the actual server only acts as the host system for the jails while the applications themselves run within those independent containers. Traditionally every jail has it’s own IP for the user to be able to address the individual services. But if you’re still using IPv4 this might get you in trouble as the most hosters don’t offer more than one single public IP address per server. Create the internal network In this case NAT (“Network Address Translation”) is a good way to expose services in different jails using the same IP address. First, let’s create an internal network (“NAT network”) at 192.168.0.0/24. You could generally use any private IPv4 address space as specified in RFC 1918. Here’s an overview: https://en.wikipedia.org/wiki/Privatenetwork. Using pf, FreeBSD’s firewall, we will map requests on different ports of the same public IP address to our individual jails as well as provide network access to the jails themselves. First let’s check which network devices are available. In my case there’s em0 which provides connectivity to the internet and lo0, the local loopback device. options=209b [...] inet 172.31.1.100 netmask 0xffffff00 broadcast 172.31.1.255 nd6 options=23 media: Ethernet autoselect (1000baseT ) status: active lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 nd6 options=21``` > For our internal network, we create a cloned loopback device called lo1. Therefore we need to customize the /etc/rc.conf file, adding the following two lines: cloned_interfaces="lo1" ipv4_addrs_lo1="192.168.0.1-9/29" > This defines a /29 network, offering IP addresses for a maximum of 6 jails: ipcalc 192.168.0.1/29 Address: 192.168.0.1 11000000.10101000.00000000.00000 001 Netmask: 255.255.255.248 = 29 11111111.11111111.11111111.11111 000 Wildcard: 0.0.0.7 00000000.00000000.00000000.00000 111 => Network: 192.168.0.0/29 11000000.10101000.00000000.00000 000 HostMin: 192.168.0.1 11000000.10101000.00000000.00000 001 HostMax: 192.168.0.6 11000000.10101000.00000000.00000 110 Broadcast: 192.168.0.7 11000000.10101000.00000000.00000 111 Hosts/Net: 6 Class C, Private Internet > Then we need to restart the network. Please be aware of currently active SSH sessions as they might be dropped during restart. It’s a good moment to ensure you have KVM access to that server ;-) service netif restart > After reconnecting, our newly created loopback device is active: lo1: flags=8049 metric 0 mtu 16384 options=600003 inet 192.168.0.1 netmask 0xfffffff8 inet 192.168.0.2 netmask 0xffffffff inet 192.168.0.3 netmask 0xffffffff inet 192.168.0.4 netmask 0xffffffff inet 192.168.0.5 netmask 0xffffffff inet 192.168.0.6 netmask 0xffffffff inet 192.168.0.7 netmask 0xffffffff inet 192.168.0.8 netmask 0xffffffff inet 192.168.0.9 netmask 0xffffffff nd6 options=29 Setting up > pf part of the FreeBSD base system, so we only have to configure and enable it. By this moment you should already have a clue of which services you want to expose. If this is not the case, just fix that file later on. In my example configuration, I have a jail running a webserver and another jail running a mailserver: Public IP address IP_PUB="1.2.3.4" Packet normalization scrub in all Allow outbound connections from within the jails nat on em0 from lo1:network to any -> (em0) webserver jail at 192.168.0.2 rdr on em0 proto tcp from any to $IP_PUB port 443 -> 192.168.0.2 just an example in case you want to redirect to another port within your jail rdr on em0 proto tcp from any to $IP_PUB port 80 -> 192.168.0.2 port 8080 mailserver jail at 192.168.0.3 rdr on em0 proto tcp from any to $IP_PUB port 25 -> 192.168.0.3 rdr on em0 proto tcp from any to $IP_PUB port 587 -> 192.168.0.3 rdr on em0 proto tcp from any to $IP_PUB port 143 -> 192.168.0.3 rdr on em0 proto tcp from any to $IP_PUB port 993 -> 192.168.0.3 > Now just enable pf like this (which is the equivalent of adding pf_enable=YES to /etc/rc.conf): sysrc pf_enable="YES" > and start it: service pf start Install ezjail > Ezjail is a collection of scripts by erdgeist that allow you to easily manage your jails. pkg install ezjail > As an alternative, you could install ezjail from the ports tree. Now we need to set up the basejail which contains the shared base system for our jails. In fact, every jail that you create get’s will use that basejail to symlink directories related to the base system like /bin and /sbin. This can be accomplished by running ezjail-admin install > In the next step, we’ll copy the /etc/resolv.conf file from our host to the newjail, which is the template for newly created jails (the parts that are not provided by basejail), to ensure that domain resolution will work properly within our jails later on: cp /etc/resolv.conf /usr/jails/newjail/etc/ > Last but not least, we enable ezjail and start it: sysrc ezjail_enable="YES" service ezjail start Create a jail > Creating a jail is as easy as it could probably be: ezjail-admin create webserver 192.168.0.2 ezjail-admin start webserver > Now you can access your jail using: ezjail-admin console webserver > Each jail contains a vanilla FreeBSD installation. Deploy services > Now you can spin up as many jails as you want to set up your services like web, mail or file shares. You should take care not to enable sshd within your jails, because that would cause problems with the service’s IP bindings. But this is not a problem, just SSH to the host and enter your jail using ezjail-admin console. EuroBSDcon 2018 Talks & Schedule (https://2018.eurobsdcon.org/talks-schedule/) News Roundup OpenBSD on an iBook G4 (https://bobstechsite.com/openbsd-on-an-ibook-g4/) > I've mentioned on social media and on the BTS podcast a few times that I wanted to try installing OpenBSD onto an old "snow white" iBook G4 I acquired last summer to see if I could make it a useful machine again in the year 2018. This particular eBay purchase came with a 14" 1024x768 TFT screen, 1.07GHz PowerPC G4 processor, 1.5GB RAM, 100GB of HDD space and an ATI Radeon 9200 graphics card with 32 MB of SDRAM. The optical drive, ethernet port, battery & USB slots are also fully-functional. The only thing that doesn't work is the CMOS battery, but that's not unexpected for a device that was originally released in 2004. Initial experiments > This iBook originally arrived at my door running Apple Mac OSX Leopard and came with the original install disk, the iLife & iWork suites for 2008, various instruction manuals, a working power cable and a spare keyboard. As you'll see in the pictures I took for this post the characters on the buttons have started to wear away from 14 years of intensive use, but the replacement needs a very good clean before I decide to swap it in! > After spending some time exploring the last version of OSX to support the IBM PowerPC processor architecture I tried to see if the hardware was capable of modern computing with Linux. Something I knew ahead of trying this was that the WiFi adapter was unlikely to work because it's a highly proprietary component designed by Apple to work specifically with OSX and nothing else, but I figured I could probably use a wireless USB dongle later to get around this limitation. > Unfortunately I found that no recent versions of mainstream Linux distributions would boot off this machine. Debian has dropped support 32-bit PowerPC architectures and the PowerPC variants of Ubuntu 16.04 LTS (vanilla, MATE and Lubuntu) wouldn't even boot the installer! The only distribution I could reliably install on the hardware was Lubuntu 14.04 LTS. > Unfortunately I'm not the biggest fan of the LXDE desktop for regular work and a lot of ported applications were old and broken because it clearly wasn't being maintained by people that use the hardware anymore. Ubuntu 14.04 is also approaching the end of its support life in early 2019, so this limited solution also has a limited shelf-life. Over to BSD > I discussed this problem with a few people on Mastodon and it was pointed out to me that OSX is built on the Darwin kernel, which happens to be a variant of BSD. NetBSD and OpenBSD fans in particular convinced me that their communities still saw the value of supporting these old pieces of kit and that I should give BSD a try. > So yesterday evening I finally downloaded the "macppc" version of OpenBSD 6.3 with no idea what to expect. I hoped for the best but feared the worst because my last experience with this operating system was trying out PC-BSD in 2008 and discovering with disappointment that it didn't support any of the hardware on my Toshiba laptop. > When I initially booted OpenBSD I was a little surprised to find the login screen provided no visual feedback when I typed in my password, but I can understand the security reasons for doing that. The initial desktop environment that was loaded was very basic. All I could see was a console output window, a terminal and a desktop switcher in the X11 environment the system had loaded. > After a little Googling I found this blog post had some fantastic instructions to follow for the post-installation steps: https://sohcahtoa.org.uk/openbsd.html. I did have to adjust them slightly though because my iBook only has 1.5GB RAM and not every package that page suggests is available on macppc by default. You can see a full list here: https://ftp.openbsd.org/pub/OpenBSD/6.3/packages/powerpc/. Final thoughts > I was really impressed with the performance of OpenBSD's "macppc" port. It boots much faster than OSX Leopard on the same hardware and unlike Lubuntu 14.04 it doesn't randomly hang for no reason or crash if you launch something demanding like the GIMP. > I was pleased to see that the command line tools I'm used to using on Linux have been ported across too. OpenBSD also had no issues with me performing basic desktop tasks on XFCE like browsing the web with NetSurf, playing audio files with VLC and editing images with the GIMP. Limited gaming is also theoretically possible if you're willing to build them (or an emulator) from source with SDL support. > If I wanted to use this system for heavy duty work then I'd probably be inclined to run key applications like LibreOffice on a Raspberry Pi and then connect my iBook G4 to those using VNC or an SSH connection with X11 forwarding. BSD is UNIX after all, so using my ancient laptop as a dumb terminal should work reasonably well. > In summary I was impressed with OpenBSD and its ability to breathe new life into this old Apple Mac. I'm genuinely excited about the idea of trying BSD with other devices on my network such as an old Asus Eee PC 900 netbook and at least one of the many Raspberry Pi devices I use. Whether I go the whole hog and replace Fedora on my main production laptop though remains to be seen! The template user with PAM and login(1) (http://oshogbo.vexillium.org/blog/48) > When you build a new service (or an appliance) you need your users to be able to configure it from the command line. To accomplish this you can create system accounts for all registered users in your service and assign them a special login shell which provides such limited functionality. This can be painful if you have a dynamic user database. > Another challenge is authentication via remote services such as RADIUS. How can we implement services when we authenticate through it and log into it as a different user? Furthermore, imagine a scenario when RADIUS decides on which account we have the right to access by sending an additional attribute. > To address these two problems we can use a "template" user. Any of the PAM modules can set the value of the PAM_USER item. The value of this item will be used to determine which account we want to login. Only the "template" user must exist on the local password database, but the credential check can be omitted by the module. > This functionality exists in the login(1) used by FreeBSD, HardenedBSD, DragonFlyBSD and illumos. The functionality doesn't exist in the login(1) used in NetBSD, and OpenBSD doesn't support PAM modules at all. In addition what is also noteworthy is that such functionality was also in the OpenSSH but they decided to remove it and call it a security vulnerability (CVE 2015-6563). I can see how some people may have seen it that way, that’s why I recommend reading this article from an OpenPAM author and a FreeBSD security officer at the time. > Knowing the background let's take a look at an example. ```PAMEXTERN int pamsmauthenticate(pamhandlet *pamh, int flags _unused, int argc _unused, const char *argv[] _unused) { const char *user, *password; int err; err = pam_get_user(pamh, &user, NULL); if (err != PAM_SUCCESS) return (err); err = pam_get_authtok(pamh, PAM_AUTHTOK, &password, NULL); if (err == PAM_CONV_ERR) return (err); if (err != PAM_SUCCESS) return (PAM_AUTH_ERR); err = authenticate(user, password); if (err != PAM_SUCCESS) { return (err); } return (pam_set_item(pamh, PAM_USER, "template")); } In the listing above we have an example of a PAM module. The pamgetuser(3) provides a username. The pamgetauthtok(3) shows us a secret given by the user. Both functions allow us to give an optional prompt which should be shown to the user. The authenticate function is our crafted function which authenticates the user. In our first scenario we wanted to keep all users in an external database. If authentication is successful we then switch to a template user which has a shell set up for a script allowing us to configure the machine. In our second scenario the authenticate function authenticates the user in RADIUS. Another step is to add our PAM module to the /etc/pam.d/system or to the /etc/pam.d/login configuration: auth sufficient pamtemplate.so nowarn allowlocal Unfortunately the description of all these options goes beyond this article - if you would like to know more about it you can find them in the PAM manual. The last thing we need to do is to add our template user to the system which you can do by the adduser(8) command or just simply modifying the /etc/master.passwd file and use pwdmkdb(8) program: $ tail -n /etc/master.passwd template::1000:1000::0:0:User &:/:/usr/local/bin/templatesh $ sudo pwdmkdb /etc/master.passwd As you can see,the template user can be locked and we still can use it in our PAM module (the * character after login). I would like to thank Dag-Erling Smørgrav for pointing this functionality out to me when I was looking for it some time ago. iXsystems iXsystems @ VMWorld ###ZFS file server What is the need? At work, we run a compute cluster that uses an Isilon cluster as primary NAS storage. Excluding snapshots, we have about 200TB of research data, some of them in compressed formats, and others not. We needed an offsite backup file server that would constantly mirror our primary NAS and serve as a quick recovery source in case of a data loss in the the primary NAS. This offsite file server would be passive - will never face the wrath of the primary cluster workload. In addition to the role of a passive backup server, this solution would take on some passive report generation workloads as an ideal way of offloading some work from the primary NAS. The passive work is read-only. The backup server would keep snapshots in a best effort basis dating back to 10 years. However, this data on this backup server would be archived to tapes periodically. A simple guidance of priorities: Data integrity > Cost of solution > Storage capacity > Performance. Why not enterprise NAS? NetApp FAS or EMC Isilon or the like? We decided that enterprise grade NAS like NetAPP FAS or EMC Isilon are prohibitively expensive and an overkill for our needs. An open source & cheaper alternative to enterprise grade filesystem with the level of durability we expect turned up to be ZFS. We’re already spoilt from using snapshots by a clever Copy-on-Write Filesystem(WAFL) by NetApp. ZFS providing snapshots in almost identical way was a big influence in the choice. This is also why we did not consider just a CentOS box with the default XFS filesystem. FreeBSD vs Debian for ZFS This is a backup server, a long-term solution. Stability and reliability are key requirements. ZFS on Linux may be popular at this time, but there is a lot of churn around its development, which means there is a higher probability of bugs like this to occur. We’re not looking for cutting edge features here. Perhaps, Linux would be considered in the future. FreeBSD + ZFS We already utilize FreeBSD and OpenBSD for infrastructure services and we have nothing but praises for the stability that the BSDs have provided us. We’d gladly use FreeBSD and OpenBSD wherever possible. Okay, ZFS, but why not FreeNAS? IMHO, FreeNAS provides a integrated GUI management tool over FreeBSD for a novice user to setup and configure FreeBSD, ZFS, Jails and many other features. But, this user facing abstraction adds an extra layer of complexity to maintain that is just not worth it in simpler use cases like ours. For someone that appreciates the commandline interface, and understands FreeBSD enough to administer it, plain FreeBSD + ZFS is simpler and more robust than FreeNAS. Specifications Lenovo SR630 Rackserver 2 X Intel Xeon silver 4110 CPUs 768 GB of DDR4 ECC 2666 MHz RAM 4 port SAS card configured in passthrough mode(JBOD) Intel network card with 10 Gb SFP+ ports 128GB M.2 SSD for use as boot drive 2 X HGST 4U60 JBOD 120(2 X 60) X 10TB SAS disks ###Reflection on one-year usage of OpenBSD I have used OpenBSD for more than one year, and it is time to give a summary of the experience: (1) What do I get from OpenBSD? a) A good UNIX tutorial. When I am curious about some UNIXcommands’ implementation, I will refer to OpenBSD source code, and I actually gain something every time. E.g., refresh socket programming skills from nc; know how to process file efficiently from cat. b) A better test bed. Although my work focus on developing programs on Linux, I will try to compile and run applications on OpenBSD if it is possible. One reason is OpenBSD usually gives more helpful warnings. E.g., hint like this: ...... warning: sprintf() is often misused, please use snprintf() ...... Or you can refer this post which I wrote before. The other is sometimes program run well on Linux may crash on OpenBSD, and OpenBSD can help you find hidden bugs. c) Some handy tools. E.g. I find tcpbench is useful, so I ported it into Linux for my own usage (project is here). (2) What I give back to OpenBSD? a) Patches. Although most of them are trivial modifications, they are still my contributions. b) Write blog posts to share experience about using OpenBSD. c) Develop programs for OpenBSD/BSD: lscpu and free. d) Porting programs into OpenBSD: E.g., I find google/benchmark is a nifty tool, but lacks OpenBSD support, I submitted PR and it is accepted. So you can use google/benchmark on OpenBSD now. Generally speaking, the time invested on OpenBSD is rewarding. If you are still hesitating, why not give a shot? ##Beastie Bits BSD Users Stockholm Meetup BSDCan 2018 Playlist OPNsense 18.7 released Testing TrueOS (FreeBSD derivative) on real hardware ThinkPad T410 Kernel Hacker Wanted! Replace a pair of 8-bit writes to VGA memory with a single 16-bit write Reduce taskq and context-switch cost of zio pipe Proposed FreeBSD Memory Management change, expected to improve ZFS ARC interactions Tarsnap ##Feedback/Questions Anian_Z - Question Robert - Pool question Lain - Congratulations Thomas - L2arc Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

Nyheter ——- * Fedora 28 med GNOME 3.28 Fedora 28 Beta finns nu redo att ladd ner för att testas, GNOME 3.28 för Fedora 28 Workstation, och nya modulära repository för Fedora 28 Server.  ”Instead of a separate modularized operating system, we’ve added a new Modular Repository alongside the traditional Everything Repository,” said Eduard Lucena. ”With the Fedora Server Edition, the Modular repository will be immediately available. You will have access to a few modules today with more to come during the run-up to the F28 release.” Modulrity initiative för Fedora 28 Server systemadministratörer kan köra multipla versioner av samma mjukvara utan att kompromisa med stabilitet och pålitligheten. https://lnxpod.link/2Eq0dos * Du kan nu köra Arch Linux på Raspberry Pi 3 Model B+ med RaspArch Med Linux kärna 4.14.31 och de senaste mjukvarupaketen från Arch Linux, RaspArch Build 180402 är speciellt utvecklad till Raspberry Pi Foundation’s nya Raspberry Pi 3 Model B+ dator, Man kan även anvvända distron på älder Raspberry Pi 3 Model B och Raspberry Pi 2 Model B.  RaspArch är ett derivatat av Arch Linux ARM operating system, RaspArch använder sig av LXDE som skrivbordsmiljö som standard och kommer med populära Open Source progam som Mozillas Firefox, GIMP, Yaourt grafiska packethanterare, PulseAudiol ljud. Enligt utveckarna är RaspArch en redo-att-köra för ARM-system. https://lnxpod.link/2ErBMXu   * Valve meddelar att de inte övergett linux Som vi alla vet har Valve inte sålt så många enheter av sin spelkonsoll. Detta är synd då det var ett Debiansystem med lite extra arbete för just deras spelklient steam. Företaget har dock fortfarande som mål att utveckla en öppen spelplattform, där bland annat satsningen på grafikgränssnittet Vulkan. De har även en hel del linuxinitiativ på gång men inget de kan prata om för tillfället.  https://www.sweclockers.com/nyhet/25475-valve-vi-har-inte-overgett-satsningen-pa-linux * OpenBSD 6.3 Släppt Som vi sagt tidigare så måste vi förtjäna att ha BSD i vår logga så för den som bryr sig meddelar vi nu att OpenBSD 6.3 är släppt. 

As we continue to experiment with the newly stable Debian Stretch, we'll compare the out-of-box new user experience of Cinnamon, LXDE, Gnome and KDE. Read the complete show notes, comment or rate this episode, view pictures and obtain links from this episode at https://category5.tv/shows/technology/episode/510/ Running time: 1 Hour 25 Seconds

Today on BSD Now, the latest Dragonfly BSD release, RaidZ performance, another OpenSSL Vulnerability, and more; all this week on BSD Now. This episode was brought to you by Headlines DragonFly BSD 4.8 is released (https://www.dragonflybsd.org/release48/) Improved kernel performance This release further localizes cache lines and reduces/removes cache ping-ponging on globals. For bulk builds on many-cores or multi-socket systems, we have around a 5% improvement, and certain subsystems such as namecache lookups and exec()s see massive focused improvements. See the corresponding mailing list post with details. Support for eMMC booting, and mobile and high-performance PCIe SSDs This kernel release includes support for eMMC storage as the boot device. We also sport a brand new SMP-friendly, high-performance NVMe SSD driver (PCIe SSD storage). Initial device test results are available. EFI support The installer can now create an EFI or legacy installation. Numerous adjustments have been made to userland utilities and the kernel to support EFI as a mainstream boot environment. The /boot filesystem may now be placed either in its own GPT slice, or in a DragonFly disklabel inside a GPT slice. DragonFly, by default, creates a GPT slice for all of DragonFly and places a DragonFly disklabel inside it with all the standard DFly partitions, such that the disk names are roughly the same as they would be in a legacy system. Improved graphics support The i915 driver has been updated to match the version found with the Linux 4.6 kernel. Broadwell and Skylake processor users will see improvements. Other user-affecting changes Kernel is now built using -O2. VKernels now use COW, so multiple vkernels can share one disk image. powerd() is now sensitive to time and temperature changes. Non-boot-filesystem kernel modules can be loaded in rc.conf instead of loader.conf. *** #8005 poor performance of 1MB writes on certain RAID-Z configurations (https://github.com/openzfs/openzfs/pull/321) Matt Ahrens posts a new patch for OpenZFS Background: RAID-Z requires that space be allocated in multiples of P+1 sectors,because this is the minimum size block that can have the required amount of parity. Thus blocks on RAIDZ1 must be allocated in a multiple of 2 sectors; on RAIDZ2 multiple of 3; and on RAIDZ3 multiple of 4. A sector is a unit of 2^ashift bytes, typically 512B or 4KB. To satisfy this constraint, the allocation size is rounded up to the proper multiple, resulting in up to 3 "pad sectors" at the end of some blocks. The contents of these pad sectors are not used, so we do not need to read or write these sectors. However, some storage hardware performs much worse (around 1/2 as fast) on mostly-contiguous writes when there are small gaps of non-overwritten data between the writes. Therefore, ZFS creates "optional" zio's when writing RAID-Z blocks that include pad sectors. If writing a pad sector will fill the gap between two (required) writes, we will issue the optional zio, thus doubling performance. The gap-filling performance improvement was introduced in July 2009. Writing the optional zio is done by the io aggregation code in vdevqueue.c. The problem is that it is also subject to the limit on the size of aggregate writes, zfsvdevaggregationlimit, which is by default 128KB. For a given block, if the amount of data plus padding written to a leaf device exceeds zfsvdevaggregation_limit, the optional zio will not be written, resulting in a ~2x performance degradation. The solution is to aggregate optional zio's regardless of the aggregation size limit. As you can see from the graphs, this can make a large difference in performance. I encourage you to read the entire commit message, it is well written and very detailed. *** Can you spot the OpenSSL vulnerability (https://guidovranken.wordpress.com/2017/01/28/can-you-spot-the-vulnerability/) This code was introduced in OpenSSL 1.1.0d, which was released a couple of days ago. This is in the server SSL code, ssl/statem/statemsrvr.c, sslbytestocipherlist()), and can easily be reached remotely. Can you spot the vulnerability? So there is a loop, and within that loop we have an ‘if' statement, that tests a number of conditions. If any of those conditions fail, OPENSSLfree(raw) is called. But raw isn't the address that was allocated; raw is increment every loop. Hence, there is a remote invalid free vulnerability. But not quite. None of those checks in the ‘if' statement can actually fail; earlier on in the function, there is a check that verifies that the packet contains at least 1 byte, so PACKETget1 cannot fail. Furthermore, earlier in the function it is verified that the packet length is a multiple of 3, hence PACKETcopybytes and PACKET_forward cannot fail. So, does the code do what the original author thought, or expected it to do? But what about the next person that modifies that code, maybe changing or removing one of the earlier checks, allowing one of those if conditions to fail, and execute the bad code? Nonetheless OpenSSL has acknowledged that the OPENSSL_free line needs a rewrite: Pull Request #2312 (https://github.com/openssl/openssl/pull/2312) PS I'm not posting this to ridicule the OpenSSL project or their programming skills. I just like reading code and finding corner cases that impact security, which is an effort that ultimately works in everybody's best interest, and I like to share what I find. Programming is a very difficult enterprise and everybody makes mistakes. Thanks to Guido Vranken for the sharp eye and the blog post *** Research Debt (http://distill.pub/2017/research-debt/) I found this article interesting as it relates to not just research, but a lot of technical areas in general Achieving a research-level understanding of most topics is like climbing a mountain. Aspiring researchers must struggle to understand vast bodies of work that came before them, to learn techniques, and to gain intuition. Upon reaching the top, the new researcher begins doing novel work, throwing new stones onto the top of the mountain and making it a little taller for whoever comes next. People expect the climb to be hard. It reflects the tremendous progress and cumulative effort that's gone into the research. The climb is seen as an intellectual pilgrimage, the labor a rite of passage. But the climb could be massively easier. It's entirely possible to build paths and staircases into these mountains. The climb isn't something to be proud of. The climb isn't progress: the climb is a mountain of debt. Programmers talk about technical debt: there are ways to write software that are faster in the short run but problematic in the long run. Poor Exposition – Often, there is no good explanation of important ideas and one has to struggle to understand them. This problem is so pervasive that we take it for granted and don't appreciate how much better things could be. Undigested Ideas – Most ideas start off rough and hard to understand. They become radically easier as we polish them, developing the right analogies, language, and ways of thinking. Bad abstractions and notation – Abstractions and notation are the user interface of research, shaping how we think and communicate. Unfortunately, we often get stuck with the first formalisms to develop even when they're bad. For example, an object with extra electrons is negative, and pi is wrong Noise – Being a researcher is like standing in the middle of a construction site. Countless papers scream for your attention and there's no easy way to filter or summarize them. We think noise is the main way experts experience research debt. There's a tradeoff between the energy put into explaining an idea, and the energy needed to understand it. On one extreme, the explainer can painstakingly craft a beautiful explanation, leading their audience to understanding without even realizing it could have been difficult. On the other extreme, the explainer can do the absolute minimum and abandon their audience to struggle. This energy is called interpretive labor Research distillation is the opposite of research debt. It can be incredibly satisfying, combining deep scientific understanding, empathy, and design to do justice to our research and lay bare beautiful insights. Distillation is also hard. It's tempting to think of explaining an idea as just putting a layer of polish on it, but good explanations often involve transforming the idea. This kind of refinement of an idea can take just as much effort and deep understanding as the initial discovery. + The distillation can often times require an entirely different set of skills than the original creation of the idea. Almost all of the BSD projects have some great ideas or subsystems that just need distillation into easy to understand and use platforms or tools. Like the theoretician, the experimentalist or the research engineer, the research distiller is an integral role for a healthy research community. Right now, almost no one is filling it. Anyway, if that bit piqued your interest, go read the full article and the suggested further reading. *** News Roundup And then the murders began. (https://blather.michaelwlucas.com/archives/2902) A whole bunch of people have pointed me at articles like this one (http://thehookmag.com/2017/03/adding-murders-began-second-sentence-book-makes-instantly-better-125462/), which claim that you can improve almost any book by making the second sentence “And then the murders began.” It's entirely possible they're correct. But let's check, with a sampling of books. As different books come in different tenses and have different voices, I've made some minor changes. “Welcome to Cisco Routers for the Desperate! And then the murders begin.” — Cisco Routers for the Desperate, 2nd ed “Over the last ten years, OpenSSH has become the standard tool for remote management of Unix-like systems and many network devices. And then the murders began.” — SSH Mastery “The Z File System, or ZFS, is a complicated beast, but it is also the most powerful tool in a sysadmin's Batman-esque utility belt. And then the murders begin.” — FreeBSD Mastery: Advanced ZFS “Blood shall rain from the sky, and great shall be the lamentation of the Linux fans. And then, the murders will begin.” — Absolute FreeBSD, 3rd Ed Netdata now supports FreeBSD (https://github.com/firehol/netdata) netdata is a system for distributed real-time performance and health monitoring. It provides unparalleled insights, in real-time, of everything happening on the system it runs (including applications such as web and database servers), using modern interactive web dashboards. From the release notes: apps.plugin ported for FreeBSD Check out their demo sites (https://github.com/firehol/netdata/wiki) *** Distrowatch Weekly reviews RaspBSD (https://distrowatch.com/weekly.php?issue=20170220#raspbsd) RaspBSD is a FreeBSD-based project which strives to create a custom build of FreeBSD for single board and hobbyist computers. RaspBSD takes a recent snapshot of FreeBSD and adds on additional components, such as the LXDE desktop and a few graphical applications. The RaspBSD project currently has live images for Raspberry Pi devices, the Banana Pi, Pine64 and BeagleBone Black & Green computers. The default RaspBSD system is quite minimal, running a mere 16 processes when I was logged in. In the background the operating system runs cron, OpenSSH, syslog and the powerd power management service. Other than the user's shell and terminals, nothing else is running. This means RaspBSD uses little memory, requiring just 16MB of active memory and 31MB of wired or kernel memory. I made note of a few practical differences between running RaspBSD on the Pi verses my usual Raspbian operating system. One minor difference is RaspBSD turns off the Pi's external power light after booting. Raspbian leaves the light on. This means it looks like the Pi is off when it is running RaspBSD, but it also saves a little electricity. Conclusions: Apart from these little differences, running RaspBSD on the Pi was a very similar experience to running Raspbian and my time with the operating system was pleasantly trouble-free. Long-term, I think applying source updates to the base system might be tedious and SD disk operations were slow. However, the Pi usually is not utilized for its speed, but rather its low cost and low-energy usage. For people who are looking for a small home server or very minimal desktop box, RaspBSD running on the Pi should be suitable. Research UNIX V8, V9 and V10 made public by Alcatel-Lucent (https://media-bell-labs-com.s3.amazonaws.com/pages/20170327_1602/statement%20regarding%20Unix%203-7-17.pdf) Alcatel-Lucent USA Inc. (“ALU-USA”), on behalf of itself and Nokia Bell Laboratories agrees, to the extent of its ability to do so, that it will not assert its copyright rights with respect to any non-commercial copying, distribution, performance, display or creation of derivative works of Research Unix®1 Editions 8, 9, and 10. Research Unix is a term used to refer to versions of the Unix operating system for DEC PDP-7, PDP-11, VAX and Interdata 7/32 and 8/32 computers, developed in the Bell Labs Computing Science Research Center. The version breakdown can be viewed on its Wikipedia page (https://en.wikipedia.org/wiki/Research_Unix) It only took 30+ years, but now they're public You can grab them from here (http://www.tuhs.org/Archive/Distributions/Research/) If you're wondering what happened with Research Unix, After Version 10, Unix development at Bell Labs was stopped in favor of a successor system, Plan 9 (http://plan9.bell-labs.com/plan9/); which itself was succeeded by Inferno (http://www.vitanuova.com/inferno/). *** Beastie Bits The BSD Family Tree (https://github.com/freebsd/freebsd/blob/master/share/misc/bsd-family-tree) Unix Permissions Calculator (http://permissions-calculator.org/) NAS4Free release 11.0.0.4 now available (https://sourceforge.net/projects/nas4free/files/NAS4Free-11.0.0.4/11.0.0.4.4141/) Another BSD Mag released for free downloads (https://bsdmag.org/download/simple-quorum-drive-freebsd-ctl-ha-beast-storage-system/) OPNsense 17.1.4 released (https://forum.opnsense.org/index.php?topic=4898.msg19359) *** Feedback/Questions gozes asks via twitter about how get involved in FreeBSD (https://twitter.com/gozes/status/846779901738991620) ***

In the podcast this week... Joao gushes over Lubuntu, AG thinks RAID is a backup, and a bit of talk about piracy.---Joao's Thing He Did(I'll do a standalone post for these with screenshots and whatnot, but here's the outline)The Lubuntu ModInstall the whisker menu and indicator plugin (it pulls down the XFCE panel as a dependency):sudo apt-get updatesudo apt-get install xfce4-whiskermenu-plugin xfce4-indicator-pluginThe config file to mess with LXDE is in /home/yourUser/.config/lxsession/Lubuntu/desktop.confFind the line that says... panel/command=lxpaneland change it topanel/command=xfce4-panelRestart and you should have the XFCE menu installed and you can configure from there.For Numix and Arc, add the Numix repository, download the Numix icon set and Numix theme, and download the arc theme.sudo apt-add-repository ppa:numix/ppasudo apt-get updatesudo apt-get install arc-theme numix-blue-gtk-theme numix-icon-theme-circle---Download the episode here. Support us on Patreon (pretty please).---Listen and Subscribe...  we're @thirdworldlinux and @chFourteen on twitterwe're also on Google+but if you're oldschool, email uscontact@channelfourteen.com linux@channelfourteen.com --- 

This week on BSDNow! We've got Netflix + FreeBSD news to discuss, always a crowd pleaser, that plus EuroBSDCon is just around the corner. Stick around for your place This episode was brought to you by Headlines Protecting Netflix Viewing Privacy at Scale, with FreeBSD (http://techblog.netflix.com/search/label/FreeBSD) This blog post from Netflix tells the story of how Netflix developed in-kernel TLS to speed up delivery of video via HTTPS Since the beginning of the Open Connect program we have significantly increased the efficiency of our OCAs - from delivering 8 Gbps of throughput from a single server in 2012 to over 90 Gbps from a single server in 2016. We contribute to this effort on the software side by optimizing every aspect of the software for our unique use case - in particular, focusing on the open source FreeBSD operating system and the NGINX web server that run on the OCAs. In the modern internet world, we have to focus not only on efficiency, but also security. There are many state-of-the-art security mechanisms in place at Netflix, including Transport Level Security (TLS) encryption of customer information, search queries, and other confidential data. We have always relied on pre-encoded Digital Rights Management (DRM) to secure our video streams. Over the past year, we've begun to use Secure HTTP (HTTP over TLS or HTTPS) to encrypt the transport of the video content as well. This helps protect member privacy, particularly when the network is insecure - ensuring that our members are safe from eavesdropping by anyone who might want to record their viewing habits. The goal is to ensure that your government, ISP, and wifi sniffing neighbour cannot tell which Netflix videos you are watching Netflix Open Connect serves over 125 million hours of content per day, all around the world. Given our scale, adding the overhead of TLS encryption calculations to our video stream transport had the potential to greatly reduce the efficiency of our global infrastructure. We evaluated available and applicable ciphers and decided to primarily use the Advanced Encryption Standard (AES) cipher in Galois/Counter Mode (GCM), available starting in TLS 1.2. We chose AES-GCM over the Cipher Block Chaining (CBC) method, which comes at a higher computational cost. The AES-GCM cipher algorithm encrypts and authenticates the message simultaneously - as opposed to AES-CBC, which requires an additional pass over the data to generate keyed-hash message authentication code (HMAC). CBC can still be used as a fallback for clients that cannot support the preferred method. All revisions of Open Connect Appliances also have Intel CPUs that support AES-NI, the extension to the x86 instruction set designed to improve encryption and decryption performance. We needed to determine the best implementation of AES-GCM with the AES-NI instruction set, so we investigated alternatives to OpenSSL, including BoringSSL and the Intel Intelligent Storage Acceleration Library (ISA-L). Netflix and NGINX had previously worked together to improve our HTTP client request and response time via the use of sendfile calls to perform a zero-copy data flow from storage (HDD or SSD) to network socket, keeping the data in the kernel memory address space and relieving some of the CPU burden. The Netflix team specifically added the ability to make the sendfile calls asynchronous - further reducing the data path and enabling more simultaneous connections. However, TLS functionality, which requires the data to be passed to the application layer, was incompatible with the sendfile approach. To retain the benefits of the sendfile model while adding TLS functionality, we designed a hybrid TLS scheme whereby session management stays in the application space, but the bulk encryption is inserted into the sendfile data pipeline in the kernel. This extends sendfile to support encrypting data for TLS/SSL connections. We tested the BoringSSL and ISA-L AES-GCM implementations with our sendfile improvements against a baseline of OpenSSL (with no sendfile changes), under typical Netflix traffic conditions on three different OCA hardware types. Our changes in both the BoringSSL and ISA-L test situations significantly increased both CPU utilization and bandwidth over baseline - increasing performance by up to 30%, depending on the OCA hardware version. We chose the ISA-L cipher implementation, which had slightly better results. With these improvements in place, we can continue the process of adding TLS to our video streams for clients that support it, without suffering prohibitive performance hits. If you would like more detail, check out the papers from AsiaBSDCon 2015 (https://people.freebsd.org/~rrs/asiabsd_2015_tls.pdf) and the updated one from 2016 (https://people.freebsd.org/~rrs/asiabsd_tls_improved.pdf) *** OpenBSD on HP Stream 7 (http://www.tedunangst.com/flak/post/OpenBSD-on-HP-Stream-7) Recent events have rocked the mobile computing world to its core. OpenBSD retired the zaurus port, leaving users in desperate need of a new device. And not long before that, Microsoft released the Anniversary Update to Windows 10, but with free space requirements such that it's nigh impossible to install on cheap 32GB eMMC equipped devices such as the HP Stream series, leaving users searching for a new lightweight operating system. With necessity as both mother and father, the scene is set for a truly epic pairing. OpenBSD on the HP Stream 7. The HP Stream line is a series of budget computers in a couple form factors. The Stream 11 is a fairly typical netbook. However, the Stream 7 and 8 are tablets. They look like cheap Android devices, but inside the case, they're real boys, er PCs, with Intel Atom CPUs. To install OpenBSD on such a device, we need a few parts. Obviously, the tablet itself. There's a dearth of ports on these things, but there is a micro USB port. Attaching anything useful requires an OTG “on the go” cable that creates a type A port. Attaching more than one useful thing requires a mini hub. And completing the install requires one each USB stick, keyboard, and network adapter. First, we need to prep the machine to boot from USB. Actually, before doing anything, make sure you have a full charge. It's going to be battery only from here on out. Plug everything in. Flash drive, keyboard, and network into the hub, hub into the OTG cable, cable into the port on top of the Stream. Turn on the machine while holding the volume down button. This launches a mini menu from which we can enter the BIOS. There's a little on screen keyboard in the corner, so this can be done even without a keyboard attached, but the USB keyboard should work. We need to change two settings in the boot section. First, turn off secure boot. Second, switch boot order to prefer USB. Save and exit. The first reboot reveals a confirmation screen checking that we really want to disable secure boot. We must enter a PIN and press enter. Enter the PIN shown on the screen and press enter. And we are go. Then boot up OpenBSD from the USB drive Ted then works there a number of kernel panics and device driver issues, but after disabling ACPI and IntelDRM, the device boots OpenBSD. Of course, there's no X at this point. And definitely no touch screen. And no internal networking. However, by keeping our USB hub attached, we can drive the console and access the network. At least until the battery is depleted, even if we have no way of knowing how long that will be since we disabled all the ACPI devices, which also means no suspend or resume. With some xorg.conf hacking, he did get Xorg working *** DragonflyBSD steps towards base LibreSSL (http://lists.dragonflybsd.org/pipermail/commits/2016-September/624493.html) Project: DragonFlyBSD / Switch base to use private LibreSSL libraries (http://freshbsd.org/commit/dfbsd/304ca408000cd34559ef5319b4b5a6766d6eb35b) DragonFly BSD adopts uses of LibreSSL (http://undeadly.org/cgi?action=article&sid=20160911231651) The number of projects beginning to switch over to LibreSSL is growing and it appears we can now throw DragonFly into that camp. Following something that sounds vaguely familiar (Allan!) DFLY is now creating “private” LibreSSL libraries which are only linked against by base system binaries. For the moment OpenSSL is still built, primarily so that various ports and 3rd party apps can continue to function as before. A NO_OPENSSL option has also been added, but doesn't really do much (yet), since it'll still build and install headers / libraries even if set. *** OpenBSD g2k16 Hackathon g2k16 Hackathon Report: Antoine Jacoutot on Binary Patches (http://undeadly.org/cgi?action=article&sid=20160911012316) g2k16 Hackathon Report: Matthieu Herrb on xenodm (http://undeadly.org/cgi?action=article&sid=20160911231712) g2k16 Hackathon Report: Vincent Gross on iked(8), armv7 and sys/netinet[6] (http://undeadly.org/cgi?action=article&sid=20160911000337) g2k16 Hackathon Report: Florian Obser on httpd, networking, acme-client, and more (http://undeadly.org/cgi?action=article&sid=20160911000052) g2k16 Hackathon Report: Jasper Lievisse Adriaanse on ddb(4) and more (http://undeadly.org/cgi?action=article&sid=20160909012520) g2k16 Hackathon Report: Christian Weisgerber on gettext progress, RTC work, removing kernel cruft (http://undeadly.org/cgi?action=article&sid=20160908002430) g2k16 Hackathon Report: Brent Cook on Chromebooks, crypto, and more (http://undeadly.org/cgi?action=article&sid=20160907131655) g2k16 Hackathon Report: Ted Unangst on doas, signify, code removal (http://undeadly.org/cgi?action=article&sid=20160906230610) g2k16 Hackathon Report: Marc Espie on package signing evolution (http://undeadly.org/cgi?action=article&sid=20160905235911) g2k16 Hackathon Report: Adam Wolk on ports, wireless drivers and more (http://undeadly.org/cgi?action=article&sid=20160906004915) g2k16 Hackathon Report: Mike Larkin on vmm + vmd progress (http://undeadly.org/cgi?action=article&sid=20160905134009&mode=expanded) *** News Roundup OpenBSD (with encrypted softraid) on the Chromebook Pixel (https://jcs.org/notaweblog/2016/08/26/openbsd_chromebook/) Looking for a Laptop to make your OpenBSD road-warrior? If so, we have a great blog tutorial on getting OpenBSD setup on the Chromebook Pixel with encrypted softraid! Author Joshua Stein gives us a very verbose look at how to install and dial-in the laptop perfectly. But first for those wondering about the hardware in the pixel: The Chromebook Pixel LS (2015) has an Intel Core i7 processor (Broadwell) at 2.4Ghz, 16Gb of RAM, a 2560x1700 400-nit IPS screen (239ppi), and Intel 802.11ac wireless. It has a Kingston 64Gib flash chip, of which about 54Gib can be used by OpenBSD when dual-booting with a 1Gb Chrome OS partition. Due to this being a chromebook with seaBIOS, some manual key-press trickery will be required to initially get the OpenBSD Installer up and running. From here you'll want to pay special close attention to the disk partitioning. In particular Joshua will show us how to shrink the existing encrypted /home that ChromeOS uses, keeping the dual-boot intact. This will become important if you ever plan on updating the device. From here, we move back to a more traditional setup, but with the added bonus of doing a soft-raid setup. But the fun isn't over yet! If you want to make OpenBSD the default boot, that'll require cracking the lid on the device and removing a special pink write-protect screw. And of course if you want to remove the default splash-screen image, Joshua has you covered as well, although some flashrom magic will be required. At this point you are nearly done. Final details on enabling specific bits of hardware are discussed. Most things work, apart from Audio and Bluetooth as of right now. *** doas mastery (http://www.tedunangst.com/flak/post/doas-mastery) “doas” mastery - Paging MWL! Our buddy Ted Unangst has written up a great ‘mastery' guide of the doas command, which can come in handy if you are among the un-initiated in doas land. UNIX systems have two classes of user, the super user and regular users. The super user is super, and everybody else is not. This concentration of power keeps things simple, but also means that often too much power is granted. Usually we only need super user powers to perform one task. We would rather not have such power all the time. Think of the responsibility that would entail! Like the sudo command, doas allows for subdivision of super user privileges, granting them only for specific tasks. He starts with the basic doas.conf setup, which starts with an empty config file The doas config is much like a pf ruleset, the default is to block everything > We add the root rule second because doas evaluates rules in a last match manner. root is in the wheel group, so the first rule will match, and then we need to override that with a second rule. Remember to always start with general rules, then make them more specific. *** iXsystems iXsystems to host MeetBSD (https://www.ixsystems.com/blog/ixsystems-host-meetbsd-california-2016-uc-berkeley/) FreeBSD Foundation Welcomes New Board Members New Board Members (https://www.freebsdfoundation.org/blog/freebsd-foundation-welcomes-new-board-members/) The FreeBSD Foundation has added two new board members Interview with Kylie Liang (https://www.freebsdfoundation.org/blog/new-board-member-interview-kylie-liang/) Kylie will focus on representing FreeBSD at conferences and businesses in China I live in China. There, I can act as a bridge between Chinese companies and the FreeBSD community to help drive FreeBSD adoption. Through my leadership role in the FreeBSD Foundation, I will help promote FreeBSD in China and also represent the Foundation at conferences and events in my region. Kylie leads the team the ensures FreeBSD runs well on Hyper-V and Azure, including providing commercial support for customers who run FreeBSD or FreeBSD based appliances on the Azure Cloud I joined Microsoft and started to lead the project called FreeBSD Integration Service to get FreeBSD running well on Hyper-V and Azure. To promote our work and to understand the FreeBSD ecosystem, I started to participate in FreeBSD events where I was inspired by this technical community. Interview with Philip Paeps (https://www.freebsdfoundation.org/blog/new-board-member-interview-philip-paeps/) Philip started with FreeBSD in the early 2000s and got his commit bit in 2004 The patches I submitted to make ACPI and input devices work on that laptop led to a src commit bit in 2004. While I haven't worked on ACPI or input devices since, I have been contributing to different areas of the kernel. Taking up maintainership of some ports I cared about also got me a ports commit bit after some time. Philip will continue to help run EuroBSDCon, but is also spreading the word about FreeBSD in India and Africa Primarily, I think I can be useful! I attend (and organize) a number of conferences around the world every year, particularly in regions that have a mostly “stealthy” FreeBSD community. While I clearly don't need to be on the FreeBSD Foundation board to advocate for FreeBSD, joining as a director will provide an additional asset when working in areas of the world where organizational affiliations are meaningful. Philip has also developed network drivers and various other bits and pieces, and has extensive experience working with and for hardware vendors and appliance vendors Despite intending to eventually contribute their code to the FreeBSD Project as open source, many hardware vendors still find it very difficult to engage directly with the FreeBSD development community. The Foundation helps bridge that gap and helps facilitate collaboration between commercial vendors and the FreeBSD community. I hope to make FreeBSD more visible in regions of the world where it is historically under-represented. I expect I will be attending even more conferences and getting myself invited to even more organizations. more, less, and a story of typical Unix fossilization (https://utcc.utoronto.ca/~cks/space/blog/unix/MoreAndUnixFossilization) Chris Siebenmann from the University of Toronto digs into the history of the difference between ‘less' and ‘more' In the beginning, by which we mean V7, Unix didn't have a pager at all. That was okay; Unix wasn't very visual in those days, partly because it was still sort of the era of the hard copy terminal. Then along came Berkeley and BSD. People at Berkeley were into CRT terminals, and so BSD Unix gave us things like vi and the first pager program, more (which showed up quite early, in 3BSD, although this isn't as early as vi, which appears in 2BSD). Calling a pager more is a little bit odd but it's a Unix type of name and from the beginning more prompted you with '--More--' at the bottom of the screen. All of the Unix vendors that based their work on BSD Unix (like Sun and DEC) naturally shipped versions of more along with the rest of the BSD programs, and so more spread around the BSD side of things. However, more was by no means the best pager ever; as you might expect, it was actually a bit primitive and lacking in features. So fairly early on Mark Nudelman wrote a pager with somewhat more features and it wound up being called less as somewhat of a joke. In a sane world, Unix vendors would have either replaced their version of more with the clearly superior less or at least updated their version of more to the 4.3 BSD version. Maybe less wouldn't have replaced more immediately, but certainly over say the next five years, when it kept on being better and most people kept preferring it when they had a choice.” + “This entire history has led to a series of vaguely absurd outcomes on various modern Unixes. On Solaris derivatives more is of course the traditional version with source code that can probably trace itself all the way back to 3BSD, carefully updated to SUS compliance. Solaris would never dream of changing what more is, not even if the replacement is better. Why, it might disturb someone. Oddly, FreeBSD has done the most sensible thing; they've outright replaced more with less. There is a /usr/bin/more but it's the same binary as less and as you can see the more manpage is just the less manpage. OpenBSD has done the same thing but has a specific manpage for more instead of just giving you the less manpage. So, now you can see why I say that less is more, or more, or both, at several levels. less is certainly more than more, and sometimes less literally is more (or rather more is less, to put it the right way around). Beastie Bits PC-BSD listed in the top 8 'best' alternatives to Windows 10 (http://www.computerworlduk.com/galleries/operating-systems/-free-alternatives-windows-10-3639433/) Creating a quick DNS server with a Rapsberry Pi2 and FreeBSD 11.0-RC1 (http://bsdimp.blogspot.co.uk/2016/08/creating-quick-dns-server-with.html) Dual Boot OpenBSD and Linux + UEFI (https://bsdlaptops.wordpress.com/2016/03/07/vaio-pro-11-part-2/) DesktopBSD 2.0 various versions available (Gnome, Lumina, KDE, LXDE) (http://desktopbsd.boards.net/board/10/announcements) FreeBSD gets new ZFS features including: Compressed ARC (https://svnweb.freebsd.org/base?view=revision&revision=305323) and ZFS Allocation Throttle (https://svnweb.freebsd.org/base?view=revision&revision=305331) One Floppy NetBSD Distribution (https://github.com/user340/fdgw2) A Compendium of BUGs (https://github.com/q5sys/BUGtracker) Feedback/Questions Galahad - OpenBSD X setup (http://pastebin.com/b7W6NHqs) Tang - Subtitles (http://pastebin.com/P4MUs3Pa) Ivan - Zpool Options (http://pastebin.com/LQ8yTp0G) Brad - Replication Issue (http://pastebin.com/XTK5gXMU) MJ - HBA (http://pastebin.com/TdYTMSj9) ***

This time we talk about ... stuff? andstuffpodcast@gmail.com @andstuffpodcast on twitter soyeahandstuff.podbean.com Walker decided to get a TWSBI Eco after reading a blog post by David Rea going into a bit of physics and materials science. Cameron is mildly interested in pens, but couldn't do a whole podcast about it like "those guys". This primer on nibs explains what a "stub nib" is. Despite hearing about them many times, this blog post by Brad Dowdy is probably what made Walker decide to actually look into getting a pen with one. Nathan of Noodler's ink has a youtube video up about the story behind the "Charlie" eyedropper pen that Walker talked about. Cameron wants to get more into uploading videos. Looks like he did since we recorded. Here's a link to Walker's old shredder unboxing video. Look at all the potential discussion topics on wikipedia to use during unboxing videos! Walker found DIY cat tree/condo inspiration here. The kind of "fake joinery" Walker is doing is mostly inspired by the Mere Mortals Workbench designed by Steve Ramsey, although lots of people use this technique. Here's an article for further reading on types of twine. Here's another one. Walker is mixing other people's old forgotten tracks that he found on a Zoom R16 multi-track recorder. Here's Bob Clagget's first Arduino Programming Tutorial video on the I Like To Make Stuff channel. And here is Making It, the podcast he does. More information about arduino can be found on the website. This is what Process Controls is. Controls engineers use something called SCADA. Walker will soon be working with slivers. Arch Linux and its wonderful online documentation can be found here. When using GNU/Linux on a computer Cameron usually uses Lubuntu, a spin of Ubuntu, and Walker usually uses Debian, but sometimes uses Fedora. The desktop environment is the part of many GNU/Linux systems that actually determines what things you see on the screen. Cameron uses LXDE, while Walker is all about XFCE. Here is the Bakelite video on Periodic Videos. Love this channel. Some tracker-based music programs for linux are qtractor and lmms. Walker can't remember which one he used to make the And Stuff Opening Theme Song. Amsynth is the softsynth Cameron has been experimenting with. Walker recommends using a kernel with the PREEMPT_RT patch for music production. He uses a kernel for Fedora that comes patched from Planet CCRMA at Stanford University. It seems that similar things are available for Ubuntu. The programs Walker rattles off that he uses in music production are Jack, Whysynth, Hexter, Alsamodularsynth. Thanks for listening!

Voltamos a nos reunir para gravar mais um episódio do Opencast, desta vez a publicação atrasou devido a muito trabalho e atraso na data de gravação causado por falhas no próprio hangout. Neste episódio Ivan, Og Maciel, Aprígio Simões, Diego e Rudinei tentamos comentar alguns acontecimentos importantes que foram notícia no mundo do software livre. Entre eles estão o FISL 14, onde o Diego e o Rudinei estavam presentes, Fedora 19 que pode explodir a cabeça de alguns e o Firefox OS. Além disso, também falamos sobre o projeto Cauã, mudança de licença do MySQL, mudança do LXDE para Qt e sobre uma declaração da ABES sobre o uso de software livre. Links do episódio Mural de usuários convertidos no FISL 14 MySQL troca GPL por licença proprietária MySQL reconhece erro na troca da licença Fedora 19 LXDE considera migração para Qt ABES lamenta avanço de países que abraçaram o software livre Projeto Cauã Firefox OS Sistema Operacional do PS4 é baseado no Free BSD Governo do Rio Grande do Sul prefere ODF Microsoft ajuda a NSA Intel também ajuda a nos espionar 1 Intel também ajuda a nos espionar 2 Se você preferir, pode assistir ao vídeo da gravação do Opencast. O vídeo está quase sem edição da conversa, apenas retirada a parte inicial onde não falamos nada de importante. É até interessante para compararem como fica o trabalho pós edição. Assistir no Youtube Twitter: @tecnologiaabert Facebook: http://www.facebook.com/tecnologiaaberta Google+: Tecnologia Aberta Youtube: Tecnologia Aberta --- Send in a voice message: https://anchor.fm/opencast/message

After our usual jaunt through the tech news of the week, Chris tells us of the love/hate relationship he developed with the LXDE windowing system.

Olá pessoal! Foi com um enorme pezar que eu recebi a notícia sobre o falecimento de André Gondim, uma figura do software livre Brasileiro que, infelizmente, nos deixou na semana passada... O meu relacionamento com o André começou em 2005 quando eu ainda administrava a equipe de traduções do Ubuntu Brasil. Assim como o Fábio Nogueira e André Noel, pessoas que eventualmente também ocuparam o cardo de coordenador desta equipe, o André Gondim foi uma das pessoas com quem eu tive o prazer de trabalhar e instruir no processo de traduções. Durante o nosso dia-a-dia, vi o trabalho e dedicação que ele sempre trazia e pude acompanhar o seu desenvolvimento e crescimento dentro da equipe. Mesmo depois que eu parei de contribuir com o Ubuntu e parti para traduções para o GNOME, Xfce e LXDE, com a ajuda do André foi possível sincronizar o trabalho entre as equipes e assim garantir que o Ubuntu tivesse uma tradução de qualidade e ao mesmo tempo respeitar o trabalho dos tradutores das equipes GNOME, etc, etc.