diff options
| author | Joachim Nilsson <joachim@gnufans.org> | 2003-09-13 08:24:13 +0000 |
|---|---|---|
| committer | Joachim Nilsson <joachim@gnufans.org> | 2003-09-13 08:24:13 +0000 |
| commit | 4e7d01615f0a3c0f53dd108dff9ce962eb15a54c (patch) | |
| tree | f33ea344cd6aafcae499bb377db615d6fe16c52c | |
| parent | 4e3ea6b11783045d3f43899e22ae51886d1a9871 (diff) | |
none
| -rw-r--r-- | Mach/RemoteDebugOskitMach.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Mach/RemoteDebugOskitMach.mdwn b/Mach/RemoteDebugOskitMach.mdwn index 5e4a099b..c260ce25 100644 --- a/Mach/RemoteDebugOskitMach.mdwn +++ b/Mach/RemoteDebugOskitMach.mdwn @@ -26,7 +26,7 @@ Also, [[OskitMach]] supports the GDB remote debugging protocol over a serial lin First you need some equipment: two computers, each one should have at least one (two is preferable) free serial port(s) and one (or two) null-modem serial cable(s). -While developing the kernel it might also be a good idea to use grub to get the Mach kernel via tftp from the same server you do the remote debugging and building on. This way you don't need to reboot the target to copy or build a new kernel on its hard drive. See the [[BootGnuMachOverTFTP]] for more information on this. +While developing the kernel it might also be a good idea to use grub to get the Mach kernel via tftp from the same server you do the remote debugging and building on. This way you don't need to reboot the target to copy or build a new kernel on its hard drive. See the [[AdvancedGrubUsage]] document for more information on this. Last you need to follow the instructions given below. |