mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bongani Hlope <bonganilinux@mweb.co.za>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel File system Corruption related
Date: 29 Nov 2001 23:58:21 +0200	[thread overview]
Message-ID: <1007071109.7917.9.camel@localhost.localdomain> (raw)
In-Reply-To: <861yiho985.fsf%jeffrin@msservices.org>
In-Reply-To: <861yiho985.fsf%jeffrin@msservices.org>

Is the second machine also running 2.4.16? I am using 2.4.16
and I haven experienced any filesystem problems

On Thu, 2001-11-29 at 18:03, Jeffrin wrote:
> 
> Hello ,
> 
> I had done a 2.4.16 kernel related compilation
> and used it. When i did "init 0" for the first time
> and then again tried get a GNU/Linux system related to 2.4.16
> it might have showed related to severe filesystem corruption
> problems.And at one time related to that atleast i  could not even
> use GNU/Linux.It had atleast a i810  chipset and a Pentium
> Processor.
> 
> 
> I have in my     house 2 machines which is not i810 and i
> did not find any problems related to  typical filesystem corruption.
> 
> 
> May be a typical bug related to filesystem corruption
> is not completely fixed in 2.4.16.
> 
> 
> -- 
> Jeffrin Jose T.
> www.MSServices.org
> GPG:1024D/F5726A1B
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



       reply	other threads:[~2001-11-29 21:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <861yiho985.fsf%jeffrin@msservices.org>
2001-11-29 21:58 ` Bongani Hlope [this message]
2001-11-29 16:03 Jeffrin
2001-11-29 21:37 ` Masoud
2001-11-30  7:31   ` Gábor Lénárt

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=1007071109.7917.9.camel@localhost.localdomain \
    --to=bonganilinux@mweb.co.za \
    --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

all inboxes | Powered by JetHome®