Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*CVS\s+2\.4\.1\-XFS\s+module\s+support\s+broken\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*CVS\s+2\.4\.1\-XFS\s+module\s+support\s+broken\?\s*$/: 16 ]

Total 16 documents matching your query.

1. CVS 2.4.1-XFS module support broken? (score: 1): Author: "J. Maynard Gelinas" <gelinas@xxxxxxxxxxx>; Date: Fri, 2 Feb 2001 15:43:12 -0500 (EST); Hello folks, I CVS'd down the source to your XFS 2.4.1 kernel last night and built a kernel and tools under RH-6.2 for a RAID that I'm setting up to export home directories. The system isn't producti; /archives/xfs/2001-02/msg00039.html (8,718 bytes)
2. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>; Date: Sat, 03 Feb 2001 09:29:35 +1100; I need the output from grep printk /proc/ksyms strings -a /lib/modules/2.4.1-XFS/kernel/fs/autofs/autofs.o | grep printk grep printk 2.4.1-XFS/include/linux/modversions.h point that last command at t; /archives/xfs/2001-02/msg00043.html (8,470 bytes)
3. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: "J. Maynard Gelinas" <gelinas@xxxxxxxxxxx>; Date: Fri, 2 Feb 2001 20:07:11 -0500 (EST); OK, will do: Last login: Fri Feb 2 17:03:57 2001 from ctpjaguar.mit.edu [root@ctpraid1 /root]# grep printk /proc/ksyms c011446c printk_R__ver_printk [root@ctpraid1 /root]# strings -a /lib/modules/2.4; /archives/xfs/2001-02/msg00044.html (9,558 bytes)
4. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>; Date: Sat, 03 Feb 2001 13:01:49 +1100; You have been bitten by the broken kernel makefiles. This is not an XFS problem, it is a generic kernel bug. http://www.tux.org/lkml/#s8-8; /archives/xfs/2001-02/msg00045.html (8,208 bytes)
5. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Sat, 03 Feb 2001 00:21:09 -0600; Hm, this may be part of a different build process, RPM kernel packaging and such... Is this from the top-level Makefile (above SCRIPTS, SOURCES, SPECS, etc)? You should be able to go into cmd/xfsprog; /archives/xfs/2001-02/msg00046.html (8,385 bytes)
6. RE: CVS 2.4.1-XFS module support broken? (score: 1): Author: "Cioccarelli, Adam" <Adam.Cioccarelli@xxxxxxxxxx>; Date: Sat, 3 Feb 2001 15:57:00 +0100; I had exactly the same problem with modules, then I started again using make mrproper first (which I forgot to do the first time) and everything worked fine... --Original Message-- From: Keith Owens; /archives/xfs/2001-02/msg00047.html (8,890 bytes)
7. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: Tom Duffy <tduffy@xxxxxxxxxxxx>; Date: Sat, 3 Feb 2001 11:40:10 -0800 (PST); this can be fixed by setting the environment variable WORKAREA to your top level directory. (under SOURCES) -tduffy; /archives/xfs/2001-02/msg00048.html (8,210 bytes)
8. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: "J. Maynard Gelinas" <gelinas@xxxxxxxxxxx>; Date: Wed, 7 Feb 2001 16:41:09 -0500 (EST); I followed these instructions and got a successful kernel build. Thanks for the tip! --M; /archives/xfs/2001-02/msg00089.html (8,434 bytes)
9. CVS 2.4.1-XFS module support broken? (score: 1): Author: xxxx>; Date: Fri, 2 Feb 2001 15:43:12 -0500 (EST); Hello folks, I CVS'd down the source to your XFS 2.4.1 kernel last night and built a kernel and tools under RH-6.2 for a RAID that I'm setting up to export home directories. The system isn't producti; /archives/xfs/2001-02/msg00498.html (8,718 bytes)
10. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: xxxxx; Date: Sat, 03 Feb 2001 09:29:35 +1100; I need the output from grep printk /proc/ksyms strings -a /lib/modules/2.4.1-XFS/kernel/fs/autofs/autofs.o | grep printk grep printk 2.4.1-XFS/include/linux/modversions.h point that last command at t; /archives/xfs/2001-02/msg00502.html (8,470 bytes)
11. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: xxxx>; Date: Fri, 2 Feb 2001 20:07:11 -0500 (EST); OK, will do: Last login: Fri Feb 2 17:03:57 2001 from ctpjaguar.mit.edu [root@ctpraid1 /root]# grep printk /proc/ksyms c011446c printk_R__ver_printk [root@ctpraid1 /root]# strings -a /lib/modules/2.4; /archives/xfs/2001-02/msg00503.html (9,558 bytes)
12. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: xxxx>; Date: Sat, 03 Feb 2001 13:01:49 +1100; You have been bitten by the broken kernel makefiles. This is not an XFS problem, it is a generic kernel bug. http://www.tux.org/lkml/#s8-8; /archives/xfs/2001-02/msg00504.html (8,208 bytes)
13. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: xxxx>; Date: Sat, 03 Feb 2001 00:21:09 -0600; Hm, this may be part of a different build process, RPM kernel packaging and such... Is this from the top-level Makefile (above SCRIPTS, SOURCES, SPECS, etc)? You should be able to go into cmd/xfsprog; /archives/xfs/2001-02/msg00505.html (8,385 bytes)
14. RE: CVS 2.4.1-XFS module support broken? (score: 1): Author: xxxx>; Date: Sat, 3 Feb 2001 15:57:00 +0100; I had exactly the same problem with modules, then I started again using make mrproper first (which I forgot to do the first time) and everything worked fine... --Original Message-- From: Keith Owens; /archives/xfs/2001-02/msg00506.html (8,890 bytes)
15. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: xxxx>; Date: Sat, 3 Feb 2001 11:40:10 -0800 (PST); this can be fixed by setting the environment variable WORKAREA to your top level directory. (under SOURCES) -tduffy; /archives/xfs/2001-02/msg00507.html (8,210 bytes)
16. Re: CVS 2.4.1-XFS module support broken? (score: 1): Author: xxxx>; Date: Wed, 7 Feb 2001 16:41:09 -0500 (EST); I followed these instructions and got a successful kernel build. Thanks for the tip! --M; /archives/xfs/2001-02/msg00548.html (8,434 bytes)

Current List: 1 - 16
Page: [1]