Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On Wed, May 30, 2007 at 08:52:29PM +0530, Tej Parkash wrote: > On 5/30/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote: > >On Wed, May 30, 2007 at 08:07:53PM +0530, Tej Parkash wrote: > >> On 5/30/07, Tej Parkash <[EMAIL PROTECTED]> wrote: > >> >> > > > >> >> > > while building module i was getting following warning and it > >> >terminate > >> >> > > module building stage > >> >> > The below are only warnings and your build should succeed. > >> >> > > >> >> > It is obviously i386 - is it a clean allmodconfig or any changes? > >> >> > Is it latest -linus or some older version of the codebase? > >> >> Did an allmodconfig build of i386 - I see (almost) all warnings here. > >> >> So I will take a look based on this. > >> > >> yaa i got the warning but as i said building stage is also getting > >> terminated, without any error. > >> > >> >The MODPOST stage took a while but it proceeded with no hick-ups. > >> > MDOPSOT deals with ~2000 modules in my case and that consumes a bit > >> > of memory. Maybe you are hitting the limit with respect to available > >RAM > >> > / SWAP? > >> > > >> >Sam > >> > > >> > > >> I don't think so that RAM or SWAP space is a constraint, is it related > >> to kernel build option or some change in arch. config files > >> I am not aware of the required patches for the same. > >Can you please post relevant parts of a build with make V=2 > >That is the last couple of commands before the build suddenly stops. > >Also to error-code reported by make must be included. > > > >Ohh, and exact command-line + config you use. > > > >Sam > > > > make -C /lib/modules/2.6.21.3/build/ SUBDIR=/home/tej/Offload modules > make[1]: Entering directory `/home/tej/linux_src/linux-2.6.21.3' > CHK include/linux/version.h > CHK include/linux/utsrelease.h > Building modules, stage 2. > MODPOST 1889 modules > WARNING: vmlinux - Section mismatch: reference to > .init.text:start_kernel from .text between 'is386' (at offset > 0xc0101171) and 'check_x87' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .text between 'rest_init' (at offset 0xc0101458) and 'try_name' > WARNING: vmlinux - Section mismatch: reference to > .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset > 0xc010adfb) and 'cpu_init' > WARNING: vmlinux - Section mismatch: reference to > .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset > 0xc010ae11) and 'cpu_init' > WARNING: vmlinux - Section mismatch: reference to > .init.text:sysenter_setup from .text between 'identify_cpu' (at offset > 0xc010b46b) and 'display_cacheinfo' > WARNING: vmlinux - Section mismatch: reference to > .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset > 0xc010b475) and 'display_cacheinfo' > WARNING: vmlinux - Section mismatch: reference to > .init.text:trap_init_f00f_bug from .text between 'init_intel' (at > offset 0xc010d576) and 'cpuid4_cache_lookup' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .text between 'iret_exc' (at offset 0xc02f2c2e) and '_etext' > WARNING: vmlinux - Section mismatch: reference to > .init.data:initkmem_list3 from .text between 'set_up_list3s' (at > offset 0xc0173aff) and 's_start' > WARNING: vmlinux - Section mismatch: reference to > .init.text:eisa_root_register from .text between > 'virtual_eisa_root_init' (at offset 0xc026fecf) and > 'cpufreq_unregister_driver' > WARNING: vmlinux - Section mismatch: reference to .init.text: from > .text between 'iret_exc' (at offset 0xc02f32c8) and '_etext' > make[1]: Leaving directory `/home/tej/linux_src/linux-2.6.21.3' [It should have been make V=1 - bot is does not matter]. The build succeeds. This is expected when building modules - there are no "I'm done" messages when doing "make modules". So only thing left is a few more or less harmless warnings that you can ignore for ypur usage. Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On 5/30/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote: On Wed, May 30, 2007 at 08:07:53PM +0530, Tej Parkash wrote: > On 5/30/07, Tej Parkash <[EMAIL PROTECTED]> wrote: > >> > > > >> > > while building module i was getting following warning and it > >terminate > >> > > module building stage > >> > The below are only warnings and your build should succeed. > >> > > >> > It is obviously i386 - is it a clean allmodconfig or any changes? > >> > Is it latest -linus or some older version of the codebase? > >> Did an allmodconfig build of i386 - I see (almost) all warnings here. > >> So I will take a look based on this. > > yaa i got the warning but as i said building stage is also getting > terminated, without any error. > > >The MODPOST stage took a while but it proceeded with no hick-ups. > > MDOPSOT deals with ~2000 modules in my case and that consumes a bit > > of memory. Maybe you are hitting the limit with respect to available RAM > > / SWAP? > > > >Sam > > > > > I don't think so that RAM or SWAP space is a constraint, is it related > to kernel build option or some change in arch. config files > I am not aware of the required patches for the same. Can you please post relevant parts of a build with make V=2 That is the last couple of commands before the build suddenly stops. Also to error-code reported by make must be included. Ohh, and exact command-line + config you use. Sam make -C /lib/modules/2.6.21.3/build/ SUBDIR=/home/tej/Offload modules make[1]: Entering directory `/home/tej/linux_src/linux-2.6.21.3' CHK include/linux/version.h CHK include/linux/utsrelease.h Building modules, stage 2. MODPOST 1889 modules WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc0101171) and 'check_x87' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc0101458) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010adfb) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010ae11) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset 0xc010b46b) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset 0xc010b475) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:trap_init_f00f_bug from .text between 'init_intel' (at offset 0xc010d576) and 'cpuid4_cache_lookup' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f2c2e) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0xc0173aff) and 's_start' WARNING: vmlinux - Section mismatch: reference to .init.text:eisa_root_register from .text between 'virtual_eisa_root_init' (at offset 0xc026fecf) and 'cpufreq_unregister_driver' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f32c8) and '_etext' make[1]: Leaving directory `/home/tej/linux_src/linux-2.6.21.3' the actaul kernel where i am running this make is in /home/tej/linux_src/linux-2.6.21.3. thanks tej - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On Wed, May 30, 2007 at 08:07:53PM +0530, Tej Parkash wrote: > On 5/30/07, Tej Parkash <[EMAIL PROTECTED]> wrote: > >> > > > >> > > while building module i was getting following warning and it > >terminate > >> > > module building stage > >> > The below are only warnings and your build should succeed. > >> > > >> > It is obviously i386 - is it a clean allmodconfig or any changes? > >> > Is it latest -linus or some older version of the codebase? > >> Did an allmodconfig build of i386 - I see (almost) all warnings here. > >> So I will take a look based on this. > > yaa i got the warning but as i said building stage is also getting > terminated, without any error. > > >The MODPOST stage took a while but it proceeded with no hick-ups. > > MDOPSOT deals with ~2000 modules in my case and that consumes a bit > > of memory. Maybe you are hitting the limit with respect to available RAM > > / SWAP? > > > >Sam > > > > > I don't think so that RAM or SWAP space is a constraint, is it related > to kernel build option or some change in arch. config files > I am not aware of the required patches for the same. Can you please post relevant parts of a build with make V=2 That is the last couple of commands before the build suddenly stops. Also to error-code reported by make must be included. Ohh, and exact command-line + config you use. Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On 5/30/07, Tej Parkash <[EMAIL PROTECTED]> wrote: > > > > > > while building module i was getting following warning and it terminate > > > module building stage > > The below are only warnings and your build should succeed. > > > > It is obviously i386 - is it a clean allmodconfig or any changes? > > Is it latest -linus or some older version of the codebase? > Did an allmodconfig build of i386 - I see (almost) all warnings here. > So I will take a look based on this. yaa i got the warning but as i said building stage is also getting terminated, without any error. The MODPOST stage took a while but it proceeded with no hick-ups. MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available RAM / SWAP? Sam I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same. thanks TEJ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On 5/30/07, Tej Parkash [EMAIL PROTECTED] wrote: while building module i was getting following warning and it terminate module building stage The below are only warnings and your build should succeed. It is obviously i386 - is it a clean allmodconfig or any changes? Is it latest -linus or some older version of the codebase? Did an allmodconfig build of i386 - I see (almost) all warnings here. So I will take a look based on this. yaa i got the warning but as i said building stage is also getting terminated, without any error. The MODPOST stage took a while but it proceeded with no hick-ups. MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available RAM / SWAP? Sam I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same. thanks TEJ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On Wed, May 30, 2007 at 08:07:53PM +0530, Tej Parkash wrote: On 5/30/07, Tej Parkash [EMAIL PROTECTED] wrote: while building module i was getting following warning and it terminate module building stage The below are only warnings and your build should succeed. It is obviously i386 - is it a clean allmodconfig or any changes? Is it latest -linus or some older version of the codebase? Did an allmodconfig build of i386 - I see (almost) all warnings here. So I will take a look based on this. yaa i got the warning but as i said building stage is also getting terminated, without any error. The MODPOST stage took a while but it proceeded with no hick-ups. MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available RAM / SWAP? Sam I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same. Can you please post relevant parts of a build with make V=2 That is the last couple of commands before the build suddenly stops. Also to error-code reported by make must be included. Ohh, and exact command-line + config you use. Sam - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On 5/30/07, Sam Ravnborg [EMAIL PROTECTED] wrote: On Wed, May 30, 2007 at 08:07:53PM +0530, Tej Parkash wrote: On 5/30/07, Tej Parkash [EMAIL PROTECTED] wrote: while building module i was getting following warning and it terminate module building stage The below are only warnings and your build should succeed. It is obviously i386 - is it a clean allmodconfig or any changes? Is it latest -linus or some older version of the codebase? Did an allmodconfig build of i386 - I see (almost) all warnings here. So I will take a look based on this. yaa i got the warning but as i said building stage is also getting terminated, without any error. The MODPOST stage took a while but it proceeded with no hick-ups. MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available RAM / SWAP? Sam I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same. Can you please post relevant parts of a build with make V=2 That is the last couple of commands before the build suddenly stops. Also to error-code reported by make must be included. Ohh, and exact command-line + config you use. Sam make -C /lib/modules/2.6.21.3/build/ SUBDIR=/home/tej/Offload modules make[1]: Entering directory `/home/tej/linux_src/linux-2.6.21.3' CHK include/linux/version.h CHK include/linux/utsrelease.h Building modules, stage 2. MODPOST 1889 modules WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc0101171) and 'check_x87' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc0101458) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010adfb) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010ae11) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset 0xc010b46b) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset 0xc010b475) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:trap_init_f00f_bug from .text between 'init_intel' (at offset 0xc010d576) and 'cpuid4_cache_lookup' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f2c2e) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0xc0173aff) and 's_start' WARNING: vmlinux - Section mismatch: reference to .init.text:eisa_root_register from .text between 'virtual_eisa_root_init' (at offset 0xc026fecf) and 'cpufreq_unregister_driver' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f32c8) and '_etext' make[1]: Leaving directory `/home/tej/linux_src/linux-2.6.21.3' the actaul kernel where i am running this make is in /home/tej/linux_src/linux-2.6.21.3. thanks tej - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On Wed, May 30, 2007 at 08:52:29PM +0530, Tej Parkash wrote: On 5/30/07, Sam Ravnborg [EMAIL PROTECTED] wrote: On Wed, May 30, 2007 at 08:07:53PM +0530, Tej Parkash wrote: On 5/30/07, Tej Parkash [EMAIL PROTECTED] wrote: while building module i was getting following warning and it terminate module building stage The below are only warnings and your build should succeed. It is obviously i386 - is it a clean allmodconfig or any changes? Is it latest -linus or some older version of the codebase? Did an allmodconfig build of i386 - I see (almost) all warnings here. So I will take a look based on this. yaa i got the warning but as i said building stage is also getting terminated, without any error. The MODPOST stage took a while but it proceeded with no hick-ups. MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available RAM / SWAP? Sam I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same. Can you please post relevant parts of a build with make V=2 That is the last couple of commands before the build suddenly stops. Also to error-code reported by make must be included. Ohh, and exact command-line + config you use. Sam make -C /lib/modules/2.6.21.3/build/ SUBDIR=/home/tej/Offload modules make[1]: Entering directory `/home/tej/linux_src/linux-2.6.21.3' CHK include/linux/version.h CHK include/linux/utsrelease.h Building modules, stage 2. MODPOST 1889 modules WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc0101171) and 'check_x87' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc0101458) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010adfb) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010ae11) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset 0xc010b46b) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset 0xc010b475) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:trap_init_f00f_bug from .text between 'init_intel' (at offset 0xc010d576) and 'cpuid4_cache_lookup' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f2c2e) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0xc0173aff) and 's_start' WARNING: vmlinux - Section mismatch: reference to .init.text:eisa_root_register from .text between 'virtual_eisa_root_init' (at offset 0xc026fecf) and 'cpufreq_unregister_driver' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f32c8) and '_etext' make[1]: Leaving directory `/home/tej/linux_src/linux-2.6.21.3' [It should have been make V=1 - bot is does not matter]. The build succeeds. This is expected when building modules - there are no I'm done messages when doing make modules. So only thing left is a few more or less harmless warnings that you can ignore for ypur usage. Sam - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Followup to: <[EMAIL PROTECTED]> By author:Matti Aarnio <[EMAIL PROTECTED]> In newsgroup: linux.dev.kernel > > On Thu, Sep 21, 2000 at 07:38:15AM -0500, Joshua Jore wrote: > > Huh? *is* supposed to be equivalent to according to RFC822. > > *NOT* for Procmail's REGULAR EXPRESSIONS. > > They are, after all, just regular UNIX REs without special > knowledge about e.g. EMAIL. > Actually, procmail does canonicalize the header somewhat. This is one of the things that it really should have canonicalized. -hpa -- <[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
On Thu, Sep 21, 2000 at 11:27:01PM +0100, Alan Cox wrote: > >From: Alan Cox <[EMAIL PROTECTED]> > > > >Having slowly switched every list I have to run or help run to > >mailman I can recommend the pain of the switch over the pain of > >running majordomo > > > > I suggested this but Matti immediately told me that mailman has > > several RFC compliancy "issues" which I am sure he can elaborate on. > > I'd like to hear more. I think mailman is worth fixing even if so - the fact > folks who change email address dont have to send you hate mail being one > major reason 8) A year or two ago I had a peek after I got reports that it didn't work together with ZMailer -- turned out that some baseline PYTHON library for SMTP does something stupid in its protocol line construction.. The system experiencing problems was running ZMailer with ultra-strict RFC 821 (plus amendaments) mode. Ergo, the MAILMAN might be ok, but underneath it there may be buggy language library.. (may STILL be, that is.) Another point, DaveM, was that MAILMAN is written in Python, and neither of us "speaks" that language... > BTW tell Matti that zmailer is positively vicious - when I put my mail server > back online on the cable modem after 3 days offline vger streamed mail at it > at a steady 512Kbits/second and nearly killed it Oh dear me. It is feeding those one message at a time with least possible resource usage... Perhaps it can be made less "vicious" with e.g. sprinkling sleep(1) calls all over the code, but I would rather not do such a gross thing.. /Matti Aarnio - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Alan Cox said: > Having slowly switched every list I have to run or help run to mailman I can > recommend the pain of the switch over the pain of running majordomo There is a Majordomo 2 in development. I'm using it for all of my lists now. The upgrade from Majordomo 1 wasn't terribly painful. Note that it's not really a new version, but rather a total rewrite. MIME, archives, digests, and everything else you would expect to "just work" does. Of course, the catch is that there hasn't been an official, stable release yet. See http://www.hpc.uh.edu/majordomo/#mj2 for more info. Steve -- [EMAIL PROTECTED] | Linux Users of Central Illinois (618)398-7320 | Meetings the 4th Tuesday of every month Steven Pritchard | http://www.luci.org/ for more info - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Date:Thu, 21 Sep 2000 22:58:16 +0100 (BST) From: Alan Cox <[EMAIL PROTECTED]> Having slowly switched every list I have to run or help run to mailman I can recommend the pain of the switch over the pain of running majordomo I suggested this but Matti immediately told me that mailman has several RFC compliancy "issues" which I am sure he can elaborate on. Later, David S. Miller [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
> According to DaveM: No. > (Sometimes he holds possibly bad opinnions as ferociously as Linus, >but on the other hand, that Majordomo 1.x digester breaks structured >MIME messages BADLY. It should be trivial to fix, but I don't hack >Md, I hack ZMailer -- and also sometimes the kernel.) Having slowly switched every list I have to run or help run to mailman I can recommend the pain of the switch over the pain of running majordomo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
On Thu, Sep 21, 2000 at 07:38:15AM -0500, Joshua Jore wrote: > Huh? *is* supposed to be equivalent to according to RFC822. *NOT* for Procmail's REGULAR EXPRESSIONS. They are, after all, just regular UNIX REs without special knowledge about e.g. EMAIL. /Matti Aarnio - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Huh? *is* supposed to be equivalent to according to RFC822. >From the spec: SPACE = ; ( 40, 32.) HTAB= ; ( 11, 9.) LWSP-char = SPACE / HTAB ; semantics = SPACE linear-white-space = 1*([CRLF] LWSP-char) ; semantics = SPACE ; CRLF => folding Josh (not that I need linux-kernel-digest, pine separates linux-kernel to a folder just fine) On Wed, 20 Sep 2000, Matti Aarnio wrote: > I think DaveM also supplied an answer: "procmail" > > Select by header: > > X-Mailing-List: [EMAIL PROTECTED] > > Do note that TAB character, for some reason it really is not space.. > Store into separate folder from your normal inbox. > > > On Wed, Sep 20, 2000 at 02:26:33PM -0400, Dmitry Pogosyan wrote: > > Date: Wed, 20 Sep 2000 14:26:33 -0400 > > From: Dmitry Pogosyan <[EMAIL PROTECTED]> > > X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-12 i686) > > X-Accept-Language: en > > To: [EMAIL PROTECTED] > > Subject: Re: linux-kernel-digest ? > > Precedence: bulk > > X-Mailing-List: [EMAIL PROTECTED] > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Huh? TAB *is* supposed to be equivalent to SPACE according to RFC822. From the spec: SPACE = ASCII SP, space; ( 40, 32.) HTAB= ASCII HT, horizontal-tab ; ( 11, 9.) LWSP-char = SPACE / HTAB ; semantics = SPACE linear-white-space = 1*([CRLF] LWSP-char) ; semantics = SPACE ; CRLF = folding Josh (not that I need linux-kernel-digest, pine separates linux-kernel to a folder just fine) On Wed, 20 Sep 2000, Matti Aarnio wrote: I think DaveM also supplied an answer: "procmail" Select by header: X-Mailing-List: TAB [EMAIL PROTECTED] Do note that TAB character, for some reason it really is not space.. Store into separate folder from your normal inbox. On Wed, Sep 20, 2000 at 02:26:33PM -0400, Dmitry Pogosyan wrote: Date: Wed, 20 Sep 2000 14:26:33 -0400 From: Dmitry Pogosyan [EMAIL PROTECTED] X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-12 i686) X-Accept-Language: en To: [EMAIL PROTECTED] Subject: Re: linux-kernel-digest ? Precedence: bulk X-Mailing-List: [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
According to DaveM: No. (Sometimes he holds possibly bad opinnions as ferociously as Linus, but on the other hand, that Majordomo 1.x digester breaks structured MIME messages BADLY. It should be trivial to fix, but I don't hack Md, I hack ZMailer -- and also sometimes the kernel.) Having slowly switched every list I have to run or help run to mailman I can recommend the pain of the switch over the pain of running majordomo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Alan Cox said: Having slowly switched every list I have to run or help run to mailman I can recommend the pain of the switch over the pain of running majordomo There is a Majordomo 2 in development. I'm using it for all of my lists now. The upgrade from Majordomo 1 wasn't terribly painful. Note that it's not really a new version, but rather a total rewrite. MIME, archives, digests, and everything else you would expect to "just work" does. Of course, the catch is that there hasn't been an official, stable release yet. See http://www.hpc.uh.edu/majordomo/#mj2 for more info. Steve -- [EMAIL PROTECTED] | Linux Users of Central Illinois (618)398-7320 | Meetings the 4th Tuesday of every month Steven Pritchard | http://www.luci.org/ for more info - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
On Thu, Sep 21, 2000 at 11:27:01PM +0100, Alan Cox wrote: From: Alan Cox [EMAIL PROTECTED] Having slowly switched every list I have to run or help run to mailman I can recommend the pain of the switch over the pain of running majordomo I suggested this but Matti immediately told me that mailman has several RFC compliancy "issues" which I am sure he can elaborate on. I'd like to hear more. I think mailman is worth fixing even if so - the fact folks who change email address dont have to send you hate mail being one major reason 8) A year or two ago I had a peek after I got reports that it didn't work together with ZMailer -- turned out that some baseline PYTHON library for SMTP does something stupid in its protocol line construction.. The system experiencing problems was running ZMailer with ultra-strict RFC 821 (plus amendaments) mode. Ergo, the MAILMAN might be ok, but underneath it there may be buggy language library.. (may STILL be, that is.) Another point, DaveM, was that MAILMAN is written in Python, and neither of us "speaks" that language... BTW tell Matti that zmailer is positively vicious - when I put my mail server back online on the cable modem after 3 days offline vger streamed mail at it at a steady 512Kbits/second and nearly killed it Oh dear me. It is feeding those one message at a time with least possible resource usage... Perhaps it can be made less "vicious" with e.g. sprinkling sleep(1) calls all over the code, but I would rather not do such a gross thing.. /Matti Aarnio - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Date:Thu, 21 Sep 2000 22:58:16 +0100 (BST) From: Alan Cox [EMAIL PROTECTED] Having slowly switched every list I have to run or help run to mailman I can recommend the pain of the switch over the pain of running majordomo I suggested this but Matti immediately told me that mailman has several RFC compliancy "issues" which I am sure he can elaborate on. Later, David S. Miller [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Matti Aarnio wrote: > I think DaveM also supplied an answer: "procmail" > > Select by header: > > X-Mailing-List: [EMAIL PROTECTED] > > Do note that TAB character, for some reason it really is not space.. > Store into separate folder from your normal inbox. Ah!!! Thats why my there never matched. I just always do: X-Mailing-List:.*[EMAIL PROTECTED] but now I know why. Thanks. (This also makes it easy to put all mailing lists from one site in one mailbox. :-) Roger. -- ** [EMAIL PROTECTED] ** http://www.BitWizard.nl/ ** +31-15-2137555 ** *-- BitWizard writes Linux device drivers for any device you may have! --* * Common sense is the collection of* ** prejudices acquired by age eighteen. -- Albert Einstein - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
I think DaveM also supplied an answer: "procmail" Select by header: X-Mailing-List: [EMAIL PROTECTED] Do note that TAB character, for some reason it really is not space.. Store into separate folder from your normal inbox. On Wed, Sep 20, 2000 at 02:26:33PM -0400, Dmitry Pogosyan wrote: > Date: Wed, 20 Sep 2000 14:26:33 -0400 > From: Dmitry Pogosyan <[EMAIL PROTECTED]> > X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-12 i686) > X-Accept-Language: en > To: [EMAIL PROTECTED] > Subject: Re: linux-kernel-digest ? > Precedence: bulk > X-Mailing-List: [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Matti Aarnio wrote: > On Wed, Sep 20, 2000 at 04:38:45PM +0100, Robert Greimel wrote: > > Hi, > > I am just wondering if linux-kernel-digest is going to come back. > > Greetings > > According to DaveM: No. > (Sometimes he holds possibly bad opinnions as ferociously as Linus, >but on the other hand, that Majordomo 1.x digester breaks structured >MIME messages BADLY. It should be trivial to fix, but I don't hack >Md, I hack ZMailer -- and also sometimes the kernel.) > This is very unfortunate, since linux-kernel-digest was the great way to keep many interested people informed about state of Linux development Without it, > 200 mails daily in linux-kernel is fairly prohibitive if you are not an active developer. Dmitri Pogosyan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
On Wed, Sep 20, 2000 at 04:38:45PM +0100, Robert Greimel wrote: > Hi, > I am just wondering if linux-kernel-digest is going to come back. > Greetings According to DaveM: No. (Sometimes he holds possibly bad opinnions as ferociously as Linus, but on the other hand, that Majordomo 1.x digester breaks structured MIME messages BADLY. It should be trivial to fix, but I don't hack Md, I hack ZMailer -- and also sometimes the kernel.) > Robert /Matti Aarnio - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
On Wed, Sep 20, 2000 at 04:38:45PM +0100, Robert Greimel wrote: Hi, I am just wondering if linux-kernel-digest is going to come back. Greetings According to DaveM: No. (Sometimes he holds possibly bad opinnions as ferociously as Linus, but on the other hand, that Majordomo 1.x digester breaks structured MIME messages BADLY. It should be trivial to fix, but I don't hack Md, I hack ZMailer -- and also sometimes the kernel.) Robert /Matti Aarnio - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Matti Aarnio wrote: On Wed, Sep 20, 2000 at 04:38:45PM +0100, Robert Greimel wrote: Hi, I am just wondering if linux-kernel-digest is going to come back. Greetings According to DaveM: No. (Sometimes he holds possibly bad opinnions as ferociously as Linus, but on the other hand, that Majordomo 1.x digester breaks structured MIME messages BADLY. It should be trivial to fix, but I don't hack Md, I hack ZMailer -- and also sometimes the kernel.) This is very unfortunate, since linux-kernel-digest was the great way to keep many interested people informed about state of Linux development Without it, 200 mails daily in linux-kernel is fairly prohibitive if you are not an active developer. Dmitri Pogosyan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: linux-kernel-digest ?
Matti Aarnio wrote: I think DaveM also supplied an answer: "procmail" Select by header: X-Mailing-List: TAB [EMAIL PROTECTED] Do note that TAB character, for some reason it really is not space.. Store into separate folder from your normal inbox. Ah!!! Thats why my space there never matched. I just always do: X-Mailing-List:.*[EMAIL PROTECTED] but now I know why. Thanks. (This also makes it easy to put all mailing lists from one site in one mailbox. :-) Roger. -- ** [EMAIL PROTECTED] ** http://www.BitWizard.nl/ ** +31-15-2137555 ** *-- BitWizard writes Linux device drivers for any device you may have! --* * Common sense is the collection of* ** prejudices acquired by age eighteen. -- Albert Einstein - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
