The Place to Start for Operating System Developers
http://f.osdev.org/
VirtualBox has it's own tool for this.bluemoon wrote:There is probably some tools to convert from raw image to the listed format too. Try google it.
Code: Select all
VBoxManage convertFromRaw --format VDI input.dmg output.vdiI've found QEMU to be faster on the new i5 and i7 based Macs.berkus wrote:I would still recommend bochs.app over any other tool for osdev on osx.
WTF?!? What's wrong with it's native stuff? You have bash, vim, perl, binutils, gcc, llvm, gnu/make, nasm, fasm, dd... everything you'll ever need for OSDEV. You can create and mount FAT natively. Only thing to do is a cross-compiler (same as with Linux), that's all (or you can use objconv).iansjack wrote:The best tool for programming OS stuff on a Mac (IMO) is Linux running in a VM.
LoL, by definition this is not programming OS stuff on a Mac, but is programming on Linux.iansjack wrote:The best tool for programming OS stuff on a Mac (IMO) is Linux running in a VM.
I would add building gdb to the list as well. Mac's built-in gdb won't work with elf. But then, develop on mac is totally workable, as I'm just doing that.turdus wrote:You have bash, vim, perl, binutils, gcc, llvm, gnu/make, nasm, fasm, dd... everything you'll ever need for OSDEV. You can create and mount FAT natively. Only thing to do is a cross-compiler (same as with Linux), that's all (or you can use objconv).
+1 from me too. You also have Eclipse and Xcode. I use vmware fusion and connect a cross-gdb to the vmware kernel debugger to debug my OS. I also use VMware serial ports tailed to a terminal for kernel logging. The only time I need Windows or Linux is to occasionally check that my build scripts work on those OS's.bluemoon wrote:I would add building gdb to the list as well. Mac's built-in gdb won't work with elf. But then, develop on mac is totally workable, as I'm just doing that.turdus wrote:You have bash, vim, perl, binutils, gcc, llvm, gnu/make, nasm, fasm, dd... everything you'll ever need for OSDEV. You can create and mount FAT natively. Only thing to do is a cross-compiler (same as with Linux), that's all (or you can use objconv).
I always have a copy of clean disk image, so when I messed up the testing image, I'd just "cp initial.img testing.img".gerryg400 wrote:I also occasionally use Linux to reformat my virtual disks when my ext2 driver trashes them.
I think you confuse Macs and OS X; they are not the same thing. It is programming in Linux on a Mac (it sure as hell isn't a PC!).bluemoon wrote:LoL, by definition this is not programming OS stuff on a Mac, but is programming on Linux.iansjack wrote:The best tool for programming OS stuff on a Mac (IMO) is Linux running in a VM.
Well, I think it's useful to keep my cross-compiling environment jailed from my native environment. I can take snapshots of the environment, play about with it and revert easily if I don't like the results.turdus wrote:WTF?!? What's wrong with it's native stuff? You have bash, vim, perl, binutils, gcc, llvm, gnu/make, nasm, fasm, dd... everything you'll ever need for OSDEV. You can create and mount FAT natively. Only thing to do is a cross-compiler (same as with Linux), that's all (or you can use objconv).iansjack wrote:The best tool for programming OS stuff on a Mac (IMO) is Linux running in a VM.
I think using linuxvm is a very very bad advice.
I always have a clean copy of my entire development environment. Same logic.bluemoon wrote:I always have a copy of clean disk image, so when I messed up the testing image, I'd just "cp initial.img testing.img".gerryg400 wrote:I also occasionally use Linux to reformat my virtual disks when my ext2 driver trashes them.