similar to: Samba 1.9.17p4 for STRATUS VOS now available

This is an updated version of my patches to get rsync to build and run its tests on the Stratus VOS operating system. I have updated this patch to apply cleanly to the current copy of HEAD. I also ran the test suite and discovered that I needed to tweak a few spots in the Makefile to append the executable suffix (VOS is one of the few systems that has a required executable suffix). There are a

This is a corrected version of the patch I originally submitted on September 5th, and resubmitted on October 14th. I have removed the changes that added $(CFLAGS) to the link-only invocations of gcc. Otherwise, the patch is the same as before. My thanks to Paul (prj@po.cwru.edu) for noticing my error and kindly correcting me. ** text of original letter, with corrections ** I had to make some

I had to make some patches to rsync to get it to build on VOS. We are a POSIX-96 (but not Unix) system. Here is the subset of the patches that I think are general to all platforms. I have tested these here. I was surprised that CPPFLAGS is not available to the compilation rules in the Makefile. Most other packages (e.g. Samba) seem to allow CPPFLAGS to be set by the user. Since this is how I

** This is a resend of mail I originally sent on September 5th. I am still interested in getting these patches applied, and getting a new config.guess and config.sub. Is there anything else I need to do in order to get these changes accepted? Thanks. PG ** I had to make some patches to rsync to get it to build on VOS. We are a POSIX-96 (but not Unix) system.

The following patch still applies cleanly to the current cvs copy of rsync. I apply it each night after I grab rsync from the build farm. Without it, I don't get far at all. The purpose of the patch is to add executable extension handling, which we need, and to clean up a few POSIX things and supply defaults for a few #defines we don't have. (See the original letter for full details).

Ville Herva [mailto:vherva@niksula.hut.fi] wrote: > Of course, whether O_TEXT is defined or not does not > necessarily imply the availability of "t", but I > can't think of better alternative. Stratus VOS implements O_TEXT and O_BINARY but does not recognize "t". We have the options defined in ANS C and in POSIX. I'm at home and don't have my reference

On Fri, Jul 31, 2015 at 12:15 AM, Herbie Robinson <HerbieRobinson at verizon.net> wrote: > I have been quietly working on a port of LLVM to Stratus VOS. The OS is > always big endian (because customers need to migrate data to new hardware > quickly and can't afford to convert). This entails presenting a big endian > programming model no matter what the hardware does. We

I have been quietly working on a port of LLVM to Stratus VOS. The OS is always big endian (because customers need to migrate data to new hardware quickly and can't afford to convert). This entails presenting a big endian programming model no matter what the hardware does. We did this about 15 years ago with the Stratus compilers and GCC. We offered the GCC changes back to the

http://bugzilla.mindrot.org/show_bug.cgi?id=978 Summary: The supplied realpath function mangles pathnames. Product: Portable OpenSSH Version: 3.9p1 Platform: Other OS/Version: other Status: NEW Severity: minor Priority: P3 Component: Miscellaneous AssignedTo: openssh-bugs at mindrot.org

<http://jbala.ws/lists/lt.php?id=MkxaBQUECR0FTgEDXVVW> -- Pour vous d?sabonner ? cette liste, visitez http://jbala.ws/lists/lt.php?id=MkxaBQUFAB0FTgEDXVVW Pour mettre vos pr?f?rences ? jour, visitez http://jbala.ws/lists/lt.php?id=MkxaBQUFAR0FTgEDXVVW Faire suivre un message a quelqun http://jbala.ws/lists/lt.php?id=MkxaBQUFAh0FTgEDXVVW -- Powered by PHPlist, www.phplist.com --

Hello Everyone, I've just started using rsync to copy files from Windows NT RCS library to Stratus VOS (Posix like fauilt tolerant Mini system) as a shadow. I would also like to setup rsync to copy log or other process output files from VOS to an NT system. Some questions if anyone here can help: 1. is there any computational or disk IO difference between the rsync client and server

Hopefully I'm not out to lunch here. I ported tftp-hpa to our proprietary OS, VOS (at stratus.com). We've always runs the old legacy tftpd from inetd, so I wanted to continue doing so with tftp-hpa. It seems to work okay, but I noticed that the code in tftpd.c has a 'while (1)' loop that has this at the end: /* * Now that we have read the request packet from

I am guessing that since the error is on the first instance of the use of foo$(VAR): foo.o construct, that the Irix makefile parser doesn't know how to deal with this line. Obviously they don't use GNU make.... So here is a patch to Makefile.in that simplifies the use of variables. This only uses constructs that should work in all makes. It should not break anything, and it

On Thu, 2014-01-30 at 11:25 -0500, Dan Swartzendruber wrote: > Hopefully I'm not out to lunch here. I ported tftp-hpa to our proprietary > OS, VOS (at stratus.com). We've always runs the old legacy tftpd from > inetd, so I wanted to continue doing so with tftp-hpa. It seems to work > okay, but I noticed that the code in tftpd.c has a 'while (1)' loop that > has

I'm stuck on 10.8.5 and got around it by: 1. Building the most recent stable branch of libc++. I got a couple of errors in the regression tests, but they looked like something obscure enough to net affect the compiler and so far, that is panning out. 2. I ran configure as follows: ../llvm/configure CXXFLAGS="-stdlib=libc++ -I/Programming/llvm/libcxx34/test/support

I'd like to suggest that this is now a great time to create two separate cvs branches for the rsync product. One, which I'll tentatively call 2_5, would hold the version of the code that has been released to the world as 2.5.6. The other, which I'll tentatively call head, would hold the development activity leading up to the next field release. I'm not bound to these names, but I

-------------------------------------------------------------------------------- Cette newsletter vous a ?t? envoy?e au format graphique HTML. Si vous lisez cette version, alors votre logiciel de messagerie pr?f?re les e-mails au format texte. Vous pouvez lire la version originale en ligne: http://ymlp225.net/z2Sppv --------------------------------------------------------------------------------

Our environment: samba4 (alpha12) running on centos 5.4. We are experimenting with Hyper-V 2008 R2 Failover Clustering, which requires Active Directory. We are trying to see if samba-4 will work as the AD server. We are trying to create 2 node failover cluster. Both nodes have joined the domain successfully (with samba-4 as the DC). But subsequent steps of creating the "Failover

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We've just posted a preview release of Samba 2.2.8 on samba.org. This is a non-production release provided for testing only. The final 2.2.8 will only include bug fixes for the 2.2.7a release. The source code can be downloaded from : http://download.samba.org/samba/ftp/pre/ The unpcompressed tarball and patch file have been signed using

Ah, with an internal block size [Is that what one calls it?] of 64 bytes. From: Damien Miller <djm at mindrot.org> Sent: Wednesday, March 29, 2023 3:08 PM To: Robinson, Herbie <Herbie.Robinson at stratus.com> Cc: Chris Rapier <rapier at psc.edu>; Christian Weisgerber <naddy at mips.inka.de>; openssh-unix-dev at mindrot.org Subject: RE: [EXTERNAL] Re: ChaCha20 Rekey