similar to: Permissions issues after 'upgrade'

Samba Gurus, I've recently built a new Solaris samba server to replace an older one, the older one is running 2.0.7 & the new one is running 2.2.2. I pretty much just copied over the the smb.conf file & made some small adjustments via swat - the options are a bit different. The old server was just the way we needed it.....but now that the new server has gone live it appears we

Samba Gurus, I've got a Solaris box running samba 2.0.7. A couple of users on Windows XP clients are reporting problems saving files from within MS Word, and Wordpad to the samba share, which of course is a mapped drive. They get an error saying "This is not a valid file name".... These XP boxes do have the reg hacks plainpassword.reg and signorseal.reg installed. The work around

Thanks a million to Wendell Wilson, who offered a solution to the problem we've been seeing regarding saving a document in MS Word. I know we really do need to upgrade to at least 2.2.6, and I am planning it - but this gives us little more breathing room with everything else going on. Once again, appreciate your help! --Gene Original Question: At 04:35 PM 11/14/2002 -0800, I wrote:

share TO a Samba share (physically on a Solaris 2.7 box). Copying the other direction is fine. Snippet from one of the Client's log file on the Solaris box: smbd/error.c:error_packet(112) error packet at smbd/notify.c(67) cmd=160 (SMBnttrans) eclass=0 ecode=-1073741536 [2002/08/14 11:00:27, 3] smbd/nttrans.c:reply_ntcancel(1480) reply_ntcancel: cancel called on mid = 512. ..........

Hello, I try to convert a LDIF contain some users to a LDIF with samba3 sh?ma. But, the convertion on my computers don't work ! Attached files : a ldif with one user (users.ldif) and a LDIF file after convertion (users3.ldif) Can anyone help me ? RedHat 8 Samba 3.1 beta1 -------------- next part -------------- dn: ou=users, dc=toto,dc=be ou:: dXNlcnMN description::

Thank very much for this answer, so my last question will be: is it possible to use the LLVM JIT on a PS3 with Yellow Dog 6.2 distribution, instead of the LLVM interpreter, by using the PPE as it seems to be similar to 64-bit PowerPC processors? 2009/12/18 Scott Michel <scooter.phd at gmail.com> > Jerome: > > No, there are no plans to JIT to SPU. That's considerably more

Jerome: No, there are no plans to JIT to SPU. That's considerably more complicated -- you'd have to figure out when to JIT to the SPU and live with all of the constraints that the SPU imposes (data reformatting, r/w DMA, ensure your code lives in 256K unless you can manage to interface with the virtual I-cache work.) Basically, it's not trivial and it doesn't quite fit into the

SAMBA Gurus, I'm sure this has been experienced & addressed by somebody.....but here's the issue: Running version 2.2.2 on Solaris 2.8.....some users who try to copy a file from a Novell share into a mapped Unix SAMBA share (copy, drag & drop via windows explorer) cannot - they get this error message: "Cannot copy geology: Access is denied." "Make sure the disk

I compiled the following code with llvm-gcc (4.2.1) and llc (2.3svn) for spu of Cell broadband engine processor. > cat add.c float add (float a, float b) { return a + b; } > llvm-gcc add.c --emit-llvm -c -o add.bc > llc -march=cellspu add.bc Cannot yet select: 0x867c700: v4f32 = SPUISD::INSERT_MASK 0x8670800 Abort (core dumped) But llc returned the above error. If I

Hello, list; This is my second try asking for help. One person responded and provided help, but I still can't seem to work this out. I've searched, but have failed. I'm not new to Samba, but I can and do make mistakes...so here I am. I have a fresh install of Ubuntu 13.10 with Samba 3.6.18. I have Kerberos properly configured and have successfully joined the domain, and can list

Firstoff, let me say what a mind fsck the Cell SPU can be. It's really not that hard an architecture to get one's mind around, but I can see how it becomes a compiler writer's nightmare. And I'm attempting to write a SPU backend. And it's going slowly. Here's my problem: The SPU's registers are all 128-bit vector registers. That's their native mode. They can be

On Mar 29, 2010, at 6:50 AM, Kalle Raiskila wrote: > attached is a second try for the bigstack patch for SPU, with testcase. It is essentially the patch committed as 97091, and reverted as 97099, but with the following additions: > -in vararg handling, registers are marked to be live, to not confuse the register scavenger Looks good. You can try running with -verify-machineinstrs to detect

On Thu, 2010-06-03 at 02:53 +0200, Jakob Stoklund Olesen wrote: > If you are using the local register allocator, please try switching to the fast allocator and report any bugs you find. > Tried it, and it seems to break quite a big chunk of our tests on SPU :) Before r103488 ("Mostly rewrite RegAllocFast") there was no problem. But with r103488, I get a:

Hi, On SPU, variables in the .bss section that are allocated with the .lcomm directive are not aligned on 16 byte boundaries. This causes misaligned loads, as the generated assembly assumes this "default" alignment. A patch to disable .lcomm in favour of '.local .comm' is attached. kalle P.s. As an example, the following function returns '3', when '5' is

Chris Lattner wrote: >>It is possible to write multi-instruction pattern, e.g. >>X86InstrSSE.td line 1911. But how are you defining HI16 and LO16? >>Sounds like you want to define them as SDNodeXform that returns upper >>and lower 16 bits respectively. Take a look at PSxLDQ_imm in >>X86InstrSSE.td as an example. > > > Another good example is the PPC

On Jan 9, 2007, at 5:23 PM, Scott Michel wrote: > Chris Lattner wrote: >>> It is possible to write multi-instruction pattern, e.g. >>> X86InstrSSE.td line 1911. But how are you defining HI16 and LO16? >>> Sounds like you want to define them as SDNodeXform that returns >>> upper >>> and lower 16 bits respectively. Take a look at PSxLDQ_imm in

On Thu, May 7, 2009 at 9:39 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Thu, May 7, 2009 at 9:03 AM, Kshitiz Garg <ksh.cseiitk at gmail.com> wrote: >>    I was trying to extract out the IR for some CELLBE code. However i >> was not able to compile with llvm-gcc. > > Can you give a couple examples of error messages you're getting? llvm-gcc

On Jun 4, 2010, at 1:57 AM, <Kalle.Raiskila at nokia.com> <Kalle.Raiskila at nokia.com> wrote: > On Thu, 2010-06-03 at 02:53 +0200, Jakob Stoklund Olesen wrote: >> If you are using the local register allocator, please try switching to the fast allocator and report any bugs you find. >> > Tried it, and it seems to break quite a big chunk of our tests on SPU :)

On Thu, May 7, 2009 at 9:25 AM, Kshitiz Garg <ksh.cseiitk at gmail.com> wrote: >> Can you give a couple examples of error messages you're getting? >  llvm-gcc -emit-llvm -S        -W -Wall -Winline -Wno-main  -I.  -I > /opt/cell/sysroot/usr/spu/include -I > /opt/cell/sysroot/opt/cell/sdk/usr/spu/include  -O3 -c simpleDMA_spu.c > simpleDMA_spu.c:42:23: error:

Hi, I'm doing some preliminary work to get Clang to compile for PS3 targets. As an intermediate step in that direction, could someone do me the favor of reviewing and submitting the enclosed patch, or giving me feedback on it? Basically, I need to be able to differentiate the triple for a PS3 target. These are the triples currently used in the gcc-based compiler from the PS3 devkit: