Reputation
36,742
Next tag badge:
367/400 score
104/80 answers
Badges
5 72 121
Newest
 Enlightened
Impact
~2.3m people reached

May
15
comment gnu parallel: quoted arguments and spaces in file names. How to solve?
@SomebodystillusesyouMS-DOS Ok. "Hardware limitations" count as a good reason. You may also need to find ffmpeg's equivalent of LAME's -B.
May
15
answered gnu parallel: quoted arguments and spaces in file names. How to solve?
May
15
revised Why can't unrar expand this expression?
fix trivial things
May
14
answered Get Dropbox version
May
13
comment Why can't unrar expand this expression?
Ah, nice to know different unrar versions behave differently. (You may also have the very ancient free version of unrar, that could be quite different. After all, someone may have patched it to behave sanely, unlike the non-free version...)
May
13
comment Why can't unrar expand this expression?
file*rar doesn't work. unrar takes the first file argument as the archive, then the rest as (I'd guess) which files to extract from the archive—not as additional archives to extract.
May
13
revised Why can't unrar expand this expression?
added 284 characters in body
May
13
answered Why can't unrar expand this expression?
May
13
revised Why can't unrar expand this expression?
edited tags
May
13
comment Why can't unrar expand this expression?
The asterisk is actually preventing shell expansion, passing the unexpanded string to unrar. So your question is actually why unrar doesn't handle that pattern.
May
13
comment Recover LUKS partition after overwriting first few bytes of LUKS container? System still up!
@Ned64 You really shouldn't be trying e2fsck until after your dd is done. But probably best to ask a new question with the e2fsck errors, to see if anyone knows how to get the FS repaired. I take it then that tar wasn't able to get anything off? :-(
May
13
answered Launch Win 7 from Grub Terminal?
May
13
awarded  networking
May
12
comment Recover LUKS partition after overwriting first few bytes of LUKS container? System still up!
@Ned64 considering those errors, tar probably won't get everything. But at each step you want to get as much as you can. So first get what you can with tar, then fsck one of your copies, and get what you can from that. Compare, see if there is anything critical missing. If anything critical is missing, you can figure out your next step. Some types of files (e.g., JPEG images) can be recovered using media scan undelete tools.
May
12
comment Recover LUKS partition after overwriting first few bytes of LUKS container? System still up!
@Ned64 BTW: You want the whole line. Maybe the output of dmsetup info -c as well. Those will make your life easier should you have to use them (the other things can be brute forced fairly trivially, but not having to do so is much easier. The encryption key, of course, can not be brute forced, at least not with the computing power available on Earth.)
May
12
comment Recover LUKS partition after overwriting first few bytes of LUKS container? System still up!
@Ned64 if it's still mounted, you might just be able to use tar. Other than that, I suspect fsck will be able to get it mountable. But you want to do that on a copy (maybe even a copy of a copy, or at least set up a snapshot—fsck may also destroy things). You should be able to use one of the backup superblocks. You may have lost more than the first however many bytes you overwrote; e.g., by destroying filesystem metadata about other data—but that metadata is spread out, so you probably only hit a little of it.
May
12
revised Recover LUKS partition after overwriting first few bytes of LUKS container? System still up!
added 90 characters in body
May
12
answered Recover LUKS partition after overwriting first few bytes of LUKS container? System still up!
May
12
awarded  Nice Answer
May
11
comment CVLC: alsa name?
@elbarna and what audio output are you using with mplayer? -ao alsa:device=front or something else?