search for: _explicit_

How can I get a full URL for anything on CRAN? Using Safari, Google Chrome, and Firefox under OS X 10.11.2, I select a CRAN mirror from "www.r-project.org" and get a URL like "https://cran.rstudio.com/". Then I select "packages" and get a different web page, but the URL displayed doesn't change. I'd like to access the full URL of a vignette in a

...supported. Shorewall 1.4 behavior is the same as 1.3 with ALLOWRELATED=Yes. 7. The ''multi'' interface option is no longer supported. Shorewall will generate rules for sending packets back out the same interface that they arrived on in two cases: a) There is an _explicit_ policy for the source zone to the destination zone. An explicit policy names both zones and does not use the ''all'' reserved word. b) There are one or more rules for traffic for the source zone to or from the destination zone including rules that use the ''...

...loud.r-project.org/web/packages/sos/vignettes/sos.pdf This is of the form ${SERVER}/web/packages/${PACKAGE}/${VIGNETTE} I have been using url such as the one in 5) for a long while. Works like a charm. Now, from your vague text above, maybe you prefer NOT to use a CDN. In that case, insert an _explicit_ server, say Berkeley's mirror and you get https://cran.cnr.berkeley.edu/web/packages/sos/vignettes/sos.pdf but that is _still_ of the form ${SERVER}/web/packages/${PACKAGE}/${VIGNETTE} yet simple uses a different value for ${SERVER}. Makes sense? Dirk -- http://dirk.eddelbuettel.com...

...supported. Shorewall 1.4 behavior is the same as 1.3 with ALLOWRELATED=Yes. 7. The ''multi'' interface option is no longer supported. Shorewall will generate rules for sending packets back out the same interface that they arrived on in two cases: a) There is an _explicit_ policy for the source zone to or from the destination zone. An explicit policy names both zones and does not use the ''all'' reserved word. b) There are one or more rules for traffic for the source zone to or from the destination zone including rules that use th...

...nger supported. Shorewall 1.4 behavior is the same as 1.3 with ALLOWRELATED=Yes. 7) The ''multi'' interface option is no longer supported. Shorewall will generate rules for sending packets back out the same interface that they arrived on in two cases: a) There is an _explicit_ policy for the source zone to the destination zone. An explicit policy names both zones and does not use the ''all'' reserved word. b) There are one or more rules for traffic for the source zone to or from the destination zone including rules that use the ''all&...

...nger supported. Shorewall 1.4 behavior is the same as 1.3 with ALLOWRELATED=Yes. 8) The ''multi'' interface option is no longer supported. Shorewall will generate rules for sending packets back out the same interface that they arrived on in two cases: a) There is an _explicit_ policy for the source zone to the destination zone. An explicit policy names both zones and does not use the ''all'' reserved word. b) There are one or more rules for traffic for the source zone to or from the destination zone including rules that use the ''all&...

Apparently there is one or more concepts that I do not fully understand from the descriptions of a function and the apply material. I have been reading the mail from this forum and have learned much but, in this case, what I have been reading here and from the manual isn't enough. The following code produces what I want with the for loop. From what I have read from this forum, a for

...hich modifies ptes in a loop needs to avoid looking at the modified ptes. 9/13 fixes the one place where it happens. 11/13 depends on removing these read hazards for correctness when running under a direct page table hypervisor which batches updates. However, it is generally agreed that using an _explicit_, rather than an _implicit_ notion of batching makes it easy to find and reason about the paths which are doing batching. This allows easy inspection to remove read hazards from the code. 13/13 "Put .note.* sections into a PT_NOTE segment in vmlinux" is mostly here to shake out problems...

...hich modifies ptes in a loop needs to avoid looking at the modified ptes. 9/13 fixes the one place where it happens. 11/13 depends on removing these read hazards for correctness when running under a direct page table hypervisor which batches updates. However, it is generally agreed that using an _explicit_, rather than an _implicit_ notion of batching makes it easy to find and reason about the paths which are doing batching. This allows easy inspection to remove read hazards from the code. 13/13 "Put .note.* sections into a PT_NOTE segment in vmlinux" is mostly here to shake out problems...