- WLUG - wlug.mailman3.com

VGA cables ; BBQ

by Doug Mildram

doug> hi! packrat alert and BBQ teaser/feeler. 1) who has stashed VGA monitor cables (M/M, not extension) from dead monitors ? (from monitors whose cables are not molded on! ) I need a bunch for work... a remote to-be-shutdown-site simpleton packed up LCD monitors and shipped them to the mother ship withOUT cables. I have a semi-new job at EMC, the mother ship/flotilla in Hopkinton. True, I could buy 10 cables for maybe $20 on ebay. 2) Coming to the WLUG bbq next thursday 7/13 at my house in Boylston? (details later, perhaps by Andy). I'll be shopping for that soon, Soliciting ideas and "I'll be there" (or not) reply-to-me appreciated. (BYOB, bring your kids/dogs/SO's, the cheesy aboveground pool is working) Idea hunting: burgers,dogs(easy); sausages?(more challenging, what's a good brand/type that won't turn my grill into an inferno?). Healthy side dishes? (can't think of any at the moment. Maybe you'll bring something or suggest something easy). Chips: normal like Lays/Ruffles? exotic like Cape Cod? Salsa+cornchips? One of each, probably...I can be real cheap when it comes to things like chips. e.g. $3 for 8oz of hummus==toomuch! Oh well, "whiner off". I usually save big at PriceRite (in Worcester and many other locations), it's a very multicultural experience :) - doug and the dogs...

July 16, 2009

Fedora 11 and mingw32

by dulsi＠identicalsoftware.com

I installed fedora 11 on my old laptop and turned back on glitch free audio. It almost works perfectly. Sufficient that I probably wouldn't bother turning it off now. I think the hard drive is starting to fail so I decided to purchase a new laptop. Since I'd like some 3D functionality now I decided to go with the Intel GMA X4500. Unfortunately Fedora 11 stumbled here. I thought the picture quality wasn't very good and found it was using the vesa drivers not the intel drivers. Searching found that others had the same issue but it worked on Fedora 10. Tried a Fedora 10 live CD and the display was nice and sharp. Modified the xorg.conf to use the intel drivers and Fedora 11 also became nice and sharp. Anyway onto my question, has anyone played with the mingw32 cross compiler on Fedora 11? I've created a simple hello world app and cmake file (since I hate autotools). I've got it compiling by creating a Toolchain file but it seems like that is something that should be provided with the mingw32. Is there a standard Toolchain file somewhere and I just haven't found it?

July 5, 2009

Re: [Wlug] Making a pipe or socket look like a file.

by John Stoffel

Alex> I'm trying to extend the functionality of a piece of CAD Alex> software i'm using. The software package is called eagle and it Alex> has a custom in application scripting language that allows you Alex> to access an open CAD document by manipulating a tree of Alex> objects. The scripting language is fairly limited when it comes Alex> to talking to the outside world and only offers rudimentary file Alex> IO. I was wondering if any of you know how to make one end of a Alex> unix socket look like a file? What exactly are you trying to achive here with eagle's rudimentary file IO? Do you want to feed Eagle a design in realtime from the socket? Or be able to send data to/from the app from another host? What? I've read the suggestions, and they all have some merit, but I'm still at a loss to understand what you're trying to accomplish. Once we know that, maybe we can suggest a better solution than sockets. John

July 1, 2009

Fwd: Making a pipe or socket look like a file.

by J. R. Mauro

Damn phone didn't let me reply all Begin forwarded message: > From: "J. R. Mauro" <jrm8005(a)gmail.com> > Date: July 1, 2009 10:00:44 EDT > To: Mike Frysinger <vapier(a)gentoo.org> > Subject: Re: [Wlug] Making a pipe or socket look like a file. > > > > > > On Jul 1, 2009, at 9:33, Mike Frysinger <vapier(a)gentoo.org> wrote: > >> On Tuesday 30 June 2009 22:35:44 J. R. Mauro wrote: >>> On Jun 30, 2009, at 22:24, Mike Frysinger wrote: >>>> On Tuesday 30 June 2009 21:47:18 J. R. Mauro wrote: >>>> >>>> please dont top post >>> >>> Who did? >> >> i'm guessing you made this comment ironically > > Actually, I was probably drunk, and I was definitely typing on my > phone both times, so forgive me if I wasn't an ml-etiquette zealot. > > Moving things is a worse sin than top posting. > >> >> >>>>> On Jun 30, 2009, at 21:42, Alex Camilo <alex.camilo(a)gmail.com> >>>>> wrote: >>>>>> I'm trying to extend the functionality of a piece of CAD software >>>>>> i'm using. The software package is called eagle and it has a >>>>>> custom >>>>>> in application scripting language that allows you to access an >>>>>> open >>>>>> CAD document by manipulating a tree of objects. The scripting >>>>>> language is fairly limited when it comes to talking to the >>>>>> outside >>>>>> world and only offers rudimentary file IO. I was wondering if >>>>>> any of >>>>>> you know how to make one end of a unix socket look like a file? >>>>> >>>>> Unfortunately, you can't. It's one of the design flaws of Unix. >>>>> You >>>>> might be able to wrap it with a FUSE filesystem. But sockets and >>>>> FIFOs >>>>> are unfortunately "special" >>>> >>>> i imagine you could use netcat to redirect from a named pipe so >>>> that >>>> you can >>> >>> FIFOs are kind of a hack. >> >> no one said otherwise. the fun thing about *nix is you can >> leverage these >> kind of hacks quickly. > > And then go through the pain of hacking on top of them and > supporting them. The *real* unix mindset was careful, elegantly > minimal design, not ad-hackery. That started outside Bell Labs. > > c.f. most perl programs > >> >> >>> Make a fuse filesystem in 20 lines of python >>> and you get something more robust and specialized, plus network >>> transparency for free >> >> if you say so, i havent done fuse work myself >> -mike > > It's laughably easy. I had a filesystem written to expose stuff from > the x server (mouse coordinates, snarf buffer, etc) in about four > hours. The hard part was dealing with how crappy x11 is (400 lines > to r/w the snarf buffer?! Gag me with a spoon! X is the epitome of > bad design and bad APIs) The fuse part was a joy, and probably all > of it was fewer lines than the snarf buffer. > > It seems like the OP wants a permanent solution, and maybe one that > involves biderectional communication and separation of roles into > multiple channels (he didn't say the last bit, but I've got five > bucks that says he'll want to once he thinks about it and looks at > other fileserver-based programs like Acme, rio, factotum, flickrfs, > etc) > > Using fifos for this is lunacy.

July 1, 2009

Re: [Wlug] Making a pipe or socket look like a file.

by Mike Frysinger

On Tuesday 30 June 2009 22:35:44 J. R. Mauro wrote: > On Jun 30, 2009, at 22:24, Mike Frysinger wrote: > > On Tuesday 30 June 2009 21:47:18 J. R. Mauro wrote: > > > > please dont top post > > Who did? i'm guessing you made this comment ironically > >> On Jun 30, 2009, at 21:42, Alex Camilo <alex.camilo(a)gmail.com> wrote: > >>> I'm trying to extend the functionality of a piece of CAD software > >>> i'm using. The software package is called eagle and it has a custom > >>> in application scripting language that allows you to access an open > >>> CAD document by manipulating a tree of objects. The scripting > >>> language is fairly limited when it comes to talking to the outside > >>> world and only offers rudimentary file IO. I was wondering if any of > >>> you know how to make one end of a unix socket look like a file? > >> > >> Unfortunately, you can't. It's one of the design flaws of Unix. You > >> might be able to wrap it with a FUSE filesystem. But sockets and > >> FIFOs > >> are unfortunately "special" > > > > i imagine you could use netcat to redirect from a named pipe so that > > you can > > FIFOs are kind of a hack. no one said otherwise. the fun thing about *nix is you can leverage these kind of hacks quickly. > Make a fuse filesystem in 20 lines of python > and you get something more robust and specialized, plus network > transparency for free if you say so, i havent done fuse work myself -mike

July 1, 2009

Re: [Wlug] Making a pipe or socket look like a file.

by J. R. Mauro

On Jun 30, 2009, at 22:47, Alex Camilo <alex.camilo(a)gmail.com> wrote: > I'm thinking fuse might work. I'l look into working with fuse in It's dead simple, even in C. And then you can have a bunch of files for specific tasks > > python when I get to a real computer. Thanks! > > > > On Jun 30, 2009, at 10:35 PM, "J. R. Mauro" <jrm8005(a)gmail.com> wrote: > >> >> >> >> >> On Jun 30, 2009, at 22:24, Mike Frysinger <vapier(a)gentoo.org> wrote: >> >>> On Tuesday 30 June 2009 21:47:18 J. R. Mauro wrote: >>> >>> please dont top post >> >> Who did? >> >>> >>> >>>> On Jun 30, 2009, at 21:42, Alex Camilo <alex.camilo(a)gmail.com> >>>> wrote: >>>>> I'm trying to extend the functionality of a piece of CAD software >>>>> i'm using. The software package is called eagle and it has a >>>>> custom >>>>> in application scripting language that allows you to access an >>>>> open >>>>> CAD document by manipulating a tree of objects. The scripting >>>>> language is fairly limited when it comes to talking to the outside >>>>> world and only offers rudimentary file IO. I was wondering if any >>>>> of >>>>> you know how to make one end of a unix socket look like a file? >>>> >>>> Unfortunately, you can't. It's one of the design flaws of Unix. You >>>> might be able to wrap it with a FUSE filesystem. But sockets and >>>> FIFOs >>>> are unfortunately "special" >>> >>> i imagine you could use netcat to redirect from a named pipe so that >>> you can >> >> FIFOs are kind of a hack. Make a fuse filesystem in 20 lines of >> python >> and you get something more robust and specialized, plus network >> transparency for free >> >>> >>> read/write via the network ... seems to work for me >>> >>> $ mkfifo fifo >>> shell 1: $ nc -l -p 12345 localhost > fifo >>> shell 2: $ cat fifo >>> shell 3: $ nc localhost 12345 >>> -mike >> _______________________________________________ >> Wlug mailing list >> Wlug(a)mail.wlug.org >> http://mail.wlug.org/mailman/listinfo/wlug > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug

July 1, 2009

Re: [Wlug] Making a pipe or socket look like a file.

by Alex Camilo

I'm thinking fuse might work. I'l look into working with fuse in python when I get to a real computer. Thanks! On Jun 30, 2009, at 10:35 PM, "J. R. Mauro" <jrm8005(a)gmail.com> wrote: > > > > > On Jun 30, 2009, at 22:24, Mike Frysinger <vapier(a)gentoo.org> wrote: > >> On Tuesday 30 June 2009 21:47:18 J. R. Mauro wrote: >> >> please dont top post > > Who did? > >> >> >>> On Jun 30, 2009, at 21:42, Alex Camilo <alex.camilo(a)gmail.com> >>> wrote: >>>> I'm trying to extend the functionality of a piece of CAD software >>>> i'm using. The software package is called eagle and it has a custom >>>> in application scripting language that allows you to access an open >>>> CAD document by manipulating a tree of objects. The scripting >>>> language is fairly limited when it comes to talking to the outside >>>> world and only offers rudimentary file IO. I was wondering if any >>>> of >>>> you know how to make one end of a unix socket look like a file? >>> >>> Unfortunately, you can't. It's one of the design flaws of Unix. You >>> might be able to wrap it with a FUSE filesystem. But sockets and >>> FIFOs >>> are unfortunately "special" >> >> i imagine you could use netcat to redirect from a named pipe so that >> you can > > FIFOs are kind of a hack. Make a fuse filesystem in 20 lines of python > and you get something more robust and specialized, plus network > transparency for free > >> >> read/write via the network ... seems to work for me >> >> $ mkfifo fifo >> shell 1: $ nc -l -p 12345 localhost > fifo >> shell 2: $ cat fifo >> shell 3: $ nc localhost 12345 >> -mike > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug

July 1, 2009

Re: [Wlug] Making a pipe or socket look like a file.

by J. R. Mauro

On Jun 30, 2009, at 22:24, Mike Frysinger <vapier(a)gentoo.org> wrote: > On Tuesday 30 June 2009 21:47:18 J. R. Mauro wrote: > > please dont top post Who did? > > >> On Jun 30, 2009, at 21:42, Alex Camilo <alex.camilo(a)gmail.com> wrote: >>> I'm trying to extend the functionality of a piece of CAD software >>> i'm using. The software package is called eagle and it has a custom >>> in application scripting language that allows you to access an open >>> CAD document by manipulating a tree of objects. The scripting >>> language is fairly limited when it comes to talking to the outside >>> world and only offers rudimentary file IO. I was wondering if any of >>> you know how to make one end of a unix socket look like a file? >> >> Unfortunately, you can't. It's one of the design flaws of Unix. You >> might be able to wrap it with a FUSE filesystem. But sockets and >> FIFOs >> are unfortunately "special" > > i imagine you could use netcat to redirect from a named pipe so that > you can FIFOs are kind of a hack. Make a fuse filesystem in 20 lines of python and you get something more robust and specialized, plus network transparency for free > > read/write via the network ... seems to work for me > > $ mkfifo fifo > shell 1: $ nc -l -p 12345 localhost > fifo > shell 2: $ cat fifo > shell 3: $ nc localhost 12345 > -mike

July 1, 2009

Re: [Wlug] Making a pipe or socket look like a file.

by Mike Frysinger

On Tuesday 30 June 2009 21:47:18 J. R. Mauro wrote: please dont top post > On Jun 30, 2009, at 21:42, Alex Camilo <alex.camilo(a)gmail.com> wrote: > > I'm trying to extend the functionality of a piece of CAD software > > i'm using. The software package is called eagle and it has a custom > > in application scripting language that allows you to access an open > > CAD document by manipulating a tree of objects. The scripting > > language is fairly limited when it comes to talking to the outside > > world and only offers rudimentary file IO. I was wondering if any of > > you know how to make one end of a unix socket look like a file? > > Unfortunately, you can't. It's one of the design flaws of Unix. You > might be able to wrap it with a FUSE filesystem. But sockets and FIFOs > are unfortunately "special" i imagine you could use netcat to redirect from a named pipe so that you can read/write via the network ... seems to work for me $ mkfifo fifo shell 1: $ nc -l -p 12345 localhost > fifo shell 2: $ cat fifo shell 3: $ nc localhost 12345 -mike

July 1, 2009

Re: [Wlug] Making a pipe or socket look like a file.

by Scott Venier

J. R. Mauro wrote: > Unfortunately, you can't. It's one of the design flaws of Unix. You > might be able to wrap it with a FUSE filesystem. But sockets and FIFOs are > unfortunately "special" > FIFOs do exist in the filesystem (see mkfifo(3)), but they're only unidirectional. If you want bidirectional, either need a pair of FIFOs, or as a bit of a hack, you could have your external process open up a unix socket and write the fd number and it's PID into some pre-arranged file (say, /tmp/<username>/eagle/socket_location). Your script could then open that file, and use the information to construct a path to /proc/<PID>/fd/<fd> and access the socket as a file that way. Or, I suppose you could simplify the script side by making that pre-arranged file into a symlink to /proc/<PID>/fd/<fd>. Scott

July 1, 2009