similar to: Samba 4 to replicate my samba3.6 config

We are running Arch Linux as a new sever and only has samba4 available officially I am trying to migrate my samba 3 config to work with samba 4 I currently use samba to authenticate windows users to use our Linux shares using the unix groups as the valid users. Here is the problem. I can see the shares using samba 4 but it uses the "Domain users" group to write to the shares and not

In some tests of moving from samba3.5 to samba3.6 I find that the netapp filer don't recognize the groups of the users. Anybody knows where is the problem? Thanks. -- ------------------------- Alejandro Escanero Blanco Servicio de Inform?tica Sistemas - GISI Tel: 671 569 262 (769262) Edificio Empresarial Aljarafe, mod. 36 41940 Tomares (Sevilla)

Hello. I'm trying to update their samba3.6 to the new version. Use the instructions https://wiki.samba.org/index.php/Samba4/samba-tool/domain/classicupgrade/HOWTO Just use the latest build of sernet. My samba3.6 work is not in the role AD, and as a standart file server with LDAP Backend, which stores users and groups. I'm trying to take advantage of the update utility. But getting

On 23/06/15 10:35, Florentin Richard wrote: > Hi i'm actually trying to migrate my samba 3.6 PDC NT-4 domain with openldap as backend to samba4 AD type domain witch bind_dlz > > so i followed the documentation https://wiki.samba.org/index.php/Samba_Classic_Upgrade_%28NT4-style_domain_to_AD%29 > the command : > samba-tool domain classicupgrade --dbdir=/root/sambe/

Hi i'm actually trying to migrate my samba 3.6 PDC NT-4 domain with openldap as backend to samba4 AD type domain witch bind_dlz so i followed the documentation https://wiki.samba.org/index.php/Samba_Classic_Upgrade_%28NT4-style_domain_to_AD%29 the command : samba-tool domain classicupgrade --dbdir=/root/sambe/ --use-xattrs=yes --realm=mydom.local --dns-backend=BIND9_DLZ

I'm working on lldb. I've just submitted a very small change (r217229) to Triple.h/.cpp. Soon after I get a mail subject: buildbot failure in LLVM on lld-x86_64-darwin13 Details: http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571 Blamelist: mg11 My small change certainly did not cause lldb's build to fail on my machine. I looked into the build-log:

Hi, We have some DSP architectures (kalimba) which have 24-bits as their "minimum addressable unit". So this means that the sizeof a char (and an int and a short for that matter) is 24-bits. I quickly read the posted link WritingAnLLVMBackend.html but did not see an obvious answer to the following question: Is it possible to write a backend that faithfully represents these

Eric Christopher wrote: > On Wed, Jul 9, 2014 at 11:39 AM, Jonathan Roelofs > <jonathan at codesourcery.com> wrote: >> >> On 7/9/14, 12:33 PM, Eric Christopher wrote: >>> Any reason why you deleted code that isn't related? >>> >>> -eric >>> >>>> - enum SubArchType { >>>> - NoSubArch, >>>> -

Hello LLVMdev!! Yesterday I posted a patch request to the llvm-commits list requesting that someone could apply a patch to Triple.h and Triple.cpp for me. I didn't get any response so I wondered whether I should have posted to this list instead. My story is as follows: we are trying to get lldb/llvm support for CSRs range of Kalimba DSPs. Eventually we are planning to hire someone to

Hi Johnny, Thanks for this - particularly the tip about cfe-dev. I'm currently trying to coerce lldb to debug these type of architectures (our current toolchain already outputs good dwarf info). However, I'm struggling since lldb has just assumes that the size of a byte is universally 8-bits. At some stage, I *think* at some stage we'd like to derive a compiler, from the "same

Hi Fred, Thanks. How did you get to " The build log show this error: /Users/buildslave/as-bldslv9/lld-x86_64-darwin13/llvm.src/lib/Target/ARM/MCTargetDesc/ARMMCTargetDesc.cpp:92:11: error: enumeration values 'KalimbaSubArch_v3', 'KalimbaSubArch_v4', and 'KalimbaSubArch_v5' not handled in switch [-Werror,-Wswitch] switch (triple.getSubArch()) { " from here

Hi Patrik, Thanks for this note. It's encouraging to read there has been some provision made for non-8-bit bytes. I'm not a compiler/backend expert, (although maybe I'll need to be soon!), so I won't look at the patches right now, however may at some stage in the future myself or colleague may request these patches from yourself. Yes, our 24-bit architectures have non-power-of-2

Hi, I'm a bit confused about how Asterisk decides in which order of preference it should list the different codecs in its SDP message during SIP call setup. In my sip.conf [general] section I've got disallow=all allow=gsm allow=ulaw allow=alaw But when Asterisk bridges a call from an E1 to VoIP it sends out an INVITE with the codecs listed in the following order of preference

How does LLVM generate machine code for different architectures? For example, the machine code for x86 and amd will vary. How does LLVM convert its IR to machine code for different architectures.Can you please explain the approach? Is it just write two different programs for two different architectures and pass a flag to the compiler based on which machine code you want to generate? Thanks a lot

On 7/9/14, 12:33 PM, Eric Christopher wrote: > Any reason why you deleted code that isn't related? > > -eric > >> - enum SubArchType { >> - NoSubArch, >> - >> - ARMSubArch_v8, >> - ARMSubArch_v7, >> - ARMSubArch_v7em, >> - ARMSubArch_v7m, >> - ARMSubArch_v7s, >> - ARMSubArch_v6, >> -

> There are no dumb questions. My answer might seem a bit disappointing though > :-) I just scrolled quickly though the log. The errors appear in red, they > were easy to spot. Depending on the build system used, you can also search > for specific patterns (like *** for make) in the log. Specifically, it's the "stdio" link under the red failing step in this case.

Hi, I'm looking into support for SS7 and I found an article (http://www.openss7.com/news13022002.html) which says that OpenSS7 supports Linux Support Inc's T400P-SS7 Quad T1 and E400P-SS7 Quad E1 PCI interface cards. It also says that Linux Support Inc is the primary sponsor of Asterisk. However I cannot find these cards on the Asterisk hardware page

Hi all, We use linux-2.4.20 in one of our products and we've found what looks to be a problem in the bridge module. (I know this is old code but we don't send our customers kernel upgrades unless we really have to!) The problem is that some of our bridges have become orphaned from the bridge module. Specifically ifconfig ourbridgename shows that the device "ourbridgename"

Hi, I'm trying to implement a vorbis decoder, and am having some trouble getting it to work with stereo vorbis data. It's giving me some PCM output which is roughly right, but it has artefacts. I think it's most likely something to do with my handling of floor decode/curve synthesis. My first thoughts are that I'm handling the submap number/floor mapping incorrectly; I'm

ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal