From: "Igor Gueths" <igueths@attbi.com>
To: <speakup@braille.uwo.ca>
Subject: Re: Kernel panic: no init found. try passing init to kernel
Date: Mon, 27 May 2002 11:40:06 -0400 [thread overview]
Message-ID: <000d01c20594$c6efd3e0$02263e18@mycomputer> (raw)
In-Reply-To: <Pine.LNX.4.44.0205271031160.307-100000@homerun.us>
Hi Adam. Actually I forgot to point out that fat is broken under 2.4.18
----- Original Message -----
From: Adam Myrow <myrow@eskimo.com>
To: <speakup@braille.uwo.ca>
Sent: Monday, May 27, 2002 11:32 AM
Subject: Re: Kernel panic: no init found. try passing init to kernel
> I just remembered that when Slackware 8.0 first came out, they said not to
> use a 2.4.X kernel with Zipspeak because UMSDOS didn't work right.
> However, this was 2.4.5, and I figured that they would have fixed this by
> now, but maybe not.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
Ann
` Gregory Nowak
` 'Georgina'
` Adam Myrow
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` Adam Myrow
` Igor Gueths [this message]
` Adam Myrow
` Igor Gueths
` Gregory Nowak
` Igor Gueths
` Gregory Nowak
` 'Georgina'
` Ann
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='000d01c20594$c6efd3e0$02263e18@mycomputer' \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).