Date: Fri, 02 Oct 1998 09:51:30 -0700 From: Mike Smith <mike@smith.net.au> To: Peter Wemm <peter@netplex.com.au> Cc: Andreas Klemm <andreas@klemm.gtn.com>, "Kenneth D. Merry" <ken@plutotech.com>, ken@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/cam/scsi scsi_sa.c src/sys/conf options src/sys/i386/conf LINT Message-ID: <199810021651.JAA00381@dingo.cdrom.com> In-Reply-To: Your message of "Sat, 03 Oct 1998 00:32:31 %2B0800." <199810021632.AAA23867@spinner.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hmm.. Perhaps 'sysctl -W foo.bar=10' might be a way to request > persistance. Implementing it would be hell though, but for INT variables > at least it should just be a matter of grubbing around inside /dev/kmem > (or some option to sysctl itself to tell us the kva of the backing > variable) and then stow that away in the booted kernel image (if > permitted). And it would only work for varaiables in the data segment > rather than bss or initialized-to-zero. > > Argh.. On second thoughts maybe I'll just shutup. Add some more code to the sysctl initialiser to go looking for a kernel environment variable that matches the name of the sysctl variable and initialises it from there. Then put 'set kern.some.variable=value' in /boot/boot.conf (or wherever). Not much code to add, really. Not that it gets the 'persistence' idea right either, of course. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810021651.JAA00381>