home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.minix
- Path: sparky!uunet!mcsun!sun4nl!star.cs.vu.nl!ast
- From: ast@cs.vu.nl (Andy Tanenbaum)
- Subject: Re: Version 1.6.24b upgrade problems
- Message-ID: <C0n1Ip.B3C@cs.vu.nl>
- Sender: news@cs.vu.nl
- Organization: Fac. Wiskunde & Informatica, VU, Amsterdam
- References: <HEIM.93Jan7115122@spike.peanuts.informatik.uni-tuebingen.de> <C0I9qB.I1v@cs.vu.nl> <HEIM2.93Jan8130543@frieda.frieda>
- Date: Sun, 10 Jan 1993 12:32:48 GMT
- Lines: 98
-
- In article <HEIM2.93Jan8130543@frieda.frieda> heim2@frieda.frieda (Gerald Heim) writes:
- >OK. I'll try. I think the name of the program was "construct". It's
- >appearently used to build a bootimage consisting of kernel,fs, mm, init,
- >monitor and the bootblock. Somewhere in the makefile it's called as
- > "construct -i image <parts>", but it doesn't build a image. Since
- >I had no manual available, I gave up and used shoelace, with which I was able
- >to boot the new kernel. Init, the kernel, fs and mm ran (I could see by
- >pressing F1), but init didn't fork any processes, nor was it wasting time,
- >nor complaining about anything. The idle-task accumulated cpu-ticks as usual.
- >A running system, but completely unusable :->
-
- Here is a manual (written by the author of the new boot mechanism, Kees Bot).
-
- Andy Tanenbaum
-
- .SH
- Doing more with the Minix Boot Monitor.
- .PP
- This text describes the menu interface of the Minix Boot Monitor, and
- the commands that may be used to customize it.
- .LP
- First of all, the monitor mode as distributed normally hides some of the
- functionality, but shows you an explanation of the environment
- variables instead. If you add -DEXTENDED_LIST to CFLAGS in the Makefile
- and recompile, then you will no longer see the long explanation (you
- should know it by now), but you will see all the commands the monitor
- knows about.
- .SH
- The commands.
- .PP
- The boot command has two functions, one is to load and start Minix, the
- other is to boot a different operating system. If the first partition
- on your hard disk contains MS-DOS, then
- .DS
- .B
- boot hd1
- .R
- .DE
- will boot MS-DOS. (Not all operating systems like to be called this
- way, some insist on being on the active partition.)
- .LP
- The delay, ls, and other simple commands are not too difficult to
- understand, just try them out. The trap command may be used to execute
- a function after a delay. You can show a menu first and boot Minix
- after 5 seconds of inactivity like this:
- .DS
- .B
- trap 5000 boot; menu
- .R
- .DE
- (This must be typed on one line, traps are cancelled when the prompt is
- printed.)
- .SH
- Functions.
- .PP
- Functions are used to bundle commands, or to build menu items. The best
- example of a simple function is 'main', the function executed by the
- monitor on startup. Main is by default defined as:
- .DS
- .B
- main() { menu }
- .R
- .DE
- So that's why you see a menu at the start. The example with 'trap'
- above could be executed by main if you type:
- .DS
- .B
- main() { trap 5000 boot; menu }
- save
- .R
- .DE
- The save command will save the changed environment of the monitor to the
- second half of the boot block, the "boot parameters sector".
- .LP
- Functions may have one or two arguments, the first is a key to be
- pressed from the menu to execute the function, the optional second
- argument is the text that is to be displayed on the menu. The single
- argument functions should only be produced by construct, like this
- one:
- .DS
- .B
- AT(a) {label=AT;image=42:626;echo AT kernel selected;menu}
- .R
- .DE
- It invites you to choose one of many kernels on a special boot floppy.
- .LP
- The two argument functions are used to customize the menu, once you
- define one the default option disappears, so your first function will
- probably be one to start Minix. Example:
- .DS
- .B
- minix(=,Start Minix) { boot }
- dos(d,Boot MS-DOS) { boot hd1 }
- save
- menu
- .R
- .DE
- Now you can type '=' or 'd' to choose between Minix and DOS.
-