Fedora Installation Notes: Difference between revisions
| Line 37: | Line 37: | ||
NOTE: Even though the system won't have a graphical desktop started, you may still want to change the graphics driver to ''vesa'' using the following command: "'''system-config-display --set-driver=vesa'''". This way you will at least be able to see the screen if you forget and try to start '''X''' via: "'''init 5'''". | NOTE: Even though the system won't have a graphical desktop started, you may still want to change the graphics driver to ''vesa'' using the following command: "'''system-config-display --set-driver=vesa'''". This way you will at least be able to see the screen if you forget and try to start '''X''' via: "'''init 5'''". | ||
== Development Case Study Using VMWARE by a newbie == | |||
I undertook a challenge to see if I could make a working NST under VMWARE. The motivation is that I needed extra functions beyond what was available in the NST 1.5 VMWARE image. I needed the ability to use the VMWARE hgfs function and add additional tools. Samba was an alternative to hgfs. But to add the additional tools I needed to build an FC image anyway. So why not do it under VMWARE? | |||
I started by following the instructions, [[Building From Source]], that were developed by the primary NST developers. FC7 was built under Fusion. | |||
Revision as of 17:17, 6 September 2007
Fedora 7 Installation Notes
VMware Server
If you install VMware server onto your Fedora 7 box, you will likely need to install the any any updates. In short:
- Install VMware Server.
- Download and extract the any any updates. Look for a file name like: "vmware-any-any-update113.tar.gz" (the 113 will probably be different) at: "http://platan.vc.cvut.cz/ftp/pub/vmware/".
- Run the: "runme.pl" script from any any updates.
NOTE: The recommended virtual SCSI drivers in VMware Server v1.0.3 did not seem to work with the SCSI modules in Fedora 7. We ended up using the lower performance virtual ATA drivers in our setup (maybe we should have tried the virtual BusLogic adapter).
Virtual PC
Installation of Fedora 7 on a Windows box using Microsoft Virtual PC 6.0.156.0 is possible. Here are some notes:
- Use text installation mode.
- After the installation completes and the system reboots, the screen will come up in an unreadable state. However, you will be able to connect to the system using a ssh client (you can use: nmap -p 22 192.168.1.100-250 on a range of IP addresses to help identify the system).
- After connecting to the system using a ssh client, add the vga=771 boot option to: "/boot/grub/grub.conf". It will look something like the following:
title Fedora (2.6.22.1-41.fc7)
root (hd0,0)
kernel /vmlinuz-2.6.22.1-41.fc7 ro root=/dev/VolGroup00/LogVol00 rhgb quiet vga=771
initrd /initrd-2.6.22.1-41.fc7.img
- Edit the file: "/etc/inittab" and set the default run level to 3.
- Reboot the system.
At this point you should have a stable development system. You won't have a graphical desktop, but you can use a VNC desktop should you need graphical access.
NOTE: Even though the system won't have a graphical desktop started, you may still want to change the graphics driver to vesa using the following command: "system-config-display --set-driver=vesa". This way you will at least be able to see the screen if you forget and try to start X via: "init 5".
Development Case Study Using VMWARE by a newbie
I undertook a challenge to see if I could make a working NST under VMWARE. The motivation is that I needed extra functions beyond what was available in the NST 1.5 VMWARE image. I needed the ability to use the VMWARE hgfs function and add additional tools. Samba was an alternative to hgfs. But to add the additional tools I needed to build an FC image anyway. So why not do it under VMWARE?
I started by following the instructions, Building From Source, that were developed by the primary NST developers. FC7 was built under Fusion.
