Browse Source

Plan 9 from Bell Labs 2003-06-06

David du Colombier 21 years ago
parent
commit
79877199fb
3 changed files with 77 additions and 43 deletions
  1. 1 1
      dist/replica/plan9.db
  2. 1 0
      dist/replica/plan9.log
  3. 75 42
      sys/src/9/bitsy/Booting101

+ 1 - 1
dist/replica/plan9.db

@@ -4970,7 +4970,7 @@ sys/src/9/alphapc/vgasavage.c - 664 sys sys 1015012788 29
 sys/src/9/alphapc/vgatvp3026.c - 664 sys sys 1015012788 30
 sys/src/9/alphapc/vgax.c - 664 sys sys 1015012788 24
 sys/src/9/bitsy - 20000000775 sys sys 1018721429 0
-sys/src/9/bitsy/Booting101 - 664 sys sys 1053341743 7306
+sys/src/9/bitsy/Booting101 - 664 sys sys 1054798506 8841
 sys/src/9/bitsy/bitsy - 664 sys sys 1043922351 450
 sys/src/9/bitsy/bitsyreset.s - 664 sys sys 1017695510 2352
 sys/src/9/bitsy/clock.c - 664 sys sys 1037028998 4835

+ 1 - 0
dist/replica/plan9.log

@@ -12037,3 +12037,4 @@
 1054391577 1 c sys/src/9/ip/ip.h - 664 sys sys 1054391400 16066
 1054479750 0 c sys/src/cmd/aux/vga/nvidia.c - 664 sys sys 1054479635 12043
 1054551764 0 c 386/bin/aux/vga - 775 sys sys 1054551530 300312
+1054800131 0 c sys/src/9/bitsy/Booting101 - 664 sys sys 1054798506 8841

+ 75 - 42
sys/src/9/bitsy/Booting101

@@ -7,20 +7,26 @@ get the Linux boot loader onto the bitsy (and to save away wince, if you so
 desire).  The Plan 9 machine is used to get the plan 9 kernel and a read only
 file system onto the bitsy.
 
-0) charge up the bitsy.
+0.  charge up the bitsy.
 
-1) go to
-ftp://ftp.handhelds.org/pub/linux/compaq/ipaq/stable/install.html Get
-the latest version of the Linux "osloader" and "bootldr" programs
+1.  go to
+	ftp://ftp.handhelds.org/pub/linux/compaq/ipaq/stable/install.html
+Get the latest version of the Linux "osloader" and "bootldr" programs
 (we have tried versions 1.3.0 and 0000-2.14.8, respectively; newest
- versions seem not to allow you to suspend your bitsy due to a bug
- which is probably ours).
+versions seem not to allow you to suspend your bitsy due to a bug
+which is probably ours).  You can find them all at
+www.collyer.net/who/geoff/9/bitsy/.
 
-2.  Use ActiveSync to copy osloader to the bitsy.
+2.  Use ActiveSync to copy osloader and bootldr to the bitsy.  Copy or
+rename the bootldr binary to "bootldr" on Windows, then copy it to the
+bitsy; trying to rename it on WinCE won't produce the right result.
+
+Steps 3 - 7 may work on a Pocket PC bitsy, but see Steps 3a - 7a
+if they don't or if you have a Pocket PC 2002 bitsy.
 
 3.  Run osloader by clicking on it under the WinCE File Explorer
 
-(4).  Use osloader to save your WinCE flash away.  This takes a while,
+4.  Use osloader to save your WinCE flash away.  This takes a while,
 as it's 16MB over a 115,200 baud line.
 
 5.  Select "Run" from the osloader menu.  Ignore "Run from RAM"; it's
@@ -37,18 +43,35 @@ command "help" lists the OS loader's commands.
 7.  Now you need to download the BOOT loader program into flash (right
 now, you're only running the OS loader program out of RAM; rebooting
 will get you back to WinCE).  In the con window, "load bootldr" to the
-bitsy.  It will indicate that it's starting an xmodem download.  
-Under con, type "Ctrl-\" to get a ">>>" prompt.  At this prompt, you 
+bitsy.  It will indicate that it's starting an xmodem download.
+Under con, type "Ctrl-\" to get a ">>>" prompt.  At this prompt, you
 want to run Plan 9's xms program to pipe the bootldr program to the
 bitsy.  For example, to download /tmp/bootldr, type "!xms /tmp/bootldr".
 
 If this step works successfully, the OS loader will print out some sort
 of OK checksum message.
 
+If you have a Pocket PC 2002 or steps 3 - 7 above didn't work for you,
+try 3a - 7a.
+
+3a.  Copy BootBlaster (also) to the bitsy via ActiveSync.
+
+4a.  Save your flash by running osloader and selecting "Flash->Save to
+File".  As it produces 4MB files, use ActiveSync to copy them off the
+bitsy.
+
+5a.  Move the bitsy and its cable over to a Plan 9 machine and connect
+using "con -b 115200 /dev/eia[01]" to talk to the console.
+
+6a.  Run BootBlaster by clicking on it under the WinCE File Explorer.
+
+7a.  Select "Program"; it should copy "bootldr" into your flash in
+about 15 seconds.
+
 8.  Reboot your bitsy (either cycle the power or use the reset
 switch).  The new boot loader runs out of Flash.  You'll get the linux
 penguin splash screen and a bunch of options triggered by buttons.
-Pick the one that gets you to the boot loader. 
+Pick the one that gets you to the boot loader.
 
 9.  Make the partitions you need in the bitsy's flash, type, using
 the con program:
@@ -92,7 +115,7 @@ These are the partitions as shown by partition show:
 
 After each line you'll get a message like `defining partition: params'.
 Different versions of the bootloader predefine different partitions.
-The bootldr partitions is usually predefined, so you don't have to remake
+The bootldr partition is usually predefined, so you don't have to remake
 that.  You may have to delete one or two partitions.  The command is
 	partition delete <name>
 Make sure the partition layout is as given above; some of this knowledge is
@@ -105,22 +128,25 @@ the necessary arm binaries installed in /arm and examine the file
 paqfiles/mfs to see what you need to change for connecting to your local
 file servers.
 
-11. Now you can type "load kernel".  The boot loader will prompt for
+11.  Now you can type "load kernel".  The boot loader will prompt for
 another xmodem download.  Again escape using "Ctrl-\", then use
-"!xms /sys/src/9/bitsy/9bitsy".
+"!xms /sys/src/9/bitsy/9bitsy" (or "!xms /arm/9bitsy" if you've already
+installed it).
 
-12. Download the ramdisk, using "load ramdisk" and
-"!xms /sys/src/9/bitsy/paqdisk", similarly to 10, above. 
+12.  Download the ramdisk, using "load ramdisk" and
+"!xms /sys/src/9/bitsy/paqdisk" (or "!xms /arm/paqdisk" if you've already
+installed it), similarly to 10, above.
 
 13. Type `boot' or `boot flash' depending on your version of the boot loader.
 If you need the latter, you may want to
+
 	set boot_type flash
-and
 	params save
+
 to make boot flash the default.
 
 You'll get a Dutch flag (or a French one, if you hold the iPaq the wrong way),
-then the boot screen will say:
+then the boot screen will say, on the serial port, thus in your con window:
 
 	root is from [paq]:
 
@@ -133,13 +159,16 @@ machine in your hand the way you'ld normally use it or the calibration
 could be off since there is depth to the glass in the screen.
 
 15.  You'll get a new screen with a single line at the top and a
-keyboard/scribble area at the bottom.  This is a simple one file editor.
-This file is similar to plan9.ini on PC's.  There may be garbage on the
-top line.  If there is, delete the garbage letters.  You should be left with
-a single line containing (with different numbers)
+keyboard/scribble area at the bottom.  This is a simple one file
+editor.  This file is similar to plan9.ini on PC's.  There may be
+garbage on the top line.  If there is, delete the garbage letters.
+(Be careful here: the backspace and delete keys are adjacent on the
+wee keyboard and it's much too easy to hit delete instead of
+backspace, especially if you haven't calibrated the screen dead-on.)
+You should be left with a single line containing (with different
+numbers):
 	calibrate='-16374 22919 251 -24'
-You need to enter a few more things, including,
-but not limited to:
+You need to enter a few more things, including, but not limited to:
 
 	user=<user-name>
 	wvkey1=<key string>
@@ -148,35 +177,33 @@ but not limited to:
 	wvtxkey=<key string>
 	wvessid=<wavelan name>
 	auth=<ip address>
+	cpu=<ip address>
+	proxy=<ip address>
 	fs=<ip address>
 
-Your best bet is to copy these off a working bitsy.  When you're done,
-hit the "ESC" key on the simulated keyboard, or the side button near
-the word iPAQ on the bitsy.  The system will now come
-up as you.  However, you'll get a message about the flash file system
-being corrupted, because we haven't yet initialized it.
+Your best bet is to copy these off a working bitsy.  wv*key* only
+matter if your wireless network is encrypted.  When roaming the world,
+omit wv*.  When you're done, hit the "ESC" key on the simulated
+keyboard, or the side button near the word iPAQ on the bitsy.  The
+system will now come up as you.  However, you'll get a message about
+the flash file system being corrupted, because we haven't yet
+initialized it.
 
 16. To set up the file systems, sweep a window and give the following
 sequence of commands.
 
 	# aux/mkflashfs /dev/flash/fs
-
 	# aux/flashfs
 
 aux/flashfs created a Plan 9 server in /srv/brzr, which we can use to set up
-default directories. 
+default directories.
 
 	# mount -c /srv/brzr /n/brzr
-
 	# cd /n/brzr
-
 	# mkdir n usr
-
 	# mkdir n/fs n/emelie n/choline n/nslocum
-
 	# mkdir usr/yourname usr/yourfriend
 
-
 17. For safety, reboot the system:
 
 	# reboot
@@ -187,20 +214,26 @@ editor, and sweep yourself a new rio window.
 Before you can connect to other machines, you need a way to enter
 passwords and keys into factotum.  The easiest way to do this is to
 run
-	# auth/fgui
-in the window you just made.  The window will disappear (fgui
-spends most of its time hidden), so sweep a new window and run
-the command
+
+	# auth/fgui &
+
+in the window you just made.  The window will disappear (fgui spends
+most of its time hidden), so sweep a new window and run the command
 
 	# mfs
 
 to connect to file servers.  You will probably need to modify mfs to
-work in your environment (see point 10).
+work in your environment (see point 10), though you can supply many
+of the variables it needs in step 15, and doing
+
+	# import $cpu /net
+
+before running mfs can go a long ways.
 
 19.  When you're all set with a working wavelan, you can download new
 kernels more quickly using
 
-	# bitsyload k 
+	# bitsyload k
 
 and new paqdisks using