ianw1974
-
Posts
14090 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Forums
Events
Posts posted by ianw1974
-
-
Thanks, almost enough detail for me....
Do you mean /usr/lib rather than /usr/local ??
When I execute the tar command, will it automatically create a directory in /usr/? for the firefox 9 files?
Thanks -- Roger
No, I mean /usr/local
/usr/lib is for libraries only and better not to unpack binaries here. And if you do as I wrote, it will create a directory called firefox under /usr/local like in my example that I put in my post.
-
I am a /opt man myself B)
Sure, another fine location ;)
-
As you've used Kubuntu 11.10 which is October 2011, I would suggest using the latest Mandriva 2011 available and simply trying if nobody has this particular camera. I haven't a Canon, so can't help you there. Sometimes it's just worth trying the latest release and see what happens.
-
Hi Roger,
Here is an example from my download:
ian@jasiek ~/Downloads $ tar xjf firefox-9.0.1.tar.bz2 ian@jasiek ~/Downloads $ cd firefox ian@jasiek ~/Downloads/firefox $ ls Throbber-small.gif icons libsoftokn3.so application.ini jsloader libssl3.so blocklist.xml libfreebl3.chk libxpcom.so chrome libfreebl3.so libxul.so chrome.manifest libmozalloc.so mozilla-xremote-client components libmozsqlite3.so omni.jar crashreporter libnspr4.so platform.ini crashreporter-override.ini libnss3.so plugin-container crashreporter.ini libnssckbi.so precomplete defaults libnssdbm3.chk removed-files dependentlibs.list libnssdbm3.so run-mozilla.sh dictionaries libnssutil3.so searchplugins extensions libplc4.so update.locale firefox libplds4.so updater firefox-bin libsmime3.so updater.ini hyphenation libsoftokn3.chk ian@jasiek ~/Downloads/firefox $
in the last directory listing is an executable called firefox. So wherever you unpack this, is where you would create the link for the executable. For the icon use the path icons/mozicon128.png from within the firefox directory.
I unpacked in /home/ian/Downloads/firefox, so for my shortcut the program would be:
/home/ian/Downloads/firefox/firefox
and the icon would be:
/home/ian/Downloads/firefox/icons/mozicon128.png
of course, ideally you would unpack this in for example /usr/local. So to do this:
su (enter root password when prompted) cd /usr/local tar xjf /home/ian/Downloads/firefox-9.0.1.tar.bz2
then your paths would be /usr/local/firefox/firefox and /usr/local/firefox/icons/mozicon128.png.
-
The alternative is simple, as willie pointed out, just download the tar file from Mozilla and extract this somewhere. Then it's just a case of creating a shortcut to the firefox executable inside here and you're done. No need to go searching for an rpm and getting into a dependency nightmare of which you've just found. Alternatively, updating your system to a newer release of Mandriva, and you'd have Firefox 9 - but a bit extreme for just changing the browser.
-
I have Dropbox instead of Ubuntu One, then I'm platform independant. Can access via a web browser, and the dropbox client for sync of files is available for most distros without any problems. 2GB free space, if I or someone you know who has dropbox was to invite you, we/you and your friend would both get an extra 256MB.
Had two Android phones, one Samsung (private), one HTC (work) which now is superceded by iPhone 4S (work - thanks for the present). Prefer the HTC, implementation of Android with HTC Sense is great user experience. Manage to survive disconnected, although with the phones I can still connect, but then it's just for email mostly.
-
What you've done is install Apache, MySQL, PHP and Perl all in one, without separately installing the packages with urpmi or MCC :)
-
Hey, thanks for the post and sorry nobody was able to help you, but you managed to get it sorted
and many thanks for providing the feedback with the solution, that way can help other members if they search for the same problem.A virtual
for you :) -
Looking back the working system was a desktop kernel and the problem one was a server kernel which I ignored at the time as I thought that the only difference in the server kernel was support for PAE (Physical Address Extensions) but it may have security measures built in that require the full path to usb_modeswitch in udev rules.
We'll never know until someone files a bug report so that the developers can look at the problem.
It was actually the other way around :) server version worked, but desktop one didn't. His laptop has server kernel, and his wife's that failed with the desktop one. Although, the path would be better off provided by default, that way the problem wouldn't occur irrespective of kernel or other potential measures be it the security level or something else.
-
@ ken, "By the way I do have the utmost respect for the members here and the help they give or I would not be here."
I never doubted that for a second. :-)
Cheers. John.
Me either :) btw Ken, agree with you about the bug, although it should be dead easy to fix, if they just fix the rule to have the full path like we did here, then it would work for all installs :)
But is a weird one in that it works on one and not the other without the amendment.
-
The decision about where to ask about a problem is chosen by the user (dude67) in this case, so he has the right to ask it here, or on the Mageia forums or on any other Linux forum to get a solution to his problem. As Mageia is Mandriva based, then there is still a reason why he has chosen to ask his question here or more importantly he asked it here because he has been frequenting here for a long time now and is a regular member like most of us here. Anyone who uses google, will find it. A quick search of google proves this:
simple, few keywords of mageia huawei e367 and this site provides the first search results. I didn't force google to do it. Anyone using Mageia would then find these results. If dude67 is happy asking his question here about another distro, and gets his answer/solution, that's great
if not, he can always ask it in alternative forums. I personally, generally start here, and try elsewhere if I don't find a solution, but then the majority of the ones I've asked of late have been more complex :) -
Sweet
Glad you got it sorted. Usually the path is required, because normally as users, we have various environment variables set that allow it to work for us. But things like udev, etc, won't have paths set up, and so requires it being provided in it's full entirety :)
So I'll take those virtual
and change them into real ones located in my fridge :) -
Yes, exactly as it might not find it otherwise. Needs to be the correct path as per your installation, it might or might not be /usr/sbin.
-
Did you check that the full path to usb_modeswitch was put in the udev config file? Because previously this was not set, and can be a reason as to why it doesn't work automatically. You will probably need to put /usr/bin/usb_modeswitch or whatever the path is depending on where it is.
locate will work only if the locate database has been updated, so the database could be out-of-date, if updatedb was not run first. But we can forget about the modem-modeswitch, but check the full path has been added like I mentioned earlier for usb_modeswitch.
EDIT:
I installed usb_modeswitch on my system, and so this is my path:
jasiek ian # which usb_modeswitch /usr/sbin/usb_modeswitch
so if I was editing the udev config, I'd put all of this in there, instead of usb_modeswitch on it's own without the full path.
-
Or if not installed, check if it can be installed with urpmi.
-
The modem-modeswitch could be in a different place, you could locate it easily enough:
find / -name modem*
different distros put things in different places. But also, with usb_modeswitch, you might have to put the full path to it, so for example, /usr/bin/usb_modeswitch if that is where it existed.
-
I don't know if what I did was done correctly. It didn't help, so could someone see there's something wrong with this. I want this dongle to automatically be recognized as a modem instead of harddrive or cd rom.
I wrote a new rule to udev. Should this rule automatically run the command whenever this dongle is plugged in?
# cat /lib/udev/rules.d/huawei_e367.rules SUBSYSTEM=="usb",SYSFS{idProduct}=="1446",SYSFS{idVendor}=="12d1",RUN+="usb_modeswitch -c /usr/share/usb_modeswitch/12d1:1446"Maybe try formatting the same as the guy in the link that was provided by Ken, does it work any better?
SUBSYSTEM=="usb",SYSFS{idProduct}=="1446",SYSFS{idVendor}=="12d1",RUN+="/lib/udev/modem-modeswitch --vendor 0x12d1 --product 0x1446 --type option-zerocd"do you have modem-modeswitch on your system? Or maybe you need to put the full path to usb_modeswitch. And is /usr/share/usb_modeswitch/12d1:1446 a file? Just curious.....
-
Is there a usb-modeswitch-data package? I have this under Debian/Ubuntu based systems, maybe that would help.
-
Try installing usb-modeswitch (if that package name exists for Mandriva). This is because some USB devices are known as "zerocd" so that when you plug it in in Windows, the drivers can be installed, and so the USB device appears as storage. Installing usb-modeswitch solves this problem, and will save you writing UDEV rules, or amending them.
Easier option :)
-
What size are your partitions? How big?
-
Updated kernel, updated packages for web server, later versions obviously than Mandriva 2010. Some good reasons for using 2011 instead of 2010.
Other good reasons for using 2010, in case 2011 doesn't support your hardware, therefore would be better to stay with 2010. Updates for 2010 will still be coming for at least another six months. Or at least should be if they kept everything the same as the previous owners.
Need Mandriva supported longer than PWP, choose Enterprise Server, but it'll cost you a bit more obviously.
-
Mandriva does support native Linux document formats. If TimeFrame doesn't, that doesn't mean that Mandriva is at fault just because of one feature.
-
Mostly good. You have one reallocated sector on the second test results, but other than that any error values are zeros. Take a closer look, you'll know what to look for, and compare against the results I cut out from your failed disk on the other post, you'll see some of the values I chopped out for you to focus on.
-
You do have a problem with that old disk:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0033 073 073 036 Pre-fail Always - 1111 7 Seek_Error_Rate 0x000f 079 060 030 Pre-fail Always - 94882296 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 103
so you were right to replace it. But also, considering the reallocated sectors and uncorrected, I'd not use that disk for anything important.
Updating RAID set
in Hardware
Posted
It would be easy enough as you'd need to remove the faulty disk, and then add the new one. Add a partition to it marked as Raid Autodetect. Edit /etc/mdadm.conf so that the second disk is missing. Then you will need to add it to the array after the system has started. The array will then rebuild on the new disk. Then you edit /etc/mdadm.conf again to add back the config as it was before with the second disk.
Of course, if you're replacing with a disk of the same size. I know you want larger. Therefore, you'd create Raid1 on the 1TB disk with the second disk missing, then LVM inside this. Copy the data to the disk. Then add another 1TB disk later similar in my procedure for replacing a faulty disk and adding it to your 1TB array.