Live data from Hacker News

AmigaOS 3.1.4 released

hyperion-entertainment.com

11–20 of 30 posts

Re: AmigaOS 3.1.4 released

#11
post #7

"Remember "Diskdoctor"? It earned its PhD and is now ready to reliably rescue data from your floppies or hard disks." Remember the cool old "AGA - time to upgrade - AGA" slogan in some of the demos? Now it's ZFS - time to upgrade - ZFS ...it's the 21st century, and AmigaOS doesn't even have software RAID, let alone ZFS yet. We still have to check filesystems for metadata corruption, and checking them for data corrupt…

It's the 21st century, so maybe you should upgrade from 1992 to 2018! That's 26 years!

You really want a heavy weight like ZFS (which is a total memory hog, btw., I use it in my server) on Amiga hardware from 1992?

You should be happy, that there is such an update to AmigaOS at all !

I understand the enthusiasm. I used an A4000/Cyberstorm060/CyberGfx64 exclusively till 2001. I did not care, that each reboot would take 6 minutes (with starting all the background stuff) and that my system was runtime memory patched into oblivion, and no memory protection in the system. That it crashed 10 times a day (multiply this with boot times, HO HO!). But one day a day has come and one needs to realize: Reality!

Re: AmigaOS 3.1.4 released

#13
post #11
post #7

"Remember "Diskdoctor"? It earned its PhD and is now ready to reliably rescue data from your floppies or hard disks." Remember the cool old "AGA - time to upgrade - AGA" slogan in some of the demos? Now it's ZFS - time to upgrade - ZFS ...it's the 21st century, and AmigaOS doesn't even have software RAID, let alone ZFS yet. We still have to check filesystems for metadata corruption, and checking them for data corrupt…

It's the 21st century, so maybe you should upgrade from 1992 to 2018! That's 26 years! You really want a heavy weight like ZFS (which is a total memory hog, btw., I use it in my server) on Amiga hardware from 1992? You should be happy, that there is such an update to AmigaOS at all ! I understand the enthusiasm. I used an A4000/Cyberstorm060/CyberGfx64 exclusively till 2001. I did not care, that each reboot would tak…

"It's the 21st century, so maybe you should upgrade from 1992 to 2018! That's 26 years!"

I did upgrade: 128 MB FAST RAM, 64-bit MC68080 @ ~234 MHz with AMMX SIMD instructions, 16 GB industry grade CF and 8 GB microSDHC. OS 3.9 @ 1300 x 768 x 32-bit color HDMI.

"You really want a heavy weight like ZFS (which is a total memory hog, btw., I use it in my server) on Amiga hardware from 1992?"

Yes, I do, because as a Solaris engineer, I understand that ZFS will release memory due to memory pressure from applications, and can in fact run in memory constrained systems. Should be able to run on an Amiga with a Vampire accelerator and 129 MB of RAM. ZIL is auto tuned. Just don't use features like de-duplication and it'll be fine.

(My reboots take about three seconds, with or without the Vampire accelerator, and that's even with OS 3.9.)

Re: AmigaOS 3.1.4 released

#14
post #12

Why 3.1.4 and not 3.9.1 ?

The AmigaOS 3.9 code was largely unavailable for development work. What remained and was availabie is material which was licensed for inclusion in AmigaOS4.

What we got here is a mix of the AmigaOS 3.1 code (bug fixes galore, plus enhancements), the 3.5 update, the 3.9 update plus completely new software such as Disk Doctor V2.134 (written from scratch to support large storage devices and all Amiga file system flavours descended from the 1986 default file system; this is not your father's Disk Doctor any more).

The other reason why it's 3.1.4 is that we realized early on that we could not continue development of the 3.x line anyway, so we joked it would have to be an irrational version number instead, perhaps one digit at a time.

Re: AmigaOS 3.1.4 released

#15
post #8
post #7

"Remember "Diskdoctor"? It earned its PhD and is now ready to reliably rescue data from your floppies or hard disks." Remember the cool old "AGA - time to upgrade - AGA" slogan in some of the demos? Now it's ZFS - time to upgrade - ZFS ...it's the 21st century, and AmigaOS doesn't even have software RAID, let alone ZFS yet. We still have to check filesystems for metadata corruption, and checking them for data corrupt…

You could use OFS (Original File System, before FFS) which has checksums in every block! Note blocks are <512byte because of that (ouch) and everything else about OFS sucks.

Smaller than 512 bytes? I beg to differ. The file system data structure layout requires a minimum of 512 bytes per block.

The Amiga OFS/FFS, etc. file system data structures scale with the block size (block sizes of 512, 1024, .., 65536 bytes are possible).

At 256 bytes per block, for example, the directory hash table size would shrink so much that you'd have so many hash collisions that it would be morbidly funny...

Anyway, the data blocks in OFS have to account for the checksum and some metadata which aids in recovery. So you are correct that the payload (488 bytes for a 512 byte block) is smaller than the raw block size.

Re: AmigaOS 3.1.4 released

#16
post #12

Why 3.1.4 and not 3.9.1 ?

The AmigaOS 3.9 code was largely unavailable for development work. What remained and was availabie is material which was licensed for inclusion in AmigaOS4. What we got here is a mix of the AmigaOS 3.1 code (bug fixes galore, plus enhancements), the 3.5 update, the 3.9 update plus completely new software such as Disk Doctor V2.134 (written from scratch to support large storage devices and all Amiga file system flavou…

Good old "PiVer", the TeX approach to versioning: https://en.wikipedia.org/wiki/Software_versioning#TeX

Re: AmigaOS 3.1.4 released

#17
post #2

Already bought and tried in an emulator. I find it annoying the rom doesn't include workbench.library, and the provided one in LIBS: isn't romable. It'd only be proper to provide a 1MB rom image with it, or a limited functionality version.

ROM space is very tight for this release on account of the much larger mass storage drivers (SCSI, IDE) and the integrated OCS/ECS/AGA graphics.library.

Commodore was already pushing the limits for the 1994 Kickstart 3.1 in the Amiga 1200 ROM, and it only got worse. The Amiga 4000T ROM would no longer contain workbench.library either (in 1994) because the graphics.library and the SCSI driver took up so much room.

There is no room for workbench.library and icon.library in the 512 KB 3.1.4 ROM. Going back to a previous set of workbench.library/icon.library versions is not an option because these do not fit either.

1 MB ROMs are not viable solution at this point. Only a select few models support these, and the point was to make the 3.1.4 update available to all desktop systems.

Besides, a 1 MB ROM would require retooling of the build process for the operating system, which we did not attempt. The last 1 MB ROMs were built in 1994 (for the CD32) and very little documentation survives on how this is done, and how the ROM images need to be prepared.

We were already quite busy with the desktop systems and chose not to spend the time on research and QA work necessary for the 1 MB ROM build.

Re: AmigaOS 3.1.4 released

#18
post #10
post #6

Earlier quoted context omitted.

There's going to be a physical version at some point, but summary: 1. Buy A500/A600 download version, or A1200 if you've got a Vampire accelboard. 2. Get adf into Amiga floppies by whatever means (serial cable, pcmcia nic adapter, flashfloppy-enabled floppy drive emulator) 3. Boot workbench disk or installer disk. ROM patches will be loaded by loadmodule @ startup-sequence. 4. (Optional) Flash into (E/EE)PROM chip or…

And where could one get a compatible ROM flasher and WORM chips?

If you are looking for an affordable solution you can use this: https://gglabs.us/node/2038

Re: AmigaOS 3.1.4 released

#19
post #2

Already bought and tried in an emulator. I find it annoying the rom doesn't include workbench.library, and the provided one in LIBS: isn't romable. It'd only be proper to provide a 1MB rom image with it, or a limited functionality version.

ROM space is very tight for this release on account of the much larger mass storage drivers (SCSI, IDE) and the integrated OCS/ECS/AGA graphics.library. Commodore was already pushing the limits for the 1994 Kickstart 3.1 in the Amiga 1200 ROM, and it only got worse. The Amiga 4000T ROM would no longer contain workbench.library either (in 1994) because the graphics.library and the SCSI driver took up so much room. The…

>There is no room for workbench.library and icon.library in the 512 KB 3.1.4 ROM.

Unfortunately. Understandable.

>Only a select few models support these, and the point was to make the 3.1.4 update available to all desktop systems.

Nobody is telling you to ditch the 512k rom. It's just it sucks not to have workbench.library and icon.library, when using a system that does maprom with 1mb support.

>The Amiga 4000T ROM would no longer contain workbench.library either (in 1994) because the graphics.library and the SCSI driver took up so much room.

And roms with workbench inside were proudly released recently. Meaning both there's interest, and that you understand this interest.

>We were already quite busy with the desktop systems and chose not to spend the time on research and QA work necessary for the 1 MB ROM build.

It's good if there was at least consideration.

Maybe try and release romable versions of workbench and icon library? The community will take over from there, with tools.

Re: AmigaOS 3.1.4 released

#20
post #8

Earlier quoted context omitted.

You could use OFS (Original File System, before FFS) which has checksums in every block! Note blocks are <512byte because of that (ouch) and everything else about OFS sucks.

Smaller than 512 bytes? I beg to differ. The file system data structure layout requires a minimum of 512 bytes per block. The Amiga OFS/FFS, etc. file system data structures scale with the block size (block sizes of 512, 1024, .., 65536 bytes are possible). At 256 bytes per block, for example, the directory hash table size would shrink so much that you'd have so many hash collisions that it would be morbidly funny...…

Payload vs block size. Noted.
Post reply on HN