- On installation: Windows could not determine if this computer contains a valid system volume This can occur if you have a USB drive in your machine on installation - see here for details.
- Turn off Windows needs your permission to continue (known as UAC) - Basically it can be done in a variety of ways (see this handy blog) - like using the user account control panel, msconfig or TweakUAC.
Wednesday, 5 December 2007
Wednesday, 28 November 2007
Tuesday, 27 November 2007
An example response should look like:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 7.04
In theory it should work on any LSB (Linux Standard Base) distro...
Monday, 19 November 2007
Never use them again (they are too good to be true). There are plenty more out there - see this handy Motley Fool article.
Tuesday, 13 November 2007
sudo opcontrol --event=default
the following lines occur:
/usr/bin/opcontrol: 1: arith: syntax error: "NR_CHOSEN - 1"
/usr/bin/opcontrol: 1: arith: syntax error: "NR_CHOSEN - 1"
No events given.
ophelp --get-default-event gives the following
According to this bug report - Here's how to fix it: Replace /bin/sh with /bin/bash in the first line of /usr/bin/opcontrol
Thursday, 1 November 2007
News flash: It seems that this bug was reported a while ago on the Firefox bugzilla but it _still_ hasn't been fixed??!!
Wednesday, 31 October 2007
Using another app (such as xpdf - to get it on Ubuntu: sudo apt-get install xpdf-reader) won't help - the same thing happens.
It turns out that this only happens when Evince/Xpdf is started from Firefox - which is probably how alot of people start evince. It seems that this only happens if Firefox has already opened the audio device (e.g. after playing some flash content). So it's actually an issue with Firefox..... Darn. I suspect this may happen with any app spawned by Firefox... Firefox isn't very good with letting go of audio devices once it's done with them - or maybe it's Flash being crap....
It's a particular bummer when you restart firefox whilst leaving evince running 'cos then you're stuck with evince attached to the audio and the pesky thing won't play anything anymore. You'll have to restart evince as well in that case.
Monday, 8 October 2007
Using something like Launchd Editor or Apple's Property list editor (which comes with their dev package - (you'll need to run 'em using sudo) or just a text editor (e.g. sudo vim /Library/LaunchDaemons/com.vmware.launchd.vmware.plist). Basically if you want to disable the services then a add a new key:
Friday, 5 October 2007
Wednesday, 26 September 2007
For more info on which services can be forsaken check out the delightful Black Viper's site.
Tuesday, 25 September 2007
Also there's the Mactel Linux site that's working on enhancing Linux on the Mac - they've got a bunch of patches for the kernel - some of these patches also provide for coolin' down...
Sunday, 2 September 2007
$ sudo "/Library/Application Support/VMware Fusion/boot.sh" --stop
There's also a bunch of handy stuff in that directory....Things like vmware-rawdiskCreator can be used to create virtual disks to link to existing partitions for booting physically (i.e. those bootable by rEFIt or Boot Camp ) installed operating systems like Linux or Windows.
Wednesday, 29 August 2007
To read out the temperatures from the loaded kernel extension use the systctl command:
or to read all speedit monitored info try:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 3f:d6:e7:72:9a:ab:4e:e1:21:91:3a:88:6b:78:83:ce. Please contact your system administrator. Add correct host key in /Users/username/.ssh/known_hosts to get rid of this message. Offending key in /Users/username/.ssh/known_hosts:73 RSA host key for localhost has changed and you have requested strict checking. Host key verification failed.It's worrying.... Has someone hacked my machine (again!?). Or am I being paranoid for the 13th time this week?
This error is due to a mismatch between the RSA key that you already have stored on your machine in the /Users/username/.ssh/known_hosts file, and the one that ssh has just obtained over the network on this login attempt. Note: newer versions of ssh now store hashes of hostnames (see: ssh-keygen -H) in the known_hosts file to maintain privacy. Either the ssh server key has been changed legitimately (by you or some admin) or it's been hacked. It's also possible that someone on has set up a machine on the same IP address as the server you're trying to contact then you'll find you can't login - in which case you (or some admin) needs to track down the rogue machine.
To check the key is correct login to the machine in question - preferably on the console, but if you're connecting via ssh then you'll have to ignore the warnings above. Then you can directly print your server's key's fingerprint. There are a few types of keys: RSA, DSA, ECDSA (for SSHv2), and RSA for SSHv1. If your on a 'standard' Linux box then it's probably at: /etc/ssh/ssh_host_rsa_key.pub (or for DSA /etc/ssh/ssh_host_dsa_key.pub). If you're on a Mac OSX it is in: /etc/ssh_host_rsa_key.pub (or /etc/ssh_host_key.pub or /etc/ssh_host_dsa_key.pub). e.g. So on a Mac OSX box try:
% ssh-keygen -l -f /etc/ssh_host_rsa_key.pub
2048 3f:d6:e7:72:9a:ab:4e:e1:21:91:3a:88:6b:78:83:ce. /etc/ssh_host_key.pub
The key fingerprint (of the corresponding key type - in this case RSA) should match the one shown above. If these don't match then something fishy is going on....
Also just for info you can list all the fingerprints of all your stored host keys
% ssh-keygen -l -f .ssh/known_hosts
Instead you can just compare the public keys stored on your client in ~/.ssh/known_hosts with the keys on the server in /etc/ssh/ssh_host_*.pub
It is also possible that if you've upgraded your version of ssh (or altered your ssh-agent setup), and your machine has previously stored an RSA key in your ~/.ssh/known_hosts file but it is now getting an ECDSA key from the server which obviously won't match but may still be a valid key for that machine. It seems that ssh could work out this problem for itself without any lack of security but currently can lead to such warnings.
[22jan16: Updated to simplify and include ECDSA keys]
Thursday, 23 August 2007
Wednesday, 22 August 2007
Before you start you'll need to have an /Users/username/.ssh directory (where username is your username) - or alter the scripts appropriately below. Create file /Users/username/Library/LaunchAgents/ssh-agent.plist containing:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
Then create a file /Users/username/.ssh/ssh-agent.sh containing:
exec /usr/bin/ssh-agent -a /Users/username/.ssh/ssh-agent.pipe -d
Note: ssh-agent has to be started using -d option as launchd doesn't like processes to fork off into 'daemons'...probably why a few people don't like it.
Make the script executable:
$ chmod +x /Users/username/.ssh/ssh-agent.sh
Then ssh-agent will get started next time you login by launchd, or you can start it immediately by running:
$ launchctl start com.ssh.ssh-agent
Now you need to set the following environment variable (you can use RCEnvironment to set ~/.MacOSX/environment.plist) - probably easiest to add the following line to your /Users/username/.profile:
You can then add your keys (assuming you've set 'em up using ssh-keygen or whatever) to the agent using:
Tuesday, 21 August 2007
/usr/include/g2c.h:21: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘integer’
Then, as suggested here, just add the missing typedefs to your code (then it _should_ work in gcc4.1):
typedef int __g77_integer;
typedef unsigned int __g77_uinteger;
typedef long int __g77_longint;
typedef unsigned long int __g77_ulongint;
The alternative is just to use gcc-3.4 which apparently 'just works'.
Thursday, 9 August 2007
It is generated by the lrm subsystem - linux-restricted-modules-2.* (Note: the module creation is controlled at bootup by /etc/default/linux-restricted-modules-common - make sure you haven't messed that filei - the modules created by /sbin/lrm-manager into a ramfs and mounted onto /lib/modules/2.6.XX-XX-generic/volatile) - why doesn't dpkg know??? (I guess since they're dynamic dpkg would need some more dynamic DB of such files...)
The nvidia.ko, nvidia_new.ko, nvidia_legacy.ko are loaded by the shell script /sbin/lrm-video (called from /etc/modprobe.d/lrm-video) based on [dot]trigger files in /lib/linux-restricted-modules/ e.g. .nvidia_new_installed
Using your favourite editor as root e.g:
sudo vi /etc/vim/vimrc