Date: Mon, 12 Sep 2005 11:04:34 -0700 From: Nate Lawson <nate@root.org> To: obrien@FreeBSD.org Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/conf kern.post.mk Message-ID: <4325C332.3060105@root.org> In-Reply-To: <20050912165939.GB94181@dragon.NUXI.org> References: <20050911002229.51F4916A471@hub.freebsd.org> <432382BC.5080105@root.org> <p0623090bbf493c4e4b1e@[128.113.24.47]> <20050911022901.GA3090@xor.obsecurity.org> <432397EF.5000409@FreeBSD.org> <4324A5EF.3050803@root.org> <20050911215807.GA96773@xor.obsecurity.org> <4325A5A1.8080804@root.org> <20050912165939.GB94181@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote: > On Mon, Sep 12, 2005 at 08:58:25AM -0700, Nate Lawson wrote: > >>Kris Kennaway wrote: >> >>>On Sun, Sep 11, 2005 at 02:47:27PM -0700, Nate Lawson wrote: >>> >>>>Can we put it somewhere other than /? /var/run/kernel? >>> >>>Why? That would use up even more space, in total. >> >>Huh? I mean kernel, *.ko -> /boot/kernel and kernel.debug (or >>kernel.sym once that's fixed) -> /var/crash/kernel/kernel.debug > > > I believe you'll get at least one response that it makes it harder to > keep the straight which symbols match which kernel. One may > 'mv /boot/kernel /boot/kernel.good-fifo' and forget to > 'mv /var/crash/kernel /var/crash/kernel.good-fifo'. By keeping kernel + > symbols in one place this isn't an issue. > > I think a better approach would be to split the kernel into runnable part > and symbols part. The symbols would be bzip2'ed and kept beside the > runnable part. kgdb would grow support to read a bzip2'ed file (using > libbz2.so). Then the space issue wouldn't be such an issue. > This sounds good to me. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4325C332.3060105>