From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Reserved first sector for UFS
Date: Fri, 07 Jan 2011 11:57:13 +0100 [thread overview]
Message-ID: <4D26F189.4040206@gmail.com> (raw)
In-Reply-To: <4D26EF82.10006@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
On 01/07/2011 11:48 AM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 01/07/2011 11:30 AM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>
>> On 01/07/2011 10:35 AM, Grégoire Sutre wrote:
>>
>>
>>> Isn't the first sector reserved for the boot block in UFS?
>>>
>>>
>>>
>> Depends on OS:
>>
>> /* The blocks on which the superblock can be found. */
>> static int sblocklist[] = { 128, 16, 0, 512, -1 };
>>
>>
>>
>>
> AFAIU:
> if (superblock isn't on sector 0) and (inoblk_offs isn't 0 or inode zero
> isn't used) then first sector is reserved
>
Inode 0 shouldn't be used but I see nothing in the on-disk format to
enforce that. Moreover some OSes may put their own information outside
of standard basic UFS in the sector 0. Writing to sector 0 of UFS needs
more investigation because by now there are a lot of UFS variants
>>> Grégoire
>>>
>>>
>>> _______________________________________________
>>> Grub-devel mailing list
>>> Grub-devel@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/grub-devel
>>>
>>>
>>>
>>
>>
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-01-07 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 9:35 Reserved first sector for UFS Grégoire Sutre
2011-01-07 10:30 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-01-07 10:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-01-07 10:57 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-01-07 11:23 ` Grégoire Sutre
2011-01-07 12:20 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-01-07 14:18 ` Grégoire Sutre
2011-01-07 16:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4D26F189.4040206@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).