As someone who has been an avid, long-time user of the distro that bears his name, this is sad news.
The Ars Technica article casts a grim (well, grimmer) shadow on the circumstances.
Update: fixed! The recently-released FTL by Subset Games has a problem with the 12.8 AMD Catalyst Drivers, whereby the jump map and enemy ships are not rendered See below) due to an issue with edge detection in anti-aliasing. The fix is to create a custom profile for FTLGame.exe in the Catalyst Control Center to over-ride the settings (support thread with instructions, and setting).
Update: Now with video!
(yes the overlaps the menu, but there’s not much interesting there anyway!)
This is another case of “should have read the manual”, but there are ways to see previous output in both screen and byobu.
ctrl + a + [
These key combinations cause screen/byobu to enter copy mode, where you can navigate using vi keys, can set marks for copying using
return and the like.
This should have been blindingly obvious, but I guess years ago I got used to using screen without scrollback. There more you know… the more it seems that you don’t know anything at all.
The media browser on my LG TV has been acting up recently. Instead of listing the categories set up in Plex it pops up a dialog saying “Warning: Not Found”. It does this despite being able to see the Plex Media Server (going to ‘bowse sources’ or similar brings up the server’s name but selecting it gives the same error).
Fortunately Dunhillsmoker on the Plex forums had a solution:
sudo service plexmediaserver stop
mv /var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Plug-ins/System.bundle/ ~/plex
mv /var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Plug-ins/Framework.bundle/ ~/plex
(note, depending on permissions you may need ot be root to do this)
sudo service plexmediaserver start
This sorted the problem for me.
Mousing to the “hot corner” in Cinnamon gives an overview of current workspaces, à la expose. Unfortunately a careless click can close one of those workspaces, as I found out last night. Equally, you may feel that the default 2 workspaces is too few and wish to expand upon that. Now, I think the numvber of workspaces should increase automatically*, but it’s nice to control such things. Unfortunately there is no “control panel” option to control the number of virtual desktops, and right clicking the workspace changer widget in the toolbar doesn’t seem to have any useful effect.
However, hit Ctrl+Alt+Down and there should be a ‘+’ icon on the right hand side which will add as many workspaces as you require.
Update: Apparently the hot-corner expose has the plus to add workspaces too. I guess I just didn’t see it there! Cheers James.
saved my server. It wasn’t booting after an upgrade to Debian Squeeze, despite following the upgrade instructions. Connecting to the serial console showed there were problems with finding root (grub error while parsing number, error 23) which was at md1.
Changing the first line to
root (hd0,0) and adding
initrd /boot/initrd.img-2.6.32-5-amd64 allowed the system to boot normally. I’m not sure why
grub-setup didn’t add the initrd line, but I can forgive that as it’s working now.
Remember to update grub’s config once you have it booting.
Because I keep forgetting, here’s a reminder to myself of the correct way to iterate through files and directories in bash, even considering spaces in filenames, whith a hat-tip to Thomas Howard Uphill:
find . -type f|grep .ext$ |while read file
I was doing my initial “is it working?” tests after reinstalling mpc, and
ncmpc was also showing no files. What I didn’t appreciate was that the music database is no populated by default- you have to issue an “update” command manually (or semi-manually by running a client that issues the command for you).
and your directories should be searched!
There are a number of ways of showing the progress of a
dd copy. The easiest is sending the USER1 signal to the dd process, like:
dd if=FILE1 of=FILE2
pkill -USER1 dd
But that only gives a current status – eg 12345678 bytes transferred (11.77MB) … [8.56MB/s]. Not that helpful if you want an ongoing update. You can make it periodic by using the
watch -n 10 pkill -USR1 dd
Still not perfect. If you want a progress bar, ETA and so forth, you’re best off using
pv, a utility that measures the speed of a file through a pipe. If you don’t know what that means, I’d recommend reading up on the UNIX philosophy and pipes, but basically it means you can tell what dd is doing. Use it like so:
pv FILE1 | dd of=FILE2
For my use, backing up a 500GB hard drive that I use with a NAS (an NSLU2 I’ve probably mentioned before), I used the following command:
sudo pv /dev/sde3 |dd of=~/tera/nslu2.img
/dev/de3 is the data partition on the drive
~/tera/nslu2.img is the image file I want written to a terabyte-sized hard drive, mounted at
As a post-script, the reason I’m backing this drive up is my nslu2 is failing weirdly. It was running without a hitch for years, then it without apparent warning dismounted the drive in slot1 and reverted to running from flash. I only figured that out as I had to log in with an old password. Trying to start it up results in it beeping once every minute or so, with the ready status lamp flashing orange. It seems to go through a loop. I thought it was a temporary glitch, as when I plugged the drive into my desktop to check the thing was intact the partitions showed up, then when I plugged it back into the nslu2 and turned it on it worked fine.
That was 3 nights ago. This evening it’s done the same thing, except repeating the steps didn’t sort it out. Running the drive through some brief SMART diagnostics and a partition check shows up no problems, so I’m inclined to believe the problem lies in the nslu2. I’ll post again if I can sort it, but at this stage I think a re-flashing is in order. Only problem is I can’t remember what firmware I flashed onto the nslu2 in the first place. D’oh!
I was using scp to upload some files (as you should!) and maxing out my connection while doing it. It made using ssh problematic! Fortunately there’s an easy switch to use to limit the rate:
scp -l 1024 /file1 user@host:/file2
The -l switch limits scp to the specified upload rate in kilobits per second. Handy!