FreeBSD 8.2 Stable w KDE4.6.3
FreeBSD 8.2 Stable w KDE4.6.3 | 10.2 GB
Represent a virtual machine for VMware installed
FreeBSD, and the graphic environment KDE 4.6.3, Midnight Commander (console) localized ripozitary standard for KDE under FreeBSD: system utilities, editors, multimedia applications, the Internet - Explorer (Firefox-3.6.8, 1, browsers Konqueror, Opera .) Also present in the assembly video course "to install and configure VMware".
The instruction is equally true for Windows XP and Windows 7.
It is assumed that our Computer is already installed VMware Workstation 6.5.3 or higher (if it is run under Windows 7, or VMware Workstation 5.x and above). Unpack the archive to a virtual machine (file FreeBSD.7z). Before running to necessarily tune VMware-network. Running VMware Workstation, then in the menu Edit -> Virtual Network Settings ... Summary of contributions see which adapter corresponds to a virtual NAT (usually VMnet8). Then we go to the tab Host Virtual Network Mapping. To the right of the arrow VMnet8 click ">" and select the item Subnet ... In the box IP-address, you must install 192.168.231.0.
Our virtual desktop will be available on the IP 192.168.231.26. His domain name - usr
start the virtual machine and wait until the boot FreeBSD and will display:
FreeBSD/i386 (usr) (ttyv0)
At this stage, until you can not enter a password and just roll (not close) the window with the virtual machine and make sure that it is accessible from Windows. Perform the "Start" -> "All Programs" -> "Accessories" -> "Command Prompt". In the window that appears, write:
Look, if successfully passed the ping. If packets are not transmitted, the network is not configured correctly.
Now back to our virtual machine. The system has 2 user: root (password toor) and user (password resu). Having come from any of them, you can also see that the ping goes in the opposite direction:
and if the local machine has access to the Internet, a virtual must also be able to ping and external addresses, such as:
If the ping is not likely to blame for any security settings Windows, firewall, etc.
To correctly shut down the system (I have a shutdown in VMware just "power off") neobhodmo the command:
usr # shutdown-p now
It can execute as root, or a user, we collect
$ Sudo shutdown-p now
and to request the user's password user.
That's probably all could have been screwed and samba or make an exchange with the host via ftp, but can be another time. Password for root: toor, password user: resu
And of course, once logged in, the best course is not as root.
And do not forget to change paroliki before going to the big network.
usr # passwd
for this root, if you authenticate as root and
$ Passwd user
For the user, respectively. Good luck to try how it all happens on UNIX.
I will check, If link dead, I will reupload at here