Date: Thu, 24 Jul 1997 23:42:29 +0100 From: Ade Lovett <ade@lovett.com> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: current@freebsd.org Subject: Re: Well, I finally bought a test laptop and decided to jump in... Message-ID: <E0wrWab-0003Ik-00@byako.lovett.com> In-Reply-To: Your message of "Thu, 24 Jul 1997 10:13:52 PDT." <13127.869764432@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Jordan K. Hubbard" writes: > >Shall we get this stuff into 3.0? It's light-years better than what >we have now, and had it not been for the PAO kit I would not have had >an easy time of installing this machine at all. By not integrating >the PAO stuff in all this time, we've denied laptop users the ability >to install the 3.0 SNAPs and that's an unfortunate situation which >should be fixed. Yes yes yes yes yes :) I'm willing to commit some time and effort to this -- my own laptop is running 2.2.2-release + PAO patches, and there seems to be no way for me to move to 3.0-current -- I really don't want to have to go and buy a smallish uni-processor 'normal' PC in order to test uni-processor 3.0-current systems against their SMP big brothers. Should I wish to run -current on my laptop, I'm faced with the rather daunting prospect of applying/patching the current PAO every time my -current kernel tree gets updated.. this would seem to be a major waste of time and effort. Given that there appears to be a reasonable level of PAO support in 2.2.2-release, even without the extra PAO stuff, surely it makes sense to merge the PAO project into -current? -aDe -- Ade Lovett, Demon Internet Ltd.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0wrWab-0003Ik-00>