Re: BitchX in X?

[Shannon -jj Behrens]

> > I'm using WindowMaker, how would I go about getting bitchx to run in gtk
> > mode?
> 
> This question isn't appropriate for -stable. It's probably not
> appropriate for freebsd lists in general, but I'm not sure of a bitchx
> list to send you to.

Yeah, probably better on -questions.

Based on looking at /usr/ports/irc/bitchx/Makefile, it looks like you'll want 
to "cd /usr/ports/irc/bitchx && make WITH_GNOME=yes install clean".

Best Regards,
-jj

-- 
Real programmers don't draw flowcharts.  Flowcharts are, after all, the
illiterate's form of documentation.  Cavemen drew flowcharts; look how
much good it did them.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: XFree86 faster!?

[JJ Behrens]

> I just upgraded from 4.6 Release to -STABLE (Jun 27 21:42:28).
> My X feels much snappier now. Any ideas what might cause that?

I'm curious about your mouse configuration.  Are you using:

Driver  "mouse"
Option "Protocol""auto"
Option "Device"  "/dev/sysmouse"

I remember hearing that certain other configurations could result in missing
mouse interrupts.  This would definitely result in slowness.

Also, is the server you're using now accelerated, whereas the previous 
wasn't?

-jj

-- 
Real programmers don't draw flowcharts.  Flowcharts are, after all, the
illiterate's form of documentation.  Cavemen drew flowcharts; look how
much good it did them.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: Build of x11-toolkits/qt23 (qt-2.3.1_1) still broken in 4-STABLE

[JJ Behrens]

Please forgive me for this silly question, but do you have any other versions
of QT installed?

-jj

> uname -a FreeBSD inferno.graddiv.ucsb.edu 4.6-RC
> FreeBSD 4.6-RC #0: Thu May 16 13:49:28 PDT 2002
> 
> cvsup from today
> 
> cd /usr/ports/x11-toolkits/qt23/ fails with:
> 
> c++ -pthread -D_THREAD_SAFE -DQT_THREAD_SUPPORT -c
> -I/usr/X11R6/include
> -I/usr/ports/x11-toolkits/qt23/work/qt-2.3.1/include
> -pthread -D_THREAD_SAFE -I/usr/X11R6/include
> -DQT_PREFIX=\"/usr/X11R6\" -pipe -fno-exceptions  -O
> -pipe  -I/usr/include -D_PTH_H_ -D_PTH_PTHREAD_H_ -O
> -pipe  -fPIC -DQT_BUILTIN_GIF_READER=1 -DQT_XFT
> -fno-exceptions  -I/usr/local/include  -o
> kernel/qpsprinter.o kernel/qpsprinter.cpp
> In file included from kernel/qapplication.h:42,
>  from kernel/qpsprinter.cpp:73:
> kernel/qwidget.h:129: syntax error before `('
> kernel/qwidget.h:417: `WId' was not declared in this
> scope
> kernel/qwidget.h:489: `WId' was not declared in this
> scope
> kernel/qwidget.h:489: syntax error before `='
> kernel/qwidget.h:490: variable or field `create'
> declared void
> kernel/qwidget.h:490: ANSI C++ forbids initialization
> of member `create'
> kernel/qwidget.h:490: making `create' static
> kernel/qwidget.h:490: ANSI C++ forbids in-class
> initialization of non-const static member `create'
> kernel/qwidget.h:490: `create' declared as a `virtual'
> field
> kernel/qwidget.h:520: `WId' was not declared in this
> scope
> kernel/qwidget.h:520: variable or field `setWinId'
> declared void
> kernel/qwidget.h:545: syntax error before `;'
> kernel/qwidget.h:628: syntax error before `::'
> cpp0: output pipe has been closed
> gmake[2]: *** [kernel/qpsprinter.o] Error 1
> gmake[2]: Leaving directory
> `/usr/ports/x11-toolkits/qt23/work/qt-2.3.1/src'
> gmake[1]: *** [src-mt] Error 2
> gmake[1]: Leaving directory
> `/usr/ports/x11-toolkits/qt23/work/qt-2.3.1'
> gmake: *** [src-mt] Error 2
> *** Error code 2
> 
> Stop in /usr/ports/x11-toolkits/qt23.

-- 
Users of C++ should consider hanging themselves rather than shooting their 
legs off--it's best not to use C++ simply as a better C.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: makeworld problem - my first attempt at this

[JJ Behrens]

> > [...]
> > > #make installworld
> > >   faild again, same message as before - required smmsp user ismissing.
> > > According to UPDATING running mergemaster would take care of  this
> > > problem.
> > > 
> > > That is where I am stuck. What to do now?
> > 
> > You can add the smmsp user and group manually to /etc/master.passwd and 
> > /etc/group. Remember to run pwd_mkdb, and then try the mergemaster again
> > -- 
> > Jonathan Chen <[EMAIL PROTECTED]>
> 
> Thanks for the tips guys, it's running right now, has been for a while.
> I ran pwd_mkdb /etc/master.passwd, then ran mergemaster -p, and this
> time it worked. I don't know why mergemaster -p didn't work before. Even
> the -help screen did not show -p as an available option.
> Anyway, my first time at this and it appears to be going okay for now.

Hey everyone,

Do you think this is because he was running an older very of mergemaster?
Perhaps it was necessary to run the recently built mergemaster.  Afterall, 
mergemaster -p is run *before* make installworld and is thus an older version.
Whereas, when running mergemaster after make installworld, the newer version
is being used.  Perhaps we should document that when you use mergemaster -p,
it's probably safer to use the full path to the recently built mergemaster.

-jj

-- 
Users of C++ should consider hanging themselves rather than shooting their 
legs off--it's best not to use C++ simply as a better C.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: kernel trap 9 with interrupts disabled

[JJ Behrens]

> Almost, but not quite.  In your scenario the low-priority task would
> get to run since the high-priority task is blocked and would thus
> eventually release the resource. No deadlock, no problem.
> 
> The classic priority inversion that I have heard about is the following
> scenario:
> 
> Three processes of low, medium and high priority respectively.
> The low-priority task locks some resource. Before this resource is
> released both the medium-priority and the high-proiority task starts to
> run. Since these have higher priority the low-priority task doesn't get
> any CPU.  The medium-priority task is CPU-intensive and uses all
> CPU-time it gets (but it won't get any while the HP-task is running.)
> Eventually the high-priority task tries to lock the resource that the
> low-priority task is holding. The high-priority task is then blocked
> and the medium-priority task gets to run.
> 
> Now the high-priority task is blocked waiting for the resource that the
> low-priority task is holding. The LP-task does not get to run since the
> MP-task has higher priority and thus can't release the resource.
> 
> This means that the priority between the HP task and the MP task has in
> effect been inverted, since the medium priority task blocks the
> high-priority task from running even if there is no resource that both
> of them are trying to lock.
> 
> The problem is that when the high-priority task got blocked trying to
> acquire the resource that the low-priority task held it effectively
> inherited the priority of the low-priority task and can therefore be
> preempted by the medium-priority task.
> 
> 
> To get a priority inversion like this one needs at least three tasks
> with different priorities.

Ah, yes.  I stand corrected :)

Thanks,
-jj

-- 
Users of C++ should consider hanging themselves rather than shooting their 
legs off--it's best not to use C++ simply as a better C.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: very old bug

[JJ Behrens]

> > > In fact, MS-DOS provide far superior support for floppies than Linux or
> > > FreeBSD or any other Unix I've used.
> >
> > In what way?
> 
> Perhaps in the way this thread has been discussing for the past 10 or so
> posts? Namely the handling of error conditions, when dealing with a floppy
> that has been write protected.
> 
> In MS-DOS you weren't stuck in an endless loop of attempting to write to the
> floppy.

I fear that this is getting *way OT*, but:

MS-DOS didn't mount the floppies.  This problem is difficult because we *do*
mount the floppies.  However, mounting has a lot of benefits that MS-DOS
doesn't provide.

-jj

-- 
Users of C++ should consider hanging themselves rather than shooting their 
legs off--it's best not to use C++ simply as a better C.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: usb CanonScan 650U

[JJ Behrens]

> I noticed the yesterday built 4.5-stable reconized my CanoScan usb
> scanner, it shew up as uscanner0 from `dmesg`. But sane-find-scanner
> doesn't now the type of my scanner still. I cheched the
> /sys/dev/usb/uscanner.c and only found 656U, has anyone get it worked
> for 650U? 

Looking at  it appears
that Sane itself does not support your scanner. 

What you see from dmesg is the fact that the kernel itself recognizes that the
USB device is a scanner.  However, you'll need Sane to actually use the device.
Apparently, "Canon appears to be unwilling to release the necessary
documentation to enable a Linux driver and SANE backend to be written."

Looking at 
 confirms
this. Hence, I'd take a stab at editing /usr/local/etc/sane.d/canon.conf, and
if that doesn't work, I imagine you're outta luck :(

Sorry,
-jj 

-- 
The set-uid bit is patented by Dennis Ritchie.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: KDE mixup: was samba package

[JJ Behrens]

> Sure. Why the kde meta-package was left out??

There was an unfortunate accident. The FreeBSD KDE team was attempting to 
reduce the amount of KDE material on the first CD, and (accidentally) the
material didn't make it onto any of the CD's.

> And teTeX??

teTeX was a dependency for KDE graphics, specifically, KDVI. Due to teTeX's
large size, KDE graphics, by default, now builds without KDVI. You can still
get it from ports. 

I'm just reporting the facts. Further details may be gather by going to 
 and signing up on the mailing list.

Best Regards,
-jj

P.S. Forgive me if any of the above is off topic--someone asked the question, 
and I knew the answer.

-- 
PGP: if encryption is a munition, where's my right to bear arms?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message