POPULARITY
Thinkpad von IBM/Lenovo: Das wohl bekannteste Business-Notebook der Welt?Wenn wir uns bei den verwendeten Laptops von Tech-Worker*Innen so umschauen, fallen besonders zwei Firmen bzw. Modelle auf. Das eine sind MacBooks von Apple. Das andere Thinkpad von IBM bzw. Lenovo. Besonders unter Software Entwickler*innen und Linux-Usern sind Thinkpads sehr weit verbreitet. Wir haben uns die Frage gestellt, warum dies so ist. Warum sind ThinkPads schon so lange am Markt und so beliebt? Was ist daran besonders? Diese Frage(n) versuchen wir in dieser Podcast-Episode zu beantworten. Christian Stankowic ist Sammler von ThinkPads und betreibt ein digitales Museum und einen Podcast zu diesem Thema. Mit ihm klären wir, den Grund für die Beliebtheit von Thinkpads, wie die Geschichte zu der Notebook-Marke aussieht, wer Richard Sapper ist, was es mit der roten Farbe im Produkt-Design auf sich hat, welche Hardware-Kuriositäten es bei verschiedenen Modellen gibt, woher eigentlich der Name Think kommt und vieles mehr.Bonus: Nobody gets fired for buying IBM.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partners Das schnelle Feedback zur Episode:
In this episode of Tech Talks Daily, I'm joined by Ada Lopez, Senior Manager of Lenovo's Product Diversity Office, recorded live at Lenovo Tech World in Seattle. Ada is on a mission to make AI more inclusive, accessible, and free of bias, and her passion for driving change through technology is truly inspiring. We dive into the critical issue of AI bias and explore how algorithms, often unintentionally, reinforce gender, racial, and social biases. Ada breaks down real-world examples, from AI systems used in criminal justice to everyday applications like Google searches and loan approvals, illustrating how bias can creep into these systems. She also shares how Lenovo is actively working to mitigate AI bias through its product diversity office, ensuring that inclusivity and accessibility are built into the design process from the start. Ada also sheds light on how Lenovo's AI initiatives are making a tangible difference, including their partnership with the Scott Morgan Foundation to help ALS patients preserve their voices, and the creation of tactile markings on ThinkPads to support users with visual impairments. We also discuss the excitement within Lenovo's development teams about building ethical AI systems and fostering empathy in product design. This conversation is a must-listen for anyone interested in the future of AI, the challenges of ensuring fairness and accessibility in technology, and how major tech companies like Lenovo are leading the charge for responsible innovation. Join us as we explore the impact of AI on our lives today—and what's next for the technology of tomorrow.
Here are the topics covered in this episode, and the time in the file for each. Welcome to 289 0:00 Send a text or voice message to us on WhatsApp 1:06 Outstanding technical support from Pulseway 6:43 Accessibility of X for iOS badly broken 11:36 Beatles book 13:59 The LenovoThinkBios Utility 19:44 Dr Nicholas Giudice discusses how we ensure blind people can use autonomous vehicles, and robot guide dogs 31:45 Sign up to participate in research on these fascinating topics. How to use the Capslock key in JAWS desktop layout 1:32:06 My recent app advocacy experience 1:33:47 TV apps for DeafBlind people 1:39:05 Orbit Writer 1:40:46 Beware of y2Mate 1:44:13 The Bonnie Bulletin ahead of convention time 1:45:13 Closing and contact info 1:58:13 With listeners in 113 countries, our Living Blindfully community offers a wide range of knowledge and perspectives. We welcome your contribution to the show. Here's how to have your say. Send us a text or audio message via WhatsApp. +447874464152 Write an email or attach an audio file recorded in your app of choice. The email address is opinion at LivingBlindfully.com Phone the listener line and record a voice message. This is a US number, so long distance or international charges may apply. +18646066736.
The newest version of Windows 11 is entering a new rollout phase. Some new exciting hardware from Lenovo emerged from this year's Mobile World Congress. And Paul has been using Copilot Pro for some time and is quite happy with it so far! Windows Windows 11 version 23H2 enters a new rollout phase - the "you're getting it whether you want it or not" phase. Canary: Wi-Fi 7 support, 16 new actions for Windows (+13 there already), separates from Dev channel again. Photos app to get generative erase functionality. Hardware Snapdragon X Elite destroys Intel Core Ultra in AI performance tests. Is this finally the year of Windows on Arm? Intel rolls out vPro versions of Core Ultra for businesses. Lenovo imagines transparent displays, ships actual ThinkPads. HP brings NPUs to its consumer PCs. Samsung Galaxy Book4 series is now available in the U.S. with unique Copilot features. Microsoft lays out its 2024 event calendar, and Ignite is in Chicago in November! AI Microsoft (quietly) adds four GPTs to Microsoft Copilot. Microsoft partners with Mistral AI, and gets immediate regulatory notice GitHub Copilot Enterprise is now available with organizational GPTs Google pauses Gemini image creation after, um, some issues Help Me Write is now in Google Chrome Brave Leo now supports PDFs and Google Drive Xbox Xbox will attend GDR, and will discuss DirectSR Microsoft starts testing Game Hubs in Xbox app for PC Lots of Age of Empire releases this year GeForce Now Free is adding pre-roll advertising Tips and picks Tip of the week: Turn off Microsoft Start in Widgets. Widget is finally closer to what most people will want. App pick of the week: Microsoft Copilot Pro Podcast pick of the week: Copilot Governance with Martina Grom Brown liquor pick of the week: Ian Macleod's Isle of Skye Range Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to this show at https://twit.tv/shows/windows-weekly Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Sponsor: GO.ACILEARNING.COM/TWIT
The newest version of Windows 11 is entering a new rollout phase. Some new exciting hardware from Lenovo emerged from this year's Mobile World Congress. And Paul has been using Copilot Pro for some time and is quite happy with it so far! Windows Windows 11 version 23H2 enters a new rollout phase - the "you're getting it whether you want it or not" phase. Canary: Wi-Fi 7 support, 16 new actions for Windows (+13 there already), separates from Dev channel again. Photos app to get generative erase functionality. Hardware Snapdragon X Elite destroys Intel Core Ultra in AI performance tests. Is this finally the year of Windows on Arm? Intel rolls out vPro versions of Core Ultra for businesses. Lenovo imagines transparent displays, ships actual ThinkPads. HP brings NPUs to its consumer PCs. Samsung Galaxy Book4 series is now available in the U.S. with unique Copilot features. Microsoft lays out its 2024 event calendar, and Ignite is in Chicago in November! AI Microsoft (quietly) adds four GPTs to Microsoft Copilot. Microsoft partners with Mistral AI, and gets immediate regulatory notice GitHub Copilot Enterprise is now available with organizational GPTs Google pauses Gemini image creation after, um, some issues Help Me Write is now in Google Chrome Brave Leo now supports PDFs and Google Drive Xbox Xbox will attend GDR, and will discuss DirectSR Microsoft starts testing Game Hubs in Xbox app for PC Lots of Age of Empire releases this year GeForce Now Free is adding pre-roll advertising Tips and picks Tip of the week: Turn off Microsoft Start in Widgets. Widget is finally closer to what most people will want. App pick of the week: Microsoft Copilot Pro Podcast pick of the week: Copilot Governance with Martina Grom Brown liquor pick of the week: Ian Macleod's Isle of Skye Range Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to this show at https://twit.tv/shows/windows-weekly Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Sponsor: GO.ACILEARNING.COM/TWIT
The newest version of Windows 11 is entering a new rollout phase. Some new exciting hardware from Lenovo emerged from this year's Mobile World Congress. And Paul has been using Copilot Pro for some time and is quite happy with it so far! Windows Windows 11 version 23H2 enters a new rollout phase - the "you're getting it whether you want it or not" phase. Canary: Wi-Fi 7 support, 16 new actions for Windows (+13 there already), separates from Dev channel again. Photos app to get generative erase functionality. Hardware Snapdragon X Elite destroys Intel Core Ultra in AI performance tests. Is this finally the year of Windows on Arm? Intel rolls out vPro versions of Core Ultra for businesses. Lenovo imagines transparent displays, ships actual ThinkPads. HP brings NPUs to its consumer PCs. Samsung Galaxy Book4 series is now available in the U.S. with unique Copilot features. Microsoft lays out its 2024 event calendar, and Ignite is in Chicago in November! AI Microsoft (quietly) adds four GPTs to Microsoft Copilot. Microsoft partners with Mistral AI, and gets immediate regulatory notice GitHub Copilot Enterprise is now available with organizational GPTs Google pauses Gemini image creation after, um, some issues Help Me Write is now in Google Chrome Brave Leo now supports PDFs and Google Drive Xbox Xbox will attend GDR, and will discuss DirectSR Microsoft starts testing Game Hubs in Xbox app for PC Lots of Age of Empire releases this year GeForce Now Free is adding pre-roll advertising Tips and picks Tip of the week: Turn off Microsoft Start in Widgets. Widget is finally closer to what most people will want. App pick of the week: Microsoft Copilot Pro Podcast pick of the week: Copilot Governance with Martina Grom Brown liquor pick of the week: Ian Macleod's Isle of Skye Range Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to this show at https://twit.tv/shows/windows-weekly Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Sponsor: GO.ACILEARNING.COM/TWIT
The newest version of Windows 11 is entering a new rollout phase. Some new exciting hardware from Lenovo emerged from this year's Mobile World Congress. And Paul has been using Copilot Pro for some time and is quite happy with it so far! Windows Windows 11 version 23H2 enters a new rollout phase - the "you're getting it whether you want it or not" phase. Canary: Wi-Fi 7 support, 16 new actions for Windows (+13 there already), separates from Dev channel again. Photos app to get generative erase functionality. Hardware Snapdragon X Elite destroys Intel Core Ultra in AI performance tests. Is this finally the year of Windows on Arm? Intel rolls out vPro versions of Core Ultra for businesses. Lenovo imagines transparent displays, ships actual ThinkPads. HP brings NPUs to its consumer PCs. Samsung Galaxy Book4 series is now available in the U.S. with unique Copilot features. Microsoft lays out its 2024 event calendar, and Ignite is in Chicago in November! AI Microsoft (quietly) adds four GPTs to Microsoft Copilot. Microsoft partners with Mistral AI, and gets immediate regulatory notice GitHub Copilot Enterprise is now available with organizational GPTs Google pauses Gemini image creation after, um, some issues Help Me Write is now in Google Chrome Brave Leo now supports PDFs and Google Drive Xbox Xbox will attend GDR, and will discuss DirectSR Microsoft starts testing Game Hubs in Xbox app for PC Lots of Age of Empire releases this year GeForce Now Free is adding pre-roll advertising Tips and picks Tip of the week: Turn off Microsoft Start in Widgets. Widget is finally closer to what most people will want. App pick of the week: Microsoft Copilot Pro Podcast pick of the week: Copilot Governance with Martina Grom Brown liquor pick of the week: Ian Macleod's Isle of Skye Range Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to this show at https://twit.tv/shows/windows-weekly Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Sponsor: GO.ACILEARNING.COM/TWIT
The newest version of Windows 11 is entering a new rollout phase. Some new exciting hardware from Lenovo emerged from this year's Mobile World Congress. And Paul has been using Copilot Pro for some time and is quite happy with it so far! Windows Windows 11 version 23H2 enters a new rollout phase - the "you're getting it whether you want it or not" phase. Canary: Wi-Fi 7 support, 16 new actions for Windows (+13 there already), separates from Dev channel again. Photos app to get generative erase functionality. Hardware Snapdragon X Elite destroys Intel Core Ultra in AI performance tests. Is this finally the year of Windows on Arm? Intel rolls out vPro versions of Core Ultra for businesses. Lenovo imagines transparent displays, ships actual ThinkPads. HP brings NPUs to its consumer PCs. Samsung Galaxy Book4 series is now available in the U.S. with unique Copilot features. Microsoft lays out its 2024 event calendar, and Ignite is in Chicago in November! AI Microsoft (quietly) adds four GPTs to Microsoft Copilot. Microsoft partners with Mistral AI, and gets immediate regulatory notice GitHub Copilot Enterprise is now available with organizational GPTs Google pauses Gemini image creation after, um, some issues Help Me Write is now in Google Chrome Brave Leo now supports PDFs and Google Drive Xbox Xbox will attend GDR, and will discuss DirectSR Microsoft starts testing Game Hubs in Xbox app for PC Lots of Age of Empire releases this year GeForce Now Free is adding pre-roll advertising Tips and picks Tip of the week: Turn off Microsoft Start in Widgets. Widget is finally closer to what most people will want. App pick of the week: Microsoft Copilot Pro Podcast pick of the week: Copilot Governance with Martina Grom Brown liquor pick of the week: Ian Macleod's Isle of Skye Range Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to this show at https://twit.tv/shows/windows-weekly Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Sponsor: GO.ACILEARNING.COM/TWIT
The newest version of Windows 11 is entering a new rollout phase. Some new exciting hardware from Lenovo emerged from this year's Mobile World Congress. And Paul has been using Copilot Pro for some time and is quite happy with it so far! Windows Windows 11 version 23H2 enters a new rollout phase - the "you're getting it whether you want it or not" phase. Canary: Wi-Fi 7 support, 16 new actions for Windows (+13 there already), separates from Dev channel again. Photos app to get generative erase functionality. Hardware Snapdragon X Elite destroys Intel Core Ultra in AI performance tests. Is this finally the year of Windows on Arm? Intel rolls out vPro versions of Core Ultra for businesses. Lenovo imagines transparent displays, ships actual ThinkPads. HP brings NPUs to its consumer PCs. Samsung Galaxy Book4 series is now available in the U.S. with unique Copilot features. Microsoft lays out its 2024 event calendar, and Ignite is in Chicago in November! AI Microsoft (quietly) adds four GPTs to Microsoft Copilot. Microsoft partners with Mistral AI, and gets immediate regulatory notice GitHub Copilot Enterprise is now available with organizational GPTs Google pauses Gemini image creation after, um, some issues Help Me Write is now in Google Chrome Brave Leo now supports PDFs and Google Drive Xbox Xbox will attend GDR, and will discuss DirectSR Microsoft starts testing Game Hubs in Xbox app for PC Lots of Age of Empire releases this year GeForce Now Free is adding pre-roll advertising Tips and picks Tip of the week: Turn off Microsoft Start in Widgets. Widget is finally closer to what most people will want. App pick of the week: Microsoft Copilot Pro Podcast pick of the week: Copilot Governance with Martina Grom Brown liquor pick of the week: Ian Macleod's Isle of Skye Range Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to this show at https://twit.tv/shows/windows-weekly Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Sponsor: GO.ACILEARNING.COM/TWIT
Here are the topics covered in this episode, and the time in the file for each. Welcome back for 2024 0:00 Episode 263 1:54 Blind is fine 3:45 Jonathan Mosen speaks with Ryan Jones,VicePresident, Software Product Management at Vispero 13:20 Level Access buys Userway 1:15:15 A new key is coming to your Windows keyboard 1:21:30 The AI Microsoft DisabilityAnswer Desk 1:29:16 My favourite podcast app 1:34:50 Sonos ERA300 versus FIVE 1:36:49 Looking for a laptop that does audio production 1:40:22 Making the iPhone Action Button do double duty 1:42:39 The BonnieBulletin, Yoto, ThinkPads, tablets and terminology 1:45:59 Closing and contact info 1:59:12
Für die einen ist es einfach nur ein schwarzes Gerät - für die anderen aufgrund des guten Linux-Support eine beliebte Wahl: die Rede ist von ThinkPads. In der heutigen Folge behandeln wir einen Themenwunsch von Lucas und klären auf, woher der Trend kommt und wie es um den Linux-Support heutzutage steht.
Hackaday Editors Elliot Williams and Tom Nardi meet up virtually to talk about the week's top stories and hacks, such as the fine art of resistor trimming and lessons learned from doing overseas injection molding. They'll go over circuit bending, self-driving cars, and a solar camera that started as a pandemic project and turned into an obsession. You'll also hear about Linux on the Arduino, classic ICs etched into slate, and an incredible restoration of one of the most interesting Thinkpads ever made. Stay tuned until the end to hear about a custom USB-C power supply and the long-awaited Hackaday Supercon 2023 Vectorscope badge. Check out the links and as always, tell us what you think about this episode in the comments over at Hackaday!
Hello, my name is André Jaenisch. You can find myself online under Ryuno-Ki as well. This is my first episode on Hacker Public Radio! It is recorded on 8th May 2023 using Audacity. It is published under a Creative Commons Attribution Share-Alike 4.0 International License. Today I want to introduce myself. I'm a web developer for ten years now and recently turned into a freelancer. My area of expertise is with Frontend technologies, although I also know Node.js and Python. I taught myself these languages because my studies in mathematics did not cover them. During my studies I switched to GNU/Linux. I started with Ubuntu but discovered that I prefer Rolling Release distributions more. So I jumped to Sabayon Linux which was based on Gentoo back then but pre-compiled the binaries while staying compatible. Now they decided to turn into another direction so I was looking for another home. I tried Gecko Linux based on openSUSE for a while until they had bad news in the press. I'm currently running Kaisen Linux which is based on Debian Bookworm. Speaking of, I love to read. I have whole shelves filled with books here. There is so much to learn from books even in the age of the Internet. I enjoy that they have a finite amount of content you can walk through. I learned about Hacker Public Radio at FOSDEM 2023. When I mentioned that I have a RODE NT-USB microphone at home already I was encouraged to contribute to the show. Now I have been listening to the podcast since the beginning of the year and already heard some of the emergency shows. I noticed that the hackers on the show are mainly from the United States. I hope you welcome people from other parts of the world as well. I'm from Germany in Europe. A beautiful place to live and I bet as diverse as in the States when it comes to the landscape. We have more than Berlin and Bavaria here! I'm not quite sure what kind of content you would love to hear about. I have the requested topics page in front of me and could talk about different items. For example, my first smartphone ever was a Firefox OS (I still have it. As well as a tablet). I switched to Android with F-Droid when Mozilla was cancelling the project. I'm running on a Fairphone here, which is a small Dutch manufacturer that already managed to move the whole industry into a more sustainable direction. Because we produce lots of waste. So I could talk about that. Or I could talk about building things for the web. Usually I blog about that because I feel like text feels more natural to it. But then I saw that some episodes contained code snippets in the show notes. I could talk about mathematics. We don't have enough podcasts about math! My focus was on statistics and numerics so that might be interesting? What I would love to hear more about is music theory. You see I haven't learned to play an instrument in my life. Mainly because those are expensive. My personal taste goes more into heavy metal but I'm not sure whether you would call me a fan. What does make a metalhead anyway? But in order to improve my game development having some sort of music and sound effects is important. So I was really enjoying the episode 3792 on reading music sheets. I lend some books on the library to learn more. These subjects weren't covered in depth in my school days! Another subject I would like to learn more about is electronics. Especially repairing one's computers. Look, I'm using ThinkPads since years now. I have a X250 (from FOSDEM) in current use. But I also have a X200 and a T520 gathering dust here. Mainly because something „broke” with the hardware and I'm too afraid to crack them open. Then there's a HP Pavilion standing under my desk to wait for repair. And even one of the old machines from the DOS era with an original Lemmings installed! But I have no idea how to refurbish them into a bootable state. Do you have ideas? I'm sharing my homepage as well as my e-mail address in the show notes. I would really love to hear back from you. I feel like I already touched on different ideas today, but looking at the time the recording is rather short. Personally I can tune into episodes up to 30 minutes best, so I will try to respect this threshold myself.
Kia ora Mosen At Largers. A reminder that this podcast is indexed by chapter. If you listen with a podcast client that offers chapter support, you can easily skip between segments. We also make transcripts available, thanks to sponsorship by Pneuma Solutions, a global leader in accessible cloud technologies. Visit them on the web at . You can find the transcripts on our website at This is the last episode for 2022. Mosen at Large is now taking a summer break and will return on 29 January. You are welcome to keep the contributions coming in during the break, so that we have a packed first show. Here are the topics covered in this episode, and the time in the file for each. Welcome to the final show for 2022,0:00.000 Giving you the info on 211,1:26.780 Plenty of great holiday programming on MushroomFM,3:20.007 There is a fault affecting a good number of Lenovo ThinkPad X1 Carbon 9th gen machines,4:21.728. Here is the long thread I referred to on the podcast. Apple Watch Ultra unboxing and setup,33:35.838 Evidence 111 is a compelling audio game for iOS and Android,1:19:56.438 Deep Fried turkey,1:36:18.345 Audio description,1:38:01.225 Is there a Dvorak keyboard tutor app?,1:43:25.048 Crossing in a straight line,1:44:16.563 Microsoft Teams,1:46:24.683 Newspaper content in audio,1:48:36.789 Performing an iPhone clean install,1:49:41.079 CCLVI,1:53:54.237 IPA Braille,1:54:47.025. Here is the article referred to about IPA Braille. Wanting to be independent in health clubs and other places,1:55:21.933 Keep the contributions coming over the break,2:00:43.832 Share your thoughts on these topics or any others. Drop me an email in writing or with an audio attachment, Jonathan at MushroomFm.com, or phone the listener line in the United States, +1864-60Mosen, that's +18646066736. Keep up with Mosen At Large between episodes. Follow MosenAtLarge on Twitter where you'll get audio extras, links to interesting news stories, sneak peeks about what's coming up and more. If you'd like to subscribe to our announcements only email list, please send email to And if you like the show, we'd love a positive review and for you to spread the word. Thank you.
Buenas muchachada hoy le toco a todos los palos pendientes que tenia por contar (Popliteo, Thinkpads, JPOD) y más anécdotas del D.N.I.
Buenas muchachada hoy le toco a todos los palos pendientes que tenia por contar (Popliteo, Thinkpads, JPOD) y más anécdotas del D.N.I.
Weiter geht's mit Stimmen aus der Community. Diesmal zu Gast: Mr. ISO-DE himself - Christian Stankovic. Er erzählt uns über seine Liebe zu Vintage-Keyboards und ThinkPads aber auch wie er zu mechanischen Keyboards gekommen ist, welche Switches er mag und welche nicht und natürlich warum ISO-DE (für Ihn) besser ist als andere Layouts. Ein paar News und Neuigkeiten gibt es für euch auch.
Thinkpads that won't boot Linux by default, Lennart moves to Microsoft, the Firefox Snap is finally a lot faster, Reddit shows its true colours, KDE Korner, and more. News London Meetup 5th August near The Eye Lenovo Secured-core PC unable to boot Linux from a USB stick Responsible stewardship of the UEFI secure boot... Read More
Thinkpads that won't boot Linux by default, Lennart moves to Microsoft, the Firefox Snap is finally a lot faster, Reddit shows its true colours, KDE Korner, and more. News London Meetup 5th August near The Eye Lenovo Secured-core PC unable to boot Linux from a USB stick Responsible stewardship of the UEFI secure boot... Read More
kvalitetsdatorer.se https://www.kvalitetsdatorer.se/se/ The company where I bought my refurbished Thinkpad T530 inxi -Bxxx Command to get full information about all batteries in the system. Even on devices connected to the computer, as my Sansa Clip+ f.ex. Thinkpad X230 battery patch https://bystram.be/posts/thinkpad-x230-battery-ec-patch/ batteriexperten.se https://www.batteriexperten.com/sv/ tpacpi-bat A Perl script with ACPI calls for recent ThinkPads (such as T420 and W520) whose battery thresholds are not supported by tp_smapi
Peter hat ein PinePhone Pro, Marius hat ein JingPad A1 und sie reden über Cloud-Streaming auf Android, Chrome OS Flex, ThinkPads mit ARM CPU, Neuigkeiten zum Steam Deck, Apple Event Vorhersagen und vieles mehr!
Peter hat ein PinePhone Pro, Marius hat ein JingPad A1 und sie reden über Cloud-Streaming auf Android, Chrome OS Flex, ThinkPads mit ARM CPU, Neuigkeiten zum Steam Deck, Apple Event Vorhersagen und vieles mehr!
Peter hat ein PinePhone Pro, Marius hat ein JingPad A1 und sie reden über Cloud-Streaming auf Android, Chrome OS Flex, ThinkPads mit ARM CPU, Neuigkeiten zum Steam Deck, Apple Event Vorhersagen und vieles mehr!
2/12/12 - IBM's Thinkpad was the first laptop to have a keyboard light THINK: A brief history of ThinkPads, from IBM to Lenovo| IBM ThinkPad 701C: The Iconic Butterfly Keyboard| The ThinkLight: Shedding Light on the Legend (ft. David Hill)| What was the first backlit keyboard? 2/14/12 - How to burn a USB Lion disk and rotate multiple pages at once in Preview Make a Bootable Mac OS X 10.7 Lion Installer from a USB Flash Drive| How can you rotate all the pages of a PDF file in Preview? 2/15/12 - Clear command in terminal Clear(1) – Linux Manual Page 2/16/12 - I can middle click things in the Windows 7 Taskba Middle-Click on the Taskbar to Quickly Open and Close Application Windows 2/17/12 - You can move the chat bar in League of Legends 2/18/12 - The Dice app on Android can lock dice as well as have multiples/change dice color. 2/19/12 - Windows 7 can condense down to 2GB in size. Microsoft confirms MinWin is in Windows 7, after all | Mark Russinovich Explains MinWin Once and For All 2/20/12 - About Potosi, the city of Silver 2/21/12 - The "College Freshman" meme picture was taken in the upper quad courtyard. Know Your Meme: College Freshman | Why Every College Freshman Should Start a Roth IRA | My Picture is Internet Gold Right Now 2/22/12 - Henry Morgan = Captain Morgan, and he wasn't a pirate, he was a privateer. Also, purge in OSX Terminal clears out inactive used memory 2/23/12 - Ton of stuff on Martin Luther. Also figured out IRC. 2/24/12 - defaults write com.apple.iCal IncludeDebugMenu 1 will turn on debug mode for ical in 10.7 How to enable iCal's debug menu 2/25/12 - How the Frenzied Barbarian works in D&D Ultimate Barbarian (3.5e Class) Extra topics: Club Bing's shutdown Housing damages bills This episode's music comes from archive.org, the Free Music Archive, and Apple iMovie Tracks featured in this episode include: Kevin MacLeod - Dat groove [ Kevin MacLeod (incompetech.com) | Licensed under Creative Commons: By Attribution 3.0 | http://creativecommons.org/licenses/by/3.0/ Apple - Daydream Apple - Coming of Age Jason Shaw - Thingamajig Jason Shaw - Mountain Sun Jason Shaw - Solo Acoustic Guitar
Uppföljning/uppvärmming Sportsnack: Hockey, OS, mm. Mål 2022: avstämning efter januari Fredriks Apple arcade-rapport såhär långt Tio år med Thinkpads Apple introducerar kontaktlösa betalningar för butiker Fandrake släpper Kickstartern för boken om Drakar och Demoner den 10:e mars Ämnen Två år med Covid-19. Vad blir framtiden nu? Kommer ni att kindpussas på jobbet framöver? Jocke berättar om sitt Kubernetes cluster. IIS sjabblar med .SE-domänen och DNSSEC. Fredrik RSS-tjänst uppdaterar sig inte. NetNewsWire till undsättning. Fredrik skaffar adaptrar till sin Ipad, gör pull to refresh med mushjul. Film och TV Douglas Trumbull har lämnat oss After Life, säsong 3: 4/5BMÅ Snowpiercer säsong 3: Vi är skeptiska Länkar Anders Eldebrink - SSK-legenden som numera är sportchef för SSK Emblemet Inlägget Fredrik läste om Emblemet Frida Hansdotters logga Christians nyårsmål Jimmy joy Sayonara wild hearts Alto's odyssey Mini motorways Mini metro Beyond a steel sky Tio år med Thinkpads Apple introducerar kontaktlösa betalningar Apple cash Boken om Drakar och Demoner Nej – jag kan inte ta hänsyn till att du skaffat hund. Att jobba hemifrån är ingen rättighet! Kubernetes K3s Rancher IIS - Internetstiftelsen DNSSEC Jockes postning på Linkedin om IIS problem Myndigheten för samhällsberedskap Freshrss Tiny tiny rss Netnewswire Hoverbar Spidermonkey-stället Universal Control Douglas Trumbull har lämnat oss Douglas Trumbulls arkiverade webbsajt The man who killed Hitler and then the bigfoot Afterlife Billions Fullständig avsnittsinformation finns här: https://www.bjoremanmelin.se/podcast/avsnitt-295-konsultkramar.html
¡¡¡Muy buenas amante del Software Libre!!! Bienvenido a otra entrega de Podcast Linux, la número 130. Un saludo muy fuerte de quien te habla, Juan Febles. Hoy tenemmos en el programa a Bote, amante y propietario de muchos Thinkpads y miembro de Thinkpad_es, grupo de Telegram dedicado a compartir las experiencias con estos modelos de Lenovo. Recordar a los oyentes que estamos en una sala Jitsi para esta charla, un servicio libre para videoconferencias, y que este podcast aloja su web en Gitlab, un servicio libre de repositorios git y su contenido en Archive.
I've been wanting to bring RetroEdge.Tech onto the show for ages, he's a Linux enthusiast, runs a computer repair business, owns way too many Thinkpads and is all around cool dude who does a lot of videos only the line between retro and modern tech. ==========Guest Links========== Website: https://retroedge.tech/ Odysee: https://odysee.com/@retroedge.tech:4 Twitter: https://twitter.com/retroedgetech Mastodon: https://distrotoot.com/@retroedgetech ==========Support The Channel========== ► Patreon: https://www.patreon.com/brodierobertson ► Paypal: https://www.paypal.me/BrodieRobertsonVideo ► Amazon USA: https://amzn.to/3d5gykF ► Other Methods: https://cointr.ee/brodierobertson =========Video Platforms==========
Gnome celebrates 20 Million downloads from the LVFS! Lenovo launches a gang of Linux powered Thinkpads, a WSL alternative for users who prefer MS-DOS environments, and OBS 26 learns how to browser. Show notes & Timestamps
The first Thinkpads loaded with Fedora go live, but there is a lot more to the story. Plus, the new PinePhone options coming soon, our thoughts on recent Mozilla news, lessons from the GNOME Patent Troll, and AWS Bottlerocket.
The first Thinkpads loaded with Fedora go live, but there is a lot more to the story. Plus, the new PinePhone options coming soon, our thoughts on recent Mozilla news, lessons from the GNOME Patent Troll, and AWS Bottlerocket.
The first Thinkpads loaded with Fedora go live, but there is a lot more to the story. Plus, the new PinePhone options coming soon, our thoughts on recent Mozilla news, lessons from the GNOME Patent Troll, and AWS Bottlerocket.
ThinkPads med Linux, i3-gaps, och Alex gör en Nuke 'n Pave. Detta och massa mer gött i veckans avsnitt av Trevlig Mjukvara. Länkar: https://trevligmjukvara.se/s04e06
The first Thinkpads loaded with Fedora go live, but there is a lot more to the story.
The first Thinkpads loaded with Fedora go live, but there is a lot more to the story.
Bill is still on Manjaro! The Ubuntu MATE Guide is now available online. We answer questions about MeWe, dual booting, fresh install, replacing a sheet feed scanner, System76, Crossover, and LibreOffice spell check. Episode 395 Time Stamps 00:00 Going Linux #395 · Listener Feedback 01:09 Ubuntu MATE Guide available online 03:34 Bill pauses his distrohopping, explores Vivaldi browser on Manjaro 06:49 Daniel: Help with MeWe and screen reader 08:55 George: Thank you 09:38 George: Dual booting for Mike 16:06 Nathan: Fresh Install 21:24 David: Replacing a sheet feed scanner 25:46 Reid: System76 and Thinkpads 31:25 David: Manjaro and Crossover 33:51 Tim: LibreOffice spellcheck not working on Manjaro on Pinebook Pro 35:56 Next episode 37:07 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 38:16 End
Bill is still on Manjaro! The Ubuntu MATE Guide is now available online. We answer questions about MeWe, dual booting, fresh install, replacing a sheet feed scanner, System76, Crossover, and LibreOffice spell check. Episode 395 Time Stamps 00:00 Going Linux #395 · Listener Feedback 01:09 Ubuntu MATE Guide available online 03:34 Bill pauses his distrohopping, explores Vivaldi browser on Manjaro 06:49 Daniel: Help with MeWe and screen reader 08:55 George: Thank you 09:38 George: Dual booting for Mike 16:06 Nathan: Fresh Install 21:24 David: Replacing a sheet feed scanner 25:46 Reid: System76 and Thinkpads 31:25 David: Manjaro and Crossover 33:51 Tim: LibreOffice spellcheck not working on Manjaro on Pinebook Pro 35:56 Next episode 37:07 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 38:16 End
Computers that we wish we didn't own, a terrible funding model for Linux, shunning the work of bad people, and a shocking revelation from popey about ThinkPads. You can support creation of The New Show episodes via Patreon or Paypal, and you can send us your questions on Twitter. This episode is sponsored by Lernard. … Continue reading "The New Show 07: Pinebook Bros"
This episode of the Business Karaoke Podcast is a first - it is our first episode in Japanese!The Business Karaoke exists to modernize the conversations around doing business in and with Japan. In order to be authentic to that promise we need to explore today's pressing topics of innovation, people and technology from both sides and in both languages. To premier our Japanese dialogue, we were joined by Junji Matsuguma. Junji is cross-products systems architect at IBM, utilizing customer workshops about IT infrastructure optimization, hybrid cloud, IT economics study and Design Thinking for customer's digital transformation. I had the pleasure of getting to know Junji through our mutual interest of evangelizing Design Thinking among Japanese clients. Below is the list of our conversation so you can quickly navigate and find what is most relevant for you.00:53 An introduction to Junji | 自己紹介02:55 Working at home during COVID-19 | 新型コロナウイルスの時期で在宅で仕事をすること。08:30 Tips for video conferencing | ビデオカンファレンスのチッピス。13:56 Changes in the IT industry | ITインダストリーの変化。18:00 Role of Design Thinking | デザインシンキングの役割。20:15 How are traditional Japanese companies responding to Design Thinking? | 日本の伝統的な会社はデザインシンキングを受けれるでしょうか?23:41 Junji's personal 'wow' points of Design Thinking | 個人的にデザインシンキングのいいポイント。27:55 Benefits of Design Thinking with customers | お客さんとデザインシンキングの利益。38:00 The world after COVID-19 | 新型コロナウイルス後の世界。46:50 Hopes for the future| 将来の希望。As usual, a big thank you to YOU for listening and an even bigger thank you to Junji for his time.-- Read more on Junji Matsuguma before or connect with him on LinkedIn. Junji joined IBM in 1988 and worked as a hardware engineer for product development from gate array modules to IBM PCs and ThinkPads. Junji changed his role to pre-sales technical specialist for engineering workstation and blade servers. He now works as cross-products systems architect utilizing customer workshops about IT infrastructure optimization, hybrid cloud, IT economics study and Design Thinking for customer's digital transformation.His hobby is handcraft. He is learning “relieur”, or book binding in traditional European way from 2005 and now in advanced course.Support the show (https://www.buymeacoffee.com/1QnboZC)
Liam and Noah talk all things laptops, from Chromebooks to Gaming laptops, it's all here. Liam also introduces Lenovo's newest line of ThinkPads.
Neste episódio falámos do encontro mensal da Comunidade e dos planos para o encontro de Junho, das nossas aventuras semanais, migração de infraestrutura com LXD, financiamento de Software Livre, doações da Slimbook para a comunidade, do crowdfunding do Ubuntu Podcast, adopção responsável de Thinkpads e dos super-descontos nas Libretrend Librebox.
There are more than eight million dynamic pages that run on Lenovo.com, where the majority of shoppers go to buy their products. It is a massive Ecommerce platform that has to work for more than one billion website visitors per year. Ajit Sivadasan is the Vice President and General Manager of Lenovo, and even though managing those pages is part of his job, what he’s more interested in is making sure that those pages are offering relevant content and an efficient experience to a new generation driving Ecommerce growth. On this episode of Up Next in Commerce, Ajit explains why figuring out what content is relevant to Gen Z will be the driving factor in how successful your Ecommerce platform will be. 3 Takeaways: There is a massive demographic shift happening in the consumer market, so rather than focusing on producing more and more content, companies need to focus on producing content that is relevant to this new audience of digitally-native consumers Customer irritants are data points that matter and constantly change. Constantly addressing those irritants – from delivery time to language on the credit card processing screen – has an impact on consumer satisfaction and your NPS Behavioral economics states that humans are predictable and predictably irrational. Therefore, you have to take this behavior into account in everything from website design to offering comparisons of products as a counterbalance for the fact that humans will deviate to the path of least resistance more often than not For an in-depth look at this episode, check out the full transcript below. Quotes have been edited for clarity and length. --- Up Next in Commerce is brought to you by Salesforce Commerce Cloud. Respond quickly to changing customer needs with flexible Ecommerce connected to marketing, sales, and service. Deliver intelligent commerce experiences your customers can trust, across every channel. Together, we’re ready for what’s next in commerce. Learn more at salesforce.com/commerce --- Stephanie: Hey everyone. This is Stephanie Postles, your host of Up Next In Commerce. Ajit, how's it going? Ajit: Good. Thank you for getting me on the show, Stephanie. Stephanie: Yeah, I'm excited to have you on. So I'd love to hear a little bit about your background at Lenovo. You've been there 15 years, right? Ajit: Close to, yeah. This is my 15th year. Stephanie: So I'm sure a lot has changed since you joined the company back then. Ajit: Yeah. I joined Lenovo in 2006, and came to Lenovo to build a consumer brand online. And obviously, when I joined, we didn't have much of a infrastructure or even sales. We were in a very limited set of countries. We were actually in four countries and we probably had a very small amount of revenue. Since then, obviously, we have scaled the business about 10X on revenues, and profits have grown about 10X. And we have scaled from four countries to 35 countries. And in the process, we have seen several acquisitions. We acquired the Motorola brand. We acquired the System X brand. So we have had to integrate all of those businesses. So Lenovo has gone from a company that's sold PCs, to being a company that basically is trying to drive intelligent transformation for its enterprise customers, and for its consumers around the world. Obviously, we have a footprint in more than 165 countries. So it's exciting. Ajit: When I joined the company, we were number six in the world. Obviously, we've been number one for a number of years now, and have a significant market share in the PC space, and we continue to make progress in the data center space, which we acquired from IBM. And the Motorola phones, you might have seen some of the latest phones that we introduced. We were the first ones with the foldable phone, that was a take on the Razr phone, the iconic Razr phone. So, yeah, it's been very exciting. We have obviously enjoyed our ride. I'm very excited because we get to interact with a number of customers on Lenovo.com and really bring the technology to life, and the brand to life, using the platform we have. So yeah, it's been a good ride. Stephanie: That's awesome. And what does your day-to-day look like at Lenovo? Ajit: I manage the platform for Lenovo, which is basically Lenovo.com. And since it serves all of our stakeholders, we have the Lenovo.com footprint in more than 90 countries. So I have to manage both the sales side, which is primarily a combination of B2C and SMB. And then I have to manage the enterprise side of the customer. So mostly B2B customers that buy from us using a procurement type of strategy, where we actually service them one-on-one. So I have the sales part, which is basically running the whole end-to-end business, all the way from marketing, CRM, UX/UI design, sales and marketing, phone sales, to really even trying to help with the supply chain piece, working closely with our supply chain organization. Ajit: But then the other side is really trying to figure out how to position Lenovo.com to become a brand voice, and figure out how we bring to life all of the innovation, and the products, and the enterprise strategy we have, for the stakeholders that come to Lenovo.com around the world. We get over a billion people coming to the website any given year. So it is a pretty substantial property. And so we have a ton of work that we need to do to manage all of those aspects that take care of basically all of the customer needs we have. Stephanie: Wow. What are some of the key learnings when it comes to moving globally? So it started out, I think in 1985, and it was just a reseller in China, right? And then, now it's a global company. What has that transition been like, and what have you learned in the process as you open up new countries and start selling there? Ajit: When I joined, obviously, my journey beyond Lenovo, was at Gateway. I was at Gateway for five years. So I've been in the PC space for about 20 years. And what you have to really understand is, all the transitions that have happened in the business model. When I started, internet was relatively new, and people used it as a very siloed organization that was doing just the phone and the web. So it was very limited. But today, as you know, 70% of the traffic that comes to the website is mobile traffic. The patterns have shifted quite a bit. So the business model transformation that has happened over the last 15 years has been interesting. Ajit: And what you see is, initially when we started, a lot of our colleagues around the world were maybe a little apprehensive. They were worried about things like conflict. They were worried about issues like pricing and things like that. And what you notice as things have evolved is, what you find is that, that is a very complimentary system. A number of our customers that are very sophisticated, technology-focused, innovation-focused, want to buy online. They want to be able to customize their products, they want a full breadth of products. And then there is a bunch of customers who would like to go to retail stores, look at our products, touch, understand it a little bit better before they actually make a purchase. So what we have found out is, thought we had a lot of skepticism, maybe even like six, seven years ago, that has changed into, people now trying to figure out how to leverage the business models, including connecting retail and the offline presence we have. How do we get our enterprise customers the best experience possible? How do we make sure the supply chain is responsive? How do we get them more capabilities that love them to buy products on credit, allow them to buy using a subscription type of service, give customized services that add them for SMB customers. Ajit: So, if you really think about it, the evolution has been quite interesting. And look, day-to-day, there's tons of things that you need to do because it's a fast-pace, technology-driven, very innovation-focused space. And people like Amazon and others, they're really driving the paradigm as far as online commerce is concerned. So it's not sufficient for us to just look at our traditional competitors. We also have to understand that the customers are getting sophisticated, and their expectations are much, much higher than what they used to be. So in many ways, the decision to go into a country now, is much more driven by the customers, than it is even proven by our direct stakeholders. And when I say stakeholders, internal folks, because customers really demand that you actually have an online presence. And they really want to transact with you online. So the transition has been interesting, but I think it's accelerating and the business models getting very complex. And our ability to actually react to them fast is going to be critical, as we move to the future. Stephanie: Yeah. I completely agree. So I heard that you have eight million dynamic and other pages, on lenovo.com. Maybe it's more at this point, compared to when I heard that stat'. How do you keep up with all the pages that you have, behind the scenes, being custom, depending on who's coming, depending on what country they're coming from? How do you make sure that it doesn't turn into a black box? like an algorithm when it starts getting too much stuff in it, you're like, "I don't even know what's happening behind the scenes anymore." How do you keep up with the pace? Ajit: A lot of this is automated. If you really think of our bulk of the products... I'll give you an example. So we sell thousands and thousands of third party products, accessories. Whether it is hard drives, whether it is even headphones and monitors and lots of things that are serviced and provided by other companies. And those are all managed automatically. So it's in a database. It's a data-driven process. So you don't have to worry about it. But if you multiply those into the number of countries, suddenly the numbers look staggeringly big. Now, having said that, it still is a pretty big number of pages. And clearly, there is a process for us to manage level one, level two, level three type of page, home page, right? If we look at the efficacy that is periodic checks on usage of the pages, there's teams basically managing content across the site, across the countries. Obviously, there is a strategy for how many layers of product pages we want to have. We look at data to understand who is using it, how often are they using it, and things that are not being used. Obviously they get [inaudible] as time goes by. Ajit: But more and more, it is clear to us that we need a very cohesive data strategy for formality content. So the formats customers prefer for content is changing. A lot more focused on videos, a lot more focused on how to do things, through a short-form video. Even content that you provide in terms of words are very succinct, and to the point. So you let customers pull the data, pull the content, as opposed to publishing everything and letting the customer go through stuff. Clearly it takes a lot of time and effort. And the key is to make sure that your systems, from the product management, all the way to what the customer actually sees on the glass, all managed in a way that makes sense. And that clearly is a challenge, because you've got a lot of legacy systems. And what somebody puts in as they're designing a product, may be marketed different from the marketing content that somebody needs to see in order to make a decision on a sale. Ajit: So you really have to figure out the process, streamline it. You need to make sure, periodically, you look for paradigm shifts. You need to understand demographics. 70% of the population that's going to be in the workforce is going to be millennials. And I can tell you that they are not really interested in reading a lot of stuff. They prefer much short-form formats, and they like videos and things like that. So if you're not connecting with them, and your engagement is not right, I think you're going to have a problem in the long run. So, I think the page count is less of a problem, than relevance. And I think that what we really are trying to do is to figure out how to be relevant, and drive content that truly drives engagement with our audiences. Stephanie: That completely makes sense. Are there certain trends that you see coming that Lenovo is preparing for, when it comes to, like you said, videos, preparing for millennials? What things are on your radar right now that you're preparing for the future? Ajit: So I'd say a couple of things on that. We are definitely seeing a pretty significant shift in demographics. Though we see a bimodal distribution. And by that, we see a lot more older people, and we see a lot more younger people. And the number of people in between actually is very low. So you would see very young people. 60%-70% of the population will be in the 20-30 age group, going forward. Which means that, these are native millennials. These are generation Z, Gen Zs, who basically are native digitally. And therefore, their expectations and how they consume data, and how they consume information is very, very different. So we have to really worry. I think everybody needs to worry, if you're online, as to how they are going to be part of your community, how you're going to get engaged with them, how are you going to keep their interest in the products that you have? Ajit: Part of the challenge is that they are so sophisticated, and are pretty much, in my mind, no nonsense, in terms of technology, that it's highly unlikely that they are going to support anything that is cumbersome, or verbose, or anything that basically takes away from efficiency, in terms of how they deal with online content. And so, I think the big challenge is for companies to truly make that shift of saying, "Look, this was the audience in the past. They had a very different predisposition to how they looked at data, and how they analyzed things. And then there's this new generation that truly is looking at content differently." Ajit: Now, the key points will be when they start truly having money in their pockets, and they're going to be in positions where they're going to be making decisions for companies, in terms of purchasing, technology decisions. And many of them already are making those decisions. And then if you are not able to engage with them appropriately, I think that you have a challenge. So truly trying to figure out how to build that relationship with the gen Z, millennial audience, I think is key. We are definitely looking at a couple of segments where we believe that that's an area that we need to really get good at, which is, gamers who are basically a big part of the online ecosystem. They are very sophisticated. They know exactly what they want. They are very community-driven. They're very content-driven. Ajit: And so, the proxy for us, at least in my mind is, "Look, you now have to figure it out how to engage these people online." Because you will learn from that set of experiences, that if you are, as a brand, not able to work that in your favor, it becomes increasingly challenging, I think, for the brand to have relevance in the future. And so, we are really focused on gamers. We believe that we have to cater to them end-to-end. From content, from products, online experiences, capabilities, giving them access to a broader set of products and portfolio, game titles, being able to give them subscription services and other things. Ajit: And the second audience that's really, really important are students. So a big part of students are going to be online, and quite frankly, this Covid crisis brings out the issue much more readily, where you see high schoolers, pretty much all schoolers, including colleges, basically offering courses online. And everybody's online study. I can tell you that it looked like a big deal when it happened, but we have been thinking about this thing for several years now. And this crisis obviously has accelerated that thinking even more. But the reality is that this is going to be the new norm. And, what is interesting is that a lot of people that aren't online students, because of the fact that for 1,000 years we have always told students that they need to go to a school, and be an apprentice, and study and learn because they can find a job. Ajit: And now, companies have come out and said, "Look, you don't really need a college degree to get a job. All you need is knowledge. And if you're good at something, then we'll figure out a way to test you, and you'll be fine. You don't need a formal degree." And we think that that trend will accelerate in the coming years. And I think that universities and colleges and institutions will figure out how to deal with it. And then at the same time, people like us, brands, we'll have to figure out how to engage this audience. Because, they're looking for information, they're looking for technology, they're looking for solutions. And the question is, "Can we provide them solutions and technologies that make learning online easier for students?" So that is the audience. Obviously, we make PCs, and we make phones, and we made monitors and all these things that really are part of the technology solution that enables people to learn online. And therefore, we believe that we should figure out how to engage with this audience who are basically online, and in a direct way, so that we understand their needs much more concretely. So those are two segments that are key. Stephanie, you had a question? Stephanie: Yeah, that makes sense. When it comes to thinking about this new generation, and they're, like you said, no nonsense. They want things quick. The website better be super quick. They better be able to buy fast. They have, I'd say, a higher risk tolerance when it comes to ordering online, as long as there's a good return policy. They're probably okay with just buying right away and hoping for the best. How are you thinking about your retail strategy? Because like you said, a lot of people in the past have been used to going into stores, and trying things out. Do you see that being something in the future? Especially with Covid, it seems like a good forcing function, where it's pushing more people online, and to just try it instead of having to experience it in person. Are you all shifting your thoughts around that area? Ajit: Well, I think Covid clearly will be an outlier. It will accelerate the digital transformation. But I still think that retail will have a pretty important place and role to play in the long run, but it will get redefined. And for our part, we are doing a couple of things. We are trying to figure out how to help our resellers, how to help our retail partners, and quite frankly trying to connect offline and online in a meaningful way. So where we own stores like in China and India and other places, we are trying to figure out how to connect the online experience with the offline experience, so that people can buy products online. They can go to the shop and order it online there. So really trying to figure out how to manage the customer experience a little bit more readily. Ajit: Now, having said that, I think the interesting transformation that's happening is really trying to connect the social, the retail, and online together. And if we can, at some point, get the mobile piece to work, then it becomes a very, very interesting value proposition for the customer because you truly have the customer for the whole cycle. So if they are outside, we know where they are, and therefore we can give them recommendations if they're interested in looking at our product. If they're online, obviously they can do things online. But if they do stuff on their phone, we can actually translate some of those things meaningfully to their desktop, and therefore we make it very, very easy, experientially for them to experience a good a brand experience. So we don't have to act surprised when the same person is in two different places, or as two different ways they connect to the brand. We just need to figure out how we connect those pieces. Ajit: And I think that these are the types of business model shifts that we will see accelerated as we go through this crisis and beyond. I think that people are finally trying to figure it out, "How are we going to connect this?" Look, Amazon has already done some of this with what they have done with Whole Foods and the Prime. So they've figured out how to connect the store to Prime users, and the online stuff. So the blueprint is there, and I think that most companies are doing some stuff. But I think that you're right. It's going to get accelerated as this crisis progresses. Stephanie: Yeah. I think connecting those platforms is key to making sure you understand the customers and can deliver value to them wherever they're at. Are there any technologies that you guys are experimenting with, to try and connect that online, to offline, to social, and mobile? Ajit: Yeah. It depends from place to place, and it depends on the companies footprint, right? In China, obviously, I think we are the most progressed in terms of the technology piece. We have a substantial online, merged with offline footprint, which connects WeChat, and online cloud, and our application layers, which allows our customers to actually be connected fully with the brand. And it actually connects all the retailers also to the brand in a very, very meaningful way. So that is, I think, the aspirational model for everybody. We have a very different model in Japan, as an example, where we are connected in kiosks, in the retail store, that's connected to the online world. In Taiwan as an example, we have an offline store that we are connected to. In India, it's the same thing. It's an offline-online model. Ajit: So yeah, the business model is different from different country to country. But it also depends on who is innovating more, and what's the landscape look like in the country? So it's not one size fits all. And I would be remiss if I didn't mention that privacy, as an example, is a key consideration in some countries, and some countries they're more relaxed. So it just depends, also, on some of the privacy laws that enable customers to share information more freely versus some others where you can't. Ajit: But my sense is that depending on the country, and depending on the business, you will see hybrid models emerge. They already are emerging. And some will have much more traction than others. But I would see a lot of partnerships being formed between online companies and offline retailers, to really manage the customer experience to be much smoother, and much more productive, going forward. Stephanie: Got it. And I saw that Lenovo is leaning more into focusing on the consumer and their needs, and becoming a more consumer-first company. Is there certain data points that you all are using to meet your consumer better than you were before? Or were in that end-to-end consumer journey do you see the most room for growth or improvement? Ajit: Yeah. Lenovo's history and its heritage has always been a product company. We have some of the best brands in the world, whether it's Thinkpad, Yoga, Moto, System x, these are all brands that are at the top of their game when it comes to their specific categories. Stephanie: I used a ThinkPad at Google. I love my ThinkPad. Ajit: There you go. And nine out of 10 people that I speak to in the business will tell me the same thing. I used to use a ThinkPad before I worked for Lenovo long, long time ago, as well as a consultant for Deloitte. And there's plenty of people who actually use ThinkPad because it's an iconic brand. So we always have been a company of engineers, historically. But as we move into the internet era, and as digital becomes more mainstay, it is absolutely critical for us to really understand what our end users look like, what they are doing with our products, how do we collect feedback that's more direct? And truly, really understand and have a pulse on what the customer sentiment is for our brands. Ajit: It becomes extremely difficult for us to get feedback more directly, as from an indirect channel, because of the fact that we don't really talk to the customer directly. We have to remain and collect information in an indirect fashion. And depending on the privacy laws and other things, it becomes very, very complicated for us to collect information. Having said that, three or four years ago, as a company, we decided that it was such an existential reason for us to really start thinking customers first, and truly trying to figure out how to connect with them, and drive digital transformation, that we decided to start measuring all of our customer segments, whether it's direct or indirect, in either use proxies or direct measures. But mostly, the entire company has been on a Net Promoter Score basis, and trying to understand how customers value our products and our services, and what they actually think about the brand. Ajit: So our employees and our executives get paid based on a customer satisfaction metric. At one point, it was actually imperative, in terms of how they got paid. So we take this very, very seriously. And the transformation is clearly much more evolved than what it was three years ago. And now, pretty much every group in the company has a customer-focused metric. Whether it's product development and supply chain, eCommerce, or our global accounts customers. So everybody is measured on a customer-centric metric, which allows us to then drive the focus that's stated. And it's one of the top priorities for our COO, our CEO, my boss who basically runs all of the PC plus the IDC group. It's a key focus for him. So clearly, it's something that we take very, very seriously, and we are all trying to evolve with this one metric that we can look at and say, "Are we making absolute progress as a company, or not?" Stephanie: Got it. So a lot of times, metrics can actually have unintended consequences where maybe someone's trying to meet that metric and they're not doing the best thing to meet that. Did you see that when you guys were thinking about creating that customer metric? Did you see anything go wrong where you're like, "Oh, that's actually not a good one to rely on?" Any learnings throughout that process? Ajit: Yeah, look, e-commerce, we have been measuring customer satisfaction for the last, I don't know, 13 years or so. So as soon as I joined the company, two years into it, I figured out that, "Look, we need some form of getting feedback from our customers." So we have a very robust and mature process for eCommerce that we've been collecting roughly 20,000 customer feedback from a survey that we do online. So we have had a model for a long time, that uses the feedback. The biggest challenge, always, I think, is trying to figure out correlation of what factors will drive it. I think that's been the big controversy. So is it delivery metrics? Is it quality metrics? Is it product design? Is it the call center experience? So, I think there is a ton of data, and we have requested data to find out the top factors. And those factors keep changing. So- Stephanie: What are the top factors right now, that you see? Ajit: So what we see is product quality is undeniably the number one thing that the customers actually value. Hybrid customers truly value delivery. So delivery times and making sure that you're keeping your commitment in terms of products. They definitely value help in the call center as a metric. So there's probably a list of about 20, that we track. And the big ones really are product quality, delivery, out-of-the-box experience, those kinds of things. Service, as an example, right? We do surveys of customers on their service. That's a pretty important part of their feedback. But the purchase survey that we do is more around the purchasing experience. And customers are not shy, and they give you exactly you know what is important to them. And the one thing that we find is that some of the metrics that are difficult to move. Like product quality, as an example, Lenovo's product quality is very high. So it's always in the 90% range. And for us to move a percentage point on product quality is very, very difficult. Ajit: But there are several others where, like delivery and other metrics that float a lot more in this, there's ability for us to go change that, if you are focused on trying to drive certain changes. So the key for us is to say, "Which are the metrics that we can influence, that the team can actually take actions? Whether it's on the website, whether it's on trying to do training, or whether it's really trying to figure out how we message things to the customer differently, do proactive phone calls." One of the things that we do. But the key is to really identify those things that truly can be moved meaningfully, and we can put energy behind it, and then keep going. Ajit: Last year, we moved our CSAT score, or our NPS score by almost 35%. So that's a pretty substantially good jump, in terms of effectiveness. And that's because we identified a few things that we thought compelling. We had a business management system around it, we made IT changes. So all those things configured into us focusing and moving things in a certain direction. So I think that's the key. When it comes to customer-centricity, the challenge is that the customers are not standing still. Their expectations are going up every single day. So you have to do a lot more, to make meaningful progress. So you can't just stop. You have to continually change and continually improve the processes. Ajit: And that's always tricky because you have to really be at it, and you've got to use data to really understand what's changed, what's moving, what's the new irritant? You have to do social listening, you have to really start scanning your data that you get from your customers to figure out what's the new irritant, and how are you going to manage them. So it is certainly not an easy process. It's a very challenging process. But it is also something, I think, that is very, very important, if you, as a brand, need to keep your customers happy. Stephanie: Yeah, I completely agree. If you were to point to, the larger theme of being able to improve your customer satisfaction score, what was the largest thing that you changed, or adjusted, that made it so you could improve that score, by, I think you said 35%? Ajit: Yeah. So the one big thing that we changed was, we always had a very high amount of customization on the website. So ThinkPads, as you know, can be customized. And obviously, a customized product takes a longer time than if you had something in stare. So we have traditionally had a lot of our ThinkPads customized. And we made a conscious choice to really figure out how to keep stock of some of our high-flying products, or the fast-selling products. And so, that is a pretty significant shift, because when you have to ship something centrally from one warehouse, versus, you have to ship products from a warehouse or a manufacturing facility to a distribution center, and manage inventory, it obviously is not as efficient as trying to run something directly from the factory. Ajit: But we made the choice to move some other products to local distribution, to speed up delivery of our products. And that definitely helped. And we had some issues with supply. We're having some industry-wide constraints on some of the supply. And therefore, this whole process of managing inventory locally really helped us manage customer expectations a little bit better than what we're used to. So that is one example of what we did, that really helped. Ajit: Now, we also made a number of changes on the website, from messaging, whether it's a credit card processing screen, or whether it's a product page, or whether it's a configurator design. Any number of things that we feel are irritating customers, we have it list of maybe 500 items that we work through at any given time. And everybody is going through those things and fixing it. And then that incrementally adds a little bit of help. But the big ticket items are always around supply, product quality, call center management, pricing, promotion challenges. Some customers see discounts that are different, and I.e. managing those correctly... So it really is those big buckets that we want to make sure that we are focused on, we're fixing. And ultimately, the customer feels like we are being responsive to their needs. Stephanie: That's really fun, haring how you're able to drill in on a few of those things, and shift customer perception and happiness so much. Are there certain metrics that you use when it comes to, like you said, looking at what's irritating the customers, or where the website is maybe failing in certain areas? Is there a set of metrics that you look at, maybe bi-weekly or weekly with your team, to see how things are doing? And if so, what are those metrics? Ajit: Yeah. So when you talk about metrics, we have a website, a technical side of looking at metrics for the website, which is the IT organization that basically looks at all the technology stuff. It is, "What does the response time look like? What is your mobile performance? What's the page performance? 404 errors, page not found, the timeout errors on your checkout page, blah, blah, blah, blah. So there's probably like 100 things that somebody looks at every single day and then we manage those by exception. So we know what the numbers are. There's somebody constantly looking at those. Ajit: Then that is the website feedback mechanism, which is, when a customer comes online, something like our opinion lab, or a survey mechanism that basically allows customers to give you a feedback. So we randomly select customers that are on the website. We actually give them the opportunity to respond to the experience. We collect experience on their research process, their buying process, the website complexity, blah, blah, blah. So we get a ton of feedback from our customers on that particular thing. And then like I mentioned to you, we have this thing called the online ordering experience, and the purchase experience. So we get 20,000 or so responses every two weeks from all these countries, which we analyze. Ajit: Then, we obviously have social listening, where we actually listen to what the customers say. And then that is a common section where customers give us comments, and we use some form of AI stuff, to actually binge through all that stuff, to really get the sentiment analysis, and big ticket items that are coming back. And we take all of these things into a composite score that then allows us to go look at and say, "Where are we falling short? What are the benchmarks? What's the threshold? What's the competitive benchmark that we should be looking at for each of these categories? Best in class." And then we benchmark ourselves and figure out what actions we need to take, based on why this mentions the regression analysis to say, "Okay, these things actually have a meaningful impact through the customer experience. And therefore, we got to go figure out how to remove people who are giving us ones twos and threes. How do we increase our nines and tens? And then everybody in between, how do we move them up," to basically minimize the customer irritations that we have in the system. Ajit: So it's a very systematic process. There is a team that basically looks at it. There's a supply chain element that's very real. There is a services element. There is a phone sales element. There is a chat sales element. So it's a very complex set of metrics that basically transcends all of the functional groups that have a small stake in that experience, as the customer goes from the website research, to buying the product, getting it serviced, talking to a customer rep'. So we take the end-to-end customer with journey and figure out all the points, if they touch something, and figure out how to measure them, so that we have an accurate understanding of where the irritant is, and what we need to do to make it better. Stephanie: Got it. So I know when it comes to getting feedback, I go on websites all the time and it's asking me to do a survey, give feedback, and at least for me, I don't normally do it. I just X-off, and I try and find what I want. How are you incentivizing these potential buyers or buyers to give you the feedback, and take these surveys, and get them to do what you want? Ajit: It's tricky. You have to do it in a way that doesn't bias the sample. And that's what I'm most worried about, is that I don't want to incite people to do the wrong thing. So what we do is, we have a... What I've noticed is that the core customers, they are actually always very vocal, especially if they are a brand loyalist. So we get a steady stream of feedback on brands loyals, which is great because I think they are finicky, and they are brand zealots, and they really take pride in making sure that they're providing feedback on things that they like and things that don't like. And quite frankly, it shapes perception and product strategy in many ways because it's a big group of customers. Ajit: The tricky part is the random customer, or the customer that truly hasn't built a relationship with us but just bought something. Those folks, we have to figure out how to drive the subscription into the process a little bit more meaningfully. We periodically a 5% off coupon. We periodically send out emails to people who have bought product. We always send out emails to people buy products for us, saying, "Give us feedback. Tell us what is it that we have done well, and what are the things that we haven't done well." On the phone, obviously, we have more success because we get a chance to talk to people. But it's a combination of things. In the past, I remember like five, six years ago we would run contest that basically gave prizes for people to actually participate. And then we reduce that a little bit, because it may tend to bias the sample a little bit. Ajit: Look, online reviews is the other one. We have a very robust online review process that we have on the website. So we get a ton of online reviews of our particular products also. So we use that, sometimes, to also incent people to give us more feedback. So there isn't a one size fits all answer for others. It just depends. Again, in some countries we get local feedback, and some others... And so, countries where we don't get as much feedback, we try to figure out what's the right way? Can we leverage our community? Can we leverage our brand? And other things. Can we gamify it? So there's lots of strategies depending on which country and which part of the world you're in, to incentivize the customer to actually engage more readily. In some countries it's a challenge. Just because it is challenging in countries like Europe, where trying to get around some of the privacy laws can be tricky. So it's a balance. But we have tried discounts, newsletters, contests, reviews, and rating, promoting them. Ajit: Having said all that, I do believe that building a community and trying to nurture that community is probably the easiest way for us to get more and more feedback, which is what we are trying to do, is to try and figure out how to engage these customers more meaningfully over a longer period of time, beyond the purchasing. But we're connecting them with the brand. And then, I think that that solves some of the feedback issues, because I think we can get a much higher response rate when that happens. Stephanie: Yeah. I've heard a lot of brands leaning towards that community aspect, at least from the people that we've had on the show. What are some of the initiatives that you guys are doing, to create that community? Ajit: Well, I won't give away all the secrets, but- Stephanie: Just give us a couple. Come on. Ajit: So the big communities that we are focused on, obviously one is SMB. SMB, we fundamentally believe are underserved. And I think that there's going to be a lot more SMBs in the workplace, going forward. Because I think a lot of them are millennials and Gen-Zs are very entrepreneurial. With the advent of technology progressing the way it's progressing, and digital technologies becoming more ubiquitous, but with the online space, I do believe that we will see a lot of internet businesses springing up. It's no longer really difficult for somebody to actually open a business or start a business if they have a good idea. So you will see a significant number of people actually coming online in the SMB space. And we are obviously very aware that we need to provide them an experience, a community, and a set of resources that make them productive and useful. Useful in the sense that, we give them something that is useful for them to be more productive. Ajit: So part of our challenge is to try figure out what is really important for them. So we definitely think community is important. But the work, I think, is very, very important. And the question is, "How do we drive relevance? What is really important for the SMB customer as they are online, beyond the products that they buy from us? How do we get them more out of technology? How do we get the more out of their work, their productivity, and how do we make sure that they are ultimately successful as they are part of our ecosystem?" Ajit: So I'll give you an example. Maybe they can hear from other SMB customers who are probably struggling with similar challenges. Maybe the ability to belong to a community that has other people doing similar things, or at least dealing with broad themes that they're dealing with, money, resources, training, those things become important. So the question is, "Can we provide some of those things to our SMB customers that make their lives a little bit easier, and therefore their affinity for our brand a little bit higher?" So that's one thing that we are definitely doing for SMBs. A lot of work to be done. We are just at the very, very early stages. But we do believe that a well thought out, longterm strategy will definitely help our ecosystem and our customers. Likewise, we will be thinking about students and gamers, and trying to figure out what we can do meaningfully to nurture the relationship we have with them. Stephanie: Got it. Have you shifted your strategy around online learning, students, gamers, since Covid started? Did you guys have to go into a quick pivot mode to start doing something different or planning for a different future than what you were maybe planning for six months ago? Ajit: Well, we started this strategy two years ago. Haven't changed much. So therefore, we do have a leg up because we have been thinking this for a little while. Covid just made it a little bit more easier to sell, and get traction. But the strategy we are on has basically been in place for a while, because we have been building IT capabilities and some of those things that we need to service our customers. This is not something you can just spin up in a day. These take much, much more longer-term. And there's plenty of partnerships and relationships that are [inaudible 00:42:24]. So it's not, certainly, something that you can just copy, or you can just do. It is capital-intensive. You need to put money into it. You need to do a lot of development. Do you need to really start thinking about the strategy much more clearly? So it's certainly not something that's the thought about yesterday. But I think that there's a lot more that we need to do to be relevant and to drive this to a scale. Stephanie: Cool. So I've heard that you like behavioral economics. I was wondering- Ajit: Yes. Stephanie: Yeah. I watched a few videos. I'm like, "Oh, me too." What principles have been useful, or how have they shaped the digital experiences that you build at Lenovo? Ajit: Yeah. Look, pretty much everything that you do on a website, or you do on business lends itself to some of the principles from behavioral economics. And some of them that are really interesting... I became a fan of behavioral economics with Dan Ariely, who basically is local here at Duke. And we had Dan come to campus and speak to our people a couple of times. This was like maybe seven, eight years ago. So I've been a big follower of it. And clearly, what I understand from it is that people are predictable, and they can be predictably irrational in how they make decisions. So sometimes, common sense is probably overrated, believe it or not, when it comes to some of the design principles and some of the things that we do from a merchandising and marketing standpoint. Ajit: So big couple of things for me is, look, people want to compare things, right? And they freeze when they're not able to compare things that are similar. If you give them these similar things and ask them to compare it, they always rationalize it to something that is a common denominator. So as an example, you don't have to bet an apple to an orange. Obviously, they are very different fruits. And to ask them to really say which one you like more becomes a preference issue, more than a rational exercise. And so, if you're truly asked them to assign value to it, more likely, they are going to say an apple cost $1 and an orange costs 50 cents. So maybe the apple is 2X better than the orange. That would be the natural way of thinking. Ajit: Now, when you tell them to compare a PC of one kind to a PC of a completely different kind, they are likely to be completely lost because they just are not able to understand the fundamental differences between them. Or, it would take them an inordinate amount of time for them to actually compare the products, disparate products. And so what they do is they start thinking about price. And price is not necessarily the best way to make a decision on something that basically is going to be your technology partner for a few years, and going to make you productive in the kinds of things that you need to do. Ajit: So I've realized that look, you have to really enable a comparison of products in a much more meaningful way. So make sure that the customers don't have to really go out of their way to think about how to compare products. And obviously, it's challenging when we have so many products coming out at this breakneck speed, that some of the technology cannot keep up. But to me, comparing things is an important paradigm, in my opinion. Stephanie: It brings back the memories when I used to open up a bunch of tabs to compare products before the company started shifting to that comparison model. But I do still think there's a long way to go when it comes to, especially comparing tech. Because when I'm looking at a computer and it's saying, "Here's all the specs of this computer." A lot of those things, I don't even know, why would I want to upgrade? Whereas if it said, "Well this means that you'll be able to store this many pictures versus this." Or, "You'll have a much faster internet speed," or, "Remember how your computer's working really slowly when you try and open up Photoshop? It won't do that anymore." It would be nice to start seeing a more consumer perspective of, "What does this do for me?" Instead of just being like, "It's this many terabytes," and all the technical specs to it. Are you all thinking about that kind of shift, or how are you incorporating them? Ajit: Definitely, comparison of products is a big thing. Search, how you do search comparison is a big thing. So we are absolutely focused on it. And to make things worse, the mobile form factor doesn't facilitate very readily, comparison of complex things. So we have to figure out more elegant and meaningful ways in which we can have people compare products on a small form factor like a phone. So yeah, clearly very, very important, on top of our list. Always challenging, always evolving. So yeah, we have to go figure out how to do that. Ajit: One other thing that I would tell you when it comes to behavioral economics and behavioral science is, bias, the role of bias. And I think that this is a big one because I think people will generally, when they're making decisions, executives like me included, we make decisions based on anecdotal evidence, based on what we have done. And we take that size, and of one, and we try to generalize, hypothesize our theory based on a bad experience or a good experience. And we extrapolate that to the population and end up driving everybody crazy and not looking at numbers the right way, and ignoring numbers, and making decisions that are suboptimal. Ajit: So, the work by Kahneman and some of the work that the Israelis have done, especially because it seems like that's where all of the cool stuff is coming from on behavioral economics, from the Hebrew University, the work is really, really telling us not to be biased, and to suspend judgment, and to really focus on what the data tells us, and to pay attention to not fall into the trap of the bias. So, it takes a while, and it takes a lot of effort, but I think it's a good reminder for us to really focus on managing and minimizing our biases, so that we can make optimal decisions that affect our customers in a very positive way. Stephanie: Completely agree. Do you all do trainings at Lenovo? Whether it's for the executives, or the employees, when it comes to how to create surveys and look at the data in a non-biased way, and collect data from certain people, where it's not biased. Do you do anything around that to teach those principles? Ajit: I also teach, sometimes. So I have been pushing this very heavy and hard with my teams. And obviously, a lot of the executives read these books, so it's not lost on them. But look, because we have such a huge direct customer-facing interface, the focus on the online space has to be much inordinately higher, because I think the impact is much, much higher on the direct interface. So we are definitely driving this. A lot of our people are classically trained. They all go to classic UX/UI trading. But more and more, I also have started relying on quantitative data at scale, for making decisions, rather than opinion. So I am not, and my team hates me for this. But I'm not a big fan of qualitative information. I would much rather not ask people anything and just look at the data and interpret the data and start making decisions. Ajit: Because people say one thing, and they do another. And it's not a new notion. I think a lot of people know this. And at scale, when you're talking about tens of millions of records, I think the data doesn't lie. In fact, if the data says that, then that's what we should do because it services a majority of our customers positively. So that's the other principle that I use is, "Don't ask, just look at the data and try and make decisions based on the data. Try to understand the data, and then design your tests and your experiments based on what you see, rather than asking a bunch of people in a panel, and they'll tell you some stuff." And I'm sure it goes in some places, but I am always skeptical when that happens because I'm worried about bias. Stephanie: Do you think, from your experience, a lot of companies are still focusing on that qualitative data and it's actually leading them down the wrong path, or they're creating either new products or new website experiences that are probably going to fail because they're using that qualitative data? Ajit: I am sure people are. But I think people also... They all read these same things. But I think there is probably enough anecdotal evidence that suggests that there's lot of people who still use those principles. So I don't know the exact number, and any guess that I would venture would be wrong, so I would not venture it. But my sense is that yeah, it requires activism, like for some of the people and the executives, to actually read the books, get interested, get excited, and then drive everybody to get to follow it and understand it. It's a field that's still evolving. So it takes effort. Right? And then the infrastructure that's needed to do at-scale testing, and A/B testing, they're not cheap. It's expensive. Ajit: So, I think the question is, how many people are driving digital transformation? How many people are digitally savvy? How many companies are? And my sense is that that's a very small number. I think everybody's talking about digital transformation now, because of all the issues that are around them. But I can tell you that the number of companies that are digitally savvy after you take out some of the tech companies and the internet companies, is very small companies. There are a few who companies have a pretty big gap. So my sense is that they're not, probably, using it as much. Stephanie: Yeah. I completely agree. So, zoom out a bit for the last couple of minutes. In the world of e-commerce, are there any big disruptions you see coming or what do you see in the future, that you guys are planning for? Ajit: Well, I think this whole transformation, this whole crisis actually points to the fact that the digital transition will be much faster. I think that people have realized a couple of things. One, travel, may be overrated. People have realized that education, going to school, sitting in classrooms, may be overrated. People are going to realize that working from home is not such a big deal. And so, I think the workforce productivity, the online education, travel as a paradigm, and how companies operate, all of that will, I think, become ripe for disruption. So you will see, increasingly, technology solutions practices that's going to upend a lot of the work practices, and the educational practices. So that's happening. That's going to happen, and it's going to accelerate. Ajit: Clearly, I think that this will also boost some of the technology things like AR, VR, IOT, both from home and from work. I think it'll accelerate some of those things because it'll be a natural extension of some of the things that people are doing. I think the move to cloud is going to get accelerated, because I think everybody wants access to everything. As 5G comes, I think a lot of these things that are laborious today might experience a complete revival, and complete transformation when it comes to speed, and feel, and what's possible. So I think that the time is right for us to get much more digitally-connected. Ajit: The last one is mobile, in terms of what's going on with mobile and how mobile is going to get a face, or as 5G comes on. So it'll be interesting to see how retail, how millennials and gen-Zs, how SMBs, all of these groups of people that make up a pretty significant part of the population... I think students, gamers and SMB is probably at about 40% of the world's population. So you'll see that there's going to be a significant shift, quite rapidly, in the next three to five years. And there's going to be a considerable amount of disruption that'll happen as a result of this. Ajit: You will see winners and losers. This will be probably a long list of people we're going to go out of business if they're not able to adapt quickly to some of the changes that are happening. The companies that get it naturally will have much bigger gains, which will make them much more competitive, and difficult to beat. So you will see a lot of winners and losers emerging out of this whole crisis, and as the digital evolution continues in a significant way. Stephanie: Yeah. I love that answer. So before we move on to the lightning round, which is where we ask a question and you have one minute or less to answer, are there any other high-level thoughts or words of wisdom that you want to drop in the podcast? Ajit: No. Well, I just tell the people who are in this space, the eCommerce space, that their time has come, finally. So they should just buckle up and help their companies and see where the ride goes. Stephanie: I love that. All right. So the lightning round, like I said, brought to you by Salesforce Commerce Cloud, is where I will ask a question and you have one minute or less to answer it. Are you ready Ajit? Ajit: Okay. Stephanie: All right. What's up next in your travel destinations, after we're allowed to travel? Ajit: I would like to go to Cuba because I'm running very low on my cigars. Stephanie: Wow, that sounds cool. All right. What's up next on your Netflix queue? Ajit: I just finished Ozark. And I'm trying to figure it out how to watch The Last Dance. But it's not on Netflix, unfortunately. Stephanie: Maybe Hulu? Ajit: I've been watching Heist. So maybe I'll keep watching that. Stephanie: Cool. What's up next for... Is it lunchtime there? I guess a little bit past lunch. What's that next for dinner? Ajit: Dinner, I had cooked on the weekend, some lamb curry and some roti. So I'm going to just reheat that and eat it. Stephanie: Yum. What's up next on your podcast list or your reading list? Ajit: Ah, reading. I'm reading The Billion Dollar Whale. Stephanie: What's that one about? Ajit: It's about this dude, Wall Streeter, who basically flees a billion dollars right under the nose of Wall Street and big finance people and everybody else in the world. So it's like DiCaprio movie. Stephanie: Oh, which one is that? The Wolf of Wall Street? Ajit: The Wolf of Wall Street. So it's loosely a character like that. So I'm just a quarter into it. It's unbelievably engaging and interesting. Stephanie: I have to look into that. Ajit: Yeah, you should. It's pretty cool. Stephanie: You have a few, you said? A few more books that you're working on? Ajit: I still haven't finished Homo Sapiens, and some of the books that he had written. So I'm still trying to figure it out when I can finish those, with things slow. Stephanie: All right. What's your favorite tool or technology that you're either learning right now or you're thinking about implementing in the future? Or it could be a skill? Ajit: I don't know about skill. I don't know very many skills. Technology. We are constantly thinking about technology. And the big technology that we are thinking about is how to drive the subscriptions business. So it really is trying to figure out how to give customers the convenience of buying something as they pay-for-use concept. Because I think it's becoming very, very clear that the reason why people like Netflix and Adobe and some of our other customers and clients are successful, is because people are able to pay. And in [inaudible 00:58:45], I think that business model is very appropriate. People don't want to spend a lot of money upfront. So trying to figure out how to make their lives a little easier. Stephanie: Awesome. Yeah, I definitely- Ajit: Hello. Stephanie: Subscription business. All right, the last big one. So it sounds like you guys are doing a great job of staying ahead of expectation, and your competition. So in your opinion, what's up next for e-commerce professionals? Ajit: Well, I think it will become a key priority for most organizations. I think the digital transformation plus e-commerce, if they are in a business that does e-commerce, will become a major priority. The key will be to try and figure out how to build out that strategy in a meaningful way. If they are global, I think they have to figure out how to make it more global. If they are not global, they have to figure out how to get more local. Either way, you really have to figure out what that business model will look like. And it's not going to be easy because you have to deal with legacy systems, and you have to deal with legacy operating processes, and you have to deal with the legacy sales force and the legacy set of go-to-market strategies. So trying to figure out how to meaningfully make sense of it. There's a bunch of companies that are doing well. But there's going to be a bunch of companies that will have to figure this thing out. So they will be busy, and they will be in demand. Stephanie: Awesome. Love it. Any final plugs before we hop off the podcast? Ajit: No. I just want to say that if you have good people that work for you, you should try and figure out how to hold on to them, because it's going to get a mad rush to get to good people. Stephanie: Oh yeah. I completely agree with that one. All right. Ajit, it's been a blast. Thanks so much for coming on the show. Ajit: Thank you so much, Stephanie. I enjoyed our conversation.
Employers wanting cameras always on? The Chinese government is forcing cameras into homes? And...what the Hell are a UAPs?!?!?!?!? All that and much, much more… Guest Co-Host: N/A Opening Audio: N/A The Foreplay: --The Sovryn Tech Polytechnic Telegram group (https://bit.ly/2vrgcnr), help out the show with the Sovryn Tech Amazon Wishlist (http://wishlist.sovryntech.com), Firefox 76 (https://bit.ly/2SGcFdA), Lenovo pre-installing Fedora Workstation on Thinkpads (https://bit.ly/35Fsma4), iOS opt-out “exposure notifications” (https://bit.ly/2L6J88P), Kindles getting dark mode. The Main Story: --”The Navy and UAPs” Link: https://bit.ly/3ba2Lr2 HackSec: --”Get a FREE Camera in Front of Your Home!” Link: https://youtu.be/f5UpkQPiRCQ, https://cnn.it/2LcMjeZ Important Messages (Q&A):(Send your questions to: questions@sovryntech.com) --”Hiding the Key for 100 Years” Link: http://ollydbg.de/Paperbak/ The Gaming Grid: --”Mortal Kombat 11: Aftermath” Link: https://bit.ly/2YNTkLt Album of the Week: --”Terri Tims (Paul Sabu) -- Whole Lotta Trouble (2001)” The Climax: --”Gene Roddenberry: The Last Conversation” APPENDIX & SPONSORS: --”Sovryn Tech Polytechnic Telegram Group” Link: https://bit.ly/2vrgcnr --”The Sovryn Tech Amazon Wishlist” Link: http://wishlist.sovryntech.com --”Listen to Free Talk Live” Link: https://www.freetalklive.com --”Blocktap.io” Link: https://www.blocktap.io/ --”Check out Vaultoro for Crypto & Gold!” Link: https://www.vaultoro.com/ --”Check out the Free State Project!” Link: https://www.fsp.org/join/ --”BlueChew.com & Use Code ‘TECH’” Link: https://bluechew.com/ --”Blocktap.io” Link: https://www.blocktap.io/ --”Use Fastmail!” Link: https://fastmail.sovryntech.com --”Use Booking.com and Earn $25!” Link: https://booking.sovryntech.com --"Buy the Insurgo PrivacyBeast X230!” Link: http://bit.ly/2GoFjdj --"Surveillance Self-Defense" Link: https://ssd.eff.org/ --"RetroShare" Link: http://retroshare.net/ --“Books of Liberty” Link: http://booksofliberty.com/ --"Dark Android: 2017 Edition" Link: http://darkandroid.info --”Sovryn Universe, Vol. 1” Link: https://amzn.to/2MrvfEy ------------------------------------------------------------------------- Donate with BTC: 364mWGVeAEJmMmTKdirbYW8Earai6e9X2F You can e-mail the show at: bbs@sovryntech.com ------------------------------------------------------------------------- You can also visit our IRC channel on Freenode: #SovNet Or just go to: http://sovryntech.com ------------------------------------------------------------------------- https://t.me/joinchat/Amg5yBMU608MIsbOSa3wew http://sovryntech.com https://twitter.com/sovryntech
Employers wanting cameras always on? The Chinese government is forcing cameras into homes? And...what the Hell are a UAPs?!?!?!?!? All that and much, much more… Guest Co-Host: N/A Opening Audio: N/A The Foreplay: --The Sovryn Tech Polytechnic Telegram group (https://bit.ly/2vrgcnr), help out the show with the Sovryn Tech Amazon Wishlist (http://wishlist.sovryntech.com), Firefox 76 (https://bit.ly/2SGcFdA), Lenovo pre-installing Fedora Workstation on Thinkpads (https://bit.ly/35Fsma4), iOS opt-out “exposure notifications” (https://bit.ly/2L6J88P), Kindles getting dark mode. The Main Story: --”The Navy and UAPs” Link: https://bit.ly/3ba2Lr2 HackSec: --”Get a FREE Camera in Front of Your Home!” Link: https://youtu.be/f5UpkQPiRCQ, https://cnn.it/2LcMjeZ Important Messages (Q&A):(Send your questions to: questions@sovryntech.com) --”Hiding the Key for 100 Years” Link: http://ollydbg.de/Paperbak/ The Gaming Grid: --”Mortal Kombat 11: Aftermath” Link: https://bit.ly/2YNTkLt Album of the Week: --”Terri Tims (Paul Sabu) -- Whole Lotta Trouble (2001)” The Climax: --”Gene Roddenberry: The Last Conversation” APPENDIX & SPONSORS: --”Sovryn Tech Polytechnic Telegram Group” Link: https://bit.ly/2vrgcnr --”The Sovryn Tech Amazon Wishlist” Link: http://wishlist.sovryntech.com --”Listen to Free Talk Live” Link: https://www.freetalklive.com --”Blocktap.io” Link: https://www.blocktap.io/ --”Check out Vaultoro for Crypto & Gold!” Link: https://www.vaultoro.com/ --”Check out the Free State Project!” Link: https://www.fsp.org/join/ --”BlueChew.com & Use Code ‘TECH’” Link: https://bluechew.com/ --”Blocktap.io” Link: https://www.blocktap.io/ --”Use Fastmail!” Link: https://fastmail.sovryntech.com --”Use Booking.com and Earn $25!” Link: https://booking.sovryntech.com --"Buy the Insurgo PrivacyBeast X230!” Link: http://bit.ly/2GoFjdj --"Surveillance Self-Defense" Link: https://ssd.eff.org/ --"RetroShare" Link: http://retroshare.net/ --“Books of Liberty” Link: http://booksofliberty.com/ --"Dark Android: 2017 Edition" Link: http://darkandroid.info --”Sovryn Universe, Vol. 1” Link: https://amzn.to/2MrvfEy ------------------------------------------------------------------------- Donate with BTC: 364mWGVeAEJmMmTKdirbYW8Earai6e9X2F You can e-mail the show at: bbs@sovryntech.com ------------------------------------------------------------------------- You can also visit our IRC channel on Freenode: #SovNet Or just go to: http://sovryntech.com ------------------------------------------------------------------------- https://t.me/joinchat/Amg5yBMU608MIsbOSa3wew http://sovryntech.com https://twitter.com/sovryntech
The Fedora and Lenovo partnership is about more than just selling Thinkpads with Linux pre-installed. In this special video interview, Fedora lead Matthew Miller and Lenovo's Senior Linux Software Engineer Mark Pearson join me to discuss a TON of details. There are SEVERAL surprises along the way, and most of them are going to make you jump for joy. This is how Linux gets treated like a first-class citizen. Special Guests: Mark Pearson and Matthew Miller.
The team discusses a dodgy Windows Update, Lenovo's new Linux-based ThinkPads, the ups and downs of life in lockdown and a tool that turns your Canon DSLR into a webcam. Our Hot Hardware candidate is Huawei's P40 Pro - an Android smartphone that ships without Google apps and services.
This Week in Linux is a Proud Member of the Destination Linux Network! https://destinationlinux.network Sponsored by Digital Ocean - https://do.co/dln On this episode of This Week in Linux, the amount of news we have to cover is just crazy! We've got multiple big stories in Distro News with Ubuntu 20.04 releasing, Manjaro 20 releasing, Fedora announcing that Fedora is coming to Lenovo's ThinkPads, and even more from Void Linux and Intel's Clear Linux. In the housekeeping section were going to be talking about the new DLN News & Article website, Front Page Linux. There's just so much news this week. LXQt 0.15 was released and there's a little bit of weirdness around the LXQt project to discuss. We've also got some new releases in the App News section for Kdenlive 20.04, BleachBit 4.0 and Vivaldi 3.0. All that and much more coming up. I'm Michael Tunnell with TuxDigital and this is your Weekly Source for Linux GNews. Become a Patron: - https://tuxdigital.com/patreon - https://tuxdigital.com/sponsus - https://tuxdigital.com/contribute Other Links: - https://destinationlinux.network/store - https://michaeltunnell.com Segment Index: Show Notes - https://tuxdigital.com/twinl101 01:07 = Sponsored by Digital Ocean ( https://do.co/dln ) 02:35 = Ubuntu 20.04 LTS Released 14:02 = Manjaro 20.0 Lysia Released 22:17 = Fedora is Coming to Lenovo ThinkPads 26:29 = Void Linux: The Drama & The Future 29:53 = Front Page Linux 33:27 = Destination Linux 37:20 = Become a Patron of TuxDigital & TWinL 39:31 = LXQt 0.15 Released (What's Up with LXQt) 45:59 = Kdenlive 20.04 Released 50:47 = BleachBit 4.0 Released 53:25 = Vivaldi 3.0 Released 59:06 = Outro Linux #GNews #OpenSource
Fedora Project Leader Matthew Miller joins us to discuss Lenovo shipping ThinkPads loaded with Fedora, and our review of the new 32 release.
Fedora Project Leader Matthew Miller joins us to discuss Lenovo shipping ThinkPads loaded with Fedora, and our review of the new 32 release. Plus Ubuntu's Director of Desktop Martin Wimpress covers the details everyone missed in 20.04. Special Guests: Martin Wimpress, Matthew Miller, and Neal Gompa.
On this episode of This Week in Linux, the amount of news we have to cover is just crazy! We’ve got multiple big stories in Distro News with Ubuntu 20.04 releasing, Manjaro 20 releasing, Fedora announcing that Fedora is coming to Lenovo’s ThinkPads, and even more from Void Linux and Intel’s Clear Linux. In the… Read more
Ubuntu releases 20.04 LTS, Kdenlive picks up support for the OpenTimelineIO interchange format, Mozilla expands its community analysis program with a new blog, Lenovo and Fedora announce a partnership for pre-installation on some ThinkPads, and Intel gives a boost to The Linux Foundation's mentorship program.
Ubuntu releases 20.04 LTS, Kdenlive picks up support for the OpenTimelineIO interchange format, Mozilla expands its community analysis program with a new blog, Lenovo and Fedora announce a partnership for pre-installation on some ThinkPads, and Intel gives a boost to The Linux Foundation's mentorship program.
This week we’ve been auditing Thinkpads and making beta releases of Ubuntu. We round up some of what’s new in the Ubuntu flavours Focal Fossa beta releases and discuss stories from the tech world. It’s Season 13 Episode 03 of… Read more ›
The Personal Computer Show Wednesday January 29, 2020 PRN.fm Streaming On the Internet 6:00 PM Eastern Time IN THE NEWS • Nearly all ThinkPads have defective USB-C ports • Relief from hidden cable TV fees • Pluto TV Is a Must Have Free Streaming Service for Cord Cutters • Microsoft issuing free Windows 7 fix after introducing bug in final updates • Apple Macs Can't Get Viruses or Malware - Fact or Myth? FEATURE SEGMENTS IT Pro Series – Benjamin Rockwell • Passwords Are a Necessary Evil From the Tech Corner • What is the Internet of Things, and how does it work? • FCC gives Google and Sony permission to dole out 3.5GHz spectrum All Hands on Tech – Marty Winston • Small-scale solar power for outdoor devices
This week we’ve been talking to the BBC about Thinkpads and Ubuntu goes Pro. We round up the news from the Ubuntu community and discuss our picks from the wider tech news. It’s Season 12 Episode 35 of the Ubuntu… Read more ›
Chz sits down with Alan Pope (popey) to discuss his thoughts about ThinkPads, and why they might be the perfect Linux laptop. Find out what those model numbers really mean, plus our tips for picking which one is right for you. Special Guest: Alan Pope.
Chz sits down with Alan Pope (Popey) to discuss his thoughts about Thinkpads, and why they might be the perfect Linux laptop.
This week we’ve been playing LEGO Worlds and tinkering with Thinkpads. We round up the news and goings on from the Ubuntu community, introduce a new segment, share some events and discuss our news picks from the tech world. It’s… Read more ›
This week we’ve been cataloging hardware (mostly crusty Thinkpads). We interview Kyle Fazzari, serior robotics engineer at Canonical, bring you some command line love and go over all your feedback. It’s Season 12 Episode 24 of the Ubuntu Podcast! Alan… Read more ›
* Adios Antergos - https://antergos.com/blog/antergos-linux-project-ends/ * Adguard follow up - https://blog.linuxserver.io/2019/05/20/adguard-home-first-thoughts/ * New AMD powered Thinkpads! - https://hothardware.com/news/lenovo-thinkpad-x395-t495-t495s-amd-ryzen-pro-apus-radeon-vega * Github package registry - https://www.reddit.com/r/docker/comments/bn3lgl/github_releases_package_registry_with_docker/ LSIO News * BaseImage updates * New site design to be released soon. Will officially deprecate old image list in favour of Fleet.
Welcome to the second episode of the Neowin Podcast, where we discuss the new OnePlus 7 and 7 Pro, the upcoming spec variant for the Suface Book 2 15-inch, and much more. Come join us! For timestamps please visit: https://www.neowin.net/news/oneplus-two-new-phones-another-20h1-build-and-more-in-episode-2-of-the-neowin-podcast
Mehr Informationen, Quellen und Timecodes im Artikel unter: http://url.qso4you.com/4yh Timecode 02:50 - Daten von Millionen US-Bürgern ungeschützt im Netz 25:08 - ThinkPads von Lenovo / IBM und Erfahrungen mit HP 33:30 - NextGen VPN WireGuard 43:40...
OpenBSD on Microsoft Surface Go, FreeBSD Foundation August Update, What’s taking so long with Project Trident, pkgsrc config file versioning, and MacOS remnants in ZFS code. ##Headlines OpenBSD on the Microsoft Surface Go For some reason I like small laptops and the constraints they place on me (as long as they’re still usable). I used a Dell Mini 9 for a long time back in the netbook days and was recently using an 11" MacBook Air as my primary development machine for many years. Recently Microsoft announced a smaller, cheaper version of its Surface tablets called Surface Go which piqued my interest. Hardware The Surface Go is available in two hardware configurations: one with 4Gb of RAM and a 64Gb eMMC, and another with 8Gb of RAM with a 128Gb NVMe SSD. (I went with the latter.) Both ship with an Intel Pentium Gold 4415Y processor which is not very fast, but it’s certainly usable. The tablet measures 9.65" across, 6.9" tall, and 0.3" thick. Its 10" diagonal 3:2 touchscreen is covered with Gorilla Glass and has a resolution of 1800x1200. The bezel is quite large, especially for such a small screen, but it makes sense on a device that is meant to be held, to avoid accidental screen touches. The keyboard and touchpad are located on a separate, removable slab called the Surface Go Signature Type Cover which is sold separately. I opted for the “cobalt blue” cover which has a soft, cloth-like alcantara material. The cover attaches magnetically along the bottom edge of the device and presents USB-attached keyboard and touchpad devices. When the cover is folded up against the screen, it sends an ACPI sleep signal and is held to the screen magnetically. During normal use, the cover can be positioned flat on a surface or slightly raised up about 3/4" near the screen for better ergonomics. When using the device as a tablet, the cover can be rotated behind the screen which causes it to automatically stop sending keyboard and touchpad events until it is rotated back around. The keyboard has a decent amount of key travel and a good layout, with Home/End/Page Up/Page Down being accessible via Fn+Left/Right/Up/Down but also dedicated Home/End/Page Up/Page Down keys on the F9-F12 keys which I find quite useful since the keyboard layout is somewhat small. By default, the F1-F12 keys do not send F1-F12 key codes and Fn must be used, either held down temporarily or Fn pressed by itself to enable Fn-lock which annoyingly keeps the bright Fn LED illuminated. The keys are backlit with three levels of adjustment, handled by the keyboard itself with the F7 key. The touchpad on the Type Cover is a Windows Precision Touchpad connected via USB HID. It has a decent click feel but when the cover is angled up instead of flat on a surface, it sounds a bit hollow and cheap. Surface Go Pen The touchscreen is powered by an Elantech chip connected via HID-over-i2c, which also supports pen input. A Surface Pen digitizer is available separately from Microsoft and comes in the same colors as the Type Covers. The pen works without any pairing necessary, though the top button on it works over Bluetooth so it requires pairing to use. Either way, the pen requires an AAAA battery inside it to operate. The Surface Pen can attach magnetically to the left side of the screen when not in use. A kickstand can swing out behind the display to use the tablet in a laptop form factor, which can adjust to any angle up to about 170 degrees. The kickstand stays firmly in place wherever it is positioned, which also means it requires a bit of force to pull it out when initially placing the Surface Go on a desk. Along the top of the display are a power button and physical volume rocker buttons. Along the right side are the 3.5mm headphone jack, USB-C port, power port, and microSD card slot located behind the kickstand. Charging can be done via USB-C or the dedicated charge port, which accommodates a magnetically-attached, thin barrel similar to Apple’s first generation MagSafe adapter. The charging cable has a white LED that glows when connected, which is kind of annoying since it’s near the mid-line of the screen rather than down by the keyboard. Unlike Apple’s MagSafe, the indicator light does not indicate whether the battery is charged or not. The barrel charger plug can be placed up or down, but in either direction I find it puts an awkward strain on the power cable coming out of it due to the vertical position of the port. Wireless connectivity is provided by a Qualcomm Atheros QCA6174 802.11ac chip which also provides Bluetooth connectivity. Most of the sensors on the device such as the gyroscope and ambient light sensor are connected behind an Intel Sensor Hub PCI device, which provides some power savings as the host CPU doesn’t have to poll the sensors all the time. Firmware The Surface Go’s BIOS/firmware menu can be entered by holding down the Volume Up button, then pressing and releasing the Power button, and releasing Volume Up when the menu appears. Secure Boot as well as various hardware components can be disabled in this menu. Boot order can also be adjusted. A temporary boot menu can be brought up the same way but using Volume Down instead. ###FreeBSD Foundation Update, August 2018 MESSAGE FROM THE EXECUTIVE DIRECTOR Dear FreeBSD Community Member, It’s been a busy summer for the Foundation. From traveling around the globe spreading the word about FreeBSD to bringing on new team members to improve the Project’s Continuous Integration work, we’re very excited about what we’ve accomplished. Take a minute to check out the latest updates within our Foundation sponsored projects; read more about our advocacy efforts in Bangladesh and community building in Cambridge; don’t miss upcoming Travel Grant deadlines, and new Developer Summits; and be sure to find out how your support will ensure our progress continues into 2019. We can’t do this without you! Happy reading!! Deb August 2018 Development Projects Update Fundraising Update: Supporting the Project August 2018 Release Engineering Update BSDCam 2018 Recap October 2018 FreeBSD Developer Summit Call for Participation SANOG32 and COSCUP 2018 Recap MeetBSD 2018 Travel Grant Application Deadline: September 7 ##News Roundup Project Trident: What’s taking so long? What is taking so long? The short answer is that it’s complicated. Project Trident is quite literally a test of the new TrueOS build system. As expected, there have been quite a few bugs, undocumented features, and other optional bits that we discovered we needed that were not initially present. All of these things have to be addressed and retested in a constant back and forth process. While Ken and JT are both experienced developers, neither has done this kind of release engineering before. JT has done some release engineering back in his Linux days, but the TrueOS and FreeBSD build system is very different. Both Ken and JT are learning a completely new way of building a FreeBSD/TrueOS distribution. Please keep in mind that no one has used this new TrueOS build system before, so Ken and JT want to not only provide a good Trident release, but also provide a model or template for other potential TrueOS distributions too! Where are we now? Through perseverance, trial and error, and a lot of head-scratching we have reached the point of having successful builds. It took a while to get there, but now we are simply working out a few bugs with the new installer that Ken wrote as well as finding and fixing all the new Xorg configuration options which recently landed in FreeBSD. We also found that a number of services have been removed or replaced between TrueOS 18.03 and 18.06 so we are needing to adjust what we consider the “base” services for the desktop. All of these issues are being resolved and we are continually rebuilding and pulling in new patches from TrueOS as soon as they are committed. In the meantime we have made an early BETA release of Trident available to the users in our Telegram Channel for those who want to help out in testing these early versions. Do you foresee any other delays? At the moment we are doing many iterations of testing and tweaking the install ISO and package configurations in order to ensure that all the critical functionality works out-of-box (networking, sound, video, basic apps, etc). While we do not foresee any other major delays, sometimes things happen that our outside of our control. For an example, one of the recent delays that hit recently was completely unexpected: we had a hard drive failure on our build server. Up until recently, The aptly named “Poseidon” build server was running a Micron m500dc drive, but that drive is now constantly reporting errors. Despite ordering a replacement Western Digital Blue SSD several weeks ago, we just received it this past week. The drive is now installed with the builder back to full functionality, but we did lose many precious days with the delay. The build server for Project Trident is very similar to the one that JT donated to the TrueOS project. JT had another DL580 G7, so he donated one to the Trident Project for their build server. Poseidon also has 256GB RAM (64 x 4GB sticks) which is a smidge higher than what the TrueOS builder has. Since we are talking about hardware, we probably should address another question we get often, “What Hardware are the devs testing on?” So let’s go ahead and answer that one now. Developer Hardware JT: His main test box is a custom-built Intel i7 7700K system running 32GB RAM, dual Intel Optane 900P drives, and an Nvidia 1070 GTX with four 4K Acer Monitors. He also uses a Lenovo x250 ThinkPad alongside a desk full of x230t and x220 ThinkPads. One of which he gave away at SouthEast LinuxFest this year, which you can read about here. However it’s not done there, being a complete hardware hoarder, JT also tests on several Intel NUCs and his second laptop a Fujitsu t904, not to mention a Plethora of HP DL580 servers, a DL980 server, and a stack of BL485c, BL460c, and BL490c Blades in his HP c7000 and c3000 Bladecenter chassis. (Maybe it’s time for an intervention for his hardware collecting habits) Ken: For a laptop, he primarily uses a 3rd generation X1 Carbon, but also has an old Eee PC T101MT Netbook (dual core 1GHz, 2GB of memory) which he uses for verifying how well Trident works on low-end hardware. As far as workstations go, his office computer is an Intel i7 with an NVIDIA Geforce GTX 960 running three 4K monitors and he has a couple other custom-built workstations (1 AMD, 1 Intel+NVIDIA) at his home. Generally he assembled random workstations based on hardware that was given to him or that he could acquire cheap. Tim: is using a third gen X1 Carbon and a custom built desktop with an Intel Core i5-4440 CPU, 16 GiB RAM, Nvidia GeForce GTX 750 Ti, and a RealTek 8168 / 8111 network card. Rod: Rod uses… No one knows what Rod uses, It’s kinda like how many licks does it take to get to the center of a Tootsie-Roll Tootsie-Pop… the world may just never know. ###NetBSD GSoC: pkgsrc config file versioning A series of reports from the course of the summer on this Google Summer of Code project The goal of the project is to integrate with a VCS (Version Control System) to make managing local changes to config files for packages easier GSoC 2018 Reports: Configuration files versioning in pkgsrc, Part 1 Packages may install code (both machine executable code and interpreted programs), documentation and manual pages, source headers, shared libraries and other resources such as graphic elements, sounds, fonts, document templates, translations and configuration files, or a combination of them. Configuration files are usually the means through which the behaviour of software without a user interface is specified. This covers parts of the operating systems, network daemons and programs in general that don’t come with an interactive graphical or textual interface as the principal mean for setting options. System wide configuration for operating system software tends to be kept under /etc, while configuration for software installed via pkgsrc ends up under LOCALBASE/etc (e.g., /usr/pkg/etc). Software packaged as part of pkgsrc provides example configuration files, if any, which usually get extracted to LOCALBASE/share/examples/PKGBASE/. Don’t worry: automatic merging is disabled by default, set $VCSAUTOMERGE to enable it. In order to avoid breakage, installed configuration is backed up first in the VCS, separating user-modified files from files that have been already automatically merged in the past, in order to allow the administrator to easily restore the last manually edited file in case of breakage. VCS functionality only applies to configuration files, not to rc.d scripts, and only if the environment variable $NOVCS is unset. The version control system to be used as a backend can be set through $VCS. It default to RCS, the Revision Control System, which works only locally and doesn’t support atomic transactions. Other backends such as CVS are supported and more will come; these, being used at the explicit request of the administrator, need to be already installed and placed in a directory part of $PATH. GSoC 2018 Reports: Configuration files versioning in pkgsrc, part 2: remote repositories (git and CVS) pkgsrc is now able to deploy configuration from packages being installed from a remote, site-specific vcs repository. User modified files are always tracked even if automerge functionality is not enabled, and a new tool, pkgconftrack(1), exists to manually store user changes made outside of package upgrade time. Version Control software is executed as the same user running pkgadd or make install, unless the user is “root”. In this case, a separate, unprivileged user, pkgvcsconf, gets created with its own home directory and a working login shell (but no password). The home directory is not strictly necessary, it exists to facilitate migrations betweens repositories and vcs changes; it also serves to store keys used to access remote repositories. Using git instead of rcs is simply done by setting VCS=git in pkginstall.conf GSoC 2018 Reports: Configuration files versioning in pkgsrc, part 3: remote repositories (SVN and Mercurial) GSoC 2018 Reports: Configuration files versioning in pkgsrc, part 4: configuration deployment, pkgtools and future improvements Support for configuration tracking is in scripts, pkginstall scripts, that get built into binary packages and are run by pkgadd upon installation. The idea behind the proposal suggested that users of the new feature should be able to store revisions of their installed configuration files, and of package-provided default, both in local or remote repositories. With this capability in place, it doesn’t take much to make the scripts “pull” configuration from a VCS repository at installation time. That’s what setting VCSCONFPULL=yes in pkginstall.conf after having enabled VCSTRACKCONF does: You are free to use official, third party prebuilt packages that have no customization in them, enable these options, and point pkgsrc to a private conf repository. If it contains custom configuration for the software you are installing, an attempt will be made to use it and install it on your system. If it fails, pkginstall will fall back to using the defaults that come inside the package. RC scripts are always deployed from the binary package, if existing and PKGRCDSCRIPTS=yes in pkginstall.conf or the environment. This will be part of packages, not a separate solution like configuration management tools. It doesn’t support running scripts on the target system to customize the installation, it doesn’t come with its domain-specific language, it won’t run as a daemon or require remote logins to work. It’s quite limited in scope, but you can define a ROLE for your system in pkginstall.conf or in the environment, and pkgsrc will look for configuration you or your organization crafted for such a role (e.g., public, standalone webserver vs reverse proxy or node in a database cluster) ###A little bit of the one-time MacOS version still lingers in ZFS Once upon a time, Apple came very close to releasing ZFS as part of MacOS. Apple did this work in its own copy of the ZFS source base (as far as I know), but the people in Sun knew about it and it turns out that even today there is one little lingering sign of this hoped-for and perhaps prepared-for ZFS port in the ZFS source code. Well, sort of, because it’s not quite in code. Lurking in the function that reads ZFS directories to turn (ZFS) directory entries into the filesystem independent format that the kernel wants is the following comment: objnum = ZFSDIRENTOBJ(zap.zafirstinteger); / MacOS X can extract the object type here such as: * uint8t type = ZFSDIRENTTYPE(zap.zafirstinteger); */ Specifically, this is in zfsreaddir in zfsvnops.c . ZFS maintains file type information in directories. This information can’t be used on Solaris (and thus Illumos), where the overall kernel doesn’t have this in its filesystem independent directory entry format, but it could have been on MacOS (‘Darwin’), because MacOS is among the Unixes that support d_type. The comment itself dates all the way back to this 2007 commit, which includes the change ‘reserve bits in directory entry for file type’, which created the whole setup for this. I don’t know if this file type support was added specifically to help out Apple’s MacOS X port of ZFS, but it’s certainly possible, and in 2007 it seems likely that this port was at least on the minds of ZFS developers. It’s interesting but understandable that FreeBSD didn’t seem to have influenced them in the same way, at least as far as comments in the source code go; this file type support is equally useful for FreeBSD, and the FreeBSD ZFS port dates to 2007 too (per this announcement). Regardless of the exact reason that ZFS picked up maintaining file type information in directory entries, it’s quite useful for people on both FreeBSD and Linux that it does so. File type information is useful for any number of things and ZFS filesystems can (and do) provide this information on those Unixes, which helps make ZFS feel like a truly first class filesystem, one that supports all of the expected general system features. ##Beastie Bits Mac-like FreeBSD Laptop Syncthing on FreeBSD New ZFS Boot Environments Tool My system’s time was so wrong, that even ntpd didn’t work OpenSSH 7.8/7.8p1 (2018-08-24) EuroBSD (Sept 20-23rd) registration Early Bird Period is coming to an end MeetBSD (Oct 18-20th) is coming up fast, hurry up and register! AsiaBSDcon 2019 Dates ##Feedback/Questions Will - Kudos and a Question Peter - Fanless Computers Ron - ZFS disk clone or replace or something Bostjan - ZFS Record Size Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv
AsiaBSDcon review, Meltdown and Spectre Patches in FreeBSD stable, Interview with MidnightBSD founder, 8 months with TrueOS, mysteries of GNU and BSD split This episode was brought to you by Headlines AsiaBSDCon 2018 has concluded (https://2018.asiabsdcon.org/) We have just returned from AsiaBSDCon in Tokyo, Japan last weekend Please excuse our jetlag The conference consisted two days of meeting followed by 2 days of paper presentations We arrived a few days early to see some sights and take a few extra delicious meals in Tokyo The first day of meetings was a FreeBSD developer summit (while Benedict was teaching his two tutorials) where we discussed the FreeBSD release cycle and our thoughts on improving it, the new Casper capsicum helper service, and developments in SDIO which will eventually enable WiFi and SD card readers on more embedded devices The second day of meetings consisted of bhyvecon, a miniconf that covered development in all hypervisors on all BSDs. It also included presentations on the porting of bhyve to IllumOS. Then the conference started There were a number of great presentations, plus an amazing hallway track as usual It was great to see many old friends and to spend time discussing the latest happenings in BSD. A couple of people came by and asked to take a picture with us and we were happy to do that. *** FreeBSD releases Spectre and Meltdown mitigations for 11.1 (https://www.freebsd.org/security/advisories/FreeBSD-SA-18:03.speculative_execution.asc) Speculative execution vulnerability mitigation is a work in progress. This advisory addresses the most significant issues for FreeBSD 11.1 on amd64 CPUs. We expect to update this advisory to include 10.x for amd64 CPUs. Future FreeBSD releases will address this issue on i386 and other CPUs. freebsd-update will include changes on i386 as part of this update due to common code changes shared between amd64 and i386, however it contains no functional changes for i386 (in particular, it does not mitigate the issue on i386). Many modern processors have implementation issues that allow unprivileged attackers to bypass user-kernel or inter-process memory access restrictions by exploiting speculative execution and shared resources (for example, caches). An attacker may be able to read secret data from the kernel or from a process when executing untrusted code (for example, in a web browser). + Meltdown: The mitigation is known as Page Table Isolation (PTI). PTI largely separates kernel and user mode page tables, so that even during speculative execution most of the kernel's data is unmapped and not accessible. A demonstration of the Meltdown vulnerability is available at https://github.com/dag-erling/meltdown. A positive result is definitive (that is, the vulnerability exists with certainty). A negative result indicates either that the CPU is not affected, or that the test is not capable of demonstrating the issue on the CPU (and may need to be modified). A patched kernel will automatically enable PTI on Intel CPUs. The status can be checked via the vm.pmap.pti sysctl PTI introduces a performance regression. The observed performance loss is significant in microbenchmarks of system call overhead, but is much smaller for many real workloads. + Spectre V2: There are two common mitigations for Spectre V2. This patch includes a mitigation using Indirect Branch Restricted Speculation, a feature available via a microcode update from processor manufacturers. The alternate mitigation, Retpoline, is a feature available in newer compilers. The feasibility of applying Retpoline to stable branches and/or releases is under investigation. The patch includes the IBRS mitigation for Spectre V2. To use the mitigation the system must have an updated microcode; with older microcode a patched kernel will function without the mitigation. IBRS can be disabled via the hw.ibrsdisable sysctl (and tunable), and the status can be checked via the hw.ibrsactive sysctl. IBRS may be enabled or disabled at runtime. Additional detail on microcode updates will follow. + Wiki tracking the vulnerabilities and mitigations on different platforms (https://wiki.freebsd.org/SpeculativeExecutionVulnerabilities) Interview with MidnightBSD Founder and Lead Dev Lucas Holt (https://itsfoss.com/midnightbsd-founder-lucas-holt/) Recently, I have taken a little dip into the world of BSD. As part of my attempt to understand the BSD world a little better, I connected with Lucas Holt (MidnightBSD founder and lead developer) to ask him a few questions about his project. Here are his answers. It's FOSS: Please explain MidnightBSD in a nutshell. How is it different than other BSDs? Lucas Holt: MidnightBSD is a desktop focused operating system. When it's considered stable, it will provide a full desktop experience. This differs from other efforts such as TrueOS or GhostBSD in that it's not a distro of FreeBSD, but rather a fork. MidnightBSD has its own package manager, mport as well as unique package cluster software and several features built into user land such as mDNSresponder, libdispatch, and customizations throughout the system. It's FOSS: Who is MidnightBSD aimed at? Lucas Holt: The goal with MidnightBSD has always been to provide a desktop OS that's usable for everyday tasks and that even somewhat non technical people can use. Early versions of Mac OS X were certainly an inspiration. In practice, we're rather far from that goal at this point, but it's been an excellent learning opportunity. It's FOSS: What is your background in computers? Lucas Holt: I started in technical support at a small ISP and moved into web design and system administration. While there, I learned BSDi, Solaris and Linux. I also started tinkering with programming web apps in ASP and a little perl CGI. I then did a mix of programming and system administration jobs through college and graduated with a bachelors in C.S. from Eastern Michigan University. During that time, I learned NetBSD and FreeBSD. I started working on several projects such as porting Apple's HFS+ code to FreeBSD 6 and working on getting the nforce2 chipset SATA controller working with FreeBSD 6, with the latter getting committed. I got a real taste for BSD and after seeing the lack of interest in the community for desktop BSDs, I started MidnightBSD. I began work on it in late 2005. Currently, I'm a Senior Software Engineer focusing on backend rest services by day and a part-time graduate student at the University of Michigan Flint. It's FOSS: I recently installed TrueOS. I was disappointed that a couple of the programs I wanted were not available. The FreeBSD port system looked mildly complicated for beginners. I'm used to using pacman to get the job done quickly. How does MidnightBSD deal with ports? Lucas Holt: MidnightBSD has it's own port system, mports, which shared similarities with FreeBSD ports as well as some ideas from OpenBSD. We decided early on that decent package management was essential for regular users. Power users will still use ports for certain software, but it's just so time consuming to build everything. We started work on our own package manager, mport. Every package is a tar lzma archive with a sqlite3 manifest file as well as a sqlite 3 index that's downloaded from our server. This allows users to query and customize the package system with standard SQL queries. We're also building more user friendly graphical tools. Package availability is another issue that most BSDs have. Software tends to be written for one or two operating systems and many projects are reluctant to support other systems, particularly smaller projects like MidnightBSD. There are certainly gaps. All of the BSD projects need more volunteers to help with porting software and keeping it up to date. It's FOSS: During your June 2015 interview on BSDNow, you mentioned that even though you support both i386 and amd64, that you recommend people choose amd64. Do you have any plans to drop i386 support in the future, like many have done? Lucas Holt: Yes, we do plan to drop i386 support, mostly because of the extra work needed to build and maintain packages. I've held off on this so far because I had a lot of feedback from users in South America that they still needed it. For now, the plan is to keep i386 support through 1.0 release. That's probably a year or two out. It's FOSS: What desktop environments does MidnightBSD support? Lucas Holt: The original plan was to use Etoile as a desktop environment, but that project changed focus. We currently support Xfce, Gnome 3, WindowMaker + GNUstep + Gworkspace as primary choices. We also have several other window managers and desktop environments available such as Enlightenment, rat poison, afterstep, etc. Early versions offered KDE 3.x but we had some issues with KDE 4. We may revisit that with newer versions. It's FOSS: What is MidnightBSD's default filesystem? Do you support DragonflyBSD's HAMMER filesystem? What other filesystems? Lucas Holt: Boot volumes are UFS2. We also support ZFS for additional storage. We have read support for ExFat, NTFS, ext2, CD9660. NFS v3 and v4 are also supported for network file systems. We do not support HAMMER, although it was considered. I would love to see HAMMER2 get added to MidnightBSD eventually. It's FOSS: Is MidnightBSD affected by the recent Spectre and Meltdown issues? Lucas Holt: Yes. Most operating systems were affected by these issues. We were not informed of the issue until the general public became aware. Work is ongoing to come up with appropriate mitigations. Unfortunately, we do not have a patch yet. It's FOSS: The Raspberry Pi and its many clones have made the ARM platform very popular. Are there any plans to make MidnightBSD available on that platform? Lucas Holt: No immediate plans. ARM is an interesting architecture, but by the very nature of SoC designs, takes a lot of work to support a broad number of devices. It might be possible when we stop supporting i386 or if someone volunteers to work on the ARM port. Eventually, I think most hobby systems will need to run ARM chips. Intel's planning on locking down hardware with UEFI 3 and this may make it difficult to run on commodity hardware in the future not only for MidnightBSD but other systems as well. At one point, MidinightBSD ran on sparc64. When workstations were killed off, we dropped support. A desktop OS on a server platform makes little sense. It's FOSS: Does MidnightBSD offer support for Linux applications? Lucas Holt: Yes, we offer Linux emulation. It's emulating a 2.6.16 kernel currently and that needs to be updated so support newer apps. It's possible to run semi-recent versions of Firefox, Thunderbird, Java, and OpenOffice on it though. I've also used it to host game servers in the past and play older games such as Quake 3, enemy territory, etc. It's FOSS: Could you comment on the recent dust-up between the Pale Moon browser developers and the team behind the OpenBSD ports system? [Author's Note: For those who haven't heard about this, let me summarize. Last month, someone from the OpenBSD team added the Pale Moon browser to their ports collection. A Pale Moon developer demanded that they include Pale Moon's libraries instead of using system libraries. As the conversation continued, it got more hostile, especially on the Pale Moon side. The net result is that Pale Moon will not be available on OpenBSD, MidnightBSD, or FreeBSD.] Lucas Holt: I found this discussion frustrating. Many of the BSD projects hear a lot of complaints about browser availability and compatibility. With Firefox moving to Rust, it makes it even more difficult. Then you get into branding issues. Like Firefox, the Pale Moon developers have decided to protect their brand at the cost of users. Unlike the Firefox devs, they've made even stranger requirements for branding. It is not possible to use a system library version of anything with Pale Moon and keep their branding requirements. As such, we cannot offer Pale Moon in MidnightBSD. The reason this is an issue for an open source project is that many third party libraries are used in something as complex as a web browser. For instance, Gecko-based browsers use several multimedia libraries, sqlite3 (for bookmarks), audio and video codecs, etc. Trying to maintain upstream patches for each of these items is difficult. That's why the BSDs have ports collections to begin with. It allows us to track and manage custom patches to make all these libraries work. We go through a lot of effort in keeping these up to date. Sometimes upstream patches don't get included. That means our versions are the only working copies. With pale moon's policy, we'd need to submit separate patches to their customized versions of all these libraries too and any new release of the browser would not be available as changes occur. It might not even be possible to compile pale moon without a patch locally. With regard to Rust, it requires porting the language, as well as an appropriate version of LLVM before you can even start on the browser. It's FOSS: If someone wanted to contribute to your project, both financial and technical, how can they do that? Lucas Holt: Financial assistance for the project can be submitted online. We have a page outlining how to make donations with Patreon, Paypal or via bitcoin. Donations are not tax deductible. You can learn more at http://www.midnightbsd.org/donate/ We also need assistance with translations, porting applications, and working on the actual OS. Interested parties can contact us on the mailing list or through IRC on freenode #midnightbsd We also could use assistance with mirroring ISOs and packages. I would like to thank Lucas for taking the time to reply to my many questions. For more information about MidnightBSD or to download it, please visit their website. The most recent version of MidnightBSD is 0.8.6. News Roundup 8 months with TrueOS (https://inflo.ws/blog/post/2018-03-03-trueos-8th-month-review/) Purpose of this review - what it is and what it is not. I vowed to write down what I felt about TrueOS if I ever got to the six month mark of usage. This is just that. This is neither a tutorial, nor a piece of evangelism dedicated towards it. This is also not a review of specific parts of TrueOS such as Lumina or AppCafe, since I don't use them at all. In the spirit of presenting a screen shot, here is my i3wm displaying 4 windows in one screen - a configuration that I never use. https://inflo.ws/blog/images/trues-screenshot.png The primary tasks I get done with my computer. I need a tiling wm with multi-desktop capability. As regards what I do with a computer, it is fairly straightforward to describe if I just list down my most frequently used applications. xterm (CLI) Emacs (General editing and org mode) Intellij IDEA (Java, Kotlin, SQL) Firefox (Main web browser, with Multi-Account Containers) Thunderbird (Work e-mail) Notmuchmail (Personal e-mail) Chromium/Iridium (Dumb web browser) Telegram Desktop weechat (with wee-slack) cmus (Music player) mpv (Video player) mps-youtube (Youtube client) transmission-gtk Postgresql10 (daemon) Rabbitmq (daemon) Seafile (file sync) Shotwell (manage pictures) GIMP (Edit pictures) Calibre (Manage e-books) VirtualBox All of these are available as binary packages from the repository. Since I use Intellij Ultimate edition, I decided to download the no-jdk linux version from the website rather than install it. This would make sure that it gets updated regularly. Why did I pick TrueOS ? I ran various Linux distributions from 2001 all the way till 2009, till I discovered Arch, and continued with it till 2017. I tried out Void for two months before I switched to TrueOS. Over the last few years, I started feeling like no matter which Linux distribution I touched, they all just stopped making a lot of sense. Generally in the way things were organised, and particularly in terms of software like systemd, which just got pushed down my throat. I couldn't wrap my head around half the things going on in my computer. Mostly I found that Linux distributions stopped becoming a collection of applications that got developed together to something more coupled by software mechanisms like systemd - and that process was more and more opaque. I don't want to talk about the merits and de-merits of systemd, lets just say that I found it of no use and an unnecessary hassle. In February, I found myself in charge of the entire technology stack of a company, and I was free to make choices. A friend who was a long time FreeBSD user convinced me to try it on the servers. My requirement then was to run Postgres, Rabbitmq, Nginx and a couple of JVM processes. The setup was zero hassle and it hasn't changed much in a year. About three months of running FreeBSD-11.x on servers was enough for me to consider it for my laptop. I was very apprehensive of hardware support, but luckily my computer is a Thinkpad, and Thinkpads sort of work out of the box with various BSDs. My general requirements were: Must run Intellij IDEA. Must have proper graphics and sound driver support. Must be able to run VirtualBox. I had to pick from FreeBSD, NetBSD and OpenBSD, since these were the major BSDs that I was familiar with. One of my requirements was that I needed to be able to run VMs just in case I needed to test something on Windows/Linux. This ruled out OpenBSD. Then I was left with NetBSD and FreeBSD. NetBSD's driver support for newer Intel chip-sets were questionable, and FreeBSD was the only choice then. When I was digging through FreeBSD forums, I found out that running the 11.x RELEASE on my laptop was out of the question since it didn't have proper drivers for my chip-set either. A few more hours of digging led me to GhostBSD and TrueOS. I picked TrueOS straightaway because - well because TrueOS came from the old PC-BSD and it was built off FreeBSD-12-CURRENT with the latest drivers integrated. I downloaded the UNSTABLE version available in June 2017, backed up ALL my data and home directory, and then installed it. There were no glitches during installation - I simply followed the installation as described in the handbook and everything was fine. My entire switch from Arch/Void to TrueOS took about an hour, discounting the time it took to backup my data to an external hard disk. It was that easy. Everything I wanted to work just worked, everything was available in the repo. Tweaks from cooltrainer.org : I discovered this excellent tutorial that describes setting up a FreeBSD 11 desktop. It documents several useful tweaks, some of which I applied. A few examples - Fonts, VirtualBox, Firewall, UTF-8 sections. TrueOS (and FreeBSD) specific things I liked Open-rc The open-rc init system is familiar and is well documented. TrueOS specific parts are described here. When I installed postgresql10-server, there was no open-rc script for it, but I could cobble one together in two hours with zero prior experience writing init scripts. Later on I figured out that the init script for postgresql9 would work for 10 as well, and used that. Boot Environments This was an alien concept to me, but the first time I did an update without waiting for a CDN sync to finish, my computer booted into the shell and remained there. The friendly people at TrueOS discourse asked me to roll back to an older BE and wait for sync to finish. I dug through the forums and found "ZFS / Snapshots basics & How-To's for those new to TrueOS". This describes ZFS and BEs, and is well worth reading. ZFS My experience with boot environments was enough to convince me about the utility of ZFS. I am still reading about it and trying things out, and whatever I read just convinces me more about why it is good. File-system layout Coming from the Linux world, how the FreeBSD file-system is laid out seemed odd at first. Then I realised that it was the Linux distros that were doing the odd thing. e.g : The whole OS is split into base system and applications. All the non base system configurations and apps go into /usr/local. That made a lot of sense. The entire OS is developed along with its applications as a single coherent entity, and that shows. Documentation The handbooks for both TrueOS and FreeBSD are really really good. For e.g, I kept some files in an LUKS encrypted drive (when I used Arch Linux). To find an equivalent, all I had to do was read the handbook and look at the GELI section. It is actually nice being able to go to a source like Handbook and things from there just work. Arch Linux and Gentoo has excellent documentation as well, if anyone is wondering about Linux distros. Community The TrueOS community on both Telegram as well as on Discourse are very friendly and patient. They help out a lot and do not get upset when I pose really stupid questions. TrueOS core developers hangout in the Telegram chat-room too, and it is nice being able to talk to them directly about things. What did not work in TrueOS ? The following things that worked during my Linux tenure doesn't work in TrueOS. Netflix Google Hangouts Electron based applications (Slack, Skype) These are not major concerns for the kind of work I do, so it doesn't bother me much. I run a WinXP VM to play some old games, and a Bunsenlabs installation for Linux things like Hangouts/Netflix. I don't have a video calling system setup in TrueOS because I use my phone for both voice and video calls exclusively. Why am I staying on TrueOS ? Great community - whether on Discourse or on the telegram channel, the people make you feel welcome. If things go unanswered, someone will promise to work on it/file a bug/suggest work-arounds. Switching to TrueOS was philosophical as well - I thought a lot more about licenses, and I have arrived at the conclusion that I like BSD more than GPL. I believe it is a more practical license. I believe TrueOS is improving continuously, and is a great desktop UNIX if you put some time into it. AsiaBSDCon 2016 videos now available (https://www.youtube.com/playlist?list=PLnTFqpZk5ebD-FfVScL-x6ZnZSecMA1jI) The videos from AsiaBSDCon 2016 have been posted to youtube, 30 videos in all We'll cover the videos from 2017 next week The videos from 2018 should be posted in 4-6 weeks I are working on a new version of https://papers.freebsd.org/ that will make it easier to find the papers, slides, and videos of all talks related to FreeBSD *** syspatches will be provided for both supported releases (https://undeadly.org/cgi?action=article;sid=20180307234243) Good news for people doing upgrades only once per year: syspatches will be provided for both supported releases. The commit from T.J. Townsend (tj@) speaks for itself: ``` Subject: CVS: cvs.openbsd.org: www From: T.J. Townsend Date: 2018-03-06 22:09:12 CVSROOT: /cvs Module name: www Changes by: tj@cvs.openbsd.org 2018/03/06 15:09:12 Modified files: . : errata61.html stable.html faq : faq10.html Log message: syspatches will now be provided for both supported releases. ``` Thanks to all the developers involved in providing these! Update: An official announcement has been released: ``` I'm happy to announce that we are now able to provide two releases worth of syspatches on the amd64 and i386 platforms. The binary patches for 6.1 will hit the mirrors shortly, so you will be able to catch up with the errata on https://www.openbsd.org/errata61.html using the syspatch utility. People running amd64 will thus get the meltdown workaround. This means in particular that 6.2 will remain supported by syspatch when 6.3 comes out. Thanks to robert and ajacoutot for their amazing work on syspatch and for all their help. Thanks also to tj and the volunteers from #openbsd for their timely tests and of course to Theo for overseeing it all. ``` Exploring permutations and a mystery with BSD and GNU split filenames (https://www.lorainekv.com/permutations_split_and_gsplit/) Recently, I was playing around with the split command-line tool on Mac OS X, and I decided to chop a 4000-line file into 4000 separate single-line files. However, when I attempted to run split -l1, I ran into a funny error: split: too many files Curious to see if any splitting had occurred, I ran ls and sure enough, a huge list of filenames appeared, such as: xaa xab ... xzy xzz Now I could see why you'd run out of unique filenames - there are only 26 letters in the alphabet and these filenames were only three letters long. Also, they all seemed to begin with the letter "x". BSD split's filename defaults I checked the manual for split's defaults and confirmed what I was seeing: each file into which the file is split is named by the prefix followed by a lexically ordered suffix using suffix_length characters in the range 'a-z'. If -a is not specified, two letters are used as the suffix....with the prefix 'x' and with suffixes as above. Got it, so running split with the defaults for prefix name and suffix length will give me filenames that always start with the letter "x" followed by two-letter alphabetical permutations composed of a-z letters, with repeats allowed. I say "repeats allowed" because I noticed filenames such as xaa and xbb in the output. Side node: The reason why I say "permutations" rather than "combinations" is because letter order matters. For example, xab and xba are two distinct and legitimate filenames. Here's a nice explanation about the difference between permutations and combinations. Some permutation math So how many filenames can you get from the BSD split tool using the defaults? There are permutation formulas out there for repeating values and non-repeating values. Based on split's behavior, I wanted to use the repeating values formula: n^r where n equals the number of possible values (26 for a-z) and r equals the number of values (2, since there are only 2 letters after "x" in the filename). 26^2 = 676 So the total number of filename permutations allowed with BSD split's defaults should be 676. To double check, I ran ls | wc -l to get the total number of files in my split_test directory. The output was 677. If you subtract my original input file, input.txt, then you have 676, or the number of permutations split would allow before running out of filenames! Neat. But I still wanted my 4000 files. Moar permutations pls While 26^2 permutations doesn't support 4000 different filenames, I wondered if I could increase r to 3. Then, I'd have 17,576 different filename permutations to play with - more than enough. Earlier, I remembered the manual mentioning suffix length: -a suffixlength Use suffixlength letters to form the suffix of the file name. So I passed 3 in with the -a flag and guess what? I got my 4000 files! split -l1 -a3 input.txt ls | wc -l 4001 But that was a lot of work. It would be great if split would just handle these permutations and suffix lengths by default! In fact, I vaguely remember splitting large files into smaller ones with numerical filenames, which I prefer. I also remember not having to worry about suffixes in the past. But numerical filenames didn't seem to be an option with split installed on Mac OS X - there was no mention of it in the manual. Turns out that I was remembering GNU split from using the Debian OS two years ago, a different flavor of the split tool with different defaults and behaviors. Beastie Bits Michael Lucas is speaking at mug.org 10 April 2018 (https://blather.michaelwlucas.com/archives/3121) PkgsrcCon 2018 July 7+8 Berlin (http://pkgsrc.org/pkgsrcCon/2018/) Tint2 rocks (http://www.vincentdelft.be/post/post_20180310) Open Source Summit Europe 2018 Call for Proposals (https://www.freebsdfoundation.org/news-and-events/call-for-papers/open-source-summit-europe-2018-call-for-proposals/) Travel Grants for BSDCan 2018 (https://www.freebsdfoundation.org/blog/bsdcan-2018-travel-grant-application-now-open/) BSDCan 2018 FreeBSD Developers Summit Call for Proposals (https://www.freebsdfoundation.org/news-and-events/call-for-papers/bsdcan-2018-freebsd-developers-summit-call-for-proposals/) OpenBSD vmm(4) update, by Mike Larkin (https://www.openbsd.org/papers/asiabsdcon2018-vmm-slides.pdf) Feedback/Questions Morgan ZFS Install Question (http://dpaste.com/3NZN49P#wrap) Andre - Splitting ZFS Array, or not (http://dpaste.com/3V09BZ5#wrap) Jake - Python Projects (http://dpaste.com/2CY5MRE#wrap) Dave - Screen Sharing & Video Conference (http://dpaste.com/257WGCB#wrap) James - ZFS disk id switching (http://dpaste.com/3HAPZ90#wrap)
How the term open source was created, running FreeBSD on ThinkPad T530, Moving away from Windows, Unknown Giants, as well as OpenBSD and FreeDOS. This episode was brought to you by Headlines How I coined the term 'open source' (https://opensource.com/article/18/2/coining-term-open-source-software) In a few days, on February 3, the 20th anniversary of the introduction of the term "open source software" is upon us. As open source software grows in popularity and powers some of the most robust and important innovations of our time, we reflect on its rise to prominence. I am the originator of the term "open source software" and came up with it while executive director at Foresight Institute. Not a software developer like the rest, I thank Linux programmer Todd Anderson for supporting the term and proposing it to the group. This is my account of how I came up with it, how it was proposed, and the subsequent reactions. Of course, there are a number of accounts of the coining of the term, for example by Eric Raymond and Richard Stallman, yet this is mine, written on January 2, 2006. It has never been published, until today. The introduction of the term "open source software" was a deliberate effort to make this field of endeavor more understandable to newcomers and to business, which was viewed as necessary to its spread to a broader community of users. The problem with the main earlier label, "free software," was not its political connotations, but that—to newcomers—its seeming focus on price is distracting. A term was needed that focuses on the key issue of source code and that does not immediately confuse those new to the concept. The first term that came along at the right time and fulfilled these requirements was rapidly adopted: open source. This term had long been used in an "intelligence" (i.e., spying) context, but to my knowledge, use of the term with respect to software prior to 1998 has not been confirmed. The account below describes how the term open source software caught on and became the name of both an industry and a movement. Meetings on computer security In late 1997, weekly meetings were being held at Foresight Institute to discuss computer security. Foresight is a nonprofit think tank focused on nanotechnology and artificial intelligence, and software security is regarded as central to the reliability and security of both. We had identified free software as a promising approach to improving software security and reliability and were looking for ways to promote it. Interest in free software was starting to grow outside the programming community, and it was increasingly clear that an opportunity was coming to change the world. However, just how to do this was unclear, and we were groping for strategies. At these meetings, we discussed the need for a new term due to the confusion factor. The argument was as follows: those new to the term "free software" assume it is referring to the price. Oldtimers must then launch into an explanation, usually given as follows: "We mean free as in freedom, not free as in beer." At this point, a discussion on software has turned into one about the price of an alcoholic beverage. The problem was not that explaining the meaning is impossible—the problem was that the name for an important idea should not be so confusing to newcomers. A clearer term was needed. No political issues were raised regarding the free software term; the issue was its lack of clarity to those new to the concept. Releasing Netscape On February 2, 1998, Eric Raymond arrived on a visit to work with Netscape on the plan to release the browser code under a free-software-style license. We held a meeting that night at Foresight's office in Los Altos to strategize and refine our message. In addition to Eric and me, active participants included Brian Behlendorf, Michael Tiemann, Todd Anderson, Mark S. Miller, and Ka-Ping Yee. But at that meeting, the field was still described as free software or, by Brian, "source code available" software. While in town, Eric used Foresight as a base of operations. At one point during his visit, he was called to the phone to talk with a couple of Netscape legal and/or marketing staff. When he was finished, I asked to be put on the phone with them—one man and one woman, perhaps Mitchell Baker—so I could bring up the need for a new term. They agreed in principle immediately, but no specific term was agreed upon. Between meetings that week, I was still focused on the need for a better name and came up with the term "open source software." While not ideal, it struck me as good enough. I ran it by at least four others: Eric Drexler, Mark Miller, and Todd Anderson liked it, while a friend in marketing and public relations felt the term "open" had been overused and abused and believed we could do better. He was right in theory; however, I didn't have a better idea, so I thought I would try to go ahead and introduce it. In hindsight, I should have simply proposed it to Eric Raymond, but I didn't know him well at the time, so I took an indirect strategy instead. Todd had agreed strongly about the need for a new term and offered to assist in getting the term introduced. This was helpful because, as a non-programmer, my influence within the free software community was weak. My work in nanotechnology education at Foresight was a plus, but not enough for me to be taken very seriously on free software questions. As a Linux programmer, Todd would be listened to more closely. The key meeting Later that week, on February 5, 1998, a group was assembled at VA Research to brainstorm on strategy. Attending—in addition to Eric Raymond, Todd, and me—were Larry Augustin, Sam Ockman, and attending by phone, Jon "maddog" Hall. The primary topic was promotion strategy, especially which companies to approach. I said little, but was looking for an opportunity to introduce the proposed term. I felt that it wouldn't work for me to just blurt out, "All you technical people should start using my new term." Most of those attending didn't know me, and for all I knew, they might not even agree that a new term was greatly needed, or even somewhat desirable. Fortunately, Todd was on the ball. Instead of making an assertion that the community should use this specific new term, he did something less directive—a smart thing to do with this community of strong-willed individuals. He simply used the term in a sentence on another topic—just dropped it into the conversation to see what happened. I went on alert, hoping for a response, but there was none at first. The discussion continued on the original topic. It seemed only he and I had noticed the usage. Not so—memetic evolution was in action. A few minutes later, one of the others used the term, evidently without noticing, still discussing a topic other than terminology. Todd and I looked at each other out of the corners of our eyes to check: yes, we had both noticed what happened. I was excited—it might work! But I kept quiet: I still had low status in this group. Probably some were wondering why Eric had invited me at all. Toward the end of the meeting, the question of terminology was brought up explicitly, probably by Todd or Eric. Maddog mentioned "freely distributable" as an earlier term, and "cooperatively developed" as a newer term. Eric listed "free software," "open source," and "sourceware" as the main options. Todd advocated the "open source" model, and Eric endorsed this. I didn't say much, letting Todd and Eric pull the (loose, informal) consensus together around the open source name. It was clear that to most of those at the meeting, the name change was not the most important thing discussed there; a relatively minor issue. Only about 10% of my notes from this meeting are on the terminology question. But I was elated. These were some key leaders in the community, and they liked the new name, or at least didn't object. This was a very good sign. There was probably not much more I could do to help; Eric Raymond was far better positioned to spread the new meme, and he did. Bruce Perens signed on to the effort immediately, helping set up Opensource.org and playing a key role in spreading the new term. For the name to succeed, it was necessary, or at least highly desirable, that Tim O'Reilly agree and actively use it in his many projects on behalf of the community. Also helpful would be use of the term in the upcoming official release of the Netscape Navigator code. By late February, both O'Reilly & Associates and Netscape had started to use the term. Getting the name out After this, there was a period during which the term was promoted by Eric Raymond to the media, by Tim O'Reilly to business, and by both to the programming community. It seemed to spread very quickly. On April 7, 1998, Tim O'Reilly held a meeting of key leaders in the field. Announced in advance as the first "Freeware Summit," by April 14 it was referred to as the first "Open Source Summit." These months were extremely exciting for open source. Every week, it seemed, a new company announced plans to participate. Reading Slashdot became a necessity, even for those like me who were only peripherally involved. I strongly believe that the new term was helpful in enabling this rapid spread into business, which then enabled wider use by the public. A quick Google search indicates that "open source" appears more often than "free software," but there still is substantial use of the free software term, which remains useful and should be included when communicating with audiences who prefer it. A happy twinge When an early account of the terminology change written by Eric Raymond was posted on the Open Source Initiative website, I was listed as being at the VA brainstorming meeting, but not as the originator of the term. This was my own fault; I had neglected to tell Eric the details. My impulse was to let it pass and stay in the background, but Todd felt otherwise. He suggested to me that one day I would be glad to be known as the person who coined the name "open source software." He explained the situation to Eric, who promptly updated his site. Coming up with a phrase is a small contribution, but I admit to being grateful to those who remember to credit me with it. Every time I hear it, which is very often now, it gives me a little happy twinge. The big credit for persuading the community goes to Eric Raymond and Tim O'Reilly, who made it happen. Thanks to them for crediting me, and to Todd Anderson for his role throughout. The above is not a complete account of open source history; apologies to the many key players whose names do not appear. Those seeking a more complete account should refer to the links in this article and elsewhere on the net. FreeBSD on a Laptop - A guide to a fully functional installation of FreeBSD on a ThinkPad T530 (https://www.c0ffee.net/blog/freebsd-on-a-laptop) As I stated my previous post, I recently dug up my old ThinkPad T530 after the embarrassing stream of OS X security bugs this month. Although this ThinkPad ran Gentoo faithfully during my time in graduate school at Clemson, these days I'd much rather spend time my wife and baby than fighting with emerge and USE flags. FreeBSD has always been my OS of choice, and laptop support seems to be much better than it was a few years ago. In this guide, I'll show you the tweaks I made to wrestle FreeBSD into a decent experience on a laptop. Unlike my usual posts, this time I'm going to assume you're already pretty familiar with FreeBSD. If you're a layman looking for your first BSD-based desktop, I highly recommend checking out TrueOS (previously PC-BSD): they've basically taken FreeBSD and packaged it with all the latest drivers, along with a user-friendly installer and custom desktop environment out of the box. TrueOS is an awesome project–the only reason I don't use it is because I'm old, grumpy, and persnickety about having my operating system just so. Anyway, if you'd still like to take the plunge, read on. Keep in mind, I'm using a ThinkPad T530, but other ThinkPads of the same generation should be similarly compatible. Here's what you'll get: Decent battery life (8-9 hours with a new 9-cell battery) UEFI boot and full-disk encryption WiFi (Intel Ultimate-N 6300) Ethernet (Intel PRO/1000) Screen brightness adjustment Suspend/Resume on lid close (make sure to disable TPM in BIOS) Audio (Realtek ALC269 HDA, speakers and headphone jack) Keyboard multimedia buttons Touchpad/Trackpoint Graphics Acceleration (with integrated Intel graphics, NVIDIA card disabled in BIOS) What I haven't tested yet: Bluetooth Webcam Fingerprint reader SD Card slot Installation Power Saving Tweaks for Desktop Use X11 Fonts Login Manager: SLiM Desktop Environment: i3 Applications The LLVM Sanitizers stage accomplished (https://blog.netbsd.org/tnf/entry/the_llvm_sanitizers_stage_accomplished) I've managed to get the Memory Sanitizer to work for the elementary base system utilities, like ps(1), awk(1) and ksh(1). This means that the toolchain is ready for tests and improvements. I've iterated over the basesystem utilities and I looked for bugs, both in programs and in sanitizers. The number of detected bugs in the userland programs was low, there merely was one reading of an uninitialized variable in ps(1). A prebuilt LLVM toolchain I've prepared a prebuilt toolchain with Clang, LLVM, LLDB and compiler-rt for NetBSD/amd64. I prepared the toolchain on 8.99.12, however I have received reports that it works on other older releases. Link: llvm-clang-compilerrt-lldb-7.0.0beta_2018-01-24.tar.bz2 The archive has to be untarballed to /usr/local (however it might work to some extent in other paths). This toolchain contains a prebuilt tree of the LLVM projects from a snapshot of 7.0.0(svn). It is a pristine snapshot of HEAD with patches from pkgsrc-wip for llvm, clang, compiler-rt and lldb. Sanitizers Notable changes in sanitizers, all of them are in the context of NetBSD support. Added fstat(2) MSan interceptor. Support for kvm(3) interceptors in the common sanitizer code. Added devname(3) and devname_r(3) interceptors to the common sanitizer code. Added sysctl(3) familty of functions interceptors in the common sanitizer code. Added strlcpy(3)/strlcat(3) interceptors in the common sanitizer code. Added getgrouplist(3)/getgroupmembership(3) interceptors in the common sanitizer code. Correct ctype(3) interceptors in a code using Native Language Support. Correct tzset(3) interceptor in MSan. Correct localtime(3) interceptor in the common sanitizer code. Added paccept(2) interceptor to the common sanitizer code. Added access(2) and faccessat(2) interceptors to the common sanitizer code. Added acct(2) interceptor to the common sanitizer code. Added accept4(2) interceptor to the common sanitizer code. Added fgetln(3) interceptor to the common sanitizer code. Added interceptors for the pwcache(3)-style functions in the common sanitizer code. Added interceptors for the getprotoent(3)-style functions in the common sanitizer code. Added interceptors for the getnetent(3)-style functions in the common sanitizer code. Added interceptors for the fts(3)-style functions in the common sanitizer code. Added lstat(3) interceptor in MSan. Added strftime(3) interceptor in the common sanitizer code. Added strmode(3) interceptor in the common sanitizer code. Added interceptors for the regex(3)-style functions in the common sanitizer code. Disabled unwanted interceptor __sigsetjmp in TSan. Base system changes I've tidied up inclusion of the internal namespace.h header in libc. This has hidden the usage of public global symbol names of: strlcat -> _strlcat sysconf -> __sysconf closedir -> _closedir fparseln -> _fparseln kill -> _kill mkstemp -> _mkstemp reallocarr -> _reallocarr strcasecmp -> _strcasecmp strncasecmp -> _strncasecmp strptime -> _strptime strtok_r -> _strtok_r sysctl -> _sysctl dlopen -> __dlopen dlclose -> __dlclose dlsym -> __dlsym strlcpy -> _strlcpy fdopen -> _fdopen mmap -> _mmap strdup -> _strdup The purpose of these changes was to stop triggering interceptors recursively. Such interceptors lead to sanitization of internals of unprepared (not recompiled with sanitizers) prebuilt code. It's not trivial to sanitize libc's internals and the sanitizers are not designed to do so. This means that they are not a full replacement of Valgrind-like software, but a a supplement in the developer toolbox. Valgrind translates native code to a bytecode virtual machine, while sanitizers are designed to work with interceptors inside the pristine elementary libraries (libc, libm, librt, libpthread) and embed functionality into the executable's code. I've also reverted the vadvise(2) syscall removal, from the previous month. This caused a regression in legacy code recompiled against still supported compat layers. Newly compiled code will use a libc's stub of vadvise(2). I've also prepared a patch installing dedicated headers for sanitizers along with the base system GCC. It's still discussed and should land the sources soon. Future directions and goals Possible paths in random order: In the quartet of UBSan (Undefined Behavior Sanitizer), ASan (Address Sanitizer), TSan (Thread Sanitizer), MSan (Memory Sanitizer) we need to add the fifth basic sanitizer: LSan (Leak Sanitizer). The Leak Sanitizer (detector of memory leaks) demands a stable ptrace(2) interface for processes with multiple threads (unless we want to build a custom kernel interface). Integrate the sanitizers with the userland framework in order to ship with the native toolchain to users. Port sanitizers from LLVM to GCC. Allow to sanitize programs linked against userland libraries other than libc, librt, libm and libpthread; by a global option (like MKSANITIZER) producing a userland that is partially prebuilt with a desired sanitizer. This is required to run e.g. MSanitized programs against editline(3). So far, there is no Operating System distribution in existence with a native integration with sanitizers. There are 3rd party scripts for certain OSes to build a stack of software dependencies in order to validate a piece of software. Execute ATF tests with the userland rebuilt with supported flavors of sanitizers and catch regressions. Finish porting of modern linkers designed for large C++ software, such as GNU GOLD and LLVM LLD. Today the bottleneck with building the LLVM toolchain is a suboptimal linker GNU ld(1). I've decided to not open new battlefields and return now to porting LLDB and fixing ptrace(2). Plan for the next milestone Keep upstreaming a pile of local compiler-rt patches. Restore the LLDB support for traced programs with a single thread. Interview - Goran Mekic - meka@tilda.center (mailto:meka@tilda.center) / @meka_floss (https://twitter.com/meka_floss) CBSD website (https://bsdstore.ru) Jail and VM Manager *** News Roundup Finally Moving Away From Windows (https://www.manios.ca/blog/2018/01/finally-moving-away-from-windows/) Broken Window Thanks to a combination of some really impressive malware, bad clicking, and poor website choices, I had to blow away my Windows 10 installation. Not that it was Window's fault, but a piece of malware had infected my computer when I tried to download a long lost driver for an even longer lost RAID card for a server. A word of advice – the download you're looking for is never on an ad-infested forum in another language. In any case, I had been meaning to switch away from Windows soon. I didn't have my entire plan ready, but now was as good a time as any. My line of work requires me to maintain some form of Windows installation, so I decided to keep it in a VM rather than dual booting as I was developing code and not running any high-end visual stuff like games. My first thought was to install Arch or Gentoo Linux, but the last time I attempted a Gentoo installation it left me bootless. Not that there is anything wrong with Gentoo, it was probably my fault, but I like the idea of some sort of installer so I looked at rock-solid Debian. My dad had installed Debian on his sweet new cutting-edge Lenovo laptop he received recently from work. He often raves about his cool scripts and much more effective customized experience, but often complains about his hybrid GPU support as he has an Intel/Nvidia hybrid display adapter (he has finally resolved it and now boasts his 6 connected displays). I didn't want to install Windows again, but something didn't feel right about installing some flavour of Linux. Back at home I have a small collection of FreeBSD servers running in all sorts of jails and other physical hardware, with the exception of one Debian server which I had the hardest time dealing with (it would be FreeBSD too if 802.11ac support was there as it is acting as my WiFi/gateway/IDS/IPS). I loved my FreeBSD servers, and yes I will write posts about each one soon enough. I wanted that cleanliness and familiarity on my desktop as well (I really love the ports collection!). It's settled – I will run FreeBSD on my laptop. This also created a new rivalry with my father, which is not a bad thing either. Playing Devil's Advocate The first thing I needed to do was backup my Windows data. This was easy enough, just run a Windows Image Backup and it will- wait, what? Why isn't this working? I didn't want to fiddle with this too long because I didn't actually need an image just the data. I ended up just copying over the files to an external hard disk. Once that was done, I downloaded and verified the latest FreeBSD 11.1 RELEASE memstick image and flashed it to my trusty 8GB Verbatim USB stick. I've had this thing since 2007, it works great for being my re-writable “CD”. I booted it up and started the installation. I knew this installer pretty well as I had test-installed FreeBSD and OpenBSD in VMs when I was researching a Unix style replacement OS last year. In any case, I left most of the defaults (I didn't want to play with custom kernels right now) and I selected all packages. This downloaded them from the FreeBSD FTP server as I only had the memstick image. The installer finished and I was off to my first boot. Great! so far so good. FreeBSD loaded up and I did a ‘pkg upgrade' just to make sure that everything was up to date. Alright, time to get down to business. I needed nano. I just can't use vi, or just not yet. I don't care about being a vi-wizard, that's just too much effort for me. Anyway, just a ‘pkg install nano' and I had my editor. Next was obvious, I needed x11. XFCE was common, and there were plenty of tutorials out there. I wont bore you with those details, but it went something like ‘pkg install xfce' and I got all the dependencies. Don't forget to install SLiM to make it seamless. There are some configs in the .login I think. SLiM needs to be called once the boot drops you to the login so that you get SLiM's nice GUI login instead of the CLI login screen. Then SLiM passes you off to XFCE. I think I followed this and this. Awesome. Now that x11 is working, it's time to get all of my apps from Windows. Obviously, I can't get everything (ie. Visual Studio, Office). But in my Windows installation, I had chosen many open-source or cross-compiled apps as they either worked better or so that I was ready to move away from Windows at a moments notice. ‘pkg install firefox thunderbird hexchat pidgin gpa keepass owncloud-client transmission-qt5 veracrypt openvpn' were some immediate picks. There are a lot more that I downloaded later, but these are a few I use everyday. My laptop also has the same hybrid display adapter config that my dad's has, but I chose to only run Intel graphics, so dual screens are no problem for me. I'll add Nvidia support later, but it's not a priority. After I had imported my private keys and loaded my firefox and thunderbird settings, I wanted to get my Windows VM running right away as I was burning productive days at work fiddling with this. I had only two virtualisation options; qemu/kvm and bhyve. qemu/kvm wasn't available in pkg, and looked real dirty to compile, from FreeBSD's point of view. My dad is using qemu/kvm with virt-manager to manage all of his Windows/Unix VMs alike. I wanted that experience, but I also wanted packages that could be updated and I didn't want to mess up a compile. bhyve was a better choice. It was built-in, it was more compatible with Windows (from what I read), and this is a great step-by-step article for Windows 10 on FreeBSD 11 bhyve! I had already tried to get virt-manager to work with bhyve with no luck. I don't think libvirt connects with bhyve completely, or maybe my config is wrong. But I didn't have time to fiddle with it. I managed it all through command lines and that has worked perfectly so far. Well sorta, there was an issue installing SQL Server, and only SQL Server, on my Windows VM. This was due to a missing ‘sectorsize=512' setting on the disk parameter on the bhyve command line. That was only found after A LOT of digging because the SQL Server install didn't log the error properly. I eventually found out that SQL Server only likes one sector size of disks for the install and my virtual disk geometry was incorrect. Apps Apps Apps I installed Windows 10 on my bhyve VM and I got that all setup with the apps I needed for work. Mostly Office, Visual Studio, and vSphere for managing our server farm. Plus all of the annoying 3rd party VPN software (I'm looking at you Dell and Cisco). Alright, with the Windows VM done, I can now work at work and finish FreeBSD mostly during the nights. I still needed my remote files (I setup an ownCloud instance on a FreeNAS jail at home) so I setup the client. Now, normally on Windows I would come to work and connect to my home network using OpenVPN (again, I have a OpenVPN FreeNAS jail at home) and the ownCloud desktop would be able to handle changing DNS destination IPs Not on FreeBSD (and Linux too?). I ended up just configuring the ownCloud client to just connect to the home LAN IP for the ownCloud server and always connecting the OpenVPN to sync things. It kinda sucks, but at least it works. I left that running at home overnight to get a full sync (~130GB cloud sync, another reason I use it over Google or Microsoft). Once that was done I moved onto the fstab as I had another 1TB SSD in my laptop with other files. I messed around with fstab and my NFS shares to my FreeNAS at home, but took them out as they made the boot time so long when I wasn't at home. I would only mount them when my OpenVPN connected or manually. I really wanted to install SpaceFM, but it's only available as a package on Debian and their non-package install script doesn't work on FreeBSD (packages are named differently). I tried doing it manually, but it was too much work. As my dad was the one who introduced me to it, he still uses it as a use-case for his Debian setup. Instead I kept to the original PCManFM and it works just fine. I also loaded up my Bitcoin and Litecoin wallets and pointed them to the blockchain that I has used on Windows after their sync, they loaded perfectly and my balances were there. I kinda wish there was the Bitcoin-ABC full node Bitcoin Cash wallet package on FreeBSD, but I'm sure it will come out later. The rest is essentially just tweaks and making the environment more comfortable for me, and with most programs installed as packages I feel a lot better with upgrades and audit checking (‘pkg audit -F' is really helpful!). I will always hate Python, actually, I will always hate any app that has it's own package manager. I do miss the GUI GitHub tool on Windows. It was a really good-looking way to view all of my repos. The last thing (which is increasing it's priority every time I go to a social media site or YouTube) is fonts. My god I never thought it was such a problem, and UTF support is complicated. If anyone knows how to get all UTF characters to show up, please let me know. I'd really like Wikipedia articles to load perfectly (I followed this post and there are still some missing). There are some extra tweaks I followed here and here. Conclusion I successfully migrated from Windows 10 to FreeBSD 11.1 with minimal consequence. Shout out goes to the entire FreeBSD community. So many helpful people in there, and the forums are a great place to find tons of information. Also thanks to the ones who wrote the how-to articles I've referenced. I never would have gotten bhyve to work and I'd still probably be messing with my X config without them. I guess my take home from this is to not be afraid to make changes that may change how comfortable I am in an environment. I'm always open to comments and questions, please feel free to make them below. I purposefully didn't include too many technical things or commands in this article as I wanted to focus on the larger picture of the migration as a whole not the struggles of xorg.conf, but if you would like to see some of the configs or commands I used, let me know and I'll include some! TrueOS Rules of Conduct (https://www.trueos.org/rulesofconduct/) We believe code is truly agnostic and embrace inclusiveness regardless of a person's individual beliefs. As such we only ask the following when participating in TrueOS public events and digital forums: Treat each other with respect and professionalism. Leave personal and TrueOS unrelated conversations to other channels. In other words, it's all about the code. Users who feel the above rules have been violated in some way can register a complaint with abuse@trueos.org + Shorter than the BSD License (https://twitter.com/trueos/status/965994363070353413) + Positive response from the community (https://twitter.com/freebsdbytes/status/966567686015782912) I really like the @TrueOS Code of Conduct, unlike some other CoCs. It's short, clear and covers everything. Most #OpenSource projects are labour of love. Why do you need a something that reads like a legal contract? FreeBSD: The Unknown Giant (https://neomoevius.tumblr.com/post/171108458234/freebsd-the-unknown-giant) I decided to write this article as a gratitude for the recent fast answer of the FreeBSD/TrueOS community with my questions and doubts. I am impressed how fast and how they tried to help me about this operating system which I used in the past(2000-2007) but recently in 2017 I began to use it again. + A lot has changed in 10 years I was looking around the internet, trying to do some research about recent information about FreeBSD and other versions or an easy to use spins like PCBSD (now TrueOS) I used to be Windows/Mac user for so many years until 2014 when I decided to use Linux as my desktop OS just because I wanted to use something different. I always wanted to use unix or a unix-like operating system, nowadays my main objective is to learn more about these operating systems (Debian Linux, TrueOS or FreeBSD). FreeBSD has similarities with Linux, with two major differences in scope and licensing: FreeBSD maintains a complete operating system, i.e. the project delivers kernel, device drivers, userland utilities and documentation, as opposed to Linux delivering a kernel and drivers only and relying on third-parties for system software; and FreeBSD source code is generally released under a permissive BSD license as opposed to the copyleft GPL used by Linux.“ But why do I call FreeBSD “The Unknown Giant”?, because the code base of this operating system has been used by other companies to develop their own operating system for products like computers or also game consoles. + FreeBSD is used for storage appliances, firewalls, email scanners, network scanners, network security appliances, load balancers, video servers, and more So many people now will learn that not only “linux is everywhere” but also that “FreeBSD is everywhere too” By the way speaking about movies, Do you remember the movie “The Matrix”? FreeBSD was used to make the movie: “The photo-realistic surroundings generated by this method were incorporated into the bullet time scene, and linear interpolation filled in any gaps of the still images to produce a fluent dynamic motion; the computer-generated “lead in” and “lead out” slides were filled in between frames in sequence to get an illusion of orbiting the scene. Manex Visual Effects used a cluster farm running the Unix-like operating system FreeBSD to render many of the film's visual effects” + FreeBSD Press Release re: The Matrix (https://www.freebsd.org/news/press-rel-1.html) I hope that I gave a good reference, information and now so many people can understand why I am going to use just Debian Linux and FreeBSD(TrueOS) to do so many different stuff (music, 3d animation, video editing and text editing) instead use a Mac or Windows. + FreeBSD really is the unknown giant. OpenBSD and FreeDOS vs the hell in earth (https://steemit.com/openbsd/@npna/openbsd-and-freedos-vs-the-hell-in-earth) Yes sir, yes. Our family, composed until now by OpenBSD, Alpine Linux and Docker is rapidly growing. And yes, sir. Yes. All together we're fighting against your best friends, the infamous, the ugliest, the worst...the dudes called the privacy cannibals. Do you know what i mean, sure? We're working hard, no matter what time is it, no matter in what part in the world we are, no matter if we've no money. We perfectly know that you cannot do nothing against the true. And we're doing our best to expand our true, our doors are opened to all the good guys, there's a lot here but their brain was fucked by your shit tv, your fake news, your laws, etc etc etc. We're alive, we're here to fight against you. Tonight, yes it's a Friday night and we're working, we're ready to welcome with open arms an old guy, his experience will give us more power. Welcome to: FreeDOS But why we want to build a bootable usb stick with FreeDOS under our strong OpenBSD? The answer is as usual to fight against the privacy cannibals! More than one decade ago the old BIOS was silently replaced by the more capable and advanced UEFI, this is absolutely normal because of the pass of the years and exponencial grow of the power of our personal computers. UEFI is a complex system, it's like a standalone system operative with direct access to every component of our (yes, it's our not your!) machine. But...wait a moment...do you know how to use it? Do you ever know that it exist? And one more thing, it's secure? The answer to this question is totally insane, no, it's not secure. The idea is good, the company that started in theory is one of the most important in IT, it's Intel. The history is very large and obviously we're going to go very deep in it, but trust me UEFI and the various friend of him, like ME, TPM are insecure and closed source! Like the hell in earth. A FreeDOS bootable usb image under OpenBSD But let's start preparing our OpenBSD to put order in this chaos: $ mkdir -p freedos/stuff $ cd freedos/stuff $ wget https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/fdboot.img $ wget https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/sys/sys-freedos-linux/sys-freedos-linux.zip $ wget https://download.lenovo.com/consumer/desktop/o35jy19usa_y900.exe $ wget http://145.130.102.57/domoticx/software/amiflasher/AFUDOS%20Flasher%205.05.04.7z Explanation in clear language as usual: create two directory, download the minimal boot disc image of FreeDOS, download Syslinux assembler MBR bootloaders, download the last Windows only UEFI update from Lenovo and download the relative unknown utility from AMI to flash our motherboard UEFI chipset. Go ahead: $ doas pkg_add -U nasm unzip dosfstools cabextract p7zip nasm the Netwide Assembler, a portable 80x86 assembler. unzip list, test and extract compressed files in a ZIP archive. dosfstoolsa collections of utilities to manipulate MS-DOSfs. cabextract program to extract files from cabinet. p7zipcollection of utilities to manipulate 7zip archives. $ mkdir sys-freedos-linux && cd sys-freedos-linux $ unzip ../sys-freedos-linux.zip $ cd ~/freedos && mkdir old new $ dd if=/dev/null of=freedos.img bs=1024 seek=20480 $ mkfs.fat freedos.img Create another working directory, cd into it, unzip the archive that we've downloaded, return to the working root and create another twos directories. dd is one of the most important utilities in the unix world to manipulate at byte level input and output: The dd utility copies the standard input to the standard output, applying any specified conversions. Input data is read and written in 512-byte blocks. If input reads are short, input from multiple reads are aggregated to form the output block. When finished, dd displays the number of complete and partial input and output blocks and truncated input records to the standard error output. We're creating here a virtual disk with bs=1024 we're setting both input and output block to 1024bytes; with seek=20480 we require 20480bytes. This is the result: -rw-r--r-- 1 taglio taglio 20971520 Feb 3 00:11 freedos.img. Next we format the virtual disk using the MS-DOS filesystem. Go ahead: $ doas su $ perl stuff/sys-freedos-linux/sys-freedos.pl --disk=freedos.img $ vnconfig vnd0 stuff/fdboot.img $ vnconfig vnd1 freedos.img $ mount -t msdos /dev/vnd0c old/ $ mount -t msdos /dev/vnd1c new/ We use the perl utility from syslinux to write the MBR of our virtual disk freedos.img. Next we create to loop virtual node using the OpenBSD utility vnconfig. Take care here because it is quite different from Linux, but as usual is clear and simple. The virtual nodes are associated to the downloaded fdboot.img and the newly created freedos.img. Next we mount the two virtual nodes cpartitions; in OpenBSD cpartition describes the entire physical disk. Quite different from Linux, take care. $ cp -R old/* new/ $ cd stuff $ mkdir o35jy19usa $ cabextract -d o35jy19usa o35jy19usa_y900.exe $ doas su $ cp o35jy19usa/ ../new/ $ mkdir afudos && cd afudos $ 7z e ../AFUDOS* $ doas su $ cp AFUDOS.exe ../../new/ $ umount ~/freedos/old/ && umount ~/freedos/new/ $ vnconfig -u vnd1 && vnconfig -u vnd0 Copy all files and directories in the new virtual node partition, extract the Lenovo cabinet in a new directory, copy the result in our new image, extract the afudos utility and like the others copy it. Umount the partitions and destroy the loop vnode. Beastie Bits NetBSD - A modern operating system for your retro battlestation (https://www.geeklan.co.uk/files/fosdem2018-retro) FOSDEM OS distribution (https://twitter.com/pvaneynd/status/960181163578019840/photo/1) Update on two pledge-related changes (https://marc.info/?l=openbsd-tech&m=151268831628549) *execpromises (https://marc.info/?l=openbsd-cvs&m=151304116010721&w=2) Slides for (BSD from scratch - from source to OS with ease on NetBSD) (https://www.geeklan.co.uk/files/fosdem2018-bsd/) Goobyte LastPass: You're fired! (https://blog.crashed.org/goodbye-lastpass/) *** Feedback/Questions Scott - ZFS Mirror with SLOG (http://dpaste.com/22Z8C6Z#wrap) Troels - Question about compressed ARC (http://dpaste.com/3X2R1BV#wrap) Jeff - FreeBSD Desktop DNS (http://dpaste.com/2BQ9HFB#wrap) Jonathon - Bhyve and gpu passthrough (http://dpaste.com/0TTT0DB#wrap) ***
Back from their globe-trotting adventures in Tokyo, Las Vegas, and Greenville, S.C., Matt and Rich discuss last week’s security product news from Continuum, SYNNEX’s solution-based growth strategy, and some wacky-but-real software error messages. Matt also gives us a glimpse of the exclusive behind-the-scenes look he recently got of the astonishingly harsh testing regimen Lenovo subjects its ThinkPads to, and discusses the new 25th anniversary throwback ThinkPad Lenovo unveiled last week. All of that, however, follows a getting-to-know-you visit with new ChannelPro contributor Lisa Hendrickson, impresario of the Call That Girl blog. Read that last sentence very carefully, people. Sometimes word order matters a lot. Subscribe to ChannelPro Weekly! Look for us in your favorite podcast app. If you don't see us (yet) then you can subscribe via RSS in almost any podcast app using this link: http://www.channelpronetwork.com/rss/cpw Show Information: Episode #: 059Title: Meet Call That Girl...Not That Call GirlDuration: 1:26:32File size: 39.7MBRegulars: Regulars: Rich Freeman - Executive Editor, Matt Whitlock - Technology Editor Topics and Related Links Mentioned: Marketing & SEO Tips for Business Owners Continuum CEO: Our Year Ahead Is All About Security Continuum Enters Managed Security Market with Multi-Product Offering SYNNEX is Building a Future for Itself and its Partners in Solutions 5 Horrifying Tests Lenovo ThinkPads Must Face Funny Error Messages Where's Joel? Matt's tech pick: Lenovo ThinkPad 25 Rich's ICYMI preview and peek ahead at the news week to come
We recap vBSDcon, give you the story behind a PF EN, reminisce in Solaris memories, and show you how to configure different DEs on FreeBSD. This episode was brought to you by Headlines [vBSDCon] vBSDCon was held September 7 - 9th. We recorded this only a few days after getting home from this great event. Things started on Wednesday night, as attendees of the thursday developer summit arrived and broke into smallish groups for disorganized dinner and drinks. We then held an unofficial hacker lounge in a medium sized seating area, working and talking until we all decided that the developer summit started awfully early tomorrow. The developer summit started with a light breakfast and then then we dove right in Ed Maste started us off, and then Glen Barber gave a presentation about lessons learned from the 11.1-RELEASE cycle, and comparing it to previous releases. 11.1 was released on time, and was one of the best releases so far. The slides are linked on the DevSummit wiki page (https://wiki.freebsd.org/DevSummit/20170907). The group then jumped into hackmd.io a collaborative note taking application, and listed of various works in progress and upstreaming efforts. Then we listed wants and needs for the 12.0 release. After lunch we broke into pairs of working groups, with additional space for smaller meetings. The first pair were, ZFS and Toolchain, followed by a break and then a discussion of IFLIB and network drivers in general. After another break, the last groups of the day met, pkgbase and secure boot. Then it was time for the vBSDCon reception dinner. This standing dinner was a great way to meet new people, and for attendees to mingle and socialize. The official hacking lounge Thursday night was busy, and included some great storytelling, along with a bunch of work getting done. It was very encouraging to watch a struggling new developer getting help from a seasoned veteran. Watching the new developers eyes light up as the new information filled in gaps and they now understood so much more than just a few minutes before, and they raced off to continue working, was inspirational, and reminded me why these conferences are so important. The hacker lounge shut down relatively early by BSD conference standards, but, the conference proper started at 8:45 sharp the next morning, so it made sense. Friday saw a string of good presentations, I think my favourite was Jonathan Anderson's talk on Oblivious sandboxing. Jonathan is a very energetic speaker, and was able to keep everyone focused even during relatively complicated explanations. Friday night I went for dinner at ‘Big Bowl', a stir-fry bar, with a largish group of developers and users of both FreeBSD and OpenBSD. The discussions were interesting and varied, and the food was excellent. Benedict had dinner with JT and some other folks from iXsystems. Friday night the hacker lounge was so large we took over a bigger room (it had better WiFi too). Saturday featured more great talks. The talk I was most interested in was from Eric McCorkle, who did the EFI version of my GELIBoot work. I had reviewed some of the work, but it was interesting to hear the story of how it happened, and to see the parallels with my own story. My favourite speaker was Paul Vixie, who gave a very interesting talk about the gets() function in libc. gets() was declared unsafe before the FreeBSD project even started. The original import of the CSRG code into FreeBSD includes the compile time, and run-time warnings against using gets(). OpenBSD removed gets() in version 5.6, in 2014. Following Paul's presentation, various patches were raised, to either cause use of gets() to crash the program, or to remove gets() entirely, causing such programs to fail to link. The last talk before the closing was Benedict's BSD Systems Management with Ansible (https://people.freebsd.org/~bcr/talks/vBSDcon2017_Ansible.pdf). Shortly after, Allan won a MacBook Pro by correctly guessing the number of components in a jar that was standing next to the registration desk (Benedict was way off, but had a good laugh about the unlikely future Apple user). Saturday night ended with the Conference Social, and excellent dinner with more great conversations On Sunday morning, a number of us went to the Smithsonian Air and Space Museum site near the airport, and saw a Concorde, an SR-71, and the space shuttle Discovery, among many other exhibits. Check out the full photo album by JT (https://t.co/KRmSNzUSus), our producer. Thanks to all the sponsors for vBSDcon and all the organizers from Verisign, who made it such a great event. *** The story behind FreeBSD-EN-17.08.pf (https://www.sigsegv.be//blog/freebsd/FreeBSD-EN-17.08.pf) After our previous deep dive on a bug in episode 209, Kristof Provost, the maintainer of pf on FreeBSD (he is going to hate me for saying that) has written the story behind a recent ERRATA notice for FreeBSD First things first, so I have to point out that I think Allan misremembered things. The heroic debugging story is PR 219251, which I'll try to write about later. FreeBSD-EN-17:08.pf is an issue that affected some FreeBSD 11.x systems, where FreeBSD would panic at startup. There were no reports for CURRENT. There's very little to go on here, but we do know the cause of the panic ("integer divide fault"), and that the current process was "pf purge". The pf purge thread is part of the pf housekeeping infrastructure. It's a housekeeping kernel thread which cleans up things like old states and expired fragments. The lack of mention of pf functions in the backtrace is a hint unto itself. It suggests that the error is probably directly in pfpurgethread(). It might also be in one of the static functions it calls, because compilers often just inline those so they don't generate stack frames. Remember that the problem is an "integer divide fault". How can integer divisions be a problem? Well, you can try to divide by zero. The most obvious suspect for this is this code: idx = pfpurgeexpiredstates(idx, pfhashmask / (Vpfdefaultrule.timeout[PFTMINTERVAL] * 10)); However, this variable is both correctly initialised (in pfattachvnet()) and can only be modified through the DIOCSETTIMEOUT ioctl() call and that one checks for zero. At that point I had no idea how this could happen, but because the problem did not affect CURRENT I looked at the commit history and found this commit from Luiz Otavio O Souza: Do not run the pf purge thread while the VNET variables are not initialized, this can cause a divide by zero (if the VNET initialization takes to long to complete). Obtained from: pfSense Sponsored by: Rubicon Communications, LLC (Netgate) That sounds very familiar, and indeed, applying the patch fixed the problem. Luiz explained it well: it's possible to use Vpfdefaultrule.timeout before it's initialised, which caused this panic. To me, this reaffirms the importance of writing good commit messages: because Luiz mentioned both the pf purge thread and the division by zero I was easily able to find the relevant commit. If I hadn't found it this fix would have taken a lot longer. Next week we'll look at the more interesting story I was interested in, which I managed to nag Kristof into writing *** The sudden death and eternal life of Solaris (http://dtrace.org/blogs/bmc/2017/09/04/the-sudden-death-and-eternal-life-of-solaris/) A blog post from Bryan Cantrill about the death of Solaris As had been rumored for a while, Oracle effectively killed Solaris. When I first saw this, I had assumed that this was merely a deep cut, but in talking to Solaris engineers still at Oracle, it is clearly much more than that. It is a cut so deep as to be fatal: the core Solaris engineering organization lost on the order of 90% of its people, including essentially all management. Of note, among the engineers I have spoken with, I heard two things repeatedly: “this is the end” and (from those who managed to survive Friday) “I wish I had been laid off.” Gone is any of the optimism (however tepid) that I have heard over the years — and embarrassed apologies for Oracle's behavior have been replaced with dismay about the clumsiness, ineptitude and callousness with which this final cut was handled. In particular, that employees who had given their careers to the company were told of their termination via a pre-recorded call — “robo-RIF'd” in the words of one employee — is both despicable and cowardly. To their credit, the engineers affected saw themselves as Sun to the end: they stayed to solve hard, interesting problems and out of allegiance to one another — not out of any loyalty to the broader Oracle. Oracle didn't deserve them and now it doesn't have them — they have been liberated, if in a depraved act of corporate violence. Assuming that this is indeed the end of Solaris (and it certainly looks that way), it offers a time for reflection. Certainly, the demise of Solaris is at one level not surprising, but on the other hand, its very suddenness highlights the degree to which proprietary software can suffer by the vicissitudes of corporate capriciousness. Vulnerable to executive whims, shareholder demands, and a fickle public, organizations can simply change direction by fiat. And because — in the words of the late, great Roger Faulkner — “it is easier to destroy than to create,” these changes in direction can have lasting effect when they mean stopping (or even suspending!) work on a project. Indeed, any engineer in any domain with sufficient longevity will have one (or many!) stories of exciting projects being cancelled by foolhardy and myopic management. For software, though, these cancellations can be particularly gutting because (in the proprietary world, anyway) so many of the details of software are carefully hidden from the users of the product — and much of the innovation of a cancelled software project will likely die with the project, living only in the oral tradition of the engineers who knew it. Worse, in the long run — to paraphrase Keynes — proprietary software projects are all dead. However ubiquitous at their height, this lonely fate awaits all proprietary software. There is, of course, another way — and befitting its idiosyncratic life and death, Solaris shows us this path too: software can be open source. In stark contrast to proprietary software, open source does not — cannot, even — die. Yes, it can be disused or rusty or fusty, but as long as anyone is interested in it at all, it lives and breathes. Even should the interest wane to nothing, open source software survives still: its life as machine may be suspended, but it becomes as literature, waiting to be discovered by a future generation. That is, while proprietary software can die in an instant, open source software perpetually endures by its nature — and thrives by the strength of its communities. Just as the existence of proprietary software can be surprisingly brittle, open source communities can be crazily robust: they can survive neglect, derision, dissent — even sabotage. In this regard, I speak from experience: from when Solaris was open sourced in 2005, the OpenSolaris community survived all of these things. By the time Oracle bought Sun five years later in 2010, the community had decided that it needed true independence — illumos was born. And, it turns out, illumos was born at exactly the right moment: shortly after illumos was announced, Oracle — in what remains to me a singularly loathsome and cowardly act — silently re-proprietarized Solaris on August 13, 2010. We in illumos were indisputably on our own, and while many outsiders gave us no chance of survival, we ourselves had reason for confidence: after all, open source communities are robust because they are often united not only by circumstance, but by values, and in our case, we as a community never lost our belief in ZFS, Zones, DTrace and myriad other technologies like MDB, FMA and Crossbow. Indeed, since 2010, illumos has thrived; illumos is not only the repository of record for technologies that have become cross-platform like OpenZFS, but we have also advanced our core technologies considerably, while still maintaining highest standards of quality. Learning some of the mistakes of OpenSolaris, we have a model that allows for downstream innovation, experimentation and differentiation. For example, Joyent's SmartOS has always been focused on our need for a cloud hypervisor (causing us to develop big features like hardware virtualization and Linux binary compatibility), and it is now at the heart of a massive buildout for Samsung (who acquired Joyent a little over a year ago). For us at Joyent, the Solaris/illumos/SmartOS saga has been formative in that we have seen both the ill effects of proprietary software and the amazing resilience of open source software — and it very much informed our decision to open source our entire stack in 2014. Judging merely by its tombstone, the life of Solaris can be viewed as tragic: born out of wedlock between Sun and AT&T and dying at the hands of a remorseless corporate sociopath a quarter century later. And even that may be overstating its longevity: Solaris may not have been truly born until it was made open source, and — certainly to me, anyway — it died the moment it was again made proprietary. But in that shorter life, Solaris achieved the singular: immortality for its revolutionary technologies. So while we can mourn the loss of the proprietary embodiment of Solaris (and we can certainly lament the coarse way in which its technologists were treated!), we can rejoice in the eternal life of its technologies — in illumos and beyond! News Roundup OpenBSD on the Lenovo Thinkpad X1 Carbon (5th Gen) (https://jcs.org/2017/09/01/thinkpad_x1c) Joshua Stein writes about his experiences running OpenBSD on the 5th generation Lenovo Thinkpad X1 Carbon: ThinkPads have sort of a cult following among OpenBSD developers and users because the hardware is basic and well supported, and the keyboards are great to type on. While no stranger to ThinkPads myself, most of my OpenBSD laptops in recent years have been from various vendors with brand new hardware components that OpenBSD does not yet support. As satisfying as it is to write new kernel drivers or extend existing ones to make that hardware work, it usually leaves me with a laptop that doesn't work very well for a period of months. After exhausting efforts trying to debug the I2C touchpad interrupts on the Huawei MateBook X (and other 100-Series Intel chipset laptops), I decided to take a break and use something with better OpenBSD support out of the box: the fifth generation Lenovo ThinkPad X1 Carbon. Hardware Like most ThinkPads, the X1 Carbon is available in a myriad of different internal configurations. I went with the non-vPro Core i7-7500U (it was the same price as the Core i5 that I normally opt for), 16Gb of RAM, a 256Gb NVMe SSD, and a WQHD display. This generation of X1 Carbon finally brings a thinner screen bezel, allowing the entire footprint of the laptop to be smaller which is welcome on something with a 14" screen. The X1 now measures 12.7" wide, 8.5" deep, and 0.6" thick, and weighs just 2.6 pounds. While not available at initial launch, Lenovo is now offering a WQHD IPS screen option giving a resolution of 2560x1440. Perhaps more importantly, this display also has much better brightness than the FHD version, something ThinkPads have always struggled with. On the left side of the laptop are two USB-C ports, a USB-A port, a full-size HDMI port, and a port for the ethernet dongle which, despite some reviews stating otherwise, is not included with the laptop. On the right side is another USB-A port and a headphone jack, along with a fan exhaust grille. On the back is a tray for the micro-SIM card for the optional WWAN device, which also covers the Realtek microSD card reader. The tray requires a paperclip to eject which makes it inconvenient to remove, so I think this microSD card slot is designed to house a card semi-permanently as a backup disk or something. On the bottom are the two speakers towards the front and an exhaust grille near the center. The four rubber feet are rather plastic feeling, which allows the laptop to slide around on a desk a bit too much for my liking. I wish they were a bit softer to be stickier. Charging can be done via either of the two USB-C ports on the left, though I wish more vendors would do as Google did on the Chromebook Pixel and provide a port on both sides. This makes it much more convenient to charge when not at one's desk, rather than having to route a cable around to one specific side. The X1 Carbon includes a 65W USB-C PD with a fixed USB-C cable and removable country-specific power cable, which is not very convenient due to its large footprint. I am using an Apple 61W USB-C charger and an Anker cable which charge the X1 fine (unlike HP laptops which only work with HP USB-C chargers). Wireless connectivity is provided by a removable Intel 8265 802.11a/b/g/n/ac WiFi and Bluetooth 4.1 card. An Intel I219-V chip provides ethernet connectivity and requires an external dongle for the physical cable connection. The screen hinge is rather tight, making it difficult to open with one hand. The tradeoff is that the screen does not wobble in the least bit when typing. The fan is silent at idle, and there is no coil whine even under heavy load. During a make -j4 build, the fan noise is reasonable and medium-pitched, rather than a high-pitched whine like on some laptops. The palm rest and keyboard area remain cool during high CPU utilization. The full-sized keyboard is backlit and offers two levels of adjustment. The keys have a soft surface and a somewhat clicky feel, providing very quiet typing except for certain keys like Enter, Backspace, and Escape. The keyboard has a reported key travel of 1.5mm and there are dedicated Page Up and Page Down keys above the Left and Right arrow keys. Dedicated Home, End, Insert, and Delete keys are along the top row. The Fn key is placed to the left of Control, which some people hate (although Lenovo does provide a BIOS option to swap it), but it's in the same position on Apple keyboards so I'm used to it. However, since there are dedicated Page Up, Page Down, Home, and End keys, I don't really have a use for the Fn key anyway. Firmware The X1 Carbon has a very detailed BIOS/firmware menu which can be entered with the F1 key at boot. F12 can be used to temporarily select a different boot device. A neat feature of the Lenovo BIOS is that it supports showing a custom boot logo instead of the big red Lenovo logo. From Windows, download the latest BIOS Update Utility for the X1 Carbon (my model was 20HR). Run it and it'll extract everything to C:driversflash(some random string). Drop a logo.gif file in that directory and run winuptp.exe. If a logo file is present, it'll ask whether to use it and then write the new BIOS to its staging area, then reboot to actually flash it. + OpenBSD support Secure Boot has to be disabled in the BIOS menu, and the "CSM Support" option must be enabled, even when "UEFI/Legacy Boot" is left on "UEFI Only". Otherwise the screen will just go black after the OpenBSD kernel loads into memory. Based on this component list, it seems like everything but the fingerprint sensor works fine on OpenBSD. *** Configuring 5 different desktop environments on FreeBSD (https://www.linuxsecrets.com/en/entry/51-freebsd/2017/09/04/2942-configure-5-freebsd-x-environments) This fairly quick tutorial over at LinuxSecrets.com is a great start if you are new to FreeBSD, especially if you are coming from Linux and miss your favourite desktop environment It just goes to show how easy it is to build the desktop you want on modern FreeBSD The tutorial covers: GNOME, KDE, Xfce, Mate, and Cinnamon The instructions for each boil down to some variation of: Install the desktop environment and a login manager if it is not included: > sudo pkg install gnome3 Enable the login manager, and usually dbus and hald: > sudo sysrc dbusenable="YES" haldenable="YES" gdmenable="YES" gnomeenable="YES"? If using a generic login manager, add the DE startup command to your .xinitrc: > echo "exec cinnamon" > ~/.xinitrc And that is about it. The tutorial goes into more detail on other configuration you can do to get your desktop just the way you like it. To install Lumina: > sudo pkg install lumina pcbsd-utils-qt5 This will install Lumina and the pcbsd utilities package which includes pcdm, the login manager. In the near future we hear the login manager and some of the other utilities will be split into separate packages, making it easier to use them on vanilla FreeBSD. > sudo sysrc pcdmenable=”YES” dbusenable="YES" hald_enable="YES" Reboot, and you should be greeted with the graphical login screen *** A return-oriented programming defense from OpenBSD (https://lwn.net/Articles/732201/) We talked a bit about RETGUARD last week, presenting Theo's email announcing the new feature Linux Weekly News has a nice breakdown on just how it works Stack-smashing attacks have a long history; they featured, for example, as a core part of the Morris worm back in 1988. Restrictions on executing code on the stack have, to a great extent, put an end to such simple attacks, but that does not mean that stack-smashing attacks are no longer a threat. Return-oriented programming (ROP) has become a common technique for compromising systems via a stack-smashing vulnerability. There are various schemes out there for defeating ROP attacks, but a mechanism called "RETGUARD" that is being implemented in OpenBSD is notable for its relative simplicity. In a classic stack-smashing attack, the attack code would be written directly to the stack and executed there. Most modern systems do not allow execution of on-stack code, though, so this kind of attack will be ineffective. The stack does affect code execution, though, in that the call chain is stored there; when a function executes a "return" instruction, the address to return to is taken from the stack. An attacker who can overwrite the stack can, thus, force a function to "return" to an arbitrary location. That alone can be enough to carry out some types of attacks, but ROP adds another level of sophistication. A search through a body of binary code will turn up a great many short sequences of instructions ending in a return instruction. These sequences are termed "gadgets"; a large program contains enough gadgets to carry out almost any desired task — if they can be strung together into a chain. ROP works by locating these gadgets, then building a series of stack frames so that each gadget "returns" to the next. There is, of course, a significant limitation here: a ROP chain made up of exclusively polymorphic gadgets will still work, since those gadgets were not (intentionally) created by the compiler and do not contain the return-address-mangling code. De Raadt acknowledged this limitation, but said: "we believe once standard-RET is solved those concerns become easier to address separately in the future. In any case a substantial reduction of gadgets is powerful". Using the compiler to insert the hardening code greatly eases the task of applying RETGUARD to both the OpenBSD kernel and its user-space code. At least, that is true for code written in a high-level language. Any code written in assembly must be changed by hand, though, which is a fair amount of work. De Raadt and company have done that work; he reports that: "We are at the point where userland and base are fully working without regressions, and the remaining impacts are in a few larger ports which directly access the return address (for a variety of reasons)". It can be expected that, once these final issues are dealt with, OpenBSD will ship with this hardening enabled. The article wonders about applying the same to Linux, but notes it would be difficult because the Linux kernel cannot currently be compiled using LLVM If any benchmarks have been run to determine the cost of using RETGUARD, they have not been publicly posted. The extra code will make the kernel a little bigger, and the extra overhead on every function is likely to add up in the end. But if this technique can make the kernel that much harder to exploit, it may well justify the extra execution overhead that it brings with it. All that's needed is somebody to actually do the work and try it out. Videos from BSDCan have started to appear! (https://www.youtube.com/playlist?list=PLeF8ZihVdpFfVEsCxNWGDmcATJfRZacHv) Henning Brauer: tcp synfloods - BSDCan 2017 (https://www.youtube.com/watch?v=KuHepyI0_KY) Benno Rice: The Trouble with FreeBSD - BSDCan 2017 (https://www.youtube.com/watch?v=1DM5SwoXWSU) Li-Wen Hsu: Continuous Integration of The FreeBSD Project - BSDCan 2017 (https://www.youtube.com/watch?v=SCLfKWaUGa8) Andrew Turner: GENERIC ARM - BSDCan 2017 (https://www.youtube.com/watch?v=gkYjvrFvPJ0) Bjoern A. Zeeb: From the outside - BSDCan 2017 (https://www.youtube.com/watch?v=sYmW_H6FrWo) Rodney W. Grimes: FreeBSD as a Service - BSDCan 2017 (https://www.youtube.com/watch?v=Zf9tDJhoVbA) Reyk Floeter: The OpenBSD virtual machine daemon - BSDCan 2017 (https://www.youtube.com/watch?v=Os9L_sOiTH0) Brian Kidney: The Realities of DTrace on FreeBSD - BSDCan 2017 (https://www.youtube.com/watch?v=NMUf6VGK2fI) The rest will continue to trickle out, likely not until after EuroBSDCon *** Beastie Bits Oracle has killed sun (https://meshedinsights.com/2017/09/03/oracle-finally-killed-sun/) Configure Thunderbird to send patch friendly (http://nanxiao.me/en/configure-thunderbird-to-send-patch-friendly/) FreeBSD 10.4-BETA4 Available (https://www.freebsd.org/news/newsflash.html#event20170909:01) iXsystems looking to hire kernel and zfs developers (especially Sun/Oracle Refugees) (https://www.facebook.com/ixsystems/posts/10155403417921508) Speaking of job postings, UnitedBSD.com has few job postings related to BSD (https://unitedbsd.com/) Call for papers USENIX FAST ‘18 - February 12-15, 2018, Due: September 28 2017 (https://www.freebsdfoundation.org/news-and-events/call-for-papers/usenix-fast-18-call-for-papers/) Scale 16x - March 8-11, 2018, Due: October 31, 2017 (https://www.freebsdfoundation.org/news-and-events/call-for-papers/scale-16x-call-for-participation/) FOSDEM ‘18 - February 3-4, 2018, Due: November 3 2017 (https://www.freebsdfoundation.org/news-and-events/call-for-papers/fosdem-18-call-for-participation/) Feedback/Questions Jason asks about cheap router hardware (http://dpaste.com/340KRHG) Prashant asks about latest kernels with freebsd-update (http://dpaste.com/2J7DQQ6) Matt wants know about VM Performance & CPU Steal Time (http://dpaste.com/1H5SZ81) John has config questions regarding Dell precision 7720, FreeBSD, NVME, and ZFS (http://dpaste.com/0X770SY) ***
00:45 - Introducing the Wood brothers and their work Upgrade Rails Hint.io Ben’s Twitter Joshua’s Twitter 3:05 - Upgrading Rails without breaking it 6:25 - Working with clients with technical debt 12:20 - Frequently seen projects and clients 14:45 - Upgrading clients from older versions of Rails 22:50 - Why do clients push off upgrading? 28:10 - How do you know when it’s time to upgrade? 34:35 - Finding the right clients Website Ruby Weekly 37:50 - Avoiding technical debt Rails Xss gem Bundler 40:30 - Upgrading Rails yourself http://guides.rubyonrails.org/ contact@hint.io Picks: Suture Gem (Ben) Debride Gem (Ben) JRuby Truffle Project by Oracle (Josh) ThinkPads (Josh) Honeybadger IO (Josh) “A Rubyist’s Guide to Big-O Notation” blog post (Josh) Eat That Frog!: 21 Great Ways to Stop Procrastinating and Get More Done in Less Time by Brian Tracey (Brian) Codefights (Brian) Basics of Mechanical Engineering by Paul D. Ronney (Jason) The Demon-haunted World by Carl Sagan (Jason)
00:45 - Introducing the Wood brothers and their work Upgrade Rails Hint.io Ben’s Twitter Joshua’s Twitter 3:05 - Upgrading Rails without breaking it 6:25 - Working with clients with technical debt 12:20 - Frequently seen projects and clients 14:45 - Upgrading clients from older versions of Rails 22:50 - Why do clients push off upgrading? 28:10 - How do you know when it’s time to upgrade? 34:35 - Finding the right clients Website Ruby Weekly 37:50 - Avoiding technical debt Rails Xss gem Bundler 40:30 - Upgrading Rails yourself http://guides.rubyonrails.org/ contact@hint.io Picks: Suture Gem (Ben) Debride Gem (Ben) JRuby Truffle Project by Oracle (Josh) ThinkPads (Josh) Honeybadger IO (Josh) “A Rubyist’s Guide to Big-O Notation” blog post (Josh) Eat That Frog!: 21 Great Ways to Stop Procrastinating and Get More Done in Less Time by Brian Tracey (Brian) Codefights (Brian) Basics of Mechanical Engineering by Paul D. Ronney (Jason) The Demon-haunted World by Carl Sagan (Jason)
00:45 - Introducing the Wood brothers and their work Upgrade Rails Hint.io Ben’s Twitter Joshua’s Twitter 3:05 - Upgrading Rails without breaking it 6:25 - Working with clients with technical debt 12:20 - Frequently seen projects and clients 14:45 - Upgrading clients from older versions of Rails 22:50 - Why do clients push off upgrading? 28:10 - How do you know when it’s time to upgrade? 34:35 - Finding the right clients Website Ruby Weekly 37:50 - Avoiding technical debt Rails Xss gem Bundler 40:30 - Upgrading Rails yourself http://guides.rubyonrails.org/ contact@hint.io Picks: Suture Gem (Ben) Debride Gem (Ben) JRuby Truffle Project by Oracle (Josh) ThinkPads (Josh) Honeybadger IO (Josh) “A Rubyist’s Guide to Big-O Notation” blog post (Josh) Eat That Frog!: 21 Great Ways to Stop Procrastinating and Get More Done in Less Time by Brian Tracey (Brian) Codefights (Brian) Basics of Mechanical Engineering by Paul D. Ronney (Jason) The Demon-haunted World by Carl Sagan (Jason)
Bill and Larry solve the world's Linux issues... well the ones provided via our listener feedback anyway! From printers to ThinkPads and from marketing Linux to backups and processors, we discuss it all, and more. Episode 310 Time Stamps 00:00 Going Linux #310 · Listener Feedback 00:15 Introduction 00:52 Larry needs more coffee 02:25 Snake: Partitioning a new hard drive 05:33 Tony: Email issues 09:24 JackDeth: Printers and Linux 14:46 Steve: ThinkPads on Linux 21:34 Marcio: New listener 22:18 JackDeth: 12-button mouse 23:58 Paul: Marketing Linux computers 30:42 Troy: Backups for small businesses 35:22 Ken: AMD processors and Linux 40:14 Eduardo: Securing backups 45:03 Madison: Gone Linux 54:24 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 55:33 End
Bill and Larry solve the world's Linux issues... well the ones provided via our listener feedback anyway! From printers to ThinkPads and from marketing Linux to backups and processors, we discuss it all, and more. Episode 310 Time Stamps 00:00 Going Linux #310 · Listener Feedback 00:15 Introduction 00:52 Larry needs more coffee 02:25 Snake: Partitioning a new hard drive 05:33 Tony: Email issues 09:24 JackDeth: Printers and Linux 14:46 Steve: ThinkPads on Linux 21:34 Marcio: New listener 22:18 JackDeth: 12-button mouse 23:58 Paul: Marketing Linux computers 30:42 Troy: Backups for small businesses 35:22 Ken: AMD processors and Linux 40:14 Eduardo: Securing backups 45:03 Madison: Gone Linux 54:24 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 55:33 End
On this weeks episode we cover a UEFI firmware bug that is affecting computers including ThinkPads, tell you how your windows box can be totally pwned even if it's fully encrypted & talk about the shortcomings of the MD5 checksum. Plus the feedback, the roundup & more!
On this weeks episode we cover a UEFI firmware bug that is affecting computers including ThinkPads, tell you how your windows box can be totally pwned even if it's fully encrypted & talk about the shortcomings of the MD5 checksum. Plus the feedback, the roundup & more!
On this weeks episode we cover a UEFI firmware bug that is affecting computers including ThinkPads, tell you how your windows box can be totally pwned even if it's fully encrypted & talk about the shortcomings of the MD5 checksum. Plus the feedback, the roundup & more!
Going Linux 295 · Linux on ThinkPads In this episode, Larry speaks with Charles Tendell about Linux on ThinkPad computers. Charles is an ethical hacker and has successfully adopted the 5 year old ThinkPad T420 as an economical substitute for a new Macbook Pro for his business -- without sacrificing performance or capabilities! Episode 295 Time Stamps 00:00 Going Linux 295 · Linux on ThinkPads 00:15 Introduction 00:40 Charles Tendell: Certified Ethical Hacker 01:59 Why the ThinkPad instead of a Macbook Pro? 07:07 Comparing specifications: T420 vs. MBP 12:31 Battery life: WOW! 16:21 The skeptic decides 17:25 How the operating system was selected 19:05 Dispelling the myth that Linux is still only for geeks 19:44 Why Elementary and Kali Linux? 22:28 What applications does a hacker use for daily use? 24:35 How does a hacker use Kali? 27:17 The T420 har What applications does a hacker use for daily use?dware quality 28:50 Is the T420 too much computer for the average computer user? 30:38 T420 for media production 32:10 T420 Macbook Pro Killer 32:56 Upgrade recommendations 33:40 Azorian Cyber Security 34:13 Charles Tendell on TV 35:00 goinglinux.com, goinglinux@gmail.com, +1-904-468-7889, @goinglinux, feedback, listen, subscribe 35:59 End
This week on the show we're joined by Olivier Cochard-Labbé, the creator of both FreeNAS and the BSD Router Project! We'll be discussing what the BSD Router Project is, what it's for and where it's going. All this week's headlines and answers to viewer-submitted questions, on BSD Now - the place to B.. SD. This episode was brought to you by Headlines BSD Devroom CFP (https://lists.fosdem.org/pipermail/fosdem/2014-October/002038.html) This year's FOSDEM conference (Belgium, Jan 31st - Feb 1st) is having a dedicated BSD devroom They've issued a call for papers on anything BSD-related, and we always love more presentations If you're in the Belgium area or plan on going, submit a talk about something cool you're doing There's also a mailing list (https://lists.fosdem.org/listinfo/bsd-devroom) and some more information in the original post *** Bhyve SVM code merge (https://lists.freebsd.org/pipermail/freebsd-virtualization/2014-October/002905.html) The bhyve_svm code has been in the "projects" tree of FreeBSD, but is now ready (https://svnweb.freebsd.org/base?view=revision&revision=273375) for -CURRENT This changeset will finally allow bhyve to run on AMD CPUs, where it was previously limited to Intel only All the supported operating systems and utilities should work on both now One thing to note: bhyve doesn't support PCI passthrough on AMD just yet There may still be some issues (https://lists.freebsd.org/pipermail/freebsd-virtualization/2014-October/002935.html) though *** NetBSD at Open Source Conference Tokyo (https://mail-index.netbsd.org/netbsd-advocacy/2014/10/20/msg000671.html) The Japanese NetBSD users group held a booth at another recent open source conference As always, they were running NetBSD on everything you can imagine One of the users reports back to the mailing list on their experience, providing lots of pictures and links Here's an interesting screenshot of NetBSD running various other BSDs in Xen (https://pbs.twimg.com/media/B0NnfcbCEAAmKIU.jpg:large) *** More BSD switchers every day (https://www.reddit.com/r/unix/comments/2il383/question_about_the_bsd_community_as_a_whole/) A decade-long Linux user is considering making the switch, and asks Reddit about the BSD community Tired of the pointless bickering he sees in his current community, he asks if the same problems exist over here and what he should expect So far, he's found that BSD people seem to act more level-headed about things, and are much more practical, whereas some FSF/GNU/GPL people make open source a religion There's also another semi-related thread (https://www.reddit.com/r/BSD/comments/2jpxj9/question_about_the_current_state_of_freebsd/) about another Linux user wanting to switch to BSD because of systemd and GNU people There are some extremely well written and thought-out comments in the replies (in both threads), be sure to give them all a read Maybe the OPs should've just watched this show *** Interview - Olivier Cochard-Labbé - olivier@cochard.me (mailto:olivier@cochard.me) / @ocochardlabbe (https://twitter.com/ocochardlabbe) The BSD Router Project News Roundup FreeBSD -CURRENT on a T420 (https://www.banym.de/freebsd/install-freebsd-11-on-thinkpad-t420) Thinkpads are quite popular with BSD developers and users Most of the hardware seems to be supported across the BSDs (especially wifi) This article walks through installing FreeBSD -CURRENT on a Thinkpad T420 with UEFI If you've got a Thinkpad, or especially this specific one, have a look at some of the steps involved *** FreeNAS on a Supermicro 5018A-MHN4 (https://www.teckelworks.com/2014/10/building-a-freenas-server-with-a-supermicro-5018a-mhn4/) More and more people are migrating their NAS devices to BSD-based solutions In this post, the author goes through setting up FreeNAS on some of his new hardware His new rack-mounted FreeNAS machine has a low power Atom with eight cores and 64GB of RAM - quite a lot for its small form factor The rest of the post details all of the hardware he chose and goes through the build process (with lots of cool pictures) *** Hardening procfs and linprocfs (http://hardenedbsd.org/article/shawn-webb/2014-10-15/hardening-procfs-and-linprocfs) There was an exploit published recently for SFTP in OpenSSH, but it mostly just affected Linux There exists a native procfs in FreeBSD, which was the target point of that exploit, but it's not used very often The Linux emulation layer also supports its own linprocfs, which was affected as well The HardenedBSD guys weigh in on how to best solve the problem, and now support an additional protection layer from writing to memory with procfs If you want to learn more about ASLR and HardenedBSD, be sure to check out our interview with Shawn (http://www.bsdnow.tv/episodes/2014_08_27-reverse_takeover) too *** pfSense monitoring with bandwidthd (http://pfsensesetup.com/bandwidth-monitoring-with-bandwidthd/) A lot of people run pfSense on their home network, and it's really useful to monitor the bandwidth usage This article will walk you through setting up bandwidthd to do exactly that bandwidthd monitors based on the IP address, rather than per-interface It can also build some cool HTML graphs, and we love those pfSense graphs Have a look at our bandwidth monitoring and testing (http://www.bsdnow.tv/tutorials/vnstat-iperf) tutorial for some more ideas *** Feedback/Questions Dave writes in (http://slexy.org/view/s2b5ZZ5qCv) Chris writes in (http://slexy.org/view/s20aVvhv2d) Zeke writes in (http://slexy.org/view/s2Vmwxy1QM) Bostjan writes in (http://slexy.org/view/s2LB6MKoNT) Patrick writes in (http://slexy.org/view/s2xxB9uOuV) *** Mailing List Gold More (https://www.marc.info/?l=openbsd-tech&m=141357595922692&w=2) old bugs (https://www.marc.info/?l=openbsd-cvs&m=141358124924479&w=2) The Right Font™ (https://www.marc.info/?l=openbsd-cvs&m=141332534304117&w=2) (see also (https://twitter.com/blakkheim/status/522162864409546753)) ***
Lenovo officially sets it sights on the consumer market with the touchable and convertible N20p. With industry leading enterprise computers, can Lenovo produce a low end Chromebook? They have produced expensive heavy duty Thinkpads like the x31 and the new 11e for the education market, but with this model they are more Chromebook like. Inexpensive, light, good battery life, but with
We discuss LG G2 Android, Apple iPad Mini with Retina display, Logitech’s iPad Air covers, Samsung Galaxy Note 10.1, new ThinkPads, Apple buy’s gesture tech firm, PlayStation 4 vs Xbox One, NZ’s Quebee cam coming to Kickstarter, 3D printing on Windows 8.1 Running time : 0:51:49
Ueber Eingabegeräte kann man stundenlang reden. Darum haben wir gleich noch eine Folge dazu gemacht. Und es wird wohl in absehbarer Zeit auch noch einen dritten Teil geben dazu. Trackpoints :: Ersatzknubbels für Thinkpads Spacemouse :: Spacemouse Galerie Spaceball 1003 :: Der Ur-Spaceball von 1988 Spaceorb :: Der Spaceorb 360 Datenhandschuh :: Der Datenhandschuh, die Mutter aller Fuchtelsteuerungen Nintendo Wii :: Wii mit dem Wiimote Fuchtelcontroller USB-Skateboard :: Der Tony Hawks Skateboard Gamecontroller File Download (66:00 min / 96 MB)
Ueber Eingabegeräte kann man stundenlang reden. Darum haben wir gleich noch eine Folge dazu gemacht. Und es wird wohl in absehbarer Zeit auch noch einen dritten Teil geben dazu. Trackpoints :: Ersatzknubbels für Thinkpads Spacemouse :: Spacemouse Galerie Spaceball 1003 :: Der Ur-Spaceball von 1988 Spaceorb :: Der Spaceorb 360 Datenhandschuh :: Der Datenhandschuh, die Mutter aller Fuchtelsteuerungen Nintendo Wii :: Wii mit dem Wiimote Fuchtelcontroller USB-Skateboard :: Der Tony Hawks Skateboard Gamecontroller File Download (66:00 min / 96 MB)
Immer wieder passierts, dass die eine oder andere Komponente des neuen Computers oder Laptops einfach nicht mit dem geliebten Linux funktionieren will. In dieser Sendung geben XTaran und Venty Tips, wie aus Kauflust kein Treiberfrust wird. Trackliste Old Slush – Ärger mit dem Verstärker Alpha C – Foreign Girl Mordi – Resolution Nächste Sendung am 3. März 2012, 19:00 Uhr auf Radio LoRa Device Driver Check :: Debian Hardware Compatibility List SuSE HardwareDB :: Hardware Datenbajnk von SuSE SMOLT :: SMOLT vom Fedora Project ThinkWiki :: Wiki rund um die Linuxkonfiguration auf Thinkpads von IBM und Lenovo OpenPrinting :: Rund um Drucker für Linux File Download (61:26 min / 77 MB)
Immer wieder passierts, dass die eine oder andere Komponente des neuen Computers oder Laptops einfach nicht mit dem geliebten Linux funktionieren will. In dieser Sendung geben XTaran und Venty Tips, wie aus Kauflust kein Treiberfrust wird. Trackliste Old Slush – Ärger mit dem Verstärker Alpha C – Foreign Girl Mordi – Resolution Nächste Sendung am 3. März 2012, 19:00 Uhr auf Radio LoRa Device Driver Check :: Debian Hardware Compatibility List SuSE HardwareDB :: Hardware Datenbajnk von SuSE SMOLT :: SMOLT vom Fedora Project ThinkWiki :: Wiki rund um die Linuxkonfiguration auf Thinkpads von IBM und Lenovo OpenPrinting :: Rund um Drucker für Linux File Download (61:26 min / 77 MB)