Date: Mon, 24 Nov 2003 13:56:02 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Stefan Bethke <stb@lassitu.de> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: LOR filedesc structure / Giant Message-ID: <20031124215602.GA22244@xor.obsecurity.org> In-Reply-To: <8E91F75D-1EC8-11D8-8B89-000393496BE8@lassitu.de> References: <310DD19B-1EBF-11D8-8B89-000393496BE8@lassitu.de> <20031124211946.GA21432@xor.obsecurity.org> <8E91F75D-1EC8-11D8-8B89-000393496BE8@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 24, 2003 at 10:52:54PM +0100, Stefan Bethke wrote: >=20 > Am 24.11.2003 um 22:19 schrieb Kris Kennaway: >=20 > >On Mon, Nov 24, 2003 at 09:45:51PM +0100, Stefan Bethke wrote: > >>This is with a current from around two days ago, with a kernel not=20 > >>much > >>different from GENERIC. > > > >Known problem. >=20 > I do follow -current quite closely, but none of the cvs lists. It=20 > appears that I missed some important info. What should I monitor more=20 > closely? What can I do to analyze this more closely? First checking the mailing list archives and PR database for similar problem reports is often prudent. This one has been reported for several months, and I also submitted a PR about it. Kris --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/wn5yWry0BWjoQKURAtHlAKCBYSfE4UegXLj5G30SG7w30IDyAACg667i 4pLCH5hASoPI3S1BLeAtrps= =Kn6S -----END PGP SIGNATURE----- --huq684BweRXVnRxX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031124215602.GA22244>