search for: micromanaging

On Fri, Aug 11, 2017 at 11:17 AM, Mark Haney <mark.haney at neonova.net> wrote: > On Fri, Aug 11, 2017 at 1:00 PM, Chris Murphy <lists at colorremedies.com> > wrote: > >> Changing the subject since this is rather Btrfs specific now. >> >> >> >> >> >> >> Sounds like a hardware problem. Btrfs is explicitly optimized for SSD,

>> What size is recommended for the /boot partition? After doing a fresh >> install and lengthy backup restore I realized I only made it 200M. Is >> this going to be a problem? > > Mine was about 500 MB and I removed some kernels because I got a warning the > partition was getting full. > > With only two kernels installed, 182 MB are used. I would suggest 1 GB

...a lot of decisions for the sake of efficiency for things that cannot even be possibly measured. Exceptions vs no exceptions in the compiler was one of those. Algorithm complexity and choice is what usually dominates efficiency unless you are talking about some tight loop in the kernel of an OS. Micromanaging small things usually ends up making things more complicated and in the end; slower, bigger, more error prone and harder to maintain. My 2c. Reed On 10/03/2012 07:07 PM, Sean Silva wrote: > Hi all, I'm sure that the last thing that you want to think about is > TableGen's guts, but...

...y philosophical reason why there's no bundled default for the control path if none is given, or is this simply one of those things that no one ever got around to doing? The analogous feature in PuTTY/plink (and also IntelliJ) Just Works, so coming from those clients this feels like ssh(1) needs micromanaging. Thing 4: Are there any widespread conventions on where these socket files go, or does everyone pretty much do their own ad-hoc thing? Thing 5: Is there any way to tell the ssh client "try to connect using path/to/my-ctl.socket, and if it doesn't work, then exit with an error code"?...

...the language, which could have significant positive benefits across the codebase by e.g. making target descriptions easier to write and maintain. > Algorithm complexity and choice is what usually dominates efficiency unless > you are talking about some tight loop in the kernel of an OS. > Micromanaging small things usually ends up making things more complicated > and in the end; slower, bigger, more error prone and harder to maintain. Indeed. Generating the .inc files actually is a small fraction of the build time. However, the number of files dependent on those .inc files is huge, and the cu...

Hi there, I''m looking for a powerful pdf creation libary. I already tried: prawn - Nice handling but way too slow when lots of tables are involved PDFKit - too slow Actually I''m trying prince with xml input. It''s pretty fast but I don''t like the page-break control. I need a libary which can create pdf''s with up to 90 pages with lots of nested

...losophical reason why there's no bundled default for the control path if none is given, or is this simply one of those things that no one ever got around to doing? > The analogous feature in PuTTY/plink (and also IntelliJ) Just Works, so coming from those clients this feels like ssh(1) needs micromanaging. This could be done, but see #2. Also Unix domain sockets are finicky wrt maximum path lengths and this can be a problem if the path is long, e.g. a user with a very long username (e.g. a GUID) connects to a host with a long hostname. > Thing 4: Are there any widespread conventions on where th...

Hi all, I'm sure that the last thing that you want to think about is TableGen's guts, but I'm pursuing a course in bringing TableGen up to snuff with the rest of LLVM. Basically, I would like to introduce a "TGContext" class (by analogy with LLVMContext) to harbor a proper unique'd type system and BumpPtr allocate all of TableGen's data (RecTy's, Record's,

Hello Ingo, On Fri, Jun 23, 2017 at 1:26 AM, Ingo Schwarze <schwarze at usta.de> wrote: > > Hi Emmanuel, > > Emmanuel Deloget wrote on Fri, Jun 23, 2017 at 12:26:47AM +0200: > > > * the openssl team has no real incentive to propose a shim ; > > If major application projects refuse to support their new release, > thus putting pressure on operating system

On Wed, 16 Nov 2016, Matt wrote: > Can I just change yum.conf with the setting installonly_limit=2 to > limit kernels installed too two? I really wouldn't. You can scrape by with that if you also make sure you don't have dracut-config-rescue installed, but you can find yourself struggling even with that, and so have to micromanage even further. Upgrade a kmod, watch /boot fill

In Sweave, if the locale is set to C, non-ASCII characters are not handled nicely even if I declare the encoding of the file to be "UTF-8". I'm trying to find a workaround for this, because I'm using Sweave from within TeXShop. TeXShop runs its typesetting engines in the C locale, and non-ascii characters are messed up. Is there a way to declare that I am in a

...losophical reason why there's no bundled default for the control path if none is given, or is this simply one of those things that no one ever got around to doing? > The analogous feature in PuTTY/plink (and also IntelliJ) Just Works, so coming from those clients this feels like ssh(1) needs micromanaging. This could be done, but see #2. Also Unix domain sockets are finicky wrt maximum path lengths and this can be a problem if the path is long, e.g. a user with a very long username (e.g. a GUID) connects to a host with a long hostname. > Thing 4: Are there any widespread conventions on where th...

We're looking at getting an HBR (that's a technical term, honkin' big RAID). What I'm considering is, rather than chopping it up into 14TB or 16TB filesystems, of using xfs for really big filesystems. The question that's come up is: what's the state of xfs on CentOS6? I've seen a number of older threads seeing problems with it - has that mostly been resolved? How does

...y philosophical reason why there's no bundled default for the control path if none is given, or is this simply one of those things that no one ever got around to doing? The analogous feature in PuTTY/plink (and also IntelliJ) Just Works, so coming from those clients this feels like ssh(1) needs micromanaging. Thing 4: Are there any widespread conventions on where these socket files go, or does everyone pretty much do their own ad-hoc thing? Thing 5: Is there any way to tell the ssh client "try to connect using path/to/my-ctl.socket, and if it doesn't work, then exit with an error code"?...

...losophical reason why there's no bundled default for the control path if none is given, or is this simply one of those things that no one ever got around to doing? > The analogous feature in PuTTY/plink (and also IntelliJ) Just Works, so coming from those clients this feels like ssh(1) needs micromanaging. This could be done, but see #2. Also Unix domain sockets are finicky wrt maximum path lengths and this can be a problem if the path is long, e.g. a user with a very long username (e.g. a GUID) connects to a host with a long hostname. > Thing 4: Are there any widespread conventions on where th...

Changing the subject since this is rather Btrfs specific now. On Fri, Aug 11, 2017 at 5:41 AM, hw <hw at gc-24.de> wrote: > Chris Murphy wrote: >> >> On Wed, Aug 9, 2017, 11:55 AM Mark Haney <mark.haney at neonova.net> wrote: >> >>> To be honest, I'd not try a btrfs volume on a notebook SSD. I did that on >>> a >>> couple of

Hello everybody, ? ? I saw that another discussion about OpenSSL 1.1 support started on this list, and I'd like to know what is the current status about this. >From what I understand, at least ?one patch set already exists: ? ? a github PR [1] from , Kurt Roeckx announced on the list in september 2016 [2] ? and which also exist as a fedora patch [3]? (I haven't checked the details,

OpenSC has taken a different approach to OpenSSL-1.1. Rather then writing a shim for OpenSSL-1.1, the OpenSC code has been converted to the OpenSSL-1.1 API and a sc-ossl-compat.h" file consisting of defines and macros was written to support older versions of OpenSSL and Libressl. https://github.com/OpenSC/OpenSC/blob/master/src/libopensc/sc-ossl-compat.h The nice part of this approach is

Hello. I installed under Ubuntu (Dapper) Park Place. I followed the instructions given at the RedHanded site. I get the following mongrel error when launching the application: ** Please login in with `admin'' and password `pass@word1'' ** You should change the default password or delete the admin at soonest chance!/usr/lib/ruby/gems/1.8/gems/mongrel-0.3.12.5/lib/mongrel.rb:584:in