search for: foretelling

Samba bottlenecks? As my network grows I'll probably find Samba bottlenecks sooner or later - such as saturated bandwidth, internal I/O, bloated user database. Are there any signs to read foretelling the apocalypse? Are the any viable solutions? -- J?rgen Persson

According to the MikTex bug reports [1], MikTex 2.9 has removed texi2dvi.exe last week (on 2015-09-29) as "it was not compatible (anymore) with the original shell script texi2dvi (GNU Texinfo)." I found this out the hard way as I just (unknowingly) updated MikTex this evening, and then, while building R-devel_2015-10-08 on Windows7 64bit using the Rtools 3.3 toolchain (4.9.3 branch), had

Hmm, look in MkRules.dist for the setting you failed to make .... Obviously available in R-patched and R-devel only as we cannot foretell such changes. On 09/10/2015 06:24, Avraham Adler wrote: > According to the MikTex bug reports [1], MikTex 2.9 has removed > texi2dvi.exe last week (on 2015-09-29) as "it was not compatible > (anymore) with the original shell script texi2dvi (GNU

On Tue, 31 Jul 2018 09:48:37 -0700 Gregory Sloop via samba <samba at lists.samba.org> wrote: > Top posting: > > So, I do want the five years of LTS in 18.04. {I think - see below.] > > A substantial reason I'm not using debian/devuan is LTS support. Debian has its own version of LTS: https://wiki.debian.org/LTS >I'm > glad to be schooled in that regard, if

Top posting: So, I do want the five years of LTS in 18.04. {I think - see below.] A substantial reason I'm not using debian/devuan is LTS support. I'm glad to be schooled in that regard, if someone has arguments to make. But I generally want to install a VM/Server/Box for a client and leave it alone as much as possible for as long as possible, and while it still works as initially