The most critical componets are the ivtv driver that runs the PVR-250 and MPlayer. I won’t update the ivtv because I built it for a 2.4.24 kernel and I had to write my own recording application and my own scheduler daemon for recording TV. So as with all interdependent software - its easy to break something.

My MPlayer has been giving a great deal of trouble recently. It is running version 1.0pre5 which I beleive was released in 2004(?). Some of the MPEG2 recordings from the PVR-250 have some issues during playback. I’m hoping the problem will go away with an updated MPlayer, although I know I will get improvement with ivtv, but I can’t afford to do that.

The last “released” version of MPlayer was 1.0RC2. There are no available packages for Redhat 8, so I used my MPlayer compile guide. Since MPlayer only recently supported a GTK2 gui I chose to use a GTK1 gui since that’s what I had in Redhat 8. Virtually everything else was properly autodetected. So my configure step looked like this (quite simple):

[root@proteus MPlayer-1.0rc2]# ./configure --enable-gui \
	--enable-largefiles \
	--enable-gtk1

Unfortunately the make step (the compiling) broke with this error:

In file included from /usr/include/netdb.h:28,
                 from network.h:16,
                 from stream.h:65,
                 from stream_dvd.c:32:
/usr/include/netinet/in.h:259: parse error before '(' token
/usr/include/netinet/in.h:259: parse error before \"__u32\"
/usr/include/netinet/in.h:260: parse error before '(' token
/usr/include/netinet/in.h:260: parse error before \"__u16\"
/usr/include/netinet/in.h:262: parse error before '(' token
/usr/include/netinet/in.h:262: parse error before \"__u32\"
/usr/include/netinet/in.h:264: parse error before '(' token
/usr/include/netinet/in.h:264: parse error before \"__u16\"
stream_dvd.c: In function `dvd_parse_chapter_range':
stream_dvd.c:168: warning: passing arg 2 of `strtol' from incompatible pointer type
make[1]: *** [stream_dvd.o] Error 1
make[1]: Leaving directory `/root/dvr/mm/mplayer/MPlayer-1.0rc2/stream'
make: *** [stream/stream.a] Error 2

I hunted through the mplayer-users mailing list and found out that this is a problem with a Redhat being very old and basically no longer support. Someone suggested doing the following.
Edit /usr/include/netinet/in.h and at line 259, add following:

//mjm - to compile for MPlayerRC2
#undef ntohl
#undef ntohs
#undef htonl
#undef htons
//mjm

Then I was able to rerun the make. Then I reverted the file back to its original.

Some other things: I did also update to the latest release of XviD. I’m pretty sure that the ancient version of Xine is probably broken as well, but since I only used that to play DVD’s, I’d much rather use my Samsung DVD Player.

I know that Redhat 8 is forever out of date, so I’m updating the system to CentOS, but that’s been quite troublesome, more on that later.

Unless you need an older version for some very specific task, I strongly recommend that you use a recent version of Fedora.

To find an older version, start by going through the mirrors to see if you can find a site that is physically closer to you (for faster downloads). If you cannot find the version on a mirror, try downloading from Redhat’s site (below).

Some things to note:

• Redhat’s site does not seem to have any DVD images.
• To find DVD images either generate your own DVD from CD’s or look on a mirror.
• The SRPM ISO images are for source code and not useful for running and/or installing.
• The follow links could be removed at any point in the future.
• The rescue-CD is not needed for installing/running but maybe helpful to boot or fix an existing installation.
• Since you need to download each ISO individually, make sure to check the SHA1SUM.

Download Links:

Related:
Fedora Public Mirror List
How to download Fedora

# history | awk '{a[$2]++ } END{for(i in a){print a[i] \" \" i}}'|sort -rn|head

On my Fedora 8 box:

481 ls
297 cd
54 vim
24 rm
17 du
12 sudo
12 mv
9 who
9 screen
9 find

On my CentOS 5.1 box:

344 ls
234 cd
54 sudo
29 vim
23 rpm
22 ./annoying_app_i_cant_get_to_work_on_centos5
18 ./configure
16 pwd
15 wget
15 scp

On my web server:

378 ls
213 cd
130 vim
47 grep
39 exit
37 cat
30 diff
14 cp
10 who
9 rm

Bonus points for anyone who can point out interesting things…

To address these issues, there were many decisions I made. First of all I did not need any peripherals. The server could be entirely “headless” (i.e. no monitor, no keyboard, no mouse, etc). The primary things of value are: disk storage, memory, cpu and network. Hence the following are my requirements:

• Processor - CPU speed should be about 1Ghz. Preferably a low power processor (ex: Geode-NX, Pentium-M, etc.). I prefer a CPU without a fan and that could be cooled with the heat-sink alone. Although I do not plan to do major computational critical tasks, in the past I have seen certain processors (Via) have difficult with SSH (something that will be critical to performance for me).
• Memory - Minimum memory: 256MB. From my experience using Fedora as a server and building other minimalistic Linux machines, I know that all my tasks/processes should be fine with about 150-200MB of memory after some tweaking. For safety, about 512MB will be perfect.
• Disk - Minimum storage space: 80GB. All of my critical documents, development, music (mp3’s, etc) and server backups could be fit easily into 20-30GB. I think double that amount should be adequate. However, realistically, since I most likely would want a SATA drive for performance, most drives are at 160GB for the best price.
• Video - Don’t care. On board. The most I would need to do is run a remote X-server session, which does not benefit from better video hardware.
• Sound - Don’t care. On board. Would never be used.
• Network - Standard networking is now 100Mbit, however it would be a nice to have 1Gbit. Although both my desktop and laptop are both 1Gbit, I do NOT have a gigabit switch.
• DVD - For installation, a DVD drive would be needed, but once complete, everything would be done over the network. However, there is a practical advantage to having a DVD-RW. Even if the hard drive was very large, a 4GB DVD backup could still be useful for incremental long term backups.

What did I end up getting?

• Motherboard/CPU - Intel Celeron 220 1.2Ghz. I found a mini-ITX CPU/board combination. My primary reasons for purchase were (1) price - less than $80 USD, (2) no noise - fanless, (3) power consumption was only 27W. The other features of the board were SATA, Onboard video/sound, ethernet and USB2.
• Memory - 1GB 533Mhz. I did not need 1GB, but the price was only $25 USD and since the motherboard only had 1 slot which supported maximum 1GB, I decided that it was best to just max it out for now.
• Storage - Seagate Barracuda 7200.10 SATA 250GB. I did not need the space either but the price was only $70 USD which for the features (16MB Cache SATA 3.0Gb/s) was a good deal. I currently recommend Seagate Barracuda drives, they are great performance and reliability.
• Case - Antec NSK MicroATX Cube (350W). I thought it would be best to minimize the space the system would take. Also this series of cases is known to be absolutely silent as well as power efficient. This was the most expensive part: $100 USD.
• DVD - I recycled an old DVD-ROM I was not using.

Total spent: ~$280 USD. This was well within my budget of $300-400.

There were some things I learned and I did run into some issues. I should first mention that everything did “work” correctly.

• Motherboard SATA - I realized later that the motherboard only supported 1.5Gb/s SATA. So my drive is not operating as fast as it can be, but this is acceptable since majority of my file transfers will be somewhat smaller and the standard SATA performance is very good.
• Motherboard Video - I knew that onboard video is pretty low performance (in this case SiS Chipset). However for whatever reason the VGA-out on this board was especially noisy. While this would be unacceptable for normal use, I never intended to have a monitor on this machine.
• Motherboard BIOS - This board had an Intel BIOS. I am most familiar with Asus motherboards and in the BIOS setup there is an option to manually set the startup time (fixed, daily, etc.). The nvram-wakeup utilizes the setting to wake-up the computer. However this board does NOT have that option. I was hoping the machine would sleep during in-activity and wake automatically. I have not yet decided how to work around this other than manually starting it each morning.
• Celeron CPU - While this CPU met my needs perfectly, I was a little disappointed it did not power-throttle (i.e. reduce clock speeds to save power). The ACPI information is a little bit confusing, however given that it is low power anyways and it does support 64-bit, this is acceptable.
• Case - Any “smaller” case typically has problems. Antec is usually known for their quality, however I found my case incredibly noisy. The power supply fan rattled too much. I was thinking I would have to RMA to Newegg, but luckily I eliminated the noise by taking everything apart and re-tightening every single screw. Very frustrating but it worked.

Overall I am happy with the purchase. I did end up saving quite a bit, but I can’t help thinking that perhaps spending a little bit more would have allowed for some slight benefits.

I guess I was a little bit wordy, but I wanted to explain very clearly my thought process in assembling a computer with a very specific purpose.

More on this after the software is up and running!

The following is list of ideas, requirements and plans I hope to achieve with this server.

1. Provide file access locally (on the LAN) and remotely (over the internet).
Samba is needed for file access for Windows machines and SSH will provide both remote file access via scp and sftp. I considered using NFS additionally for Linux file access, however Samba works efficiently both Linux-to-Linux as well as Linux-to-Windows and multiple services seemed redundant.

2. Provide backup to local data (multiple Windows and Linux machines) and for remote servers (web servers).
While this may seem similar to the previous requirement, it adds the need for services like time based schedulers and remote access applications like Rsync. This may impact how/when this local server should be started.

3. Provide a web development environment.
This can easily be summarized as L.A.M.P. development which stands for “Linux, Apache, MySQL and PHP/Perl/Python”. I need a webserver (Apache), a database server (MySQL) and at least one server side scripting language (PHP). Seeing as I do have multiple websites which I develop this provides for me a both a staging area for new ideas as well as active work on “mirrored” versions of live sites. The only concern here is that it is very difficult to duplicate exact the same versions of software that is running on commercial web hosts. Issues like PHP backwards compatibility do raise issues in this planning, more on this later.

4. Provide version control and change management.
While many will recognize this as either using a version control like CVS or SVN, the truth is that using tools like this become increasing difficult when you do things like dual boot or develop on different machines. Having a dedicated server makes this functionality more practical.

Outside of some miscellaneous odds and ends, the above is exactly what I want. Note that I did not add things like DVR or HTPC. Basically, all my server should be is: Data Development and Dependability, anything else will be a waste of time/resources for me.

Going forward, I can use the specific details of my requirements to pick the proper hardware to meet my needs.

I am finally giving up on Fedora as a server. I find it just too unreliable. I have been using Fedora since FC1 (and been on Redhat since RH6.0), but for the most part I only used it as a desktop operating system.

When I was using FC3, I found it very helpful to mirror my website(s) on my local machine. This worked great, however with each new Fedora release I found more things breaking with my scripts and setup. For a while I put up with the struggle by doing things like re-compiling PHP4, but even that became quite tiring. I concluded that Fedora just moved too fast for my server development needs. I cannot fault Fedora, rather that it did not meet my needs. However I still used it.

As recently as FC6, I found the need to access my computer remotely. I started tweaking my desktop for some security and making it more “remote-access” friendly. This did work for a while. All I was doing was using SSH and working on my Apache mirrors. My frustration began with the security. I took a long hard attempt at trying to secure the system with SELinux, however for multiple reasons I abandoned it.

Later when moving to Fedora7 I was pleasantly surprised with the performance. The major problem arose when I updated my 2.6.21 kernel to 2.6.23. Some nasty bug was killing my SSH performance. Basically it left me dead in the water. I accepted to fall back on the older kernel, however soon enough I came to install Fedora8 which also had the bug. For the most part I didn’t use Fedora8 for 2 months since I was out of the country. However when I finally did, I got so frustrated that I ended up installing the old F7 kernel on F8. Of course I broke sound, PulseAudio, ACPI and the X-server, but I REALLY needed SSH to work. While this again is not Fedora’s fault, I find the following comment pretty helpful from the kernel mailing list: “Please note that 2.6.23 kernel has a lot of bugs and we don’t recommend using it…” - Regardless, it WAS a kernel that Fedora used.

I personally do not think that a given Fedora release is very stable and/or reliable. Until I started expanding my usage I really did not mind, however now I am finding it more difficult to handle. While some people may suggest I upgrade less frequently, that’s fine and all, but it does NOT change the quality of the release. Furthermore, as my desktop I like to have a new release. … And some people may tell me that I should have been more pro-active and filed bug-reports and other information. Well, I do agree with that, but unfortunately I just did not have the time.

So what’s the solution? Simple: don’t use Fedora as a server. For myself, I bought a brand new computer. I built a low powered file/web server and put CentOS 5.1 on it. In the next few weeks I will migrate all my development onto this machine. Hopefully I won’t need to upgrade it for a very long time.

Will I stop using Fedora? No. It will still be on my desktop. However I will have more realistic expectations from software considered totally “free”.

Sorry for the rant.

My biggest problems with PHP in general are its very poor track record for security, its flaws in design/configuration and finally it’s tendency to break software on updates. In some ways: its just a nuisance to maintain!!! PHP4 will be supported for critical security issues till 2008-08-08 by the PHP developers. However being open source there is no reason why someone else could not support it after that. Redhat Enterprise Linux still supports a PHP 4.3.9 package. I was supporting a 4.3.11 package for Fedora which I updated last in 2007 for Fedora 7. However I only installed it on my personal web server on a development box. I guess it would be really easy to finally abandon supporting old packages and just move to version 5, however I don’t know the effect it may have on my public server with a dozen or so websites.

For now I will set a deadline for myself to migrate to PHP5 by the August deadline. However for the time being, if people would find it useful I am considering repackaging the RHEL PHP 4.3.9 for Fedora 8. My 4.3.11 package is greatly out of date. On my development server, I’ll just go ahead and install the PHP5.2 included in Fedora 8. That will be my testing ground for my server updates coming soon.

Realistically in the long run I should just slowly stop using PHP altogether, given that PHP6 will be another mess very soon. Perhaps I will look into Python or J2EE options, not sure yet.

I will have no linux, no windows - not even a remote SSH session. Internet will be scarce but I welcome the change of pace.

Wishing everyone a very blessed Christmas and a wonderful New Year!

The Fedora project just released Fedora 8 with a great deal of enthusiasm. Fedora had been slipping behind in the past few releases and there have always been quality issues, but the team hopes this release will put them back on track.

The highlights from the Release Summary:

Graphics/Multimedia

• PulseAudio - A revamped sound system addressing many of the limitations and problems with older Linux sound systems.
• CodecBuddy - A tool to help install codecs and multimedia formats that Fedora cannot legally or ethically distribute directly.
• Compiz / Compiz-Fusion - Improvements on the Linux hardware accelerated user interface including cool effects.

Administration/Hardware

• Network Manager - significant improvements for wireless network management.
• Firewall Administration is much more user friendly.
• Package Manager - You can install software using your media (DVD). Finally! We lost this in Fedora Core 5!
• PolicyKit - When accessing restricted tasks or hardware you now have a much more user-friendly password prompt
• Improved Laptop support
• Improved Bluetooth support
• Improved power management support

Desktop

• Gnome 2.20, KDE 3.5.8, Xfce 4.4.1 (unfortunately KDE4 was delayed by the KDE team)
• GNOME Online Desktop - An application on the desktop to interface with online applications like GMail, Photobucket, Facebook, EBay, Wikipedia, and countless others
• New desktop theme

Java

• IcedTea - This is a Fedora packaged version of the Java that Sun open sourced in the OpenJDK project. Now a working Java plus browser plugin comes included in Fedora.

SoftwareUpdates

• Eclipse 3.3
• OpenOffice 2.3.0
• Kernel 2.6.23

You can download Fedora 8 using the standard mirrors or using the Torrent (recommended).

Please user the Fedora-List mailing list or any of the forums for help. There are some basic tips provided in my Personal Fedora 8 Installation Guide which should be updated within the week with the installation.

The release so far looks much more polished than the past few. I hope it is well received!

* - The Werewolf would have been much cooler if the release somehow made it on October 31! Oh well.

UPDATE - NOTE please DO NOT COMMENT here if you have problems with my Install Guide, use the CONTACT form with a proper email address. THANK YOU.

I don’t know if we will ever see an official 1.0 release, however it seems unimportant as everyone probably should just be updating their “snapshots” of MPlayer ever 3-4 months so they don’t have to wait 14 or 12 months.

I took this as an opportunity to update my MPlayer compile guide for Fedora. I do not recommend compiling from source, but I myself prefer doing it. For the more practical users, most repositories should be coming online soon with updates for yum. Simply run:

# su -c ‘yum update mplayer’

I’ve checked Livna, FreshRPMs and ATrpms, none seem to have the update yet. So yum users will have to wait.