Platform: Redhat Linux 8.0
Installing Dante--the build doesn't work. I was trying to install dante-1.1.13 (a free implementation of a SOCKS server that installs on Linux). During the build process I got the following errors:
sockd_request.c: Undefined
reference to `__bwap_32’ (I got 6 of these errors)
sockd_request.0:~/dante-1.1.13/sockd/sockd_request.c:352:
more undefined references to `__bswap_32’ follow
collect2: ld
returned 1 exit status
I dug all over looking for this one, and eventually discovered it’s due to a broken entry in the gcc compiler under Redhat 8.0. The fix is to make some changes to /usr/include/bits/byteswap.h. Full details are in the gcc-prs mail archive. This is broken on my gcc RPM version gcc-3.2-7.
Change line 84 from
# define __bswap_16(x) \
to
# define __bswap_32(x) \
and now your build should work!
Dante
Dante Installation Instructions
Thursday, March 13, 2003
Platform: Pocket PC 2002
I was testing out an installation of Microsoft's Mobile Information Server, and didn't want to run it with obtaining a spendy SSL certificate from Verisign, Thawte, etc. I maintain my own internal SSL Certificate Server, so I gave my MIS installation a certificate. Problem is, this certificate is not trusted by the Pocket PC 2002 platform (in my case, a Dell Axim). So, how could I get it do this? The documentation for MIS seems to indicate that it cannot be done. But that is incorrect. On Microsoft Support Base Article #Q322956, example code is given to add root certificates to a Pocket PC device, with compiled example code to make it rock. This allowed me to get ActiveSync up and going with MIS, and expose my server to the internet. One could argue it's even a little better for security--other people's devices wouldn't necessarily trust my internal certificates. :-)
I was testing out an installation of Microsoft's Mobile Information Server, and didn't want to run it with obtaining a spendy SSL certificate from Verisign, Thawte, etc. I maintain my own internal SSL Certificate Server, so I gave my MIS installation a certificate. Problem is, this certificate is not trusted by the Pocket PC 2002 platform (in my case, a Dell Axim). So, how could I get it do this? The documentation for MIS seems to indicate that it cannot be done. But that is incorrect. On Microsoft Support Base Article #Q322956, example code is given to add root certificates to a Pocket PC device, with compiled example code to make it rock. This allowed me to get ActiveSync up and going with MIS, and expose my server to the internet. One could argue it's even a little better for security--other people's devices wouldn't necessarily trust my internal certificates. :-)
Platform: Windows 2000
My problem yesterday was that I needed a way to interrogate a Windows 2000 Server and determine which drives were connected to which controllers. When you've got a server with 3 dual channel SCSI cards and 8 hard drives, 2 backplanes, and a tape drive, it can be a bit of a bear to figure out. Adaptec has their commercial products that do this, I wanted something free. There was some German freeware that I found by googling it, but nothing free and easy. I started digging around looking for sample code from Microsoft to determine if I could write an app that would troll through the registry and see if I could manage to pull this off, and I ran across this little gem. FILE: Rescan. This sample app, a console Win32 C application, causes the system to rescan SCSI devices on the system. Redirect the output to a text file and you're done. Be careful--I wouldn't run this on a machine with lots of active I/O, but it did the job for me, and saved a bundle. Works on XP, too. Someday I'll test in on Win2k3.
My problem yesterday was that I needed a way to interrogate a Windows 2000 Server and determine which drives were connected to which controllers. When you've got a server with 3 dual channel SCSI cards and 8 hard drives, 2 backplanes, and a tape drive, it can be a bit of a bear to figure out. Adaptec has their commercial products that do this, I wanted something free. There was some German freeware that I found by googling it, but nothing free and easy. I started digging around looking for sample code from Microsoft to determine if I could write an app that would troll through the registry and see if I could manage to pull this off, and I ran across this little gem. FILE: Rescan. This sample app, a console Win32 C application, causes the system to rescan SCSI devices on the system. Redirect the output to a text file and you're done. Be careful--I wouldn't run this on a machine with lots of active I/O, but it did the job for me, and saved a bundle. Works on XP, too. Someday I'll test in on Win2k3.
Subscribe to:
Posts (Atom)