Read and share these 5 reasons to avoid ...


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Read and share these 5 reasons to avoid ...
# 1  
Old 07-11-2008
Read and share these 5 reasons to avoid ...

Read and share these 5 reasons to avoid iPhone 3G with friends, family and coworkers. The iPhone's DRM prevents free software from being run on it at all, and gives Apple the authority to determine what can legally be installed by anyone on their own mobile computer.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Red Hat

Read speed too bad on NAS share on VM

Hi, We have two servers in scenario (vmsoldot01 is Oracle VM with Linux and tldtppod15 is physical Linux server). One NAS share is mounted on both servers with similar permissions and access. But READ speed is too bad on virtual in comparison to physical server. While trying to diagnose this, I... (2 Replies)
Discussion started by: solaris_1977
2 Replies

2. Shell Programming and Scripting

Directoy Size - avoid cannot read directory

Hello, I need to write a script to check directory size on a linux server. I do not have access to some directories Inside the directory tree so I've got some warning in the output that say : du : cannot read directory .... Could you please help me. I did try Inside of my script to... (2 Replies)
Discussion started by: Aswex
2 Replies

3. Solaris

Reasons for NOT using LDOMs? reliability?

Dear Solaris Experts, We are upgrading from sun4u to T4 systems and one proposal is to use LDOMs and also zones within LDOMs. Someone advised using only zones and not LDOMs because the new machines have fewer chips and if a chip or a core fails then it doesn't impact the zones, but impacts... (3 Replies)
Discussion started by: User121
3 Replies

4. Shell Programming and Scripting

Help with data reformat if share share content

Input data: read1_data1 read1_data1 read2_data1 read3_data1 read4_data1 read4_data1 read4_data1 read5_data1 . . Desired output result: read1_data1 read1_data2 read2_data1 read3_data1 read4_data1 (3 Replies)
Discussion started by: perl_beginner
3 Replies

5. Solaris

Samba: share subfolder as read only.

Hi, Currently I have a Samba shared configured as follows: comment = Public fileshare path = /u02/pub guest ok = Yes writeable = Yes There is a subfolder under /u02/pub called /u02/pub/expenses/hardware that I need to make read only. How do I do this? I am new to using Samba. ... (2 Replies)
Discussion started by: sparcman
2 Replies

6. Ubuntu

Kubuntu on (certain) Lenovo laptops not possible - reasons?

Hi. I've used the Wubi install of Ubuntu and Kubuntu on my Windows XP machine for close to half a year now. My brother has let me know of a program where he works by which they're getting rid of (with support negated) several Lenovo laptops, on which, he also informs me, the K 'flavor' of Ubuntu... (1 Reply)
Discussion started by: SilversleevesX
1 Replies

7. IP Networking

netstat - possible reasons for high IP count ???

One of my servers started getting heavily loaded a few weeks ago for a few hours, so I did some studying and wrote a script to use netstat to get the IP addresses connected and the count. I put a new chain in iptables and if an IP is using more than 40 connections, it gets added to that chain which... (3 Replies)
Discussion started by: PWSwebmaster
3 Replies

8. UNIX for Advanced & Expert Users

How to Mount a Remote NTFS Share for Read/Write under Linux

I've done this in the past, but I didn't save the syntax. I'm still kicking myself about that... I am trying to mount \\server_name\share_name for read/write under CentOS 5.2 (a "generic" version of RedHat). As I recall, there was a fairly simple (maybe a oneline) command that would allow NTFS... (2 Replies)
Discussion started by: shew01
2 Replies

9. Solaris

To find out the reasons it crash

What are the steps to find out the reasons it crash in the solaris machine (3 Replies)
Discussion started by: sandeepkv
3 Replies
Login or Register to Ask a Question
update_dyld_shared_cache(1)				    BSD General Commands Manual 			       update_dyld_shared_cache(1)

NAME
update_dyld_shared_cache -- Updates dyld's shared cache SYNOPSIS
update_dyld_shared_cache [-root directory] [-overlay directory] [-arch arch] [-force] [-debug] [-sort_by_name] [-universal_boot] [-verify] [-dylib_list file] [-iPhone] [-cache_dir dir] DESCRIPTION
update_dyld_shared_cache ensures that dyld's shared cache is up-to-date. This tool is normally only run by Apple's Installer and Software Update, as they are the only official ways for OS dylibs to be updated. But if for some reason you used another mechanism to alter an OS dylib, you should manually run update_dyld_shared_cache. Note that the new cache does not take effect until the OS is rebooted. If a safe-boot is done (booting with shift key held down) the cache is deleted. The dyld shared cache is mapped by dyld into a process at launch time. Later, when loading any mach-o image, dyld will first check if is in the share cache, and if it is will use that pre-bound version instead of opening, mapping, and binding the original file. This results in significant performance improvements to launch time. update_dyld_shared_cache scans the directory /var/db/dyld/shared_region_roots for text files containing paths to mach-o executables. The full dependencies of all dylibs required by those executables is used to determine which libraries are commonly used and should be placed in the shared cache. If one of the text files contains a path to a dylib, that dylib and its dependents will be forced into the cache. update_dyld_shared_cache builds a separate cache file for each architecture. The cache files and a readable text map of the cached are gen- erated to /var/db/dyld. You must be root to run this tool. The options are as follows: -root directory This option specifies the root of an OS installation for which dyld's shared cache should be updated. This is used by the In- staller to update the dyld shared cache in a partition other than the one you into which you are currently booted. The cache files are created in the var/db/dyld directory of the specified directory. Note: if you are manually doing this, be sure to run the update_dyld_shared_cache tool that is in the partition being updated. This assures the cache format created will match that expected when booting off that partition. -overlay directory This option specifies the root of a sparse directory tree. When building the dyld shared cache, any corresponding mach-o files in the sparse directory will override those in the boot partition. This is used by Software Update to build a dyld shared cache for the update that is about to be installed. The cache files are created in the var/db/dyld directory of the specified direc- tory. -arch arch By default update_dyld_shared_cache generates cache files for all architecture that the current machine can execute. You can override this behavior by specifying one or more -arch options and list exactly which architectures should have their shared caches updated. -force This option will cause update_dyld_shared_cache to regenerated the shared cache files even if they appear to be already up-to- date. -debug This option prints out additional information about the work being done. -sort_by_name By default update_dyld_shared_cache assigns a random start address to each mach-o image in the cache. This option causes the start addresses to be chosen in path order, thus subsequent runs will produce the same address layout which can help reproduce some bugs. -universal_boot This option can only be used running on an machine with an Intel processor. It builds caches that can be used when booting on both 32-bit and 64-bit machines. -dylib_list file Instead of scanning /var/db/dyld/shared_region_roots/, this option provides a file that contains a list of the dylibs to use when building the shared cache file. -verify Will regenerate a shared cache in-memory that matches the randomization of the existing shared cache file. Then instead of writ- ing the cache file, it compares the in-memory cache file to the on disk version and reports any differences. -iPhone indicates that cache is not for the current Mac OS X, but for rather for an iPhone -cache_dir directory This option specifies the directory in which to create the cache file(s). If not specified, the cache file(s) are created in the standard location (e.g. var/db/dyld/) of the root partition. FILES
/var/db/dyld/shared_region_roots directory of text files with paths to mach-o images used to determine what should be in shared cache. SEE ALSO
dyld(1) Darwin Oct 10, 2008 Darwin