From: Jarmo <oh1mrr@nic.fi>
To: Ralf Baechle DO1GRB <ralf@linux-mips.org>
Cc: linux-hams@vger.kernel.org
Subject: Re: Timers in 2.6.x kernels
Date: Sun, 14 Mar 2004 08:01:27 +0200 [thread overview]
Message-ID: <200403140801.27105.oh1mrr@nic.fi> (raw)
In-Reply-To: <20040313220622.GA18544@linux-mips.org>
On Sunday 14 March 2004 00:06, you wrote:
> MS drivers and Linux drivers are technically very different. So quite
> likely the version numbers are refering to different drivers. And anyway,
> the Linux driver has been changed fairly often, just not the version
> number of the driver. So in short, the content of information in the
> version number is probably approximating that of cosmic noise ;-)
True...
But also true,that there is no maintainer for 6pack at the moment..
So we here,who use it,are in "liquid"...Want to modernize system,
hardware and software, but seems to take some time...
In a way this is fun,to try solve problems,but packetradio/cluster
users does not feel that way,when everything is crushed most
of the time...
> > Hope,that get it running more stable..9 hours max uptime was quite
> > annoying.
8 hours 14mins...AAARGGHHHH!
Still have to remember,that this is a hobby..isn't it?
>
> Maybe - but software that works less than reliable sucks.
>
> 73 de DO1GRB op Ralf
True,but this case I've started to think,that there sucks my linux
skills;-)
No...I'm not giving up...Next..... HW change...again..
Jarmo
next prev parent reply other threads:[~2004-03-14 6:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 11:10 Timers in 2.6.x kernels Jarmo
2004-03-12 19:09 ` Jeroen Vreeken
2004-03-13 14:19 ` Ralf Baechle DO1GRB
2004-03-13 14:59 ` Jarmo
2004-03-13 22:06 ` Ralf Baechle DO1GRB
2004-03-14 6:01 ` Jarmo [this message]
2004-03-15 0:51 ` Ralf Baechle DO1GRB
[not found] ` <200403150806.46071.oh1mrr@nic.fi>
2004-03-15 13:38 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200403140801.27105.oh1mrr@nic.fi \
--to=oh1mrr@nic.fi \
--cc=linux-hams@vger.kernel.org \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox