Re: [Haifux] slides for monday's 'kernel, modules, drivers' lecture
On Mon, Jan 19, 2004 at 03:34:36PM +0200, guy keren wrote: > in redhat 7.3's 2.4.18-17.7.x kernel, 'cryptography support'/'crypto > devices' - can't make it allow me to choose 'y'. either 'm' (module) or > 'n'(no). Yikes, that's ancient :-) With your permissino, I'll check on 2.4.24. Let's see: [EMAIL PROTECTED]:~/kernel/linux-2.4$ egrep 'CONFIG_CRYPTO=|CONFIG_USB_AUDIO=' .config CONFIG_USB_AUDIO=y CONFIG_CRYPTO=y > or in USb, 'usb audio support'. maybe there is a way to tell it > to let me compile it as a module - i don't see how. CONFIG_CRYPTO can be either built in or no in 2.4.24, so let's leave that for a second. I have no idea what RH did in their kernel and am too lazy to check right now. As for CONFIG_USB_AUDIO, here's the relevant bit, from drivers/usb/Config.in: dep_tristate ' USB Audio support' CONFIG_USB_AUDIO $CONFIG_USB $CONFIG_SOUND I am guessing (but it's a pretty safe guess) that you have either CONFIG_USB or CONFIG_SOUND as a module? if you do, the configuration system, which knows that USB_AUDIO depends on those two, will not let you choose it as a builtin. > *shrug* we,, let them be doomed ;) [EMAIL PROTECTED]:~/tmp$ uname -a Linux alhambra 2.6.1-life #2 SMP Sat Jan 17 19:01:29 IST 2004 i686 GNU/Linux [EMAIL PROTECTED]:~/tmp$ No comment necessary, me'thinks ;-) Cheers, Muli -- Muli Ben-Yehuda http://www.mulix.org | http://mulix.livejournal.com/ "the nucleus of linux oscillates my world" - [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: [Haifux] slides for monday's 'kernel, modules, drivers' lecture
On Mon, 19 Jan 2004, Muli Ben-Yehuda wrote: > On Mon, Jan 19, 2004 at 02:37:28PM +0200, guy keren wrote: > > > > - the capitalization of Kernel, Driver and Hardware is a bit > > > jarring. Same thing for all other slides. > > > > i want the terms discussed in the lecture to Stand Out, in the > > least-intrusive possible manner. > > Then make them bold, or italic, or even _like this_. Capitalizing > inappropriate Words Makes it Look silly. > > > if i get more ocmplaints about this, i'll > > un-capitalize them next time. > > You can count my complaint as two, if you wish ;-) ok, ok. next time. > > > slide 2 > > > > > > - the kernel can be compiled entirely monolithic (no modules) > > > > ok, but this is not what people normally do (and there are features which, > > as far as i know, can only be compiled as modules). > > In the core kernel? few if any. I would consider any such a feature a > bug. Pointers? in redhat 7.3's 2.4.18-17.7.x kernel, 'cryptography support'/'crypto devices' - can't make it allow me to choose 'y'. either 'm' (module) or 'n'(no). or in USb, 'usb audio support'. maybe there is a way to tell it to let me compile it as a module - i don't see how. > > i don't want to get > > into that - this is not a lecture for people in the embedded systems area, > > after all :) > > Compiling a monolithic kernel is the easiest thing to do when you > compile on one machine and install on another - but it's your talk and > your call. and it's beyond the scope. > > > - explain why we have major and minors? > > > > hmmm... good idea. i did write what they stand for - just not why they > > exist. however, this explanation matters more for kernel programmers, and > > for users, so i'm not sure if it fits into this lecture. won't it be > > better to leave this for your 'device drivers' lecture? :) > > Possibly. Your call. or yours :0 > > > - mention that for the user, the distrinction between character and > > > block devices is irrelevant? it's only the driver that cares > > > (different kernel APIs) > > > > ok. thought this is not entirely correct. it reflects on the nature of > > data tranasfer to/from the device. > > And the user cares because? > > > after all, passing data in blocks is > > normally faster then passing it in serial (ofcourse, passing in blocks ot > > a floppy is much much slower then passing serially to a firewire > > device...). hmmm.. ok, i'll mention this, after all. > > For the user, /dev/kmem and /dev/sda are accessed exactly the same > (cat, dd, tail, echo, whatever). It's only for the programmer that the > distinction matters. as i said, just expected throughput... > > > slide 11 > > > > > > - 2.6 disables module unloading (by default?) > > > > i'm focusing on eisting kernels and existing distributions. > > Some distros already have 2.6 in their testing branches. Fedora > "testing" already comes with a 2.6 kernel, AFAICR. *shrug* we,, let them be doomed ;) -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
Re: [Haifux] slides for monday's 'kernel, modules, drivers' lecture
On Mon, Jan 19, 2004 at 02:37:28PM +0200, guy keren wrote: > > - the capitalization of Kernel, Driver and Hardware is a bit > > jarring. Same thing for all other slides. > > i want the terms discussed in the lecture to Stand Out, in the > least-intrusive possible manner. Then make them bold, or italic, or even _like this_. Capitalizing inappropriate Words Makes it Look silly. > if i get more ocmplaints about this, i'll > un-capitalize them next time. You can count my complaint as two, if you wish ;-) > > slide 2 > > > > - the kernel can be compiled entirely monolithic (no modules) > > ok, but this is not what people normally do (and there are features which, > as far as i know, can only be compiled as modules). In the core kernel? few if any. I would consider any such a feature a bug. Pointers? > i don't want to get > into that - this is not a lecture for people in the embedded systems area, > after all :) Compiling a monolithic kernel is the easiest thing to do when you compile on one machine and install on another - but it's your talk and your call. > > - explain why we have major and minors? > > hmmm... good idea. i did write what they stand for - just not why they > exist. however, this explanation matters more for kernel programmers, and > for users, so i'm not sure if it fits into this lecture. won't it be > better to leave this for your 'device drivers' lecture? :) Possibly. Your call. > > - mention that for the user, the distrinction between character and > > block devices is irrelevant? it's only the driver that cares > > (different kernel APIs) > > ok. thought this is not entirely correct. it reflects on the nature of > data tranasfer to/from the device. And the user cares because? > after all, passing data in blocks is > normally faster then passing it in serial (ofcourse, passing in blocks ot > a floppy is much much slower then passing serially to a firewire > device...). hmmm.. ok, i'll mention this, after all. For the user, /dev/kmem and /dev/sda are accessed exactly the same (cat, dd, tail, echo, whatever). It's only for the programmer that the distinction matters. > > slide 11 > > > > - 2.6 disables module unloading (by default?) > > i'm focusing on eisting kernels and existing distributions. Some distros already have 2.6 in their testing branches. Fedora "testing" already comes with a 2.6 kernel, AFAICR. Cheers, Muli -- Muli Ben-Yehuda http://www.mulix.org | http://mulix.livejournal.com/ "the nucleus of linux oscillates my world" - [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: [Haifux] slides for monday's 'kernel, modules, drivers' lecture
On Sat, 17 Jan 2004, Muli Ben-Yehuda wrote: > On Sat, Jan 17, 2004 at 09:10:46PM +0200, guy keren wrote: > > > > the slides are temporarily available at: > > > > http://users.actcom.co.il/~choo/kernel-modules-drivers/ > > slide 1 > > - the capitalization of Kernel, Driver and Hardware is a bit > jarring. Same thing for all other slides. i want the terms discussed in the lecture to Stand Out, in the least-intrusive possible manner. if i get more ocmplaints about this, i'll un-capitalize them next time. > slide 2 > > - the kernel can be compiled entirely monolithic (no modules) ok, but this is not what people normally do (and there are features which, as far as i know, can only be compiled as modules). i don't want to get into that - this is not a lecture for people in the embedded systems area, after all :) > slide 8 > > - mention what 'c' and 'b' stand for i explain that in a later slide, so i add 'will be explained later'. > - explain why we have major and minors? hmmm... good idea. i did write what they stand for - just not why they exist. however, this explanation matters more for kernel programmers, and for users, so i'm not sure if it fits into this lecture. won't it be better to leave this for your 'device drivers' lecture? :) > slide 10 > > - mention that for the user, the distrinction between character and > block devices is irrelevant? it's only the driver that cares > (different kernel APIs) ok. thought this is not entirely correct. it reflects on the nature of data tranasfer to/from the device. after all, passing data in blocks is normally faster then passing it in serial (ofcourse, passing in blocks ot a floppy is much much slower then passing serially to a firewire device...). hmmm.. ok, i'll mention this, after all. > slide 11 > > - 2.6 disables module unloading (by default?) i'm focusing on eisting kernels and existing distributions. but ok, i added a reference to 'the next generation kernel'. > slide 13 > > - mention /lib/modules/`uname -r`/build? i'll mention this in the next lecture, when i talk about compiling the kernel and ocmpiling out-of-kernel modules. > slide 16 > > -mention that module options can also be passed on the > insmod/modprobe command line? ok. > - mention how to find which modules options a driver supports? > (modinfo, source) ok. added a slide about 'modinfo'. -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
Re: [Haifux] slides for monday's 'kernel, modules, drivers' lecture
On Sat, Jan 17, 2004 at 09:10:46PM +0200, guy keren wrote: > > the slides are temporarily available at: > > http://users.actcom.co.il/~choo/kernel-modules-drivers/ slide 1 - the capitalization of Kernel, Driver and Hardware is a bit jarring. Same thing for all other slides. slide 2 - the kernel can be compiled entirely monolithic (no modules) slide 8 - mention what 'c' and 'b' stand for - explain why we have major and minors? slide 10 - mention that for the user, the distrinction between character and block devices is irrelevant? it's only the driver that cares (different kernel APIs) slide 11 - 2.6 disables module unloading (by default?) slide 13 - mention /lib/modules/`uname -r`/build? slide 16 - mention that module options can also be passed on the insmod/modprobe command line? - mention how to find which modules options a driver supports? (modinfo, source) Overall, excellent talk! see you on Monday. Cheers, Mul i -- Muli Ben-Yehuda http://www.mulix.org | http://mulix.livejournal.com/ "the nucleus of linux oscillates my world" - [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: [Haifux] slides for monday's 'kernel, modules, drivers' lecture
On Sat, 17 Jan 2004, guy keren wrote: > > hopefully, someone would install it on haifux's web site soon. > (by the way, if it's more convinient that i e-mail the tar.z file to > someone, please let me know, for the next time to come.) > guy, and every other propect lecturer: supplying a URL from which the whole slides show can be downloaded is a great way to transfer them. Thanks to wget! Orna. -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
Re: [Haifux] slides for monday's 'kernel, modules, drivers' lecture
Slides can be also d/led from http://www.haifux.org/lectures/084-sil2/ On Sat, 17 Jan 2004, guy keren wrote: > > the slides are temporarily available at: > > http://users.actcom.co.il/~choo/kernel-modules-drivers/ > > These slides do NOT cover kernel compilation procedures - these will be > covered by a seperate lecture, in 2 weeks from now. > > the current lecture deals with the notions and basic ideas one needs in > order to be prepared for the grand kernel compilation task ;) > > the downloadable tar.gz file is at > > http://users.actcom.co.il/~choo/kernel-modules-drivers.tar.gz > > hopefully, someone would install it on haifux's web site soon. > (by the way, if it's more convinient that i e-mail the tar.z file to > someone, please let me know, for the next time to come.) > > thanks, > -- Orr Dunkelman, [EMAIL PROTECTED] "Any human thing supposed to be complete, must for that reason infallibly be faulty" -- Herman Melville, Moby Dick. Spammers: http://vipe.technion.ac.il/~orrd/spam.html -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
