SuSe 10.1 and filePro 5.0.14D4

[Nancy Palmquist]

Kenneth Brody wrote:
> Quoting Fairlight (Tue, 18 Jul 2006 13:06:39 -0400):
> 
> 
>>This public service announcement was brought to you by Kenneth Brody:
>>
>>>The script has been fixed since the 5.0.14 release.  (Can someone
>>>please verify that the latest 5.6 has the fix in it?)
>>
>>No offense, but you're lead developer the company releasing it and can't
>>tell?
> 
> 
> Okay, so I took the lazy way out.  :-)
> 
> The Linux masters are made at a different office, by a different
> person, on a system I don't normally access.  Yes, I could have
> asked him directly, but I was already typing my reply to Nancy.
> 
> 
>>>The problem is that chown will reset the setuid bit.  This is for
>>>security reasons, to prevent the setuid bit from applying to the
>>>new uid, and is probably documented on the chown man page.
>>
>>There's another reason it could possibly fail.  Could be installing to
>>an NFS partition with nosuid set.  Not as likely, but still possible.
> 
> 
> According to the documentation on chown (the program, not the system
> call), the behavior depends on how the O/S handles the system call,
> as it is not a behavior that is built in to the chown program itself.
> 
> And does the nosuid flag mean that the setuid bit cannot be set, or
> does it mean that it is to be ignored?
>

I verified the behavior of chown on SuSe Linux 10.1. It will unset the 
suid bit.  All I did to fix it was swap and chown /chmod commands so the 
chown always happened first.

Then all worked great.  In fact, I only found 2 I had to change, I think.

No it is not writing to a NFS file structure.  Just a normal 
installation.  Trying to test an install on my new SuSe 10.1 started me 
down this road.

I still have no good solution for the graphic display.  If I use windows 
to telnet to the SuSe the graphics in filePro are just fine.  If I use 
SCOUnix to telnet, I get the strange graphics.  (Anzio worked fine also.)

The LANG is set to English.  UTF-8 encoding is unchecked.

Telnet from windows, TERM defaults to ansi.

telnet from SCO Unix, TERM defaults to scoansi.  This will not work, 
even if I change it to ansi, xterm, scoansi-new.

Tried them all.

I can use this and telnet from Windows when it bugs me too much.

I tried the SuSe console to see what was displayed there.

TERM=linux.  The graphics are all invisible except the vertical with the 
right line (key 4 in filePro graphics).

It sure looks weird.  I tried different termcaps provided with filepro 
Linux stuff (5.0), but something is not good.

Nancy


-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com