Login with username and password (forgot your password?)

On a related note, was watching the "What's New in Android Developer Tools" Google IO 2013 session, and noticed that it looks like there's a fair bit of energy going into Android support for IntelliJ.  FWIW, there was an intro to IntelliJ functionality starting at around 03:27.

Mmm, I like those examples, Jibz

On a related note, came across a handy alternative invocation:

wine explorer /desktop=root path-to-program.exe

via:

  http://www.winehq.org/pipermail/wine-devel/2010-July/084921.html

Neat!  Never seen this sort either.

Thanks for sharing 

[Perl]

Hmm...looking closely at the thread content, I'm not sure the issue is so clear:

Finally, something that must be mentioned: As far as we know, the MBR and partition table are (currently) ALWAYS written to the drive at the beginning of a restore, without asking. Previous versions of Redo did not write the MBR after a restore, until lately. (This was done because some users reported being unable to boot after a restore, and it appears to have corrected that issue.) So be careful using Redo under the assumption that an older version won't completely overwrite your MBR and partition table using data from the backup image, because it probably is. (If it doesn't, it is more likely a "bug" than a "feature"!)

I got the impression that the developer(s)? are not confident about the matter...

At any rate, IIUC, at least in some versions the relevant code lives in the subroutine named do_restore.  In one version, some of the relevant bits appear to be:

Formatted for Perl with the GeSHI Syntax Highlighter [copy or print]
  print "*** Writing MBR to $dest_drive\n";
  set_status("Writing master boot record to destination drive...");
  system("dd of=/dev/$dest_drive if=$src_mbr bs=32768 count=1; sync;");
  sleep(0.5);  
  print "*** Restoring partition table to $dest_drive\n";
  set_status("Writing extended partition table to destination drive...");
  system("sfdisk -fx /dev/$dest_drive < $src_sfdisk; sync");
  sleep(0.5);
  print "*** Reloading partition table from $dest_drive\n";
  set_status("Reloading new partition table from destination drive...");
  system("umount /mnt/$dest_drive?* 2>&1");
  system("sfdisk -R /dev/$dest_drive");
  sleep(1);

BTW, I have extracted one of the versions of Redo from a live CD image and experimentally made an Arch-based live cd that runs Redo.  I tried this because it seems a lot easier to customize and tinker with Arch-based live cds as compared with the Ubuntu-based ones.  If there is interest in this, I might write up some relevant instructions.

If I understand correctly, before version 1.0.3 (so 1.0.2 and earlier), the MBR was not restored.

May be the following thread has some relevant discussion:

  MBR restore to be optional

[add #t=03m22s (#t=XXmYYs for XX mins and YY seconds) to the end of the URL]

Found the following (old!) tip handy:

3. Cut the chase and link to the interesting part

Linking to a video where the real action starts at 3 minutes 22 seconds, wondered if you could make it start at 03:22? You are in luck. All you have to do is add #t=03m22s (#t=XXmYYs for XX mins and YY seconds) to the end of the URL.

via:

  http://www.makeuseof.com/tag/10-youtube-url-tricks-you-should-know-about/

FWIW, the collection is from some years back -- and some of the comments suggest that some of the tips no longer work.


As an example of how this might be useful...

The following set of links show a sequence of design diagrams for the Yamba Android sample example application covered in the Android Bootcamp video series:

• Part 1
• Part 2
• Part 3
• Part 4
• Part 5
• Part 6
• Part 7

Didn't figure out how to not have the video automatically start playing though...

I overheard a lord of JavaScript mention something about a clipboard and a link:

  http://www.pcworld.com/article/2036604/windows-8s-complexity-leaves-it-vulnerable-kaspersky-says.html



In any case, thanks for the post!

Thanks for the heads-up.

Don't know how much time is left, but the Defective by Design page also mentioned No Starch Press as a participant.

SmartGit/Hg 4.5 was released recently.

Some interesting parts include:

• Syntax coloring in some of the code viewing windows
• Staging hunks from within the Changes tool window (haven't tested)
• Additional polishing of Blame interface (tested a little)

via:

  What's New in SmartGit/Hg 4.5

Is there anyone here who runs Windows as (non-guest OS) and has their PC's (BIOS or other low-level) clock set to using UTC?

Reference:

  http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html

[* Restore now overwrites MBR and partition table upon completion]

Tried 1.0.3 and 1.0.4 today.

1.0.3 worked pretty well, however...

1.0.4. would not restore a backup made with 1.0.3.  1.0.4 also failed to backup the same set up.  Of course, these things may be particular to the local setup.

It appears that along with the backups being made, it might be prudent to backup the iso image of Redo Backup used to create the backup (or note the version used).

Also from 1.0.3:

Restore now overwrites MBR and partition table upon completion

and this appears to be something one cannot opt out of.

Despite these gotchas, 1.0.3 appears to be a viable alternative here to using OneKey Recovery Factor Default Recovery discs.  Redo Backup probably took less than 30 minutes to perform a recovery while the OneKey discs took over an hour.  Also, with Redo Backup it is not necessary to swap among 4 optical discs during the restore.


Changelogs:

Version 1.0.3 (2012-05-10)

* Restore now overwrites MBR and partition table upon completion

Version 1.0.4 (2012-11-20)

* Base upgrade to Ubuntu 12.04 LTS (Precise)
* Percent complete now based on part sizes rather than total number of parts
* Windows now have titlebars to ease minimizing, maximizing and closing
* Time is now synced to localtime (hardware clock) after boot
* Widget theme changed to Bluebird for Gtk3 compatibility
* Now has a helpful beep to indicate when long processes are finished
* Added alsamixergui to enable mixer button on volume control
* Drive reset utility can now operate on multiple drives simultaneously
* Removed synaptic and boot-repair packages to reduce image size

I found the smily at the bottom right corner of the image to be illuminating

This still is a mostly unanswered question though; for sake of discussion, if the drive did have some crazy important data on it, would it just have to be destroyed in this situation? Is that really a real-world "solution"? What would a company's IT department do if they had amassed a group of failed SSDs with company data still on them?

I've wondered over the years about "services" that offer to destroy such things...why would one trust them, and even if one did, would they not be a major target?

On a peripheral note, found the following info on the .vdi and .vmdk formats:

  .vdi - All About VDIs
  .vmdk - Virtual Disk Format 5.0

FWIW, I found some explanation of tweaking at:

  https://code.google.com/p/xdelta/wiki/TuningMemoryBudget

Source buffer size

The encoder uses a buffer for the source input (of size set by the command-line flag -B). To ensure the source input is read sequentially, with no backward seeks, the encoder maintains the source horizon at half the source buffer size ahead of the input position. A source copy will not be found if it lies more than half the source buffer size away from its absolute position in the input stream.

For large files, -B may need to be raised. The default is 64MB. This means data should not shift more than 32MB, that is, not more than 32MB should be added or removed from the source.

The minimum value of -B is 16KB.

The source file is not mmaped, it is read into the source buffer (Xdelta-1.x used mmap()).

Note: all flags are set in bytes, so for example to set a 512MB source buffer you must pass -B536870912.

Some additional bits on xdelta3 with command line tweaks:

  -B268435456 results in a patch a little under 139,000,000 bytes
  -B536870912 results in a patch a little over 103,000,000 bytes
  -B536870913 results in a patch a little over 56,000 bytes
 
So it looks like in this case, comparable sizes (to xdelta 1.x) are obtainable by tweaking the -B option.

Any recommendations for patching guest OS images that may not differ by much?

I've tried xdelta, xdelta3, bsdiff, and beat so far and discovered that:

  1. xdelta (1.x series) created a very small patch (a bit over 70,000 bytes) when the difference was between a .vdi file and a .vmdk file (vdi being somewhat over 810,000,000 bytes and vmdk being somewhat less than 745,000,000 bytes) -- here the vmdk file was created via conversion from the vdi file.

  2. xdelta3 (without tweaking of parameters) for the same scenario created an enormous file (a bit under 280,000,000 bytes) by comparison

  3. bsdiff exited with a message about not being able to allocate memory...

  4. beat created a large file (I think it was over 500,000,000 bytes) in linear mode and killed my X session in delta mode...(actually, it may have been systemd that killed my X session)

(AFAICT, xdelta3 does not process patches generated with xdelta 1.x...)

Finally got CyanogenMod running

Here's an updated list of what I've been using these days:

Aldiko	a reader - finally it can remember the zoom settings while navigating
aLogcat	logcat viewer - only useful up through Android 4.1?
Barcode Scanner	QR and other barcode reader
Camera
EBookDroid	reader with support for PDF (and other formats), auto-crop, per-book settings, and lots more
ES File Explorer	multi-feature file explorer
F-Droid	discovering potential apps with source available
File Expert	nice for quick file-sharing
Firefox	has support for some add-ons and OpenSearch
Gallery
Hacker's Keyboard	hurray, arrow keys and friends!
Kitchen Timer
MX Player	video player
OI ShoppingList	for managing various lists (not just shopping)
Opera Mobile	helps for downloading
Quickdroid	a bit like QuickSilver and/or FARR
Settings
Terminal Emulator
TubeMate

EBookDroid "almost" has this nice feature of being able to specify a page offset so that page numbers displayed by the app can be made to match better what the document displays.  Unfortunately, negative page offsets don't seem to work yet.

The attached patch appears to be working here so far.

Thanks Stephen66515

May be someone can upload a patch.

Testing out Wine here and encountered a "visual" problem.

When I have multiple displays enabled, starting up applications via Wine can result in black edges/borders/bars (along the bottom and/or right side of an application's window (at least on the larger display):

[attachthumb=1]

Actually, where the black areas appear seems to match what would be the edges of the smaller display if its top-left corner were aligned with the top-left corner of the larger display.

Some work-arounds seem to be:

• Disabling displays so that only one is active
• Enable "Emulate a virtual desktop" via winecfg
• Launch an application in a virtual desktop (e.g. wine explorer /desktop=atitle,1920x1080 path-to-program.exe)

(The last two are mentioned in the WineHQ FAQ: "How do I get Wine to launch an application in a virtual desktop?")

Anyone encountered this and come up with a better fix?

I haven't used rsync in a while -- my memory of it was that it was great for synchronizing things, but that remembering the command line options was not something I succeeded at


On a related note, I found that the upload.c example for the mongoose web server provides upload-by-form-via-http.  I made a minor change (save location /tmp -> .) and compiled it using mingw.  Also includes files necessary for compilation -- see included README.txt.

See attachment.

md5:c24c2e8b3a8f540b65ca43726a87e465

The following are some of the simpler file transfer options I've come across.

"Simpler" here is deliberately vague, but the situations under which I've thought to look for these has typically when I want to transfer a file between two machines without much set-up hassle.

• netcat, sbd, ncat, and friends -- if you don't mind the command line
• HTTP File Server (HFS) -- easy to start, uploading and downloading, even works under WINE (HTTP)
• Droopy -- uploading only(?) and needs Python (HTTP)
• Python 2: python -m SimpleHTTPServer / Python 3: python -m http.server -- downloading only and needs Python (HTTP)
• mongoose -- cross-platform, no config necessary for simple downloading (HTTP)
• osws -- one-shot file download and *nix-only(?) (HTTP)

Anyone have any favorites?

May be tagging the most recent commit before going through an interactive rebase is cheap way to make reverting easy (and upon success, deleting the tag)...

As a side note, I've disabled Preferences -> Commands -> Clean Up -> Periodically invoke Git's garbage collection when idle.

May be that makes it a bit easier to recover from my own errors...