Date: Wed, 10 Apr 2002 19:37:11 -0700 From: Jonathan Mini <mini@haikugeek.com> To: Andrzej Bialecki <abial@webgiro.com> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: Feature removal without replacement (was: cvs commit: src/sys/alpha/alpha machdep.c src/sys/conf NOTES) Message-ID: <20020410193711.C34704@stylus.haikugeek.com> In-Reply-To: <3CB4A9CC.B5D46293@webgiro.com>; from abial@webgiro.com on Wed, Apr 10, 2002 at 11:08:28PM %2B0200 References: <4868.1018415500@critter.freebsd.dk> <3CB4A9CC.B5D46293@webgiro.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrzej Bialecki [abial@webgiro.com] wrote : > > I wonder also how to retrieve later the hints settings from running > kernel, in order to save them into a file (a la kget, or dset before > that)... Are hints preserved and exported anywhere to userland? > Well, there are a few ways that this information can be retained between boots. You can set it up so that it is passed from the loader to the kernel to userland and back to disk. This sounds like a hack, but it might be useful in some cases (like to know when a particular boot actually worked). Alternatively, ficl scripts can write to file already allocated on a ufs partition. They can't create, remove, extend, truncate, or rename files. They can't modify directories. This is a somewhat limited interface to the disk, but it is enough to make nextboot(8) like functionality, and I've seen it used to implement a reliable failover system. We should be able to lay down device hints as well, though some hacks may be required to make it pretty. -- Jonathan Mini mini@haikugeek.com <baka^ni> desolation... despair... plastic forks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020410193711.C34704>