Source-Changes-D archive

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

Re: CVS commit: src/usr.sbin/makefs




To: martin%duskware.de@localhost

Subject: Re: CVS commit: src/usr.sbin/makefs

From: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>

Date: Wed, 25 May 2011 00:38:15 +0900


> Ok, so this differs from both sparc64 and sgimips significantly. Now, what is
> the purpose of the change starting this thread if it only does the minor step
> but leaves out the complex one that realy fits well into makefs?

Hmm.

Now I've checked macppccd.iso and FreeBSD's hfs-boot, and
it seems they have a small HFS behind of iso9660.
http://www.freebsd.org/cgi/cvsweb.cgi/src/release/powerpc/generate-hfs.sh?rev=1.1
(though I'm not sure if MacOS (for mac68k bootstrap) can mount FreeBSD's one)

Probably your question is now "why we have put emul-boot and ElTorito
boot support into makefs(8)?"

The answer might be that they were heavily tied to ISO9660 spec?
Other MD (Apple, CHRP, Acorn etc) formats as well?
(and Sun's format is simple enough to handle with shell script?)
---
Izumi Tsutsui


References:

Re: CVS commit: src/usr.sbin/makefs
From: Martin Husemann




Prev by Date: Re: CVS commit: src/usr.sbin/makefs

Next by Date: Re: CVS commit: src/usr.sbin/makefs

Previous by Thread: Re: CVS commit: src/usr.sbin/makefs

Next by Thread: Re: CVS commit: src/usr.sbin/makefs

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index