"Jordan K. Hubbard" wrote:
> You can always have verbosity as a selective option. We're talking
> about what to do for the great majority of users who aren't in your
> shoes at all and don't want to be.
True, although the messages (OK, admitadly not the ones we're talking about at
the moment) a
> ... and add a magic key combination to turn on the verbose flag.
gdb -kW :-)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Sun, 17 Jan 1999, Chris Tubutis wrote:
> > Coming from someone who's spent the best part of last week trying to
> > diagnose
> > various hardware & software problems on NT & Win'95 machines (to almost no
> > avail), I'd appreciate as much verbosity being left _in_ the kernel &
> > FreeBSD
> >
> Coming from someone who's spent the best part of last week trying to diagnose
> various hardware & software problems on NT & Win'95 machines (to almost no
> avail), I'd appreciate as much verbosity being left _in_ the kernel & FreeBSD
You can always have verbosity as a selective option. We're t
Karl Pielorz wrote:
>
> Coming from someone who's spent the best part of last week trying to diagnose
> various hardware & software problems on NT & Win'95 machines (to almost no
> avail), I'd appreciate as much verbosity being left _in_ the kernel & FreeBSD
> as possible... I'm fed up with seeing
In message <36a24f91.478b5...@tdx.co.uk>, Karl Pielorz writes:
>jack wrote:
>
>> Nowhere near as annoying as "tagged openings now xx".
>>
>> Perhaps `|| 1' could be changed to `|| crs->openings < some
>> critical number' in cam_xpt.c. As it is now a boy and a wolf
>> come to mind.
>
>Coming from
jack wrote:
> Nowhere near as annoying as "tagged openings now xx".
>
> Perhaps `|| 1' could be changed to `|| crs->openings < some
> critical number' in cam_xpt.c. As it is now a boy and a wolf
> come to mind.
Coming from someone who's spent the best part of last week trying to diagnose
variou
