similar to: Feedback request on a tentative proposal to enhance smb.conf symlink-related params

On Thu, Mar 01, 2018 at 10:48:02AM +0000, Stilez Stilezy wrote: > As mentioned in another thread, I notice that the params used to control > symlinks feel a bit inefficient and inelegant, and quite limited.  I think > there might be a good opportunity to simplify and also make their management in > Samba more powerful and adaptable to use-cases.  I'm guessing this list is a >

https://bugzilla.samba.org/show_bug.cgi?id=13364 Bug ID: 13364 Summary: rsyncd clips trims relative symlinks outside of source tree Product: rsync Version: 3.1.3 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee:

Hello all, I have,say 4 R objects... bar1, bar2, bar3, bar4.. that I'd like to include in an R package "foobar". The desired functionality would be: > library(foobar) > data(foo) > ls() [1] "bar1" "bar2" "bar3" "bar4" I've tried the following two approaches: 1) I created the file 'datalist' under pre-build directory

Thank you. So, If I understand correctly, "ordinary" "wide links = yes", means Samba *will* traverse an existing symlink that points outside the root of the share, if permissions allow. However because it *also* disables SMB1 Unix extensions, it *also* prevents the user from creating or modifying symlinks on the share, so in wffect it inherently prevents this being

Thanks - that much I (pretty much) got. Its really the "wide links" option that isn't well distinguished/clarified. *insecure* wide links is much more clear, although the detail you've given helps a lot. What exactly is the "ordinary" "wide links = yes" option going to do (with or without Unix extensions), and how does it compare/how much exposure to

Hello Mehdi Amini, Sorry for slow progress this week but it was due to interesting mistake of mine. I had build llvm with ipra enable by default and that build files were on my path ! Due to that next time I tried to build llvm it was terribly slow (almost 1 hour for 10% build ). I spend to much time on fixing this by playing around with environment variables, cmake options etc. But I think this

I'd like to understand reasonably fully,, the difference between the two options "wide links" and "allow insecure wide links" in smb.conf. The docs make them sound very similar but as there are obvious security implications for anything to do with symlink scope, it's important to know what each of them allows/blocks and where they differ. Interestingly, only the

Dear List, I need a barplot with vertical bars. Each bar should have a label. The problem is, that the labels are too long, so they overlap, or only every seccond label is displayed in the output. Here is a little syntax: dd <- c(100,110,90,105,95) barplot(dd,names.arg=c('Conduct Disorders','Attention Deficit', 'Eating Disorders',

On Sun, Jun 5, 2016 at 8:56 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > > On Jun 4, 2016, at 7:56 PM, vivek pandya <vivekvpandya at gmail.com> wrote: > > > > Hello Mehdi Amini, > > > > Sorry for slow progress this week but it was due to interesting mistake > of mine. I had build llvm with ipra enable by default and that build files >

On Sun, Jun 5, 2016 at 9:15 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Jun 4, 2016, at 8:32 PM, vivek pandya <vivekvpandya at gmail.com> wrote: > > > > On Sun, Jun 5, 2016 at 8:56 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> > On Jun 4, 2016, at 7:56 PM, vivek pandya <vivekvpandya at gmail.com> >> wrote:

Hello, I want to have an operation foo with variable number of operands, and I am trying to achieve it using multiple operations. Let's say I want to have [FOO r1, r2], I am constructing the DAG as follows : consumeArg(r1) -> consumeArg(r2) -> FOO -> arg(r1) -> arg(r2) Note that the arrows are all "Chain"s. I need to have consumeArg(r1) because, I don't want the

This is slightly off-topic, I guess, but I'm not sure who better to ask for help. I'm active within the FreeNAS community and involved in their (FreeBSD based) documentation work. There is a long standing bug ticket - years old now - to update their "network ups tools" docs page, to cover Ethernet attached UPS that use nut for the link. Currently the docs mainly describes

Hi Ben, I've been working with an mmio-constrained pci hierarchy intended almost solely for nvme devices and switches. Binding nouveau to an NV50-based gpu results in a kernel panic as the device cannot be fully mapped. I've made modifications in nv50 and vmm to unbind the driver from this hierarchy, and modified gf100 assuming it will have the same issue. 1/4 also includes a fix where

Yes, the hairy-edges of undefined behaviour - UB is UB. It does mean that given: __attribute__((noinline)) int foo(int a, int b) { return a + b; } int bar1(int x) { return foo(x, INT_MIN); } int bar2(int x) { return x + INT_MIN; } 'bar1' and 'bar2' have different outcomes. However, I think that the new optimisation is neat and valid and I am not suggesting that it should

https://bugzilla.samba.org/show_bug.cgi?id=13364 --- Comment #3 from Chris Severance <samba.severach at spamgourmet.com> --- >enable munge-symlinks. That way the client will get back the same out-of-tree symlink as it started with This is a lousy option for backups. The only way to get my original links back is to pull the restore through rsync. Restoring directly from the rsyncd server

I''m trying now to do "sudo fixrbconfig" in the terminal, and I get this: /usr/lib/ruby/1.8/powerpc-darwin8.0/ruby.h does not exist. This probably means you haven''t yet installed Xcode from the Tiger DVD. You won''t be able to compile Ruby extensions without it. Please install it then rerun this program. I''m on an intel mac. Am I unable to use

Dear Mentors, I will be writing test cases for IPRA for lit infrastructure. Following 2 basic test cases I have identified : Program that does not have recursive function call. Program that does have recursive calls. Please suggest some other test cases or provide some hints. Sincerely, Vivek -------------- next part -------------- An HTML attachment was scrubbed... URL:

I am another person who has had trouble documenting S4 classes and (particularly) methods. The methods package itself is pretty cool by the way, but it is a pity that there are as yet no guidelines on S4 in the "Writing R Extensions" document. I have actually put together a guide on S4 documentation myself for the use of my own lab which is at

Do not pass GLOB_MARK as flag for glob(3) in the daemon implementation of glob, so names of directories will not have a trailing slash. This allows users to have filenames that can be used with other tools, such as rm. Add a new test to check this (based on RHBZ#1293271). A mild behaviour change is that users of the glob API now need to append the slash when building paths using its results.

Commit bbb163e18960 ("drm/nouveau/bar: implement bar1 teardown") introduced add a teardown helper function for BAR1. During initialisation of the Nouveau, initially all the teardown helpers are called once, before calling their init counterparts. For gk20a, after the BAR1 teardown function is called, the device is hanging during the initialisation of the FB sub-device. At this point it