Is possible to create a symlink for a remote file?
I'm developing an application that reads from /dev/ttyusb0 on remote raspberry. Is possible to create a symlink to the remote device (raspy) on my local development machine?
Thanks!
linux
add a comment |
I'm developing an application that reads from /dev/ttyusb0 on remote raspberry. Is possible to create a symlink to the remote device (raspy) on my local development machine?
Thanks!
linux
add a comment |
I'm developing an application that reads from /dev/ttyusb0 on remote raspberry. Is possible to create a symlink to the remote device (raspy) on my local development machine?
Thanks!
linux
I'm developing an application that reads from /dev/ttyusb0 on remote raspberry. Is possible to create a symlink to the remote device (raspy) on my local development machine?
Thanks!
linux
linux
asked Jan 19 at 18:12
Luigi CanditaLuigi Candita
1033
1033
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
No.
Symlinks only point to a path – the symlink resolution process essentially just replaces a part of the original name. For example, if you had a path /home/mario/docs/notes.txt
and docs
was a symlink to ../luigi/documents
, the process would give you /home/mario/../luigi/documents/notes.txt
.
Therefore you can only create symlinks for something that already has a local path. (For regular files this could be a path provided by a network filesystem such as NFS/SMB/AFS/9p, but devices usually cannot be exported this way.)
If your program only reads & writes data but doesn't use any parameters specific to serial ports (flow control, etc.) then you could create an adhoc tunnel using socat
or ser2net
on the remote device to link its serial port to a TCP connection, and the opposite on your local machine to link that TCP connection to a "pty".
- https://stackoverflow.com/questions/22624653/create-a-virtual-serial-port-connection-over-tcp
- https://serverfault.com/questions/360321/forwarding-linux-terminal-from-serial-port-to-tcp-with-socat
But you should implement an alternative mechanism in your application itself – in addition to local devices, it should support e.g. RFC2217 over TCP/IP, which is a common "serial over TCP" protocol.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396134%2fis-possible-to-create-a-symlink-for-a-remote-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
No.
Symlinks only point to a path – the symlink resolution process essentially just replaces a part of the original name. For example, if you had a path /home/mario/docs/notes.txt
and docs
was a symlink to ../luigi/documents
, the process would give you /home/mario/../luigi/documents/notes.txt
.
Therefore you can only create symlinks for something that already has a local path. (For regular files this could be a path provided by a network filesystem such as NFS/SMB/AFS/9p, but devices usually cannot be exported this way.)
If your program only reads & writes data but doesn't use any parameters specific to serial ports (flow control, etc.) then you could create an adhoc tunnel using socat
or ser2net
on the remote device to link its serial port to a TCP connection, and the opposite on your local machine to link that TCP connection to a "pty".
- https://stackoverflow.com/questions/22624653/create-a-virtual-serial-port-connection-over-tcp
- https://serverfault.com/questions/360321/forwarding-linux-terminal-from-serial-port-to-tcp-with-socat
But you should implement an alternative mechanism in your application itself – in addition to local devices, it should support e.g. RFC2217 over TCP/IP, which is a common "serial over TCP" protocol.
add a comment |
No.
Symlinks only point to a path – the symlink resolution process essentially just replaces a part of the original name. For example, if you had a path /home/mario/docs/notes.txt
and docs
was a symlink to ../luigi/documents
, the process would give you /home/mario/../luigi/documents/notes.txt
.
Therefore you can only create symlinks for something that already has a local path. (For regular files this could be a path provided by a network filesystem such as NFS/SMB/AFS/9p, but devices usually cannot be exported this way.)
If your program only reads & writes data but doesn't use any parameters specific to serial ports (flow control, etc.) then you could create an adhoc tunnel using socat
or ser2net
on the remote device to link its serial port to a TCP connection, and the opposite on your local machine to link that TCP connection to a "pty".
- https://stackoverflow.com/questions/22624653/create-a-virtual-serial-port-connection-over-tcp
- https://serverfault.com/questions/360321/forwarding-linux-terminal-from-serial-port-to-tcp-with-socat
But you should implement an alternative mechanism in your application itself – in addition to local devices, it should support e.g. RFC2217 over TCP/IP, which is a common "serial over TCP" protocol.
add a comment |
No.
Symlinks only point to a path – the symlink resolution process essentially just replaces a part of the original name. For example, if you had a path /home/mario/docs/notes.txt
and docs
was a symlink to ../luigi/documents
, the process would give you /home/mario/../luigi/documents/notes.txt
.
Therefore you can only create symlinks for something that already has a local path. (For regular files this could be a path provided by a network filesystem such as NFS/SMB/AFS/9p, but devices usually cannot be exported this way.)
If your program only reads & writes data but doesn't use any parameters specific to serial ports (flow control, etc.) then you could create an adhoc tunnel using socat
or ser2net
on the remote device to link its serial port to a TCP connection, and the opposite on your local machine to link that TCP connection to a "pty".
- https://stackoverflow.com/questions/22624653/create-a-virtual-serial-port-connection-over-tcp
- https://serverfault.com/questions/360321/forwarding-linux-terminal-from-serial-port-to-tcp-with-socat
But you should implement an alternative mechanism in your application itself – in addition to local devices, it should support e.g. RFC2217 over TCP/IP, which is a common "serial over TCP" protocol.
No.
Symlinks only point to a path – the symlink resolution process essentially just replaces a part of the original name. For example, if you had a path /home/mario/docs/notes.txt
and docs
was a symlink to ../luigi/documents
, the process would give you /home/mario/../luigi/documents/notes.txt
.
Therefore you can only create symlinks for something that already has a local path. (For regular files this could be a path provided by a network filesystem such as NFS/SMB/AFS/9p, but devices usually cannot be exported this way.)
If your program only reads & writes data but doesn't use any parameters specific to serial ports (flow control, etc.) then you could create an adhoc tunnel using socat
or ser2net
on the remote device to link its serial port to a TCP connection, and the opposite on your local machine to link that TCP connection to a "pty".
- https://stackoverflow.com/questions/22624653/create-a-virtual-serial-port-connection-over-tcp
- https://serverfault.com/questions/360321/forwarding-linux-terminal-from-serial-port-to-tcp-with-socat
But you should implement an alternative mechanism in your application itself – in addition to local devices, it should support e.g. RFC2217 over TCP/IP, which is a common "serial over TCP" protocol.
answered Jan 19 at 18:40
grawitygrawity
237k37504558
237k37504558
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396134%2fis-possible-to-create-a-symlink-for-a-remote-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown