From: Jim Gifford <maillist@jg555.com>
To: sparclinux@vger.kernel.org
Subject: Re: More on the Sun Disk Label Issue
Date: Tue, 11 Apr 2006 06:12:07 +0000 [thread overview]
Message-ID: <443B48B7.1090809@jg555.com> (raw)
In-Reply-To: <443AE0BA.8070706@jg555.com>
David S. Miller wrote:
> From: Jim Gifford <maillist@jg555.com>
> Date: Mon, 10 Apr 2006 20:24:40 -0700
>
>
>> I think the problem may be with the way fdisk is creating the
>> labels. Here is how they are doing it.
>>
>
> It's how they are "doing it" eh?
>
> You've shown a data structure, data structures don't "do" anything,
> whereas code executes and "does" things.
>
> What about this data structure layout makes you think fdisk is
> doing something wrong?
>
> Please don't just dump information into the discussion without saying
> what you think it's showing us. What's wrong with it?
>
Dave, the reason I say this is parted works. That's what's frustrating,
because of trying to determine what is actually at fault, is it the
kernel, or something else.
> People really need to learn how to report bugs properly and help the
> process move forward, instead of backward. Many people who report
> sparc64 bugs do things which waste time and hinder the debugging
> process. Cheers to the folks who do not fall into this category, but
> sadly most do and since I'm the only person working on the sparc64
> kernel actively this is incredibly frustrating.
>
The bottom line somehow the writing of the header is not being done
correctly. If it's fdisk or something related to the kernel, that's what
I'm trying to determine.
next prev parent reply other threads:[~2006-04-11 6:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 22:48 More on the Sun Disk Label Issue Jim Gifford
2006-04-10 23:03 ` David S. Miller
2006-04-11 3:24 ` Jim Gifford
2006-04-11 6:03 ` David S. Miller
2006-04-11 6:12 ` Jim Gifford [this message]
2006-04-11 6:36 ` David S. Miller
2006-04-11 6:42 ` Jim Gifford
2006-04-11 6:52 ` David S. Miller
2006-04-15 0:47 ` Jim Gifford
2006-04-15 2:44 ` David S. Miller
2006-04-15 2:48 ` Jim Gifford
2006-04-15 2:56 ` David S. Miller
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=443B48B7.1090809@jg555.com \
--to=maillist@jg555.com \
--cc=sparclinux@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.