/g/ - Technology

install openbsd

[Make a Post]
[X]





Operating system Nanonymous No.4302 [D][U][F][S][L][A][C] >>4305 >>5970
File: 20958bc1de2f95df562aae6c74a687070dee300fb5bae94e6373bd5bce7088c7.jpg (dl) (9.11 KiB)

How hard would it be to make a basic OS that lacks networking and other fancy functions? Something light weight comparable to Raspbian OS for raspberry pi. Which programming language would be best suited for such task and where can I learn the basics of OS making? Could you recommend any book?



Nanonymous No.4304 [D] >>4305

>what programming language
javascript

Nanonymous No.4305 [D] >>4309 >>4311 >>4328

>>4304
you mean html5
>>4302
Op come back when you understand how a compiler/assembler works and how the OS you're using works them maybe where gonna take you seriously. also raspbian is not really lightweight

Nanonymous No.4309 [D] >>4311 >>4318

>>4305
You sound like a gatekeeper.Why would I ask questions if I have to google everything?Have you tried searching for tech related information?The search results are full of Hindu code guroos, trannies and buzzfeed journalists.



Nanonymous No.4311 [D]

At top uni's this may be done in an OS class, so I wouldn't think it would be too hard however I believe that you would have to keep at it and really research what you were doing beforehand to really make sure that you don't fuck up.

>>4309
OP listen to >>4305 and also lose some weight.

Nanonymous No.4316 [D][U][F]
File: f8e38f2d856f56ade899490196f16cb0d0e9cc4f5beb8f44b65bf3f3c2603c00.jpg (dl) (143.51 KiB)

I have a passing interest in OSdev, so I can offer some advice snippets.

>Something light weight comparable to Raspbian OS for raspberry pi.
Raspbian is Debian-based. That means it's still using the Linux kernel, which is gigantic. So it's not something to compare your hypothetical project against. Try Multics (Organick's "The Multics System") or the earlier version of Unix (with the book being "Lions' Commentary On UNIX 6th Edition"). They have a lot less lines of code and a clearer structure that you can study.

Something I stumbled on recently is Niklaus Wirth's Project Oberon and his return to it relatively recently (2013-2014). It's a kind of research OS, written in Oberon, that, according to the authors, is designed so that a single person can understand the internals and work on it. But I'm fairly sure the 2013 version is implemented for RISC, so you'd have to do some emulation/VM.
Resource pool website that doesn't fucking have HTTPS
http://www.projectoberon.com
Wirth's personal page with the book available there
https://inf.ethz.ch/personal/wirth/ProjectOberon/index.html
Video of a talk he gave in 2014 about it
https://invidio.us/watch?v=EXY78gPMvl0

Nanonymous No.4318 [D][U][F]
File: 7df3d262c59dadfd921553d2ec5dbc13fbaa28183009f709597b53f3ef4afe6d.png (dl) (132.47 KiB)

>>4309
I don't want to hold you back, please try to make an OS nanon, it's always an experience, post results after, but my point is that you can't really find "how to make an OS" on google, cause it's something incredibly complex, if you want to take a shot at it you should:
first, understand how existing OSes works and try to go from there, try to make a Linux From Scratch, look up at Terry's videos and TempleOS source etc
second, understand how the low level works, to make an OS you should learn assembly, how a compiler works, how the processor works etc

So to conclude this and to answer you, there's not an easy way to do this, tech is a mess, there are plenty of things that could go wrong in such a project and there's nothing such as a book thats gonna tell how to do it as far as i know, maybe there's some book from the 80' but i don't know how useful is to make a modern OS, like remember that TempleOS runs only on the x86_64 architecture with no GPU support, as much as i love TempleOS that's unacceptable for a modern OS, and don't get me wrong it's not really Terry's fault, it's fault of proprietary hardware.รน

Good Luck

Nanonymous No.4328 [D]

>>4305
i wish you've never said that
https://greenteaos.github.io/

Nanonymous No.4329 [D] >>4344

>Green tea is like coffee, Greentea is like OS. Greentea OS is fine too :)
dafuq did you link nanon xD

Nanonymous No.4344 [D] >>5946

>>4329
the entire os is faggy enough, but I specifically had this in mind
https://greenteaos.github.io/Greentea/User-Guide/Web.html

Nanonymous No.4438 [D][U][F]
File: 277a44581b89356faeb4532fdc4d41062a0ec41cba5b72b43457d723d542d473.jpg (dl) (92.28 KiB)

The creator of MINUX is an academic and created it to teach students about OS design. IIRC, he wrote a book about it so that may be a start, but you'll likely need to learn everything equivalent to a computer engineering degree to understand it. Look up the course requirements for such a degree.

For a simple microkernel OS, look up the one that the new Google, Android replacement, OS is based on. The creator has the source posed on the clearweb.

Learning how an older 8-bit computer worked (like the C64) will be a good starting point too. New OS/hardware is way more complicated, but builds off the same ideas. In other words, if you can't understand how a C64 works, you shouldn't even bother with anything modern.

Nanonymous No.5940 [D]
we need a public domain operating system like templeos but modernized

Nanonymous No.5946 [D][U][F]
File: 3f1805de1a909cda2f813994e9f47bf70bfb5858c1c8a98f3d22c5a35ac13756.jpg (dl) (31.50 KiB)
>>4344
>Classic GUI technologies are known to be fast aging and non-portable, while they also are vulnerable, slow and buggy.
the last 3 only apply to webshit
>In comparison, there is HTML - old, proven, highly portable and quick to adapt GUI building model.
>proven
no
>portable
not even close
>quick to adapt GUI building model
not sure what that means, but programming webshit is not RAD in any way
>We are OK to drop some realtime app performance to gain nearly ultimate development opportunity - HTML is highly known very videly used tech.
>nearly ultimate development opportunity - HTML
into the trash you go
>There is also a solid bet on Vulkan graphics API, which should highly improve performance and responsiveness of apps.
I wouldn't be on anything that goes remotely near the GPU. enjoy your vulns from 1988
>Hexa has strict nullability, enforced exception checking, safe metaprogramming and supports advanced object oriented techniques.
but does it haves ruby inspired syntax?

Nanonymous No.5970 [D][U][F] >>5977
File: df88714551eddeb863ac951cc4441449d0786602659087a5ebc6ac54e5d413d3.pdf (dl) (3.96 MiB)
>>4302
>Could you recommend any book.
Reading is the best place to start. Attached is recommended. Operating systems do a lot - it's a lot more important to know the broader concepts and ideas first. Then you can choose to deep dive on individual parts and understand their implementation.

Nanonymous No.5972 [D] >>5973 >>5977
> Operating systems do a lot
bloat

Nanonymous No.5973 [D]
>>5972
Yep, operating systems are for niggers and snowniggers.

Nanonymous No.5975 [D] >>5976
>5973
>snowniggers
MAGA with DACA Mestizo detected

Nanonymous No.5976 [D]
>>5975
Fuck off back to /pol/, you have your containment pit so don't spill over.

Nanonymous No.5977 [D][U][F]
File: 7a42bdc57043c307a6f6177a64c789ecbc5e8ca087fbcd7049d291a903a01bc0.png (dl) (871.63 KiB)
>>5970
>>5972
>bloat
Well If you had a look at the book - "Operating Systems: Three Easy Pieces" you'll find that they can be divided into
- virtualization (resource management)
- concurrency
- persistence
but I guess it's too much to expect people on imageboards to read these days. These three elements are present in one form or another in all operating systems.

Of course, there are systems that do not have operating systems, where the programs run on bare metal, but that is another story. If you truly believe that all operating systems are bloat, then this isn't the thread for you.

Nanonymous No.5992 [D]
Qubes OS ftw