[gobolinux-users] Wheel Mouse -- MouseInfo and utmp/Shutdown

[Lucas C. Villa Real]

On 2/6/07, John E. Rose <jerose54 at gmail.com> wrote:
> I've just started using GoboLinux, and I had the same problem I have seen
> mentioned in the Knowledge Base regarding the mouse wheel. This was strange
> becuase I could see during boot-up that the mouse was found and identified
> correctly. After some digging, I think I found the problem in the "mice" array
> (or whatever it's called in Python). I believe that for key:
> ("Generic - 3 Button Mouse (PS/2)"):
> the entry:
> ("ps/2", "PS/2", "psaux", 0, "generic3ps/2"),
> should be:
> ("imps/2", "IMPS/2", "psaux", 1, "generic3ps/2"),
> or something similar. This fixed the problem for my mouse, anyway.

Hi John,

Thanks for the update, and sorry for the late reply. Indeed, this
makes sense. I've updated our MouseInfo script in the CVS, just
replacing "imps/2" by "imps2", which is probably what you used there.

> I also found that the Reboot and Shutdown scripts were not being called after
> first reboot or shutdown. Removing the /System/Variable/run/utmp file on
> shutdown in the (Shutdown script) fixes this problem, but I'm not sure this is
> the appropriate action. Any ideas about what's going on here?

I was wondering here whether it was correct to remove these files at
boot, but I just saw the following line in our default BootUp:

Exec "Creating utmp and wtmp..."              CreateChmod 644
$goboVariable/run/{u,w}tmp

So, I guess it's fine to remove utmp on reboot. wtmp, as far as I
know, should not be touched, though. Is that correct? I never did pay
too much attention to these /var files.

-- 
Lucas
powered by /dev/dsp