Greetings and welcome to the Introduction to Astronomy. In this lecture we are going to discuss determining ages of solar system objects. So how do we figure out how old something is in the solar system? Now there are a couple of ways that we can do this and we can look at two things that we call either the relative age or the absolute ages or the true age. So a relative age would be one way to do it. That shows how things are related to each other and the absolute ages are actual ages that we can determine. So there are a couple ways we can determine how old objects are in the solar system by looking at them or by getting samples of them. So relative ages is done by looking at the object. You don't need a sample of anything and it's essentially based on superposition. That if something is on top of something else then the thing on top must be more recent. So if you see craters and one crater is on top of another crater then the crater that is on top is the one that must have formed more recently. If you see something cutting through a feature, so if you have a crater and you have some kind of fault crack going through it, then that fault must have come later. So it tells you relatively how old things are. Now essentially what this means is that the more craters you see on the object the older the surface is. Remember that everything in the solar system is about four and a half billion years old but that does not mean that their surfaces have been unchanged all that time. Things like the moon have been relatively unchanged over the last few billion years. It's essentially looks the same now as it did a billion or two billion years ago. Other surfaces like the earths look nothing like they did a couple of billion years ago. So it tells you really not how old the surface, how old the object is, but how long it's been since it's has been resurfaced. So the moon was last resurfaced, worked a long time ago, whereas the earth has been relatively recently reworked. And we can use this throughout the solar system because the cratering rate has been effectively the same. Now the absolute ages are based on radioactive materials and radioactive decay. The way the radioactive material decays is in a very predictable manner and we can use that to figure out the exact age of a sample of a rock and how long it was since that rock solidified from molten lava. So let's look at these in a little bit more detail. And first of all looking at determining relative ages, first of all it's just countering the crater. Since cratering rates have been about the same for the last few billion years that tells you how old an object surface is. So if we look at an object when we see it we see more craters on the surface. That's the longer that surface has been exposed to space and to impacts. And what happens is that there are effects that will then wipe that out and that can be geological effects, volcanic eruptions, lava flows, can wipe out craters, and weathering effects can slowly wear down craters over time. So craters that formed a million years ago on the earth are now long since, could be long since gone, could have been wiped out. Especially smaller craters would not no longer exist. And craters that formed a billion years ago would no longer exist at all on the earth. However on the moon we can see craters that formed a billion or two billion or even three billion years ago. They are still present because there are far fewer weathering effects there. So a couple things like geological activity, weathering effects, and the presence of an atmosphere can really affect the number of craters that we will see on an object. So if we look at our example here, the earth has very few craters while the moon has many. That tells us that the earth's surface is younger and has been reworked by geological and weathering processes over the last, since the craters have formed. So over billions of years the earth's craters have been wiped out leaving only the most recent ones while many of the craters that ever formed on the moon are still there. So let's take a quick look at our moon here. And what we see are that there are regions that have lots of craters and regions that have very few craters. So the maria are the dark regions which have few craters and are a younger surface. And you can see some of the maria here and here. And these darker regions have fewer craters than the highland regions which are the lighter colored regions which have far more craters. So the rest of these regions you can see lots and lots of impact craters scattered around in between the maria and those are the older regions. So we know that the maria are younger and that the highlands over here are older regions. So we can tell the regions just by looking at the number of craters. Now if we were to actually do crater counts and how many craters there are per square mile, square kilometer, how many craters actually existed we could actually determine relatively how old these various sections are. However to get actual ages we really need a sample of the rock from the surface. So we can really tell which areas are younger or older here and we could even compare that among different objects. We could compare the moon to the earth but we could also compare things like Mars and Mercury and Venus and kind of get the ages for them as well. Now if we want to determine absolute ages or actual ages that requires a little bit more. If we want to find out how old it actually is we do need a sample of rock from the surface. So what happens is when rocks solidify they all have some radioactive minerals that will decay over time and we can look at the relative concentrations of these to determine how old that rock is. Once we can figure out how old the rock is that helps us get absolute ages and lets us calibrate our crater counts that we would use to determine other ages because we do not have samples of the entire moon for example. We have samples from various regions that the Apollo astronauts explored so we have to then use the ages that we determined there to help us to extrapolate and determine ages elsewhere on the moon. So let's look at how this process works and it uses a concept of half-life and what half-life means is that it's the amount of time required for one half of the parent atoms to decay into the daughter atoms. So however many half-lifes it is if we look at an object with a half-life of say one year as an example so let's look at a one year example half-life that means if you start off with 100 percent of your parent atom then after one half-life or one year you are down to 50 percent you have lost you have decayed half of those original atoms that had formed after two half-lives or two years you're now down to one quarter after three half-lives you've cut that in half and you're now down to just about 12 and a half percent so if you want to write that in 12 and a half percent of the atoms left after three years so what we can do is then compare the ratio of parent to daughter atoms to just discover the age so if they were equal we would know it is one half-life old if you have three times the number of daughter atoms that you have parent atoms then you would be able to say it's two half-lives old and so on you can just look at the relative ratios how many parent atoms relative to the daughter atoms do you see so this works very well when the curve is changing quickly here when you get out to the far end it doesn't work very well it's very hard to get the difference between six and seven and eight half-lives so if you were looking here to try to determine something it would be hard to tell whether it was six years or seven years or eight years old because the ratios would become very similar but in this part of the curve it's very easy to determine and that's why we look for minerals that have half-lives that are in this range that several half-lives would be about the approximate age of the of the rock so let's look at it let's make it into an example here for potassium 40 and what we can do is make a little table to look at how this changes over time so we can talk about the number of half-lives we'll do half-life here in the first column of the table how many half-lives have we passed then we want to put the age or the time that is passed and then we want to put the number of atoms that we see so we would have potassium 40 which potassium symbol is k and argon 40 argon is ar and what we want to look at is how much we'd have of each of these so let's just start off with the half-life zero which is time zero so when the when the object formed and let's just give it a number just to count here and we could say 1000 atoms of potassium 40 and since we haven't started the clock yet we would have no argon 40 and then we can continue and make tape make a table here for one half-life the half-life is 1.3 billion years so this would be 1.3 billion years which sometimes abbreviated as gyr for giga years or giga meaning billion and at that point you would have had one half of the potassium 40 decay so you would now have 500 potassium 40 atoms and they would have decayed into argon 40 so you would now have 500 argon 40 atoms if we wait another half-life so after two half-lives we double this this would now be 2.6 giga years now we would cut this in half again it's not the original amount it's the amount you had here that gets cut gets cut in half so it's not that you'd have zero potassium 40 you would now have half of the 500 or 250 atoms and you would now have gained that 250 in argon and have 750 argon 40 atoms let's just do a couple more here after three half-lives or 3.9 giga years 3.9 billion years you'd now be down to 125 potassium and 875 argon and finally if we went to four half-lives you would be at 5.2 billion years and that would get you down to 62 and a half atoms of potassium and 937 and a half atoms of argon 40 now you might wonder how do we get half of an atom it is because this is a probability each half-life each had an atom remaining has a 50 chance of decaying so what this means is that you have an equal chance of there being 62 or 63 potassium 40 atoms that would be present and then you would of course have either 937 or 938 argon atoms you cannot have an atom halfway decay but then you can look at the ratios how do they compare as I said a one to one ratio here you could have a one to three ratio here you could have a one to seven ratio here so when we determine that ratio how many daughter atoms there are relative to the parent atom that then tells us where we fall in this and what the age would be so let's finish up with our summary here and what we find is that we can measure we can determine ages of objects in the solar system it is something we can figure out and we talked about relative ages using crater counts how many craters there are in different regions to determine relatively how old they are and that works for regions on a planet or or moon or regions between different planets and different moons and we looked at how we can determine absolute ages by looking at the radioactive decay of minerals from rock samples brought back from an object's surface so that concludes our lecture on ages in the solar system we'll be back again next time for another topic in astronomy so until then have a great day everyone and I will see you in class


Welcome to Microterrorz. Scary stories for kids, where it's always the spooky season, full of chills, thrills, and spine-tingling spooks. Microterrorz are family-friendly frights for those ages 8 and up. And while our stories are for younger years, we are still talking about things that go bump in the night, and some children may not be able to handle what others can. Parental consent is recommended. Now for tonight's Microterrorz. The Doctor is in by Scott Donnelly. I awoke suddenly to something cold and metallic touching my chest. I gasped and sat up. When my eyes adjusted, I saw the Doctor. She pulled the metallic bell part of her stethoscope away from the top of my chest and let the neckline of my shirt rise back up. What's going on here? I asked her. Shhh! The Doctor whispered, You've been hurt. That's funny, I thought. I didn't remember getting hurt. How? I asked. The Doctor smiled at me. Her smile was small, but her dimples were big. It was a familiar smile, a comforting one. But behind it, I knew there was more to disappointment than met the eye. I looked around briefly, realizing I was in an enclosed room. Most of the lights were off, and only a slit of daylight was coming through the window blinds. I'm going to have to run some tests, the Doctor said. This appointment won't be quick. I continued to lay there as the Doctor revealed a medical bag. As she dug through its contents, I tried to feel my body trying to detect any pain or injuries, but for some reason I couldn't. All I felt was tired. Have you been getting enough exercise? The Doctor calmly asked me as she extracted a small scope from her bag. Yes ma'am, I responded, as she used the scope to look into each of my ears. Have you been eating well? She then asked me, using the same scope to look into my nose. Yes, I said. Well, I mean, I enjoy the occasional cheeseburger. Do you use extra cheese, sir? The Doctor asked me, using the same scope to then look into my mouth. Did she not care about sterilization? What kind of a Doctor's appointment was this? I pulled my face away from the scope. Yes, I admitted, I used extra cheese. The Doctor smiled. Well, that would explain a lot then. I was confused. She was just staring at me with a strange yet pretty smile. What is my consumption of extra cheese explain? It would explain all the spider boils on your leg. My stomach sank. Spider boils? I exclaimed. I sat up and ripped the sheets off my lower half. Up and down my legs were dozens of pulsating boils. Within their fleshy, bubbly confines, I could see dark things swishing about. There are spiders in those? Oh, yes, the Doctor said, and if I were to pop them, the spiders would all come out. But if I did that, they'd probably get into the walls and electrical outlets, and our power would go out. Oh, I said. I let myself fall back to a lying down position. Extra cheese caused this? I asked the Doctor. Confused and growing uneasy with this appointment. The more and more I tried to remember, I couldn't think of how I even ended up here. Last I knew I was at work, came home, tried to rest, and now... Oh, and we'll probably have to surgically remove the alien heart we put in you. The Doctor so casually interrupted. What alien heart? I asked. When you first came in, she said, you were scheduled for surgery, but one of our other doctors put an alien heart in you by mistake. What? I exclaimed. I tried to sit up again. I need to leave, I said. I can't be here anymore. I don't know what's going on. This all has to be a bad dream or something. I'm so sorry you can't leave, the Doctor said. You won't be able to without these. She held up a pair of shoes. My shoes? I asked. I don't need those. I'll just walk out of this nightmare appointment barefoot. The Doctor laughed at me. Well, that's going to be a problem because your feet are still in these shoes. What? I screamed, throwing your sheets off my spider-boil-covered legs. They ended at my ankles, withering away to just wilty strands of skin. My feet were gone. I looked back up at the Doctor. As professional as she acted and as innocent as she looked, this woman was absolutely nuts. Bulkers. We can put your feet back on if you'd like, the Doctor added. But it's not going to be cheap. We're talking about a multi-billion dollar surgery here, and I'll need the cash upfront. I became loud and unruly with her. Let me go. I just need to help someone. This Doctor is crazy. Just then the door to the Doctor's office burst open with energy and ferocity. In the doorway, a futuristic soldier posed in the shadows, wearing heavy armor, a helmet with a visor, and wielding a gigantic neon-colored laser cannon. Did someone say, the crazy, smelly Doctor must perish? The soldier growled. Then, without warning or even waiting for an answer, he opened fire, shooting lasers every which way into the room. I covered my head, but all I could hear were the heavy laser blasts and the screaming of the soldier and Doctor at each other. The lasers did stop, but the screaming continued. It sounded more like arguing, like siblings bickering. I uncovered my head just as the light in the room was switched on. Then I knew things had gotten out of hand. My wife stood in the doorway, shouting at the kids to stop fighting with each other. I climbed out of bed and joined her side. Guys! I shouted, loud enough to catch their attention. My six-year-old daughter, dressed in her white Doctor's costume, wearing plastic glasses and a toy stethoscope around her neck, stood in the middle of our bedroom. My a-year-old son, dressed in his science fiction soldier Halloween costume and holding a brightly-colored laser-tag gun, stood next to her. Both of them faced my wife and I. What's with all the arguing? I asked.  My son complained. It's my turn. I wasn't done. My daughter whined to my wife and I. We were in the middle of a Doctor's appointment and he just came in and started shooting lasers everywhere. As a second argument began, my wife was the one to shut it down immediately. No one was supposed to be playing with Dad. She said, he worked an overnight shift last night and was trying to get some sleep. I already told you guys to wait until he wakes up to play with him. The kids just stood there, now ashamed that they'd woken me. Sorry, Dad, they both said. I just smiled as I looked at them. Dressed up and immersed within play scenarios that required their minds to be creative and energetic. In the modern times, it was almost like a lost art amongst children. It's fine, I said, turning to my wife. As a matter of fact, I'm without feet, infected with spider and alien organs and the only two people in the world who can save me are this doctor and this soldier. The kids were ecstatic and bounced around the room with excitement. My wife just smiled and left the room. Dad, quick! My daughter yelled. Get back on the bed. We need to get your feet attached. The aliens are going to be back to harvest your organs any minute. What? I exclaimed, hopping back into the bed.  My son snarled as he opened a barrage of laser cannon blasts out into the hallway. I hope you enjoyed this video. Don't forget to like, comment, and subscribe. See you next time. Hey Weirdos, be sure to click the like button and subscribe to this channel and click the notification bell so you don't miss future videos. I post videos seven days a week, and while you're at it, spread the darkness by sharing this video with someone you know who loves all things strange and macabre. If you want to listen to the podcast, you can find it at WeirdDarkness.com. Listen.


You gotta give me the skincare routine because you got some some pretty skin over there. I don't know if it's the light, but I'm like, you gotta. My wife, my wife has been working on me. My wife's been working on me. Tell her A plus. She's doing a great job. Tell you just received an Emmy nom. Congratulations, number one. Thank you. Our awarding is that for you, given your labor of love with the show. Oh my goodness. It's wild. Like I'm I was sitting on a plane actually because I went to a game in Toronto to watch the Hawks and as we're sitting on the tarmac, I my phone is like blowing up. It's my boss is one of my producers. I'm like, I did something really good or really bad and I need to figure out why everyone at work is calling me. So it was really nice. You know, they are calling to say I was nominated for this Emmy. It was a major like shock for me. I didn't know these things were coming out, nor that I was even like up for it. So it was just really, really, really cool to see, you know, the work be received and people enjoy it and I just, I felt very proud and very happy and super honored to be with this group of people that I respect and admire so much. So it's it was exciting. You know, Taylor, I feel like interviews is this is too formal. What you're having are conversations. And there's the real, there's a real art to it. When did you fall in love with that art? I mean, honestly, I've always loved it. Like I've always really enjoyed people and learning about them in a very like real way. I've just always always enjoyed that. I think a lot of that is my parents like they're very warm welcoming, you know, we're Southern so we want to talk to everybody and get to know everybody. And I've always loved it. And growing up, my dad would like really make me do things like on stages or like talk to crowds of people like, because he would always tell me I should not be scared of people. And I'm so happy that he did that because I really enjoy just like talking and asking questions. And you know, when I think about it, I just think about so much of how I grew up and how you know one day when I have kids like how I'd want them to grow up. And it's so important that you really help like incubate the talents that your children have. Like a lot of the times, you know, if the kid is talking a lot, it's easy to say like, you know, be quiet and kind of try and silence them a little bit. But you have to like, encourage that curiosity, and like that want to know more. And I'm really thankful that my parents like pushed me to ask questions and pushed me to talk. So I never felt like these were these were negative things like I felt like this is something about myself that I should, I should work on and continue to do. And so I'm just very appreciative of them for doing that. That's amazing. That's amazing. So many key things you said in there. But it all accumulates to you having this superpower now that you're that's your parents. Is that something you noticed along the way, given that I mean the number one fear for a lot of people is speaking in public. You know, you're talking in intimate situations as well. I mean you realize along the way that this is a superpower. Yeah, you know, I think there's something I would say I think people have like their talent, but then they have whatever their gift is, you know, and I think that, you know, maybe the talent is like journalism or interviewing but I think the gift is like making people accountable, you know, are like being warm and being welcoming I think I think people feel like they can trust me. And I just feel very lucky that I'm able to make the thing that I feel as my gift, also my job. I think it really is like a superpower I know we talk a lot about okay like knowledge is power which it is. But I think that really knowing how to deal with people is one of the biggest powers you can have like if you know how to navigate rooms and you know how to connect with others. You learn what makes people happy it makes them sound makes them light up like learning how to read a person. I think it's one of the the greatest things that you can have on your side as you go through life. What are some of your favorite interviews slash conversations that you've had on your career. So many I mean like, I know it's cliche but I love them all. All your babies. Yeah, they're literally it's like choosing a child no. I first of want to say I'm always so just like thankful.  So I'm so thankful for anybody that just decided to do an interview with me, but I think my interview with DeMar DeRozan always sticks out. Now the interview I do with Candice Parker always sticks out I really enjoyed that. I also like interviewing people that don't do a lot of sit down types like job doesn't do a bunch and we've done like for this point he's always very open in them. So I like that too. This wasn't on my show but I got to like interview Barack Obama for eight minutes and I was like this is the greatest thing ever. Barack Obama. But yeah I think DeMar and Candice really really stick out especially because with DeMar I was interviewing him at a time that you probably didn't want to talk to many people because he was with the Spurs the Raptors were about to win the championship and the whole narrative is like they were able to get there with Kawhi they couldn't get there with DeMar like there was just so many things to talk about, and he was very open and I think same thing with Candice she was, she was really candid about that her relationship or lack of with you know Oriama and it was just really nice to really dig deep in those conversations. Yeah, she has some quotes. Yeah, yeah, it was getting hot. He was hot and Alan.  And I don't know that there's something you can teach that something you have in you there's a aura about you. You know, that great interviewers like yourself, conversations like yourself has have comes from being a good person with good intentions. I talk about that with folks, you know, getting in the field and being a good person is just a basic thing that kind of gets lost. Totally. Yeah. On a human level is something that the people that you get to talk to, they connect with without even maybe vocalizing it. Yeah, I mean, thank you. I mean, I would hope so. I think the number one thing you can do in this business is just be good to people. And that's not even in the business that's just in life. I don't know why anybody would be the opposite of kind to a person. And I think that in media and maybe specifically with interviewing two people know whether to believe you or not. You know, I think especially players like they have gone their whole lives with people, maybe having ill intentions or wanting to like catch them up in something or wanting to use them in some way. So I think it's very clear to them when somebody is genuine, and just wants to get to know like who they are. I think with interviews like I genuinely never try to have like, gotcha moments or get them caught up or like get a headline. I think that the best stuff just comes from being inquisitive like it just comes from asking why, you know, we're having them expand on things. I think that's like what's actually meaningful within interviews. So I would hope that at this point I've created a space or people understand that I might have to talk about something like I don't necessarily want to. But I'll talk about it in a way that I am being heard, not in a way that I'm like being judged or being tricked. And I think interviews really are better when it is that way and a lot of that does just spur from like wanting the best for people wanting to be kind of others wanting them to have good experiences with you and with your show. So that is absolutely the goal so I'm, I'm very thankful that you you feel that way. I think the toughest part of this business, or the most trying part of your journey. It's really good question was trying part of toughest. I think I'm, I know I'm much better at this now, but you certainly deal with feeling like you're consistently having to prove that you deserve or like, or that you're good enough. I think you're really young and for me I always say I think my life moved like really quickly like right when I graduated school, I was working a bit to network so I'm like this 21 year old doing this live show five days a week and I was kind of thrown into the fire, both at work but then also like personally like what it means to be like a journalist and like this public facing person. I think sometimes when you're young you're hearing people like say things about you that maybe you like don't agree with, but you hear them so much that you're like, is this true.  And I very like quickly had to learn that like knowing who you are at your core is like the most important thing that you can know, because it can be very trying when so many people are trying to tell you who you are and you're like wondering whether that's right or not. So I just think. Yeah, I would say, I would say being able to cancel out what anybody has to say about you is like the number one thing you have to be able to do because that can be difficult having to hear about yourself all the time. I'm not going to explain that correctly. It's absolutely true and it happens on, you know, on different levels and as your star has grown I'm sure it's gotten louder and louder. And that's you have to put those earmuffs on and as you said, you are remember who you are. You have to navigate through, you know, in this industry. I, I heard you mentioned this in an interview once and somebody told you, you can do anything, but you can't do everything. Yeah, and that reminded me of story when I was in Indiana I was doing, I was key announced for the Pacers I was doing radio show doing TV. And I was doing everything. Yeah, I would say that I was feeling myself but I was feeling pretty good and I grew up and even have listened here I was, you know doing these different things and I remember before Pacers game and walking on the court and Quinn Buckner does TV for the Pacers and he called me over. And he says, no, it's pretty good, but you got to pick one. And I just kind of hit me like, wait a minute, I'm doing everything like this. Who does everything who does all these different things. But he was, he was giving me a lesson then that it took me a little bit for it to resonate to narrow that focus a little bit still do multiple things but narrowing. Yeah. But how did you can do anything but you can't do everything how did that resonate. Oh my gosh in so many ways and it's like, I mean you know I think we have this. We have this idea that like we have to be able to do it all like to be worthy almost like you want to say like, I want to be your place both of I can do this I can also do this and I can do this and I can do this. But there really is a power in learning the thing that you're best at, and like trying to hone in on that specifically, like being the best act that thing is really really important. Obviously you still want to be versatile at that moment comes or somebody does ask you radio you want to have the ability and capability to do that but if you say no you come to me to do this, and you perfect to that. And there's just like something important about knowing what you are great at honing in on that. And so yeah when someone said that to me I was like well what do I think is, what's my lane like what can I excel at. And I realized the thing that I thought I could excel at was also a thing that made me feel the most purposeful which was having these actual conversations and focusing on interviewing specifically. I didn't feel as fulfilled like doing sideline I didn't feel as fulfilled like hosting I think those are obviously like amazing things to do but I was like I don't know like am I, my like a host in a way of like being with others and facilitating or do I just like want to ask questions and talk for an hour. And for me it was asking questions thing. So I really tried my best lunch I realized the thing that made me feel fulfilled, like making sure every decision I made like was on that trajectory. You know the thing you're good at, you make decisions to be able to do just that. But if you can do everything. Or if you're doing everything that path is so scattered, because you can go in so many different directions and I just work better when I have like a very specific plan that I want to make decisions towards.  Do you remember when that moment was when you noticed you're being recognized people are complimenting your work. Yeah. Um, I always say like the thing I think about is it was all star and Charlotte, like, what was that maybe like four years ago. Yeah, I was all star and Charlotte, and like dream bill did an event. And I went to it was like a brunch or something. And I went to it. I remember J Cole had seen my interview and I remember thinking, Oh my goodness, J Coles interview like I'm such a big fan of music.  But it's always I love whenever like if I'm on the street and someone says you know I really enjoyed this interview or like what you do and I will sit and have conversations like what did you like what was in your life because I think talking to the viewer about it is important too because you know you want you want to ask questions that the viewer wants to know that's the whole point. I'm just I'm really appreciative of anyone that has watched an interview, even if it was for one minute. That just makes me happy that the work resonates with people. It's amazing I grew up and was watching inside stuff with a modern shot was an athlete himself and he brought the human element out of these NBA players he was interviewing also understanding that their life is 24 seven basketball. There are other things outside of the sport so being able to connect with them on a human level on other interests, and you know it just really inspired me watching with a modern shot was doing to talk about I talked about representation a lot on this show, knowing that I don't know how often you think about it, but you're having an impact that you know people are watching their young people watching and seeing what you're doing and saying, I want to do, I want to do that, you know what is representation I mean I, I think representation really is everything in so many different ways. I read this book once got heavy by KSA lamb that's one of my favorite books and he's like my favorite author but in it, he talks about how you know, growing up, he could turn on any show whether it was a soap opera or if it was like prices right or if he was watching sports and he saw like white men that were like prices he could turn on anything, and he could see white people but not only could you see white people he was able to see all different types of white people white people were very heavily represented to him. What I use in the book is that representation the way that it's important for people that look like you, it is almost as important for people that don't like we have to show that black people are not a monolith to people who maybe don't have black people right next to them in their everyday lives. The responsibility I have is to people that look like me specifically black women you know black men, but I think it's also important to show who we are to people who don't know, because we don't have unfortunately that wealth of options that we see in the media of black people in a specific picture of black people is painted a lot of the time. So I think it's it's just very important to show the wide array of blackness the wide array of black people whether it's their interests the way that they have grown up, you know what they're into what we'd like to watch what we do like that's very very important to me. But I would, I would also say to any like young black woman that wants to do this, that we are truly exactly alike, like I think everybody is the equal amount of special. I don't think that I am more special or more talented than somebody that isn't doing this. I think that I have had things on my side I have had advantages I have had advocates I have had a lot of luck. I think I think everybody's value is incredibly constant and everybody's value is the exact same. So, I think sometimes we were young and we're looking at people that look like us doing the thing we want to do. We think it's because they are more special than us and that then makes them feel like it makes them feel like what you're doing is unattainable. But that actually isn't true. I am an incredibly attainable person because I am exactly like everyone else, right. So I think that's, that's the main thing that I think about about representation is just like, everyone is the same like I want every black woman to feel like they can do everything that they see every other black woman do, because that really is the truth. And I just to piggyback on what you're saying. I also love seeing that I think it's, I think a lot of people enjoy seeing everybody cheer each other on. And this media is kind of dog eat dog and only so many people can be in this space.  And to see you pumping up someone else or enjoying time out and you know group pictures with people who are all in the same industry and showing kind of that love that that sisterhood that whatever it may be. I think that that's huge. I think that that's huge also. For sure. I mean, it honestly makes the job more fun like, I love being friends with people in the business like I don't believe in this idea of like it has to be cut throat.  But since we're all a part of that system, it tricks us into thinking that the person across from you is the issue. But really it's like no, there should be room for multiple women at this station, or multiple black people, like we, you end up fighting each other when you should be fighting whoever is making like these, these decisions if that makes sense. So I don't see any of my peers as somebody that I should not enjoy or be friends with or root for, because I just want to eventually there to be a time where everybody knows there is more than enough space for all of us to co exist. I know we talked about interview the conversations or would not and we started with your, you know, the nomination. What is the most rewarding part of your pockets. I don't even ask that's a good question. The most rewarding part of the podcast. I think it's two things. I think number one I take a lot of pride in being a trusted person for athletes who I'm sure feel like they can't trust people like I take a lot of pride and people sitting in that chair and thinking they can talk about things and maybe they don't want to. So I think the, the trust aspect is very rewarding for me. And then secondly, I like I love nothing more than when somebody is like, if never saw this before but and then they start saying something so it's rewarding for me to when like people get to like reveal things right there's like a moment that happens on it that nobody that always like really makes me happy because you know like that's a point of interviewing you want you want them to say something that they haven't said. So I just, I like that people feel like they can talk about things maybe they haven't on the show. And you know excited about watching throughout the NBA playoffs and every time those interviews dropping and looking forward to it. What is next what's the future hold for Taylor books. Oh my God I hope so many things you know I want, I wanted all I want to be able to interview whoever I want if you have something to say like you think about doing it with me. That's what I want I think that for for me the future is like, it's a feeling and a concept it's like, I know what I'm going to get when I watch her interviews like I want. That's like what I ultimately want to do. There are so many things I like need to get better at and want to get better at. There's so much room to grow. There's so many like things I don't know about sports that I want to learn more about I want to push myself to do more interviews. I really want to do a live interview to that's something I've been talking about. So there's a lot like I just think for everybody all the opportunities are endless so I want to I want to grab things as they as they come my way and just just keep getting better. It's been amazing watching your journey and in all that the future holds thank you so much appreciate you.


Hi, everyone. I hope you can hear me. So we still have a few more minutes. So before I start, just wanted to get a feel about what people in room, what they normally work on. Do we have many other software programmers here? That's great. Many people focus on security, or people who focus on security. OK. How many of you have used ARM CPUs? Oh, that's nice. How many of you have heard of trust zone? OK. You're going to make my life slightly easier today. Hello, everyone. Hi. My name is Ashutosh. I work for ARM. I am a security architect, and I take lead with all the trusted firmware projects from ARM. And today, I'm going to be talking about some of the challenges that we face, security challenges that we face in the connected devices in this industry. I know every use case is different. Every device is going to be different. But there are some common underlying challenges that are going to be solved for all of these different use cases. So I'm going to talk about some of these security challenges. Then I'm going to talk about some of these common security functions that are needed to solve these different security challenges. Then I'll briefly talk about platform security architecture and trusted firmware project. When I initially submitted this talk, I was thinking I'll have enough time to talk about different workflows, and then we'd go in depth on different technical solutions. But then I realized I'll only have 35 minutes. So instead of giving solutions or talking about solutions, I'm only going to talk about problems. So security challenges. Let's first look at the supply chain model. This is a very simplified model. This is a very simplified view of how supply chain works. You'll typically have a silicon vendor that collects all sort of different hardware IPs and build a SOC. Then you have different OEMs. They would license the SOC from the silicon vendor and then build a device around it. Now, the different steps involved in the supply chain. Again, this is a very simplistic view. It gets a lot more complex and individual cases are completely different. But this is a very, again, simplified view of what happens in different stages. When you talk about the silicon vendor, silicon vendor would want to install some secure operating system. Void is required. I'll try to cover that in one of the latest slides. Silicon vendor would also want to provision some secrets, some cryptographic secrets, so it can have some control over the device in the later stage of the lifecycle. And devices could have some hardware or software IPs, where the silicon vendor might want to let OEMs use those IPs, but not necessarily let them see those IPs. So for example, if you have a software Bluetooth stack, it's very common for vendors to define APIs to let people use those Bluetooth stacks. But they normally don't want to share the code base, not even in binary form. So silicon vendor would want to protect those hardware and software IPs in one way or the other. Similarly, when you go to the next stage, when OEM is trying to build a device, what OEM normally does is build a system around the silicon, attach all sorts of different peripherals, and create a system based on the use case they're trying to solve. And they will have to have a similar kind of, they'll have to do similar kind of provisioning as well on their side. They might want to install some secure applications. So let me see if I can get the pointer here. So they might want to install some secure applications, which has to work with the Trusted OS. And at the same time, you don't want to completely expose the Trusted OS to the OEM stage here. And the OEMs will have their own secrets, their own cryptographic assets to provision on the device. And finally, when you talk to the OS vendors or when you want to install a rich operating system, you need to have some sort of agreement with the OS vendor to be able to use their operating system on your device. And they would want to provision some of their own secrets as well, some cryptographic keys or TLS certificates, TLS, if you're doing PSK TLS, maybe the key itself. Now, when you look at this supply chain model, there are many security challenges here. You need to be able to securely inject the Trusted OS system so no malicious code can actually run on the secure side on your secure domain. Basically, you have a lot of secrets there. You will have a lot of keys, protected IPs, so you don't want to run any malicious software. The code that you inject there need to be verified. You need to ensure that it's not coming from some malicious place. Similarly, when you do the provisioning of the device, the provisioning will have a lot of secrets. You have cryptographic keys, your device certificates. And when you provision that on the factory floor, those secrets will get exposed to everyone on the factory floor. And you don't want that to happen. So you don't want that to happen. Because once that has leaked, all the secrets are leaked, your device is completely compromised. Similar challenges are there when you move to the next stage. OEM will want to provision their own secrets in a secure way. They would want to ensure the integrity of the software they install. And at the same time, two different OEMs wouldn't want to trust each other. I wonder why. And you need to have a secure way of installing the rich operating system. Traditionally, this has been done using secure facilities. So if you want to provision your device in the Silicon vendor stage, then Silicon vendors will have some secure facility where you have physical locks and keys, and only certain people are allowed to go inside. But in a globally distributed supply chain model, that doesn't work very well. It doesn't scale very well. So we need to find better solutions that scale very well. When you talk about the trillion devices, when you talk about trillion connected devices, you can't have physical locks and keys to protect these kind of supply chain attacks. So as a promise, I'm going to talk only about the challenges for now. Now your device is provisioned. You have gone through the different lifecycle stages. And your device is in the field. Each use case is going to be different. Each use case will have its own quirks, its own security requirements. But if you analyze, if you look now at different connected devices use cases, they will all have a set of common usage patterns. They will all need some form of connectivity. The connectivity could be between device to device, or it could be between device and the cloud entity. They all will have to deal with some sort of data. The data could be a biometric data if you're doing financial transactions, or it could be a DRM content, or it could be just sensor data in your home, or it could be industrial automation data. They'll all need some sort of device management. All of these different use cases will need some sort of common device management use cases.  How do you report that? These are common challenges. Doesn't matter what use case you're building. These are common problems, common challenges. And finally, the multivendr supply chain that we already talked about. All of these different use cases or use case patterns have their own security challenges again. When you talk about the connectivity, the connectivity is usually over a non-secure physical medium. So you want to establish secure communication over a non-secure physical medium. Even if you ensure that, even if you establish a secure communication over a non-secure physical medium, you still need the devices, the communicating entities to trust each other. The communication itself might be secure, but I might be talking to a malicious actor in first place. So how do you establish the trust between the communicating entities? On the data management side, you will have to deal with sometimes very sensitive content. If you're talking about the DRM use case, you don't want the device or a malicious actor to be able to get their hands on the decrypted content. For example, if you have a Netflix subscription, Netflix wouldn't want that content to be freely available to everyone without paying for it. So you need to have some sort of protection on the content. Similarly, for device management, you need to be able to sometimes remotely provision the device in a secure way. So you have some level of control on the device. And you should be able to secure firmware updates if something goes on the device. So when you build a device, it will have, eventually, it will have vulnerabilities. No matter how much effort you put in designing your hardware and software, eventually, someone is going to break it. Someone is going to find a flaw in it. And you need to be able to patch it. You need to be able to basically, if it's a software flaw, then it's easy. You update your software and then you're good. Sometimes there'll be hardware flaws, hardware vulnerabilities that you need to find a workaround about and fix that in the software. So you need to have a secure way of updating the firmware. At the same time, you don't want to be able to roll back to a previous version of the firmware, which had vulnerability in the first place. When you look at these different security challenges for all the different connected devices, there are some common security building blocks that apply to all of these devices. All of them need to have immutable root of trust. What this means is this is the very starting point of your system. This is the, you could say, probably the most trusted part of your system.  This is the very starting point of your security in a system on a device. That leads to the next stage, which is chain of trust and software integrity. You need to be able to prove your software all the way starting from the boot ROM code to the application that you are running maybe on top of Linux. So the whole chain need to be able to be verifiable. Principle of least privilege. This is an interesting one. What this means is in a given system, you should give only just enough privileges, just enough access to any part of the software so that it is able to perform its job. Nothing more, nothing less. What that means is if there is a vulnerability in one part of your system, that doesn't compromise all of your different parts of the system. By the way, if you want to stop me on the way or ask a question or heckle, feel free to do so. Software updateability, we already talked about it. We all know, and I just talked about that as well, why we need software to be updateable. Device identification and authentication. You need to have a secure way of establishing the identity of the device. So when it communicates to another entity, the other entity can put some level of trust on the device. So it knows which entity it is actually talking to. And finally, lifecycle management. So lifecycle management is about when you move through different stages of your production. You compartmentalize that as well. So this is kind of extension of principle of least privilege. You extend the same concept in the supply chain flow as well. So if you are in the silicon vendor stage, then you get to access certain parts of the system, certain hardware keys. When you move to the next stage, the OEM stage, OEM gets to access only certain part of the system. So you have some sort of hygiene on the system. And different entities in the supply chain don't end up compromising each other. So a bit more detail about different building blocks. I'll try to cover this as fast as I can. Root of trust and chain of trust. A typical root of trust looks something like this. You will have a ROM code, which is your starting point in the system. ROM code is something that you would put as part of the RTL itself. So when the device comes out of the fab, it will have the ROM code. It will have some RTL key as well, which is known only to the silicon vendor. And that RTL key forms the basis of your rest of the provisioning security. The next stage in the chain of trust would be a richer bootloader. Arguably, you could put the immutable root of trust and the updatable bootloader in the same place. You don't need to have updatable bootloader if you know how to write perfect software. But we are not. We know that we are not perfect software engineers. We make mistakes. Or sometimes we write perfect software, but mistakes. And by hardware engineers, any hardware engineer here? No. OK, so it's safe to say that hardware engineers also make a mistake. So what happens is, since the first part of the chain of trust, this is going to be part of your RTL itself. You can't change. Once it is in the RTL, it's there. You can't change it. And so if you put a lot of software here, a lot of complex software and a lot of complex logic here, then you run a risk that if someone finds a vulnerability, you can't do much about it. So usually, a really secure system, what it would do is have a very simple ROM code. As simple it can actually deal with. And all of your richer functionalities, your firmware updates, your rest of the system's chain of trust, that functionality gets pushed out to a updatable bootloader. So if you find a flaw in that implementation as well, you can still update it. Finally, your runtime software. Runtime software is your business software where you would have what not, could be Linux, some file system distribution, and your business software. Principle of least privilege. I'm going to rush a bit because we don't have a lot of time. Principle of least privilege applies to hardware and software both. As I said, each part of the system should have access to just enough resources so that it can do its job. This concept also extends to cryptographic keys. When you do deal with different cryptographic keys, it's quite tempting to use the same key for different use cases. But from the cryptographic point of view, that's a very poor implementation. There's a very poor use of your cryptographic functionalities. What happens with that is, if one part of your system is compromised, it will end up compromising all of your system because you're going to use the same. If you're using the same key for every single use case, so you need to have some sort of cryptographic key hygiene as well in your system, one key for one specific use. Similarly, for my update, we talked about it, why we need it. It's encouraged to have a certificate-based image authentication so that you don't put a lot of secrets on the device. It's possible to do a symmetric key-based image authentication, and it's typically faster as well.  So typically, in most of the cases, it's better to use a public-private key setup where you just have the public key on the device and store that in a immutable way so no one can change that key on your device and use the private key to sign the images and authenticate that on your device. And rollback protection, again, if you don't have the rollback protection, basically, firmware update kind of becomes pointless because if you go to the next version of the firmware which fixes some of the security vulnerabilities, an attacker can try to rollback to previous version which had those vulnerabilities in the first place. Device identification and authentication. This is highly linked to the trust establishment between two entities when they're two communicating entities. They need to be securely identifying each other. So they need to carry a identity. And that identity need to be proven, need to be proved using a certificate. And finally, attestation. Attestation is a kind of report from your device that could go to the server. And it will contain information like what version of software you're running, what version of secure firmware is there, what's your bootloader, what's its geographical location. So based on that, server can decide how much trust it should put on that particular device. For example, if the report, if the attestation report says this is a old firmware version which had security vulnerabilities, what server would do, or the cloud entity would do, is say, fine. You have this old version which has security vulnerability. I'm not going to let you do anything more than just the firmware update. So until you give me a report which says I have got the latest, greatest firmware running on the device, I'm not going to let you do anything useful apart from firmware update. Again, life cycle management. In the life cycle management, you would have a silicon manufacturer. They will, if you want to do the secure provisioning of the device, you need to have the RTL key in the system. RTL key in the system. So that allows you to basically not rely on physically secure facilities for provisioning the device. Also, most of the silicon vendors, what they do is create the same device, distribute the same device to different OEMs, but control feature on the same family of the device based on different licensing models. So you create the same SOC, but create different licensing models, different proof points based on who is ready to pay how much and what they actually need. And those things, you would want to be able to control in a secure fashion because it's directly linked to the revenues. The next stage of the life cycle, again, is OEMs or application vendors. They would, again, want to provision the, actually, I'll come back to this, the life cycle, because I'm going to talk, at least I'm going to talk about one solution today, which is about how do you solve the supply chain problem. So let's skip this one and come back again. When we look at the different security functions, to support those different security functions, there are certain hardware building blocks that are required. Immutable route of trust, we talked about that already. We talked about the device identity as well. And this need to be immutable so no one can come and change those device identities. Hardware unique key, this is an interesting one. Hardware unique key is, as the name says, you need to have a unique key on each device. Not each type of the device, but on each sample of the device, you need to have a unique key. So you can bind the file system on that device to that specific device. No one should be able to take out the flash and put that on another device because then you have all the gray market attacks linked to it. Non-volatile counters, this is where you would want to fuse the non-volatile counters. This is where you would want to fuse the firmware versions. So if a rollback attack happens, it can easily be verified at the boot stages. And you can check against it. You can predict your device against the rollback attacks. Similarly, harder isolation support to support the principle of least privilege. So you can compartmentalize your system in much smaller segments. Root of trust keys, these will form the, they will be part of your chair of trust. So you need to have them in the device in a secure fashion. And crypto accelerators and lifecycle management as well. Crypto accelerator, I'm going to skip talking about. Life cycle management is, again, an interesting one because to prevent all sort of supply chain attacks, you want the lifecycle management to be unidirectional. Once the device has gone from the silicon manufacturers phase to the OEM phase, this should be a non-reversible process. Because if it is, then OEM could do the reverse engineer, try to get all of the silicon manufacturers secrets, and that open spandora's box that would lead to OEMs compromising each other and all sort of different problems. So as I said, I'm going to talk about at least one solution today. As I said, it's perfectly OK to have a physically secure facility to do the device provisioning. It doesn't scale very well. Alternatively, you could find the trusted operating system using the RTL key. Remember, we talked about the RTL key that you would have baked in in the silicon itself. So you could find the trusted firmware, the trusted OS, using a RTL key. And now you can distribute that binary to your provisioning facility, and it could be anywhere in the globe, because now it's signed and encrypted. So it doesn't matter who gets their hands on these trusted operating systems, and the rest of your provisioning assets is encrypted. And only your device will be able to understand what actually it is. So you sign and encrypt the content using RTL key. It goes on the device. Device will be able to decipher that content, because device has the RTL key. It will allow provisioning of the secrets and the trusted operating system that you want to install. And from the silicon vendor point of view, you're safe. Before moving to the next stage, what silicon vendor would do is create a OEM provisioning key. So there's a bit of a complex challenge where you need to solve this problem operationally, as well as technologically. Silicon vendor will create a provisioning key for the OEM, but it need to somehow transmit that key to the OEM. They need to establish some operational mechanism, maybe sign and encrypt using PGP, and they need to set up some operational communication between the silicon vendor and the OEM. But the point is silicon vendor will have to provision a OEM specific provisioning key and change the lifecycle stage from silicon vendor to the OEM stage. What this means is now OEM has this key acquired somehow through operational mechanisms. And lifecycle stage has gone to the next stage. So the silicon manufacturer is now assured that no matter what the OEM does, the silicon manufacturer's secrets are safe. Again, OEM signs and encrypts its own content using the OEM key. Before moving to the next stage, we need to provision the rich OS signing and update key, and then change the lifecycle stage to the finally deployed state. What this means is your device is provisioned, and you can let it go in the field and do its job. The key point here is the key that gets generated here, OEM provisioning key, is going to be different for different OEMs. So even if OEM2 somehow gets their hand on this encrypted blob, they can't do much about it because this encrypted blob is going to be understood only if you have the corresponding provisioning key. Any questions so far, or anyone who doesn't think this is the right thing to do? All good? Platform security architecture. Platform security architecture is an initiative from ARM to drive some sort of standardization around security, device security in our industry. So far, everyone has been left to fend for themselves, and there have been so many competing mechanisms and specifications. ARM is trying to bring some sort of standardization around security, device security, so that it's a problem that we could solve in one place rather than everyone trying to solve the same problem, spending parallel and duplicate efforts trying to solve the same problem. Platform security architecture is a collection of a lot of generic specifications. It has, in most of the cases, is quite architecture and hardware independent. What it does is it specifies security properties that you need to have in your system. If you are building hardware, hardware need to have these different hardware building blocks with these different security properties. If you are writing software, the software should have these different kind of security properties. Now, whether you use ARM IPs to get those properties, security properties, or you build your own IP or license it from someone else, that's a different story. At the same time, we also provide implementations, hardware and software implementation, that comply with these standards. So if a device maker want to make a device, they can quickly get on to building the device using the baseline security that has already taken care of. And they could focus on their business software, rather than worrying about the security from scratch. Of course, that's a very simplified statement. There will be some security work to be done by our partners as well. If you're OEM or if you're a Silicon manufacturer, there will be some security-related work that you need to do. But as long as we are able to solve the problem in a common way, then we are setting ourselves for a future where we don't have to reinvent the same thing again and again. Trusted firmware, M, is implementation of PSA for Cortex-M devices. It provides firmware implementation. So it provides all of the secure-sized software as well. So you don't have to spend a lot of time reinventing the software is it already takes care of all of the different security properties that I talked about. It provides all of your security endpoints as well. Some of the security endpoints as well, things like attestation, secure boot, your cryptographic derivatives that you may need on your system. And then you can go on and build your system based on this. TrustedFarmware.org, this is, again, initiative from ARM to move to a more collaborative environment, where instead of arm trying to push, saying that this is what you have, this is what you should do, try to get more people on board, try to get more people, more companies on board, and have a collective thought about how this should be done in terms of how do we solve these challenges in terms of technology? How do we solve some of the operational challenges in getting there? And collaboration is always good. Collaboration would mean that we can solve the common problems together, and then everyone else can focus on their specific business cases. So the TrustedFarmware project now, as of now, is not a ARM-owned project anymore. It's a collaborative project. It's hosted by TrustedFarmware.org. ARM still has a very big stake in this. We have quite a big development team there. We are still the biggest contributor there, but we want more people to get involved. To get involved, you don't have to be part of the TrustedFarmware.org board. So there is a board, basically, where companies can pay and become part of the board. And that board decides the general direction of the travel for the project. But to contribute or to participate in the project, you don't need to be part of the board. Literally, anyone can just go to the TrustedFarmware.org, create a GitHub ID if you don't have one already, and start contributing. That's all I had for today. Any questions? Yeah. Under what circumstances the bootloader doesn't become trusted? So if you have built your system, if you have followed the rules of a chain of trust, then even if your bootloader is trusted, it may still have vulnerabilities. So it's not about whether your software component, be it bootloader or any other software component, higher up in the chain. It's not about how trusted or how untrusted it is. It's about how mature it is. So even if it is trusted, even if you're talking about the trusted OS, which is the ultimate root of trust in your device, even if it is trusted, it doesn't mean it will not have flaws. It will not have security vulnerabilities. So it's more about being able to identify the security vulnerabilities and be able to fix those vulnerabilities rather than saying whether a part of the system is trusted or not trusted. So bootloader usually forms the chain of trust. It's part of the chain of trust. So you would typically impose a lot of trust on it. It is a trusted component. Is that what you have been asking? Or OK. Any? So this is where the hardware need to be able to back that up. It should be a non-reversible process. What that means is your hardware should have capability to identify that it has gone to the next stage. Typically, how you would do is burn some fuses, some OTPs or some other fuses. And burning those fuses will signify that the device has gone to the next stage. Typically, hardware itself will mask off the assets belonging to the previous stage, so you can't go back. Burning fuses is something you will probably have to do in the factory to make this transition from one stage to another stage. There is element of trust. So the trust flows in one direction here. OEM has to have some level of trust in the chip manufacturer. But the chip manufacturer doesn't have to have any trust in the OEM itself. You could potentially solve that trust issue, but that requires a lot of redundancies in the hardware itself. So it's a balancing act there. You could say OEM doesn't want to trust at all the silicon vendor, but how much are you ready to pay for it? So this architecture focuses on open standards like SIBO and COSE. They specify how you architect your attestation token and how you sign it. So as long as you are compliant to SIBO and COSE standards, you're good. At the same time, it's a open source project. So if there is some tailoring that you need to do for your specific use case, the trust-afirmware project doesn't really stop you from doing that. It's a open source project with permissive license. It's a BSD licensed project.  Any more questions? Thank you, everyone, for coming here today.


One of my favorite Linux distributions is Debian. It is a fantastic Gnu slash Linux distribution It's been around forever. It's one of the oldest actively maintained Linux distributions. It got its start in late 1993 so it's been around for a long time and Debian is also kind of like the grandfather Distribution because so many other distributions base off of Debian because it has a fantastic repository of software a huge repository of software where It's hard to to find a piece of software that's not in the Debian repos And that's one of the reasons people run Debian the other reason people typically run Debian is because of how rock solid stable The main Debian edition is matter of fact the the real product that they push is actually Debian stable Even though they have three different branches. They have stable testing and unstable You're gonna have a hard time going to the Debian website and finding an ISO for Debian testing or Debian unstable The reason you're gonna have a hard time finding those isos those isos don't exist Debian actually doesn't want people running the testing and unstable branches because those are rolling release branches And obviously things can break when you run a rolling release distribution, but I like living on the edge, right? I like running rolling release distributions like arch Linux and arch based Distributions that's kind of what I've lived on here in the last couple of years So if I was gonna install Debian on any of my personal machines I probably would use the unstable branch and today I'm gonna show you guys how to get Debian unstable installed So let me switch over to my desktop and let me get to my web browser Now the Debian website is very confusing They have a lot of different isos on their website But it's really weird how you have to navigate through a ton of different pages to grab an ISO But what you guys want to do if you want to install Debian unstable go to the Debian unstable page in the Debian wiki I will link to this in the show description And if you scroll down you have installation and they tell you three different ways you can install Debian The recommended way is to install Debian stable and then change the app sources So they're pointing to the unstable repositories and then do a full system upgrade So you update all the stable packages to the unstable packages. That's the recommended way I don't like doing it that way because Why install Debian stable and then do a massive update to install all the unstable packages Why not just install the unstable packages directly? And that's what I'm gonna do and it's the section here use the unstable mini ISO image so what you want to do is you want to grab the mini ISO from the Debian mirrors and It's listed under Debian slash dist slash unstable slash main slash installer slash current slash images slash netboot That is a very very long path. I would have to navigate here Through this first. I would choose a country. I am in the US.  I forget the full path and just unstable okay, we keep going down to unstable and Then main looks like I've been there before Installer dash amd 64 because I'm on a 64 bit system and then current and then images And then netboot And then mini.iso that is the image that you want to download now My problem with this mini.iso is I'm looking at the date and the last time that this was released was the 6th of june And right now it is july 30th. That's two months old that mini.iso and because we're installing a rolling release I don't like doing a two month old ISO. So what i'm going to do is i'm actually going to go to their daily images So if you go to d-i dot debian dot org for daily images go to daily images and follow the same kind of path I'm going to do amd 64 daily Netboot and here is mini.iso and that's the one i'm going to grab And i'm going to go ahead and install debian inside of virtual machines So what you want to do when you first boot into the mini.iso instead of choosing install Don't choose install because if you just choose install you're going to get the standard debian installer that installs debian stable because that's what they expect Most people to actually want but you want to go to advanced options and go to expert install and this is going to launch a in-curses installer But don't worry that it's an in-curses installer. It's very very easy to navigate this installer So the very first thing choose language just hit enter and by default it selects english That's correct for me if you needed to change the language of course you would navigate through the list and then hit enter on your language, but i'm just going to hit enter And choose country or territory. United states is already selected. So i'm going to hit enter Country to base default locale settings my locale should be united states as well And do we want to add any additional locales? I'm okay with just the one locale So i'm going to tab to get to the continue box over here Let me move my head out of the way so you have continue here And then we just go to the next part of the installation So the next step access software for a blind person using a braille display. I won't have any Visually impaired people using this virtual machine. So i'm actually going to skip that step I'm just going to arrow down to the next thing here, which is configure the keyboard. I'm just going to hit enter Keymaps american english is the default. That's correct for me. So i'm just going to hit enter Detect network hardware. I'm going to hit enter and do we want to install a usb storage module? That's ticked on by default I would just leave that ticked on then I would hit tab to get to continue and hit enter The next step is configure the network just hit enter and it asks you do you want to have debian auto configure networking? Absolutely. So just hit enter and then it's going to say waiting time for link detection The default is three just leave it as three tab to get to the continue button and hit enter This will take just a few seconds to configure the networking Next it asks you to enter a hostname. So this is the hostname of the computer by default is chosen debian I'm just going to leave it as debian and then we need to enter a domain name Now obviously we only need really a domain name if this is going to be like a web server I'm just going to hit tab to get to continue and I'll just leave the domain name blank Now choose a mirror of the debian archive. So let me hit enter This is of course syncing some some mirrors so we can actually download software. How do we want to get this? Do we want to do it over http https or ftp? The default is http and they say it's less prone to problems such as If you had a firewall installed or something. So i'm just going to leave it as http So i'm going to hit enter and then it asks what country we're in. I'm in the united states So it'll show us mirrors inside the united states by default deb dot debian dot org is selected for us I'm okay with that. I'm just going to hit enter http proxies i'm not using a proxy So i'm just going to tab to get to continue and hit enter Then it says debian comes in several flavors. So we have stable testing and unstable I'm going to arrow down to the SID branch, which is the unstable branch and hit enter Then download installer components. I'm just going to hit enter on this and then it gives us a bunch of extra Installer related stuff that we could add if we needed it But honestly most people are never going to need any of this stuff This is just extra Installer components to use during the installation process if you needed to for example, there's modules for SSH I guess if you were installing debian over SSH and things like that I'm just going to hit tab to get to the continue button to move forward here And now we get back to the menu and this time the menu Has more things in it because now we have the option of setting up users and passwords and things like this So let's go ahead and set up the user and password it asks us do we want to enable shadow passwords? Yes is recommended. So I will choose yes Do we want a root user and do we want to allow the root user to actually be able to log in? That's okay for me So i'm just going to hit yes And now we need to create a root password for the root user So let's create a strong and complicated password for the root user and then tab over to continue Then re-enter that strong and complicated root password and hit continue Now it asks us do you want to create a normal user because you don't want just the root user because It's dangerous to do everything as root. You need a normal user. So definitely create one. So i'm going to hit enter I'm going to call my New user my normal user dt and then i'll Tab over to continue the user name for the account is dt And then we need to create a strong and complicated password for the dt user and then tab over and then Re-enter the password and tab over and then configure the clock just hit enter set the clock using ntp. That is okay And it's asking about the ntp server just use the default and then select the time zone I'm in the central time zone in the us. So I will hit enter on central Detect disc just hit enter and it should detect your physical disc in your machine for me I'm using a virtual machine and there is one virtual disc in this virtual machine Then it asked about partitioning the disc so hit enter on that And now we get the standard partitioning screen that you guys have probably seen and things like the ubiquity installer the calamari's installer What do you want to do with your partitions? Do you want the automatic partitioning? Which is the first option use the entire disc? That's what i'm going to go with but if you wanted to you could go down here to manual partitioning and do it manually yourself I'm just going to let dibby and do its thing. So we're going to do The entire disc and it's going to take up the entire 20 gig hard drive virtual hard drive in this virtual machine I'm going to hit enter on that then it asks us Do we want to create a separate home partition in this virtual machine? That would be unused space that would cause me some problems. So I'm actually not going to separate my home partition I'm just going to do all falls in one partition And then we get an overview of the partition scheme and finally just hit enter on finish partitioning and write changes to disc And then it asks for confirmation one more time tab over to yes and hit enter And then install the base system hit enter This may take a few minutes and then we get to the next screen which asks about the kernel What kernel do you want to install by default? It's chosen the standard generic kernel here There is also the rt kernel. That's the real-time kernel. There's some other stuff here But i'm just going to go with the standard generic kernel. So i'm just going to hit enter Now it's asking about drivers to include in the init rd It's selected generic which includes all available drivers And of course that's for safety purposes right that covers everybody just give all the drivers, right? So that's the one I would go with you could also do targeted where it kind of surges your machine and figures out the Exact drivers you need i'm just going to do generic here And the base system finished installing now the next thing is to configure the package manager And then it asks us do we want to use non-free software? So this will enable the non-free repositories inside debian because by default debian is strictly free software Now you want to enable the non-free software So that way you can get your proprietary drivers if you need them and most hardware is going to need some proprietary drivers Your laptops many of them have wi-fi chips that must have a proprietary wi-fi driver for them to work And then of course nvidia users typically are going to want to use the proprietary nvidia drivers for their graphics cards So I strongly advise you to turn on non-free software unless for you know for sure that your hardware works with strictly free software Then it's asking about the default source repositories And this allows you to be able to run the command app dash get source Make sure that command works do you want to enable the source repositories in apt by default? Yes, I selected i'm just going to go with that Now it's configuring the apt package manager the standard package manager in debian Now it's asking about select and install software. So let's hit enter on that First it's asking us do we want to set up automatic updates that way we never have to worry about updating the machine It'll do it automatically. I don't like doing automatic updates. I would rather do it myself So i'm going to do no automatic updates if you want automatic updates, obviously you would choose the other option Then it's asking about pop con pop con is the popularity contest program that's built into debian It sends information back to debian So if you choose to participate in this what it does it's going to send information about your machine back to debian So they can make a better distribution typically on real machines. I would choose yes for this I don't mind giving them a little information in this vm though. I'm just going to choose no And now we get to the screen where we can choose our desktop environment by default is chosen the standard debian desktop environment, which is typically gnom. I'm going to tick these off though because I'm going to install a different one I'm going to install kde plasma Then I'm going to tab down to continue and hit enter And kde plasma has a lot of packages that have to install Thankfully debian is a binary distribution rather than a source based distribution So this should only take just a few minutes And it's finished installing plasma. The next thing is to install the grub bootloader So i'm just going to hit enter on that and it should do this automatically There's nothing for us to do We don't have to edit any kind of config files or anything that the debian incurses installer is actually very very easy Now it's asking us where should we install the grub bootloader which device And it's asking do you want to install it to the primary drive? That's okay. If this is a single operating system computer, so i'm just going to hit yes Now it's asking for the device. It's slash dev slash vda in my case Now it's asking do we want to force the grub installation to the efi removable media path? So i'm actually going to decline that Now it's asking do we want to finish the installation and absolutely so They should do some last-minute things such as setting the clock and then Hopefully we're getting close to the reboot. Yes, and now it's saying finish the installation hit continue And it should reboot the machine for us And it reboots just fine. We get a grub menu. So let's go ahead and boot in to our freshly installed debian unstable All right, and we get the login manager So let's go ahead and i'm going to click the screen here the drop down just to make sure plasma is the only Desktop environment installed and it is that's the only one I selected during the installation. Let's go ahead and log in All right, and we log in to a very plain vanilla Looking of plasma desktop environment although plasma is very very attractive out of the box I am going to go ahead and change the screen resolution to 1920 by 1080 that way That is set every time I open this vm from here on out because I may keep this vm around for a little bit And that is really all there is to getting up and running with debian unstable I'm just going to go to the applications menu just very briefly to see what is installed by default here in the plasma edition Looks like it did install a pretty good suite of software including gimp So it's not all just the kde applications because gimp, of course is a gtk application So there is actually a little bit of stuff installed here if I go back to internet Let's see. Does it install a browser for us? Yes, it installed firefox for us and under multimedia We have dragon player and k3b the disk burner. Do we have an office suite? Libre office was also installed by default for us. So the debian kde Desktop actually does include a pretty good bit of software. So that's nice So one thing I do want to show you guys is let me go ahead and open up a terminal So in kde the terminal is called console with a k So i'm going to open up console and i'm going to zoom way in so you guys can see this and i'm going to run this command sudo apt update And and sudo apt upgrade This command is the standard command you run in debian and all debian based distributions to update all your software So this works in ubuntu linux mint mx all debian based distributions It asks for the sudo password. So let me type dt's password And dt is not in the sudoers file meaning he does not have sudo privileges So this is how debian differs from ubuntu and mint and a lot of the other debian based distributions You've probably used is your normal user can't do anything with sudo until you add him to the sudoers file So let's do this So let's su over to the root user because we need root privileges here And then as root open in your favorite text editor. It can be nano. It can be vim Um, but whatever text editor you want to use open slash ipsy slash sudoers And then you have this file here and i'm going to go down to this line here root And then all equals all colon all all What i'm going to do here in vm as i'm just going to copy that line I'm going to do yy to copy and then p to paste And it's going to complain i'm changing a read only file. That's fine Then i'm going to do cw for change word and i'm going to do dt and then i also need to change some of this Because i don't need the colon all so i'm going to delete that and hit escape And now if i do a colon wq to write and quit out of vm It's going to complain that it is a read only file So i need to do colon wq exclamation point to override that and now let me su to the dt user And now my up arrow back to sudo apt update and then sudo apt upgrade It's going to ask for a sudo password. Let me hit enter And there you go It's updating the system There shouldn't be anything to update because we just did a fresh internet install So all the packages should be absolutely up to date But now we know that dt has sudo privileges and close out that So that was a very quick installation process, right? It's very easy to install debian and if you want to move to debian testing or in my case debian unstable Just grab that mini iso I'm going to give you a link in the show description because it is very confusing how to find that mini iso from debian's website Because it's like a labyrinth Of isos that you've got to navigate from their site now Should you be running debian unstable because obviously the debian guys would say you probably need to run the stable version of Debian well, it depends on use case if you're if you need the Bleeding edge software you need the latest and greatest especially if you maybe you're a developer and you need the latest and greatest Libraries for whatever programming languages you work in and things like that then being on a rolling release distribution Makes a lot more sense than being on a stable distribution for what I do because I play with so much Software I'm always trying out new software You know I hear about this new piece of software and I want to try it out It's not going to be available in debian stable Right, it's that piece of software this brand new hasn't made it into debian stable yet But it will be in debian unstable and that's why I run rolling release distributions Now before I go I want to thank a few special people I want to thank the producers of this episode Epsy Gabe james michael paul west a commie allen chuck curt david dylan gregory hyco erion alexander peace arch infador Polytech raver scott steven and willy these guys They're my highest tiered patrons over on patreon without these guys This episode about how to install debian unstable would not have been possible The show is brought to you by each and every one of these ladies and gentlemen as well These names you're seeing on the screen right now. These are all my supporters over on patreon Because i'm sponsored by you guys the community if you like my work and want to support me Please consider subscribing to distro tube over on patreon. All right guys peace I love unstable distributions. Keep you on your toes