developersguide:trackingcurrent
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
developersguide:trackingcurrent [2015/11/30 13:12] gtkelly changed from pkgin ing it-base clang binutils to pkgin_sets; fewer compiling errors |
developersguide:trackingcurrent [2018/07/28 21:08] (current) stux [Rebooting] fix typo |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| It's a great way to give new code early exposure; so, everyone who wants to is encouraged to give it a try. | It's a great way to give new code early exposure; so, everyone who wants to is encouraged to give it a try. | ||
| + | ===== Install the Latest Snapshot ===== | ||
| + | Due to lack of developer time, tracking current is only supported from the latest snapshot of Minix. | ||
| + | You can find the latest snapshot [[http://download.minix3.org/iso/snapshot/|here]] | ||
| + | <div center round important>Special emphasis for the current state of affairs: if you want to track current, **do not** start from the 3.3.0 release. It **will not** work. Instead, start from one of the 3.4.0 release candidates on the snapshot page.</div> | ||
| ===== Obtaining the Sources from the Git repository ===== | ===== Obtaining the Sources from the Git repository ===== | ||
| * You'll be grabbing a new "/usr/src" tree, which will contain Git metafiles also. | * You'll be grabbing a new "/usr/src" tree, which will contain Git metafiles also. | ||
| Line 83: | Line 86: | ||
| When you see the boot monitor's menu, either choose to boot the //custom// MINIX, or just wait three seconds -- the monitor automatically will boot the latest revision that it sees. <fs small>(Rebuilding the system creates a custom version of MINIX! So, you don't want to boot the original version.)</fs> | When you see the boot monitor's menu, either choose to boot the //custom// MINIX, or just wait three seconds -- the monitor automatically will boot the latest revision that it sees. <fs small>(Rebuilding the system creates a custom version of MINIX! So, you don't want to boot the original version.)</fs> | ||
| - | If all goes well, your new system will come up normally. If something goes so wrong that you can't boot, you can boot your previous image manually using the boot monitor menu: all the system images stored in subdirectories of ''/boot/minix'' are given a separate entry in the menu, as well as the system used when installing for the first time whcih is stored under ''/boot/minix_default''. You can also proceed manually: select the option to ''Drop to boot prompt'' and then issue the following commands: | + | If all goes well, your new system will come up normally. If something goes so wrong that you can't boot, you can boot your previous image manually using the boot monitor menu: all the system images stored in subdirectories of ''/boot/minix'' are given a separate entry in the menu, as well as the system used when installing for the first time which is stored under ''/boot/minix_default''. You can also proceed manually: select the option to ''Drop to boot prompt'' and then issue the following commands: |
| <code> | <code> | ||
developersguide/trackingcurrent.1448885524.txt.gz · Last modified: 2015/11/30 13:12 by gtkelly
