From mboxrd@z Thu Jan  1 00:00:00 1970
From: smiley@zenzebra.mv.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
References: <86ipu0evi2.fsf@cmarib.ramside>
	<95260b7e190c22af011c28169a4b2c38@brasstown.quanstro.net>
	<86oc3sv31d.fsf@cmarib.ramside>
	<1fda448af4d14fd45e11fc96eb572eef@ladd.quanstro.net>
	<864o5ipg2z.fsf_-_@cmarib.ramside>
	<139b00c13de072ed8b51dd8629ccf849@coraid.com>
	<86d3k6nyfl.fsf@cmarib.ramside>
	<bb6d42b413a2283823d126e87305ca0f@coraid.com>
	<86pqo647el.fsf@cmarib.ramside>
	<1423139127405d65159aa569ebf07497@coraid.com>
Date: Fri, 29 Apr 2011 04:31:59 +0000
In-Reply-To: <1423139127405d65159aa569ebf07497@coraid.com> (erik quanstrom's
	message of "Thu, 28 Apr 2011 14:33:47 -0400")
Message-ID: <86hb9h1xvk.fsf@cmarib.ramside>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [9fans] Compiling 9atom kernel WAS: Re: spaces in filenames
Topicbox-Message-UUID: d7e5acac-ead6-11e9-9d60-3106f5b1d025

erik quanstrom <quanstro@labs.coraid.com> writes:

> ; 9diff mkfile
> /n/sources/plan9//sys/src/libc/386/mkfile:23,28 - mkfile:23,29
>   	strcpy.s\
>   	strlen.s\
>   	tas.s\
> + 	trace.s\
>   	vlop.s\

Oh, of course!  If it isn't assembled, the loader will never find the
symbols.  :) That addition enabled libc to compile successfully.  The
subsequent kernel compile succeeded as well.  After a reboot, my file
system is now able to store files with spaces in their names.  Yeay!

Much thanks!

(Interestingly, the 9pcf.gz produced was about 7KB smaller than the one
you gave me.  I'm guessing that there's some additional stuff in your
9pcf that's not in mine, but it seems to be working fine.)

--
+---------------------------------------------------------------+
|E-Mail: smiley@zenzebra.mv.com             PGP key ID: BC549F8B|
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA  3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+