Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Nikita V. Youshchenko 
> They.  Will.  Not.  Read.

Maybe there will be somewhat less complains from those who don't read, if 
debconf stuff will calculate and store a checksum of autogenerated part of 
the file, and later don't touch it (or give extra warnings before touching) 
if the checksum does not match.


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

Bug#166177: xserver-common: dexconf creates temporary directory outside /tmp

2002-10-24 Thread herbert 
Package: xserver-common
Version: 4.1.0-17
Severity: normal

dexconf created a temporary directory in my home directory:

$ ls -d ~/dex*
/home/gondolin/herbert/dexconf-tmp-22005
$

This is a bad idea because if dexconf is killed with SIGKILL, or if
there is a bug in its signal handling when it is terminated more
gracefully, the directory will be left behind until it is deleted
manually.

In my case it called bomb because I wasn't running it as root so
you probably want to setup an EXIT trap as well.

Please put this directory in /tmp by default where it will be cleaned
automatically.  You can always use ${TMPDIR:-/tmp} so that users can
override it if they wish.

-- System Information
Debian Release: testing/unstable
Kernel Version: Linux gondolin 2.4.18-686-smp #1 SMP Sun Apr 14 12:07:19 EST 2002 i686 
unknown unknown GNU/Linux

Versions of the packages xserver-common depends on:
ii  debconf1.2.10 Debian configuration management system
ii  libc6  2.2.5-14.3 GNU C Library: Shared libraries and Timezone
ii  xfree86-common 4.1.0-17   X Window System (XFree86) infrastructure



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

Bug#165899: xlibs-dbg: no unstripped libs for /usr/X11R6/lib/X11/locale/common/*

2002-10-24 Thread MINAMI Hirokazu 
I've thought some more deeply about the usage of unstripped libs.

On Tue, 22 Oct 2002 11:31:14 -0500
[EMAIL PROTECTED] wrote:

> Package: xlibs-dbg
> [...]
>  Unstripped versions of Xlib's internationalization loadable modules are
>  provided in /usr/X11R6/lib/debug/X11/locale/common.  Note that if you wish
>  to debug these modules, you will need to set XLOCALEDIR to
>  /usr/X11R6/lib/debug/X11/locale.  Also note that for security reasons,
>  unprivileged users are unable to override XLOCALEDIR in this way, so you
>  may have to perform your debugging of the Xlib modules as root.

It may worth mentioning that by intercepting dlopen() call,
 we can make a process to load alternate(unstripped) modules
without having root privilege.

How about creating dlwrap.c which looks like
BEGIN HERE
#define _GNU_SOURCE 1
#include
#include
void * dlopen(const char *filename, int flag){
static void * (* fptr)() = 0;
char buffer[] = "/usr/X11R6/lib/debug/X11/locale/common/0123456789ABCDEF";
if (!fptr) {
fptr = dlsym(RTLD_NEXT, "dlopen");
if (!fptr) 
return 0;
}
if ((strncmp("/usr/X11R6/lib/X11/locale/common/", filename, 33) == 0) && 
(strlen(filename) < 33+16)){
memcpy(buffer+32, filename+33, strlen(filename) -32);
return ((*fptr)(buffer, flag));
}
return ((*fptr)(filename, flag));
}
END HERE

and doing
 ~$ gcc -shared -o dlwrap.so dlwrap.c -ldl
 ~$ LD_PRELOAD=./dlwrap.so FOOBAR
?



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

Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Susan Kleinmann 
Hello,

On Wed, Oct 23, 2002 at 05:16:23PM -0500, Branden Robinson wrote:
> You can tell people to put their shit outside the debconf area, but they
> won't.  

Here are two peripherally related suggestions that might help:

1.  There is at least one other package that has a do-not-configure-here
component to its file: grub.  I wonder if it might be possible to find
some commonalities between the way grub tells users to keep their mits
off of various sections, and the way the XF86Config file does it?  Just
using the same words or the same case or the same placement in the file
for the warning might be a start.  My point is that if there is a common 
set of characteristics in several programs that tell users to keep out,
then a broader group of users might come to expect and know to look for 
"do-not-touch" sections.
It would also help users if the utilities that manipulated files
that were only partially user-changeable had common names, or some
other common features.

2.  It might be interesting to develop either colorized vim or emacs
modes that were invoked when editing only-partially-editable files, such
that the "hands-off" part appeared, say, in some distinct color.

Cheers,
Susan


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

Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Oliver Kurth 
On Thu, Oct 24, 2002 at 09:26:48AM -0400, Susan Kleinmann wrote:
> Hello,
> 
> On Wed, Oct 23, 2002 at 05:16:23PM -0500, Branden Robinson wrote:
> > You can tell people to put their shit outside the debconf area, but they
> > won't.  
> 
> Here are two peripherally related suggestions that might help:
> 
> 1.  There is at least one other package that has a do-not-configure-here
> component to its file: grub.  I wonder if it might be possible to find

There is another one: masqmail (mine). I used xfree86 as an example. The
main conf has these lines on top, copied from /etc/X11/XF86Config-4:

### BEGIN DEBCONF SECTION
# Do not edit within this region if you want your changes to be 
preserved by
# debconf.  Instead, make changes after the "### END DEBCONF SECTION" 
line.

I have no idea how someone can miss those lines...

> some commonalities between the way grub tells users to keep their mits
> off of various sections, and the way the XF86Config file does it?  Just
> using the same words or the same case or the same placement in the file
> for the warning might be a start.  My point is that if there is a common 
> set of characteristics in several programs that tell users to keep out,
> then a broader group of users might come to expect and know to look for 
> "do-not-touch" sections.
> It would also help users if the utilities that manipulated files
> that were only partially user-changeable had common names, or some
> other common features.
> 
> 2.  It might be interesting to develop either colorized vim or emacs
> modes that were invoked when editing only-partially-editable files, such
> that the "hands-off" part appeared, say, in some distinct color.

That's an idea.

Greetings,
Oliver

-- 
DAM approval waiting time: 127 days.
See http://nm.debian.org/nmstatus.php?email=oku%40masqmail.cx



msg04289/pgp0.pgp
Description: PGP signature

Bug#166234: xserver-xfree86: [i810] Xv doesn't work with i810 in X 4.2.1

2002-10-24 Thread Mattias Ostergren 
Package: xserver-xfree86
Version: 4.2.1-3
Severity: normal
Tags: sid

Xv doesn't work with i810 in X 4.2.1 (it worked with X 4.1.x).
When trying to play movies with xine or mplayer using Xv as output the movie
window only contains the keycolor that Xv should overlay.

xvinfo output:

X-Video Extension version 2.2
screen #0
  Adaptor #0: "I810 Video Overlay"
number of ports: 1
port base: 55
operations supported: PutImage =

supported visuals:
  depth 16, visualID 0x23
  depth 16, visualID 0x24
number of attributes: 3
  "XV_COLORKEY" (range 0 to 16777215)
  client settable attribute
  client gettable attribute (current value is 2110)
  "XV_BRIGHTNESS" (range -128 to 127)
  client settable attribute
  client gettable attribute (current value is 0)
  "XV_CONTRAST" (range 0 to 255)
  client settable attribute
  client gettable attribute (current value is 64)
maximum XvImage size: 1440 x 1080
Number of image formats: 4
  id: 0x32595559 (YUY2)
guid: 59555932--0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)
  id: 0x32315659 (YV12)
guid: 59563132--0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
  id: 0x30323449 (I420)
guid: 49343230--0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
  id: 0x59565955 (UYVY)
guid: 55595659--0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)


-- Package-specific info:
00:01.0 VGA compatible controller: Intel Corp. 82810 DC-100 CGC [Chipset Gr=
aphics Controller] (rev 02)
00:01.0 Class 0300: 8086:7123 (rev 02)


Section "Files"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
#FontPath "/usr/X11R6/lib/X11/fonts/TrueType"
FontPath "/usr/local/share/fonts/ttfonts"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi"
FontPath"/usr/lib/X11/fonts/Type1"
FontPath"/usr/lib/X11/fonts/Speedo"
FontPath"/usr/lib/X11/fonts/75dpi"
EndSection

### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) generated by dexconf, the
# Debian X Configuration tool, using values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# If you want your changes to this file preserved by dexconf, only make cha=
nges
# before the "### BEGIN DEBCONF SECTION" line above, and/or after the
# "### END DEBCONF SECTION" line below.
#
# To change things within the debconf section, run the command:
#   dpkg-reconfigure xserver-xfree86
# as root.  Also see "How do I add custom sections to a dexconf-generated
# XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz.

Section "Module"
Load"GLcore"
Load"bitmap"
Load"dbe"
Load"ddc"
Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"record"
Load"speedo"
Load"type1"
Load"vbe"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "keyboard"
Option  "CoreKeyboard"
Option  "XkbRules"  "xfree86"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "se"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/psaux"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
EndSection

Section "InputDevice"
Identifier  "Generic Mouse"
Driver  "mouse"
Option  "SendCoreEvents""true"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
EndSection

Section "Device"
Identifier  "i810"
Driver  "i810"
EndSection

Section "Monitor"
Identifier  "Philips 17B"
HorizSync   30-66
VertRefresh 50-160
Option  "DPMS"
EndSection

Section "Screen"
Identifier  "Default Screen"
Device  "i810"
Monitor "Philips 17B"
DefaultDepth16
SubSection "Display

Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Malte Cornils 
Hi,

On Thu, Oct 24, 2002 at 12:19:20PM -0500, Branden Robinson wrote:
> > 2.  It might be interesting to develop either colorized vim or emacs
> > modes that were invoked when editing only-partially-editable files, such
> > that the "hands-off" part appeared, say, in some distinct color.
> 
> A nice idea, but my guess is that a lot of the people who struggle with
> concepts like "put your changes before ### BEGIN DEBCONF AREA or after
> ### END DEBCONF AREA" also aren't using Vim or Emacs.

Well, as one of those who edit config files but don't grok the ### HANDS OFF
HERE concept, maybe I should explain why I did it (and yes, now I've seen
the error of my ways and lo and behold... it works just like Branden
promises!). The reason is... it feels bad. You duplicate one of the sections
in the debconf area, change it a little and put it up front. Two identical
section headers in config files just go against every ingrained belief in
fighting redundancy. Also, I was not so sure where to put my updated
section.. before the DEBCONF area? After it? When would *my* section win
over the debconf area section, and when would it lose? (Sure it's
documented. But it's not... intuitive.)

Taking a look at the other side, I must confess that just deactivating
debconf support for the X config file feels bad, too (like an evil, though
supported, hack). Luckily, I was bright enough not to complain about "that
weird ### BEGIN DEBCONF AREA stuff" and almost settled with re-updating my X
config file after every X update. Until I got a clue.

You may now officially brand me as stupid, but maybe this relevation(sp?) 
helps design a better system/a bigger warning message/whatever.

-Malte #8-)

(Maybe a debianplanet vote on "Did you know you can put your own config
changes into /etc/X11/XF86Config-4?" - "No. What's this?" "No. I do this
manually." "No, it felt forbidden" "Yes. I'm Branden." could shed some
additional light on this important issue... :))


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

Re: xfree86 4.2.1-0pre1v1 available at the X Strike Force

2002-10-24 Thread Richard Zidlicky 
On Wed, Oct 23, 2002 at 10:23:38AM -0700, Erik van Roode wrote:
> At 09:36 10/22/2002, Branden Robinson wrote:
> 
> >I beseech you to help debug and fix the XFree86 module loader on m68k.
> 
> If I understand correctly the issue with 68040/68060 is cache coherency. 
> When looking
> at the 68040 manual from Motorola, (page 4-10):
> 
>  >  It is imperative that a CPUSHA instruction be executed before the 
> execution of the first
> self-modified instruction.
> 
> (68060 manual has identical text)
> 
> There has been some discussion about cache flushing strategy (last 
> January?), and
> CPUSHA is expensive, but  it should fix the loader?

It would fix the loader, the expensive part is the system call
overhead. CPUSH* are privileged instruction so you need a syscall 
for each flush.
Next thing to try is to use the move16 instruction to flush the
cache, but iirc there is nothing like that on 68020-30.

Richard


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

Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Branden Robinson 
On Thu, Oct 24, 2002 at 09:26:48AM -0400, Susan Kleinmann wrote:
> Here are two peripherally related suggestions that might help:
> 
> 1.  There is at least one other package that has a do-not-configure-here
> component to its file: grub.  I wonder if it might be possible to find
> some commonalities between the way grub tells users to keep their mits
> off of various sections, and the way the XF86Config file does it?  Just
> using the same words or the same case or the same placement in the file
> for the warning might be a start.  My point is that if there is a common 
> set of characteristics in several programs that tell users to keep out,
> then a broader group of users might come to expect and know to look for 
> "do-not-touch" sections.
> It would also help users if the utilities that manipulated files
> that were only partially user-changeable had common names, or some
> other common features.

Well, Matt Zimmerman has a proposal for some standardized debconfage
that would basically duplicate the functionality of dpkg's
conffile-update prompting, but for configuration files that aren't
conffiles -- like XF86Config-4.

His proposal is generalized, so I imagine it could be applied to any
package that works this way.  We'll pilot-test it with xserver-xfree86
and see how it goes.  If, eventually, we can teach dpkg to use it for
real conffiles as well, the last big hurdle to eliminating dpkg's
dependency on an interactive terminal will have been removed, as I
understand it.

> 2.  It might be interesting to develop either colorized vim or emacs
> modes that were invoked when editing only-partially-editable files, such
> that the "hands-off" part appeared, say, in some distinct color.

A nice idea, but my guess is that a lot of the people who struggle with
concepts like "put your changes before ### BEGIN DEBCONF AREA or after
### END DEBCONF AREA" also aren't using Vim or Emacs.

-- 
G. Branden Robinson|Any man who does not realize that
Debian GNU/Linux   |he is half an animal is only half a
[EMAIL PROTECTED] |man.
http://people.debian.org/~branden/ |-- Thornton Wilder



msg04293/pgp0.pgp
Description: PGP signature

xvidtune: floating point exception

2002-10-24 Thread Oleg 
Hi

This may or may not be considered a bug, because I'm using version 4.2.1-3 of 
xbase-clients from 
deb http://people.debian.org/~blade/woody/i386/ ./
on Woody.

When I run xvidtune, it gives

Vendor: AutoDetected, Model: AutoDetected
Num hsync: 1, Num vsync: 1
hsync range 0:  30.00 -  90.00
vsync range 0:  56.00 -  83.00
Floating point exception

(The last line goes to STDERR)

Oleg
P.S. Cc: to me please.


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

Re: xvidtune: floating point exception

2002-10-24 Thread Drew Parsons 
On Thu, Oct 24, 2002 at 05:24:47PM -0400, Oleg wrote:
> Hi
> 
> This may or may not be considered a bug, because I'm using version 4.2.1-3 of 
> xbase-clients from 
> deb http://people.debian.org/~blade/woody/i386/ ./
> on Woody.
> 
> When I run xvidtune, it gives
> 
> Vendor: AutoDetected, Model: AutoDetected
> Num hsync: 1, Num vsync: 1
> hsync range 0:  30.00 -  90.00
> vsync range 0:  56.00 -  83.00
> Floating point exception
> 

I get the f.p. exception on unstable too (4.2.1-2)

Drew

-- 
PGP public key available at http://people.debian.org/~dparsons/drewskey.txt
Fingerprint: A110 EAE1 D7D2 8076 5FE0  EC0A B6CE 7041 6412 4E4A


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

Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Manoj Srivastava 
Hi,
>>"Branden" == Branden Robinson <[EMAIL PROTECTED]> writes:

 Branden> On Wed, Oct 23, 2002 at 10:09:58PM +0200, Andreas Metzler wrote:
 >> Time for a third opinion: I think your setup circumvents the problem
 >> (parsing XF86Config) _very_ nicely with little overhead. It allows me
 >> to customize any section I want while still letting debconf handle the
 >> rest. Basically I just have to copy it and move it outside of the debconf
 >> part.

 Branden> Well, that was the use case I had in mind when I wrote
 Branden> XFree86's debconf support, but judging by the dozens of
 Branden> config files I've seen, that's not the use case in widest
 Branden> deployment.


 Branden> Cutting and pasting a block of text is Too Hard.

Perhaps you should add that to the comment: that the unit to
 copy is a section; and any section may be copied at will. 

 Branden> The scenario you enjoy will die, because People Will Not
 Branden> Read.  It's also arguably a violation of way Debconf is
 Branden> supposed to work (there's not supposed to be any such thing
 Branden> as a "debconf area", and for files that aren't as
 Branden> potentially insanely complex as XF86Config, I agree), so I'm
 Branden> not getting any support from the Orthodox Church of Debconf,
 Branden> either.

Perhaps the solution is to grab the area between the debconf
 markers, store a md5sum of that area, and act like dpkg does with
 conffiles: allow the user to accept, refuse, view diffs, of the
 section inside the debconf area.

Once I get ucf cleaned up and insert the diff3 functionality
 in there, you can use ucf to really preserve user changes.

manoj
-- 
 People will do tomorrow what they did today because that is what they
 did yesterday.
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


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

Processed: retitle 166234 to xserver-xfree86: [i810] Xv windows show only chromakey (regression from 4.1.0) on i810-dc100 rev 2

2002-10-24 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

> retitle 166234 xserver-xfree86: [i810] Xv windows show only chromakey (regression 
>from 4.1.0) on i810-dc100 rev 2
Bug#166234: xserver-xfree86: [i810] Xv doesn't work with i810 in X 4.2.1
Changed Bug title.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



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

Re: xvidtune: floating point exception

2002-10-24 Thread Branden Robinson 
Already filed as #89323 and #94888.

-- 
G. Branden Robinson|Build a fire for a man, and he'll
Debian GNU/Linux   |be warm for a day.  Set a man on
[EMAIL PROTECTED] |fire, and he'll be warm for the
http://people.debian.org/~branden/ |rest of his life. - Terry Pratchett



msg04298/pgp0.pgp
Description: PGP signature

Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Nikita V. Youshchenko 
> They.  Will.  Not.  Read.

Maybe there will be somewhat less complains from those who don't read, if 
debconf stuff will calculate and store a checksum of autogenerated part of 
the file, and later don't touch it (or give extra warnings before touching) 
if the checksum does not match.

Bug#166177: xserver-common: dexconf creates temporary directory outside /tmp

2002-10-24 Thread herbert 
Package: xserver-common
Version: 4.1.0-17
Severity: normal

dexconf created a temporary directory in my home directory:

$ ls -d ~/dex*
/home/gondolin/herbert/dexconf-tmp-22005
$

This is a bad idea because if dexconf is killed with SIGKILL, or if
there is a bug in its signal handling when it is terminated more
gracefully, the directory will be left behind until it is deleted
manually.

In my case it called bomb because I wasn't running it as root so
you probably want to setup an EXIT trap as well.

Please put this directory in /tmp by default where it will be cleaned
automatically.  You can always use ${TMPDIR:-/tmp} so that users can
override it if they wish.

-- System Information
Debian Release: testing/unstable
Kernel Version: Linux gondolin 2.4.18-686-smp #1 SMP Sun Apr 14 12:07:19 EST 
2002 i686 unknown unknown GNU/Linux

Versions of the packages xserver-common depends on:
ii  debconf1.2.10 Debian configuration management system
ii  libc6  2.2.5-14.3 GNU C Library: Shared libraries and Timezone
ii  xfree86-common 4.1.0-17   X Window System (XFree86) infrastructure

Bug#165899: xlibs-dbg: no unstripped libs for /usr/X11R6/lib/X11/locale/common/*

2002-10-24 Thread MINAMI Hirokazu 
I've thought some more deeply about the usage of unstripped libs.

On Tue, 22 Oct 2002 11:31:14 -0500
[EMAIL PROTECTED] wrote:

> Package: xlibs-dbg
> [...]
>  Unstripped versions of Xlib's internationalization loadable modules are
>  provided in /usr/X11R6/lib/debug/X11/locale/common.  Note that if you wish
>  to debug these modules, you will need to set XLOCALEDIR to
>  /usr/X11R6/lib/debug/X11/locale.  Also note that for security reasons,
>  unprivileged users are unable to override XLOCALEDIR in this way, so you
>  may have to perform your debugging of the Xlib modules as root.

It may worth mentioning that by intercepting dlopen() call,
 we can make a process to load alternate(unstripped) modules
without having root privilege.

How about creating dlwrap.c which looks like
BEGIN HERE
#define _GNU_SOURCE 1
#include
#include
void * dlopen(const char *filename, int flag){
static void * (* fptr)() = 0;
char buffer[] = 
"/usr/X11R6/lib/debug/X11/locale/common/0123456789ABCDEF";
if (!fptr) {
fptr = dlsym(RTLD_NEXT, "dlopen");
if (!fptr) 
return 0;
}
if ((strncmp("/usr/X11R6/lib/X11/locale/common/", filename, 33) == 0) 
&& (strlen(filename) < 33+16)){
memcpy(buffer+32, filename+33, strlen(filename) -32);
return ((*fptr)(buffer, flag));
}
return ((*fptr)(filename, flag));
}
END HERE

and doing
 ~$ gcc -shared -o dlwrap.so dlwrap.c -ldl
 ~$ LD_PRELOAD=./dlwrap.so FOOBAR
?

Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Susan Kleinmann 
Hello,

On Wed, Oct 23, 2002 at 05:16:23PM -0500, Branden Robinson wrote:
> You can tell people to put their shit outside the debconf area, but they
> won't.  

Here are two peripherally related suggestions that might help:

1.  There is at least one other package that has a do-not-configure-here
component to its file: grub.  I wonder if it might be possible to find
some commonalities between the way grub tells users to keep their mits
off of various sections, and the way the XF86Config file does it?  Just
using the same words or the same case or the same placement in the file
for the warning might be a start.  My point is that if there is a common 
set of characteristics in several programs that tell users to keep out,
then a broader group of users might come to expect and know to look for 
"do-not-touch" sections.
It would also help users if the utilities that manipulated files
that were only partially user-changeable had common names, or some
other common features.

2.  It might be interesting to develop either colorized vim or emacs
modes that were invoked when editing only-partially-editable files, such
that the "hands-off" part appeared, say, in some distinct color.

Cheers,
Susan

Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Oliver Kurth 
On Thu, Oct 24, 2002 at 09:26:48AM -0400, Susan Kleinmann wrote:
> Hello,
> 
> On Wed, Oct 23, 2002 at 05:16:23PM -0500, Branden Robinson wrote:
> > You can tell people to put their shit outside the debconf area, but they
> > won't.  
> 
> Here are two peripherally related suggestions that might help:
> 
> 1.  There is at least one other package that has a do-not-configure-here
> component to its file: grub.  I wonder if it might be possible to find

There is another one: masqmail (mine). I used xfree86 as an example. The
main conf has these lines on top, copied from /etc/X11/XF86Config-4:

### BEGIN DEBCONF SECTION
# Do not edit within this region if you want your changes to be 
preserved by
# debconf.  Instead, make changes after the "### END DEBCONF SECTION" 
line.

I have no idea how someone can miss those lines...

> some commonalities between the way grub tells users to keep their mits
> off of various sections, and the way the XF86Config file does it?  Just
> using the same words or the same case or the same placement in the file
> for the warning might be a start.  My point is that if there is a common 
> set of characteristics in several programs that tell users to keep out,
> then a broader group of users might come to expect and know to look for 
> "do-not-touch" sections.
> It would also help users if the utilities that manipulated files
> that were only partially user-changeable had common names, or some
> other common features.
> 
> 2.  It might be interesting to develop either colorized vim or emacs
> modes that were invoked when editing only-partially-editable files, such
> that the "hands-off" part appeared, say, in some distinct color.

That's an idea.

Greetings,
Oliver

-- 
DAM approval waiting time: 127 days.
See http://nm.debian.org/nmstatus.php?email=oku%40masqmail.cx


pgpqaV8z7ZRcS.pgp
Description: PGP signature

Re: xfree86 4.2.1-0pre1v1 available at the X Strike Force

2002-10-24 Thread Richard Zidlicky 
On Wed, Oct 23, 2002 at 10:23:38AM -0700, Erik van Roode wrote:
> At 09:36 10/22/2002, Branden Robinson wrote:
> 
> >I beseech you to help debug and fix the XFree86 module loader on m68k.
> 
> If I understand correctly the issue with 68040/68060 is cache coherency. 
> When looking
> at the 68040 manual from Motorola, (page 4-10):
> 
>  >  It is imperative that a CPUSHA instruction be executed before the 
> execution of the first
> self-modified instruction.
> 
> (68060 manual has identical text)
> 
> There has been some discussion about cache flushing strategy (last 
> January?), and
> CPUSHA is expensive, but  it should fix the loader?

It would fix the loader, the expensive part is the system call
overhead. CPUSH* are privileged instruction so you need a syscall 
for each flush.
Next thing to try is to use the move16 instruction to flush the
cache, but iirc there is nothing like that on 68020-30.

Richard

Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Branden Robinson 
On Thu, Oct 24, 2002 at 09:26:48AM -0400, Susan Kleinmann wrote:
> Here are two peripherally related suggestions that might help:
> 
> 1.  There is at least one other package that has a do-not-configure-here
> component to its file: grub.  I wonder if it might be possible to find
> some commonalities between the way grub tells users to keep their mits
> off of various sections, and the way the XF86Config file does it?  Just
> using the same words or the same case or the same placement in the file
> for the warning might be a start.  My point is that if there is a common 
> set of characteristics in several programs that tell users to keep out,
> then a broader group of users might come to expect and know to look for 
> "do-not-touch" sections.
> It would also help users if the utilities that manipulated files
> that were only partially user-changeable had common names, or some
> other common features.

Well, Matt Zimmerman has a proposal for some standardized debconfage
that would basically duplicate the functionality of dpkg's
conffile-update prompting, but for configuration files that aren't
conffiles -- like XF86Config-4.

His proposal is generalized, so I imagine it could be applied to any
package that works this way.  We'll pilot-test it with xserver-xfree86
and see how it goes.  If, eventually, we can teach dpkg to use it for
real conffiles as well, the last big hurdle to eliminating dpkg's
dependency on an interactive terminal will have been removed, as I
understand it.

> 2.  It might be interesting to develop either colorized vim or emacs
> modes that were invoked when editing only-partially-editable files, such
> that the "hands-off" part appeared, say, in some distinct color.

A nice idea, but my guess is that a lot of the people who struggle with
concepts like "put your changes before ### BEGIN DEBCONF AREA or after
### END DEBCONF AREA" also aren't using Vim or Emacs.

-- 
G. Branden Robinson|Any man who does not realize that
Debian GNU/Linux   |he is half an animal is only half a
[EMAIL PROTECTED] |man.
http://people.debian.org/~branden/ |-- Thornton Wilder


pgpc2JJEq4cQi.pgp
Description: PGP signature

Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Malte Cornils 
Hi,

On Thu, Oct 24, 2002 at 12:19:20PM -0500, Branden Robinson wrote:
> > 2.  It might be interesting to develop either colorized vim or emacs
> > modes that were invoked when editing only-partially-editable files, such
> > that the "hands-off" part appeared, say, in some distinct color.
> 
> A nice idea, but my guess is that a lot of the people who struggle with
> concepts like "put your changes before ### BEGIN DEBCONF AREA or after
> ### END DEBCONF AREA" also aren't using Vim or Emacs.

Well, as one of those who edit config files but don't grok the ### HANDS OFF
HERE concept, maybe I should explain why I did it (and yes, now I've seen
the error of my ways and lo and behold... it works just like Branden
promises!). The reason is... it feels bad. You duplicate one of the sections
in the debconf area, change it a little and put it up front. Two identical
section headers in config files just go against every ingrained belief in
fighting redundancy. Also, I was not so sure where to put my updated
section.. before the DEBCONF area? After it? When would *my* section win
over the debconf area section, and when would it lose? (Sure it's
documented. But it's not... intuitive.)

Taking a look at the other side, I must confess that just deactivating
debconf support for the X config file feels bad, too (like an evil, though
supported, hack). Luckily, I was bright enough not to complain about "that
weird ### BEGIN DEBCONF AREA stuff" and almost settled with re-updating my X
config file after every X update. Until I got a clue.

You may now officially brand me as stupid, but maybe this relevation(sp?) 
helps design a better system/a bigger warning message/whatever.

-Malte #8-)

(Maybe a debianplanet vote on "Did you know you can put your own config
changes into /etc/X11/XF86Config-4?" - "No. What's this?" "No. I do this
manually." "No, it felt forbidden" "Yes. I'm Branden." could shed some
additional light on this important issue... :))

Bug#166234: xserver-xfree86: [i810] Xv doesn't work with i810 in X 4.2.1

2002-10-24 Thread Mattias Ostergren 
Package: xserver-xfree86
Version: 4.2.1-3
Severity: normal
Tags: sid

Xv doesn't work with i810 in X 4.2.1 (it worked with X 4.1.x).
When trying to play movies with xine or mplayer using Xv as output the movie
window only contains the keycolor that Xv should overlay.

xvinfo output:

X-Video Extension version 2.2
screen #0
  Adaptor #0: "I810 Video Overlay"
number of ports: 1
port base: 55
operations supported: PutImage =

supported visuals:
  depth 16, visualID 0x23
  depth 16, visualID 0x24
number of attributes: 3
  "XV_COLORKEY" (range 0 to 16777215)
  client settable attribute
  client gettable attribute (current value is 2110)
  "XV_BRIGHTNESS" (range -128 to 127)
  client settable attribute
  client gettable attribute (current value is 0)
  "XV_CONTRAST" (range 0 to 255)
  client settable attribute
  client gettable attribute (current value is 64)
maximum XvImage size: 1440 x 1080
Number of image formats: 4
  id: 0x32595559 (YUY2)
guid: 59555932--0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)
  id: 0x32315659 (YV12)
guid: 59563132--0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
  id: 0x30323449 (I420)
guid: 49343230--0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
  id: 0x59565955 (UYVY)
guid: 55595659--0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)


-- Package-specific info:
00:01.0 VGA compatible controller: Intel Corp. 82810 DC-100 CGC [Chipset Gr=
aphics Controller] (rev 02)
00:01.0 Class 0300: 8086:7123 (rev 02)


Section "Files"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
#FontPath "/usr/X11R6/lib/X11/fonts/TrueType"
FontPath "/usr/local/share/fonts/ttfonts"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi"
FontPath"/usr/lib/X11/fonts/Type1"
FontPath"/usr/lib/X11/fonts/Speedo"
FontPath"/usr/lib/X11/fonts/75dpi"
EndSection

### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) generated by dexconf, the
# Debian X Configuration tool, using values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# If you want your changes to this file preserved by dexconf, only make cha=
nges
# before the "### BEGIN DEBCONF SECTION" line above, and/or after the
# "### END DEBCONF SECTION" line below.
#
# To change things within the debconf section, run the command:
#   dpkg-reconfigure xserver-xfree86
# as root.  Also see "How do I add custom sections to a dexconf-generated
# XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz.

Section "Module"
Load"GLcore"
Load"bitmap"
Load"dbe"
Load"ddc"
Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"record"
Load"speedo"
Load"type1"
Load"vbe"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "keyboard"
Option  "CoreKeyboard"
Option  "XkbRules"  "xfree86"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "se"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/psaux"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
EndSection

Section "InputDevice"
Identifier  "Generic Mouse"
Driver  "mouse"
Option  "SendCoreEvents""true"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
EndSection

Section "Device"
Identifier  "i810"
Driver  "i810"
EndSection

Section "Monitor"
Identifier  "Philips 17B"
HorizSync   30-66
VertRefresh 50-160
Option  "DPMS"
EndSection

Section "Screen"
Identifier  "Default Screen"
Device  "i810"
Monitor "Philips 17B"
DefaultDepth16
SubSection "Display

xvidtune: floating point exception

2002-10-24 Thread Oleg 
Hi

This may or may not be considered a bug, because I'm using version 4.2.1-3 of 
xbase-clients from 
deb http://people.debian.org/~blade/woody/i386/ ./
on Woody.

When I run xvidtune, it gives

Vendor: AutoDetected, Model: AutoDetected
Num hsync: 1, Num vsync: 1
hsync range 0:  30.00 -  90.00
vsync range 0:  56.00 -  83.00
Floating point exception

(The last line goes to STDERR)

Oleg
P.S. Cc: to me please.

Re: xvidtune: floating point exception

2002-10-24 Thread Drew Parsons 
On Thu, Oct 24, 2002 at 05:24:47PM -0400, Oleg wrote:
> Hi
> 
> This may or may not be considered a bug, because I'm using version 4.2.1-3 of 
> xbase-clients from 
> deb http://people.debian.org/~blade/woody/i386/ ./
> on Woody.
> 
> When I run xvidtune, it gives
> 
> Vendor: AutoDetected, Model: AutoDetected
> Num hsync: 1, Num vsync: 1
> hsync range 0:  30.00 -  90.00
> vsync range 0:  56.00 -  83.00
> Floating point exception
> 

I get the f.p. exception on unstable too (4.2.1-2)

Drew

-- 
PGP public key available at http://people.debian.org/~dparsons/drewskey.txt
Fingerprint: A110 EAE1 D7D2 8076 5FE0  EC0A B6CE 7041 6412 4E4A

Re: [desktop] Unix configuration nightmare

2002-10-24 Thread Manoj Srivastava 
Hi,
>>"Branden" == Branden Robinson <[EMAIL PROTECTED]> writes:

 Branden> On Wed, Oct 23, 2002 at 10:09:58PM +0200, Andreas Metzler wrote:
 >> Time for a third opinion: I think your setup circumvents the problem
 >> (parsing XF86Config) _very_ nicely with little overhead. It allows me
 >> to customize any section I want while still letting debconf handle the
 >> rest. Basically I just have to copy it and move it outside of the debconf
 >> part.

 Branden> Well, that was the use case I had in mind when I wrote
 Branden> XFree86's debconf support, but judging by the dozens of
 Branden> config files I've seen, that's not the use case in widest
 Branden> deployment.


 Branden> Cutting and pasting a block of text is Too Hard.

Perhaps you should add that to the comment: that the unit to
 copy is a section; and any section may be copied at will. 

 Branden> The scenario you enjoy will die, because People Will Not
 Branden> Read.  It's also arguably a violation of way Debconf is
 Branden> supposed to work (there's not supposed to be any such thing
 Branden> as a "debconf area", and for files that aren't as
 Branden> potentially insanely complex as XF86Config, I agree), so I'm
 Branden> not getting any support from the Orthodox Church of Debconf,
 Branden> either.

Perhaps the solution is to grab the area between the debconf
 markers, store a md5sum of that area, and act like dpkg does with
 conffiles: allow the user to accept, refuse, view diffs, of the
 section inside the debconf area.

Once I get ucf cleaned up and insert the diff3 functionality
 in there, you can use ucf to really preserve user changes.

manoj
-- 
 People will do tomorrow what they did today because that is what they
 did yesterday.
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Processed: retitle 166234 to xserver-xfree86: [i810] Xv windows show only chromakey (regression from 4.1.0) on i810-dc100 rev 2

2002-10-24 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

> retitle 166234 xserver-xfree86: [i810] Xv windows show only chromakey 
> (regression from 4.1.0) on i810-dc100 rev 2
Bug#166234: xserver-xfree86: [i810] Xv doesn't work with i810 in X 4.2.1
Changed Bug title.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Re: xvidtune: floating point exception

2002-10-24 Thread Branden Robinson 
Already filed as #89323 and #94888.

-- 
G. Branden Robinson|Build a fire for a man, and he'll
Debian GNU/Linux   |be warm for a day.  Set a man on
[EMAIL PROTECTED] |fire, and he'll be warm for the
http://people.debian.org/~branden/ |rest of his life. - Terry Pratchett


pgpn2VEvzfNUg.pgp
Description: PGP signature