Search Results for 'samba'

[Member Robin]

Anonymous wrote:

so maybe there’s a conditionally-triggered problem that I haven’t yet discovered.

dug deeper here. Result:

Robin wrote:

and/or possibly reading from slow USB or network devices.

Turned out this is part of the solution. Under some circumstances (haven’t found out what exactly triggers this) the obviously existing cache (usb devices don’t always power up for re-reading) of entries from external drives is emptied. This causes external mechanical hdds to power up from sleep and reread the complete directory (snooooooooooze…), waiting with a blank tab until power up and reading process has finished. When the connection is slow (like USB 1.x) this may take 10 or more seconds each tab, depending on the number of items and speed of drive and connection. In case connection gets lost for some more time the display of content in a specific tab will wait indefinitely, keeping you from reaching the other end of the tab-bar at all.
You will be able to trigger this by creating a connection to a directory stored on an external Samba server using “connectshares” via WLAN and opening a tab for this device (shouldn’t I really say protocol here?) in zzzFM amidst some more local devices tabs. Now chose another tab and cut off Wlan connection using the hardware wlan switch of your computer. And now try to cross over the tab containing a folder on this device. It’ll stop you until you power up your wlan hardware again, waiting for automatically reestablishing the server connection and until rereading the complete list of items from the resource is done, before allowing you to move to the next tab. If you don’t use wlan you could probably trigger this effect by unplugging a network cable instead, faking a slow or lost connection condition this way, and replugging it to see what happens. Stay calm while waiting, display content of the tab will come back somewhen after connection is re-established, allowing you to proceed.

I believe this is the main reason for the behaviour observed. The need for real re-rendering graphics display content for each tab here on the way from one end of tab bar to the other is probably neglectable compared to this.

What I didn’t found out until now was the reason for exhausting the single core 1,7GHz CPU to 100% while only switching across some tabs in this program, which really shouldn’t be a task like compiling some code. Since a dedicated GPU is installed here, this probably isn’t caused by the redraw of display content in the tabs.

Again, I had to perform all my testing still using SpaceFM, so maybe zzzFM reacts differently already.

So long

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

1. It’s recommended to be up to date so first run

sudo apt-get update

and

sudo apt-get upgrade

2. You will need the dpkg-dev package installed to use dpkg-scanpackages command.

sudo apt-get install dpkg-dev

3. Create a folder for downloaded deb packages. This can be in your home folder or a
samba share as well.

sudo mkdir -p /usr/local/debs

then place any downloaded packages in it. /usr/local directory will need sudo or root
permissions to copy them into it.

4. cd into that folder and create the file update-debs.sh to contain these lines.

#! /bin/bash
cd /usr/local/debs
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz

5. make the script executable.

sudo chmod u+x ./update-debs.sh

6. move the script to /usr/bin. Can run from the folder each time if it is in your home folder.

sudo mv ./update-debs.sh /usr/bin/update-debs.sh

7. Open /etc/apt/sources.list in an editor as root and add this to it.

deb [ trusted=yes ] file:/usr/local/debs ./

8. run update-debs.sh

sudo update-debs.sh

for globally or

sudo ./update-debs.sh

if it’s in your home folder.

9. run apt

sudo apt-get update

then

sudo apt-get install {package name}

say yes to installing an unverified package.

10. when you add deb packages to the folder must run

sudo apt-get update-debs

and

sudo apt-get update

each time for apt to see the new packages. After updating the debs they will
also show up in synaptic.

[Forum Admin Dave]

As it is likely an arm based system antiX will not run on it anyway.
Debian runs on a nas fine (I have a dlink setup with debian) but you will likely find to run anything gui will be slow. (my dlink only has 512mb of ram). However it is possible to run a vnc service over ssh for this task. Samba, webserver, Owncloud all seem to run fine. In fact the first year of the antiX repo’s existence was piloted on one of these hacked dlinks. If you are looking for an high performance nas, it will most likely become a computer. Fanless computers seem to make good “high performance” nas systems. You can probably find a cheap one with decent ram/cpu but with 2 network cards. Then you can attach the nas directly with the one network card with a minimal debian install with nfs-kernel-server+raid, mount the kernel server share on the fanless computer and use the fanless computer for all the heavy duty fancy network tasks you are looking for.

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

Hello

I asked this question over at MX Linux forum, but I think it’s more useful I ask it here after some advice.

I have QNAP NAS (TS-251+ with hdmi output, 2gb DDR3L-1333 ram, celeron 2ghz quad core cpu) – and hate its bloated slow operations and plan to replace its OS, to use as a home server/LAN only. I wouldn’t be using this for any heavy lifting; more like samba sharing, syncthing, duplicati, data partition disk encryption, (maybe nextcloud).

While I have experience of messing about with linux and I’m ok with cli, it would be nice to use some type GUI to manage the nas box. I first thought of installing debian with xfce. But why not antiX? Is this a good idea? Any cons that you could think of, problems I may run into?

Thanks for any advice

[Member LarryDC]

OK. I just apt-get install the above packages:
libbsd0 libbsd0:i386 libmpv1 libpython3.9 libpython3.9-minimal
libpython3.9-stdlib libsndfile1 libsndfile1:i386 python3.9 python3.9-minimal
xfsprogs

Then:

# apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  libldb2 libreadline5 libsmbclient python3-ldb python3-talloc samba-libs
0 upgraded, 0 newly installed, 6 to remove and 1 not upgraded.
After this operation, 27.1 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 194102 files and directories currently installed.)
Removing libsmbclient:amd64 (2:4.13.4+dfsg-1) ...
Removing samba-libs:amd64 (2:4.13.4+dfsg-1) ...
Removing python3-ldb (2:2.2.0-3+b1) ...
Removing libldb2:amd64 (2:2.2.0-3+b1) ...
Removing libreadline5:amd64 (5.2+dfsg-3+b13) ...
Removing python3-talloc:amd64 (2.3.1-2+b1) ...
Processing triggers for man-db (2.9.4-1) ...
Processing triggers for libc-bin (2.31-9) ...

Now this is what apt says is the problem:`
# apt upgrade
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
elogind : Conflicts: systemd
Conflicts: systemd:i386
eudev : Breaks: systemd (> 220)
Breaks: systemd:i386 (> 220)
libelogind0 : Conflicts: libsystemd0
libelogind0:i386 : Conflicts: libsystemd0
runit-init : Conflicts: systemd-sysv
Conflicts: systemd-sysv:i386
E: Broken packages`

But apt-get upgrade is happy:`
# apt-get upgrade
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
The following packages have been kept back:
init
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.`

While apt dist-upgrade still complains:

# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  getty-run
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
  init runit-init
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  init runit-init (due to init)
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 73.7 kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
 ?]

"ουκ εν τω πολλώ το ευ" Aristotle
i5 8GB RAM, 3 HDs mainly JWM.
Linux User #305687 (Antix runit, Crowz, Michaels-Duvuan, Absolute, Sparky, Endeavouros)
Pawtucket RI EE.UU.

[Member LarryDC]

anticapitalista wrote:

after apt-get upgrade? What does apt dist-upgrade show?

Here it is:

apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  getty-run libldb2 libreadline5 libsmbclient python3-ldb python3-talloc
  samba-libs
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  init runit-init
The following NEW packages will be installed:
  libinih1 libmd0 libmd0:i386 libmpdec3 libopus0:i386 libplacebo72
The following packages will be upgraded:
  libbsd0 libbsd0:i386 libmpv1 libpython3.9 libpython3.9-minimal
  libpython3.9-stdlib libsndfile1 libsndfile1:i386 python3.9 python3.9-minimal
  xfsprogs
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  init runit-init (due to init)
11 upgraded, 6 newly installed, 2 to remove and 0 not upgraded.
Need to get 11.2 MB of archives.
After this operation, 7,484 kB of additional disk space will be used.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'

"ουκ εν τω πολλώ το ευ" Aristotle
i5 8GB RAM, 3 HDs mainly JWM.
Linux User #305687 (Antix runit, Crowz, Michaels-Duvuan, Absolute, Sparky, Endeavouros)
Pawtucket RI EE.UU.

[Member LarryDC]

Sorry Murdock2525, it does not show only bullseye.
to anticapitalista: “Is it bullseye or sid? Did you upgrade from buster?”

What I installed was: antiX-19.3-runit_x64-full.iso
And as can be seen from my repositories I did change to testing NOT sid:

$ inxi -br
System:
  Host: i5 Kernel: 4.19.152-antix.1-amd64-smp x86_64 bits: 64 
  Desktop: JWM 2.4.0 Distro: Debian GNU/Linux bullseye/sid 
Machine:
  Type: Desktop Mobo: ASUSTeK model: P8B75-V v: Rev X.0x 
  serial: <superuser required> BIOS: American Megatrends v: 1601 
  date: 09/19/2013 
CPU:
  Info: Quad Core Intel Core i5-3350P [MCP] speed: 1596 MHz 
  min/max: 1600/3300 MHz 
Graphics:
  Device-1: NVIDIA GT218 [GeForce 210] driver: nvidia v: 340.108 
  Display: x11 server: X.Org 1.20.10 driver: loaded: nvidia 
  resolution: 1920x1080~75Hz 
  OpenGL: renderer: GeForce 210/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  driver: r8169 
Drives:
  Local Storage: total: 1.35 TiB used: 270.42 GiB (19.6%) 
Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list 
  1: deb http://la.mxrepo.com/antix/testing testing main nonfree nosystemd
  Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 
  1: deb http://deb.debian.org/debian buster-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.us.debian.org/debian/ testing main contrib non-free
  2: deb http://security.debian.org testing-security main contrib non-free
  No active apt repos in: /etc/apt/sources.list.d/onion.list 
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 234 Uptime: 5m Memory: 7.72 GiB used: 907.7 MiB (11.5%) 
  Shell: Bash inxi: 3.3.01 

Perhaps the whole antix Updater listing will help?

The following packages were automatically installed and are no longer required:
   getty-run (2.1.2-40.0antix1)
   libldb2 (2:2.2.0-3+b1)
   libreadline5 (5.2+dfsg-3+b13)
   libsmbclient (2:4.13.4+dfsg-1)
   python3-ldb (2:2.2.0-3+b1)
   python3-talloc (2.3.1-2+b1)
   samba-libs (2:4.13.4+dfsg-1)
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
   init (1.60)
   runit-init (2.1.2-40.0antix1)
The following NEW packages will be installed:
   libinih1 (53-1+b1)
   libmd0 (1.0.3-3)
   libmd0:i386 (1.0.3-3)
   libmpdec3 (2.5.1-1)
   libopus0:i386 (1.3.1-0.1)
   libplacebo72 (2.72.2-1)
   system-keyboard-qt (21.02.01+antix2)
The following packages will be upgraded:
   antix-installer (1.3.5 => 1.4.1)
   cdparanoia (3.10.2+debian-13+b1 => 3.10.2+debian-13.1)
   gir1.2-vte-2.91 (0.62.2-1 => 0.62.3-1)
   git (1:2.30.0-1 => 1:2.30.1-1)
   git-man (1:2.30.0-1 => 1:2.30.1-1)
   intel-microcode (3.20201118.1 => 3.20210216.1)
   libbsd0 (0.10.0-1 => 0.11.3-1)
   libbsd0:i386 (0.10.0-1 => 0.11.3-1)
   libcdparanoia0 (3.10.2+debian-13+b1 => 3.10.2+debian-13.1)
   libcmis-0.5-5v5 (0.5.2-2+b2 => 0.5.2-3)
   libdns-export1110 (1:9.11.19+dfsg-1 => 1:9.11.19+dfsg-2)
   libisc-export1105 (1:9.11.19+dfsg-1 => 1:9.11.19+dfsg-2)
   libjson-glib-1.0-0 (1.6.0-3 => 1.6.2-1)
   libjson-glib-1.0-common (1.6.0-3 => 1.6.2-1)
   libmpv1 (0.32.0-2+b1 => 0.32.0-2.0antix1)
   libpcsclite1 (1.9.0-1 => 1.9.1-1)
   libpython3.9 (3.9.1-2 => 3.9.1-4)
   libpython3.9-minimal (3.9.1-2 => 3.9.1-4)
   libpython3.9-stdlib (3.9.1-2 => 3.9.1-4)
   libsdl1.2debian (1.2.15+dfsg2-5 => 1.2.15+dfsg2-6)
   libsndfile1 (1.0.28-8 => 1.0.31-1)
   libsndfile1:i386 (1.0.28-8 => 1.0.31-1)
   libvte-2.91-0 (0.62.2-1 => 0.62.3-1)
   libvte-2.91-common (0.62.2-1 => 0.62.3-1)
   nano (5.5-1.0antix1 => 5.6-1.0antix1)
   python3.9 (3.9.1-2 => 3.9.1-4)
   python3.9-minimal (3.9.1-2 => 3.9.1-4)
   tar (1.32+dfsg-1 => 1.34+dfsg-1)
   xfsprogs (5.6.0-1+b2 => 5.10.0-4)
   xserver-common (2:1.20.10-2 => 2:1.20.10-3)
   xserver-xorg-core (2:1.20.10-2 => 2:1.20.10-3)
   xserver-xorg-input-elographics (1:1.4.1-2+b1 => 1:1.4.2-1)
   xserver-xorg-video-mach64 (6.9.6-2+b1 => 6.9.6-3)
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
   init
   runit-init (due to init)
33 upgraded, 7 newly installed, 2 to remove and 0 not upgraded.
Need to get 32.0 MB of archives.
After this operation, 7,933 kB of additional disk space will be used.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'

"ουκ εν τω πολλώ το ευ" Aristotle
i5 8GB RAM, 3 HDs mainly JWM.
Linux User #305687 (Antix runit, Crowz, Michaels-Duvuan, Absolute, Sparky, Endeavouros)
Pawtucket RI EE.UU.

[Member eric]

down to differences in the boot scripts re Debian(antiX)/arch(obarun).

Let me the time to make some test to see what happens.

“Unable to find a connection to the system bus”

The script just install the necessary to boot the machine and do not add runtime service like dbus (except slim). You need to enable what you need. You can find good example here https://framagit.org/pkg/observice and here https://github.com/mobinmob/void-66-services/tree/samba/usr/share/66/service

• This reply was modified 2 years, 2 months ago by eric.

[Member seaken64]

Since your goal is to use the machine as a file server you should focus your learning on setting up a server. You can use a GUI but most file server setups are done using the command line and editing text configuration files. Since antiX is not formally designed to be a server you will need to make some modifications to antiX to “create” your server. antiX is fully capable of this application.

But if you want to learn more quickly about setting up servers you should explore some other distros that are specific to that application. antiX is a great tool for bringing old unused computer back into use. But file servers do not require the typical GUI used in antiX (which defaults to ROX-IceWM). I agree with anticapitalista and recommend you use the CORE version and build up from there. But this is not going to be easy for a newbie. The upside is that you will learn a lot about Linux in general. Unfortunately there is not a lot of tutorials on how to use antiX as your server OS. There are better distros for learning that application. Once you get your feet wet in those server distros you can use antiX Core to build.

In your newer computers it won’t matter. But on the 20+ year old equipment it will be better to not use a GUI at all. And upgrading to 512MB was a good move. I have had good success using Samba when sharing the LAN with Windows machines. FTP/SFTP has also been useful.

Welcome to antiX.

Seaken64

[Forum Admin anticapitalista]

Could testers give feedback on the following areas.

Printing/Scanning
Snapshot
Remaster/Persistence
Frugal install onto an existing encrypted partition
Wifi/Network Connection
Network sharing (Droopy or Samba)
Internationalisation – menus, antiX apps
High definition screen support
Nvidia
Any crashes

Thanks

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

antiX with runit - leaner and meaner.

[Anonymous]

ftp//sftp, or via http, or cifs//samba?

vsftpd (it might even be preinstalled) https://wiki.debian.org/vsftpd
setup tutorial posted here: https://www.antixforum.com/forums/topic/ftp-for-new-antix-user/

also available, preinstalled:
cd /dir/i/want/to/serve/from && python -m SimpleHTTPServer port_number

or

busybox httpd -p 127.0.0.1:8080 -h /dir/i/want/to/serve/from
(check “busybox httpd –help”. This commandstring might not be correct)

[Anonymous]

I use Caja as a file manager and

and antiX does not ship Caja

and websearch is a thing

and 5 seconds after typing
caja could not display network
into startpage.com searchbox
several potential solutions are at my fingertips.

self-help is an important first step.
If solutions found via websearch fail for your case, post back to report which possible solutions you have already tried, toward solving.

Could not display network:///
Caja cannot handle network locations.

samba is not setup, or is misconfigured?
Someone else might chime in and provide links to the antiX samba docs and video tutorial.

[Member oops]

Wallon wrote:

I have tested my first backup with Timeshift but I receive also some warnings regarding GTK.
…
It works but I have some problems regarding inodes and times …. Antix launch a king of check disk to repare the installation.
It’s not possible to put here the terminal output because there is an automatic reboot after the restore.

Maybe the rsync version need to be newer than the actual antix one, lot of bugs have been fixed from v3.1.3 to 3.2.3:

chroot> rsync --version
rsync  version 3.1.3  protocol version 31

https://rsync.samba.org/

[Anonymous]

# service apache2 restart
bash: service: command not found

# whereis service
service: /usr/sbin/service /etc/service /usr/share/man/man8/service.8.gz

???

—————————————————————————–

So this was my path:

# apt install backuppc
$Conf{SmbClientPath} = ‘/usr/bin/smbclient’ is not a valid executable program
# apt install smbclient
# apt purge backuppc
# apt install backuppc
$Conf{NmbLookupPath} = ‘/usr/bin/nmblookup’ is not a valid executable program
# apt install samba-common-bin
# apt purge backuppc
# apt install backuppc

now it works.

This is the first time I encounter that package’s dependencies are not auto-resolved, I expected packages to be installed with one command, especially on a distro like Debian stable…
😕 🤨 🤔

Thank you for your push, sybok

[Member Robin]

Hello all,
I can confirm this behaviour, I have observed these continuous regular spikes also for a long period of time, but not in the 19.x version which I don’t have installed due to hardware driver issues, but in 17.4.1. (having installed all upgrades from apt near-term always).

Whether this is true already in a fresh (persistent )install I can’t tell at the moment, but it has happened in a varying intensity. I thought of the connection to the samba file server being the cause, and also suspected NTP of this, since when I remember things correctly it attracted my attention for the first time after I activated one of these. But also it may have started for the first time after installing virtualbox potentially.

Since there seem to be transmitted very small amounts of data on every spike only, they are hidden by normal traffic usually and will not show up before several minutes of idle state of network connection, giving the conky display a chance to zoom up scale of network activity monitor.

I will report here when I observe this behaviour again, right at the moment I can’t see the spikes at all, though just having restarted NTP. Strange thing this.

• This reply was modified 2 years, 4 months ago by Robin.
• This reply was modified 2 years, 4 months ago by Robin. Reason: word order corrected

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