Re: Heavy on the Verbosity (was) Re: Annoying messages on startup..

1999-01-17 Thread Karl Pielorz
"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

Re: Annoying messages on startup..

1999-01-17 Thread S�ren Schmidt
It seems Jordan K. Hubbard wrote: > > > Also, I suspect having acd in the kernel and wcd in MAKEDEV may > > lead to confusion for some people. > > I was under the impression that Soren was going to rename acd to wcd > before the branch. Oops, forgot about that one... In fact I was going to add B

Re: Heavy on the Verbosity (was) Re: Annoying messages on startup..

1999-01-17 Thread Jordan K. Hubbard
> ... 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

Re: Heavy on the Verbosity (was) Re: Annoying messages on startup..

1999-01-17 Thread jack
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 > >

Re: Heavy on the Verbosity (was) Re: Annoying messages on startup..

1999-01-17 Thread Jordan K. Hubbard
> 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

Re: Annoying messages on startup..

1999-01-17 Thread Jeroen C. van Gelderen
From: Jordan K. Hubbard >I don't like this error much either (especially since it generates >tech support questions on USENET and other places from users going >"Aieee! What does this mean?!") me too Question is what to do about the messages. I can think of a few options: 1. move them to verbo

Re: Annoying messages on startup..

1999-01-17 Thread jack
On Sun, 17 Jan 1999, Jordan K. Hubbard wrote: > > Nowhere near as annoying as "tagged openings now xx". > > I don't like this error much either (especially since it generates > tech support questions on USENET and other places from users going > "Aieee! What does this mean?!") but I was overrul

Re: Heavy on the Verbosity (was) Re: Annoying messages on startup..

1999-01-17 Thread Chris Tubutis
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

Re: Annoying messages on startup..

1999-01-17 Thread Jordan K. Hubbard
> Nowhere near as annoying as "tagged openings now xx". I don't like this error much either (especially since it generates tech support questions on USENET and other places from users going "Aieee! What does this mean?!") but I was overruled on the issue by arguments that it was still providing

Re: Heavy on the Verbosity (was) Re: Annoying messages on startup..

1999-01-17 Thread Poul-Henning Kamp
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

Heavy on the Verbosity (was) Re: Annoying messages on startup..

1999-01-17 Thread Karl Pielorz
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

Re: Annoying messages on startup..

1999-01-17 Thread Peter Wemm
sth...@nethelp.no wrote: > > > j...@zippy-> dmesg|grep Freeing > > > Freeing (NOT implemented) redirected ISA irq 11. > > > Freeing (NOT implemented) redirected ISA irq 10. > > > > Nowhere near as annoying as "tagged openings now xx". > > Agreed. They are confusing to those who don't know what i

Re: Annoying messages on startup..

1999-01-17 Thread sthaug
> > j...@zippy-> dmesg|grep Freeing > > Freeing (NOT implemented) redirected ISA irq 11. > > Freeing (NOT implemented) redirected ISA irq 10. > > Nowhere near as annoying as "tagged openings now xx". Agreed. They are confusing to those who don't know what it means. As for me, I just ignore them

Re: Annoying messages on startup..

1999-01-17 Thread jack
On Sat, 16 Jan 1999, Jordan K. Hubbard wrote: > j...@zippy-> dmesg|grep Freeing > Freeing (NOT implemented) redirected ISA irq 11. > Freeing (NOT implemented) redirected ISA irq 10. Nowhere near as annoying as "tagged openings now xx". Perhaps `|| 1' could be changed to `|| crs->openings < some

Re: Annoying messages on startup..

1999-01-17 Thread Steve Passe
Hi, > j...@zippy-> dmesg|grep Freeing > Freeing (NOT implemented) redirected ISA irq 11. > Freeing (NOT implemented) redirected ISA irq 10. > Freeing (NOT implemented) redirected ISA irq 10. > Freeing (NOT implemented) redirected ISA irq 10. > Freeing (NOT implemented) redirected ISA irq 9. > Free

Annoying messages on startup..

1999-01-16 Thread Jordan K. Hubbard
j...@zippy-> dmesg|grep Freeing Freeing (NOT implemented) redirected ISA irq 11. Freeing (NOT implemented) redirected ISA irq 10. Freeing (NOT implemented) redirected ISA irq 10. Freeing (NOT implemented) redirected ISA irq 10. Freeing (NOT implemented) redirected ISA irq 9. Freeing (NOT implemente