public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott Robert Ladd <coyote@coyotegulch.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test6 -- Huh???
Date: Tue, 30 Sep 2003 16:30:38 -0400	[thread overview]
Message-ID: <3F79E7EE.80808@coyotegulch.com> (raw)

I freely admit to being something of a neophyte when it comes to the 
internal details of the Linux kernel. I've been successfully running 
development and test kernels since 2.5.40 or so, and I've never before 
seen anything like the following:

   Message from syslogd@Tycho at Tue Sep 30 16:09:01 2003 ...
   Tycho vmunix: ris/b/la/up.us0:rr - rdi ptests

   Message from syslogd@Tycho at Tue Sep 30 16:09:01 2003 ...
   Tycho vmunix: dreruscls/blc:bl: ro-1eangriertas

   Message from syslogd@Tycho at Tue Sep 30 16:09:01 2003 ...
   Tycho vmunix: ris//cs/lp: lper -rengin sus>dersbasus.csb: or9
       diprerat<3iv/u/cs/lp up0rr-1eag ntsts

   Message from syslogd@Tycho at Tue Sep 30 16:09:01 2003 ...
   Tycho vmunix: ris//cs/lp up0rr -rengin sus>dersbassbc:bl: or9
       diprerat<3iv/ucl/up. up0rr-1eag ntsts

The above messages appeared in a root terminal running from Gnome, while 
I was outside replacing fuses in my truck. Given that my truck is not 
yet running Linux or connected to my network (give me time...), I'm at a 
loss as to what caused the above, and what it means.

Polite illumination will be most graciously appreciated.

-- 
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Software Invention for High-Performance Computing


             reply	other threads:[~2003-09-30 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 20:30 Scott Robert Ladd [this message]
2003-10-01 21:21 ` 2.6.0-test6 -- Huh??? bill davidsen

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=3F79E7EE.80808@coyotegulch.com \
    --to=coyote@coyotegulch.com \
    --cc=linux-kernel@vger.kernel.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