Search Results for 'samba'

[Member olsztyn]

anticapitalista wrote:

@Sybok – yes there is an issue on Testing. It needs some python3 packages that haven’t yet migrated from sid.

Just to mention, samba 2.4.17.4 appears to install with no issues on antiX 22 SID/Bookworm/SID. So looks like fixes are on the way…
Samba version is 2.4.17 as settled for Debian 12 Bookworm release, but modified for Nosystemd.

• This reply was modified 3 months, 2 weeks ago by olsztyn.
• This reply was modified 3 months, 2 weeks ago by olsztyn.

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

[Member sybok]

I wonder where the issue described by @spaz comes from.

@anticapitalista: Thanks for the all the info (on both stable and testing).
Fortunately, testing’s issue does not trouble me currently since I do not have samba installed. 🙂 Not sure about others.

If you have to reinstall antiX for some reason from ISO you’ll notice much work will have to be done until basic things like email are back to normal.

Probably, when upgrading to a new antiX version from ISO it is not a good idea to keep (or copy) complete ./home folder from previous installation, since multiple version mismatches of all the config files living there are to be expected. Also some program specific files need to be treated one by one, following the upgrade instructions of the respective program rather than copying the old files 1:1 to the new version.

Part 1:
Claws Mail.

In order to all emails received and sent as well as all existing email account setup from an old antiX installation to a new one (e.g. on a different PC) some steps are to be observed:

1.) Copy complete the following folders recursively to the new antiX system, matching your email account names assigned by claws mail:

   ~/.claws-mail
   ~/<account.name-1>
   ~/<account.name-2>
   ...

(You need to preserve/adapt ownership while copying. You need to preserve permissions of all files and folders while copying)

Start Claws-Mail. Everything from your old system should be present and usable immediately.

2.) In case you have used use S/MIME encryption (see Claws-Mail email encryption thread) you will notice existing sent or received encrypted emails are not readable on the new system.
From claws-mail menu bar „Configuration” choose „Plugins and Addons”, activate the plugins

       PGP/core
       PGP/inline
       PGP/MIME
       S/MIME

Accept and close claws-mail

Additionally copy the complete folder recursively to the fresh antiX system (Don’t apply this when you already have created a gpg key on the new system, since it will get lost):

    ~/.gnupg

(Again, you need to preserve/adapt ownership while copying. You need to preserve permissions of all files and folders while copying)

After restart of claws-mail all old encrypted emails should be readable again immediately.

—–
General hint: Don’t use samba / connectshare for file copy here, it will remove/change ownership and permissions while transferring. If using an USB stick for transfer it must be formatted ext4. Don’t use fat/fat32/exfat formatted file systems for transfer, it will remove/change ownership and permissions.

As a safe alternative transfer method you can use the scp command in console window:

  scp -rp ~/.claws-mail <user@host:path>
  scp -rp ~/<account.name> <user@host:path>
  scp -rp ~/.gpg <user@host:path>

(this will transfer all files via SSH to the target PC)

Also you can simply copy the folders in zzzFM by drag and drop (as long neither source nor target are remote) if both file systems are formatted to ext4 (ext2 and ext3 should be fine also).

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

[Forum Admin anticapitalista]

On default antiX-21/22 ie with Debian bullseye repos, I see no issues

 apt install samba
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  python3-samba samba-common samba-common-bin tdb-tools
Suggested packages:
  bind9 bind9utils ctdb ldb-tools smbldap-tools winbind heimdal-clients
Recommended packages:
  python3-gpg attr samba-dsdb-modules samba-vfs-modules
The following NEW packages will be installed:
  python3-samba samba samba-common samba-common-bin tdb-tools
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,741 kB of archives.
After this operation, 39.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

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

antiX with runit - leaner and meaner.

[Member Robin]

For me in antiX 22 full 64bit (stable) (apt-upgraded from antiX 21, completely no elogind no systemd) nothing is broken.

$ sudo apt-get update
$ sudo apt-get install samba
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
samba ist schon die neueste Version (2:4.13.13+dfsg-1~deb11u5.0nosystemd1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 47 nicht aktualisiert.

$ apt-cache policy samba python3-samba
samba:
  Installiert:           2:4.13.13+dfsg-1~deb11u5.0nosystemd1
  Installationskandidat: 2:4.13.13+dfsg-1~deb11u5.0nosystemd1
  Versionstabelle:
     2:4.17.4+dfsg-3~bpo11+1 100
        100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
 *** 2:4.13.13+dfsg-1~deb11u5.0nosystemd1 500
        500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 Packages
        100 /var/lib/dpkg/status
     2:4.13.13+dfsg-1~deb11u5 500
        500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages
        500 http://security.debian.org bullseye-security/main amd64 Packages
     2:4.6.5+dfsg-2.0nosystemd1 500
        500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bullseye bullseye/main amd64 Packages
python3-samba:
  Installiert:           2:4.13.13+dfsg-1~deb11u5.0nosystemd1
  Installationskandidat: 2:4.13.13+dfsg-1~deb11u5.0nosystemd1
  Versionstabelle:
     2:4.17.4+dfsg-3~bpo11+1 100
        100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
 *** 2:4.13.13+dfsg-1~deb11u5.0nosystemd1 500
        500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bullseye bullseye/nosystemd amd64 Packages
        100 /var/lib/dpkg/status
     2:4.13.13+dfsg-1~deb11u5 500
        500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages
        500 http://security.debian.org bullseye-security/main amd64 Packages

$ inxi -Fzr
System:
  Kernel: 5.10.142-antix.2-amd64-smp arch: x86_64 bits: 64 Desktop: IceWM
    v: 3.3.0 Distro: antiX-21_x64-full Grup Yorum 31 October 2021
Machine:
  Type: Desktop Mobo: ASUSTeK model: P7P55-M v: Rev X.0x
    serial: <superuser required> BIOS: American Megatrends v: 0903
    date: 07/09/2010
CPU:
  Info: dual core model: Intel Core i3 540 bits: 64 type: MT MCP cache:
    L2: 512 KiB
  Speed (MHz): avg: 1951 min/max: 1200/3067 cores: 1: 2630 2: 1284 3: 2007
    4: 1883
Graphics:
  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] driver: radeon
    v: kernel
  Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: radeon
    unloaded: fbdev,modesetting,vesa gpu: radeon resolution: 2048x1152~60Hz
  OpenGL:
    renderer: AMD CEDAR (DRM 2.50.0 / 5.10.142-antix.2-amd64-smp LLVM 11.0.1)
    v: 3.3 Mesa 20.3.5
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio
    driver: snd_hda_intel
  Device-2: AMD Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series]
    driver: snd_hda_intel
  Sound Server-1: ALSA v: k5.10.142-antix.2-amd64-smp running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 2.1 TiB used: 1.76 TiB (83.5%)
  ID-1: /dev/sda vendor: Maxtor model: STM3250318AS size: 232.89 GiB
  ID-2: /dev/sdb type: USB vendor: Generic model: Flash Disk
    size: 58.59 GiB
  ID-3: /dev/sdc type: USB vendor: Toshiba model: External USB 3.0
    size: 1.82 TiB
Partition:
  Message: No partition data found.
Swap:
  ID-1: swap-1 type: partition size: 3.91 GiB used: 3.82 GiB (97.8%)
    dev: /dev/sda2
Sensors:
  System Temperatures: cpu: 43.5 C mobo: 32.0 C gpu: radeon temp: 52.0 C
  Fan Speeds (RPM): cpu: 1278 case-1: 1259
Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list
    1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bullseye bullseye main nosystemd nonfree
  Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list
    1: deb http://deb.debian.org/debian bullseye-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://ftp.de.debian.org/debian/ bullseye-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://ftp.de.debian.org/debian/ bullseye main contrib non-free
    2: deb http://security.debian.org/ bullseye-security main contrib non-free
  No active apt repos in: /etc/apt/sources.list.d/various.list
Info:
  Processes: 262 Uptime: 32d 12h 20m Memory: 7.76 GiB used: 7.03 GiB (90.6%)
  Shell: Bash inxi: 3.3.19

Same result on 32bit antiX 22 (stable): Also no issues with default samba packages.

$ inxi -Fzr
System:
  Kernel: 5.19.0-0.deb11.2-686-pae arch: i686 bits: 32 Desktop: IceWM
    v: 3.1.0 Distro: antiX-21_386-full Grup Yorum 31 October 2021
Machine:
  Type: Other-vm? System: Notebook product: RIM2000 v: N/A
    serial: <superuser required>
  Mobo: Notebook model: RIM2000 serial: <superuser required> BIOS: Phoenix
    v: RIM00F0A date: 05/27/2005
Battery:
  ID-1: BAT0 charge: 59.2 Wh (100.0%) condition: 59.2/65.1 Wh (90.9%)
CPU:
  Info: single core model: Intel Pentium M bits: 32 cache: 2 MiB note: check
  Speed (MHz): 800 min/max: 800/1733 core: 1: 800
Graphics:
  Device-1: NVIDIA NV43M [GeForce Go 6600] driver: nouveau v: kernel
  Display: server: X.Org v: 1.20.11 driver: X: loaded: nouveau
    unloaded: fbdev,modesetting,vesa gpu: nouveau resolution: 1440x900~60Hz
  OpenGL: renderer: NV43 v: 2.1 Mesa 20.3.5
Audio:
  Device-1: Intel 82801FB/FBM/FR/FW/FRW High Definition Audio
    driver: snd_hda_intel
  Device-2: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder
    driver: saa7134
  Sound Server-1: ALSA v: k5.19.0-0.deb11.2-686-pae running: yes
Network:
  Device-1: Marvell 88E8036 PCI-E Fast Ethernet driver: sky2
  IF: eth0 state: down mac: <filter>
  Device-2: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200
  IF: eth1 state: up mac: <filter>
Drives:
  Local Storage: total: 151.75 GiB used: 111.5 GiB (73.5%)
  ID-1: /dev/sda vendor: Seagate model: ST9100823A size: 93.16 GiB
  ID-2: /dev/sdb type: USB vendor: Generic model: Flash Disk
    size: 58.59 GiB
Partition:
  Message: No partition data found.
Swap:
  ID-1: swap-1 type: partition size: 2.16 GiB used: 988.7 MiB (44.7%)
    dev: /dev/sda9
Sensors:
  System Temperatures: cpu: 62.1 C mobo: 52.0 C
  Fan Speeds (RPM): N/A
Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list
    1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/bullseye bullseye main nosystemd nonfree
  Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list
    1: deb http://deb.debian.org/debian bullseye-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://ftp.de.debian.org/debian/ bullseye-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://ftp.de.debian.org/debian/ bullseye main contrib non-free
    2: deb http://security.debian.org/ bullseye-security main contrib non-free
  No active apt repos in: /etc/apt/sources.list.d/various.list
Info:
  Processes: 183 Uptime: 69d 16h 23m Memory: 1.96 GiB used: 1.28 GiB (65.2%)
  Shell: Bash inxi: 3.3.19

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

[Member sybok]

Hi
1) Please post your repositories, output of e.g. ‘inxi -Fzr’.
2) Please also post output of ‘apt-cache policy python3-samba’.

I suspect that the samba packages, repacked without systemd, are not currently correct in the repositories (you use).
Perhaps, @anticapitalista should be informed.

As a reference, antiX-testing I use outputs the below:
A) Install samba:

$ sudo apt install samba
Reading package lists... Done
Building dependency tree... Done
Reading state information... 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:
 python3-samba : Depends: python3-ldb (>= 2:2.1.0) but it is not going to be installed
                 Depends: python3 (>= 3.11~) but 3.10.6-3+b1 is to be installed
E: Unable to correct problems, you have held broken packages.

B) Package candidates:

$ apt-cache policy samba python3-samba
samba:
  Installed: (none)
  Candidate: 2:4.17.4+dfsg-3.0nosystemd1
  Version table:
     2:4.17.4+dfsg-3.0nosystemd1 500
        500 http://ftp.linux.cz/pub/linux/mxlinux/packages/antix/testing testing/nosystemd amd64 Packages
     2:4.17.4+dfsg-2 500
        500 http://ftp.cz.debian.org/debian testing/main amd64 Packages
     2:4.13.14+dfsg-1.0nosystemd1 -1
        100 /var/lib/dpkg/status
     2:4.6.5+dfsg-2.0nosystemd1 500
        500 http://ftp.linux.cz/pub/linux/mxlinux/packages/antix/testing testing/main amd64 Packages
python3-samba:
  Installed: (none)
  Candidate: 2:4.17.4+dfsg-3.0nosystemd1
  Version table:
     2:4.17.4+dfsg-3.0nosystemd1 500
        500 http://ftp.linux.cz/pub/linux/mxlinux/packages/antix/testing testing/nosystemd amd64 Packages
     2:4.17.4+dfsg-2 500
        500 http://ftp.cz.debian.org/debian testing/main amd64 Packages

Of course, the perils of using antiX|Debian-testing is that sometimes something gets broken.
This is expected not to occur in stable (frequently).
My inxi-output is attached.

• This reply was modified 3 months, 2 weeks ago by sybok. Reason: Fix inxi data

Attachments:

1. INXItesting.txt

#################################################################################
Error messages when installing Samba – packages could not be installed – broken packages
#################################################################################
Hi All.
Been using antix past fortnight, so far really enjoying it, thank you so much devs.
I have a lot of tweaks to make and stuff to learn,
but overall it is running really well on a low-spec system. Great work.

I am getting an error message when trying to install Samba as below.

error message from :
sudo apt install samba

——————
Reading package lists…
Building dependency tree…
Reading state information…
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:
samba : Depends: python3-samba but it is not going to be installed
Depends: samba-common-bin (= 2:4.13.13+dfsg-1~deb11u5) but it is not going to be installed
Depends: libwbclient0 (= 2:4.13.13+dfsg-1~deb11u5) but 2:4.17.4+dfsg-2~bpo11+1 is to be installed
Depends: samba-libs (= 2:4.13.13+dfsg-1~deb11u5) but it is not going to be installed

——————

I tried installing all the dependencies mentioned – and received similar error messages to the original one.

——————
I read through this thread
https://www.antixforum.com/forums/topic/how-to-fix-broken-packages-after-upgrade/

Unlike the guy in the thread, I have not added any repos (to my knowledge)
other than the following for brave browser (if that even counts as adding a repo – probably not) :

sudo curl -fsSLo /usr/share/keyrings/brave-browser-archive-keyring.gpg https://brave-browser-apt-release.s3.brave.com/brave-browser-archive-keyring.gpg
echo “deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main”|sudo tee /etc/apt/sources.list.d/brave-browser-release.list
sudo apt update
sudo apt install brave-browser

As suggested to the guy in the thread,
I tried :

sudo apt update && sudo apt upgrade

Then retried install of samba, which returned the same error message as the original :

$ sudo apt install samba
Reading package lists… Done
Building dependency tree… Done
Reading state information… 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:
samba : Depends: python3-samba but it is not going to be installed
Depends: samba-common-bin (= 2:4.13.13+dfsg-1~deb11u5) but it is not going to be installed
Depends: libwbclient0 (= 2:4.13.13+dfsg-1~deb11u5) but 2:4.17.4+dfsg-3~bpo11+1 is to be installed
Depends: samba-libs (= 2:4.13.13+dfsg-1~deb11u5) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

——————–
I am hoping there is some option other than “reinstall your entire system”
as suggested to the guy in the thread I quoted 😛

As I mentioned –
I have not intentionally / consciously installed any repos, and this is something I try to avoid,
and very rarely do (and probably won’t do on this system).
————-
Thanks in advance for any assistance, and to anybody who is developing and participating in supporting such an awesome operating system.

[Member Xunzi_23]

Seems Leafpad was removed due problems with small files on network saves with samba o.a. being lost/failing.

Never seen the issue but I only use it localy, the rework, now mousepad has more functionality but is by no
means as light. As long as leafpad works I will continue using it.

On sid, up to now, it is still doing all I need.

Hi,
I was searching on multiple forum which include antiX forum, MX Linux forum, Linux and Unix forum etc but not able to solve my problem which is unable to detect my USB external HD. It is able to detect in MX Linux. Please help..

I attached:
1. inxi -F
2. lsblk
3. udevil.conf (in which even I had allowed devices)
4. photos type of USB external drive (FAT32/NTFS format)

===============================================================================
From Terminal:

$ inxi -F
System:
  Host: user2831 Kernel: 5.10.142-antix.2-686-smp-pae arch: i686 bits: 32
    Desktop: IceWM v: 3.3.0
    Distro: antiX-22_386-full Grup Yorum 18 October 2022
Machine:
  Type: Desktop System: Gigabyte product: N/A v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: H61M-S2P-R3 serial: <superuser required>
    BIOS: American Megatrends v: F2 date: 04/26/2013
CPU:
  Info: dual core model: Intel Core i3-2120 bits: 32 type: MT MCP cache:
    L2: 512 KiB
  Speed (MHz): avg: 1646 min/max: 1600/3300 cores: 1: 1797 2: 1596 3: 1596
    4: 1596
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
    driver: i915 v: kernel
  Device-2: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo
  Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: i915 resolution: 1024x768~60Hz
  OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1)
    v: 3.3 Mesa 20.3.5
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    driver: snd_hda_intel
  Device-2: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo
  Sound Server-1: ALSA v: k5.10.142-antix.2-686-smp-pae running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: eth0 state: down mac: 74:d4:35:23:00:48
  Device-2: Qualcomm Atheros TP-Link TL-WN322G v3 / TL-WN422G v2 802.11g
    [Atheros AR9271]
    type: USB driver: ath9k_htc
  IF: wlan0 state: up mac: 94:0c:6d:8c:46:9f
Drives:
  Local Storage: total: 614.81 GiB used: 8.25 GiB (1.3%)
  ID-1: /dev/sda vendor: Western Digital model: WD5000AAKX-193CA0
    size: 465.76 GiB
  ID-2: /dev/sdb vendor: Hitachi model: HDT721016SLA380 size: 149.05 GiB
Partition:
  ID-1: / size: 89.67 GiB used: 8.25 GiB (9.2%) fs: btrfs dev: /dev/sdb1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 89.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 176 Uptime: 2m Memory: 3.77 GiB used: 983.1 MiB (25.5%)
  Shell: Bash inxi: 3.3.19

===============================================================================

$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 465.8G  0 disk 
├─sda1   8:1    0   100M  0 part 
├─sda2   8:2    0 115.3G  0 part 
├─sda3   8:3    0     1K  0 part 
├─sda4   8:4    0    80G  0 part 
└─sda5   8:5    0 270.3G  0 part 
sdb      8:16   0 149.1G  0 disk 
├─sdb1   8:17   0  89.7G  0 part /
└─sdb2   8:18   0  59.4G  0 part 
sr0     11:0    1  1024M  0 rom 

===============================================================================

file udevil.conf

##############################################################################
#
# udevil configuration file    /etc/udevil/udevil.conf
#
# This file controls what devices, networks, and files users may mount and
# unmount via udevil (set suid).
# 
# IMPORTANT:  IT IS POSSIBLE TO CREATE SERIOUS SECURITY PROBLEMS IF THIS FILE
# IS MISCONFIGURED - EDIT WITH CARE
#
# Note:  For greater control for specific users, including root, copy this
# file to /etc/udevil/udevil-user-USERNAME.conf replacing USERNAME with the
# desired username (eg /etc/udevil/udevil-user-jim.conf).
#
# Format:
#   OPTION = VALUE[, VALUE, ...]
#
# DO NOT USE QUOTES except literally
# Lines beginning with # are ignored
#
##############################################################################

# To log all uses of udevil, set log_file to a file path:
# log_file = /var/log/udevil.log

# Approximate number of days to retain log entries (0=forever, max=60):
log_keep_days = 10

# allowed_types determines what fstypes can be passed by a user to the u/mount
# program, what device filesystems may be un/mounted implicitly, and what
# network filesystems may be un/mounted.
# It may also include the 'file' keyword, indicating that the user is allowed
# to mount files (eg an ISO file).  The $KNOWN_FILESYSTEMS variable may
# be included to include common local filesystems as well as those listed in
# /etc/filesystems and /proc/filesystems.
# allowed_types_USERNAME, if present, is used to override allowed_types for
# the specific user 'USERNAME'.  For example, to allow user 'jim' to mount
# only vfat filesystems, add:
# allowed_types_jim = vfat
# Setting allowed_types = * does NOT allow all types, as this is a security
# risk, but does allow all recognized types.
allowed_types = $KNOWN_FILESYSTEMS, file, cifs, smbfs, nfs, curlftpfs, ftpfs, sshfs, davfs, tmpfs, ramfs
#allowed_types = $KNOWN_FILESYSTEMS, file

# allowed_users is a list of users permitted to mount and unmount with udevil.
# Wildcards (* or ?) may be used in the usernames.  To allow all users,
# specify "allowed_users=*".  UIDs may be included using the form UID=1000.
# For example:  allowed_users = carl, UID=1000, pre*
# Also note that permission to execute udevil may be limited to users belonging
# to the group that owns /usr/bin/udevil, such as 'plugdev' or 'storage',
# depending on installation.
# allowed_users_FSTYPE, if present, is used to override allowed_users when
# mounting or unmounting a specific fstype (eg nfs, ext3, file).
# Note that when mounting a file, fstype will always be 'file' regardless of
# the internal fstype of the file.
# For example, to allow only user 'bob' to mount nfs shares, add:
# allowed_users_nfs = bob
# The root user is NOT automatically allowed to use udevil in some cases unless
# listed here (except for unmounting anything or mounting fstab devices).
allowed_users = *

# allowed_groups is a list of groups permitted to mount and unmount with
# udevil.  The user MUST belong to at least one of these groups.  Wildcards
# or GIDs may NOT be used in group names, but a single * may be used to allow
# all groups.
# Also note that permission to execute udevil may be limited to users belonging
# to the group that owns /usr/bin/udevil, such as 'plugdev' or 'storage',
# depending on installation.
# allowed_groups_FSTYPE, if present, is used to override allowed_groups when
# mounting or unmounting a specific fstype (eg nfs, ext3, file).  For example,
# to allow only members of the 'network' group to mount smb and nfs shares,
# use both of these lines:
# allowed_groups_smbfs = network
# allowed_groups_nfs = network
# The root user is NOT automatically allowed to use udevil in some cases unless
# listed here (except for unmounting anything or mounting fstab devices).
allowed_groups = *

# allowed_media_dirs specifies the media directories in which user mount points
# may be located.  The first directory which exists and does not contain a
# wildcard will be used as the default media directory (normally /media or
# /media/$USER).
# The $USER variable, if included, will be replaced with the username of the
# user running udevil.  Wildcards may also be used in any directory EXCEPT the
# default.  Wildcards will not match a /, except a /** suffix for recursion.
# allowed_media_dirs_FSTYPE, if present, is used to override allowed_media_dirs
# when mounting or unmounting a specific fstype (eg ext2, nfs).  For example,
# to cause /media/network to be used as the default media directory for
# nfs and ftpfs mounts, use these two lines:
# allowed_media_dirs_nfs   = /media/network, /media, /media/$USER
# allowed_media_dirs_ftpfs = /media/network, /media, /media/$USER
# NOTE: If you want only the user who mounted a device to have access to it
# and be allowed to unmount it, specify /media/$USER as the first
# allowed media directory (only /media/$USER is created on demand).
# IMPORTANT:  If an allowed file is mounted to a media directory, the user may
# be permitted to unmount its associated loop device even though internal.
# INCLUDING /MNT HERE IS NOT RECOMMENDED.  ALL ALLOWED MEDIA DIRECTORIES
# SHOULD BE OWNED AND WRITABLE ONLY BY ROOT.
allowed_media_dirs = /media/$USER, /run/media/$USER

# allowed_devices is the first criteria for what block devices users may mount
# or unmount.  If a device is not listed in allowed_devices, it cannot be
# un/mounted (unless in fstab).  However, even if a device is listed, other
# factors may prevent its use.  For example, access to system internal devices
# will be denied to normal users even if they are included in allowed_devices.  
# allowed_devices_FSTYPE, if present, is used to override allowed_devices when
# mounting or unmounting a specific fstype (eg ext3, ntfs).  For example, to
# prevent all block devices containing an ext4 filesystem from being
# un/mounted use:
# allowed_devices_ext4 =
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "allowed_devices=*" which allows any device.  The recommended setting is
# allowed_devices = /dev/*
# WARNING:  ALLOWING USERS TO MOUNT DEVICES OUTSIDE OF /dev CAN CAUSE SERIOUS
# SECURITY PROBLEMS.  DO NOT ALLOW DEVICES IN /dev/shm
allowed_devices = /dev/*
# allowed_devices = *

# allowed_internal_devices causes udevil to treat any listed block devices as
# removable, thus allowing normal users to un/mount them (providing they are
# also listed in allowed_devices).
# allowed_internal_devices_FSTYPE, if present, is used to override
# allowed_internal_devices when mounting or unmounting a specific fstype
# (eg ext3, ntfs).  For example, to allow block devices containing a vfat
# filesystem to be un/mounted even if they are system internal devices, use:
# allowed_internal_devices_vfat = /dev/sdb*
# Some removable esata drives look like internal drives to udevil.  To avoid
# this problem, they can be treated as removable with this setting.
# WARNING:  SETTING A SYSTEM DEVICE HERE CAN CAUSE SERIOUS SECURITY PROBLEMS.
# allowed_internal_devices =
allowed_internal_devices = *

# allowed_internal_uuids and allowed_internal_uuids_FSTYPE work similarly to
# allowed_internal_devices, except that UUIDs are specified instead of devices.
# For example, to allow un/mounting of an internal filesystem based on UUID:
# allowed_internal_uuids = cc0c4489-8def-1e5b-a304-ab87c3cb626c0
# WARNING:  SETTING A SYSTEM DEVICE HERE CAN CAUSE SERIOUS SECURITY PROBLEMS.
# allowed_internal_uuids = 

# forbidden_devices is used to prevent block devices from being un/mounted
# even if other settings would allow them (except devices in fstab).
# forbidden_devices_FSTYPE, if present, is used to override
# forbidden_devices when mounting or unmounting a specific fstype
# (eg ext3, ntfs).  For example, to prevent device /dev/sdd1 from being
# mounted when it contains an ntfs filesystem, use:
# forbidden_devices_ntfs = /dev/sdd1
# NOTE: device node paths are canonicalized before being tested, so forbidding
# a link to a device will have no effect.
forbidden_devices =

# allowed_networks determines what hosts may be un/mounted by udevil users when
# using nfs, cifs, smbfs, curlftpfs, ftpfs, or sshfs.  Hosts may be specified
# using a hostname (eg myserver.com) or IP address (192.168.1.100).
# Wildcards may be used in hostnames and IP addresses, but CIDR notation 
# (192.168.1.0/16) is NOT supported.  IP v6 is supported.  For example:
# allowed_networks = 127.0.0.1, 192.168.1.*, 10.0.0.*, localmachine, *.okay.com
# Or, to prevent un/mounting of any network shares, set:
# allowed_networks =
# allowed_networks_FSTYPE, if present, is used to override allowed_networks
# when mounting or unmounting a specific network fstype (eg nfs, cifs, sshfs,
# curlftpfs).  For example, to limit nfs and samba shares to only local
# networks, use these two lines:
# allowed_networks_nfs = 192.168.1.*, 10.0.0.*
# allowed_networks_cifs = 192.168.1.*, 10.0.0.*
allowed_networks = *

# forbidden_networks and forbidden_networks_FSTYPE are used to specify networks
# that are never allowed, even if other settings allow them (except fstab).
# NO REVERSE LOOKUP IS PERFORMED, so including bad.com will only have an effect
# if the user uses that hostname.  IP lookup is always performed, so forbidding
# an IP address will also forbid all corresponding hostnames.
forbidden_networks = 

# allowed_files is used to determine what files in what directories may be
# un/mounted.  A user must also have read permission on a file to mount it.
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "allowed_files=*" which allows any file, and a /** suffix, which matches
# all files recursively.
# For example, to allow only files in the /share directory to be mounted, use:
# allowed_files = /share/*
# To allow all files in the /share directory AND all subdirectories use:
# allowed_files = /share/**
# NOTE:  Specifying allowed_files_FSTYPE will NOT work because the fstype of
# files is always 'file'.
allowed_files = *

# forbidden_files is used to specify files that are never allowed, even if
# other settings allow them (except fstab).  Specify a full path.
# Note: Wildcards may be used, but a wildcard will never match a /, except
# for "forbidden_files = *", or a /** suffix, which matches all recursively.
# NOTE: file paths are canonicalized before being tested, so forbidding
# a link to a file will have no effect.
forbidden_files = 

# default_options specifies what options are always included when performing
# a mount, in addition to any options the user may specify.
# Note:  When a device is present in /etc/fstab, and the user does not specify
# a mount point, the device is mounted with normal user permissions using
# the fstab entry, without these options.
# default_options_FSTYPE, if present, is used to override default_options
# when mounting a specific fstype (eg ext2, nfs).
# The variables $USER, $UID, and $GID are changed to the user's username, UID,
# and GID.
# FOR GOOD SECURITY, default_options SHOULD ALWAYS INCLUDE: nosuid,noexec,nodev
# WARNING:  OPTIONS PRESENT OR MISSING CAN CAUSE SERIOUS SECURITY PROBLEMS.
default_options           = nosuid, noexec, nodev, noatime
default_options_file      = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, ro
# mount iso9660 with 'ro' to prevent mount read-only warning
default_options_iso9660   = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, ro, utf8
default_options_udf       = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_vfat      = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, utf8
default_options_exfat     = nosuid, noexec, nodev, noatime, uid=1000, gid=1000
default_options_msdos     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_umsdos    = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_ntfs      = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, utf8
default_options_cifs      = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_smbfs     = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_sshfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, nonempty, allow_other
default_options_curlftpfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, nonempty, allow_other
default_options_ftpfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_davfs     = nosuid, noexec, nodev, uid=$UID, gid=$GID
default_options_tmpfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_ramfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID

# allowed_options determines all options that a user may specify when mounting.
# All the options used in default_options above must be included here too, or
# they will be rejected.  If the user attempts to use an option not included
# here, an error will result.  Wildcards may be used.
# allowed_options_FSTYPE, if present, is used to override allowed_options
# when mounting a specific fstype (eg ext2, nfs).
# The variables $USER, $UID, and $GID are changed to the user's username, UID,
# and GID.
# If you want to forbid remounts, remove 'remount' from here.
# WARNING:  OPTIONS HERE CAN CAUSE SERIOUS SECURITY PROBLEMS - CHOOSE CAREFULLY
allowed_options           = nosuid, noexec, nodev, noatime, fmask=0133, dmask=0022, uid=$UID, gid=$GID, ro, rw, sync, flush, iocharset=*, utf8, remount
allowed_options_nfs       = nosuid, noexec, nodev, noatime, ro, rw, sync, remount, port=*, rsize=*, wsize=*, hard, proto=*, timeo=*, retrans=*
allowed_options_cifs      = nosuid, noexec, nodev, ro, rw, remount, port=*, user=*, username=*, pass=*, password=*, guest, domain=*, uid=$UID, gid=$GID, credentials=*
allowed_options_smbfs     = nosuid, noexec, nodev, ro, rw, remount, port=*, user=*, username=*, pass=*, password=*, guest, domain=*, uid=$UID, gid=$GID, credentials=*
allowed_options_sshfs     = nosuid, noexec, nodev, noatime, ro, rw, uid=$UID, gid=$GID, nonempty, allow_other, idmap=user, BatchMode=yes, port=*
allowed_options_curlftpfs = nosuid, noexec, nodev, noatime, ro, rw, uid=$UID, gid=$GID, nonempty, allow_other, user=*
allowed_options_ftpfs     = nosuid, noexec, nodev, noatime, ro, rw, port=*, user=*, pass=*, root=*, uid=$UID, gid=$GID
#allowed_options_exfat     = nosuid, noexec, nodev, noatime, fmask=0133, dmask=0022, uid=$UID, gid=$GID, umask=0077, namecase=*, ro, rw, sync, flush, iocharset=*, remount, nonempty

# mount_point_mode, if present and set to a non-empty value, will cause udevil
# to set the mode (permissions) on the moint point after mounting  If not
# specified or if left empty, the mode is not changed.  Mode must be octal
# starting with a zero (0755).
# mount_point_mode_FSTYPE, if present, is used to override mount_point_mode
# when mounting a specific fstype (eg ext2, nfs).
# NOT SETTING A MODE CAN HAVE SECURITY IMPLICATIONS FOR SOME FSTYPES
mount_point_mode = 0755
# don't set a mode for some types:
mount_point_mode_sshfs =
mount_point_mode_curlftpfs =
mount_point_mode_ftpfs =

# Use the settings below to change the default locations of programs used by
# udevil, or (advanced topic) to redirect commands to your scripts.
# When substituting scripts, make sure they are root-owned and accept the
# options used by udevil (for example, the mount_program must accept --fake,
# -o, -v, and other options valid to mount.)
# Be sure to specify the full path and include NO OPTIONS or other arguments.
# These programs may also be specified as configure options when building
# udevil.
# THESE PROGRAMS ARE RUN AS ROOT
# mount_program   = /bin/mount
# umount_program  = /bin/umount
# losetup_program = /sbin/losetup
# setfacl_program = /usr/bin/setfacl

# validate_exec specifies a program or script which provides additional
# validation of a mount or unmount command, beyond the checks performed by
# udevil.  The program is run as a normal user (if root runs udevil,
# validate_exec will NOT be run).  The program is NOT run if the user is
# mounting a device without root privileges (a device in fstab).
# The program is passed the username, a printable description of what is
# happening, and the entire udevil command line as the first three arguments.
# The program must return an exit status of 0 to allow the mount or unmount
# to proceed.  If it returns non-zero, the user will be denied permission.
# For example, validate_exec might specify a script which notifies you
# of the command being run, or performs additional steps to authenticate the
# user.
# Specify a full path to the program, with NO options or arguments.
# validate_exec =

# validate_rootexec works similarly to validate_exec, except that the program
# is run as root.  validate_rootexec will also be run if the root user runs
# udevil.  If both validate_exec and validate_rootexec are specified, 
# validate_rootexec will run first, followed by validate_exec.
# The program must return an exit status of 0 to allow the mount or unmount
# to proceed.  If it returns non-zero, the user will be denied permission.
# Unless you are familiar with writing root scripts, it is recommended that
# rootexec settings NOT be used, as it is easy to inadvertently open exploits.
# THIS PROGRAM IS ALWAYS RUN AS ROOT, even if the user running udevil is not.
# validate_rootexec =

# success_exec is run after a successful mount, remount, or unmount.  The 
# program is run as a normal user (if root runs udevil, success_exec
# will NOT be run).
# The program is passed the username, a printable description of what action
# was taken, and the entire udevil command line as the first three arguments.
# The program's exit status is ignored.
# For example, success_exec might run a script which informs you of what action
# was taken, and might perform further actions.
# Specify a full path to the program, with NO options or arguments.
# success_exec =

# success_rootexec works similarly to success_exec, except that the program is
# run as root.  success_rootexec will also be run if the root user runs udevil.
# If both success_exec and success_rootexec are specified,  success_rootexec
# will run first, followed by success_exec.
# Unless you are familiar with writing root scripts, it is recommended that
# rootexec settings NOT be used, as it is easy to inadvertently open exploits.
# THIS PROGRAM IS ALWAYS RUN AS ROOT, even if the user running udevil is not.
# success_rootexec =

===============================================================================

Thanks…

• This topic was modified 4 months ago by rokytnji. Reason: Needed code tags

Attachments:

1. 

   photo_2023-01-06_12-52-58.jpg
   

[Member PPC]

Dear Olsztyn and Xunzi_23- I’m not a moderator here, but I’m the Original Poster of this thread, so please allow me to present my opinion:

-We are all free to present our opinions here in the forum ( as long as we do not insult anyone). Saying that someone is “tiring” may even be considered as a derogatory term, I think it’s not considered an insult- I’m but a native English speaker, anyone that is, please, correct me if I’m wrong on that assumption- and I don’t consider that expression to be a “personal attack”. Even so, please, dear Xunzi_23, I ask you to present a bit more “constructive critic” in your posts on this thread. That would avoid taking the attention from the matter on the center of this thread- make FT10 the best possible package it can be, no matter if it’s included by default in antiX or not, right? 🙂
-We can support any view we want, even those expressed by users that were banned. I even agreed with somethings that users that were banned said, but, to avoid any conflict, I choose not to reply to a particular user that is currently banned. We do not have to like each other here, but we do have to live together on this forum and respect each other!
– And I don’t think that you can say the moderators have a “strategy”, other than enforce forum rules – anticapitalista sets the “strategy” here. All we can do is present our opinions, and wait for his decision. He kindly (in what I assume was an effort to try to make future antiX versions more user friendly) asked if FT10 should be included in antiX.

I would change many default antiX settings and even include some extra packages (like debinstaller, a compositor, skippy-xd, and maybe my script to connect to samba shared folders and it’s tiny dependencies). I suggest those changes all the time, not for myself (advanced users can modify antiX to look any way they want and install anything they want), but because I think having a more user friendly OS would only benefit us all- and no major User Interface change is needed for that to happen. If users think: “antiX is fine as it is”, I partly agree with them, if users think “antiX needs some changes” I also partly agree with them… Both opinions have their merits. I don’t mind recognizing that opinions other than mine are perfectly valid.

-Also, sorry, I did not realize any attempt at humor on this thread – I usually like humor, and mine is usually dark. Some of my posts even have (I hope) humorous references to pop culture movies and books… I can see how having a “kill switch” on a toolbar can both be practical and also kind of a gag, for example…

P.

• This reply was modified 4 months, 1 week ago by PPC.

[Member PPC]

Hi, All

After a mini end of the year family time with my daughter, I’m back and happy to see that this thread has been very active. Because functionalit of FT10 is relevant to this thread, I’ll address some concerns that were addressed here this last days:

*The clock:
– The default FT10 toolbar settings window (that you can reach right clicking the +/- FT10 toolbar icon) was created by me, partly based in a very old brazilian script I found on-line, and partly built from scratch. Tint2 toolbar comes, out of the box with an extremely powerful GUI configuration editor- but because I thought it was a bit too powerful and complex for the average user that needs FT10 because it’s more in line with how other OS’s interfaces work- the very first time I used that GUI I nixed my tint2 configuration. So I created a tool that easily edits the most used toolbar settings (size, position, auto-hide, colors, fonts, hide/show some icons on the right side, and show 12h/24h clock). It never came to me that users would prefer seeing the seconds go by on the toolbar clock, or that they would prefer using some date format that does not make sense to me, and that I never personally saw being used… So my configuration GUI does not allow to set that… Fortunately, as mentioned previously, any option that FT10’s costume Settings menu does not allow users to change, the default tint2 GUI config application does- I’ll try to improve the my “Settings GUI”, because I still think that the default one is overkill for the average user…

* “Live previews” of running window – I love this feature, but I guess some users can find it annoying. I’ll try to add an option to switch it on/off, but it will be on be default. as far as I know, this preview never fails, but it has an annoying “bug”/”feature”- it shows the preview os the window as it currently is. If it has an over lapping window partly or totally hiding it, the preview will also be partly/totally blank!

*Changing desktops when running FT10
FT10 should only be activated on the Window Manager it was activated on (IceWM, JWM, Fluxbox). I did not add a menu entry to change “Desktops” because changing desktops can have strange results:
Ex: you activate FT10 on IceWM. You use the default antiX menu and select Fluxbox. The end result is a Fluxbox desktop but with Ft10’s toolbar drawn on top of the regular toolbar for that window manager (if they overlap- i.e – they are both on the bottom of the screen).
This strange result happens because switching “desktops” on the fly, using antiX’s default menu, keeps all applications running… And FT10’s toolbar is just a regular application, that is not closed, when you switch to another desktop).
Work around – If you change to a desktop that does not have FT10 activated on it, you may menu > run > “pkill tint2”
That will kill Close FT10’s toolbar. The side effect is, that if you want to use antiX0s menu to switch back to the “desktop” that is configured to use FT10, no toolbar will be show… The fastest way to “solve” that is: right click the desktop > run > “tint2”
That will summon the toolbar again.
The best way to switch between a window manager with FT10’s toolbar and other window manager without FT10 is using the log off menu, then, at the log in screen, press F1 to select the desired “desktop”. This is, does not work if your system automatically logs on (i.e.- you do not have to enter a password).
FT10 is not a Desktop Environment, although, when used with a very well developed Window Manager (like antiX’s IceWM) and with helper apps (like a composition and Dunst, for system notifications) it gets very close to it. My aim is that it’s all seamless for the average user, that does not know what a compositor or a window manager even is, but just wants a familiar system, or something with transparency, etc…

*Fluxbox code – I have to clean up some of FT10’s scripts code. It still has some legacy code, from back when I developed it to work only with Fluxbox. I haven’t touched that part of the code because it’s a “rabbit hole”. It can be very time consuming. But it’s not anything of relevance. FT10 includes many scripts, some massive, but the main scripts, that setup the Window Manager so FT10 runs smoothly simple do this:
– Edit the startup file and add “ft10-start” to it, it’s a tiny script that launches tint2, but first, checks for the existence of a file, that indicates if FT10 was already setup. If it was not, the script shows the activation window (this can be handy if creating an ISO with FT10 installed- the user can select, in live mode, if the default antiX settings should be used, or the “categories menu” or the “Tiles menu”)
– Edit the Window Manager configuration file to disable the system tray on the default toolbar (so FT10’s Tint2 toolbar can display the system tray)
– Disables/hides the default Window Manager’s toolbar (so only FT10’s Tint2 toolbar is displayed)

That’s it. that’s basically all the important changes the “activation” script does to your system. I choose to not even change the default File Manager to Zzzfm/spacefm because I wanted users to have full control of everything- FT10’s toolbar and menu icon’s for File Manager summon ZZZfm, but it does not impose ZZZfm as default File Manager.
NOTE: by default FT10’s activation window does offer to change the default zzzfm configuration to FT10’s and also disable volumeicon (because I created a non memory resident GUI way to set the volume – wich saves a couple of MB of RAM, when compared to running volumeicon and offer the same basic functionality)
There’s a “bug”, not a “feature”- if you disable FT10 the only permanent changes that it does not undo it’s restoring ZZZfm default settings and restoring Volumeicon.
Sorry about this- I tried to solve the volumeicon problem, but I messed up and ended up having to patch FT10 and sending anticapitalista a new version… Since then I’ve stayed away from that seemingly easily solved problem…

*On “why so much pressure is being exercised now to force FT10 modifications on everyone”
I think folks are reading this situation wrong – anticapitalista merely asked the community if the community felt antiX should come with FT10.
As the main creator of this package I made my position clear to everyone:
– I do think it’s a good idea that antiX Full comes with FT10 pre installed – because it adds not just a more “modern and familiar” interface, but also because it includes many small scripts that may make life simpler for some users (like easily mounting Samba Shared folders, Google Drive, get the weather, a GUI calendar/agenda, a world clock, a timer, etc). The aim of those small scripts is giving antiX the same basic functionality that you get with any smartphone today. Some of this functionalities only become active after the user selects to use them- then the script downloads the needed packages- so, if you do not want to use a functionality, it takes next to 0 disk space, only a tiny script and a .desktop file).
Please note that I said “FT10 pre installed” not “activated”. This means that users get exactly the same antix as they have today, plus some extra menu entries.
I do think that having an iso of antiX with FT10 pre installed and activated is a good idea. In it’s current form, FT10 should be configured in such a way as it always asked (when being run Live without persistence) what menu should be used.
I can add an initial option, “Stick with antiX’s default look and feel” – if the user clicked that, all they get is regular “old” antix desktop. If I add a timer to this window (example: if the user does not select any option in 10 or 20 seconds, just exit the script and start the default antiX desktop). With this possible change (kind of suggested by BobC), then we can please both crowds- the people that love FT10 and the people that love the current antiX’s look and feel- the only change would be a pop up window when you started the live system)

*Using FT10 with untested Window Managers –
Some notable users already tested, and reported back on this thread, how FT10 handles in Openbox,etc.
and yes- the toolbar part of FT10 (what most users see) is a toolbar that gives access to a menu. This toolbar is a heavily configured Tint2 toolbar (with some helper scripts to allow access to some funcionality and jgmenu to give access to customized menus). tint2 runs great in window managers without a default toolbar, such as Openbox – just add tint2 to the Window Manager start up file) and you’re set! To be on the safe side, also make sure that no tint2 toolbar is running, or you can end up with overlapping tint2 toolbars, taking up your RAM, if you reload your desktop (something like “pkill tint2 & sleep 2 && tint2 &”)…

* I’ll have to fix debinstaller’s .desktop file, as per anticapitalista’s recommendation, and also probably change the script’s name, because MX is creating a package with the same functionality and a similar name- probably antiX will adopt that “deb installer” program in the future…

P.

• This reply was modified 4 months, 1 week ago by PPC.
• This reply was modified 4 months, 1 week ago by PPC.

[Moderator BobC]

You could simulate removing it to see what depends on it? Run these two commands and post the results. I expect they will give you some good hints.

This command shows the details for that package

$ sudo apt show libtalloc2
Package: libtalloc2
Version: 2.3.1-2+b1
Priority: optional
Section: libs
Source: talloc (2.3.1-2)
Maintainer: Debian Samba Maintainers <pkg-samba-maint@lists.alioth.debian.org>
Installed-Size: 95.2 kB
Depends: libc6 (>= 2.16)
Breaks: python3-talloc (<< 2.1.13-2~)
Homepage: https://talloc.samba.org/
Tag: role::shared-lib
Download-Size: 29.3 kB
APT-Manual-Installed: no
APT-Sources: http://ftp.us.debian.org/debian bullseye/main amd64 Packages
Description: hierarchical pool based memory allocator
 A hierarchical pool based memory allocator with destructors. It uses
 reference counting to determine when memory should be freed.

N: There is 1 additional record. Please use the '-a' switch to see it

This command simulates purging it so we can see what you have installed that depends on it.

$ sudo apt -s purge  libtalloc2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  cifs-utils* connectshares-antix* libtalloc2* libtevent0* libwbclient0*
0 upgraded, 0 newly installed, 5 to remove and 14 not upgraded.
Purg connectshares-antix [0.3.6]
Purg cifs-utils [2:6.11-3.1+deb11u1]
Purg libwbclient0 [2:4.13.13+dfsg-1~deb11u5.0nosystemd1]
Purg libtevent0 [0.10.2-1]
Purg libtalloc2 [2.3.1-2+b1]
bobc@XPS15-I7:~/Downloads

[Member olsztyn]

stevesr0 wrote:

1. /etc/xdg/openbox/autostart
2. /home/stevesr0/.profile
3. /home/stevesr0/.desktop-session/default-desktop
4. /etc/skel/.desktop-session/desktop-session.conf
5. /etc/skel/.desktop-session/startup

My content of these below. Just to remind – I do not have pipewire installed yet:
1. /etc/xdg/openbox/autostart contains just one entry – lxpanel
2. /home/demo/.profile copied in-line here:
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

# if running bash
if [ -n “$BASH_VERSION” ]; then
# include .bashrc if it exists
if [ -f “$HOME/.bashrc” ]; then
. “$HOME/.bashrc”
fi
fi

# set PATH so it includes user’s private bin if it exists
if [ -d “$HOME/bin” ] ; then
PATH=”$HOME/bin:$PATH”
fi

# set PATH so it includes user’s private bin if it exists
if [ -d “$HOME/.local/bin” ] ; then
PATH=”$HOME/.local/bin:$PATH”
fi

3. /home/demo/.desktop-session/default-desktop: openbox

4. /etc/skel/.desktop-session/desktop-session.conf is copied in-line below:
#This is the desktop-session config file.
#This is structured in a bash script format, so all options must be option=”desired-option

#Session service delay.
#This is to set how long to delay startup to give enough time for the wm to completely load.
#before starting to load other applications. This wait period will be started after the
#window manager has been found running.
#TIME is expressed in seconds
#Options: 0-9…
STARTUP_DELAY=”2″

#Session window manager check
#This is to set the amount of times desktop-session checks for a running window manager
#before giving up and denying the session to load.
#Options: 0-9…
TIMES_TO_CHECK=”20″

#Session give up override
#This is to set the override if the window manager is never found to be running by
#desktop-session. This will force the session to load if set to true.
#Options: true | false
FORCE_LOAD=”false”

#Session Protect.
#This is how to protect the user from automatic updating of any file within desktop-session.
#Examples are the menu, any file compare within file_compare, etc
#Options for this are:
#SESSION_PROTECT=”true #Strictly protect the user, leave the user to deal with any of the updating
#SESSION_PROTECT=”ask #Notify me at startup of any changes and allow me to choose what to update
#SESSION_PROTECT=”false #Just update me, I dont want to worry about falling behind.
SESSION_PROTECT=”false”

#Notification Dialog
#This is where to enable / disable the session loading dialog
#Options: true | false
NOTIFICATION_DIALOG=”false”

#Notification text or program
#This is where the text is set for the notification that the session is loading.
#This can be a specified text string or a program that will return a text string
#Examples:
#NOTIFICATION_TEXT=”Session is Loading, Please Wait…..”
#NOTIFICATION_TEXT=”/usr/games/fortune”
NOTIFICATION_TEXT=”Session is Loading, Please Wait…..”

#Startup Sound
#Play Sound when loading the desktop (uses terminal command play)
#Options: true | false
STARTUP_SOUND=”false”

#Startup Sound File
#Location of the file for the startup sound
STARTUP_SOUND_FILE=”$HOME/.desktop-session/startup.ogg”

#Startup Dialog
#This is where to enable / disable the session startup dialog
#Options: true | false
STARTUP_DIALOG=”false”

#Startup Dialog Command
#This is where to set the startup dialog command
#Examples:
#STARTUP_DIALOG_CMD=”leafpad ~/.startup-text”
#STARTUP_DIALOG_CMD=”yad –image=’info’ –text=’this is my startup dialog'”
#STARTUP_DIALOG_CMD=”/usr/local/lib/desktop-session/startup-dialog.py”

#Session load conky
#This will load a window manager specific conky from ~/.conky
#There must be a corresponding conkyrc in ~/.conky in the form of windowmanager-conkyrc
#Else we will load conky without the -c parameter
#Options: true | false
LOAD_CONKY=”true”

#Session load xdg autostart
#This will load any application that is setup to autostart via xdg autostart directories /
#.desktop files.
#Options: true | false
LOAD_XDG_AUTOSTART=”false”

#Session load of dbus-launch
#This will make it possible to start a session bus instance of dbus-daemon with the window manager
#Options: true | false
DBUS_SESSION_LAUNCH=”false”

#Session load startup
#This will load any application that is setup to autostart via /etc/desktop-session/startup
#Options: true | false
LOAD_STARTUP_FILE=”true”

#Session screen blank
#This is to set the amount of time that the screen stays visible.
#Desktop-session sets the dpms settings according to the screen blank value set here.
#TIME expressed in seconds
#Options: 0-9…
SCREEN_BLANK_TIME=”3600″

#Session other desktops window
#This is to set the other desktops window to pop up or not.
#true = pop up
#false = no pop up
OTHER_DESKTOPS_WINDOW=”true”

#Default Sound Level
#Set the sound volume level when starting up to default level when startup sound is true
#Set using amixer sset ‘Master’ -M
#Level is set from 0% – 100%
STARTUP_SOUND_LEVEL=”65%”

5. /etc/skel/.desktop-session/startup: Copied in-line below:
#!/bin/bash

## fix HiDPI screen if necessary.
## Not needed if there is no HiDPI screen
autoscale-antix

## Only use ONE (or neither)
## Simple script to check for connectivity (NCA).
## If no network connection is detected, activate wi-fi networks, open connman and go straight to the wi-fi connections tab.
network-check-antix &
## OR More comples tool (NCR) that provides on screen info while waiting for a network connection to be established.
## NRS reports in both GUI and non-GUI environments.
#network-readiness-state &

## Puts connman gui monitor icon on the taskbar
#cmst -m &

## Uncomment if using pulseaudio (you need to install it). Make sure it starts before volumeicon.
#pulseaudio -D &

## 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 &

## 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 (you need to install ssh-conduit-antix)
#ssh-conduit-x11vnc.sh gui &

## Uncomment to use clipboard manager
#clipit &

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

## Uncomment both to show wicd networking monitor (you need to install wicd).
#wicd-client -t &
#grep -q “START_DAEMON=no” /etc/default/wicd || wicd-client -t &

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

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

## Uncomment if using network-manager (you need to install it)
#nm-applet &

## Create a bootchart image if bootchart was run
test -e /etc/live/config/bootchart \
&& (sleep 6 && test -e /var/log/bootchart.tgz \
&& ! test -e ~/bootchart.png \
&& pybootchartgui)&

## Used on live system only
(sleep 5 && toram-eject) &

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

[Member flyingchap]

Hello Gourry

One thing to REMEMBER and be careful of with NTFS, are the fundamental limitations / differences NTFS has from other more ‘Linux/Unix-friendly’ filesystem formats.

KEY difference is, the likes of EXT3 /EXT4 and other Linux file systems is they *are designed with differential user permissions in mind*, and have room within the filesystem, to remember permissions for more than one user. NTFS DOES NOT have that – it essentially has no idea who you are – SO, Linux has to cope and manage read/write permissions on the fly based on other criteria (others more skilled than I in the nuances of device permissions management can doubtless tell you much more than I can on this.

Where I have found this an issue, is on using an NTFS volume at the far end of a NETWORK DRIVE on Samba: confusion can easily arise if the person attempting write-access at a mounted network drive which is an NTFS volume: simplest solution I have found, is to MOUNT that [network] drive using a bash script which expressly makes sure it my userID which is used to mount the volume R/W and then I generally have no issues.

You are presumably talking of a local mount so will differ. There’s good advice out among general Linux guidance about mount commands to deal with NTFS. I’d recommend ‘stay command line’ – GUI tools only add to unclarity on things like this. 100.00% of things can be done from CLI in Linux which is part of its power and it’s worth getting comfortable with BASH so you can use bash scripts for tasks like this.

Dear forum members:

I’ve used Linux in my office for some 12 years and antiX for about half of that time. My old office desktop motherboard went to heaven a few days ago, and it’s replacement, a motherboard with a quad core and 2 GB of RAM and my old 2 hd (old spinning disks) is great for office work:
antiX running IceWM (no dekstop icons but with Conky running) with a nice looking theme (+ tint2 toolbar and a jgmenu- AKA FT10) + Firefox with 3 tabs open (one, very heavy- Gmail, this forum and one page I need for work), zzzfm with 3 tabs, Thunderbird, LibreOffice Writer

RAM usage: 1460mb, no Swap used
CPU usage: 11 – 13%

So, if you want to use antiX for real office work, with this very well known Open Source pieces of software (well zzzfm is a gem probably known only to us), you can do it- hell, you can use GUI scripts to mount Samba Shared Folders or Cloud Drives, so probably you can do most office work (involving webpages, e-mail, text documents or spreadsheets) with plenty of resources to spare, as long as you have more than 1 CPU core and 2Gb of RAM.

Edit: most modern OSes probably require about 1.4Gb of RAM just to be idle! If I really wanted I could, of course, shave one or two dozens of mb of RAM usage.
This system, on idle, uses about 150-160Mb of RAM and about 1% of CPU.

P.

• This topic was modified 4 months, 4 weeks ago by PPC.
• This topic was modified 4 months, 4 weeks ago by PPC.