RE: ColdFusion 4.5 RC3
Are there differences in the Linux emulation from -stable -> -current? > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Hechinger > Sent: Thursday, January 27, 2000 5:34 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: ColdFusion 4.5 RC3 > > > I can consistantly get ColdFusion 4.5 RC3 installed on > FreeBSD-current. > It will not work on -stable (i didn't really mess with it too much > however) > > i haven't gotten the Apache module to work yet (but i haven't > even looked > at it, so give me time) > > instructions are at http://users.tmok.com/~wonko/cf > > -wonko > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: SMP changes and breaking kld object module compatibility
SMP is a significant area of weakness for 4.0 and begs for improvement. I for one am thrilled at the progress Matt's made in this area and am itching to incorporate the changes into my 4.0 development servers (my production servers are still at 3.4-STABLE pending 4.1). If recompiling bothers you so much, we can have make a tarball distribution of the new module binaries. There - problem solved. People are going to have to recompile their kernels also, in order to get the SMP changes. Why is it such a stretch to require recompiling the kernel modules as well? My 2 cents... > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Richard > Wackerbarth > Sent: Monday, April 24, 2000 5:47 AM > To: Matthew Dillon > Cc: [EMAIL PROTECTED] > Subject: Re: SMP changes and breaking kld object module compatibility > > > On Mon, 24 Apr 2000, Matthew Dillon wrote: > > : However, I consider your SMP changes VERY destablizing; they BREAK > > : lots of modules :-( > > > > Huh? No they don't. They simply require recompiling > the modules. If > > they actually broke the modules I wouldn't be trying to > MFC it to > > -stable. > > >From the USER's perspective, anything that requires me to as > much as reload > a module/program that I have already installed "breaks" it. > The fact that it is only necessary to recompile it in order > to fix it only > means that it is easy to fix IF I have the source code. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: SMP changes and breaking kld object module compatibility
> No-one forces you to upgrade you systems. Partial upgrades > are something that are > nice when they work, but understood when they don't. > > We don't accept bug reports (typically) when a person hasn't > upgraded their world, > kernel, and modules. I don't understand why we're accepting > preemptive bitching. Very well said. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: SMP changes and breaking kld object module compatibility
One (relatively minor) example is Open Sound System... http://www.opensound.com/freebsd.html Al > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Jordan > K. Hubbard > Sent: Monday, April 24, 2000 2:58 PM > To: Rodney W. Grimes > Cc: Jacques A . Vidrine; Richard Wackerbarth; > [EMAIL PROTECTED] > Subject: Re: SMP changes and breaking kld object module compatibility > > > > Gee, is that perhaps because FreeBSD keeps breaking the ABI > to modules > > so every vendor that has ever tried to use them has been > bitten by the > > fact that they have to maintain N version for each branch > of FreeBSD??? > > Can you list some specific examples? I'm not trying to be a wise-ass, > I'm trying to figure out which vendors are using KLDs in general since > I've still yet to actually bump into a real-life example of this kind > of breakage in the field. I'm not saying that it's never happened, > I'm simply saying that I've not seen it and would like some details on > such incidents - company name and module type will do fine. > > - Jordan > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
