Why do callers need to install "whistle"?

I cannot reproduce this myself.  But I have an online number from Skype, and I've verified that it works at least from my land line: when I run Skype on my Android phone, and dial my online number from my land line, I hear a ringing sound from the land line (just as if I'd called any other number), and my Android phone vibrates and displays a Skype screen that tells me that there's an incoming call.  This is all exactly what I'd expect.
However, the one other person who has ever tried to call my Skype number says that he doesn't hear a ringing sound, but instead gets a recorded voice telling him that he needs to install something called "Whistle" on his computer.  This makes no sense to me, as his phone isn't connected to his computer in any way that I know of.
Can anyone explain this?

Which version of Java do you already have installed?
Java 1.6.0_12 or higher?

Similar Messages

  • Why do we need to install java during sap installation

    why do we install Java during SAP installation?

    Hello Satish,
    Sapinst tool requires JRE for the running and as JRE cannot be integrated to sapinst due to licensing issues we need to install seprately java before sap installation.
    Hope this clarifies your query.
    Thansk and Regards,
    -Bijesh.

  • Why do I need to install RSAT on Windows 8.1 for accessing Hyper-V Server 2012 R2?

    Since Windows 8.1 has Hyper-V Platform and Hyper-V Manager built in to it, if I just enable the Hyper-V Manager on my Windows 8.1 client machine I should be able to access the standalone Hyper-V Server 2012 R2 (which I'm planning to install on my 2nd machine)
    right?  
    Then why every article I found on this suggests to install RSAT on my client machine?

    Hi Nero,
    RSAT is used for these server/client can not enable hyper-v role  to manage the corresponding hyper-v server .
    Please refer to following supported OS list of
    client hyper-v :
    Windows 8 Pro 64-bit Edition
    Windows 8 Enterprise 64-bit Edition
    Windows 8.1 Pro 64-bit Edition
    Windows 8.1 Enterprise 64-bit Edition
    Best Regards
    Elton JI
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Why do I need to install Office a second time?

    I have a Mac 27' and its great! I love it lol but I have a little problem. I've installed Microsoft office 365 on my computer and my brother made another account for the house to keep separate from his account. When I go to the house account I have to "re-install' Office even though i have already installed it the first time.. I'm just wondering why i have to installed it again after i have already installed it the first time.

    Ask Microsoft. Their requirement, not Apple's.
    Microsoft Support

  • Why did I need to install Google Crome

    Because I wanted a modern browser on Windows Server 2008. Microsoft will only allow IE 9 and that browser will not display modern web sites.
    I just don't understand why ... what is the thinking process at Microsoft.
    Let me say it again. I HAD to install Crome.

    See if anything here helps,
    Tweaks for Internet explorer
    Post a link t the site where you had issues,
    I can't say If ever had an issue with any websites ?
    Cheers.

  • Why do I need to install Lion again?

    This is an odd one.. I have tried to search the support communities to see if anyone else is having the same problem but cant find it so this could be an isolated case... Anyway....
    I have just updated my Lion OSX to the latest version 10.7.3 through the Mac app store - while it was downloading and to kill a bit of time while it was downloading  I clicked onto the 'Purchased' tab to have a browse at my previous purchases and noticed that it was asking me to download the full version of Lion again!!.. The 4GB version... Has anyone else noticed this in their purchase tab? - I have checked the other Macs I have in case it was just the machine I was working on but all of them are saying the something. Appreciate your comments back before I download it again... Maybe its just a glitch in the app store but wanted to check if anyone else has had the same message. Thanks.

    UPDATE... Gone onto the mac store today and now in the purchase tab Lion has been removed so looks like I have not even purchased it... I did a search for it in the store and instead of saying "Installed" - its giving me the selling price... Just like it does when you first purchase the software!!
    What's going on?... HELP!!!

  • HT3669 I only have a HP printer and why I need to install a file for all the HP printers drivers 590MB??? if normally the size of my file should be 5MB.  some one could me help to avoid installation of 590MB for my new mountain lion software???

    Hi guys..!!
    I would like to know if someone could help on this:
    I just have a HP printer (HP Designjet 100) and for some reason I need to install a file for all the HP printers drivers in total 590MB to be able to use my printer in my mountain lion???
    If normally the size of my files in the for previous software was more or less 5MB why now i need to install 590?
    Some one could help me how to avoid installation of 590MB for my new mountain lion software???
    Thanks

    If you go to http://support.apple.com/downloads and locate the HP Printer Drivers installer, you will find that it is 473.4 MB (for version 2.11). If you install this, it will install the full set of drivers for every model of HP printer that is supported by the drivers distributed through Apple. The disk space occupied once installed will probably be larger than the download, since the downloaded file is compressed.
    On the other hand, if you have an HP printer connected and you use Software Update (or the Update tab in App Store), that should offer you a much smaller set of HP drivers, which are only applicable to your printer (and possibly a few similar ones). These updates are typically only tens of megabytes rather than hundreds of megabytes.
    If Software Update doesn't offer you any HP drivers then it either thinks you have the latest drivers installed already, or the printer model is not supported by the drivers available from Apple.
    This article lists all of the printer models for which Apple distributes the driver:
    http://support.apple.com/kb/HT3669

  • HT4718 i need to install a fresh copy of OS X onto my macbook pro 13. i did erase the old partition "macintosh hd" & now when i am trying to create a new partition, it shows "partition failed..couldnt unmount disk"...pls help !!

    i need to install a fresh copy of OS X onto my macbook pro 13. i did erase the old partition "macintosh hd" & now when i am trying to create a new partition, it shows "partition failed..couldnt unmount disk"...pls help !!

    First of all, I have to ask, why to you "need" to install a fresh copy of OSX?
    This may mean that your hard drive is failing, so hopefully you have a backup.
    I'm assuming you were in your recovery partition when you did this.
    I would, from the recovery partition, repair your hard drive and permissions.
    When to Run First Aid in Mountain Lion's Disk Utility - For Dummies
    And then try to create the partition again.
    If that doesn't work, you have a few options:
    Try a third party utility like DiskWarrior or TechTool which may be able to repair your hard drive:
    DiskWarrior 4 - The Disk Utility for Mac Disk Repair, Mac Directory Repair, Mac Disk Recovery, Mac Data Recovery or Techtool Pro 7
    Try internet recovery, perhaps erase the entire hard drive and reinstall ML.
    If nothing else works, then I'd replace the HD and start over.

  • New iTunes & need for Safari Update, why do I need Safari!?

    I absolutely HATE Safari, why do we need to install the latest version to be able to get into iTunes, or have it at all? This is why I do not trust updates "if it ain't broke don't fix it".
    Seriously thinking of going elsewhere for my music needs and I have been loyal to the iTunes store since day one.

    Thanks, just do not even want it taking up space on my computer. Took FOREVER to install in South America. Was not even worth it New iTunes user unfriendly.

  • Why do I need consolekit or dbus?

    I currently run DWM as my window manager, and the last line of my .xinitrc is:
    exec ~/scripts/startdwm
    I see a lot of others have something to the effect of:
    exec ck-launch-session dbus-launch --sh-syntax --exit-with-session ~/.bin/startdwm
    What is the purpose of this?  What am I missing out on by not starting with consolekit or dbus?  What is the best practice?

    jasonwryan wrote:There are wiki pages on both of these: please research topics before asking questions here:
    I did some research before coming here. My initial post was not very descriptive, and for that I apologize.  Let me try to explain myself better.
    In the quest to learn more about the dark corners of my Arch Linux machine, I'm picking out components and learning more about them. Currently in the hot-seat are dbus & consolekit.  I'll break down my experience so far with each of them separately, [hopefully] for the benefit of clarity.
    dbus
    As do most archers, I started out with the Beginner's guide. Here is what it says about dbus:
    Arch Wiki wrote:Note: dbus is likely required for many of your applications to work properly, if you know you do not need it, skip this section
    In other words, "just install dbus 'cause you probably need it".  I had no idea whether or not I needed it, so I just installed it, as was recommended. However, I'd like to note that this seems to deviate with The Arch Way. The arch way stresses simplicity and code correctness over convenience, so to ask the user to install something without explaining why seems out of place. The more typical approach throughout the wiki is to explain why, like "install mesa for 3D support" or "install alsa-mixer to control sound".
    Next, looking at the dbus Arch Wiki entry, it's clear that dbus is a system for easy inter-process communication, but I still have no idea why almost everyone needs to install it.  Won't apps requiring dbus for IPC have dependencies on dbus, and then install and use dbus like any other dependency? If not, don't I need to know what common applications use dbus, as well as how and why they do so?  This is where my confusion lies. 
    ConsoleKit
    The Arch Wiki ConsoleKit entry explains:
    Arch Wiki wrote:ConsoleKit is a framework for managing user sessions, and permissions.
    What is not done already that ConsoleKit solves with its session management?  What does ConsoleKit do with permissions that isn't handled by either the Linux kernel or sudo/su/chmod/etc...?
    The ConsoleKit Official documentation comically avoids answering this:
    ConsoleKit Documentation wrote:
    Defining the Problem
    To be written.
    The Arch Wiki ConsoleKit entry further explains:
    Arch Wiki wrote:Some of the most common usages of ConsoleKit is allowing non-root users to mount removable media, and suspending/shutting down the computer through common desktop applications (ie: thunar, nautilus, the gnome shutdown menu, etc).
    Why is this better than just using sudo for mounting media and shutting down / restarting?  If I can do some cool stuff with ConsoleKit managing my X sessions, sign me up, but tell me what I can do & where to start. 
    If there is nothing new that ConsoleKit does, and some apps just arbitrarily decided to use it as opposed to more common components for certain functionality, then how do I know that before using those apps? If it's just guess and check that's fine, but I feel like I'm missing something here.
    Also, is there a best-practice way to launch several apps under consoleKit, as opposed to this "dirty workaround":
    Arch Wiki wrote:A dirty workaround is to have the entire session started by a second script (don't forget dbus-launch, it's likely you need it too).
    And again with the "you probably need dbus" without explaining why. 
    My poorly-thought out original post begged to be dismissed with a "google it". Hopefully I have better explained myself, and someone can point me in the right direction.  If I've just stupidly missed something basic (most likely the case, I'm somewhat new to all of this), have mercy on me and kindly point me in the right direction.
    Thanks!

  • Do I need to install J2EE 1.4 SDK if I already have J2SE 1.5.0_08 SDK?

    Currently my system installed J2SE 1.5.0_08 SDK and Java Studio Enterprise 8. My OS is Windows XP Professional Edition.
    I want to start to learn J2EE. I read the software requirement in the J2EE tutorial and it asked me to install J2EE 1.4 SDK package which contains System Application Server Platform Edition 8.2 and J2SE SDK.
    Refer to : http://java.sun.com/j2ee/1.4/docs/tutorial/doc/
    Its quite confusing me. The question is:
    1) Do i need to install the J2EE 1.4 SDK cause I already installed J2SE SDK?
    2) I have Java Studio Enterprise 8, do i still need to install the System Application Server Platform Edition 8.2? Because i saw inside my Java Studio Enterprise 8 its contain the function to start and stop default application server. Can this be consider as the Java Application Server too?

    no i guess, since if u can start the server, why do u need to install j2ee sdk, one more thing, be carefull about the versions
    u can check the version by going to the command prompt and type
    java -version
    there it shows the version of the jvm u r using, but see that u set the java home to point to the same version even if u have different jdk's installed on the same machine
    i am not sure what other thing this j2eesdk gives besides normal things which comes with sun studio, u can always try it if u want to but be careful about the JAVA_HOME settings

  • I'm about to install snow leopard on my 2006 macbook, OSX 10.4.11. I read that I'm supposed to copy my old OS to an external drive before hand. Why is this? What does it accomplish? If I upgrade to 10.6.3, why do I need a copy of my old 10.4.11?

    I'm about to install snow leopard onto my 2006 macbook with OSX 10.4.11. I read that I should copy my old OSX to an external drive before I start. Why? What is the purpose of this? Once I have snow leopard, why do I want a copy of 10.4.11? Won't I be able to import what I need while installing?   Also, what is the point of partitioning my disk?  I don't understand what that's for if I'm only going to run one OS on there. Any experience or advice is greatly appreciated.

    It is always wise to have a copy of your latest working system ... preferably on an external drive.   As Neil says, you may run into trouble and if you do you can always return to the original situation and start again.
    Once you have installed Snow Leopard (an excellent system if I might say so) then you probably won't need 10.4.11 though you can never have enough back ups in my opinion.   It's amazing how often a need arises.
    Having a backup on an external drive allays the need to partion your hard iMac drive for the same purpose..

  • 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 I need a second java.exe when I alreayd have another in a JDK instal

    When I install JDK then there are two instances of java.exe
    (and other programs like javaws.exe). One instance in
    INSTALL_DIR\bin\
    and the other in
    INSTALL_DIR\jre\bin\
    So why do I need two exes instead of one?
    Peter

    Hello!
    So why do I need two exes instead of one?Don't know the reason myself, ask the developers..........
    One instance in INSTALL_DIR\bin\
    and the other in
    INSTALL_DIR\jre\bin\Yes, checked that, you are right.
    But , whats the problem, It hardly takes 2MB more space.
    Or, were you implying that ideally java.exe and javaws.exe should not be in "INSTALL_DIR\bin\" as they are involved in running the java programs.
    Thanks!

  • If RuneScape uses Java 3D why don't you need to install it?

    I was just wondering if RuneScape uses Java 3D, why doesn't anyone need to install it? Is it because the game is intirely server side and all the graphics and stuff is done over on their servers and not on your own computer? Thanks.

    Most likely, you have a web plugin that depends on the Java runtime distributed by Apple, such as the Facebook video calling plugin or the "NexDef" plugin for watching baseball streams. If you no longer need the plugin, remove it, including its automatic update mechanism (if any) according to the developer's instructions. Otherwise, install Java.

Maybe you are looking for