From here to glory, shield of faith will show you the way. Hallelujah. So come on, join in. Savior, hallelujah. Father, in the name of Jesus, hallelujah. We come into your presence. I thank you because you came into our church this morning. Your presence is here. We feel in hallelujah. Thank you, Lord. We came to praise you and glorify you. We came to lift you up and exalt you. What a wonderful Savior you are. You're the king of kings and the Lord of lords. Besides you, there is no other God. Thank you, Lord. Thank you, Lord, because you bless us in so many ways. We just want to say thank you. Thank you.  In the name of Jesus, bless our service today. We came to worship you. We came to honor you. We came to lift you up. We came to exalt you, Lord. In the name of Jesus, be exalted. Hallelujah. Turn your word to our hearts this morning. Your word. Thank you, Lord. It's a lamp unto our feet and a light unto our pathway. Your word illuminates our heart. Your word keeps us going. We look forward to your coming. Even so, come, Lord Jesus. Come, Lord Jesus. In the name of Jesus. Hallelujah. Please send more people to this church, Lord. Let them hear the word. Thank you, Jesus. Be among the worship that they can fill your presence, Lord. Our desire is to see other people say that they can go to heaven, too. In Jesus' name, be exalted. We glorify you, oh God. We honor you, oh God. In Jesus' name, thank you, Jesus. Amen. Romans chapter number 12 verses 1 and 2 and then 1 Corinthians chapter number 6 verses 16 and 17. So, I'll read and you just follow along with me. I beseech you therefore, brethren, by the mercies of God that you present your bodies, a living sacrifice, holy, acceptable unto God, which is your reasonable service. And be not conformed to this world, but be transformed by the renewing of your mind that you may prove what is that good and acceptable and perfect will of God. Amen. Now, second Corinthians verse number 6, 16 and 17. And what agreement has the temple of God with idols? For ye are the temple of the living God, as God has said, I will dwell in them and walk in them, and I will be their God and they shall be my people. Wherefore come out from among them, be ye separated, said the Lord, and touch not the unclean things, and I will receive you. Let's make the Lord add a blessing to the reading of the word. Let's give the Lord a hand clap for the word. Amen. Hallelujah, hallelujah, highest, hallelujah. And our God, he rose with all power, right? Hallelujah. There's nothing in no one that can defeat our God. Sometimes we might feel defeated, but we are not defeated. We are victorious in Jesus Christ. Hallelujah. Psalm 3, this is Psalm 3. Amen. We're singing. Lord, how are they increased that trouble me? Many there be. It's me. Many there be. Honest left eye for me.  Hallelujah. Yes, glory. Hallelujah. The best thing that I ever could have done was to fall in love with my Lord and save your Jesus Christ. Amen. Hallelujah. Ever since that day, my life has never been the same. And I thank God. Thank you, Jesus. Thank you. Bless you, Lord. Falling in love, falling in love with Jesus. Falling in hallelujah. It was the best thing. It was the best thing. It was the best thing. It was the best thing. Hallelujah. It was the best thing I've ever. Bless the Lord. Bless the Lord. Bless the Lord. At this time, we're going to have Bishop Alexander come forward. Somebody's got to do. I'm the Sunday morning solo for today and singing my solo. Here it is right here. Here it is right here. This is Pentecost Sunday. Anybody know what Pentecost Sunday is about? Anybody been affected by the Sunday of Pentecost that came to the world? Hallelujah. Hallelujah. Thank you, Jesus. What a privilege it is. What an honor it is to walk with our Lord and Savior Jesus Christ. Amen. He provides strength when we're weak. And the value of His strength is that the road that we must travel if we want to see Jesus is difficult and more than any human being could. But Jesus said, my strength is made perfect in your weakness. When you're weak, He said, I'm strong. Thank you, Lord. Thank you, Jesus. Thank God for the strength He provides for us. Thank you, Lord. Now, Pentecost Sunday, we're encouraging everybody who has the Holy Ghost to keep in tune. Amen. Continue your walk. That's right. And for those who have not found Jesus, we want to introduce this to you as the day and the time of the hour that is available to you to find the Savior we've found. Hallelujah. Hallelujah. And my subject for my message today is I want to be a follower of Christ. Amen. Amen. Let me be a follower of Christ. So I found a song that says something like that. All right. I want to be a follower of Christ. Oh, I want to be one of His disciples. I want to walk in the newness of life. Oh, so let me be a follower. Oh, I want to be a follower. I feel like the message is just about in this song that I want to be a follower of Christ. I want to be a disciple. I want to walk in a new life. So I say, let me be a follower of Christ. As we found in our devotional scripture in Romans chapter 12, those of us who have been called unto Jesus, the Lord has done a work in us for holiness. We're instructed, I beseech you, therefore, brethren, so I beg you, brethren, by the mercy of God that you present your bodies a living sacrifice, holy, acceptable unto God, which is your reasonable service. Now pause right here to say you can't be a disciple of Jesus Christ unless you live a sacrificial life, one that is holy and is acceptable to God. You can have the Holy Ghost not be acceptable, not doing things that are acceptable unto God. And He said, it's just your reasonable service to live right. We live in terrible times. Anybody witness to that?  People doing their own thing, not concerned about what ought to come to them as a consequence. This next verse said, be not conformed to the world. He said, don't be conformed. Don't do what the world is doing. Don't be conformed to the world, but be ye transformed by the renewing of your mind because you need to prove something. That you may prove what is not good and acceptable, acceptable and perfect will of God. I want to be a disciple. I want to be a follower of Christ. And I understand that it is my duty and responsibility to meet the acceptable standard that has been set by God. Oh, I want y'all to say amen. Amen. This is as well. But it's right. This is the second sentence, chapter 6, verse 16. It causes us to take a look at the world and its action towards religion, their religiosity. These two verses said, what agreement have the temple of God with idols? So you can't serve God and idols too. The temple of the living God.  You're the temple of the living God. As God has said, I will dwell in them and walk in them and I will be their God. They shall be my people. He said, I'll be their God and they can be my disciples. He said, I'll take them, I'll honor them, I'll bring them into the family. 17th verse, wherefore come out from among them and be separate, said the Lord. And touch not the unclean thing and I will receive you. Now it's about being received into the body. Received where the Lord claims us as His own. Let me just digress for a minute. Let me take you back to St. Louis, Missouri back in the 40s and the 50s, Dr. Sykes. We had enough people in our family to have our own baseball team against each other. And when we would have family techniques, we'd have a baseball game. Usually dad would be the leader on one side and mother would be the leader on the other side. And when I was chosen, I was proud to be on whichever team I was on. But after I was chosen, some others came along and I wasn't happy that they were chosen to be on my team. Come on somebody. You see because we're all interested in our own personal interests. And so now being chosen by the leader is a great honor. Being chosen by God is an honor. It's not just a great honor, it's a great, great, great honor. And we need to understand and appreciate the fact that He would choose to bother with us as no good as we are. I have to clap for myself. I'm clapping for myself, but I'm clapping for the Word of God. We were born in sin and we were shaping in iniquity. And we were no good for anything until Jesus came to turn things around and bring us back to Him. Because He did that, my soul rejoices. I'm happy. I'm happy to be a child of the King. Now I'm going to take you to the text for today in Mark chapter 8. Mark chapter 8 finds Jesus on His way to the cross. And Jesus along the way, He stopped and healed a man who was blind. He laid His hands on him, prayed for him, and He healed him. And He told him, go his way and don't talk about it. Then when it gets to verse 27, Jesus went out and His disciples into the town of Caesarea Philippi. And by the way, He asked His disciples saying unto them, whom do men say that I am? They began to say to Him, they said, John the Baptist. Some said Elias and others, one of the prophets. And Jesus said to them, that's good enough for that.  Who do you say? What do you know about me? He said unto them, whom do? He said unto them, but whom say ye that I am? And Peter answered and said unto him, thou art the Christ. Peter didn't come with that on his own. In another place where this is brought to us, he said thou art the Christ. And then Jesus returned and said Peter flesh and blood didn't reveal this to you. He said, but that came straight out of heaven. He said, so all right. Then verse 30 said, and He charged them, they should tell no man of Him. And He began to teach them that the sons of men must suffer many things and be rejected of the elders and the chief priests and the scribes and be killed. And after three days rise again. So Jesus began to unload on them after Peter gave him that little bit of who he is. He said, yes, that's who I am. He said, and I'm going to tell you what is going to cost you. He said, I'm going to go. I'm going to suffer. He knew what was before him. He said, I'm going to suffer many things and I'm going to be rejected. When I go among the elders and the chief priests and scribes, they're going to kill me. And after three days I'll rise again. And he spake that saying openly and Peter took him and began to rebuke him. And when he had turned about and looked on his disciples, he rebuked Peter saying, get thee behind me Satan, for thou savoth not that, not the things that be of God, but the things of the world. Jesus said to him, it should be something in this that you're very satisfied with. Now when we are involved with food, some things are okay and other things are just great. They meet the appetite perfectly and we want to savor that. So I want to hold on to that. Jesus said to Peter, he said, you're not savoring, you're not appreciating the things that are of God. He said, all you have come to do is you're thinking about the things of men. And so now we get to verse 34. We're addressing issues of God and issues of men. Verse 34 said, and when he had called the people unto him with his disciples also, he said unto them, whosoever will come after me. Let him deny himself and take up his cross and follow me. Now I want to dissect this verse right here for a minute. He said to the people and his disciples, first his disciples were following and others began to join with them. And so he said unto his disciples and the people whosoever will come after me. Now where Jesus said come, he said, I'm going to the cross. I'm headed up to Calvary and I know what's going to take place at Calvary. He said, I'm not afraid. He said, I am called to destiny. I'm called to bring man back into relationship with the God who created them. So he said, if anyone wants to be my disciple, he said, you're going to have to walk the same road that I'm going to walk. He said, I'm not afraid. I've already settled with God in the garden and I've decided that I'm determined to do what I've been sent here to do. He said, I'm going to Calvary and it's going to cost me my life. He said, but I'm going to do it in spite of what it takes. And everybody who's going to be a follower of me, he said, if you're going to be my disciple, you're going to have to lose some of stuff. You're going to have to give up everything that you have a desire to hold on to. He said, you can't follow me.  You got to stop it. Stop it now and follow me. You got to walk too. The devil's alive. My voice is coming back. Come on somebody. He said, whoso will come after me, let him deny himself. The problem with all of society today is people are selfish. They only want what they want and they don't care about anybody else. He said, you must deny himself and take up his cross and follow me. I want to be a disciple. I want to follow Jesus. But tell me what does it cost? What does it cost? It's going to cost you everything. Everything is going to cost you every desire that you have for your human flesh. I talk about things that I know and you all have to excuse me if it makes it uncomfortable for you or something like that. But I don't have to talk about what happened yesterday to get my point across. You talk about old stuff in the 40s and 50s. Yeah, that's where I came from and that's what I know. I know back in those days they had a bargain basement down under the store for people who weren't willing to pay the price for the main floor. And they say, can I get a bargain? Go down to the bargain basement. There's a different price. I want to tell you there's no bargain basement here. Come on somebody. There's no other way other than doing what God called you to do and giving yourself, give your life to following Christ. You've got to struggle every day. If you're not struggling you ain't making it. You're not proving what is acceptable. No, you're not proving what is good nor acceptable. Certainly not the perfect will of God. You've got to get it perfect. You're scared. You're scared. You're scared. You can't be perfect. Yes you can. Yes you can. You can be perfect. God wouldn't call you to perfection if you couldn't accomplish it. The thing that is exciting is we don't have to do it alone. Oh, there's a helper. God provided a helper. He sent a paraclete to stand by us, to strengthen us in our weakness, to make us strong in our mind and in our desire to walk with Him. Oh, we can make it. What do you think the Holy Ghost is about? The Holy Ghost is the power of God.    Hallelujah, hallelujah. Then he went on to say, Jesus went on to say, for whosoever will serve will save his life. She'll lose it. He said, you don't even know what you're doing. You want satisfaction.  You walk around thinking, well I'm not going to do that one. That's too hard. I'm going to save myself. Jesus said, whosoever will save his life, that's the one who's going to lose it. But whosoever shall lose his life for my sake. Come on, my sake. And the Gospel, the same shall save. When he talks about saving your own life, you want to have the best of everything. You don't want any rules or regulations. You want to be like the songwriter that says, I did it my way. That's one of the dumbest songs I've ever heard.  Scripture said, in the multitude of counsel, in the multitude of counsel, there's safety. But no, we got egos that are tall as the Empire State building. And we refuse for anybody to say anything that disagrees with what you say.  One day you're going to have trouble with your voice when you preach it. You're going to have trouble with your voice when you used to be a sanga-sanga. Always find a way to put this in. We used to be very proud to say, we're the young people. We're the young people. Well, I tell you what, I used to be the young people. You're not a permanent fixture here.  You got to get on the right road and stay on the right road until you reach the kingdom of God in heaven. But if you seek to save yourself, you're going to lose it. If you're going to keep everything that you want to do and do what you want to do, you're going to hell. And who seeks to save his life, he's certainly the one that's going to lose it. But he said, whosoever shall lose his life, for my sake, Jesus said, Jesus said, quit it. This is Pentecost Sunday. We're talking about what Pentecost can do. It's not an imagination. This is proven. He says, when you put yourself headlong into service to the king, he said, that's what's going to save your life. When you get to the place where you can prove the good and the acceptable and perfect will of God in your life, you got it made. Come on, somebody. You got it made. 36 says, for what shall it profit a man if he should gain the whole world? I have to posit that because that's unfathomable. I can't fathom a man gaining the whole world. But Jesus said, if that would be possible for a man to gain the whole world, he said, what would it profit him to gain the whole world and then lose his own soul? Now there's foolishness in the thought of trying to go out with the most marvels. The one who dies with the biggest account behind his name, he's the winner. That's wrong. That's a lie. It's a faulty economy. When one who has gained the whole world and loses his soul, then to hell he goes. Jesus said, if you choose to save it, you're going to lose it. If you're willing to give it up, give that stuff up. I feel like I'm talking into a vacuum. I'm going to say it anyway, huh? Because this is what the Lord gave me for the day. What shall a man give in exchange for his soul?  That's looking pretty good. Yeah, I could have a great time with that. Whatever that is. Chasing? I'll just say it. Drinking? Smoking? Any kind of drug? Whether it be male or female drug? All of it, all of it, all of it. None of it is worth losing your soul over. None of it for a temporary fix. One that cannot satisfy. It will not. It cannot and will not satisfy.   A huge price that is going to be the end of you. And you don't know, you don't have sense enough to say, I won't take that. I'll take Jesus for mine. You can have the whole round world, but give me Jesus. Lord, when I've done my best. Lord, when I've stood my test. Lord, when I've done everything, I can't give me Jesus. Jesus will hold me. He'll take me in His arms. He'll embrace me. He'll claim me as His own. And I'll come before Him and say, well done. I'm good and faithful servant. Come on, enter into the joy of thy salvation. Hallelujah. I want to be a disciple.  You got to give it up. Turn the news. Give it to God. And it's appointed unto death. The destination of everybody in this room is death. You're not going to live forever. You don't know how long you're going to live. You don't know the day or the hour or the way you're going to leave here. When people went to this grocery store to get their groceries, they didn't know they was on their way out. When those kids got up and went to school and stood in line and received their awards and all that, they didn't know that was the end of their life. With that, what the Lord is saying is, don't try to half step. Don't try to half do it. Don't try. Well, I'll try. You're going to try. Yeah, I'll try my best. How about trying more than your best? Your best ain't good enough. You can't please God with your own ability.  And it caused your conscious to not leave you alone when you acting crazy. I had to turn to my wife. That was the rule in the house. She said, stop acting crazy. All the kids, all three of them, stop acting crazy. Y'all stop acting crazy. The Lord is saying there are idols in temples. And he said an idol is of no use to you. An idol can never serve you in any kind of way. Buddhas and all. It pricks my heart. When I see maybe innocent people with a Buddha sitting up somewhere in front of them, I can't understand that. Buddha has never done anything that cost anybody to get to heaven. So he said, what agreement has the temple of God with idols? He said, there's no agreement there because you are the temple of the living God. You're not called to be the temple of Buddha. You're called out of darkness into a marvelous light. And you're called to be a temple of the Holy Ghost. The Lord said, I'll put my spirit down in you and cause you to walk right. It'll give you the ability to say no to yourself and all kind of other distractions from God. He said, there's no agreement between you. God has said, I will dwell in them and walk in them and I will be their God and they shall be my people. Wherefore, come out.   Don't hold on to none of it. Come on out. Come on. This is the law out here and I know you in there and I know what you're doing. Drop what you're doing and come on out. Come up from among them and be separate. Who said it? The Lord? The Lord said, you ought to be different than the rest of the world. He said, you can't represent me doing what the world is doing. What kind of foolishness is that? What kind of witness is that? Wherefore, come out from among them and be separate. Who said it? The Lord said it. He said, and touch not the unclean thing. He said, if you'll do that, you can be my disciple. It may be the greatest gymnast in the world. That doesn't give you an opening for the position of a disciple. Maybe to dribble with both hands and shoot from under your leg. But that's not an entree into discipleship. The entree into discipleship is, hold on now, put your seatbelt on. Suffer it. Suffer it. Suffer it. Y'all ain't never heard this before because this is old time preaching. When we were growing up back in the 40s, we heard it all the time. It's a suffering way. We understood that it wasn't going to be a cake walk.  Because you've got to watch something on TV. Your favorite show is coming on. I want to be one of his disciples. What do I have to do? Is it something I have to say? How am I supposed to walk? Eating every day? I can do it for a while, but I can't do it every day. You know what? I want to know. Tell me what it costs. Tell me what it costs to carry the cross, to follow Jesus. You tell me what it takes and I'm going to do it. I'm going to determine that I'm going to be in the number when the saints go marching in.   Come on somebody. Now I belong to Jesus and Jesus belongs to me not for a year or time alone, but for all of eternity. You can get your kicks right here and now and go to the lake. It's a different route. I'm choosing another way. I'm choosing the way of holiness. Holiness. I want to be a disciple. Stand on your feet. Let's just sing a round of that song one more time and then I'm going to turn you into the hands of minister Marilyn Alexander. Oh I want to be a follower of Christ. Oh I want to be one of His disciples. I want to walk in the newness of life. Let me be a follower. I want to be a follower. It costs you something. Come on it costs you something. It costs Jesus something. Hallelujah. Hey man, we can't just walk through here willy-nilly. Hallelujah. Just doing whatever we think we're big enough to do. We have to submit to the Lord. We have to. We have to. We have to. He was our example. And He said that greater works. We'll do even greater works. Hallelujah. If we submit ourselves. But He has called us to do. Amen. Does anybody want to be a follower? Come on, anybody want to be a follower? Hallelujah. Come on if you haven't accepted Him as your Savior and your Lord. Hallelujah. We want the salvation sometimes but we don't want the Lord. Come on now. Come on. Hallelujah.  The one that governs your actions. The one that tells you which way to go. And which way not to go. Come on if you want Him today. Hallelujah. Is everyone in here a follower? Come on if you want to even recommit yourself. Hallelujah. You say Lord I need your help even more. Amen. You need Him to touch you. Hallelujah. Amen. And stir up the gift that's already in you. Hallelujah. Come on. Come on. Hallelujah. Hallelujah. Lord we surrender. We want you. Hallelujah. We want to be a follower. We want to submit our ways to you. Hallelujah. We want to do what you are asking us to do. Hallelujah. So that we'll reap the benefits of following you. We'll be a witness of you. Hallelujah. Amen. And when we get to heaven. Hallelujah. We can hear you say well done. Thy good and faithful servant. Enter. Hallelujah. Into the joy of the Lord. Come on. Hallelujah. Thank you Lord. Thank you Lord. Amen. Everybody's alright. Everybody's alright. Alright. Amen. Amen. Amen. You better come on while you're getting. Come on. It's okay. It's okay. Sometimes we need a little more strength. Sometimes we need a little encouragement. Amen. That's what the word is for. That's what the word of the Lord is for. God gives the man of God. Amen. A word for his people. Come on. What do I have to do? What do I have to say? How do I have to walk? Each and every, each and every day. Tell me what it cost. Hallelujah. Oh. Let me be. Come on. What do I have to do? What do I have to say? How do I have to walk? Each and every day. Tell me what does it cost. Just to carry the cross. Oh. Let me be. Father we thank you. God we thank you that you called us out of darkness.   And we thank you because it is the power. It is the power. It is the power to live right. And we submit. Hallelujah. We submit. Hallelujah to your leading. Hallelujah. We know that you know the way. Hallelujah. And so we submit to follow. That's all we have to do is follow. And we thank you in praise you. Hallelujah. For making the difference in our lives. We thank you God. Hallelujah. Hallelujah. Hallelujah. For being the best thing that has happened to us. Hallelujah. We bless your name. And we give you all the glory. It's our reasonable service to present our bodies to you. And we do it willingly. Hallelujah. Lay ourselves on the altar. Hallelujah. Sacrifice. We thank you in praise you for all that you do. Each and every day. We are helpless to carry the cross. Let me be your follow. Thank you Lord. Thank you Lord. Thank you God for calling us out of darkness. Hallelujah. Praise the Lord everybody. Praise the Lord. I'm up here too. We worship God in music, prayer, scripture. The great word of God. All to call. And a lot of times people when it's time for the offering, they think that's the end of service. But that is not the end of service. Because there's one place only in the Bible where the Lord said prove me. That means test me. See if I would do this. There's only one place in the scripture that you would find that in. And I'm going to read that for you. He said bring you all the ties into the storehouse. Y'all stop writing while I'm talking. I want you to hear me. See all the ties in the storehouse. That there may be meat in my house. And prove me. Or test me. Or do this and find out what I'm going to do about it. Then he tell us prove me now. There we have sent the Lord of hosts. If I would not open up you the witness of heaven and pour out your blessing that there shall be not room enough to receive it. And the Lord tell us to bring all the tithing. A tithing is a 10%. And the thing about God, he made it equal. If I make $100, how much tithes do I pay? That's right. If I make $1,000, all right. If I make $10,000, how much I pay? So he made it equal. So we all have an equal part in bringing our tithes to offering. We don't. We don't bear tithes anymore. They used to but they stopped doing it. When the pandemic came, they stopped doing it or they forget to do it. God want us regardless. That's no excuse. He said prove me. Test me. Try me. If I would not open up the witness of heaven and pour out a blessing there shall not be room enough to receive. Then it goes to verse 11. and he shall not destroy the fruit of your ground, neither shall your vine cast her fruit before the times in the field, said the Lord of Hosts. And we know we need God's blessings right now, His financial blessing, because gas is $6 in summer gallon, one gallon, eggs are $3 for 12. So you know we need God to open up the winners of heaven. In order for him to open up the winners of heaven for you, guess what you got to do? You got to give him 10% of your earning. He said, it belongs to me anyway. It's not yours to spend. It belongs to me. And then when you do that, give me an offering. I want an offering also. And guess what? He said the cattle on the side of his belongs to him. He owns all the money in the world. He owns all the land in the world. Everything is God. So he just made you stewards over what he has given you. And if you so stingy that you don't want to give back to him, guess what he can do? He can take it back away from you or have a basket where it could be eaten up. So we got to give God what's to him. That's all part of worship. We love to worship in songs. We love to do this and we love to do that. But finances also a part of worship.  I mean, somebody this morning asked me that. Say, how do you all just afford to go to church now as far as you go? I said, we don't even think about it. Because we know that God is in charge of a gasoline. Cause we know just like the widow, the widow who didn't have meal and the Prophet told her, and the Prophet told her, give me what little you have. She gave him what little you have and she never went hungry, her and her son. You know what? God is our provider. That's what the preacher preached last Sunday, Jehovah Jireh. He is going to provide for you. Not your job. You might be making a lot of money. You might have a lot of property. You might be doing this and might be doing that, but that's not what your provisions come from. Your provisions come from God. So I want to challenge everyone today to start paying tithes and giving an offering because it's not only tithing, you have to give an offering. He told us how much tithing it gives, but he said tithing is free will. You give what you want, but offering is free will. Be a cheerful giver and don't regret giving it. I don't regret giving to God. That's why we're blessed because we don't regret giving to God. And that's what God wants us to do, amen. And those in media land, if you want to send monies to this ministry, which is a great ministry, none of it goes to the pastor, none of it goes to the musicians. None of it goes to me. It all goes to the work of the Lord. You can send your money in. You can give a fine. And when you go to give a fine, make sure that you click Shilafate Christian Center of Long Beach because there's other Shilafate churches. But we want to make sure you give to Long Beach Church, amen. And also, if you want to mail it in, you can mail it in at 4934 4934 Long Beach Boulevard. Long Beach, California, 90805. Or if you want to just stop by church and drop it into our mailbox here, just slide it through the slot. We'll get it, amen. Because God want you also to be blessed. And you know the thing about this scripture? It's not only for the believers. It's for the unbelievers. There's many musicians top making top money. They pay their tithes in offering. I hope the Lord saved them one day because it's more than giving. It's also being, having salvation. So without further ado, you can stand and bring your tithes and your offering and put it in. We're gonna pray first. Oh, you're offering up before the Lord. Bishop got our offering. Father, in the name of Jesus. Lord, got your word. Tell, you tell us in your word that we are to test you and prove, and you will prove to us what you can do. You will open up the witness of heaven. And we all need the witness of heaven open now, Lord. Will the prices going up the way they are? The food going up the way they are? The gasoline. We need your blessings right now. Property the way it is. We need your blessings, Lord God. And we're asking you, Lord God, to give unto us. And we will give back to you in the name of Jesus, bless every offering that comes forth. Double it, triple it. Oh God, we know that you're able to do it right now. In Jesus' name we pray. Amen. Bring your offering in. And do it with joy. Do it with joy. Let's sing our offering in. Come on, give us a joy song. Give us a joy song. My service, I want everyone to repeat after me. May the Lord watch The Lord watch Between me and thee Between me and thee When we're absent When we're absent One from another One from another May the Lord bless thee And keep thee And keep thee May the Lord make his face shine upon thee May the Lord make his face shine upon thee And be gracious unto thee And be gracious unto thee May the Lord lift up His countenance. May the Lord lift up His countenance. Unto you. Unto you. And give it peace. And give you peace. In the name of Jesus, we're gonna have Pastor Minister Maryland to sing us out with our favorite going out song, amen. And hallelujah. Yes. Make you shine, hallelujah.


Is the Holy Spirit comfortable taking up residence in you? Does the Holy Spirit feel at home in you?  And the things that you're putting before your eyes, are they breaking His heart? The things you're listening to, are they breaking His heart? What you see and what you hear, do those things remind the Holy Spirit of things that break His heart? The question is, how do you host the Holy Spirit? Is He at home in you? There's this philosophy in the world called moral relativism. And that philosophy can be summarized in this phrase, to each His own. So this person believes this, that person believes that, I believe this, to each His own. You believe what you believe, I'll believe what I believe. The problem with that, is that only works so long as each doesn't actually believe His own, because eventually there's going to be some contradiction. But that's how the world lives, in the irrational, in the illogical. Everyone just believe what you want to believe, you have your truth, I have my truth, there's no such thing as the truth. That's moral relativism. And that is a mindset in the world. Now as Christians, we understand that the word of God is truth. As believers, we know that we take the word of God as the final authority. Now here's what's interesting. Is that the church has its own version of moral relativism. The church has its own version of the phrase, to each His own. You see in the church world, we don't say to each His own. In the church world, we don't say, well there are many truths. What do we say in the church world? What do Christians say? We say, well I'm not convicted about it. Well that's your conviction, but these are my convictions. Wait a minute, wait a minute, wait a minute. Since when was it about your convictions? Since when was it about your standard? Should not we live by the Holy Spirit's convictions? And would the Holy Spirit set different standards for individuals when it comes to basic holiness? That's something to think about. You see, if you want to be a friend of the Holy Spirit, if you want to stand out, if you want to have that uniqueness about you, you have to learn to live at a higher standard. Amen. You can't do what unbelievers do. You can't even do what some Christians do. I'm not saying you have to do these things to be saved. Sure, if you're truly saved, you'll want to live holy. But you know there are some things that you won't be able to do, some places you won't be able to go, some things you won't be able to watch. You know there's things that I won't watch, that some Christians are perfectly fine with. That's not me slamming other Christians. I'm in no way better than other believers. We are all sinners saved by grace. But maybe, just maybe, God's calling you to a higher standard, because that's what it takes.  But when you start to walk in friendship with the Holy Spirit, you begin to lose your lukewarm friends too.  You're taking that too far. Well, you've got to live a little. Well, and I understand some people are really weird, and they get really strange, and it's not really the Holy Spirit talking to them.  I'm not talking about weird people. I'm talking about holy people. I'm talking about people who understand that they're going to have to raise the standard of their living.  They're not going to spend hours on social media. They're not going to allow certain things that are distracting and secular. You're just going to have to live at a higher standard. Is it worth it? Absolutely. No sin is worth the anointing on your life. No compromise is worth the sweet presence of the Holy Spirit himself. You can't replace that. You can't replace it, and you have to learn to protect that anointing, protect that relationship with the Holy Spirit. That's how you have to live. Not in paranoia, not in fear, not in legalism, not in superstition and all these rules and regulations, but simply out of love for the Spirit. You carry that relationship with the Holy Spirit and you guard it. You protect it. You don't let anyone... That is my friendship with the Holy Spirit. If it hurts him, I won't do it. If it makes him even slightly uncomfortable, I move it out of my life immediately. I don't want it. I just want him. So, you want to make the Holy Spirit at home in you. Here's how to host His presence. Number one, avoid the demonic. This should be simple enough. I remember one time I was ministering in the Midwest and I think it was a youth service. I don't quite remember. But I do remember pooling up to the service and noticing that there was some spiritual warfare in the atmosphere. I just knew there was going to be some resistance. So I get into the service. I'm standing there in the front row, ready to preach. The worship is continuing. And suddenly out of the blue, I sense this almost like a brushing across the back of my neck. And I got chills all over my body. Like a brushing across the back of my neck and I got chills all over my body. It wasn't a physical brushing, but in the spirit I can sense something here. And there was something very ugly, very dark right behind me, right over my right shoulder. And I just sense this heaviness. I turned around and I'm looking behind me and there's this guy dressed in all black. He's got these thick, like those things, like those plugs that they do in the ears where they extend them. We look like, almost like, it almost looked like his ears were made of Play-Doh. Like it was stretched out all big. He had a lip piercing, a nose piercing. He had tattoos all over.  I turned to look at him and he's got his eyes locked right on me. And he's looking at me and he just had this weird grin on his face. He grinned at me and just starts nodding his head. Like, yeah, it's me that you're feeling. So I said, okay, that's fine. I get on the platform. I began. I said, everybody take three minutes, pray in the Holy Ghost. Boy, that guy, you could see his whole demeanor shift. He was very uncomfortable in that atmosphere and he ended up leaving the service. But the point is, the demonic and the spiritual clash, don't allow the demonic in your life to any degree. Not even a little bit. This doesn't mean you go avoiding people who need deliverance and freedom. No, God sends you to them to drive out demons. You need to do that. But what actually begins to happen here is you begin to recognize demonic things and you avoid your participation in demonic things. Number two, you want to host the presence of the Holy Spirit. Minimize the secular. Now, the secular is more subtle than the satanic. Let me say that again. The secular is more subtle than the satanic. Certain things diminish the power of God on your life. There are certain things that cause your faith to be stifled. Think about in Mark chapter 5 verse 40, where Jesus goes to the home of Jairus and he goes to raise the little girl from the dead and people in the building in the house start to laugh at him. What does he do? He throws them out. He removes them from his life. There may be a point where you have to start disconnecting from secular people who have too much of an influence on your life. I sense a strong anointing on that. There's someone watching me. You know that people who are secular are influencing in your life. And I'm not talking about quarantining the gospel and never reaching another lost soul. Again, we're in the world, not of the world. We participate in conversations and interactions with people who are of the world, of course. But I'm talking about giving someone a place in your life where they have influence. The Holy Spirit will not share influence. Let me say that again. The Holy Spirit will not share influence. He will remove people from your life who are influencing you in the opposite direction you should go. That's a fact. The Holy Spirit, James says, is jealous over you. So there will be some things that are secular in your life that the Holy Spirit will minimize that influence. Now, again, we can't be completely detached from the world. Some people say, well, I don't go to this business because they believe in that, or I don't go here because they believe in that. Do you realize that everything in this world has touched something unclean? That everything in this world can be connected to some type of demonic or sinful agenda, just a reality. So I'm talking about not participating. I'm talking about minimizing the influence of the secular in your life. Now, there was this service that I was administering at in Southern California, and man, the prophetic was so strong. I started seeing in the prophetic, this only happened to me like two or three times. I was actually able to hear. You may call me crazy. I was able to hear the thoughts going on in people's heads, and I was calling it out through the prophetic. I can't turn that on and off at will. It should be kind of cool, but it's only happened a couple of times. In almost 20 years of ministry, I think maybe three times I've had it to where I could hear in the spirit so clearly, and man, the prophetic anointing came on me so strong. And I say prophetic anointing, not that there's an actual literal prophetic anointing. It's one anointing, and the prophetic expression was stirred by that anointing. So I'm walking around the service, and I'm calling people out, pulling them out of their seats, saying, you're going through this, this, this, and this, and very specific things about their lives. And so I'm in this flow. I'm enjoying it. I felt like I was in a whole different world.   I watched her because she was so distracting about it.  And I literally, this is what I did. I had the microphone in my hand. I watched her. She sits down. I go, well, church. I sensed it lift. I'm released to the Lord. I'm going to turn it over now. And I handed the microphone over to the pastor because this girl walked in and just sat down, decided to be a distraction to everyone. She's a young teenager. Now I didn't call her out. I didn't get the conversation with her. I just knew that because of the distraction, I was pulled away from it. So I don't even necessarily say it was the girl's fault, but I had become focused on her because she distracted me, and I lost sight that pinpointed sight in the spirit. I lost it for that moment because of the secular. Did she do anything sinful? No. Was she practicing witchcraft? No. Did she do something blatantly obviously wrong? No. It was just a secular distraction. Sometimes I really do believe that the mundane world itself is an insult to the glory of God. So number one, avoid the demonic. Number two, minimize the secular. Number three, subject the flesh. 1 Corinthians 9, 27, I discipline my body like an athlete, training it to do what it should do. Otherwise, now this is Paul the apostle writing this. Get this. Otherwise, I fear that after preaching to others, I myself might be disqualified. Whoa! That Paul the apostle would write that? That's how much of an enemy the flesh is. You see, you can cast devils out, and you can be free of the demonic by giving your heart to Jesus being filled with the Holy Spirit. Here's the problem with you.  You're stuck with you until the day of redemption, until the day we receive our glorified bodies.  The flesh does not come and go. The flesh shrinks and grows. It grows stronger and weaker depending upon how you interact with it. Now, there was this one time when I prayed for this woman who got healed. I'm exhausted. I'm tired. I'm praying with her, believing for her miracles. She gets healed. And she says, thank you. Thank you. Thank you. And I said, you're welcome. I'm half asleep. She walks away. And as she's walking away, I realize, oh, she thanked me, not the Holy Spirit, not the Lord. So, you may call me religious, but these are the types of things you have to do. This is the standard. I ran after her and I said, ma'am, I don't want to sound rude and I'm not trying to correct you just for fun. I said, but I need to make it clear to you. I did not heal you. Jesus healed you and he's the only one who deserves the glory. So, I'm doing all this. I think it's like this intense moment. She goes, oh, yeah, I know. Thank you. Thank you. And she just keeps walking away. To her, it was just probably something weird that I did. But to me, it was a check in my heart and the Holy Spirit revealed to me, that's how it begins. That's how it begins. Wow. Little by little. Little things we don't allow ourselves to correct. So, you want the Holy Spirit to fill that home in you. Number one, avoid the demonic. Number two, minimize the secular. Number three, subject the flesh. Thank you for watching EncounterTV. Don't forget to subscribe and click the notification bell. Also, help us spread the Gospel of Jesus Christ in the power of the Holy Spirit. Make a one-time donation or become a monthly supporter by clicking on the donate link now.


Ladies and gentlemen, the President of the United States, and the Vice President. Please be seated with stars and stripes, Skipper and Dennis Conner, members of the crew, and ladies and gentlemen, to the day the cup that went down under has come back up.  And by the way, you might be interested to know that Prime Minister Hawk of Australia and I had a little bet on the side. If Cucabura III had won, I was going to give the Prime Minister one of those cowboy type hats that I wear now and then out at the ranch. And if you all won, well, there it is. It'll be revealed. That's the Australian version.  I just know that whenever I put that on, I'm going to find myself turning to Nancy and saying goodbye, mate. But there are so many people who help to make this victory possible. All together, the United States was represented by six syndicates in Australia. Each had its own yachts, and each involved literally hundreds of people, bringing the best of American technology to bear on the complicated challenges of 12-meter racing. In designing stars and stripes, herself engineers used computer techniques to provide the yacht with a wing keel and a special rounded nose. Plastic experts gave the hull a coating that sheeted the yacht with thousands of tiny V-shaped grooves called riblets. Sailmakers used a mixture of Kevlar, Mylar, and an entirely new fabric, Spectra, to produce hundreds of sails suited to every conceivable weather condition. And stars and stripes was fitted with an onboard computer to monitor performance and communicate before the race with computers on shore and in her tender. I just have to believe it says something about the competitiveness of American technology that this time around, the United States entered perhaps the best designed, most technologically advanced 12-meter yacht ever crescent. But no matter how sleek the yacht, it still all comes down to what the skipper and crew do with her on the open ocean. To the skipper, the navigator, tactician, mainsail trimmer, pitman, bowman, sewerman, grinders, and trimmers of stars and stripes, congratulations. You performed up to the highest standards in conditions that were arduous and exhausting, and you made considerable sacrifices to do so. And now, if you'll permit me, a word to the skipper himself, Dennis Conner. Dennis, in 1983, you sailed against the Australian Challenger in what was universally acknowledged to be a slower boat. But your skills as a sailor were such that you forced the Challengers to go all seven races before Australia, too, finally took the America's Cup. In the races off Fremantle, you showed your skill all over again. During the Challenger final race against New Zealand, stars and stripes blew a jib to many skippers that would have been caused for panic. But you only said, hey, this is too bad. That's not all I said. All that you said that was printable was a pain. But then, while your crew scrambled to replace the bad sail, you calmly tacked to keep your opponent from gaining the wind. And in three minutes and two seconds, both the new jib and jig were up, and stars and stripes won the race. And the finals themselves, well, there's no better way to describe your performance than to quote the skipper you defeated, Australian Ian Murphy, Murray. At the suggestion that stars and stripes had simply had better luck, Skipper Murray answered, I'm not a great believer in luck in sailing. The wind Dennis left us was pretty much zilch. He won because he was always in the right spot. Beyond your skill, Dennis, there's the matter of your commitment. The matter to put is simply of heart.  In his words, quote, before the last tack, Dennis said, OK guys, this is the last tack in the 1987 America's Cup. I turned around and looked back. He was crying. He had tears in his eyes. And the crewman went on to explain that you have to remember that this hasn't been any gravy walk for Dennis. He's a regular American guy, a smart guy who worked his way up from the bottom and deserves the credit for what he's done. Well, Dennis, today we congratulate you, and today we give you that credit. Thank you. I'm going to word now to your Australian hosts and competitors, Ambassador and Mrs. Dahlrippel. Of course, millions of Australians must be disappointed by the outcome of these races, just as so many Americans felt the 1983 loss so keenly. But I want you to know that I've heard again and again from Dennis and others that the Australian people could not have been more open, friendly, or sportsman-like. On behalf of the thousands of Americans who have visited Australia for these races, I want to thank Prime Minister Hawk, the Perth Yacht Club, and the Australian people themselves. I can't help thinking that the America's Cup has brought our two nations already close, still closer. For in following these races, we were all able to share something ancient and deep within us, man's fascination with wind and water. Listen, if you wanted the words of sports writer Tony Champlin, in sailing, there is a term called lift, which is both technical and poetic at once. It describes the moment of acceleration in a sailboat, the moment when the sails harden against the wind and the boat begins to slide forward faster and faster until you can suddenly feel what William Buckley meant by the title of his sailing book, Airborne. How something moving so slowly about the pace of a moderate jog can impart such exhilaration in this moment is probably unanswerable. Hang gliding, dropping in a parachute, doing barrel rolls in a light airplane, the thrills are easy to understand. But the moment of lift in a sailboat is just as much a leap off the earth, Airborne. Well, gentlemen of the Stars and Stripes, for a few days, you enable all of us to become Airborne. And we thank you. Thank you, Mr. President. As you might remember, I got a phone call from you back in 1983, and Tom answered the phone. I think he said the president saw on the phone and wants to tell you that you fouled up. That's the printed version anyway. Well, you might remember that I made you a personal promise at that time to do everything I could to bring the cup back home to America where it belonged. So here it is. This is not only a victory for the great crew and team of Stars and Stripes. It's a victory for American technology, a victory for the American will to compete anywhere in the world. And I might say, and be able to win. It's really a victory for the American spirit, of which you've done such a tremendous job to be our leader. And I can't tell you how much it means to the entire team and support crew of Stars and Stripes to be part of this tremendous victory and bringing the cup back home where it belongs. And I'd just like to say thank you all for the tremendous reception that we got. We had no idea what it would be like when we got home. We were 12,000 miles away, and we were just concentrating on winning the cup. And this meant so much for us to come back here and have this tremendous reception. And I just can't tell you how great it is to be back home in America. It really means a lot to see all of our friends and supporters to be with us in this tremendous victory. So at this time, trying to remember all my lines, Bob Hock made sure that he sent me a little message to go along with your cup here, and I'll find it in a second. Don't worry now. My dear Ron, enjoy the hat. You can keep it. Well, that's nice of him there. Take pleasure in the cup. But remember, it's only a temporary possession, and we'll be back to get it in 1990. Congratulations and best wishes, Bob Hock, Prime Minister. So congratulations. And I'd just like to take a moment and add to the president's comments about what tremendous people the Australians were. In defeat, they couldn't have been more gracious, and they just were a wonderful sportsmanship. And any of you that have the chance to visit Australia will find out for yourself. But I'm sure any one you talk to on the Stars and Stripes group will tell you and reaffirm what tremendous people they were in Western Australia, and they were really part of the whole cup. So my congratulations to people of Australia. As a remembrance from the Mr. President, from the crew of Stars and Stripes, we'd like to have you display this wherever you choose and remember us here in our victory, a half-model of our boats, the first one we've seen, and we'd like to have you have this as part of our victory. Thank you very much. So if you'd help me hoist this cup, I'm sure everyone would like to take your picture here. Thanks for having us. It really means a lot to us. Thank you very much.


Okay, we can get started. Welcome to the Yachter Project and Open Embedded BOF. My name is Armin Custer and I work for Monivista Software. I've been working on the Yachter project for about six, seven years. I'm on the technical steering committee for the Yachter project and I'm the stable branch maintainer for Paki and Meta Open Embedded. Hi, everyone. My name is Dengla Deshain. I work for Linaro. I'm the committee manager for the Yachter project. So we definitely want to thank you all for being here today. I've been involved with the project for a couple of years as well and we do this BOF at every of this ELC conference. So I mean, this is usually the time when we really want you to ask questions to the developers and the Yachter project people. So today, we are going to start with a couple of information that we want to share about project updates and status updates and then hopefully it will be quite quick and we'll open up for questions. So we have a few people from the project in the rooms. Hopefully we can answer the questions and if we cannot answer the questions, we'll get you the answers as soon as we can. A couple of project updates. So this is a fun one. I don't know if you've seen this slide. I mean, that was actually one of the recent Linux Foundation events that was presented by Jim from the Linux Foundation. The Yachter project has basically put Linux on Mars. I know if you missed that news, if you want to learn more about that, I thought it was a fun fact to share with everyone. There is a small module that actually runs Linux that has been used for the Mars Insight project last year. So if you want to learn more, I mean, you can ask Google, you will find some interesting data. That's a fun fact about the project. Since we've done the last both, it was an ELCE last October, the project and the developers have made a couple of releases and we are actually working on the next release for October. I just wanted to give a couple of numbers and all numbers about that shows, I mean, how much changes and what we are actually doing. I mean, how many people get involved in the release and how many changes. So it's, I mean, it's definitely a significant amount of change for the size of the project and number of the developers. We've done a couple of stable releases and as I said, we are marching toward the 3.0 release and we are in the middle of the cycle for now. Yeah, so you noticed that we are actually switching, we've decided to switch from 2.7 to 3.0. The reason is actually on the next slide. We are very happy about the state of the project for different reasons. Many changes happened last year. So they are technical, that's a lot of the optimization and the recent changes are you're going to learn for the next release and so we are very happy with the state of the release and so happy that we actually want to change and make like a much bigger number. So that's, we've completely refreshed the hardware infrastructure that we use. You probably know that building all the York 20 open embedded recipes takes a significant amount of resources. So we refresh the infrastructure. We've completely redesigned the way we also do the testing. So we have now pre-testing before each of the merge. We run on all the testing on QMU and emulation on hardware like X86 and ARM, which is also new. So this is a significant release that is going to happen in the next few months. The next change that also happened this last year, which is not a technical change, but a very big change for the project, is we've ratified a new government's agreement and we have formalized the creation of the technical steering committee. So it's a big change for the project, the way it's organized. The TSC is made of five people. Three are actually nominated and elected by the York two members, board of members and two are coming from the open embedded side of things. So you have the name here. And overall, the responsibility of the TSC is to everything that relates to the Yachto project, all the gate trees, any kind of issues with maintenance. The infrastructure, the testing, the release process, the compatibility program, everything that deals with the Yachto project and that this is now under the responsibility of the TSC. The goal is not to have the TSC decide and do everything, but when there are issues or when decision needs to be made and that the committee cannot reach to an agreement, we will actually go and use the TSC for that. There's a wiki as well, if you want more details. Okay, so one change which we are going to do soon, we've started to mention that on a couple of mailing lists, but the change is significant enough that we wanted to use the opportunity today to have like lots of, I mean, quite a bit of people in the room. We are going to change our mailing lists. And the mailing list is basically the heart of, I mean, everything that we do as an open source community so it's a significant change. Many projects have started to use groups.io and switching away from Mailman or new projects are actually using groups.io without never being able, never used Mailman before. So this is, we are planning to make the change and Michael is in the room here. The week of, next, the week of September 1st, the weekend of September 1st, which is a public holiday in the US. We hope that not so many emails will be sent that day. And we will send instructions. If you are on a mailing list, we have 3000 people actually on our mailing list. You will get all the instructions, all the account and everything. I just wanted to mention that this is going to happen. We will be on the hook to make sure that it does not have too much impact on the workflow on anything. And for now, we are only going to do that for your YoctoProject.org mailing list. If everything happens and everything goes well, we will also plan the same migration for open embedded mailing list, which is where most of the patch and most of the discussion happen. But just that you know, one small technical issue and that we have to highlight is that the name of the mailing list will change. We had to deal with some DNS issues or limitations. And so we are actually moving every list to YoctoProject.org to list at dot YoctoProject.org. Again, if you have any questions, any concerns, if you hate Groups.io or if you love Groups.io and you want to talk about that, come to me or come to Michael in the room and we can discuss and chat about that. Something else that I wanted to mention also that we started three months ago. It's quite an interesting story. Someone from the community stepped up and came to us to the advocacy mailing list of the project. And he wanted to contribute something and it's time to the project. So Joseph is based in Germany. I said I want to basically start doing some live streaming sessions of me and showing what we can do and how we can actually use and start with the YoctoProject. So it's meant to be mostly for people who start with the YoctoProject, like an introduction sessions and how do I make my first build and so on. So once every month, and we've done that for five times I think already, is coming and basically does like a simple thing, like build my first image, build my first recipe, make my first layers and so on. So it's very open about what you will be talking next. The next session is on September 10. If you have not watched yet, I encourage that you just have a look. If you have any idea about what you would like Joseph to talk about, let us know. We can give the idea. If you want to help Joseph and make your own sessions, that's also something we will welcome. It's a very interesting story because it came out of the blue from the community. There are many ways you can actually contribute and help the project. I mean, it's not just sending patch or sending money. We also take patch and money, but just doing anything like that is actually very welcome and we are very happy to see that. All the videos are also uploaded on the YouTube channel if you want to look at the past video. Next thing, which is also like a big thing which happens this year, we are going to do the first ever Yocto Project Summit. So if you're here and if you know the Yocto project, you're probably familiar with the Yocto Dev Day. We've done that many, many, many times. We used to have like one day where some, we gave like trainings about the Yocto project and open embedded. So realize that the trainings were sessions about new things or topics about the Yocto projects. What we really wanted to do is slightly different. We want to submit like a conference about two, so that we get a chance to have the developers and the users and everybody. I mean, that I is actually involved with the project or just using the project to come together for like two days. The first day will be mostly presentations and talks and we are actually opening for CFP right now. So there are the instructions if you want to submit your own talk and we will actually decide the agenda, I think sometimes by mid of September. We definitely encourage you to come and tell us about what you do. I mean, so you probably think you are not doing something very interesting with Yocto or maybe you think that everybody else is doing the same thing, but we really want to hear what you guys are doing with the Yocto project. Whether you make a product or whether you will have some contribution. I mean, we are very open about hearing from you. So it will be the two days right after ELCE. It's in France, in Lyon, and we'll have some reception evening, social event the first evening. And yeah, you are very much welcome to join. And yeah, so that's it in terms of, I mean, a couple of updates we wanted to share. So usually this both is really up to you. I mean, to come and ask questions. So I'll go down and I'll share the mic and we'll try to get the answers. So we have a couple of people who can actually answer, hopefully all the questions. If you don't have any questions, that not going to be a really good buff. So I really encourage that you come with questions. So who wants to start with the first question? Yeah, you might need one, Mike. What are the barriers to an LTS version of Yocto? Why do you start with the tough question? You want to? It's a couple of things. One that keeps stopping us initially has been QA, keeping and maintaining the quality that we have for previous release. The other piece is mostly political. How do you decide an LTS for the Yocto project? Who's going to make that decision? And obviously the maintenance is, who's going to maintain it and what they maintain? Do you continue doing what the stable branch maintainer does or do you have something different? So it comes up every year or so in the meetings. Yeah, yeah. So like what are you thinking of? So as Armin said, I mean this is something which is, I mean one of the biggest requests we hear from everywhere. So this is an open source project. So I mean the project is good at actually maintaining the master branch and adding new features. And I mean there is no doubt. The maintenance right now, I mean the options is to actually engage with someone. I mean I actually will do that for you. About the project being able to actually itself do some LTS. I mean some other, I mean like they, I mean Ubuntu or all that. I mean this kind of model where one specific release would be maintained for maybe five years. It boils down to actually resources. And the problem I mean at this moment, we don't have resources. So if the open source community by itself and for free is not going to do that, which is obvious. The other option would be to actually collectively, I mean through the Yocto project membership for example. I mean we would add more resources to actually do that. So that would, I mean this is something we could discuss. If there is enough members, enough companies interested in joining the project and say I mean this is what we want. I mean the Yocto project is based on membership. So every people join, people vote, every decision is voted and so on. So if there is enough resources to do that and if the membership agree to do that, that can happen. If it doesn't happen collectively for free by the open source community, it can happen in the membership. And if it doesn't happen in the membership, then you have to do it yourself. That's it. So and the discussion we've had is yes, some people are interested, some people could join if we were doing LTS, but right now I mean this is not materializing to something which exists. But that's something we discuss very often. Yeah, so we work in the same company and we also have the same requirement for like seven years after the last sale. And we currently do maintain LTS for Krogot and THAT and we plan to maintain them for at least seven years. So and we also get approval to share our branches somewhere on GitHub. So we plan to do this. If somebody is interested, they can just use our branches. But we obviously don't do the full testing cycles Yocto does, but we do use them in production. So they are get tested in the main product QA cycles. This is good, really good. The only issue is it gets tested for your very specific use case and product, which is not the same thing as being tested and certified as a release by Yocto project. But it's the first step. So again, I mean the only answer, which is unfortunate, but the answer is definitely, I mean there is resource involved. So if there is enough people interested and willing to participate and contribute resources, yes, I mean we are very open to do that. Especially with what I mentioned earlier and all the improvement in the testing. A lot of the testing has actually become like automated. So I mean if we want to run more release, what we need is more computers to actually do the testing. I mean to some extent. So yeah, there is a scalable process, but we still, I mean we will still end up into missing some of the resources. Yeah, of course, but we are still, we are doing better with automation. We need, we can tell you, I mean Michael, we can tell you what we have today, so. So the tests right now are running on two generations old, rather high end Intel CPUs. They have at least two terabytes of storage and 128 gigabytes of RAM. And we use an NFS backing for part of it. So we require 10 gigabit network on these machines. Yeah, yeah. These are fairly similar machines to what you're using. I think we're at 96 cores, but very close. I just want to go back a little bit with the LTS discussion. And the question I always have, and I heard this discussion many, many times before is, what do people actually backport for more maintenance in LTS? And when do they stop backporting things? The question is, you know, when does the effort to do the backporting by far eclipse the effort to keep on a rolling, progressing move forward? And, well, I don't have the perfect answer for that. Well, there's probably no perfect answer for that, but I would like to understand from people who are actually doing backporting. And I did some of that for some things, for some CPUs and things. When is just not worth the effort anymore? And the other experience that I made is, you can push moving on to a new release or so for that much time, but then the effort that you have to put in is a big, big step forward to move forward. And for me, it always looked like it's easier to do small incremental continuous integration, keeping up the date with the new releases rather than doing the LTS in the backport effort. Anyone who wants to share some experience about that LTS or any reason why people cannot upgrade? I mean, that could also be a valid reason why people cannot keep up with the anybody wants. So in our case, we do regular updates on our main development branch, but we have stable branches that customer like to stick on them and they expect only some minor bug fixes and security updates. So for that one, we are using kind of LTS model. So but the main, like it's too risky to update them because the stack, the Yocto is not only the part, like it's only small part of the whole software stack. So if you update Yocto, it has a ripple effect through the whole software stack. So it makes it not that stable branch anymore. Yeah, security and bug fixes. So I think this is a good feedback. We can always take it to the AB, but I think people have discussed all the pros and cons. And I think LTS, as with time, it has maintenance cost as increases. And I think so there are policies, like what policies you want to institute? Do you want to do package upgrades? Are you doing new feature development that needs newer libraries? Now, do you want to build, you know, backport new libraries or not? What's your policy for LTS? So and that defines the cost structure to it. And it's not something small. And for an open source project like this, you know, this is a big step. And we are certainly interested, as Nico said, but again, you know, we are limited by our resources. So the TSC for the decision about the policy, but the AB for the resourcing on the thing. Yeah. So any more questions on LTS? I mean, that seems to be like the topic. I think it was the same thing as the last part for me, LTS came a lot. So maybe we should do something about it. Anyone? As I said, if you don't have any questions, that's not an issue. Any experience? So this is going to be the most important question of the day. How do you guys come up with the names for the code names for the releases? Just in general, what's the primary reason behind the code names? So the algorithm is simple. Richard made the decision. So one day we just learned from Richard what the next release name is going to be. That's it. And so, yeah, that's how it came to us. Okay. I think we have stories about the very first names. And then, I mean, we... Yeah. So these are game characters. And earlier, they didn't follow any convention, but now you will see that they are in chronological order. Like, you know, they're alphabetical order, at least. So, yeah. So I think, but they are totally random. There is no logic behind them, as such. Yeah, I think the latest alphabetical series has been from Total Annihilation, and Zeus is probably the last one in that series. So there'll be a new video game. I know there are several people that wanted to ask about CVEs. Are they in the audience? So I think it comes to the same LTS conversation. I was involved in Yachto over a year now, and one of the first impressions was it's great. It's used by everybody. But why do we have so many CVEs in these stable products? It just doesn't make sense. Then I realized that every single company is doing their own CVE-backport business. Nobody's actually giving back maybe a few companies, I think Intel is doing a great job, and I think I also saw Garmin as well. So I think the, as a user, it gives bad impression that, you know, we have all these vulnerabilities, nobody's addressing them. So what do we feel about this? So the question is, who wants to answer this one? So yeah, contribute them, right? Nobody's saying no. Essentially, we have what we have, and I think that's a good feedback. But I think, as you can see, that most of projects, you know, who is doing the security updates, you know, project itself, they do based upon what they can do, but mostly these are like deployed products who do this and then upstream them. So my request here is to everybody who's using Yachto project to upstream as much as they can in their CVEs. So, you know, that's a collective way to fix it. We don't run like, you know, a separate team that we can afford that here is our security response team, right? So I don't think we can do that. But yeah, I think my request is there for everyone to, you know, upstream their fixes as they find. Yeah, I just want to add that, holy, that it's, as you can see, every release is pretty cutting edge. Like right now you look at it and we're like at 5.2, kernel 5.2.9 or something. And then GCC is like at 9.2 and Bing Utils at 232. So every release we try to keep up with like the closest that we can to what's upstream. And that is kind of a reason why sometimes a lot of CVEs come, right? Because we release with the latest possible version. But at the same time, it's hard to maintain that version for a long time. There's a process issue as well. If you have a CVE for Thud, I can't take it a stable branch maintainer unless it goes into Warrior first. And it is done in Master as well. So you can send the patches, but they may not land in a stable branch unless everything, you know, before that gets fixed. And it's like, who does that? Don't look at me. Just wanted to make. So when you fix CVE in the stable branches, it's still alive. Sometimes you upgrade the version of the package. Sometimes you apply the patches. What general logic you're using? Anything else? Anyone? I want to follow up on this. I think what I was expecting is a kind of mailing list where every company has some packages that they care about. And they share the CVEs and take some work, right? So it's not, we can't expect everybody to do all the work, but rather create that communication environment. I can say, I care about binitiles. I'm going to take care of this. And then the next person takes care of the something else. Right? I don't even see that right now. So that's bothering me. And so you mean like mailing this on the Yocto project? I mean, I'll just say most of the work in CVEs has been done by the commercial partners, mentor ourselves onto this. And a lot is going straight to outsource, as Kim was saying. So that communication is happening, but it's kind of happening directly between the companies. So our secretary lead, Mark Hadley, talks directly to other partner companies. So it's not really happening through Yocto project, but it's happening and we're all contributing back to Yocto project. So we're not using Yocto project as a center for CVEs because there's no staffing, but it is definitely happening because it's crucial to our business and everyone else's business. And so it's happening. It's just not happening in a visible way. So, and I think when we talked together earlier, and I think there is value in making it more visible because people ask and they don't realize a lot is going on with their CVE process, with the Yocto project. They're just not visible. And as you say, there's a security mailing list that's just quiet because as I said, most of the communication is outside of that. So I just want to say there's a lot going on. So what would it take to make this discussion more public? So you take that as a feedback? So a long time ago, I met with some Toshiba folks and they were working on a project to build Yocto using Debian sources. And their motivation was for IoT devices that had long lifespans. And further, by using Debian sources, they could take advantage of LTS Debian and their management of CVEs to provide updates. I admit I haven't looked into that project in a while, but is there any one around that knows the status of that, or if that's even viable, what the challenges are with that kind of approach as opposed to using the project? I think that's the meta Debian layer, right? Can we just use that or wants to talk about the layer? Except, Ken. Yeah, so I think that's an interesting approach. I think it's still alive. They still are following up. You can see some talks they did in this conference. I forgot when the last one was in Europe, I think. So it's an interesting approach for the project in general. We target across build systems and what you end up doing is just not sources, but also patches and this and all. So you end up basically creating additional shim that you have to maintain on top. So it's quite a bit of work rather than just simply pointing to Debian sources and building. The reason how they store sources is also not very homogeneous. In some cases, it's some gate. They'll commit into the gate. In some cases, it is like a tar ball and then they will patch it. If you have to do something like that, I would see that it has to be wholesome. And you cannot go case by case basis because Debian has like 75,000 packages or something like that. So I would rather concentrate on creating a process that we have for the project and concentrate on that one and maybe collaborate with other projects like Debian and others. And that gentleman was saying there to have our security mailing list and what needs are there and approach it from that way rather than sneaking in through into the Debian by building the sources. I think it's not a viable approach in the long term because they do change things. At that time, you might have to change your formats and stuff like that. So I would think that the effort-wise, it's probably a more progressive effort if you had like the security working group or some ways to share your CVEs and bug fixes like that. I think that would be probably a lesser effort also because in this case, you're not marrying two very different build systems. Anybody wants to talk about any experience or anything that you guys are doing with the Yocto projects? Any things that pain points? I mean, I would be surprised if there are no pain points. I wasn't going to talk about pain points, but what I was going to ask is besides the stuff that we've discussed, is there a to-do list you guys have for people who are interested in contributing directly? Yes, so there are a few things that the project is doing. So first, there are meetings. Like, there is a monthly technical meeting that is open to everyone. So I mean, the core developers join, and that's where some of the key new features are being discussed or new issues. I mean, so that's every first Tuesday of the month, something like that. So that's one thing.  Then, I mean, we heavily rely on Bugzilla.  So at the beginning of the cycle, we do like a planning phase. So we look at everything that exists in Bugzilla, and we try to say, okay, this is going this, we can do this, we can do this, we cannot do. So during the planning phase, you can also help and like pick some task and say, I'm committing to actually doing this task for the next release. So that would be one way. Recently, what we started also, we had people who said that we want to contribute, but this is way too difficult. How do we start? So we have these newcomers. I think we send an email once every week or once every two weeks, where whenever we find something on Bugzilla, we find something that is very trivial. We don't do it. We don't fix it. And we take it as something for somebody who is new to actually come and start. So there is a newcomer list somewhere on the wiki, so which is really, I mean, and like what I said at the beginning, this is for somebody who is just sending your first patch.  But at least it's learning through how to actually contribute and how to work with our community. So we do this on the two different sides. So for the very first few patches or if you want to contribute and really contribute to the release and be part of the technical team. Does it answer the question? Every Thursday morning, we have a weekly bug triage. So whatever failed at the builds or what bugs came in, we look at it and say, who's going to fix what goes into the newcomer's bucket and things like that. Yeah, that's actually even more than that. We have a triage team, a squad team, which is actually rotating. So we have like a SWAT team, sorry. Okay, yes, but that, so there's basically five, six people which we rotate every week or so. And the role of these guys, just to monitor for build failures and report and try to do like the first personality. So if you have someone and if you want to actually help, the project is very helpful. It's testing master and master next. And we need someone. I mean, there are issues and sometimes it's not an issue sometimes. So we need someone to do actually the first step triage. So it would be one way. So if you have people that actually want to start engaging and work with that, you can also come to Armin and I and we can actually help you with that. You can also look at the Yachta project weekly and then the planning is there and the features for release are there. And actually it gives you a summary of the bugs that are planned for every milestone and what their priority is basically. So if you're interested in fixing something, you can go ahead and just fix it. How many people use like the SDK or the extendable SDK or depth tool? Okay, because we're kind of looking for somebody to take on the technology to maintain it because we don't have maintainers for that. So that would be a good place to get involved if you like. Otherwise we may drop them on maintainers. Yeah, I don't know if I can maintain it but we certainly put depth tools not able to run menu config for the kernel as well. So it's a different flow. Some people like depth tools. Some people like BitBit. It works for some. And I would just say that I wouldn't like to die. No, it's useful, it's definitely useful. That might be a topic that's a bit petty with the rest of the discussion that's happening here but you mentioned if we have pain points. Before talking about pain points I just want to mention that I enjoy Yocto a lot. I'm always amazed that it can build for seven hours and it actually delivers something that you can run on your system. To me it's still incredible. Anyway, so there are many pain points on the flip side. One of them that I stumble across a lot is a state mismatch. And I've found in the manual that there is a big minus S print if they'll try to explain why it's not matching but I'm having so much difficulty finding information in there and I'm not sure how it works, how it traces back. If it goes to the estate mirrors to find possible targets and which estate it finds as the possible the nearest match and how it compares. But I find a lot of times I will dig for because I'm trying to save hours. When it triggers a build of one or two components I don't mind but when it triggers a build of libc then I'm in for the full rebuild and I don't understand why sometimes so it's kind of weird. I'm just wondering if there are tools that I'm missing or analysis that I'm not performing correctly. I mean a hint that I can give is that we have a CI infrastructure so our builds are being performed inside Docker containers and inside GitLab and each of the runners actually will rsync the estate folder back to a central server that we maintain. So each one contribute and so we have a central, I think we use the estate mirror variables to declare and it's a simple HTTP serve of all of our estate folder and it looks like it doesn't go there to find the diff and the possible candidate. So it's always trying to find something on my machine as a possible candidate and it's diffing against that. So first of all the setup you use is very common so many people use that so I mean there is nothing wrong with the setup. Which tool did you say that you are using? And you are on the recent version of Yocto? So I think you have to also look at what you're building right? So if you're rebuilding libc for example then all bets are off. So the reason is because and I think if you were at Yocto Dev Day there was a talk on hash equivalency. So there is a new feature that is being implemented which basically is trying to weed out some trivial changes you do in recipes and that results in rebuilds. But if you are kind of making a real change say into libc we do not yet have a mechanism to detect ABI change. So we might have fixed a bug really not change any API from glibc ideally you don't need to rebuild it if you're not doing static linking. But we cannot detect that so we have to be conservative. Right so there are tools and we talked about that here as well where you can do like ABI compliance check and if nothing changes you don't have to change your hash. But these are technologies that are a little complex right now so what happens is if you are patching it will go and rebuild all the dependencies. Thinking that the patch you change might have a transit dependency that will kind of you know reflect on to other packages. So that's one reason why it will result in rebuilds. That is a problem. Yeah yeah yeah yeah yeah yeah so yeah so there is a tool called BIFsig. Yes so what it will do is if you use BitBake BIFsig it's going to tell you why he is building it compared to what's the difference why it is thinking that it has to redo that task. So that task will give you actually down to a variable. That variable is causing it to think that it should rebuild it. So that way you can debug it right and I think we do use shared state cache quite a bit on auto builders and so I think certainly we do a lot of testing you know on the auto builder as well where we generate a state cache exactly like you and then we consume it from different builders. Yeah so there's a tool I think it's documented yeah it's called BitBake-DIFsig, D-I-F-F-S-I-G. You can target a recipe you can target a task within the recipe right yeah yeah maybe I think that's certainly possible I mean there are possibly there are issues I don't deny those but I think there is a lot of testing we do on a state. Yeah yeah yeah certainly I think you know you could also go to the mailing list and start a discussion provide the feedback hey you know this is what's happening and we can take it there certainly open for all kind of issues I think we take them yeah yeah yeah yeah certainly I think you know for example you know one of the reason is if you don't use uninative right we have had that kind of problems in the past so we have provided a uninative which is basically a uniform environment right so very important use it you use it for consistency to use a state across say your builder is running a different operating system right say it's running Debian and your host is a Bantu right so using that helps quite a bit for it to not confuse the native packages for example if you are using pocky then it is it is already enabled yeah right so so you already have it enabled so so yeah it could be something you know a bug or something you know well yeah that's good I don't have to convince you then so I was being polite but but yeah you know on serious note you can just reach out on on mailing list and then I will certainly help you out I think there is a nice wiki somewhere in the yokto wiki that explains how to debug the hash mismatch but I think the easiest way if you have two hashes that are like usually says you have these two hashes that mismatch in stamps directory you can find the the signature data this it's like compressed files and then use the tool like the bit bake dash dump seek or diff seek and if you have these two files you can see what's the difference and then you can find find variables that are different between your two builds it's usually like date or or some past name but I mean the setup you use is the one we use on the auto builder I mean we have a shared state and we have like 10 different machines that build I mean keep building all the time so I mean there is nothing wrong of this on the setup side at least that that you know one last question maybe yeah this isn't quite a question directly so much well it's a question but it's a follow on to the signature stuff because I've done the same thing many times because there's three or four of us in the company that understand Yachto and there's 800 developers and so when something happens in the you know that that corrupts or not yet that corrupts their environment so they're seeing three hour build time suddenly it's worth several days of my time to go dig it out and figure it out and a huge chunk of the time I see you know there are recipes that take a long time to build and those are the ones that I tend to see the issue on where I can see okay this is building and it shouldn't be but oftentimes quite frequently in fact the issue is not that recipe and its source or something like that but a dependency and if you look at the bit big bit big diff sigs output you know it basically just tells you oh hey the hash for this dependency changed and so you have to go into that hash file and the corresponding one in both cases and do that diff and then another layer up and then another layer up continuously unwrapping the onion until you finally get to the top where something actually changed or there's a variable somewhere that shouldn't actually be included or should be in the what is it hash base whitelist so my question is has anybody worked on creating any semblance of a recursive version of the bit big diff sigs tool or thought about it so the search order is that will search locally if it doesn't find it it will go if you have mirrors it'll go to the mirrors no it will calculate a hash and if you yes so yeah so if you have built something right and that is on your estate mirror that will have a signature and now you're trying to build it it's going to calculate the dependency signature and then it goes on the hunt for signature match right so if you have built this signature before it'll go and fetch it which means right no there is no nearest there is either match or no match yeah there is match or no match right so because see if one thing changed it could change whole things right so so okay so I think it could be that first time you are there and it's not creating a hash locally right because there is no local downloaded equivalent estate um that could be a corner case we might have to look at it that it's not able to then give you uh a hash that it has calculated to compare against something because it needs two versions to compare right yeah right right so there has to be a policy for it for the access so yeah yeah so so I think that is something probably an item that you could bring up on mailing list or maybe as a we might have some clarifications in there and then it could be a feature we could implement if it's missing it could be tied to the build history I mean we could record in the build history what were the last things that we build and the last hashes so then when you build the next one you know at least what is the last state that you were in so maybe that could be that the build history will keep a history of what has been built so we could also record I mean the hashes that were used to make that build so the next time we build I mean we actually have the previous hashes so we don't have any local estate right and you build it and it doesn't find a match and he hasn't made a change and it doesn't match when it should match and now he can't debug it either right yeah but yeah so there has to be a search policy where you can define preferences and stuff so that's actually a whole different game yeah so it's something that I think yeah so so let me yeah I think I think it definitely could be something we could enhance right it could be something that you are doing that's causing this behavior yeah I think I mean enough people I mean I guess I mean these also were interested I've now I mean now that you've told the story yeah I'm sure you really made we believe yeah that's an interesting situation so so so when I when I when I debug these and I debug them a lot generally what happens is I'll have a build I'll basically start with no at local estate cash and remove the temp and do a build and then basically when it gets to the very absolute first thing that it tries to build I basically take that and generate the signatures and try looking through the signatures because if you if you I think if you do say just one it'll tell you all the things that's using to calculate the signature and if you look through those oftentimes you can see oh I've got a path in here that's a local path or something of that nature and that's what's causing it and so I need to go and whitelist that that's usually my first step is basically clear out the workstays do a build and see the very first thing kill the build and generate the signatures for that and just just look at the look through the signatures that it's using to calculate the hash and usually often you know you'll find oh there's a straight time date or yeah basically basically what happens is is it's a dependency tree right and the the one hash at the very beginning cascades through the whole system so starting at the very beginning the very first thing that starts building that it fails yeah yeah basically start at the very beginning and just just generate the signatures look through the signatures and you'll often find there's a date tag or something something of that nature that that is triggering the whole thing yeah you can also tell bit big to just do the set scene tasks it makes you look really smart in front of your coworkers well you want it to run the set scene tasks so it does all the estate it can and then dry run after that and you'll see everything that it would have built that wasn't an estate that way you don't actually do the build on their laptop but you run as much set scene and that way you can figure out where you can at least pairs it down a lot right I figure what the option is but there is a manual okay so we any any last questions or are we done one more okay okay is somebody using reproducible builds and what's your experience how much reproducible packages do you are you getting I'm not using them but I'm writing test cases for them I think the plan they're very close to passing so I think the plan there is to write test cases that will run on the auto builder to make sure that core image minimal and core image seto are reproducible and Richard really wants to get that in for 3.0 right now it's me and Ross has been helping to well it's really important for hash equivalence and I'm not sure what the other use case oh I know people have other use cases just because they want binary reproducible builds you will have issues right now with the infrared in phrase there but we have to patch packages right now in our recipes you know there are packages which use date and then time and stuff like that so I can't tell you like you know a number what percent it is but right now I think you can't build an image where you don't have one package that is not I mean that is you'll have at least one that will fail so yeah so but I think it's it's progressing I think once the testing goes in you know what what Josh is doing I think that's that's actually pretty good there after I think you know we can basically enable it on world builds and you know we can get a lot more information on what all is failing basically right so yeah so we are working on it um we want okay good so it's always like that we don't have any questions and then we can't stop anymore so thanks everyone again I mean we really like I mean unfortunately I mean it's not a lot of time but we are I mean most of these guys I mean this conference all the time so you can find us at the york to booth somewhere anywhere so you can always come and ask questions and you can obviously always use a mailing list so thank you for coming today and yeah thanks for your feedback about the project thanks