From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Tue, 8 Jan 2008 20:25:11 +0100 From: "Sander van Dijk" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] Re: Duplicate entries in fresh plan9.ini In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Topicbox-Message-UUID: 28d44a3c-ead3-11e9-9d60-3106f5b1d025 On Jan 7, 2008 11:18 PM, erik quanstrom wrote: > 9fans is a fine place for this. perhaps no one with much experience > with the install process has had time to take a look. you might also > consider submitting a patch. I'd like to, but I'm not sure yet what the right fix is. The hack I suggested in my initial mail could be sufficient temporarily, but definitely not in the long run. Before the introduction of the third boot menu item, all the things from the plan9.ini on the cd-rom that needed to go into a freshly installed plan9.ini would be some of the lines under [common]. That's what the original grep line accomplished back when the menu items only indicated what bootfile and bootargs to use. Now however, the menu items set more things. So I guess a starting point would be to replace the grep line with something that takes only the necessary lines from [common], and never any other lines. This would create a fresh plan9.ini pretty much the same as it was before the third boot menu item was introduced. However, I believe the extra settings under the different menu items aren't there for no reason; not adding them to a fresh plan9.ini could possible leave a fresh installation unbootable. In other words, some of the lines from [install] or [cdboot] should probably go into a fresh plan9.ini as well, but I'm not sure which ones (or based on what the install script should decide which ones, and whether to take them from [install] or [cdboot]). If anyone can answer those questions, or at least provide some thoughts about it, thanks! Greetings, Sander.