Hi

To clarify what I said in the other email. I use the same
naming rule for the Xvnc4/Xtightvnc/Xvnc as for the "normal"
X server and that is Xorg (nowdays).

As the Xtightvnc is a drop in replacement of any other X
server this is the naming convention used. The server just
have an other access method (vnc) instead of the normal
X server access method (VGA and keyboard+mouse).

Best regards,

// Ola

On Sun, Sep 27, 2009 at 05:20:08PM +0300, Jari Aalto wrote:
> Ola Lundqvist <[email protected]> writes:
> 
> >> It appears that tightvncserver installs as:
> >> 
> >>     /usr/bin/Xtightvnc
> >
> >
> > This is actually intentional. The reason is that you should start
> > it with the command tightvncserver. The Xtightvnc is likely not
> > what you want to start.
> 
> In this case the /usr/bin/Xtightvnc is a user command, because it's
> installed under /usr/bin. Non-user commands get installaed elsewhere,
> like /var/lib/<package>
> 
> > I mean you probably start X with "startx" and not with the
> > "Xorg" command, right?
> 
> Usually yes, but it can be invoked directly. This happens in cases where
> you need to debug things, and reduce layers that may affect the command
> invocation.
> 
> Having all user callable programs, how seldom callable they be, in
> lowercase would be more clean approach[1]. It would 1)reduce typing
> mistakes both in command line and scripts 2) allow TAB completion to
> work and 3) would not create special cases; e.g. for find(1)
> 
> Jari
> 
> [1] Modern gnome-* and kde* commands are good examples of this.
> 

-- 
 --------------------- Ola Lundqvist ---------------------------
/  [email protected]                     Annebergsslingan 37      \
|  [email protected]                      654 65 KARLSTAD          |
|  http://inguza.com/                  +46 (0)70-332 1551       |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---------------------------------------------------------------



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to