Difference between revisions of "SRA840 Lab3"
| (3 intermediate revisions by 2 users not shown) | |||
| Line 34: | Line 34: | ||
===Nestor Chan=== | ===Nestor Chan=== | ||
| − | http://de-luxer.blogspot.com/2009/02/emtional-freebsd-in-vm-with-bad- | + | Some experience with FreeBSD on Virtual Box |
| + | http://de-luxer.blogspot.com/2009/02/emtional-freebsd-in-vm-with-bad-temper_04.html | ||
| − | === | + | How to clone a HD image(vdi) |
| + | http://de-luxer.blogspot.com/2009/02/vm-clone-war_11.html | ||
| + | |||
| + | |||
| + | There are some bugs in VBox if you install applications from source. The bug claims to be fixed in XP, but my experience that the bug is still not fixed. You may need to 'make' few times to compile a package successfully. | ||
| + | 2009/04/24 broken link due to reposting all blogs. link fixed now. | ||
| + | |||
| + | ===Katherine Masseau=== | ||
I finally managed to find the time to complete reinstalling FreeBSD on a Virtual machine, after accidentally losing my old VM a couple of weeks ago. As always, installing FreeBSD is relatively simple, straightforwards, and surprisingly fast - once you've done it a few times and remember what keys to press in what order, you can pretty much finish the portion of installation requiring human interaction in under a minute. Being half asleep, I somehow managed to miss the confirmation for the ports collection the first time, so I had to reinstall, but the second time was as quick as the first. After installation, the system comes up with no problems and everything appears to be working out of the box, including networking. | I finally managed to find the time to complete reinstalling FreeBSD on a Virtual machine, after accidentally losing my old VM a couple of weeks ago. As always, installing FreeBSD is relatively simple, straightforwards, and surprisingly fast - once you've done it a few times and remember what keys to press in what order, you can pretty much finish the portion of installation requiring human interaction in under a minute. Being half asleep, I somehow managed to miss the confirmation for the ports collection the first time, so I had to reinstall, but the second time was as quick as the first. After installation, the system comes up with no problems and everything appears to be working out of the box, including networking. | ||
| Line 47: | Line 55: | ||
Looking at the software selections available in each, I find that while many crucial pieces of software are held in the sysinstall package list, the ports selection has an overall wider selection of software available. I think overall that both are necessary, as you cannot necessary get a given package from both methods. If a package is available by both methods, it seems that sysinstall is quicker due to avoiding the need to compile. | Looking at the software selections available in each, I find that while many crucial pieces of software are held in the sysinstall package list, the ports selection has an overall wider selection of software available. I think overall that both are necessary, as you cannot necessary get a given package from both methods. If a package is available by both methods, it seems that sysinstall is quicker due to avoiding the need to compile. | ||
| + | |||
| + | ===Mohak Vyas=== | ||
| + | '''Host OS:''' Fedora Core 10 x64 | ||
| + | |||
| + | '''Guest Os:''' FreeBSD 7.1 i386 | ||
| + | |||
| + | I tried installing FreeBSD on kvm-qemu but didnt work probably because I dont have the 'vmx' flag set in my processor. But I was successfully able to install FreeBSD in my VirtualBox. It works fine. I also installed packages like gnome and bash etc. | ||
Latest revision as of 22:41, 16 July 2012
Contents
Milton Paiva Neto
Host OS: Fedora Core 10 x64
Guest Os: FreeBSD 7.1 i386
Processor: Intel(R) Core(TM)2 Duo CPU T5450 @ 1.66GHz
- How my processor does not have the instruction vmx I could not use kvm, then I used Virtual Box that only supports 32 bits guest operational systems.
Installing a port: Install a port is the same thing as compile and install a software from the source in Fedora, just ./configure, make, and make install.
Varinder Singh
Configuring Network On freeBSD (Virtual Box)
Host Setup: Dell Laptop D610 Fedora 9.0
- 192.169.1.101 IP for Host NIC (Connected to Internet)
- 192.168.122.1 IP Host Machine's Vibr0
On Virtual Machine FreeBSD
- ifconfig em0 192.168.122.10 netmask 255.255.255.0
- route add -net 0.0.0.0 192.168.122.1
- vi /etc/resolv.conf
- nameserver 192.168.122.1
Kezhong Liang
The most advantage of using packages is that it would save your time when you install large applications on your slow machine. The other benefit is that it is easy to install and you don't need to read the boring document. By comparison with package, the benefit of ports is that the technical person can install the application according to his requirement.
Nestor Chan
Some experience with FreeBSD on Virtual Box http://de-luxer.blogspot.com/2009/02/emtional-freebsd-in-vm-with-bad-temper_04.html
How to clone a HD image(vdi) http://de-luxer.blogspot.com/2009/02/vm-clone-war_11.html
There are some bugs in VBox if you install applications from source. The bug claims to be fixed in XP, but my experience that the bug is still not fixed. You may need to 'make' few times to compile a package successfully.
2009/04/24 broken link due to reposting all blogs. link fixed now.
Katherine Masseau
I finally managed to find the time to complete reinstalling FreeBSD on a Virtual machine, after accidentally losing my old VM a couple of weeks ago. As always, installing FreeBSD is relatively simple, straightforwards, and surprisingly fast - once you've done it a few times and remember what keys to press in what order, you can pretty much finish the portion of installation requiring human interaction in under a minute. Being half asleep, I somehow managed to miss the confirmation for the ports collection the first time, so I had to reinstall, but the second time was as quick as the first. After installation, the system comes up with no problems and everything appears to be working out of the box, including networking.
I decided to first try installing a package using the ports method, and settled on the 'nano' text editor. As far as use goes, the ports collection is quite easy to use -- usually, you just change directories to the one containing the port you want and run 'make install distclean'. The disadvantage, however, appears to be speed - nano has been compiling for the past 15 minutes, and I'm still waiting for it to complete!
Wow... after 20 minutes, nano is finally done compiling, and appears to work as expected. Using the ports method was easy, and simple, but it certainly did take a while for the software to compile.
Next, I decided to install the emacs text editor using the 'package' (sysinstall) method. Getting the install going took a few more steps than the ports method since there are a few intervening menus in the curses interface of sysinstall before one arrives at the actual list of packages, but, despite emacs' great size in comparison to nano, isntalling it proved much quicker since it did not have to be compiled from scratch.
Looking at the software selections available in each, I find that while many crucial pieces of software are held in the sysinstall package list, the ports selection has an overall wider selection of software available. I think overall that both are necessary, as you cannot necessary get a given package from both methods. If a package is available by both methods, it seems that sysinstall is quicker due to avoiding the need to compile.
Mohak Vyas
Host OS: Fedora Core 10 x64
Guest Os: FreeBSD 7.1 i386
I tried installing FreeBSD on kvm-qemu but didnt work probably because I dont have the 'vmx' flag set in my processor. But I was successfully able to install FreeBSD in my VirtualBox. It works fine. I also installed packages like gnome and bash etc.
