Re: Two queries [ KDE / XFree86 ]
Donn Miller [EMAIL PROTECTED] wrote: Thomas Graichen wrote: one other thing: does anyone have the XFree86 pre 4.0 snapshot running with moused and SysMouse ? - it works fine for me without moused and the moues directly under X - but with moused and "SysMouse" "/dev/sysmouse" nothing happens when moving the mouse - any further XF86Config magic required for this ? - does anyone have an hint here ? (btw. - all this on a fresh 4.0-CURRENT box) Did you select the "mouse systems" protocol in the xf86config menu? Also, does your mouse work under moused at the console? You should leave moused_type="auto" as the default. Basically, does your mouse work under syscons? That's the main thing. yes - "Auto" did it - looks like "SysMouse" as config entry in the XF86Config is broken - anyone here from the XFree86 devel people to take a look at this ? t -- [EMAIL PROTECTED] innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Cliff Rowley [EMAIL PROTECTED] wrote: Greetings, I'm just wondering if anyone has encountered the following, and what solutions you may have come up with / ideas you may have. This may not be a FreeBSD problem, since I am using the latest XFree86 pre-4.0 snapshot. First: Almost every time I load a page in Netscape (latest port), I get the message: "XFree86-BigFont extension: shmat() failed, size = 4096, errno = 24" with those options the error is gone for me - i think the relevant one is the SHMALL (the others are for postgres) - i found this out by simply reading the piece of source of XFree86 which emits this error and there is written that SHMALL should be at least 48M - so 16k pages = 64M should be fine options SHMMAXPGS=4096 options SHMALL=16384 options SHMSEG=16 options SEMMNI=32 options SEMMNS=128 t -- [EMAIL PROTECTED] innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
options SHMMAXPGS=4096
options SHMALL=16384
options SHMSEG=16
options SEMMNI=32
options SEMMNS=128
Tried those, same error :(
_XF86BigfontQueryFont: could not attach shm segment
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
On 1 Mar 2000, Thomas Graichen wrote: Basically, does your mouse work under syscons? That's the main thing. yes - "Auto" did it - looks like "SysMouse" as config entry in the XF86Config is broken - anyone here from the XFree86 devel people to take a look at this ? $ grep -5 -in sysmouse /etc/X11/XF86Config 208-# Identifier and driver 209- 210-Identifier "Mouse1" 211-Driver "mouse" 212-Option "Protocol""MouseSystems" 213:Option "Device" "/dev/sysmouse" 214- I'd recommend just backing up your old /etc/X11/XF86Config, and using the tty mode program xf86config to generate your config file. Or, just do as I have shown above. Apparently, they changed the format of XF86Config. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
On 1 Mar 2000, Thomas Graichen wrote: "XFree86-BigFont extension: shmat() failed, size = 4096, errno = 24" with those options the error is gone for me - i think the relevant one is the SHMALL (the others are for postgres) - i found this out by simply reading the piece of source of XFree86 which emits this error and there is written that SHMALL should be at least 48M - so 16k pages = 64M should be fine options SHMMAXPGS=4096 options SHMALL=16384 options SHMSEG=16 options SEMMNI=32 options SEMMNS=128 Here's what I've added to my kernel config to get rid of those errors: # Options for SHM options SHMMAXPGS=4097 options SHMSEG=128 It looks like SHMMAXPGS has to be a power of two + 1. (The original config file says options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 So, it looks like SHMMAXPGS has to be a power of two + 1. That's why I chose 4097 instead of 4096 - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Try increasing SHMSEG to 128.
Appears to be working fine with SHMAXPGS=4097 and SHMSEG=128 - fingers
crossed ;) Thanks for your help everyone...
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
On 1 Mar, Donn Miller wrote: It looks like SHMMAXPGS has to be a power of two + 1. (The original No. config file says options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 Thats from LINT. So, it looks like SHMMAXPGS has to be a power of two + 1. That's why I chose 4097 instead of 4096 LINT increases the default value by one (I think LINT didn't want to make useless modifications). See /sys/arch/include/vmparam.h. Bye, Alexander. -- It's not a bug, it's tradition! http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Do you have any plans to make XFree86-devel port of it? This let us to test
it and refine before XF-4.0 will be released.
I had no plans, personally, but then I'm not a ports
maintainer. Compiling the snapshot is pretty simple anyway.
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Thanks for pointing. What is your opinion about it (stability, compatability,
performance etc)?
Haven't had time to screw with it any more than just a basic twm setup. I'd
have to reinstall most of my X apps to use it (and I already have a nice
3.3.6 setup right now).
I made it so I could try it out seriously sometime.. right now my priority
is getting other things ready for 4.0-RELEASE.
I've been using it since the release of 3.9.1.7, and I've really enjoyed
using it. It's somewhat faster than 3.x, but that may just be because my
video card has better drivers this time around.
The release notes detail how XFree86 has become easier and easier to build
and install, and it's true. I've always scared away from editing the 3.x
config by hand - the config file format is well organised this time. As I
mentioned in a previous mail in this chain, compilation and installation
was a total breeze. Adding a single line to site.def, making
World/Install and that was that - it took a while, but it was plain
sailing.
Usage wise it's fast, it's smooth and it's been completely
reliable. Aside from a few teething problems with -current (which is to
be expected). If you're waiting for it's official release, you will be
pleasantly suprised :)
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
I've got the same problem also, and can confirm it is a
-current/XFree86-3.9.18 problem. (Probabably mainly an XFree86
problem, I presume.) Apparently, the XFree86 build process isn't
perfect either, since certain options in xc/config/cf/host.def can
cause the "make install" to fail. One set of options I had in
host.def caused the make World to finish successfully. But when I did
the ensuing "make install", it began compiling the aout shared libs,
which it didn't do during the make World. (What the hell?)
Strange, the build process was wonderfully successful for me. The only
modification I made before the make World/install process was adding:
BuildAoutLibraries
to site.def... Since posting my last mail, I've also encountered a
similar message, thie time reported by Imlib. It's not the exact same
message, but it's the same meaning. They are both having trouble getting
a handle on shared memory (at least, this is my interpretation). I've got
SYSV* in my kernel, so it's not that...
It would be nice to know if it was a FreeBSD or XFree86 thing, perhaps
someone on the list not using a pre 4.0 XFree86 snapshot could help us out
here?
Of course, it could just be (and most likely is) just being triggered by a
change in FreeBSD 4.0, which the XFree86 code (obviously) hasnt caught up
on yet.
It's not urgent, there are no critical errors produced by this situation,
everything still works just fine.
Keep me posted on anything you encounter...
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
I have a similar situation: On one of my stations: - xdm works - kdm does now. On the other, both work. Running 'FreeBSD 4.0-CURRENT #2: Thu Feb 24 15:08:07 CST 2000' on both boxes, reinstalled XFree and KDE from ports last week. The only difference I can find: one system runs XFree_S3V, the broken one runs XF86_SVGA. On 29 Feb 2000, Thomas Graichen wrote: Cliff Rowley [EMAIL PROTECTED] wrote: Second: Using KDM in place of XDM, XFree86 just dies immediately, resulting in several attempts at launching, and then a 30 second pause. XFree86 works perfectly otherwise. i see the same problem here (with an kde build outside of the ports but with all the relevant patches applied) - the sources built and worked fine with 3.3 but when built with 4.0-current kdm core- dumps ... ok so i tried to start debugging it - compiled it with -g intead of -O2 and ... it worked - so i tried -O ... it crashed - without any optimisation options it runs fine too - it looks a bit like a compiler bug or some strange bug in kdm which arises from the maybe changed optimisation in the current gcc ... but before i built kde with the gcc 2.95 port (and that was the 3.3 working version) - thus i'm a bit wondering what this comes from but did not have the time for further de- bugging - any idea ? t -- [EMAIL PROTECTED] innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
On 28 Feb, Cliff Rowley wrote: to site.def... Since posting my last mail, I've also encountered a similar message, thie time reported by Imlib. It's not the exact same message, but it's the same meaning. They are both having trouble getting a handle on shared memory (at least, this is my interpretation). I've got SYSV* in my kernel, so it's not that... Add "options SHMMAXPGS=8192" to your kernel-config to get rid of the errors from imlib (perhaps you have to increase the number if you still get errors after adding it). Bye, Alexander. -- The computer revolution is over. The computers won. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Alexander Leidinger wrote: On 28 Feb, Cliff Rowley wrote: to site.def... Since posting my last mail, I've also encountered a similar message, thie time reported by Imlib. It's not the exact same message, but it's the same meaning. They are both having trouble getting a handle on shared memory (at least, this is my interpretation). I've got SYSV* in my kernel, so it's not that... Add "options SHMMAXPGS=8192" to your kernel-config to get rid of the errors from imlib (perhaps you have to increase the number if you still get errors after adding it). What was the previous default value of SHMMAXPGS? Why was it changed? (Just curious, not slamming anybody...) - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Alexander Leidinger [EMAIL PROTECTED] wrote: On 28 Feb, Cliff Rowley wrote: to site.def... Since posting my last mail, I've also encountered a similar message, thie time reported by Imlib. It's not the exact same message, but it's the same meaning. They are both having trouble getting a handle on shared memory (at least, this is my interpretation). I've got SYSV* in my kernel, so it's not that... Add "options SHMMAXPGS=8192" to your kernel-config to get rid of the errors from imlib (perhaps you have to increase the number if you still get errors after adding it). one other thing: does anyone have the XFree86 pre 4.0 snapshot running with moused and SysMouse ? - it works fine for me without moused and the moues directly under X - but with moused and "SysMouse" "/dev/sysmouse" nothing happens when moving the mouse - any further XF86Config magic required for this ? - does anyone have an hint here ? (btw. - all this on a fresh 4.0-CURRENT box) a lot of thanks in advance t -- [EMAIL PROTECTED] innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Thomas Graichen wrote: one other thing: does anyone have the XFree86 pre 4.0 snapshot running with moused and SysMouse ? - it works fine for me without moused and the moues directly under X - but with moused and "SysMouse" "/dev/sysmouse" nothing happens when moving the mouse - any further XF86Config magic required for this ? - does anyone have an hint here ? (btw. - all this on a fresh 4.0-CURRENT box) Did you select the "mouse systems" protocol in the xf86config menu? Also, does your mouse work under moused at the console? You should leave moused_type="auto" as the default. Basically, does your mouse work under syscons? That's the main thing. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
On Tue, Feb 29, 2000 at 05:56:08PM +, Thomas Graichen wrote: one other thing: does anyone have the XFree86 pre 4.0 snapshot running with moused and SysMouse ? - it works fine for me without moused and the moues directly under X - but with moused and "SysMouse" "/dev/sysmouse" nothing happens when moving the mouse - any further XF86Config magic required for this ? - does anyone have an hint here ? (btw. - all this on a fresh 4.0-CURRENT box) This works for me with moused: Identifier "Mouse1" Driver "mouse" Option "Resolution" "100" Option "Buttons""5" Option "Protocol""Auto" Option "Device" "/dev/mouse" -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Same thing happened to me... :( one other thing: does anyone have the XFree86 pre 4.0 snapshot running with moused and SysMouse ? - it works fine for me without moused and the moues directly under X - but with moused and "SysMouse" "/dev/sysmouse" nothing happens when moving the mouse - any further XF86Config magic required for this ? - does anyone have an hint here ? (btw. - all this on a fresh 4.0-CURRENT box) a lot of thanks in advance t to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
On 29 Feb, Donn Miller wrote: What was the previous default value of SHMMAXPGS? Why was it changed? (Just curious, not slamming anybody...) 1024. I'm using 8k right now and I didn't encounter an error from imlib anymore (depends on what's used/screen resolution/resolution of pictures loaded by imlib). Bye, Alexander. -- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
No problems here... * Nawfal M. Rouyan ([EMAIL PROTECTED]) [000229 20:44]: Same thing happened to me... :( one other thing: does anyone have the XFree86 pre 4.0 snapshot running with moused and SysMouse ? - it works fine for me without moused and the moues directly under X - but with moused and "SysMouse" "/dev/sysmouse" nothing happens when moving the mouse - any further XF86Config magic required for this ? - does anyone have an hint here ? (btw. - all this on a fresh 4.0-CURRENT box) a lot of thanks in advance t to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Hasan Diwan [[EMAIL PROTECTED]] :) Rensselaer Polytechnic Institute Computer Science Department PGP signature
Re: Two queries [ KDE / XFree86 ]
Your message dated: Mon, 28 Feb 2000 23:49:07 EST Will Andrews wrote: One compatability problem would seem to be lack of support for the Number Nine I128 board, previously supported in 3.3.*. AOL Me too! :-) /AOL This is very disappointing, as I've got to use that board to drive my SGI 1600x1200 LCD display.. I guess I'll be using 3.3.6 a bit longer on that machine :-( I'd love to be proved wrong, but the release notes for the snapshots have been pretty silent on support for this board. *grumble* Yeh, and I'd like to know why the DGA (specifically, Direct Video) support the VMware folks kindly provided as patches for 3.3.3.1 haven't made it into 3.x yet - I've been manually patching them in ever since so that I can run 'fxtv'... Cheers, AS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Will Andrews wrote: On Mon, Feb 28, 2000 at 10:42:22PM +0200, Maxim Sobolev wrote: Do you have any plans to make XFree86-devel port of it? This let us to test it and refine before XF-4.0 will be released. I already made one. However, since XFree86 4.0's release is impending within the next three or four weeks (as per xfree86.org), I've left it on my website for those daring enough to try it out. http://www.psn.net/~andrews/XFree86-beta.tar.gz Thanks for pointing. What is your opinion about it (stability, compatability, performance etc)? One compatability problem would seem to be lack of support for the Number Nine I128 board, previously supported in 3.3.*. This is very disappointing, as I've got to use that board to drive my SGI 1600x1200 LCD display.. I guess I'll be using 3.3.6 a bit longer on that machine :-( I'd love to be proved wrong, but the release notes for the snapshots have been pretty silent on support for this board. louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Cliff Rowley [EMAIL PROTECTED] wrote: Second: Using KDM in place of XDM, XFree86 just dies immediately, resulting in several attempts at launching, and then a 30 second pause. XFree86 works perfectly otherwise. i see the same problem here (with an kde build outside of the ports but with all the relevant patches applied) - the sources built and worked fine with 3.3 but when built with 4.0-current kdm core- dumps ... ok so i tried to start debugging it - compiled it with -g intead of -O2 and ... it worked - so i tried -O ... it crashed - without any optimisation options it runs fine too - it looks a bit like a compiler bug or some strange bug in kdm which arises from the maybe changed optimisation in the current gcc ... but before i built kde with the gcc 2.95 port (and that was the 3.3 working version) - thus i'm a bit wondering what this comes from but did not have the time for further de- bugging - any idea ? t -- [EMAIL PROTECTED] innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Two queries [ KDE / XFree86 ]
Greetings, I'm just wondering if anyone has encountered the following, and
what solutions you may have come up with / ideas you may have.
This may not be a FreeBSD problem, since I am using the latest XFree86
pre-4.0 snapshot.
First:
Almost every time I load a page in Netscape (latest port), I get the
message:
"XFree86-BigFont extension: shmat() failed, size = 4096, errno = 24"
Second:
Using KDM in place of XDM, XFree86 just dies immediately, resulting in
several attempts at launching, and then a 30 second pause. XFree86 works
perfectly otherwise.
The main reason I'm asking this here is so that if it is a known problem
with -current, I'll have no need to investigate further, and i can just
wait until it's fixed.
If it is not a known problem, then I shall report my findings to the
relevant parties.
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Cliff Rowley wrote: This may not be a FreeBSD problem, since I am using the latest XFree86 pre-4.0 snapshot. "XFree86-BigFont extension: shmat() failed, size = 4096, errno = 24" I've got the same problem also, and can confirm it is a -current/XFree86-3.9.18 problem. (Probabably mainly an XFree86 problem, I presume.) Apparently, the XFree86 build process isn't perfect either, since certain options in xc/config/cf/host.def can cause the "make install" to fail. One set of options I had in host.def caused the make World to finish successfully. But when I did the ensuing "make install", it began compiling the aout shared libs, which it didn't do during the make World. (What the hell?) So, it appears that this snapshot can be very "touchy" depending on what you put in host.def. Changing one minor thing can throw the whole XFree86 distribution out of whack. I finally got it right, though, and I'm getting the errors you describe. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Donn Miller wrote: Cliff Rowley wrote: This may not be a FreeBSD problem, since I am using the latest XFree86 pre-4.0 snapshot. "XFree86-BigFont extension: shmat() failed, size = 4096, errno = 24" I've got the same problem also, and can confirm it is a -current/XFree86-3.9.18 problem. (Probabably mainly an XFree86 problem, I presume.) Apparently, the XFree86 build process isn't perfect either, since certain options in xc/config/cf/host.def can cause the "make install" to fail. One set of options I had in host.def caused the make World to finish successfully. But when I did the ensuing "make install", it began compiling the aout shared libs, which it didn't do during the make World. (What the hell?) So, it appears that this snapshot can be very "touchy" depending on what you put in host.def. Changing one minor thing can throw the whole XFree86 distribution out of whack. I finally got it right, though, and I'm getting the errors you describe. Do you have any plans to make XFree86-devel port of it? This let us to test it and refine before XF-4.0 will be released. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
On Mon, Feb 28, 2000 at 10:42:22PM +0200, Maxim Sobolev wrote: Do you have any plans to make XFree86-devel port of it? This let us to test it and refine before XF-4.0 will be released. I already made one. However, since XFree86 4.0's release is impending within the next three or four weeks (as per xfree86.org), I've left it on my website for those daring enough to try it out. http://www.psn.net/~andrews/XFree86-beta.tar.gz I will be submitting a XFree4 port once the release goes out. Until then, people can hack it and let me know of any problems. I've tested twm with the basic install. I do not know much about PC98/etc. so if patches could be submitted to allow for easy PC98 integration in the port, please do that. Thanks. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
On Mon, Feb 28, 2000 at 11:11:27PM +0200, Maxim Sobolev wrote: Thanks for pointing. What is your opinion about it (stability, compatability, performance etc)? Haven't had time to screw with it any more than just a basic twm setup. I'd have to reinstall most of my X apps to use it (and I already have a nice 3.3.6 setup right now). I made it so I could try it out seriously sometime.. right now my priority is getting other things ready for 4.0-RELEASE. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Two queries [ KDE / XFree86 ]
Will Andrews wrote: On Mon, Feb 28, 2000 at 10:42:22PM +0200, Maxim Sobolev wrote: Do you have any plans to make XFree86-devel port of it? This let us to test it and refine before XF-4.0 will be released. I already made one. However, since XFree86 4.0's release is impending within the next three or four weeks (as per xfree86.org), I've left it on my website for those daring enough to try it out. http://www.psn.net/~andrews/XFree86-beta.tar.gz Thanks for pointing. What is your opinion about it (stability, compatability, performance etc)? -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
