ANNOUNCEMENT: progOS

I'm happy to announce I'm starting to work on creating the prog Operating System. Stay tuned.

wots dis lonox fing evywun tolkin aboot?

Whats the advantage of writing yet another kernel other than having even less driver support than plan 9 and losethos?

>>35
Unless you consider the OS kernel to be OS, an OS needs more than a kernel to be useful. When I was an OS hacker, I never considered the kernel but as one part of a complete system.

>>43
Hi, Richard

>>42
Escaping the GPL (yes, there are legitimate reasons to do this other than hurr durr my source code is so precious).

>>45
What about the BSD kernels?

>>46
Can they be linked against proprietary code?

>>45
legitimate
You don't know what that word means.

>>48
http://oxforddictionaries.com/definition/english/legitimate
2 able to be defended with logic or justification; valid

I want my own OS with my own features. I don't want a hierarchical filesystem, memory protection, C code. I want my own software.

>>50
so... tell us about your desired fs

also C code has nothing to do with the final product and without memory protection the kernel would be so easy to break it wouldn't even be funny

>>45
What legitimate reason would you want to escape the GPL? I thought the only reason was to keep the source code hidden.

modern operating systems must be rewritten in javascript. javascript interpreters emit highly optimized machine code and can be optimized while the program is running, making them faster than any other language.

>>53
Lisp did that earlier than Javascript.

Anybody care to explain what Lisp Machines are? How is it different from contemporary OSes?

Linux runs on fucking everything. It's the greatest OS of all time.

>>52
You could come up with a license that allows not-for-profit non-commercial non-governmental personal/educational use for free (and forces users to publish any changes they make to the source code), and makes you pay up otherwise.  The project can be entirely open source.

>>56
Linux is fucking awful!
It keeps saying "no init found" or something like that no matter what i try and which version i try it with.

>>57
That sounds more complex than what the GPL3 requires.

We need a license that says you can do whatever you want with the code as long as you make no profit from it. Or if you do make profit, you must give 100% of it to the original author.

MAKE ONE PROGRAM DO ONE THING VERY WELL
MAKE PROGRAMS WORK TOGETHER
LISP OR DEATH!

>>59
That reminds me, it should also ban tivoization.

>>60
The second part doesn't sound very reasonable.

The second part doesn't sound very reasonable.
That's true, it should be more like 300%.

hardware is too complicated, what do i need to read to make an OS? something like losethos, maybe better. Intel manuals are too large, and some parts are hard to read. also need to learn about disks and other stuff, but what else?

>>64
Start by writing your own C compiler. That alone should take a couple years. If you still have the energy, then write an operating system.

>>65
>a couple years

Maybe if you

write the whole thing in raw machine code with 8 hours a day 5 five days a week,

write the whole thing in c with 2 hours a day 4 days a week

write the whole thing in lisp with 1 hour a day, 1 day a year.

>>65
tcc was written real fast. what does c have to do with an OS? i dont want to write a c compiler.

WE NEED BETTER NON BLOAT SOFTWARE

SOFTWARE IS SHIT, NOT CPUS

ALSO HARDWARE NEEDS TO BECOME OPEN AND MODIFIABLE LIKE IN THE EARLY 80S TRULY BUILD YOUR OWN COMPUTER

>>68
80's hardware are relatively simple that people can actually go get some parts and put it together. Today's miniature electronics are difficult to manufacture by hand and must be done with special manufacturing equipment.

>>64

If you were writing a modern operating system from scratch, why on earth would you use C in stead of LISP?

Unless you're writing Yet Another Shitty UNIX Clone, in which case I suggest you do something worthwhile and write drivers for Plan 9.

>>69

My software needs have been growing more and more minimalist over the years[1].  If I ever take an interest in hardware beyond ``it just works'' it would be super cool to build my own 680x0 machine with certain modern conveniences, like a 16 GB CF card SSD[2] and double-buffered graphics because RAM is dirt cheap.

Unfortunately the later 68k-series processors that can address more than 16MB don't come in DIP, because they need too many pins.

Except for Firefox I don't even notice the difference between my 2011 Thinkpad and 1997 Dell.  Once I can break my addiction to Web shit[3] I'll have no reason whatsoëver to run a modern machine.

Too bad I can't into hardware beyond blathering on the Internet.

[1]: In 2005 I used OpenOffice.  In 2009 I switched to LaTeX.  In 2012 I switched to TROFF.

[2]: CF cards use the IDE interface.  I used a passive CF::IDE adaptor for a year when my laptop's hard drive died.

[3]: The only ``web shit'' I do with any regularity that doesn't Just Work in Plan 9's Abaco browser is posting on the imageboards.  That worked fine in text mode in Lynx until the advent of CAPTCHA.

>>70
Modern scripting languages require fast CPUs and a lot of memory. I doubt anyone writes C/C++ anymore.

>>71

Are you addressing my comment about LISP and C, or about old-fashioned machines?

>>71
Modern scripting languages require fast CPUs and a lot of memory.
Modern scripting languages are shit