[9fans] Mirroring plan9 sources

[9fans] Mirroring plan9 sources

[clueelf]

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

Any thoughts on how to mirror plan9 sources?I would be willing to pay for and setup a mirror, but finding servers spec’d to run plan9 in the US seems impossible.

Would setting up plan9port on a hosted Linux vm make sense as an alternative?Anyone doing this?

Looking for thoughts, pointers or experiences in doing this.

If this has already been covered feel free to send a link to a doc or ml archive post.

Thanks!

Tony

[-- Attachment #2: Type: text/html, Size: 578 bytes --]

Re: [9fans] Mirroring plan9 sources

[Lyndon Nerenberg]

clueelf@tonymendoza.us writes:


> or and setup a mirror, but finding servers spec'd to run plan9 in
>  the US seems impossible.

I have run 9front on VPSes at ARP Networks.  These days 9front
should just work out of the box.  ARP's support staff have been
very helpful tuning the underlying qemu/kvm settings for me when
I have needed that, and they don't shy away from helping run
"oddball" OSes like Plan 9.

--lyndon

Re: [9fans] Mirroring plan9 sources

[Skip Tavakkolian]

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

Plan 9 does run on AWS and GCP.  There are at least two existing images to
start from. Richard Miller created an image for AWS and David du
Colombier created one for GCP.  Check out 9legacy and this list's archive
for the how-to's.

On Thu, Mar 7, 2019, 1:51 PM <clueelf@tonymendoza.us> wrote:

> Any thoughts on how to mirror plan9 sources?  I would be willing to pay
> for and setup a mirror, but finding servers spec’d to run plan9 in the US
> seems impossible.
>
> Would setting up plan9port on a hosted Linux vm make sense as an
> alternative?  Anyone doing this?
>
> Looking for thoughts, pointers or experiences in doing this.
>
> If this has already been covered feel free to send a link to a doc or ml
> archive post.
>
> Thanks!
>
> Tony
>

[-- Attachment #2: Type: text/html, Size: 1130 bytes --]

Re: [9fans] Mirroring plan9 sources

[clueelf]

I just finished walking thru David's directions in the notes I found on 9legacy

http://9legacy.org/9legacy/doc/gce/notes

Unfortunately, it appears that GCP doesn't allow non-win/linux images.  Got this error when trying to create an image:

$ gcloud compute images create plan9 --source-uri gs://superbadmofo-plan9/plan9-gce.tar.gz
ERROR: (gcloud.compute.images.create) Could not fetch resource:
 - The tar archive is not a valid image.

I tried both the 9legacy-gce image and the stock plan9-gce image

Tony

On 3/7/2019 at 4:20 PM, "Skip Tavakkolian" <skip.tavakkolian@gmail.com> wrote:Plan 9 does run on AWS and GCP.  There are at least two existing images to start from. Richard Miller created an image for AWS and David du Colombier created one for GCP.  Check out 9legacy and this list's archive for the how-to's.
On Thu, Mar 7, 2019, 1:51 PM  <clueelf@tonymendoza.us> wrote:
Any thoughts on how to mirror plan9 sources?  I would be willing to pay for and setup a mirror, but finding servers spec’d to run plan9 in the US seems impossible.


Would setting up plan9port on a hosted Linux vm make sense as an alternative?  Anyone doing this?


Looking for thoughts, pointers or experiences in doing this.


If this has already been covered feel free to send a link to a doc or ml archive post.


Thanks!


Tony

Re: [9fans] Mirroring plan9 sources

[clueelf]

Thanks!  I will look into them.

Tony

On 3/7/2019 at 4:08 PM, "Lyndon Nerenberg" <lyndon@orthanc.ca> wrote:
>
>clueelf@tonymendoza.us writes:
>
>
>> or and setup a mirror, but finding servers spec'd to run plan9 in
>>  the US seems impossible.
>
>I have run 9front on VPSes at ARP Networks.  These days 9front
>should just work out of the box.  ARP's support staff have been
>very helpful tuning the underlying qemu/kvm settings for me when
>I have needed that, and they don't shy away from helping run
>"oddball" OSes like Plan 9.
>
>--lyndon

Re: [9fans] Mirroring plan9 sources

[David du Colombier]

> I tried both the 9legacy-gce image and the stock plan9-gce image

These images are old and I haven't tried them for a while.
You should have better luck building an image yourself using
the following script on Linux:

https://raw.githubusercontent.com/golang/build/master/env/plan9-386/make.bash

You'll have to remove the "buildlet" part, since this script has been
made to build the Plan 9 image running the Go builders.

--
David du Colombier

Re: [9fans] Mirroring plan9 sources

[clueelf]

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

Thanks David!I will check it out.

T

On March 8, 2019 at 9:15 AM, David du Colombier<0intro@gmail.com>wrote:
> > I tried both the 9legacy-gce image and the stock plan9-gce image
>
> These images are old and I haven't tried them for a while.
> You should have better luck building an image yourself using
> the following script on Linux:
>
> https://raw.githubusercontent.com/golang/build/master/env/plan9-386/make.bash
>
> You'll have to remove the "buildlet" part, since this script has been
> made to build the Plan 9 image running the Go builders.
>
> --
> David du Colombier
>
>

[-- Attachment #2: Type: text/html, Size: 842 bytes --]

Re: [9fans] Mirroring plan9 sources

[clueelf]

Just an update, as a test, I was able to get a GCE VM running using the default script you sent.  Here was the output:

tmendoza@pollux:~/Downloads/plan9$ gcloud compute instances get-serial-port-output plan9-test --zone us-central1-c
SeaBIOS (version 1.8.2-20190122_225043-google)
Total RAM Size = 0x000000006cc00000 = 1740 MiB
CPUs found: 1     Max CPUs supported: 1
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=20971520 = 10240 MiB
drive 0x000f2a20: PCHS=0/0/0 translation=lba LCHS=1024/255/63 s=20971520
Booting from Hard Disk 0...
pcirouting: BIOS workaround: PCI.0.1.3 at pin 1 link 96 irq 10 -> 9

no vga; serial console only
 disk loader

cpu0:  2301MHz GenuineIntel P6 (cpuid: AX 0x306F0 DX 0x1F8BFBFF)
ELCR: 0C00
497M memory: 497M kernel data, 0M user, 18M swap
found partition #S/sd01/data 0 20,971,520
disks: sd01
trying sd01....found 9pccpuf
.1178434...............................................................................................................................................+2414552.......................................................................................................................................................................................................................................................................................................+489820=4082806
entry: 0xf0100020

Plan 9
E820: 00000000 0009fc00 memory
E820: 0009fc00 000a0000 reserved
E820: 000f0000 00100000 reserved
E820: 00100000 6cbfd000 memory
E820: 6cbfd000 6cc00000 reserved
E820: fffbc000 100000000 reserved
cpu0:  2302MHz GenuineIntel P6 (cpuid: AX 0x306F0 DX 0x1F8BFBFF)
ELCR: 0C00
#l0: virtio: 1Gbps port 0xC040 irq 11: 42010a80000a
1740M memory: 256M kernel data, 1483M user, 2108M swap
/boot/usbd: /dev/usb: no hubs
/boot/usbd: /dev/usb: no hubs
boot: can't open /srv/usb: '/srv/usb' file does not exist
time...
fossil(#S/sd01/fossil)...version...aux/randfs: '/bin/aux/randfs' does not exist
downloading git
starting buildlet script
hget: Not found on server
usage: hget [-dhv] [-o outfile] [-p body] [-x netmtpt] [-r header] url
/tmp/buildlet: exec header invalid
syncing.../srv/fscons...prompt:
halting.../srv/fscons...
prompt:
done halting

Specify --start=2092 in the next get-serial-port-output invocation to get only the new output starting from here.

Now that I know it works, I will modify the script to build the server types I need and post those somewhere once done.

Thanks again David!

Tony

On 3/8/2019 at 9:16 AM, "David du Colombier" <0intro@gmail.com> wrote:
>
>> I tried both the 9legacy-gce image and the stock plan9-gce image
>
>These images are old and I haven't tried them for a while.
>You should have better luck building an image yourself using
>the following script on Linux:
>
>https://raw.githubusercontent.com/golang/build/master/env/plan9-
>386/make.bash
>
>You'll have to remove the "buildlet" part, since this script has
>been
>made to build the Plan 9 image running the Go builders.
>
>--
>David du Colombier