[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology

[Advertise on 4chan]


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


I'm currently building my own kernel and operating system. Should I stick with POSIX or create something that actually works?
>>
Why?
>>
>>80346482
Skip to the end by just drawing the mascot and abandoning the project today.
>>
Recreate everything from scratch like a good autist
>>
>>80346492
can't install gentoo
>>
>>80346482
If you're doing this for fun then absolutely do not stick to established conventions.
>>
i'd say take inspiration but obviously fuck around with the conventions and see if you end up with altered working version or an absolute fucking mess.
>>
There is literally nothing wrong with POSIX. People just hate on it to be contrarian.
>>
>>80346706
>creat
>>
Nakadashi Vignette
>>
>>80346706
>still has a worst security model than Multics
>atomically working with files is a landmine
>>
>>80346944
>an API
>whines about implementation details
your blow level retarded
>>
>>80346482
do what you want, you can add a posix compatibility layer later on
>>
>>80346482
If you manage to make something that actually works and isn't plagued by POSIX retardation, by all means go ahead.
Otherwise, don't waste your time. The world doesn't need more Unix braindamage.
>>
>>80347115
The API is very picky about how details are implemented. There's a reason some *nix programs have special modes that no one uses.
>>
>>80348099
the API can't be anything about anything. It's just a spec.
>>
>>80346482
will it use CISC or RISC instruction set(s)?
>>
>>80346482
you're probably in over your head if you think you're gonna get to a point where that matters, however if your serious then the choice boils down to:

write a posix compatible kernel and have access to all the libraries and software made for posix to run on your os eventually.
don't write posix compatible kernel and you'll have to implement everything yourself (which is fun but takes years)

by implementing everything yourself you can implement interesting features such as done in Synthesis kernel or Singularity. maybe even look at some of the interesting ideas behind plan9 and templeOS.

also there's already like 300 people reimplementing posix in their own os, so you can look at what that brings you in the long term before starting on it.
>>
>>80348155
>look ma' im sm0rt
it's about writing a kernel, not designing an architecture....
>>
what is vigne-chan developing?
>>
>>80346482
bump
>>
>>80348273
porn
>>
>>80346482
>I'm currently building my own kernel and operating system.
Contribute to the Hurd, thank you.
>Should I stick with POSIX or create something that actually works?
POSIX is shit and UNIX is shit, we have enough of this already.
Better make an OS in LISP and make a LISP machine.
>>
>>80350540
How does one manage to contradict themselves in every sentence they write?
>we have enough Unix-like shit but contribute to GNU/TURD (another Unix-like pile of shit)
>actually no, make a LispM instead
>>
if you're making it for fun, try to be as unorthodox as possible. otherwise go with POSIX
>>
>>80348246
Has to be designed for some kind of isa, I guess
>>
File: 1613950153249.jpg (159 KB, 1280x960)
159 KB
159 KB JPG
>>80351863
if you want to write your kernel in assembly, sure.
y tho?



Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.