From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <2024739E-69C6-4A14-9B11-2D583B3A1FC8@utopian.net> From: Josh Wood To: corey@bitworthy.net, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: <200907212221.16902.corey@bitworthy.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Tue, 21 Jul 2009 22:59:49 -0700 References: <200907212221.16902.corey@bitworthy.net> Subject: Re: [9fans] a few misc. questions... Topicbox-Message-UUID: 2a329558-ead5-11e9-9d60-3106f5b1d025 > How do I enable hd dma? There's a dmamode=ask in my plan9.ini, but > I don't > see that option mentioned in the plan9.ini man. echo dma on > /dev/sdXY/ctl see in sd(3). > I've been running into mention of kfs throughout various rc scripts > and > whatnot; is kfs simply the default file system for a plan 9 terminal? Kfs is the older disk file system for standalone terminals and the like. For most purposes, fossil replaces it. Fossil is user-mode, while kfs is a "kernel file system." See in kfs(4). > Where's the boot log located (I looked in /sys/log)? I'm seeing some > errors > being printed to the console after I specified which user to log in > as at the > prompt, but those errors vanish too quickly for me to parse. > cat /dev/kmesg You will usually need to be hostowner. See in cons(3). (And also kprint there, for routing the messages elsewhere.) > Finally, regarding the errors I just mentioned, they seem to be > something > along the lines of: > > "can't initialize venti /dev/scd0/arenas: arena header or trailer > corrupted" My first guess is to ensure you haven't overlapped partitions or something. -Josh