Search Results for 'samba'

[Member berghsg]

The best way is to uninstall the whole program, I find connectshares too much hassle and prefer using command line typed on the client PC such as:
sudo mount -t cifs -o username=’username-on-server’,vers=2.0 //ip-address-of-server/shared-folder-on-server /mount-point-on-client
Note: the server needs to have samba installed and share setup in /etc/samba/smb.conf

How to remove connectshares on Antix21 (may apply on Antix 19), refer below:

Start menu > Control Centre > Software > Manage Packages >

Run apt-get update now?
> yes
> no

select no

Please select an action
> Upgrade 167 packages now
> View a list of packages to be upgraded
> Ignore these upgrades for now
> Update package index (last update Sat Mar 4 17:28:56 SAST 2023)
Press <Enter> to select the highlighted entry
Use ‘h’ for help, ‘r’ to redraw, ‘q’ to go back to the main menu

select Ignore these upgrades for now

Main Menu
> Search for packages to mark or install
> View a list of 84 suggested Command Line packages
> View a list of 165 suggested GUI packages
> Search for antiX kernels
> Search for all kernels
> Update package index (last update Sat Mar 4 17:28:56 SAST 2023)
> Edit the repo source files
> View or perform 167 upgrades now
> Quit
Press <Enter> to select the highlighted entry

Select Search for packages to mark or install

Please enter the term you want to search for
Standard globbing wildcards ‘*’ and ‘?’ work

Use an empty string or q<Enter> to return to main menu
>

enter the keyword “connectshares”
Enter

Please select an action
> Show more information about package connectshares-antix
= Uninstall package connectshares-antix
> Do a different search

Select Uninstall package connectshares-antix

Please choose an action for this package
> Un-install package [remove package but not its config files]
= Purge package [remove package AND its config files]
> Reinstall package [even if it is up to date]
> Install package [only if it is not up to date]

Select Purge package [remove package AND its config files]

Quit

[Member Robin]

ren1268 wrote:

the larger file will give Input/Output error and incomplete process. … and this process made the antiX-Live-UBS became Read-only flash drive when it hung.

Please be carefully. This points to a hardware (USB-stick-controller or USB memory chip) issue. I have seen this several times shortly before an usb stick turned unresponsive completely. You might easily loose all your data stored on it.

Check your dmesg output for USB related i/o errors. If these happen frequently, don’t trust the stick any longer.

The other transfer path via LAN is pretty easy. All you need to do is to setup a samba server on one of the PC’s, then you can use the antiX tool „Connectshares” on the other one to mount the samba share(s) for fast and easy file transfer within zzzFM. There are many threads here in the forum already where the details are explained. (Additional hint: When the second PC happens to run on Windows, you can access it’s shared folders with „Connectshares” without any need of a samba server).

Windows is like a submarine. Open a window and serious problems will start.

[Member RJP]

metajo wrote:

Ok I installed antix. It is very fast indeed!!
I also managed to isntall xrdp (along with xorg ) and I can now get acces to it from my Windows machine. GOOD.
I’m going o install samba for folder sharing now.

I’m now trying to figure out how to add launch icons on the bar.

Thanks

It is icewm-toolbar-icon-manager via app-select

• This reply was modified 1 month, 1 week ago by RJP.

Attachments:

1. 

   icewm-toolbar-manager.jpg
   

[Member metajo]

Ok I installed antix. It is very fast indeed!!
I also managed to isntall xrdp (along with xorg ) and I can now get acces to it from my Windows machine. GOOD.
I’m going o install samba for folder sharing now.

I’m now trying to figure out how to add launch icons on the bar.

Thanks

• This reply was modified 1 month, 1 week ago by metajo.

[Member PPC]

To install and setup SAMBA in antiX: https://www.antixforum.com/forums/topic/how-to-create-a-samba-shared-folder-your-private-network/#post-79058

You can install xrdp on antiX, using Synaptic or the terminal (sudo apt install xrdp). I never used it, but it’s available under antiX.

I also created a small GUI script that detects and connects to samba shared folders- it’s available if you serch for Samba, here in the forum, but it’s also part of the package ft10-transformation, available on our repo, that includes a few extras for antiX and also allows a different interface, using tint2 as toolbar and jgmenu as toolbar menu…

It’s almost 100% certain that if something exists for Debian, Ubuntu (that’s Debian based), it’s available under other Debian based distros, even non systemd ones (like antiX), with very few exceptions.
I advise you to take a look at our pinned entries, on the threads, that help you figure out how antiX and the forum work. That will probably save you from asking many questions!

P.

[Member metajo]

ok

PPC wrote:

Snaps, that are systemd dependent, won’t run on antiX, other than that, you probably won’t notice any change…

P.

Would I install and setup samba, xRDP, the same way for example? Thanks

[Member PPC]

I don’t mean to sound “pushy” about my own scripts, but I really do think that these scripts would add some value to the default antiX setup:
– the script to connect to samba2 shared folders (I already made it available here, it was reported as not working, but I haven’t been able to test because my samba network at home is down)
– the script to connect to cloud drives

Those 2 scripts give what I consider to be modern functionality to antiX, costing about 0 in system resources, since the dependencies are installed only if the user wants to use those functionalities…

As nice little extras:
– the Weather script (it’s basically a on-liner, that opens a wttr.in window with the local weather, in the local language- users can check the weather without using a browser)
– the News script (it allows users to check out local news headlines without a browser- if they click a link, it opens in the default browser).
These 2 scripts are equivalent to some “gadgets” that most D.E.’s include, and cost just some kb of disk space, do not run in the background.

Scripts that may offer some nice funcionality:
– My “Clocks” script offers a World clock, a very basic Stopwatch, Count down timers (that can sound an alarm or even suspend antiX when they reach 0), and and Alarm
– My Agenda – it’s basically an extension to yad-agenda that pops up when users click the clock. It allows to add all day events, or timed events. Events for the current day are shown on the top of the calendar, days with events show up in a different colour and when users hover the mouse above those days, they see the events. Optionally, users can turn on the Alarm function. A tiny process runs in the background, and an alarm will sound at the exact time of the event. It looks about the same as the current yad agenda, but with an extra button, to search for events and another to enable/disable Alarms- they are off by default, to save system resources).

All this scripts, will their respective localization files take maybe a few hundreds of kb…

Once again, if you are interested in having any of this FT10 scripts in antiX, I can prepare them to be part of your yad-goddies, for example- adapting their names to avoid incompatibilities with FT10 (and, if those scripts are included in antiX, they will be removed in a future FT10 version).

P.

[Forum Admin anticapitalista]

antiX runit editions provide service files for the following via our own custom-built packages (antiX-22 and antiX-23).
Have a look in /etc/sv. Only ‘essential’ services are running by default (ls -la /etc/service/) and services that are also logging can be seen (as root) in var/log/runit. runit-service-manager should also show you all this information.

acpi-support
anacron
avahi-daemon
bluetooth
connman
cron
cups
dbus
dhclient
various getty-tty
gpm
haveged
ntpsec
rpcbind
rsync
seatd
slimski
udevd
ufw

Debian provides 2 (acpid and ssh).

Once user installs applications, it is 99% certain that a runit service file (/etc/sv) is not provided so user has to create their own if needed.
This is not trivial.
Debian still provides probably 80% of sysVinit startup files if needed (/etc/init.d and symlinks to /etc/rc*).

antiX is not 100% ‘pure’ runit like it is implemented on Void and possibly Artix.
It is very close though due to the work undertaken by me and Xecure since antiX-19.
The benefit of antiX not being 100% pure runit is that users can still use the sysVinit way to start and stop services as @Robin shows in their post (samba IIRC).
We cannot provide runit services for every app. Even Debian with its thousands of devs/helpers/packagers won’t do it even when pressed to do so by the init diversity group. Devuan doesn’t do it either. They just keep to how Debian sets up runit, which is basically just running it as pid1 over syVinit runtime scripts (we did this in our first implementation of runit).

The pipewire example probably wasn’t a good one. I used it as an example to show how writing runit services is not trivial, especially for complex apps like pipewire, samba etc. Does it need a runit service file? Caprea has shown it fdoesn’t. There isn’t an init startup file for it on sysVinit either.
My logic is that if Debian provides an init startup script in /etc/init.d (sysVinit), then you probably need a runit service set up in /etc/sv.

Hope this helps.

Oh, I forgot to mention that as far as I am aware there is no gui runit sevice manager except our own written by Xecure.
Something else: Void, Artix and Devuan do use elogind/libelogind0.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member Robin]

anticapitalista wrote:

Do the apps you mention need a service/startup script?

Not sure about this by now. Sorry for my ignorance, antiX 23 is first time I see runit and will need some time to get used to it. Still learning, reading tons of manuals, try and error…

Not sure what to think about this: I understood it that way, »sv« was meant to replace »service« command on runit systems completely. But on antiX 23 alpha I still get:

$ sudo sv status smbd
fail: status: unable to change to service directory: file does not exist

$ sudo sv stop smbd
fail: status: unable to change to service directory: file does not exist

So I tried to apply the sysvinit syntax from antiX 22 sysvinit:

$ sudo service smbd status
smbd is running.

$ sudo service smbd stop
Stopping Samba SMB/CIFS daemon: smbd.

Surprisingly this works on runit, and even starts and stops this service properly, while sv can’t do it. So it’s a bit confusingly which of the two commands to use for which system service to check, start and stop.

– Concerning alsa-utils: On antiX 22 I needed to restart alsa-utils after modprobing snd_aloop, but on antiX 23 this doesn’t seem to be necessary anymore, alsa seems to be aware of the new loopback device without restarting it. Same after modifications to ~/asoundrc files, on antiX 23 the changes are active immediately after the device was accessed next time, and even present and usable then in the amixer. So I’m not sure whether alsa-utils actually still need a startup script.

– Concerning lm-sensors:
For some reason I did get an odd reading from antiX conrtrol center → hardware → pc information → full info (section: Sensors), really odd counts. So I’ve writen down a note to mention in next report. But right now, some hours later, the readouts are perfectly fine:

Sensors:
  System Temperatures: cpu: 46.0 C mobo: 36.0 C gpu: radeon temp: 56.5 C
  Fan Speeds (RPM): cpu: 1406 case-1: 1259
  Power: 12v: 12.32 5v: N/A 3.3v: 3.42 vbat: N/A

So probably these also don’t need to get a startup script, they are running fine out of the box on antiX 23. But for debuging wrong data readouts (e.g. falsely set multipliers for fan speed or temperatures on some hardware) it might be useful to know how to start or stop the respective service after changing its multiplier config file. On antiX 23 by now I didn’t figure how to do it (not even sure whether this is the proper service running, without service –status-all command I don’t know how to get a survey of all running system services):

$ service lm-sensors status
lm-sensors: unrecognized service

$ sudo sv status lm-sensors
fail: lm-sensors: unable to change to service directory: file does not exist

So I’m not sure at all whether this is actually still the service used to control the sensors on antiX 23, or whether some other tool does this job now.

– concerning timidity:
Since I’ve switched meanwhile completely to qsynth/fluidsynth, which works way more smoothly and can simply get started when needed from menu and stoped by quiting the GUI window of qsynth (saving resources when not needed running), I’m not sure whether timidity would need a startup script like on antiX 22 sysvinit. But I’ll check it anyway, and report as soon I’ve found out.

Windows is like a submarine. Open a window and serious problems will start.

[Member Robin]

anticapitalista wrote:

This is the tool antiX runit users should use.

Please let me know how to start and stop alsa-utils, samba, lm-sensors, timidity, etc. with this tool? I can’t find them in »Runit service control« from antiX control center, neither in the »Listing of Services« nor in the »Listing of Services Currently Not Used« (after clicking on “Add Service” button). Many of the services running on the system fail to answer to sv command on antiX 23. What am I missing, or is it simply not ready yet?
And what’s the runit replacement on console for sudo service –status-all ? The sv command iteslf doesn’t seem to provide such an option. Do I need to loop through a directory listing for that?

Windows is like a submarine. Open a window and serious problems will start.

[Member PPC]

I just checked out:

-Remote Access – all entries installed, ran and got uninstalled (I did not try to connect anywhere, I just checked if the apps ran. I did not try to uninstall)
-Network- I partly tested this category:
AirVPN-Eddie (the binary is called Eddie) complained about “unabled to obtain elevated privileges”, even if if I tried to run it with sudo
Droopy and Dropbox installed and launched (Dropbox installed dropbox at first run, but I have no account to test it)
Network-Samba: failed to install- the terminal blinked on and off once. Also, I think this entry was missenamed- shouldn’t it be just “Samba”? Network-samba may confuse users…
This were the only tests I did on the Network category.

P.

• This reply was modified 1 month, 4 weeks ago by PPC.

[Member PPC]

Since I know next to zero about the inner workings of Linux, what I try to contribute here is some GUI scripts that ease the life of the less tech minded folks here, and waste a bit of time theming, too…

I already made available here in the forum my GUI script to easily connect to samba2 shared folder- I edited the script and it’s .desktop file so, if it’s included in antiX, there’s no conflict with the FT10 package… My point:

@anticapitalista – is there any interest in included in antiX any of my extra packages, that I include in FT10? The most important one, I think it’s the Shared folder one, but there are some little useful scripts, specially meant to use on-line services without forcing the users to use the Web browser (that’s particulary useful for extremely old devices). If so, just let me know, if not, any interested users can just install FT10…

Note: From what I’ve seen of it, I really do feel that MX’s deb-installer probably is less helpful to antiX users than FT10’s deb-installer, but including MX’s version, at least spares users from asking “how do I install the xyz.deb file?”, and that is a very welcomed feature!

P.

[Member 1040STE]

Well I updated/upgraded often, but maybe not with the good repos. I already had a major update, the grub was already updated…
At least now there’s a smb.conf file. I’m suggested to add
min protocol = SMB2
in the [global] part, but it doesn’t prevent the computer to carry on with SMB1, according to the NAS log. Even after a reboot (it appears I can’t restart Samba with the suggested systemctl restart).

[Member PPC]

1040STE wrote:

That caused a ton of upgrades for a while, and gave me the impression that all the system was changed/reinstalled (and that maybe I shouldn’t have done that),

No, quite the opposite- that’s what you should do. Having an updated system is probably one of the best security mesures you can have. If you never updated the system, then, manyyyyyy hundreds of megabytes will be downloaded. It’s normal. Unfortunalty, this updates also include a grub update – which can confuse many newbie users (since it has a very peculiar interface, and just pressing enter in the wrong place can make your system unbootable…- it’s basicaly the only dangerous thing in the entire update process).
My script does not work with Samba 1 shared folders, sorry… you’ll have to finde another way to connect to it, if that’s the problem.

P.

[Member olsztyn]

PPC wrote:

Hi. there is no need to install FT10 to use the samba2 shared folder GUI script- it’s available here in the forum.

Thank you PPC for sharing this useful tool independently from FT10…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters