1 |
32 |
wfjm |
# $Id: README_211bsd_rlset.txt 688 2015-06-05 13:15:10Z mueller $
|
2 |
29 |
wfjm |
|
3 |
|
|
Notes on oskit: 2.11BSD system on RL02 volumes
|
4 |
|
|
|
5 |
|
|
Table of content:
|
6 |
|
|
|
7 |
|
|
1. General remarks
|
8 |
|
|
2. Installation
|
9 |
|
|
3. Usage
|
10 |
|
|
|
11 |
|
|
1. General remarks ---------------------------------------------------
|
12 |
|
|
|
13 |
|
|
See notes on
|
14 |
|
|
|
15 |
|
|
1. I/O emulation setup
|
16 |
|
|
2. FPGA Board setup
|
17 |
|
|
3. Rlink and Backend Server setup
|
18 |
|
|
4. Legal terms
|
19 |
|
|
|
20 |
|
|
in $RETROBASE/doc/w11a_os_guide.txt
|
21 |
|
|
|
22 |
|
|
2. Installation ------------------------------------------------------
|
23 |
|
|
|
24 |
|
|
- A disk set is available from
|
25 |
|
|
http://www.retro11.de/data/oc_w11/oskits/211bsd_rlset.tgz
|
26 |
|
|
Download, unpack and copy the disk images (*.dsk), e.g.
|
27 |
|
|
|
28 |
|
|
cd $RETROBASE/tools/oskit/211bsd_rl/
|
29 |
|
|
wget http://www.retro11.de/data/oc_w11/oskits/211bsd_rlset.tgz
|
30 |
|
|
tar -xzf 211bsd_rlset.tgz
|
31 |
|
|
|
32 |
|
|
3. Usage -------------------------------------------------------------
|
33 |
|
|
|
34 |
|
|
- Start backend server and boot system (see section 3 in w11a_os_guide.txt)
|
35 |
|
|
boot script: 211bsd_rl_boot.tcl
|
36 |
30 |
wfjm |
example: ti_w11 @211bsd_rl_boot.tcl
|
37 |
|
|
where is the proper option set for the board.
|
38 |
29 |
wfjm |
|
39 |
|
|
- Hit in the xterm window to connnect to backend server.
|
40 |
|
|
The boot dialog in the console xterm window will look like
|
41 |
|
|
(required input is in {..}, with {} denoting a carriage return:
|
42 |
|
|
|
43 |
|
|
70Boot from rl(0,0,0) at 0174400
|
44 |
|
|
: {}
|
45 |
|
|
: rl(0,0,0)unix
|
46 |
|
|
Boot: bootdev=03400 bootcsr=0174400
|
47 |
|
|
|
48 |
|
|
2.11 BSD UNIX #1: Thu Jan 1 22:05:02 PST 2009
|
49 |
|
|
root@curly.2bsd.com:/usr/src/sys/RETRONFPRL
|
50 |
|
|
|
51 |
|
|
phys mem = 3932160
|
52 |
|
|
avail mem = 3577344
|
53 |
|
|
user mem = 307200
|
54 |
|
|
|
55 |
|
|
January 1 22:44:48 init: configure system
|
56 |
|
|
|
57 |
|
|
dz ? csr 160100 vector 310 skipped: No CSR.
|
58 |
|
|
lp 0 csr 177514 vector 200 attached
|
59 |
30 |
wfjm |
rk 0 csr 177400 vector 220 attached
|
60 |
29 |
wfjm |
rl 0 csr 174400 vector 160 attached
|
61 |
31 |
wfjm |
tm 0 csr 172520 vector 224 attached
|
62 |
30 |
wfjm |
xp 0 csr 176700 vector 254 attached
|
63 |
29 |
wfjm |
cn 1 csr 176500 vector 300 attached
|
64 |
|
|
erase, kill ^U, intr ^C
|
65 |
|
|
|
66 |
|
|
In first '#' prompt the system is in single-user mode. Just enter a ^D
|
67 |
|
|
to continue the system startup to multi-user mode:
|
68 |
|
|
|
69 |
|
|
#^D
|
70 |
|
|
|
71 |
|
|
Fast boot ... skipping disk checks
|
72 |
|
|
checking quotas: done.
|
73 |
|
|
Assuming non-networking system ...
|
74 |
|
|
preserving editor files
|
75 |
|
|
clearing /tmp
|
76 |
|
|
standard daemons: update cron accounting.
|
77 |
|
|
January 1 22:46:13 acctd[51]: open(/usr/adm/acct,O_WRONLY|O_APPEND): 2
|
78 |
|
|
starting lpd
|
79 |
|
|
starting local daemons:Thu Jan 1 22:46:13 PST 2009
|
80 |
|
|
January 1 22:46:13 init: kernel security level changed from 0 to 1
|
81 |
|
|
January 1 22:46:15 getty: /dev/tty01: Device not configured
|
82 |
|
|
January 1 22:46:15 getty: /dev/tty00: Device not configured
|
83 |
|
|
January 1 22:46:15 getty: /dev/tty02: Device not configured
|
84 |
|
|
January 1 22:46:15 getty: /dev/tty03: Device not configured
|
85 |
|
|
|
86 |
|
|
2.11 BSD UNIX (curly.2bsd.com) (console)
|
87 |
|
|
|
88 |
|
|
login:
|
89 |
|
|
|
90 |
|
|
The login prompt is sometimes mangled with the 'Device not configured'
|
91 |
|
|
system messages, if its not visible just hit to get a fresh one.
|
92 |
|
|
|
93 |
|
|
login: {root}
|
94 |
|
|
erase, kill ^U, intr ^C
|
95 |
|
|
|
96 |
|
|
Now the system is in multi-user mode, daemons runnng. You can explore
|
97 |
|
|
the system, e.g. with a 'pstat -T' or a 'mount' command. The second
|
98 |
|
|
xterm can be activated too, it will connect to a second emulated DL11.
|
99 |
|
|
At the end is important to shutdown properly with a 'halt':
|
100 |
|
|
|
101 |
|
|
# {pstat -T}
|
102 |
|
|
7/186 files
|
103 |
|
|
40/208 inodes
|
104 |
|
|
11/150 processes
|
105 |
|
|
6/ 46 texts active, 31 used
|
106 |
|
|
2/135 swapmap entries, 420 kB used, 2139 kB free, 2133 kB max
|
107 |
|
|
34/150 coremap entries, 2906 kB free, 2818 kB max
|
108 |
|
|
1/ 10 ub_map entries, 10 free, 10 max
|
109 |
|
|
# {mount}
|
110 |
|
|
/dev/rl0a on /
|
111 |
|
|
/dev/rl1h on /usr
|
112 |
|
|
# {halt}
|
113 |
|
|
syncing disks... done
|
114 |
|
|
halting
|
115 |
|
|
|
116 |
|
|
While the system was running the server process display the
|
117 |
|
|
cpumon>
|
118 |
|
|
prompt. When the w11 has halted after 211bsd shutdown a message like
|
119 |
|
|
|
120 |
|
|
CPU down attention
|
121 |
|
|
Processor registers and status:
|
122 |
|
|
PS: 030350 cm,pm=k,u s,p,t=0,7,0 NZVC=1000 rust: 01 HALTed
|
123 |
|
|
R0: 177560 R1: 161322 R2: 053770 R3: 000010
|
124 |
|
|
R4: 003400 R5: 147510 SP: 147466 PC: 000014
|
125 |
|
|
|
126 |
|
|
will be visible. Now the server process can be stopped with ^D.
|