alexpank

Sorry, I wasn't 100% clear. I'm using scim in KDE, and can get Korean out of it (like this 냉 - I hope that's not something offensive...) AFAIK, the ~/.i18n file is a user-related file, rather than just skim/scim.

I don't know if this will help you much, because it relates to Japanese and not Korean, but I'll put it out there anyway. I found that I had to edit/add the ~/.i18n file to get this going properly. Mine currently looks like this: LC_TELEPHONE=ja_JP.UTF-8 LC_CTYPE=en_GB.UTF-8 LANGUAGE=en_GB.UTF-8:en_GB:en LC_MONETARY=ja_JP.UTF-8 LC_ADDRESS=ja_JP.UTF-8 LC_COLLATE=en_GB.UTF-8 LC_PAPER=ja_JP.UTF-8 LC_NAME=ja_JP.UTF-8 LC_NUMERIC=ja_JP.UTF-8 LC_MEASUREMENT=ja_JP.UTF-8 LC_TIME=en_GB.UTF-8 LANG=en_GB.UTF-8 LC_IDENTIFICATION=ja_JP.UTF-8 LC_MESSAGES=en_GB.UTF-8 [b]GTK_IM_MODULE=scim QT_IM_MODULE=scim XIM_PROGRAM="scim -d" XMODIFIERS=@im=SCIM[/b] Note that I'm using scim and not skim, too. I've used it for a while now and have had no trouble with it so far. Hope this helps you a little.

So, is the happy man's external drive NTFS, or not? Alas, I fear not. Sorry for muddying the waters. That'll teach me for having my brain still set to "stunned" when I type something... Also, favar, I didn't mention that my fstab looks like that because my HDD happens to be at /dev/sda5. Yours might be somewhere else. However, I don't have any experience with NTFS in Linux, so you are probably better off listening to the advice of someone more knowledgeable.

What, so I did all that fiddling for nothing?! Argh... Oh well, it (apparently) works, so I'm happy :D

The other thing you could do, to save yourself from having to type all that in every time, is to edit your /etc/fstab (after backing it up, of course). I'm using a 120GB Buffalo, and the relevant line in my fstab looks like this: As you can see, this mounts it to /mnt/removable-2 (I've got something else on /mnt/removable), allowing users to mount. Check out the man page for mount (man mount from the command line) for what the options mean. Then what I did was to put mount /mnt/removable-2 in my ~/.bash_profile, which mounts it automatically when I log in. Hope this helps a little. Alex

Ahh, I had a funny feeling that I had the wrong end of the stick. That sure is an annoying problem, though. Why can't these programs just read our minds and do exactly what we want them to, dammit?! I hear you on that one, seaeagle. I also hope that they'll bring at least the file size one back.

Hi Seaeagle, I feel your pain about being on dial-up. It's agony knowing that there's all this awesome software out there to try, and then finding out that it's a 200MB download... From what you're describing, it sounds like MCC is automatically selecting dependencies. I'm not sure if you can get around MCC selecting these automatically, but I would recommend that you don't. Sometimes certain versions of a program will not work unless a particular version of another program installed. You could be lucky and have it work, but this is not always the case. What I used to do was to try to select only the packages that would download in the time I could spend online, including their dependencies. Unfortunately, this means that packages with a lot of deps, or with large deps, inevitably get pushed to the bottom of the pile a lot (e.g. KDE basic packages). Another thing you can do is download the packages with an FTP program (I like gFTP) and then do your updates from the command line with either urpmi or rpm. If you really want to install an update without the recommended dependencies, I think you can only do it from the command line, with this: rpm -U --nodeps /location/of/package/foo.rpm Hope this helps a little (and that I haven't misunderstood your post after that).

The other thing you can do is go to the Control Centre > Software Management > Select where packages are downloaded from..., and then select the installation disc. Clicking Edit... will tell you where it has been put (probably where ianw said it would be). You can then use your favourite method to remove the copy, and click Remove in the Control Centre window to stop your computer from looking there. Then all you have to do is use the Control Centre or urpmi to add the DVD as a removable source.

I'm not sure if this would fix your problem or not. I'm using 2007 and it worked for me, so it might be worth a try. For what it's worth, I didn't have any sound at all in youtube, and now it works fine. There are also a couple of other solutions suggested further up in the thread, so they might be something to try if updating Flash doesn't work. Hope this helps you a little.

Hi everyone, Firstly (somewhat OT), very belated thanks to Gowator for his suggestion in this post - I am now able to use Linux without any fiddling around with keyboard or BIOS settings at all, just by changing to a keyboard that is not a hub itself. Now to the main part of the problem. It seems to have been solved, but I'm still a little worried/curious. I have an internet connection through NTT (Japan). It's a PPPOE connection, connecting to my Buffalo (Melco) LGY-OCI-TL LAN Board through an NTT-supplied ADSL Modem (MS5-SPLR). I set the connection up in MCC as a PPPOE connection, and can connect to the internet without any trouble (the connection is established during startup). However, after about 25-30 minutes, the connection would died for some reason. The connection was still shown in the system tray as being up, but I could not use the internet in Firefox and urpmi could not connect to RPM servers. I found this post and added the line ianw1974 suggested to /etc/modprobe.conf. This did not solve the problem. Also, /etc/resolv.conf contains two entries when the connection is up, but only one when it goes down, and the entry that's there when the connection's down is different from both the entries that are there when it's up. Following arctic's advice, I locked /etc/resolv.conf, which seems to have fixed the problem (I'm now up to 46 minutes connected, which is a record). I have a couple of questions to do with this. Firstly, should I take the line out of /etc/modprobe.conf again? Secondly, even though the problem is apprently solved, could there be something else that doesn't work that I just haven't come up against yet? Thanks for your attention. Alex

Also not trying to be smart, but I thought the OP said that he couldn't connect to the internet. Archie, what kind of internet connection is it? (Sorry, this probably exposes my ignorance more than anything...)

Thanks for the advice, Gowator! I'll have to try another USB keyboard and see if that works. Unfortunately, there's no PS2 port, so I can't try that... This is the same that I had experienced with Windows when using somewhat older hardware. Because the BIOS doesn't detect anything USB at startup, it has to wait for some software to load in before anything USB (keyboard, mouse, hub, memory card reader, etc.) will begin to work. I have not used a USB keyboard with Linux though. Edwardp, the BIOS finds my keyboard fine, but I either have the choice of being able to use it in LILO and not use it in Linux (which means I can boot in Windows), or being unable to use it in LILO (meaning I'm stuck with Linux) and able to use it in Linux. It'll be interesting to see what happens with a non-OEM keyboard. Only good things, I hope. In any case, I think I've accidentally hijacked the thread, so I'll continue this somewhere else when further developments arise :)

I'm sorry to hear about everyone's problems with 2007. Just for another point on the graph, the only trouble I have had so far has been with the USB keyboard not working until the kernel fires up, which made installation 'interesting' (I had to set the root password and set up users after installing). Having said that, I had the same trouble with 10.1, so I think it's this keyboard. Damn.* I have to agree with ianw and AJ, though - it is pretty darn stupid that hardware that was supported in not one, but two previous versions is now suddenly unsupported, as if by magic. As they say in the classics, WTF? * Caveat - I've not been using 2007 much because it is rather slow on the small amount of RAM I have at the moment. Be prepared for the potential of a swift change in tune once I get some more RAM in this old crate. ;)

True, true. Both the literal subject matter and the allegorical subject matter are serious. Alas, I think you were a little before my uncle's time. I'm not sure how old he is, but I think he would still have been at high school/tech for a lot of the time you were in RAAF. Nevertheless, you may have crossed paths at some stage :) On another note, sorry to read about your troubles with 2007... Alex

Yankee, that solution might work OK for you, but I'm sure that there are many other users out there who would not be able to "click where [they] knew stuff was" and fix things up. Some might learn from the experience, reinstall and think twice about doing the same thing again (whether that's logging into the GUI as root or doing whatever it was that killed their system), but there are many people who would say 'What is this useless system? I'm going back to Windows' and abandon Linux. You might be resilient and/or patient, but not everyone is. This is especially the case with a distro like Mandriva, which prides itself on a reputation for being easy to use even for beginners. You don't like having to dig through thousands of files to find out what's wrong? That's how Linux works sometimes. I had to do the same thing to work out how to install a Japanese IME in Mandrake 10.1, and no amount of root GUI would have fixed that for me. What I'm saying is, a root GUI can be great for some things, but there are always other, safer ways of doing things. Why not do what ramfree does and launch programs you want to run as root from the CLI? It's not that hard; a lot of the time all you have to do is punch in the name of the program, hit [Enter] and there you are. Yes, there are cases where this doesn't work, and it does depend on your system being set up correctly, but it's worked well for me so far. By the way, with the whole 'no root password' thing - I had no choice but to do this when I installed MDV2007 on this computer. I'm using a USB keyboard that doesn't work in Linux without legacy USB support disabled, which meant that to install Linux, I had to do it with mouse only. No way of typing in a root password there. Of course, I set one up once I got things up and running and was able to do so, but without the option of installing with no root password, I wouldn't have been able to install at all. I agree that it is a security risk to be able to install with no root password, but is it worse than using the GUI as root? There are some cases where you need to be able to install without a root password, but are there any cases where you need to be logged in to the GUI as root?

AussieJohn, unless I'm reading Gowator wrong, I think he is joking about the microwave thing, using it as an analogy for being able to login into the GUI as root. I didn't know about you being in the RAAF! I have an uncle who was in a similar area of the RAAF (I think) down in Sale and other places :) Small world, huh!

You know, Gowator, I was having this discussion just the other day about why my ATM card should need to have a PIN on it. It's such a drag to have to key it in all the time, and I never lose my card, so why should I have to have this inconvenience foisted upon me? I probably shouldn't weigh into this debate (I just wanted an excuse to use the word 'foist' in a post), but there are safeguards that are there for a reason, and I agree with Gowator that door locks on microwaves and restrictions on root logins to the GUI are but two examples. Anyway, if you're smart enough to know how to safely use a microwave oven with the door open, surely you're smart enough to be able to override the device that stops you from doing that? By the way, any particular reason for the Persian/Tabby mix?

I can help with Japanese (nihongo) if anyone needs it :)

Awesome! Thanks heaps :) Now if I could only get this stupid USB keyboard to behave, everything would be perfect :S

Thanks for the speedy replies, guys! Ilia_kr, I'm glad for what you said about KDE, cos I like using it better, although this is probably just because it's what I'm used to. I've fiddled around a little bit with some of the other DEs, but not a whole lot. But now that I have a fast internet connection, look out! By the way, you said that you were mixing RAM speeds and the clock rate was set to the lowest speed (100hz). So does that mean that if I have two PC133 128MB modules, the clock rate will go up to 133hz, assuming the m/b supports it? I'll post back about how it all goes. Thanks again :) Alex

Hi everyone, I just downloaded and installed Mandriva 2007, which looks really sweet :) ... eventually. You see, I'm running it on a rather old PC (566 MHz) with only 64 MB of RAM. I was running 10.1 on a computer with a slower processor (about 350 MHz or so, I think) but more RAM (I forget how much) and it was so much faster. I've seen in other threads that Linux loves RAM - there's probably some kind of joke about animal husbandry you can slot in here, I'll leave it to your imagination. Anyway, getting to the point, I've been looking a bit into getting more RAM. I have no idea what motherboard I have - is it possible to find out without opening the computer up? But the RAM that's in there is apparently a single 64MB PC-100 SDRAM module. I saw it with my own li'l eyes and also confirmed it through this site. The computer's an NEC Valuestar VE56H/35C or D that I got from a friend. Checking on that same site, it says that you can increase the RAM to a maximum of 256M, presumably with two 128MB modules. This is where my question comes in. The site says you can throw in PC-133 modules (but only if you have really good aim; most people have to put it in carefully :D) but I'm wondering if this is really OK, given that there is a PC-100 module in there at the moment. Can anyone confirm that I'm not going to kill my computer by using two 128MB PC-133 modules instead of the currently-installed 64MB PC-100 module? Many thanks! Alex

My hard drive has done this to me ever since I put Mandrake 9.0 on. It'll do a small read/write (can't remember which) at intervals of a few seconds (always the same amount of time, but I can't remember exactly how much). I always just assumed this was something to do with the different way the filesystems work under Linux, but I could be wrong. I've got two hard drives installed, hda with Mandriva and hdb with Win2k (NTFS), and hdb never does anything like this - most of the time it sits there doing nothing unless I check out something on that drive, which is rare these days. I don't really have a solution, but it might be worth installing gkrellm or something like that so that you can see if the disk activity is regular, as mine is, or more random. And can anyone confirm or deny my theory that regular activity like this is simply a feature of the filesystem Linux uses?

The other thing you could do is install SCIM. From memory, it has a Kazakh IME. I'm no user of Kazakh, so I can't tell you how well it works, but it might be good short-term solution. Should be in either main or contrib repository, and you might need scim-tables too - try googling for scim to see what turns up.

How exactly did you install it? Installing via urpmi (usually the best option for Mandrake) should set up menu entries and so on, but even installing from source should give you something when you enter kget from the terminal. Does anything happen if you type kget into the Run box (Alt+F2)?

Just read through the posts again and noticed that I only half answered your question. What you need to set up your permissions is chmod, a lovely little utility for changing read, write and execute permissions for files, and possibly chown, for changing who owns all the files. Basically, what you want to do is give all the files you don't want accessed to root or an admin or something like that: chown [I]admin[/I] * You can either do this for each directory, or go to the root directory and do chown -R [I]admin[/I] * Only thing is, this might stuff up some of your permissions and ownerships that are already set up. I can't remember exactly, but I think when you install Mandrake, everything except the /home directories is set up to be protected from being written to by ordinary users. If that's the case, then all you should need to do is use chmod to let them get to /mnt: chmod -r a+rw /mnt Now, that's a bit more complete (but possibly incorrect or inadvisable - you might want to check out the man pages for chmod and chown to make sure that that's what you really want to do for your system, and failing that, it might be an idea to give someone a bit more knowledgeable than me the chance to run in and say "What the heck did you tell him to do that for, you nincompoop?!?" Alex (still on waterwings)