I've been trying to get samba configured on my home office LAN with mixed results. I only want basic share level access among my boxes. I have a good set of firewall rules, and samba is binded to the local LAN, so for a simple home LAN, share level security is sufficient.

Box 1 is multi-boot, but this problem occurs when that box is using Slackware. Using samba when Box 1 is in Windows works just fine with Box 2 in Slackware. The problem is the Slack-Slack combo, not Windows-Slack.

I can connect just fine between two boxes. Samba works okay at that point. Oddly, however, I experience different results despite using the same config files, etc.

I've created two shares on two boxes, exactly the same. One share is to /home/public and I assigned permissions to that directory as 777. Anybody can do anything there. I also created a share to the root (/) directory tree. This is for browsing and file comparison purposes for maintenance as root.

From Box 1 I can connect to Box 2. I receive all expected permissions to /home/public on Box 2. The head scratcher is that as root on Box 1 I do not have access to all directories on Box 2 from the root (/) share. As root I also cannot access the home/$user directories or /root.

Contrarily, from Box 2 everything works close to what I expect. All normal users have all permissions to Box 1 /home/public. Root has access to all files on the Box 1 root (/) share, including rights to /root and all /home/$users. Normal users on Box 2 can see files and directories on Box 1 with expected results, and cannot view files in privileged directories such as /root, /home/$any_other_user, /etc/samba/private, etc.

So things seem to be in order when connecting Box 2 to Box 1, but not from Box 1 to Box 2. Odd.

These two boxes are configured as identically as possible. The samba config files are the same, firewall rules, etc. Because of these similarities, I do not think this is a samba issue but something more fundamental. Rather than immediately post a bunch of config files that will water your eyes, I'll pause at this point and will post as needed based upon your responses.

FWIW, I have not installed NFS. That option is down the road on the to-do list. Right now I just want to get the samba wrinkles ironed.

Thanks.

Just a wild guess here: you might want to install and use NFS since you are going from linux to linux. Samba might not do that very well.

Lately this message has been appearing on my boxes as I have been updating to 10.2 to prepare for 11.0.

Many moons ago I experienced this error, and I learned that the message appears when using Midnight Commander. I added a command alias mc -d to stop that. I did not see the error message until recently.

Some recent sleuthing led me to discover that the ncurses tools used in pkgtools and other ncurses-based Slackware scripts, such as setconsolefont, will also trigger this error message. Now, the pkgtools are scripts and there is nothing in them to trigger this nuisance message. The problem is in the ncurses tools, probably triggered when using the dialog command.

Tonight I confirmed that the error message appears when using ncurses-based tools. I ran setconsolefont and voila!

I further discovered that the error message appears only when using the ncurses-based tools from the console. When using those same tools from within an xterm (Konsole) window the error message does not appear.

Any ncurses experts here to verify this problem or how to permanently stop the nuisance message? Yes, the message is non fatal, but as a Slacker I prefer clean and crisp logs.

I'm using ncurses-5.4-i486-2 and gpm-1.19.6-i486-6, although I never use gpm.

Thanks.

Hi,

You could disable as root the gpm by;

If you use pkgtool or any ncurses based slackware tool then you are using the gpm. You might not use the mouse with the tools but you are using the gpm when you use ncurses if the rc.gpm is executable.

I find that gpm is very useful from the cli. I use gpm a lot to copy, cut or insert/paste in the cli or console.

Well, when I wrote " . . . although I never use gpm" I also meant that rc.gpm is already disabled. I could have been more clear.

I just ran another test and if gpm is enabled then a system log message appears about finding the mouse. If gpm is not installed then the nuisance message appears. The problem must be in the way the ncurses libraries look for the gpm. Possibly the updated version of these packages might have a cure, perhaps not. Distracting and irritating nonetheless.

Moderator:

FWIW, I don't know how I inserted this gpm discussion into my original thread. I thought I had started a new thread. Would a moderator kindly move this gpm discussion to a new thread? I don't want this discussion mixing with my question about file and directory permissions. If possible then thanks!