You are not logged in.
And I suggest you do set up identical usernames
I had already done that. Checking /etc/passwd reveals they both have the same UID in each OS environment. So, good there.
Using an entry like the following in fstab reveals that the User has Read and Write permissions on the partition without the need to use chown nor to do it manually through a sudo session of Thunar in both OS environments.
UUID=xxxxxxxx /media/UserName/LinuxData ext4 defaults 0 2
mount in Terminal reveals that the options rw and relatime are enabled.
So, how are we doing folks?
Thanks!!
But don't let non-root users write into it
That would seem to suggest that the User wouldn't be able to create any directories or files on the partition?
On my own system, for an external hard drive ls -al produces the following.
/media/mtbvfr/LinuxDataExt-4TB
$ ls -al
total 32
drwxrwxr-x 5 root mtbvfr 4096 Apr 3 2024 .
drwxr-x---+ 17 root root 4096 Jan 8 18:46 ..
drwx------ 2 root root 16384 Jul 27 2018 lost+found
drwxrwxr-x 34 mtbvfr mtbvfr 4096 Jan 21 2024 MyStuff
drwx------ 4 mtbvfr mtbvfr 4096 Apr 3 2024 .Trash-1000
Hi Guys @RedGreen925, @rolfie and @steve_v,
Thanks!! for all your input.
My I.T. invovlvement began in December 82 in a Mainframe Operations environment. NCR and then IBM. After 5+ years of fkn shiftwork, I got into the programming side of things starting with COBOL and Wang Procedure Language.
My vision is currently stuffed (screwed, fucked, whatever vernacular tickles your facncy) you could say. So, I'm always looking for quick but sound solutions with easily sourced comprehensive technical documentation where necessary. One of my pet peeves is lousy and incomplete documentation.
My use of Linux began in 2014 after I got my first Laptop (Lenove B590 with no OS) on which I installed Windo$e 8 (what a disaster). Was installed without Secure Boot from the beginning in preparation for dual-booting with Linux. I began with a version of Linux Mint that was only valid for 3 months which caused me some upgrade problems. I learnt about the systemd crap during that year as well as other nefarious crap going on. I switched to a non-systemd Manjaro based distro for a while which became defunct unfortunately.
I dabbled with Debian a bit also before the systemd takeover was done. I even made a persistent version installation of it on a USB Flash Drive.
I eventually got onto MX Linux and started looking at Devuan when it became available. Stuck with MX Linux because there were teething issues when migrating from Devuan1 to Devuan 2 but good to see it has now matured.
I was helping make improvements with luckyBackup mostly with English to Spanish translation at one time. I had dabbled with YAD also to improve the interface and some basic expected functionality but can't remember the exact details now.
I think my fstab configurations are based on what was orignally created by the installation of Linux Mint.
I had already started on the page, suggested by @RedGreen925 in Post #7, before I submitted my Post #6.
I also looked at the following 2 pages.
https://man.archlinux.org/man/mount.8#F … NT_OPTIONS
It would be great if the manuals were more comprehensive. For example, I had to do a string search on character or block special devices on the filesystem to learn what the dev and nodev options are for.
The following pages gave better insight but unsure if needed for my use case.
https://sebastien-copin.com/posts/the_n … unt_option
https://www.suse.com/support/kb/doc/?id=000020660
Does what Sebastien describes present itself for my scenario for a tech illiterate user, who just needs to store their own media and document files on the partition? What would you all suggest?
Similarly, suid and nosuid are not expanded on in the first 3 pages I mentioned. Am I correct in guessing that it was the nosuid that was preventing the default rw option from being enabled?
If such a partition is to be shared between 2 Linux installations, can both installations own the partition or would it be better to give the user Read and Write access to the Root directory of the Data partition within each OS?
Thanks!!, MTB.
not the vfat options now set on it
The file system type is set as ext4.
Which are the vfat options that you are referring to?
Adding the rw option after defaults appears to have it fixed it but is that the correct way to do it?
If I had allowed the installation process to format things, how would have fstab have been configured?
Should I chown the partition to the User account or only its root directory or should I only give Read & Write Access to the Group with the same name as the User Name?
It would help if I included the fstab entry wouldn't it?
It's like the following one but with a different User Name and UUID.
UUID=65dfc273-13a4-4d93-8dec-7f2f59f43a3b /media/mtbvfr/LinuxDataExt-4TB ext4 defaults,nosuid,nodev,relatime,data=ordered 0 0
Hi Folks,
I partitioned the drive with GParted using the Live DVD for the 32bit version of Devuan 5 before installation of the Operating System.
When I try to access the partition that is to be used for storage of the User's files, I am prompted with an Authentication dialogue window.
I have added an entry to the fstab file for this partition but I am still being prompted with an Authentication dialogue window.
What's the fix?
Thanks!!
@fsmithred - Works great!!
Were you referring to the last setting for the Gamma or the Brightness?
What's usually the best way, with Yad, to store the Brightness value that can later be retrieved by a bash script using xrandr on startup?
Thanks!!
This one is a little fancier
Thanks mate, I will give it a go mañana.
Should I comment out the lines referring to gamma?
Ah, I see, I think. You are only using select_brightness in the Main Procedure.
Complete removal by Synaptic occurred without error.
Installation using apt produced the same error in Post #33.
Although xbindkeys and xdotool are installed on my Daily Driver, there wasn't any .xbindkeysrc in my Home directory.
Is there any other directory where such a configuration file exists?
It may have been MX17 or MX18 I was using that.
I can't remember, now, how I got my head around this stuff.
Is there better documentation on the use of xbindkeys than the following page?
https://wiki.archlinux.org/title/Xbindkeys
Section 2.2 Backlight control I find interesting but I find Section 5 confusing as it refers to xmodmap.
I am wondering if I could use XF86MonBrightnessUp and XF86MonBrightnessDown in the graphical Settings Editor for xfconf.
If using xbindkeys and xdotool
Thanks for reminding me about those. It must be like 7+ years when I did something with those when I bought a Micro$oft Natural Keyboard with the "Wave" style key layout. It has 5 extra keys that can be programmed for whatever. I stopped using it because I prefer the layout of the Home-End-Delete-PageUp-PageDown and Multimedia Keys of my 2004 Micro$oft Natural Multimedia PS/2 keyboard for which I bought a Perixx PS/2 to USB adapter. It also has much better Build Quality.
I may even have it setup on this MX 19.4 installation I'm on and still using as my Daily OS. I will look into it later. What would be good is to be able to prompt the User for a value.
Now there is thought now I think of it,
It doesn't install correctly in MX neither, see post #33.
Just looked at the Devuan environment and there is no /proc/acpi/toshiba directory at present, only the /proc/acpi.
I noticed the Laptop running cooler when using Devuan also.
I will try Complete Removal from Synaptic again and then reinstalling using apt in the Devuan environment and see if the output is different to MX
The post by Mavrik on 8th, 2007, 11:43 AM and some following ones on the following page are interesting.
https://ubuntuforums.org/archive/index. … 16358.html
In a search for "Phoenix BIOS 1.70 acpi" I found the following pages:
https://support.dynabook.com/support/vi … Id=1401578
https://support.dynabook.com/support/vi … Id=1991832
Others to look at too.
The Fn Key only works with the F10 and F11 Keys on my Sister's Laptop which are for using the overlayed Numpad. Windoze XP was installed on the original Hard Drive and there is a Windows Vista Capable sticker near the Fingerprint reader,
She told me that with Win XP, there is a Brightness Adjustment feature in Settings.
If Devuan created a Brightness Adjustment Applet using xrandr, that would solve the problem.
Using xrandr --output LVDS --brightness 0.5 for example reduces the brightness by half.
Interesting page:
https://bugs.launchpad.net/ubuntu/+sour … bug/127611
My Sister's Laptop has a Phoenix BIOS 1.70.
I noticed today that the Laptop seems to be running cooler now.
I tried installing on MX Linux 24.3 with apt install after doing modprobe and lsmod and the following output before which there were no errors as there was when I installed on Devuan with synaptic:
Setting up fnfxd (0.3-18) ...
Starting Toshiba hotkeys utils: FnFX Daemon v0.3 (c) 2003, 2004 Timo Hoenig <thoenig@nouse.net>fatal error: Could not open /proc/acpi/toshiba/keys.
Please make sure that your kernel has enabled the Toshiba option in the ACPI section.
For more information read the documentation and/or http://fnfx.sf.net/index.php?section=doc#kernel.invoke-rc.d: initscript fnfxd, action "start" failed.
dpkg: error processing package fnfxd (--configure):
installed fnfxd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
fnfxd
I can't find any reference to /proc/acpi/toshiba/keys in the files in the .deb file.
/proc/acpi/toshiba was created today. Would that have been done by the use of modprobe?
I've started searching on "Could not open /proc/acpi/toshiba/keys".
In Post #29 I had deleted /etc/init.d/fnfxd.
Why was it not installed again?
What's the best way to do a complete removal and purge so that I can reinstall using apt instead?
sudo apt autoremove produced the following:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
libpeas-1.0-0 libpeas-common libwpe-1.0-1 libwpebackend-fdo-1.0-1
linux-image-6.1.0-10-686-pae
0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
After this operation, 188 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 137881 files and directories currently installed.)
Removing libpeas-1.0-0:i386 (1.34.0-1+b1) ...
Removing libpeas-common (1.34.0-1) ...
Removing libwpebackend-fdo-1.0-1:i386 (1.14.2-1) ...
Removing libwpe-1.0-1:i386 (1.14.0-1) ...
Removing linux-image-6.1.0-10-686-pae (6.1.38-1) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-10-686-pae
/etc/kernel/postrm.d/zz-update-grub:
Generating grub configuration file ...
Found theme: /usr/share/desktop-base/grub-themes/desktop-grub-theme/theme.txt
Found linux image: /boot/vmlinuz-6.1.0-28-686-pae
Found initrd image: /boot/initrd.img-6.1.0-28-686-pae
Found linux image: /boot/vmlinuz-6.1.0-27-686-pae
Found initrd image: /boot/initrd.img-6.1.0-27-686-pae
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
Processing triggers for libc-bin (2.36-9+deb12u9) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
I'm hoping that didn't remove MX Linux from the Grub Menu.
Installing fnfxd from synaptic produced the following:
(dpkg-preconfigure:5560): Gtk-WARNING **: 15:02:30.976: Theme parsing error: gtk-widgets.css:1346:25: The style property GtkRange:stepper-size is deprecated and shouldn't be used anymore. It will be removed in a future version
(dpkg-preconfigure:5560): Gtk-WARNING **: 15:02:30.976: Theme parsing error: gtk-widgets.css:1347:34: The style property GtkScrollbar:min-slider-length is deprecated and shouldn't be used anymore. It will be removed in a future version
(dpkg-preconfigure:5560): Gtk-WARNING **: 15:02:30.976: Theme parsing error: gtk-widgets.css:1348:28: The style property GtkRange:stepper-spacing is deprecated and shouldn't be used anymore. It will be removed in a future version
(dpkg-preconfigure:5560): Gtk-WARNING **: 15:02:30.976: Theme parsing error: gtk-widgets.css:1349:34: The style property GtkRange:trough-under-steppers is deprecated and shouldn't be used anymore. It will be removed in a future version
Selecting previously unselected package fnfxd.
(Reading database ... 132741 files and directories currently installed.)
Preparing to unpack .../archives/fnfxd_0.3-18_i386.deb ...
Unpacking fnfxd (0.3-18) ...
Setting up fnfxd (0.3-18) ...
Processing triggers for man-db (2.11.2-2) ...
According to the Installed Files tab of synaptic there is supposed to be an /etc/init.d/fnfxd file but there isn't.
The following directory and files do exist:
/etc/fnfxd
/etc/fnfxd/fnfxd.conf
/etc/fnfxd/keymap
fnfxd.conf contains the assignments for the F6 and F7 keys for adjusting brightness.
Should I now reboot to see if the change takes effect?
Try the sudo rm /etc/init.d/fnfxd
sudo rm /etc/init.d/fnfxd produced no output and the file was deleted.
sudo apt remove fnfxd produced the following output:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libpeas-1.0-0 libpeas-common libwpe-1.0-1 libwpebackend-fdo-1.0-1
linux-image-6.1.0-10-686-pae
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
fnfxd
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 70.7 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 137890 files and directories currently installed.)
Removing fnfxd (0.3-18) ...
Processing triggers for man-db (2.11.2-2) ...
It is no longer shown as installed in synaptic.
fnfxd_0.3-18_i386.deb file still resides in /var/cache/apt/archives.
Run from the / directory, sudo find -name *fnfxd* | grep fnfxd produced the following output:
./etc/rc2.d/S03fnfxd
./etc/rc6.d/K01fnfxd
./etc/rc0.d/K01fnfxd
./etc/fnfxd
./etc/fnfxd/fnfxd.conf
./etc/rc4.d/S03fnfxd
./etc/rc3.d/S03fnfxd
./etc/rc5.d/S03fnfxd
./etc/rc1.d/K01fnfxd
./var/cache/apt/archives/fnfxd_0.3-18_i386.deb
./var/lib/dpkg/info/fnfxd.postrm
./var/lib/dpkg/info/fnfxd.list
sudo /sbin/modprobe toshiba_acpi produced no output.
sudo /sbin/lsmod | grep toshiba_acpi produced the following output which has some extra flags(?) compared to your example:
toshiba_acpi 53248 0
industrialio 65536 1 toshiba_acpi
sparse_keymap 16384 1 toshiba_acpi
rfkill 20480 6 toshiba_bluetooth,bluetooth,toshiba_acpi,cfg80211
video 57344 3 amdgpu,radeon,toshiba_acpi
wmi 24576 2 video,toshiba_acpi
battery 24576 1 toshiba_acpi
sudo apt remove fnfxd
produced the following:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libpeas-1.0-0 libpeas-common libwpe-1.0-1 libwpebackend-fdo-1.0-1
linux-image-6.1.0-10-686-pae
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
fnfxd
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 70.7 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 137890 files and directories currently installed.)
Removing fnfxd (0.3-18) ...
Stopping Toshiba hotkeys utils: invoke-rc.d: initscript fnfxd, action "stop" failed.
dpkg: error processing package fnfxd (--remove):
installed fnfxd package pre-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Starting Toshiba hotkeys utils: FnFX Daemon v0.3 (c) 2003, 2004 Timo Hoenig <tho
enig@nouse.net>fatal error: Could not open /proc/acpi/toshiba/keys.
Please make sure that your kernel has enabled the Toshiba option in the ACPI sec
tion.
For more information read the documentation and/or http://fnfx.sf.net/index.php?
section=doc#kernel.invoke-rc.d: initscript fnfxd, action "start" failed.
dpkg: error while cleaning up:
installed fnfxd package post-installation script subprocess returned error exit
status 1
Errors were encountered while processing:
fnfxd
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
The pre-removal script is as follows:
#!/bin/sh
set -e
# Automatically added by dh_installinit/13.11.4
if [ -z "${DPKG_ROOT:-}" ] && [ "$1" = remove ] && [ -x "/etc/init.d/fnfxd" ] ; then
invoke-rc.d --skip-systemd-native fnfxd stop || exit 1
fi
# End automatically added section
You can extract the file
Happy New Day,
Are you referring to extraction of the deb file?
The postinst script is as follows:
#!/bin/sh
set -e
# Automatically added by dh_installinit/13.11.4
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -z "${DPKG_ROOT:-}" ] && [ -x "/etc/init.d/fnfxd" ]; then
update-rc.d fnfxd defaults >/dev/null
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
invoke-rc.d --skip-systemd-native fnfxd $_dh_action || exit 1
fi
fi
# End automatically added section
Thanks!!
Heading to bed. Catch up mañana amigo.
Thanks!!
P.S.
synaptic doesn't indicate any Broken packages.
I used synaptic to install. When attempting to remove it, I get the details you saw in post #18.
When I close synaptic and reopen it, fnfxd is still installed.
I didn't install from a .deb file. fnfxd is in the Devuan repositories. Latest version is 0.3-18. The executable (fnfxd) in sbin has a modified date of 2023-02-14.
The fnfxd_0.3-18_i386.deb file in /var/cache/apt/archives has a Modified Date of 2023-02-15.
Given invoke-rc.d: initscript fnfxd, action "start" failed. during installation, do we need to be looking in the init area somewhere?
Let it remove it
Do I use apt or dpkg to remove it?
Open a terminal and sudo dpkg --configure -a
The following output is produced:
Setting up fnfxd (0.3-18) ...
Starting Toshiba hotkeys utils: FnFX Daemon v0.3 (c) 2003, 2004 Timo Hoenig <thoenig@nouse.net>fatal error: Could not open /proc/acpi/toshiba/keys.
Please make sure that your kernel has enabled the Toshiba option in the ACPI section.
For more information read the documentation and/or http://fnfx.sf.net/index.php?section=doc#kernel.invoke-rc.d: initscript fnfxd, action "start" failed.
dpkg: error processing package fnfxd (--configure):
installed fnfxd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
fnfxd
Have you tried the install again with the module loaded?
fnfxd is still installed.
When I attempt to remove it or I install other packages (e.g. apt-file), I get the following responses:
The following dialogue window is displayed:
An error occurred
The following details are provided:
E: fnfxd: installed fnfxd package pre-removal script subprocess returned error exit status 1
Close Button
After closing the above window, the Changes applied dialogue window appears and the following details are output:
For more information read the documentation and/or http://fnfx.sf.net/index.php?section=doc#kernel.
invoke-rc.d: initscript fnfxd, action "start" failed.
dpkg: error while cleaning up:
installed fnfxd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
fnfxd
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up fnfxd (0.3-18) ...
Starting Toshiba hotkeys utils: FnFX Daemon v0.3 (c) 2003, 2004 Timo Hoenig <thoenig@nouse.net>fatal error: Could not open /proc/acpi/toshiba/keys.
Please make sure that your kernel has enabled the Toshiba option in the ACPI section.
For more information read the documentation and/or http://fnfx.sf.net/index.php?section=doc#kernel.invoke-rc.d: initscript fnfxd, action "start" failed.
dpkg: error processing package fnfxd (--configure):
installed fnfxd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
fnfxd
After closing the Changes applied window, fnfxd is still marked with an icon indicating "Marked for complete removal".
Should I attempt to run the modprobe and lsmod commands with the fnfxd package in this state?
Thanks!!