[haiku-commits] Re: haiku: hrev50718 - build/jam
- From: kallisti5 <kallisti5@xxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Tue, 29 Nov 2016 10:04:49 -0600
On 2016-11-29 09:52, Adrien Destugues wrote:
29 novembre 2016 16:42 kallisti5@xxxxxxxxxxx a écrit:
hrev50718 adds 1 changeset to branch 'master'
old head: ecb395852e86c5deac1ca0b01ecb317ca831eebc
new head: 738ca0a3a31da260d5b3ba18b6dd616dc59a0e03
overview:
http://cgit.haiku-os.org/haiku/log/?qt=range&q=738ca0a3a31d+%5Eecb395852e86
----------------------------------------------------------------------------
738ca0a3a31d: build: Change anyboot output from image to iso
* Re ML discussions, this should make a lot more
sense to users as it is inline with what most
linux distros ship.
* This will require a tweak to the buildbot.
* First step to shipping anyboot instead of plain iso.
I would prefer .img for correctness, as this is not (only) an ISO9660
filesystem. Is .img widely recognized by burning software?
Fedora, Debian, Ubuntu, etc all ship a hybrid iso which can be written
anywhere like our anyboot. (via different technology though)
ISO appeals to the lowest common denominator. Any new user can "take
an iso and throw it in virtual box or burn it to a cd".
Generally more advanced users will want to "dd it to a hard disk / flash
drive to boot"
While .img is technically more accurate since we ship BFS behind the
ISO filesystem, we need to keep the bar for new users as low as
possible.
You got to remember the install image is the first experience users
will have with Haiku... everyone doesn't understand the complexities
of the anyboot vs iso.
BeOS was a hybrid ISO as well if I remember correctly. (however they
shipped as bin / cue as well)
I'm not seeing any guidance on Hybrid disks anywhere, I think the
assumed
standard at this point is "if it can quack like an iso, call it an iso"
https://en.wikipedia.org/wiki/ISO_image
https://en.wikipedia.org/wiki/Hybrid_disc
-- Alex
Other related posts:
