Experience with p1v8-current(p2v5)

[Gordon Sadler <gbsadler1@ispchannel.com>]

Really good job by debian team on these, probably mostly Branden, but since
I don't know... thanks all for the effort.

Since this is where we are directed for bugs/info on these packages thought
I might give some feedback. I've been running these since phase 1 v8, and now
I am using apt to keep them current off of samosa.

>From the initial d/l and install over woody 3.3.6? debs things have gone fairly
smooth. Read the docs and try to follow as best I could. The warning on install 
about app-defaults being a dir and not a symlink etc... I tried something that
seems to 'work for me'.
	I used cp /...app-defaults/* to /etc...new loc, realizing this may/may not
	work and if it does only at that moment, any new packages/upgrades would put
	the same old info in wrong spot. Works for me for now.

	I use vesafb for text console display, my initial attempts at xf86cfg,
	etc. left me with a blank screen and a skeleton XF86Config in my home 
	directory. My best solution was to run the old xf86config textmode program
	and use that with some cut/paste from the skeleton file having to do with
	my Nvidia Riva TNT video card and CTX monitor to piece together a usable
	config file. Odd though, under 3.3.6 I could run at 32bpp now limited to 
	24 bpp, think that has to do with TNT card however.

	I have xbase-clients installed 4.0.1.etc. However trying to run the xconsole
	from that package is a bit odd. Firstly, my /etc/alternatives/xconsole points
	to /usr/X11R6/bin/xconsole.real which is nonexistant. Attempting to exec
	update-alternatives --config xconsole gave me (zero)0 choices? I am able to run
	xconsole via the command line. Think the postint script is misconfigured to
	handle/update the /etc/alternatives linkage?

Again thanks for all the hard work.

Gordon Sadler