Fedora

Switching to a Virtual Server

Rather than having an entire machine dedicated to a single server operation, a graphical desktop can be installed to administrate the implementation of a single or multiple Virtual Servers. VirtualBox is the Virtual environment of choice, with the main decision being the base OS. Contrary to past experience, Ubuntu Gutsy won’t install Graphically on the new machine that I purchased; I guess is an incompatible graphics card. Not a problem, Fedora 8 is close by. Overall my OS choices typically ranges between Ubuntu and Fedora, and Fedora 8 will be the Desktop environment of choice for my new server. I will be using Debian for the server environment in the Virtual machine. Utilizing a Virtual machine for your web server allows for substantially easier backups. Instead of having to copy multiple files, a single file represents the entirety of the server environment. A single VDI file represents everything, consolidating everything for supremely easy management.

Fedora 8 Ubuntu Gutsy IP Address

To get your external IP address go to the following http address in a web browser: http://www.whatismyip.com If you are behind a router, you can configure your router to provide a particular local IP address. This would be configured in the LAN IP setup menu. This is a convenient feature for applying a particular IP address to a machine with a particular MAC address. The IP address of your machine is configured in the administrator>>network panel. You can switch between DHCP and static ip. These parameters are typically configured during installation, and DHCP is the default. For most configurations DHCP is the easiest choice, as your router is most likely setup by default as a DHCP server. A static IP only really comes in handy with web servers, and when you have to turn off the router DHCP server because of conflict with a software DHCP server.

Cube Panel Fedora 7 Dependencies

This dependency list is straight out of the Cube Panel instruction manua. You must install the following before trying to install Cube Panel: yum -y install sharutils perl python vsftpd httpd mod_ssl php php-mysql mysql perl-Crypt-SSLeay awstats mysql-server bind-chroot spamassassin squirrelmail cyrus-imapd cyrus-imapd-utils libc-client2006 perl-XML-Simple bind patch binutils libxslt perl-Archive-Tar perl-Archive-Zip perl-Authen-SASL perl-BerkeleyDB perl-Bit-Vector perl-Carp-Clan perl-Compress-Zlib perl-Convert-ASN1 perl-Convert-BinHex perl-Convert-TNEF perl- Convert-UUlib perl-Date-Calc perl-DateManip perl-DBD-SQLite perl-File-Slurp perl-FreezeThaw perl-IO-Socket-SSL perl-IO- stringy perl-IO-Zlib perl-libwww-perl perl-Mail-SPF-Query perl-MailTools perl-MIME-Lite perl-MIME-tools perl-MLDBM perl-Net-CIDR-Lite perl-Net-Server perl-Net-SSLeay perl-Razor-Agent perl-SOAP-Lite perl-TimeDate perl-Unix-Syslog perl-URI amavisd-new clamav clamav-data clamav-lib clamav-server clamav-update arc cabextract distcache fedora-usermgmt freeze lzo lzop ncompress nomarch postfix postgresql-libs yum caching-nameserver php-pear compat-db curl-devel libc-client2006 php-cli postgresql postgresql-libs postgresql-server php-pgsql perl-LDAP arj With these programs the Cube Panel software should be able to install accordingly. For more information about Cube Panel and to download: http://www.cubepanel.com I haven’t tried this yet on Fedora 8, but hey you never know, it may indeed work :) **–Update 11:37 PM Saturday November 10th–** This works flawlessly with Fedora 7.

Fedora 7 Instead of Fedora 8 – Cube Panel

The Cube Panel hosting suite has an installation candidate for a Fedora 7 operating system. Because of this I am choosing Fedora 7 instead of Fedora 8. I have used Fedora 8, and uploaded a VDI VirtualBox file to http://www.virtlinux.com, and can report a good experience. I also have a good opinion of Fedora 7, which I use for a permanent mail server on another system. Cube Panel is available in a Free Lite Version: http://www.cubepanel.com/download/index.htm

ISPConfig Difficulties on Debian – Switched to Fedora 8

Due to difficulties achieving a successful ISPConfig installation of Debian Etch, I have decided to go with a Fedora 8 installation. HowToForge.com offers a convenient installation tutorial to get an ISPConfig server up and running on Fedora 8! http://www.howtoforge.com/fedora-8-server-lamp-email-dns-ftp-ispconfigĂ‚ 

Fedora 8 – bcm43xx – NDISWrapper

This article is applicable to people who want to use a Windows wireless driver, instead of bcm43xx or a derivative. The benefit is usually increased performance. The bcm43xx Firmware does not operate at 54 Mb/s therefore the windows driver can be utilize with ndiswrapper. To get the driver visit your manufacturers website; for instance I have a HP laptop, therefore I go to HP.com and then to their drivers page. On the drivers page I look for the broadcom driver package for WIndows XP; it will be an .exe file. You will have to install cabextract to unpack the file. One of the files after unpacking will be bcmwl5.inf: yum install cabextract Your downloaded driver package will most likely be on the desktop: cd Desktop cabextract sp43654.exe The .exe file will unzip and all the inner files will now be on the desktop. Proceed with the installation of NDISWrapper and then you can install the driver (bcmwl5.inf). To download NDISWrapper you can visit: http://sourceforge.net/project/showfiles.php?group_id=93482 You need gcc and the kernel headers to compile ndiswrapper: yum install gcc kernel-devel-$(uname -r) With these two packages, and associated dependencies NDISWrapper will install successfully. Once your headers and compilation software are installed, navigate to the NDISwrapper folder and proceed to build: cd Desktop cd ndiswrapper-1.49 make sudo make install Then install the driver. Navigate to the desktop where you unzipped the .exe driver pack. Then proceed to install the new driver: cd ~/Desktop sudo ndiswrapper -i bcmwl5.inf Now you have to blacklist the bcm43xx driver to prevent conflict: sudo nano /etc/modprobe.d/blacklist Add at the bottom of the file “blacklist bcm43xx”. Save and exit. Now add NDISWrapper to the modules list for autostart purposes: sudo nano /etc/modules Add on a new line “ndiswrapper”. Done, finito, completo :)