From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed, 13 Jan 2010 07:31:07 -0500
To: 9fans@9fans.net
Message-ID: <9b0fd7860db0bf9c30c4998b6fb7e58b@brasstown.quanstro.net>
In-Reply-To: <20100113063909.1D13711803D@smtp.hushmail.com>
References: <20100113063909.1D13711803D@smtp.hushmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [9fans] Ken Fileserver problem
Topicbox-Message-UUID: be39acaa-ead5-11e9-9d60-3106f5b1d025

> I am using the floppy only for testing plan9.ini parameters.
> This should be possible with qemu or other emulators too. Later
> I will use an IDE disk or IDE flash disk (I would prefer the
> second).
> So I am not sure whether it makes sense to spend time to make this
> possible. I can live wíthout the floppy support.
>
> I would like to ask where are the differences between the original
> Ken fileserver and your modifications? Many documents in the web
> seems
> to be made for the original fileserver. So it would be helpfull for
> me to know the differences.

i'm not sure why you are doing it this way.  typically one puts the
plan9.ini right on the hard drive with everything else.  i added
support for the partitions that plan 9 supports to ken fs.  this is
important when sharing aoe equipment.  so it would be easy to
create a 9fat partition with your plan9.ini and other files.  for
example here is the configuration i had for a testing fileserver
on a soekris box.  i had partitioned h0 as usual for a plan 9
cpu server with a 10mb 9fat.

- erik
-----
[menu]
menuitem=fs, fs
menuitem=cpu, cpu
menudefault=fs,5
menuconsole=0 b19200

[fs]
bootfile=sdC0!9fat!9askafs.gz
ether0=type=83815
ether1=type=83815
dumpctl=off
nvr=ph0"9fat"!fs.nvr

[cpu]
bootfile=sdC0!9fat!9pc.gz
bootfile=ether0!ladd!/386/9pc.gz
bootargs=il
nobootprompt=il

[common]
console=0 b19200
*e820print=1