From: Andrew Clausen <clausen@gnu.org>
To: Chris Mason <mason@suse.com>
Cc: Andreas Dilger <adilger@turbolabs.com>,
Oleg Drokin <green@namesys.com>, Hans Reiser <reiser@namesys.com>,
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: Tue, 15 Jan 2002 07:29:40 +1100 [thread overview]
Message-ID: <20020115072940.J20639@gnu.org> (raw)
In-Reply-To: <20020113223803.GA28085@emma1.emma.line.org> <20020114095013.A4760@namesys.com> <3C42BE0E.2090902@namesys.com> <20020114143650.D828@namesys.com> <20020114104242.M26688@lynx.adilger.int> <551760000.1011039675@tiny>
In-Reply-To: <551760000.1011039675@tiny>; from mason@suse.com on Mon, Jan 14, 2002 at 03:21:15PM -0500
On Mon, Jan 14, 2002 at 03:21:15PM -0500, Chris Mason wrote:
> Hmmm mke2fs seems to always zero out the first 1024, except on sparcs (when
> ZAP_BOOT_BLOCK not defined). I thought alphas stored the partition table on
> the first block of the first partition as well, and that we didn't want to
> zero it then.
*nitpick*
I think that's Sun... Alpha's use either BSD or MSDOS tables, neither
of which do that...
Andrew
next prev parent reply other threads:[~2002-01-14 20:32 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
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 [this message]
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=20020115072940.J20639@gnu.org \
--to=clausen@gnu.org \
--cc=adilger@turbolabs.com \
--cc=ewald.peiszer@gmx.at \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--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 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.