davxy/beeos

A simple "Unix-like" kernel trying to be POSIX compliant

• I like distributed systems, cryptography and applied cryptography
• From time to time I publish something on my website
• I may have very strong opinions 🤓
• Currently I mostly work on Polkadot as a core engineer.

PGP Keyring Fingerprints:

• CERT: 9484AE9C0DE026ADF6A15A538F550699515C84CB
• SIGN: A9DB468DF6E72CBACFABD1DA1072DA289B21507F
• AUTH: 5170D3182B209970FBB6CF0AE95FB548607777F7
• ENCR: 6E9E1AF980F08CB580F148E4EF4E1FB501474DC0

On-chain identities:

• KSM: HyPMjWRHCpJS7x2SZ2R6M2XG5ZiCiZag4U4r7gBHRsE5mTc
• DOT: 16Q4qkRcWd4r8196dVGNLYVfy7H86MJYJBMockPaMigFXCyv

You can reach me via mail, matrix, mastodon, twitter

beeos's Issues

Could BeeOS fit on a floppy?

Good day @davxy ! Please tell, could BeeOS fit inside a floppy? Even today the floppies are still being used, for example - as virtual floppies inside the coreboot open source BIOS. Just imagine: your wonderful OS could be a part of someone's BIOS build! (for coreboot supported motherboard, maybe you have or could get one - see https://www.coreboot.org/Supported_Motherboards ) It seems that BeeOS size is less than 1.44MB, but I would like to make sure

Why not build a community in this project?

I think this project is very good. At least it is a lightweight kernel, which is very conducive to learning and research. Why doesn't the author plan to set up an open source community for this project?

BUILD FAILED

@davxy
@Mcpg
@informer2016
@malbx
@game-lover
linker could not found -lgcc flag.

Memory limit

with more than 466mb of memory beeos crashes at startup

This problem occurs when I jump the memory size to 2G or more, and cannot start

This problem occurs when I jump the memory size to 2G or more, and cannot start

Error adding high mem zone

*** kernel panic: init exiting

I have tried building this kernel on a few different machines but seem to have an issue getting a build to run in QEMU.

I didn't make any changes to the source code, and simply ran the following commands:
make all && (cd misc; sudo ./mkfs.sh; ./qemu.sh)

From some preliminary println debugging, it seems that the execve syscall is throwing an error, since named(path) ends up being NULL. This is due to !S_ISDIR(dent->inod->mode) in named() returning false on the first iteration.

I am testing on a very clean version of Ubuntu 20.04.2 LTS.

I would love if you could give some insight as to why the first build might not be succeeding. I have attached the disk.img file below.

Thanks!

disk.zip

Question: Where you take user apps?

This is your own user apps or you took it from someone?