- The "Reopen windows when logging back in" feature It can now be disabled. The UI will still have the checkbox but it will have no effect. This is good enough for me. Here is how to fix it.
- NTFS Support Regarding the NTFS support it is still not available for free as the NTFS-3G driver that works with MacFUSE under Snow Leopard. I did however find yet another available driver: Paragon software has a driver for NTFS on Mac OSX as well.
Status on unwanted features of Mac OSX Lion
Here is an update on the issues I encountered running OSX Lion.
Requirements for building osslsigncode 1.3 on openSUSE 11.4
osslsigncode is not available on the OBS. So if you need this tool you need to install the proper dependencies and build it yourself.
You need to run the following command to install the components needed to be able to build osslsigncode on openSUSE 11.4 64-bit:
You need to run the following command to install the components needed to be able to build osslsigncode on openSUSE 11.4 64-bit:
sudo zypper in gcc make libopenssl-devel libcurl-develBack to Snow Leopard
So I have reverted back to Mac OS X Snow Leopard. Three or four things made me go back.
Now and then you see the department of badly chosen defaults has to much to say because the software vendor are trying to control the way their software is used. That could be fine - if only it was possible to change these values.
Now and then you see the department of badly chosen defaults has to much to say because the software vendor are trying to control the way their software is used. That could be fine - if only it was possible to change these values.
- Relaunching the running applications By default ones applications are relaunched every time you start up Lion. When you shut down there is a checkbox you need to uncheck to not enable this feature. I have found no way to change this checkbox to be unchecked by default.
- Supported filesystems I have an external drive that is formatted with NTFS since that was working in both Windows, Linux and OS X. With Lion that is not working at the time of writing unless you buy Tuxera NTFS. It is not because Tuxera NTFS is extremely expensive but relative to what Mac OS X Lion cost it will be an expensive feature. Then there is support for exFAT which could be a solution in the long run. For now there is no working support for that filesystem in Linux. Another detail is that Time Machine only works with the JFS+ filesystem. I am trying to solve this issue in another way. My router has a USB port and I have installed Tomato on it. So it is my plan to make this disk available over some network protocols that are supported across multiple operating systems.
- Mission control I don't like the new mission control view. I'm not using the widgets so the Dashboard should just be as hidden as possible if you ask me. Launchpad and the Dashboard is not features I use. My minimized windows are not visible in mission control as they are in the All Windows view in Snow Leopard which is not available in Lion.
In time I will probably upgrade again. The filesystem issue will probably be resolved over time. The thing about being able to permanently uncheck the checkbox about relaunching is a feature that shouldn't be to hard to add. Hopefully that will be resolved soon as well.
Mission control and Launchpad are probably here to stay - and I am able to avoid these features most of the time so that is not keeping me from upgrading.
How to change default application for opening pdf files in openSUSE
Gnome applications in openSUSE 11.4 apparently defaults to opening pdf files in Gimp. Okular would be a more sane choice here. To get that to work you need to edit the file:
Change the line that starts with
Actually there is a long discussion about the issue focusing on it being a Firefox issue in the openSUSE forums.
There is also a discussion on whether correct way is to edit
/usr/share/applications/defaults.listChange the line that starts with
application/pdf= toapplication/pdf=kde4-okularApplication_pdf.desktop;gimp.desktopActually there is a long discussion about the issue focusing on it being a Firefox issue in the openSUSE forums.
There is also a discussion on whether correct way is to edit
/etc/gnome_defaults.conf but editing this file in openSUSE 11.4 and running SuSEconfig --module glib2 as root didn't have the desired effect.
Mac OS X Lion impressions
So the install procedure was totally smooth - actually pretty boring.
First thing to notice was that MacFUSE wasn't working and therefore I had no access to my NTFS partitions and drives.
I tried to reinstall MacFUSE and the NTFS-3G driver. But that didn't help.
Next thing I did was to uninstall the NTFS-3G driver. Now I didn't get the error message every time OS X booted. I also uninstalled MacFUSE and then I was able to mount the NTFS drives (both BOOTCAMP and external USB drives) in read only mode. That is a start.
It seems that OSXFUSE will be around soon - and that could be the solution.
I'll keep you updated on this issue.
Next thing to notice was that the three finger gesture for switching back and forth in Google Chromes browser now did not work anymore (in safari it was changed to a two finger gesture). The three finger gesture switched between spaces instead it seems. Here there were an easy fix. Go to "System Preferences" > "Trackpad" > "More Gestures" and change the "Swipe between pages" from two to three fingers. That disables the new three finger gesture functionality but instead you can change that to a four finger gesture. I don't use spaces or the dashboard so disabling it will be just fine for me.
Next thing that was different (and not in a good way) was my "Hot Corners" configuration. I had configured it so that when I moved the mouse to the top-left screen corner i would see all the running applications. Now I get the "Mission Control" view instead. It is not that different from what I had so I will just have to get used to that.
There are also a few new applications in the dock - but other than that it seems to be business as usual seen from my perspective.
First thing to notice was that MacFUSE wasn't working and therefore I had no access to my NTFS partitions and drives.
I tried to reinstall MacFUSE and the NTFS-3G driver. But that didn't help.
Next thing I did was to uninstall the NTFS-3G driver. Now I didn't get the error message every time OS X booted. I also uninstalled MacFUSE and then I was able to mount the NTFS drives (both BOOTCAMP and external USB drives) in read only mode. That is a start.
It seems that OSXFUSE will be around soon - and that could be the solution.
I'll keep you updated on this issue.
Next thing to notice was that the three finger gesture for switching back and forth in Google Chromes browser now did not work anymore (in safari it was changed to a two finger gesture). The three finger gesture switched between spaces instead it seems. Here there were an easy fix. Go to "System Preferences" > "Trackpad" > "More Gestures" and change the "Swipe between pages" from two to three fingers. That disables the new three finger gesture functionality but instead you can change that to a four finger gesture. I don't use spaces or the dashboard so disabling it will be just fine for me.
Next thing that was different (and not in a good way) was my "Hot Corners" configuration. I had configured it so that when I moved the mouse to the top-left screen corner i would see all the running applications. Now I get the "Mission Control" view instead. It is not that different from what I had so I will just have to get used to that.
There are also a few new applications in the dock - but other than that it seems to be business as usual seen from my perspective.
Fixing Squeezebox Radio loosing connection
I got a Logitech Squeezebox Radio for my birthday. What a great toy. With a WiMP subscription this is really a great product.
It did however loose connection to the internet fairly often. It happened kind of random. When it lost connection the menus did not respond very well anymore. I had to turn of the device and turn it on again for it to connect to mysqueezebox.com again.
Under the diagnostics screen I could see that there were a status for different ports. Investigating a little more I thought it would help to forward these ports in my router to the Squeezebox Radio. That actually fixed the issue.
The ports that needs to be forwarded are:
Using DD-WRT on my router at the moment port forwarding was easily configured.
It did however loose connection to the internet fairly often. It happened kind of random. When it lost connection the menus did not respond very well anymore. I had to turn of the device and turn it on again for it to connect to mysqueezebox.com again.
Under the diagnostics screen I could see that there were a status for different ports. Investigating a little more I thought it would help to forward these ports in my router to the Squeezebox Radio. That actually fixed the issue.
The ports that needs to be forwarded are:
- 3483 for UDP and TCP
- 9000 for TCP
Using DD-WRT on my router at the moment port forwarding was easily configured.
How to get Back To The Future - The Game to work on Mac OSX
Everytime I download a new episode of "Back To The Future" from Telltale Games I end up with a screen that looks like the one below.
On the forum from telltale games it takes a while before a solution comes up.
I now found a solution (specifically for the mac) that seems to be the right way to solve it:
Try 'Command'+'Shift+'-' (yes the actual -), press yes, then 'Command'+'Shift+'+'. Then log back in.
An alternative option is to run the game as root. From a terminal run:
sudo /Applications/BackToTheFuture103.app/Contents/MacOS/Mac_Game
Google deleted my blog
So what just happened. I typed blog.vester.org one day and my blog was gone!
What just happened?
So it became possible to transition Google Apps account to regular Google Accounts. I tried that out but it turned out I had a regular Google Account with my Google Apps email address which blocked the possibility of transitioning my user to the new infrastructure. I never really used that user so the obvious move was to delete that user. I used the user to write one post on my blog at some time. I believe that is why my blog got deleted. I haven't been able to confirm this anywhere yet. It is a pretty scary thought that someone can delete a whole blog if they at some time wrote a post in a blog. The user wasn't even authorized to post to the blog anymore.
How did I recover the blog?
Bloggers own help did not help me in recovering my blog.
Luckily i discovered that the blog had disappeared in time. By "in time" I mean that Google still had my blog in it's cache. To save my blog I saved a local copy of all the blog entries. Luckily I had only been blogging for 7 months so that wasn't to bad.
Then I recreated the blog and created all the posts again. To create the posts again I used some features of blogger I usually didn't need.
It turned out that it is possible to set the exact time of when a post should be published - even in the past.
By expanding the "Post Options" at the bottom of the post editor it is possible to set the exact date and time of when the post should be published. That way I could recreate the blog.
Next step needed to be able to rebuild the blog in the future is to look for ways to backup the blog.
What just happened?
So it became possible to transition Google Apps account to regular Google Accounts. I tried that out but it turned out I had a regular Google Account with my Google Apps email address which blocked the possibility of transitioning my user to the new infrastructure. I never really used that user so the obvious move was to delete that user. I used the user to write one post on my blog at some time. I believe that is why my blog got deleted. I haven't been able to confirm this anywhere yet. It is a pretty scary thought that someone can delete a whole blog if they at some time wrote a post in a blog. The user wasn't even authorized to post to the blog anymore.
How did I recover the blog?
Bloggers own help did not help me in recovering my blog.
Luckily i discovered that the blog had disappeared in time. By "in time" I mean that Google still had my blog in it's cache. To save my blog I saved a local copy of all the blog entries. Luckily I had only been blogging for 7 months so that wasn't to bad.
Then I recreated the blog and created all the posts again. To create the posts again I used some features of blogger I usually didn't need.
It turned out that it is possible to set the exact time of when a post should be published - even in the past.
By expanding the "Post Options" at the bottom of the post editor it is possible to set the exact date and time of when the post should be published. That way I could recreate the blog.
Next step needed to be able to rebuild the blog in the future is to look for ways to backup the blog.
Splitting VPNC connection
When using VPNC to connect through vpn it is possible to only route parts of the traffic from the NIC through vpn.
To do that you need to add a script to your VPNC configuration. It could be stored in this file /etc/vpnc/split
The script needs to be made executable:
The script is documented here and can look like this:
The first line of the configuration (for instance /etc/vpnc/default.conf) should then reference the script like this:
Then when you connect through VPN only IPs starting with 10, 159 and 139 will be routed through VPN.
To do that you need to add a script to your VPNC configuration. It could be stored in this file /etc/vpnc/split
The script needs to be made executable:
chmod +x /etc/vpnc/splitThe script is documented here and can look like this:
#!/bin/bash
#http://svn.unix-ag.uni-kl.de/vpnc/branches/vpnc-nortel/split_tunnel.txt
#Add one IP to the list of split tunnel
add_ip ()
{
export CISCO_SPLIT_INC_${CISCO_SPLIT_INC}_ADDR=$1
export CISCO_SPLIT_INC_${CISCO_SPLIT_INC}_MASK=255.255.255.255
export CISCO_SPLIT_INC_${CISCO_SPLIT_INC}_MASKLEN=8
export CISCO_SPLIT_INC=$(($CISCO_SPLIT_INC + 1))
}
# Initialize empty split tunnel list
export CISCO_SPLIT_INC=0
# Delete DNS info provided by VPN server to use internet DNS
# Comment following line to use DNS beyond VPN tunnel
#unset INTERNAL_IP4_DNS
# List of IPs beyond VPN tunnel
add_ip 10.0.0.0 # pop3.mycom.com and smtp
add_ip 159.0.0.0 # ldap.mycom.com
add_ip 139.0.0.0
# Execute default script
. /etc/vpnc/vpnc-script
# End of scriptThe first line of the configuration (for instance /etc/vpnc/default.conf) should then reference the script like this:
Script /etc/vpnc/split
IPSec gateway...Then when you connect through VPN only IPs starting with 10, 159 and 139 will be routed through VPN.
Abonner på:
Opslag (Atom)