similar to: Compiling on Tru64

Hi. Here is the short version: If dom0 experiences a short (< 120 second) network outage the guests whose disks are on iSCSI LUNs get (seemingly) unrecoverable IO errors. Is it possible to make Xen more resiliant to such problems? And now the full version: We''re testing Xen on iSCSI LUNs. The hardware/software configuration is: * Dom0 and guest OS: SLES10 x86_64 * iSCSI LUN on

Hi. I have another question, hopefully easier than my last: Do all physical interfaces in dom0 need to have an IP addresse in order to be used as a bridge by guest domains? I thought that the interface would have to merely be "up" but not necessarily have an IP address configured since bridging is done at layer 2. But alas, if I don''t configure an IP address on dom0 the bridge

I'm in a bit of a pickle, and I need some help. I'm forced to disable netbios on any machine that leaves the company because of how MS Exchange works over a VPN. I have Samba 2.x on two Compaq Tru64 5.x machines, each with one (public) share. With netbios enabled, the client machines can access the share with no issues. With netbios disabled, I get something like "No network

Hello, I want to use samba on Tru64 Unix. Can anybody let me know the location from where i can download this version. Raghu

I am just looking for a quick answer as to whether or not OpennSSH is compatible with Digital Unix Tru64 v 4.0F. Hing Fei Wong Systems Engineer Building 100, M1309 Valley Forge, PA Admin # 4-6242 -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Friday, June 23, 2006 3:53 AM To: Wong, Hing Fei Cc: www at openbsd.org Subject: Re: OpenSSH compatibility with

http://bugzilla.mindrot.org/show_bug.cgi?id=52 espenra at lpl.nu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |espenra at lpl.nu ------- Comment #25 from espenra at lpl.nu 2006-06-07 21:39 ------- (In reply to comment #24) > Anything more on

Samba 2.0.7 running on Compaq Tru64 UNIX V5.0A with latest tru64 patches. "mget *" works OK, "mput *" or something like "mput *.bat" fails with the error message "find: bad option -maxdepth". Several questions - Anyone else come across this one? Would dropping back to 2.0.6 fix the problem? Could it be an issue with 2.0.7 on Tru64 V5? Regards, Brian

http://bugzilla.mindrot.org/show_bug.cgi?id=933 Summary: compile problem on tru64 5.1A code outside of a #ifdef that should not be included on tru64 Product: Portable OpenSSH Version: 3.8p1 Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: normal Priority: P2 Component: Build

Tru64 patch will not make it into 3.5 (this is final) due to lack of willing people to test. I have given the Tru64/osf1 community almost a month to test it. And *ONE* person came forward to give me verification. And don't give me shit about "I don't have time." The person who tested it was LEAVING his employer with Tru64. He found time. IT IS YOUR GAWD DAMN PLATFORM. IF

Hi, I am trying to compile rsync 2.5.5 on a Tru64 box. I downloaded configure.in revision 1.148, which I believe is the correct fix for the getaddrinfo problem; however I still have errors compiling rsync. Also I had to change line 22 in options.c from #include "popt.h" to #include "popt/popt.h". Any suggestions or ideas? Tan Dang

Well, after digging around and thinking some more, I'm giving up on the idea of preallocating a TTY to get post-auth privsep working on Tru64. I don't think it will work, because just allocating a TTY doesn't fix the problem - there's no valid way to tie that TTY back to the client process (because it hasn't requested a TTY yet and may not ever do so). The problem is that the

I have recently written a (minimal) Tru64 Unix SIA password module for Dovecot as part of testing a Dovecot installation. Has anyone else written a Tru64 Unix SIA module? Is anyone else interested in such a module? If so, how might I/we go about getting this/such a module into the main Dovecot source? Thanks -- Simon L Jackson Carringbush.Net +- Carringbush.Net Hosting * Development *

http://bugzilla.mindrot.org/show_bug.cgi?id=716 Summary: OpenSSH 3.7.1p2: sshd doesn't start at reboot (Tru64 UNIX) Product: Portable OpenSSH Version: -current Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: openssh-bugs

Does anyone know why I cannot compile the 3.0.0 release of Samba on Compaq Tru64 4.0f (aka DEC OSF1 version 4.0f) I have read the mailing list quite a lot and have done the chmod adjustment to the "install-sh" file, and then ran "./configure" I am not using gcc nor am I using GNU make, I am using the default compiler and make supplied with the OS. the "./configure"

I believe that there is one more patch required for a successful build on Tru64: # diff ./src/lib/mountpoint.c.orig ./src/lib/mountpoint.c 60a61,63 > #ifdef __osf__ > point_r->type = p_strdup(pool, getvfsbynumber(buf.f_type)); > #else 62c65,66 < point_r->block_size = buf.f_bsize; --- > #endif > point_r->block_size = buf.f_bsize; Cheers

Hi list, I am planning to deploy samba 2.2.6 on a two-node cluster running Tru64 UNIX 5.1A. Each node will be running an instance of samba providing different services, but I want the locks directory to be shared between them so that if one node goes down, the other can take over its services and still have correct information about open files etc. My question: Can the tdb's handle being

I think I'm ready with the SIA (Security Integration Architecture) patches for Tru64 UNIX. All of the code was written by Tom Woodburn, an engineer at Compaq. I've only performed integration and testing of the patches with more help from Tom. Tom's original patches were included in the "other" ssh. We'd both like to see SIA support get into OpenSSH. SIA provides PAM-like

Hi, I'm attempting to get openssh-3.4p1 up and running on our DEC/Compaq Alpa workstations. They are running Tru64 Unix 5.1A. I compile the package myself. Openssh-3.1 worked perfectly, with the default sshd_config file. Openssh-3.4p1 works, if I set UsePrivilegeSeparation to "no" in the sshd_config file. NOTE: I have a secondary issue with the ListenAddress default setting

Either this never made it to the list or no one cares about Tru64. This is the last time I'll send this patch to the list. If no one steps up and finishes it or provides me with enough information to fix any remaining bugs (one being complaint that 'ssh site cmd' does not work right). If there is no activity on this for a week. I'll post it to bugzilla and will ignore any

The ls_file function in sftp-server.c calls snprintf with "%8llu" as part of the format string and a "unsigned long long" type argument. The "%ll" format is not a valid format on Tru64 (at least 4.0F). Apparently it can confuse snprintf as well - sftp-server will segfault and core dump if the user types "ls". This isn't really a needed format string on