-
Notifications
You must be signed in to change notification settings - Fork 16
/
maninstall.expect
executable file
·154 lines (150 loc) · 3.75 KB
/
maninstall.expect
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
#!/usr/bin/expect -f
#
# This Expect script was generated by autoexpect on Wed Feb 3 18:49:12 2016
# Expect and autoexpect were both written by Don Libes, NIST.
#
# Note that autoexpect does not guarantee a working script. It
# necessarily has to guess about certain things. Two reasons a script
# might fail are:
#
# 1) timing - A surprising number of programs (rn, ksh, zsh, telnet,
# etc.) and devices discard or ignore keystrokes that arrive "too
# quickly" after prompts. If you find your new script hanging up at
# one spot, try adding a short sleep just before the previous send.
# Setting "force_conservative" to 1 (see below) makes Expect do this
# automatically - pausing briefly before sending each character. This
# pacifies every program I know of. The -c flag makes the script do
# this in the first place. The -C flag allows you to define a
# character to toggle this mode off and on.
set force_conservative 1 ;# set to 1 to force conservative mode even if
;# script wasn't run conservatively originally
if {$force_conservative} {
set send_slow {1 .1}
proc send {ignore arg} {
sleep .1
exp_send -s -- $arg
}
}
#
# 2) differing output - Some programs produce different output each time
# they run. The "date" command is an obvious example. Another is
# ftp, if it produces throughput statistics at the end of a file
# transfer. If this causes a problem, delete these patterns or replace
# them with wildcards. An alternative is to use the -p flag (for
# "prompt") which makes Expect only look for the last line of output
# (i.e., the prompt). The -P flag allows you to define a character to
# toggle this mode off and on.
#
# Read the man page for more info.
#
# -Don
set timeout -1
# set env(https_proxy) <set proxy here, if necessary, and uncomment>
spawn /usr/bin/python3 /usr/bin/ister_gui.py --exit-after
match_max 100000
expect -re ".*Clear Linux. OS Installer.*"
send -- "\r"
send -- "\t"
expect -re ".*Network Requirements.*"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\r"
expect -re ".*Choose Action.*"
send -- "\r"
# check < previous > button functionality
expect -re ".*Stability Enhancement Program.*"
send -- "\t"
send -- "\t"
send -- "\r"
send -- "\r"
expect -re ".*Stability Enhancement Program.*"
send -- "\t"
send -- "\r"
send -- "\r"
expect -re ".*Choose Installation Type.*"
# tab to manual
send -- "\t"
send -- "\r"
expect -re ".*Choose partitioning method.*"
# use default - not doing cgdisk testing with expect
send -- "\r"
expect -re ".*Choose target device.*"
send -- "\r"
expect -re ".*Warning.*"
# tab to Yes
send -- "\t"
send -- "\r"
expect -re ".*Append to kernel cmdline.*"
send -- "\t"
send -- "\r"
expect -re ".*Configuring Hostname.*"
# accept default
send -- "\r"
# Next
send -- "\r"
expect -re ".*User configuration.*"
# manually create a user
send -- "\r"
send -- "User\r"
send -- "Name\r"
# Username is now uname
send -- "\t"
send -- "UserPass\r"
send -- "UserPass\r"
# Add user to sudoers
send -- "\r"
send -- "\t"
send -- "\r"
expect -re ".*Bundle selector.*"
# editors
send -- "\r"
# tab to Next
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
# Next
send -- "\r"
expect -re ".*Network configuration.*"
send -- "\t"
# Static IP configuration
send -- "\r"
expect -re ".*Step 12 of 13.*"
# tab through options, don't actually set anything
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
send -- "\t"
# Previous
send -- "\r"
expect -re ".*Step 12 of 13.*"
send -- "\t"
send -- "\t"
# Use DHCP
send -- "\r"
expect -re ".*Attention.*"
send -- "\t"
# Yes
send -- "\r"
expect -re ".*Ok.*"
send -- "\r"
expect -re ".*will be rebooted.*"
send -- "\r"
expect eof