Jump to content

ianw1974

Admin
  • Content Count

    14036
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by ianw1974

  1. 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.
  2. 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?
  3. 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.
  4. ianw1974

    Updating Python

    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.
  5. 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.
  6. 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.
  7. 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.
  8. 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
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. Make sure your username and password for Windows and Linux are the same, then it won't ask.
  14. You would need to map a drive and make it persistent so that it connects each time you reboot.
  15. There is this: ERROR: Kernel configuration is invalid. include/linux/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it so go to the /usr/src/kernel-linus-devel-2.6.21.5-1mdv directory, and then do this: make oldconfig make prepare then try and do the driver stuff again with the make command that you issued before: [root@localhost rtl8712_8188_8191_8192SU_usb_linux_v2.6.0005.20091229]# make
  16. Glad it's working, and my pleasure for the assistance.
  17. Your kernel source probably doesn't match the kernel that you have installed.
  18. If you're losing connectivity when you set up a static IP, then there are possibilities that you didn't configured the default router, and also perhaps your DNS is incorrect as well. You can check this when you have a DHCP address you can then see what your default route is and also what your DNS is. Alternatively, you gave it an IP which conflicted with something on your network already. Best thing to do is find out what DHCP range is configured on your router, and then use an address outside of this range. Or, find out which systems you have and where the IP range starts, and how they increment, and give an address from the other end of the scale. For example, your router is 192.168.1.1 - you get addresses which start at 192.168.1.11, 12, 13 and so on. So you would then use a static IP from the other end of the scale so that it won't conflict, eg: 192.168.1.200. Since it's unlikely you are going to have 190 devices. Or, if your IP DHCP range is 192.168.1.11 to 192.168.1.100, then you can start from 101 for your servers and go up from there. If a system is operating as a server, such as with samba, then yes it's best to have a static IP. You need to give the router as your default gateway, and there is also a possibility that this is also being used for your DNS. Alternatively, you can set the DNS to 8.8.8.8 and 8.8.4.4 for Google DNS, or 208.67.222.222 and 208.67.220.220 for OpenDNS.
  19. You don't need joomla in the repos, it's dead easy to setup without it. Just extract and then when you're going through the installer, you'll get to add in any dependencies from the repos anyway. I've been using it for years, although now one of my sites is on Drupal. I thoroughly recommend Joomla, it's cool. I still need to migrate sites from 1.5 to the latest version and will get around to it soon. The problem with Joomla from repos, is in my experience from Gentoo, that when I updated, I then had to go through all the config again to get the site working. This is why it's best just to extract the source into /var/www or wherever your web site will be located on your machine. It's not that hard, there's nothing to compile. Just any dependencies just need to be installed if it's PHP, etc, and a MySQL database is required so get that installed first also.
  20. I would add those options, mainly because then it secures it a bit more, and could be part of the reason why you cannot save anything. If you have the writable option and you logged in, then it should work, but perhaps the valid user option is blocking it. Did you add a user with smbpasswd?
  21. Check your /etc/samba/smb.conf: [homes] comment = Home Directories browseable = no read only = no create mask = 0700 directory mask = 0700 valid users = %S guest ok = no this is part of my smb.conf for the home directories. Also, after you've done this, you'll need to create the samba user for "username", so in my example, I use my name "ian". smbpasswd -a ian provide password for connecting from windows. ian is my Linux home directory user. I generally set the password the same as my Linux user password.
  22. You should normally just click Start and then Run (or can use the Windows key + R) and it will bring up the run dialog. In here, put: \\x.x.x.x\username and it will then ask you to provide username and password details. Replace x.x.x.x with the IP of your Linux machine, and username with your username on the Linux box. Homes by default are not browseable, and it's why you don't see them.
  23. Providing it still exists in Mageia, install the drakwizard package, and you can then use MCC to click and configure Samba easily enough. However, the default packages should install and configure samba enough for you to be able to access your home directory. In terms of network name, not entirely sure what you're on about - if you mean workgroup, then you configure whatever you want, best bet is to make sure that the workgroup on the Windows machine and the Linux machine are the same. The workgroup will show when you browse under Network Neighbourhood. The share is just as I put, with home directories there is nothing to configure, later you just connect to \\x.x.x.x\username (in my example I put ian). If you are just mapping drives, or connecting with Start, Run and then typing like what I've put here, then the workgroup you won't need to worry about.
  24. That's about your only way, with samba configured and running on the Linux Machine. I do similar to this. I have my user "ian", which has the home directory /home/ian. My samba is configured to allow the users to connect, of course to \\x.x.x.x\ian from the Windows machine (where x.x.x.x is the IP of your Linux machine). I then give my Linux username "ian" and the associated password so that I can connect. All the work you do then on Linux will be under your home directory, so you won't have to store it anywhere else. If of course you want others to access it, then you would have to store it in another place and allow either public access (eg: without authentication - not secure), or configure a specific share that everyone will have access to once you add the users. They can then authenticate with their own username/password to access the files. I have the first method I suggested using my home directory, because I'm the only user, and so makes more sense and keeps things simple.
×
×
  • Create New...