Search results

Like I said, I *think* you need to get ahold of ncurses, build it and compile mutt w/ it. It appears to work correctly for me but I may not be fully understanding you.

well, I just went there and 2.0.18 (dated TODAY) is 'stable'. You should try that.

well, I have mutt doing exactly what you want. What I did was obtain and compile ncurses and then compile mutt w/ ncurses. Then get a good termcap entry and make it your ~/.termcap. Set your TERM to whatever (xterm-color, rxvt) as defined in your .termcap and away you go. I dont...

sorry but I dont remember how exactly I did it but it wasn't any heroics. The CVS version found the thread libraries properly and the compile went smooth. Where in Boston are you? I'm in Waltham. When I get into the office, I can see if I can maybe tar up what I have for you but I may...

I did it :D You have to get the latest source code from the openldap CVS server. That built and tested just fine (I did it a couple of months ago under 10.0.x). The officially released tarball does fail miserably on the threads stuff.

Sorry, this isn't a pipe problem. It's a user error and lack of understanding about when and why pipes get used. ps2pdf doesn't send its output to STDOUT (try man ps2pdf) therefore, there is nothing to pipe. It creates a new .pdf file and then exits. And I'll bet preview doesn't accept...

Emacs and vi get their primary information from the TERM variable. The terminal definition lives in /usr/share/misc/termcap and that keys into the TERM setting. Emacs works just fine for me (I'm not a vi guy) but all I have is TERM set to either vt100 or xterm. As a test, unsetenv...

Here in the US it does ;) At home I have my Lombard/10.1 connected to the office via bridged ISDN (Pipeline75). The ISDN is transparent to the TCP/IP stack. I'm also using the Wavelan 802.11 drivers but that doesn't make any difference WRT ISDN.

you might want to check out the macwindows.com VPN page. I'm in the same-ish boat. One of the only Mac's and I need to talk IPsec to VPN into our corporate network.

if you go ahead and chmod -x, you will find some applications failing in interesting ways. That's because the filesystem sees the eXecute bit on a directory as permission to search it. you can probably however set the sticky bit on directory which, as I recall, prevents new files from...

One simple thing is to doublecheck that the device it's trying to open is correct. It may have been hard compiled w/ an incorrect device. They're different on every unix system (eth0, le0, en0, .......). On my Lombard, it's en0

It certainly looks like it wants X11. You should './configure --help' and see if there is an option like '--with-x11' or '--disable-x11' or something like that. That would be the cleanest way. I dont have access to the GD stuff right now to see if it absolutely requires X11.

You can load them but they will not work. You must have/get the 10.1 devtools. Either eat the $20 for the Apple upgrade (no, not the free in-store upgd) or download it from ADC for free (180MB download).

I just wanted to let you know that the newest driver works fine on a Lombard/Orinoco Silver/Lucent RG1000 once you use the latest Lucent AP manager (maybe you can use the Sevy Configurator) to allow non-encrypted traffic. The card picked up the home base station. This isn't workable for...

yes, unfortunately, my Lombard is even more marginalized. No DVD, no wireless and the dreaded Lombard hi-memory problem. Just fantastic. :(

Yuri, Any idea when a WEP enabled version will be available? I gotta have encryption to connect to the corporate network. Dont make me buy a TiPBG4 ;)

Just be aware of the fact that if you use HFS+, the file system is case-preserving but NOT case-sensitive. So, if you have 'makefile' and 'Makefile' in the directory, you will see both but in fact they point to the same disk object. :( Can cause a problem on certain things (like compiling...

Proxies work fine for me in IE5.1/10.1.

that worked fine for me. The 3 NFS partitions I had mounted pre-10.1 are still there post-10.1

works fine for me. I removed the 1.0a1 and installed 1.0a2. I always start via command line 'startx -- -quartz' and not the dock X icon.