> But the challenge of BSD have so far proven too much for me. It would take > too long to configure FreeBSD to my liking. I couldn't figure out what to > enter in GRUB to multi-boot Linux and BSD. I tried PC-BSD, GhostBSD, and > DragonflyBSD in VirtualBox. I've found PC-BSD agonizingly slow to install > and operate, and KDE didn't even boot up when I logged in. GhostBSD has too > many things that don't work, such as the keyboard on my laptop and my > Internet connection on my desktop. DragonflyBSD didn't boot up in Virtualbox.
To boot FreeBSD, you need the code in the master boot record to simply pass control to the boot sector code sitting in the FreeBSD partiton. The boot sector code on the FreeBSD partition has everything it needs to boot FreeBSD. So, in GRUB: title FreeBSD root (hd0,2) makeactive chainloader +1 (hd0,2) means FreeBSD is on the 3rd partition of the hard drive. Side note: When you install FreeBSD there is an option to "don't touch the MBR" (master boot record). However in practice and with certain versions of FreeBSD I have found that even with the "don't touch" selected, it still modifies little things in the MBR. Therefore, I would recommend backing up the 512 bytes in the MBR on your system so that you can restore in case things become unbootable, which was the case for me when I installed CURRENT a few days ago. Another side note: FreeBSD might not be for the faint at heart. It's very powerful however. For me, FreeBSD is an opportunity to learn more about how computers actually work. And I'm delighted by the experience. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
