On 6/5/06, Danial Thom <[EMAIL PROTECTED]> wrote:
Seemed appropriate. People that terminate threads
because they don't want to fix a problem in their
OS because its too much work deserve such.
Why can't he just admit that he broke something
that was fixed and it needs to be repaired,
rather than
Seemed appropriate. People that terminate threads
because they don't want to fix a problem in their
OS because its too much work deserve such.
Why can't he just admit that he broke something
that was fixed and it needs to be repaired,
rather than blaming it on chip manufacturers, and
somehow clai
All I can really say is, Daniel, you're a f*cking idiot.
> Will you also stand on your desk and beat your
> chest as you delete it?
--- Matthew Dillon <[EMAIL PROTECTED]>
wrote:
> :And the whole fanless, diskless moving parts
> BS
> :is just so stupid I can't stand it. Its like a
> :bunch of college kids sitting around thinking
> of
> :things to complain about. The guy is using
> crap
> :hardware, stripped down os and has to
Will you also stand on your desk and beat your
chest as you delete it?
--- Matthew Dillon <[EMAIL PROTECTED]>
wrote:
> This thread will be terminated at midnight
> (PDT) tonight. As usual I'll
> give all parties involved the last word.
> Then postings related to it
> will start bou
This thread will be terminated at midnight (PDT) tonight. As usual I'll
give all parties involved the last word. Then postings related to it
will start bouncing.
I am also going to issue a public warning to Danial Thom... this is
the third time in as many years that you have
:And the whole fanless, diskless moving parts BS
:is just so stupid I can't stand it. Its like a
:bunch of college kids sitting around thinking of
:things to complain about. The guy is using crap
:hardware, stripped down os and has to put all the
:design effort into shrinking everything down, and
:
--- W B Hacker <[EMAIL PROTECTED]> wrote:
> Danial Thom wrote:
>
>
> >>
> >>Same as always:
> >>
> >>1) ALT-F2 (3, 4, etc.) before logging in.
> >>
> >>2) Edit /etc/syslog.conf to send soem/all
> >>console messages elsewhere
> >>- after which (1) is no longer necessary.
> >>
> >>Bill
> >>
> >
--- Scott Ullrich <[EMAIL PROTECTED]> wrote:
> Scott Ullrich wrote:
> > Gergo Szakal wrote:
> >
> >> FYI, the leader of m0n0wall, talking about
> the feature of his OS
> >> mentioned that DragonFlyBSD is not even
> taken into consideration by
> >> him to base his system on, 'cause it's
> 'des
Scott Ullrich wrote:
Gergo Szakal wrote:
FYI, the leader of m0n0wall, talking about the feature of his OS
mentioned that DragonFlyBSD is not even taken into consideration by
him to base his system on, 'cause it's 'desktop oriented.'
Actually that is partially untrue. Fred Wright said this
Gergo Szakal wrote:
FYI, the leader of m0n0wall, talking about the feature of his OS mentioned that
DragonFlyBSD is not even taken into consideration by him to base his system on,
'cause it's 'desktop oriented.'
Actually that is partially untrue. Fred Wright said this...
Manuel still has
On 6/4/06, Danial Thom <[EMAIL PROTECTED]> wrote:
Talk about wasting a lot of time! lol
Yeah, I really miss those 5 minutes now that I come to think about it.
The difference between being an idiot and using Google is about the
same as the difference between a long time and 5 minutes.
Please ju
Talk about wasting a lot of time! lol
--- Dmitri Nikulin <[EMAIL PROTECTED]> wrote:
> On 6/4/06, Ben Cadieux <[EMAIL PROTECTED]>
> wrote:
> > O_o
> >
> > You guys sure waste a lot of time on trolls.
> Too bad Danial didn't
> > post any official title, he's starting to
> remind me of the Jerry
>
On Sun, 4 Jun 2006 08:50:25 +1000
"Dmitri Nikulin" <[EMAIL PROTECTED]> wrote:
>there is no point in DragonFly
>working to be a user-friendly desktop OS now, since such efforts often
>get in the way of Real Work like the heroic effort Matt has applied to
>the kernel architecture, and so would defea
On 6/4/06, Ben Cadieux <[EMAIL PROTECTED]> wrote:
O_o
You guys sure waste a lot of time on trolls. Too bad Danial didn't
post any official title, he's starting to remind me of the Jerry
Taylor incident. It's pretty clear this guy is too ignorant to have
"23 years" of life experience, let alone
Thats why you need a substantial staff to do what
you're attempting to do. Whats going to happen
when your customer base grows to beyond the 32
guys who think you're God?
You've clearly made the problem worse, and you'll
have to decide whether you want to fix it, or
have people reject using your O
O_o
You guys sure waste a lot of time on trolls. Too bad Danial didn't
post any official title, he's starting to remind me of the Jerry
Taylor incident. It's pretty clear this guy is too ignorant to have
"23 years" of life experience, let alone that much time using unixes.
I vote for the ban :
Er. Danial, you are just being an idiot now. Programmers are
lazy? Why don't YOU try to reverse engineer an ethernet card
with half a dozen HARDWARE bugs in it without vendor documentation!
Vendors not only do not provide documentation, they also tend to
hide hardware bugs and d
These comments are really unfair.
You have to consider that people who work on projects like DFly or
FreeBSD - they dont have access to every single motherboard every made.
And the Bios quirks can be like fixing leaky pipes. You fix a leak in
one spot, and it causes a new leak somewhere else.
--- Matthew Dillon <[EMAIL PROTECTED]>
wrote:
>
> :Thats not really a solution as I don't want a
> :system thats processing 100s of interrupts per
> :second for no reason. I previously reported
> that
> :these were gone, but now that I put another
> card
> :in the box (a dual port intel etherne
:Thats not really a solution as I don't want a
:system thats processing 100s of interrupts per
:second for no reason. I previously reported that
:these were gone, but now that I put another card
:in the box (a dual port intel ethernet), they're
:back.
:
:I know I've been told that its a bios
:conf
On 6/3/06, Danial Thom <[EMAIL PROTECTED]> wrote:
--- Bill Hacker <[EMAIL PROTECTED]> wrote:
> Danial Thom wrote:
>
> > My tech tried firing up 1.4 on an opteron MB
> with
> > an HT1000 chipset and, although it seems to
> work,
> > the console is literally flooding with "stray
> irq
> > 7" mes
--- Bill Hacker <[EMAIL PROTECTED]> wrote:
> Danial Thom wrote:
>
> > My tech tried firing up 1.4 on an opteron MB
> with
> > an HT1000 chipset and, although it seems to
> work,
> > the console is literally flooding with "stray
> irq
> > 7" messages. Freebsd at least suppressed
> these
> > afte
Danial Thom wrote:
My tech tried firing up 1.4 on an opteron MB with
an HT1000 chipset and, although it seems to work,
the console is literally flooding with "stray irq
7" messages. Freebsd at least suppressed these
after a few, but when is someone actually going
to FIX this in BSD? Someone told
On 2006-06-02 00:24, Danial Thom wrote:
--- Simon 'corecode' Schubert
<[EMAIL PROTECTED]> wrote:
On 01.06.2006, at 20:42, Danial Thom wrote:
> OK, it seems that enabling the printer got
rid of
> the messages. We usually disable the printer
port
> and remove the printer device and it seems
that
--- Simon 'corecode' Schubert
<[EMAIL PROTECTED]> wrote:
> On 01.06.2006, at 20:42, Danial Thom wrote:
> > OK, it seems that enabling the printer got
> rid of
> > the messages. We usually disable the printer
> port
> > and remove the printer device and it seems
> that
> > DFLY doesn't like that
On 01.06.2006, at 20:42, Danial Thom wrote:
OK, it seems that enabling the printer got rid of
the messages. We usually disable the printer port
and remove the printer device and it seems that
DFLY doesn't like that too much.
Now that you're talking about it: I also experienced some of those
s
OK, it seems that enabling the printer got rid of
the messages. We usually disable the printer port
and remove the printer device and it seems that
DFLY doesn't like that too much.
DT
--- Danial Thom <[EMAIL PROTECTED]> wrote:
>
>
> --- Matthew Dillon
> <[EMAIL PROTECTED]>
> wrote:
>
> >
--- Matthew Dillon <[EMAIL PROTECTED]>
wrote:
> A flood of stray irq 7 messages is
> typically indicative of a BIOS
> SMP configuration problem. It usually
> means that the PIC is sending
> EXT interrupt acknowledgement requests to
> several cpus at once (or
> to one dual-core
--- Erik Wikström <[EMAIL PROTECTED]>
wrote:
> On 2006-06-01 15:49, Danial Thom wrote:
> > My tech tried firing up 1.4 on an opteron MB
> with
> > an HT1000 chipset and, although it seems to
> work,
> > the console is literally flooding with "stray
> irq
> > 7" messages. Freebsd at least suppres
A flood of stray irq 7 messages is typically indicative of a BIOS
SMP configuration problem. It usually means that the PIC is sending
EXT interrupt acknowledgement requests to several cpus at once (or
to one dual-core cpu), and the BIOS hasn't setup the hardware to
properly di
On 2006-06-01 15:49, Danial Thom wrote:
My tech tried firing up 1.4 on an opteron MB with
an HT1000 chipset and, although it seems to work,
the console is literally flooding with "stray irq
7" messages. Freebsd at least suppressed these
after a few, but when is someone actually going
to FIX this
My tech tried firing up 1.4 on an opteron MB with
an HT1000 chipset and, although it seems to work,
the console is literally flooding with "stray irq
7" messages. Freebsd at least suppressed these
after a few, but when is someone actually going
to FIX this in BSD? Someone told me years ago
that thi
33 matches
Mail list logo
