All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:39:48 +0100	[thread overview]
Message-ID: <4D2741D4.3050903@gmail.com> (raw)
In-Reply-To: <4D2720CC.8030207@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]

On 01/07/2011 03:18 PM, Grégoire Sutre wrote:
> On 01/07/2011 13:20, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>
>>> Do you know of any OS that would put the superblock in sector 0?
>>> I  googled a bit, but I couldn't find examples where UFS would
>>> not start with a boot sector (afaics, it usually starts with a
>>> bootblock area of at least 8KiB -- with OS-specific data in it,
>>> e.g. a disklabel).
>>>
>> According to *BSD http://fxr.watson.org/fxr/source/ufs/ffs/fs.h:
>>
>> */"* Depending on the architecture and the media, the superblock may/*
>> */* reside in any one of four places. For tiny media where every
>> block /*
>> */* counts, it is placed at the very front of the partition.
>> Historically,/*
>> */* UFS1 placed it 8K from the front to leave room for the disk label
>> and/*
>> */* a small bootstrap. For UFS2 it got moved to 64K from the front to
>> leave/*
>> */* room for the disk label and a bigger bootstrap, and for really
>> piggy/*
>> */* systems we check at 256K from the front if the first three fail/*"
>
> Interesting.  So, when searching for a UFS superblock, sector 0 is a
> candidate (after sectors 128 and 16).  It seems to me that this use of
> sector 0 for tiny media does not apply to (recent) NetBSD newfs(8),
> though.
>
> If we want to improve the situation, we could let the filesystem driver
> dynamically decide whether the first sector is reserved or not.  But
> I'm not sure that it's worth it (the first sector of a partition
> containing a filesystem is only used for blocklist embedding, right?).
>
It's used for putting boot.img into partition. But you're right, it's
used mainly for blocklists installs.
> 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 --]

      reply	other threads:[~2011-01-07 17:44 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
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 [this message]

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=4D2741D4.3050903@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 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.