Linked by Thom Holwerda on Mon 18th Jul 2005 16:23 UTC
Mandriva, Mandrake, Lycoris TuxMachines has a quick look at Mandriva Linux 2006 Beta 1. This beta has been quietly released over the weekend; DistroWatch lists the mirrors where you can download. You can see the full package list here, and a screenshot gallery here.
Thread beginning with comment 6660
To view parent comment, click here.
To read all comments associated with this story, please click here.
AdamW
Member since:
2005-07-06

Oh, yeah, someone mentioned on Cooker list the menu item had disappeared, I never use it and that's not my responsibility so I didn't follow it too closely, but I guess someone's aware of it. Using the MCC wizard to mount a Samba share mounts it in the traditional way, by adding it to fstab where it will be mounted by mount -t smb, so it can be persistent and it will store the username and password if required. You can always do this operation manually, of course, I'm surprised you didn't do that already ;) . No need for autofs if the share is always available, just have it mounted at boot time by putting it in fstab.

Since you have Chinese input you're running into the known bug with Acrobat; it doesn't happen if you don't have a Chinese / Japanese locale defined (and consequently have SCIM loaded), which is why it wasn't caught sooner. Fortunately there's a fix. Edit the file /usr/lib/Acrobat7/bin/acroread (it's a plain text file) and add these two lines right after the second line (which should just be a # symbol on its own):

GTK_IM_MODULE=xim
export GTK_IM_MODULE

save the file, exit your editor, and you should find Acrobat now works. The problem is that due to a compiler mismatch, Acrobat will not work with our default input method for CJK locales, which is SCIM.

Reply Parent Score: 1

Member since:

Thanks for the tip on Acrobat 7.

With regard to mcc and samba mount, I have checked it out. However, I think there's still the following problems.

1) password are stored, not too comforting for admin, especially if you have a 'well-defined' security policy already in place, (normally dictated from someone higher up)
2) Whatever username and password being entered at mcc, will only reflect access right of that particular user. if you have more than one person who share the same workstation or simply having a few roaming users, this will quickly turn out to be a nightmare since everyone should have different level of access right.

Over the years I haved tried pam_mount etc...(there was another one which name I can't remember now). wasn'too happy with it as well. Guess there's this long wait till nfsv4 is production-ready.

Reply Parent Score: 0