Date: Thu, 30 Sep 1999 13:50:20 +1000 From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au> To: Adam Strohl <adams@digitalspark.net> Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: sigset_t changes committed Message-ID: <99Sep30.134732est.40334@border.alcanet.com.au> In-Reply-To: <Pine.BSF.4.10.9909292212100.7566-100000@nightfall.digitalspark.net> References: <37F2BA3C.D54CC74B@acm.org> <Pine.BSF.4.10.9909292212100.7566-100000@nightfall.digitalspark.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 30, 1999 at 08:17:16AM +1000, Adam Strohl wrote: >On Wed, 29 Sep 1999, Jim Bloom wrote: > >>I believe this must be fixed. At some point in time, there is going >>to be another change to the kernel such that some older version of the >>code cannot run on a new kernel. > >FTPing a GENERIC kernel from somewhere would solve this, then just >single user the box, make world. Build your kernel. Reboot. This assumes that your old world can work correctly with your new kernel (remembering that `make world' is seen as our standard system stress test). The whole justification for the `install the world then upgrade the kernel' approach has been that we _do_not_ guarantee this. >Furthermore, for when 4.0 becomes a -R or -S, ftping in a compiled kernel >shouldn't be that hard of a price to pay for going from 3.2. We've never required this before. I managed to convert from 2.2.6 to -current using `make upgrade'. Why should I need to FTP a kernel from another machine to go from 3.x to 4.x? Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 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?99Sep30.134732est.40334>