-
Notifications
You must be signed in to change notification settings - Fork 16
/
Copy pathfaq.html
556 lines (494 loc) · 31.8 KB
/
faq.html
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
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
<!DOCTYPE html>
<!--[if lt IE 7]> <html class="ie ie6 lt-ie9 lt-ie8 lt-ie7" lang="en"> <![endif]-->
<!--[if IE 7]> <html class="ie ie7 lt-ie9 lt-ie8" lang="en"> <![endif]-->
<!--[if IE 8]> <html class="ie ie8 lt-ie9" lang="en"> <![endif]-->
<!--[if IE 9]> <html class="ie ie9" lang="en"> <![endif]-->
<!--[if !IE]><!-->
<html lang="en" class="no-ie">
<!--<![endif]-->
<!-- Mirrored from themicon.co/theme/beadmin/ by HTTrack Website Copier/3.x [XR&CO'2014], Fri, 29 Jan 2016 16:44:20 GMT -->
<head>
<!-- Meta-->
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=0">
<meta name="description" content="">
<meta name="keywords" content="">
<meta name="author" content="">
<title>FAQ</title>
<!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
<!--[if lt IE 9]><script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script><script src="https://oss.maxcdn.com/libs/respond.js/1.4.2/respond.min.js"></script><![endif]-->
<!-- Bootstrap CSS-->
<link rel="stylesheet" href="app/css/bootstrap.css">
<!-- Vendor CSS-->
<link rel="stylesheet" href="vendor/fontawesome/css/font-awesome.min.css">
<link rel="stylesheet" href="vendor/animo/animate%2banimo.css">
<link rel="stylesheet" href="vendor/csspinner/csspinner.min.css">
<link rel="shortcut icon" type="image/png" href="img/favicon.jpg" />
<!-- START Page Custom CSS-->
<!-- END Page Custom CSS-->
<!-- App CSS-->
<link rel="stylesheet" href="app/css/app.css">
<!-- Modernizr JS Script-->
<script src="vendor/modernizr/modernizr.js" type="application/javascript"></script>
<!-- FastClick for mobiles-->
<script src="vendor/fastclick/fastclick.js" type="application/javascript"></script>
</head>
<body>
<!-- START Main wrapper-->
<div class="wrapper">
<!-- START Top Navbar-->
<nav role="navigation" class="navbar navbar-default navbar-top navbar-fixed-top">
<!-- START navbar header-->
<div class="navbar-header">
<a href="#" class="navbar-brand">
<div>
<h3>eXpOS<span style="color:#14ddb3">NITC<span></h3>
</div>
</a>
</div>
<!-- END navbar header-->
<!-- START Nav wrapper-->
<div class="nav-wrapper" style="background:black">
<!-- START Left navbar-->
<ul class="nav navbar-nav">
<li>
<!-- Button used to collapse the left sidebar. Only visible on tablet and desktops-->
<!--a href="#" data-toggle-state="aside-collapsed" class="hidden-xs">
<em class="fa fa-navicon"></em>
</a>
<!-- Button to show/hide the sidebar on mobile. Visible on mobile only.-->
<a href="#" data-toggle-state="aside-toggled" class="visible-xs">
<em class="fa fa-navicon"></em>
</a>
</li>
<li>
<h3 class="pull-right" style="color:white"> FAQ : Frequently Asked Questions</h3>
</li>
</ul>
<!-- END Left navbar-->
</div>
<!-- END Nav wrapper-->
</nav>
<!-- END Top Navbar-->
<!-- START aside-->
<aside class="aside">
<!-- START Sidebar (left)-->
<nav class="sidebar">
<ul class="nav">
<!-- START Menu-->
<li id="home">
<a href="index.html" title="Home" data-toggle="" class="no-submenu">
<em class="fa fa-home"></em>
<span class="item-text">Home</span>
</a>
</li>
<li>
<a href="documentation.html" title="Documentation" data-toggle="" class="no-submenu">
<em class="fa fa-files-o"></em>
<span class="item-text">Documentation</span>
</a>
</li>
<li>
<a href="Roadmap.html" target="_blank" title="Roadmap" data-toggle="" class="no-submenu">
<em class="fa fa-road"></em>
<span class="item-text">Roadmap</span>
</a>
</li>
<!-- <li>
<em class="fa fa-download"></em>
<span class="item-text">Downloads</span>
</a> </li>-->
<li class="active">
<a href="faq.html" title="FAQ" data-toggle="" class="no-submenu">
<em class="fa fa-question"></em>
<span class="item-text">FAQ</span>
</a>
</li>
<li>
<a href="googlegroup.html" title="googlegroup" data-toggle="" class="no-submenu">
<em class="fa fa-link"></em>
<span class="item-text">Google Group</span>
</a>
</li>
<li>
<a href="https://exposnitc.github.io/user-contrib/" target="_blank" title="user-contrib" data-toggle=""
class="no-submenu">
<em class="fa fa-link"></em>
<span class="item-text">User Contributions</span>
</a>
</li>
<li>
<a href="feedback.html" title="Feedback" data-toggle="" class="no-submenu">
<em class="fa fa-comments"></em>
<span class="item-text">Student Feedback</span>
</a>
</li>
<li>
<a href="About_us.html" title="About Us" data-toggle="" class="no-submenu">
<em class="fa fa-group"></em>
<span class="item-text">About Us</span>
</a>
</li>
<!-- <li class="nav-heading">More elements</li>
<li>
<a href="./reports.html" title="Reports" data-toggle="" class="no-submenu">
<em class="fa fa-file-pdf-o"></em>
<span class="item-text">Project Reports</span>
</a>
</li>
</li>-->
<li>
<a href="http://xosnitc.github.io" title="Read about XOS" class=" no-submenu" data-toggle="">
<em class="fa fa-link"></em>
<span class="item-text">Read about XOS</span>
</a>
</li>
<!-- END Menu-->
</ul>
<span style="position: absolute; bottom: 40px;color:white;">National Institute of Technology, Calicut</span>
<a style="position: absolute; bottom: 2px; right: 2px" rel="license" href="http://creativecommons.org/licenses/by-nc/4.0/"><img
alt="Creative Commons License" style="border-width:0" src="./img/creativecommons.png" /></a>
</nav>
<!-- END Sidebar (left)-->
</aside>
<!-- END aside-->
<!-- START Main section-->
<section id="faq" style="text-align:justify;font-size:15px">
<!-- START Page content-->
<div class="content-wrapper">
<div class="row">
<!-- START dashboard main content-->
<div class="col-lg-12">
<!-- START widget-->
<br />
<p>This FAQ is about the educational package involving the eXpOS operating system and its supporting tools
– the XSM machine simulator, the xfs-interface tool and the SPL and ExpL programming languages,
collectively referred to as the "eXpOS package". </p>
<br />
<ul class="list-group">
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse1"><b>1. What is eXpOS? What is its purpose?</b></a>
<div id="collapse1" class="panel-collapse collapse">
<p>eXpOS stands for eXperimental Operating System. The <a href="os_spec.html" target="_blank">eXpOS
specification</a> describes a very simple multi-user multi-tasking operating system. </p>
<p>eXpOS is not intended to be used as a practical operating system. It is designed with the
following intentions:
<ol>
<li>To have a multi-tasking OS specification that can be comprehended by a junior undergraduate
student in computer science who is undergoing a first course in Operating System such that
he/she will be able to implement the OS in two or three months. This educational package comes
with enough guidance and support tools as well as documentation to allow the student to achieve
this goal without the supervision of a specialist teacher.</li>
<li>The student will write the complete code for the OS from scratch. He/She will not be building
the OS on top of a given code base. The only programming support provided will be a compiler
for a programming language (called SPL) in which the OS kernel will be written. </li>
</ol>
</p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse2"><b>2. Who will benefit by implementing eXpOS?</b></a>
<div id="collapse2" class="panel-collapse collapse">
<p>If you are a non-expert in computer science – like an undergraduate student or some non-specialist
systems enthusiast – and you have a basic understanding of programming, and computer organization,
implementing eXpOS will help you to get a feel of some of the core ideas involved in implementing a
multi-tasking operating system on a single processor. You will learn how to:</p>
<ol>
<li>Initally load the operating system from secondary storage to memory – <b>Bootstrapping</b>.
</li>
<li>Manage several processess in memory simultaneously – <b>Process Management</b>. </li>
<li>Handle allocation and de-allocation of memory to processes – <b>Memory Management</b> (includes
virtual memory management). </li>
<li>Manage organization of data and program files in secondary storage – <b>File Management</b>.</li>
<li>Implement a mechanism to allow multiple processes to share files/memory – <b>Resource Sharing</b>.</li>
<li>Realize primitives that help application programs to avoid inconsistency when resources are
shared by several processes executing concurrently – <b>Process Sychronization</b>.</li>
<li>Handling multiple users with different privileges over resources shared among them – <b>Multi-user
Capability.</b></li>
</ol><br />
<p>The experiment is akin to guiding a third year aerospace engineering student to build a small
unmanned flight in two months. (The flight will not be usable outside the laboratory!)</p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse3"><b>3. What are the OS concepts that eXpOS will help me to
comprehend better than – say just learning from a text book?</b></a>
<div id="collapse3" class="panel-collapse collapse">
<p>Please see FAQ 2. </p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse3a"><b>4. What are the prerequisites for doing the eXpOS
project?</b></a>
<div id="collapse3a" class="panel-collapse collapse">
<p>The project presumes that the student has undergone a basic sophomore course in computer
organization and data structures and has either completed or is currently undergoing a theory
course in operating systems. The project does not require the student
to be familar with the principles of compilers. It is not expected that the student has a high
level of proficiency in programming or computer hardware. The required background on paging
hardware, interrupts, runtime stack of application programs etc. are provided as reading material
at appropriate places in the project roadmap. </p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse4"><b>5. Who must not be spending time on eXpOS?</b></a>
<div id="collapse4" class="panel-collapse collapse">
<p>People who want to learn about operating systems, but who belong to the following category are not
advised to proceed with eXpOS:</p>
<ol>
<li>You are a confident programmer comfortable with reading and understanding professionally
written code – like the source code of linux. In this case, more sophisticated packages like <a
href="http://minix3.org/">Minix</a> allow you to do real hard stuff. However, this is not for
novices. </li>
<li>You are not an expert; you want to try out the things listed in FAQ 2, but you do not want to
do dirty work at a low level. (Although you can avoid assembly language programming in the eXpOS
project, you still will have to get into quite a bit of “low level” architectural details). We
suggest you to look for alternatives like <a href="https://en.wikipedia.org/wiki/Not_Another_Completely_Heuristic_Operating_System"
target="_blank">NACHOS</a>. </li>
</ol>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse5"><b>6. Can eXpOS be actually be used in a real application?</b></a>
<div id="collapse5" class="panel-collapse collapse">
<p>Please see FAQ 2. </p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse6"><b>7. What are the important OS concepts I miss out when
working with eXpOS?</b></a>
<div id="collapse6" class="panel-collapse collapse">
<p>What you learn is very little compared to what is needed to become an OS expert. So, listing out
everything is impossible. But here are some important misses: </p>
<ol>
<li>The XSM machine allows you to store a character string in a memory word. No real machine
architecture permits you to do such stuff. This is made possible just because XSM is a software
simulated. However, XSM makes your data manipulation job much simpler without getting bogged down
by details of data formatting. It is in principle possible to implement eXpOS on “more real”
machines like <a href="http://en.wikipedia.org/wiki/MIPS_instruction_set" target="_blank">MIPS</a>.
However, this would involve considerably more time and effort. </li>
<li>The project involves very little work involving input-ouput, device interfacing, security or
networking. Moreover the file system and multi-user support are very primitive. The methods
studied won't scale up when there is <a href="https://en.wikipedia.org/wiki/Computer_multitasking#Preemptive_multitasking"
target="_blank"> pre-emptive multitasking </a>. </li>
</ol>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse7"><b>8. What are the system requirements for working on the
eXpOS package?</b></a>
<div id="collapse7" class="panel-collapse collapse">
<p>We expect you to have a Linux/Unix Machine with Lex/Flex and Yacc/Bison software packages
installed. (For Flex/Bison installation on your Linux system, see <a href="http://en.kioskea.net/faq/30635-how-to-install-flex-and-bison-under-ubuntu"
target="_blank">link</a>). Once you have these, you can download the eXpOS package by following
instructions at <a href="./support_tools-files/setting-up.html" target="_blank"> Setting Up</a>.</p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse8"><b>9. What are the contents of the eXpOS package?</b></a>
<div id="collapse8" class="panel-collapse collapse">
<p>The eXpOS package available <a href="./support_tools-files/setting-up.html" target="_blank">here</a>
comes with the following: </p>
<ol>
<li>A simulator for the <a href="arch_spec.html" target="_blank">Experimental String Machine (XSM)</a>
on which you implement eXpOS. The machine consists of a CPU, Memory and a disk and a small
Input-Ouput subsystem.</li>
<li>A compiler (into the XSM machine) for the <a href="support_tools-files/spl.html" target="_blank">System
Programmer's Language (SPL)</a> using which you will be writing all your code for implementing
eXpOS. SPL is a simple programming language which essentially is an extended assembler for the
XSM machine, specifically designed for the eXpOS package.</li>
<li>A compiler (into the XSM machine) for the <a href="support_tools-files/expl.html" target="_blank">Experimental
String Language (ExpL)</a>. This language is used for writing application programs that can run
on top of eXpOS. You will be using this language for writing some of the user level programs of
the OS including the shell. Test programs that are used to test your OS will also be written in
ExpL.</li>
<li>An interface tool called <a href="support_tools-files/xfs-interface.html" target="_blank">XFS-interface</a>
that allows you to transfer data files and executable programs from your Unix/Linux system into
the hard disk of the XSM machine.</li>
<li>You also download the source code of all the above tools and their formal specification
documents, the sample test programs testing your OS, some help etc. </li>
</ol>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse9"><b>10. I have downloaded the eXpOS package. How can I get
started with the work? </b></a>
<div id="collapse9" class="panel-collapse collapse">
<p>The best way is to follow the eXpOS roadmap. It is a journey taken one simple step at a time. You
will be provided with links to learn the concepts on a “learn when needed” way. Just go ahead
following this <a href="Roadmap.html" target="_blank">link</a>.</p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse10"><b>11. What differenciates eXpOS from other educational
packages like NACHOS?</b></a>
<div id="collapse10" class="panel-collapse collapse">
<p>It is difficult to answer this question for all similar packages available elsewhere, but here is
a comparison with NACHOS. </p>
<p>NACHOS learning system asks you to implement OS software that allows application programs in the
noff executable format, running on a the software simulation of a MIPS machine, to invoke system
calls. However, the OS code you write really doesn't run on the MIPS machine! Your code is actually
C code running on your Linux/Unix machine. When an application program invokes an OS system call,
the MIPS simulator transfers control to a corresponding “stub” function in the simulating
environment. You must write C code in the stub to do “whatever is expected from the OS” to satisfy
the calling application program invoking the system call. Since the MIPS machine is simulated, your
code has access to its memory, registers etc. Thus you can implement the system call, put return
values in appropriate memory locations on the simulated MIPS machine and transfer control back to
the calling program. </p>
<p>In eXpOS, the OS and the application programs run in the same machine as is the case in real
systems. The compromise made in achieving this goal was to make the machine “unreal” and the OS
simple enough so that additional complexity is manageable for a short term project. </p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse11"><b>12. What is the difference between eXpOS and XOS?</b></a>
<div id="collapse11" class="panel-collapse collapse">
<p><a href="http://xosnitc.github.io/" target="_blank">XOS</a> is an earlier version of this project.
XOS did not support blocking system calls.</p>
<p> This means that a process will never do a context switch while it is running in the kernel mode.
However eXpOS, system calls may block in the kernel mode and other processes could be scheduled.
The version of XSM provided with eXpOS has the necessary hardware support for doing this.</p>
<p> The addition of this single feature makes the eXpOS substantially more complex than XOS. This is
because a blocked process might have made partial updates to some OS data structures before
blocking and a newly scheduled process, while executing in the kernel mode, must be careful not to
modify these data structures and leave the OS in an inconsistent state. </p>
<p> Apart from the above feature, eXpOS adds support for semaphores, shared memory, file locking etc.
There is also limited multi-user support. However, the additional complexity introduced by these
features is minor. </p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse12"><b>13. How do I write OS code and load the OS in the eXpOS
system?</b></a>
<div id="collapse12" class="panel-collapse collapse">
<p>You have to write your OS code from your Linux/Unix system in a custom programming language called
SPL that comes with the eXpOS package, compile the code and install the target code into the hard
disk of the XSM machine. The xfs-interface tool allows you to do this pre-loading. Your OS code
must include set up code that will be executed when the system is started. This code must load the
rest of the OS into memory during bootstrap. </p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse13"><b>14. How do I write application programs that run on
eXpOS?</b></a>
<div id="collapse13" class="panel-collapse collapse">
<p>Application programs must be compiled in the Linux/Unix environment outside and pre-loaded into
the XSM machine's disk. The ExpL language allows applications to be written and compiled into the
eXpOS executable format called the <a href="abi.html#xexe" target="_blank"> XEXE </a> format.</p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse14"><b>15. What is meant by user mode and kernel mode?</b></a>
<div id="collapse14" class="panel-collapse collapse">
<p>In a multitasking OS like Linux, there are two types of programs running. Firstly, there are
application programs that users write. These are called "user mode programs". Secondly, there are
"kernel mode programs" which constitute the OS code. These routines implement the system call
interface for application programs and other OS functions like process, memory, file and device
management etc. </p>
<p>User mode programs can execute only a restricted instruction set and has access only to a limited
memory (called the virtual address space). These programs must invoke OS system calls to do tasks
which involve capacity beyond their limited instruction set. Kernel mode programs on the other hand
have full access to the machine instruction set. </p>
<p>Any machine supporting eXpOS needs to recognize and support two modes of program execution. The OS
must be designed such that the machine switches to kernel mode when a user mode program invokes a
system call and goes back to user mode when the system call returns. This requires architecture
support. XSM machine is equipped with the necessary hardware support. </p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse15"><b>16. Why do you need two programming languages in the
eXpOS package – the SPL and ExpL?</b></a>
<div id="collapse15" class="panel-collapse collapse">
<p>We need separate programming systems for writing user mode programs and kernel mode programs
because these languages serve different purposes. The high level language - ExpL provided with the
package can be used for writing application programs that run on top of the operating system.
However, ExpL does not support low level programming necessary to write the OS. The SPL language
(which is essentially an enriched XSM assembly language) must be used to write the OS modules.</p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse16"><b>17. What is eXpOS Library? </b></a>
<div id="collapse16" class="panel-collapse collapse">
<p>The ExpOS library is a piece of code that provides a generic interface for application programs to
access OS services like system calls and dynamic memory management routines.</p>
<p>ExpL permits applications to invoke OS routines only through the library interface. The compiler
simply translates the library call to a low level library call. However, ExpL compiler will not
attach the library to the application at compile time. The OS loader must attach the library to the
application at run time. </p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse17"><b>18. What is XFS interface? </b></a>
<div id="collapse17" class="panel-collapse collapse">
<p>XFS interface is a tool that permits you to transfer programs and data files between your host
system and the XSM machine's simulated hard disk. The tool is capable of handling various eXpOS
file types (like OS modules, application programs, data files, library etc.) and store them in the
XSM disk, updating the disk data structures appropriately. </p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse18"><b>19. My friend has implemented eXpOS after downloading
the package and following the roadmap. I want to write a program and test his implementation. How
to do it?</b></a>
<div id="collapse18" class="panel-collapse collapse">
<p>You must write your code in ExpL language in your Unix/Linux machine, compile it using the ExpL
compiler that comes with the eXpOS package and load the target executable file into the XSM
machine's disk using the xfs-interface tool. Now start the machine (assuming that your friend has
already written his OS routines in SPL, compiled it using the SPL compiler and loaded it into the
disk) so that her OS boots up and runs the shell program. From the shell, you will be able to type
in the name of your executable program and execute it, just like in bash. </p>
</div>
</li>
<li class="list-group-item">
<a data-toggle="collapse" href="#collapse19"><b>20. I am a teacher and wants to use eXpOS for
laboratory instruction. How should I proceed?</b></a>
<div id="collapse19" class="panel-collapse collapse">
<p>You are welcome use eXpOS. You may also fork the project on GitHub and customize the project to
your own needs subject to the <a href="http://creativecommons.org/licenses/by-nc/4.0/">Creative
Commons</a> license conditions.</p>
<p>Pro Tip: Suppose your institution has the name ABC University, to host your project on GitHub as
exposabc.github.io, create a GitHub account by the name eXpOSABC, fork this project, rename your
repository to exposabc.github.io, and host your website using <a href="https://pages.github.com/">GitHub
Pages</a></p>
</div>
</li>
</ul>
</div>
</div>
</div>
</section>
<!-- END dashboard main content-->
</div>
</div>
<!-- END Page content-->
</section>
<!-- END Main section-->
</div>
<!-- END Main wrapper-->
<!-- START Scripts-->
<!-- Main vendor Scripts-->
<script src="vendor/jquery/jquery.min.js"></script>
<script src="vendor/bootstrap/js/bootstrap.min.js"></script>
<!-- Plugins-->
<script src="vendor/chosen/chosen.jquery.min.js"></script>
<script src="vendor/slider/js/bootstrap-slider.js"></script>
<script src="vendor/filestyle/bootstrap-filestyle.min.js"></script>
<!-- Animo-->
<script src="vendor/animo/animo.min.js"></script>
<!-- Sparklines-->
<script src="vendor/sparklines/jquery.sparkline.min.js"></script>
<!-- Slimscroll-->
<script src="vendor/slimscroll/jquery.slimscroll.min.js"></script>
<!-- Store + JSON-->
<script src="vendor/store/store%2bjson2.min.js"></script>
<!-- ScreenFull-->
<script src="vendor/screenfull/screenfull.min.js"></script>
<!-- START Page Custom Script-->
<!--[if lt IE 8]><script src="js/excanvas.min.js"></script><![endif]-->
<!-- END Page Custom Script-->
<!-- App Main-->
<script src="app/js/app.js"></script>
<!-- END Scripts-->
</body>
<!-- Mirrored from themicon.co/theme/beadmin/ by HTTrack Website Copier/3.x [XR&CO'2014], Fri, 29 Jan 2016 16:47:29 GMT -->
</html>