On Thu, 2005-03-10 at 11:10 -0400, bbruce wrote:
> I have a few questions about uClibc and X/xterm/utempter that hopefully
> someone can answer.  To start with, this isn't for an "embedded" device
> in the normal sense, I'm looking into uClibc to most effectively utilize
> disk and memory under virtual machines (primarily XEN, but would/could
> also apply to vmware, etc).  
> 
> 1)  I would love to use kdrive instead of the full blown xorg-x11,
> however it's using the X11-4.4.3 sources and not the xorg-x11-6.8.x
> sources.  Does anyone know if the mini-x build is included in the 6.8.x
> source?  ( I realize I'm being lazy but I thought I'd ask anyways -
> sorry ).
> 
> 2)  For those that don't know how XEN works, you have a primary instance
> (XEN0) that can use the physical hardware in the box, and other
> instances (vm's) that can't.  For XEN0 all I need is an X server that
> can support "-query <ip>", however in one of the unprivileged I need to
> run X (vnc, actually) which ultimately requires some sort of xterm. 
> With the standard Gentoo install of xterm depending on utempter (which
> uses utmpx.h) and uClibc not having the utmpx interface, it becomes
> obvious that changes are required.
> Would it be best to:
> 
>       a)  Try to port utmpx over to uClibc (I'm not sure if I'm really up for
> this, but I'll try) - which leads me to asking if anyone knows why it
> hasn't been implemented to date.
> 
>       b)  Change the xterm ebuild to not compile in utempter capability when
> under uClibc and conditionally remove the dependency - obviously
> utempter exists for a reason ... 
> 
>       c)  Modify utempter to use utmp instead of utmpx.  It seems as if the
> biggest difference between the two (besides the x in the names) is the
> use of __THROW.  Obviously this is a big enough difference for someone
> out there to think a separate interface was required, otherwise utmpx
> wouldn't exist, but being that I'm so far out of my element I'd love
> input from the people that know.


I seem to remember that uclibc considers utmp to be wasteful bloat.
Somewhere in the docs it says "we dont need no stinkin utemp" I would
fix the xterm ebuild under uclibc as preferable option.


--
[email protected] mailing list

Reply via email to