[ViewVC] Diff of: cvs/rxvt-unicode/README.FAQ

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.20 by root, Sat Dec 24 12:55:17 2005 UTC vs.
Revision 1.24 by root, Wed Jan 11 19:55:33 2006 UTC

         Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k),
         this still fares rather well. And compared to some monsters like
         gnome-terminal (21152k + extra 4204k in separate processes) or
         konsole (22200k + extra 43180k in daemons that stay around after
-        exit, plus half aminute of startup time, including the hundreds of
+        exit, plus half a minute of startup time, including the hundreds of
         warnings it spits out), it fares extremely well *g*.
     Why C++, isn't that unportable/bloated/uncool?
         Is this a question? :) It comes up very often. The simple answer is:
         I had to write it, and C++ allowed me to write and maintain it in a
         terminal as an example embedding application.
     How do I know which rxvt-unicode version I'm using?
         The version number is displayed with the usage (-h). Also the escape
         sequence "ESC [ 8 n" sets the window title to the version number.
-        When using the urxvtc client, the version displayed is that of the
+        When using the rxvtc client, the version displayed is that of the
         daemon.
     I am using Debian GNU/Linux and have a problem...
         The Debian GNU/Linux package of rxvt-unicode in sarge contains large
         patches that considerably change the behaviour of rxvt-unicode.
         For other problems that also affect the Debian package, you can and
         probably should use the Debian BTS, too, because, after all, it's
         also a bug in the Debian version and it serves as a reminder for
         other users that might encounter the same issue.
+    I am maintaining rxvt-unicode for distribution/OS XXX, any
+    recommendation?
+        You should build one binary with the default options. configure now
+        enables most useful options, and the trend goes to making them
+        runtime-switchable, too, so there is usually no drawback to enbaling
+        them, except higher disk and possibly memory usage. The perl
+        interpreter should be enabled, as important functionality (menus,
+        selection, likely more in the future) depends on it.
+        You should not overwrite the "perl-ext-common" snd "perl-ext"
+        resources system-wide (except maybe with "defaults"). This will
+        result in useful behaviour. If your distribution aims at low memory,
+        add an empty "perl-ext-common" resource to the app-defaults file.
+        This will keep the perl interpreter disabled until the user enables
+        it.
+        If you can/want build more binaries, I recommend building a minimal
+        one with "--disable-everything" (very useful) and a maximal one with
+        "--enable-everything" (less useful, it will be very big due to a lot
+        of encodings built-in that increase download times and are rarely
+        used).
+    I need to make it setuid/setgid to support utmp/ptys on my OS, is this
+    safe?
+        Likely not. While I honestly try to make it secure, and am probably
+        not bad at it, I think it is simply unreasonable to expect all of
+        freetype + fontconfig + xft + xlib + perl + ... + rxvt-unicode
+        itself to all be secure. Also, rxvt-unicode disables some options
+        when it detects that it runs setuid or setgid, which is not nice.
+        Besides, with the embedded perl interpreter the possibility for
+        security problems easily multiplies.
+        Elevated privileges are only required for utmp and pty operations on
+        some systems (for example, GNU/Linux doesn't need any extra
+        privileges for ptys, but some need it for utmp support). It is
+        planned to mvoe this into a forked handler process, but this is not
+        yet done.
+        So, while setuid/setgid operation is supported and not a problem on
+        your typical single-user-no-other-logins unix desktop, always
+        remember that its an awful lot of code, most of which isn't checked
+        for security issues regularly.
     When I log-in to another system it tells me about missing terminfo data?
         The terminal description used by rxvt-unicode is not as widely
         available as that for xterm, or even rxvt (for which the same
         problem often arises).
     "tic" outputs some error when compiling the terminfo entry.
         Most likely it's the empty definition for "enacs=". Just replace it
         by "enacs=\E[0@" and try again.
-    "bash"'s readline does not work correctly under urxvt.
+    "bash"'s readline does not work correctly under rxvt.
     I need a termcap file entry.
         One reason you might want this is that some distributions or
         operating systems still compile some programs using the
         long-obsoleted termcap library (Fedora Core's bash is one example)
         and rely on a termcap entry for "rxvt-unicode".
         indeed look correct.
         In that case, select a font of your taste and add it to the font
         list, e.g.:
-           urxvt -fn basefont,font2,font3...
+           rxvt -fn basefont,font2,font3...
         When rxvt-unicode sees a character, it will first look at the base
         font. If the base font does not contain the character, it will go to
         the next font, and so on. Specifying your own fonts will also speed
         up this search and use less resources within rxvt-unicode and the
     Mouse cut/paste suddenly no longer works.
         Make sure that mouse reporting is actually turned off since killing
         some editors prematurely may leave the mouse in mouse report mode.
         I've heard that tcsh may use mouse reporting unless it otherwise
         specified. A quick check is to see if cut/paste works when the Alt
-        or Shift keys are depressed. See urxvt(7)
+        or Shift keys are depressed. See rxvt(7)
     What's with this bold/blink stuff?
         If no bold colour is set via "colorBD:", bold will invert text using
         the standard foreground colour.
            URxvt.color6:       #73f7ff
            URxvt.color14:      #73f7ff
            URxvt.color7:       #e1dddd
            URxvt.color15:      #e1dddd
-    How can I start urxvtd in a race-free way?
+    How can I start rxvtd in a race-free way?
-        Try "urxvtd -f -o", which tells urxvtd to open the display, create
+        Try "rxvtd -f -o", which tells rxvtd to open the display, create the
-        the listening socket and then fork.
+        listening socket and then fork.
     What's with the strange Backspace/Delete key behaviour?
         Assuming that the physical Backspace key corresponds to the
         BackSpace keysym (not likely for Linux ... see the following
         question) there are two standard values that can be used for
         For starting a new rxvt-unicode:
            # use Backspace = ^H
            $ stty erase ^H
-           $ urxvt
+           $ rxvt
            # use Backspace = ^?
            $ stty erase ^?
-           $ urxvt
+           $ rxvt
-        Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in urxvt(7).
+        Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
         For an existing rxvt-unicode:
            # use Backspace = ^H
            $ stty erase ^H
         There are some compile-time selections available via configure.
         Unless you have run "configure" with the "--disable-resources"
         option you can use the `keysym' resource to alter the keystrings
         associated with keysyms.
-        Here's an example for a URxvt session started using "urxvt -name
+        Here's an example for a URxvt session started using "rxvt -name
         URxvt"
            URxvt.keysym.Home:          \033[1~
            URxvt.keysym.End:           \033[4~
            URxvt.keysym.C-apostrophe:  \033<C-'>

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing rxvt-unicode/README.FAQ (file contents): Revision 1.20 by root, Sat Dec 24 12:55:17 2005 UTC vs. Revision 1.24 by root, Wed Jan 11 19:55:33 2006 UTC

Diff Legend

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.20 by root, Sat Dec 24 12:55:17 2005 UTC vs.
Revision 1.24 by root, Wed Jan 11 19:55:33 2006 UTC