Error Making Symbolic Link
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of error making symbolic link read-only file system this site About Us Learn more about Stack Overflow the company Business
Creating Symbolic Link Protocol Error
Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask making a symbolic link mac Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign
Making A Symbolic Link Windows
up creating symbolic link: Protocol error up vote 9 down vote favorite I have created linux (Centos) on my virtual box. When I ssh to it and I try to create symbolic link (on my shared folder with full access): ln -s path/folder/example myFolder I get error: ln: creating symbolic link `myFolder': Protocol error Is there any reason or solution to this? linux making a symbolic link in linux symlink share|improve this question asked Jul 27 '13 at 7:11 TroodoN-Mike 5,69863556 add a comment| 3 Answers 3 active oldest votes up vote 5 down vote accepted It's a problem with the host filesystem. Check the permissions on the host folder are adequate and the the host filesystem supports symlinks. share|improve this answer answered Jul 27 '13 at 7:20 Paul Dixon 185k33248302 The host system is windows 7. Is there any solution to enable it? –TroodoN-Mike Jul 27 '13 at 7:29 3 Bad solution for this is to create symlinks in windows 7 by using mklink. Example: mklink /D myFolder path/folder/example –TroodoN-Mike Jul 27 '13 at 7:59 from which API/layer does the Protocol error message come from here? –n611x007 Apr 16 '15 at 13:28 add a comment| up vote 6 down vote Right click on your command prompt and "Run as Administrator" (or whatever program you're using to make those symlinks needs to be run as adminstrator). share|improve this answer answered Oct 24 '13 at 19:37 Angela Zenner 7712 This is for a Linux system, meaning no "Command Prompt." –Sign
Opened 13 months ago Last modified 12 months ago Symbolic links with `..` result in `protocol error` on vboxsf + 5.0.4 Reported by: scoates Owned by: Priority: major Component:
Creating Symbolic Link Unix
shared folders Version: VirtualBox 5.0.4 Keywords: Cc: sean@… Guest type:
Creating Symbolic Link Ubuntu
Linux Host type: Mac OS X Description When creating a symlink that contains .., we're seeing creating symbolic link file exists "protocol error" messages. For this example /vagrant is none on /vagrant type vboxsf (rw,nodev,relatime). cd /vagrant ; mkdir test ; cd test ; ln -s ../Vagrantfile . http://stackoverflow.com/questions/17895256/creating-symbolic-link-protocol-error ln: failed to create symbolic link `./Vagrantfile': Protocol error This also happens when linking .. and not into the root. It does not happen when linking .. outside of the vboxsf system. This happens for us on 5.0.4r102546 but not on 5.0.0r101573. It may be related to the following: https://www.virtualbox.org/ticket/14463 https://www.virtualbox.org/ticket/14153 Note: if the https://www.virtualbox.org/ticket/14563 symlink is made on the host FS (and not created on the VM), it seems to behave normally/correctly. Host for our tests is Mac OS X 10.10, guest is Debian Jessie. Change History comment:1 Changed 13 months ago by scoates Also worth noting: I can successfully create symlinks on the vboxsf filesystem that do not contain .. comment:2 Changed 13 months ago by cama900 Just wanted to add my voice to this. Took me hours to figure out the problem because it occurred by trying to run npm install, not just making symlinks comment:3 Changed 13 months ago by scoates FWIW, mine happened when doing an automated-at-provisioning git checkout (which happened to contain ../ symlinks). comment:4 follow-up: ↓ 5 Changed 13 months ago by sunlover Fixed in https://www.virtualbox.org/download/testcase/VirtualBox-5.0.5-102721-OSX.dmg Please test whether this build it works for you. Thanks. comment:5 in reply to: ↑ 4 Changed 13 months ago by frastel Replying to sunlover: Fixed in https://www.virtualbox.org/download/testcase/VirtualBox-5.0.5-102721-OSX.dmg Please test whether this b
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring http://askubuntu.com/questions/599516/symbolic-links-error-while-creating-ubuntu-uefi-bootable-usb developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how http://unix.stackexchange.com/questions/197642/getting-protocol-error-when-trying-to-create-a-symlink-in-docker it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Symbolic links error while creating Ubuntu UEFI bootable USB up vote 1 down vote favorite I have tried to symbolic link create UEFI bootable USB drive within Ubuntu 14.10 (Startup disk creator didn't help nor I am interested in using it.). I have formated USB with FAT32 and GPT. So the only thing left to do would be just to copy all files from ISO to USB. That method worked when it comes to Linux Mint 17.1 and Clonezilla live CD, but when I tried to create bootable USB for Ubuntu 14.04 or Kubuntu 15.04 beta 1 there was an error copying creating symbolic link files. Actually, on several occasions (4 or 5) pop-up window appeared. After ignoring this errors, both Ubuntu and Kubuntu USB boot-up just fine, with no apparent problems in Live mode. Can someone please elaborate what this symbolic links presents? Will this cause some problem when OS is installed? boot usb uefi share|improve this question asked Mar 21 '15 at 12:46 VRR 730416 We're sorry, but this site is all about Ubuntu and its official derivatives as posted on wiki.ubuntu.com/Releases so Mint is off-topic here as well. –Fabby Mar 24 '15 at 23:15 I couldn't agree more. It was mentioned so people can get a better insight of the problem, since it is based on Ubuntu. –VRR Mar 26 '15 at 14:35 I understand, but the question and answer will still be closed as off-topic as it is off-topic... –Fabby Mar 26 '15 at 19:09 I got an error trying to create a bootable Ubuntu USB from Ubuntu. How's that off-topic? How acn people use Ubuntu if they cannot install it? –VRR Mar 26 '15 at 19:17 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote You can find symbolic links with the -type l option to find. I don't happen to have a 15.04 beta CD image handy, but I do have a 14.10 image, and I ran the command against it: $ find /mnt/cdrom -type l /mnt/cdrom/dists/stab
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Getting “Protocol Error” when trying to create a symlink in Docker up vote 3 down vote favorite I'm trying to setup a symlink, using the command ln -s /var/www/data/cache/widget/overlay/ /var/www/public_html/images/overlay but it outputs ln: failed to create symbolic link '/var/www/public_html/images/overlay': Protocol error The host OS is Windows 8, and the Docker image is Ubuntu. I believe the issue could be something to do with permissions, as when the Docker image is started, /var/www/public_html is mapped to a folder inside Windows 8, /C/Users/Username/Documents/development/public_html. However, I can create folders, and files via command line inside the public_html folder, which kind of goes against it being permissions. I also can't find anyway to start Docker as admin to see if that helps, as it's just a .sh script that runs. Has anybody else had the "Protocol error" when creating symlinks? Or any idea how I could get more information about what causes this issue? EDIT: Also, if I try to save an image via PHP to the public_html folder or copy a file there (again, via PHP), that gives the same "Protocol error" message. ubuntu windows symlink virtual-machine docker share|improve this question edited Apr 22 '15 at 2:51 Scott 3,78421328 asked Apr 21 '15 at 14:44 Tom Hart 19019 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted So /var/www/public_html is actually as Windows folder, but /var/www/data is not? You're trying to create a symbolic link from a Windows directory into a Ubuntu directory in a virtual machine. There's no way that Windows can support an object like that. share|improve this answer answered Apr 22 '15 at 2:58 Scott 3,78421328 Yea