Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make initial ramdisk server work again #35

Merged
merged 40 commits into from
May 24, 2015

Conversation

perlun
Copy link
Contributor

@perlun perlun commented May 21, 2015

As noted, this is unfinished yet. Not trivial because of problems w/ floppy images:

vagrant@packer-debian-7:/vagrant/servers/block/initial_ramdisk$ mdir
 Volume in drive A has no label
 Volume Serial Number is B1A5-B4DA
Directory for A:/

GRUB         <DIR>     2011-11-15  12:28  grub
storm           431746 2015-05-21  20:25
servers      <DIR>     2013-06-21  20:57
        3 files             431 746 bytes
                            210 432 bytes free

~200 KiB is simply too small to be able to fit in any reasonable ramdisk. Even a 360k 5,25 floppy image wouldn't fit there. So either I have to make the floppy.image be 2.88m (by figuring out how to do that in mtools) or go the "right" way and replace floppy.image with a dynamically rebuilt ISO9660 CD .iso image instead. The latter is obviously the nicer way, but maybe (?) more work. The "hard" part is getting grub installed onto the .iso I think, but this must have been done by others before us... so there should be a recipe somewhere.

@perlun perlun mentioned this pull request May 21, 2015
9 tasks
@perlun
Copy link
Contributor Author

perlun commented May 24, 2015

Seems to be rather cool now!

[boot] beginning of boot
[boot] Mounted the first available block service as //ramdisk.
[boot] Reading startup script...
[virtual_file_system] Mounting 20 at //ramdisk.
[boot] //ramdisk/config/servers/boot/startup not found.

This was fixed because of #37. The really nice part is that we can now have a much bigger initial ramdisk, maybe even large enough to fit a minimal Quake 1 installation? 😉 At least cluido, tetris, modplay etc etc should be no problem at all to fit now. If we want to use even more space, I'd suggest trying to implement an iso9660fs file system driver or something (but it also means we need an accompanying block server, so it's a bit of work - clearly doable but not something I will attempt this very moment).

@perlun perlun changed the title WIP: Make initial ramdisk server work again Make initial ramdisk server work again May 24, 2015
@perlun
Copy link
Contributor Author

perlun commented May 24, 2015

Should be green now (there was an obvious error in the build process, so merging).

perlun added a commit that referenced this pull request May 24, 2015
…erver-work-again

Make initial ramdisk server work again
@perlun perlun merged commit 5e7eb63 into master May 24, 2015
@perlun perlun deleted the feature/make-initial-ramdisk-server-work-again branch May 24, 2015 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant