Hello from Boulder
Posted: Fri Aug 31, 2012 12:04 am
Just got Mint and I think it's the nicest Linux I've seen. Certainly the least scary.
I'm running Mac OSX, VirtualBox, and Mint as a precursor to installing Mint on VirtualBox in Windows 7. My setup is pretty typical, I think: I have an Airport WiFi base station connected to ComCast. Airport gives the Mac a private IP address via DHCP (10.0.1.2). I'm confused about how to configure VirtualBox and Mint so that the Mac and Mint can be members of the same LAN, can connect to each other by hostname, and can share folders.
Can anyone point me to a document that just says "do it this way" rather than tries to encyclopedically explain every configuration option and its purpose? As I say, I believe I have a pretty middle-of-the-road configuration. But making choices like NAT vs. Bridged vs. Host-only (in VirtualBox Network settings), or wondering if I should worry that Mint's DHCP doesn't appear to populate the DNS Server list, is starting to make my head throb.
Thanks for any pointers at all!
Chap
I'm running Mac OSX, VirtualBox, and Mint as a precursor to installing Mint on VirtualBox in Windows 7. My setup is pretty typical, I think: I have an Airport WiFi base station connected to ComCast. Airport gives the Mac a private IP address via DHCP (10.0.1.2). I'm confused about how to configure VirtualBox and Mint so that the Mac and Mint can be members of the same LAN, can connect to each other by hostname, and can share folders.
Can anyone point me to a document that just says "do it this way" rather than tries to encyclopedically explain every configuration option and its purpose? As I say, I believe I have a pretty middle-of-the-road configuration. But making choices like NAT vs. Bridged vs. Host-only (in VirtualBox Network settings), or wondering if I should worry that Mint's DHCP doesn't appear to populate the DNS Server list, is starting to make my head throb.
Thanks for any pointers at all!
Chap
Thanks for joining the forums! As to your VirtualBox challenge, you would normally want to set it up as Bridged Adapter (assuming Airport works with non-Apple devices?). A Bridged Adapter means your VirtualBox guest OS will try to lease its own IP address from your DHCP server, just as the VirtualBox host OS has done. So your VirtualBox guest OS will have a working Internet connection, and it is reachable on its IP address on your local network and it can reach other devices on your local network, such as the VirtualBox host OS, on their IP addresses. A good article (though a bit dated) discussing the differences between the three: 