Why do i need a us address

trying to download an app onto my ipod touch it is insisting I have a U S address what do I do????

You can only download iTunes purchases for the iTunes store in whihc you are physically located in and you your iTunes account must by associted with that country. Thus, I assum that you are trying to purchased from the USA store but yur iTunes account is not associted with the USA.

Similar Messages

HT201342 Why do I need a iCloud address I really don't understand what e iCloud is? I'd like to sync calendars from my iPad to my Mac will this help we achieve this open to anyone's input w previews experience!

Why do I need an iCloud email address? I mean I know I already have one set up but have never activated it what is the benefit?
Also does it make it easier to sync items between devices ie I'd like to get the calendar on my iPad 2 to transfer to my MacBook pro and vice versa.
Is it possible to activate iCloud syncing with out the iCloud email?
Any advice would be much appreciated

You can go to Settings>iCloud and enter you Apple ID to set up your account, then turn on syncing for the data you want to sync. If you don't want to use iCloud email, don't turn Mail to On. If you're Mac is runniing OS X 10.7.2 or later, you can sync it with your iCloud account. You do this by going to System Preferences>iCloud, signing into your iCloud account, then checking the data you want to sync with iCloud (see http://www.apple.com/icloud/setup/mac.html).
If you sync your calendar on both your phone and your Mac with your iCloud account, then will remain in sync using iCloud.

Why 10g RAC need 2 virtual address.

Hi,
I was reading on document for RAC installation and it tell me to configure 2 virtual IP.
Can any one tell me why two IP's for two machine.Can it be one IP as in windows cluster.
What is the IDEA behind VIRTUAL IP's.
Regards
MMU

Hi,
I understand this.My question is
on NODE 1
1 PRIVATE IP
1 PUBLIC IP
1 VIRTUAL IP
on NODE 2
1 PRIVE IP
1 PUBLIC IP
1 VIRTUAL IP
Why VIRTUAL IP on each node.
Regards
MMU

Why do we need WS Addressing??

What is WS Addressing? Why do we need in SOA??? Give me Some Examples guys

WS-Addressing is a transport-neutral mechanism by which web services communicate addressing information. SOAP envelopes & headers used within web services for transporting data throught transport layers like HTTP does not possess intelligence to specify unique addressing information. Hence, WS-Addressing evolved which contained endpoint references (EPR) and message information headers for identification. This information is processed independently of the transport mechanism or application.
For reference on WS-Addressing click here
By default, Oracle BPEL PM implements WS-Addressing for all asynchronous web service calls, hence we don't have to explicitly implement identification relationship between the incoming & outgoing messages.
Hope this will help
-Venkat Ch

Why is my iPhone telling me to go right and on the map it show to make a left uturn? I think this needs to get addressed quickly before anymore serious problem arise and it's on ios6

Well I use my iPhone to direct to where I need to go especially now with ios6 maps since then I can drop Tom Tom app and not pay the yearly fee, but it's kinda hard when my iPhone tell me to make a right turn and on the map it clearly show me to make a left u turn and never a right turn what's so ever. This issue I think need to be addressed ASAP before someone gets injured making a turn. This type of issues can put people at risk and should be taken serious. I have other issues non related to maps, but this mainly the only one I care about because it is a danger to people.

I have done that and it is definitely on. My husband has the exact same phone and I upgraded his IOS at the same time, but this problem is not happening to his phone (we are also on the same plan, so our service should be the same). Our settings appear to be identical and my phone is showing the 3G symbol at the top, so I can't understand why it won't access the network.
I've turned it on and off twice and have reset all settings with my iTunes account, but it still isn't working.
I'm not a complete idiot with this sort of stuff - I have tried all the obvious things.

HT201342 why would I need another e-mail address?

hi, Why would I need another e-mail address. When .me came out I thought that .mac would be erased so I gave everyone my .me account (even though I prefered the .mac name) the .mac continued to work and now everyone sends me TWO e-mails which arrive at exactly the same place. I can understand if the e-mails arrive at different mail boxes, then you could give your family one, your business another, your kids school a third, but why... why 3 accounts that go to exactly the same place. I realise I don't have to use all 3 but can someone tell me how to get the most out of these e-mail addresses. Thanks!

Just give out the one email address you want to use. They are all the same account anyway. People do not need to send emails to both email addresses so tell them to only use the one you prefer.

Why do I need to use MOLGA?

I know that this is a very basic question, but I have been asked why do we need to have a new MOLGA for every country; what I know of is:
1.     Is the standard method of supporting multi-country (Global) HCM. MOLGA is central to the SAP HCM solution.
2.     The correct screens are shown in PA30 to maintain the personnel data in the correct formats for social security or equivalent number, form of address, addresses, bank details and so on.
3.     The correct infotypes can be made available by MOLGA, where there are particular pieces of information required on a country by country basis u2013 therefore reducing the risk of non compliance
4.     Correct ESS screens are available
5.     Payroll available by country. For example the payroll program is run per country using the MOLGA PC00_Mxx_calc, where xx is the country code, therefore for GB it is PC00_M08_calc.
But apparently this is not a compelling enough reason - can anyone help with more good reasons?

Hi Marina
hope you are doing good.
Globalized firms need Integrated systems with Independent County Legal, Labor, Taxation ,Currency , Language requirements.
So a Global ERP System will help to achieve this without compromising the local requirements.
I shared my experience , hope it sound sane.
Regards
Rohit.S

I have a brand new MacBook Pro . I am trying to connect to the private wifi at my house but I need the IP address of my laptop . Everywhere I go on the laptop, the IP address is blank . How do I find the IP address if laptop is not connected to the wifi

I have a brand new MacBook Pro and I'm trying to connect to the private wifi at my house however, I need the IP address. Everywhere I go to find it, the adress is blank. What do I do ?

Your Mac won't have an IP address, at least not a valid IP, until you actually connect it to your home LAN. Not sure why you think you need the IP, you don't.
To connect to your home WiFi you need to know the SSID name, IE the name of your home WiFi, and the password for it. Once you have those two things click the little antenna looking icon on the right side of the menu bar and select your home WiFi name and click connect. A dialog box will pop up asking for the password, type in the password and click OK/Connect/Whatever.

Why do i need udev+udisks+udisks2+gvfs installed to dynamic mount?

hi there,
yes, i have used the search function on that, but still have unanswered questions.
1.
why do i need udev+udisks+udisks2+gvfs installed to dynamically mount internal (ntfs, ext4) partitions ?
If one these packages is missing, mounting an internal drive with "pcmanfm" is not possible.
I know how to static mount these drives via "fstab", but i want to mount them when i need the access.
2.
why are my removable devices not automatically mounted in "pcmanfm" when plugged in?
I have another OS (Lubuntu) running and this automatically recognizes when a cd is inserted or a usb stick is plugged in.
I have tried to install the package "gvfs-afc" and rebooted, still no usb stick to see. But when i enter:
sudo blkid -c /dev/null
The usb stick is listed as "sdb1"
I am using 64bit arch linux 3.9.3-1 with openbox+lxde.

jasonwryan wrote:
You don't. You need udev for a whole lot of other stuff, so leave that aside. To automount removable media, you can just use udisks and a helper like ud{iskie,evil}.
For an ntfs partition, you will also need that driver.
Comparing it with the Lubuntu; I am sure there is a lot more cruft preinstalled that makes this happen. In Arch, you just install what you need.
The udev page has the details.
so i have uninstalled the gvfs+udisks2 packages, rebooted and installed udevil-git and rebooted again.
No partition is shown in the filemanager now. I really dont get it. The udev wiki says udev needs rules but my "/etc/udev/rules.d" folder is empty.
The udisks wiki says that udisks and udisks2 are incompatible and that only one is needed and that udisks2 should be installed for gnome systems and udisks for xfce, but i have lxde installed. So it is not working with udisks and lxde (pcmanfm), when i try to install udisks2 additionally, it also does not work. Uninstalling udisks is also not possible because of the dependancy to libfm and so on...
Here is my /etc/udevil/udevil-user-harry.conf:
# udevil configuration file /etc/udevil/udevil.conf
# This file controls what devices, networks, and files users may mount and
# unmount via udevil (set suid).
# IMPORTANT: IT IS POSSIBLE TO CREATE SERIOUS SECURITY PROBLEMS IF THIS FILE
# IS MISCONFIGURED - EDIT WITH CARE
# Note: For greater control for specific users, including root, copy this
# file to /etc/udevil/udevil-user-USERNAME.conf replacing USERNAME with the
# desired username (eg /etc/udevil/udevil-user-jim.conf).
# Format:
# OPTION = VALUE[, VALUE, ...]
# DO NOT USE QUOTES except literally
# Lines beginning with # are ignored
# To log all uses of udevil, set log_file to a file path:
#log_file = /var/log/udevil.log
# Approximate number of days to retain log entries (0=forever, max=60):
log_keep_days = 10
# allowed_types determines what fstypes can be passed by a user to the u/mount
# program, what device filesystems may be un/mounted implicitly, and what
# network filesystems may be un/mounted.
# It may also include the 'file' keyword, indicating that the user is allowed
# to mount files (eg an ISO file). The $KNOWN_FILESYSTEMS variable may
# be included to include common local filesystems as well as those listed in
# /etc/filesystems and /proc/filesystems.
# allowed_types_USERNAME, if present, is used to override allowed_types for
# the specific user 'USERNAME'. For example, to allow user 'jim' to mount
# only vfat filesystems, add:
# allowed_types_jim = vfat
# Setting allowed_types = * does NOT allow all types, as this is a security
# risk, but does allow all recognized types.
# allowed_types = $KNOWN_FILESYSTEMS, file, cifs, smbfs, nfs, curlftpfs, ftpfs, sshfs, davfs, tmpfs, ramfs
allowed_types = $KNOWN_FILESYSTEMS, file, ntfs, vfat
# allowed_users is a list of users permitted to mount and unmount with udevil.
# Wildcards (* or ?) may be used in the usernames. To allow all users,
# specify "allowed_users=*". UIDs may be included using the form UID=1000.
# For example: allowed_users = carl, UID=1000, pre*
# Also note that permission to execute udevil may be limited to users belonging
# to the group that owns /usr/bin/udevil, such as 'plugdev' or 'storage',
# depending on installation.
# allowed_users_FSTYPE, if present, is used to override allowed_users when
# mounting or unmounting a specific fstype (eg nfs, ext3, file).
# Note that when mounting a file, fstype will always be 'file' regardless of
# the internal fstype of the file.
# For example, to allow only user 'bob' to mount nfs shares, add:
# allowed_users_nfs = bob
# The root user is NOT automatically allowed to use udevil in some cases unless
# listed here (except for unmounting anything or mounting fstab devices).
allowed_users = harry, root
# allowed_groups is a list of groups permitted to mount and unmount with
# udevil. The user MUST belong to at least one of these groups. Wildcards
# or GIDs may NOT be used in group names, but a single * may be used to allow
# all groups.
# Also note that permission to execute udevil may be limited to users belonging
# to the group that owns /usr/bin/udevil, such as 'plugdev' or 'storage',
# depending on installation.
# allowed_groups_FSTYPE, if present, is used to override allowed_groups when
# mounting or unmounting a specific fstype (eg nfs, ext3, file). For example,
# to allow only members of the 'network' group to mount smb and nfs shares,
# use both of these lines:
# allowed_groups_smbfs = network
# allowed_groups_nfs = network
# The root user is NOT automatically allowed to use udevil in some cases unless
# listed here (except for unmounting anything or mounting fstab devices).
allowed_groups = storage
# allowed_media_dirs specifies the media directories in which user mount points
# may be located. The first directory which exists and does not contain a
# wildcard will be used as the default media directory (normally /media or
# /run/media/$USER).
# The $USER variable, if included, will be replaced with the username of the
# user running udevil. Wildcards may also be used in any directory EXCEPT the
# default. Wildcards will not match a /
# allowed_media_dirs_FSTYPE, if present, is used to override allowed_media_dirs
# when mounting or unmounting a specific fstype (eg ext2, nfs). For example,
# to cause /media/network to be used as the default media directory for
# nfs and ftpfs mounts, use these two lines:
# allowed_media_dirs_nfs = /media/network, /media, /run/media/$USER
# allowed_media_dirs_ftpfs = /media/network, /media, /run/media/$USER
# NOTE: If you want only the user who mounted a device to have access to it
# and be allowed to unmount it, specify /run/media/$USER as the first
# allowed media directory.
# IMPORTANT: If an allowed file is mounted to a media directory, the user may
# be permitted to unmount its associated loop device even though internal.
# INCLUDING /MNT HERE IS NOT RECOMMENDED. ALL ALLOWED MEDIA DIRECTORIES
# SHOULD BE OWNED AND WRITABLE ONLY BY ROOT.
allowed_media_dirs = /media, /run/media/$USER
# allowed_devices is the first criteria for what block devices users may mount
# or unmount. If a device is not listed in allowed_devices, it cannot be
# un/mounted (unless in fstab). However, even if a device is listed, other
# factors may prevent its use. For example, access to system internal devices
# will be denied to normal users even if they are included in allowed_devices.
# allowed_devices_FSTYPE, if present, is used to override allowed_devices when
# mounting or unmounting a specific fstype (eg ext3, ntfs). For example, to
# prevent all block devices containing an ext4 filesystem from being
# un/mounted use:
# allowed_devices_ext4 =
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "allowed_devices=*" which allows any device. The recommended setting is
# allowed_devices = /dev/*
# WARNING: ALLOWING USERS TO MOUNT DEVICES OUTSIDE OF /dev CAN CAUSE SERIOUS
# SECURITY PROBLEMS. DO NOT ALLOW DEVICES IN /dev/shm
allowed_devices = /dev/*
# allowed_internal_devices causes udevil to treat any listed block devices as
# removable, thus allowing normal users to un/mount them (providing they are
# also listed in allowed_devices).
# allowed_internal_devices_FSTYPE, if present, is used to override
# allowed_internal_devices when mounting or unmounting a specific fstype
# (eg ext3, ntfs). For example, to allow block devices containing a vfat
# filesystem to be un/mounted even if they are system internal devices, use:
# allowed_internal_devices_vfat = /dev/sdb*
# Some removable esata drives look like internal drives to udevil. To avoid
# this problem, they can be treated as removable with this setting.
# WARNING: SETTING A SYSTEM DEVICE HERE CAN CAUSE SERIOUS SECURITY PROBLEMS.
# allowed_internal_devices =
# allowed_internal_uuids and allowed_internal_uuids_FSTYPE work similarly to
# allowed_internal_devices, except that UUIDs are specified instead of devices.
# For example, to allow un/mounting of an internal filesystem based on UUID:
# allowed_internal_uuids = cc0c4489-8def-1e5b-a304-ab87c3cb626c0
# WARNING: SETTING A SYSTEM DEVICE HERE CAN CAUSE SERIOUS SECURITY PROBLEMS.
# allowed_internal_uuids =
# forbidden_devices is used to prevent block devices from being un/mounted
# even if other settings would allow them (except devices in fstab).
# forbidden_devices_FSTYPE, if present, is used to override
# forbidden_devices when mounting or unmounting a specific fstype
# (eg ext3, ntfs). For example, to prevent device /dev/sdd1 from being
# mounted when it contains an ntfs filesystem, use:
# forbidden_devices_ntfs = /dev/sdd1
# NOTE: device node paths are canonicalized before being tested, so forbidding
# a link to a device will have no effect.
forbidden_devices =
# allowed_networks determines what hosts may be un/mounted by udevil users when
# using nfs, cifs, smbfs, curlftpfs, ftpfs, or sshfs. Hosts may be specified
# using a hostname (eg myserver.com) or IP address (192.168.1.100).
# Wildcards may be used in hostnames and IP addresses, but CIDR notation
# (192.168.1.0/16) is NOT supported. IP v6 is supported. For example:
# allowed_networks = 127.0.0.1, 192.168.1.*, 10.0.0.*, localmachine, *.okay.com
# Or, to prevent un/mounting of any network shares, set:
# allowed_networks =
# allowed_networks_FSTYPE, if present, is used to override allowed_networks
# when mounting or unmounting a specific network fstype (eg nfs, cifs, sshfs,
# curlftpfs). For example, to limit nfs and samba shares to only local
# networks, use these two lines:
# allowed_networks_nfs = 192.168.1.*, 10.0.0.*
# allowed_networks_cifs = 192.168.1.*, 10.0.0.*
allowed_networks = *
# forbidden_networks and forbidden_networks_FSTYPE are used to specify networks
# that are never allowed, even if other settings allow them (except fstab).
# NO REVERSE LOOKUP IS PERFORMED, so including bad.com will only have an effect
# if the user uses that hostname. IP lookup is always performed, so forbidding
# an IP address will also forbid all corresponding hostnames.
forbidden_networks =
# allowed_files is used to determine what files in what directories may be
# un/mounted. A user must also have read permission on a file to mount it.
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "allowed_files=*" which allows any file. For example, to allow only
# files in the /share directory to be mounted, use:
# allowed_files = /share/*
# NOTE: Specifying allowed_files_FSTYPE will NOT work because the fstype of
# files is always 'file'.
allowed_files = *
# forbidden_files is used to specify files that are never allowed, even if
# other settings allow them (except fstab). Specify a full path.
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "forbidden_files = *".
# NOTE: file paths are canonicalized before being tested, so forbidding
# a link to a file will have no effect.
forbidden_files =
# default_options specifies what options are always included when performing
# a mount, in addition to any options the user may specify.
# Note: When a device is present in /etc/fstab, and the user does not specify
# a mount point, the device is mounted with normal user permissions using
# the fstab entry, without these options.
# default_options_FSTYPE, if present, is used to override default_options
# when mounting a specific fstype (eg ext2, nfs).
# The variables $USER, $UID, and $GID are changed to the user's username, UID,
# and GID.
# FOR GOOD SECURITY, default_options SHOULD ALWAYS INCLUDE: nosuid,noexec,nodev
# WARNING: OPTIONS PRESENT OR MISSING CAN CAUSE SERIOUS SECURITY PROBLEMS.
default_options = nosuid, noexec, nodev, noatime
default_options_file = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, ro
# mount iso9660 with 'ro' to prevent mount read-only warning
default_options_iso9660 = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, ro, utf8
default_options_udf = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_vfat = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID, utf8
default_options_msdos = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID
default_options_umsdos = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID
default_options_ntfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, utf8
default_options_cifs = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_smbfs = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_sshfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, nonempty, allow_other
default_options_curlftpfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, nonempty, allow_other
default_options_ftpfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_davfs = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_tmpfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_ramfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
# allowed_options determines all options that a user may specify when mounting.
# All the options used in default_options above must be included here too, or
# they will be rejected. If the user attempts to use an option not included
# here, an error will result. Wildcards may be used.
# allowed_options_FSTYPE, if present, is used to override allowed_options
# when mounting a specific fstype (eg ext2, nfs).
# The variables $USER, $UID, and $GID are changed to the user's username, UID,
# and GID.
# If you want to forbid remounts, remove 'remount' from here.
# WARNING: OPTIONS HERE CAN CAUSE SERIOUS SECURITY PROBLEMS - CHOOSE CAREFULLY
allowed_options = nosuid, noexec, nodev, noatime, fmask=0022, dmask=0022, uid=$UID, gid=$GID, ro, rw, sync, flush, iocharset=*, utf8, remount
allowed_options_nfs = nosuid, noexec, nodev, noatime, ro, rw, sync, remount, port=*, rsize=*, wsize=*, hard, proto=*, timeo=*, retrans=*
allowed_options_cifs = nosuid, noexec, nodev, ro, rw, remount, port=*, user=*, username=*, pass=*, password=*, guest, domain=*, uid=$UID, gid=$GID, credentials=*
allowed_options_smbfs = nosuid, noexec, nodev, ro, rw, remount, port=*, user=*, username=*, pass=*, password=*, guest, domain=*, uid=$UID, gid=$GID, credentials=*
allowed_options_sshfs = nosuid, noexec, nodev, noatime, ro, rw, uid=$UID, gid=$GID, nonempty, allow_other, idmap=user, BatchMode=yes, port=*
allowed_options_curlftpfs = nosuid, noexec, nodev, noatime, ro, rw, uid=$UID, gid=$GID, nonempty, allow_other, user=*
allowed_options_ftpfs = nosuid, noexec, nodev, noatime, ro, rw, port=*, user=*, pass=*, ip=*, root=*, uid=$UID, gid=$GID
# mount_point_mode, if present and set to a non-empty value, will cause udevil
# to set the mode (permissions) on the moint point after mounting If not
# specified or if left empty, the mode is not changed. Mode must be octal
# starting with a zero (0755).
# mount_point_mode_FSTYPE, if present, is used to override mount_point_mode
# when mounting a specific fstype (eg ext2, nfs).
# NOT SETTING A MODE CAN HAVE SECURITY IMPLICATIONS FOR SOME FSTYPES
mount_point_mode = 0755
# don't set a mode for some types:
mount_point_mode_sshfs =
mount_point_mode_curlftpfs =
mount_point_mode_ftpfs =
# Use the settings below to change the default locations of programs used by
# udevil, or (advanced topic) to redirect commands to your scripts.
# When substituting scripts, make sure they are root-owned and accept the
# options used by udevil (for example, the mount_program must accept --fake,
# -o, -v, and other options valid to mount.)
# Be sure to specify the full path and include NO OPTIONS or other arguments.
# These programs may also be specified as configure options when building
# udevil.
# THESE PROGRAMS ARE RUN AS ROOT
# mount_program = /bin/mount
# umount_program = /bin/umount
# losetup_program = /sbin/losetup
# setfacl_program = /usr/bin/setfacl
# validate_exec specifies a program or script which provides additional
# validation of a mount or unmount command, beyond the checks performed by
# udevil. The program is run as a normal user (if root runs udevil,
# validate_exec will NOT be run). The program is NOT run if the user is
# mounting a device without root priviledges (a device in fstab).
# The program is passed the username, a printable description of what is
# happening, and the entire udevil command line as the first three arguments.
# The program must return an exit status of 0 to allow the mount or unmount
# to proceed. If it returns non-zero, the user will be denied permission.
# For example, validate_exec might specify a script which notifies you
# of the command being run, or performs additional steps to authenticate the
# user.
# Specify a full path to the program, with NO options or arguments.
# validate_exec =
# validate_rootexec works similarly to validate_exec, except that the program
# is run as root. validate_rootexec will also be run if the root user runs
# udevil. If both validate_exec and validate_rootexec are specified,
# validate_rootexec will run first, followed by validate_exec.
# The program must return an exit status of 0 to allow the mount or unmount
# to proceed. If it returns non-zero, the user will be denied permission.
# Unless you are familiar with writing root scripts, it is recommended that
# rootexec settings NOT be used, as it is easy to inadvertently open exploits.
# THIS PROGRAM IS ALWAYS RUN AS ROOT, even if the user running udevil is not.
# validate_rootexec =
# success_exec is run after a successful mount, remount, or unmount. The
# program is run as a normal user (if root runs udevil, success_exec
# will NOT be run).
# The program is passed the username, a printable description of what action
# was taken, and the entire udevil command line as the first three arguments.
# The program's exit status is ignored.
# For example, success_exec might run a script which informs you of what action
# was taken, and might perform further actions.
# Specify a full path to the program, with NO options or arguments.
# success_exec =
# success_rootexec works similarly to success_exec, except that the program is
# run as root. success_rootexec will also be run if the root user runs udevil.
# If both success_exec and success_rootexec are specified, success_rootexec
# will run first, followed by success_exec.
# Unless you are familiar with writing root scripts, it is recommended that
# rootexec settings NOT be used, as it is easy to inadvertently open exploits.
# THIS PROGRAM IS ALWAYS RUN AS ROOT, even if the user running udevil is not.
# success_rootexec =
I have no idea what to do next, the only way it works, is the combination i mentioned in the title of this post. Any suggestion to solve that problem?

Why do we need to soft proof?

So it occurred to me that when LR soft proofs an image it "knows" how to represent my original image as though it it is printed. My job then is to get the "Proof image" to look like the original image by tweaking the sliders etc.
But here's the thing, LR "knows" all of the colours of my original image and the way I want them represented. It then changes the image to represent how it will be printed, so it "knows" the effect the profile will have. So why do I need to fiddle with sliders etc when LR has the knowledge to do the tweaking to get the colours via the profile, back to the original?
Surely the experts could program a function that when I click a button automatically it changes the settings in the proof copy to match as close as possible the original? I can then make choices from there.
Any thoughts?
Peter

You can assing one there, and / or on dialer interfaces. It depends on what you are doing.
These will be the address used by PPP when it runs on the B-channels.

Why do I need a TITLE to create an account?

Why, why, why do I need a title to create an account with a billing address? Is this really industry-standard encryption? BS on that! I never needed a title to obtain the credit card in the first place. This isn't security, it is mindlessness. I don't need a title in any aspect of my life, nor do I use one. I'm sure this sort of namby pamby bureaucratic inanity of being name police must have Steve spinning in his grave. My apologies, I meant Mr. Jobs. Get with the 21st century Apple, I mean a title, come on! Oh, and the choices are: Mr., Mrs., Ms., and Dr.. I guess Sir Paul McCartney can't use iTunes. If I used some title I'd be signing in as my parents and, God rest their souls, they are unable to provide me their credit card anymore (they never liked my music anyway). Hey Apple, I've got the money to spend baby, what concern is it of yours what I am called.

Have you created an iCloud account? This is not the account or ID you use for iTunes. And where exactly are you turning on notes? In what area within settings of your devices?

Why do we need to distributed computing?

Hi all,
Why do we need distribute objects and what are the major advantages that this approach offer us?
Thanks.

Look up on the web; the 10 misconceptions of distributed programming; I haven't got time to find it in my data now. But it still fails to mention this one and only utterly important question; how many CPU cycles must a process miss before it becomes affordable to sacrifice even more CPU cycles to set up a TCP/IP connection to marshall every aspect of your call, send it to the other side and process the response in the reverse order ? Answer: a whole lot of CPU cycles. If the time it took to process the thing locally is smaller than the time it takes to set up the whole thing to work accross a network, then forget about it completely. You can't beat it. Not to mention that if your front-end is so busy that it needs a back-end to do some things, then the bandwidth it's going to need is usually so big, that the boxes should normally not be more than a slight distance apart, so there goes the argument for using it to address specialized services (which are usually not around the corner).

Why do we need to assign ip for the D channel ISDN-PRI

Why do we need to assign ip address to the D channel (signaling ) when we configure ISDN-PRI in the example below :
http://www.cisco.com/univercd/cc/td/doc/product/access/ap/ap_ts3/ap_ts3sw/apswisd.htm
<quote>
Step 1:Specify the D channel of the first Primary Rate Interface (PRI):
AS01(config)# interface Serial 0:23
AS01(config-if)#
Step 2: Assign an IP address and subnet mask to the interface:
AS01(config-if)# ip address 172.16.254.253
</quote>
Regards

You can assing one there, and / or on dialer interfaces. It depends on what you are doing.
These will be the address used by PPP when it runs on the B-channels.

Service Registry: why do i need two bindings (wsdlDeployment and endPoint)

based on the technical note of Clemens Utschig "Enabling a Dynamic, Reusable SOA with Oracle BPEL Process Manager and Oracle Service Registry" i have one question:
why do i need two bindings (wsdlDeployment and endPoint) in my service in the service registry. if i only define the wsdlDeployment if get this messages:
<2006-12-07 09:39:02,559> <FATAL> <default.collaxa.cube.ws> no endpoint found - nothing to adjust
<2006-12-07 09:39:02,559> <WARN> <default.collaxa.cube.ws> Could not lookup base endpoint!
the problem of defining two bindings is that the url to my partner is redundant.

Hi Clemens,
The UDDI Version 3.0.2 Specification (http://www.uddi.org/pubs/uddi_v3.htm) say this:
B.1.2 Using the "wsdlDeployment" value
Instead of directly providing the network address in the accessPoint, it is occasionally useful or necessary to provide this information through indirect means. One common scenario for such a behavior is when the accessPoint is embedded within a WSDL file. In such a scenario, the UDDI accessPoint contains the address of the WSDL file, and the client then must retrieve the WSDL file and extract the end point address from the WSDL file itself.
In this case, decorating the UDDI accessPoint with a useType="wsdlDeployment" is appropriate. A sample of such behavior is as follows:
<bindingTemplate bindingKey="uddi:example.org:catalog">
   <description xml:lang="en">
       Browse catalog Web service
   </description>
   <accessPoint useType="wsdlDeployment">
       http://www.example.org/CatalogWebService/catalog.wsdl
   </accessPoint>
   <categoryBag>
       <keyedReference keyName="uddi-org:types:wsdl"
       keyValue="wsdlDeployment"
       tModelKey="uddi:uddi.org:categorization:types"/>
   </categoryBag>
</bindingTemplate>In the example above, a client would be able to parse the result of the bindingTemplate and determine the end point of the Web service within the WSDL file discovered in the accessPoint element. Note that the bindingTemplate has also been categorized with the "wsdlDeployment" value from the uddi.org:categorization:types scheme so that it can be discovered through a find_binding API call.
1) This means for me that providing one binding with useType=wsdlDeployment should be enough.
2) Sadly the "Business Service Control" of the Service Registry (Publish new WSDL service) does not create the correct structure needed by the bpel-engine. The "Publish new WSDL service" wizard just creates one service with one binding with useType=other (http). So if i want to reuse this published service from bpel (as a service consumer) i have to switch to the "Service Registry Admin Control" and create a second binding with useType=wsdlDeployment. But i don't want the developers to get inside the "Service Registry Admin Control"! They should only work with the "Business Service Control".
All this makes the usage of the service-registry very unhandy and reduce the acceptance for developers because of unnecessary manual steps and broken security principles.
My wish for this issue is that the "Publish new WSDL service" inside the "Business Service Control" of the Service Registry would additionlly create this needed binding with useType=wsdlDeployment.
Best Regards,
Harald Reinmueller

Why do i need outlook 2007 or 2010 for i cloud

why do i need outlook 2007 for i cloud i dont understand.

iCloud will still work for free, i.e sync your contacts between ios devices and the cloud (icloud.com) but for the calendar and addresses to sync with a windows PC you will need outlook 2007+.
However as you dont use that part at the moment i'm sesning no great loss - icloud bookmarks and photo stream will sync with a windows pc without outlook so the rest of icloud will still work for you for free

Why do i need a us address

Similar Messages

Maybe you are looking for