symlink

Following on from a previous question , I am creating a symbolic link on a Server 2008 from a Vista machine using UNC paths. I can create the link just fine. I can go to the Server 2008 box and double click on the link in explorer to open the target file. What I cannot do though is use FileCreateW to get a handle to the UNC path link (from the Vista box). When I try it, it fails and GetLastError() returns error code 1463 (0x5B7), which is: The symbolic link cannot be followed because its type is disabled. How to enable its "type" in Server 2008 (assuming the error means what it says)?

I'm trying to check if a symlink exists in bash. Here's what I've tried. mda=/usr/mda if [ ! -L $mda ]; then echo "=> File doesn't exist" fi mda='/usr/mda' if [ ! -L $mda ]; then echo "=> File doesn't exist" fi However, that doesn't work. If '!' is left out, it never triggers. And if '!' is there, it triggers every time. drysdam -L returns true if the "file" exists and is a symbolic link (the linked file may or may not exist). You want -f (returns true if file exists and is a regular file) or maybe just -e (returns true if file exists regardless of type). According to the GNU manpage , -h is

I have a symlink to an important directory. I want to get rid of that symlink, while keeping the directory behind it. I tried rm and get back rm: cannot remove 'foo' . I tried rmdir and got back rmdir: failed to remove 'foo': Directory not empty I then progressed through rm -f , rm -rf and sudo rm -rf Then I went to find my back-ups. Is there a way to get rid of the symlink with out throwing away the baby with the bathwater? # this works rm foo # versus rm foo/ Basically, you need to tell it to delete a file, not delete a directory. I believe the difference between rm and rmdir exists because

Windows 6 (Vista and Server 2008) support proper symbolic links, which can be created via the CreateSymbolicLink function. But there doesn't appear to be a corresponding function for interrogating a symbolic link to obtain the path of the link's target. I have found out that symbolic links are an implementation of reparse points, and so the reparse point functions can be used to obtain the target path. But the header files that I need to use reparse points appear to come with the Windows Driver Kit . Setting up this kit with VS2008 appears to be a non trivial task. Is there a nice simple

In PowerShell, I need resolve the target path of a junction (symlink). for example, say I have a junction c:\someJunction whose target is c:\temp\target I tried variations of $junc = Get-Item c:\someJunction , but was only able to get c:\someJunction How do I find the target path of the junction, in this example c:\temp\target , of a given junction? Josh You can get the path by doing the following: Get-ChildItem -Path C:\someJunction Edit for finding the path and not the contents of the folder Add-Type -MemberDefinition @" private const int FILE_SHARE_READ = 1; private const int FILE_SHARE

When I try to symlink a binary in my /usr/bin folder, I get an Operation not permitted error: sudo ln -s /usr/bin/python2.7 /usr/bin/python2 ln: /usr/bin/python2: Operation not permitted Even as sudo, I get this error. Gordon Davisson Why can't I symlink into /usr/bin ? El Capitan's new System Integrity Protection feature prevents changes to several core parts of OS X, including most of /usr/ , even by root. How can I still add executable files to my path? Local customizations, such as what you're doing, belong in /usr/local instead. The path /usr/local/bin doesn't exist by default, but you

Is there a single way of detecting if a directory/file/symlink/etc. entity (more generalized) exists? I need a single function because I need to check an array of paths that could be directories, files or symlinks. I know File.exists?"file_path" works for directories and files but not for symlinks (which is File.symlink?"symlink_path" ). The standard File module has the usual file tests available: RUBY_VERSION # => "1.9.2" bashrc = ENV['HOME'] + '/.bashrc' File.exist?(bashrc) # => true File.file?(bashrc) # => true File.directory?(bashrc) # => false You should be able to find what you want