I'm pretty sure I was the user who'd reviewed the most edits across SE for a while, I don't know if I still am (a couple of people have done more reviews than me on SO now)
I don't know Ruby but want to run an script where:
D:/Heather/Ruby/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require': cannot load such file -- iconv (LoadError)
it works somehow if I comment iconv code but it will be much better if I can recode this part:
return Iconv.ico...
I wouldn't even engage him at this point, unless you like wasting your time in a circle jerk.
If you search for him on google you'll find him in a variety of forums and other ask types of SE sites. The patterns been the same as far as I can tell, he asks Q's and no one A's them.
@slm As long as you don't have to drive or operate heavy machinery, I guess you'll be Ok. But in that case, wouldn't you start passing out in the afternoon? That's what happens to me.
@FaheemMitha just keep up with the espresso and sugary foods. Sure sugar will pick you up and crash you hard, you just have to keep consuming to postpone the crash :)
Hah, so @strugee says to do the lvm raid on Jessie, and @Gilles on Wheezy. I guess I should try Wheezy. Maybe we'll get lucky and the steps will be the same...
BTW! Guess what time it is! Time to replace another Seagate drive! Got a SMART failure warning this morning for my workstation...
@FaheemMitha terrible actually, but correctable to 20/20. That pic was taken further back than I sit. From where I normally sit the monitors cover a FOV somewhere between 90 and 100 degrees
@Networker (not sure if this ping will reach you). Please reject suggested edits which are minor and leave glaring errors. E.g., unix.stackexchange.com/review/suggested-edits/58797 has "to to", spelling errors, etc.
multiple video cards is doable (though I'd only go for this with SLI with same make/model of cards) but you need a motherboard space and enough cooling and power to run two cards
Scalable Link Interface (SLI) is a brand name for a multi-GPU technology developed by NVIDIA for linking two or more video cards together to produce a single output. SLI is an algorithm of parallel processing for computer graphics, meant to increase the processing power available for graphics.
The acronym SLI was first used by 3dfx for Scan-Line Interleave, which was introduced to the consumer market in 1998 and used in the Voodoo2 line of video cards. After buying out 3dfx, NVIDIA acquired the technology but did not use it. NVIDIA later reintroduced the SLI name in 2004 and intended for it to...
@FaheemMitha my first computer have 64kb ram and my first PC had 512 kb. This machine as 24 GB, and if the mobo supported bigger sticks it would have 48 GB, but sadly it does not :(
@FaheemMitha Well, I just killed the machine a day or so ago from OOM :-) But that was doing something stupid. Currently, though, I have a rather disturbingly high free amount:
@mikeserv Hah, that server doesn't OOM. That was my workstation I managed to OOM, by attempting to use perl Archive::Tar to tar up all those logical volumes...
Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: Multi-bit ECC Maximum Capacity: 32 GB Error Information Handle: Not Provided Number Of Devices: 4
@mikeserv I looked at it, still haven't managed to test it out... But @FaheemMitha was the one complaining about all the stuff done as root. If I were going to automate it, I'd write my own script anyway...
some people might open a record oriented file and read it line by line. I'll just memmap that file and cast the void* to a structure pointer and reference it directly!
@mikeserv memmap just makes a file accessible as if were memory, it can be very nice from a programming standpoint
@mikeserv Normally, to read a file, you allocate "anonymous" memory (with malloc, etc.) and then ask the kernel to copy the file contents to that memory. This has a downside, nothing realizes that block of memory is exactly the same as the file on disk, so if there is memory pressure it might get written to swap
wait maybe I get it. mmap asks the kernel to please provide this file in memory - maybe like tmpfs. malloc asks the kernel to please address this data from mark -> mark?
When you read from a page in that 100TB mmap'd range, the relevant part of the file will be read in. And---if you don't modify that page---when its no longer needed, it can be discarded (not written to swap) because the kernel can always just read it again.
The main thing from a programming standpoint is a lot of times its much easier to have the entire file available at once (or at least appear to be so), instead of only having small chunks of it available (as you would with a normal seek/read)
You can use mmap in C. Or even Perl.
mmap has some downsides. It's hard to resize a mapped file. It's also limited by address space, so 32-bit systems can't map that much.
well, it is also available with zsh and bash, but severely limited. all or none, really. You can split the source up if you like - but the only way to do that efficiently is in tmpfs, and then... well.. why mmap?
Limitations Although reading and writing of the file in ques‐ tion is efficiently handled, zsh's internal memory management may be arbitrarily baroque; however, mapfile is usually very much more efficient than anything involving a loop. Note in particular that the whole contents of the file will always reside physically in memory when accessed (possibly multi‐ ple times, due to standard parameter substitution operations). In particular, this means handling of sufficiently long files (greater than the machine's
Ok, so maybe not. possible multiple times looks pretty contraindicated, huh?
string = mmap "/path/to/file"
print string[1099511627776] # will print just the byte at 1TB
string[1099511627776]='c' # it's now a c, and that will be saved in the file
yep, and when your file is record oriented and corresponds to a C struct, it is a lot easier to read/write a record just using its index (e.g. record[5]) than seeking to the position of record 5/reading/writing.
@casey - beats me. don't use it - I would just qemu something. but I hate the how to fool a user questions. they're stupid - and I regard the idea as self-defeating anyway.
how can I seamlessly emulate a function with another function would be far better. don't fool users - educate them.
@FaheemMitha - you can probably print it to text. or copy+paste the contents to plain text.
I have a 72.9MB pdf file that I need to shrink into under 500KB.
The file was a jpeg image that I had scanned, and then converted to pdf.
Can someone please offer any suggestions?
well, gs is really a preprocessor - it could be used, but only to magically select a script that would ocr it. but you'd have to write the ghostscript that does the selection and... don't use gs.
looks like dude there provides the gs bits to do it, huh?
They don't have anything of mine that I care that they read. They do have some precompressed/encrypted archives containing information I wouldn't want them reading, but good luck to them trying.
but if you're sending an email to an unknown, what do you care if google reads it to?
@Braiam Hmm. Not that far fetched. And yes, all apt questions could reasonably have the debian tag, though not that important in this case, because the apt tag kind of defines is already
I might not use the debian tag here because the apt tag is so specific to debian