Monday, August 22, 2005


I was particularly amazed that I managed to get away with installing dotproject on a xampp set-up on a Fedora RH4 linux box, on our office network so easily! I came back in today still not believing that its still sitting there. Certainly a highlight of last week.

Thursday, August 18, 2005


Well the Xampp Intranet server is up and running on my Linux box. Now to install DotProject...


There seems to be a requirement to create two of the same users in phpmyadmin priveleges otherwise that user can't gain access. I followed the root example which has a root@linux and a root@localhost both the same. I tried various combinations but this seemed to be the one that worked.


Got Xampp up and running on a workstation which I am hoping will be able to act as an intranet site for dotproject. The trick with getting Xampp going properly is not to alter any of the passwords via the phpmyadmin page but to create them via /opt/lampp/lampp security. Then everything seems to work ok. The whole shebang can then be accessed over a network.

Wednesday, August 17, 2005


There's a bit of work to do prior to installing DotProject. I though I might cut a few corners by installing Xampp on an intranet that could be accessed by staff. So thats the first thing to do. I've read up on the woes and gos for this kind of lampp and it seems it will save the time of stuffing around with a 'typical' lampp install. Then I can see if DotProject will run on this kind of thing. Hope it does!

Wednesday, August 03, 2005


After working out how to set the laptop up to boot from cd, that you have to press "enter" instead of following the instructions that ask you to click the "next" button to start the install (waited for about 15 minutes, rebooted, reconfigured anaconda waited again for something to happen before starting to explore other options), a retry on a package, everything's peachy.


Yesterday I got things sorted on the server and today it has booted up fine. Yep I was right. Redhat keeps looking for config parameters during boot up if they don't work. It took a couple of boots and correct config of the network (had the wrong IP address), as well as the domain controller to recognise the machine on the network before things all went along smoothly.

Tuesday, August 02, 2005


Yesterday I started to install Redhat 4 on a temporary fileserver. I started with enthusiasm, thinking I would install via a Kickstart file. After a bit of a look on the web I couldn't really find much about reinstalling using Kickstart, so instead of wasting hours of trying to work it out, I thought I'd go for the manual installation via Anaconda.

I started by doing it in the way that I usually install linux. Thats to set up a bare bones facility and then add the packages I need. So I configured Anaconda and started the install and it died. So I started again. Second time lucky it worked.

I went into the gnome package manager and selected the packages that I wanted to install - Samba for the file server. Clicked the update button and got the dialogue box that tells you you need extra packages providing you with a list of the missing items. Great. Tried a couple more times, reducing any superfluous packages that I didn't really need. Not much luck there either kept getting the same box with things I had checked off. In the end I thought well I can either download the spare packages or chance a reinstall at a server config, which I eventually chose.

Would it have been quicker to get the dependancy packages from the web? Well at the moment I have so much trouble installing new software on linux that I avoid it like the plague! I've tried with some software and after about a day or so of trying to install it I just chuck in the towel. I really need to brush up in this area. I need some sort of best practice method for install programs. It's not like windows, files go all over the shot. Where's the best place to put them - theres no program file folder, you could put them in your home folder for all I know. Especially in those compile from source things. They are the worst! You go about from the command line. I've managed to get files from one end of town to the other with those things and given up in the end. That's why its listed on my wishlist ( see previous post ).

Anyway, I started with the second install. There were a few retry dialogue boxes for installation of various software but fortunately on each retry it continued installing instead of having to reboot and start all over again.

So I got my RH4 up and going and am now configuring it network and samba wise. I had this idea that I'd use the network setting files from temporary server version 1, so I had copied my config files over from that to my laptop. Having no other way to transfer these files other than floppy or cd first up I went for floppy. RH4 would not recognise the file system that my floppy was formatted as. RH3 on my laptop had no probs. Not wishing to stuff around with this any further and it being almost the end of the day I thought, oh well I'll configure the network by gnome.
Did that, stopped and started the network just to see what I could see, knowing that sometimes you have to do a reboot so that it registers round the local network. Ended up having to reboot.
When I went to log off, the log off dialogue box took ages to pop up. Guess the computer didn't want me to go home. So by the time I packed my bags and got ready to leave it finally was nice and was able to shutdown, with the hesitation that things were going awfully slowly.

Got in today and had to do an interactive boot to get the RH4 server up after a couple of stalls on the boot up. I know linux doesn't like to start up network daemons when there's not network cable available from experience with my laptop set-up. So this didn't really worry me. Finally the login came up and I logged in. It took about a minute to load up my preferences and left the loading preference dialogue box on the screen up while I was getting down to work out why I couldn't see the network. I had noticed that last night after using the terminal from a right click on the desktop that it took ages to initialise. I have noticed though, on previous installations of RH that for a few initial boots, linux seems to be a bit vague. I'm crossing my fingers that this is the case.

Any comments appreciated.


Well this is the second time. As I'm on the list I wonder if I'll get an email this time



This is a wishlist of linux stuff I still haven't got in my head around but need to have in there. Its a wishlist that will hopefully be the basis for maintaining and acting as a linux trouble shooter for staff of our system. I'm sure there'll be more:

Have a best practice methodology for installing and updating rpms, packages and programs downloaded from the web.
Be able to implement Kickstart on installs
Be able to use Yum to update rpms on networked machines
Have underpinning knowledge of Bash Scripting for crond system admin tasks such as backups
Be able to understand the special flags for permissions and implement them for the fileserver
Ensure that smb.conf file config is secure
Set up Linux server as Domain Controller for Windows Workstations
Install a Lamp setup on linux for development purposes
Configure a Lamp setup for a webserver - maintainable with PHPmysqladmin such as in Xampp
Configure a Lamp setup for a intranet - maintainable with PHPmysqladmin such as in Xampp
Maintain a basic understanding of IP Cop