[9fans] /dist is empty

[9fans] /dist is empty

[Matthias Teege]

Moin,

I have setup a standalone fileserver. All looks god and I can mount
the fileserver to the cpu/auth server to install plan9.9gz. But my
/dist on the cpu/auth server is empty except "replica".

Is it possible, to build a plan9.9gz from the installation CD,
transfer it to the cpu/auth server and then install it on the
fileserver?

Many thanks
Matthias

--
Matthias Teege -- http://www.mteege.de
make world not war
PGP-Key auf Anfrage

Re: [9fans] /dist is empty

[Russ Cox]

[-- Attachment #1: Type: text/plain, Size: 182 bytes --]

plan9.9gz?  that's the old 3e format.
the new format is just a cd.  you want
to mount the cd and then replica/pull -v script
where script is an edited copy of
/dist/replica/cd.

[-- Attachment #2: Type: message/rfc822, Size: 2331 bytes --]

From: Matthias Teege <matthias@mteege.de>
To: 9fans@cse.psu.edu
Subject: [9fans] /dist is empty
Date: Mon, 15 Sep 2003 16:48:13 GMT
Message-ID: <86u17eypdh.fsf@gic.mteege.de>

Moin,

I have setup a standalone fileserver. All looks god and I can mount
the fileserver to the cpu/auth server to install plan9.9gz. But my
/dist on the cpu/auth server is empty except "replica".

Is it possible, to build a plan9.9gz from the installation CD,
transfer it to the cpu/auth server and then install it on the
fileserver?

Many thanks
Matthias

--
Matthias Teege -- http://www.mteege.de
make world not war
PGP-Key auf Anfrage

Re: [9fans] /dist is empty

[Matthias Teege]

rsc@plan9.bell-labs.com (Russ Cox) writes:

> plan9.9gz?  that's the old 3e format.
> the new format is just a cd.  you want

Ok, is because the documentation in the wiki. I'll change this.

> to mount the cd and then replica/pull -v script
> where script is an edited copy of
> /dist/replica/cd.

I have a problem whith the CD. My cpu/auth server run under vmware
and vmware try to boot from the CDROM every time. To work around I
make a copy of the Plan9 CD with "mkisofs -o mp9.iso /cdrom" (under
BSD) which is not bootable. This cd image I can mount but I'm not
sure, if this is a exact copy of the Plan9 CD.

What is the best way to create a non bootable Plan9 CD?

Many thanks
Matthias

--
Matthias Teege -- http://www.mteege.de
make world not war
PGP-Key auf Anfrage

Re: [9fans] /dist is empty

[Russ Cox]

>I have a problem whith the CD. My cpu/auth server run under vmware
>and vmware try to boot from the CDROM every time. To work around I
>make a copy of the Plan9 CD with "mkisofs -o mp9.iso /cdrom" (under
>BSD) which is not bootable. This cd image I can mount but I'm not
>sure, if this is a exact copy of the Plan9 CD.
>
>What is the best way to create a non bootable Plan9 CD?
>
>

just uncheck "connected at power on" from the cd config.
and then connect it manually when you want to use it.
that's like leaving the cd out of the drive until you need it.

Re: [9fans] /dist is empty

[Matthias Teege]

rsc@plan9.bell-labs.com (Russ Cox) writes:

> to mount the cd and then replica/pull -v script
> where script is an edited copy of
> /dist/replica/cd.

I solved my CD problem, transfer the plan9.iso to the cpu/auth
server and mount it via "mount /srv/9660 /n/dist
/usr/bootes/plan9.iso". After that I read man 1 replica and the
"cd" script but I didnt get it.

I mount the fileserver via "9fs batida" to /n/batida and change the
"cd" script on the cpu/auth server like that:

s=/n/dist/dist/replica
serverroot=/n/dist
serverlog=/dist/replica/plan9.log
serverproto=$s/plan9.proto
fn servermount { status='' }
fn serverupdate { status='' }

fn clientmount { status='' }
c=/dist/replica
clientroot=/n/batida
clientproto=$c/plan9.proto
clientdb=$c/client/plan9.db
clientexclude=(dist/replica/client)
clientlog=$c/client/plan9.log

applyopt=(-u -T$c/client/plan9.time)

replica/pull -v script runs without error (after touching
/dist/replica/plan9.log) but there are no files transfered to the
fileserver.

What do I missing?

Many thanks
Matthias

--
Matthias Teege -- http://www.mteege.de
make world not war
PGP-Key auf Anfrage

Re: [9fans] /dist is empty

[Russ Cox]

Matthias Teege wrote:

>rsc@plan9.bell-labs.com (Russ Cox) writes:
>
>
>
>>to mount the cd and then replica/pull -v script
>>where script is an edited copy of
>>/dist/replica/cd.
>>
>>
>
>I solved my CD problem, transfer the plan9.iso to the cpu/auth
>server and mount it via "mount /srv/9660 /n/dist
>/usr/bootes/plan9.iso". After that I read man 1 replica and the
>"cd" script but I didnt get it.
>
>I mount the fileserver via "9fs batida" to /n/batida and change the
>"cd" script on the cpu/auth server like that:
>
>s=/n/dist/dist/replica
>serverroot=/n/dist
>serverlog=/dist/replica/plan9.log
>serverproto=$s/plan9.proto
>fn servermount { status='' }
>fn serverupdate { status='' }
>
>fn clientmount { status='' }
>c=/dist/replica
>clientroot=/n/batida
>clientproto=$c/plan9.proto
>clientdb=$c/client/plan9.db
>clientexclude=(dist/replica/client)
>clientlog=$c/client/plan9.log
>
>applyopt=(-u -T$c/client/plan9.time)
>
>replica/pull -v script runs without error (after touching
>/dist/replica/plan9.log) but there are no files transfered to the
>fileserver.
>
>What do I missing?
>
>

i'm not sure exactly, but i bet you should be setting
c=/n/batida/dist/replica.
as it is, it's using your local machines /dist database to decide
how to handle /n/batida.  if your local machine is up-to-date
then no copying is going to happen on /n/batida.

Re: [9fans] /dist is empty

[Dan Cross]

Russ Cox <rsc@plan9.bell-labs.com> writes:
> i'm not sure exactly, but i bet you should be setting
> c=/n/batida/dist/replica.
> as it is, it's using your local machines /dist database to decide
> how to handle /n/batida.  if your local machine is up-to-date
> then no copying is going to happen on /n/batida.

Please don't do this.  Use what's already there.

	9fs batida
	bind -c /n/batida /n/inst
	mount /srv/9660 /n/dist /path/to/plan9.iso
	replica/inst -v /dist/replica/inst

If /dist/replica/inst doesn't exist on your system (it should; it used to
be on sources, at least) you can try something else.  You don't even really
need the CD (except to be nice to the labs).  Ostensibly, you could just
do:

	mount -c /srv/batida /n/inst
	9fs sources
	bind /n/sources/plan9 /n/dist
	replica/inst -v /dist/replica/inst

I do something like that to update my fileserver from sources all the time.

	- Dan C.

Re: [9fans] /dist is empty

[Russ Cox]

> Please don't do this.  Use what's already there.
>
> 	9fs batida
> 	bind -c /n/batida /n/inst
> 	mount /srv/9660 /n/dist /path/to/plan9.iso
> 	replica/inst -v /dist/replica/inst

Dan is right.  I'd forgotten this.

> If /dist/replica/inst doesn't exist on your system (it should; it used to
> be on sources, at least) you can try something else.  You don't even really
> need the CD (except to be nice to the labs).  Ostensibly, you could just
> do:
>
> 	mount -c /srv/batida /n/inst
> 	9fs sources
> 	bind /n/sources/plan9 /n/dist
> 	replica/inst -v /dist/replica/inst
>
> I do something like that to update my fileserver from sources all the time.

This is great for updating your file server once it's going.
It's not so great for populating it from scratch -- copying
from a CD will be a lot faster, due to the latency of 9P to
sources.

Russ

Re: [9fans] /dist is empty

[boyd, rounin]

From: "Russ Cox" <rsc@plan9.bell-labs.com>
> Dan is right.  I'd forgotten this.

more fine research.

Re: [9fans] /dist is empty

[Matthias Teege]

cross@math.psu.edu (Dan Cross) writes:

> Please don't do this.  Use what's already there.

> 	9fs batida
> 	bind -c /n/batida /n/inst
> 	mount /srv/9660 /n/dist /path/to/plan9.iso
> 	replica/inst -v /dist/replica/inst

Is it necessary to create the directorys (29000, 68000, 68020, i386
...) on the fileserver before running replica?

Many thanks
Matthias

--
Matthias Teege -- http://www.mteege.de
make world not war
PGP-Key auf Anfrage

Re: [9fans] /dist is empty

[Russ Cox]

> Is it necessary to create the directorys (29000, 68000, 68020, i386
> ...) on the fileserver before running replica?

No, replica will do that.

Russ

Re: [9fans] /dist is empty

[Dan Cross]

> plan9.9gz?  that's the old 3e format.
> the new format is just a cd.  you want
> to mount the cd and then replica/pull -v script
> where script is an edited copy of /dist/replica/cd.
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

*Ahem*  That's what /dist/replica/inst is for.

	- Dan C.