Hey Guys, After Searching the kernel Docs there is very little information on this for new developers. I want to know more about how the kernel code is written to handle TCP/UDP as even with Google and kernel programming books it's not good enough to learn how to write code for this particular subsystem at a high level. Cheers Nick
I don't mean to be rude, but about two days ago you said that you would not mail this mailing list until you completed the eudyptula challenge, please stick to this policy. As per your question, start by reading and completely understanding the TCP/IP Protocol and Linux sockets, write some user space test applications such as a IM client, and keep writing these applications until you are confident that you can understand the kernel code,then you should do what you said three days ago and read the kernel code and not mail the mailing list for a few months, i say this because people are getting saturated at you and your disregard for the community and the people involved in it. Maybe you were just searching the wrong phrases/keywords, but there is an enormous amount of information regarding TCP/IP and the Linux kernel http://unix.stackexchange.com/questions/45160/books-resources-which-explain-... This stack exchange question seems to be related. 2014-08-18 17:25 GMT+01:00 Nick Krause <xerofoify@gmail.com>:
Hey Guys, After Searching the kernel Docs there is very little information on this for new developers. I want to know more about how the kernel code is written to handle TCP/UDP as even with Google and kernel programming books it's not good enough to learn how to write code for this particular subsystem at a high level. Cheers Nick
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Mon, Aug 18, 2014 at 12:51 PM, Afonso Bordado <afonsobordado@gmail.com> wrote:
I don't mean to be rude, but about two days ago you said that you would not mail this mailing list until you completed the eudyptula challenge, please stick to this policy.
As per your question, start by reading and completely understanding the TCP/IP Protocol and Linux sockets, write some user space test applications such as a IM client, and keep writing these applications until you are confident that you can understand the kernel code,then you should do what you said three days ago and read the kernel code and not mail the mailing list for a few months, i say this because people are getting saturated at you and your disregard for the community and the people involved in it.
Maybe you were just searching the wrong phrases/keywords, but there is an enormous amount of information regarding TCP/IP and the Linux kernel
http://unix.stackexchange.com/questions/45160/books-resources-which-explain-...
This stack exchange question seems to be related.
2014-08-18 17:25 GMT+01:00 Nick Krause <xerofoify@gmail.com>:
Hey Guys, After Searching the kernel Docs there is very little information on this for new developers. I want to know more about how the kernel code is written to handle TCP/UDP as even with Google and kernel programming books it's not good enough to learn how to write code for this particular subsystem at a high level. Cheers Nick
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies I was just curious. I will keep to my stated promise then. Nick
On Mon, 18 Aug 2014 12:25:53 -0400, Nick Krause said:
Hey Guys, After Searching the kernel Docs there is very little information on this for new developers. I want to know more about how the kernel code is written to handle TCP/UDP as even with Google and kernel programming books it's not good enough to learn how to write code for this particular subsystem at a high level.
Do we need to stick a "CAUTION: NO USER SERVICEABLE PARTS INSIDE" sticker on there before you get the hint? Let me quote a mail of yours from less than 24 hours ago:
Further more I learn really fast in my areas of interest, after my first year of programming I was already have build my own distro of Linux from Scratch, and after my second year was learning how to program embedded bootloaders and the like. I am not lying this is no joke
If this is the truth, you should be having *zero* difficulty with the Linux network stack. Anyhow, I'm not feeling like digging up any good references for you, because I have zero guarantee it's worth my time. Beagleboads apparently lasted all of 36 hours - why should I dig up references fo something that you probably won't be interested in by the time I finish typing the mail?
On Mon, Aug 18, 2014 at 12:57 PM, <Valdis.Kletnieks@vt.edu> wrote:
On Mon, 18 Aug 2014 12:25:53 -0400, Nick Krause said:
Hey Guys, After Searching the kernel Docs there is very little information on this for new developers. I want to know more about how the kernel code is written to handle TCP/UDP as even with Google and kernel programming books it's not good enough to learn how to write code for this particular subsystem at a high level.
Do we need to stick a "CAUTION: NO USER SERVICEABLE PARTS INSIDE" sticker on there before you get the hint?
Let me quote a mail of yours from less than 24 hours ago:
Further more I learn really fast in my areas of interest, after my first year of programming I was already have build my own distro of Linux from Scratch, and after my second year was learning how to program embedded bootloaders and the like. I am not lying this is no joke
If this is the truth, you should be having *zero* difficulty with the Linux network stack.
Anyhow, I'm not feeling like digging up any good references for you, because I have zero guarantee it's worth my time. Beagleboads apparently lasted all of 36 hours - why should I dig up references fo something that you probably won't be interested in by the time I finish typing the mail? Valdis, I was interested in both at the same time, just asked about Beagle-boards first. I aren't having any difficulty with it , I just wanted to known more about this area as the docs out there are terrible and not worth reading on this part of the networking stack.
On Mon, Aug 18, 2014 at 1:13 PM, Nick Krause <xerofoify@gmail.com> wrote: > On Mon, Aug 18, 2014 at 12:57 PM, <Valdis.Kletnieks@vt.edu> wrote: >> On Mon, 18 Aug 2014 12:25:53 -0400, Nick Krause said: >>> Hey Guys, >>> After Searching the kernel Docs there is very little information on >>> this for new developers. I want to know more about how >>> the kernel code is written to handle TCP/UDP as even with Google and >>> kernel programming books it's not good enough to >>> learn how to write code for this particular subsystem at a high level. >> >> Do we need to stick a "CAUTION: NO USER SERVICEABLE PARTS INSIDE" sticker >> on there before you get the hint? >> >> Let me quote a mail of yours from less than 24 hours ago: >> >>> Further more I learn really fast in my areas of interest, after my first year >>> of programming I was already have build my own distro of Linux from Scratch, >>> and after my second year was learning how to program embedded bootloaders and >>> the like. I am not lying this is no joke >> >> If this is the truth, you should be having *zero* difficulty with >> the Linux network stack. >> >> Anyhow, I'm not feeling like digging up any good references for you, >> because I have zero guarantee it's worth my time. Beagleboads apparently >> lasted all of 36 hours - why should I dig up references fo something that >> you probably won't be interested in by the time I finish typing the mail? > Valdis, > I was interested in both at the same time, just asked about Beagle-boards first. > I aren't having any difficulty with it , I just wanted to known more about this > area as the docs out there are terrible and not worth reading on this part of > the networking stack. Valdis, In addition I generally learn 5 or 6 areas of a topic or program at the same time so I am just asking at different times. Just to make you and the other developers have an easier time I will paste my kernel interests below in a list. Regards Nick 1. Networking 2. Usb, PCI , Networking and CPU Freq Drivers 3. Embedded Boards 4. Kernel Booting with UEFI(curiosity mostly) 5. Btrfs , F2FS ,NFS filesysems 6. VFS 7. Process and Virtual Memory Subsystems 8. Memory Management
On Mon, Aug 18, 2014 at 10:21 AM, Nick Krause <xerofoify@gmail.com> wrote: > On Mon, Aug 18, 2014 at 1:13 PM, Nick Krause <xerofoify@gmail.com> wrote: > > On Mon, Aug 18, 2014 at 12:57 PM, <Valdis.Kletnieks@vt.edu> wrote: > >> On Mon, 18 Aug 2014 12:25:53 -0400, Nick Krause said: > >>> Hey Guys, > >>> After Searching the kernel Docs there is very little information on > >>> this for new developers. I want to know more about how > >>> the kernel code is written to handle TCP/UDP as even with Google and > >>> kernel programming books it's not good enough to > >>> learn how to write code for this particular subsystem at a high level. > >> > >> Do we need to stick a "CAUTION: NO USER SERVICEABLE PARTS INSIDE" > sticker > >> on there before you get the hint? > >> > >> Let me quote a mail of yours from less than 24 hours ago: > >> > >>> Further more I learn really fast in my areas of interest, after my > first year > >>> of programming I was already have build my own distro of Linux from > Scratch, > >>> and after my second year was learning how to program embedded > bootloaders and > >>> the like. I am not lying this is no joke > >> > >> If this is the truth, you should be having *zero* difficulty with > >> the Linux network stack. > >> > >> Anyhow, I'm not feeling like digging up any good references for you, > >> because I have zero guarantee it's worth my time. Beagleboads > apparently > >> lasted all of 36 hours - why should I dig up references fo something > that > >> you probably won't be interested in by the time I finish typing the > mail? > > Valdis, > > I was interested in both at the same time, just asked about > Beagle-boards first. > > I aren't having any difficulty with it , I just wanted to known more > about this > > area as the docs out there are terrible and not worth reading on this > part of > > the networking stack. > Valdis, > In addition I generally learn 5 or 6 areas of a topic or program at > the same time so I > am just asking at different times. Just to make you and the other > developers have > an easier time I will paste my kernel interests below in a list. > Regards Nick > 1. Networking > 2. Usb, PCI , Networking and CPU Freq Drivers > 3. Embedded Boards > 4. Kernel Booting with UEFI(curiosity mostly) > 5. Btrfs , F2FS ,NFS filesysems > 6. VFS > 7. Process and Virtual Memory Subsystems > 8. Memory Management > This is amusing :-). So when you wrote linux from scratch, did you implement it in the following order too ? Thanks - Manish > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >
On Mon, Aug 18, 2014 at 1:26 PM, Manish Katiyar <mkatiyar@gmail.com> wrote: > On Mon, Aug 18, 2014 at 10:21 AM, Nick Krause <xerofoify@gmail.com> wrote: >> >> On Mon, Aug 18, 2014 at 1:13 PM, Nick Krause <xerofoify@gmail.com> wrote: >> > On Mon, Aug 18, 2014 at 12:57 PM, <Valdis.Kletnieks@vt.edu> wrote: >> >> On Mon, 18 Aug 2014 12:25:53 -0400, Nick Krause said: >> >>> Hey Guys, >> >>> After Searching the kernel Docs there is very little information on >> >>> this for new developers. I want to know more about how >> >>> the kernel code is written to handle TCP/UDP as even with Google and >> >>> kernel programming books it's not good enough to >> >>> learn how to write code for this particular subsystem at a high level. >> >> >> >> Do we need to stick a "CAUTION: NO USER SERVICEABLE PARTS INSIDE" >> >> sticker >> >> on there before you get the hint? >> >> >> >> Let me quote a mail of yours from less than 24 hours ago: >> >> >> >>> Further more I learn really fast in my areas of interest, after my >> >>> first year >> >>> of programming I was already have build my own distro of Linux from >> >>> Scratch, >> >>> and after my second year was learning how to program embedded >> >>> bootloaders and >> >>> the like. I am not lying this is no joke >> >> >> >> If this is the truth, you should be having *zero* difficulty with >> >> the Linux network stack. >> >> >> >> Anyhow, I'm not feeling like digging up any good references for you, >> >> because I have zero guarantee it's worth my time. Beagleboads >> >> apparently >> >> lasted all of 36 hours - why should I dig up references fo something >> >> that >> >> you probably won't be interested in by the time I finish typing the >> >> mail? >> > Valdis, >> > I was interested in both at the same time, just asked about >> > Beagle-boards first. >> > I aren't having any difficulty with it , I just wanted to known more >> > about this >> > area as the docs out there are terrible and not worth reading on this >> > part of >> > the networking stack. >> Valdis, >> In addition I generally learn 5 or 6 areas of a topic or program at >> the same time so I >> am just asking at different times. Just to make you and the other >> developers have >> an easier time I will paste my kernel interests below in a list. >> Regards Nick >> 1. Networking >> 2. Usb, PCI , Networking and CPU Freq Drivers >> 3. Embedded Boards >> 4. Kernel Booting with UEFI(curiosity mostly) >> 5. Btrfs , F2FS ,NFS filesysems >> 6. VFS >> 7. Process and Virtual Memory Subsystems >> 8. Memory Management > > > This is amusing :-). So when you wrote linux from scratch, did you implement > it in the following order too ? > > Thanks - > Manish > > >> >> >> _______________________________________________ >> Kernelnewbies mailing list >> Kernelnewbies@kernelnewbies.org >> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > Of course not, just listing it off. Nick
On 08/18/2014 01:13 PM, Nick Krause wrote:
Valdis, I was interested in both at the same time, just asked about Beagle-boards first. I aren't having any difficulty with it , I just wanted to known more about this area as the docs out there are terrible and not worth reading on this part of the networking stack. Nick,
the Linux kernel requires a lot of focus. I have no doubt that you are smart enough to learn things about the Linux kernel, but nobody is smart enough to learn everything at once. Nobody. If you are serious about learning Linux kernel internals, it would be good to focus on one thing at a time. One thing. Learn everything about it, before moving on to the next topic. Kernel hacking is much more about attitude than about aptitude. Focus is the key.
On Mon, Aug 18, 2014 at 10:06 PM, Rik van Riel <riel@surriel.com> wrote:
On 08/18/2014 01:13 PM, Nick Krause wrote:
Valdis, I was interested in both at the same time, just asked about Beagle-boards first. I aren't having any difficulty with it , I just wanted to known more about this area as the docs out there are terrible and not worth reading on this part of the networking stack. Nick,
the Linux kernel requires a lot of focus.
I have no doubt that you are smart enough to learn things about the Linux kernel, but nobody is smart enough to learn everything at once. Nobody.
If you are serious about learning Linux kernel internals, it would be good to focus on one thing at a time.
One thing. Learn everything about it, before moving on to the next topic.
Kernel hacking is much more about attitude than about aptitude. Focus is the key.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies Absolutely, I am trying to learn btrfs and networking for now. Cheers Nick
On Mon, Aug 18, 2014 at 10:55 PM, Nick Krause <xerofoify@gmail.com> wrote:
On Mon, Aug 18, 2014 at 10:06 PM, Rik van Riel <riel@surriel.com> wrote:
On 08/18/2014 01:13 PM, Nick Krause wrote:
Valdis, I was interested in both at the same time, just asked about Beagle-boards first. I aren't having any difficulty with it , I just wanted to known more about this area as the docs out there are terrible and not worth reading on this part of the networking stack. Nick,
the Linux kernel requires a lot of focus.
I have no doubt that you are smart enough to learn things about the Linux kernel, but nobody is smart enough to learn everything at once. Nobody.
If you are serious about learning Linux kernel internals, it would be good to focus on one thing at a time.
One thing. Learn everything about it, before moving on to the next topic.
Kernel hacking is much more about attitude than about aptitude. Focus is the key.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies Absolutely, I am trying to learn btrfs and networking for now. Cheers Nick My issue now is that due to my issues I can't mail the right list for being banned for my questions. If someone wants to talk to the other developers about removing the ban that would be great and very helpful as I can my questions to the right maintainers/developers. Cheers Nick
On Mon, Aug 18, 2014 at 10:59 PM, Nick Krause <xerofoify@gmail.com> wrote:
On Mon, Aug 18, 2014 at 10:55 PM, Nick Krause <xerofoify@gmail.com> wrote:
On Mon, Aug 18, 2014 at 10:06 PM, Rik van Riel <riel@surriel.com> wrote:
On 08/18/2014 01:13 PM, Nick Krause wrote:
Valdis, I was interested in both at the same time, just asked about Beagle-boards first. I aren't having any difficulty with it , I just wanted to known more about this area as the docs out there are terrible and not worth reading on this part of the networking stack. Nick,
the Linux kernel requires a lot of focus.
I have no doubt that you are smart enough to learn things about the Linux kernel, but nobody is smart enough to learn everything at once. Nobody.
If you are serious about learning Linux kernel internals, it would be good to focus on one thing at a time.
One thing. Learn everything about it, before moving on to the next topic.
Kernel hacking is much more about attitude than about aptitude. Focus is the key.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies Absolutely, I am trying to learn btrfs and networking for now. Cheers Nick My issue now is that due to my issues I can't mail the right list for being banned for my questions. If someone wants to talk to the other developers about removing the ban that would be great and very helpful as I can my questions to the right maintainers/developers. Cheers Nick I am working on btrfs for now. :) Thanks for the advice Rik. Cheers Nick
I'm sure Avi is looking forward to your contribution... On Tuesday, 19 August 2014, Nick Krause <xerofoify@gmail.com> wrote:
On Mon, Aug 18, 2014 at 10:59 PM, Nick Krause <xerofoify@gmail.com <javascript:;>> wrote:
On Mon, Aug 18, 2014 at 10:55 PM, Nick Krause <xerofoify@gmail.com <javascript:;>> wrote:
On Mon, Aug 18, 2014 at 10:06 PM, Rik van Riel <riel@surriel.com <javascript:;>> wrote:
On 08/18/2014 01:13 PM, Nick Krause wrote:
Valdis, I was interested in both at the same time, just asked about Beagle-boards first. I aren't having any difficulty with it , I just wanted to known more about this area as the docs out there are terrible and not worth reading on this part of the networking stack. Nick,
the Linux kernel requires a lot of focus.
I have no doubt that you are smart enough to learn things about the Linux kernel, but nobody is smart enough to learn everything at once. Nobody.
If you are serious about learning Linux kernel internals, it would be good to focus on one thing at a time.
One thing. Learn everything about it, before moving on to the next topic.
Kernel hacking is much more about attitude than about aptitude. Focus is the key.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org <javascript:;> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies Absolutely, I am trying to learn btrfs and networking for now. Cheers Nick My issue now is that due to my issues I can't mail the right list for being banned for my questions. If someone wants to talk to the other developers about removing the ban that would be great and very helpful as I can my questions to the right maintainers/developers. Cheers Nick I am working on btrfs for now. :) Thanks for the advice Rik. Cheers Nick
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org <javascript:;> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- -- Teach your kids Science, or somebody else will :/ jason@ball.net vk2vjb@google.com <vk2flnx@google.com> callsign: vk2vjb
On August 18, 2014 10:59:05 PM EDT, Nick Krause <xerofoify@gmail.com> wrote:
On Mon, Aug 18, 2014 at 10:55 PM, Nick Krause <xerofoify@gmail.com> wrote:
On Mon, Aug 18, 2014 at 10:06 PM, Rik van Riel <riel@surriel.com> wrote:
On 08/18/2014 01:13 PM, Nick Krause wrote:
Valdis, I was interested in both at the same time, just asked about Beagle-boards first. I aren't having any difficulty with it , I just wanted to known more about this area as the docs out there are terrible and not worth reading on this part of the networking stack. Nick,
the Linux kernel requires a lot of focus.
I have no doubt that you are smart enough to learn things about the Linux kernel, but nobody is smart enough to learn everything at once. Nobody.
If you are serious about learning Linux kernel internals, it would be good to focus on one thing at a time.
One thing. Learn everything about it, before moving on to the next topic.
Kernel hacking is much more about attitude than about aptitude. Focus is the key.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies Absolutely, I am trying to learn btrfs and networking for now. Cheers Nick My issue now is that due to my issues I can't mail the right list for being banned for my questions. If someone wants to talk to the other developers about removing the ban that would be great and very helpful as I can my questions to the right maintainers/developers. Cheers Nick
I checked my watch, then my sundial, and finally my calendar. All said check back after beard has grown 6 additional inches. I have no idea if you will ever be un-banned, but it certainly not going to happen in 2014. I doubt seriously it will happen in 2015. You do realize that most of the kernel devs do it both for a living and out of sheer love of the work. Your participation the last few months impacted both in a negative way. I've never heard of anyone being banned before, so you are novel. None of us how long the blackball will stay in place, maybe forever. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
On Tue, Aug 19, 2014 at 8:13 AM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
On August 18, 2014 10:59:05 PM EDT, Nick Krause <xerofoify@gmail.com> wrote:
On Mon, Aug 18, 2014 at 10:55 PM, Nick Krause <xerofoify@gmail.com> wrote:
On Mon, Aug 18, 2014 at 10:06 PM, Rik van Riel <riel@surriel.com> wrote:
On 08/18/2014 01:13 PM, Nick Krause wrote:
Valdis, I was interested in both at the same time, just asked about Beagle-boards first. I aren't having any difficulty with it , I just wanted to known more about this area as the docs out there are terrible and not worth reading on this part of the networking stack. Nick,
the Linux kernel requires a lot of focus.
I have no doubt that you are smart enough to learn things about the Linux kernel, but nobody is smart enough to learn everything at once. Nobody.
If you are serious about learning Linux kernel internals, it would be good to focus on one thing at a time.
One thing. Learn everything about it, before moving on to the next topic.
Kernel hacking is much more about attitude than about aptitude. Focus is the key.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies Absolutely, I am trying to learn btrfs and networking for now. Cheers Nick My issue now is that due to my issues I can't mail the right list for being banned for my questions. If someone wants to talk to the other developers about removing the ban that would be great and very helpful as I can my questions to the right maintainers/developers. Cheers Nick
I checked my watch, then my sundial, and finally my calendar. All said check back after beard has grown 6 additional inches.
I have no idea if you will ever be un-banned, but it certainly not going to happen in 2014. I doubt seriously it will happen in 2015.
You do realize that most of the kernel devs do it both for a living and out of sheer love of the work. Your participation the last few months impacted both in a negative way. I've never heard of anyone being banned before, so you are novel. None of us how long the blackball will stay in place, maybe forever.
Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
That's understandable and I hope to get back on, I did screw up and yes I understand your points. Cheers Nick
No one will ever help you with the generic questions. _That is not how the mailing list work_. You really have to dig _on your own_ for that. Don't ask useless questions, show us something concrete. Better invest your time in Stevens TCP/IP illustrated volumes....(1 and 2nd one) and Unix network programming. On Monday, August 18, 2014, Nick Krause <xerofoify@gmail.com> wrote:
Hey Guys, After Searching the kernel Docs there is very little information on this for new developers. I want to know more about how the kernel code is written to handle TCP/UDP as even with Google and kernel programming books it's not good enough to learn how to write code for this particular subsystem at a high level. Cheers Nick
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org <javascript:;> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- Regards, Denis
On Mon, Aug 18, 2014 at 1:31 PM, Denis Kirjanov <kirjanov@gmail.com> wrote:
No one will ever help you with the generic questions. _That is not how the mailing list work_. You really have to dig _on your own_ for that. Don't ask useless questions, show us something concrete.
Better invest your time in Stevens TCP/IP illustrated volumes....(1 and 2nd one) and Unix network programming.
On Monday, August 18, 2014, Nick Krause <xerofoify@gmail.com> wrote:
Hey Guys, After Searching the kernel Docs there is very little information on this for new developers. I want to know more about how the kernel code is written to handle TCP/UDP as even with Google and kernel programming books it's not good enough to learn how to write code for this particular subsystem at a high level. Cheers Nick
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- Regards, Denis That's fine, Denis I have no problems with that at all just stating my areas of interest and if someone wants to give me some kernel work for a newbie in that area I would be glad to help :). Thanks for your support guys, I didn't want to have to push the Linux from Scratch build but I have no choice, sorry. Nick
On Mon, Aug 18, 2014 at 1:33 PM, Nick Krause <xerofoify@gmail.com> wrote:
On Mon, Aug 18, 2014 at 1:31 PM, Denis Kirjanov <kirjanov@gmail.com> wrote:
No one will ever help you with the generic questions. _That is not how the mailing list work_. You really have to dig _on your own_ for that. Don't ask useless questions, show us something concrete.
Better invest your time in Stevens TCP/IP illustrated volumes....(1 and 2nd one) and Unix network programming.
On Monday, August 18, 2014, Nick Krause <xerofoify@gmail.com> wrote:
Hey Guys, After Searching the kernel Docs there is very little information on this for new developers. I want to know more about how the kernel code is written to handle TCP/UDP as even with Google and kernel programming books it's not good enough to learn how to write code for this particular subsystem at a high level. Cheers Nick
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- Regards, Denis That's fine, Denis I have no problems with that at all just stating my areas of interest and if someone wants to give me some kernel work for a newbie in that area I would be glad to help :). Thanks for your support guys, I didn't want to have to push the Linux from Scratch build but I have no choice, sorry. Nick The reason I got into my mess here was not listening to testing patches and over thinking the code. Cheers Nick
I'm looking for an efficient way to determine the type of an fd (file, socket...) given its number, from a kernel module. The closest thing I found by looking at the kernel sources is sockfd_lookup(), which works but is limited to telling me if the fd is a socket or not. Is there something else I can look at? Thank you in advance, Loris
On August 18, 2014 8:46:16 PM EDT, Loris Degioanni <loris@draios.com> wrote:
I'm looking for an efficient way to determine the type of an fd (file, socket...) given its number, from a kernel module. The closest thing I found by looking at the kernel sources is sockfd_lookup(), which works but is limited to telling me if the fd is a socket or not.
Is there something else I can look at?
Thank you in advance.
Loris, Apparently you replied to a different email then changed the subject. Email clients that thread conversations based on "in-reply-to" will lump your supposedly new thread in with the one you replied to. That guarantees a reduced audience of readers, especially considering the email you replied to. You should repost by composing a brand new email. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
participants (9)
-
Afonso Bordado -
Denis Kirjanov -
Greg Freemyer -
Jason Ball -
Loris Degioanni -
Manish Katiyar -
Nick Krause -
Rik van Riel -
Valdis.Kletnieks＠vt.edu