Re: qt3-tools make error

2006-07-30 Thread Petr Janda
pkg-config reports the same as yours, but I just dont have the libXcursor files in the .buildlink directory... the libdir entry is correct also. What the hell is going on? walt wrote: On Sun, 30 Jul 2006, walt wrote: On Sun, 2006-07-30 at 22:53 +1000, Petr Janda wrote: Im wondering

Re: Another annoying dvd playback bug

2006-07-30 Thread Petr Janda
Ive got the gdb backtrace: #0 0x0847bca5 in mpeg2_set_buf () #1 0x081080bf in mpcodecs_draw_slice () #2 0x08105b33 in decode_video () #3 0x080808ee in main () Dunno if its of anyhelp. Commandline mplayer seems to be working fine. Petr walt wrote: Petr Janda wrote: ...I recompiled gm

Re: Locked out - need a little help (caution: n00b meter on high!)

2006-07-30 Thread Matthew Dillon
: :On Sunday 30 July 2006 23:09, Gergo Szakal wrote: :> Peter Avalos wrote: :> > Since the n00b meter was pegged, I'm assuming you don't know about manual :> > pages: 'man chsh' could have helped you figure this out: :> > :> > chsh -s /bin/sh :> :> Yeah, I was in a hurry and forgot to RTFM before

Re: Locked out - need a little help (caution: n00b meter on high!)

2006-07-30 Thread Jonathan Fosburgh
On Sunday 30 July 2006 23:09, Gergo Szakal wrote: > Peter Avalos wrote: > > Since the n00b meter was pegged, I'm assuming you don't know about manual > > pages: 'man chsh' could have helped you figure this out: > > > > chsh -s /bin/sh > > Yeah, I was in a hurry and forgot to RTFM before posting, so

Re: Postfix suddenly stopped working

2006-07-30 Thread Jon Hamilton
Jon Hamilton <[EMAIL PROTECTED]>, said on Thu Jul 27, 2006 [09:43:16 PM]: } Joerg Sonnenberger <[EMAIL PROTECTED]>, said on Fri Jul 28, 2006 [04:19:35 AM]: } } On Thu, Jul 27, 2006 at 08:42:36PM -0500, Jon Hamilton wrote: } } > I never did get to the bottom of it. I rebuilt postfix and all of its

Re: Locked out - need a little help (caution: n00b meter on high!)

2006-07-30 Thread Gergo Szakal
Peter Avalos wrote: > Since the n00b meter was pegged, I'm assuming you don't know about manual > pages: 'man chsh' could have helped you figure this out: > > chsh -s /bin/sh > Yeah, I was in a hurry and forgot to RTFM before posting, sorry about that. Thanks to all for the answers, they are way

Re: Compaq Evo boot problem

2006-07-30 Thread Francois Tigeot
On Sun, Jul 30, 2006 at 11:24:17AM -0700, Matthew Dillon wrote: > :FWIW, FreeBSD 6.0 has no trouble booting from the machine I had this > :problem on. > > With the disks set to 'Auto' mode instead of 'Large' mode? Yes. > There's no real difference between FreeBSD's slice table and ours.

Re: Compaq Evo boot problem

2006-07-30 Thread Matthew Dillon
::I was told on IRC yesterday that our fdisk has issues by setting the CHS = ::information to a wrapped value instead of just willing it with ones. Don= ::'t know if that is the culprit, though. :: ::cheers :: simon : :I should be able to test it easily since I have to set my test machines :

Re: Compaq Evo boot problem

2006-07-30 Thread Matthew Dillon
:FWIW, FreeBSD 6.0 has no trouble booting from the machine I had this :problem on. : :-- :Francois Tigeot With the disks set to 'Auto' mode instead of 'Large' mode? There's no real difference between FreeBSD's slice table and ours. There might be a difference with regards to the bo

Re: Compaq Evo boot problem

2006-07-30 Thread Matthew Dillon
:I was told on IRC yesterday that our fdisk has issues by setting the CHS = :information to a wrapped value instead of just willing it with ones. Don= :'t know if that is the culprit, though. : :cheers : simon I should be able to test it easily since I have to set my test machines to us

Re: Compaq Evo boot problem

2006-07-30 Thread Francois Tigeot
On Sat, Jul 29, 2006 at 11:55:21PM -0700, Matthew Dillon wrote: > Again, in case the information got lost in the shuffle... before > messing with any DMA modes just try telling the BIOS to put the > disk in 'Large' mode. > > The problem is that the BIOS misinterprets the slice tabl

Re: qt3-tools make error

2006-07-30 Thread walt
On Sun, 30 Jul 2006, walt wrote: > On Sun, 2006-07-30 at 22:53 +1000, Petr Janda wrote: > > Im wondering why is DF not searching for libraries in /usr/pkg/lib. How > > can I add it to the search path? > > ldconfig -r will tell you which libraries your system knows about... Sorry, that was true bu

Re: qt3-tools make error

2006-07-30 Thread walt
On Sun, 2006-07-30 at 22:53 +1000, Petr Janda wrote: > Im wondering why is DF not searching for libraries in /usr/pkg/lib. How > can I add it to the search path? ldconfig -r will tell you which libraries your system knows about. If you want to add another default directory you do: ldconfig -R /n

Re: qt3-tools make error

2006-07-30 Thread Petr Janda
I certainly do... I also have the libraries installed in /usr/pkg/lib. Im wondering why is DF not searching for libraries in /usr/pkg/lib. How can I add it to the search path? walt wrote: On Sun, 30 Jul 2006, Petr Janda wrote: Im trying to compile qt3-tools from pkgsrc-current and get thi

Re: qt3-tools make error

2006-07-30 Thread walt
On Sun, 30 Jul 2006, Petr Janda wrote: > Im trying to compile qt3-tools from pkgsrc-current and get this error. > > /usr/libexec/binutils215/elf/ld: cannot find -lXcursor That library is in the x11/xcursor package. Do you have that package installed?

Re: Compaq Evo boot problem

2006-07-30 Thread Simon 'corecode' Schubert
Matthew Dillon wrote: Again, in case the information got lost in the shuffle... before messing with any DMA modes just try telling the BIOS to put the disk in 'Large' mode. The problem is that the BIOS misinterprets the slice table and puts the disk into a strange mode that t

Re: disk diagnostics

2006-07-30 Thread Pieter Dumon
You're right: softdep did the trick. Turned it on on the /usr/obj filesystem, and the rm of the whole world_i386 of 1.7 preview took about 10 seconds Thanks! I didn't expect soft updates to make such a huge difference. Pieter On 7/27/06, Joerg Sonnenberger <[EMAIL PROTECTED]> wrote: On Th

Re: Compaq Evo boot problem

2006-07-30 Thread Matthew Dillon
Again, in case the information got lost in the shuffle... before messing with any DMA modes just try telling the BIOS to put the disk in 'Large' mode. The problem is that the BIOS misinterprets the slice table and puts the disk into a strange mode that the boot code cannot