theYinYeti

As root: service haldaemon restart Yves.

And then File > Open file... > select the xpi file. Yves.

I misread the manuel, even though I read it many many times. I'm at fault: -path "Path rep" must be written -path "rep" instead. Yves.

Welcome to these forums! Although I can't tell the details, I think your issue is related to the xorg.conf file, either in the "Module" section, or to the options of your video driver in the related "Device" section. Yves.

Yes it does.I used to find it great and thus installed it, but I haven't saved an HTML file on disk in years, and so it happened that I never actually used it. Yves.

Hello, I want to use Unison in batch mode for a given path without recursivity. What I have so far does not work. Here's my test config: $ find /home/yves/test /home/yves/test/ /home/yves/test/client /home/yves/test/client/var /home/yves/test/client/var/unison /home/yves/test/client/var/unison/default.prf /home/yves/test/client/var/unison/backup /home/yves/test/client/share /home/yves/test/client/share/rep /home/yves/test/server /home/yves/test/server/share /home/yves/test/server/share/rep $ cat /home/yves/test/client/var/unison/default.prf sortbysize = true group = true owner = true times = true perms = -1 I then synchronize client/share and server/share: $ UNISON=/home/yves/test/client/var/unison \ unison default /home/yves/test/client/share ssh://yves@localhost//home/yves/test/server/share \ -ui text -dumbtty \ -backupdir /home/yves/test/client/var/unison/backup \ -logfile /home/yves/test/client/var/unison/log \ -sshargs -x From there, I create a file in the client's "rep", and a non-empty sub-directory in the server's "rep", and I try and synchronize both non-recursively using the path and ignore parameters: $ touch /home/yves/test/client/share/rep/repfic $ mkdir /home/yves/test/server/share/rep/reprep $ touch /home/yves/test/server/share/rep/reprep/reprepfic $ UNISON=/home/yves/test/client/var/unison \ unison default /home/yves/test/client/share ssh://yves@localhost//home/yves/test/server/share \ -ui text -dumbtty -auto -contactquietly -silent -batch -terse \ -backupdir /home/yves/test/client/var/unison/backup \ -logfile /home/yves/test/client/var/unison/log \ -sshargs -x -path "Path rep" -ignore "Path rep/*/*" I expected rep/repfic to go to the server, and rep/reprep (but not rep/reprep/reprepfic) to go to the client. Instead, nothing happens. Do you understand why? Yves. //EDIT Out of curiosity, I looked at my /home/yves/test/client/var/unison/log file, and Surprise! here's the content: UNISON started propagating changes at 19:40:40 on 26 Feb 2008 [BGN] Copying rep/repfic from /home/yves/test/client/share to //localhost//home/yves/test/server/share [BGN] Copying rep/reprep from //localhost//home/yves/test/server/share to /home/yves/test/client/share [END] Copying rep/reprep [END] Copying rep/repfic UNISON finished propagating changes at 19:40:40 on 26 Feb 2008 Synchronization complete (2 items transferred, 0 skipped, 0 failures) This is what I expect! Why is the result different? //EDIT 2 I tried the newer version 2.27.57 from source. Now there's not even a log file to agree with me :( Once the -auto -contactquietly -silent -batch -terse options are removed, the software just says: Nothing to do: replicas have not changed since last sync.

I'd like to try the Shift Switcher plugin from Compiz. I did and it works, so I wanted to change the bindings to use Alt+Tab instead of Super+Tab. I wasn't able to type any combination with Tab inside, so (big error) I tried another random key: %. Here's the situation now: - When Shift Switcher plugin is enabled, I cannot type %, or whatever other random key I use instead. - I'm not able to change this binding to Alt+Tab. - I'm not able to revert this binding to Super+Tab. - Unlike many other plugins', Shift Switcher preferences are NOT in gconf-editor. So my question is: Where are this plugin's preferences stored? I'm currently running "grep -rinF super+tab ~/.[a-zA-Z]*", without success so far... Yves. SOLVED: It is in ~/.config/compiz/compizconfig/Default.ini Changes to this file seem to be immediately taken into account. Only non-default values are there, though, so if you want to know the key name for which you want to change the value, you have to change it with the GUI first, so that it appears in the file. Eg: With the GUI, I chose Alt+Esc and Alt+Shift+Esc, which resulted in these values: [shift] as_prev = <Shift><Alt>Escape,Button0,,0,false as_next = <Alt>Escape,Button0,,0,false I changed these to: [shift] as_prev = <Shift><Alt>Tab,Button0,,0,false as_next = <Alt>Tab,Button0,,0,false And now I have the shortcuts I wanted :)

Yesterday morning, I decided to try Compiz, at last. I liked it, and actually found many things good for productivity. gdm (Xgl) started OK, and compiz ccp started OK too. Yesterday evening, I did my occasionnal urpmi --auto-update --auto-select. Now: - Either I update-alternatives --config gl_conf and choose "ati", and then Xgl starts, but Compiz fails; - Or I update-alternatives --config gl_conf and choose "standard", and then Compiz starts, but Xgl fails after logout. The solution so far is to choose the "ati" set of GL libraries, and setup my Gnome session to start ~/bin/compiz.sh, the contents of which is: #!/bin/bash export LD_LIBRARY_PATH=/usr/lib compiz ccp & But I didn't need this trick before. Why now? All I know is that kernel changed from 2.6.22.12-laptop-1mdv to 2.6.22.18-laptop-1mdv, but it is probably irrelevant since the problem remains with the former kernel, so it must be because of another update... I have no idea what else was updated. Do you think there is any side-issue or risk with using the above trick? Yves. [edit:]BTW, the compiz error (without the trick) is: "Fatal: GLX_SGIX_fbconfig is missing".[/edit]

Of course you won't boot both versions at the same time. However, don't forget that "suspend to disk" is often configured by default to save the computer state to swap, thus rendering this swap still used although the OS is shut down. Conclusion: if you use the "suspend to disk" feature, don't share the swap partition, or be very sure of what you do else you'll break some filesystems beyond any possibility of recovery. Yves

You could try adding the "task list" to your panel. I think it disappeared and that's why you don't see applications anymore. Yves

Besides, computer science is a broad subject, and hardly any programmer can be good at kernel programming, audio/video programming (or even those two together), office programming, etc... at the same time. I wish I was, but... no. Yves.

Not to mention X11 remote display, that was invented by Microsoft some years ago, right :lol: ? Yves. (Joke of course: remote display was reality and truly usable for hundreds of users simultaneously more than 10 years before MS announced it could be done in Windows... for up to... 4 users maybe?)

I suppose the build essentials (whatever those are...) would be installed by issueing the following command as root: urpmi rpm-build flex bison That's mostly for C, though. Yves.

Well, there's always the solution I pointed kilimanjaro at, that is creating a line in the /etc/fstab file. That's because HAL settings are ignored when there's such a line, hence you have total control on the mount point (which must then exist permanently) and on the options used. So find your UUID (let's say it is "ABCD-EFGH") with this command: find /dev/disk/by-uuid/ -lname "*sdb1" -printf "%P\n" and put this line in /etc/fstab: UUID=ABCD-EFGH /media/TRAVELDRIVE vfat,auto umask=0,users,noatime,noauto 0 0 Hopefully, you should be able to mount and umount at least this one particular device... Yves.

That's interesting. I think we should ensure the drive can be mounted by root first, and then take care of normal users. A previous post from you indicates that those are the allowed options: 'ro', 'sync', 'dirsync', 'noatime', 'nodiratime', 'noexec', 'quiet', 'remount', 'exec', 'utf8', 'shortname=', 'codepage=', 'iocharset=', 'umask=', 'dmask=', 'fmask=', 'uid=', 'flush'. This all seems quite complete to me. I wonder what this "Invalid mount option" is... Process accounting doesn't seem to show parameters. Does anyone know how to debug this situation? Yves.

I know it is not a perfect answer, and I'm sure there is a simpler solution. But this may help you: http://wiki.mandriva.com/fr/Personnaliser_le_clavier I'm not aware of any translation, but Babelfish or Google might help in this area... Yves.

Could you plug your USB drive in, and in a terminal window, type: mount If you don't see any line starting with /dev/sdb1, then please give the error message (if any) of this command: gnome-mount -d /dev/sdb1 Yves.

First, I want to warn you. It seems you are logged in as root. This is very dangerous, and strongly advised against: beginners should especially not login as root because of the security risk that is, and experienced users don't do that because they know it is not needed :) Next, let's introduce some basic concepts. In Linux, as in any Unix system, most peripherals are shown under /dev as if they were files. There you can locate scanners, printers, modems, disks, sound cards, mice, keyboards, and so on... The disks (hard drives, CD/DVD drives, USB keys...) are named /dev/hdX for IDE disks, and /dev/sdX for other drives, where X is a sequencial letter (a, b, c, d...); in your case, your USB drive is /dev/sdb. On a /dev/sdX drive, partitions are then numbered, with 1 to 4 being the "primary" partitions, one of which can be "extended", thus containing "logical" sub-partitions, numbered beginning with 5; in your case, your only partition on your USB drive is /dev/sdb1. Whereas in Windows partitions are mapped to drive letters, in Unix a partition is "mounted" to the filesystem to a fixed location. Thus if you add a new device in Windows, this leads to a shift in letters, whereas in Unix hence in Linux, most of the times the existing devices stay at the same place somewhere under /media. Mounting is often done automatically for removable media (like in Windows) but it is not mandatory. From your previous post, it seems it is not done in your case. It seems to be a problem similar to that of kilimanjaro. By the way, "unmounting" or "umount" is the equivalent of Windows' "Safely remove the device" action. Now let's try the easiest things first. Are you using Gnome or KDE? If you're using Gnome, open the "System" menu, the "Preferences" submenu, and choose the "Peripherals and removable media" item. On the first tab, make sure the 3 first checkboxes ("mount...", "mount...", and "browse...") are checked. (Note that I'm translating from French, so labels may differ). Yves.

I do need that insect spray, don't I? :lol: Well, I need to see Visio files, and there's absolutely ZERO existing Linux viewer. So I wanted to try the Windows viewer which is an ActiveX for IE. Thus I first installed ies4linux, and then the viewer (installs well with Wine configured as W2K). Unfortunately, the viewer tells me my vsd files were created by a too-new version of Visio :( Yves.

As you say you don't know linux much, we'll first try to see what the hardware is and how it is detected. In your main Mandriva Applications menu, there should be a "Tools" submenu, and inside a "Terminal" item. Please execute "Terminal" (or XTerm or Gnome-terminal or Konsole or whatever it is called). This will open a terminal window, which is to Gnome/KDE what DOS is to Windows, but infinitely more modern and powerfull. Do the following steps (don't type the quotes): 1/ In the terminal window, type "cd" and ENTER 2/ In the terminal window, type "lshal >before" and ENTER 3/ Plug your USB device in, and wait 5 seconds or so 4/ In the terminal window, type "lshal >after" and ENTER 5/ In the terminal window, type "diff before after >newdevice.txt" and ENTER 6/ In the terminal window, type "rm -f before after" and ENTER Now you can close the terminal window, either by typing Ctrl+d, or "exit" and ENTER, or just closing the window ;) Please post the contents of the "newdevice.txt" file, which should have been created in your home-directory. Also please post the output of the following three commands (in a terminal window): id mount ls -l /media You can copy the output from the terminal window to the browser by simply selecting the text in the terminal window with the mouse, and then pressing the middle mouse button in the browser text-editor. Yves.

Standard install shouldn't give this error message; that you can check using Mandriva One. So: - either you have some compatibility issue with your hardware, - or you used some "unusual" installation option. Did you change advanced options about mounting, about removable devices, boot options maybe? Do you remember what security level you chose? Yves.

Looking at the sparse documentation, I think that my main problem is the dkms build that fails at each start. I uninstalled the non-working dkms module and it's now better. I still don't understand this image enough to see if there's anything else that can be enhanced. Yves.

In case anyone is still interested, I've discovered that fuse wants the mount point to be writable, so I guess a good solution is to choose a group, for example "disk" (number 6), and ensure /media/hd is group-writable for group "disk", and add "gid=6" in the above fstab options. You must be part of the group you choose of course. Yves.

I like your desktop dude67! Here's my work desktop: ROX with an abstract background from Gnome-files, and all those cool rox apps :)

I don't know with KDE. I'm mostly a gnome user. On my "salon" PC, the video card is able to output 1024x768, and I want to be able to use this resolution, but at login, I want to have 800x600. In gnome, I used the "screen resolution" configuration applet, and chose 800x600. It asked confirmation, and now I have 800x600 at login, and I'm able to display a real 1024x768 screen (not a virtual screen that scrolls). That simple... Not obvious conclusion: were I you, I'd look at the xrandr command. :) Yves.