-
Search Results
-
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 ?
How can I access remote shares in my local network?
Using a file manager is not the only way to mount network shares.Connectshares is an easy to use share access automation tool, designed with simplicity in mind. It can be quickly set up and used by a standard user and without the need of deep technical knowledge.
Does it work in my preferred environment?
Many popular file managers work only in a Graphical User Interface (GUI) within the Linux desktop.Likewise, Connectshares works in a GUI, but also works at a Command Line Interface (CLI) within a terminal, and additionally in a console environment i.e. when no X GUI is running. This enables you to employ Connectshares as a single universal method to mount remote shares no matter which type of environment you prefer to work in.
Will it overload my system?
When using a GUI file manager to access remote shares, that file manager often must be loaded, which in turn uses CPU and RAM.After mounting the remote shares in your local system, Connectshares quits which minimizes CPU and RAM usage to zero in all practical terms. Because it does not leave apps, services, or daemons, running the CPU and RAM available to your system is maximized for other apps and tasks.
What do I need to install?
Some popular file managers use plug-ins or virtual file systems to access remote shares. Sometimes you might need to install the additional software manually to obtain the wanted functionality.Connectshares makes use of standard components that are present in almost every Linux distro. antiX ships with Connectshares installed together with everything that it needs, so installation of additional software is not required.
Will it discover which shares are available in my local network (LAN)?
Some popular file managers are able to scan the LAN, some rely on extra software being installed to find shares.Connectshares includes everything it needs discover various types of shares. These include shares on Windows boxes, Samba shares on Linux boxes, and NFS shares on Linux boxes.
How difficult is it to set up?
Popular file managers need to be told which shares to mount.Likewise Connectshares needs to be told which shares to mount. This needs to done once only. It is set-and-forget. Optionally, the way in which the shares are mounted can be finely controlled, but this is not usually needed.
How do I use it to work with shared files?
Normally remote shared files made available via a popular file manager are effectively tied to that file manager.Connectshares will work with any file manager irrespective of whether it ships in antiX or is one you choose to install. When any file manager is used together with Connectshares, you can work with network shares in a simple and familiar way.
A file manager is not actually needed. Connectshares makes network shares available to any GUI application or psuedo GUI application, whether the app is network-enabled or not.
A GUI or psuedo GUI application is not actually needed. With Connectshares you can use and manage remote shared files via the command line.
Basically, Connectshares mounts the remote shares into the local system, then quits to get out of the way, leaving the shares available to be used by any app.
Is it convenient to use
Convenience is one of those things that varies from person to person. Here are some of the things Connectshares can do that are not mentioned above.- Works with network shares that require, and those that do not require, a username+password,
- Option to automatically or manually supply the username+password to those remote shares that require credentials,
- Unchallenged log-in to network shares that do not require a username+password,
- Option to automatically access remote shares while logging-in to your local system,
- Capability to automatically access network shares on multiple remote systems at log-in, or manually on demand at any time,
- Option to automatically unmount shares at log-out, or manually on demand at any time
Is there any further help on it?
There is a step-by-step written user guide in the FAQ and a video by dolphin_oracleThe written user guide is available in the antiX FAQ:
Online
http://download.tuxfamily.org/antix/docs-antiX-17/FAQ/connectshares.html
Locally installed
See the Help section of the antiX main menuThe video is available on Youtube
https://www.youtube.com/watch?v=pp95SzXLp7QHello, I’m new to “Heather Heyer” and probably haven’t even virtualized antiX in a good five years. I’m absolutely loving what you’ve been up to except for the troubles I’m having with Samba. I didn’t have much luck with Connectshares, so I tried just using Spacefm, which would have been ideal, with the address smb://username@ip-address-of-server/share instead of my accustomed smb://ip-address-of-share and/or smb://network/workgroup/hostname-of-server from pcmanfm.
After much grumping and grumbling and shaking my fist at the sky, I finally opened a terminal and realized that it was no big deal to use my words like a big boy/girl and and sudo apt-get install pcmanfm gvs-backends gvs-fuse but I still can’t access my home network. I had the same problem with Devuan on the same Thinkpad T43 I am using for the install, but was under the impression that it was not a hardware issue, just my own inexperience and sloppiness.
I rarely actually need to connect to a windows machine, so samba may just be a bad habit. My current antiX machine(s) are old and I have a brand new hard drive install on a 12 gig IDE drive. I want to access configuration files that are stored on the server and, when all the customizing, learning, and “moving in” is done, edit and access files for word processing, .pdf and .epub books, streaming media, etc.
tia, and this is a question, not an emergency. 🙂
Gnu/Linux user #387554 (since 2005-4-17) with old thinkpads and a strong preference for free-as-in-freedom over proprietary software.
Having loved and dabbled in antiX for a long time, I find that I still have so very much to learn and that learning is so very enjoyable.
Topic: My old thinkpads…
Hello together,
my “problems” do not concern the “new” releases plus I consider myself still as “new user”, thus posting here:
(1) Thinkpad 600x: Did not play sound on 16.2 but does out of the box under 13.2 – So I did 10+ install runs playing araound and destroying the installation and starting over over the last week:
– Grub does not install on partition (was known in the Tapatalk forum) – so finally I installed to MBR and exchanged the MBR with WinXP boot-ini-sectos until everything now works nicely (booting DOS, WinXP, OS2 and antiX 13.2 and WinPE-Rescue).
– Release-Time presets for Repositories (Wheezy mostly) do not work any more. I did some guessing etc. and found something that works now (must be VERY carefully with deinstallation-requests by some newer packages) – nevertheless: can someoone maybe post a list of “correct” current Repo URLs for Wheeze, Lenny etc. and the corresponding antiX-special packages?
– Still need to get Samba working and updating the menus and standard pogramms settings -if someone remembers how that was done in 13.2 – I am happy about tips…(2) Thinkpad 600 (no x, Pentium 2!, but CF-card-“SSD” and TP-Link Atheros-9K-11n-USB-WLAN – so “modern stuff”):
– 16.2 is installed and runsn with two big probs:
– WLAN: the stick is seen and obviously tries to work, but the firmware crashes every second and writes a long message into kernel log, syslog and messages log – filling up the harddrive in about an hour. I tried a few firmware packages, but they make no difference (atheros-frimware 0.43, 0.38 or so and the 1610xx-version) – I beleive that either an older kernel (as needed for sound anyway) may help or a bug report to the driver guys (google does not find much so far) – likely troublemaker is timeout due to USB 1.1 (but no prob under W2K, so it must be possible to work that slow)… –> can anyone with some more understanding of the connections between the components and their teams advise, where I could look for a solution for that (i.e. Atheros ar9271 on USB 1.1)?
– sound: The cs423x-driver is not included in many new kernels. There are some which do have the driver, but it snot easy to install a new kernel as long as the machine has no network (see above)…(3) Is it planned to salvage at least the contents (has a huge lot of know-how, known problems and even solutions and links) of the old Tapatalk forum?
So far for now. Enjoying web radio via the 600x right now…
Torsten