Link:
https://dannyman.toldme.com/2009/09/28/howto-ubuntu-xvidcap-audio-support/
XVidCap is a very nice screen-capture program for Linux. I have been dabbling in it to capture video of my desktop.
Unfortunately, the binary offered by Ubuntu’s software distribution has audio disabled. I found a bug about that somewhere and added my two cents, then went and installed it manually. Then I had to reinstall it manually because the Ubuntu version had been bumped and the “newer” version replaced my audio-supporting version.
Step 1: Remove Existing xvidcap
sudo aptitude remove xvidcap
Step 2: Install XVidCap from SourceForge
http://sourceforge.net/projects/xvidcap/ — click “download now” and the rest is all point-and-click.
Step 3: Lock XVidCap Version
Ubuntu will be quietly bide its time until it can “upgrade” xvidcap to a version that doesn’t support Audio. Fortunately, you can tell it not to do that!
Open: System > Administration > Synaptic Package Manager
Search for “xvidcap”
Select the package, go to the Package menu and select “Lock Version”
(From what I can tell, sudo aptitude hold won’t actually prevent xvidcap from being “upgraded.”)
14 Comments
Link:
https://dannyman.toldme.com/2008/11/19/e2fsck-frog-off/
I halt my computer at night, and boot it in the morning. This reduces my carbon impact. Alas, Ubuntu for whatever brain-dead reason doesn’t trust its filesystem. As if we lived in the 1970s it insists on checking the filesystem consistency every thirtieth boot. I sip my morning coffee, check my workstation, and have to hit ESC . . .
So, I googled a bit, and found a helpful forum thread. I thought I’d offer my own tiny variation:
0-09:57 dannhowa@T60p ~$ sudo tune2fs -c 0 `mount | awk '$3 == "/" {print $1}'`
tune2fs 1.40.8 (13-Mar-2008)
Setting maximal mount count to -1
Update: wamukota made an excellent suggestion, that one can instead set an interval with the -i flag. For example, one could set their computer to check every three months:
0-19:06 djh@noneedto ~$ sudo tune2fs -i 3m `mount | awk '$3 == "/" {print $1}'`
tune2fs 1.41.4 (27-Jan-2009)
Setting interval between checks to 7776000 seconds
Okay, that is a scary-looking command-line. Let me break it down. (more…)
1 Comment
Link:
https://dannyman.toldme.com/2008/10/17/new-york-times-reviews-g1/
I should receive my first new mobile phone since 2004 on October 22. I don’t really need a new phone: the old Sidekick 2 is built like a tank and shows no sign of giving up the ghost any time soon. But I went and pre-ordered a G1 for three reasons:
1) I have a friend on Google’s Android team.
2) To annoy the iPhone weenies.
3) My employer made its targets, so I spend a little of my bonus check.
I haven’t actually used one yet, so I was pleased to catch a review in the New York Times. Some of what I enjoyed:
One crucial improvement over the iPhone: a Menu button. It summons a panel of big buttons for functions related to what you’re doing. It’s the equivalent of right-clicking a computer mouse.
“Right mouse button!” HA!
Where Android really falls down is in the iPod department. There’s no companion program like iTunes to sync your photos, music and videos to the phone; you’re expected to drag these items to the phone manually after connecting via USB cable to your Mac or PC. More time-consuming fussiness.
This is a win for me: I hate iTunes. Dragging and dropping files is just the ticket, in my book. I’ve been dealing with that interface metaphor for fifteen years and its more comfortable than dealing with the quirks of some new software package. (Back when I had lots of issues with iTunes doing stuff like copying my library over twice.) That, and I run Linux desktops.
Some of the goodies in Android will reward the iPhone holdouts: voice dialing, picture messaging, built-in audio recording and the ability to turn any song into a ring tone are all included — no charge.
Voice dialing? That should be nice. And audio recording might be fun, too. Too bad the camera is supposedly crap, and no video. But that’s why I have my Canon.
The big news is the physical keyboard. It’s not pure joy, though. The keys don’t click down much. Worse, you have to keep turning the phone 90 degrees from its customary vertical orientation every time you need to enter text. That gets old fast. And it’s bizarre that, even though the phone contains a tilt sensor like the iPhone’s, it’s not hooked up to the screen. Turning the phone 90 degrees to get a wider look at a photo or Web page doesn’t rotate the image. You have to do that manually, using a menu or by popping open the keyboard, which makes no sense.
The keyboard is my biggest concern. I think the Sidekick 2 keyboard is nearly ideal and it is a big reason I shun the iPhone. Software bugs (sounds like the e-mail client is a mess) can be addressed by future patches or possibly third-party applications. I like to think rotation can be sorted out down the road.
Overall, it sounds like the G1 will be the dowdier, more adaptable PC to the flashy smugness that is the iPhone. And, I have to admit, while I love the turtleneck sweater I bought in France, I am a PC guy. (I think that’s the point of the new Microsoft ads: Bill Gates is as big a schmuck as Jerry Seinfeld or any one else.)
Lastly, this is just sad:
Finally, there’s no headphone jack. (Hello?!) If you want to use headphones, you have to buy and carry a special adapter that connects to the USB jack.
Feedback Welcome
Link:
https://dannyman.toldme.com/2008/08/24/ubuntu-nvidia-video-violet-hue/
This week I upgraded the guts in my desktop. For the video card I jumped up to an ASUS EN9600GT silent graphics card. It is pretty “bleeding edge” as far as Linux goes, and it is a double-wide card with a massive heatsink where others would have a fan. I like to reduce the white noise.
Unfortunately, it is too new for the currently-supported Ubuntu drivers. I used Ubuntu’s NvidiaManual docs to manually upgrade to the 173.14.12 drivers from NVidia’s site, and then things were happier. Except video playback. Files and DVDs seem to work okay, but the colors are off, notably, people get rendered with blue or purple flesh. (more…)
2 Comments
Link:
https://dannyman.toldme.com/2008/07/04/shell-sh-bash-random-splay/
The other day I was working on a shell script to be run on several hundred machines at the same time. Since the script was going to download a file from a central server, and I did not want to overwhelm the central server with hundreds of simultaneous requests, I decided that I wanted to add a random wait time. But how do you conjure a random number within a specific range in a shell script?
Updated: Due to much feedback, I now know of three ways to do this . . .
1) On BSD systems, you can use jot(1):
sleep `jot -r 1 1 900`
2) If you are scripting with bash, you can use $RANDOM:
sleep `echo $RANDOM%900 | bc`
3) For portability, you can resort to my first solution:
# Sleep up to fifteen minutes
sleep `echo $$%900 | bc`
$$ is the process ID (PID), or “random seed” which on most systems is a value between 1 and 65,535. Fifteen minutes is 900 seconds. % is modulo, which is like division but it gives you the remainder. Thus, $$ % 900 will give you a result between 0 and 899. With bash, $RANDOM provides the same utility, except it is a different value whenever you reference it.
Updated yet again . . . says a friend:
nah it’s using `echo .. | bc` that bugs me, 2 fork+execs, let your shell do the math, it knows how
so $(( $$ % 900 )) should work in bsd sh
For efficiency, you could rewrite the latter two solutions:
2.1) sleep $(( $RANDOM % 900 ))
3.1) sleep $(( $$ % 900 ))
The revised solution will work in sh-derived shells: sh, bash, ksh. My original “portable” solution will also work if you’re scripting in csh or tcsh.
2 Comments
Link:
https://dannyman.toldme.com/2008/05/14/canon-i250-hardy-heron/
The Ubuntu upgrade broke printing. Among other things, it removed my canoni250.ppd file. I struggled with it to no avail. Then I went back and pasted the commands in from last time and now it all works.
Yay.
2 Comments
Link:
https://dannyman.toldme.com/2008/05/06/what-time-utc/
I wanted to know what time it was in UTC, but I forgot my local offset. (It changes twice a year!) I figured I could look in the date man page, but I came up with an “easier” solution. Simply fudge the time zone and then ask.
0-20:57 djh@noneedto ~$ env TZ=UTC date
Tue May 6 03:57:07 UTC 2008
The env bit is not needed in bash, but it makes tcsh happy.
Update: Mark points out an easier solution:
date -u
Knowing you can set TZ= is still useful in case you ever need to contemplate an alternate timezone.
(Thanks, Saul and Dave for improving my knowledge.)
3 Comments
Link:
https://dannyman.toldme.com/2008/04/25/wordpress-251/
There’s a notice on the WordPress dev blog that WordPress 2.5.1 is out. Alas, they neglected to link to the upgrade documentation. My favorite? Upgrading via Subversion:
0-11:17 djh@ratchet ~> cd public_html/toldme
0-11:17 djh@ratchet ~/public_html/toldme> svn sw http://svn.automattic.com/wordpress/tags/2.5.1/
[ . . . ]
Updated to revision 7839.
When I logged in to post this little note, it blocked me and ran the upgrade procedure, then I had to log in again, and here I am!
There’s a further note about the secret key setting:
Since 2.5 your wp-config.php file allows a new constant called SECRET_KEY which basically is meant to introduce a little permanent randomness into the cryptographic functions used for cookies in WordPress. You can visit this link we set up to get a unique secret key for your config file. (It’s unique and random on every page load.) Having this line in your config file helps secure your blog.
It leaves me to wonder: if the secret key can be randomly generated by a machine, why not go ahead and do that and then stash it in the database? There may be a good reason for that . . .
In unrelated news, I upgraded to the newer Ubuntu release at home yesterday. The only trick I have noticed so far is that it runs with Firefox 3.0, which is beta, and I lost use of my foxmarks plugin, for now. So, I’m waiting until that is supported before I upgrade my workstation.
Feedback Welcome
Link:
https://dannyman.toldme.com/2008/03/13/canon-i250-ubuntu-feisty/
I had a rough go of it until I found BlackNight’s post, and now my Canon i250 printer works with Ubuntu like a charm. I thought I would recap here for those who, like me, at first Googled in vain. If you paste these command into Ubuntu 7.10 (Feisty) things ought to work:
First, enter your sudo password:
sudo echo
Now, this paste just might set up everything you need:
sudo apt-get install libpng3 libtiff4 cupsys alien
cd /tmp
wget http://download.canon.com.au/bj/i250linux/bjfilteri250-2.3-0.i386.rpm
wget http://download.canon.com.au/bj/i250linux/bjfiltercups-2.3-0.i386.rpm
sudo alien --scripts bjfilteri250-2.3-0.i386.rpm
sudo alien --scripts bjfiltercups-2.3-0.i386.rpm
sudo dpkg -i bjfiltercups_2.3-1_i386.deb bjfilteri250_2.3-1_i386.deb
sudo ln -s /usr/lib/libtiff.so.4 /usr/lib/libtiff.so.3
sudo ln -s /usr/lib/libpng.so.3 /usr/lib/libpng.so.2
sudo /etc/init.d/cupsys restart
Then, go set up your printer in the GUI, and specify this PPD file:
/usr/share/cups/model/canoni250.ppd
(Or, in retrospect, since it has a GNU license on it, you could just download the PPD directly off my web site.)
If things turn out less-than-straightforward, definitely review BlackNight’s page for details, and if this does work out for you drop him a thank you note in the comments!
5 Comments
Link:
https://dannyman.toldme.com/2008/01/26/deader-than-amiga/
I have been playing with Google Trends, which will be happy to generate a pretty graph of keyword frequency over time. A rough gauge to the relative popularity of various things. This evening, I was riffing off a post from the Royal Pingdom, regarding the relative popularity of Ubuntu and Vista, among other things.
I got started graphing various Linux distributions against each other, XP versus Vista, and trying to figure out the best keyword for OS X. Then, I wondered about FreeBSD. Against Ubuntu, it was a flatline. So, I asked myself: what is the threshold for a dead or dying Operating System?
Amiga vs FreeBSD:
Ouch! Can we get deader?
Amiga vs FreeBSD vs BeOS:
To be fair, the cult of Amiga is still strong . . . BeOS is well and truly dead. But how do the BSDs fare?
Amiga vs FreeBSD vs BeOS vs NetBSD vs OpenBSD:
NetBSD has been sleeping with the BeOS fishes for a while, and OpenBSD is on its way. And that’s a league below Amiga!
In Red Hat land, only Fedora beats “the Amiga Line”. For Unix in general, nothing stops the Ubuntu juggernaut. But there’s a long way to go to catch up with Uncle Bill.
(Yes, it is a rainy night and the girlfriend is out of town.)
Postscript: Ubuntu versus Obama
3 Comments
Link:
https://dannyman.toldme.com/2008/01/11/etc-crontab-or-die/
This is just a note which I contributed to a thread on sage-members, to get something off my chest, as to where people should maintain their crontab entries. I sincerely doubt that reading what I have to say will bring you any great illumination.
I’d say, any reasonable SysAdmin should default to /etc/crontab because every other reasonable SysAdmin already knows where it is. If anything is used in addition to /etc/crontab, leave a note in /etc/crontab advising the new guy who just got paged at 3:45am where else to look for crons.
For production systems, I strongly object to the use of per-user crontabs. I’m glad to hear I’m not alone. One thing I have to do in a new environment tends to be to write a script that will sniff out all the cron entries.
And then there was the shop that used /etc/crontab, user crons, and fcron to keep crons from running over each other. This frustrated me enough that I did a poor job of explaining that job concurrency could easily be ensured by executing a command through (something like) the lockf utility, instead of adding a new layer of system complexity.
Yes, I am a cranky old SysAdmin.
2 Comments
Link:
https://dannyman.toldme.com/2006/11/29/crontab-l-u-star/
For production systems, I think it is best to use a single, centralized /etc/crontab, which simplifies the job of tracking batch processes. On a production system, batch scripts should be sufficiently robust such that if they are resource or lock-intensive, they make sure everything is okay before they get to work. Stuff like user crons and fcrontab can live in your development and corporate servers.
Of course, sometimes you inherit production systems with people who don’t think like you do. You’ll need to review what random user crons are running on each system. With any luck you’ll have a sane OS that keeps the user crontabs in a well-documented location. (FreeBSD? /var/cron/tabs . . . SuSE . . . still not sure . . .) Of course, luck is a fickle mistress, and sometimes you have to do it the evil way:
> cat /etc/passwd | awk -F : '{print "echo crontabs for user "$1"\ncrontab -l -u "$1"\n"}' > /tmp/crontabs.sh
> head /tmp/crontabs.sh
echo crontabs for user root
crontab -l -u root
echo crontabs for user bin
crontab -l -u bin
echo crontabs for user daemon
crontab -l -u daemon
echo crontabs for user lp
> sudo sh /tmp/crontabs.sh | mail -s "`hostname` crontabs" $USER
If you are borrowing my “recipe” you will likely want to put your e-mail address where it says $USER . . . and, you may have to do the same for fcron as well. Bah!
cat /etc/passwd | awk -F : '{print "echo fcrontabs for user "$1"\n/usr/local/bin/fcrontab -l -u "$1"\n"}' > /tmp/fcrontabs.sh
sudo sh /tmp/fcrontabs.sh | mail -s "`hostname` fcrontabs" $USER
Feedback Welcome
Link:
https://dannyman.toldme.com/2006/10/24/howto-swapon-file/
Scenario: a Linux system with two drives. The system was built with resiliency as a priority, but availability is not critical. So, the filesystems were mounted atop md raid1 for resiliency, and the swap was striped across an md raid0 for performance.
One disk failed and was removed from the system. System returns to service on remaining drive until RMA is completed. Users are informed that the system is available but does not have swap space. Consensus is reached to add some temporary swap space via a swapfile. (more…)
2 Comments
Link:
https://dannyman.toldme.com/2006/09/06/serial-console-woes/
So, I’m setting up a box. I need to test different filesystem configurations, which will involve a lot of boot-configure-install-post-install-benchmark cycles. We have a nice network boot infrastructure, but getting serial booting to work is always fun. Today I found that the vendor has set up BIOS “remote access” to COM2. Funny thing, the box only has one serial port! So, I set that to COM1, and configure console redirection only up to the boot loader, tell the bootloader that I want text console=ttyS0 and we’re in business!
But man, if SuSE’s YaST aint a bloody mess when it downgrades to text on a serial port:
What you don’t see here is the constant slow screen-redraw, constant pressing control-L. This is what it looks like at a good moment!
I think I understand why. I mean, I would think that Linux developers would take serial consoles and text mode to heart. After all, that’s the whole point, right? But that’s how I think, because I manage dozens of servers at a time, remote, and all my boxes are rack-mount jobbies with lots o’ fans and nobody wants to be in the same room.
But the developers who hack on Linux probably aren’t hard-core SysAdmins. Their dev system is some beat-up old hardware sitting near their desk, wired up to a spare VGA monitor, so yeah, text mode is kind of an afterthought. Especially given the pain in the butt that setting up serial consoles can be!
2 Comments
Link:
https://dannyman.toldme.com/2006/08/16/linux-uptime-reset/
dman: Anyone ever been on a Unix box and see uptime reset without a reboot?
SmooveB: dman: yes
David: dman: yes
***dman smiles
David: dman: my personal favorate is the rollover or the negative rollover
SmooveB: dman: linux in particular
dman: LINUX, you say?
David: SmooveB: fancy that, that’s where I’ve seen it too
It seems that this issue is near and dear to those involved in “the uptime project” where, I guess, geeks sit around comparing uptime size. Which is kind of juvenile. However, this bug gave me a hearty laugh:
How reproducible:
ALWAYS
Steps to Reproduce:
1. Boot Linux system
2. Go away for 497 days
3. check uptime
That would be a bitch to QA! (more…)
2 Comments
« Newer Stuff . . . Older Stuff »
Site Archive
