From: Dave Houghton (davehoughton@mulinux.free-online.co.uk)
Date: Wed Dec 08 1999 - 03:56:55 CET
On 7 Dec 1999, Michele Andreoli <m.andreoli@tin.it> wrote:
>
>On Mon, Dec 06, 1999 at 08:30:45PM -0600, Dave Houghton nicely wrote:
>> Michele,
>>
>> just a couple of quick bugs for you
>>
>> in setup at first boot from floppy the VNC and TCL addons are not
>> configured
>> add VNC and TCL to /setup/order before GCC.
>
>I may, but isn't a bug. The addons list is /setup/addons and order isn't
>relevant.
Sorry about that, you are quite right. What happened is that the fake/real telnetd respawn message came up at the exact time I was going through the setup procedure and it seems to have skipped the VNC and Tcl setup. Of course it works!!. Just a suggestion... what about a check to see if the real telnetd is running and if so don't un-comment the fake telnetd line in /etc/inittab ?
>
>>
>> /usr/X11R6/bin/XF86Config incorrectly configures the pointer section of
>> /usr/X11R6/lib/X11/XF86Config (at least for PS/2 mice). This is the
>> cause of most of the problems people are having with the X11 addon as
>> the X server can't start up with incorrect mouse definitions.
>> I haven't checked this as I manually edited the config file (cloned
>> system), but it seems that there are a couple of people who don't know
>> this and you obviously loose your changes on a ramdisk system.
>
>I changed xf86config because it write in the USR section: a problem,
>when this segment is loaded from a read-only media. Then, I've created
>a link with a /etc/X11/XF86Config.
>
>Now /usr/X11R6/lib/X11/XF86Config is a symlink with /etc/X11/XF86Config,
>as in all standard Linux and cannot understand what happens. Can you
>track the bug for me?
No fractures anymore, the new X11 version works 110% (well not at first because some fool had copied his original SVGA XF86Config to /root before he updated the X11 addon. The same fool then couldn't figure out why the X server was saying there was no device definition in XF86Config when more /usr/X11R6/lib/X11/XF86Config said there was. Then the brain cells woke up and remembered that the X server looks for config file in users root before /usr/X11R6 !! Stupid computers)
Dave
muLinux U.K. mirror
>
>>
>> the fvwm-95 taskbar clock still doesn't update the time correctly.
>> Change the final %m to %M in the taskbar clock line in the fvwm95 config
>> file.
>
>An old problem. BTW, changed %m->%M.
>
>>
>> Apart from that everything installs and works perfectly (again).
>> Anything else and you can bet I'll let you know!!
>>
>> Your fractured bodily
>>
>
>Please, Dave: track for me the X11 bug and let me know.
>Michele
>
>
>--
>I'd like to conclude with a positive statement, but I can't
>remember any. Would two negative ones do? -- Woody Allen
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: mulinux-unsubscribe@sunsite.auc.dk
>For additional commands, e-mail: mulinux-help@sunsite.auc.dk
>
>
>
>
>
>
>
>
>
>
------
Dave g0mxw
---------------------------------------------------------------------
To unsubscribe, e-mail: mulinux-unsubscribe@sunsite.auc.dk
For additional commands, e-mail: mulinux-help@sunsite.auc.dk
This archive was generated by hypermail 2.1.6 : Sat Feb 08 2003 - 15:27:12 CET