tech-userlevel archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Issues with FFS vs UFS name in applications and documentation

On Tue, Mar 31, 2009 at 12:28:20PM +1100, Luke Mewburn wrote:
  | There are various issues in how we refer to FFS versus UFS
  | and the different versions (FFSv1, FFSv2), and this causes
  | confusion and potential failure.
  | 2.  installboot(8) doesn't have the ability to confirm that the
  |     primary bootstrap (/usr/mdec/bootxx_FOO) matches the underlying
  |     file system that is being installbooted to.
  |     installboot(8) can already determine the file system type
  |     (based on magic numbers in the superblock, for example).
  |     However, there isn't an easy way to determine which file
  |     system a given primary bootstrap is implemented for.
  |     A hacky solution would be to check the suffix on the
  |     filename, but I dislike this.
  |     We should investigate a technique to encode details
  |     of which file system the bootstrap is for.  This would
  |     most likely need to be a Machine Dependent (MD) solution,
  |     handled by a new method in usr.sbin/installboot/arch/*.c
  |     It could be implemented by encoding into the primary boostrap
  |     a descriptive text string or even just the magic number of
  |     the superblock of the target file system.

We could probably use a PR for this feature request.

  | 4.  The dumpfs(8) output can be confusing when attempting to determine
  |     if a file system is FFSv2 (so that /usr/mdec/bootxx_ffsv2
  |     is to be installboot(8)ed.)

I've resolved this.

Attachment: pgpqbWYRNvygq.pgp
Description: PGP signature

Home | Main Index | Thread Index | Old Index