This forums is for OS project announcements including project openings, new releases, update notices, test requests, and job openings (both paying and volunteer).
I recently completed a beta version of my operating system's installer (Bootable floppy that installs the OS to the hard drive) and I'm thinking that it would be possible to modify it so that it can be used by almost any operating system.
But before I commit the time to doing so, I would like to hear from people if there would be any interest in such a tool. What do you guys think? I've provided some screenshots so you can see what it's like.
The Installer Start Screen
Partition Select Menu
Installing Files... (No progress bar yet )
Feel free to comment or ask questions. If there's interest, I'll start working on it
Edit: Work has begun! Changed topic
Last edited by Thor on Fri Aug 21, 2009 9:38 pm, edited 1 time in total.
That's probably one of the better ideas I've read on these forums. If it were as customizable as GRUB, for instance, another osdeving tool used by much of the community, I can see your installer as being a counterpart to it.
To note, however, I have for use for it at the moment. (My osdev work has been *slow* in the last months.)
xvedejas wrote:Grub itself already has lots of support for various filesystems, I wonder how practical it would be to build your tool on top of grub?
Meh, not very. It uses its own custom bootloader, and the installer itself runs in 32-bit protected mode. It can only boot from a FAT12 floppy right now, but I was more meaning filesystems used by the Operating System being installed.
However, the MBR and Bootloader files to be written to the HDD can be customized, so there's nothing stopping the installed OS from using GRUB.
GRUB would actually be a good default bootloader to be installed (if no custom one is specified).
I say its a neat idea, but I see a few problems with it.
1. Filesystems. A lot of us OS devers also like to be FS designers while we are at it. How would we use your installer with a custom filesystem?
2. Install-time scripts. Many OSs need for certain things to be set a certain way at installation time. How would you accommodate for this? (please don't say an installer scripting language. That is very limited)
other than that. It really sounds like a good idea if it can be implemented right
earlz wrote:
1. Filesystems. A lot of us OS devers also like to be FS designers while we are at it. How would we use your installer with a custom filesystem?
2. Install-time scripts. Many OSs need for certain things to be set a certain way at installation time. How would you accommodate for this? (please don't say an installer scripting language. That is very limited)
Good points. I suppose the 2nd could be accomplished through modules making use of the installer's standard library, but even that is rather limiting.
I suppose the best way would be for an OS to have a kind of "Stage 2 Installer" that is only loaded on first boot - ie, it doesn't actually install anything, but simply sets it up. But of course we're talking about a way to fix it with the installer.
As for custom filesystems, it would be possible to also do so through a module loaded by the installer...
Anyways, I have decided that I will go through with the project, so I'll try to keep you guys updated on what's happening with it
good luck and be sure to create a decent design before starting.. (contrary to popular belief, things don't just fall into place as you start implementing)
I'd use something that could install my OS to a hard drive.. provided it can install GRUB Legacy too. At one point I was trying to figure out how to use GRUB's menu to install itself, my kernel, and my kernel's support files to the hard drive, but I gave up on that, hehe.
As long as it supports at least FAT, I'm in
Solar wrote:It keeps stunning me how friendly we - as a community - are towards people who start programming "their first OS" who don't even have a solid understanding of pointers, their compiler, or how a OS is structured.
I have a basic config file, which allows you to provide a list of files to be copied as well as an MBR and bootsector, and OS Name. The bootsector is installed to the start of the partition being installed to, and files are installed to the partition using the appropriate FS driver. So you could specify the bootsector as GRUB and include the second stage in the files list, and there you are .
I'm planning on adding support for modules which will be executed after files are copied once I'm done the restructuring / updating phase.
There should be a companion bootloader to this. Sort of like GRUB on banned substances.
That would be awesome.
Solar wrote:It keeps stunning me how friendly we - as a community - are towards people who start programming "their first OS" who don't even have a solid understanding of pointers, their compiler, or how a OS is structured.
How would it handle such things as "install_boot" on OpenBSD for writing it's boot loader onto disk. It first writes the first stage bootloader, and then the second stage it put in boot (iirc) in a special disk location so that it can be found easily? (using FFS)
This installer is a good idea, most people are confined to virtual floppy disks. I think this is a great tool. By the way how is going with it has been 2 months since you lasted posted.
)
