From: Prasanna P Subash <psubash@turbolinux.com>
To: Jagan_Pochimireddy@3com.com
Cc: CaT <cat@zip.com.au>, linux-kernel@vger.kernel.org
Subject: Re: kernel ver 2.4.1 VFS problem
Date: Thu, 1 Feb 2001 17:20:56 -0800 [thread overview]
Message-ID: <20010201172056.A7259@turbolinux.com> (raw)
In-Reply-To: <882569E7.0001FE39.00@hqoutbound.ops.3com.com>
In-Reply-To: <882569E7.0001FE39.00@hqoutbound.ops.3com.com>; from Jagan_Pochimireddy@3com.com on Thu, Feb 01, 2001 at 04:22:03PM -0800
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
On Thu, Feb 01, 2001 at 04:22:03PM -0800, Jagan_Pochimireddy@3com.com wrote:
>
>
> But the driver for my Hard disk is not there in the list, mine is FUJISTU disk
> .I think Generic scsi driver will work
>
> Thanks
> Jagan
>
>
Your scsi driver could be compiled into as a module. "mkinitrd" to boot off
a scsi root disk and update lilo info.
Another quick solution would be to compile the scsi driver into the kernel.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
--
Prasanna Subash --- psubash@turbolinux.com --- TurboLinux, INC
------------------------------------------------------------------------
Linux, the choice | Can't open /usr/fortunes. Lid stuck on
of a GNU generation -o) | cookie jar.
Kernel 2.2.16 /\\ |
on a i686 _\\_v |
|
------------------------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-02-02 1:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 0:22 kernel ver 2.4.1 VFS problem Jagan_Pochimireddy
2001-02-02 0:25 ` CaT
2001-02-02 1:20 ` Prasanna P Subash [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-02 1:34 Jagan_Pochimireddy
2001-02-02 13:12 ` Rik van Riel
2001-02-01 23:58 Jagan_Pochimireddy
2001-02-02 0:09 ` CaT
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=20010201172056.A7259@turbolinux.com \
--to=psubash@turbolinux.com \
--cc=Jagan_Pochimireddy@3com.com \
--cc=cat@zip.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.