Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!newshost.marcam.com!usc!cs.utexas.edu!natinst.com!news.dell.com!swrinde!howland.reston.ans.net!Germany.EU.net!zib-berlin.de!irz401!uriah.heep!bonnie.heep!not-for-mail
From: j@bonnie.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Comparison
Date: 4 Sep 1995 17:01:24 +0200
Organization: Private U**x site, Dresden.
Lines: 35
Message-ID: <42f4c4$rj2@bonnie.tcd-dresden.de>
References: <427nlp$9c1@parsifal.nando.net> <429mv4$7on@i-2000.com> <429r1b$8un@gryphon.phoenix.net> <42baln$7kb@zagnut.cs.umd.edu>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Frank W. Miller <fwmiller@cs.umd.edu> wrote:
>If you missed my previous post, FreeBSD recognizes my old HardCard XL,
>NetBSD did not. I ended up having to remove it tho, it crashed the
>installation after the device probe phase.
Curious: what exactly is it?
>The fonts I used in XFree under NetBSD look different under FreeBSD, this
>is probably due to a different X server config but I don't know. One
I think it's a question whether the 75dpi or 100dpi font directory is
included first in the FontPath.
>interesting thing. My pulldown menus on applications like xfontsel and
>xman don't work with my Logitech 3-button mouse under FreeBSD, they
>worked fine under NetBSD. Anybody have any ideas about that?
The default behaviour for FreeBSD (until XFree86 3.1.1) was to inherit
the NumLock LED setting to the X server. This finally made a bug in
Xaw very obvious: the X server now handles NumLock as a modifier key,
and many Xaw clients didn't ignore the NumLock modifier in their
translation tables as they ought to be. (Neither does Tk.)
As a consequence of all the complaints, the XConsortium finally fixed
the Xaw clients :) in their latest public fix as included in XFree86
3.1.2. Additionally, XFree86 does no longer inherit the NumLock
setting from the console driver and starts up with NumLock off by
default, as almost any other X server does. (Actually, you can also
observe the bug on many workstations as soon as you turn NumLock on.)
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)