Maybe it's just the particular Linux distribution I use (Libranet, built
from Debian) but I don't find the command s-povray anywhere on my
system.   I _can_ run POVray by typing: 
povray ... (w/arguments) in either an xterm or at console, but I can't
use the +D option unless I'm in an xterm (or Eterm or rxvt, whatever...)

Does anyone know if it's normal for the deb-packaged POVRay to exclude
the s-povray that can be run with the +D option at a console?  Should I
just purge the Deb package and reinstall from the official povlinux.tgz
?

--Mark

Post a reply to this message

Mark M. Wilson wrote:

> Maybe it's just the particular Linux distribution I use (Libranet, built
> from Debian) but I don't find the command s-povray anywhere on my
> system.   I _can_ run POVray by typing: 
> povray ... (w/arguments) in either an xterm or at console, but I can't
> use the +D option unless I'm in an xterm (or Eterm or rxvt, whatever...)


   The s-povray binary is for svga display, I think. Perhaps it is not 
bundled on your distro, as it is not much used. If you are using X, the 
most common choice is x-povray, which must be surely installed on your 
system.

--
Jaime Vives Piqueres

La Persistencia de la Ignorancia
http://www.ignorancia.org/

Post a reply to this message

Jaime Vives Piqueres wrote:
> 
>    The s-povray binary is for svga display, I think. 

Yes, I know.  That's what I'm seeking ( I'm trying to run X as little as
possible these days, as there may be something wrong with my ATI Rage
card -- rapid mouse clicking&dragging or intense bursts of keyboarding
can cause EVERYTHING to crash. -- long story, still sussing that problem
out...)  

> Perhaps it is not bundled on your distro, as it is not much used. If you are using
X, the
> most common choice is x-povray, which must be surely installed on your
> system.

Yes, but I believe if I explicitly typed "x-povray (+args)"  it would
come back with "command not found" or something to that effect.  The
command 'povray' by itself performs that function, and displays the
image as it renders IF the +D is chosen.
 -- Mark
 
> --
> Jaime Vives Piqueres
> 
> La Persistencia de la Ignorancia
> http://www.ignorancia.org/

Post a reply to this message

On Mon, 03 Dec 2001 14:26:09 -0500, Mark M. Wilson wrote:
> Maybe it's just the particular Linux distribution I use (Libranet, built
> from Debian) but I don't find the command s-povray anywhere on my
> system.   I _can_ run POVray by typing: 

It's possible that they chose not to include it because it has to be 
setuid root to work.  As such, it's a security hole big enough to drive a 
fleet of aircraft carriers through.

I'm pretty sure s-povray is dead as of 3.5.

-- 
#local R=<7084844682857967,0787982,826975826580>;#macro L(P)concat(#while(P)chr(
mod(P,100)),#local P=P/100;#end"")#end background{rgb 1}text{ttf L(R.x)L(R.y)0,0
translate<-.8,0,-1>}text{ttf L(R.x)L(R.z)0,0translate<-1.6,-.75,-1>}sphere{z/9e3
4/26/2001finish{reflection 1}}//ron.parker@povray.org My opinions, nobody else's

Post a reply to this message

Ron Parker wrote:

> It's possible that they chose not to include it because it has to be
> setuid root to work.  As such, it's a security hole big enough to drive a
> fleet of aircraft carriers through.

Not an issue for a standalone, single-user box that doesn't live on the
'net. ;-) 
 
I guess I just don't understand much about (SVGA) graphics:  why is
there this apparent connection?  There are quite a few apps out there,
if I'm not mistaken, that require 1) SVGA and 2) to be run setuid root. 
Yet I can use a console-based graphic file viewer called zgv that can be
run as regular joe-user.

--Mark

Post a reply to this message

On Mon, 03 Dec 2001 16:30:21 -0500, Mark M. Wilson wrote:
> I guess I just don't understand much about (SVGA) graphics:  why is
> there this apparent connection?  There are quite a few apps out there,
> if I'm not mistaken, that require 1) SVGA and 2) to be run setuid root. 
> Yet I can use a console-based graphic file viewer called zgv that can be
> run as regular joe-user.

It might use the framebuffer device instead; that's a little newer
and can be used more securely.

--
#macro R(L P)sphere{L __}cylinder{L P __}#end#macro P(_1)union{R(z+_ z)R(-z _-z)
R(_-z*3_+z)torus{1__ clipped_by{plane{_ 0}}}translate z+_1}#end#macro S(_)9-(_1-
_)*(_1-_)#end#macro Z(_1 _ __)union{P(_)P(-_)R(y-z-1_)translate.1*_1-y*8pigment{
rgb<S(7)S(5)S(3)>}}#if(_1)Z(_1-__,_,__)#end#end Z(10x*-2,.2)camera{rotate x*90}

Post a reply to this message

I have no idea what that even means (no implicit request for
explanation, unless it's simpler than I realize...)
--Mark

Ron Parker wrote:
> > run as regular joe-user.
> 
> It might use the framebuffer device instead; that's a little newer
> and can be used more securely.
> 
> --
> #macro R(L P)sphere{L __}cylinder{L P __}#end#macro P(_1)union{R(z+_ z)R(-z _-z)
> R(_-z*3_+z)torus{1__ clipped_by{plane{_ 0}}}translate z+_1}#end#macro S(_)9-(_1-
> _)*(_1-_)#end#macro Z(_1 _ __)union{P(_)P(-_)R(y-z-1_)translate.1*_1-y*8pigment{
> rgb<S(7)S(5)S(3)>}}#if(_1)Z(_1-__,_,__)#end#end Z(10x*-2,.2)camera{rotate x*90}

Post a reply to this message