On Fri, 09 Jun 2000, Shane wrote about, Re: RH 6.2 X config:
> > Sorry i cant agree there.
> > xf86config "will" configure what others cant, espesialy unsupported cards.
>
> But you forgot to allow for the newbie factor.
> I really liked the gui tool that caldera used as you could pick any
> combination you liked and test them on the spot. Really good for
> unkown cards and VDU's. And it seemed to probe better than anything
> else I've tried.
Ok, well i found when i tryed XF86Setup that it would not set a decent
resolution for a S3 card or a SiS6326 AGP card, yes they are now widely
supported but they were not when i tryed them, at that time xf86config did
a lot more than XF86Setup or even Xconfigurator for that matter.
What my point is, is, when a card is unsupported or has nominal support
xf86config will do a better job than other progs.
Anyway, its what one finds best for "him/herself" that counts.
>
> Most of my work with linux has been in console mode. When I was using
> RH5.2, I was able to do a bit using X. Now that I've bitten the bullet and
> put linux on the best computer in the shack, I'm trying to explore the GUI
> more and see what I can do with it.
> Long term linux will be doing mostly server work and a fancy GUI will be
> less important, but for now it's play time :-) while I get to know it
> better.
>
> > One possable explanation for xf86config setting color depth to 8 is, that
> > one can startx using -- -bpp8 or 16 or 32
>
> I used to be able to set up the same VDU with a different card and do the
> above, but doing it with the voodoo card has been ..um..fun.
>
> > Here is how i start x from my profile.
> >
> > if [ -f /tmp/.X0-lock ]; then
> > echo "X already running..."
> > else
> > startx -- -bpp 16 2>&1 &> /var/log/startx.log &
> > fi
> > #
>
> I like that. I'll keep it for later use.
> The scary bit is that I pretty much understand it.
>
> > So i login to my system and it looks to see if X is running, if yes, then
> > it says
> > X already running...
> > If its not then bang, X starts and exits from the console where it was
> > started.
> >
> > make sure (if you use the above) that /var/log/startx.log is owned by the
> > user who starts X.
>
> I wouldn't have known that, thanks.
That you should have really known, you possably do know, but it does not
dawn on you untill you as a "user" try to read "system logs".
/var/log is owned by root and log files in that dir belong to root.
On the otherhand you can redirect the output of X to where ever you want.
>
> >
> > >
> > > I still have a few zillion other things to sort out. I'll be back :)
> > > Shane..
> >
> > Dont we all ;-)
>
> I think most of my other problems were due to either RF getting into
> my computers or voltage spikes from a loose power plug when I
> shoehorned the linux computer into the middle of my operating
> bench. Must have a tidy up.
Ferriet cores, bless them, 5 windings on a ferrit core as close as possable
to the input of the computer plug will keep 400 watts of RF at bay, belive
me, i am an operator of PI4ZLD a fanatical contest stn, here in the
Netherlands, our logging/contesting computer has one ferriet core on every
end of "every" cable.
Dont ask me what software we use, i would have to say "huum".
Ok widows.
>
> > Regards Richard
> > [EMAIL PROTECTED]
> > http://people.zeelandnet.nl/pa3gcu/
>
> Had a quick poke around. Will have a better look when I've got more time.
As a matter of fact if it still works, PI4ZLD has a link from my home page.
Sorry folks that was a little of topic for this list.
>
> Shane..
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
