Re: XF86Setup - need help.
>hi all! > >can anybody tell me the correct entries for ADB-mouse in /etc/X11/XF86Config? >(quadra 700/68040; debian m68k potato) >i don't know the reason why, but it seems impossible for debian to >run XF86Setup, ~Config, xf86config or anything like these on my >machine. Robert, am quoting almost directly from the message Henry Garcia sent replying to my question on the same topic in the linux-mac68k mailing list: Quote: edit your XF86Config file in the /etc/X11/ directory If you're going to use the gpm program, then edit the pointer section as follows: Protocol"Microsoft" Device "/dev/gpmdata" Or else kill the gpm program before starting X and edit as follows Protocol"BusMouse" Device "/dev/mouse" Endquote. If your set-up is like mine, then you will not have gpm (you have to load it in addition to X from tasksel) so the second option above should work. Thank Henry for this. It works for me either way. I have other problems with X, but that's for another time. Regards, pgrb
Re: XF86Setup - need help.
>hi all! > >can anybody tell me the correct entries for ADB-mouse in /etc/X11/XF86Config? >(quadra 700/68040; debian m68k potato) >i don't know the reason why, but it seems impossible for debian to >run XF86Setup, ~Config, xf86config or anything like these on my >machine. Robert, am quoting almost directly from the message Henry Garcia sent replying to my question on the same topic in the linux-mac68k mailing list: Quote: edit your XF86Config file in the /etc/X11/ directory If you're going to use the gpm program, then edit the pointer section as follows: Protocol"Microsoft" Device "/dev/gpmdata" Or else kill the gpm program before starting X and edit as follows Protocol"BusMouse" Device "/dev/mouse" Endquote. If your set-up is like mine, then you will not have gpm (you have to load it in addition to X from tasksel) so the second option above should work. Thank Henry for this. It works for me either way. I have other problems with X, but that's for another time. Regards, pgrb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: A critical bug in all xfont packages
> In <[EMAIL PROTECTED]> > Anton Zinoviev <[EMAIL PROTECTED]> wrote: >> On 2.II.2001 at 23:43 ISHIKAWA Mutsumi wrote: >> > So, if there are X bitmap fonts only in the directory, the directory >> > is not needed to contain encordings.dir. >> Some of the font directories belong to only one package (such >> as sharefont). The following directories contain scalable fonts and are >> shared by more than one package: >> TrueType: ttf-twmoe-kai, ttf-twmoe-sung, xfonts-arphic-bkai00mp, >> xfonts-arphic-bsmi00lp, xfonts-arphic-gbsn00lp, >> xfonts-arphic-gkai00mp xfonts-arphic-* are only provides fonts.dir for X-TT. The fonts.dir uses TTCap extension syntax, so it is not able to use with FreeType backend. >> X-TT: ttf-xtt-wadalab-gothic, ttf-xtt-watanabe-mincho ttf-xtt-* are provides fonts.dir for FreeType and X-TT. (Can select which one want to use). And ttf-xtt-* uses mkfontdir with -e option. >> I don't know do the packages in TrueType and X-TT directories >> need encodings.dir or not. FreeType backend does use fontenc layer. So, It does need encordings.dir. X-TT backend does not use fontenc layer, it uses code conversion dynamic loading modules. So, it does not need encordings.dir >> The problem with removed encodings.dir file may be is not so >> urgent with the other font packages, but should be solved---no package >> is allowed to remove a file belonging to another package. Should I file >> bug reports against them too (with normal severity)? I think so, this problem should be solved. If xfonts-* packages will use mkfontsdir at install/remove, it is better to add `-e /usr/X11R6/lib/X11/fonts/encodings -e /usr/X11R6/lib/X11/fonts/encodings/large' options. -- ISHIKAWA Mutsumi <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
Re: A critical bug in all xfont packages
> In <[EMAIL PROTECTED]> > Anton Zinoviev <[EMAIL PROTECTED]> wrote: >> On 2.II.2001 at 23:43 ISHIKAWA Mutsumi wrote: >> > So, if there are X bitmap fonts only in the directory, the directory >> > is not needed to contain encordings.dir. >> Some of the font directories belong to only one package (such >> as sharefont). The following directories contain scalable fonts and are >> shared by more than one package: >> TrueType: ttf-twmoe-kai, ttf-twmoe-sung, xfonts-arphic-bkai00mp, >> xfonts-arphic-bsmi00lp, xfonts-arphic-gbsn00lp, >> xfonts-arphic-gkai00mp xfonts-arphic-* are only provides fonts.dir for X-TT. The fonts.dir uses TTCap extension syntax, so it is not able to use with FreeType backend. >> X-TT: ttf-xtt-wadalab-gothic, ttf-xtt-watanabe-mincho ttf-xtt-* are provides fonts.dir for FreeType and X-TT. (Can select which one want to use). And ttf-xtt-* uses mkfontdir with -e option. >> I don't know do the packages in TrueType and X-TT directories >> need encodings.dir or not. FreeType backend does use fontenc layer. So, It does need encordings.dir. X-TT backend does not use fontenc layer, it uses code conversion dynamic loading modules. So, it does not need encordings.dir >> The problem with removed encodings.dir file may be is not so >> urgent with the other font packages, but should be solved---no package >> is allowed to remove a file belonging to another package. Should I file >> bug reports against them too (with normal severity)? I think so, this problem should be solved. If xfonts-* packages will use mkfontsdir at install/remove, it is better to add `-e /usr/X11R6/lib/X11/fonts/encodings -e /usr/X11R6/lib/X11/fonts/encodings/large' options. -- ISHIKAWA Mutsumi <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
