SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Had an accident about 10 days ago. Lost my home partition.
It was mostly backed up, so nothing important was lost.
After rebuilding, I found I could not run scripts, except in my home directory,
even if I owned the external directory.
Symptoms:
Run a bash script as ./<script> and all that happens is "Permission denied"
Run it as "bash <script>" (or "sh <script>" and it will run if there are no
functions in the script. Any function and again "Permission denied"
A google search turned up a similar problem in Slackware13, which was caused
by wrong permissions in glibc files, but a careful comparison with the file
permissions vs permissions shown in the manifest uncovered no problems there.
If anyone has any idea of what is wrong, please give me a clue.
Sorry to be so long getting back to this, but I've had a few external problems,
mostly a grandson in the hospital with a ruptured appendix. He's out and healing
now, so I can get back to other things.
I have found the problem. Somehow my /etc/fstab file became corrupted. Visually it was
okay, but some partitions were mounted with wrong partions, as shown below:
Quote:
/dev/sda9 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sdb1 on /home type ext4 (rw)
/dev/sda1 on /boot/efi type vfat (rw)
/dev/sdc1 on /home/photos type ext4 (rw,noexec,nosuid,nodev) [PHOTOS]
/dev/sdc2 on /mnt/repos type ext4 (rw,noexec,nosuid,nodev) [REPOSITORY]
/dev/sdg1 on /mnt/sfs_basic type ext4 (rw,noexec,nosuid,nodev) [SFS_BASIC]
/dev/sdf1 on /mnt/backup type ext4 (rw,noexec,nosuid,nodev) [BACKUP]
/dev/sda5 on /mnt/lfs type ext4 (rw,noexec,nosuid,nodev) [LFS]
/dev/sda6 on /mnt/sfs type ext4 (rw,noexec,nosuid,nodev) [SFS]
/dev/sde1 on /mnt/xfr type ext4 (rw,noexec,nosuid,nodev) [XFR]
/dev/sdd1 on /home/Data1 type ext4 (rw,noexec,nosuid,nodev) [DATA1]
/dev/sdd2 on /home/Data2 type ext4 (rw,noexec,nosuid,nodev) [DATA2]
/dev/sdd3 on /home/Data3 type ext4 (rw,noexec,nosuid,nodev) [DATA3]
gvfsd-fuse on /home/jeg/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=jeg)
I edited fstab, retyping several lines, then rebooted. Now "mount -l" shows this:
Quote:
/dev/sda9 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sdb1 on /home type ext4 (rw)
/dev/sda1 on /boot/efi type vfat (rw)
/dev/sdc1 on /home/photos type ext4 (rw,noexec,nosuid,nodev) [PHOTOS]
/dev/sdc2 on /mnt/repos type ext4 (rw) [REPOSITORY]
/dev/sde1 on /mnt/sfs_basic type ext4 (rw,noexec,nosuid,nodev) [SFS_BASIC]
/dev/sdf1 on /mnt/backup type ext4 (rw,noexec,nosuid,nodev) [BACKUP]
/dev/sda5 on /mnt/lfs type ext4 (rw) [LFS]
/dev/sda6 on /mnt/sfs type ext4 (rw) [SFS]
/dev/sdg1 on /mnt/xfr type ext4 (rw,noexec,nosuid,nodev) [XFR]
/dev/sdh1 on /home/Data1 type ext4 (rw,noexec,nosuid,nodev) [DATA1]
/dev/sdh2 on /home/Data2 type ext4 (rw,noexec,nosuid,nodev) [DATA2]
/dev/sdh3 on /home/Data3 type ext4 (rw,noexec,nosuid,nodev) [DATA3]
gvfsd-fuse on /home/jeg/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=jeg)
REPOSITORY, LFS, and SFS partitions now allow scripts to run normally.
I'll mark this thread as closed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.