- This topic has 13 replies, 6 voices, and was last updated Dec 17-6:23 pm by Anonymous.
-
Posts
-
Ninho
Hi ! What is the most natural, easily setup, way to share browse and move files between stations running antiX on a LAN ? I am aware of the Connectshares application bundled which our distro, but altho support for NFS is briefly mentionned, the setup – described in the guide – is oriented only towards accessing MS.Windows (aka SMB, Samba) shares from Linux *clients*.
My question is different : given two or more stations each running Linux, on a home network without security obstructions, what is the best option to provide seamless access to one another’s file system, on a peer to peer basis if possible (rather than FTP, and similar)? With Connectshares would I be forced to run one or more Samba *servers* (in addition to clients, and is the “SMB server” installed as part of Connectshares or a szparately installed application ? What is “NFS” and can I use that to advantage in the situation described ?
SamK
What is the most natural, easily setup, way to share browse and move files between stations running antiX on a LAN ?
What you mean ny “natural” is anyone’s guess.
Droopy is shipped in antiX and out-of-the-box allows browse and move without setting anything up.I am aware of the Connectshares application bundled which our distro, but altho support for NFS is briefly mentionned, the setup – described in the guide – is oriented only towards accessing MS.Windows (aka SMB, Samba) shares from Linux *clients*.
That is not an entirely appropriate summation. The example in the FAQ guide does illustrate how to access Samba shares. If you had inspected the connectshares.conf file it refers to, you will see the section on NFS shares provides commented guidance in precisely the same manner as that for Samba shares.
…given two or more stations each running Linux, on a home network without security obstructions, what is the best option to provide seamless access to one another’s file system,…
That is going to vary from user to user. What one user views as the bast may not be the best in the opinion of a second user. You also appear to be introducing different criteria to that given in the opening question.
…would I be forced to run one or more Samba *servers*…
If you choose to share files with Samba, each system that publishes a share to the LAN will need its own Samba server.
…is the “SMB server” installed as part of Connectshares…
Connectshares is only a client-side share access automation tool, which mounts shares published by another remote system in the LAN. It does not include a Samba server.
What is “NFS”…
Some web research is required on your part to get a grasp of that question. There is lots of info available on the topic out on the net. It will be very difficult for you to make informed decisions without acquiring some basic knowledge and understanding.
In greatly oversimplified terms, Samba/CIFS is often (but by no means exclusively) used to interact between Linux and Windows boxes. NFS is a native Linux networking method of long-standing used for Linux to Linux interaction.
Anonymous
Have you read this yet? (maybe not, it was posted just this week)
https://www.antixforum.com/forums/topic/remote-share-access-connectshares-v-file-manager/At the bottom of that post, follow the link & watch dolphin_oracle’s video
After you have tried (actually used, not just read about) connectshares, come back here and mention what aspects of connectshares doesn’t suit your intended usage
What is “NFS” and can I use that to advantage in the situation described ?
Do some legwork, Chief.
websearch and you’ll find plenty of references (definition, setup, tutorials)
BTW, the pre-installed spacefm file manager provides easy mounting & browsing of NFS (and other) network URLs (see: spacefm usermanual)====
edited to add:
When I posted, I didn’t notice SamK had already replied.
Even though you stated “(rather than FTP, and similar)”… for me, the longstanding “natural” goto has been FileZilla (sudo apt instalal filezilla)
Although it’s mature (stable), cross-platform, supports drag-n-drop… it’s seldom pre-installed by distros nowadays.Dear SamK you are confirming my suspicion, built upon previous expermintation with Connectshare I must say, that Connectshares is ONLY A CLIENT for Samha, i.e. mostly Windows shares. You did not give a clue clue as to whether a Samba server exists for Linux (I suspect there should be a couple implementations), whether one is provided in antiX, or can be fetched and installed from the repos.
As for Droopy, which I have used in the past too, it is just a minimal HTTP server, that is OK for quick and dirty serving of a file/ or directory thru the Internet, but if you vooled down and considered the question again you’d realise that I am talking of sharing across a trusted LAB – not internet – ala Windows-file-sharing, IOW sort of mounting or grafting (all or part of) the distant file system on the local FS, in order to browse it like it were local, in ANY file manager, or command line tool. Which SMB does pretty well in the MS Windows world.
So yes – unless you deign explain NFS ; is that built-in our Linux ? Server and client ? – it’s prolly a SAMBA server I need.
dolphin_oracle
there is an area in the Package Installer for bring in the samba server which will get what you need.
Setting up a samba share is not complicated but its a little bit of a manual process. My video on the subject may help.
its an older video so some of the links referred to don’t work anymore, but the information is still valid and there is a working example smb.conf file in the show notes. A common stumbling block is making sure your samba-user has the correct linux permissions to access the shared folder (this may be automatic now, its been a while since I set mine up.
- This reply was modified 5 years, 4 months ago by anticapitalista. Reason: shrunk video
(acceder-a-worgroup-t6627-s30.html)
posted: 2016-11-26
posted by: NinhoD’après vos premiers messages, vous vouliez mettre en place des partages (“network shares”) pour accéder depuis antiX à vos fichiers sur des machines”Windows” de votre réseau local – c’est bien cela ? Vous devez utiliser l’application”connectshares” d’antiX ! Y êtes-vous parvenu ?
related:
https://antix-skidoo.github.io/archive/browse-ntfs-partitions-in-rox-filer-t6664.htmlDolphin_Oracle said : there is an area in the Package Installer for bring in the samba server which will get what you need.
Setting up a samba share is not complicated but its a little bit of a manual process. My video on the subject may help.Ah, this is exactly what I needed to hear. I’ll follow your write up and (or)video. Very much obliged
—
Ninho@Skidoo wrote – google translated :
According to your first messages, you wanted to set up shares (“network shares”) to access antiX from your files on “Windows” machines on your local network – is that it? You must use the antiX “connectshares” app! Did you manage?
You sure must be joking ! That question was over one year back ! Of course I “managed” to use Connectshares for the then stated purpose and appreciated its simplicity. I also used Droopy around the same period to publish shares over the Internet to selected correspondents.
The new question is to access files/shares residing on a Linux – NOT MS windows system, and on the LOCAL betwork (LAN – NOT internet – NOT (not necessarily at least) thru TCP or other internet protocols).
According to Dolphin Oracle I should be able to install the SMB SERVER on one (or more antiX systems, which appears to be the (or an) answer to my needs. I’m still curious about NFS, what it is and whether it would be usable/appropriate for sharing files on a LAN too.
Good day (night here and well past bed time even) ! Going to the sack now.
rust collector
nfs is usable to share files on a lan.
Go play with it, and see if you like it@Rust Collector :
nfs is usable to share files on a lan.
Interesting ! Now that is answering my question and removing any doubts I had.
I am seeing our antiX has the NFS-common package already installed as well as
the Samba-common, so it’s a matter of choosing which one to add as server.
D-d-g found a simple practical guide for installing the NFS server There :
https://linuxconfig.org/how-to-configure-nfs-on-linux
with additional pointers to more in depth information.While it wouldn’t surprise me that NFS were in fact a superior protocol – after all,
SMB is mostly an IBM/MS creature and has the longstanding, unflattering, reputation
of being a “chatty” protocol – and I would hence surely choose it over SMB in a pure
Linux network, yet for practical reasons I am not prepared yet to forego MS-systems
completely, hence the best choice appears to be to setup SMB-servers on the Linux machines
for sharing files and printers in a heteogeneous network configuration.Thanks…
As for Droopy, … that is OK for quick and dirty serving of a file/ or directory thru the Internet, … I am talking of sharing across a trusted LAB – not internet…
Your assertion is entirely incorrect. If you had referred to, and understood, the Droopy FAQ guide and/or the Droopy video you would have known they both make it clear that Droopy works in both LAN and internet scenarios.
The FAQ tells you in:
• the first point of the features section,
• the section headed “Transfer Across Local Network”.The video tells you:
• within the first 45 seconds.Droopy was mentioned as it fits the criteria you gave in your opening question.
What is the most natural, easily setup, way to share browse and move files between stations running antiX on a LAN ?
• It cannot get any easier than not having to do any set up,
• It allows you to share files from any system on which you run it,
• It allows you to browse the shared files in any system on which you run a web browser,
• It allows you to move files (upload and download) between the systems.An answer that fulfills the specific question you ask is not invalid simply because you choose to decline it based on your mistaken view of the app.
…if you vooled down and considered the question again you’d realise that I am talking of sharing across a trusted LAB – not internet – ala Windows-file-sharing, …
Again you appear to have misunderstood. In my reply, I pointed out that you were introducing criteria that were different to those in you first question at the head of your opening post. That could not have been done without a realization of the changes you were introducing.
…in order to browse it [a share] like it were local, in ANY file manager, or command line tool.
That is yet a further change in criteria that is not mentioned anywhere in your opening post.
…Connectshares is ONLY A CLIENT for Samha, i.e. mostly Windows shares.
Once again you are making statements that are wrong.
In both the Connecshares FAQ guide and the Connectshares video it is made clear that it handles Samba/CIFS and NFS shares. Also the point is again made in the Tips and Tricks post that provides a comparison summary of accessing remote shares using Connectshares v a file manager.
Additionally using capital letters in that way is best avoided. It is generally regarded as shouting and impolite. When it is shouting something that is wrong extra care should be taken to avoid it.
You did not give a clue clue as to whether a Samba server exists for Linux…
It is odd to expect a reply to your opening post to include an answer to a question that was not asked in that opening post. It is also a perverse expectation when you object to a previously given answer which actually addresses the criteria of that question.
The fact that you did not know that Samba is extensively used across Linux is a clear pointer to the paucity of your understanding and knowledge about file sharing. That is further emphasized by asking “What is NFS…” rather than doing some research and testing yourself in order to gain a basic working awareness.
…unless you deign explain NFS ; is that built-in our Linux ? Server and client ? – it’s prolly a SAMBA server I need.
You will make whatever choice you want to based on whatever level of understanding you deem appropriate. If you think a Samba server on each system is the way to go, by all means go ahead. I am disinclined to provide detailed information to someone that conducts such a limited amount of research, together with negligible levels of self help while expecting others to provide them with assistance that effectively does the work for them.
Again I am responding to correct inaccurate statements.
You seem to be under the impression I am advocating the use of Droopy rather than Connectshares+Samba/NFS. This is incorrect. In my reply #3841 to your opening post #3840, Droopy was mentioned only because it fitted the criteria of your opening question at the head of your post.
The information about Droopy occupies a tiny portion of my post #3841, the majority of that post relates to Connectshares, Samba and NFS.
Your post #3843 is the reply to my post #3841. It contains a complaint that I did not answer a question you did not ask, a requirement not mentioned in your opening post, a provocatively worded prompt for me to explain the NFS client/server networking system, and 3 factually inaccurate statements.
Each was responded to in turn in my post #3874. At the very least, your factually wrong statements needed to be addressed for the benefit of current and future readers of this topic. These corrected the incorrect statements you were making about Droopy and Connectshares and also pointed to where you can find the correct information about them.
My post #3874 also included advice about avoiding shouting in posts. This advice was ignored and you continued to shout in you post #3877. You are requested to edit that post to remove the shouting.
Dave
I am sorry, I did not read the whole thread… just going to post the wiki link in case it was missed.
MX/antiX Wiki NFS- This reply was modified 5 years, 4 months ago by Dave.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
PSA:
Something within #3877 (or repeated edits to its content?) triggered the forum’s anti-spam mechanism.
After manually marking #3877 “un-spammed”, the Akismet mechanism RE-flagged it… so I have moved #3877 to “Trash”
- You must be logged in to reply to this topic.
