[02:46] <fwec> Hi all.  It seems we are again seeing javascript based flood spam.  If you are experiencing this, please do not click the links in the messages as they will cause you to repeat the spam. More information is available at http://peoplesprimary.com.  Thanks!
[02:46] <fwec> Hi all.  It seems we are again seeing javascript based flood spam.  If you are experiencing this, please do not click the links in the messages as they will cause you to repeat the spam. More information is available at http://peoplesprimary.com.  Thanks!
[03:01] <sbufw> sloth and jenk show is LIVE Theme: Hating on Haiti (877-419-7477) http://klulz.fm/listen.pls
[03:01] <sbufw> sloth and jenk show is LIVE Theme: Hating on Haiti (877-419-7477) http://klulz.fm/listen.pls
[03:01] <sbufw> sloth and jenk show is LIVE Theme: Hating on Haiti (877-419-7477) http://klulz.fm/listen.pls
[03:01] <sbufw> sloth and jenk show is LIVE Theme: Hating on Haiti (877-419-7477) http://klulz.fm/listen.pls
[03:01] <sbufw> sloth and jenk show is LIVE Theme: Hating on Haiti (877-419-7477) http://klulz.fm/listen.pls
[03:01] <sbufw> sloth and jenk show is LIVE Theme: Hating on Haiti (877-419-7477) http://klulz.fm/listen.pls
[04:45] <JFo> thanks kloeri_ :)
[04:46] <kloeri__> you're welcome
[04:56] <mtx_init> since C is a foundation for the kernel, is it also possible use another language like python?
[05:06] <RAOF> mtx_init: In linux kernel code?  No.
[05:07] <mtx_init> why not, given its just libraries no?
[05:08] <RAOF> Because kernel code doesn't get to depend on libraries.
[05:09] <RAOF> It doesn't even link to libc.
[05:13] <mtx_init> but it does have a library it uses? it must
[05:15] <mtx_init> Freebsd uses libc, so linux doesnt?
[05:21] <RAOF> Why would the kernel need a library?  libc *uses* the kernel to do its stuff; the kernel can't use libc :).  It has to be actually implemented somewhere :)
[05:21] <RAOF> Code *written* for linux can use libc or whatever libraries it wants.  The kernel can't, because the kernel is the thing which is providing the underlying bit-twiddling that makes the libraries work.
[05:36] <mtx_init> so lets say you want to use a basic c function like read, if the kernel doesnt use a library where does it get read from?  I mean when you compule a kernel it goes through a linker doesnt it?
[05:43] <johanbr> it doesn't get read from anywhere, the kernel can only rely on functions internal to itself
[05:47] <mtx_init> yeah but the kernel is just a image like everybody else and needed to be built and compiles with libraries. The functions still came from a library at one time or another. 
[05:47] <RAOF> No.  No libraries.
[05:47] <RAOF> Compiled, but not linked.
[05:47] <RAOF> (Well, not to anything outside itself).
[05:48] <mtx_init> why does the freebsd kernel need to be linked then and not the linux?
[05:49] <RAOF> All the “standard C functions” you can think of are implemented *on top of* functions provided by the kernel.  The kernel can't use read(), because the kernel is providing the functionality that read() uses to work :)
[05:50] <RAOF> Maybe the freebsd developers are more confident in their ability to segregate the code that can't link to anything from the code that can?
[05:50] <mtx_init> so how does a system call use read()
[05:51] <RAOF> You mean, a call from within the kernel?  *It doesn't*.
[05:52] <RAOF> There's a whole bunch of stuff you can't do from within kernel (linux) code.  Use the FPU, for example.
[05:53] <mtx_init> so usermode can only do that?
[05:53] <RAOF> Right.
[05:57] <mtx_init> so the kernel knows what read is but cant use it?, how the heck is the kernel pulls if the hdd then?
[05:57] <mtx_init> pulled*
[21:38] <DanaG> hmm, are the mainline kernel builds supposed to have staging drivers disabled?
[21:38] <DanaG> I need two specific drivers: r8192se, and samsung-laptop.