Re: upgrading to 'testing' failure

2001-03-03 Thread Brendan Simon
el where X does not try to fire up automatically. Then use startx to manually invoke X and see what the error messages are. They should also be logged to /var/log/XFree86.0.log Brendan Simon. tom wrote: > tom wrote: > > > > Well, I upgraded from stable to testing. > > &

Re: upgrading to 'testing' failure

2001-03-03 Thread Brendan Simon
el where X does not try to fire up automatically. Then use startx to manually invoke X and see what the error messages are. They should also be logged to /var/log/XFree86.0.log Brendan Simon. tom wrote: > tom wrote: > > > > Well, I upgraded from stable to testing. > > &

apt-cache (was as86 ...)

2000-07-06 Thread Brendan Simon
> > ah, quite useful that ;-) > > i thought apt-cache was not able to tell you what package a file might > be contained in unless the package was already installed though. can > it do that? if it can, that'd be fantastic! I think it can. Try it on a package that you haven't got installed. Brendan Simon.

apt-cache (was as86 ...)

2000-07-06 Thread Brendan Simon
uite useful that ;-) > > i thought apt-cache was not able to tell you what package a file might > be contained in unless the package was already installed though. can > it do that? if it can, that'd be fantastic! I think it can. Try it on a package that you haven't got installed. Brendan Simon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: time

2000-06-08 Thread Brendan Simon
I think a combination of "hwclock" and "date" commands should do it for you.  Read the man pages.  You can set the time/date with "date" and then set the hardware clock to reflect this using "hwclock". Regards, Brendan Simon. Jack Morgan wrote: