search for: 490mb

Will (does) Centos 6 require 512Mb of memory for the GUI install like FC14 or the lower requirement of FC13? My ASUS EE 700 has ~490Mb of memory (vidoe steals some from the 512Mb base) and FC14 switches to text install and does not install any GUI, leaving the boot in test mode. I recall a message earlier that 6 is based off of 14, but not the final Anaconda, thus my question. It would be NICE if the install can work with at...

...o fix this with a smarter implementation). As far as object file sizes go, in the resulting clang binary (2.3GB), the new .debug_names section takes up about 160MB (7%), which isn't negligible, but considering that it supersedes the .debug_pubnames/.debug_pubtypes tables whose combined size is 490MB (21% of the binary), switching to this table (and dropping the other two) will have a positive impact on the binary size. Further reductions can be made by merging the individual indexes into one large index as a part of the link step (which will also increase debugger speed), but it's hard to...

...000, 4096) = 0 [pid 17960] select(5, NULL, [4], NULL, {60, 0} (then very long pause with no updates). I'm using rsync 2.5.7, release 5.3E on Red Hat Enterprise Linux 3. The command is running as root. Weird thing is: there's another directory on the machine called 'logs', with 490MB of data. Running: rsync -vvvr --progress /local/CA/eTrustDirectory/dxserver/logs /local/CA/archive works fine. Syncing the ldif dir to /tmp/foo also fails. So it looks like there's something wrong with the ldif dir - the only thing that makes it different from the dir that works is that it...

On Wed, 17 Jan 2018 17:13:36 +0100, Pavel Labath via lldb-dev wrote: > so I'm writing this email to see if there's anyone > else interested in this topic, and to try to synchronize our efforts. I am sure interested in DWARF-5 .debug_names. I wrote its producer+consumer for GDB (but not producing/using DW_IDX_DIE_offset as GDB cannot use it). > 1. add .debug_names support to

...t;> >> As far as object file sizes go, in the resulting clang binary (2.3GB), >> the new .debug_names section takes up about 160MB (7%), which isn't >> negligible, but considering that it supersedes the >> .debug_pubnames/.debug_pubtypes tables whose combined size is 490MB >> (21% of the binary), switching to this table (and dropping the other >> two) will have a positive impact on the binary size. Further >> reductions can be made by merging the individual indexes into one >> large index as a part of the link step (which will also increase &g...

...gt;=64=0.0% issued r/w: total=98316/32756, short=0/0 lat (usec): 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.03% lat (usec): 250=0.40%, 500=2.43%, 750=3.51%, 1000=6.98% lat (msec): 2=38.68%, 4=38.79%, 10=8.85%, 20=0.30% Run status group 0 (all jobs): READ: io=3,073MB, aggrb=490MB/s, minb=64,257KB/s, maxb=66,641KB/s, mint=6042msec, maxt=6267msec WRITE: io=1,023MB, aggrb=163MB/s, minb=21,326KB/s, maxb=22,214KB/s, mint=6042msec, maxt=6267msec Disk stats (read/write): sdb: ios=784970/261501, merge=117/13, ticks=662700/221522, in_queue=884812, util=98.44% -------------- nex...

...gt;=64=0.0% issued r/w: total=98316/32756, short=0/0 lat (usec): 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.03% lat (usec): 250=0.40%, 500=2.43%, 750=3.51%, 1000=6.98% lat (msec): 2=38.68%, 4=38.79%, 10=8.85%, 20=0.30% Run status group 0 (all jobs): READ: io=3,073MB, aggrb=490MB/s, minb=64,257KB/s, maxb=66,641KB/s, mint=6042msec, maxt=6267msec WRITE: io=1,023MB, aggrb=163MB/s, minb=21,326KB/s, maxb=22,214KB/s, mint=6042msec, maxt=6267msec Disk stats (read/write): sdb: ios=784970/261501, merge=117/13, ticks=662700/221522, in_queue=884812, util=98.44% -------------- nex...