Re: Removed from eudyptula challenge
Am 2014-09-19 21:05, schrieb Jeshwanth Kumar N K: Hello, Today I was asking some suggestions in IRC for my eudyptula challenge (indirectly, because working for it for 1 month). So I am removed from the challenge now. So, who all doing the challenge please do everything yourself by reading the docs, kernel codes or ask little directly. Because, you will feel really bad after removing from challenge, anyway my mistake, I shouldn't have break the integrity. And my mistake was I thought I am smart in asking questions and nobody will get doubt :). So don't do that :). I'm stuck at a task now for _months_ (but because of no time for it) and really hope the challenge, little, to continue. That's because patience has been key for previous tasks, and I love to not-fear that the challenge may go away. Have patience and take time to enjoy every task! It's insanely awesome of him / the people to run the callenge and it sucks that they, now, need to go after people who don't follow the rules. Nobody is forced to take the challenge. The challenge is for _free_ (!) and you can _really_ get a lot out of it, if you simply follow the rules and respect what you have in front of you, like a normal grown-up. That's what I think when I read about people trying to ask and cheat anytime, not you in particular. Depending on how far you have come, I'm sorry you can't continue. Don't try to trick anybody. _If_ this was a one-time-thing you regret and you honestly and quietly want to continue, maybe, ask one last time, give reasons. Starting over anonymously somehow wouldnt really make you happy, be honest. And little would find out anyways. I know I would hate to be removed, that's motivation enough to stick to my kerneltree and search basic stuff ;) I hope little has fun and finds ways to reduce his own challenge-related workload while being able to keep the challenge alive. thanks, martin ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
The Kernel Newbies Crash Course LKD4 Challenge! Play along at home!
In the spirit of the Eudyptula Challenge, we here at the Crash Course Linux Training Centre and Craft Gin Appreciation Institute introduce the LKD4 Challenge. Everyone can play ... fun for the whole family, ages 6 and up. Seriously, though, if you're looking for something to put your Linux kernel understanding to work with a challenge you probably can't get kicked out of, here's a suggestion. It's sort of explained here: http://www.crashcourse.ca/wiki/index.php/Updates_to_LKD3 although it's been a while since I've added anything to that page so I probably need to do a bit of updating and restructuring, but here's the short version. There are frequent references on this list to the standard books that any kernel newbie should have (along with their common acronyms for brevity): * LKD3: Linux Kernel Development (3rd ed), by Robert Love * LDD3: Linux Device Drivers (3rd ed), by Corbet et al * ELDD: Essential Linux Device Drivers, by Venkateswaran Sad part is that at least the first two of those books are starting to show their age -- I should know about LKD3, I was the technical editor. Yes, you can look inside at the masthead and that's me. Now, there is absolutely *no* schedule for an LKD4 (yet), but it doesn't hurt to look ahead and prepare for it if it happens. It's possible I might tech edit that next edition but, even if not, it doesen't hurt to prepare for it, which is why I started that wiki page; to start keeping track of everything that would need to be updated. If you want to play along, the rules are pretty simple (actually, the rules are non-existent, you just have to want to participate). First, you need a copy of LKD3. And, second, you just need to figure out what needs updating. That's about it. This doesn't require a massive investment of time -- you don't need to tackle entire sections or chapters at once. An update could represent something as simple as a change to a single line or single paragraph, an update to a filename, a revision to a listed snippet of code or what have you. You also don't need to try to deal with the whole book -- just pick the part of the Linux kernel that most interests you and work on that. As for what constitutes reporting an update, it's pretty flexible but it's always best if you try to be complete and provide as much context as possible. As a hypothetical example, say a listed structure in LKD3 has changed since publication -- then that's something that should be reported as an update. But don't stop there. Figure out *why* it changed, perhaps identify the Git commit where it happened, investigate what else might have been affected by the same commit, and so on. Other things to be reported would naturally include: * new features added since publication * entire subsystems deleted since publication * suggestions for topics that should be covered in more detail It's all very open-ended -- just a totally *unofficial* project to update LKD3. Finally, while that's a wiki page, I'm reluctant to make it world-writable given the immediate infestation of spammers, so people are free to just email me, and I can add their stuff and give them credit if they want. It's all in good fun and, in the end, the goal is to improve the content. Questions? rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: console fonts
On Fri, Sep 19, 2014 at 08:12:23PM -0700, Greg KH wrote: the kernel EFI framebuffer driver is odd, and probably can not support your console fonts. I know mine can not, sorry. When the machine first starts loading the kernel it swtiches from the tiny fonts that gummiboot uses to the Sparc 12x22 fonts, then switches back. What framebuffer driver is being used when the kernel first starts loading? I tried disabling the EFI-based Framebuffer thinking it would not switch, but this causes no output at all after gummiboot. My point is, my system *does* show the fonts I want (for a second) so this makes me think it can support this. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: console fonts
On Sat, Sep 20, 2014 at 09:47:10AM -0400, John de la Garza wrote: On Fri, Sep 19, 2014 at 08:12:23PM -0700, Greg KH wrote: the kernel EFI framebuffer driver is odd, and probably can not support your console fonts. I know mine can not, sorry. When the machine first starts loading the kernel it swtiches from the tiny fonts that gummiboot uses to the Sparc 12x22 fonts, then switches back. gummiboot uses the default UEFI terminal mode, it doesn't select any specific font or size, it just uses what UEFI provides it. Same for the UEFI console driver, I don't think there is a way to change the fonts for it. What framebuffer driver is being used when the kernel first starts loading? The default framebuffer. VGA perhaps? You can try to force it to be this one but on an UEFI system, I don't think it will work. I tried disabling the EFI-based Framebuffer thinking it would not switch, but this causes no output at all after gummiboot. My point is, my system *does* show the fonts I want (for a second) so this makes me think it can support this. Good luck, and let us know if you get this working, as my machines would like to see it happen as well, but I don't know if it is possible. greg k-h ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Removed from eudyptula challenge
Hi, I just shared this info with kernelnewbies who taken eudyptula challenge not to ask anything in public :). May be learning for others :). May be I loved too much this challenge, today the phrase You removed from challenge was always flashing in my mind, thats made me really sad. Thanks little for everything (I can't reach him directly), you made my dream come true Sending first patch to linux kernel. Hope I will continue learning and contribute to the community whenever I am capable of :). Thanks On Sat, Sep 20, 2014 at 3:25 PM, Martin Kepplinger mart...@posteo.de wrote: Am 2014-09-19 21:05, schrieb Jeshwanth Kumar N K: Hello, Today I was asking some suggestions in IRC for my eudyptula challenge (indirectly, because working for it for 1 month). So I am removed from the challenge now. So, who all doing the challenge please do everything yourself by reading the docs, kernel codes or ask little directly. Because, you will feel really bad after removing from challenge, anyway my mistake, I shouldn't have break the integrity. And my mistake was I thought I am smart in asking questions and nobody will get doubt :). So don't do that :). I'm stuck at a task now for _months_ (but because of no time for it) and really hope the challenge, little, to continue. That's because patience has been key for previous tasks, and I love to not-fear that the challenge may go away. Have patience and take time to enjoy every task! It's insanely awesome of him / the people to run the callenge and it sucks that they, now, need to go after people who don't follow the rules. Nobody is forced to take the challenge. The challenge is for _free_ (!) and you can _really_ get a lot out of it, if you simply follow the rules and respect what you have in front of you, like a normal grown-up. That's what I think when I read about people trying to ask and cheat anytime, not you in particular. Depending on how far you have come, I'm sorry you can't continue. Don't try to trick anybody. _If_ this was a one-time-thing you regret and you honestly and quietly want to continue, maybe, ask one last time, give reasons. Starting over anonymously somehow wouldnt really make you happy, be honest. And little would find out anyways. I know I would hate to be removed, that's motivation enough to stick to my kerneltree and search basic stuff ;) I hope little has fun and finds ways to reduce his own challenge-related workload while being able to keep the challenge alive. thanks, martin ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies -- Regards Jeshwanth Kumar N K Bangalore, India ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: console fonts
On Sat, Sep 20, 2014 at 07:41:17AM -0700, Greg KH wrote: Good luck, and let us know if you get this working, as my machines would like to see it happen as well, but I don't know if it is possible. It is possible! I just got it working the way I want. I saw that the kernel messages where using the custom font (the larger font). I put a while(1); right before the kernel called init. The system booted and hung at the while(1); and was using the custom fonts. I realized then this was a userspace issue. I ran dpkg-reconfigure console-set and went through the menus and choose the option- 'Do not change the boot/kernel font' now it doesn't switch back and I am able to see the cusom font sun 12x22 I was also about to select VGA from the dpkg-reconfigure menu and get large fonts I'm really happy about this, because now I can do more work without X, not have to strain my eyes, and I understand my system a little better. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: The Kernel Newbies Crash Course LKD4 Challenge! Play along at home!
2014-09-20 14:59 GMT-05:00 Gustavo Silva silvagustavosi...@gmail.com: 2014-09-20 8:24 GMT-05:00 Robert P. J. Day rpj...@crashcourse.ca: In the spirit of the Eudyptula Challenge, we here at the Crash Course Linux Training Centre and Craft Gin Appreciation Institute introduce the LKD4 Challenge. Everyone can play ... fun for the whole family, ages 6 and up. Seriously, though, if you're looking for something to put your Linux kernel understanding to work with a challenge you probably can't get kicked out of, here's a suggestion. It's sort of explained here: http://www.crashcourse.ca/wiki/index.php/Updates_to_LKD3 although it's been a while since I've added anything to that page so I probably need to do a bit of updating and restructuring, but here's the short version. There are frequent references on this list to the standard books that any kernel newbie should have (along with their common acronyms for brevity): * LKD3: Linux Kernel Development (3rd ed), by Robert Love * LDD3: Linux Device Drivers (3rd ed), by Corbet et al * ELDD: Essential Linux Device Drivers, by Venkateswaran Sad part is that at least the first two of those books are starting to show their age -- I should know about LKD3, I was the technical editor. Yes, you can look inside at the masthead and that's me. Now, there is absolutely *no* schedule for an LKD4 (yet), but it doesn't hurt to look ahead and prepare for it if it happens. It's possible I might tech edit that next edition but, even if not, it doesen't hurt to prepare for it, which is why I started that wiki page; to start keeping track of everything that would need to be updated. If you want to play along, the rules are pretty simple (actually, the rules are non-existent, you just have to want to participate). First, you need a copy of LKD3. And, second, you just need to figure out what needs updating. That's about it. This doesn't require a massive investment of time -- you don't need to tackle entire sections or chapters at once. An update could represent something as simple as a change to a single line or single paragraph, an update to a filename, a revision to a listed snippet of code or what have you. You also don't need to try to deal with the whole book -- just pick the part of the Linux kernel that most interests you and work on that. As for what constitutes reporting an update, it's pretty flexible but it's always best if you try to be complete and provide as much context as possible. As a hypothetical example, say a listed structure in LKD3 has changed since publication -- then that's something that should be reported as an update. But don't stop there. Figure out *why* it changed, perhaps identify the Git commit where it happened, investigate what else might have been affected by the same commit, and so on. Other things to be reported would naturally include: * new features added since publication * entire subsystems deleted since publication * suggestions for topics that should be covered in more detail It's all very open-ended -- just a totally *unofficial* project to update LKD3. Finally, while that's a wiki page, I'm reluctant to make it world-writable given the immediate infestation of spammers, so people are free to just email me, and I can add their stuff and give them credit if they want. It's all in good fun and, in the end, the goal is to improve the content. Questions? rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies Hi Robert, So at this moment the idea is just update the topics as they are currently covered in LDD3 without going any further? I mean, the suggestions for topics to be covered in more detail will be considered by you as a wish list or can we also try to start writing down those details? Best regards -- Gustavo Silva Embedded Software Engineer silvagust...@users.sourceforge.net silvagu...@users.sourceforge.net Sorry, typo correction: LKD3 Best regards -- Gustavo Silva ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: The Kernel Newbies Crash Course LKD4 Challenge! Play along at home!
2014-09-20 15:12 GMT-05:00 Robert P. J. Day rpj...@crashcourse.ca: On Sat, 20 Sep 2014, Gustavo Silva wrote: Hi Robert, So at this moment the idea is just update the topics as they are currently covered in LDD3 without going any further? LKD3, not LDD3. two very different books. Yep, you are right, it was a typo. I mean, the suggestions for topics to be covered in more detail will be considered by you as a wish list or can we also try to start writing down those details? the challenge is simply to review Linux Kernel Development (3rd ed) by robert love, and identify *anything* that needs to be updated for the (hypothetical) LKD4. there are no hard and fast rules ... you can peruse LKD3 and make note of *anything* that needs to be updated with respect to the current version of the kernel. eventually, there *might* be an LKD4, and if there is, it will make it a much better book if numerous people have already identified (in detail) the parts that need to be updated. so take on the challenge, pick the parts of the book that interest you most, and let me know what needs fixing, and i'll keep track of it all, and when/if LKD4 comes out, it will be a much better book because of everyone's efforts. OK, I got it, thanks for the clarification. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday Best regards -- Gustavo Silva Embedded Software Engineer silvagust...@users.sourceforge.net silvagu...@users.sourceforge.net Twitter: https://twitter.com/embeddedgus ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
