Search Results for 'ssh'

[Member ile]

 Private  +   Shared  =  RAM used	Program

200.0 KiB +  39.5 KiB = 239.5 KiB	anacron
204.0 KiB +  38.5 KiB = 242.5 KiB	gpm
224.0 KiB +  66.5 KiB = 290.5 KiB	init
296.0 KiB +  39.5 KiB = 335.5 KiB	acpid
312.0 KiB +  94.5 KiB = 406.5 KiB	cron
336.0 KiB + 137.5 KiB = 473.5 KiB	dbus-launch
476.0 KiB +  33.5 KiB = 509.5 KiB	rpc.idmapd
440.0 KiB + 126.5 KiB = 566.5 KiB	rpc.statd
468.0 KiB + 117.5 KiB = 585.5 KiB	rpcbind
376.0 KiB + 307.5 KiB = 683.5 KiB	udevil
160.0 KiB + 574.0 KiB = 734.0 KiB	saned (2)
448.0 KiB + 469.0 KiB = 917.0 KiB	avahi-daemon (2)
652.0 KiB + 454.5 KiB =   1.1 MiB	devmon
720.0 KiB + 414.0 KiB =   1.1 MiB	dbus-daemon (2)
804.0 KiB + 458.5 KiB =   1.2 MiB	desktop-session
828.0 KiB + 551.0 KiB =   1.3 MiB	getty (6)
  1.3 MiB + 105.5 KiB =   1.4 MiB	sshd
  1.6 MiB +  35.5 KiB =   1.6 MiB	smartd
  1.5 MiB + 291.5 KiB =   1.8 MiB	connmand
  1.7 MiB +  82.5 KiB =   1.8 MiB	elogind-daemon
  1.7 MiB + 193.5 KiB =   1.9 MiB	ntpd
  1.5 MiB + 468.5 KiB =   2.0 MiB	bash
  1.5 MiB + 576.5 KiB =   2.0 MiB	sudo
  1.9 MiB + 485.5 KiB =   2.4 MiB	bluetoothd
  3.2 MiB +  29.5 KiB =   3.2 MiB	haveged
  2.8 MiB + 440.5 KiB =   3.2 MiB	wpa_supplicant
  3.3 MiB + 430.5 KiB =   3.7 MiB	udevd
  3.5 MiB + 518.5 KiB =   4.0 MiB	cupsd
  3.8 MiB +   1.0 MiB =   4.9 MiB	conky
  4.3 MiB +   1.4 MiB =   5.7 MiB	fluxbox
  4.7 MiB +   1.1 MiB =   5.9 MiB	slimski
  2.6 MiB +   3.5 MiB =   6.1 MiB	volumeicon
 11.7 MiB +   4.6 MiB =  16.3 MiB	roxterm
  5.7 MiB +  11.5 MiB =  17.2 MiB	zzzfm
 24.9 MiB +   9.1 MiB =  34.0 MiB	Xorg
---------------------------------
                        129.6 MiB
Kernel: 5.10.137-antix.1-amd64-smp x86_64
 Desktop: Fluxbox v: 1.3.5
    Distro: antiX-21_x64-full Grup Yorum 31 October 2021
__
then new kernel and conky shows a regular bounce 162, 182,162,182, 162, 182,, 
Kernel: 6.1.11-antix.1-amd64-smp arch: x86_64 bits: 64
    Desktop: Fluxbox v: 1.3.5
    Distro: antiX-21_x64-full Grup Yorum 31 October 2021
212.0 KiB +  37.5 KiB = 249.5 KiB	gpm
228.0 KiB +  68.5 KiB = 296.5 KiB	init
296.0 KiB +  43.5 KiB = 339.5 KiB	acpid
308.0 KiB +  89.5 KiB = 397.5 KiB	cron
336.0 KiB + 141.5 KiB = 477.5 KiB	dbus-launch
484.0 KiB +  33.5 KiB = 517.5 KiB	rpc.idmapd
448.0 KiB + 123.5 KiB = 571.5 KiB	rpcbind
444.0 KiB + 133.5 KiB = 577.5 KiB	rpc.statd
360.0 KiB + 262.5 KiB = 622.5 KiB	udevil
152.0 KiB + 591.0 KiB = 743.0 KiB	saned (2)
432.0 KiB + 500.0 KiB = 932.0 KiB	avahi-daemon (2)
652.0 KiB + 409.5 KiB =   1.0 MiB	devmon
700.0 KiB + 413.0 KiB =   1.1 MiB	dbus-daemon (2)
828.0 KiB + 418.5 KiB =   1.2 MiB	desktop-session
832.0 KiB + 464.0 KiB =   1.3 MiB	getty (6)
  1.3 MiB + 116.5 KiB =   1.4 MiB	sshd
  1.6 MiB +  34.5 KiB =   1.6 MiB	smartd
  1.5 MiB + 272.5 KiB =   1.8 MiB	connmand
  1.7 MiB +  83.5 KiB =   1.8 MiB	elogind-daemon
  1.7 MiB + 196.5 KiB =   1.9 MiB	ntpd
  1.4 MiB + 529.5 KiB =   2.0 MiB	sudo
  1.6 MiB + 434.5 KiB =   2.0 MiB	bash
  1.9 MiB + 470.5 KiB =   2.4 MiB	bluetoothd
  3.2 MiB +  28.5 KiB =   3.2 MiB	haveged
  2.8 MiB + 466.5 KiB =   3.2 MiB	wpa_supplicant
  3.3 MiB + 446.5 KiB =   3.7 MiB	udevd
  3.4 MiB + 523.5 KiB =   3.9 MiB	cupsd
  4.3 MiB +   1.4 MiB =   5.6 MiB	fluxbox
  4.8 MiB +   1.1 MiB =   5.9 MiB	slimski
  2.6 MiB +   3.4 MiB =   6.0 MiB	volumeicon
  5.9 MiB +   1.1 MiB =   7.0 MiB	conky
 11.6 MiB +   4.6 MiB =  16.2 MiB	roxterm
  7.7 MiB +  11.4 MiB =  19.1 MiB	zzzfm
 48.9 MiB +   9.1 MiB =  58.0 MiB	Xorg
---------------------------------
                        156.8 MiB

the diff is anacron and xorg(?) 

[Member h2]

I personally like the feature, which is quite literally the only reason it continues to exist, and I tend to avoid removing things I like, and sometimes use, myself.

The intention of this was never to be a weather widget, and I really did not even think that was the case until it grew instantly obvious after an update that it was the primary use people were using it for, without by the way ever even looking at the damned thing, which I could tell because some russian dude was hitting the server with about 10k requests a week, despite having been banned years before. He’s finally gone, but only recently. This means literally 100s of thousands of requests had been made without looking at the results a single time. That’s an extreme case, but most users do not look at their automated script outputs at all.

The latest tightening has been ok, which were required when the last significant weather api massively slashed its free quota, leaving only 1 now that has a reasonable max.

This feature has one valid use case: login into remote system, check the weather, one time. As the messages now say, if you want your local weather, then look out your damned windows, lol, inxi doesn’t give predictions or forecasts, and the local weather is often hours out of date anyway, so I’m always puzzled by why people need to know the weather outside their door or windows.

I am just suggesting that the feature not be highlighted, though it continues to be, but almost universally, when users post about it, they NEVER read the man or help, and ALWAYS ignore any message about automated or excessive use, which then leads to the next banned users who follow those online directions.

Now that I think on it, I think the next case of someone wasting my time on it, usually via a plaintive email or github issue, I’ll just remove the weather stuff from the man and help, but leave the options in place. I think that would probably resolve most issues with long term abuse since they wouldn’t see those options.

Note that it’s also entirely possible that the weather apis will just force this on me, 2 shut off access last year, 1 slashed their quota massively, another a year or so back massively slashed their quota, to the degree it was not usable at all anymore, so it will take only one more real cut I think to just make the feature non-usable.

There is one thing I may look into internally since the single quality api remaining that is usable at scale of any sort requires location data in a specific format, so if I can map -W [location] to that format, I could probably extend the life of the feature maybe a few more years.

I’ll see how it goes.

But the basic takeaway is: if you did not type in the weather request, it’s automated. If you use it as a widget of any sort, it’s abuse.

If you are using it for more than a single hand-typed check of something now and then, it’s abuse.

I used to do these bans manually, but users were starting to really piss me off by trying to be clever and work around the detections, which proved that I was dealing with true little assholes who do not understand what free software is, what actual work is, or what the difference between billion dollar corporations funding themselves by selling your personal data and violating your privacy and a single person doing something that is hopefully useful for a community. I realize asbergers, and it’s accompanying failure to be able to empathize with other humans, is a significant feature of the tech sector, which is really what drove this entire process, but that type of thoughtless rude childish behavior has real consequences in the real world.

• This reply was modified 3 months ago by h2.
• This reply was modified 3 months ago by h2.

inxi system information script (install info) :: inxi git

[Member PPC]

For anyone wanting to localize most of the new entries in zzzfm, mixing all my previous suggestions, the correct (and nearly) final script should be:

#!/bin/bash
#Script to localize antiX Linux File Manager (zzzFM's) "add-ons": Common Bookmarks, Home Bookmark, Recent Files and Trash related entries, by PPC, 7/2/2023, GPL
        TEXTDOMAINDIR=/usr/share/locale
        TEXTDOMAIN=zzzfmlocalize  ###NOTE: this is just an example, the dev team is free to choose how to name this resource, of course

#Variables with the text this zzzfm's "add-ons" displays, for easy editing and localization:
trash_label=$"Trash"
trash_menu_entry=$"Send to Trash" 
restore_menu_entry=$"Restore" 
recents_label=$"Recent Files"

#script's variable(s):
targetfile=~/.config/zzzfm/session

#Localize Downloads Bookmark and path:
label=$(echo $XDG_DOWNLOAD_DIR| cut -d/ -f4)
sed -i "s/cstm_6c99bdd2-label=.*/cstm_6c99bdd2-label=$label/g"  $targetfile
sed -i "s|cstm_6c99bdd2-z=.*|cstm_6c99bdd2-z=$HOME/$label|g"  $targetfile

#Localize Documents Bookmark and path:
label=$(echo $XDG_DOCUMENTS_DIR| cut -d/ -f4)
sed -i "s/cstm_1f966a72-label=.*/cstm_6c99bdd2-label=$label/g"  $targetfile
sed -i "s|cstm_1f966a72-z=.*|cstm_6c99bdd2-z=$HOME/$label|g"  $targetfile

#Localize Pictures Bookmark and path:
label=$(echo $XDG_PICTURES_DIR| cut -d/ -f4)
sed -i "s/cstm_23f8698b-label=.*/cstm_6c99bdd2-label=$label/g"  $targetfile
sed -i "s|cstm_23f8698b-z=.*|cstm_6c99bdd2-z=$HOME/$label|g"  $targetfile

#Localize Videos Bookmark and path:
label=$(echo $XDG_VIDEOS_DIR| cut -d/ -f4)
sed -i "s/cstm_3be1d265-label=.*/cstm_3be1d265-label=$label/g"  $targetfile
sed -i "s|cstm_3be1d265-z=.*|cstm_3be1d265-z=$HOME/$label|g"  $targetfile

#Maybe to TODO???: anticapitalista did not insert a "Music" Bookmark. If it's inserted, it will require localization too, using label=$(echo $XDG_MUSIC_DIR| cut -d/ -f4)

#localize Home bookmark:
TEXTDOMAINDIR=/usr/share/locale
TEXTDOMAIN=zzzfm
homie=$"Home"
sed -i "s/cstm_2b7f3cb1-label=.*/cstm_2b7f3cb1-label=$homie/g"  $targetfile

#Localize Recent Files bookmark: 
#NOTE: currently, all lines until the one that starts with "sed" are a workaround, using "geany's localization file, instead of our own 
#Get label localization, from geany's localization file
export TEXTDOMAIN=geany;  recents_label=$(echo "$(gettext "Recent _Files")")
#remove any underscore
recents_label=${recents_label//_/}
sed -i "s/cstm_0f7a0cea-label=.*/cstm_0f7a0cea-label=$recents_label/g"  $targetfile

#Localize Trash related entries: 
#"Trash" bookmark:
sed -i "s/cstm_3ca29516-label=.*/cstm_3ca29516-label=$trash_label/g"  $targetfile
#"Send to Trash" contextual menu entry:
sed -i "s/cstm_25a291d5-label=.*/cstm_25a291d5-label=$trash_menu_entry/g"  $targetfile
#"Restore" (from Trash) contextual menu entry:
sed -i "s/cstm_2b015761-label=.*/cstm_2b015761-label=$restore_menu_entry/g"  $targetfile

How to use this script to localize zzzfm’s new entries:
save the script in your home folder, call it “zzzfmlocalize”
antiX Menu > Terminal
pkill zzzfm

run the script, from the terminal:
bash ~/zzzfmlocalize

If you were using the default zzz-icewm desktop, to re-enable desktop icons:
antiX Menu > Desktops > … select zzzIceWM

Note:
You can open zzzfm and test the localization for yourself. The bookmarks should all work now, in any language and all (except the Trash related ones) should be correctly localized.

Note: you can edit the contents of the variables related to the “Trash” entries, on the start of the script so they show text in your own language, or, as it currently is, those entries will remain in English, until a localization file is created for this script… Adapt the script and repeat the process above, for it to change zzzfm’s config file.

Edit: Just in case anticapitalista wants a nice multilingual .desktop file, so users can access the Trash Can from the menu (I would advise using it with a variation of GUI scripts to manage the Trash Can, not just direct access to it. Ideally, launching that .desktop file should show users 2 choices: View Trash Can’s contents or Empty Trash Can (with a confirmation dialog before emptying it, of course).

trash.desktop:

[Desktop Entry]
Categories=System;FileTools;Utility;Core;GTK;FileManager;
Exec=zzzfm ~/.local/share/Trash/files/
Icon=/usr/share/icons/papirus-antix/48x48/status/user-trash.png
MimeType=inode/directory;inode/mount-point;x-scheme-handler/ssh;x-scheme-handler/smb;x-scheme-handler/nfs;x-scheme-handler/ftp;x-scheme-handler/ptp;x-scheme-handler/mtp;x-scheme-handler/webdav;x-scheme-handler/http;x-scheme-handler/https;
StartupNotify=true
Type=Application
Terminal=false
X-KDE-Protocols=ftp,smb,ssh,ptp,mtp,nfs,webdav,http,https

Name=Trash
Name[fr]=Corbeille
Name[pt]=Reciclagem
Name[pt_BR]=Lixeira
Name[es]=Papelera de reciclaje
Name[it]=Cestino
Name[de]=PapierKorb

Comment=Access Files Moved to Recycle Bin
Comment[fr]=Accès aux fichiers mis à la corbeille
Comment[pt]=Aceder Ficheiros Removidos para a Reciclagem
Comment[pt_BR]=Acessar os Arquivos Movidos para a Lixeira
Comment[es]= Acessar Papelera de reciclaje

Keywords=file;manager;file-manager;
Keywords[fr]=fichier;gestionnaire;gestionnaire de fichiers;
Keywords[pt]=ficheiro;gestor;gestor de ficheiro;
Keywords[pt_BR]=arquivo;gerenciador;gerenciador de arquivos;

P.

• This reply was modified 3 months ago by PPC.
• This reply was modified 3 months ago by PPC.
• This reply was modified 3 months ago by PPC.

[Member sybok]

Not quite sure what exactly you intend to do but why not use simple ‘ssh -XC <username>@$(hostname)’?
Of course, the switches to ‘ssh’ can be adjusted to your needs.

[Moderator BobC]

I have another critical project that I need to put my time into now (before I retire), so until that one is working, I’m not planning to take on any other major projects.

I was working on a FT10 respin for antiX 22 a couple months ago, but since learned that the “make changes and remaster” method I was using wasn’t good, so don’t plan to work on it further. I should have setup the ssh key and used a fork, made my changes, and built a new iso from it, but its beyond my knowledge level how to do it that way.

A note for anyone thinking about doing an FT10 respin. It is designed to be an add on package, not a starting point, so that means it changes the antiX setups including translations as it installs, so its not as simple as it seems.

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.

[Member xinomilo]

PPC wrote:

– the upgrade command now includes “–fix-missing”, to be on the safe side [I assume there is no harm on always using this flag- am I wrong? Please, do correct me on that, I did not research that in detail)

completely harmless.
not sure how it runs along with dist-upgrade. never run it in the same upgrade command, usually running it after upgrade (eg. apt update && apt upgrade && apt -f install).
and under some circumstances (eg. failed upgrade) that could fail too… a failed package upgrade needs attention/fix first, then apt install –fix-missing .

blur13 wrote:

I dont use apt -y myself, but does this automatically say yes to all package upgrades? even if it entails removing some packages?

yes, apt dist-upgrade -y does that (=removing packages). apt upgrade -y doesn’t. (see : man apt)
—

tbh, i don’t like automation when it involves system upgrades.. users should always keep an eye on what’s changing.
so i would never use ‘-y’ flag or “Dpkg::Options::=–force-confold”, because that would mean that some packages could be removed, some daemons might have security vulnerabilities because of old config versions. eg. still using SSLv23, or old versions of sshd_config, or whatever.

my 2c

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

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 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 banned]

rikardfribergvs wrote:

* Cannot get Midori to work – I can ping sites and use SSH in the terminal but I cannot browse. Might be some setting in Midori maybe.

Did you download from here? Have you asked their forum?

https://astian.org/midori-browser-desktop/

I have used Midori with great success so can’t quite understand all the fuss?
Super lightweight..! Shipped as standard browser with some light distros.

Good luck

[Member rikardfribergvs]

Progress!

Found an old CD-R lying around. Unfortunately just 700mb so I had to choose Antix Core. Managed to install after a couple of attempts (some undefined problems). The bios-battery is of course dead after 20 years and it took me a while to understand why apt told me that the packages I were trying to install was not valid yet (will be valid in 7600 days”. Well success anyway at last.

Listened to Andy above and installed XORG and LXDE. Took a while to configure XORG (never done it before) but now it works. Computer boots, lightdm starts, I can login to LXDE. Might use Openbox later on. Quite fun to configure if you like XML.

Some things I still need to solve:

* Cannot get Midori to work – I can ping sites and use SSH in the terminal but I cannot browse. Might be some setting in Midori maybe.
* Have not checked sound yet, might do today.
* Have to change the bios battery.
* Have to check if there is working card for wireless. Otherwise I might buy a pcmcia-card.
* Might look for a new battery – seems to be the original battery.

This was really fun actually!

Rikard

[Member sybok]

Update system, SSH login with forwarding (compressed) graphics, change to a set folder

alias deb_update='echo "sudo apt update/dist-upgrade/autoclean"; sudo apt update && sudo apt dist-upgrade && sudo apt autoclean'
alias sybokser='ssh -XC sybok@<server>'
alias miscdir='cd /data/Audio/Misc/'

And a final one that sometimes pops out to remind me of my mischievous sense of humour.
alias exot='echo "Did you mean *exit*? Be more careful when you type!"'

[Moderator BobC]

I’m not sure why you thought LXDE was lighter. The difference is significant.

The Dell 620 luckily hadn’t been changed since then. Its idling at about 120 mb, and that’s running 64 bit and using Roxterm. If I was to run 32 bit and use Urxvt it would be better still. Those extra mb could be used for Zram to speed it up more.

bobc@antix1:~
$ sudo ps_mem.py
 Private  +   Shared  =  RAM used	Program

204.0 KiB +  30.5 KiB = 234.5 KiB	gpm
216.0 KiB +  66.5 KiB = 282.5 KiB	init
324.0 KiB +  34.5 KiB = 358.5 KiB	acpid
312.0 KiB +  81.5 KiB = 393.5 KiB	cron
460.0 KiB +  30.5 KiB = 490.5 KiB	rpc.idmapd
328.0 KiB + 179.5 KiB = 507.5 KiB	dbus-launch
460.0 KiB + 106.5 KiB = 566.5 KiB	rpcbind
460.0 KiB + 120.5 KiB = 580.5 KiB	rpc.statd
352.0 KiB + 365.5 KiB = 717.5 KiB	icewm-session
168.0 KiB + 572.0 KiB = 740.0 KiB	saned (2)
396.0 KiB + 457.5 KiB = 853.5 KiB	udevil
452.0 KiB + 471.0 KiB = 923.0 KiB	avahi-daemon (2)
640.0 KiB + 451.5 KiB =   1.1 MiB	devmon
776.0 KiB + 425.0 KiB =   1.2 MiB	dbus-daemon (2)
804.0 KiB + 463.5 KiB =   1.2 MiB	desktop-session
816.0 KiB + 457.0 KiB =   1.2 MiB	getty (6)
  1.3 MiB + 106.5 KiB =   1.4 MiB	sshd
  1.5 MiB +  76.5 KiB =   1.5 MiB	smartd
  1.7 MiB +  82.5 KiB =   1.7 MiB	elogind-daemon
  1.5 MiB + 277.5 KiB =   1.7 MiB	ntpd
  1.6 MiB + 370.5 KiB =   2.0 MiB	connmand
  1.5 MiB + 537.5 KiB =   2.0 MiB	sudo
  1.7 MiB + 488.5 KiB =   2.1 MiB	bash
  3.2 MiB +  22.5 KiB =   3.2 MiB	haveged
  3.7 MiB + 493.5 KiB =   4.1 MiB	cupsd
  5.1 MiB + 539.5 KiB =   5.7 MiB	wpa_supplicant
  6.4 MiB +   3.5 MiB =   9.9 MiB	icewm
  6.1 MiB +   5.6 MiB =  11.8 MiB	udevd (13)
 15.3 MiB +   1.3 MiB =  16.6 MiB	slimski
 17.9 MiB +   1.4 MiB =  19.3 MiB	Xorg
 18.1 MiB +   4.4 MiB =  22.5 MiB	roxterm
---------------------------------
                        116.8 MiB
=================================
bobc@antix1:~
$ inxi -Fxv
CPU: dual core Intel Core2 T5500 (-MCP-) speed/min/max: 1469/1000/1667 MHz
Kernel: 5.10.57-antix.1-amd64-smp x86_64 Up: 1h 9m
Mem: 363.5/1974.7 MiB (18.4%) Storage: 232.89 GiB (2.1% used) Procs: 126
Shell: Bash 5.1.4 inxi: 3.3.19
bobc@antix1:~
$ inxi -Fxz7
Error 22: Unsupported option: -7
Check -h for correct parameters.
bobc@antix1:~
$ inxi -Fxz
System:
  Kernel: 5.10.57-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc
    v: 10.2.1 Desktop: IceWM v: 3.0.1
    Distro: antiX-21_x64-full Grup Yorum 31 October 2021
    base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Portable System: Dell product: Latitude D620 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 0FT292 serial: <superuser required> BIOS: Dell v: A08
    date: 04/03/2007
Battery:
  ID-1: BAT0 charge: 0% condition: 39.6/56.6 Wh (70.0%) volts: 2.4 min: 11.1
    model: Panasonic DELL J825J8 status: N/A
CPU:
  Info: dual core model: Intel Core2 T5500 bits: 64 type: MCP
    arch: Core2 Merom rev: 2 cache: L1: 128 KiB L2: 2 MiB
  Speed (MHz): avg: 1664 min/max: 1000/1667 cores: 1: 1664 2: 1664
    bogomips: 6657
  Flags: ht lm nx pae sse sse2 sse3 ssse3 vmx
Graphics:
  Device-1: Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics
    vendor: Dell driver: i915 v: kernel arch: Gen3.5 bus-ID: 00:02.0
  Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: intel gpu: i915
    resolution: 1440x900~60Hz
  OpenGL: renderer: Mesa DRI Intel 945GM v: 1.4 Mesa 20.3.5
    direct render: Yes
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
  Sound Server-1: ALSA v: k5.10.57-antix.1-amd64-smp running: yes
Network:
  Device-1: Broadcom NetXtreme BCM5752 Gigabit Ethernet PCI Express
    vendor: Dell Latitude D620 driver: tg3 v: kernel port: N/A bus-ID: 09:00.0
  IF: eth0 state: down mac: <filter>
  Device-2: Broadcom BCM4311 802.11a/b/g
    vendor: Dell Wireless 1490 Dual Band WLAN Mini-Card driver: b43-pci-bridge
    v: N/A bus-ID: 0c:00.0
  IF-ID-1: wlan0 state: up mac: <filter>
Drives:
  Local Storage: total: 232.89 GiB used: 4.85 GiB (2.1%)
  ID-1: /dev/sda vendor: Crucial model: CT250MX200SSD1 size: 232.89 GiB
Partition:
  ID-1: / size: 19.52 GiB used: 4.85 GiB (24.8%) fs: ext4 dev: /dev/sda9
Swap:
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 66.0 C mobo: N/A sodimm: SODIMM C
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 126 Uptime: 1h 9m Memory: 1.93 GiB used: 363.9 MiB (18.4%)
  Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Packages: 1595
  Shell: Bash v: 5.1.4 inxi: 3.3.19
bobc@antix1:~
$ date
Fri 18 Nov 2022 02:32:42 AM EST
bobc@antix1:~
$ 

[Member banned]

$ pstree
init─┬─acpid
├─at-spi-bus-laun─┬─dbus-daemon
│ └─3*[{at-spi-bus-laun}]
├─at-spi2-registr───2*[{at-spi2-registr}]
├─avahi-daemon───avahi-daemon
├─bluetoothd
├─connmand
├─cron
├─cupsd
├─3*[dbus-daemon]
├─2*[dbus-launch]
├─2*[dconf-service───2*[{dconf-service}]]
├─devmon───udevil
├─elogind-daemon
├─gconfd-2
├─6*[getty]
├─gpm
├─gvfs-udisks2-vo───3*[{gvfs-udisks2-vo}]
├─gvfsd─┬─gvfsd-trash───2*[{gvfsd-trash}]
│ └─2*[{gvfsd}]
├─haveged
├─menu-cached───2*[{menu-cached}]
├─ntpd───{ntpd}
├─polkitd───2*[{polkitd}]
├─rpc.idmapd
├─rpc.statd
├─rpcbind
├─saned───saned
├─seatd
├─slimski─┬─Xorg───5*[{Xorg}]
│ └─desktop-session───lxsession─┬─lxpanel─┬─lxterminal─┬─bash───ps+
│ │ │ └─3*[{lxter+
│ │ ├─oosplash─┬─soffice.bin+++
│ │ │ └─{oosplash}
│ │ ├─x-www-browser─┬─Isolat+
│ │ │ ├─2*[Iso+
│ │ │ ├─Isolat+
│ │ │ ├─RDD Pr+
│ │ │ ├─Socket+
│ │ │ ├─Utilit+
│ │ │ ├─3*[Web+
│ │ │ ├─WebExt+
│ │ │ └─97*[{x+
│ │ └─3*[{lxpanel}]
│ ├─lxpolkit───2*[{lxpolkit}]
│ ├─openbox───2*[{openbox}]
│ ├─pcmanfm───2*[{pcmanfm}]
│ └─2*[{lxsession}]
├─smartd
├─ssh-agent
├─sshd
├─udevd
├─udisksd───4*[{udisksd}]
├─volumeicon
└─wpa_supplicant
Andy@antix1:~

Note saned in tree (twice?)

• This reply was modified 6 months ago by banned.
• This reply was modified 6 months ago by banned.

[Moderator Brian Masinick]

caprea wrote:

Please post the terminal output of
groups

Does simple scan find the scanner if started as root from terminal ?
gksudo simple-scan

Just to come BACK to this informative post, I just did exactly as this suggested:
FIRST I opened a terminal emulator window
SECOND I typed in groups

Here is the output I received:

masinick root daemon bin sys adm disk lp dialout cdrom floppy sudo audio dip www-data shadow utmp video plugdev users messagebus ssh input netdev lpadmin scanner saned

THIRD I typed in the next suggestion:
gksudo simple-scan

This opened up the Document Scanner. I don’t have anything set up, but at least the Document Scanner tool appeared. To actually scan, you have to have images/content and the scanner interface. We can see above that the necessary groups (and more) ARE set up, but the one thing lacking are items to scan…

--
Brian Masinick