Date: Mon, 9 Jun 2008 06:55:06 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Michel Talon <talon@lpthe.jussieu.fr>, freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 Message-ID: <20080608205506.GI67629@server.vk2pj.dyndns.org> In-Reply-To: <20080608154920.GA8266@lpthe.jussieu.fr> References: <20080608154920.GA8266@lpthe.jussieu.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
--x1F0m3RQhDZyj8sd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jun-08 17:49:20 +0200, Michel Talon <talon@lpthe.jussieu.fr> wrote: >and it is now working perfectly well without any trouble. The only >"gotcha" is the slowness of X problem when compiling, but i live with that. Have you tried SCHED_ULE? In my experience, it does a better job of scdeduling than SCHED_4BSD, even on UP machines (YMMV). >which are perhaps susceptible of destabilising it. Personnally i have >seen the same occurring with 6.0, 5.0 and 4.*, for me the last releases >of the 4.* were very poor on my laptop while the early 4.* releases were >perfectly OK. =20 The difficulty with the later 4.x releases was that there were major differences between the 4.x and later kernels and this made it increasingly difficult to backport bugfixes. This is less of an issue with now 4.x is out of the way. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --x1F0m3RQhDZyj8sd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhMRyoACgkQ/opHv/APuIfVrACgxBeYGtq6kuqyRCquTq968eON pXwAnjrIcz0s8Yv0ZLXV1KLDY5cH4DUg =zbJz -----END PGP SIGNATURE----- --x1F0m3RQhDZyj8sd--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080608205506.GI67629>