Been a while since posting here, learnt a few things during that time.
Booting into runlevel 3 by default can have some odd side effects when you've spent time building scripts in runlevel 5.
Namely, I discovered my backup script wouldn't work for some reason when I tried to fire it off from the command line. I had taken the command generated by GRsync GUI and put it in a #! script so I could run from where ever and not have to remember the command and the flags I was using.
After a bit of poking I determind the backup disk had died. Or so I thought.
I log in locally, startx up x and no disk available. It used to live under /media/backup but it just wasn't there.
Discovered lshw to find out about hardware in the system, that reported the disk was present. So hopefully it was a config thing rather than hardware failure as first feared.
My GRsync (that I had originally used to launch the backup process) wouldn't run either.
Experiment time... logout of X, su and change the run level back to 5 (init 5). Login as regular user and presto, backup works again.
Seems running startx to get to desktop rather than switching run level means some script or other (presumably in /etc/rc5.d) that mounts the backup disk isn't being fired.
Another useful little program I've discovered during investigations is conky. A system monitoring tool. When first launched it is really dull looking black/white, but with the addition of a .conkyrc file to my home area it can be customised very heavily. A quick bit of googling brings up loads of screenshots with sample .conkyrc files to play with.
Been experiencing some strange behaviour with Banshee recently too... when downloading a podcast from the BBC, one one box (FC11 64bit) any - or _ characters in the filename get stripped.
On my home machine (FC10 32bit) the - and _ are left alone and remain in the filename.
On the face of it that wouldn't be an issue so long as each Banshee can find the files right? Problem is I want to setup a process to keep the two postcast directories in sync, so if one or other machine doesn't get turned on the other would make the download. Redundancy if you like to make sure I get the podcast!
Not worked that one out yet :/
Monday, 29 June 2009
Wednesday, 3 June 2009
Dynamic DNS (contd.)
Turns out I was looking in the wrong place in my router config. I was expecting it to live under the firewall options and open a port there, but instead it is actually under 'Virtual servers'.
Ahh well, either way it works now and I can get CLI access from anywhere to my home machine via SSH :)
Ahh well, either way it works now and I can get CLI access from anywhere to my home machine via SSH :)
Monday, 1 June 2009
Playing with DynDNS
My router is an older one. But it was a good one when I chose it, still does the job even if it can't support latest WiFi encryption tech (so have to rely on WEP!).
What it dows support however is out of the box dynamic DNS. So having a play with it last night and getting some odd results.
If I give my browser the magic URL it goes out, get redirected to my router, which passes the request to a http instance on my LAN (I assume the first one it finds) and passes results back to the browser. So as a proof of concept, I'm happy.
Now the server it is finding is my dev server, which I have not yet put any effort into nailing down http.conf so it displays the default 'welcome to fedora/apache instance' page. Not good.
Simple thinks I, I only want Dynamic DNS for use with SSH so I'll turn on firewall blocking of all ports but the ssh port.
Added to IPTables config on the macine and (re)started IPTables but still the machine seems to be serving out html from httpd :(
Looked at whether I could block incoming requests by port in the router firewall, but not found the options I need yet. I'm sure they should be there somewhere.
Maybe playing with these things at 1 in the morning is not such a good idea :/
Needless to say I switched off DynDNS in my router and PC is now off :P
What it dows support however is out of the box dynamic DNS. So having a play with it last night and getting some odd results.
If I give my browser the magic URL it goes out, get redirected to my router, which passes the request to a http instance on my LAN (I assume the first one it finds) and passes results back to the browser. So as a proof of concept, I'm happy.
Now the server it is finding is my dev server, which I have not yet put any effort into nailing down http.conf so it displays the default 'welcome to fedora/apache instance' page. Not good.
Simple thinks I, I only want Dynamic DNS for use with SSH so I'll turn on firewall blocking of all ports but the ssh port.
Added to IPTables config on the macine and (re)started IPTables but still the machine seems to be serving out html from httpd :(
Looked at whether I could block incoming requests by port in the router firewall, but not found the options I need yet. I'm sure they should be there somewhere.
Maybe playing with these things at 1 in the morning is not such a good idea :/
Needless to say I switched off DynDNS in my router and PC is now off :P
Friday, 15 May 2009
Update breaks keyboard (and mouse!)
Got a fright at the weekend, after my PC booted to the login screen sans problem I found I couldn't login. Not because my password/user had become corrupt or anything like that but I simply could not enter my username/password as both my mouse and keyboard were dead.
Both are plugged in to the box via USB->PC2 adaptors. I unplugged them and plugged into my USB hub and presto - fully functional peripherals again. :/
So it seems the last update either broke the way the OS talks to PC sockets or Fedora guys have switched off support by default. Took me by suprise that sort of change would be done in an update rather than a major release as it seems a shift in policy (assuming it was switched off rather than broken).
Both are plugged in to the box via USB->PC2 adaptors. I unplugged them and plugged into my USB hub and presto - fully functional peripherals again. :/
So it seems the last update either broke the way the OS talks to PC sockets or Fedora guys have switched off support by default. Took me by suprise that sort of change would be done in an update rather than a major release as it seems a shift in policy (assuming it was switched off rather than broken).
Saturday, 28 March 2009
Hurrah for Nokia!
Here's me, sat at home. Knowing at some point if I am to use my shiny new Nokia N85 for music at the gym etc I am going to have to spend some time fiddling to get my Nokia and Banshee talking nicely.
So I try plugging in that little USB cable to see if Linux recognises a mass storage device. Not only is it recognised but Banshee instantly adds the phone as a writable device for syncing my music.
Wow!
No tinkering at all needed. Not sure who's done the work or whether it's just that Nokia have followed the same protocol standards as the Banshee coders did, but either way I'm very happy I don't have to spend ages getting it to work.
Only ages to sync it all!
So I try plugging in that little USB cable to see if Linux recognises a mass storage device. Not only is it recognised but Banshee instantly adds the phone as a writable device for syncing my music.
Wow!
No tinkering at all needed. Not sure who's done the work or whether it's just that Nokia have followed the same protocol standards as the Banshee coders did, but either way I'm very happy I don't have to spend ages getting it to work.
Only ages to sync it all!
Friday, 20 March 2009
Banshee 1.4.2 problem with flash drive
Since upgrading to FC10, the Banshee install I have has been refusing to write to my generic USB sticks.
When transferring tracks, using the Banshee interface, to my USB drive I was getting an error "Object reference not set to an instance of an object".
While I have a reasonable grasp what the error means from a coding perspective, I don't have the time nor the inclination to dig into the source code. Nor would the average non-coder trying to move to Linux have any idea.
When transferring tracks, using the Banshee interface, to my USB drive I was getting an error "Object reference not set to an instance of an object".
While I have a reasonable grasp what the error means from a coding perspective, I don't have the time nor the inclination to dig into the source code. Nor would the average non-coder trying to move to Linux have any idea.
Turns out that a fix found here:
http://blog.hyperandy.com/2009/01/20/banshee-141-object-reference-not-set-to-an-instance-of-an-object-error-fix/#comment-4224
Sorted out my problem nicely.
I added output_formats=audio/mp3 to the .is_audio_player file on the USB device and I can now copy my tunes for the car and I'm a happy raver once again :)
Apparently this is something to do with telling Banshe the device supports mp3 format audio and not to bother re-encoding for the device.
Monday, 2 February 2009
Streaming Radio1 now works :)
Followed a link from the BBC help pages to get to the rpm download of the latest (11) RealPlayer (http://www.real.com/linux).
Installed as root:
yum installlocal /home/-path to .rpm
Restart my browser and hey presto it works :) Much more succesful than previous attempts with Realplayer10 pluging nonsense!
Installed as root:
yum installlocal /home/
Restart my browser and hey presto it works :) Much more succesful than previous attempts with Realplayer10 pluging nonsense!
Subscribe to:
Posts (Atom)