Re: (Warning long!) Re: X11 CVS with linux 2.6.0-test9?
On Sat, 2003-11-29 at 21:03, Fred Heitkamp wrote: On Sat, 29 Nov 2003, Michel [ISO-8859-1] Dnzer wrote: On Fri, 2003-11-28 at 19:27, Fred Heitkamp wrote: name of display: :0.0 display: :0 screen: 0 direct rendering: No server glx vendor string: Brian Paul server glx version string: 1.4 Mesa 4.0.4 Current XFree86 CVS is based on Mesa 5.0.x, it seems to be picking up the wrong libGL? The libOSMesa libraries as of Nov 22 seems to be the following on my system. The OS stands for off-screen, it's unrelated. Start with the output of ldd `which glxinfo` | grep libGL.so (**) RADEON(0): Option AGPMode 4 Have you tried lower AGP modes? No but there doesn't seem to be a problem with the 2.4.x kernels running on mode 4. I will lower the mode and try disabling backing store and see what happens. [...] I tried just leaving the display running without doing anything interactive with the interface and X ran for several hours before freezing. All that was running was Xscreensaver. I then tried again using X normally but with a different window manager (XFCE 4) and it worked for about an hour and then froze again. But that was still at AGP 4x? -- Earthling Michel Dnzer | Debian (powerpc), X and DRI developer Software libre enthusiast| http://svcs.affero.net/rm.php?r=daenzer ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Problem connecting to IPv4 in IPv6 format
David Dawes wrote (in a message from Thursday 27) Incidentally related to this is another problem I've run in to. Old FreeBSD X apps, that use a version of libc without IPv6 support, crash when run on a recent system when trying to connect to a remote display when using our newly built X libraries. I have a patch that restores compatibility to our X libraries by checking if the IPv6 libc support is available at run-time, and falling back to the IPv4 code otherwise. I think it is complete enough, but I'd like some feedback before committing it. I think that this particular case (using binary libraries with IPv6 enabled on a older libc which doesn't know at all about IPv6) is probably going to fail in applications too. I'm not sure if it's worth handling it inside of Xlib. There are enough issues and separate cases when the libraries are consistent wrt. IPv6 to handle not to add this additional complexity. But having said that, your patch seem to handle this particular situation and since it's the base for your 2nd patch that handles something more important, I guess both should go in. Matthieu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Problem connecting to IPv4 in IPv6 format
A related problem is that I was not able to connect to a v4 only X server running on a machine which happens to have a DNS record, from a NetBSD or OpenBSD host with IPv6 configured. The following patch fixes that: Index: xc/lib/xtrans/Xtranssock.c === RCS file: /cvs/xf86/xc/lib/xtrans/Xtranssock.c,v retrieving revision 3.65 diff -u -r3.65 Xtranssock.c --- xc/lib/xtrans/Xtranssock.c 20 Nov 2003 00:41:37 - 3.65 +++ xc/lib/xtrans/Xtranssock.c 30 Nov 2003 16:36:34 - @@ -1639,7 +1639,11 @@ || ( ((addrlist-addr-ai_next != NULL) || (addrlist-addr != addrlist-firstaddr)) (olderrno == ENETUNREACH || olderrno == EAFNOSUPPORT || -olderrno == EADDRNOTAVAIL || olderrno == ETIMEDOUT)) +olderrno == EADDRNOTAVAIL || olderrno == ETIMEDOUT +#if defined(EHOSTDOWN) + || olderrno == EHOSTDOWN +#endif + )) #endif ) res = TRANS_TRY_CONNECT_AGAIN; Matthieu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Problem connecting to IPv4 in IPv6 format
On Sun, Nov 30, 2003 at 03:45:17PM +0100, Matthieu Herrb wrote:
David Dawes wrote (in a message from Thursday 27)
Incidentally related to this is another problem I've run in to. Old
FreeBSD X apps, that use a version of libc without IPv6 support, crash
when run on a recent system when trying to connect to a remote display
when using our newly built X libraries. I have a patch that restores
compatibility to our X libraries by checking if the IPv6 libc support
is available at run-time, and falling back to the IPv4 code otherwise.
I think it is complete enough, but I'd like some feedback before
committing it.
I think that this particular case (using binary libraries with IPv6
enabled on a older libc which doesn't know at all about IPv6) is
probably going to fail in applications too. I'm not sure if
it's worth handling it inside of Xlib. There are enough issues and
separate cases when the libraries are consistent wrt. IPv6 to handle
not to add this additional complexity.
But having said that, your patch seem to handle this particular
situation and since it's the base for your 2nd patch that handles
something more important, I guess both should go in.
I agree that it isn't worth going to extreme lengths. But since it was
relatively straightforward to do, I think it is worth doing to avoid
breaking what is probably the most common usage. This essentially
amounted to changing a build-time choice to a run-time choice, so didn't
really require new code.
The separation of IPv4 and IPv6 sockets/addresses required the most changes.
I've attached an updated verion of the complete patch, including the
EHOSTDOWN patch you posted today. It fixes a couple of flaws in the
IPv4/IPv6 separation, and cleans up a few other things. (It is a 'diff
-ubB' patch so whitespace noise is minimised.) I'm planning on committing
it in a day or so pending further testing and feedback.
Post-4.4 we might want to look at whether this (and other IPv6-related
code) needs to be restructured to handle the separation more cleanly
and naturally.
I don't follow the IPv6 standards process closely, so I don't know how
much of the separation vs combining is political, or whether it is
likely that future RFCs will favour one method over the other. If we
handle IPv6 by keeping IPv6 sockets for IPv6 only, we should be in good
shape either way.
David
--
David Dawes
developer/release engineer The XFree86 Project
www.XFree86.org/~dawes
--- Xtranssock.c-3.65 Sun Nov 30 19:15:30 2003
+++ Xtranssock.cSun Nov 30 19:17:25 2003
@@ -206,6 +206,9 @@
#define NUMSOCKETFAMILIES (sizeof(Sockettrans2devtab)/sizeof(Sockettrans2dev))
+#ifdef TCPCONN
+static int TRANS(SocketINETClose) (XtransConnInfo ciptr);
+#endif
#ifdef UNIXCONN
@@ -278,6 +281,8 @@
#if defined(IPv6) defined(AF_INET6)
static const struct in6_addr local_in6addr_any = IN6ADDR_ANY_INIT;
#pragma weak in6addr_any = local_in6addr_any
+#pragma weak getaddrinfo
+static int haveIPv6 = 1;
#endif
/*
@@ -312,19 +317,32 @@
{
#if defined(IPv6) defined(AF_INET6)
-struct sockaddr_storage sockname;
-#else
-struct sockaddr_in sockname;
+struct sockaddr_storage socknamev6;
#endif
+struct sockaddr_in socknamev4;
+void *socknamePtr;
#if defined(SVR4) || defined(SCO325)
-size_t namelen = sizeof sockname;
+size_t namelen;
#else
-int namelen = sizeof sockname;
+int namelen;
#endif
PRMSG (3,SocketINETGetAddr(%p)\n, ciptr, 0, 0);
-if (getsockname (ciptr-fd,(struct sockaddr *) sockname,
+#if defined(IPv6) defined(AF_INET6)
+if (haveIPv6)
+{
+ namelen = sizeof(socknamev6);
+ socknamePtr = socknamev6;
+}
+else
+#endif
+{
+ namelen = sizeof(socknamev4);
+ socknamePtr = socknamev4;
+}
+
+if (getsockname (ciptr-fd,(struct sockaddr *) socknamePtr,
(void *)namelen) 0)
{
PRMSG (1,SocketINETGetAddr: getsockname() failed: %d\n,
@@ -345,12 +363,17 @@
}
#if defined(IPv6) defined(AF_INET6)
-ciptr-family = ((struct sockaddr *)sockname)-sa_family;
-#else
-ciptr-family = sockname.sin_family;
+if (haveIPv6)
+{
+ ciptr-family = ((struct sockaddr *)socknamePtr)-sa_family;
+}
+else
#endif
+{
+ ciptr-family = socknamev4.sin_family;
+}
ciptr-addrlen = namelen;
-memcpy (ciptr-addr, sockname, ciptr-addrlen);
+memcpy (ciptr-addr, socknamePtr, ciptr-addrlen);
return 0;
}
@@ -366,19 +389,32 @@
{
#if defined(IPv6) defined(AF_INET6)
-struct sockaddr_storage sockname;
-#else
-struct sockaddr_in sockname;
+struct sockaddr_storage socknamev6;
#endif
+struct sockaddr_in socknamev4;
+void *socknamePtr;
#if defined(SVR4) || defined(SCO325)
-size_t namelen = sizeof sockname;
+size_t namelen;
#else
-int namelen = sizeof sockname;
+int namelen;
#endif
+#if defined(IPv6) defined(AF_INET6)
+if
Sending Resume
Hello David I'm looking for new project as independent CONSULTANT Will call you tomorrow to schedule meeting as we were talking before, possible this week or in Monday; E-mail: [EMAIL PROTECTED] Tel. (408) 309-7006 Engineer or Manager or INDEPENDENT CONSULTING or Engineering Manager and/or Senior Mechanical Design ENGINEER, Design Analyst Program Manager Project Manager, Product Manager Product Development Specialist Manufacturing Engineering Electro-Mechanical Industrial Designer RD, CADD Manager, SBIR Over 20 years combine experience in Technical Managerial Positions performing Engineering Design Service Systems Design System Integration, RD, Product Process Development, Projects Products Engineering Management, Manufacturing Operations Preparation Managing teams of Engineering Specialist; 08-1993 to present; MECH-TRONIC DESIGN MFG; SANTA CLARA, CA Engineering Manager, Project Product Manager, SR. Mechanical Design Engineer, CADD Manager. Duties included: Preparing technical documentation, calculations, engineering, design, layouts, drawings, 3D and Solid Modeling, development propositions. Hard Drive Designing, testing, balancing, recalculating and redesign. Solid Works, Mechanical Desktop. Manufacturing and Assembly Equipment design and build. Hard Drive Testing Equipment design mfg. Tooling and Operations Development, Implementation Automation for mass production. Pro-E, CADD Management, Automation and Operations, Analyzing, AutoCAD 2000 M D, Win 95/98/2000/NT, Creating, revising implementing improvements to existing and new manufacturing processes. Mfg Assy Development support. Cost study and cost reduction analyzing. Purchasing manufacturing equipment, Bill of Materials creation. Copy Machines Color commercial Printers design build. Paper path Heads - dynamic orientation. Rapid Thermo Processing, Wafer 200 300 mm with automatic Door and manual inserting, Scanners, Sensors Cassette opening and rotation, LASER Equipment Motion Control. Fiber Optics equipment, enclosures, connectors, tools manufacturing; assembly equipment design build. Wafer Handling Processing Equipment, Stages Sliders, Thickness Measurement, Robotics. Network Electronic / Computer Testing Equipment. Plastic Enclosures Design Build; Hard Drive, modems, ICT Equipment Des, Mfg Assy. Teaching Mechanical Engineering and Descriptive Geometry, CADD. Computer Graphics, Electro - Mechanical Engineering Design, AutoCAD, Plotting, DOS, Lecture and practical assignment. Software and computer support. Electrical Mechanical Projects, Production Equipment Machinery. Designing Electric Cars, Analyzes Calculations, Prototypes electronic and electrical schematic Layouts, mechanical detailing body shell. CAD and Plotting Station Management, Lib, Analyzes Calculations, Prototypes Product Mfg. Development, design redesigning mechanical components for manufacturing, Assembly draw, Customizing Electronic, Mechanical and Electrical Equipment, AutoCAD, Spreadsheet, Basic, dB; Lotus, Excel, Paradox, Quadro Project Management Production, scheduling, quality control, controlling production planning injection molding, plastic parts and elements design and manufacturing Manufacturing hydraulic pneumatic equipment, machinery and control systems, mechanisms, robotics device, precision machine elements. Inspecting and control manufacturing standards, analyzing stresses and tolerances, selecting materials, engineering computations and technical improvements, documentation, projects development, supplying. Automation, Conveyors, Spiral Elevator, Fast Cannery Transportation, Electronic and Electrical Components, Master Control Center, Sheet Metal Oven Rebuilding Project. LASER MEDICAL DEVICE, Lasers, Optics, Fiber Optics 3 SETS OF OPTICAL LENSES MOVE-AUTOMATON COLIMMATOR Project Management, Design, Product Development Manufacturing, Production, Operation Manager Sales Customer Service Transportation Shop Manager Service Station Operating Management CREATIVE THINKING AND SOLUTION DEVELOPMENT OPEN FOR TRAVEL (domestic /international) US Citizen Permanent preferred INDEPENDENT CONSULTING TEL. (408) 309-7006 E-mail: [EMAIL PROTECTED] ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
