All off topic discussions go here. Everything from the funny thing your cat did to your favorite tv shows. Non-programming computer questions are ok too.
Hello,
After a long break from OSDev, I have decided to revive my OS project, with a new focus, and much code redesign. I am excited to start working my microkernel based system again, and I have some interesting ideas for it. I hope everyone else's OSes are going very well also
"How did you do this?"
"It's very simple — you read the protocol and write the code." - Bill Joy
Projects: NexNix | libnex | nnpkg
Hi, and welcome back, though you were here in April, yes? Just a few months ago. I have been missing in action a lot longer than that, on occasion . :-)
Since this is in the General Ramblings forum, I guess it is okay to ask, hoping others will participate.
If I see a fellow developer post his/her site, I will usually go and have a look. Most of the time it is a github or similar style page with no binary to speak of. Yes, most of them have build instructions, but, in my opinion, every build environment shown is just enough different than the next, that you have to have practically every build environment known to man to simply build a fellow coders OS. Something I will not do. Also, and I think I speak for most, I won't take the time to create a local source tree, setup the build environment, and build your OS. I have one of my own already set up.
So, here is my question. Is it wrong to include an actual disk image of an already built system?
For example, most of us, including myself, can have a bootable 100meg image contain our entire work. Then when zipped down, won't be more than 4 or 5 Meg. A simple and quick download.
If I see a disk image, I will usually download it, point QEMU or Bochs to it and run it. If I see a source tree only, I may spend 10 seconds or so browsing, and probably never return.
Also, if I can run it with a quick modification of an already created generic command-line file, I am more apt to test it and point out errors. Not in the sense of being critical, but in the sense that all of us would like to someone to point out flaws in our work so that we can fix them. Yes?
BenLunt wrote:So, here is my question. Is it wrong to include an actual disk image of an already built system?
For example, most of us, including myself, can have a bootable 100meg image contain our entire work. Then when zipped down, won't be more than 4 or 5 Meg. A simple and quick download.
Is it wrong? In the repository, probably yes. But you can easily build it from source using one of the free CI services (I would recommend GitHub actions).
managarm: Microkernel-based OS capable of running a Wayland desktop (Discord: https://discord.gg/7WB6Ur3). My OS-dev projects: [mlibc: Portable C library for managarm, qword, Linux, Sigma, ...] [LAI: AML interpreter] [xbstrap: Build system for OS distributions].
nexos wrote:Hello,
After a long break from OSDev, I have decided to revive my OS project, with a new focus, and much code redesign. I am excited to start working my microkernel based system again, and I have some interesting ideas for it. I hope everyone else's OSes are going very well also
It's nice to see you around again
I wish you all the best with your redesign plan!
nexos wrote:Hello,
After a long break from OSDev, I have decided to revive my OS project, with a new focus, and much code redesign. I am excited to start working my microkernel based system again, and I have some interesting ideas for it. I hope everyone else's OSes are going very well also
It's nice to see you around again
I wish you all the best with your redesign plan!
Thanks! I think this time my OS should be good.
"How did you do this?"
"It's very simple — you read the protocol and write the code." - Bill Joy
Projects: NexNix | libnex | nnpkg
