ianw1974

There could be a couple of things here. You say it's an old machine? So it's possible it only has a CD-ROM drive, rather than a DVD-ROM drive. Could it be that the later versions that you have burned are DVD's and not CD's? Alternatively, it could always be a bad burn, or corrupted ISO download, and hence the problem with not being able to read the disks that you install. EDIT: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c00282472&tmp_task=prodinfoCategory&cc=us&dlc=en&lc=en&product=446896 from here it looks like it just has a CD-RW drive, so if you're attempting to start from DVD's, that will not work and might be the source of your problem. If using CD's for later versions, then I guess a bad burn or corrupted ISO download. Verify the ISO with the md5sum, and if incorrect download and burn again. The other alternative, if there are no CD ISO images for the distro that you want to install (which can be the case), just replace the CD-RW with a DVD-RW, and then you're done. Best bet will be to take out the one you have in there, verify the type of connection (I expect IDE), and make sure you get a DVD drive with IDE. A lot of them now are SATA, which because this is an old machine, isn't going to work.

Maybe not trivial, but on my particular system it didn't work with the new installer. The old installer however did. Had I had the time, I would have probably posted about it to get it fixed and get my system working. However, I didn't have time, I needed my system working as I didn't have another, so dropped it for something else that just installed and worked immediately.

Yep, you'll be fine :)

If you aren't natting on the router (port-forwarding) to gain access to it externally, then no, you won't need to. Then you are just using it for internal use on your private network.

On private network yes it's enough, but if you will access it from the internet then you'll need to secure SSH with public keys instead of passwords, and also install something like denyhosts to protect SSH from being attacked by people trying to login to your server. Can even change SSH to run on a different port than port 22, to also minimise the risk. And yes, the chown is fine, because you upload everything using the web browser which connects to the web server, and the web server needs access to that folder/directory to save any files you upload. I expect all of that is in the owncloud docs.

You probably already had self-signed certificates by default, if you connected to owncloud with https from the beginning. Firefox will shout about self-signed certificates. If you want to generate free one's which are verified Class I certs, you can get from http://startssl.com

The bit paul wrote is for helping with access to the directory, it doesn't fix your webdav issue. That's something you need to get apache configured for. Maybe you need to install some extra packages? Trying installing: apache-mod_dav I found this when googling "mageia apache webdav". Restart apache afterwards, and try again.

Changing the owner of data is correct. You probably need to enable the webdav module in apache - that's what your error is throwing. I found a post that curl is optional, so another way is edit php.ini find the php_curl module in there, and comment it out. Maybe curl is just throwing an error because something is not quite correct. Two things to check at least. Normally I download and extract manually from owncloud. This means you get something without any "distro" tampering - which is something you might be experiencing because you installed it via MCC. Also you don't necessarily have the newest version available. Too many times I've had problems with distros and installing from the repo, for example joomla, redmine, owncloud (Debian when I experienced problems). Sometimes it's just easier and better to do it a bit more "manual" and download and extract manually.

I stopped using Arch when they changed the installation process, because it was a piece of crap and didn't work after the reboot, and I consider myself quite good on Linux now, and even I couldn't figure out how to get it working. Something so simple as an installation process should work. But yes you are right when people reply with RTFM, it's not exactly helpful at the least. Gentoo is probably more complex to install, but the documents work, and the help on the forum is also excellent, even if you are a newbie. I lately am Ubuntu, mainly because I just want it to work. I still use more complex things for servers, but that depends on what I'm attempting to achieve, and then use an appropriate distro.

Are they both USB based modems?

Now there is OpenMandriva. Or Mageia, if you're wanting to stick with something like Mandrake/Mandriva used to be.

First of all, you will have to modify the boot loader on the first drive, otherwise it's just not going to work. Therefore grub will have to be on this drive, other than that, it would just remain Windows only. Normally your order for Windows has to be as follows: 1. Install Windows 98 2. Install Windows XP 3. Install Linux you can do some trickery with grub to switch the drive ordering to allow the second drive to become the first drive, and then boot Windows 98. Because you won't be able to boot it any other way, because I can imagine the original install is for C:, and if you put it in as the second drive, it effectively becomes D:, and then Windows will not start, because mostly of the registry settings, etc and would be too much of a pain to change all this. Maybe this will help for the reordering of the drives for grub to then boot Windows 98 on the second disk, as if it was still C:. https://www.google.co.uk/#q=grub+change+drive+order although I've never done it, some other people have done something similar. Normally installing in the order above would be best. You can try and see how it goes with the grub reordering, but I can't help you any further with that, as I've never done it and haven't the ability to check and test it for you.

I see you are impatient, considering you posted and then make a comment in less than two hours that the board is dead. Were you expecting an immediate reply, that people are here waiting to fix your problem?

As someone has pointed out, libraries on RHEL 5.3 are too old. Maybe if you updated with yum to RHEL 5.9, but I doubt it. As Jim said in previous message, upgrade to latest RHEL, in which someone already posted RHEL6 and that version of Firefox would work. Or, if you do not have a subscription, change to CentOS - but again version 6 is what you'll need since CentOS is effectively rebadged RHEL.

You can have multiple versions of python on your system. One will be system-wide which you have in your distro already, and another you can have and run alongside it. I think I did do it once, but on a Debian system, so can't really tell you exactly how I did it now. But it's possible.

It's possible that it's a KDE bug, I don't have KDE on my system, and haven't used it since 2007. Seems strange that it shows it in Dolphin when you go to the properties of the file, but not anywhere else. I'd have thought that once you changed it, that it should show it correctly. Sorry that I can't be of much help.

If you could find the name of the original icon file, locate this, then rename it and symlink to your new one, or copy your new one into place, and that would be one way of solving it. We used to do similar with Gnome and the Mandriva star, changing it to display the gnome foot instead of the star. So a similar process should exist for the particular icon set that you are using in KDE.

You don't listen. We were just a mirror, we don't have the code. And even if we did have it, we too would have to ask for permission from the easyurpmi team. You will have to contact the easyurpmi team directly if you want it. Sorry, but we can't do anything.

OK, based on the mdadm command that I gave you before, just put all this in the mdadm.conf, then make sure mdadm is enabled at bootup: chkconfig mdadm on and then reboot, and see what happens. Check that it's active with: cat /proc/mdstat

From what I know yes, you copy it all and put it in. That's what I understood from the post. Make sure there are no other ARRAY lines in the /etc/mdadm/mdadm.conf or /etc/mdadm.conf - it depends where this file exists on your system. No idea where you configured the arrays, whether you did it within the controller, or within Linux. I understood that previously you had it under Linux, and not configured on the Intel controller before booting the system.

Some info here on activating the array: http://superuser.com/questions/117824/how-to-get-an-inactive-raid-device-working-again the last paragraph mention susing the madadm --examine --scan command and then putting this in your mdadm.conf file. Then ensuring that /etc/fstab matches in terms of the arrays.

I guess that as mdadm isn't installed, this means that dmraid has been used to configure/create/manage your arrays. However, if you need mdadm and it isn't installed, simply install it.

What exactly is the problem? Why do you need to run it? The command you are using is similar to what I would have used to activate and scan LVM's to activate volumes: vgchange -a y which obviously then allows me to mount them. Let me know more about your problem, so I can help with your boot issue. I expect something with initrd, or some grub config perhaps.

Make sure your username and password for Windows and Linux are the same, then it won't ask.