I have seen some chatter online, overall just 10 out of 10, honestly. I am Jackson to lack of surprise that Damon would joke brain air, because if they weren't going to fight before, they sure as heck are going to fight now. House of the Dragon, episode 10, the season finale. Did it stick the landing? Yes, it did. I have seen some chatter online, not much, because I don't have time to be looking online and stuff, but what a little I have been informed of people saying that it did not stick the landing. And that is just objectively false. So let's talk about it. The first section I have is something that I had planned to talk about already, that I wanted to bring up as a positive, as something that I quite like about the show. And then I learned that people have a problem with this. And also, well, now I'm definitely talking about it. That is pregnancy and childbirth. I think it's great. I know that people have a problem with this. So even I found myself at times watching the show inching towards the thought of, like, is it is it a bit much to have this again, having had enough childbirth scenes? And then immediately like pulling back and being like, I would never think that about a battle scene, about a fight scene. This is equally relevant to the plot. If not more so, it's just not something that gets depicted all that often. It's the exception, not the rule. And I love the fact that this show is one, giving an equal time, basically saying the bloody battle that goes on in childbed is as important if not more important than what goes on on an actual battlefield, especially to the story they're telling, but in general. But add to that the fact that this story, this show, this is about essentially two mothers going to civil war with each other, setting the kingdom at war with itself. So Alison and Rhaenyra, you know, this is these are the two loggerheads in the story. They are both mothers and they have both had to fight to birth children and now we'll have to fight for their children's legacy. And I think in general, let me the idea that in stories we show battle, we show war, we show hand to hand comment, we show blood in that regard, but childbirth, if at all mentioned, is, you know, someone, some lady screaming in the other room while a father paces. And we see his story. We see how he's like worried about his child being born.  And then the father deciding what to do about it. But it's not often that we actually see the birthing room and seeing what the mother is going through or if it goes wrong. Oftentimes, again, stories will be like, everything went great. Here you go. Here's the baby.  Isn't that sad? But like, you don't see that, but you often see battles. You see men die on the battlefield. You see duels. You see beheadings. You see executions. You see, you see this all the time. So just in general, yeah, I'm glad they're they're showing childbirth, too. Because like, yeah, that's just as relevant. But again, these are two mothers and to really bring home what they have had to do to bring forth this life, which they will now fight to fight for the legacies for, for their children, you know, for Allison to fight to get Aegon on the throne, Rhaenyra to fight to get herself. And then thereafter, her children on the throne. It is extremely appropriate to show that the birth that we saw in this episode was a failed one. It came prematurely and the child did not survive.  But so then having the scene of the pyre for the dead child, I hadn't really thought of it in these terms until I heard the show owners say that this is kind of how they thought of this scene, is that it is kind of paralleling and mirroring the scene with the Viserys early on the show when they are at the pyre for his baby that his wife Emma dies trying to bear. When they said it, I was like, oh, yeah, huh. But like, I didn't clock that at all when I was watching it. And I think the reason I didn't think of it in those terms and I still don't really, I mean, when they said it, I was like, I mean, I guess so. But I just don't think that Viserys and Rhaenyra situations other than the being at a pyre for your baby are similar enough to be a parallel or in fact, polar opposite enough to be a parallel. They're just kind of different situations, you know? So it's not, again, for it to parallel something or to juxtapose your things in that way or for you to like mirror them in some way. Usually, at least to me, that signifies that some you're trying a parallel because these situations are in some way similar or you're drawing a parallel because these situations are in some way the polar opposite. And that's why we're connecting the two to show them as mirror images either because of how similar or because of how different they are. And here, I mean, yes, it is a child's funeral, but that's it. Like that's the only part of it that's the same, like where Rhaenyra is in her life and what situation she's in and what she's being forced to consider right now is so, so different from Viserys. But again, not in a way that's like the direct opposite of that, you know, like on a color wheel or whatever. Like it's not like so different because it's the opposite. It's just very different. So I just don't see what the point of paralleling that would be other than simply to do it, which is kind of how it seemed. I was like when I said it was paralleling it, I was like, OK, but why? Why would you parallel that? Like just to say that she's now in her father's shoes, because like what makes her be in her father's shoes isn't that she's burying a child. That is not what makes her be in her father's place right now. And even then, she's not really in her father's place either because her the legitimacy of her inheritance is in question. And he hadn't like just been named the king. So anyway, I don't get the point of paralleling that. So I didn't clock that at all. But again, I liked that this episode showed that like the instant she gets this news, right, that her throne has been usurped, she goes into labor and has to spend the first hours, the first day of this of this new knowledge of her father being dead and of her effect that she should be Queen now, but isn't that she has to spend that time with birthing and birthing a child. It's not going to make it at that. The way that in this situation, because this is what happens, then people go into these like default modes, including Damon and Rainier has to like take extra steps to ensure that the default is not what happens moving forward because Damon by default then takes control of the armed forces and starts taking action. It's like, OK, she's going to go birth a baby as women do. I the dude, I'm now going to, you know, take care of the army side of things. And I don't necessarily think that Damon was trying to usurp her. I don't think it occurred to him that this is not what he should do immediately. You know, like Damon's already kind of a take charge kind of guy. And Rainier is going to go going to go birth a child. So it's just the natural thing for him to do again. I don't feel like he's like, oh, good, she's in labor. Now I can take charge. Like I don't think that that's the reading of it at all. Just that this is the default, just like that's why Aegon's been crowned. It's the default that it goes to the dude. That's what this kind of whole war and situation and question is about. And Rainier going into labor at that very moment has to go even further to prevent again, the default from happening.  I should be queen now, but Aegon was crowned and I'm in charge now. I'm the queen. Your legacy is through me. Nothing goes without my say and her sons. Then she kind of like deputizes them to like be her voice in the room while she can't be because it is through her, as she rightly says, that they would have any claim anyway. So it behooves them to strengthen her position in the room that she can't be in right now. And again, she has to work extra hard now to set everyone's mind right to be that she's the one that's if they're fighting for her to inherit for her to be the queen, then it's because she's going to be in command. She's the one in charge. It's for her that they are fighting, not just in name, but to actually rule. So I think we can segue nicely then to Rainier and Daemon and what their dynamic is like in this episode. So I want to start with Daemon crowning Rainier because I kind of already covered Daemon's reaction to her going into labor, which was not ideal, but it was very Daemon. So anyway, the crowning scene here is actually where I did immediately think of a parallel to Viserys, not with the pyre. So we did learn or at least I learned, I don't think I mentioned it in the video, but it was, it became known online that the scene in the episode two ago now, in episode eight, when Viserys takes the throne for the last time to reaffirm their legitimacy of Rainier and his sons, he, the crown falls off his head as he's trying to make it up to the throne and Daemon comes up and picks up the crown and then puts it back on his head. And so this was not planned. But nonetheless, you know, what they choose to do with the footage that they have, what they choose to keep in and show remains, like these remain choices that they make. Whether or not that was an accident, their choice, what to do with that, then moving forward is a choice. They kept this footage of Daemon standing over Viserys and crowning him, where he's, Viserys is lower and Daemon is higher and this continues to trend of talking about several times now, where the show would often frame Viserys as weaker by having the camera angled down at him and frame Daemon as stronger by having the camera angled up at him. They did this even in the first episode when Viserys was on the throne and Daemon was standing lower before him. The camera angles did not show Viserys in as dominating a position compared to Daemon as you would imagine they would, given their actual physical positions and political positions as well. So anyway, we did that yet again, right? In this throne room scene in episode eight, where Daemon is standing over Viserys and putting the crown on his head and they pan out to show that they didn't just show Viserys getting the crown back on his head. They very clearly showed Daemon standing over him and I don't mean to suggest that in that scene they're implying that Daemon holds the power in the room, but they did show that. And here, when Daemon receives the crown from Eric and goes to Rhaenyra with it and crowns her with it, the camera does not pan out to show us Daemon standing taller than Rhaenyra because he is taller than her and he would be from a higher position lowering the crown onto her head. That's just based on their sizes, that's what would be going on. But the camera doesn't show that. It just shows Rhaenyra's head receiving the crown. And then the next time you see Daemon, he's already kneeling. So there is never a shot where he is standing over her, putting the crown down on her head.  He is kneeling before her. And I really liked that they chose to do that. So they've shown him being in charge. He is obviously taller than her. There's no helping that. But once she becomes queen, once she receives the crown, he is shown to be subservient to her. I also love that in this scene I got the return of this beautiful piece of music that I don't know what it's called in the soundtrack, but I called it Rhaenyra's theme when I talked about it a few episode reviews ago. I love this theme music that Rami and Jamadi wrote for Rhaenyra. They've used it several times in iconic moments for Rhaenyra throughout the show. It's this kind of like base kind of drumming, heavy sound with these light feminine vocals atop. And it is I think a great piece of music for representing Rhaenyra as a character. And I love the way that they have used this music several times and it's always been in quite sort of like epic, like very character shaping and character defining moments. They've played this music and it feels almost like planting and payoff where they've shown these scenes where again they've been pretty important, significant moments for Rhaenyra and played this music because this is sort of like her on her way to her final form, if you will. And so in this scene, when she gets the crown and everyone is kneeling for her to hear this music again, it feels like a reprise. It feels like this is what all of those other moments were leading towards and here she is finally. But you know, not all is well between Damon and Rhaenyra as I already alluded to. He kind of takes charge while she's away. Again, I don't feel like he was intentionally usurping her but that's nonetheless what he does. And I do like that they didn't immediately show him being deferential to her. His instinct is to command and to lead and take charge always. Viserys had to deal with this side of Damon as well. And you know, Viserys is a man and his older brother. This is just kind of how Damon is. So it would have been extremely out of character for Damon to immediately be like, you know, Rhaenyra's in charge, no one would do anything with that Rhaenyra I say. So like that's just not who he's been this whole time. So that would just not be in character. So it felt very Damon of him to just be like, all right, I'm in charge now. Here's what we do. And even when Rhaenyra comes back, he's still not quite willing to like, oh, he's like, this I know better. I'm older than you. I don't care if you're clean. And again, I don't mean to say that Damon thinks he should be king and not Rhaenyra. That he should be like the one in charge really. But at the same time, he's like, I mean, you're queen and all, but like I know better about this. Like I just do. Then this is just how this goes. It's again, it's a very, like it's the default attitude. When they argue, he uses a comparison to Viserys as an insult to Rhaenyra.  It's like, there's too much of Viserys in you and that's a bad thing. Which is also interesting because of how many times Viserys complained that Rhaenyra was too much like Damon. So I guess she's out of the worst of both worlds at the best of both worlds. Both Viserys and Damon see too much of each other in Rhaenyra. And I mean, perhaps that is what would make her in other circumstances, the ideal queen. But she has the more calm temperament that Viserys has but has the chutzpah and willingness to do what is necessary to go to war, to do that kind of thing as well. So again, in different circumstances, she might be the exact ideal queen if that is the case, that she's the perfect blending of Viserys and Damon. Then we get to Damon choking Rhaenyra and again, this completely checks out as something Damon would do. I mean, for all the positivity on the internet about Damon, he's not exactly the ideal person to choose as a mate. He does awful things all the time. So I'm not at all surprised that he would choke Rhaenyra. I'm not condoning him choking Rhaenyra to be clear. We're talking about the writing here. And Damon, as written, as portrayed in the show, him choking Rhaenyra, I'm like, yeah, I am Jack's complete lack of surprise that Damon would choke Rhaenyra. What I love about this scene is that despite the fact that Damon physically dominates her in this scene, right? Cause he's taller than her and he chokes her. She doesn't do anything violent against him. She still comes away from that conversation, the one on top. She dominates him in terms of her power and her position because in this conversation, we have this realization. Rhaenyra realizes that Damon doesn't know about the prophecy of ice and fire. And this moment, not only does it give her the upper hand over Damon in this individual circumstance in this individual conversation between the two of them, it does give her the upper hand in this dynamic in this room, but it also gives her that final certainty that Viserys truly meant her to be his heir. And I think this is a fantastic parallel to what has been going on over Yonder with Allicent because for Allicent, the prophecy served as a final confirmation that what Viserys intended was for Aegon to take the throne. So once again, we're kind of paralleling what each of them gets from Viserys. Each of them now has this realization about that it's prophecy related. Allicent feels that he has confirmed that he wants Aegon. And Rhaenyra realizing that she is the only one that heard this prophecy, that he didn't just maybe not tell it to Aegon, but that he didn't even tell Damon. Damon was his heir up until he named Rhaenyra, and he never told Damon. And that realization for Rhaenyra about how this was not just a passing thing, this wasn't like a, well, you know, in the moment, I got no other kids so I'll name Rhaenyra. This serves as that confirmation that he really, really meant it. But yeah, overall in this episode, I think I like that they showed Damon not immediately kowtowing to Rhaenyra. He takes over when she goes to give birth. He takes charge. He argues with her in front of everybody. He chokes her. But I don't think that this episode at all shows him not supporting her weirdly. Like he, in his way, in the most Damon way imaginable, he 100% supports her. And he believes he's doing everything in his power to strengthen her claim. Often that means he thinks he knows better and he's in charge and he should make the call. But he does believe that she should be queen. And he does, in his way, defer to her, at least eventually. And he does support her and her claim. Moving on then to Rhaenyra and the Valarians. So first of all, I just wanna say I called it. When Damon reacts to Rhaeny's showing up at the news that, you know, the greens crowned Aegon, I escaped on the back of my dragon. Here I am. Damon is the voice of the audience is like you could have ended this right then and there. You could have burned them all, why didn't you? And Rhaeny's says exactly what I said her position was when I watched that episode. This is not Rhaeny's fight. She does not have a dog in this fight.  But whether or not the kingdom goes to war over the question of succession here is not Rhaeny's call. It's not up to her if that happens. So when that's exactly what she says, she's like, if there's gonna be war, that's not my call. That's on you. I was just getting out of there because I'm not gonna side with them. But it's not up to me if we go to war over this. So as soon as she said that, I was like, yes. Nailed it. But again, it makes sense that that would be the call she'd make. It's not the one Damon or Rhaenyra would want. Necessarily it's not the one the audience would want. But it makes sense that that would be her call. Because as again, what I'm about to talk about Rhaeny's doesn't have much reason to super duper support Rhaenyra. If when Push comes to shove, it's a matter of honor of swearing odes of this is the side that we did swear we would support when Viserys named her as heir, this is the side on which our grandkids are. So I guess if we have a side, it's this one. But she has no love for Rhaenyra, at least at the time of her escaping on the back of her dragon. So I liked how throughout this episode we watched Rhaeny's kind of come around to the idea of Rhaenyra, not just because, okay, if I have to choose, I'm choosing this side because of the aforementioned reasons. You know, that she actually comes to respect Rhaenyra as an actual person who might be the better choice as a ruler, and not just because she's not Aegon, who's like the worst choice, that she watches, that we see Rhaeny's watching her and weighing her and measuring her.  And the fact that that is something that she's able to not forgive but set aside and still support Rhaenyra and still recognize Rhaenyra as the better choice and as a worthy choice to rule Westeros, that she has the level head to be able to say, hey, Coralus, I've been watching Rhaenyra. I mean, Coralus is for good reason, not down with that at first. He's just learned that Daemon killed Vaemond. They both believe that they're responsible for Lainor's death. Coralus is like, you know, screw all of them. Why shouldn't we side with them? And Rhaeny's is like, look, we have to choose a side, that is clear. And Rhaenyra is trying to keep everyone from going to war. She is showing good judgment and would make a good ruler.  And so I like that the episode just spent time showing us Rhaenys and Coralus having to come around to this idea that it's not just a given that they would side with Rhaenyra, that they have to kind of come to actually choose that. And then again, to show that Rhaenyra does not take that for granted, that she did not fully rely on the fact that they would join her side for, you know, obvious reasons. So that when Coralus comes forward and is like, we're on your side, that this is not lost on Rhaenyra, what a monumental thing this is to have them on her side. And not just Coralus saying, hey, you have our fleet, but that Rhaeny's herself personally is like, I'm putting my skin in this game also, me and my dragon. Did that moment felt as epic as it should because they had to set aside a lot in order to make this choice? It was not made lightly and you really feel that from all sides. Moving on then to Rhaenyra and her kids. It's been pointed out by a lot of people that in the depiction of these characters on this show, Rhaenyra is a lot more motherly than Allison towards her children. So we see Rhaenyra frequently, sort of like touching their heads and their shoulders and kind of being very like physically affectionate with her kids, very touching her pregnant belly a lot. And the way that she speaks to them is usually patient and coaching and teaching and comforting and consoling. That's how she's shown with her kids. Allison by contrast, we see her slapping her kids, yelling at her kids.  There's no like physical affection. She never displays any physical affection towards them. When Aegon asks if she loves him in the previous episode, again, I don't think she actually means to say that he actually is an imbecile. Like she's not like insulting him while she is insulting him. But I don't think she means, I mean, obviously she's saying you imbecile, of course I love you. But again, like what I meant, I suppose, which I feel like people weren't clear on that or I wasn't clear on that in the previous episode, when I pointed out and others have pointed this out as well that Aegon, when he says, do you love me, mom?  No, we don't mean when we say or when we point that out, that she is saying with that that she does not love him. But to me, it's telling if somebody can't say the words. If someone says, do you love me? And you say, what do you think? I mean, like the fact that you can't find it in you to actually say the words, you find a way to imply it rather than saying it outright, I think it's telling. Because people struggle to say things that they don't mean. They'll find an excuse not to or to say something similar that's not quite it. She didn't say you imbecile, of course I love you. She just said you imbecile. You know, it's like if someone says, do you love me? And the response is, I wouldn't be here if I didn't, you know, okay, why can't you just say you love them? Or use that as a supporting statement. Say, I do love you, I wouldn't be here if I didn't. But because you couldn't utter the phrase, I love you, you just skipped to the you imbecile, I wouldn't be here if I didn't kind of response. I think it's very telling. Which again, when we see ain't gone asking her, he's clearly at his lowest and he doesn't believe his father ever loved him. He's asking mom if she does and all she can say is you imbecile, I think it's telling. Again, Rainier, when she's in labor, she calls her sons to her and tells them, you know, it's up to them because their legacy is through her. And she's sort of like forcing them to take up the mantle of their positions now, the same as she is being forced to. The show has established several times that Lucerys does not want it when he's a little kid, he says it. And then at the beginning of this episode, when he's older, he also says that he doesn't want to be the heir of Drift Market, he doesn't know what he's doing. And again, we see this as a parallel to Aegon, who also was like, I don't want to be king, I shouldn't be king. But Rainier, unlike Allison, she's kind to Lucerys and she doesn't say, you know, shape up or ship out. She's not cruel to him.  I don't know what I was doing either. She's very affectionate. And so later on in the episode, when Lucerys and Gissari is both volunteer to take up some piece of this mission, you know, of reaching out to their allies, Rainier earlier in this episode has asked them to take up the mantle of being heirs to the queen now because that's what she is now, that's what they are now. And seeing them now take on that duty and asking to actually do something to contribute, she then has to let go as a mother and has to accept that they are going to have to be at risk. She asked them to grow up and they are now asking to be allowed to really do so. So she has to honor that if she really does want them to grow up. And then we have the scene where she's explaining to them the mission, making the promise not to engage in violence, which is again, her kind of approach to this whole situation of like, we're not gonna strike first, we're not gonna be the violent ones. We will respond to that if it comes to that.  So I was like preemptively getting devastated watching this scene, but where Rainier is then essentially telling Luceri is like, look, like, you know, based on the conversation they had earlier in the episode, you know, like, I know you don't feel ready. I know you don't. I know this is a lot. I know this is scary. You're getting the easy job. Don't worry, we're easing you into this, which again, it's devastating to watch when you know that he's not getting the easy job, quote unquote. Like, you go understand why she would think that there's very good reason I think that I would be the easy job. It should be the easy job. So I mean, she's asked them to grow up and they're willing to do so and now she's sending them out on what she thinks is like a good baby step for them and it's, well, it's gonna be more than that for Luceri's. A lot of growing those characters had to do all at once. And yeah, it's hard to watch. Moving then directly into Luceri's enaiment, much like what they've done with Alison, which I've praised ultimately. I mean, again, I talked about the time skip, the initial time skip version of Alison being a bit much to swallow all of a sudden, but in general, they've done a lot to add new ones to Alison's character, to her motivations. She's not just a cartoonish cookie cutter Disney villain who's like, I'm here for ambition alone, rawr. Like, there's a lot of nuance to her character in the show which I very, very much like. So they've done something similar here with Aamon, where again, the book tells us Aamon kills Luceri's on Dragonback. That's all we really know. Cause as a history book would tell it, you know, that's all they would know. Like, you wouldn't know what the conversation was like, what was going on between those characters. No historical record would have that information. And I like the idea that Aamon, hotheaded and angry, would pursue Luceri's, but that he would not have intended to kill him. And so for that to happen as a sort of like losing control of the dragon, which is already also kind of like, this would be a thing that Aamon would feel because it was such a big deal to him to claim a dragon and that he kind of had to go out there and get one for himself. So the idea of being able to control a dragon is a big point of like, of his ego, I guess, is the best way to say it. So that he would lose control of his dragon would already bruise his ego. And then the loss of control of that dragon would result in the death of Luceri's. Well, if he goes back and tells them what happened, he either has to say, I lost control of my dragon or I killed Luceri's on purpose. Neither is a great option. But the performances of both actors who played Luceri's and Aamon in the throne room scene was so well done. The tension between them, you know, you could cut it with a knife. The reveal of Aamon's eye was again, to be expected if you've read the book, but, you know, it was cool. It was cool to see. The performance of Aamon now after he's killed Luceri's of this kind of like, oh fuck, you know, I have made a huge mistake.  But given where the kingdom is right now, Aamon knows that he's basically just started the civil war. Because if they weren't gonna fight before, they sure as heck are gonna fight now. Which I thought was a really good choice to handle that scene that way.  You know, that would have been not especially believable, especially for how these characters have been painted so far. And this just, yeah. This just makes a lot of sense that this is how this would go down. Moving next to Rhaenyra and Allicent, which is something I've talked about quite a lot now in these sections, cause it's crept up in all these other sections. But there's a lot of ways in which Allicent and Rhaenyra are being paralleled and being mirrored and juxtaposed. Again, these two episodes in and of themselves are, when is the Green Council? When is the Black Queen? You know, when is the Allicent episode? When is the Rhaenyra episode? So like, obviously. This show is about these two ladies. But again, the show did a great job in this episode showing Rhaenyra really coming to grips with this position, that actually like taking on the mantle of being Queen now, what that means, what it means for her kids. And we similarly saw Allicent in the previous episode like Viserys is dead and fully coming to grips with what it means if she wants to get Aegon on the throne and what it means for her position. And going through this roller coaster of change, both of them have to go through this after Viserys' death. We also have an interesting paralleling of the dynamic between Allicent and Otto and the dynamic between Rhaenyra and Daemon. Daemon and Otto, their instinct is to jump to killing, jump to war, jump to violence. That's their instinct. And both Rhaenyra and Allicent show much more restraint and they check those impulses. When as Allicent said in two episodes ago to Rhaenyra that they both have more in common then either of them would often allow. And again, Allicent tells Otto in the previous episode an unwillingness to murder is not weakness. Rhaenyra assessed a Daemon in this episode so I should go to war because I'm angry. Neither of them wants, thinks violence is the first answer at least. They're willing to do violence but it's not their go-to first choice. Next we come to the bridge scene which is an obvious parallel. Does not need me to point that out too early on in the show when Rhaenyra went without her father saying that she should to prevent bloodshed between Otto and Daemon. Here, we obviously paralleled that scene. Rhaenyra's dragon even landed on Otto's side again so they once again had the part to let her through. Before it was Daemon that was challenging Rhaenyra's claim. Here it's Daemon defending Rhaenyra's claim but it's still violence between Otto and Daemon that Rhaenyra is once again the person to come between and say no. No, we're not gonna do violence right here today. Rhaenyra has been and continues to be the keeper of peace which is what Rhaenyra says about her to Coralus is one of the reasons she has decided to side with and support Rhaenyra. Another thing I loved about that scene which is nothing, not necessarily anything that happens in the scene but it's just that the having of this scene and because it does call to mind the much, much, much, much earlier scene that happened quite early in the show with Rhaenyra, the young Rhaenyra coming between them is just at this moment and kind of go like look at how far we've come because it makes you immediately recall this other scene because the whole time, you know, obviously you're aware of the young Rhaenyra and what all has gone on but because it calls to mind this earlier scene so vividly and you just look at these characters and how much has happened between them and how much has happened in the interim and how much they've grown and changed and how much in general has changed since that original scene. I don't know, I love the way that it just kind of like brings that into sharp relief. You know, the first time we had this scene Rhaenyra was there on behalf of Kings Landing and now she ends the scene saying that Kings Landing will have her answer. So how is this episode as a finale? I think it's a brilliant finale. Again, I've seen here and there these takes that it was a weak finale and I just think that that's, you know, I guess every opinion is valid except that one. If you think this show is good and you don't think this finale is like the landing, get out of here. You don't understand the show. I mean, this episode, it closes the loop on episode nine.   They are a duo. This completes that circle. This did so much paralleling for things that happened in the show in general but also for what happened in the previous episode. It's showing us the sides. You know, we got to really know the green side of the previous episode and not just Alison Tanauto but all the points of weakness and strength that are on that side, the breaking points, the points that they have to their advantage. We got a deep dive into what's going on over there. And then with this episode, we got the same with the blacks. The strengths and weaknesses of not just Reynira and Damon but about their allies. Who's on their team? What do they have going for them? What are their points of weakness? Where might this all fracture? I also really enjoyed that it showed us not just Reynira wondering about whether or not it's right to go to war. It also showed us the very practical concerns of going to war. Like it's not just a question of is it moral to do this? It's, is it practical to do this?  Do we have the resources to do this? It's not just I want to reclaim my throne. You have to actually think about it if that's possible. This episode, I think beautifully completed the evolution of Reynira into her final form into the black queen that would go to war for her crown. Because even at the beginning of this episode, she wasn't quite there yet. She was very, you know, still young Reynira, not quite ready to claim this position. She knows she has to. She feels uncertain about these things. Doesn't immediately want to go to war. The war is not necessarily the answer. But just in that last scene, we see that Luceris isn't just the last straw in terms of, oh, in general, this side can't let that stand. Because of course that side can't let that stand. But what it does to Reynira, to push her over the edge and to make her willing to go to war for this. Because she was not willing to go to war for the crown alone, but over the death of her son. Yes. And because this whole season had been building up to the Dance of the Dragons, I like that it showed us the first domino to fall, the first casualty of the Dance of the Dragons. Luceris' death is, I think, a brilliant way to end the first season. Because it shows us the real pain and the real stakes of what's about to happen. You could have ended it before that, I guess, and just that they're considering going to war. But this is what is the final kind of, this is the point of no return, so to speak. I think it's a perfect place to end it. I also liked that it did give us our very first glimpse of what we can expect a war between dragons to look like. Because up until this point throughout this show and also Game of Thrones, we've only ever seen Dragon versus city. Dragon versus general populace. Dragon versus castle. Dragon versus army. That's what we've seen. We've never seen dragon versus dragon. And the Dance of the Dragons is going to be many a dragon versus many a dragon. So we, we then, we saw the first casualty of this war and our first glimpse of what this war is going to look like and how devastating it's going to be. The show overall, final thoughts about sort of all 10 episodes, it's not a perfect show. I have had complaints throughout. The pacing is a little off. Again, I think they worried about losing their audience. So they were clipping along at a faster rate, ultimately I think ending with Luceri's death was the right place to end. So if they felt they needed to get to that point, I guess. I don't necessarily think that they should have waited, you know, pushed some of this plot into the second season, but then if we could have had more episodes in season one or longer episodes to help with the pacing. But otherwise, you know, if this is, this is the goal, you know, you got to get from the series becoming king to Luceri's dying. If that's, you know, those are the bookends and we have to fill in everything in between. That being the task they are set with, the pacing was decent for that. The time skips, as I said before, were drawing not just because how they tie into pacing and how they are kind of drawing every time, no matter what, you know, I had a big problem with Allison after the time skip where she was just this complete 180 of her characterization. We didn't see like, there was a point missing between point A and point C, we didn't see B. We were just kind of left to intuit that these changes had happened with her over that time skip, but didn't really see at least even the beginnings of it. Not great in my opinion.  So I don't just mean like, I personally have issues with the guys, of course I do, but like, the fact that he murdered Joffrey the way he did and there were no consequences for this, the way that he's not really aging looks kind of strange next to everybody else who's getting either aged up, you know, like Viserys was looking like our corpse, but also the actors keep getting aged up, but like Kristen looking so young and fresh this whole time is a bit weird to me.  You know, there were moments of weirdness, moments of spectacle, moments of like, this is for television, which, you know, we're not my favorite, but for, you know, accepting that a show is gonna need to do some of that. Overall, I think most of the time I handled it decently well. Again, Kristen killing Joffrey at the wedding, purely so that we could have a death at a wedding. I didn't love it. Again, I talked about it a lot, didn't love that, but it's not absolutely the worst thing ever. Vaman's Beheading was, again, a moment for television. Doesn't really work for the writing. Rainy's coming up through the floor with the dragon. Again, I talked about it, like I don't think it's as bad as people said and the people defending Kristen and Vaman as totally making sense in the logic of this universe, going bananas over, not making any sense what Rainy's did, need to pipe down. All of it makes like equal sense, meaning not very good sense. Rainy's motivations did make sense to me that this is what she would choose to do, but I agree, it's a bit ridiculous that she came up through the floor with her dragon. You know, people saying then the floor, the stones would have hit her and killed her.  It was a moment of spectacle for TV. For being that, it was certainly better than what we got in season eight. So anyone saying that we're at season eight level of writing right now, get a life, we are not. Go back and watch season eight. You've forgotten how bad it was. Laris and the feet, again, I don't know why we needed that. It was there to be weird. It was there to be a moment to make you go, ugh, didn't make a ton of sense, could have done without that. But overall, I think as I talked about before, the task of this show is to take an outline of history from Fire and Blood and to really flesh it out, to give it the meat, to give it the nuance, to give it the character and flavor that is not in the book. It's just not that kind of book. To fill in all those blanks, and I think for the most part, it did a brilliant job filling all that in. And again, not just filling it in, because of course, they would have to write in, okay, we know this happened, so we actually have to figure out what the conversation where it was decided that would happen would look like. And doing that alone takes creativity and they did a good job if and when that was what they were doing. But they also added in a lot of nuance that's not present in the book, partly because the book again could not have that nuance because it's to do with very personal moments with characters, a lot of introspection that a history book like that just would not have access to that knowledge. So Viserys character overall, George R. R. Martin even praised it as a better Viserys than his book Viserys. There's just a lot more nuance to that character. He becomes a much more tragic figure than he's in the book. Damon's character overall, I think they handled, again, a character that can very easily just be like, oh, he's the bad boy. I think they've given Damon's character a lot of nuance and a lot of it is oh, two Matt Smiths, great performance. Alison Tane and Rainier are the gimmacks that they made them friends before all this goes down and the way that they've later kind of showed them dealing with the ramifications of their actions, how to decide what to do about what's, what they're contemplating doing, in particular with Alison's character because she has such an unlikable character and is positioned that way by the story and they've given her nuance that they've given her some pretty sympathetic moments. So it's not just oh, she's the baddie. She is much more likable than Cersei Lannister. Anyone out here saying she's worse than Cersei get out of here? She's not. The way that they took the time to show us Rhaenys and Coralus siding with Rhaenira. I think a lot of that, again, a lot of nuance to that. Aamon killing Lucerys and showing again that this was accidental and how this would have gone down. I think that's brilliant. I initially was very skeptical about adding in the prophecy of ice and fire, but they won me over. In episode eight, I was like, okay, actually this was a good idea. You guys are handling this really well and then furthermore in this episode and the previous one where the way this carries through the way this is part of what shapes the motivations of our characters, I think what's handled brilliantly in a great addition to the story. From a technical standpoint, the show has been fantastic all along. I mean, they have a lot of the same people doing it as Game of Thrones, which was also stunning. I mean, the sets, the locations they shoot in, the costumes, the makeup, all of that chef's kiss, it looks fantastic. The use of dragons, I mentioned before, is always narratively purposeful. It's not just spectacle, which makes it that much more impactful when they do do it. I mean, obviously CGI is expensive, so that's part of why you'd keep it to a minimum, but they did minimally use CGI. Obviously the dragons have to be CGI and other things as well, but it didn't feel like a show that's just all filmed on a green screen. It has life to it. It has grounding to it and the dragons I've praised before, again, narratively purposeful, but also they feel like these weighty beasts that they feel alive. They feel real. They feel like they have mass, again, because they did a good job, technically speaking, with just animating these dragons. But there's a lot of attention to detail on how they've animated them, have they given them personality, when and how they use them in the story, just very, very well done. The music, as always, is fantastic. I love, love, love, love, love. Ramin Jamwadi is a composer and he knocked it out of the park again. Yeah, he wrote some absolutely beautiful new music for this show and it was always a joy to listen to what new music he'd come up with and always added to a scene. The casting and the acting of everyone was superb. Again, what problems I had with Alison's characterization after the time skip were to do with how they are writing the character, not necessarily the actress's performance. It is also how she's directed to perform it. I think overall, everyone is fantastically cast and performing their roles brilliantly. And for a season that is essentially a prologue, I think this show did everything that it needed to do to get you hooked and set up for the following season. It showed you what has laid the groundwork for the Civil War that is to come in a way that you fully understand where both sides are coming from and not just the heads of those sides, but everybody else who composes the mosaic of the Civil War, all the individual relationships that are going to be at play when we move into a Civil War.  It gave us, again, all the information we need about all these people, reasons to root for and against people. This final episode, not just leaving off on, okay, we're about to go to Civil War, but to give us our first casualty, to give us a reason to really now wanna see this war because we, like, reindeer at the end of this episode are like, you killed Lucerys. Like, this cannot stand. And to get us the audience primed, not just to be like, oh no, the kingdom's gonna go to Civil War. Oh no, oh. No, at the end of this episode, you're like, hell yeah, we're going to war. All I can say really ultimately is Bravo. They knocked it out of the park. Whatever issues I have, it's not a perfect show. I can't expect it to be a perfect show. For being an adaptation of a small, relatively small chunk of fire and blood, it did everything it really needed to do. Certain things I would have done differently, sure. I think there's a perfect adaptation, a perfect show. Overall, just 10 out of 10, honestly. As a whole, brilliantly done. And I can't wait for season two. But I'm not quite done talking about House of the Dragon in a couple of weeks. The week of November 7th, we're going to reconvene the group earlier this year, Alex from Alex Nieves and Jimmy from the Fantasy Network and myself. We did an Asong of Ice and Fire read-along and we also read The Night of the Seven Kingdoms and Fire and Blood. So we're going to reconvene the week of November 7th. We haven't quite pinned down the date yet, otherwise I would tell you to do a live to talk about House of the Dragon. I'm very much looking forward to that. Jimmy's also been covering the show on his channel, so if you haven't seen his tanks on the episodes, go over there and check out what he's had to say. Overall, I think the three of us are mostly on the same page. At least I think we all agree that this show is fantastic, but there will be individual things that we disagree about. I already know a couple. So it should be a pretty interesting conversation and it will be live. So you can join in and let us know your thoughts as well. So for the time being, do let me know your thoughts in the comments down below. I post videos on Saturdays, other random times will be up on Saturdays so like and subscribe, turn on my Patreon if you feel so inclined and I'll see you when I see you.


Demons strategize generation, but those attacks only have as much power as you choose to give them. We have to learn the difference between a consequence and a curse. Oh, I'm under a curse of alcoholism. Who did the drink? Oh, I'm under a curse of adultery. Okay, but who did the cheating?  Okay, but who chose to run the internet search? I'm not saying that those demons aren't strategizing against you. Absolutely are. I'm saying the only power they have is the power you give them. So let's stop calling it generational curse and let's call it generational consequence based on generational choice.


Dear students, in this module, we are going to talk about George Herbert Mead and the role-taking as a process of socialization. Role-taking refers to the ability to see oneself from the perspective of other person and take on the roles of other people. George Herbert Mead's focus was on the question, what is the motivating factor of the role-taking? What is the motivating factor? What is the important factor? We socialize in the same way that other people want to socialize. The idea was that individuals engage in a role-taking process. We observe and judge others in the same way that we try to imitate their behavior. He believed that role-taking is a crucial component of socialization and allows individuals to understand and anticipate the behavior of other people. The important factor in our behavior is that we can improvise and anticipate. As you must have seen in your childhood, children perform different roles. Sometimes they become parents, sometimes they become teachers, sometimes they become doctors. This role-taking is very important for their socialization process. Mead believed that role-taking allows individuals to develop a sense of self that is based on the expectations of other people. So while having these roles, while performing these roles, what we actually do? Actually we are meeting the expectations of other people. In our mind, what expectations do people have for this role? Our role-performativity will be the same as expectations. So in this approach, socialization into the self and mind is viewed as a process of learning to take on the roles and expectations of other people and integrating those roles into one's own sense of self. So as we explore those expectations, our behavior starts developing according to those expectations. However, one of the limitations of this perspective is that it tends to downplay the ways in which individuals can resist and challenge the expectations and roles assigned to them. This does not mean that we try to fully understand the expectations of the society. We resist and deviate. So these resistance and deviating processes develop new expectations in relation to these roles. So this theory of meat downplays the factor of resistance. However, in a nutshell, if we see that it's very important to understand that how our role-taking process helps us building our own personalities.


And he's going to talk about Hewlett-Packard's relationship with Debian, so I'll make a next stage. Yeah, thank you very much. So Debian, it's really wonderful to meet you back at the end of the site, and I hope that sometime while we're here, we're going to have a site that does a lot of good effect. I'm curious, how many of you have heard me talk about HP and Debian's relationship in the past? A few, yeah, even a few HP folks, surprise, surprise. How many of you have never seen me in person before anywhere? Oh, hey, that's actually really gratifying. I love coming to the Debian conference every year in part because it's a place that I feel very comfortable. There are many people that I have known for many years and had the opportunity to work together with on interesting things, but part of what I have really appreciated the last few years is that in particular, this Debian day as a first day to kick off the official part of the conference has provided a neat opportunity for us to sort of step back and talk about some things relating to the Debian project and how it fits into the larger ecosystem of free and open source software, and that's, I think, gives us an opportunity to sort of help explain the project's place in the world a little bit, and I'm going to try and talk about that in a slightly different way than some of the other presenters today, both because I personally have a long history of association with this project and with the whole idea of free software in general, made my first personal contribution of source code back in about 1979, and I've been involved with HP or its spinoff agilent technology since about 1986, so I've sort of had the opportunity to be one of the people who lived through the evolution and emergence of the Debian project, and at the same time, I've been part of HP one way or the other for a very long time, and as it says here, I've been working on Debian since about 1995. Actually, I first installed it sometime in 1994, but my real involvement in the project began right at the beginning of 1995. I did serve for years the Debian project leader back in the 2002 sort of time in history, and I continue to serve as chairman of the technical committee as well as being president of software in the public interest, which we'll have an SPI session on Monday, I guess, we have a board meeting that we're going to try and actually have the folks that are here in person be meeting in person, and we'll be happy to take questions about SPI and answer questions about where we're trying to take that organization. SPI provides a legal and financial umbrella for the Debian project in the United States, which is important for being able to hold trademarks and things like that, and I also build pieces of amateur radio satellites and play around with high-powered rocketry and all sorts of other fun things, which I occasionally allow to sneak into my presentations. But you know, people ask me, so what exactly is it that you do as chief technologist for open source and Linux at HP? And I've spent a lot of time trying to think about the right way to explain that, and I think the easy way to do it is actually to show you three quotations from wildly different places. The first one's from somebody that I only quote rarely and usually with great mirth, but this time it actually is sort of interestingly appropriate, and that's this quote from George W. Bush about three years ago when he said that my job is to like think beyond the immediate. I read that quote, and I just had to laugh because this is in some sense part of what I think my responsibility at HP is. There are other people who worry about the budgets for the engineering activities that we're engaged in this very minute to try and deliver products in the next quarter. My job is largely to be looking at longer-term trends and behaviors and to help the company figure out what it should be doing to be in the right place at the right time to successfully participate in the larger free and open source software movement and to find interesting things to do. I also really love this quote from Evan Moglen from a talk that he gave at the Harvard Law School a few years ago, where in speaking about the free software world, he said that we now have a body of software accessible to everyone on earth, so robust and so profound in its possibilities that we are a few man months away from doing whatever it is that anybody wants to do with computers all the time, and that's really very neat. That describes free software as, in effect, an infinite range of possibilities, and then Dan Shearer, who I actually saw this morning for the first time and quite some time, threw out a quip at a conference in Australia a few years ago where he said there's so many clever things that could be done. And if you take this combination of things, trying to look a little bit beyond the immediate, this incredible breadth of things that can be done with free software, and then trying to pick the right set of clever things for the company to be involved in and trying to pursue as we navigate the free and open source future, that's really sort of what I do. But you know, enough about me, let's talk about the larger bits of HP. If there's only one thing that you remember from this presentation today, this is what I'd like it to be, hp.com slash go slash Debian. This is the sort of portal launch page, home page, whatever your favorite word is for finding out information about the products that HP has specific Debian support kinds of things associated with it. I'm now going to sort of jump away from this and talk a little bit about history, how we got where we are, what we actually do in terms of using technology from Debian and various products and some of where we'd like to go in the future. And then I'll wrap up by reminding you of this URL once again. So if you go back to the beginning of my personal involvement in the Debian project around the end of 1994, the main Debian server was a machine called ftp.debian.org. And this was a PC under a student's desk at a university. He happened to be a student who was working in the university systems administration community. And as a result, was no big deal really for him to have an open source project machine sitting under his desk. But there were problems associated with this, not the least of which was that every time Debian had anything like a release, all of a sudden that university's network connections would be totally inundated with file transfer requests from people all over the world wanting to download newer software. And the university networking folks would get concerned. And every time they got concerned and dug into it and found out that it was this PC under this guy's desk, questions would get raised. And so Bruce parents who was very involved in the leadership of the Debian project at that time was really concerned about the stability of the situation and asked me, since he knew I was managing a team inside the old test and measurement part of HP that maintained lots of systems and had lots of networking resources available to us. If I'd be willing to go grab a mirror copy of that system and just keep it sort of up to date and available in case something bad happened at the university and that machine got shut down or the connection got severed or something like that. And so I grabbed an old HP Vectra 486 Tower PC that was on a pallet about to go out for scrap and stuck a SCSI controller in it, an ESA SCSI controller for those of you who ever had the dubious pleasure of dealing with those things. And a couple of hard disks. And I love pointing out that at that time the entire archive comfortably fit on a 660 megabyte SCSI drive with lots of room available for growth and put a very early version of Debian on it. And that actually ran on an HP network connection from an HP data center in Colorado Springs for a number of years until we changed internal accounting rules for how we paid ourselves for the use of network bandwidth. And all of a sudden it became a high profile visible thing that maybe should live somewhere else. But I love the fact that today my management at HP likes having me talk about that part of our early history. Since of course at the time I just happened to be a manager running a group who sort of had permission to do things like that. It's not like it was some huge corporate strategic decision involved. And then if you're on the clock forward a little bit in that same period of time it had gotten slightly embarrassing that HP's PA risk processor architecture was sort of the last 32 bit CPU family that didn't have a real Linux port associated with it. And there had been lots of internal discussions in HP about ways to do this. But frankly a lot of individual contributors working in the company were worried that if they started contributing to something like a Linux kernel port that they might get in trouble inside the company particularly if they had previously worked on the HPX kernel or things like this and maybe had access to information that the company wouldn't want them sharing publicly. Then this little group of consulting folks in I think we're all in Ottawa, Canada called the Puffin Group emerged. And as a way of getting attention for themselves and sort of making a name in the world they announced that they were going to begin a PA risk Linux port. It helped that some of them were real aficionados of that architecture and knew a fair amount about the systems. But it was also sort of a brave and audacious thing to do because they were in effect diving in to try and port Linux to a processor architecture that wasn't completely well externally documented outside of HP. But through a happy series of coincidences and because of the amount of attention that this drew by early the next year and early 1999 HP had agreed to participate in the port and the moment that announcement went out there was this amazing effect on people working inside the company because now that HP had agreed to support the port of Linux to PA risk hardware individual contributors in HP felt free to go participate in the project and help make this happen. And there were some explicit things happened regarding permissions to make certain kinds of hardware information available and so forth that really aided that. And this was one of this was a major sort of stepping stone in the history of HP's direct involvement in the Linux flavor of the free and open source software community. We've been very involved in other free software things previously. We've been supporters of the Internet software consortium and their bind and DHCP demons and so forth for many, many years. But this is a really big deal in the history of HP's involvement with the Linux community. Not long after that Linux quit care acquired the Puffin group. And at that point, it wasn't just a fun project anymore. If work was going to continue, you know, somebody needed to get paid for it and HP actually agreed to put some money in so that tool chain and kernel porting activities could continue. But you know, you get to a certain point and it's like, okay, we have a working Linux kernel. We have a compiler and tool chain that work pretty well. But if anybody's ever going to actually use that, you need to have a Linux distribution around it, not just a kit of parts. And the reason that that distribution for PA risk ended up being Debian was that while on one hand, this port would be sort of irrelevant without a full distribution built from it, HP had already publicly announced the itanium processor architecture as its future direction for many of its systems and that that was going to be replacing PA risk. And as a consequence, it was it was really hard to sell a commercial Linux distribution on the notion that they should make a big investment in porting their distribution to PA risk because they looked to the future and said, well, you know, this architecture is not going to be around forever. You've already announced what your plans are for transitioning to something else. If we're not going to sell millions and millions of units, how would we ever make back the money that we would put into causing a port to happen? And so PA risk, the PA risk report was largely perceived as a community driven activity and not something for which there was a really strongly articulated business need. And at the same time, there were some key engineers in this group in HP who were Debian developers or for other reasons had gotten to know the project and liked it. This was actually before I went back to work for HP full time to do Linux things, but I knew a lot of the people who were involved and I would get invited as many other people would to participate in these hackfests that used to be organized around the PA risk activities. And at some point, it was pretty clear that if a distribution was going to happen and if it was going to happen in this kind of a community way, that Debian was probably a really good way to make that happen. And so when HP engaged directly with the Debian project to pursue the PA risk Linux port, there were some things that were very clear that this needed to be a real port. At that time, Debian had been ported to multiple processor architectures, but it had gotten nowhere near the state that it is today where more architectures are supported than by any other distribution. And so there were lots of questions about how this could happen. And it was very clear that we wanted this to be a real Debian port maintained and merged fully into the Debian mirror network. And this is accomplished by hiring some more additional Debian developers. And at some point in that process, I ended up being one of those people. But also by encouraging some existing HP engineers to go become more active in the Debian project and eventually to sign up and become registered Debian developers themselves. There are also some select investments made in specific features that were of interest. I won't bore you with the details, but there's actually a relatively long history of HP being willing to step up and put a few hundred or a few thousand dollars here or there to help make various things that needed to happen, happen. And then over the long haul of time, the experience that HP gained working with Debian on the distribution port for the PA risk processor sort of provided the context to make it easy for us to do Debian related work for our our itanium based servers when they were first being introduced and for many other things since then. The other thing that I think is really interesting is that the experience of building a relationship with the Debian project and figuring out what it took to be successful in engaging in a community oriented distribution activity had a lot to do with the attitude that HP's taken since then on how to approach the whole open source community development effort. It's a very conscious decision at HP to participate directly in open source development communities. In HP we don't talk about working with the community. We talk about being part of the community and as a result we think of ourselves as citizens of this larger community and we think about what the appropriate behaviors for citizens are who want to engage in social processes around this kind of community development. We try to support in line with existing community values and behaviors while focusing on developing those features and capabilities particularly enterprise robustness features and capabilities that are particularly important to our customers. And I think one of the really sort of interesting subtexts here is that HP has so far never felt the need to create a new open source license just for us. Many of our competitors in the open source business world have created new licenses and used new and different licenses that people have had to go figure out and understand when they chose to release interesting pieces of source code into the open source community. This approach of aligning and working with existing projects and making contributions to existing projects under the licenses they've already chosen has actually worked really well for HP. It means that we are one of the largest distributors today and one of the largest users of GPL version two within the enterprise world and that's part of the reason that we've taken such an active role in the GPL v3 process with one of HP's senior legal counsel serving as the initially as the co-chairman and more recently as the chairman of one of the discussion committees there. It's a reasonably significant commitment on the company's part to that process and while that process has not finished yet we are all you know hopeful that the end results will be good for for us and for everyone in the community and then we work with our Linux distribution partners Debian and commercial distributions and with independent software vendors to ensure that in the end we're delivering innovative and effective solutions that our customers can use. I went back and dug this slide out you don't need to pour it all the details but this is a slide that I took out of an old HP internal presentation that was used by the R&D manager of our internal Linux support organization to explain why it was that the Debian was such an interesting thing for him to work with and you know trying to decode pictographic things is sometimes difficult but the concept he was pointing to here is that when new hardware features are being developed and when new software functionality is showing up in the open source community there is a time delay between when new things get invented and when they show up in a commercial stable distribution release. There's just the normal cycle time of when a red hat or a Suzer or someone like that schedules their stable releases. When you work back from those stable releases there's some amount of time that's required to bring new software functionality in whether it's device drivers to support new hardware or new software features get those integrated and stabilized and prepared for a release and that there was a market opportunity represented by that time window between when new things first became available and when they showed up in commercial distributions and as a hardware company for HP it would be very valuable to be able to provide working Linux distributions and related tool chains to developers before our commercial distribution partners could necessarily get there with their completely stable releases and that there were opportunities when we were investigating and supporting new software to be able to deliver that faster if we had a lighter weight process for getting it out into the community and then there's this notion that as the market matures that gap might narrow because either the pace of innovation of new functionality would change or the rate at which things got integrated and smoothly delivered to customers might change but this was actually sort of another flavor not just this strong developer community relationship piece but a real sort of sense of there being a time value of money market opportunity window for making new functionality available by putting it on top of a community distribution that HP could be engaged in delivering just as quickly and efficiently as anyone else while we were waiting for our commercial distribution partners to run their normal cycle times. So in terms of things that have actually come out of this history of development relationship if we run the clock way back to when the titanium two servers were first being introduced they used a new processor chipset called ZX one that was developed at HP and it took quite some time to get ZX one support fully integrated into the kernel dot org tree and for all of the 64-bit isms it turns out that for various reasons titanium systems put more stress on some 64-bit porting issues than alpha and other 64-bit architectures had previously partially just because we were building systems that could handle gobs more memory than ever before and partially because that memory was often organized in HP servers in a sparse way across the address space where we actually ended up tickling higher order address bits faster and more furiously than some previous 64-bit systems but the really intriguing thing is that we had full ZX one chipset support and therefore Debian was installable and usable on HP's initial titanium two server offerings in the woody stable release and that release was actually made before any of those systems shipped. That's something that we have never succeeded in doing with any other operating system Linux or otherwise is being in a situation where the operating system is actually shipping in a stable release form before the hardware starts shipping. Now you can question the value of having something that's in a stable OS release before the hardware is even available and in fact our Debian leadership has established a set of criteria for adding new architecture support to the archive in the future that suggests that there needs to be hardware available that people can actually run this on before it's relevant but I point to this as an example of something that it was possible to do through the tight development relationship that HP was maintaining with the Debian project even at that point in history that would have been difficult for us to accomplish any other way. The first time that we set the I believe that was the first spec FP 2000 record ever set by Linux system was set using Debian on an titanium two server. We have of course since then focused most of our specsmanship work on the commercial distributions that we work with but the first time we set a spec FP record with Linux on an titanium two server was done with Debian before the commercial distributions were available with support for that chip set. There was a thing that I was actually involved in helping to invent which was an installation and software recovery tool set for titanium two systems that was based on Debian. It was actually a Debian boot floppies instance with the RAM disk expanded and the hood jacked up and a few extra tools slid in an extra layer of menu at the front end. But people discovered fairly quickly that you could actually use one of those. And if you knew the right magic words you could successfully use it to do a Debian base install. And so I was very pleased that in later versions of that we explicitly added do a Debian base install as a menu option. Some of the earlier carrier grade servers and HP's first entry into blade servers and various early access titanium two servers were all shipped with Debian pre installs. That was often the default Linux that was made available for developers. In almost all cases those products have now been replaced by other more mature products online and many of those ship with commercial distribution support these days. But there is still a substantial solution that HP has made frankly a lot of money selling into the telecommunications market that is Debian with an HP customized kernel and a few additional utilities running on top of a customized version of one of our itanium server models that's now helping to make things like cell phone calls just work all over the world. And then Debian's components have ended up being used in many products that HP ships that embed Linux technology as a member of HP's open source review board I have the ability to look into the database and review all the different places where HP has had our products intersect with open source and there are currently a couple hundred products shipping from HP that embed Linux and open source technologies of one kind or another and in places where that's more than just a kernel or more than just one application being loaded on some other operating system platform. It's surprising how many of those are using Debian as the source for picking up the packages they need. One really good example of that is in the thin client product line and you'll have to pardon the bill. This is a deck I pulled from. You can tell the ones that were put together in my marketing people but in fact a couple of the thin client folks are here. Michael's in the back room you know one away of Michael he's one of the architects from that team and he's actually here this week to soak up as much as he can and to I think we're hoping that sometime in this coming week some of this model the T5725 will actually be here for folks to take a look at play with look under the hood with and so forth. But these are sort of you know self-contained no moving parts desktop or whatever client computing systems that have Debian in their guts and support customization of the image of the 5725 some of the other more embedded products are also using Debian pieces in their guts but at the same time they are doing it in a way where at the end of the day that's not part of what the customer worries about it's just a product that works really well and solves a particular need and the fact that we happen to be picking Debian technology to make that happen is you know reasonably irrelevant to the customer but the reason that they've ended up picking Debian is the same reason lots of other people do it has a lot to do with the availability of all of these packages of stuff on any given day nobody cares about all 15,000 of those packages but the fact that there's somebody in the Debian ecosystem who does care about each of those packages and maintains it means that we all get to pick the subset of those 15,000 that matter to us and they're all there and they're all available. It also helps that there's such a strong international developer and community support experience around the Debian project because it means that the internationalization support in Debian is much better than it might be otherwise and of course it doesn't hurt that at the end of the day products that we build around Debian are able to be shipped royalty free. So let's fast forward to August of 2006. This is since the last time we had a Debian developers conference but it's not the first time I've talked about this in public of course. HP announced support for Debian on our ProLiant server family and they're in fact also here this week a couple of folks from our ProLiant server organization I don't know if they want to smile and wave or not but they had a lot to do with these cool shirts that I'm wearing and your organizers are wearing today in which I hope many more of you will get a chance to see before the end of the week. This was I think a really significant moment certainly in the history of the Debian project because you know this is a first tier server vendor offering real support for Debian on its principal family of servers that are of interest to Linux customers and part of the reason that that matters is that HP ProLiants have been the market leader in worldwide x86 stuff for a long time for about a decade actually and in fact for the last nine years since they first started counting we have been the clear and undisputed leader in both number of units and revenue in sales of Linux servers worldwide as a company. So when HP decided to add support explicit support for Debian to this product line it's a big deal and you know again taken from one of our marketing decks but I think worth mentioning anyway when we talk about industry standard servers there's industry standards and then there's things that help to differentiate quality and value within that concept of standard and part of what makes the ProLiant stuff interesting is that HP's made some significant investments in technology everything from acoustics and thermal management to driving density and better cabling and all sorts of interesting common components across the different product lines that allow us to drive volumes up and therefore get high reliability and reasonable economics across a wide range of form factors and different models and when this Debian enablement activity started there were really sort of two things that were going on one was this notion that we wanted to make sure that if you were already a customer or an organization that had decided to use Debian that there were no reasons that you would want to say well you know we have to go somewhere other than HP to get this because you know it's not being officially supported but then at the same time we recognize that there were lots of customers that were also in heterogeneous environments who'd already made decisions to use some of HP's commercial management and support offerings and we wanted to make sure that it was possible to use Debian systems well there so it's sort of a two-pronged motivation one is if you're a Debian user we want to make sure that there's no reason that you don't also want to be a ProLiant user but at the same time if you're already a big HP customer we want to make sure there's no reason that you aren't comfortable also using Debian and so there are all sorts of value-added components that come as part of this product these are sort of normal things that the ProLiant folks do and what it really comes down to is making sure that all the device drivers and management agents and so forth are available and tested for the combination of these different systems and Debian and one of the things I particularly wanted to point to is this thing called Insight Control Linux Edition for those of you who follow the events in terms of mergers and acquisitions and so forth a while back HP acquired this company called RLX which was one of the first companies in the Blades Marketplace and they had a product called Control Tower which was a management interface for managing Blades the reason I wanted to mention this is not only is Insight Control Linux Edition an interesting tool to use for getting a management view of a bunch of Linux systems but it's actually based on Debian Insight Control Linux Edition is a Debian, mini Debian system with all sorts of other things running on top of it which folks don't always notice it's another one of those examples of a place where this is the right technology for putting a product together that works well and solves a real problem and at the end of the day it's not for the end user about the fact that this is Debian but for those of us in the Debian community it's really cool when we notice that the stuff that we've worked on for all these years is helping to solve yet another interesting problem and so there's all sorts of things that have happened there's been a process of getting through the qualification testing with Debian Sarge using two, six kernels that's pretty much complete now and effort has transitioned to working with etch I understand that you should watch our website starting probably sometime in July to start seeing etch qualification results showing up that's just the typical lag time after a new release that it takes our testing organizations to get things scheduled and done it's not that I'm aware of anything there that's a problem many of us are actually running etch quite happily on these servers today and have been for some time but I wanted to point out that even things like the ability to do firmware updates on the servers from a running system and other things that aren't always part of sort of the base process of making a distribution work on a box or things that we're trying to support and so if you want to know what's available today I did a little quick cut and paste of bits and pieces from the web page this morning doesn't look exactly like that in other words but if you go to that hp.com go slash Debian there are a bunch of places you can from there click off to and one of them is a support matrix that will show you for different models of HP ProLiant server what pieces are and aren't available what things are coming soon and so forth there's another site that I wanted to really point out and again this presentation slide set will be available for you to download or look at online later if you want you don't have to scribble nodes but there's actually an HP ProLiant page within the Debian wiki structure which is an effort at aggregating community information about these systems as well HP folks contribute to that but others within the Debian larger Debian community are more than welcome to contribute experience things there as well and there's various other stuff that's downloadable from HP and then beginning on the 1st of December last year part of this whole support offering is that it is actually possible to buy from HP the same kinds of support products that are available for other Linux distributions and for other operating systems on these hardware platforms and to buy them specifically for Debian as well I'm not gonna spend any time on this but in this presentation deck are these slides that have the specific part numbers that you can buy from HP to get those different kinds of support if you want to you can find all of those from the hp.com go Debian website if you follow that particular path of mouse clicks and rodent droppings but I thought I'd stick them in here to make them easier for you to find and I mentioned earlier this HP product which is Debian GNU Linux plus HP Telco extensions I wanted to mention this again just because even though you may never actually physically see one of these systems because they're mostly being sold to communication service providers we're putting them into functions and their core networks and as a result these are not the kind of things end user see there's about a 30% chance that any cell phone call that you make anywhere in the world today is somehow going to touch one of these systems in some way I just think that's pretty cool I think it's cool that Debian is a core component of how many of the world's telecommunications providers are now building and deploying services to them it's not Debian per se that's important it's the fact that there's a large number of nines high availability Linux based solution available on hardware that meets their expectations but along the way somebody noticed and discovered that Debian's distribution was a good thing to build that on and that it would work well and be able to solve the problem and as a result there's an awful lot of it out there so once again if there's only one thing that you remember from my standing up here today other than HP's done some kind of cool shirts it's this HP.com slash go-debian this is the place to go to look to see what we're working on and what we're doing there are lots of other HP externally facing sites like opensource.hp.com where you can get a wider view of the various activities that HP's engaged in the open source community but when it comes to what we're doing with Debian and how that's turning into specific product and support offerings that are relevant to our customers and they are relevant we've sold some fairly interesting support contracts to customers who are running Debian and just last night I got taken out to dinner by a customer who just bought oodles of our blade servers to run Debian on and is looking forward to spending some more time this week talking to us about how we could get that stuff even better and so you know this is a good place to go to find out that sort of information if you want I'm gonna close with one thought I you know as someone who's been involved in Debian for a long time and tried to provide some vision and thought leadership at various points there is a challenge that we have faced through this whole process and that is that Debian doesn't have a certification test suite this kinda makes it tough for companies that are used to working with commercial distributions to figure out exactly what it is they need to do to quote-unquote support Debian and I think it's this work that Ari and Vandevent at Intel's done on the Linux ready firmware developer kit has been really interesting in this regard this how many of you are aware of this have you heard of this developers kit before anybody other than Keith okay well I'm glad I mentioned it then this is really neat this is something you can go download and run on a system and it will tell you whether that system's BIOS is doing things the right way to support Linux or whether there are issues and at the end it's basically an automated set of tasks and gives you a report this has been amazingly empowering to BIOS developers at hardware companies all over the world because now all of a sudden they can go oh that's what I need to do there's no longer any sort of funny questions about what does it mean to build a system that's gonna work with Linux they've got a simple thing they can run and get the answer so it makes me wonder whether Debian should engage in offering some specific additional tests to that suite if that's something BIOS developers and so forth are already going to be running and using and it also caused me to wonder from a sort of Debian PR kind of standpoint if it would be worth creating a Debian branded derivative of something like that toolkit with more tests that are specifically relevant I don't know this is an idea I'm actually throwing out more to the Debian developers in the audience today than to those of you who are just here to figure out what we're all about but this is the kind of thing that I think could help to make more companies that are involved in providing hardware and support services that might be interesting to have as part of the larger Debian community and ecosystem in the future understand what they need to do to be able to do that so with that hopefully we have a few minutes for questions thank you for your attention does anyone have something I'd like to ask and I have a, there's a mic in the center of the room and I have this one I can hand out either so go ahead so could you summarize the different ways that H... Oops, hello, check so could you summarize the different ways that HP makes money with Debian? Yeah, so how does HP make money with Debian? A lot of it's indirect a lot of it has to do with the fact that by using Debian in an embedded product for example if the alternative was to go to some other Linux distribution or some non-Linux operating system where we would have to pay some amount of upfront money to acquire the software or where we would have to pay royalty then there's an operational expense improvement by not having to pay that by using Debian in the case of these support offerings it's that we hope we're selling more units of hardware than we would otherwise sell that people will buy from HP who wouldn't otherwise have bought from HP because this is something we've done we'd love to directly sell more support contracts if people are putting Debian servers into real IT production use we're having somebody clueful who's willing to answer the phone 24 hours a day any day of the year anywhere in the world would be a useful way to raise that customer or that IT shops confidence in using Debian to deploy that and that could be a valuable thing and worth paying somebody like HP for and then in places like this Telco thing it's a key component of enabling us to pursue a market opportunity that we might not have been able to afford to pursue otherwise that's an example of where we went to our commercial distribution partners and we said, hey, you know we see this market opportunity we're gonna go build this custom piece of hardware to go pursue this opportunity it requires building a kernel that has a bunch of stuff that the kernel.org guys don't really like and yet, you know, we can make money on this do you wanna go there with us or not and they said, well, feel free and if you're successful maybe we'll follow you there someday so those are the kind of places where working with Debian can actually bring real money into the company even if it's sort of indirectly. So obviously GPL v3 isn't finalized yet but do you have a sense as to HP's corporate direction regarding v3? Well, I think there are things that are concerning for a company with a large patent portfolio in v3 and we have raised our concerns through the process and frankly I'm very pleased that the language in the final draft that we've seen the final call draft is better for us than some of the preceding ones but at the end of the day I think it's gonna be another interesting license in the landscape I don't think we're gonna have any strong reason to try and drive people to adopt or not adopt the license. Frankly our history has been largely with GPL v2 and unlike a lot of other folks we've been very comfortable using v2 so some of the pressures that drove people to want to create a v3 are pressures that I don't think we really felt and yet if the community wanted to pursue a new license we thought the right thing to do is to try and participate actively and have that license in the end be as useful and as good a license as possible. I will comment that I think there was this hope in the beginning of the v3 process that somehow when we got to GPL v3 that there would be this wonderful unifying consequence of revisiting the terms of the GPL and I'm afraid that what's happened instead is every time some specific issue came up for discussion people who previously were willing and able to work with each other within a community even if they had differences of opinion on that particular point. When that point came up for explicit discussion now people had to take sides and decide how they felt about that and so part of this process has actually been a series of divisions where lots of people who sort of work together under the GPL v2 umbrella have had to say yeah I don't know if I'm gonna like this better or not and I'm hoping that eventually a lot of those sorts of divisions get rehealed that once the license is stable and solid and people start to use it and understand it some of that sense of community will reform around it but I think it's way too early to tell what's gonna happen there and of course the final call draft we don't know I hope there are no further substantive changes in the text before the final but this is the FSF and RMS we're talking about so who knows. That's right. Are there any thoughts about taking HPUX and making it open source? There are thoughts about that on a regular basis and I would not expect it any time soon. I mean to be honest with you that we find ourselves in this interesting situation where we have a market leading position in a Linux market and a market leading position in the Unix market and there are actually different markets with different expectations and that would be a whole other talk and could be very interesting but it's not one that we have time for today since they're waving hooks at me from the back of the room so no I don't expect that to happen anytime soon and frankly personally I'd rather see our Linux offerings just continue to grow in relevance and both financially and technically till that question's just not relevant anymore. Okay well thank you very much for your time and your attention. I will be here all week. In fact my family's joining me on Tuesday sometime and we're all gonna be here towards the end of the week so if you have other questions or would like to ask me more about the history of either the WN project or those parts of HP that I've been involved in feel free to find me and ask I'd be happy to chat with you. Thank you much.


Hi and welcome to the session. Let's discuss the following question. It says L and M are two parallel lines intersected by another pair of parallel lines P and Q. Show that triangle ABC is congruent to triangle CDA. So let us first understand the basic approach to solve it. We will be using ASA, Congruence Criteria. This approach is the K idea. Now we are given that L is parallel to M and P is parallel to Q and we have to prove that triangle ABC is congruent to triangle CDA and by the ASA criteria we need to prove that two angles and one included side of the two triangles are equal. Let's now move on to the solution. We are given that L is parallel to M and they are intersected by AC. Therefore angle DAC is equal to angle BCA. Also angle BAC is equal to angle ACD because they are alternate angles. In triangle ABC CDA angle DAC is equal to angle BCA. As we discussed above they are alternate angles and similarly angle BAC is equal to angle ACD. Now we can see that AC is the common side of both the triangles. So AC is equal to AC as it is the common side. So we have shown that two angles and one included side of both triangles are equal. Therefore by ASA criteria triangle ABC is congruent to triangle CDA by ASA criteria. Hence proved. So this completes the question. Bye for now. Take care. Hope you enjoyed the session.