Re: FreeBSD 5.0 RC3 now available
Harald Hanche-Olsen wrote: Indeed. There is an old story from the days of the big irons, when IBM had an objective release criterion stating that no new release of their OS would be shipped with more than 100 major bugs. As a result, before each release, the engineers would have a big meeting with the purpose of redefining major bugs as minor bugs. You make it sound like that doesn't happen anymore. Ah, sadly, it does, and I've been known to be an unwilling participant... :-\ Though we actually go as far as to reclassify bugs as enhancement requests. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 80386 out of GENERIC
Leif Neland wrote: But still, would it be impossible to have both a GENERIC and a GENERIC386 kernel in the distribution? Impossible, no... but would anyone use it? Seems to me that it would just take up space. And it's one more thing for the build gurus to keep a configuration for (though maybe they don't mind/care?). As long as someone can build a 386 kernel by throwing a few flags... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 80386 out of GENERIC
Juli Mallett wrote: Are you implying that these people, who are undoubtedly adding and removing lots of things in the kernel, to make things fit, and to make things do their jobs, can't be bothered to use the appropriate CPU settings? Not sure where you got that from Terry's post, but... As a sometimes embedded developer (who also runs FreeBSD on his comparatively screaming Athlon desktop box), being able to run FreeBSD, fresh off a CD, on a quirky 386 embedded toaster and have it run perfectly would be a dream. Of course, that's never been the case. As others have mentioned, you're lucky if you have a working BIOS. There's usually no room for luxuries like a robust device probing system, a nice, standard PCI bus, queriable hardware, etc. Most of your devices are sitting right on the processor bus (and hopefully you've thrown in enough wait states, but if the thing doesn't respond, spin a bit and hammer it with the request again). As long as it's feasible to compile a kernel for a 386, that's all I could ever home for. Just don't go rewriting the scheduler in assembly and use MMX/SIMD instructions... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
