FreeBSD, The Other Unix-Like Operating System and Why You Should Get Involved!

everyone my name is dub good can--at I'm the executive director of the FreeBSD Foundation yeah and I'll talk a little bit about the foundation later on but I'm here to give you an overview of FreeBSD to start off our day so the goals of today's or I'm sorry the goals of my goals for my talk it's really the share history talk about why people and organizations use FreeBSD and and then also hopefully at the end or near the end I've convinced you to try FreeBSD and hopefully contribute back to the project we're also going to talk about some of the features in FreeBSD and I'm actually going to hand that part off to Philip who is actually he's an actual developer and so he can cover those features a little bit more detail so I guess I don't let me just go back here really quick and and the reason and so I'll just give you a little bit about my background I've been running the foundation for 14 years now we're actually celebrating our 20th anniversary this year and and FreeBSD is gonna celebrates 27th anniversary this year sort of give you an idea of the history and and so in my background is where I was a low-level firmware engineer for many years and storage and so operating systems that's not my background and so but running the foundation for so many years over the years I'm learning more more about it and so I do have a goal this year that I just bought a new think pad and and i'm i've loaded freebsd on it I actually have previously on my computer here too but my goal is to be able to use that as much as I can yeah I mean really my goal is to use 100% of my to be able to to run the foundation on 100% using my freebsd system so so that's the goal and so the next conference i'm hoping to have that system used my presentation on Oh and part of logistics too so we do have some swag in the back I didn't really have a place I could put it so on when the chairs back there were mad as City he has his arm up so we do have some pens and lots of stickers so please feel free to take that that stuff with you so the freebsd world this is sort of how we picture it and you have three different components and so one on the top right is the actual operating system so that's what you download onto your computer that's what I'm running in VirtualBox here and and that's what FreeBSD is is actual code in the middle that's the project and the project is made up of a community of thousands of people who contribute code they can't read documentation they contribute in various ways to the project or I mean that is the project to FreeBSD and then the last component is the FreeBSD foundation and that's what I run and we are so in the United States so we are based in the US and we're considered 501c3 you may not be familiar with that that's how our government sort of categorizes us and it means that we're for the for the public good and so so we 100% focus on supporting the project and basically whatever the project needs if it's a critical need then we can help help them in those areas so what does FreeBSD so I know there is at least one hand that was raised or legitimate hands raised that wasn't familiar with FreeBSD so so first I always like to use this and I know it's not very nice to talks because we're really not anti-tax but but people who don't know previously or they're not familiar with it or they think like well I know it's a Linux distribution right and so so it's always the first thing I try to tell people is not and so so I want people understand that part of it it is when the oldest largest most successful open source projects around it's a complete operating system so when you think of Linux Linux is the kernel and then you have all these distributions and to add the tools in the user land and so by FreeBSD is all of that together and I'm gonna guess those numbers probably increase but I bet it supports over 33,000 third-party software packages that you can run on it to continue it's it's created by a very technical group of people and and actually people who worked on the original BSD we still have some of those people there too who are very involved in the project which is really cool they were so many different platforms and it's there's millions of deployments out there so this is my simple simplified version of where FreeBSD came from and so you may have heard of UNIX coming from AT&T they actually celebrated their 50th anniversary last year I think it was in November and so that was really exciting it went to Berkeley and they were doing research with it some people refer to it as Berkeley research oh gosh the the term slipped my mind but it's but BSD is Berkeley software distribution it's also a research UNIX version and then and then in the early 90s it's split off into net bsd and freebsd so this is this timeline that we created that's actually it scrolls and and I use it just talk just the show how you neck started in 69 and see language was was there at Bell Labs and just sort of the show you the history of how it went to Berkeley in 74 and you may have heard of names like Bill joy and and if you haven't he's when the co-founders a son and so he took over he was basically a primary developer of the 386bsd and that I'm not gonna go over all the different releases there but it's basically showing that they started implementing different features into the BSD and and the whole goal was really to be able to not only do all this research that they were doing but to provide it to users for free and so they're able to do this in 92 with that 386bsd and that was the first really truly open source unencumbered version of the BSD and that's what the FreeBSD and that BSD were based on and so we have a really nice timeline - on our website that's a little different and goes into more detail the history of FreeBSD and FreeBSD started and officially started in 1993 so I don't know if people in the back can see they'll see you around people in the front yeah and so I don't really use a slide so you can actually read the words but if you can that's great so this is you can go to you next org and you can see this and I've always been fascinated by this because it just shows it shows all these sort of branches and versions of UNIX that different companies developed them so I came up with themselves so all the the pink ones are closed source proprietary versions and so so when I was starting out after college I was easy I worked for IBM and so they had their own version of UNIX and and that's what I learned and then a green is all open source and the yellow is a combination of both and so you could see actually see if I have you know if you really see so I'm trying to show and well actually I have another slide here so well what I'm trying to show here so we have UNIX way up on top and how the lineage of FreeBSD is from that original UNIX and so and there's FreeBSD in that bsd both they had their version here and because of a lawsuit that people here are probably familiar with but and I'm not going to go into detail about it but they had they had to sort of do a restart to and to make sure everything was unencumbered and but one difference that I'd like to show is that so Linux is a unix-like operating system but its lineage is a from the original UNIX so I'm so it's a fun chart to show and and I'd recommend if you're interested in and seeing it up close to go to that website and look at it so he uses FreeBSD we put together a list of marquee companies logos that you'd recognize because I mean most of the time if you go and you ask someone honoree like I may tell someone that I work for the FreeBSD Foundation and they're like well what does FreeBSD and and everyone's heard of Linux and and so and people just don't realize that there's there a lot of companies that use FreeBSD and so we try to highlight some of them here so most likely use FreeBSD so I mean if you have an iPhone the iOS Mac OS both based on FreeBSD whatsapp you've probably heard of them they use FreeBSD if you play the Sony PlayStation 4 and the upcoming five is all FreeBSD based and if you're ordering planning at your travel travel a big-time user of FreeBSD as well as Groupon so so why use FreeBSD so like when I started here in the intro and I talked about how you know we the community is very welcoming and so so it is a very approachable community and so when you if you want to get started or if you have questions it's you you can feel pretty certain that you won't be you know you won't have a negative response that people will will answer in our appropriate fashion it's a good way to put it I follow a lot of lists and I just sort of and I watch the community and and I'm always amazed at like there's a Facebook user group and someone what house like it'll be it might be a basic question and someone will respond look uh-oh that's explained here in the handbook and so they just come back with here just here's a step just to help you you know figure it out or they may say well what more you know you know I can't answer your question because I need more information and so though they'll help that person and so it's so I really like seeing that within the community previously is known for its excellent documentation I would recommend sitting down reading the FreeBSD handbook it's actually very well written and I've read through it a few times and I'm always amazed at just how interesting it is because you would think oh this would be so boring and it's not we use modern tools and compilers there's really this consistent development process and a lot of it comes from the back then the day when it was at Berkeley that that followed that the model of that followed through the project and and then the BSD license that it's a permissive license is also secure so how does the project work so so I talked about the foundation and how I work for the foundation and then we have the FreeBSD project which is really the community and in my next slide I have more of like an org chart but the foundation is a totally separate entity they have the project has a nine person core team and the core team is basically like you can think of them as like the board of directors and so they don't tell the community what to do but they will help advise they'll step in if there's any developer relations problems like that also set some priorities but since it's a whole volunteer organization even if we say like we want to go or we as a core team want to go in this direction people could work on what they want still which is nice you because you can commit code when committer recognizes your contributions and they see that that you are getting involved and making these contributions through through patches and and so someone might step in and say you know I'd be interested in giving you a commitment I will become your mentor and so it's a mentor mentoring philosophy and we have different functional teams actually I'll show that in the next slide and it really is a collaborative development environment so this is this is sort of how I view the project there's tons of teams like I have down here I just can't really fit them on a slide but what I'm trying to show here is so the foundation is just a whole separate organization in the project I view us as working side by side we're not an umbrella organization they don't report to us and we can't tell them what to do and then the core team is that nine percent it's a committer voted on team that they get elected every two years and then you have all these functional teams and so this is just sort of a representation of all these other teams I have listed down here and what's nice about that is it allows people who want to be involved and say they're really interested in security then they might be able to be on the security team or if they're really interested in documentation they could be part of the documentation team and so it allows all these different teams to work together to produce this operating system in this project it also allows people to follow their interests and passion so this is a little more information about the core team how we have elections and and and this does talk a little bit about responsibilities the core team and and at the bottom it's it's basically we do like to stress that that we don't have like one person who approves everything who's in charge of it everything who sort of dictates what the projects going to do it's very democratically run and and the other way that it's run is that so say you're interested in contributing code and so you submit that patch and you'll have different people within the project who'll review that so it's not just one person it's usually someone from that area who's more experienced in that area and and it doesn't mean that you have substandard code you still have easy I mean we still have high expectations on the code and I code can always be reverted out so this is a distribution of the commuters and so the committers is a smaller group of people who can actually commit their own changes so whether it's source code or documentation and you become a committer by that mentorship process I talked about earlier but the reason why I like to show this chart is because [Music] you know FreeBSD was started in 93 and and the people who started it were a lot of them were from Berkeley and so you can imagine the age of those people now and and so it shows you that we do have young people who are joining the project and and so even though we still have some of the older few culture which is which is great because when we get these younger people then they can actually go to the older people or the more experienced people and they can get advice and get help and they're really approachable that's the other thing that I love about this project is so you have one person Kirk McKusick he came from Berkeley he's actually on my board but he also is actively contributing back to the project and so he's he's like a rock star and saira when he first joined our board I was like wow you know it was really cool it but the thing with Kirk is like he's yeah I see people look up to him all time and maybe they're nervous because they look at him as this icon and but he wants to talk to these people I mean he wants to be able to hand off his knowledge to other people he's he's probably going to retire at some point from FreeBSD I mean hopefully not for awhile still because he still has a lot to contribute but he loves talking telling stories and he and he definitely loves giving the newer people advice and help and so so it's great so we have releases and we try to follow the principle of least astonishment meaning you know don't change things for the sake of changing things and and don't break things that are already working we have two different types of releases we have the major release and the point releases and the major releases like right now our major release would be twelve dot oh the next one will be 13.0 and the point release we'll be so right now we have 12.1 and and so we have a schedule of really saying told that to sometime this year the actually the schedule is on online I know some of this is the slide is dated so so that's not really reflective of where we're at right now and we have the current branch where all the changes go and then the stable one which is where the releases are created from as well as weekly snapshots so say so for example with my new system that I buy I actually am using a current and using when the snapshots and so I just got it from searching for snapshots and and then that's the one that I installed so and then how do you contribute to FreeBSD there's many ways to contribute and I advise people if if you're not sure you could always start with documentation since our since we're known for our documentation your you know you're not like some projects I believe it's like if you know if your kernel developer you're looked at very highly and you know and other people are looked down upon and and that's not the case with this project and especially a documentation that it's a respected position and and in these people are usually fairly technical to who are doing documentation so that was my way to contribute back to FreeBSD I did not want to get into writing code again I considered it at the beginning but I thought it's very difficult with running the foundation and having the time to do that so I thought contributing through documentation was a great way so I started updating the website and which isn't the simplest thing I do but it was great because it also helped me understand what it takes for a new person to get involved and so so anyway what I'm saying here too and the second bullet is just because we're a small project that it's easier to step in and make a more notable contribution and it's easy to get started for contributing and so like I was saying that maybe start with documentation if you're interested there's also ports too that you can maintain we actually have a ports commuter in here at least one because I don't know if your ports commit or not but okay so but if you have any questions to at the last session today I'm gonna we're gonna have a Q&A so people Cask us specific questions to help if especially if you want to get started and and then the last thing is just go through like our PR list and submit some bug fixes so that's very helpful so why do companies he's FreeBSD I have a long list I mean probably one of the biggest reasons is because the license and being permissive and a lot of like especially when I talk to companies they just know FreeBSD they know it's a mature operating system but still innovative I mean we're still working on it and improving it yeah but they know that they understand the history of it and so they like to choose it for that this I'm going to skip but it Netflix has actually been giving a talk on their use of FreeBSD which has been going over very well they how Netflix uses it is when you think of watching Netflix and you're looking at the menu and that's all AWS based but once you push the play button then that's all off of previously servers around the world and they're getting like 90 gigabit per second transfer of each server and we're in here it's a 100 terabyte bits is over time I mean it like in a snapshot of time so so they've been talking about how they're using the the current branch the developer branch for in their production and have been very successful doing that yeah it's just a list of where freebsd stands out I mean most applications out there freebsd does very well in and one thing we are working on that I don't have on here is really in the desktop and that's something the foundation's trying to take on the help help get it because we really want people to be able and solve freebsd on their laptops like this one so what I'm going to do is I'm going to invite a guest speaker to come up here now Phillip is gonna cover he hasn't really reviewed my slides but he does know the operating system very well and so I'd like to invite you to come up here so people could see you hello Lou I know these slides very well because I think I wrote them okay maybe I stole them from him is really good at the sharing slides so this is a couple of slides on some of the features in the freebsd kernel like other open-source operating system kernels the freebsd kernel is a multi processing multi threaded kernel which means we run on multiple cpus at the same time and our kernel can do as many things at the same time as you have CPUs our kernel supports many popular hardware architectures and also some unpopular ones so we support the Intel AMD x86 x64 whatever you want to call it the 64 bits hack on top of the 32 bit hack on top of the 16 bit hack made by Intel we also run really well on arm bursts on the 32 bit harm and the 64 bits arm we have a very good support for risk 5 I know this because I work on it so if you have any of the existing risk 5 silicon FreeBSD will just run on it which is really cool we also run on some of the deeper embedded platforms like MIPS and PowerPC and also on some of the bigger PowerPC so I haven't kept up with power c.b.c much but it's the support is really good as well for software developers we support all of the programming interfaces phases which people know and love so the obviously we support the bsd programming interfaces like sockets bind listen and all those fun things we support them we have full support for POSIX I think that should be obvious and all of a classic UNIX interfaces what this means in practice is if you've got an application that runs on another unix-like operating system or on Linux there's a reasonably good chance that it will run unmodified on FreeBSD you know if it's an application that was originally written for Linux you might need to fiddle a little bit if you're using very learning specific features but if you've kept yourself TD conservative subset of POSIX a UNIX interfaces your application is just going to run on freebsd we do have the the ports tree which Deb mentioned earlier which has 30-some thousand packages which have already been ported for you so if you are looking for a any random application which you run on your Linux laptop there's a very good chance that this is just going to run on freebsd and that someone else has already done the work for you and all you need to do is package install blah and blah will be installed where blog can be anything from from a Python scripts to the chromium web browser but back to the kernel we also have a multi protocol network stack and actually FreeBSD or BSD in general was the reference implementation of many of these protocols so we support ipv4 which I like to call legacy or increasingly historical IP we support ipv6 we also still supports IP x and SP x does anyone in the room remember what IP x and SP x were all right you are all old we support apple talk on top of IP we have IPSec I think we have one ATM stack he left at some point we had three ATM stacks because sure if Y is that Y sub one we support Bluetooth our Bluetooth stack is a little but crusty in places but it works reasonably well Wi-Fi 82 11 I think the FreeBSD foundation's going to be funding some work correct me if I'm wrong yeah one of the problems which freebie is he has which Linux also has but Linux has the advantage of more market share or more eyeballs is Wi-Fi device drivers writing Wi-Fi device drivers is tedious and and difficult without data sheets so we're always a little bit behind other platforms when it comes to device drivers for Wi-Fi but the FreeBSD foundation's funding some of that work now so we should you know catch up with leaps and bounds we also support SCTP which is another you know it's a better TCP as I like to call it and FreeBSD is the reference implementation for that what are the things I like to use to sell FreeBSD you know it's free is that we have a unified and coherent build system across all components so to build your kernel you type one line in a config file if you want to add a device in the e type make and make is just going to build that one thing for you I been a couple of years since I last configured a loose kernel but there was this thing called menu config and you spend three or four weeks checking boxes and coming up with the configuration that may or may not work and then you type make and it complains at you and that's not great with FreeBSD we have this you know one config file you run it through config and config will tell you this is going to work or you know this is not going to work and then you type make it builds also our entire kernel comes with extensive documentation we have a section 9 in the in the main pages which documents not every single kernel interface because you know who has the time but most of the cartilage phases which you'll encounter say if you're writing a device driver or if you are doing grubby work inside the kernel there will be documentation for the kernel interfaces which will reflects reality which is kind of nice there we go that was the kernel we also have a user lands I hear it's a complete and integrate it's UNIX operating system what that means is we install the entire operating system out of the box we don't we are one group of people who develop all of the things that you need for a complete your next line operating system we do not have one group of people building a C library and another group of people who who don't talk to the first group of people building the shell and then the third group of people building grep and said that all those things all of those things are built and maintained by the same group of people the FreeBSD project and we install them all at the same time so if you install 3b is the you get everything you need to start working on a unix-like operating system out of the box you don't need to install packages just to get an editor you don't need to install packages just to get scripts or SEDs and also all of these kernel are usual features are maintained together so our if config to give an example is maintains and developed by the same people who write the network device drivers so there's no funny periods where you know the kernel supports a hundred and eight features but if you configure only supports 103 of them when we adds a feature to the kernel we also add the same support for the feature to user space immediately so everyone who updates three BSD immediately has supports for all the features there's no there's no concept of a distribution the whole operating system is a distribution and as Deb already said we have a strong focus on consistency one of our guiding principles is what we call the principle of least astonishment which tells us that if there's two ways of doing it's one way as fast but hugely disruptive and the other way is it'll take a six months but the the slope will be a lot flatter or the path of upgrading will be a lot flatter then we will go for the extra six months of work which you know the the the opposites of our principle of least astonishment I call the culture of surprise and we don't like the culture of surprise we like our we like our consistency did you steal any more slides oh yes you did Wow I remember writing these great then we have robust file systems entry BSD so traditionally we came with ufs the UNIX file system which was written in the mists of time and more recently we have ZFS which I'm giving a talk on in well actually actually after this talk so you have well there's also a couple of other less robust file systems we also have read-only supports for some of the Linux file systems and ms-dos FS and I think we also support fuse now so any file system a user space you can run on FreeBSD as well you usually just read only supports we have something called D trace which I could talk about for a whole week but I won't which is an advanced event based live tracing tool it shows you basically what's happening on your system in real time without what it's turned off without any measurable performance impact so you can do function boundary tracing which will tell you I have entered this function I have now left this function it keeps track of all the parameters the return values and all that good stuff and then you can just trace it it'll tell you what your system is doing at any given time the main question dtrace answers is why is my system slow or what is my system doing right now I love D trace I can't remember a time when when I developed stuff without D trace I've purged the memories we have something called jails which are lightweight virtualization basically in a nutshell it allows you to run containers on top of FreeBSD we've had it since the early 2000s jail is pretty much asha roots with an IP address or multiple IP addresses ipv4 and ipv6 but these days we also constrain other kernel names basis to some extent it's not like docker there's no there's no ecosystem it's a root with an IP address but it allows you to run multi tenant web web hosting very easily it also allows you to set up workshops and labs very easily for teaching if some evil beehive which I think Peters in the back of the room is he wrote it it's a hypervisor it's if you've used KTM or Linux it's like that it's it's a full-blown hypervisor it's it's virtualizes all of the resources on your system and as the multi the higher level page tables on Intel systems I think beehive is being ported to arm I don't know the status of that and one day it'll also run on on risk v tcp/ip I've mentioned our network stacks it was originally originally TCP and IP were developed on BSD and three bsd remains a reference implementation for several network protocols we are an active member of the the transport working groups so there's regular calls with 3bz developers and other people who are interested in in transport protocols and performance we have a an increasingly mature implementation of bbr if you want to have fast internet in Australia at the cost of being extremely antisocial you can do that on FreeBSD as well finally on this slide we have something called capsicum which is a lightweight capability framework which allows you to add sandboxing within an application say you have something like TCP dump which does several things some of which need privilege and some of which don't in the case of TCP dump capturing packets on the network needs privilege but printing or detangling the packets and printing the what's inside the package to determine all needs no privilege and in fact once no privilege what's capsicum does is it isolates the privileged bits of the application from the unprivileged bits so only the network capturing bits run with elevated privilege and detangling the packets and printing the results to the terminal runs at ambient privilege this you know kills an entire category of of exploits because detangling packets and analyzing network traffic is potentially dangerous you know you can put anything in packets so if we run that with ambient privilege and just captured at traffic with elevated privileges we don't allow you to exploits someone analyzing network traffic I keep talking away and ask Andy to come up and talk around if you just want to give a high really clear cherry is a cherry is a project from the University of Cambridge and SSRI labs it's very researchy but it's it's originally started as capability instructions added to the mix architecture and now it's in different architectures its ads what capsicum does to applications very high level overview it adds what capsicum does for applications to the CPU architecture it provides hardware sandboxing to isolates tasks that need more privileged from tasks it need less privilege the I think the canonical example of what cherry gives you is imagine a world where you have two web browser tabs one of them is your bank and one of them is a gambling sites or you know inserts inserts example here you do not want tab a to talk to tab B the way we do this in UNIX is each tab is a process but processes are fairly expensive what's cherry does is it gives you hardware extensions to put this sandboxing in hardware so the processors become cheaper or the isolation model of processors becomes cheaper because they become Hardware instructions and you get extra compiler goop to take advantage of these instructions the current state of cherry is that's you know FreeBSD boots perfectly well on cherry and the research project is now in its eighth or ninth year I don't know but you know FreeBSD has good support for that should I keep going that's the last one the Morello board I don't actually do about to mellow board but I know two people in this room microphones yeah I think you can go ahead and do what we want well thing I think the Morello board is his arm is an arm board with the cherry instructions inside the arm CPU so originally when when cherry came into existence they were Hardware extensions for MIPS but it turns out that MIPS is not really a particularly popular architecture these days there's this other popular architecture out there arm and arm really liked these cherry extensions so cherry was added to arm in some shape or form and now arm is adding a or spitting out a board for that a number a low board will be the only physical implementation of this hardware architecture I have no idea when it's coming out but as soon as it does I want one this is the first time I've seen this line okay we'll go ahead and move on you can take that with you so thank you Phillip for jumping in on that so I just have a few more slides here yeah so I wanted to quickly cover the freebsd foundational so like I I said earlier it's a whole separate organization we're a 501 C 3 were based in the US were actually based in Boulder Colorado but we are distributed so I have people all over the world who either work for us or our board members too and we're 100% funded by donations and so last year we actually raised where our goal was when in a quarter million and we actually raised 2.2 million which was really exciting and allows us to bring on to fill more positions to step in and support the project like I said earlier we're separate from the project and our whole purpose is really the support the critical needs of the project so why should we so I have the slide actually I probably should have pulled it sorry so I give this talk I've been giving this talk at quite a few Linux type of conferences and I know that like so Lennox Coffey it was sort of focused on Linux but I think I think it is trying to be more open source or an said but what I use the slide for was just to talk to people about so even if like we don't convert you you're not interested and trying out FreeBSD but reasons why we should work together and and so some of the ones that I've come up with it's just like how important is to even if like if you're sucide man to understand FreeBSD it really it just helps grow you it just it will help you with problem solving and understanding how others are doing it whether it's the right way or not at least you could determine that like why one might be better than the other you can learn from our successes and as well as failures and and we have different coding philosophies and methodologies and so understanding the reasons for that and so and it all comes down to you like just understanding the foundations of why you know in the principles of how each came about with a smaller codebase is a great reference you know platform so if you're interested in learning about operating systems we have a lot fewer Airlines code and so it's a lot less code to learn yeah so for example FreeBSD is the kernel is I think it's just like five point seven million lines of code and the Linux kernel is it was like 35 million there's a there's a humongous difference and and so this quote at the end was something I got from the Linux system n and that just that he felt by a learning FreeBSD it made having better Linux so said none and systems engineer and so why should you contribute to FreeBSD so earlier I talked about the community has great mentoring culture it's a great way to learn systems programming and like I said the code base is a great platform reference it really because the size of the project you do have more opportunities to step in I was just talking someone earlier about even they're going to have some some new young employees who have been working with FreeBSD but not a lot but really gives them an opportunity now to become an expert in area but they also have other experts that they can reach out to to get help and so that much better opportunity to make a difference and to grow and oh and just the fact that some of the founders are still involved with the project and they're very much approach to law so we suggest that if you're interested in trying out FreeBSD I list a bunch of the cloud platforms out there that you could actually run freebsd on digitalocean actually has great documentation on FreeBSD so when they started supporting FreeBSD when other writers or developers actually wrote up a series of documents on like FreeBSD for Linux people and so it's really helpful and and so or install a VM on your computer that's what I do and that's right currently how I do my documentation is I run FreeBSD on VirtualBox and when we do training so we usually are using a VirtualBox and so I try to list some of the resources here for you to go to for learning more about FreeBSD and like I said earlier the FreeBSD handbook is a great resource and then those two the two books I have here on the top once more for kernel internals and then when is more for just like how do you not just but how do you use FreeBSD especially like more from us admin perspective and they're both highly regarded resources they'll so my cutoff because of the time or did I owe my slides of that they're setting me down and but we'll put all of our slides somewhere right now I'm not sure exactly where we're gonna put them but we'll try to provide that information through Twitter and we'll tag the conference so so I've run out of time yeah but I want to thank everyone here for listening to my talk and the next one up will be here's the schedule we have five minutes in between so and get set up

Channel: linux.conf.au

Views: 36,524

Rating: 4.8297873 out of 5

Keywords: lca, lca2020, #linux.conf.au#linux#foss#opensource, DebGoodkin

Id: w6oGeTm95no

Length: 46min 21sec (2781 seconds)

Published: Wed Jan 15 2020