And so.. is Chromium's code similar to Chrome? How did they get the code? Or is Chromium a new browser, with all new code, open source, written from the ground up
@Amithkk, I meant, did you think me [this matt] was the matt you linked?
I used Google Chrome in Windows, and am now using Chromium in Ubuntu. Is there any difference to the two programs? What are the advantages and disadvantages to each program? Which one seems better?
there may be additional differences, but the biggest is that Chrome is not FLOSS, Chromium is.
Chromium also lacks the built-in flash plug-in, though i understand that it will pickup the normal plugin without issues.
lol. well, they make it so the chargers have to have 3v on a certain wire. so generic mp3 usb chargers don't work. but they make clones on ebay for $2 or so.
if you have a conflict and you're a noob,you're going to be like "uhh... so i just jacked my source. what now? and why are all these >>241 blah blah and << 51 wooots in my file?
I hope it's okay to ask a direct question here, rather than post on the site? I feel really stupid: I'm following these official instructions to decrypt the /home/torben folder of my old drive so that I can copy it onto my new drive. The command says "success" but I can't find the decrypted files in the /tmp/... location given in the command's output. Where are the files?
I'm following these instructions to decrypt my /home/torben folder of my old drive so that I can copy it onto my new drive. It seems to succeed:
INFO: Success! Private data mounted read-only at [/tmp/ecryptfs.xtltX0TT/private].
but I can't find the decrypted files in the /tmp/... location ...
Here is how you recover data from an encrypted home: (sdx should be your SATA drive)
sudo mkdir /recovery
sudo mount /dev/sdx /recovery
sudo mount -o bind /dev /recovery/dev
sudo mount -o bind /dev/shm /recovery/dev/shm
sudo mount -o bind /dev/pts /recovery/dev/pts
sudo mount -o bind /sys /recov...
mount: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
I don't see that it has any number besides "sdb"
(yes, it is "b")
ah, but disk utility says device " sdb1" so I'll try that