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
