From: Oleg Drokin <green@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org,
ewald.peiszer@gmx.at, matthias.andree@stud.uni-dortmund.de
Subject: Re: [reiserfs-list] Boot failure: msdos pushes in front of reiserfs
Date: Mon, 14 Jan 2002 14:36:50 +0300 [thread overview]
Message-ID: <20020114143650.D828@namesys.com> (raw)
In-Reply-To: <20020113223803.GA28085@emma1.emma.line.org> <20020114095013.A4760@namesys.com> <3C42BE0E.2090902@namesys.com>
In-Reply-To: <3C42BE0E.2090902@namesys.com>
Hello!
On Mon, Jan 14, 2002 at 02:16:30PM +0300, Hans Reiser wrote:
> So what solution should we use, zeroing or fixing msdos to not try
> something reiserfs can find, or both or what?
We can use both:
destroy MSDOS superblock (if any) at mkreiserfs (or don't touch 1st block of the device if there is no
msdos superblock).
And link reiserfs code into the kernel earlier than msdos code is linked in.
This second way is for those poor souls who ran mkreiserfs on top of their FAT partitions before
we released new mkreiserfs that can destroy FAT superblocks.
> I want the solution to also fixes the error messages from msdos that it
> issues when it sees reiserfs that are confusing for users.
Changing of linking order will fix that, too.
Bye,
Oleg
next prev parent reply other threads:[~2002-01-14 11:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 22:38 Boot failure: msdos pushes in front of reiserfs Matthias Andree
2002-01-14 6:50 ` [reiserfs-list] " Oleg Drokin
2002-01-14 11:16 ` Hans Reiser
2002-01-14 11:36 ` Oleg Drokin [this message]
2002-01-14 17:42 ` Andreas Dilger
2002-01-14 19:46 ` Hans Reiser
2002-01-14 20:21 ` Andrew Clausen
2002-01-14 20:21 ` Chris Mason
2002-01-14 20:29 ` Andrew Clausen
2002-01-14 14:00 ` Matthias Andree
2002-01-14 14:30 ` Oleg Drokin
2002-01-15 17:47 ` Matthias Andree
2002-01-17 6:38 ` Oleg Drokin
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=20020114143650.D828@namesys.com \
--to=green@namesys.com \
--cc=ewald.peiszer@gmx.at \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.de \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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