Date: Fri, 28 Jan 2000 23:33:44 +0100 From: "Marcel Moolenaar" <marcel@scc.nl> To: "John Baldwin" <jhb@freebsd.org> Cc: <current@freebsd.org>, <committers@freebsd.org>, "Jeroen Ruigrok van der Werven" <asmodai@bart.nl> Subject: Re: More world breakage Message-ID: <002301bf69df$bd24eb00$0301a8c0@adm.scc.nl> References: <200001281951.OAA01002@server.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I already have patches (somewhere :-) that solve this problem. I choose not > > to apply these before the release. I will fix installworld after the > > release. For now, you can use the buildkernel and installkernel targets > > (after a buildworld) to solve the (possibly complex) dependencies between > > kernel, modules and world. > > This isn't related to the kernel though, it is a dependency within the world > between libraries and binaries. It's also related to the kernel, where installworld is installing and subsequently running binaries that won't work with the current kernel. The same applies to installing shared binaries and running them without the proper libraries. > Do you have those patches somewhere where I > can look at them. I want to start testing them, because it _may_ (I'm only > saying "may" right now) be better to fix this before 4.0 so that we don't have > 4 million using cvsup to upgrade to 4.0 (despite all the warnings about 4.0 > being only for early adopters) and then running into this and flooding > -questions. I'd like to prevent a FAQ rather than create one, if you know > what I mean. I don't think we should change yet another thing before a release. The problem shouldn't have been created this close to a release in the first place. We have to stop somewhere, and I think we should stop "fixing" right here, right now unless there's a *really* good reason not to (IMO of course). BTW: I've posted the patches before on -committers IIRC... marcel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002301bf69df$bd24eb00$0301a8c0>