Podcasts about Tmux

This show has been flagged as Explicit by the host. table td.shrink { white-space:nowrap } hr.thin { border: 0; height: 0; border-top: 1px solid rgba(0, 0, 0, 0.1); border-bottom: 1px solid rgba(255, 255, 255, 0.3); } New hosts Welcome to our new host: SolusSpider. Last Month's Shows Id Day Date Title Host 4240 Fri 2024-11-01 The First Doctor, Part 1 Ahuka 4241 Mon 2024-11-04 HPR Community News for October 2024 HPR Volunteers 4242 Tue 2024-11-05 Interview with Lorenzo 'kelset' Sciandra Ken Fallon 4243 Wed 2024-11-06 Hand Warmer, long term product review MrX 4244 Thu 2024-11-07 Two methods of digitizing photos. Henrik Hemrin 4245 Fri 2024-11-08 What's in my bag? Trey 4246 Mon 2024-11-11 Bytes, Pages and Screens Lee 4247 Tue 2024-11-12 Installing GuixSD--Part Deux Rho`n 4248 Wed 2024-11-13 Millie Perkins Ken Fallon 4249 Thu 2024-11-14 Audio Streams on the Command Line Kevie 4250 Fri 2024-11-15 Playing Civilization IV, Part 3 Ahuka 4251 Mon 2024-11-18 Dave and MrX turn over a new leaf Dave Morriss 4252 Tue 2024-11-19 Privacy is not hiding Some Guy On The Internet 4253 Wed 2024-11-20 A brief introduction of myself Kinghezy 4254 Thu 2024-11-21 Cake Money Money Cake Money Money Cake! operat0r 4255 Fri 2024-11-22 What is on My Podcast Player 2024, Part 1 Ahuka 4256 Mon 2024-11-25 Birds of a Feather Talk at OLF 2024 Thaj Sara 4257 Tue 2024-11-26 Movie review: The Artifice Girl Kevie 4258 Wed 2024-11-27 Introduction and History of Using Computers SolusSpider 4259 Thu 2024-11-28 Why digitize photos Henrik Hemrin 4260 Fri 2024-11-29 The Golden Age Ahuka Comments this month These are comments which have been made during the past month, either to shows released during the month or to past shows. There are 61 comments in total. Past shows There are 21 comments on 17 previous shows: hpr0870 (2011-12-02) "Computer Memories" by Deltaray. Comment 3: SolusSpider - Peter Paterson on 2024-11-29: "Commonality on Deltaray's computer experiences" hpr1322 (2013-08-27) "Kevin O'Brien - Ohio LinuxFest 2013" by Ken Fallon. Comment 1: SolusSpider - Peter Paterson on 2024-11-26: "Attended OLF2013" hpr1642 (2014-11-18) "Frist Time at Oggcamp" by Al. Comment 2: SolusSpider - Peter Paterson on 2024-11-27: "Al at Oggcamp - 10 years later" hpr1890 (2015-10-30) "A short walk with my son" by thelovebug. Comment 4: SolusSpider - Peter Paterson on 2024-11-11: "Comment on A short walk with my son" hpr2503 (2018-03-07) "My journey into podcasting" by thelovebug. Comment 3: SolusSpider - Peter Paterson on 2024-11-18: "Comment on TheLoveBug journey into podcasting." hpr2673 (2018-10-31) "Urandom - Ohio Linux Fest 2-18 Podcaster Roundtable" by Thaj Sara. Comment 1: SolusSpider - Peter Paterson on 2024-11-26: "Wonderful OLF Podcasters Banter" hpr3315 (2021-04-16) "tesseract optical character recognition" by Ken Fallon. Comment 2: SolusSpider - Peter Paterson on 2024-11-28: "Tessaract OCR User" Comment 3: SolusSpider - Peter Paterson on 2024-11-29: "Spelling of tesseract" hpr3998 (2023-11-29) "Using open source OCR to digitize my mom's book" by Deltaray. Comment 3: SolusSpider - Peter Paterson on 2024-11-29: "Experience with Tesseract OCR software" hpr4106 (2024-04-29) "My tribute to feeds" by Henrik Hemrin. Comment 1: SolusSpider - Peter Paterson on 2024-11-27: "New(ish) to Feeds" Comment 2: Henrik Hemrin on 2024-11-29: "Thanks for feedback" hpr4129 (2024-05-30) "How I found Hacker Public Radio" by Henrik Hemrin. Comment 1: SolusSpider - Peter Paterson on 2024-11-27: "My own story of finding HPR" hpr4132 (2024-06-04) "Urandom talks about the future of HPR" by Thaj Sara. Comment 4: SolusSpider - Peter Paterson on 2024-11-18: "Comment on Urandom talks about the future of HPR" hpr4195 (2024-08-30) "Hacking HPR Hosts" by Ken Fallon. Comment 2: SolusSpider - Peter Paterson on 2024-11-29: "Another comment for Ken - he hacked this host" hpr4200 (2024-09-06) "Intro to Doctor Who" by Ahuka. Comment 5: SolusSpider - Peter Paterson on 2024-11-09: "Comment on Introduction To Doctor Who" hpr4220 (2024-10-04) "How Doctor Who Began" by Ahuka. Comment 1: SolusSpider - Peter Paterson on 2024-11-11: "Comment on How Doctor Who Began" hpr4233 (2024-10-23) "OggCamp 2024 Day 1" by Ken Fallon. Comment 1: @geospart on 2024-11-09: "Nice" hpr4236 (2024-10-28) "History of Nintendo" by Lochyboy. Comment 3: SolusSpider - Peter Paterson on 2024-11-10: "Comment on History of Nintendo" Comment 4: John Curwood - blindape on 2024-11-20: "Virtual Boy" hpr4238 (2024-10-30) "Snaps are better than flatpaks" by Some Guy On The Internet. Comment 2: Elliot B on 2024-11-01: "Snaps are the least worst" Comment 3: mpardo on 2024-11-02: "Snaps are indeed better that Flatpaks" This month's shows There are 40 comments on 16 of this month's shows: hpr4240 (2024-11-01) "The First Doctor, Part 1" by Ahuka. Comment 1: Kevie on 2024-10-31: "Keep them coming"Comment 2: Kevin O'Brien on 2024-11-02: "More to come"Comment 3: Ken Fallon on 2024-11-07: "Daleks" hpr4241 (2024-11-04) "HPR Community News for October 2024" by HPR Volunteers. Comment 1: ClaudioM on 2024-11-04: "Commentary on Ep. 4231 (Tmux+dd+FreeBSD)"Comment 2: Torin Doyle on 2024-11-10: "Hunting, Buzzing"Comment 3: Dave Morriss on 2024-11-14: "Buzzing?"Comment 4: Dave Lee (thelovebug) on 2024-11-16: "Dave's buzzing"Comment 5: Torin Doyle on 2024-11-18: "Re: Buzzing (more like a hum) in the audio for Dave Morriss."Comment 6: Dave Morriss on 2024-11-18: "The buzzing of the brain" hpr4244 (2024-11-07) "Two methods of digitizing photos." by Henrik Hemrin. Comment 1: Henrik Hemrin on 2024-11-07: "Clarification equipment for repro photo"Comment 2: Ken Fallon on 2024-11-07: "What hardware are you using"Comment 3: Henrik Hemrin on 2024-11-07: "Response to Ken"Comment 4: Charles in NJ on 2024-11-08: "Missed this show because feed is broken"Comment 5: Ken Fallon on 2024-11-08: "Bug Report"Comment 6: Ken Fallon on 2024-11-09: "Please send me your version of bashpodder" hpr4245 (2024-11-08) "What's in my bag?" by Trey. Comment 1: men Fallon on 2024-11-07: "Backdoors and breaches" hpr4246 (2024-11-11) "Bytes, Pages and Screens" by Lee. Comment 1: Ken Fallon on 2024-11-07: "Terry Pratchett"Comment 2: Torin Doyle on 2024-11-18: "Podcasts, Books, TV" hpr4248 (2024-11-13) "Millie Perkins" by Ken Fallon. Comment 1: Kevie on 2024-11-13: "A fantastic Oggcamp Talk" hpr4249 (2024-11-14) "Audio Streams on the Command Line" by Kevie. Comment 1: Ken Fallon on 2024-11-07: "Great Tips"Comment 2: SolusSpider - Peter Paterson on 2024-11-14: "Comment on Audio Streams on the Command Line"Comment 3: Jan on 2024-11-14: "Just Thanks"Comment 4: Henrik Hemrin on 2024-11-29: "Command Line" hpr4251 (2024-11-18) "Dave and MrX turn over a new leaf" by Dave Morriss. Comment 1: FXB on 2024-11-23: "using wttr.in"Comment 2: Dave Morriss on 2024-11-23: "Re: wttr.in" hpr4252 (2024-11-19) "Privacy is not hiding" by Some Guy On The Internet. Comment 1: Tim J on 2024-11-20: "Big Tech is Watching You" hpr4253 (2024-11-20) "A brief introduction of myself" by Kinghezy. Comment 1: SolusSpider - Peter Paterson on 2024-11-20: "Comment on kinghezy's introduction show hpr4253" hpr4256 (2024-11-25) "Birds of a Feather Talk at OLF 2024" by Thaj Sara. Comment 1: Ken Fallon on 2024-11-21: "Suspense"Comment 2: Thaj on 2024-11-25: "Resolution"Comment 3: Windigo on 2024-11-26: "Future shows"Comment 4: Torin Doyle on 2024-11-30: "OLF?" hpr4257 (2024-11-26) "Movie review: The Artifice Girl" by Kevie. Comment 1: SolusSpider - Peter Paterson on 2024-11-26: "Also watched The Atifice Girl" hpr4258 (2024-11-27) "Introduction and History of Using Computers" by SolusSpider. Comment 1: Dave Lee (thelovebug) on 2024-11-18: "Welcome to the HPR family"Comment 2: present_arms on 2024-11-19: "This Podcast hpr4258 :: Introduction and History of Using Computers"Comment 3: archer72 on 2024-11-27: "Welcome to HPR"Comment 4: Henrik Hemrin on 2024-11-29: "Welcome as HPR host!" hpr4259 (2024-11-28) "Why digitize photos" by Henrik Hemrin. Comment 1: SolusSpider - Peter Paterson on 2024-11-28: "The thoughts behind digitizing photos"Comment 2: Henrik Hemrin on 2024-11-29: "Thanks for your comment" hpr4272 (2024-12-17) "Embed Mastodon Threads" by hairylarry. Comment 1: Ken Fallon on 2024-11-28: "Wayne Myers ?? Where did I hear that name before ?" hpr4320 (2025-02-21) "Switching my Mastodon account" by Ahuka. Comment 1: Ken Fallon on 2024-11-25: "Target Audience of 1" Mailing List discussions Policy decisions surrounding HPR are taken by the community as a whole. This discussion takes place on the Mail List which is open to all HPR listeners and contributors. The discussions are open and available on the HPR server under Mailman. The threaded discussions this month can be found here: https://lists.hackerpublicradio.com/pipermail/hpr/2024-November/thread.html Events Calendar With the kind permission of LWN.net we are linking to The LWN.net Community Calendar. Quoting the site: This is the LWN.net community event calendar, where we track events of interest to people using and developing Linux and free software. Clicking on individual events will take you to the appropriate web page. Any other business It's been another hectic month here at HPR Towers. As we discussed on the mailing list most of the time was taken by the migration to Mastodon, and the implementation of the mirrors on the Community Content Delivery Network. Some daily stats are been updated on https://hub.hackerpublicradio.org/hpr_ccdn_stats.tsv Summary of the changes to the repo https://repo.anhonesthost.net/HPR Dave updated his tooling for processing shows and they are now available on the Gitea repo. We finally got around to creating the HPR Documentation wiki. Community Content Delivery Network (CCDN) A location to track the deployment of the HPR Community Content Delivery Network, that provides a mirror network for our content. HPR Website Design This is literally in the whiteboard phase of the HPR website redesign. Where we can track Compatibility of the clients subscribed to our feeds. Useful Resources Where we can link to other free culture sites that provide useful services. Requested Topics Where we can track topics that have been requested, and link to shows that addressed them. There is also a list with information about Podcatcher and Podcasting Platform Compatibility. If anyone wants to adopt a player then please do so. The section on Workflow will be changing shortly due to Dave stepping aside, and also the need to distribute to multiple end points. All the processing will happen first, and then all the checks will be done at the same stage just prior to posting. For this to work we need help finding a simple manageable WYSIWYG editor that can produce sane HTML when the host uploads the show. We also need a new system to distribute the files from an origin to all the mirrors. Other changes and fixes. The day of the week is now available on the website. Fixed the RSS feed to show explicit status. Fixed a bug that limited the future feed to just 10 shows. Fixed a typo in the status page. Following feedback, added emphasis about the upcoming two weeks, to the scheduling guidelines. Notable shout out to the people who are promoting HPR and are helping people out with audio issues. Provide feedback on this episode.

This show has been flagged as Explicit by the host. table td.shrink { white-space:nowrap } hr.thin { border: 0; height: 0; border-top: 1px solid rgba(0, 0, 0, 0.1); border-bottom: 1px solid rgba(255, 255, 255, 0.3); } New hosts There were no new hosts this month. Last Month's Shows Id Day Date Title Host 4217 Tue 2024-10-01 Episode 2 - Dirt Simple Photo Gallery hairylarry 4218 Wed 2024-10-02 Crazy Battery Story Swift110 4219 Thu 2024-10-03 Black diamond head lamp and other gear Some Guy On The Internet 4220 Fri 2024-10-04 How Doctor Who Began Ahuka 4221 Mon 2024-10-07 HPR Community News for September 2024 HPR Volunteers 4222 Tue 2024-10-08 Replacing backup batteries in my Kenwood TS940S HF Radio Part 5 MrX 4223 Wed 2024-10-09 Movie review of The Artifice Girl Some Guy On The Internet 4224 Thu 2024-10-10 Auto shop interaction Archer72 4225 Fri 2024-10-11 Chewing the rag with Kristoff and Ken Ken Fallon 4226 Mon 2024-10-14 JAMBOREE and Taco Bell! operat0r 4227 Tue 2024-10-15 Introduction to jq - part 3 Dave Morriss 4228 Wed 2024-10-16 Auditing Audio Files For Youtube Dave Hingley 4229 Thu 2024-10-17 Neurodiversity and Hacking Lee 4230 Fri 2024-10-18 Playing Civilization IV, Part 2 Ahuka 4231 Mon 2024-10-21 Duplicating Multiple USB Flash Drives with DD and Tmux on FreeBSD Claudio Miranda 4232 Tue 2024-10-22 Replacing backup batteries in my Kenwood TS940S HF Radio Part 6 MrX 4233 Wed 2024-10-23 OggCamp 2024 Day 1 Ken Fallon 4234 Thu 2024-10-24 OggCamp 2024 Day 2 Ken Fallon 4235 Fri 2024-10-25 What Is Plain Text Programming? hairylarry 4236 Mon 2024-10-28 History of Nintendo Lochyboy 4237 Tue 2024-10-29 My First OggCamp Experience Kevie 4238 Wed 2024-10-30 Snaps are better than flatpaks Some Guy On The Internet 4239 Thu 2024-10-31 Android Tasker and Automation operat0r Comments this month These are comments which have been made during the past month, either to shows released during the month or to past shows. There are 25 comments in total. Past shows There are 8 comments on 4 previous shows: hpr4208 (2024-09-18) "01 Plain Text Programs" by hairylarry. Comment 3: Beeza on 2024-10-03: "Plaintext Programs" Comment 4: Dave Morriss on 2024-10-04: "Regarding VMS and indexed files" Comment 5: hairylarry on 2024-10-07: "Thanks for the comments" hpr4211 (2024-09-23) "Rapid Fire 1" by operat0r. Comment 1: Sun Yat Babo on 2024-10-25: "neuro diverse film" hpr4213 (2024-09-25) "Making Waves Day 1" by Ken Fallon. Comment 1: dmt on 2024-10-12: "satdump" hpr4216 (2024-09-30) "Down the rabbit hole." by Some Guy On The Internet. Comment 1: Beeza on 2024-10-03: "Good Samaritans" Comment 2: Reto on 2024-10-23: "The humor" Comment 3: Ken Fallon on 2024-10-24: "The View from NL" This month's shows There are 17 comments on 10 of this month's shows: hpr4221 (2024-10-07) "HPR Community News for September 2024" by HPR Volunteers. Comment 1: Dave Morriss on 2024-10-05: "Show notes for the HPR New Years Eve Show 2023-24"Comment 2: brian-in-ohio on 2024-10-07: "best price?" hpr4222 (2024-10-08) "Replacing backup batteries in my Kenwood TS940S HF Radio Part 5" by MrX. Comment 1: Beeza on 2024-10-08: "Old Batteries"Comment 2: MrX on 2024-10-10: "Re Old Batteries" hpr4224 (2024-10-10) "Auto shop interaction" by Archer72. Comment 1: A. Listener on 2024-10-12: "issue with downloading shows" hpr4228 (2024-10-16) "Auditing Audio Files For Youtube" by Dave Hingley. Comment 1: Kevie on 2024-10-26: "Youtube's copyright strikes" hpr4231 (2024-10-21) "Duplicating Multiple USB Flash Drives with DD and Tmux on FreeBSD" by Claudio Miranda. Comment 1: Gumnos on 2024-10-29: "Getting status of dd in OpenBSD"Comment 2: hairylarry on 2024-10-30: "Similarly"Comment 3: ClaudioM on 2024-10-31: "Re: Similarly"Comment 4: ClaudioM on 2024-10-31: "Re: Getting status of dd in OpenBSD" hpr4236 (2024-10-28) "History of Nintendo" by Lochyboy. Comment 1: Steve Barnes on 2024-10-29: "Ahhyes."Comment 2: ClaudioM on 2024-10-31: "Virtual Boy?" hpr4237 (2024-10-29) "My First OggCamp Experience" by Kevie. Comment 1: Peter - SolusSpider on 2024-10-30: "OggCamp Dining Experience" hpr4238 (2024-10-30) "Snaps are better than flatpaks" by Some Guy On The Internet. Comment 1: Trey on 2024-10-30: "Ethernet cable"Comment 2: Elliot B on 2024-11-01: "Snaps are the least worst" hpr4240 (2024-11-01) "The First Doctor, Part 1" by Ahuka. Comment 1: Kevie on 2024-10-31: "Keep them coming" hpr4266 (2024-12-09) "What's the weather?" by Lee. Comment 1: Lee on 2024-10-21: "Errata" Mailing List discussions Policy decisions surrounding HPR are taken by the community as a whole. This discussion takes place on the Mail List which is open to all HPR listeners and contributors. The discussions are open and available on the HPR server under Mailman. The threaded discussions this month can be found here: https://lists.hackerpublicradio.com/pipermail/hpr/2024-October/thread.html Events Calendar With the kind permission of LWN.net we are linking to The LWN.net Community Calendar. Quoting the site: This is the LWN.net community event calendar, where we track events of interest to people using and developing Linux and free software. Clicking on individual events will take you to the appropriate web page. Any other business HPR Updates There has been a lot of activity this month on the Gitea repos with rho`n catching up on outstanding bugs. We also had a lot of changes due to the ongoing Internet Archive outage that is still impacting us. A quick fix was to host the 10 day feed directly from the HPR server, but since then we have made all the media available on the HPR Community Content Delivery Network. We will have three sources but if you meet the requirements for hosting, and wish to help out please get in touch. 24/7 Home Service Fixed IP address Unlimited bandwidth Fast > 500mb/sec upload Large > 1T of storage Permission from your ISP to run a web server Contact information known to the Janitors Optional: UPS We added a html link to the comments page to provide direct feedback from any app that supports it. Eg: gPodder opens Firefox at the comment form. We have consolidated a lot of repositories on Gitea, removing some and moving others. https://repo.anhonesthost.net/HPR Documentation is now available and includes: Community Content Delivery Network (CCDN) A location to track the deployment of the HPR Community Content Delivery Network, that provides a mirror network for our content. HPR Website Design This is literally in the whiteboard phase of the HPR website redesign. Podcatcher and Podcasting Platform Compatibility Where we can track Compatibility of the clients subscribed to our feeds. Useful Resources Where we can link to other free culture sites that provide useful services. Requested Topics Where we can track topics that have been requested, and link to shows that addressed them. Workflow issues. Message from Dave Morriss I am planning to "retire" from the Hacker Public Radio Janitorial Team. I have been helping to administer HPR for over 12 years now. I first offered help to Ken in 2012 in response to an appeal he made. We met at OggCamp in that year, and I joined the Community News recording for episode 1066 in September 2012. My first show was 1091 in October that year. I will turn 75 in December 2024, and am finding that I don't have the energy to do as much as I could when I first joined. I also want to be able to devote more time to the various personal projects I have. I plan to consolidate all my scripts on the HPR Gitea repositories, and document all the processes I have been looking after. I want to have completed the handover by the end of March 2025. I will continue as an HPR host for as long as I can after that. I have had a wonderful 12 years as an HPR Janitor and will always look back on it with great pleasure. Provide feedback on this episode.

Pre-planning and creating your image: Create your image with your preferred disk image creation tool. I used USB Image Tool to create an image from my "golden master" Windows 11 installation thumb drive A. USB Image Tool: https://www.alexpage.de/usb-image-tool Prepare your Tmux session on your Linux or BSD-based system. 'tmux new -s $sessionName' to create a new Tmux session window with a session name of your choice. 'Ctrl-B-"' to create a horizontal split, putting one pane over the other. 'Ctrl-B-%' to create a vertical split, putting one pane next to the other. 'Ctrl-B-UpArrow' or 'Ctrl-B-DownArrow' to move to the pane you want to split if you split the window with a horizontal line. 'Ctrl-B-LeftArrow' or 'Ctrl-B-RightArrow' to move to the pane you want to split if you split the window with a vertical line. https://tmuxcheatsheet.com/ Duplicate 4 USB thumb drives from a disk image within your new, split-paned Tmux session: CHECK DMESG FOR THE CORRECT DEVICE NAME AND WRITE IT DOWN!!! FreeBSD will show dmesg output on TTYv0, or you can use the dmesg command on Linux or BSD. You don't want to end up wiping your system drive! Within your Tmux session: Pane 1: 'dd if=$diskImageName of=/dev/da0 bs=1M status=progress' to begin imaging USB thumb drive #1. Pane 2: 'dd if=$diskImageName of=/dev/da1 bs=1M status=progress' to begin imaging USB thumb drive #2. Pane 3: 'dd if=$diskImageName of=/dev/da2 bs=1M status=progress' to begin imaging USB thumb drive #3. Pane 4: 'dd if=$diskImageName of=/dev/da3 bs=1M status=progress' to begin imaging USB thumb drive #4. 'Ctrl-B-:' to call the Tmux command prompt, followed by 'setw synchronize-panes' to sync the 4 panes to your commands. The primary pane will be highlighted in red, and the secondary panes will copy whatever command it typed into that primary pane. Hit Enter to begin the process on all 4 panes. When the image finishes, you can remove the USB thumbs drives, pop in 4 more, hit the Up arrow on the primary pane to pull up the previous commands on their respective panes, and hit Enter. When in doubt, refer to Step 0!! Repeat as needed. If you need to de-synchronize your Tmux panes, just type 'Ctrl-:' to call the Tmux command prompt, followed by 'setw synchronize-panes' to toggle pane synchronization on and off (or you can use the up arrow at the Tmux command prompt to bring up that previously-typed command). The faster your USB ports and USB thumb drives, the better!

We're excited for Linux laptops, the Rocket Accelerator for Rokchips, and a new programming language for Bash scripts. Then there's the extensible scheduler coming to 6.11 because Torvalds says so, NVIDIA making a move on the upstream kernel, and a bit of a change for ChromeOS. For tips, we have the quake terminal, a tmux environment variable, and an automount command to pick up your missing mounts. See the show notes at https://bit.ly/4esmR1N and enjoy! Host: Jonathan Bennett Co-Hosts: Rob Campbell and David Ruggles Want access to the video version and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

This is a recap of the top 10 posts on Hacker News on May 25th, 2024.This podcast was generated by wondercraft.ai(00:31): Abusing Go's InfrastructureOriginal post: https://news.ycombinator.com/item?id=40474712&utm_source=wondercraft_ai(01:59): Google scrambles to manually remove weird AI answers in searchOriginal post: https://news.ycombinator.com/item?id=40475578&utm_source=wondercraft_ai(03:25): The hikikomori in Asia: A life within four wallsOriginal post: https://news.ycombinator.com/item?id=40475178&utm_source=wondercraft_ai(05:15): Tmux is worse-is-betterOriginal post: https://news.ycombinator.com/item?id=40476410&utm_source=wondercraft_ai(06:50): Mistral Fine-TuneOriginal post: https://news.ycombinator.com/item?id=40473198&utm_source=wondercraft_ai(08:22): Google just updated its algorithm. The Internet will never be the sameOriginal post: https://news.ycombinator.com/item?id=40474202&utm_source=wondercraft_ai(09:49): Publishing AI Slop Is a ChoiceOriginal post: https://news.ycombinator.com/item?id=40474236&utm_source=wondercraft_ai(11:17): Zellij: A terminal workspace with batteries includedOriginal post: https://news.ycombinator.com/item?id=40478188&utm_source=wondercraft_ai(13:00): The Cognitive Design of Tools of Thought (2014) [pdf]Original post: https://news.ycombinator.com/item?id=40474759&utm_source=wondercraft_ai(14:41): Lapis: A Web Framework for LuaOriginal post: https://news.ycombinator.com/item?id=40474165&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

This week, it's a Wine release that fixes an ancient bug, a shiny new Nano with modern bindings, and a breaking bug fixed in VirtualBox. Then NeoFetch is officially retired, Adwaita breaks KDE apps, and run0 vies to replace sude. For tips, we have HyFetch to fill the neofetch gap, cpulimit to keep your system responsive, more tmux setup, and how to tell ping to use ipv4 or ipv6. You can find the show notes at https://bit.ly/3WsR2PD It's another great show, enjoy! Host: Jonathan Bennett Co-Hosts: Rob Campbell, Jeff Massie, and David Ruggles Want access to the video version and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Nvidia continues to amaze, Thunderbird is getting rusty, and Proton is about to go 9.0. Then there's a Flathub redesign, a shiny new QEMU release, and maybe the year of Linux in the car. For tips we have awk, the number and string wrangling do-all tool, more spring cleaning with dpkg, how to get tmux set up just right on a new install, and ydiff for much better diff highlighting. See the show notes at https://bit.ly/3xZHa60 and thanks for coming! Host: Jonathan Bennett Co-Hosts: Jeff Massie, Ken McDonald, and David Ruggles Want access to the video version and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Antes de sumergirnos en las procelosas aguas de enfrentar Zellij con otras herramientas, tengo que aclarar que yo he sido un usuario puntual de tmux. Y si bien, soy usuario de Zellij, prefiero abrir varios terminales en mi escritorio. El objetivo de traerte Zellij, no es otro que el de mostrarte alternativas a las tradiciones herramientas screen y tmux. Dar opciones. Y luego, que cada uno decida cual es la herramienta que mas le interesa o mas le conviene. Pero, que no se diga que no lo he contado. Y es que, en estos últimos tiempos estamos asistiendo a todo un nacimiento de nuevas herramientas, y creo que es muy interesante, darles un vistazo, y tenerlas en consideración. Rust, está consiguiendo renovar nuestro vetusto parque de herramientas. Ahora te toca decidir, si te quedas con tu herramienta preferida o cambias. Mi objetivo es mostrarte Zellij, como alternativa a screen y tmux. Más información, enlaces y notas en https://atareao.es/podcast/558

Antes de sumergirnos en las procelosas aguas de enfrentar Zellij con otras herramientas, tengo que aclarar que yo he sido un usuario puntual de tmux. Y si bien, soy usuario de Zellij, prefiero abrir varios terminales en mi escritorio. El objetivo de traerte Zellij, no es otro que el de mostrarte alternativas a las tradiciones herramientas screen y tmux. Dar opciones. Y luego, que cada uno decida cual es la herramienta que mas le interesa o mas le conviene. Pero, que no se diga que no lo he contado. Y es que, en estos últimos tiempos estamos asistiendo a todo un nacimiento de nuevas herramientas, y creo que es muy interesante, darles un vistazo, y tenerlas en consideración. Rust, está consiguiendo renovar nuestro vetusto parque de herramientas. Ahora te toca decidir, si te quedas con tu herramienta preferida o cambias. Mi objetivo es mostrarte Zellij, como alternativa a screen y tmux. Más información, enlaces y notas en https://atareao.es/podcast/558

DAK and the Golden Age of Gadget Catalogs, FreeBSD 13.2 upgrade to 14.0, Running OpenBSD on Raspberry Pi Zero 2 W, Netgate Releases pfSense CE Software Version 2.7.1, SSH agent forwarding and tmux done right, Some explanations about OpenBSD memory usage, and more NOTES This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/bsdnow) and the BSDNow Patreon (https://www.patreon.com/bsdnow) Headlines DAK and the Golden Age of Gadget Catalogs (https://cabel.com/2023/11/06/dak-and-the-golden-age-of-gadget-catalogs/) FreeBSD 13.2 upgrade to 14.0 – properly detailed and (hopefully) correct way (https://ozgurkazancci.com/freebsd-13-2-upgrade-to-14-0-proper-and-correct-way/) News Roundup Running OpenBSD on Raspberry Pi Zero 2 W (https://www.tumfatig.net/2023/running-openbsd-on-raspberry-pi-zero-2-w/) Netgate Releases pfSense CE Software Version 2.7.1 (https://www.netgate.com/blog/netgate-releases-pfsense-ce-software-version-2.7.1) SSH agent forwarding and tmux done right (https://jmmv.dev/2023/11/ssh-agent-forwarding-and-tmux-done.html) Some explanations about OpenBSD memory usage (https://dataswamp.org/~solene/2023-08-11-openbsd-understand-memory-usage.html) Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

This week's EYE ON NPI is switching it up, with a look at some high-voltage-capable analog switches - Texas Instruments' TMUX821x Flat RON SPST 4-Channel Switches (https://www.digikey.com/en/product-highlight/t/texas-instruments/tmux821x-flat-ron-spst-4-channel-switches). A simple and effective way to switch and control up to 4 x 100V connections with up to 200mA each from any microcontroller or microcomputer. We carry dozens of different switches (https://www.adafruit.com/category/759), and DigiKey stocks easily 50K different switch configurations (https://www.digikey.com/en/products/result?s=N4IgTCBcDaIM4HcCWAXAxgCxAXQL5A0) from push-buttons (https://www.digikey.com/en/products/filter/pushbutton-switches/199) to toggles (https://www.digikey.com/en/products/filter/toggle-switches/201) but all of these require a person to push the button mechanically, whereas the TMUX series will connect and disconnect based on a separate digital signal, as low as 1.8V and as high as 48V. These are often used for switch audio or video, but are also often used in sensor measurement or test equipment. They're not good for power supply switching, and for digital signals there's often other ways of moving signals around, although they are sometimes used for the data lines of bidirectional digital signaling systems like USB. Like mechanical switches, the TI TMUX family of analog switches are 'bidirectional' (https://www.youtube.com/watch?v=z9GRiYPq7LM) - that means you can pass signal from A to B or from B to A. However, unlike mechanical switches there is no, well, mechanical connection. Instead, the switches are created by putting an N-FET and P-FET back-to-back. This means that there is no switch-bounce (https://en.wikipedia.org/wiki/Switch#Contact_bounce) or contact oxidation (https://en.wikipedia.org/wiki/Electrical_contact). Analog switches are pretty magical, and solve design problems that involve moving an analog signal around without having to hand-build a switch on board, but there are a few things to watch out for when 'modeling' how an analog switch varies from a mechanical one! First up, analog switches have fairly low 'Ron' resistance when the analog switch connection is made - on the order of a few ohms - and that is much higher than a mechanical switch. There is also 'very very high resistance, but not an open-circuit' when the analog switch connection is broken - on the order of a few hundred mega-ohms. (https://www.youtube.com/watch?v=n9EklrCrgH8) And don't forget you will need to have positive and negative power supplies beyond the voltages switched. So, if you are trying to switch 24Vpp signal, that ranges from -12V to +12V, you will need to supply them on the VDD and VSS lines. Also these are not electrically isolated, so add a separate opto/digital isolation (https://www.ti.com/isolation/digital-isolators/overview.html) circuitry if you want to keep your microcontroller fully disconnected from any high voltages. But compared to classic jellybean analog switches like the CD4066 ,(https://www.digikey.com/short/jw44n87t) the TI TMUX series of analog switches have improved circuit protections that will keep you from popping your chips (https://www.youtube.com/watch?v=RTPHjhjUl0E) by accident - especially since this series can be used with up to 100V. Check the datasheet for all details, but highlights include: built in pull-down resistors, protection against over/undervoltage as well as out-of-order voltage application, and latch-up immunity. If you're looking to switch up some analog signals on your next design, check out the Texas Instruments' TMUX821x 4-Channel Analog Switch (https://www.digikey.com/short/r3rhn270) family with 3 different configurations of NO/NC. And all are in stock for immediate shipment from DigiKey! Order tonight and by tomorrow morning you will be switchin' and swatchin' with these low Ron SPST analog switches.

A hoy hoy! Our old friend Nick Nisi does his best to bring up TypeScript, Vim & Tmux as many times as possible while we discuss a new batch of web browsers, justify why we like the ones we do & try to figure out what it'd take to disrupt the status quo of Big Browser.

A hoy hoy! Our old friend Nick Nisi does his best to bring up TypeScript, Vim & Tmux as many times as possible while we discuss a new batch of web browsers, justify why we like the ones we do & try to figure out what it'd take to disrupt the status quo of Big Browser.

KBall interviews Nick Nisi about the Pandora's box that is his tooling/developer setup. Starting at the lowest layer of the terminal emulator he uses, they move upwards into command line tools, into Tmux (terminals within terminals!), his epic NeoVim configuration, and finally into the tools he uses for notekeeping and productivity.

KBall interviews Nick Nisi about the Pandora's box that is his tooling/developer setup. Starting at the lowest layer of the terminal emulator he uses, they move upwards into command line tools, into Tmux (terminals within terminals!), his epic NeoVim configuration, and finally into the tools he uses for notekeeping and productivity.

Using tmux, the terminal multiplexer on multiple machines Terminal is ROXTerm Uncheck 'Show Menubar' ROXTerm on Github What is Tmux? Tmux wiki on Github Getting started Tmux Getting Started page on Github Tmux Cheat Sheet & Quick Reference Tmux Cheat Sheet Basic .tmux.conf set -g prefix C-a unbind C-b bind C-a send-prefix setw -g window-status-activity-style "fg=colour27,bg=colour234,none" Remote .tmux.conf set -g prefix C-f unbind C-b bind C-f send-prefix setw -g window-status-activity-style "fg=colour27,bg=colour234,none" Start tmux tmux a -d Split pane horizontal - Prefix + % Split pane vertical - Prefix + " Tmux resurrect Key bindings prefix + Ctrl-s - save prefix + Ctrl-r - restore About This plugin goes to great lengths to save and restore all the details from your tmux environment. Here's what's been taken care of: all sessions, windows, panes and their order current working directory for each pane exact pane layouts within windows (even when zoomed) active and alternative session active and alternative window for each session windows with focus active pane for each window "grouped sessions" (useful feature when using tmux with multiple monitors) programs running within a pane! More details in the restoring programs doc. Optional: restoring vim and neovim sessions restoring pane contents restoring a previously saved environment Installing TPM (Tmux Plugin Manager) , Tmux Resurrect and Tmux Continuum In ~/.tmux/plugins/ git clone https://github.com/tmux-plugins/tpm.git git clone https://github.com/tmux-plugins/tmux-resurrect.git git clone https://github.com/tmux-plugins/tmux-continuum.git In a tmux window prefix + I Installs new plugins from GitHub or any other git repository Refreshes TMUX environment Create a directory ~/.tmux/resurrect/ This is where tmux-resurrect and tmux-continuum saves are located Do nothing and tmux-continuum saves automatically every 15 mins At any time use Prefix + Ctrl-s to save a snapshot of your session To restore a session to the last save before a reboot use Prefix + Ctrl-s Here are the steps to restore to a previous point in time: make sure you start this with a "fresh" tmux instance $ cd ~/.tmux/resurrect/ locate the save file you'd like to use for restore (file names have a stamp) symlink the last file to the desired save file: $ ln -sf last do a restore with tmux-resurrect key: Prefix + Ctrl-r Tmux on laptop tmux_laptop.conf Tmux on remote machine tmux_remote.conf Screenshot

We're back for 2023 with Kito, Danno, and special guest Andres Almiray, Senior Principal Product Manager, Database group, to talk about the latest versions of Andres' JReleaser tool, building CLIs in Java (picocli, JCommander, JCommander, Spring Boot, Quarkus, Micronaut), jban,, Jarviz, AI, whether or not Java is over the hill, http4s, and much more. We Thank DataDog for sponsoring this podcast! https://www.pubhouse.net/datadog Overview Server Side Java   – Accelerate Your Lambda Functions with Lambda SnapStart (https://aws.amazon.com/blogs/aws/new-accelerate-your-lambda-functions-with-lambda-snapstart/)   - Quarkus support for AWS Lambda SnapStart (https://quarkus.io/blog/quarkus-support-for-aws-lambda-snapstart/) IDEs and Tools  - JBang (https://www.jbang.dev/)  - Writing CLIs in Java ()    - picocli (https://github.com/remkop/picocli)    - JCommander (https://jcommander.org/)  - Frameworks that you can use to create CLIs    - Spring Boot Console Apps (https://www.appsdeveloperblog.com/spring-boot-console-application/)    - Quarkus Command Mode Apps (https://quarkus.io/guides/command-mode-reference)    - Micronaut Command Line Applications (https://docs.micronaut.io/1.0.0.M4/guide/index.html#picocli)  - Command Line Interface Guidelines (https://clig.dev/) AI   - Microsoft, GitHub, and OpenAI ask court to throw out AI copyright lawsuit (https://www.theverge.com/2023/1/28/23575919/microsoft-openai-github-dismiss-copilot-ai-copyright-lawsuit) JReleaser   - v1.4.0 released on Dec 29 2022    - Improved Maven deployment support    - New FLAT_BINARY distribution    - Threaded messages in Mastodon    - Buildx support in Docker packager    - New java-archiver  - v1.5.0 (upcoming)    - Environment variables and System properties support    - New Linkedin announcer    - New winget packager for NATIVE_PACKAGE distribution    - Updates and deprecations to CLI flags Jarvis (https://github.com/kordamp/jarviz)  - Jarviz is a JAR file analyzer tool. You can obtain metadata from a JAR such as its manifest, manifest entries, bytecode versions, declarative services, and more. Other  - Github changes checksum algorithm for source archives (https://github.blog/changelog/2023-01-30-git-archive-checksums-may-change/)  - http4s (https://http4s.org/)  - Versioning schemes:    - ChronVer    - Calver    - SemVer    - Java-Module / Java-Version  - Tmux (https://github.com/tmux/tmux/wiki)  - Charm.sh (https://charm.sh/)  - GitHub - shyiko/jabba: (cross-platform) Java Version Manager (https://github.com/shyiko/jabba)  - Snapcraft (https://snapcraft.io/)  - OpenFein (https://github.com/OpenFeign/feign) Picks   - NixOS  (https://nixos.org/)  - Neovim (https://neovim.io/)  - Toot (https://toot.readthedocs.io/en/latest/usage.html) Other Pubhouse Network podcasts  - Breaking into Open Source (https://www.pubhouse.net/breaking-into-open-source)  - OffHeap (https://www.javaoffheap.com/)  - Java Pubhouse (https://www.javapubhouse.com/) Events  - DevNexus 2023 - April 4-6, Atlanta, GA, USA (https://devnexus.com/call-for-papers)  - JCON EUROPE 2023 - June 20-23, Cologne Köln, Germany (https://jcon.one/)  - Gateway Software Symposium Mar 31 - Apr 1, 2023 (https://nofluffjuststuff.com/stlouis)  - Pacific Northwest Software Symposium April 14 - 15, 2023 (https://nofluffjuststuff.com/seattle)  - JPrime - May 30-31st, Sofia, Bulgaria (https://jprime.io/)  - Central Iowa Software Symposium June 9 - 10, 2023 (https://nofluffjuststuff.com/desmoines)  - Lone Star Software Symposium: Austin July 14 - 15, 2023 (https://nofluffjuststuff.com/austin)  - ÜberConf July 18 - 21, 2023 (https://uberconf.com/)  

FreeBSD vs. Linux – Networking, HDMI sound output through TV speakers on FreeBSD 13, Getting started with tmux, Samba Active Directory, OpenIKED 7.2 released, FreeBSD Plasma 5 GUI Install, DHCP server howto in German, and more NOTES This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/bsdnow) and the BSDNow Patreon (https://www.patreon.com/bsdnow) Headlines FreeBSD vs. Linux – Networking (https://klarasystems.com/articles/freebsd-vs-linux-networking/) (Solved), HDMI sound output through TV speakers Freebsd 13 or @4 plus VCHIQ audio patch - Raspberry Pi Forums (https://forums.raspberrypi.com/viewtopic.php?t=343233) News Roundup Getting started with tmux (https://ittavern.com/getting-started-with-tmux/) Samba Active Directory (https://cromwell-intl.com/open-source/samba-active-directory/freebsd-raspberry-pi.html) OpenIKED 7.2 released (http://undeadly.org/cgi?action=article;sid=20221202230711) FreeBSD Plasma 5 GUI Install (https://byte--sized-de.translate.goog/linux-unix/freebsd-kde-plasma-5-als-gui-installieren/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=wapp) Original German Article (https://byte-sized.de/linux-unix/freebsd-kde-plasma-5-als-gui-installieren/) *** Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) ***

Esta semana conoceremos trabajos realmente fascinantes a los que tendremos que volver en más ocasiones. Comenzaremos con el proyecto de Slon y continuaremos con Pamela Z, SineRider, Edouard Ferlet, TMUX y Om Unit. Escuchar audio

We've hit a bump in the road with the NixOS challenge, and share what it might not be great at. Plus, what we didn't cover in our Ubuntu 22.04 review. The one where we don't talk about Ubuntu 22.04 at all. Open a channel to our Lightning Node: 037d284d2d7e6cec7623adbe600450a73b42fb90800989f05a862464b05408df39 Special Guests: Alex Kretzschmar and Martin Wimpress.

BIG NEWS! Steph's expecting a baby boy!

Link to the article: https://dev.to/developertharun/8-ways-to-become-a-better-sre-right-now-8-non-technical-characteristics-to-have-3n4p Link to the YouTube video: https://youtu.be/2drsyhJzcao Subscribe the podcast if you like it! Thanks for listening. Thank you for listening to my Podcast. Follow my podcast if you find it helpful. Check out my other episodes. I talk about programming & software engineering. YouTube: https://youtube.com/c/developerTharun Blog Article on: https://tharunshiv.com Instagram: @developerTharun Dev.to: https://dev.to/developertharun Udemy: https://www.udemy.com/user/tharun-shiv/ LinkedIn: https://linkedin.com/in/tharunshiv

Talking Points Rational Sometimes, X.org just doesn't want to work Esspecially if you are a dumb n00b running Arch The terminal will always be there for you. Applications: My .bashrc: Environment Variables: export EDITOR=nvim export PAGER=most export BROWSER=lynx export XDG_DATA_HOME="$HOME/.local/share" export XDG_CONFIG_HOME="$HOME/.config" PS1: user@hostname:~ (git_branch) $ if [[ $EUID == 0 ]]; then export PS1="[e[1;31m]u[e[m]@[e[0;32m]h[e[m]:w$(__git_ps1) # " else export PS1="[e[1;34m]u[e[m]@[e[0;32m]h[e[m]:w$(__git_ps1) $ " fi Aliases: alias vim=nvim alias play=mpv Productivity ("Window Manager"): tmux Provides an easy way of splitting a tty into various panes Get multiple workspaces for free with CTL+ALT+F{1,2,3,4,5,6,7} All of the tiling window manager, none of the X-it Can set up if [ -t 0 ] && [[ -z $TMUX ]] && [[ $- = *i* ]]; then exec tmux; fi in .bashrc in order to have tmux start/stop with your terminal sessiion. Music: cmus Easy library and playlist management Dead simple to use (with cmus-tutorial) y to yank songs onto a playlist SPA to select a playlist RET to play a song/playlist TAB to switch between panes Pictures: fim Requires user be in the video group for permission to use the Linux framebuffer Radio/Video/single audio files: mpv Can display video in terminal (badly with libcaca) Can actually display video in linux framebuffer (with drm) Can handle all of your somafm files/web-video links Requires youtube-dl for video Podcasts/RSS: newsboat/podboat Orginizes all of your podcasts and RSS feeds into an easy-to-use ncurses interface Can be set up with player "mpv --save-position-on-quit" to save positions on podcasts Very convinent for articles, less so for podcasts Really needs better integration with something like cmus Runner Up: podfox Can be configured with JSON Has better directory structure than podboat, imo Tree based structure vs shove everything in ~ by default Text Editing/Word Processing: neovim/GitX Flavored Markdown/pandoc Clean modal editing Can export to whatever with pandoc Probably not as good as OrgMode if emacs wasn't the HFS+ of text editors Audio Recording/Post-Processing: ffmpeg One alias and three scripts in my .bashrc record: alias record="ffmpeg -f alsa -channels 1 -i hw:1" atrim, top-tail, and anorm: Allows me to quickly spin up a recording and run post processing function atrim() { if [ $1 ]; then local in="$1" else local in="-" fi if [ $2 ]; then local out="$2" else local out="-f nut -" fi if [[ $# > 2 ]]; then echo "atrim: requires 2 or fewer arguments" return 1 fi if [ $2 ]; then echo "atrim: silencing $in and saving to $out..."; fi ffmpeg -i $in -af silenceremove=start_periods=1:stop_periods=-1:start_threshold=-50dB:stop_threshold=-50dB:stop_duration=0.75 $out 2>/dev/null #1>/dev/null if [ $2 ]; then echo "atrim: done"; fi } function top-tail() { local top="$HOME/project/hpr-notes/template/intro-music-slick0-cc0.flac" local tail="$HOME/project/hpr-notes/template/outro-mixed-slick0-manon_fallon-cc0.flac" if [ $1 ]; then local in="$1" else local in="-" fi if [ $2 ]; then local out="$2" else local out="-f nut -" fi if [[ $# > 2 ]]; then echo "hpr-top-tail: requres 2 or fewer arguments" return 1 fi if [ $2 ]; then echo "hpr-top-tail: Topping $in with $top and tailing with $tail..."; fi ffmpeg -i "$top" -i $in -i "$tail" -vn -filter_complex " [0][1]acrossfade=d=1:c1=tri:c2=tri[a01]; [a01][2]acrossfade=d=1:c1=tri:c2=tri" $out 2> /dev/null #1> /dev/null if [ $2 ]; then echo "hpr-top-tail: done"; fi } function anorm() { if [ $1 ]; then local in="$1" else local in="-" fi if [ $2 ]; then local out="$2" else local out="-f nut -" fi if [[ $# > 2 ]]; then echo "anorm: requires 2 or fewer arguments" return 1 fi if [ $2 ]; then echo "anorm: normalizing audio $in and saving to $out..."; fi ffmpeg -i $in $(ffmpeg-lh $in) $out #2> /dev/null 1> /dev/null if [ $2 ]; then echo "anorm: done"; fi } Web Browsing: lynx Fast and easy text based web browsing Can leverage Web 4.0 technologies like Gopher!! Some sites break pretty bad... Email: mutt* I didn't really use email very much when I was living on the terminal and now, since I use protonmail, I don't really have an easy way not to use the webmail. Trying to find a fix to this. Let me know your thoughts! This is the mail client I've heard the most good things about that isn't built into a text editor I can't use Show Notes Important Links: tmux cmus Napalm Lounge by Fat Chance Lester fim mpv youtube-dl newsboat/podboat neovim CommonMark pandoc ffmpeg lynx mutt Resources: atrim.sh top-tail.sh anorm.sh Contact Me Email: izzy leibowitz at pm dot me Mastodon: at blackernel at nixnet dot social

Links from the show:DiegoDev is hiringWhy You Should Not Use Laravel. I've been a developer for over 20 years… | by Beau Beauchamp | Nerd For Tech | Jun, 2021 | MediumCryptocurrency ransom paid in Colonial Pipeline hack mostly recoveredThe encrypted messaging app ANOM was used by organized crime and created by the FBI.Laravel is 10 years old! | Laravel NewsEncrypted phone sting leads to global crackdown on organised crimeOne password allowed hackers to disrupt Colonial Pipeline, CEO tells senators | ReutersEl Salvador becomes the first country to adopt Bitcoin as legal tender / TwitterWhat is Fastly and why did it cause an outage for major websites?This episode of PHPUgly was sponsored by:Cloudways, managed cloud hosting platform built for your PHP projects. Use promo code PHPUGLY and get a $25 credit. https://www.cloudways.com/en/php-hosting.php?id=833038Honeybadger.io - https://www.honeybadger.io/Cloudways, a managed cloud hosting platform built for your PHP projects.If you simply wish to focus on your business, Cloudways is the way to go. They take over server management and security and free up time that you can dedicate to growing your business and acquiring new clients.The Platforms offers a choice of IaaS partners (AWS, Google Cloud, Digitalocean, Linode, and Vultr). In addition, you get a performance-optimized stack, managed backups, and staging environment where you can test your code before pushing it to live servers.Best of all, Composer and Git come pre-installed so you can get your projects up and running quickly.All this power, simplicity, and peace of mind falls right with their brand slogan - Moving Dreams ForwardBe sure to visit https://www.cloudways.com/en/php-hosting.php?id=833038 today. Sign up using the Promo code PHPUgly and get a $25 credit.PHPUgly streams the recording of this podcast live. Typically every Thursday night around 9 PM PT. Come and join us, and subscribe to our Youtube Channel, Twitch, or Periscope. Also, be sure to check out our Patreon Page.Twitter Account https://twitter.com/phpuglyHost:Eric Van JohnsonJohn CongdonTom RideoutStreams:Youtube ChannelTwitchPeriscopePowered by RestreamPatreon PagePHPUgly Anthem by Harry Mack / Harry Mack Youtube Channel

Si no estás habituado al uso de la terminal. Si todavía la terminal te causa respeto. O si, simplemente, la terminal, es una aplicación que no te interesa en absoluto, probablemente pienses que esto de tmux , el multiplexor de la terminal, no es para ti. Puede ser que ahora no, pero ¿quien te dice que mañana no te sea de utilidad?. Es mas, ¿quien te dice que mañana no lo necesites?. ¿Y porque te digo esto? Te tengo que confesar, que hasta hace un par de años, esto de tmux, no me interesaba lo mas mínimo. Es mas, no le veía el más mínimo de los sentidos. Sin embargo, ahora, en determinadas ocasiones, me resulta una herramienta casi imprescindible. No te preocupes, que no te voy a dejar con la incógnita, a lo largo del episodio del podcast te desvelaré la razón. El multiplexor de la terminal. Tmux. ¿Que es un multiplexor de la terminal? Antes que nada es explicarte que es esto de un multiplexor… Se trata de una herramienta que te permite tener varias terminales corriendo en una. Una terminal para gobernarlas a todas. Pero no solo esto, sino que además tienes la opción de desanclar una aplicación de la terminal en la que se está ejecutando, dejándola en segundo plano. Pero además te permite re anclar la aplicación, trayéndola a primer plano para interactuar con ella. Esto, por supuesto lo puedes hacer utilizando procesos en segundo plano como ya te comenté en el episodio 223 del podcast en el que te hablé de procesos en segundo plano. Sin embargo, te permite hacer esto de forma sencilla y te aporta mas funcionalidades. Instalación Como te comentaba anteriormente, tmux, se encuentra en los repositorios de las principales distribuciones, con lo que su instalación es realmente sencilla. Abre un terminal y ejecuta la siguiente instrucción, sudo apt install tmux Configuración Mi recomendación es que antes que te lances a trabajar con tmux, lo configures para que se adapte a tus necesidades. Si no sabes exactamente, cual es tu configuración mas adecuada, te recomiendo que le des un vistazo a mis dotfiles. Aunque sin lugar a dudas lo mas recomendable es que lo configures según tus necesidades. Como verás de mi configuración, tampoco tengo tantas opciones en marcha. Si que he configurado los atajos de teclado que me permite desplazarme entre paneles. Estos atajos de teclado, se corresponde con los movimiento de vim, mas que nada por ser coherente. Además cargo un par de plugins, así como un tema, para dar un poco de color. Por otro lado, la combinación de tecla que divide verticalmente los paneles es Ctrl+b |, y la que lo hace horizontalmente es Ctrl+b -. Lo mas visual y nemotécnico que he podido ver o leer. Y, por último, para sincronizar todos los paneles el atajo de teclado que estoy utilizando es Ctrl+b Ctrl+x ... Más información en las notas del podcast sobre Tmux. El multiplexor de terminal

Si no estás habituado al uso de la terminal. Si todavía la terminal te causa respeto. O si, simplemente, la terminal, es una aplicación que no te interesa en absoluto, probablemente pienses que esto de tmux , el multiplexor de la terminal, no es para ti. Puede ser que ahora no, pero ¿quien te dice que mañana no te sea de utilidad?. Es mas, ¿quien te dice que mañana no lo necesites?. ¿Y porque te digo esto? Te tengo que confesar, que hasta hace un par de años, esto de tmux, no me interesaba lo mas mínimo. Es mas, no le veía el más mínimo de los sentidos. Sin embargo, ahora, en determinadas ocasiones, me resulta una herramienta casi imprescindible. No te preocupes, que no te voy a dejar con la incógnita, a lo largo del episodio del podcast te desvelaré la razón. El multiplexor de la terminal. Tmux. ¿Que es un multiplexor de la terminal? Antes que nada es explicarte que es esto de un multiplexor… Se trata de una herramienta que te permite tener varias terminales corriendo en una. Una terminal para gobernarlas a todas. Pero no solo esto, sino que además tienes la opción de desanclar una aplicación de la terminal en la que se está ejecutando, dejándola en segundo plano. Pero además te permite re anclar la aplicación, trayéndola a primer plano para interactuar con ella. Esto, por supuesto lo puedes hacer utilizando procesos en segundo plano como ya te comenté en el episodio 223 del podcast en el que te hablé de procesos en segundo plano. Sin embargo, te permite hacer esto de forma sencilla y te aporta mas funcionalidades. Instalación Como te comentaba anteriormente, tmux, se encuentra en los repositorios de las principales distribuciones, con lo que su instalación es realmente sencilla. Abre un terminal y ejecuta la siguiente instrucción, sudo apt install tmux Configuración Mi recomendación es que antes que te lances a trabajar con tmux, lo configures para que se adapte a tus necesidades. Si no sabes exactamente, cual es tu configuración mas adecuada, te recomiendo que le des un vistazo a mis dotfiles. Aunque sin lugar a dudas lo mas recomendable es que lo configures según tus necesidades. Como verás de mi configuración, tampoco tengo tantas opciones en marcha. Si que he configurado los atajos de teclado que me permite desplazarme entre paneles. Estos atajos de teclado, se corresponde con los movimiento de vim, mas que nada por ser coherente. Además cargo un par de plugins, así como un tema, para dar un poco de color. Por otro lado, la combinación de tecla que divide verticalmente los paneles es Ctrl+b |, y la que lo hace horizontalmente es Ctrl+b -. Lo mas visual y nemotécnico que he podido ver o leer. Y, por último, para sincronizar todos los paneles el atajo de teclado que estoy utilizando es Ctrl+b Ctrl+x ... Más información en las notas del podcast sobre Tmux. El multiplexor de terminal

Please note: The audio version doesn't include code or commands. Those parts of the post can be seen in the text version. I spent a very long time automating my recon for bug bounties. I collaborated with a couple of friends for about 12 months to build out an automation beast. We had a custom framework, and constant recon scanning with good distribution, at times we scaled up to 100+ servers. We stored data on millions of targets and had Slack notifications for vulnerability detection. It was the third iteration of our automation and we thought it was great. I mean, it was pretty great, and it definitely helped us earn some cash on a few popular bounty programs. I learned a lot while I was coding this but ultimately, looking back I wish I had done things differently. Namely, I wish I had decoupled each component of the automation into small chainable tools instead of building everything as one giant framework. In other words, I wish I had followed the Unix philosophy. What's the Unix philosophy? Wikipedia puts it best: The Unix philosophy emphasizes building simple, short, clear, modular, and extensible code that can be easily maintained and repurposed by developers other than its creators. In this blog I'm going to show you how you can use three basic, free, open source tools to implement continuous monitoring for new subdomains in just five minutes. The three tools are: Anew by tomnomnom. Haktrails by me, you could use any subdomain enumeration tool here, like Subfinder or OWASP-Amass. Notify by Projectdiscovery. Setting up your environment Let's see what the necessary steps are to build a basic monitoring and alerting system for detecting new subdomains. Picking a VPS This is the kind of automation that you probably want to run 24, 7, 365. The easiest way to do this is to set up a VPS. You can use whatever Linux distribution but I tend to use Ubuntu because that's where I feel at home. You can set up an Ubuntu VPS on any popular hosting provider. Linode and Digital Ocean have them starting at $5 per month. If you're a new AWS customer you could also use a free tier EC2 instance which will be free for the first 12 months. Installing Golang and Tmux Once you've set up your VPS, you'll need to install Golang. If you're using Ubuntu, this should be as simple as. You probably also want Tmux so that you can leave the automation running without stopping every time your SSH session ends. Installing the tools Now that you have Golang installed, you can use the built-in Go package manager to install the tools that we'll be using. These commands work at the time that this blog post was written, but installation instructions for these tools may change so it's always best to check the installation instructions on the repositories directly. Adding GOBIN to your $PATH In order to run these new tools by typing the name of the tool: haktrails Instead of the full path. We need to modify our bash to include. We can do this by adding the following line to our file. Then restart your terminal, or run. Setting up your config files To use haktrails, you'll need to set up your config file containing your Securitytrails AP-I key. You can find instructions to do that here. To use notify, you'll need to set up your config file with your Discord, Slack, Telegram webhook(s). You can find instructions here. Gathering existing subdomains For the purpose of this blog, let's monitor securitytrails.com. The first step is to gather the existing subdomains for that domain and pop them into a file. You can achieve this by running the following command: Setting up constant monitoring There are a bunch of ways to do this. My personal preference would be to use hakcron, but you can easily achieve the same thing with some simple bash, so let's do that. To use the code above. Copy the code above into a file called monitor.sh. The bash script runs the command we created above, then does nothing for 3600 seconds. It repeats this process indefinitely. If you want ...

Please note: The audio version doesn't include code or commands. Those parts of the post can be seen in the text version. I spent a very long time automating my recon for bug bounties. I collaborated with a couple of friends for about 12 months to build out an automation beast. We had a custom framework, and constant recon scanning with good distribution, at times we scaled up to 100+ servers. We stored data on millions of targets and had Slack notifications for vulnerability detection. It was the third iteration of our automation and we thought it was great. I mean, it was pretty great, and it definitely helped us earn some cash on a few popular bounty programs. I learned a lot while I was coding this but ultimately, looking back I wish I had done things differently. Namely, I wish I had decoupled each component of the automation into small chainable tools instead of building everything as one giant framework. In other words, I wish I had followed the Unix philosophy. What's the Unix philosophy? Wikipedia puts it best: The Unix philosophy emphasizes building simple, short, clear, modular, and extensible code that can be easily maintained and repurposed by developers other than its creators. In this blog I'm going to show you how you can use three basic, free, open source tools to implement continuous monitoring for new subdomains in just five minutes. The three tools are: Anew by tomnomnom. Haktrails by me, you could use any subdomain enumeration tool here, like Subfinder or OWASP-Amass. Notify by Projectdiscovery. Setting up your environment Let's see what the necessary steps are to build a basic monitoring and alerting system for detecting new subdomains. Picking a VPS This is the kind of automation that you probably want to run 24, 7, 365. The easiest way to do this is to set up a VPS. You can use whatever Linux distribution but I tend to use Ubuntu because that's where I feel at home. You can set up an Ubuntu VPS on any popular hosting provider. Linode and Digital Ocean have them starting at $5 per month. If you're a new AWS customer you could also use a free tier EC2 instance which will be free for the first 12 months. Installing Golang and Tmux Once you've set up your VPS, you'll need to install Golang. If you're using Ubuntu, this should be as simple as. You probably also want Tmux so that you can leave the automation running without stopping every time your SSH session ends. Installing the tools Now that you have Golang installed, you can use the built-in Go package manager to install the tools that we'll be using. These commands work at the time that this blog post was written, but installation instructions for these tools may change so it's always best to check the installation instructions on the repositories directly. Adding GOBIN to your $PATH In order to run these new tools by typing the name of the tool: haktrails Instead of the full path. We need to modify our bash to include. We can do this by adding the following line to our file. Then restart your terminal, or run. Setting up your config files To use haktrails, you'll need to set up your config file containing your Securitytrails AP-I. You can find instructions to do that here. To use notify, you'll need to set up your config file with your Discord, Slack, Telegram webhook(s). You can find instructions here. Gathering existing subdomains For the purpose of this blog, let's monitor securitytrails.com. The first step is to gather the existing subdomains for that domain and pop them into a file. You can achieve this by running the following command: Setting up constant monitoring There are a bunch of ways to do this. My personal preference would be to use hakcron, but you can easily achieve the same thing with some simple bash, so let's do that. To use the code above. Copy the code above into a file called monitor.sh. The bash script runs the command we created above, then does nothing for 3600 seconds. It repeats this process indefinitely. If you want to l...

On this week's episode Chris and Steph discuss a new tmux feature and wvim, a script that streamlines shell command edits. They also discuss the value of taking a sabbatical and protecting downtime. Steph shares some exciting news about thoughtbot and they answer a listener question about GraphQL and whether your app really needs an API? This episode is brought to you by ScoutAPM (https://scoutapm.com/bikeshed). Give Scout a try for free today and Scout will donate $5 to the open source project of your choice when you deploy thoughtbot is hiring! (https://thoughtbot.com/jobs) Send a question to The Bike Shed! (https://thoughtbot.com/blog/send-your-questions-to-the-bike-shed) "which + vim = wvim" post (https://ctoomey.com/writing/which-plus-vim-wvim/) GraphQL Ruby (https://graphql-ruby.org/) Hasura (https://hasura.io/) PostGraphile (https://www.graphile.org/postgraphile/) Become a Sponsor (https://thoughtbot.com/sponsorship) of The Bike Shed!

A 35 Year Old Bug in Patch, Sandbox for FreeBSD, Changing from one dataset to another within a jail, You don’t need tmux or screen for ZFS, HardenedBSD August 2020 Status Report and Call for Donations, and more. NOTES This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/) Headlines A 35 Year Old Bug in Patch (http://bsdimp.blogspot.com/2020/08/a-35-year-old-bug-in-patch-found-in.html) Larry Wall posted patch 1.3 to mod.sources on May 8, 1985. A number of versions followed over the years. It's been a faithful alley for a long, long time. I've never had a problem with patch until I embarked on the 2.11BSD restoration project. In going over the logs very carefully, I've discovered a bug that bites this effort twice. It's quite interesting to use 27 year old patches to find this bug while restoring a 29 year old OS... Sandbox for FreeBSD (https://www.relkom.sk/en/fbsd_sandbox.shtml) A sandbox is a software which artificially limits access to the specific resources on the target according to the assigned policy. The sandbox installs hooks to the kernel syscalls and other sub-systems in order to interrupt the events triggered by the application. From the application point of view, application working as usual, but when it wants to access, for instance, /dev/kmem the sandbox software decides against the assigned sandbox scheme whether to grant or deny access. In our case, the sandbox is a kernel module which uses MAC (Mandatory Access Control) Framework developed by the TrustedBSD team. All necessary hooks were introduced to the FreeBSD kernel. Source Code (https://gitlab.com/relkom/sandbox) Documentation (https://www.relkom.sk/en/fbsd_sandbox_docs.shtml) News Roundup Changing from one dataset to another within a jail (https://dan.langille.org/2020/08/16/changing-from-one-dataset-to-another-within-a-freebsd-iocage-jail/) ZFS has a the ability to share itself within a jail. That gives the jail some autonomy, and I like that. I’ve written briefly about that, specifically for iocage. More recently, I started using a zfs snapshot for caching clearing. The purpose of this post is to document the existing configuration of the production FreshPorts webserver and outline the plan on how to modify it for more zfs-snapshot-based cache clearing. You don’t need tmux or screen for ZFS (https://rubenerd.com/you-dont-need-tmux-or-screen-for-zfs/) Back in January I mentioned how to add redundancy to a ZFS pool by adding a mirrored drive. Someone with a private account on Twitter asked me why FreeBSD—and NetBSD!—doesn’t ship with a tmux or screen equivilent in base in order to daemonise the process and let them run in the background. ZFS already does this for its internal commands. HardenedBSD August 2020 Status Report and Call for Donations (https://hardenedbsd.org/article/shawn-webb/2020-08-15/hardenedbsd-august-2020-status-report-and-call-donations) This last month has largely been a quiet one. I've restarted work on porting five-year-old work from the Code Pointer Integrity (CPI) project into HardenedBSD. Chiefly, I've started forward-porting the libc and rtld bits from the CPI project and now need to look at llvm compiler/linker enhancements. We need to be able to apply SafeStack to shared objects, not just application binaries. This forward-porting work I'm doing is to support that effort. The infrastructure has settled and is now churning normally and happily. We're still working out bandwidth issues. We hope to have a new fiber line ran by the end of September. As part of this status report, I'm issuing a formal call for donations. I'm aiming for $4,000.00 USD for a newer self-hosted Gitea server. I hope to purchase the new server before the end of 2020. Important parts of Unix's history happened before readline support was common (https://utcc.utoronto.ca/~cks/space/blog/unix/TimeBeforeReadline) Unix and things that run on Unix have been around for a long time now. In particular, GNU Readline was first released in 1989 (as was Bash), which is long enough ago for it (or lookalikes) to become pretty much pervasive, especially in Unix shells. Today it's easy to think of readline support as something that's always been there. But of course this isn't the case. Unix in its modern form dates from V7 in 1979 and 4.2 BSD in 1983, so a lot of Unix was developed before readline and was to some degree shaped by the lack of it. Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Feedback/Questions Mason - mailserver (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/367/feedback/Mason%20-%20mailserver.md) casey - freebsd on decline (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/367/feedback/casey%20-%20freebsd%20on%20decline.md) denis - postgres (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/367/feedback/denis%20-%20postgres.md) *** Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) ***

Jävla bil. Jocke fantiserar om en bil som bara behöver servas två gånger om dagen Jocke åter till kontoret. Påminns på vägen hem i köerna varför det suger att pendla Kallt ute Poolrapporten: vattnet fortsätter försvinna. tar in firma som får söka efter hålet/hålen. Pooldäcket byggs det på WSL 2: kompilera vår sajt i Jekyll tar längre tid. Undersöker varför. Varför är finns det inte fler riktigt smarta terminalprogram för Linux? DMZ Retro #4! Nytt nummer, tonvis med merch, vinn en Vic-20 med massor av tillbehör! Boka ditt ex nu! En trevlig pull request. Fredrik laddar ner ett RSS-flöde på längsta möjliga omvägar Länkar Bromsok Subaru forester Marodörkartan WSL 2 Iterm 2 Tmux Tilix Hyper Terminator Terminus Iterm 2 på Github Boka ditt exemplar av Datormagazin retro #4 nu! Koppar kafferosteri VIC-20 Commodore 1311-joysticken Hugo Kodsnacks avsnittsrepo Senaste avsnittet Avsnitt 158 av Kodsnack Avsnitt 74 av Kodsnack Senaste Accidental tech podcast T2-chippet Vangers Vangers-klippen på Peertube Vange-rs Amiga retroradion - avsnitt 1 Rust Två nördar - en podcast. Fredrik Björeman, Joacim Melin diskuterar allt som gör livet värt att leva. Fullständig avsnittsinformation finns här: https://www.bjoremanmelin.se/podcast/avsnitt-224-vi-kommer-med-dykardrakt.html.

This week's Chit Chat Across the Pond is an episode of Taming the Terminal, where Bart winds up our series within a series all about the Terminal command TMUX. In this final piece he teaches us first how to string commands together to create the TMUX sessions we want with the screens split and the processes running in each pane as we like them. After teaching us how to string them together he shows us how to make a little script file we can run so that we can automatically open up our TMUX sessions exactly the way we like them. This will be the last of our Taming the Terminal episodes for a while, but we'll be back after macOS Big Sur ships and is stabilized. In macOS Catalina the default shell was changed from bash to zsh and it does bring some changes to things we learned earlier in the series but it seems prudent to wait till we're over this big hump getting into Big Sur. You can find Bart's tutorial shownotes over at ttt.bartificer.net/... Don't forget, you can download the Taming the Terminal book at podfeet.com/tttbook. The book will be updated with this instalment shortly.

In this episode of Taming the Terminal, Bart winds up our series within a series all about the Terminal command TMUX. In this final piece he teaches us first how to string commands together to create the TMUX sessions we want with the screens split and the processes running in each pane as we like them. After teaching us how to string them together he shows us how to make a little script file we can run so that we can automatically open up our TMUX sessions exactly the way we like them. This will be the last of our Taming the Terminal episodes for a while, but we'll be back after macOS Big Sur ships and is stabilized. In macOS Catalina the default shell was changed from bash to zsh and it does bring some changes to things we learned earlier in the series but it seems prudent to wait till we're over this big hump getting into Big Sur. You can find Bart's tutorial shownotes over at ttt.bartificer.net/... Don't forget, you can download the Taming the Terminal book at podfeet.com/tttbook. The book will be updated with this instalment shortly.

This week's Chit Chat Across the Pond is an episode of Taming the Terminal, where Bart winds up our series within a series all about the Terminal command TMUX. In this final piece he teaches us first how to string commands together to create the TMUX sessions we want with the screens split and the processes running in each pane as we like them. After teaching us how to string them together he shows us how to make a little script file we can run so that we can automatically open up our TMUX sessions exactly the way we like them. This will be the last of our Taming the Terminal episodes for a while, but we'll be back after macOS Big Sur ships and is stabilized. In macOS Catalina the default shell was changed from bash to zsh and it does bring some changes to things we learned earlier in the series but it seems prudent to wait till we're over this big hump getting into Big Sur. You can find Bart's tutorial shownotes over at ttt.bartificer.net/... Don't forget, you can download the Taming the Terminal book at podfeet.com/tttbook. The book will be updated with this instalment shortly.

This week's episode of Chit Chat Across the Pond was another installment of Taming the Terminal. Two weeks ago Bart taught us the basics of a technology called `tmux`, or terminal multiplexer that allows you to access the same server in many different ways at the same time. He covered how `tmux` replaces the deprecated `screen` but he didn't go much further. In this rather light and easy-to-follow installment, he takes `tmux` up a notch and shows us how to create multiple windows, and multiple panes all within a single `tmux` session. Like I said it was super easy to understand, very visual and fun! You can listen to this week's installment by searching for Taming the Terminal in your podcatcher of choice or it's included in the full Chit Chat Across the Pond show as well. And as always you can get to Bart's fabulous tutorial shownotes at bartbusschots.ie/...

This week's episode of Chit Chat Across the Pond was another installment of Taming the Terminal. Two weeks ago Bart taught us the basics of a technology called `tmux`, or terminal multiplexer that allows you to access the same server in many different ways at the same time. He covered how `tmux` replaces the deprecated `screen` but he didn't go much further. In this rather light and easy-to-follow installment, he takes `tmux` up a notch and shows us how to create multiple windows, and multiple panes all within a single `tmux` session. Like I said it was super easy to understand, very visual and fun! You can listen to this week's installment by searching for Taming the Terminal in your podcatcher of choice or it's included in the full Chit Chat Across the Pond show as well. And as always you can get to Bart's fabulous tutorial shownotes at bartbusschots.ie/...

This week's episode of Chit Chat Across the Pond was another installment of Taming the Terminal. Two weeks ago Bart taught us the basics of a technology called `tmux`, or terminal multiplexer that allows you to access the same server in many different ways at the same time. He covered how `tmux` replaces the deprecated `screen` but he didn't go much further. In this rather light and easy-to-follow installment, he takes `tmux` up a notch and shows us how to create multiple windows, and multiple panes all within a single `tmux` session. Like I said it was super easy to understand, very visual and fun! You can listen to this week's installment by searching for Taming the Terminal in your podcatcher of choice or it's included in the full Chit Chat Across the Pond show as well. And as always you can get to Bart's fabulous tutorial shownotes at bartbusschots.ie/...

When Bart first started the Taming the Terminal series in October of 2015, he purposely declared every installment to be "of n" where n was not defined. It's been 3 years since there was an episode of Taming the Terminal, but today we've got a new one for you. In Taming the Terminal 36, recorded in 2016, Bart introduced us to a nifty command-line tool called screen. Screen allowed you to ssh into a server, and start a session but disconnect and come back to it without stopping the processes you were running. But in the last year, screen was deprecated by Red Hat Linux (which means it's gone from the free CentOS version as well). The good news is that it was replaced with an even more powerful tool called tmux. In this installment, Bart walks us through just how tmux solves the same problem as screen, but teases us with the knowledge that this tool has much more to offer. It was a super fun episode with lots of surprises (for me at least) and whether you followed along with the first 37 installments or not, I'm sure you'll find it useful as well. You can find Bart's fabulous shownotes at bartbusschots.ie/....

When Bart first started the Taming the Terminal series in October of 2015, he purposely declared every installment to be "of n" where n was not defined. It's been 3 years since there was an episode of Taming the Terminal, but today we've got a new one for you. In Taming the Terminal 36, recorded in 2016, Bart introduced us to a nifty command-line tool called screen. Screen allowed you to ssh into a server, and start a session but disconnect and come back to it without stopping the processes you were running. But in the last year, screen was deprecated by Red Hat Linux (which means it's gone from the free CentOS version as well). The good news is that it was replaced with an even more powerful tool called tmux. In this installment, Bart walks us through just how tmux solves the same problem as screen, but teases us with the knowledge that this tool has much more to offer. It was a super fun episode with lots of surprises (for me at least) and whether you followed along with the first 37 installments or not, I'm sure you'll find it useful as well. You can find Bart's fabulous shownotes at bartbusschots.ie/....

When Bart first started the Taming the Terminal series in October of 2015, he purposely declared every installment to be "of n" where n was not defined. It's been 3 years since there was an episode of Taming the Terminal, but today we've got a new one for you. In Taming the Terminal 36, recorded in 2016, Bart introduced us to a nifty command-line tool called screen. Screen allowed you to ssh into a server, and start a session but disconnect and come back to it without stopping the processes you were running. But in the last year, screen was deprecated by Red Hat Linux (which means it's gone from the free CentOS version as well). The good news is that it was replaced with an even more powerful tool called tmux. In this installment, Bart walks us through just how tmux solves the same problem as screen, but teases us with the knowledge that this tool has much more to offer. It was a super fun episode with lots of surprises (for me at least) and whether you followed along with the first 37 installments or not, I'm sure you'll find it useful as well. You can find Bart's fabulous shownotes at bartbusschots.ie/....

مع الحلقة رقم ٩ : و من لندن مع مصعب ابراهيم (مصعبوف) من مصر الي برلين ومن برلين الي لندن مصعب دلوقتي منضم حديثا لفريق تويتر ك SRE (Site Reliability Engineer) S1E9: Tech Chat With Mosab Ibrahim | The SRE!!? ----------------------------------------- رابط الحلقة | This Episode link: https://bit.ly/3gNk8Ce ---------------------------------------- You Can buy me a coffee || ادعم البودكاست واعزمني علي قهوة من هنا https://bit.ly/TechAndCoffeeBuyMeACoffee ---------------------------------------- Links in this Episode | روابط من الحلقة: S1E8: Tech Chat with Ahmad Abdelalem (The T shaped engineer) http://mosab.co.uk The Toolset: - My IDE is Vim (neovim): https://neovim.io/ - Tmux: https://github.com/tmux/tmux/wiki - Kitty terminal emulator: https://sw.kovidgoyal.net/kitty/ - Fzf: https://github.com/junegunn/fzf - Silver searcher instead of grep: https://github.com/ggreer/the_silver_searcher - bat: a better cat: https://github.com/sharkdp/bat Other Links: https://www.goodreads.com/book/show/10673823-the-google-resume https://www.goodreads.com/book/show/12544648-cracking-the-coding-interview https://www.goodreads.com/book/show/18058001-systems-performance https://stackoverflow.com/jobs https://landing.google.com/sre/books/ https://landing.google.com/sre/sre-book/chapters/embracing-risk/#id-na2u1S2SKi1 https://blog.twitter.com/engineering/en_us.html https://github.com/twitter -------------------------------------------------------------------- Follow the Podcast: Instagram: https://www.instagram.com/tech.and.coffee Facebook Page: https://www.facebook.com/techandcoffeepodcast Follow me: Instagram: https://www.instagram.com/iahmadzain Twitter: https://twitter.com/iAhmadZain Facebook: https://www.facebook.com/iahmadzain ----------------------------- رابط الحلقة | This Episode link: https://bit.ly/3gNk8Ce

Bienvenue, chers compagnons sur Radio DevOps.La Baladodiffusion des Compagnons du DevOps.Le podcast en français dédié à notre mouvement.Au menu aujourd'hui je passe DamyR sur le grill pour que vous en sachiez un peu plus sur lui.Les liens :Blog de DamyR : https://www.damyr.frAssociation pour la Promotion et la Recherche en Informatique Libre (APRIL) : https://www.april.org/Améliorez votre Linux et gérer votre configuration avec des Dotfiles : https://github.com/thoughtbot/dotfilesZsh : http://www.zsh.org/Oh my zsh : https://ohmyz.sh/Tmux : https://github.com/tmux/tmux/wikiLes conférences du DevOpsRex : https://www.youtube.com/channel/UC72Zm-H5Bx3-iGU7YzohF1QLe SRE vu par Google : https://landing.google.com/sre/Nos émissions :

**If Derek told you about us at SANS, send a DM to @brakeSec or email bds.podcast@gmail.com for an invite to our slack** OSCP/HtB/VulnHub is a game... designed to have a tester find a specific nugget of information to pivot or gain access to greater power on the system.  Far different in the 'real' world.   Privilege escalation in Windows: *as of June 2020, many of these items still work, may not work completely in the future* *even so, many of these may not work if other mitigating controls are in place*   PENTEST METHODOLOGY :  PTES -http://www.pentest-standard.org/index.php/PTES_Technical_Guidelines OSSTMM - https://www.isecom.org/OSSTMM.3.pdf   Redteam methodology: https://www.synopsys.com/glossary/what-is-red-teaming.html   https://www.fuzzysecurity.com/tutorials/16.html   https://medium.com/@Shorty420/enumerating-ad-98e0821c4c78   https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Methodology%20and%20Resources/Windows%20-%20Privilege%20Escalation.md   Enumerate the machine Services Network connections Users Logins Domains Files Software installed (putty, git, MSO, etc) *older software may install with improper permissions* Service paths (along with users services are ran as) Windows Features (WSL, SSH, etc) Patch level (Build 1703, etc) Wifi networks and passwords (netsh wlan show profile key=clear) Powershell history Bash History (if WSL is used) Incognito tokens Stored credentials (cmdkey /list) Powershell transcripts (search text files for "Windows PowerShell transcript start")   Context for above: Understand how the users make use of the system, and how they connect to other systems, follow those paths to find lateral movement, misconfigurations, etc. Each new system or user will provide further information to loot or avenues to explore   Linux EoP: https://guif.re/linuxeop   https://blog.g0tmi1k.com/2011/08/basic-linux-privilege-escalation/   Enumeration Mostly the same as above Bash history or profile files            Writable scripts (tampering with paths or environment variables) Setuid/Setgid binaries Sticky bit directories Crontabs Email spools World writable/readable files .ssh config files (keys, active sessions) Tmux/screen sessions Application secrets (database files, web files with database connectivity, hard coded creds or keys, etc) VPN profiles GNOME keyrings- https://askubuntu.com/questions/96798/where-does-seahorse-gnome-keyring-store-its-keyrings   Ways to defend against those kinds of EoP. Something cool: https://www.youtube.com/playlist?playnext=1&list=PLnxNbFdr_l6sO6vR6Vx8sAJZKpgKtWaGX&feature=gws_kp_artist  -- high Rollers   Derek is speaking at SANS SUMMIT happening on 04-05 June (FREE!) - https://www.sans.org/event/hackfest-ranges-summit-2020   Ms. Berlin is speaking at EDUCAUSE - VIRTUAL (04 June) https://www.educause.edu/

Romain Lafourcade échange avec Guillaume et Emmanuel sur Vim: comment il y est venu, ce qu’il a d’unique, comment l’appréhender, et bien d’autres choses encore. Enregistré le 16 avril 2020 Téléchargement de l’épisode LesCastCodeurs-Episode–231.mp3 Interview Ta vie, ton œuvre GitHub de Romain Je m’appelle Romain Lafourcade. Je suis Graphiste de formation et j’ai chopé le virus du développement en montant mon premier site en 1999. Je suis Développeur pour de vrai depuis 2007. J’ai beaucoup fait de JS, bien sûr, ainsi que du Flash et du Silverlight. Ça fait quelques années que je me concentre sur React et Vue.js. Aujourd’hui je suis chez Publicis Sapient France, une “agence digitale” de premier plan où je m’amusais déjà très bien jusqu’à l’arrivée des ex-Xebians. Et maintenant c’est encore mieux. Je participe actuellement à la préparation d’une conférence “front” pointue pour la fin de l’année : FrontSide. Mes intérêts personnels gravitent autour de la programmation fonctionnelle : Haskell, Elixir. Et Vim, bien sûr. Vim intro Page wikipedia de Vim Qu’est-ce que Vim en 2 phrases ? Vim est un éditeur de texte orienté programmation, puissant et non-conformiste. Que peut on dire de la différence entre un IDE et un éditeur ? Dans son expression la plus simple, un éditeur de texte est un outil permettant l’édition de fichiers de texte brut. Certains sont “standalone”, comme Vim, Nano ou Gedit, se concentrant pour la majeure partie sur des questions liées à l’édition de texte et déléguant les autres tâches liée au développement logiciel à d’autres outils “standalone”. C’est la vision UNIX traditionnelle : “Écrivez des programmes qui effectuent une seule chose et qui le font bien.” D’autres sont “intégrés” avec d’autres outils pour offrir une expérience plus “clé en main”, les IDEs. L’histoire de Vim Vim est né au début des années 90 sur Amiga, pour la même raison que tous les autres clones de vi : l’impossibilité légale d’utiliser vi sur tel ou tel système. De tous les clones, c’est celui qui s’est le plus démarqué de l’original et c’est le seul qui est encore développé activement en 2020. Les archéologues en herbe trouveront quelques liens sur le sujet en bas de page. Disponibilité de Vim sur les distros de base Un des arguments les plus souvent mis en avant pour convaincre les mécréants de l’utilité d’apprendre Vim est “Vim est partout”. Mais l’ubiquité légendaire de Vim est un mythe. Ce qui est disponible dans tous les dérivés d’UNIX, c’est la commande vi. Le programme qui assure le boulot peut être Vim comme il peut être Elvis, Nvi, Busybox vi ou même le vi original. Et même quand c’est Vim, c’est souvent un build limité. Du coup, connaître Vim n’est peut-être pas aussi utile que connaître vi. Et c’est sans compter sur le fait que le système d’exploitation le plus largement utilisé, n’a pas de commande vi ou vim du tout. Vim vs emacs: la guerre ancestrale et aussi débile que toutes les guerres ancestrales. Les variantes de Vim Neovim est un fork récent promettant une modernisation des processus de développement et du code. Vim au quotidien Pas de curseur????? On a bien un curseur, mais les dispositifs de pointage sont rarement activés par défaut. Même si c’est tout à fait possible d’utiliser la souris ou le trackpad (:help 'mouse'), on est clairement dans un monde centré autour du clavier. Les modes (normal, insert, visual, etc.) L’édition modale, un concept initié par vi, ne fait pas l’unanimité. L’idée, c’est qu’on est toujours dans un mode réservé à une certaine catégorie d’activités. Un des effets positifs, et aussi un des repoussoirs de ce mécanisme est que ça permet d’avoir un vocabulaire plus varié et expressif que dans un éditeur classique. Le déplacement du curseur, par exemple, se fait traditionnellement avec une combinaison de 4 touches de directions et 1 modificateurs, donc 8 déplacements possibles : 1 caractère vers la droite ou la gauche, 1 mot vers la droite ou la gauche, 1 ligne vers le haut ou le bas, 1 paragraphe vers le haut ou le bas. C’est très pauvre, même en ajoutant Home, End, Page Up et Page Down. Dans vim, on a tout ça, bien sûr, plus “début du mot”, “fin du mot”, “prochaine/précédente occurrence de ”, “prochaine/précédente occurrence de ”, “ligne numéro X”, “n lignes vers le haut ou le bas”, “haut/bas/milieu de la fenêtre”, “marqueur X”, etc. Rien jjque ça c’est dingue. Et comme on est dans un éditeur modal, tous ces mouvement peuvent être utilisés avec des opérateurs et là c’est la folie. Les modes les plus couramment utilisés sont : le mode normal, le mode par défaut quand on fait $ vim foo.txt, qui est utilisé pour naviguer, chercher, copier, coller, etc. le mode d’insertion, qui permet… d’insérer du texte dans le document, les modes visuels, qui permettent de sélectionner une portion de texte, le mode ligne de commande, qui permet d’utiliser les commandes héritées d’Ex : :write, :s, :g, etc. Le concept de verbe / opérateur + movement + destination C’est pour moi LA killer feature de Vim, surtout visible dans les modes normal et visuels. En gros, le modèle d’interaction est basé sur la notion de langage. Il y a : des “opérateurs”, des verbes conjugués à l’impératif comme “efface”, “copie”, “remplace”, des compléments d’objet directs comme “la ligne 78”, “ce texte entre parenthèses”, “d’ici à la fin du paragraphe”, des compléments d’objet indirects comme “en dessous de la ligne 27” ou “au début du buffer”, et des compléments circonstanciels comme “10 fois”. Avec tout ça, on donne des commandes à la machine selon une syntaxe proche de celle d’un langage parlé et elle obéit : “colle le texte contenu dans le presse papier 50 fois”, “copie (d’ici) jusqu’à la prochaine parenthèse ouvrante”, etc. Dans un éditeur de texte classique, la première se dit “ctrl+v ctrl+v … ctrl+v”, ce qui n’a presque rien à voir avec la tâche telle qu’imaginée : “colle truc 50 fois” est devenu “colle colle … colle”, ce qui est très peu expressif. Notre pensée abstraite de haut niveau doit être transformée en une série d’action concrètes de bas niveau qui n’ont que très peu de sens et souvent rien à voir avec la pensée haut niveau. Dans Vim, la première commande se dit “50p”, ce qui est très proche de la tâche telle qu’imaginée. La syntaxe est peut-être un peu sèche et les éléments sont peut-être ordonnés différemment qu’en français, mais ça reste tout à fait abordable et très proche de ce qu’on a dans la tête. L’étape suivante est exactement la même que lorsqu’on apprend une langue étrangère : penser dans la langue. Apprendre Vim, c’est apprendre une grammaire simple et un vocabulaire expressif qui s’enrichit au fur et à mesure où on avance. La notion de range Vim hérite plein de trucs de vi, qui hérite lui-même plein de trucs de ex. Dans vim, toutes les commandes qui commencent par un “deux points” sont des “commandes Ex”, qui agissent sur des lignes car ex était un éditeur de ligne. Comme dans ex, ces commandes prennent des adresses (une seule ligne) et des ranges (de telle ligne à telle autre). Une ligne peut être indiquée par son numéro, par un offset, par une recherche, par un marqueur, etc. C’est un outil extrêmement puissant. Par exemple, la commande suivante copie les lignes 10 à 24 en fin de document : :10,24t$ Celle-ci rassemble toutes les lignes contenant const dans la fonction courante vers le haut du corps de la fonction : :?func?,/^}/g/const/m?func? C’est d’une élégance insoutenable. D’autres concepts de base (window, tab, buffer, split, etc.) On a toujours au moins un “buffer”, une “fenêtre” et une “tab page”. Un buffer peut être affiché dans une ou plusieurs “fenêtres”, une “tab page” est un rassemblement de “fenêtres”. Contrairement à la plupart des éditeurs de texte il ne peut pas y avoir de relation 1-à–1 entre un buffer et une fenêtre ou entre un buffer et une tab page. C’est un piège dans lequel tous les nouveaux tombent. Tu l’utilises pour quels genre d’édition J’utilise Vim de deux façons différentes : de longues sessions de programmation et des éditions rapides (config, git commit, etc.), pratiquement tout le temps dans un terminal. Les colorschemes La dernière fois que j’ai checké il y en avait littéralement des milliers, du simple qui marche partout, utilisé par quelques barbus ronchons, à l’usine à gaz buggée à mort, utilisée par la dernière génération de boutonneux. J’en ai réalisé quelques uns, même, comme Apprentice, ainsi qu’un modèle simple à utiliser. Maintenant qu’on peut utiliser toutes les valeurs hexadécimales, même dans le terminal, c’est la fête. Pour trouver des colorschemes, je recommande VimColors. Les binding Vim dans les IDEs Peut-être utile pour accompagner l’apprentissage de Vim mais passé un certain niveau c’est l’uncanny valley. C’est un des problèmes causés par des années de Vim, d’ailleurs : ça rend exigeant. Le terminal Le nerf de la guerre d’un Vim qui fonctionne tmux? Vim écosystème La gestion des plugins Si on a beaucoup de plugins ça peut devenir compliqué sans plugin manager. Le plus populaire est vim-plug. Les plugins les plus utilisés fugitive, un client Git bien intégré à Vim surround, permet de jouer avec les paires de caractères : (), {}, etc. Souvent considéré comme un indispensable. ALE, beaucoup plus qu’un linter, YouCompleteMe, beaucoup plus que de l’autocompletion. Vim et les plugins VSCode (via LSP) Les spécifications de pas mal de fonctionnalités de Visual Studio Code sont actuellement publiées, ce qui permet à d’autres outils de développement de bénéficier de l’étendue de son ecosystème. Il y a LSP, par exemple, qui permet d’implémenter des serveurs pour n’importe quel langage et des clients pour n’importe quel éditeur. Les clients à suivre pour Vim son lsc et CoC. Peut-être aurons-nous une intégration native un jour ? Il y a aussi DAP qui est utilisé par Vimspector pour fournir une interface de débogage avancée. La navigation entre fichiers Un faux problème, souvent résolu en mode “brute force” par manque de volonté d’apprendre à se servir des fonctionnalités de base. Du coup on a des dizaines de plugins fantaisistes et des générations de vimmers superficiels. C’est triste. En vrai, :edit, :find et :buffer sont rapides et versatiles. Il suffit de prendre le temps d’apprendre à s’en servir. Il existe un nombre hallucinant de plugins pour naviguer les fichiers alors que c’est si simple et rapide avec les outils natifs. La vérification orthographique La fonctionnalité est incluse de base. Il faut néanmoins l’activer avec :help ’spell’ et, si on veut de l’aide pour autre chose que de l’anglais, installer des dictionnaires. Ça sonne plus compliqué que ça ne l’est vraiment. Des tips Indentation Tout savoir sur l’indentation dans Vim gg=G pour réparer l’indentation d’un buffer en entier :help ’equalprg’ pour indiquer à Vim quel programme externe utiliser Paramètres custom par fichier via modeline Voir :help modeline pour des exemples. Je ne suis pas hyper fan en général que je trouve ça un peu sale de mélanger data et metada mais ça peut être bien en bas d’un fichier Markdown dont on sait qu’il va être édité dans Vim : [//]: # ( Vim: set spell spelllang=en: ) En pratique, je suggère plutôt editorconfig pour les réglages d’indentation et compagnie. Vim et git Fugitive, mentionné plus haut, est très populaire. Pour ma part, je préfère garder mon éditeur de texte pour éditer du texte et utiliser d’autres outils spécialisés pour d’autres tâches spécialisées. J’aime beaucoup tig, que j’utilise au jour le jour depuis des années, et j’ai découvert git-jump récemment, qui a fait une entrée fracassante dans mon workflow. Sinon, pour les commandes basiques, un simple :!git fait largement le taf. Les macros Une macro est une séquence de commande. On peut enregistrer une macro dans le registre q : qq 02wciwfoo q et la rejouer sur plusieurs lignes, par exemple : :23,45normal! @q Mais avec un peu de pratique on peut complètement zapper la phase « enregistrement » : :23,45normal! 02wciwfoo Les macros sont un outil d’automatisation extraordinaire qui épate facilement le spectateur. Voir :help complex-repeat. Copier dans le buffer de l’OS (ctrl+c ctrl+v) Pour ça, l’idéal est d’avoir un Vim compilé avec la fonctionnalité “clipboard”. Si c’est pas possible on peut bricoler des trucs avec xclip/pbcopy/etc. ou utiliser les fonctionnalités de copier/coller du terminal. Le clipboard système est représenté par le registre + dans vim. Donc copier dans le clipboard: "+y, et ensuite coller, "+p. Note que " est la sélection de registre. Remplacer via des expressions régulières La substitution, basée sur les expressions régulières ou pas, est une pratique courante dans Vim. Par exemple, pour remplacer toutes les occurrences de java par kotlin dans le buffer courant : :%s/java/kotlin/g Voir :help :s et le site Vim Regular Expressions 101 car Vim utilise un dialecte spécial. Mode vi dans le shell Readline, la bibliothèque utilisée par bash pour gérer l’invite de commande, utilise des raccourcis inspirés par Emacs par défaut. On peut changer ça en ajoutant la ligne suivante dans ~/.inputrc: set editing-mode vi Personnellement, je préfère garder les raccourcis par défaut et éditer mes commandes directement dans Vim, avec Ctrl-x Ctrl-e. Si vous ave mis le mode vi, alors pour éditer la commande dans vim, tapez ESC v. Vimdiff On peut utiliser Vim pour afficher des diffs côte à côte et même pour gérer les merge conflicts dans Git. Voir :help diff pour les détails sanglants. Aller plus loin Livres Practical Vim Modern Vim Learn Vimscript The Hard Way The Viml Primer Histoire de vim The History Of Vim Where Vim Came From Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8 10 Questions with Vim’s creator, Bram Moolenaar Ressources Vim Galore Idiomatic Vimrc Seven habits of effective text editing :help user-manual Vimways Meetups Tuppervim Communauté #vim sur Freenode #vim-fr sur freenode r/vim sur reddit le tag Vim sur Stack Overflow le site Stack Exchange dédié à Vim En vrac Vim 9 ? Comment quitter Vim de manière… créative Vim cheatsheet Bonne explication d’un beau vimrc en détails Tmux et Vim ensemble avec les bons plugins Been using Vim for two years because I didn’t figure how to quit it! Vim primer and tutorial Resources Vim Des stickers pour clavier Mac pour se rappeler des raccourcis Nous contacter Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Faire un crowdcast ou une crowdquestion Contactez-nous via twitter https://twitter.com/lescastcodeurs sur le groupe Google https://groups.google.com/group/lescastcodeurs ou sur le site web https://lescastcodeurs.com/

Romain Lafourcade échange avec Guillaume et Emmanuel sur Vim: comment il y est venu, ce qu'il a d'unique, comment l'appréhender, et bien d'autres choses encore. Enregistré le 16 avril 2020 Téléchargement de l'épisode [LesCastCodeurs-Episode-231.mp3](http://traffic.libsyn.com/lescastcodeurs/LesCastCodeurs-Episode-231.mp3) ## Interview ### Ta vie, ton œuvre [GitHub de Romain](https://github.com/romainl) Je m’appelle Romain Lafourcade. Je suis Graphiste de formation et j’ai chopé le virus du développement en montant mon premier site en 1999. Je suis Développeur pour de vrai depuis 2007. J’ai beaucoup fait de JS, bien sûr, ainsi que du Flash et du Silverlight. Ça fait quelques années que je me concentre sur React et Vue.js. Aujourd’hui je suis chez [Publicis Sapient France](https://www.publicissapient.com/), une "agence digitale" de premier plan où je m’amusais déjà très bien jusqu’à l’arrivée des ex-Xebians. Et maintenant c’est encore mieux. Je participe actuellement à la préparation d’une conférence "front" pointue pour la fin de l’année : [FrontSide](https://frontsideconf.fr/). Mes intérêts personnels gravitent autour de la programmation fonctionnelle : Haskell, Elixir. Et Vim, bien sûr. ### Vim intro [Page wikipedia de Vim](https://en.wikipedia.org/wiki/Vim_(text_editor)) #### Qu’est-ce que Vim en 2 phrases ? Vim est un éditeur de texte orienté programmation, puissant et non-conformiste. #### Que peut on dire de la différence entre un IDE et un éditeur ? Dans son expression la plus simple, un éditeur de texte est un outil permettant l’édition de fichiers de texte brut. Certains sont "standalone", comme Vim, Nano ou Gedit, se concentrant pour la majeure partie sur des questions liées à l’édition de texte et déléguant les autres tâches liée au développement logiciel à d’autres outils "standalone". C’est la vision UNIX traditionnelle : > "Écrivez des programmes qui effectuent une seule chose et qui le font bien." D’autres sont "intégrés" avec d’autres outils pour offrir une expérience plus "clé en main", les IDEs. ### L’histoire de Vim Vim est né au début des années 90 sur [Amiga](https://en.wikipedia.org/wiki/Amiga), pour la même raison que tous les autres clones de vi : l’impossibilité légale d’utiliser vi sur tel ou tel système. De tous les clones, c’est celui qui s’est le plus démarqué de l’original et c’est le seul qui est encore développé activement en 2020. Les archéologues en herbe trouveront quelques liens sur le sujet en bas de page. #### Disponibilité de Vim sur les distros de base Un des arguments les plus souvent mis en avant pour convaincre les mécréants de l'utilité d'apprendre Vim est "Vim est partout". Mais l’ubiquité légendaire de Vim est un mythe. Ce qui est disponible dans tous les dérivés d’UNIX, c’est la commande `vi`. Le programme qui assure le boulot peut être Vim comme il peut être [Elvis](http://elvis.the-little-red-haired-girl.org/), [Nvi](https://sites.google.com/a/bostic.com/keithbostic/vi/), [Busybox vi](https://git.busybox.net/busybox/tree/editors/vi.c) ou même [le vi original](http://ex-vi.sourceforge.net/). Et même quand c’est Vim, c’est souvent un build limité. Du coup, connaître Vim n’est peut-être pas aussi utile que connaître vi. Et c’est sans compter sur le fait que le système d’exploitation le plus largement utilisé, n’a pas de commande `vi` ou `vim` *du tout*. #### Vim vs emacs: la guerre ancestrale et aussi débile que toutes les guerres ancestrales. #### Les variantes de Vim Neovim est un fork récent promettant une modernisation des processus de développement et du code. ### Vim au quotidien #### Pas de curseur????? On a bien un curseur, mais les dispositifs de pointage sont rarement activés par défaut. Même si c’est tout à fait possible d’utiliser la souris ou le trackpad (`:help 'mouse'`), on est clairement dans un monde centré autour du clavier. #### Les modes (normal, insert, visual, etc.) L’édition modale, un concept initié par vi, ne fait pas l’unanimité. L’idée, c’est qu’on est toujours dans un mode réservé à une certaine catégorie d’activités. Un des effets positifs, et aussi un des repoussoirs de ce mécanisme est que ça permet d’avoir un vocabulaire plus varié et expressif que dans un éditeur classique. Le déplacement du curseur, par exemple, se fait traditionnellement avec une combinaison de 4 touches de directions et 1 modificateurs, donc 8 déplacements possibles : 1 caractère vers la droite ou la gauche, 1 mot vers la droite ou la gauche, 1 ligne vers le haut ou le bas, 1 paragraphe vers le haut ou le bas. C’est très pauvre, même en ajoutant Home, End, Page Up et Page Down. Dans vim, on a tout ça, bien sûr, plus "début du mot", "fin du mot", "prochaine/précédente occurrence de ", "prochaine/précédente occurrence de ", "ligne numéro X", "n lignes vers le haut ou le bas", "haut/bas/milieu de la fenêtre", "marqueur X", etc. Rien jjque ça c’est dingue. Et comme on est dans un éditeur modal, tous ces mouvement peuvent être utilisés avec des opérateurs et là c’est la folie. Les modes les plus couramment utilisés sont : * le mode normal, le mode par défaut quand on fait `$ vim foo.txt`, qui est utilisé pour naviguer, chercher, copier, coller, etc. * le mode d'insertion, qui permet… d'insérer du texte dans le document, * les modes visuels, qui permettent de sélectionner une portion de texte, * le mode ligne de commande, qui permet d’utiliser les commandes héritées d'Ex : `:write`, `:s`, `:g`, etc. ##### Le concept de verbe / opérateur + movement + destination C’est pour moi LA killer feature de Vim, surtout visible dans les modes normal et visuels. En gros, le modèle d’interaction est basé sur la notion de langage. Il y a : * des "opérateurs", des verbes conjugués à l’impératif comme "efface", "copie", "remplace", * des compléments d’objet directs comme "la ligne 78", "ce texte entre parenthèses", "d’ici à la fin du paragraphe", * des compléments d’objet indirects comme "en dessous de la ligne 27" ou "au début du buffer", * et des compléments circonstanciels comme "10 fois". Avec tout ça, on donne des commandes à la machine selon une syntaxe proche de celle d’un langage parlé et elle obéit : "colle le texte contenu dans le presse papier 50 fois", "copie (d’ici) jusqu’à la prochaine parenthèse ouvrante", etc. Dans un éditeur de texte classique, la première se dit "ctrl+v ctrl+v ... ctrl+v", ce qui n’a presque rien à voir avec la tâche telle qu’imaginée : "colle truc 50 fois" est devenu "colle colle ... colle", ce qui est très peu expressif. Notre pensée abstraite de haut niveau doit être transformée en une série d’action concrètes de bas niveau qui n’ont que très peu de sens et souvent rien à voir avec la pensée haut niveau. Dans Vim, la première commande se dit "50p", ce qui est très proche de la tâche telle qu’imaginée. La syntaxe est peut-être un peu sèche et les éléments sont peut-être ordonnés différemment qu’en français, mais ça reste tout à fait abordable et très proche de ce qu’on a dans la tête. L’étape suivante est exactement la même que lorsqu’on apprend une langue étrangère : penser dans la langue. Apprendre Vim, c’est apprendre une grammaire simple et un vocabulaire expressif qui s’enrichit au fur et à mesure où on avance. #### La notion de range Vim hérite plein de trucs de vi, qui hérite lui-même plein de trucs de ex. Dans vim, toutes les commandes qui commencent par un "deux points" sont des "commandes Ex", qui agissent sur des lignes car ex était un éditeur de ligne. Comme dans ex, ces commandes prennent des adresses (une seule ligne) et des ranges (de telle ligne à telle autre). Une ligne peut être indiquée par son numéro, par un offset, par une recherche, par un marqueur, etc. C’est un outil extrêmement puissant. Par exemple, la commande suivante copie les lignes 10 à 24 en fin de document : :10,24t$ Celle-ci rassemble toutes les lignes contenant `const` dans la fonction courante vers le haut du corps de la fonction : :?func?,/^}/g/const/m?func? C'est d’une élégance insoutenable. #### D'autres concepts de base (window, tab, buffer, split, etc.) On a toujours au moins un "buffer", une "fenêtre" et une "tab page". Un buffer peut être affiché dans une ou plusieurs "fenêtres", une "tab page" est un rassemblement de "fenêtres". Contrairement à la plupart des éditeurs de texte il ne peut pas y avoir de relation 1-à-1 entre un buffer et une fenêtre ou entre un buffer et une tab page. C’est un piège dans lequel tous les nouveaux tombent. #### Tu l’utilises pour quels genre d’édition J’utilise Vim de deux façons différentes : de longues sessions de programmation et des éditions rapides (config, git commit, etc.), pratiquement tout le temps dans un terminal. #### Les colorschemes La dernière fois que j’ai checké il y en avait littéralement des milliers, du simple qui marche partout, utilisé par quelques barbus ronchons, à l’usine à gaz buggée à mort, utilisée par la dernière génération de boutonneux. J’en ai réalisé quelques uns, même, comme [Apprentice](https://github.com/romainl/Apprentice), ainsi qu’[un modèle simple à utiliser](https://github.com/romainl/vim-rnb). Maintenant qu’on peut utiliser toutes les valeurs hexadécimales, même dans le terminal, c’est la fête. Pour trouver des colorschemes, je recommande [VimColors](http://vimcolors.com/). #### Les binding Vim dans les IDEs Peut-être utile pour accompagner l’apprentissage de Vim mais passé un certain niveau c’est l’uncanny valley. C’est un des problèmes causés par des années de Vim, d’ailleurs : ça rend exigeant. #### Le terminal Le nerf de la guerre d’un Vim qui fonctionne tmux? ### Vim écosystème #### La gestion des plugins Si on a beaucoup de plugins ça peut devenir compliqué sans plugin manager. Le plus populaire est [vim-plug](https://github.com/junegunn/vim-plug). Les plugins les plus utilisés * [fugitive](https://github.com/tpope/vim-fugitive), un client Git bien intégré à Vim * [surround](https://github.com/tpope/vim-surround), permet de jouer avec les paires de caractères : (), {}, etc. Souvent considéré comme un indispensable. * [ALE](https://github.com/dense-analysis/ale), beaucoup plus qu’un linter, * [YouCompleteMe](https://github.com/ycm-core/YouCompleteMe), beaucoup plus que de l’autocompletion. Vim et les plugins VSCode (via LSP) Les spécifications de pas mal de fonctionnalités de Visual Studio Code sont actuellement publiées, ce qui permet à d’autres outils de développement de bénéficier de l’étendue de son ecosystème. Il y a [LSP](https://langserver.org/), par exemple, qui permet d’implémenter des serveurs pour n’importe quel langage et des clients pour n’importe quel éditeur. Les clients à suivre pour Vim son [lsc](https://github.com/natebosch/vim-lsc) et [CoC](https://github.com/neoclide/coc.nvim). Peut-être aurons-nous une intégration native un jour ? Il y a aussi [DAP](https://microsoft.github.io/debug-adapter-protocol/) qui est utilisé par [Vimspector](https://github.com/puremourning/vimspector) pour fournir une interface de débogage avancée. #### La navigation entre fichiers Un faux problème, souvent résolu en mode "brute force" par manque de volonté d’apprendre à se servir des fonctionnalités de base. Du coup on a des dizaines de plugins fantaisistes et des générations de vimmers superficiels. C’est triste. En vrai, `:edit`, `:find` et `:buffer` sont rapides et versatiles. Il suffit de prendre le temps d’apprendre à s’en servir. Il existe un nombre hallucinant de plugins pour naviguer les fichiers alors que c’est si simple et rapide avec les outils natifs. #### La vérification orthographique La fonctionnalité est incluse de base. Il faut néanmoins l’activer avec `:help ’spell’` et, si on veut de l’aide pour autre chose que de l’anglais, installer des dictionnaires. Ça sonne plus compliqué que ça ne l’est vraiment. ### Des tips #### Indentation * [Tout savoir sur l'indentation dans Vim](https://tedlogan.com/techblog3.html) * `gg=G` pour réparer l’indentation d’un buffer en entier * `:help ’equalprg’` pour indiquer à Vim quel programme externe utiliser #### Paramètres custom par fichier via modeline Voir `:help modeline` pour des exemples. Je ne suis pas hyper fan en général que je trouve ça un peu sale de mélanger data et metada mais ça peut être bien en bas d’un fichier Markdown dont on sait qu’il va être édité dans Vim : [//]: # ( Vim: set spell spelllang=en: ) En pratique, je suggère plutôt [editorconfig](https://editorconfig.org/) pour les réglages d’indentation et compagnie. #### Vim et git Fugitive, mentionné plus haut, est très populaire. Pour ma part, je préfère garder mon éditeur de texte pour éditer du texte et utiliser d’autres outils spécialisés pour d’autres tâches spécialisées. J’aime beaucoup [tig](https://jonas.github.io/tig/), que j’utilise au jour le jour depuis des années, et j’ai découvert [git-jump](https://github.com/git/git/tree/master/contrib/git-jump) récemment, qui a fait une entrée fracassante dans mon workflow. Sinon, pour les commandes basiques, un simple `:!git ` fait largement le taf. #### Les macros Une macro est une séquence de commande. On peut enregistrer une macro dans le registre `q` : qq 02wciwfoo q et la rejouer sur plusieurs lignes, par exemple : :23,45normal! @q Mais avec un peu de pratique on peut complètement zapper la phase « enregistrement » : :23,45normal! 02wciwfoo Les macros sont un outil d’automatisation extraordinaire qui épate facilement le spectateur. Voir `:help complex-repeat`. #### Copier dans le buffer de l’OS (ctrl+c ctrl+v) Pour ça, l’idéal est d’avoir un Vim compilé avec la fonctionnalité "clipboard". Si c’est pas possible on peut bricoler des trucs avec `xclip`/`pbcopy`/etc. ou utiliser les fonctionnalités de copier/coller du terminal. Le clipboard système est représenté par le registre `+` dans vim. Donc copier dans le clipboard: `"+y`, et ensuite coller, `"+p`. Note que `"` est la sélection de registre. #### Remplacer via des expressions régulières La substitution, basée sur les expressions régulières ou pas, est une pratique courante dans Vim. Par exemple, pour remplacer toutes les occurrences de `java` par `kotlin` dans le buffer courant : :%s/java/kotlin/g Voir `:help :s` et le site [Vim Regular Expressions 101](http://vimregex.com/) car Vim utilise un dialecte spécial. #### Mode vi dans le shell Readline, la bibliothèque utilisée par bash pour gérer l’invite de commande, utilise des raccourcis inspirés par Emacs par défaut. On peut changer ça en ajoutant la ligne suivante dans `~/.inputrc`: set editing-mode vi Personnellement, je préfère garder les raccourcis par défaut et éditer mes commandes directement dans Vim, avec `Ctrl-x Ctrl-e`. Si vous ave mis le mode vi, alors pour éditer la commande dans vim, tapez `ESC` `v`. #### Vimdiff On peut utiliser Vim pour afficher des diffs côte à côte et même pour gérer les merge conflicts dans Git. Voir `:help diff` pour les détails sanglants. ### Aller plus loin #### Livres * [Practical Vim](https://pragprog.com/book/dnvim2/practical-vim-second-edition) * [Modern Vim](https://pragprog.com/book/modvim/modern-vim) * [Learn Vimscript The Hard Way](https://learnvimscriptthehardway.stevelosh.com/) * [The Viml Primer](https://pragprog.com/book/bkviml/the-viml-primer) #### Histoire de vim * [The History Of Vim](https://medium.com/@jovica/the-history-of-vim-b707758fb54f#.u3o96g3ib) * [Where Vim Came From](https://twobithistory.org/2018/08/05/where-vim-came-from.html) * [Bram Moolenaar Discusses Developing the Popular Text Editor, How He Uses It, and Version 8](http://www.hostingadvice.com/blog/vim-creator-champions-charityware/) * [10 Questions with Vim’s creator, Bram Moolenaar](http://www.binpress.com/blog/2014/11/19/vim-creator-bram-moolenaar-interview/) #### Ressources * [Vim Galore](https://github.com/mhinz/vim-galore) * [Idiomatic Vimrc](https://github.com/romainl/idiomatic-vimrc) * [Seven habits of effective text editing](https://www.moolenaar.net/habits.html) * `:help user-manual` * [Vimways](https://vimways.org) #### Meetups * [Tuppervim](https://tuppervim.org/) #### Communauté * [#vim sur Freenode](https://www.vi-improved.org/) * #vim-fr sur freenode * [r/vim](https://www.reddit.com/r/vim/) sur reddit * [le tag Vim](https://stackoverflow.com/questions/tagged/vim/) sur Stack Overflow * [le site Stack Exchange dédié à Vim](https://vi.stackexchange.com/) #### En vrac * [Vim 9 ?](https://groups.google.com/forum/#!topic/vim_dev/__gARXMigYE) * [Comment quitter Vim de manière... créative](https://github.com/hakluke/how-to-exit-vim/blob/master/README.md) * [Vim cheatsheet](http://michael.peopleofhonoronly.com/vim/) * [Bonne explication d’un beau vimrc en détails](https://dougblack.io/words/a-good-vimrc.html) * [Tmux et Vim ensemble avec les bons plugins](https://blog.bugsnag.com/tmux-and-vim/) * [Been using Vim for two years because I didn’t figure how to quit it!](https://twitter.com/iamdevloper/status/435555976687923200) * [Vim primer and tutorial](http://danielmiessler.com/study/vim/) * [Resources Vim](https://vim.zeef.com/patrick.schanen) * [Des stickers pour clavier Mac pour se rappeler des raccourcis](https://www.editorskeys.com/products/silicone-editing-covers/vim-keyboard-cover-retina/) ## Nous contacter Soutenez Les Cast Codeurs sur Patreon [Faire un crowdcast ou une crowdquestion](https://lescastcodeurs.com/crowdcasting/) Contactez-nous via twitter sur le groupe Google ou sur le site web

The latest Ubuntu LTS is here, but does it live up to the hype? And how practical are the new ZFS features? We dig into the performance, security, and stability of Focal Fossa. Plus our thoughts on the new KWin fork, if Bleachbit is safe, and a quick Fedora update. Special Guests: Brent Gervais and Drew DeVore.

En este episodio del podcast voy a combinar algunas de las ideas y conceptos sobre los que te he comentado en episodios anteriores. Así en la coctelera entran el episodio 24 en el que te hablé de tener un servidor por cuatro euros, pasando por el episodio 31 que te comenté sobre la seguridad en las nubes, incluyendo el episodio 45 sobre gestionar contraseñas, para terminar con el episodio 82 sobre como tener tu servidor en un USB. Y es que precisamente, el episodio del hoy te explico como puedes montar un gestor de contraseñas en tu Raspberry Pi. Por supuesto, lo suyo es que sea la Raspberry Pi Zero, por aquello de que la puedes llevar contigo a cualquier sitio. Con ello, al final, se trata de mantener tu privacidad en una Raspbey Pi, tus secretos más íntimos, aquello que quieres que quede lo mas inaccesible posible. Le llamo gestor de contraseñas, aunque el desarrollador del software en cuestión lo denomina como gestor de secretos, y es que esta definición se aproxima mas a lo que realmente es esta aplicación. Sin embargo, eso de gestor de secretos, no me terminaba de sonar bien, así que he preferido dejarlo así, como un gestor de contraseñas portable. Tu privacidad en una Raspberry Pi Zero Lo que he publicado esta semana Continuando con la serie de artículos sobre la ejecución de procesos en segundo plano, y como desacoplar el proceso del terminal, he escrito un artículo sobre tmux. Tmux, es algo mas que una herramienta para desacoplar procesos del terminal. Se trata de una herramienta que te permite gestionar en una sola ventana tantos terminales como seas capaz.El otro artículo de la semana se trata de un nuevo capítulo del tutorial sobre scripts en Bash. En este caso se refiere a como realizar operaciones matemáticas en Bash, y aunque ya lo traté por encima en un capítulo anterior, he querido darle la importancia que se merece. Aplicaciones Respecto a aplicaciones de terceros, y por si no escuchaste el podcast del lunes, he subido al repositorio que creé para este caso la última versión de Sunflower. Si no conoces Sunflower, porque no escuchaste el podcast del lunes, indicarte que se trata de un gestor de archivos de doble panel, altamente personalizable y muy productivo.Sigo subiendo extensiones a al repositorio de extensiones de GNOME Shell. En este caso he subido una extension que te permite desactivar tu webcam en Ubuntu. En este caso, al hacerlo desde repositorio, tienes la ventaja que un paso que tenías que hacer vía terminal te lo ahorras, porque lo he incluido directamente en la instalación. Mas información en las notas del podcast sobre tu privacidad en una Raspberry Pi Zero

En este episodio del podcast voy a combinar algunas de las ideas y conceptos sobre los que te he comentado en episodios anteriores. Así en la coctelera entran el episodio 24 en el que te hablé de tener un servidor por cuatro euros, pasando por el episodio 31 que te comenté sobre la seguridad en las nubes, incluyendo el episodio 45 sobre gestionar contraseñas, para terminar con el episodio 82 sobre como tener tu servidor en un USB. Y es que precisamente, el episodio del hoy te explico como puedes montar un gestor de contraseñas en tu Raspberry Pi. Por supuesto, lo suyo es que sea la Raspberry Pi Zero, por aquello de que la puedes llevar contigo a cualquier sitio. Con ello, al final, se trata de mantener tu privacidad en una Raspbey Pi, tus secretos más íntimos, aquello que quieres que quede lo mas inaccesible posible. Le llamo gestor de contraseñas, aunque el desarrollador del software en cuestión lo denomina como gestor de secretos, y es que esta definición se aproxima mas a lo que realmente es esta aplicación. Sin embargo, eso de gestor de secretos, no me terminaba de sonar bien, así que he preferido dejarlo así, como un gestor de contraseñas portable. Tu privacidad en una Raspberry Pi Zero Lo que he publicado esta semana Continuando con la serie de artículos sobre la ejecución de procesos en segundo plano, y como desacoplar el proceso del terminal, he escrito un artículo sobre tmux. Tmux, es algo mas que una herramienta para desacoplar procesos del terminal. Se trata de una herramienta que te permite gestionar en una sola ventana tantos terminales como seas capaz.El otro artículo de la semana se trata de un nuevo capítulo del tutorial sobre scripts en Bash. En este caso se refiere a como realizar operaciones matemáticas en Bash, y aunque ya lo traté por encima en un capítulo anterior, he querido darle la importancia que se merece. Aplicaciones Respecto a aplicaciones de terceros, y por si no escuchaste el podcast del lunes, he subido al repositorio que creé para este caso la última versión de Sunflower. Si no conoces Sunflower, porque no escuchaste el podcast del lunes, indicarte que se trata de un gestor de archivos de doble panel, altamente personalizable y muy productivo.Sigo subiendo extensiones a al repositorio de extensiones de GNOME Shell. En este caso he subido una extension que te permite desactivar tu webcam en Ubuntu. En este caso, al hacerlo desde repositorio, tienes la ventaja que un paso que tenías que hacer vía terminal te lo ahorras, porque lo he incluido directamente en la instalación. Mas información en las notas del podcast sobre tu privacidad en una Raspberry Pi Zero

On this week's episode, Chris is joined by Edward Loveall, former thoughtbot design apprentice and now thoughtbot developer. After a quick chat about Edward's thoughtbot origin story, podcasts, and DNS, they dig into the heart of the conversation talking about their respective "must have" developer tools on new machines. edwardloveall.com thoughtbot apprenticeship Domain Name Sanity Heroku DNSimple Amazon Route53 Giant Robots podcast Edward's episode on Giant Robots talking about the apprenticeship Tweet about using a podcast as internal onboarding Hammerspoon Slate Spectacle Divvy Vim Tmux VSCode Live share tmate Alfred Alfred clipboard AppleScript Arch Linux Jeff Goldblum iMac Commercials Feedly Feedbin ReadKit JSON Feed CSS & Privacy - Why can't I set the font size of a visited link? Lobsters Thank you to CircleCI for sponsoring this episode.

Flotter Dreier ohne Elan bis kurz vor Schluss. Dann kramen wir in unserer digitalen und sozialen Vergangenheit.

What is tmux • Using tmux • Tmux windows and panes --- Support this podcast: https://anchor.fm/hackerculture/support

My Ruby Story 009 Brian Hogan On this episode we have another My Ruby Story and there is a good chance you might recognize him, he is one of Devchat.tv’s panelists Brian Hogan. Aside from being a panelists on Ruby Rouges, he also has a couple other projects like codecaster.io as well as Railsmentors.org. How did you get into programming? Brain talks about how his Dad has an old Apple 2 computer. His father was a teacher for the blind and the computer had a box on it that would talk. His Dad taught him that computers can have programs written for them and make them do things. Brain talks about having math issues one evening and his Dad helped by making a math program that would quiz him. His Dad wasn’t a programmer but he had picked up some of it from being around it. Brain talks about how the library had games you could get for the Apple 2 but you had to write code into the computer to make it work. He started tweaking the code to learn that it adjusted things in the game like the speed of the spaceship or the damage of the bomb. Brian’s First Program Brian’s first program was in fourth grade. He had an assignment on the topic of the seas and instead of doing a typical handwritten assignment he created a program for it. He learned that he could make the computer do things. Over time Brian got interested in other things, planning to go to school for law. His Dad lost his job making his plans for law school unreachable without student loan debt. He started making money on the side repairing and building computers. Computers solving problems He talks about how he never really got into the computer science level of things, but he was always excited about being able to solve people’s problems with computers. He remembers getting internet for the first time. It was Netscape and it came with a book on how to setup the internet and then in the last chapter it had a section teaching how to make a webpage with HTML. He loved making websites and so he made pages for businesses and made money on the side. He went to college aiming for computer science and then when he got into classes like computational theory, he found that it was boring to him still. He changed his major to business. He then got a job working for the college working with website stuff. The developer for the pages ended up quitting and so they asked Brian to help out. So he learned Microsoft server SQL and ASP. He adds that essentially he fell into web development by accident. He talks about his code being bad until he learned Ruby, crediting Ruby with making object oriented programming easier to understand. Charles mentions that he felt the same way in school, it wasn’t until he needed to fix a real problem that programming really started to seem useful and fun. Brian talks about how he isn’t really the best programmer, but his strengths are helping other people to program. He has trained many people to program since then. Learning with Context He talks about in school how they throw JavaScript at you and teach you the higher concepts before understanding it. He tells about how doing something like teaching Git on the first day doesn’t make sense because the students don’t understand why they need it. He suggests that the thing that is missing from the curriculum is the real work connection. Majority of adults need to be able to connect what they are learning to something they have already learned. Context is important for learning. How did you get into Ruby? Brian talks about doing PHP for a while as well as ASP. He was working with a project as an Oracle DBA. They were moving from Java to an Oracle Database. But no one there knew what Java was and a person there named Bruce suggested that the work they were doing would be better written in Ruby. The team disagreed but afterward one day Brian was talking to Bruce about a side project he was working on and how he wasn’t accomplishing it the way he wanted to. Bruce asked him to get lunch with him. Brian then talks about how in life if someone very smart asks you to get lunch that you should drop everything and do it. In a single night he was able to accomplish everything he was trying to. He took his project to work the next day and they said they wouldn’t be able to use it on Windows. Brian started working on finding ways to deploy it, and that has been the starting point of Ruby for Brian. He went to Rails full time after that. Publishing an article on how to get it deployed. His work with Ruby led to him teaching and writing books. When he needs to make something heavily data driven he always reaches for Ruby. He isn’t interested in scalability because usually he is working on a small business process behind the firewall used by less than 100 people. Framework Peer Pressure Brian talks about the fear and pressure to use the latest and greatest frameworks in the development community. He talks about how the only people who know what framework a person uses is the developer and the peers. You don’t get paid to impress peers in the community. A developer gets paid to solve peoples problems. Charles and Brian add that using new frameworks are great and can teach you new ways to solve problems, but no matter how a person solves a problem, it should be celebrated. Learn new things but don’t make people feel bad for not doing things the same way you do them. Brian adds that another reason he likes Rails is that it has a lot of things that came from basecamp and it is a well developed and tested and the framework is strong. He talks about how sometimes frameworks come out and they weren’t well thought out. Rails is not an academic framework but it is easier to integrate or upgrade to by design. What contributions have you made to the Ruby community? Brian talks about getting the Rails deploy working for Windows is one of his proudest moments. Other than that his contribution has been mainly helping people find mentors at Railsmentors.org. On Railsmentors.org, most of the work is done by volunteers and help a lot of people. Charles adds that sometimes open source project contributions tend to get glorified but things like Railsmentors.org are really what make the community great. What are you working on now? Brian talks about how he is working on a book but he can’t tell much about it at the moment. He also works on the content team on Digital Ocean. He helps other community authors with their writing and to get it published and out. He also handles some system admin background to test that each article works and he finds it a good way to keep his skills tuned. He is also working on a project in Elixir for teachers to work in the classroom better. For a teacher teaching development they can use the program, CodeCaster, to display code to the screens and the students can do things like flag things they don’t understand or let the teacher know that it’s moving too fast. It allows the students send up code for the teacher to check as well as the teacher get a snapshot of what’s on the students screen to check on them. Picks Brian Exercises for Programmers Tmux 2 Productive Mouse-Free Development Charles Coursera on AI Artificial Intelligence in Python Links Twitter bphogan.com

My Ruby Story 009 Brian Hogan On this episode we have another My Ruby Story and there is a good chance you might recognize him, he is one of Devchat.tv’s panelists Brian Hogan. Aside from being a panelists on Ruby Rouges, he also has a couple other projects like codecaster.io as well as Railsmentors.org. How did you get into programming? Brain talks about how his Dad has an old Apple 2 computer. His father was a teacher for the blind and the computer had a box on it that would talk. His Dad taught him that computers can have programs written for them and make them do things. Brain talks about having math issues one evening and his Dad helped by making a math program that would quiz him. His Dad wasn’t a programmer but he had picked up some of it from being around it. Brain talks about how the library had games you could get for the Apple 2 but you had to write code into the computer to make it work. He started tweaking the code to learn that it adjusted things in the game like the speed of the spaceship or the damage of the bomb. Brian’s First Program Brian’s first program was in fourth grade. He had an assignment on the topic of the seas and instead of doing a typical handwritten assignment he created a program for it. He learned that he could make the computer do things. Over time Brian got interested in other things, planning to go to school for law. His Dad lost his job making his plans for law school unreachable without student loan debt. He started making money on the side repairing and building computers. Computers solving problems He talks about how he never really got into the computer science level of things, but he was always excited about being able to solve people’s problems with computers. He remembers getting internet for the first time. It was Netscape and it came with a book on how to setup the internet and then in the last chapter it had a section teaching how to make a webpage with HTML. He loved making websites and so he made pages for businesses and made money on the side. He went to college aiming for computer science and then when he got into classes like computational theory, he found that it was boring to him still. He changed his major to business. He then got a job working for the college working with website stuff. The developer for the pages ended up quitting and so they asked Brian to help out. So he learned Microsoft server SQL and ASP. He adds that essentially he fell into web development by accident. He talks about his code being bad until he learned Ruby, crediting Ruby with making object oriented programming easier to understand. Charles mentions that he felt the same way in school, it wasn’t until he needed to fix a real problem that programming really started to seem useful and fun. Brian talks about how he isn’t really the best programmer, but his strengths are helping other people to program. He has trained many people to program since then. Learning with Context He talks about in school how they throw JavaScript at you and teach you the higher concepts before understanding it. He tells about how doing something like teaching Git on the first day doesn’t make sense because the students don’t understand why they need it. He suggests that the thing that is missing from the curriculum is the real work connection. Majority of adults need to be able to connect what they are learning to something they have already learned. Context is important for learning. How did you get into Ruby? Brian talks about doing PHP for a while as well as ASP. He was working with a project as an Oracle DBA. They were moving from Java to an Oracle Database. But no one there knew what Java was and a person there named Bruce suggested that the work they were doing would be better written in Ruby. The team disagreed but afterward one day Brian was talking to Bruce about a side project he was working on and how he wasn’t accomplishing it the way he wanted to. Bruce asked him to get lunch with him. Brian then talks about how in life if someone very smart asks you to get lunch that you should drop everything and do it. In a single night he was able to accomplish everything he was trying to. He took his project to work the next day and they said they wouldn’t be able to use it on Windows. Brian started working on finding ways to deploy it, and that has been the starting point of Ruby for Brian. He went to Rails full time after that. Publishing an article on how to get it deployed. His work with Ruby led to him teaching and writing books. When he needs to make something heavily data driven he always reaches for Ruby. He isn’t interested in scalability because usually he is working on a small business process behind the firewall used by less than 100 people. Framework Peer Pressure Brian talks about the fear and pressure to use the latest and greatest frameworks in the development community. He talks about how the only people who know what framework a person uses is the developer and the peers. You don’t get paid to impress peers in the community. A developer gets paid to solve peoples problems. Charles and Brian add that using new frameworks are great and can teach you new ways to solve problems, but no matter how a person solves a problem, it should be celebrated. Learn new things but don’t make people feel bad for not doing things the same way you do them. Brian adds that another reason he likes Rails is that it has a lot of things that came from basecamp and it is a well developed and tested and the framework is strong. He talks about how sometimes frameworks come out and they weren’t well thought out. Rails is not an academic framework but it is easier to integrate or upgrade to by design. What contributions have you made to the Ruby community? Brian talks about getting the Rails deploy working for Windows is one of his proudest moments. Other than that his contribution has been mainly helping people find mentors at Railsmentors.org. On Railsmentors.org, most of the work is done by volunteers and help a lot of people. Charles adds that sometimes open source project contributions tend to get glorified but things like Railsmentors.org are really what make the community great. What are you working on now? Brian talks about how he is working on a book but he can’t tell much about it at the moment. He also works on the content team on Digital Ocean. He helps other community authors with their writing and to get it published and out. He also handles some system admin background to test that each article works and he finds it a good way to keep his skills tuned. He is also working on a project in Elixir for teachers to work in the classroom better. For a teacher teaching development they can use the program, CodeCaster, to display code to the screens and the students can do things like flag things they don’t understand or let the teacher know that it’s moving too fast. It allows the students send up code for the teacher to check as well as the teacher get a snapshot of what’s on the students screen to check on them. Picks Brian Exercises for Programmers Tmux 2 Productive Mouse-Free Development Charles Coursera on AI Artificial Intelligence in Python Links Twitter bphogan.com

My Ruby Story 009 Brian Hogan On this episode we have another My Ruby Story and there is a good chance you might recognize him, he is one of Devchat.tv’s panelists Brian Hogan. Aside from being a panelists on Ruby Rouges, he also has a couple other projects like codecaster.io as well as Railsmentors.org. How did you get into programming? Brain talks about how his Dad has an old Apple 2 computer. His father was a teacher for the blind and the computer had a box on it that would talk. His Dad taught him that computers can have programs written for them and make them do things. Brain talks about having math issues one evening and his Dad helped by making a math program that would quiz him. His Dad wasn’t a programmer but he had picked up some of it from being around it. Brain talks about how the library had games you could get for the Apple 2 but you had to write code into the computer to make it work. He started tweaking the code to learn that it adjusted things in the game like the speed of the spaceship or the damage of the bomb. Brian’s First Program Brian’s first program was in fourth grade. He had an assignment on the topic of the seas and instead of doing a typical handwritten assignment he created a program for it. He learned that he could make the computer do things. Over time Brian got interested in other things, planning to go to school for law. His Dad lost his job making his plans for law school unreachable without student loan debt. He started making money on the side repairing and building computers. Computers solving problems He talks about how he never really got into the computer science level of things, but he was always excited about being able to solve people’s problems with computers. He remembers getting internet for the first time. It was Netscape and it came with a book on how to setup the internet and then in the last chapter it had a section teaching how to make a webpage with HTML. He loved making websites and so he made pages for businesses and made money on the side. He went to college aiming for computer science and then when he got into classes like computational theory, he found that it was boring to him still. He changed his major to business. He then got a job working for the college working with website stuff. The developer for the pages ended up quitting and so they asked Brian to help out. So he learned Microsoft server SQL and ASP. He adds that essentially he fell into web development by accident. He talks about his code being bad until he learned Ruby, crediting Ruby with making object oriented programming easier to understand. Charles mentions that he felt the same way in school, it wasn’t until he needed to fix a real problem that programming really started to seem useful and fun. Brian talks about how he isn’t really the best programmer, but his strengths are helping other people to program. He has trained many people to program since then. Learning with Context He talks about in school how they throw JavaScript at you and teach you the higher concepts before understanding it. He tells about how doing something like teaching Git on the first day doesn’t make sense because the students don’t understand why they need it. He suggests that the thing that is missing from the curriculum is the real work connection. Majority of adults need to be able to connect what they are learning to something they have already learned. Context is important for learning. How did you get into Ruby? Brian talks about doing PHP for a while as well as ASP. He was working with a project as an Oracle DBA. They were moving from Java to an Oracle Database. But no one there knew what Java was and a person there named Bruce suggested that the work they were doing would be better written in Ruby. The team disagreed but afterward one day Brian was talking to Bruce about a side project he was working on and how he wasn’t accomplishing it the way he wanted to. Bruce asked him to get lunch with him. Brian then talks about how in life if someone very smart asks you to get lunch that you should drop everything and do it. In a single night he was able to accomplish everything he was trying to. He took his project to work the next day and they said they wouldn’t be able to use it on Windows. Brian started working on finding ways to deploy it, and that has been the starting point of Ruby for Brian. He went to Rails full time after that. Publishing an article on how to get it deployed. His work with Ruby led to him teaching and writing books. When he needs to make something heavily data driven he always reaches for Ruby. He isn’t interested in scalability because usually he is working on a small business process behind the firewall used by less than 100 people. Framework Peer Pressure Brian talks about the fear and pressure to use the latest and greatest frameworks in the development community. He talks about how the only people who know what framework a person uses is the developer and the peers. You don’t get paid to impress peers in the community. A developer gets paid to solve peoples problems. Charles and Brian add that using new frameworks are great and can teach you new ways to solve problems, but no matter how a person solves a problem, it should be celebrated. Learn new things but don’t make people feel bad for not doing things the same way you do them. Brian adds that another reason he likes Rails is that it has a lot of things that came from basecamp and it is a well developed and tested and the framework is strong. He talks about how sometimes frameworks come out and they weren’t well thought out. Rails is not an academic framework but it is easier to integrate or upgrade to by design. What contributions have you made to the Ruby community? Brian talks about getting the Rails deploy working for Windows is one of his proudest moments. Other than that his contribution has been mainly helping people find mentors at Railsmentors.org. On Railsmentors.org, most of the work is done by volunteers and help a lot of people. Charles adds that sometimes open source project contributions tend to get glorified but things like Railsmentors.org are really what make the community great. What are you working on now? Brian talks about how he is working on a book but he can’t tell much about it at the moment. He also works on the content team on Digital Ocean. He helps other community authors with their writing and to get it published and out. He also handles some system admin background to test that each article works and he finds it a good way to keep his skills tuned. He is also working on a project in Elixir for teachers to work in the classroom better. For a teacher teaching development they can use the program, CodeCaster, to display code to the screens and the students can do things like flag things they don’t understand or let the teacher know that it’s moving too fast. It allows the students send up code for the teacher to check as well as the teacher get a snapshot of what’s on the students screen to check on them. Picks Brian Exercises for Programmers Tmux 2 Productive Mouse-Free Development Charles Coursera on AI Artificial Intelligence in Python Links Twitter bphogan.com

This week on BSD Now, we will be discussing a wide variety of topics including Routers, Run-Controls, the “Rule” of silence and some This episode was brought to you by Headlines Ports no longer build on EOL FreeBSD versions (https://www.reddit.com/r/freebsd/comments/5ouvmp/ports_no_longer_build_on_eol_freebsd_versions/) The FreeBSD ports tree has been updated to automatically fail if you try to compile ports on EOL versions of FreeBSD (any version of 9.x or earlier, 10.0 - 10.2, or 11 from before 11.0) This is to prevent shooting yourself in the food, as the compatibility code for those older OSes has been removed now that they are no longer supported. If you use pkg, you will also run into problems on old releases. Packages are always built on the oldest supported release in a branch. Until recently, this meant packages for 10.1, 10.2, and 10.3 were compiled on 10.1. Now that 10.1 and 10.2 are EOL, packages for 10.x are compiled on 10.3. This matters because 10.3 supports the new openat() and various other *at() functions used by capsicum. Now that pkg and packages are built on a version that supports this new feature, they will not run on systems that do not support it. So pkg will exit with an error as soon as it tries to open a file. You can work around this temporarily by using the pkg-static command, but you should upgrade to a supported release immediately. *** Improving TrueOS: OpenRC (https://www.trueos.org/blog/improving-trueos-openrc/) With TrueOS moving to a rolling-release model, we've decided to be a bit more proactive in sharing news about new features that are landing. This week we've posted an article talking about the transition to OpenRC In past episodes you've heard me mention OpenRC, but hopefully today we can help answer any of those lingering questions you may still have about it The first thing always asked, is “What is OpenRC?” OpenRC is a dependency-based init system working with the system provided init program. It is used with several Linux distributions, including Gentoo and Alpine Linux. However, OpenRC was created by the NetBSD developer Roy Marples in one of those interesting intersections of Linux and BSD development. OpenRC's development history, portability, and 2-clause BSD license make its integration into TrueOS an easy decision. Now that we know a bit about what it is, how does it behave differently than traditional RC? TrueOS now uses OpenRC to manage all system services, as opposed to FreeBSD's RC. Instead of using rc.d for base system rc scripts, OpenRC uses init.d. Also, every service in OpenRC has its own user configuration file, located in /etc/conf.d/ for the base system and /usr/local/etc.conf.d/ for ports. Finally, OpenRC uses runlevels, as opposed to the FreeBSD single- or multi- user modes. You can view the services and their runlevels by typing $ rc-update show -v in a CLI. Also, TrueOS integrates OpenRC service management into SysAdm with the Service Manager tool One of the prime benefits of OpenRC is much faster boot-times, which is important in a portable world of laptops (and desktops as well). But service monitoring and crash detection are also important parts of what make OpenRC a substantial upgrade for TrueOS. Lastly people have asked us about migration, what is done, what isn't? As of now almost all FreeBSD base system services have been migrated over. In addition most desktop-facing services required to run Lumina and the like are also ported. We are still going through the ports tree and converting legacy rc.d scripts to init.d, but the process takes time. Several new folks have begun contributing OpenRC scripts and we hope to have all the roughly 1k ports converted over this year. BSDRP Releases 1.70 (https://sourceforge.net/projects/bsdrp/files/BSD_Router_Project/1.70/) A new release of the BSD Router Project This distro is designed to replace high end routers, like those from Cisco and Juniper, with FreeBSD running on regular off-the-shelf server. Highlights: Upgraded to FreeBSD 11.0-STABLE r312663 (skip 11.0 for massive performance improvement) Re-Added: netmap-fwd (https://github.com/Netgate/netmap-fwd) Add FIBsync patch to netmap-fwd from Zollner Robert netmap pkt-gen supports IPv6, thanks to Andrey V. Elsukov (ae@freebsd.org) bird 1.6.3 (add BGP Large communities support) OpenVPN 2.4.0 (adds the high speed AEAD GCM cipher) All of the other packages have also been upgraded A lot of great work has been done on BSDRP, and it has also generated a lot of great benchmarks and testing that have resulted in performance increases and improved understanding of how FreeBSD networking scales across different CPU types and speeds *** DragonFlyBSD gets UEFI support (http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/7b1aa074fcd99442a1345fb8a695b62d01d9c7fd) This commit adds support for UEFI to the Dragonfly Installer, allowing new systems to be installed to boot from UEFI This script (http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/9d53bd00e9be53d6b893afd79111370ee0c053b0) provides a way to build a HAMMER filesystem that works with UEFI There is also a UEFI man page (http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/d195d5099328849c500d4a1b94d6915d3c72c71e) The install media (http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/5fa778d7b36ab0981ff9dcbd96c71ebf653a6a19) has also been updated to support booting from either UEFI or MBR, in the same way that the FreeBSD images work *** News Roundup The Rule of Silence (http://www.linfo.org/rule_of_silence.html) “The rule of silence, also referred to as the silence is golden rule, is an important part of the Unix philosophy that states that when a program has nothing surprising, interesting or useful to say, it should say nothing. It means that well-behaved programs should treat their users' attention and concentration as being valuable and thus perform their tasks as unobtrusively as possible. That is, silence in itself is a virtue.” This doesn't mean a program cannot be verbose, it just means you have to ask it for the additional output, rather than having it by default “There is no single, standardized statement of the Unix philosophy, but perhaps the simplest description would be: "Write programs that are small, simple and transparent. Write them so that they do only one thing, but do it well and can work together with other programs." That is, the philosophy centers around the concepts of smallness, simplicity, modularity, craftsmanship, transparency, economy, diversity, portability, flexibility and extensibility.” “This philosophy has been fundamental to the the fact that Unix-like operating systems have been thriving for more than three decades, far longer than any other family of operating systems, and can be expected to see continued expansion of use in the years to come” “The rule of silence is one of the oldest and most persistent design rules of such operating systems. As intuitive as this rule might seem to experienced users of such systems, it is frequently ignored by the developers of other types of operating systems and application programs for them. The result is often distraction, annoyance and frustration for users.” “There are several very good reasons for the rule of silence: (1) One is to avoid cluttering the user's mind with information that might not be necessary or might not even be desired. That is, unnecessary information can be a distraction. Moreover, unnecessary messages generated by some operating systems and application programs are sometimes poorly worded, and can cause confusion or needless worry on the part of users.” No news is good news. When there is bad news, error messages should be descriptive, and ideally tell the user what they might do about the error. “A third reason is that command line programs (i.e., all-text mode programs) on Unix-like operating systems are designed to work together with pipes, i.e., the output from one program becomes the input of another program. This is a major feature of such systems, and it accounts for much of their power and flexibility. Consequently, it is important to have only the truly important information included in the output of each program, and thus in the input of the next program.” Have you ever had to try to strip out useless output so you could feed that data into another program? “The rule of silence originally applied to command line programs, because all programs were originally command line programs. However, it is just as applicable to GUI (graphical user interfaces) programs. That is, unnecessary and annoying information should be avoided regardless of the type of user interface.” “A example is the useless and annoying dialog boxes (i.e., small windows) that pop up on the display screen with with surprising frequency on some operating systems and programs. These dialog boxes contain some obvious, cryptic or unnecessary message and require the user to click on them in order to close them and proceed with work. This is an interruption of concentration and a waste of time for most users. Such dialog boxes should be employed only in situations in which some unexpected result might occur or to protect important data.” It goes on to make an analogy about Public Address systems. If too many unimportant messages, like advertisements, are sent over the PA system, people will start to ignore them, and miss the important announcements. *** The Tao of tmux (https://leanpub.com/the-tao-of-tmux/read) An interesting article floated across my news feed a few weeks back. It's what essentially boils down to a book called the “Tao of tmux”, which immediately piqued my interest. My story may be similar to many of yours. I was initially raised on using screen, and screen only for my terminal session and multiplexing needs. Since then I've only had a passing interest in tmux, but its always been one of those utilities I felt was worthy of investing some more time into. (Especially when seeing some of the neat setups some of my peers have with it) Needless to say, this article has been bookmarked, and I've started digesting some of it, but thought it would be good to share with anybody else who finds them-self in a similar situation. The book starts off well, explaining in the simplest terms possible what Tmux really is, by comparing and contrasting it to something we are all familiar with, GUIS! Helpfully they also include a chart which explains some of the terms we will be using frequently when discussing tmux (https://leanpub.com/the-tao-of-tmux/read#leanpub-auto-window-manager-for-the-terminal) One of the things the author does recommend is also making sure you are up to speed on your Terminal knowledge. Before getting into tmux, a few fundamentals of the command line should be reviewed. Often, we're so used to using these out of street smarts and muscle memory a great deal of us never see the relation of where these tools stand next to each other. Seasoned developers are familiar with zsh, Bash, iTerm2, konsole, /dev/tty, shell scripting, and so on. If you use tmux, you'll be around these all the time, regardless of whether you're in a GUI on a local machine or SSH'ing into a remote server. If you want to learn more about how processes and TTY's work at the kernel level (data structures and all) the book The Design and Implementation of the FreeBSD Operating System (2nd Edition) by Marshall Kirk McKusick is nice. In particular, Chapter 4, Process Management and Section 8.6, Terminal Handling. The TTY demystified by Linus Åkesson (available online) dives into the TTY and is a good read as well. We had to get that shout-out of Kirk's book in here ;) From here the boot/article takes us on a whirlwind journey of Sessions, Windows, Panes and more. Every control- command is covered, information on how to customize your statusbar, tips, tricks and the like. There's far more here than we can cover in a single segment, but you are highly encouraged to bookmark this one and start your own adventure into the world of tmux. *** SDF Celebrates 30 years of service in 2017 (https://sdf.org/) HackerNews thread on SDF (https://news.ycombinator.com/item?id=13453774) “Super Dimension Fortress (SDF, also known as freeshell.org) is a non-profit public access UNIX shell provider on the Internet. It has been in continual operation since 1987 as a non-profit social club. The name is derived from the Japanese anime series The Super Dimension Fortress Macross; the original SDF server was a BBS for anime fans[1]. From its BBS roots, which have been well documented as part of the BBS: The Documentary project, SDF has grown into a feature-rich provider serving members around the world.” A public access UNIX system, it was many people's first access to a UNIX shell. In the 90s, Virtual Machines were rare, the software to run them usually cost a lot of money and no one had very much memory to try to run two operating systems at the same time. So for many people, these type of shell accounts were the only way they could access UNIX without having to replace the OS on their only computer This is how I first started with UNIX, eventually moving to paying for access to bigger machines, and then buying my own servers and renting out shell accounts to host IRC servers and channel protection bots. “On June 16th, 1987 Ted Uhlemann (handle: charmin, later iczer) connected his Apple ][e's 300 baud modem to the phone line his mother had just given him for his birthday. He had published the number the night before on as many BBSes around the Dallas Ft. Worth area that he could and he waited for the first caller. He had a copy of Magic Micro BBS which was written in Applesoft BASIC and he named the BBS "SDF-1" after his favorite Japanimation series ROBOTECH (Macross). He hoped to draw users who were interested in anime, industrial music and the Church of the Subgenius.” I too started out in the world of BBSes before I had access to the internet. My parents got my a dedicated phone line for my birthday, so I wouldn't tie up their line all the time. I quickly ended up running my own BBS, the Sudden Death BBS (Renegade (https://en.wikipedia.org/wiki/Renegade_(BBS)) on MS DOS) I credit this early experience for my discovery of a passion for Systems Administration, that lead me to my current career “Slowly, SDF has grown over all these years, never forgetting our past and unlike many sites on the internet, we actually have a past. Some people today may come here and see us as outdated and "retro". But if you get involved, you'll see it is quite alive with new ideas and a platform for opportunity to try many new things. The machines are often refreshed, the quotas are gone, the disk space is expanding as are the features (and user driven features at that) and our cabinets have plenty of space for expansion here in the USA and in Europe (Germany).” “Think about ways you'd like to celebrate SDF's 30th and join us on the 'bboard' to discuss what we could do. I realize many of you have likely moved on yourselves, but I just wanted you to know we're still here and we'll keep doing new and exciting things with a foundation in the UNIX shell.” *** Getting Minecraft to Run on NetBSD (https://www.reddit.com/r/NetBSD/comments/5mtsy1/getting_minecraft_to_run_on_netbsd/) One thing that doesn't come up often on BSDNow is the idea of gaming. I realize most of us are server folks, or perhaps don't play games (The PC is for work, use your fancy-smanzy PS4 and get off my lawn you kids) Today I thought it would be fun to highlight this post over at Reddit talking about running MineCraft on NetBSD Now I realize this may not be news to some of you, but perhaps it is to others. For the record my kids have been playing Minecraft on PC-BSD / TrueOS for years. It's the primary reason they are more often booted into that instead of Windows. (Funny story behind that - Got sick of all the 3rd party mods, which more often than not came helpfully bundled with viruses and malware) On NetBSD the process looks a bit different than on FreeBSD. First up, you'll need to enable Linux Emulation and install Oracle JRE (Not OpenJDK, that path leads to sadness here) The guide will then walk us through the process of fetching the Linux runtime packages, extracting and then enabling bits such as ‘procfs' that is required to run the Linux binaries. Once that's done, minecraft is only a simple “oracle8-jre /path/to/minecraft.jar” command away from starting up, and you'll be “crafting” in no time. (Does anybody even play survival anymore?) *** Beastie Bits UNIX on the Computer Chronicals (https://youtu.be/g7P16mYDIJw) FreeBSD: Atheros AR9380 and later, maximum UDP TX goes from 250mbit to 355mbit. (https://twitter.com/erikarn/status/823298416939659264) Capsicumizing traceroute with casper (https://reviews.freebsd.org/D9303) Feedback/Questions Jason - TarSnap on Windows (http://pastebin.com/Sr1BTzVN) Mike - OpenRC & DO (http://pastebin.com/zpHyhHQG) Anonymous - Old Machines (http://pastebin.com/YnjkrDmk) Matt - Iocage (http://pastebin.com/pBUXtFak) Hjalti - Rclone & FreeNAS (http://pastebin.com/zNkK3epM)

Maybe just don't?

Show notes: http://betweenscreens.fm/episodes/31

Pair Programming is an agile software development technique in which two programmers work together on the same development work at the same time. Many variants exist for this practice, each having there own merits and drawbacks.   From a business perspective, many companies are skeptical and critical of this practice because it incurs cost. Whether that cost is measured by time or by labor hours, determining a measure of success for pair programming is not an easy thing to do. In a world where metrics and numbers define ‘the bottom line' it is no surprise that pair programming is not used everywhere.   What does it provide for the business of product & software development? The benefits definitely outweigh the drawbacks from a developer perspective. Our Evan Light talks about the aspects of testing practices in pairing, tools, and many other secrets to unlocking the power pairing.   Evan Light (@elight) is a software developer with nearly 20 years of professional experience. Having a passion for community service, Evan has spent several years as a volunteer EMT. In 2008 Evan founded the Ruby DCamp “unconference” which he continues to organize and run each year. He is a respected member of the Ruby programming community and has spoken at several Ruby-related conferences over the years.   Evan has an extensive background in remote pair programming and recently spoke at RubyNation in Silver Springs, Maryland on the subject. Evan's talk was titled “Remote Pairing From the Comfort of Your Own Shell” where he spoke about his challenges & experiences in pair programming over the years and what has tools he uses today. Resources eXtreme Programming Explained - http://www.amazon.com/Extreme-Programming-Explained-Embrace-Change/dp/0201616416 Pomodoro technique - Agile Definition of Pair Programming -  http://en.wikipedia.org/wiki/Pair_programming #PairWithMe - http://www.pairprogramwith.me/ Ruby DCamp - http://rubydcamp.org and http://evan.tiggerpalace.com/articles/2012/10/06/the-dcamp-manifesto/ Vagrant - https://www.vagrantup.com/ Tmux - http://tmux.sourceforge.net/ Tmate - http://tmate.io/ Vimux - https://github.com/benmills/vimux My .emacs.d - https://github.com/elight/.emacs.d Pomodoro Technique - http://en.wikipedia.org/wiki/Pomodoro_Technique RubyMine - https://www.jetbrains.com/ruby/ Readme Driven Development - https://oncletom.io/talks/2014/okfestival/#/ J.B. Rainsberger “Integration Tests are a Scam” - http://vimeo.com/80533536 nitrous.io - https://www.nitrous.io/ Screen Hero - https://screenhero.com/ RubyNaition - http://www.rubynation.org/schedule/index Pairing Staircase - http://itnaut.com/pairing_staircase Evan on Twitter - https://twitter.com/elight: @elight   Evan's Site - http://tripledogdare.net or http://evan.tiggerpalace.com  

This week, Dave and Gunnar talk about more about civet cat scat, the TI-84 racket, my mobile backend, and Red Hat Cloud for Government. Soren would like to apologize for screaming bloody murder for the duration of this episode. Gunnar’s presentation au Quebec, mais pas en français. Dave enjoys Hard Core History on the Silver Line SELinux labeled NFS is super easy to configure on RHEL 7 HT Matt Micene: Catching up on the podcast, your missing Indonesian coffee animal is the Civet Cat. There’s a huge deal around “sustainable” and cruelty free gathering of scat… HT Erich Morisse: Your show got me thinking of my long neglected Yahoo! email account, and I wanted to see if there was any signal buried in the years of neglected spam. On a whim, I tried regex figuring most real people would have their name as FirstnamesLastname. By gum! It worked: from:"^[^/s]* [^/s]*$" -in:trash Worst part: Nope, no signal in the noise. (see pie chart) Ripe for disruption: The unstoppable TI-84 Plus: How an outdated calculator still holds a monopoly on classrooms See also Life imitating art: Facebook — for rich people (for just $9,000) Let’s recall Metcalfe’s law Related: New App Matches You With Others In Vicinity Who Wasted $2.99 On Same App USSS to check visitor blocks before they arrive at the White House Lauren is Code.org’s Student of the Week! Gunnar will be at Code for America 2014 in San Francisco September 23-25, NASCIO 2014 in Nashville September 28 to October 1, and the Red Hat Forum in Washington DC October 23 RHEL 5.11 Risk Report Red Hat welcomes FeedHenry! Red Hat Cloud for Government launched A Partner We Like: Autonomic’s ARCWRX Solution is Ready to Fill PaaS Void After DISA STAX Sunset Another Partner We Like Just as Much: Booz Allen Hamilton and Red Hat have teamed up to host the ManageIQ Design Summit October 7-8 D&G Job Title of the Week: Chaos Commander Gunnar did housekeeping this week Let’s talk about dotfiles and why they should all be on git Moved from screen to tmux, mostly because tmux is google-able Cupcake: help people avoid censorship by installing a Chrome extension Cutting Room Floor Prosthetic anti-surveillance face Goodnight, Dune George Mason University’s Green Machine pep band rages against the machine Hamster wheel standing desk Metástasis con Walter Blanco The Suitsy: The business suit onesie hybrid (“It’s like if a jumpsuit and a business suit had a lovechild.”) We Give Thanks Matt Micene and Erich Morisse for the follow up!

This week we'll be talking to Amitai Schlair of the NetBSD foundation about pkgsrc, NetBSD's future plans and much more. After that, if you've ever wondered what all this SSH stuff is about, today's tutorial has got you covered. We'll be showing you the basics of SSH, as well as how to combine it with tmux for persistent sessions. News, feedback and everything else, right here on BSD Now - the place to B.. SD. Headlines Faces of FreeBSD (http://freebsdfoundation.blogspot.com/2013/11/faces-of-freebsd-colin-percival.html) The FreeBSD foundation is publishing articles on different FreeBSD developers This one is about Colin Percival (cperciva@), the ex-security officer Tells the story of how he first found BSD, what he contributed back, how he eventually became the security officer Running series with more to come *** Lots of BSD presentation videos uploaded (http://www.freebsdnews.net/2013/11/14/eurobsdcon-2013-devsummit-video-recordings/) EuroBSDCon 2013 dev summit videos, AsiaBSDCon 2013 videos, MWL's presentation video Most of us never get to see the dev summit talks since they're only for developers AsiaBSDCon 2013 videos also up (https://www.youtube.com/user/bsdconferences) finally List of AsiaBSDCon presentation topics here (http://2013.asiabsdcon.org/papers/index.html) Our buddy Michael W Lucas gave an "OpenBSD for Linux users" talk (http://blather.michaelwlucas.com/archives/1879) at a Michigan Unix Users Group. He says "Among other things, I compare OpenBSD to Richard Stallman and physically assault an audience member. We also talk long long time, memory randomization, PF, BSD license versus GPL, Microsoft and other OpenBSD stuff" Really informative presentation, pretty long, answers some common questions at the end *** Call for Presentations: FOSDEM 2014 and NYCBSDCon 2014 (https://blog.netbsd.org/tnf/entry/call_for_presentations_bsd_devroom) FOSDEM 2014 will take place on 1–2 February, 2014, in Brussels, Belgium Just like in the last years, there will be both a BSD booth and a developer's room The topics of the devroom include all BSD operating systems. Every talk is welcome, from internal hacker discussion to real-world examples and presentations about new and shiny features. If you are in the area or want to go, check the show notes for details NYCBSDCon is also accepting papers (http://undeadly.org/cgi?action=article&sid=20131119053455). It'll be in New York City at the beginning of February 2014 If anyone wants to give a talk at one of these conferences, go ahead and send in your stuff! *** FreeBSD foundation's year-end fundraising campaign (https://lists.freebsd.org/pipermail/freebsd-announce/2013-November/001511.html) The FreeBSD foundation has been supporting the FreeBSD project and community for over 13 years As of today they have raised about half a million dollars, but still have a while to go Donations go towards new features, paying for the server infrastructure, conferences, supporting the community, hiring full-time staff members and promoting FreeBSD at events They are preparing the debut of a new online magazine, the FreeBSD Journal Typically big companies make their huge donations in December, like a couple of anonymous donors that gave around $250,000 each last year Make your donation today (http://www.freebsdfoundation.org/donate/) over at freebsdfoundation.org, every little bit helps Everyone involved with BSD Now made a donation last year and will do so again this year *** Interview - Amitai Schlair - schmonz@netbsd.org (mailto:schmonz@netbsd.org) / @schmonz (https://twitter.com/schmonz) The NetBSD Foundation, pkgsrc, future plans Tutorial Combining SSH and tmux (http://www.bsdnow.tv/tutorials/ssh-tmux) Note: there was a mistake in the video version of the tutorial, please consult the written version for the proper instructions. *** News Roundup PS4 released (http://www.theregister.co.uk/2013/11/16/sony_playstation_4_kernel) Sony's Playstation 4 is finally released As previously thought, its OS is heavily based on FreeBSD and uses the kernel among other things Link in the show notes contains the full list of BSD software they're using (http://www.scei.co.jp/ps4-license/) Always good to see BSD being so widespread *** BSD Mag November issue (http://bsdmag.org/magazine/1853-hast-on-freebsd-how-to-make-storage-highly-availble-by-using-hast) Free monthly BSD magazine publishes another issue This time their topics include: Configuring a Highly Available Service on FreeBSD, IT Inventory & Asset Management Automation, more FreeBSD Programming Primer, PfSense and Snort and a few others PDF linked in the show notes *** pbulk builds made easy (http://mail-index.netbsd.org/pkgsrc-users/2013/11/09/msg018881.html) NetBSD's pbulk tool (https://www.netbsd.org/docs/pkgsrc/bulk.html) is similar to poudriere (http://www.bsdnow.tv/tutorials/poudriere), but for pkgsrc While working on updating the documentation, a developer cleaned up quite a lot of code He wrote a script that automates pbulk deployment and setup The whole setup of a dedicated machine has been reduced to just three commands *** PCBSD weekly digest (http://blog.pcbsd.org/2013/11/pc-bsd-weekly-feature-digest-111513/) Over 200 PBIs have been populated in to the PC-BSD 10 Stable Appcafe Many PC-BSD programs received some necessary bug fixes and updates Some include network detection in the package and update managers, nvidia graphic detection, security updates for PCDM *** Feedback/Questions Peter writes in (http://slexy.org/view/s21oh3vP7t) Kjell-Aleksander writes in (http://slexy.org/view/s21zfqcWMP) Jordan writes in (http://slexy.org/view/s2ZmW77Odb) Christian writes in (http://slexy.org/view/s2BZq7xiyo) entransic writes in (http://slexy.org/view/s21xrk0M4k) ***

Wynn sat down with Brian Hogan and Josh Clayton to talk about tmux, dotfiles, and the joys of text mode.

Wynn sat down with Brian Hogan and Josh Clayton to talk about tmux, dotfiles, and the joys of text mode.