For some time I had wanted to have a live Linux distro in my keychain. This, in turn, preferably required encryption of, at least, the home partition.
Obvious candidates need not to be named. I thus searched for a simple tutorial and, while some exhaustive ones exist (mostly for Arch, Gentoo, and Debian), all of them required a quite custom and long (i.e. error-prone in my hands) procedure.
Me being a natural1 person, I tossed these aside and went for the obvious, dummy way. Since due to space limitations I didn't want to have a separate /home partition, Ubuntu was out of the picture (because it only allows, during install, to encrypt /home). Instead, I turned to Debian netinst, which I had recently used in a VirtualBox image. And so I did:
- Create, in VirtualBox, a VM without hard drive, enough memory for Debian netinst (I guess around 512MB should be more than enough), and USB support.
- Configure this VM with the Debian netinst image as mounted CD, and boot from it.
- Plug-in the USB key, pass ownership of it to the VM just being booted.
- Proceed with standard Debian installation. When partitioning arrived, I could select my USB key as if it were any regular hard drive. Select encryption of everything but a small /boot partition. This way almost all usable space in the pendrive goes to the root partition which also comprises /home. You could separate them if you prefer. I also threw in a small swap partition, also encrypted. I don't very much care about flash wear, for this system is to be used sporadically on unknown machines.
- Complete installation, shut down the VM, unmount the USB key, boot from it in some machine to verify installation.
- Delight on being asked your password in the early stages of console boot and everything working out of the box.
- Optional further steps:
- Insert the key in another running Linux (e.g. my desktop Ubuntu). Encrypted partitions are detected, you'll be asked for your password so you can unlock and mount them. I took advantage of this to unlock (but not mount) the USB root partition in order to remove the ext3 journal and downgrade to ext2 (and don't forget to change it in /etc/fstab), which is said to be preferable in flash media (did I just say that I don't care about flash wear? Well, if it can be avoided...)
- Change from stable to unstable in /etc/apt/sources.list if you prefer (as I do) a more bleeding-edge system. Boot from USB and upgrade system.
- Install restricted drivers, every other wifi firmware (look for firmware-* packages) in order to be ready when you use this pendrive in some unknown machine.
- Install some GUI if you like (nowadays I go with xfce4 after the KDE and Gnome debacles).
- Customize to your liking, whatever.
- Update regularly.
All in all, this was easy-peasy as any other regular installation. I was mildly2 surprised that it worked in the first try, to be honest. Even more that nobody3 else (that I could found) had documented this easier procedure to have a fully (but for /boot, of course) bootable live Debian USB.
1In the sense that mother Nature always finds the path of least resistance, i.e. effort. 2With nowadays generalized use of UUIDs and computers being regularly able to boot from USB, not so much really. 3I just learned about package live-magic which frankly makes this post moot (although it is broken in Ubuntu). As it often happens in my current world of ignorance. Sheesh.
I was going to review this anime in anidb.net but I don't want to comply with their guidelines. I just want to have out this frustration that it put into me.
I think that what most saddens me is the potential that this had and that was thrown overboard. I saw the first 9 episodes in a row. I was amazed and gloating in anticipation.
Hold your horses.
It's well and dandy that they chose to narrate this through Albert, and not the Count. That left more opportunities to enrich the Count's mystery. However, there is a gradually increasing feeling that something with the Count depiction isn't right. And indeed isn't right. We are supposed to like him, at least if we must understand the pains Albert takes to "redeem" or "save" him. We get this very clearly in the book: the Count is capable of great compassion, generosity, and he's appalled at the collateral damage of some of his vengeful acts. The struggle can be felt, and the final fate of the Count is, amongst several possible, perfectly fitting.
Here the plot takes us into a totally unnecesary relight of the Mondego character once it was almost disposed with. Mondego goes in minutes from crazy maniac to repentant father. In the end, he doesn't get neither the punishment he deserves (not by law, but by all the people that he deceived) nor a decent final stand-off.
But the Count... the Count is wasted nonsensically and acts even more incongruously. One could think he's struggling between compassion and revenge, between hate and love, ... but if this is the intention, this isn't what's depicted. Minutes before his end, he could have been master of his destiny, but ultimately he is overwhelmed by the Gankutsuou first, Albert (!!!) embrace (if not kiss) next, his pitiful attempts at killing when again human then, and finally death.
Talk about anticlimatic.
We are then "subtly" bombarded with the apparent similarity between the young trio and the previous generation one. Nice and dandy if it weren't for the detail that in the former, one man is secretly in love with the other to the point of giving his life, while in the latter the conniving bitch by any measure kills his "friend" and steals his woman. Yeah, exactly the same, fond, memories. That's enough reason to let die the condemned and let live (if even he's to coward to do so) the scum-friend. (And, since I mentioned it, since when failing to show at a duel is simply forgotten?)
Yes, I think that duel is the point where things go decidedly south. In the book this is the point where Albert has to forcibly mature, and the Count reluctantly knows it has to be done, even if in the end is for the best. Here he goes in as the murderer zombie he is, kills the wrong rival, forgives the missing one, and we are left wondering why anyone loves him).
I could go on on other characters' rationality and plot holes the size of the titanic (how does Albert board the fscking bombing cruiser? hello?), but these are secondary to the depiction of the Count. We have to accept at face value that he's worth rooting for (as in the book), but he's not (in the anime). Which in itself is a cognitive dissonance, even more so for anyone who has read the original. In the end, the last few chapters feel like random happenings, but the worst is that nothing forced them taking that route.
/Rant.
How to get high quality videos at reasonable sizes. Needed this in the past for conferences and again now for a friend submission to notodofilmfest.
$ ffmpeg -i <inputfile> -threads 0 -pass 1 -vcodec libx264 -vpre medium_firstpass -b <bitrate>k <outputfile>.flv
$ ffmpeg -i <inputfile> -threads 0 -pass 2 -vcodec libx264 -vpre medium -b <bitrate>k <outputfile>.flv
-threads 0 detects available CPUs. The important thing here is selecting the appropriate video codec.
Bitrate, I'm afraid, can only be determined somewhat empirically, if you want a target file size. I ended doing binary search.
I guess that if you're desperate for quality you can use -vpre placebo[_firstpass].
For single-pass, it's said to be better to use -crf <something in 15-25 range>, less is higher quality/larger size, instead of -b. Also the -vpre hq profile might be interesting?
For completeness, including the audio codec, I had:
$ ffmpeg -i <inputfile> -threads 0 -acodec libmp3lame -ab 160k -ar 44100 -pass 1 -vcodec libx264 -vpre medium_firstpass -b <bitrate>k <outputfile>.flv
Since no video editing program that I know understands animated gifs (kdenlive, openshot, pitivi), using this recipe one can use such gifs in these programs:
mencoder -ovc lavc -lavcopts vcodec=ffv1 -o outfile.avi infile.gif
The ljpeg codec is also lossless, but files are bigger.
I was tasked with recovering some photos from a dying drive. I finally resorted to magicrescue, which is nice and to the point. And command line and packaged in Ubuntu, so very dandy. Before finding it, however, I backed up the whole partition with dd. I'm used to mount .iso images, so I guessed that a dd dump can be likewise easily mounted. Indeed, it would be as simple as: sudo mount -o loop <dumpfile> <mount point>
This triggered an interest into creating any arbitrary filesystem within a file (saving the need for toying with real partitions or virtual machines). It turned to be damn easy: - Create the file (e.g. $ dd if=/dev/zero of=disk count=1024 ibs=1024
This will dump 1024 blocks of 1024 bytes of zeros into a file named 'disk' - Associate the file with a device (e.g. $ losetup -f disk).
This was actually the only piece of info I was missing. - Find out the loop device ($ losetup -a)
- Create the filesystem (e.g. $ mkfs.ext4 /dev/loop0)
- Mount your file! (e.g. $ mkdir mnt ; mount disk mnt)
That's it. Or, you could insert a partition table (between steps 3 and 4) with fdisk, and create several partitions inside. At that point you can use nicer graphical tools like gparted. Alex out.
So I had this glorious idea of using the CD mp3 instead of the youtube video sound, to have better audio quality. Bad idea.
Audio was slightly faster than video. At first I thought it would be some easy 25-->24 or 24-->23.976 framerate issue, easily fixed with ffmpeg. Bzzt, nope.
Empirical testing with OpenShot (Kdenlive 0.7.6 has some strange bug where clips don't snap to tracks that makes it unusable) showed a relative higher speed of 1.0025 for the audio. That implied that I needed to move from 23.976fps (the original video frame rate) to 24.03594fps. Obviously ffmpeg doesn't support this (better said, the mp4 spec doesn't allow it).
I could apply the 1.0025x in OpenShot quite easily. But, double size video, half the quality, due to this silly thing of fixed output video profiles. Scale-up, whatever, stuff; result: shitty fat video.
In the end, applying the inverse rule in yuvfps (i.e. lying about the source frame rate, which yuvfps swallows be it whatever it be) I got it. The sync is amazingly perfect, so much that I cannot understand where this 1.0025 comes from.
Conclusion: for my next ultrastar adaptation (Fantine's death), which I have already almost finished, I used the youtube audio. Too bad if it's crappy overcompressed, artifact ridden mp3. (It's actually not that bad :P) P.s: The final recipe was
ffmpeg -i orig.mp4.bak -f yuv4mpegpipe - | yuvfps -s 2403594:100000 -r 23976:1000 | ffmpeg -f yuv4mpegpipe -i - -y -r 23.976 -b 500k 24.mp4
Just discovered Performous via Ultrastar (thanks, Ster!). Isn't it great? I couldn't stop adapting some of my faves, more to come soon! Someone took the time to upload a complete package of txt+mp3 to freenet . If you have it installed you know what to do. #TITLE:Bring him home #ARTIST:Les miserables 10th anniversary Full TXT in the article body.
Today I tried to install GtkAda-2.14 in some Ubuntu Karmic machine. No luck. Until now, it sufficed to use the stock libgtk2.0-dev packages and simply compile GtkAda. However, the current gtk+ version is 2.18, and some fields in GtkEntry have changed, breaking GtkAda. So I had to unpack the gtk+-2.14 available at AdaCore in my local account folder, and export the proper folder with $ export CFLAGS=-I$HOME/local/gtk+-2.14/include/gtk-2.0 Note the last /gtk-2.0 part, that throwed me out for a minute. Now GtkAda compiles and installs. Amazingly, linking is done against the Ubuntu stock installation and it seems to work (and my program shows windows and stuff dude). I suppose this is a bomb waiting to blow up at the most interesting moment. Whatever.
|
|