Jump to content

ianw1974

Admin
  • Posts

    14042
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by ianw1974

  1. 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.
  2. 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?
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. Kdenlive and kino also. Lives is also a good one.
  8. There was also cinelerra, although it was advanced, every time I tried it it crashed, but then maybe that was a long time ago when my computer was not so fast. There was another that I used once or twice also, but I forget the name right now.
  9. Glad to hear it helped fix your problem :)
  10. When you extracted hplip, I expect it is here already. I googled this and found someone said he had to copy it from hplip-3.13.3 to hplip-3.13.3/.libs/ to get it to work. Perhaps try this. From my google search:
  11. No, not dead, just that we need to fix the library problems and perhaps then it will work. Please post any additional errors, then I can look at posting other ways of fixing the rest.
  12. I also found other errors in mine, fixed like this: cd /usr/lib ln -s xulrunner-1.9.2.28/libmozjs.so ln -s firefox/libmozalloc.so but anyway my Firefox is with my distro, but at least we can do the same with yours and see what happens.
  13. Incidently with mine I made a symlink: cd /usr/lib ln -s xulrunner-1.9.2.28/libxul.so libxul.so this made a symlink in /usr/lib for libxul.so and then when I do the ldd commmand again, you can see mine now reports libxul as OK. root@jasiek:/usr/lib/firefox# ldd libxpcom.so linux-vdso.so.1 => (0x00007fff16bff000) libpthread.so.0 => /lib/libpthread.so.0 (0x00007f3b8f49d000) libxul.so => /usr/lib/libxul.so (0x00007f3b8de62000) So if you do the same, it should work and not cause the error. Otherwise, post the output from my previous post, so we can then decide what to do to fix it.
  14. OK, so what you can do now, is from the command line go to /home/frank/firefox, and run ldd on libxpcom.so, something like this: ian@jasiek:/usr/lib/firefox$ ldd libxpcom.so linux-vdso.so.1 => (0x00007fff2b3ff000) libpthread.so.0 => /lib/libpthread.so.0 (0x00007f7f7a8b6000) libxul.so => not found libnspr4.so => /usr/lib/libnspr4.so (0x00007f7f7a679000) libplc4.so => /usr/lib/libplc4.so (0x00007f7f7a474000) libplds4.so => /usr/lib/libplds4.so (0x00007f7f7a270000) libmozalloc.so => not found libdl.so.2 => /lib/libdl.so.2 (0x00007f7f7a06b000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f7f79d57000) libm.so.6 => /lib/libm.so.6 (0x00007f7f79ad3000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007f7f798bc000) libc.so.6 => /lib/libc.so.6 (0x00007f7f79536000) /lib64/ld-linux-x86-64.so.2 (0x00007f7f7acf8000) from my example, as you can see libxul.so not found, but would be nice to see what yours says, so for completeness: cd /home/frank/firefox ldd libxpcom.so and post the output here. Maybe we need to install some package. It doesn't matter which version of Firefox, you need the libraries under /usr/lib, and this is what we're missing.
  15. We'd need to see the actual error message so that we could try and get it working. Perhaps its a problem with the libraries missing something, this can be checked with ldd command. Anyway, post the actual error, and perhaps we can help.
  16. I generally after installation, do the updates, install some extra programs that I need - usually vlc plus others and codecs, media conversion - avidemux, devede, dvdrip, changing the desktop wallpaper, plus other desktop customisation - if Gnome, then the themes, icons, etc however lately have Unity, so a bit difficult to change anything more now. Oh, and copy my data back if I was making a clean install and repartitioning of the disk/encryption of my partitions.
  17. It could be a DNS proxy issue. Edit your /etc/resolv.conf and give external DNS servers and see if it improves in terms of speed. You can use something like this: # Google DNS nameserver 8.8.8.8 nameserver 8.8.4.4 # OpenDNS nameserver 208.67.222.222 nameserver 208.67.220.220 and check if it's any faster. This will rule out the router having problems forwarding the DNS externally. Sometimes DNS Proxying can be a problem, I had this on my firewall at home, and this was a GBP 400-500 device which isn't exactly cheap, and you'd expect it to work better than standard home routers. Only thing I can think of at present. Try it and let us know. Also, check the router wireless settings, in case you are using some encryption settings that might not be completely supported by the particular WIFI module on your Linux system. If using WPA or WPA2, change to WPA and also encryption TKIP, as this is the basic one. Perhaps you are using WPA2 and AES. Another alternative is temporarily run the WIFI without encryption and see if it's any better to rule it out.
  18. I'll take a look at Mageia 2 as a virtual machine.
  19. I did, the first release, but it looked just like Mandriva, and I was expecting it to have it's own unique look and feel.
  20. I don't believe a lot of the ranking info over at distrowatch. Many times previously heard about the "head over to distrowatch and click to make our distro hit number 1 on the list". So in reality makes the figure misleading and meaningless. If Mageia is picking up, then that's a good sign. For me it didn't offer anything interesting, it just looked like Mandriva rebadged and I believe each distro should have it's own mark on the world - and not to just stay looking the same with a different name. Maybe it's different now, but I'm unlike to try it to find out. Of course, everyone is entitled to their own opinion and I'm sure people will have a different one than mine. All distros go through a flux of popularity at some point in their existence and some more than others.
  21. Chances are it's wanting you to manually check the disk with fsck to fix it, because it can't do it on it's own. Probably wants you to choose yes or no for fixing a couple of things. I'd expect just some filesystem inconsistences other than a physical problem with the disk, although there is always a possibility for this. You'll need to boot it in single user mode (they might call it something else in the boot menu), there might be a boot entry for this, so that you can then fix it. Alternatively, if the computer boots normally, open a terminal and su to root and then type: init 1 that's the number one, so that you can be in single user mode and fix your partitions.
  22. This is what I have on Ubuntu 10.04 LTS: root@jasiek:/home/ian# aptitude search pulse | grep ^i i gstreamer0.10-pulseaudio - GStreamer plugin for PulseAudio i libcanberra-pulse - PulseAudio backend for libcanberra i libpulse-browse0 - PulseAudio client libraries (zeroconf supp i libpulse-mainloop-glib0 - PulseAudio client libraries (glib support) i libpulse0 - PulseAudio client libraries i libsdl1.2debian-pulseaudio - Simple DirectMedia Layer (with X11 and Pul i pulseaudio - PulseAudio sound server i pulseaudio-esound-compat - PulseAudio ESD compatibility layer i pulseaudio-module-bluetooth - Bluetooth module for PulseAudio sound serv i pulseaudio-module-gconf - GConf module for PulseAudio sound server i pulseaudio-module-x11 - X11 module for PulseAudio sound server i pulseaudio-utils - Command line tools for the PulseAudio soun i A vlc-plugin-pulse - PulseAudio plugin for VLC root@jasiek:/home/ian# aptitude search alsa | grep ^i i alsa-base - ALSA driver configuration files i alsa-utils - ALSA utilities i bluez-alsa - Bluetooth audio support i gstreamer0.10-alsa - GStreamer plugin for ALSA I know package names will vary etc, but generally working OK. Just connected a USB Jabra Speak 410 device to my system which didn't work at first until I gave it a firmware update under Windows, but then it worked under Linux fine when I chose it under the input and output settings in pulseaudio. Other issues might be running alsamixer and choosing the second device and making sure it's not muted. Had to do this with HDMI and if I remember with my bluetooth headset too. You can do this as root, by running: alsamixer or by specifying the card directly: alsamixer -c 1 thats a number one. Or, if you need to identify the devices: aplay -l thats a lowercase L.
  23. From your previous post, pulseaudio is running. Did you try rebooting with the Creative device attached? This would at least mean that it is detected by the system before pulseaudio starts, and maybe (long shot) it would be detected, like I mentioned about my HDMI sound issue. Other than that, I'm out of ideas, as if the system is detecting it correctly as a bluetooth audio device, it should be showing up. Have you got the bluetooth packages installed that would recognise it as a sound device? And also the pulseaudio packages that allow bluetooth usage?
  24. Not in touch with Mandriva lately, but check under /etc/init.d and see if there is anything relating to pulse here. Normally the service is pulseaudio, but could be anything I suppose.
×
×
  • Create New...