Date: Wed, 26 Oct 2005 09:56:29 -0400 From: Vivek Khera <vivek@khera.org> To: freebsd-amd64 List <freebsd-amd64@freebsd.org> Subject: Re: amd64/87898: Failt to init X: can't open device/io Message-ID: <7AC768D9-B3DF-4C19-91AC-D1C9DC5646A3@khera.org> In-Reply-To: <200510252025.11989.joao@matik.com.br> References: <200510240520.j9O5KH6j006068@freefall.freebsd.org> <20051025180840.GA48844@xor.obsecurity.org> <FE8898EA-96AC-4A99-B383-E49E0F433571@khera.org> <200510252025.11989.joao@matik.com.br>
index | next in thread | previous in thread | raw e-mail
On Oct 25, 2005, at 7:25 PM, JoaoBR wrote: > any version comes wit GENERIC and this changes are correctly > adviced by beeing > set device io and mem in it > yes, but how many people replace their custom kernel with GENERIC on an upgrade from a minor version? > we are talking 6.0 I guess and this was an issue from 5.2.1 to 5.3 > so IMO your > claim is almost a year too late and this is not exactly an amd64-issue > my point was that changes like this should be documented more prominently. either that or 5.3 /really/ should have been called 6.0 due to the massive changes that went into it. and no it is not an amd64 issue, but the conversation is here, so I comment here. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-869-4449 x806home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7AC768D9-B3DF-4C19-91AC-D1C9DC5646A3>