Date: Wed, 03 Apr 2002 22:37:15 +0900 From: Makoto Matsushita <matusita@jp.FreeBSD.org> To: current@FreeBSD.org Subject: Re: BTX halted Message-ID: <20020403223715R.matusita@jp.FreeBSD.org> In-Reply-To: <20020403221142C.matusita@jp.FreeBSD.org> References: <20020325140514.92844.qmail@web21101.mail.yahoo.com> <4496.62.179.190.82.1017072085.squirrel@webmail.debolaz.com> <20020403221142C.matusita@jp.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
matusita> I doubt there is a problem around libz (which is updated matusita> between two JPSNAPs shown above), since the kernel in matusita> kern.flp is gzipped, but most users doesn't gzip their matusita> kernel on HDD. Yeah, bingo! :-) My friend on IRC confirms that 'gzip'-ed kernel on HDD doesn't boot. gzip's compression level doesn't matter; gzip -9 kernel (the same option of boot floppy's kernel) and gzip kernel (no option) is the same result. I've swapped kern.flp's /boot/loader (actually kgzip-ed loader(8)) to older one, and it works perfectly. All problems are in loader(8). loader(8) uses libstand, and libstand have a part of libz code. After importing new libz, something goes wrong with libstand. Anybody know typical pitfalls of using new libz? I've seen some commits for adapting the new libz, but sorry I forget what they were. -- - Makoto `MAR' Matsushita 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?20020403223715R.matusita>