search for: hurrah

...um, struct vhost_log *log, unsigned int *log_num, struct vring_desc *indirect) { [...] /* We will use the result as an address to read from, so most * architectures only need a compiler barrier here. */ read_barrier_depends(); --->8 Unfortunately, although the barrier is commented (hurrah!), it's not particularly enlightening about the accesses making up the dependency chain, and I don't understand the supposed need for a compiler barrier either (read_barrier_depends() doesn't generally provide this). Does anybody know which accesses are being ordered here? Usually you&...

...um, struct vhost_log *log, unsigned int *log_num, struct vring_desc *indirect) { [...] /* We will use the result as an address to read from, so most * architectures only need a compiler barrier here. */ read_barrier_depends(); --->8 Unfortunately, although the barrier is commented (hurrah!), it's not particularly enlightening about the accesses making up the dependency chain, and I don't understand the supposed need for a compiler barrier either (read_barrier_depends() doesn't generally provide this). Does anybody know which accesses are being ordered here? Usually you&...

Apologies for cross-posting. We''ve been asked to do a job for a client who wants to embrace agile development methodologies. Hurrah! However, our standard contract was written for the 1980s. It is full of phrases like "agreed specification" and "change request procedure" and so on. I was wondering, how do other people get around this in contract forms with their clients? I was thinking of just revert...

...[...] >> >> /* We will use the result as an address to read from, so most >> * architectures only need a compiler barrier here. */ >> read_barrier_depends(); >> >> --->8 >> >> Unfortunately, although the barrier is commented (hurrah!), it's not >> particularly enlightening about the accesses making up the dependency >> chain, and I don't understand the supposed need for a compiler barrier >> either (read_barrier_depends() doesn't generally provide this). >> >> Does anybody know which...

On 07/18/2019 11:32 AM, Rowland penny via samba wrote: > Hurrah and this part is easy ;-) > > You are starting the wrong binary, you need to start 'samba-ad-dc' , > you may have to unmask it though. Yippee, that worked!? I was able to unmask (systemctl unmask samba-ad-dc) and samba started.? wbinfo --ping-dc returns the new DC!? Also get cor...

...it, and must say: great work guys. So when i got my raspberry pi, and having read that llvm is better at arm than gcc, i compiled llvm on the pi. The pi has a soc with armv6 (i don't know what that means exactly though). The pi is not fast and llvm with clang compilation took 22 h, but worked. hurrah. Then i compiled llvm/clang with itself and was pleased it took "only" 12 hours. even better. But then I compiled linpack and clang numbers were less than 1/4 off gcc compiled :-( (9000kFlops about) Now according to this http://elinux.org/RPi_Performance there is something with com...

...ad >> of heimdal? > > Talk to Andreas, Guenther and Alexander for the latest. > >> The intention of our project "invis-server" is to bring samba 4 with >> AD DC functionality into openSUSE. Therefor we need arguments for >> the coming discussion. > > Hurrah ! I'm really glad to hear this ! If you could > coordinate with the people doing the Heimdal -> MIT > work then we can get there faster. > > Cheers, > > Jeremy. I'd also encourage you to take a look at the Fedora "rawhide" buindles, for tracing of cha...

On 07/18/2019 11:04 AM, Rowland penny via samba wrote: > I have never had to deal with a W2K AD server, but from my > understanding W2K didn't have the DNS records in AD, so I wondered if > yours didn't either. I am running out of ideas now. > > Have you tried Tim's patch ? > > Just in case you don't know how to apply the patch, it is pretty > simple, it

Hi List, I do my best to ask my question in english. ;-) Samba4 integrated heimdal kerberos to do the kerberos work for Active Directory. Some Linux Distributions like fedora/RedHat and openSUSE/SUSE don't accept heimdal even if it is shipped inside samba. Their argument is that heimdal isn't maintained since 2012. Compiling samba against MIT krb5 results in Samba-Packages without

Yesterday, after a long run, i've finally upgraded my DCs to stretch/samba4.9, using Louis repos. Hurrah! ;-) Looking forward, eg: http://apt.van-belle.nl/debian/dists/ seems to me that i can advance to 4.10 in stretch, but to go further i need buster (probably because of python deps, right?). Louis, i think we need a matrix of debian-samba compatibility... ;-) -- dott. Marco Gaiarin...

...d suggested that this adapter might not work on pre-2.1 apps (http://www.ruby-forum.com/topic/156143), but it appears to work just fine here. Furthermore, the ruby-pg adapter project is in the reliable hands of Jeff Davis, a superstar whose abilities mean that PG has a brilliant future with Rails. Hurrah for that! Anyway, I hope that this saves someone else some time. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5T...

...nther and Alexander for the latest. >> > >> >> The intention of our project "invis-server" is to bring samba 4 with >> >> AD DC functionality into openSUSE. Therefor we need arguments for >> >> the coming discussion. >> > >> > Hurrah ! I'm really glad to hear this ! If you could >> > coordinate with the people doing the Heimdal -> MIT >> > work then we can get there faster. >> > >> > Cheers, >> > >> > Jeremy. >> >> I'd also encourage you to tak...

...om the index, which is why I don't think this is the right approach. Arranging to delete the right documents might not be too hard. All documents for a particular subsite are indexed by the same H and P term combination so we can just check each deletion candidate against those two postlists (hurrah for skip_to!) That should be pretty efficient. The only problem I can see is that if indexroot is specified, we also need to check each remaining deletion candidate against that, which I think means we have to look in the document data for each one. Ick, that's probably going to be slow. Or...

...unanswered (I am abroad again !), but *think* the Liebert driver had been stopped. I can report the following updates for my linux setups; SuSE/FreeBSD/FreeNAS [remember here I am trying to make nut work for a physical machine running FreeNAS]: * SuSE Live CD will successfully obtain descriptors. Hurrah! * I am not sure how being able to build NUT for a SuSE environment may help, but I think I am in a situation where I can do it. - I now have a 'Live' USB stick and a partition on it that is persistent. This also reads the descriptors. * my NAS box has now been updated to FreeNAS 9.1 ... b...

Hi *, using the following snippet of code .. ------------------------------------------------------------------------ [...] 7 if ! ($installplugins in [ true, false ]) { 8 fail("nrpe installplugins parameter must be true or false") 9 } [...] 24 if $installplugins == true { 25 package { ["mypluginpackage", 26 ensure => installed } 27

On Aug 11, 2013, at 12:04 PM, Paul Smith wrote: > Anyone have any advice what I need to do next? A while back, you sent me the pcap file from the Windows side, but there was an open question as to whether the USB requests were standard Windows HID driver requests, or whether the Liebert software was still running in the background. Also, the SuSE Live CD seems to be the only non-Windows

...; > [...] > > > > /* We will use the result as an address to read from, so most > > * architectures only need a compiler barrier here. */ > > read_barrier_depends(); > > > > --->8 > > > > Unfortunately, although the barrier is commented (hurrah!), it's not > > particularly enlightening about the accesses making up the dependency > > chain, and I don't understand the supposed need for a compiler barrier > > either (read_barrier_depends() doesn't generally provide this). > > > > Does anybody know w...

...; > [...] > > > > /* We will use the result as an address to read from, so most > > * architectures only need a compiler barrier here. */ > > read_barrier_depends(); > > > > --->8 > > > > Unfortunately, although the barrier is commented (hurrah!), it's not > > particularly enlightening about the accesses making up the dependency > > chain, and I don't understand the supposed need for a compiler barrier > > either (read_barrier_depends() doesn't generally provide this). > > > > Does anybody know w...

...> struct vring_desc *indirect) > { > [...] > > /* We will use the result as an address to read from, so most > * architectures only need a compiler barrier here. */ > read_barrier_depends(); > > --->8 > > Unfortunately, although the barrier is commented (hurrah!), it's not > particularly enlightening about the accesses making up the dependency > chain, and I don't understand the supposed need for a compiler barrier > either (read_barrier_depends() doesn't generally provide this). > > Does anybody know which accesses are being or...

...t; struct vring_desc *indirect) > { > [...] > > /* We will use the result as an address to read from, so most > * architectures only need a compiler barrier here. */ > read_barrier_depends(); > > --->8 > > Unfortunately, although the barrier is commented (hurrah!), it's not > particularly enlightening about the accesses making up the dependency > chain, and I don't understand the supposed need for a compiler barrier > either (read_barrier_depends() doesn't generally provide this). > > Does anybody know which accesses are being o...