Change Snow Leopard NTFS to be Read Write

Copy from Guide: Enable native NTFS Read/Write in Snow Leopard
Rename the original /sbin/mount_ntfs tool:

sudo mv /sbin/mount_ntfs /sbin/mount_ntfs.orig

Create a script like this:

/sbin/mount_ntfs.orig -o rw “$@“

save the script to /sbin/mount_ntfs

sudo chown root:wheel /sbin/mount_ntfs
sudo chmod 755 /sbin/mount_ntfs

Enjoy R/W access to NTFS volumes…

In case you don’t like it

sudo mv /sbin/mount_ntfs.orig /sbin/mount_ntfs

and everything is back to R/O.

Move Podcast Producer to different hostname

sudo changeip old_ip new_ip old_hostname new_hostname what somewhat
But still the link to Podcast URL still does not work.

Google Search ‘change “Podcast Library URL”‘ give some insight available at Apple Discussion Forum

The key message copied here:

Check /Library/PodcastProducer/Shared/Server/member_preferences_.plist
There should be entries for server_host, tunnel_agent_host & tunnel_server_host that will need to be updated while PCP2 is shut down, which should handle it.

It works!

Rerun Apple Setup

There are files in /var/db
ls -al .*Done
-rw-r–r–@ 1 root wheel 0 Apr 2 17:34 .AppleSetupDone
-rw-r–r– 1 root wheel 0 Apr 2 17:33 .AutoBindDone
———- 1 root wheel 0 Apr 2 09:57 .WOLShutOffDone

Will this help re-run the setup

Bringing improved support for Adobe Flash Player to Google Chrome

Bringing improved support for Adobe Flash Player to Google Chrome: “Adobe Flash Player is the most widely used web browser plug-in. It enables a wide range of applications and content on the Internet, from games, to video, to enterprise apps.

The traditional browser plug-in model has enabled tremendous innovation on the web, but it also presents challenges for both plug-ins and browsers. The browser plug-in interface is loosely specified, limited in capability and varies across browsers and operating systems. This can lead to incompatibilities, reduction in performance and some security headaches.

That’s why we are working with Adobe, Mozilla and the broader community to help define the next generation browser plug-in API. This new API aims to address the shortcomings of the current browser plug-in model. There is much to do and we’re eager to get started.

As a first step, we’ve begun collaborating with Adobe to improve the Flash Player experience in Google Chrome. Today, we’re making available an initial integration of Flash Player with Chrome in the developer channel. We plan to bring this functionality to all Chrome users as quickly as we can.

We believe this initiative will help our users in the following ways:

  • When users download Chrome, they will also receive the latest version of Adobe Flash Player. There will be no need to install Flash Player separately.
  • Users will automatically receive updates related to Flash Player using Google Chrome’s auto-update mechanism. This eliminates the need to manually download separate updates and reduces the security risk of using outdated versions.
  • With Adobe’s help, we plan to further protect users by extending Chrome’s “sandbox” to web pages with Flash content.

Improving the traditional browser plug-in model will make it possible for plug-ins to be just as fast, stable, and secure as the browser’s HTML and JavaScript engines. Over time this will enable HTML, Flash, and other plug-ins to be used together more seamlessly in rendering and scripting.

These improvements will encourage innovation in both the HTML and plug-in landscapes, improving the web experience for users and developers alike. To read more about this effort, you can read this post on the Flash Player blog.

Developers can download the Chrome developer channel version with Flash built in here. To enable the built-in version of Flash, run Chrome with the –enable-internal-flash command line flag.

Posted by Linus Upson, VP, Engineering