Thread: RE: [Fault-injection-developer] Couple of issues downloading and building the FITH source code
Status: Alpha
Brought to you by:
rustyl
From: Lynch, R. <rus...@in...> - 2002-10-18 05:27:52
|
Yea, I see the same problem when I attempt to build from a RH 8.0 system. The newer version of autoconf/automake seems to have turned off some legacy options. -rusty -----Original Message----- From: Rob Rhoads [mailto:err...@li...] Sent: Thursday, October 17, 2002 4:39 PM To: fau...@li... Cc: ina...@in... Subject: Re: [Fault-injection-developer] Couple of issues downloading and building the FITH source code Ran into a problem... Since we are targeting any Linux kernel developer & not just developers using CGLE, I tried to build FITH on my CoosBay (Intel P4 DP SMP box) running RedHat 8.0. After making sure that the appropriate shared libraries/packages were installed (i.e. libdissasm, libxml2, etc.), I attempted to get the ./configure script built by running Makefile.cvs file. Below was error output. NOTE: When we get around to packaging up a source tarball, we need to include ./configure script already built, so they can just run it and then do a Make all. [errhoads@fuente FITH]$ make -f Makefile.cvs aclocal autoconf automake --add-missing configure.in: installing `./install-sh' configure.in: installing `./mkinstalldirs' configure.in: installing `./missing' man/Makefile.am:1: installing `man/texinfo.tex' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dm.o' overrides `fith_dm.o$(EXEEXT)' : change your target to read `fith_dm.o$(EXEEXT)' src/dm/Makefile.am: installing `./depcomp' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_fakeirq.o' overrides `fith_fakeirq.o$(EXEEXT)' : change your target to read `fith_fakeirq.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_clean' overrides `fith_clean$(EXEEXT)' : change your target to read `fith_clean$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_insmod' overrides `fith_insmod$(EXEEXT)' : change your target to read `fith_insmod$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `mkfithdev' overrides `mkfithdev$(EXEEXT)' : change your target to read `mkfithdev$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_aslt.o' overrides `fith_aslt.o$(EXEEXT)' : change your target to read `fith_aslt.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dbp.o' overrides `fith_dbp.o$(EXEEXT)' : change your target to read `fith_dbp.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dr.o' overrides `fith_dr.o$(EXEEXT)' : change your target to read `fith_dr.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_ovr.o' overrides `fith_ovr.o$(EXEEXT)' : change your target to read `fith_ovr.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_pf.o' overrides `fith_pf.o$(EXEEXT)' : change your target to read `fith_pf.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dm.o' overrides `fith_dm.o$(EXEEXT)' : change your target to read `fith_dm.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_fakeirq.o' overrides `fith_fakeirq.o$(EXEEXT)' : change your target to read `fith_fakeirq.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_clean' overrides `fith_clean$(EXEEXT)' : change your target to read `fith_clean$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_insmod' overrides `fith_insmod$(EXEEXT)' : change your target to read `fith_insmod$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `mkfithdev' overrides `mkfithdev$(EXEEXT)' : change your target to read `mkfithdev$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_aslt.o' overrides `fith_aslt.o$(EXEEXT)' : change your target to read `fith_aslt.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dbp.o' overrides `fith_dbp.o$(EXEEXT)' : change your target to read `fith_dbp.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dr.o' overrides `fith_dr.o$(EXEEXT)' : change your target to read `fith_dr.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_ovr.o' overrides `fith_ovr.o$(EXEEXT)' : change your target to read `fith_ovr.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_pf.o' overrides `fith_pf.o$(EXEEXT)' : change your target to read `fith_pf.o$(EXEEXT)' make: *** [all] Error 1 On Thu, 2002-10-17 at 15:17, Rob Rhoads wrote: > OK, got the source, and I'm now going through the build steps and > reading the documentation. In short, its way too TLT specific for a > general announcement on the LKML. > > I haven't attempted to build it yet, but this is what I see so far that > needs to be fixed before the project is announced (in any form) to the > LKML: > > 1. Remove all mention & dependencies on TLT, carrierlinux, etc. from > everything. The README file is full of TLT & carrierlinux 'isms. If this > is going to be posted on LKML, the instructions and code had better work > on a stock kernel by applying relevant kernel patches. > > If you rely on the TLT or CGLE kernel no one on the LKML, outside of > OSDL developers, will take a second look at it. > > The instructions need to be written so anyone can take a stock kernel > apply the relevant patches and make it work. For example, dprobes is > required, but the instruction don't clearly state that you need to apply > the patch to the stock kernel sources. > > 2. You need to break-out the required kernel patches from the user-space > components. Separate source tarballs & separate instructions, might be > one way to do it. Right now it's confusing from reading the README what > exactly you need to do in order to get going. At the very least you need > to build a new kernel with the right patches applied, and then make the > user-space components. > > 3. A lot of the info that's in the README should be in the INSTALL file. > The INSTALL file has good info, but is pretty much generic to running > ./configure. > > 4. To get the best exposure on the LKML, it would be better to also > provide instructions on how to make it work on the 2.5 kernel. I would > think that would be just a matter of getting the patches working on the > 2.5 kernel. This could be any area where we ask for community help in > making it work on 2.5. This shouldn't stop us from announcing, but after > listening to Greg K-H yesterday and my past experience this is the > conclusion I come to. > > More comments to follow...stay tuned... > > -RobR > > > On Thu, 2002-10-17 at 13:25, Rob Rhoads wrote: > > I'm attempting to download the source to FITH for building, but it > > appears that it is only available via checking out directly from CVS. It > > would be nice if you post a tarball of the source code to both the > > project web page and under the file section on the project page. > > > > Also make me a member of the project (my SF account errhoads), so I > > don't have to monkey around with trying to get anonymous :pserver to > > work around the our stupid corporate firewall. > > > > Thanks. > > > > -- > > Rob Rhoads mailto:err...@li... > > Telecom Software Platforms office: 503-677-5498 > > Intel Communications Group > > > > <disclaimer value="pointless"> > > This email message solely contains my own personal views, > > and not necessarily those of my employer. > > </disclaimer> > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by: viaVerio will pay you up to > > $1,000 for every account that you consolidate with us. > > http://ad.doubleclick.net/clk;4749864;7604308;v? > > http://www.viaverio.com/consolidator/osdn.cfm > > _______________________________________________ > > Fault-injection-developer mailing list > > Fau...@li... > > https://lists.sourceforge.net/lists/listinfo/fault-injection-developer > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: viaVerio will pay you up to > $1,000 for every account that you consolidate with us. > http://ad.doubleclick.net/clk;4749864;7604308;v? > http://www.viaverio.com/consolidator/osdn.cfm > _______________________________________________ > Fault-injection-developer mailing list > Fau...@li... > https://lists.sourceforge.net/lists/listinfo/fault-injection-developer ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ Fault-injection-developer mailing list Fau...@li... https://lists.sourceforge.net/lists/listinfo/fault-injection-developer |
From: Zhuang, L. <lou...@in...> - 2002-10-22 02:29:14
|
Thanks Rob for his push! :) We've made FITH conformable to Red hat 8.0. Now, it is conformable to ISO C99, aclocal 1.6, autoconf 2.53, automake 1.6. But, kernel with Red hat 8.0 is not suitable for compiling and running FITH because DProbes and some symbol exports are needed. The CGL precompiled kernel is most suitable for that. :) http://builds.developer.osdl.org/index.php?ver=v1_0&type=stable Louis Zhuang, SW Engineer, Intel Corporation. My opinions are my own and NEVER the opinions of Intel Corporation. -----Original Message----- From: Rob Rhoads [mailto:err...@li...] Sent: Friday, October 18, 2002 7:39 AM To: fau...@li... Cc: ina...@in... Subject: Re: [Fault-injection-developer] Couple of issues downloading and building the FITH source code Ran into a problem... Since we are targeting any Linux kernel developer & not just developers using CGLE, I tried to build FITH on my CoosBay (Intel P4 DP SMP box) running RedHat 8.0. After making sure that the appropriate shared libraries/packages were installed (i.e. libdissasm, libxml2, etc.), I attempted to get the ./configure script built by running Makefile.cvs file. Below was error output. NOTE: When we get around to packaging up a source tarball, we need to include ./configure script already built, so they can just run it and then do a Make all. [errhoads@fuente FITH]$ make -f Makefile.cvs aclocal autoconf automake --add-missing configure.in: installing `./install-sh' configure.in: installing `./mkinstalldirs' configure.in: installing `./missing' man/Makefile.am:1: installing `man/texinfo.tex' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dm.o' overrides `fith_dm.o$(EXEEXT)' : change your target to read `fith_dm.o$(EXEEXT)' src/dm/Makefile.am: installing `./depcomp' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_fakeirq.o' overrides `fith_fakeirq.o$(EXEEXT)' : change your target to read `fith_fakeirq.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_clean' overrides `fith_clean$(EXEEXT)' : change your target to read `fith_clean$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_insmod' overrides `fith_insmod$(EXEEXT)' : change your target to read `fith_insmod$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `mkfithdev' overrides `mkfithdev$(EXEEXT)' : change your target to read `mkfithdev$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_aslt.o' overrides `fith_aslt.o$(EXEEXT)' : change your target to read `fith_aslt.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dbp.o' overrides `fith_dbp.o$(EXEEXT)' : change your target to read `fith_dbp.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dr.o' overrides `fith_dr.o$(EXEEXT)' : change your target to read `fith_dr.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_ovr.o' overrides `fith_ovr.o$(EXEEXT)' : change your target to read `fith_ovr.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_pf.o' overrides `fith_pf.o$(EXEEXT)' : change your target to read `fith_pf.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dm.o' overrides `fith_dm.o$(EXEEXT)' : change your target to read `fith_dm.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_fakeirq.o' overrides `fith_fakeirq.o$(EXEEXT)' : change your target to read `fith_fakeirq.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_clean' overrides `fith_clean$(EXEEXT)' : change your target to read `fith_clean$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_insmod' overrides `fith_insmod$(EXEEXT)' : change your target to read `fith_insmod$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `mkfithdev' overrides `mkfithdev$(EXEEXT)' : change your target to read `mkfithdev$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_aslt.o' overrides `fith_aslt.o$(EXEEXT)' : change your target to read `fith_aslt.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dbp.o' overrides `fith_dbp.o$(EXEEXT)' : change your target to read `fith_dbp.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_dr.o' overrides `fith_dr.o$(EXEEXT)' : change your target to read `fith_dr.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_ovr.o' overrides `fith_ovr.o$(EXEEXT)' : change your target to read `fith_ovr.o$(EXEEXT)' Use of uninitialized value in concatenation (.) or string at /usr/bin/automake line 8449. : deprecated feature: `fith_pf.o' overrides `fith_pf.o$(EXEEXT)' : change your target to read `fith_pf.o$(EXEEXT)' make: *** [all] Error 1 On Thu, 2002-10-17 at 15:17, Rob Rhoads wrote: > OK, got the source, and I'm now going through the build steps and > reading the documentation. In short, its way too TLT specific for a > general announcement on the LKML. > > I haven't attempted to build it yet, but this is what I see so far that > needs to be fixed before the project is announced (in any form) to the > LKML: > > 1. Remove all mention & dependencies on TLT, carrierlinux, etc. from > everything. The README file is full of TLT & carrierlinux 'isms. If this > is going to be posted on LKML, the instructions and code had better work > on a stock kernel by applying relevant kernel patches. > > If you rely on the TLT or CGLE kernel no one on the LKML, outside of > OSDL developers, will take a second look at it. > > The instructions need to be written so anyone can take a stock kernel > apply the relevant patches and make it work. For example, dprobes is > required, but the instruction don't clearly state that you need to apply > the patch to the stock kernel sources. > > 2. You need to break-out the required kernel patches from the user-space > components. Separate source tarballs & separate instructions, might be > one way to do it. Right now it's confusing from reading the README what > exactly you need to do in order to get going. At the very least you need > to build a new kernel with the right patches applied, and then make the > user-space components. > > 3. A lot of the info that's in the README should be in the INSTALL file. > The INSTALL file has good info, but is pretty much generic to running > ./configure. > > 4. To get the best exposure on the LKML, it would be better to also > provide instructions on how to make it work on the 2.5 kernel. I would > think that would be just a matter of getting the patches working on the > 2.5 kernel. This could be any area where we ask for community help in > making it work on 2.5. This shouldn't stop us from announcing, but after > listening to Greg K-H yesterday and my past experience this is the > conclusion I come to. > > More comments to follow...stay tuned... > > -RobR > > > On Thu, 2002-10-17 at 13:25, Rob Rhoads wrote: > > I'm attempting to download the source to FITH for building, but it > > appears that it is only available via checking out directly from CVS. It > > would be nice if you post a tarball of the source code to both the > > project web page and under the file section on the project page. > > > > Also make me a member of the project (my SF account errhoads), so I > > don't have to monkey around with trying to get anonymous :pserver to > > work around the our stupid corporate firewall. > > > > Thanks. > > > > -- > > Rob Rhoads mailto:err...@li... > > Telecom Software Platforms office: 503-677-5498 > > Intel Communications Group > > > > <disclaimer value="pointless"> > > This email message solely contains my own personal views, > > and not necessarily those of my employer. > > </disclaimer> > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by: viaVerio will pay you up to > > $1,000 for every account that you consolidate with us. > > http://ad.doubleclick.net/clk;4749864;7604308;v? > > http://www.viaverio.com/consolidator/osdn.cfm > > _______________________________________________ > > Fault-injection-developer mailing list > > Fau...@li... > > https://lists.sourceforge.net/lists/listinfo/fault-injection-developer > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: viaVerio will pay you up to > $1,000 for every account that you consolidate with us. > http://ad.doubleclick.net/clk;4749864;7604308;v? > http://www.viaverio.com/consolidator/osdn.cfm > _______________________________________________ > Fault-injection-developer mailing list > Fau...@li... > https://lists.sourceforge.net/lists/listinfo/fault-injection-developer ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ Fault-injection-developer mailing list Fau...@li... https://lists.sourceforge.net/lists/listinfo/fault-injection-developer |
From: Rob R. <err...@li...> - 2002-10-22 02:53:30
|
On Mon, 2002-10-21 at 19:27, Zhuang, Louis wrote: > Thanks Rob for his push! :) > We've made FITH conformable to Red hat 8.0. Now, it is conformable to ISO > C99, aclocal 1.6, autoconf 2.53, automake 1.6. But, kernel with Red hat 8.0 > is not suitable for compiling and running FITH because DProbes and some > symbol exports are needed. The CGL precompiled kernel is most suitable for > that. :) http://builds.developer.osdl.org/index.php?ver=v1_0&type=stable > > Louis Zhuang, SW Engineer, Intel Corporation. > My opinions are my own and NEVER the opinions of Intel Corporation. Sorry Louis, but if we want this to be a useful SF project & one that we can announce on the LKML, we've got to provide the patches and instructions for someone to take a stock 2.4.x or 2.5.x kernel and get it working for use with FIFTH. I would further argue that 2.5.x is more important than 2.4.x, at least to the kernel developer community. Look at this way, someone on LKML has no idea what CGLE is, let alone TLT. You need to assume your intended audience only knows about the stock kernel sources on kernel.org. -RobR |
From: Zhuang, L. <lou...@in...> - 2002-10-22 02:39:58
|
OK, got the source, and I'm now going through the build steps and reading the documentation. In short, its way too TLT specific for a general announcement on the LKML. I haven't attempted to build it yet, but this is what I see so far that needs to be fixed before the project is announced (in any form) to the LKML: 1. Remove all mention & dependencies on TLT, carrierlinux, etc. from everything. The README file is full of TLT & carrierlinux 'isms. If this is going to be posted on LKML, the instructions and code had better work on a stock kernel by applying relevant kernel patches. If you rely on the TLT or CGLE kernel no one on the LKML, outside of OSDL developers, will take a second look at it. The instructions need to be written so anyone can take a stock kernel apply the relevant patches and make it work. For example, dprobes is required, but the instruction don't clearly state that you need to apply the patch to the stock kernel sources. We'll fix these issues. thx 2. You need to break-out the required kernel patches from the user-space components. Separate source tarballs & separate instructions, might be one way to do it. Right now it's confusing from reading the README what exactly you need to do in order to get going. At the very least you need to build a new kernel with the right patches applied, and then make the user-space components. Good point! Fixing... :) 3. A lot of the info that's in the README should be in the INSTALL file. The INSTALL file has good info, but is pretty much generic to running ./configure. INSTALL file is generated by 'automake' automatically. We'd like put all information in README. If you think it is an issue, we'll change some installation-relative information into INSTALL. 4. To get the best exposure on the LKML, it would be better to also provide instructions on how to make it work on the 2.5 kernel. I would think that would be just a matter of getting the patches working on the 2.5 kernel. This could be any area where we ask for community help in making it work on 2.5. This shouldn't stop us from announcing, but after listening to Greg K-H yesterday and my past experience this is the conclusion I come to. We all have little experience in 2.5, but we'll try to merge our things into 2.5. Maybe we need some help from other kernel guys :) More comments to follow...stay tuned... -RobR On Thu, 2002-10-17 at 13:25, Rob Rhoads wrote: > I'm attempting to download the source to FITH for building, but it > appears that it is only available via checking out directly from CVS. It > would be nice if you post a tarball of the source code to both the > project web page and under the file section on the project page. > > Also make me a member of the project (my SF account errhoads), so I > don't have to monkey around with trying to get anonymous :pserver to > work around the our stupid corporate firewall. > > Thanks. > > -- > Rob Rhoads mailto:err...@li... > Telecom Software Platforms office: 503-677-5498 > Intel Communications Group > > <disclaimer value="pointless"> > This email message solely contains my own personal views, > and not necessarily those of my employer. > </disclaimer> > > > > ------------------------------------------------------- > This sf.net email is sponsored by: viaVerio will pay you up to > $1,000 for every account that you consolidate with us. > http://ad.doubleclick.net/clk;4749864;7604308;v? > http://www.viaverio.com/consolidator/osdn.cfm > _______________________________________________ > Fault-injection-developer mailing list > Fau...@li... > https://lists.sourceforge.net/lists/listinfo/fault-injection-developer ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ Fault-injection-developer mailing list Fau...@li... https://lists.sourceforge.net/lists/listinfo/fault-injection-developer |
From: Rob R. <err...@li...> - 2002-10-22 02:59:34
|
Louis, not that I want to hammer you some more (better me though, than someone on the LKML -- I learned the hard way *ouch!*) but ... When you respond to someone's e-mail with in-line comments, you need to clearly mark your response or the original text w/ something. So the reader can distinguish what you are saying and what the original poster said. Needless to say, I had a very difficult time distinguishing my comments from yours in your response below. -RobR On Mon, 2002-10-21 at 19:37, Zhuang, Louis wrote: > OK, got the source, and I'm now going through the build steps and > reading the documentation. In short, its way too TLT specific for a > general announcement on the LKML. > > I haven't attempted to build it yet, but this is what I see so far that > needs to be fixed before the project is announced (in any form) to the > LKML: > > 1. Remove all mention & dependencies on TLT, carrierlinux, etc. from > everything. The README file is full of TLT & carrierlinux 'isms. If this > is going to be posted on LKML, the instructions and code had better work > on a stock kernel by applying relevant kernel patches. > > If you rely on the TLT or CGLE kernel no one on the LKML, outside of > OSDL developers, will take a second look at it. > > The instructions need to be written so anyone can take a stock kernel > apply the relevant patches and make it work. For example, dprobes is > required, but the instruction don't clearly state that you need to apply > the patch to the stock kernel sources. > We'll fix these issues. thx > > > 2. You need to break-out the required kernel patches from the user-space > components. Separate source tarballs & separate instructions, might be > one way to do it. Right now it's confusing from reading the README what > exactly you need to do in order to get going. At the very least you need > to build a new kernel with the right patches applied, and then make the > user-space components. > Good point! Fixing... :) > > > 3. A lot of the info that's in the README should be in the INSTALL file. > The INSTALL file has good info, but is pretty much generic to running > ./configure. > INSTALL file is generated by 'automake' automatically. We'd like put all > information in README. If you think it is an issue, we'll change some > installation-relative information into INSTALL. > > > 4. To get the best exposure on the LKML, it would be better to also > provide instructions on how to make it work on the 2.5 kernel. I would > think that would be just a matter of getting the patches working on the > 2.5 kernel. This could be any area where we ask for community help in > making it work on 2.5. This shouldn't stop us from announcing, but after > listening to Greg K-H yesterday and my past experience this is the > conclusion I come to. > We all have little experience in 2.5, but we'll try to merge our things into > 2.5. Maybe we need some help from other kernel guys :) > > > More comments to follow...stay tuned... > > -RobR > > -- Rob Rhoads mailto:err...@li... Telecom Software Platforms office: 503-677-5498 Intel Communications Group <disclaimer value="pointless"> This email message solely contains my own personal views, and not necessarily those of my employer. </disclaimer> |
From: Rob R. <err...@li...> - 2002-10-22 04:11:59
|
On Mon, 2002-10-21 at 21:07, Wang, Stanley wrote: > Hi Rob, > The modified version insmod's job is very simple: > 1. finds out all "in_x/out_x" instruction in the tested module and replaces > them with "int3" > 2. redirect "ioremap" and "request_irq" to FITH's hook > What does dprobes do? > These work can be done in kernel space with more difficulty :( > So we do it in user space (insmod). > > Thanks, > Stanley > -- Rob Rhoads mailto:err...@li... Telecom Software Platforms office: 503-677-5498 Intel Communications Group <disclaimer value="pointless"> This email message solely contains my own personal views, and not necessarily those of my employer. </disclaimer> |