CML2 Transition experiences
1. If I install CML2 and go directly to "make xconfig", it deduces it needs to set top level options because some of the low level options are set. For example SCSI enabled because some SCSI device is set or hot plug because PCMCIA is set...because some PCMCIA device is set. The _problem_ is...none of these options were set in the CML1 generated .config file... and it _extremely_ tedious to use xconfig to clear out all the cruft. A much better (but not yet right) way is to use "make ttyconfig" to quickly generate config.out from .config relatively fewer errors and ability to say no at a top level and cause all the lower level stuff to go away. make ttyconfig seems to parse the .config file in a different (and better) order. Suggestion: On the first pass of CML2 processing through .config, before first config.out created, trust the top level setting and ignore lower level settings if top setting off. 2. So after some playing around, I want to go back to CML1. But the .config generated by CML2 is not compatible. I don't know if it's supposed to be but there's lots of problems. Suggestion: Save your .config before you play with this stuff. Bottom line: looks promising but I still haven't gotten a good compile from it, yet. jeff - 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/
v2.4.3 networking problem other than tcp_ecn?
Several web sites have stoped working recently about the time I upgraded to 2.4.2 - 2.4.3. Some testing at one site showed it doesn't respond to pings except for an occasional reply reported as "admin prohibited filter" by tcpdump or as "packet filtered" by ping. The kernel doesn't have tcp_ecn compiled in, access is via ppp and dialup, everything possible compiled as modules, iptables firewall setup. This problem applies to machine on the local net and to the firewall itself. ideas? jeff - 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: comments on CML 1.1.0
Selecting IP_NF_COMPAT_IPCHAINS turns off IP_NF_CONNTRACK and friends. But, I think CML1, allowed both support to the new iptables and compatibility modes to allow old ipchains scripts to work with the new kernel. jeff - 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: CML2 1.0.0 doesn't remember configuration changes
- Original Message - From: <[EMAIL PROTECTED]> To: jeff millar <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; Eric S. Raymond <[EMAIL PROTECTED]> Sent: Wednesday, April 11, 2001 10:50 PM Subject: Re: CML2 1.0.0 doesn't remember configuration changes . > > > > The READ.ME says that "make config" will run configtrans to generate > > .config. But that doesn't explain why "make config" doesn't remember > > changes made to config.out. > > > > ideas? > > > > jeff > > I think it's because I misunderstood how the standard productions are supposed > to work. If you'll tell me what files you expect them to read on startup, > and in what order, I can emulate that behavior. I'm probably one of least qualified persons to answer that question. But maybe saying something wrong will create the usual flood of corrections. >From what's in the various documentation and reading about 1% of the cml2 traffic... cml2's various "make *config" invocations use config.out as a database for remembering configuration, and then on exit they all generate a fresh copy of .config. Apparently it's too hard to read the existing .config to generate an initial config.out, so I think "make *config" the first time, starts with some default and then on exit _should_ write that to config.out. Then any other invocationn of *make *config". needs to use config.out. "make xconfig", "make config" and "make editconfig" need to operate the same way. I've never use anything but "make xconfig", "make menuconfig" and "make oldconfig" and they currently all operate on the same information. I've never used editconfig and don't know what it's for. 1.0.3 feels faster, btw. - 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: CML2 1.0.0 doesn't remember configuration changes
I'm confused. Downloaded cml2-1.0.0 installed ran itappear to work but it doesn't remember my changes. Just now, I updated to 1.0.3 and it reported cleaning up existing files. Ran "make config" and it popped up menu under X. Then I changed the "config policy options" to "expert, wizard, tuning" and exited with "save and exit". Then re-opened with make config and nothing changed...expert, wizard and tuning not set. Maybe the program _knows_ I'm not a wizard but it should at least let me _tune_. (joke) By the way "make editconfig" shows the changes made under "make config" and allows me to make more changes.. The READ.ME says that "make config" will run configtrans to generate .config. But that doesn't explain why "make config" doesn't remember changes made to config.out. ideas? jeff - 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/
RedHat 7.0 anaconda installer doesn't support devfs
Redhat support got back to me today and said 7.0 doesnt support upgrades to systems running devfs. But I thought sure than Linus blessed it! :-) Does anyone have a fix? - 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: What is up with Redhat 7.0?
Sound like "Embrace and Extend" with a different flavor, similar effect. jeff - Original Message - From: "Theodore Y. Ts'o" <[EMAIL PROTECTED]> To: "Marc Lehmann" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, September 30, 2000 1:37 AM Subject: Re: What is up with Redhat 7.0? > It's not just gcc which RedHat did this to. They do this regularly with > the kernel (where they've used 2.2.17preXX kernels), glibc (they are > shipping with a beta of glibc 2.2 in RH 7.0), XFree-86 (they're using an > unstable snapshot of XFree86 taken from the CVS repository --- the > XFree86 folks I talked to weren't impressed with the stability of the > snapshot they took, and weren't entirely happy with RH's decision), etc. > > At this point, I can only hope and pray that Ulrich Drepper doesn't > choose to make any backwards incompatible changes between 2.1.94 and > 2.2. He's within his rights to do so, but if he does, it will make > RedHat possibly incompatible with all other Linux distributions. > > Sigh, we've had ISV's already complaining that it's too hard ship > versions which are compatible with all the various distributions. > Unfortunately it may be that RH 7.0 isn't going to help things in this > regard. Hopefully ISV's will be able to figure out for themselves that > it would be a Bad Idea to develop applications under RH 7.0, since it > might compromise their cross-distribution portability. > > If you don't like this, I suggest you send mail complaining to RedHat. > Customer complaints are going to be the only way that RH is going to be > influenced not to play games like this > > - Ted - 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/
