From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: jmk@plan9.bell-labs.com To: 9fans@cse.psu.edu Subject: Re: [9fans] buglet in 9load In-Reply-To: <200301080802.h0882snd095308@ducky.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Wed, 8 Jan 2003 22:09:29 -0500 Topicbox-Message-UUID: 3d048bc8-eacb-11e9-9e20-41e7f4b1d025 yes, there's a bug there. i will fix it. the failure causes it to run the entire plan9.ini without 'menu' interpretation rather than just a single menu block - you see $menuitem as 'baz' as that's the last time menuitem is assigned to in the file. On Wed Jan 8 03:03:20 EST 2003, mike@ducky.net wrote: > I just accidently created a plan9.ini file like this: > > menuitem=foo > menuitem=bar > menuitem=baz > menudefault=foo > > ... > > [foo] > > ... > > [bar] > > ... > > (I forgot to provide a [baz] configuration block.) > > When I tried to boot up, 9load correctly complained that I had > provided no [baz] configuration block. > > But then, without giving me a chance to choose between either of > the two valid configurations foo and bar, it went ahead and booted > up. And it turned out that, rather than having booted with the > specified default foo configuration, it had tried to boot baz > (that is, $menuitem in the environment after boot was baz).