Search Results for 'samba'

Hi
I have just installed Antix 32bit to a 10zig thin client to use as a samba server and spare machine. I have only had time for a quick explore but I am really liking the responsiveness and features.
I used to use puppy Linux for many years, but it looks like the support has dropped off a lot since I have been away.
Anyway, looking forward to getting stuck in and no doubt coming up with a few questions.

• This topic was modified 1 year, 7 months ago by Gary101.

Hello!

I am preparing new ISOS 32 and 64bits with some cosmetic improvements and refined choices. I stared about 10 days ago and was stopped by the installer crashing on my new respins when testing in Virtualbox : the installed DOES NOT SEE the storage unit!

The base I use is antiX 19.

This is what the output of the line in error looks like when I start minstall manually from the console:

SErr #18: “lsblk: unknown column: -bJo\nlsblk: TYPE,NAME,UUID,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,MODEL,PARTFLAGS: not a block device\n”

I have pinpointed when and how : I had first thought it might be caused by me removing some packages that I should not have removed (it had happened before), so I reverted to a previous version I had done which works perfectly, and I restarted rebuilding on it.

Then I decided to do all I wanted in it except one thing : I didn’t update the distro before redoing the snapshot!

And this one works!

So I reused it immediatly, installed, this time I updated, redid a respin and BAM ! This time the installer does not see the virtual disk!

This is why I am now coming here to ask for help.

I have prepared some files, screenshots, outputs of console, logs from the live where the installer fails.

$ su-to-root -X -c minstall
Gkr-Message: 19:13:16.809: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
Gkr-Message: 19:13:21.120: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
Gkr-Message: 19:13:21.122: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
qt5ct: using qt5ct plugin
QFSFileEngine::open: No file name specified
Cannot write to installer log: “/var/log/minstall.log”
Installer version: 1.5.4
+++ void MInstall::startup() +++
check for remastered home demo folder: false
Exec #1: du -sb /live/aufs/boot
Exit #1: 0 QProcess::ExitStatus(NormalExit)
linuxfs file is at : “/live/boot-dev/antiX/linuxfs”
Exec #2: dd if=/live/boot-dev/antiX/linuxfs bs=1 skip=20 count=2 status=none 2>/dev/null | od -An -tdI
Exit #2: 0 QProcess::ExitStatus(NormalExit)
linuxfs compression type is “4” compression factor is 25
Exec #3: df /live/linux –output=used –total |tail -n1
Exit #3: 0 QProcess::ExitStatus(NormalExit)
linuxfs file size is 2756706304 rootfs file size is 0
Minimum space: 268435456 (boot), 3830448128 (root)
Exec #4: uname -m | grep -q i686
Exit #4: 0 QProcess::ExitStatus(NormalExit)
Exec #5: grep -q 64 /sys/firmware/efi/fw_platform_size
SErr #5: “grep: /sys/firmware/efi/fw_platform_size: Aucun fichier ou dossier de ce type\n”
Exit #5: 2 QProcess::ExitStatus(NormalExit)
uefi = false
+++ void MInstall::setupAutoMount(bool) +++
Exec #6: ps -e | grep ‘udisksd’
SOut #6: ” 2590 ? 00:00:00 udisksd\n”
Exit #6: 0 QProcess::ExitStatus(NormalExit)
Exec #7: egrep -l ‘^[^#].*mdadm (-I|–incremental)’ /lib/udev/rules.d
SErr #7: “grep: /lib/udev/rules.d: est un dossier\n”
Exit #7: 2 QProcess::ExitStatus(NormalExit)
MkPath(SUCCESS): “/run/udev/rules.d”
Exec #8: echo ‘SUBSYSTEM==”block”, ENV{UDISKS_IGNORE}=”1″‘ > /run/udev/rules.d/91-mx-udisks-inhibit.rules
Exit #8: 0 QProcess::ExitStatus(NormalExit)
Exec #9: udevadm control –reload
Exit #9: 0 QProcess::ExitStatus(NormalExit)
Exec #10: udevadm trigger –subsystem-match=block
Exit #10: 0 QProcess::ExitStatus(NormalExit)
Exec #11: /bin/ls -1 /home | grep -Ev ‘(lost\+found|demo|snapshot)’ | grep -q [a-zA-Z0-9]
Exit #11: 1 QProcess::ExitStatus(NormalExit)
check for possible snapshot: false
+++ void MInstall::setupkeyboardbutton() +++
Exec #12: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
Exit #12: 0 QProcess::ExitStatus(NormalExit)
Exec #13: locale -a | grep -Ev ‘^(C|POSIX)\.?’ | grep -E ‘utf8|UTF-8’
Exit #13: 0 QProcess::ExitStatus(NormalExit)
Exec #14: grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus
Exit #14: 1 QProcess::ExitStatus(NormalExit)
Exec #15: dpkg -s samba | grep ‘^Status.*ok.*’ | sed -e ‘s/.*ok //’
SErr #15: “dpkg-query: le paquet \xC2\xAB\xC2\xA0samba\xC2\xA0\xC2\xBB n’est pas install\xC3\xA9 et aucune information n’est disponible\nUse dpkg –info (= dpkg-deb –info) to examine archive files.\n”
Exit #15: 0 QProcess::ExitStatus(NormalExit)
+++ void MInstall::buildServiceList() +++
+++ void MInstall::updatePartitionWidgets(bool) +++
+++ void BlockDeviceList::build(MProcess&) +++
Exec #16: partprobe -s
SOut #16: “/dev/sda: msdos partitions 1 2\n/dev/sr0: msdos partitions 2\n/dev/zram0: loop partitions 1\n”
SErr #16: “Warning: Unable to open /dev/sr0 read-write (Syst\xC3\xA8me de fichiers accessible en lecture seulement). /dev/sr0 has been opened read-only.\nWarning: Unable to open /dev/sr0 read-write (Syst\xC3\xA8me de fichiers accessible en lecture seulement). /dev/sr0 has been opened read-only.\nWarning: Unable to open /dev/sr0 read-write (Syst\xC3\xA8me de fichiers accessible en lecture seulement). /dev/sr0 has been opened read-only.\n”
Exit #16: 0 QProcess::ExitStatus(NormalExit)
Exec #17: blkid -c /dev/null
SOut #17: “/dev/loop0: TYPE=\”squashfs\”\n/dev/sda1: UUID=\”74321680-92b7-48cb-87af-43cce4a47526\” TYPE=\”swap\” PARTUUID=\”9e343378-01\”\n/dev/sda2: LABEL=\”rootantiX19\” UUID=\”cc346124-ba70-4900-ab3a-8c124b99e21d\” TYPE=\”ext4\” PARTUUID=\”9e343378-02\”\n/dev/sr0: UUID=\”2021-09-13-07-00-58-00\” LABEL=\”antiXLIVE\” TYPE=\”iso9660\” PTUUID=\”5082fcfe\” PTTYPE=\”dos\”\n/dev/zram0: LABEL=\”SWAP_ZRAM0\” UUID=\”32e1350d-9255-48ba-9499-85596e8fccf3\” TYPE=\”swap\”\n”
Exit #17: 0 QProcess::ExitStatus(NormalExit)
Exec #18: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,MODEL,PARTFLAGS
SErr #18: “lsblk: unknown column: -bJo\nlsblk: TYPE,NAME,UUID,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,MODEL,PARTFLAGS: not a block device\n”
Exit #18: 32 QProcess::ExitStatus(NormalExit)
Name Size Model FS | isDrive isGPT isBoot isESP isNative isStart isNasty
Exec #19: lsblk -T -bJo TYPE,NAME,UUID,SIZE,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
Exit #19: 32 QProcess::ExitStatus(NormalExit)
Segmentation fault
[demo@antix1:/usr/share/applications/antix]
$

(same result using sudo).

Here is a full zip also including the content from /etc/apt and /var/live : https://nextcloud.orditux.org/s/Lo3qoGg9jf6DBEQ

Thanks for your help! “:-)

Attachments:

1. 

   drive-not-seen-2021-09-13_19-04.png
   

2. 

   drive-not-seen-2-2021-09-13_19-04.png
   

3. 

   minstall-direct-log-2021-09-13_19-24.png
   

1. synaptic-history-last-update-sept-13-before-the-crash.txt

[Member Robin]

Hallo Amiganer,

Vielleicht ist die Konfigurationsdatei beschädigt. Versuche es manuell:

Als Rechteeinstellung sollte 600 genügen. 777 geht natürlich auch, aber bedenke daß die Datei Dein Windows-Paßwort enthalten wird.
Mache Dir zuerst durch Verschieben der vorgefundenen Datei connectshares.conf im Vezeichnis /home/demo/.config/connectshares/ z.B. zu connectshares.conf.bak eine Sicherungskopie.
Nun mache eine Kopie der Datei template.conf und nenne diese Kopie connectshares.conf
Öffne diese neu angelegte Datei, also /home/demo/.config/connectshares/connectshares.conf mit einem Texteditor (z.B. leafpad oder geany, NICHT mit einer Textverarbeitung wie z.B. LibreOffice o.ä.)

Jetzt mußt Du folgendes in dieser neu angelegten Connectshare-Konfigurationsdatei ausfüllen:

Ersetze alle spitzen Klammern und ihren Inhalt in den folgenden Einträgen komplett durch die entsprechenden Zugangsdaten. Lasse alle anderen Einträge offen. Beachte Groß- und Kleinschreibung.

# Netzwerkname des Windows-Rechners
REMOTE=<Rechnername>

# Einhängen freigegebener Windows-Netzwerkressourcen aktivieren
SAMBA=y

# Arbeitsgruppenname der Windows-Arbeitsgruppe.
WORKGROUP=<Arbeitsgruppe>

# Bezeichnung der Freigaben auf dem Windows-Rechner. Mehrere Einträge
# durch Kommata trennen. Auch der letzte Eintrag muß ein abschließendes
# Komma bekommen, genau wie ein einzelner Eintrag. Den Kommata
# darf kein Leerzeichen folgen.
SHARESUSER=<Freigabename(n),>

# Automatisches anmelden für die Freigaben auf dem Windows-Rechner
CREDAUTO=y

# Anmeldename und Paßwort eines Windows-Benutzerkontos, das Zugriff
# auf die in Windows freigegebenen Ressourcen hat.
CREDNAME=<Windows-Benutzername>
CREDPASS=<Windows-Benutzerpaßwort>

Speichere die Datei.

Wenn Du alle Einträge fehlerfrei vorgenommen hast, sollte eine Anmeldung mit dem Menüeintrag »Connectshares« sofort funktionieren, wenn eine Netzwerkverbindung zum Windows-Rechner besteht. Ein Aufruf von »Connectshares Konfiguration« ist nicht nochmals erforderlich.

Vergiß nicht, Dich hinterher wieder mit dem Menüeintrag »Disconnectshares« abzumelden, bevor Du die Netzwerkverbindung trennst. Es kann sonst bei einem nächsten Anmeldeversuch Probleme geben.

Robin

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

Moin Moin.

Ich habe gerade meinem Netbook Asus 1005HAG (1GB RAM, 160GB HDD, 1.667MHz Atom, 32bit) ein neues Leben mit antiX eingehaucht.
Mein Desktop läuft unter Windows 10. Da ich vorher auf dem Netbook Min 19.3 Xfce drauf hatte, weiß ich, dass die Netzwerk-Freigaben auf dem Desktop sichtbar sind. Da der 32bit-Support dort 2023 ausläuft, wäre das der zweite Tot des Netbook, was ich nicht will. Ich hoffe Debian wird noch lange Zeit nicht tun…

Da ich auf Linux nicht so fitt bin, brächte ich jetzt bitte eure Hilfe, ich bekomme auf dem Netbook die Freigaben nicht zu sehen. Bei Mint konnte man im Dateimanager “smb://….” eingeben und bekam die Freigaben angezeigt. Ich habe herausbekomme, dass “smb” hier für “Samba” steht. Darum habe ich nach dem Systemupdate auch noch ein “sudo apt install samba” gemacht und dann versucht, im Connectionshare die Sache so einzustellen, das da was kommt, doch das gelingt nicht.

Darum habe ich da ein paar Fragen:
Was ist ein Netbiosname? In der Config-Datei steht etwas von einem “Netbiosname”, was genau ist das und wie bekomme ich den raus? Geht nicht auch die IP wie bei Mint? Der Router weißt allen Geräten immer die selbe IP zu, das habe ich so eingestellt.

Welche Packete müßten noch installiert werden, damit es funktioniert?
Wenn ich dann das Connectionshare verwenden muß, was muß ich da wo eintragen? DA er mir immer sagt, dass die config-Datei nicht korrekt sei, habe ich da wohl noch einige Fehler drin.

Wie kann ich die Freigaben dann auch unter dem Datei-Manager sichtbar machen (so oder ähnlich wie in Mint)?

Danke füe eure Hilfe.

MfG
Christian

Moin Moin.

Hier die kleine Geschichte vorab: Ich wollte meinen NetBook (Asus 1005HAG) ein neues Leben schenken, darum habe ich mich nach einem neuen Betriebssystem für den kleinen (nur 1GB RAM, 1.667MHz Atom, 32bit) umgesehen. Als erstes ist mir Mint 19.3 Xfce in die Finger gekommen. ISO auf einen Stick, installiert wunderbar. Doch: Die Unterstützung für 32bit läuft 2023 aus, das wäre der zweite Tot für den NetBook gewesen. Auf der Suche ist mir dann antiX Linux aufgefallen, es verspricht ja besonders für alte Notebooks zu sein und basiert auf Debian, die es schon lange gibt und hoffentlich 32bit noch lange unterstützen werden. Auf einen Stick installiert, WiFi eingerichtet, updates gemacht fertig.

Da ich mich nicht so auskenne, habe ich jetzt ein Problem mit dem Windows Netzwerk. Bei Mint konnte man in Datei-Manager einfach “SMB://192.168.x.x” eingeben (user und passwort beantworten) und ich sah, was der Desktop so für mich parat hatte. Doch das habe ich bis jetzt nicht auf dem antiX hinbekommen.
Ich habe bis jetzt ein “sudo apt install samba” gemacht, mich in dem “Connectionshare” umgesehen und dort versucht, eine Verbindung zu bekommen. Hier bekomme ich immer gesagt, dass die Bespiel-config Datei nicht in Ordnung ist.
Was genau ist ein “NETBiosname” und wie bekomme ich den raus?

Der Desktop läuft unter Windows 10, smb1 fällt also raus, wie ich gesehen habe, ist das auch buggy. DA ich die Sachen unter Mint gesehen habe, denke ich, ist der zumindest korrekt konfiguriert.

Da ich nicht so viel weiß, bitte ich hier um Hilfe.

1.
Was muß ich alles installieren, damit ein Zugriff auf die Netzwerk-Freigaben des Desktop möglich sind? Ich habe bereits im Router dafür gesorgt, dass meine Geräte immer die selbe IP bekommen.

2.
Wie geht es dann weiter? Da ich im Datei-Manager kein Feld gefunden habe, wo man das “smb://…” eingeben kann, bin ich hier als Neuling schon überfragt. In der config des Connectionshare steht bei vielen Parametern, dass wenn die leer sind, man bei Bedarf gefragt wird (username/passowrt zB).

Bitte helft mir.

MfG
Christian

• This topic was modified 1 year, 8 months ago by Amiganer. Reason: errata

————————————————————————
The Debian Project https://www.debian.org/
Debian 11 “bullseye” released press@debian.org
August 14th, 2021 https://www.debian.org/News/2021/20210814
————————————————————————

After 2 years, 1 month, and 9 days of development, the Debian project is
proud to present its new stable version 11 (code name “bullseye”), which
will be supported for the next 5 years thanks to the combined work of
the Debian Security team [1] and the Debian Long Term Support [2] team.

1: https://security-team.debian.org/
2: https://wiki.debian.org/LTS

Debian 11 “bullseye” ships with several desktop applications and
environments. Amongst others it now includes the desktop environments:

* Gnome 3.38,
* KDE Plasma 5.20,
* LXDE 11,
* LXQt 0.16,
* MATE 1.24,
* Xfce 4.16.

This release contains over 11,294 new packages for a total count of
59,551 packages, along with a significant reduction of over 9,519
packages which were marked as “obsolete” and removed. 42,821 packages
were updated and 5,434 packages remained unchanged.

“bullseye” becomes our first release to provide a Linux kernel with
support for the exFAT filesystem and defaults to using it for mount
exFAT filesystems. Consequently it is no longer required to use the
filesystem-in-userspace implementation provided via the exfat-fuse
package. Tools for creating and checking an exFAT filesystem are
provided in the exfatprogs package.

Most modern printers are able to use driverless printing and scanning
without the need for vendor specific (often non-free) drivers.
“bullseye” brings forward a new package, ipp-usb, which uses the vendor
neutral IPP-over-USB protocol supported by many modern printers. This
allows a USB device to be treated as a network device. The official SANE
driverless backend is provided by sane-escl in libsane1, which uses the
eSCL protocol.

Systemd in “bullseye” activates its persistent journal functionality, by
default, with an implicit fallback to volatile storage. This allows
users that are not relying on special features to uninstall traditional
logging daemons and switch over to using only the systemd journal.

The Debian Med team has been taking part in the fight against COVID-19
by packaging software for researching the virus on the sequence level
and for fighting the pandemic with the tools used in epidemiology; this
work will continue with focus on machine learning tools for both fields.
The team’s work with Quality Assurance and Continuous integration is
critical to the consistent reproducible results required in the
sciences. Debian Med Blend has a range of performance critical
applications which now benefit from SIMD Everywhere. To install packages
maintained by the Debian Med team, install the metapackages named med-*,
which are at version 3.6.x.

Chinese, Japanese, Korean, and many other languages now have a new Fcitx
5 input method, which is the successor of the popular Fcitx4 in
“buster” ; this new version has much better Wayland (default display
manager) addon support.

Debian 11 “bullseye” includes numerous updated software packages (over
72% of all packages in the previous release), such as:

* Apache 2.4.48
* BIND DNS Server 9.16
* Calligra 3.2
* Cryptsetup 2.3
* Emacs 27.1
* GIMP 2.10.22
* GNU Compiler Collection 10.2
* GnuPG 2.2.20
* Inkscape 1.0.2
* LibreOffice 7.0
* Linux kernel 5.10 series
* MariaDB 10.5
* OpenSSH 8.4p1
* Perl 5.32
* PHP 7.4
* PostgreSQL 13
* Python 3, 3.9.1
* Rustc 1.48
* Samba 4.13
* Vim 8.2
* more than 59,000 other ready-to-use software packages, built from
more than 30,000 source packages.

With this broad selection of packages and its traditional wide
architecture support, Debian once again stays true to its goal of being
“The Universal Operating System”. It is suitable for many different use
cases: from desktop systems to netbooks; from development servers to
cluster systems; and for database, web, and storage servers. At the same
time, additional quality assurance efforts like automatic installation
and upgrade tests for all packages in Debian’s archive ensure that
“bullseye” fulfills the high expectations that users have of a stable
Debian release.

A total of nine architectures are supported: 64-bit PC / Intel EM64T /
x86-64 (amd64), 32-bit PC / Intel IA-32 (i386), 64-bit little-endian
Motorola/IBM PowerPC (ppc64el), 64-bit IBM S/390 (s390x), for ARM, armel
and armhf for older and more recent 32-bit hardware, plus arm64 for the
64-bit “AArch64” architecture, and for MIPS, mipsel (little-endian)
architectures for 32-bit hardware and mips64el architecture for 64-bit
little-endian hardware.

If you simply want to try Debian 11 “bullseye” without installing it,
you can use one of the available live images [3] which load and run the
complete operating system in a read-only state via your computer’s
memory.

3: https://www.debian.org/CD/live/

These live images are provided for the amd64 and i386 architectures and
are available for DVDs, USB sticks, and netboot setups. The user can
choose among different desktop environments to try: GNOME, KDE Plasma,
LXDE, LXQt, MATE, and Xfce. Debian Live “bullseye” has a standard live
image, so it is also possible to try a base Debian system without any of
the graphical user interfaces.

Should you enjoy the operating system you have the option of installing
from the live image onto your computer’s hard disk. The live image
includes the Calamares independent installer as well as the standard
Debian Installer. More information is available in the release notes [4]
and the live install images [5] sections of the Debian website.

4: https://www.debian.org/releases/bullseye/releasenotes
5: https://www.debian.org/CD/live/

To install Debian 11 “bullseye” directly onto your computer’s hard disk
you can choose from a variety of installation media such as Blu-ray
Disc, DVD, CD, USB stick, or via a network connection. Several desktop
environments — Cinnamon, GNOME, KDE Plasma Desktop and Applications,
LXDE, LXQt, MATE and Xfce — may be installed through those images. In
addition, “multi-architecture” CDs are available which support
installation from a choice of architectures from a single disc. Or you
can always create bootable USB installation media (see the Installation
Guide [6] for more details).

6: https://www.debian.org/releases/bullseye/installmanual

There has been a lot of development on the Debian Installer, resulting
in improved hardware support and other new features.

In some cases, a successful installation can still have display issues
when rebooting into the installed system; for those cases there are a
few workarounds [7] that might help log in anyway. There is also an
isenkram-based procedure [7] which lets users detect and fix missing
firmware on their systems, in an automated fashion. Of course, one has
to weigh the pros and cons of using that tool since it’s very likely
that it will need to install non-free packages.

7:
https://www.debian.org/releases/bullseye/amd64/ch06s04#completing-installed-system

In addition to this, the non-free installer images that include firmware
packages [8] have been improved so that they can anticipate the need for
firmware in the installed system (e.g. firmware for AMD or Nvidia
graphics cards, or newer generations of Intel audio hardware).

8:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

For cloud users, Debian offers direct support for many of the best-known
cloud platforms. Official Debian images are easily selected through each
image marketplace. Debian also publishes pre-built OpenStack images [9]
for the amd64 and arm64 architectures, ready to download and use in
local cloud setups.

9: https://cloud.debian.org/images/openstack/current/

Debian can now be installed in 76 languages, with most of them available
in both text-based and graphical user interfaces.

The installation images may be downloaded right now via bittorrent [10]
(the recommended method), jigdo [11], or HTTP [12]; see Debian on
CDs [13] for further information. “bullseye” will soon be available on
physical DVD, CD-ROM, and Blu-ray Discs from numerous vendors [14] too.

10: https://www.debian.org/CD/torrent-cd/
11: https://www.debian.org/CD/jigdo-cd/#which
12: https://www.debian.org/CD/http-ftp/
13: https://www.debian.org/CD/
14: https://www.debian.org/CD/vendors

Upgrades to Debian 11 from the previous release, Debian 10 (code name
“buster”) are automatically handled by the APT package management tool
for most configurations.

For bullseye, the security suite is now named bullseye-security and
users should adapt their APT source-list files accordingly when
upgrading. If your APT configuration also involves pinning or
APT::Default-Release, it is likely to require adjustments too. See the
Changed security archive layout [15] section of the release notes for
more details.

15:
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information#security-archive

If you are upgrading remotely, be aware of the section No new SSH
connections possible during upgrade [16].

16:
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information#ssh-not-available

As always, Debian systems may be upgraded painlessly, in place, without
any forced downtime, but it is strongly recommended to read the release
notes [17] as well as the installation guide [18] for possible issues,
and for detailed instructions on installing and upgrading. The release
notes will be further improved and translated to additional languages in
the weeks after the release.

17: https://www.debian.org/releases/bullseye/releasenotes
18: https://www.debian.org/releases/bullseye/installmanual

About Debian
————

Debian is a free operating system, developed by thousands of volunteers
from all over the world who collaborate via the Internet. The Debian
project’s key strengths are its volunteer base, its dedication to the
Debian Social Contract and Free Software, and its commitment to provide
the best operating system possible. This new release is another
important step in that direction.

Contact Information
——————-

For further information, please visit the Debian web pages at
https://www.debian.org/ or send mail to <press@debian.org>.

--
Brian Masinick

[Moderator christophe]

Devo dizer que não sou um especialista, de forma alguma. Eu gosto de habilitá-lo – “apenas no caso”.

https://averagelinuxuser.com/linux-firewall/

Aqui está um pequeno trecho desse link, que expressa minhas idéias sobre segurança na internet / web:

Mas não se preocupe, seu Linux ainda está seguro, mesmo sem um firewall ativo. Por padrão, a maioria das distribuições como Ubuntu e Linux Mint não tem portas abertas, portanto, seu computador não pode ser acessado por invasores.

No entanto, recomendo ativar um firewall. É melhor estar seguro do que pesaroso. Um firewall não usa muitos recursos, mas adiciona uma camada extra de segurança. Um usuário inexperiente pode abrir acidentalmente algumas portas sem saber, por exemplo, instalando samba, ssh, apache. Nesse caso, o firewall ainda protegerá o sistema de acessos externos.

MAS – Eu também uso um capacete sempre que dirijo um carro.

Só estou brincando sobre esse último …;)

——————————————-
original text:

I have to say I am not an expert, by any means. I like to enable it — “just in case.”

https://averagelinuxuser.com/linux-firewall/

Here’s a short excerpt from that link, which expresses my thoughts on internet/web safety:

But don’t worry, your Linux is still secure even without an active firewall. By default, most of the distributions such as Ubuntu and Linux Mint have no open ports so your computer cannot be accessed by intruders.

Nevertheless, I recommend to activate a firewall. It is better to be safe than sorry. A firewall does not use many resources, but it adds an extra layer of security. An inexperienced user can accidentally open some ports without knowing it, for example, by installing samba, ssh, apache. In this case, the firewall will still protect the system from outside access.

BUT — I also wear a crash helmet whenever I ride in a car.

Only joking about that last one… 😉

confirmed antiX frugaler, since 2019

[Member Xecure]

You could add the mounting command to /etc/rc.local (before exit), so that it tries to mount the samba command just after starting everything else in the system.
For example:
(sleep 4 && mount 192.168.0.1:/user_area /home) &
and see if it does it for you automatically, just a few seconds after the desktop comes up.

• This reply was modified 1 year, 10 months ago by Xecure.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Xecure]

Hi.

You could try your luck with Connectshares. Others have had good experience using it in antiX for the past few years. It should be included in antiX (from the Control Centre > Shares). If it isn’t,
sudo apt install connectshares-antix

You can search the forum for samba related topics too. I am no expert and can only give recommendations based on past topics.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

I just installed the latest antix version on my hd. I’m using rox-icewm. In my fstab I gave three smb entries that work in other distros but not antix when it comes to mounting them on reboot. I have to go into the terminal and type sudo mount -a everytime. Is there a way to have them automount?

Thanks!!!

Randy

[Anonymous]

but he has massive file transfers and

disk-to-disk?
across a LAN?
downloading from an external network? FTP? NFS? SAMBALAMBALOO?

https://unix.stackexchange.com/questions/48399/fast-way-to-copy-a-large-file-on-a-lan

mbuffer!

The biggest bottleneck in transferring large files over a network is, by far, disk I/O. The answer to that is mbuffer or buffer. They are largely similar but mbuffer has some advantages. The default buffer size is 2MB for mbuffer and 1MB for buffer. Larger buffers are more likely to never be empty. Choosing a block size which is the lowest common multiple of the native block size on both the target and destination filesystem will give the best performance.

Buffering is the thing that makes all the difference! Use it if you have it! If you don’t have it, get it! Using (m}?buffer plus anything is better than anything by itself. it is almost literally a panacea for slow network file transfers.

If you’re transferring multiple files use tar to “lump” them together into a single data stream. If it’s a single file you can use cat or I/O redirection. The overhead of tar vs. cat is statistically insignificant so I always use tar (or zfs -send where I can) unless it’s already a tarball. Neither of these is guaranteed to give you metadata (and in particular cat will not). If you want metadata, I’ll leave that as an exercise for you.

Finally, using ssh for a transport mechanism is both secure and carries very little overhead. Again, the overhead of ssh vs. nc is statistically insignificant.

Regardless of O/S, optimizations are probably avilable via tweaks to sysctl parameters, and choice of filesystem + settings. Changing O/S instead of identifying//fixing the bottleneck seems like misdirected effort.
.

[Member melodie]

olsztyn wrote:

The main reason to disqualify Pcmanfm for my use: It does not seem capable of addressing network shares.

you might try gigolo along with PCManFM. I haven’t had the need for such shares in a while, I use more sshfs or ssh once a while, but I remember it solved it completely, once the connection was done, I could see the related network in the left side of the file manager.
Also in PCManFM you can visit the menu “Go to > Networks” and you land at the URI ” network:/// ” (Probably meant to use Samba to reach to Windows boxes, but anyway gigolo would let you connect your regular other linux boxes).

What I like about PCManFM : it is simple to use and to configure, has anything I need, even dual side panel when needed : when you have two tabs open, you can hit “F3” or use the “View > Double Pane Mode” entry menu. (I guess the names in English, I have it in French).

There are a few more things others appreciate. There is a list here : https://wiki.lxde.org/en/PCManFM and modules you can write an load (see in Edition > Preferences).

🙂

[Member olsztyn]

Thanks skidoo. I have run into these searching web. These are primarily about improving read/write performance of Samba server, which is not my case…
If I was not clear enough, it is antiX as client accessing existing NAS servers, not Samba server that is in need of performance improvement. One might argue that perhaps the issue might still be on NAS servers, but then how come Windows client enjoys fast write performance and Linux very slow.
Still searching web for some tips relevant to case. Anyway thanks for your care to point me to some resources.
Nobody having write performance issues using antiX as client writing to NAS? I guess I should assume it is just me…
On the other hand, if others are experiencing the same and a viable solution was found on client side then I would appreciate if such solution is considered for future default configuration.
Thanks again and regards…

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

[Anonymous]

a suitable websearch query: debian smb performance slow

3 links from page one search results containing suggestions:
https://eggplant.pro/blog/faster-samba-smb-cifs-share-performance/
https://wiki.archlinux.org/title/Samba#Improve_throughput
https://superuser.com/questions/713248/home-file-server-using-samba-has-slow-read-and-write-speed
Howabout try six at least seven of the various suggested tweaks, then report back stating “toward solving the problem, here’s what I have tried…”

[Member Budgie]

I think the logshows a problem I do not understand but here is the result of the checks:

alastair@OldDell32:~
$ ls -l $HOME/Downloads/pcloud
-rwxr-xr-x 1 alastair alastair 58189846 May 12 16:32 /home/alastair/Downloads/pcloud
alastair@OldDell32:~
$ ls -l $HOME/Downloads/pcloud
-rwxr-xr-x 1 alastair alastair 58189846 May 12 16:32 /home/alastair/Downloads/pcloud
alastair@OldDell32:~
$ cat ~/.desktop-session/startup
#!/bin/bash
# Puts connman monitor icon on the taskbar
#connman-gtk & 

# Puts a volume icon on the taskbar
volumeicon & 

# Enable/Disable automounting
automount-antix &

# Puts a flag on the taskbar to show which keyboard is being used if more than 1 keyboard layout is detected
fbxkb-start &

# Added KeePassXC manually by edit to startup 12-05-21
keepassxc &
sleep 3

# Added pCloud manually by edit to startup 12-05-21
exec /home/Downloads/pcloud &
sleep 1

# Uncomment for easy search from the taskbar
#search-bar-icon &

# Uncomment the following line to mount Samba and/or NFS shares
#connectshares &

# Uncomment to show the configuration gui of a running ssh-conduit-x11vnc server
#ssh-conduit-x11vnc.sh gui &

# Uncomment to use clipboard manager
#clipit &

# Use pkexec (you need to install policykit-1-gnome)
# /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 &

# Uncomment to show wicd networking monitor
#wicd-client -t &
#grep -q "START_DAEMON=no" /etc/default/wicd || wicd-client -t &

# Uncomment after installing apt-notifier
#apt-notifier & 

# Used on live system only

#Enable Mouse Configuration at Startup
#ds-mouse -all &

#Enable connman_connect
#connman_connect &

alastair@OldDell32:~
$ cat ~/.desktop-session/log
desktop-session: started Thu 13 May 13:27:36 BST 2021 start_time: 47.74
desktop-session: pid: 2667
desktop-session: logging to: /home/alastair/.desktop-session/log
desktop-session: Raw code passed ''
desktop-session: launch  @ 4796
desktop-session: icewm
desktop-session: display_alt_desktop_window=false
desktop-session: look up executable for icewm
desktop-session: save desktop code: rox-icewm
desktop-session: Exporting desktop Variables:
desktop-session: DESKTOP_SESSION_CODE=rox-icewm
desktop-session: DESKTOP_SESSION_WM=icewm
desktop-session: DESKTOP_SESSION_IM=rox
desktop-session: run: /usr/local/lib/desktop-session/ds-config-check
desktop-session: run: amixer sset Master -M 45%
Simple mixer control 'Master',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 20 [44%] [-16.50dB] [off]
  Front Right: Playback 20 [44%] [-16.50dB] [off]
desktop-session: run: /usr/bin/icewm-session
desktop-session: Checking for running window manager @ 4835
icewm-session: Warning: Failed to execute icewmbg: No such file or directory
desktop-session: Window manager running or setup forced, setting up desktop @ 4946
desktop-session: Delaying session startup by 2 seconds
desktop-session: run: rox --pinboard=antiX-icewm &
desktop-session: run: desktop-session-wallpaper
desktop-session: Destination file is newer than the Source file.
desktop-session: run: eval blueman-applet
desktop-session: run: eval clipit
desktop-session: run: eval /usr/bin/gnome-keyring-daemon --start --components
gnome-keyring-daemon: Missing argument for --components
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
desktop-session: run: eval /usr/bin/gnome-keyring-daemon --start --components
gnome-keyring-daemon: Missing argument for --components
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
desktop-session: run: eval /usr/bin/gnome-keyring-daemon --start --components
gnome-keyring-daemon: Missing argument for --components
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
desktop-session: run: eval gsettings-data-convert
desktop-session: run: eval /usr/lib/notify-osd/notify-osd
/usr/local/lib/desktop-session/lib-desktop-session.sh: line 72: /usr/lib/notify-osd/notify-osd: No such file or directory
desktop-session: run: eval system-config-printer-applet
desktop-session: run: eval xdg-user-dirs-update xdg-user-dirs-update
Invalid argument xdg-user-dirs-update
qt5ct: using qt5ct plugin

(clipit:2803): dbind-WARNING **: 13:27:50.812: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files

** (clipit:2803): WARNING **: 13:27:50.930: Binding '<Ctrl><Alt>H' failed!

qt5ct: D-Bus global menu: no

(blueman-applet:2795): dbind-WARNING **: 13:27:56.909: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
qt5ct: D-Bus system tray: no

** (rox:2771): WARNING **: 13:27:58.889: Existing ROX-Filer process is not responding! Try with -n

** (rox:2859): WARNING **: 13:27:59.324: SOAP message sender window was destroyed before I 
could read it.
qt5ct: custom style sheet is disabled
desktop-defaults-run -fm --follow  
rox-filer  
desktop-defaults-run -fm --follow  
rox-filer  
roxterm  
roxterm  
alastair@OldDell32:~