Hi! Are you a front-end web developer? Now is your chance for you and your buddies to contribute to NodeOS (without having to decipher underlying technology in the build process; double win!)

We're redesigning our website and would love to have the talent's of all the developers combined! The first step, of course, would be to design a new page so let's use this thread and create a new idea. You may propose:

• Theme idea's
• Template ideas (you can sketch, or paste screenshots)
• Web frameworks (like bootstrap) that we should (or shouldn't) use, and why

Looking forward to getting this going with you all! Tell all your friends!

Hello, I stumbled across your project. From the looks of it you guys need a Desktop? Well I'm helping out with one it's called OS.js and runs on node.js. (I'm not the creator but one of the contributors.).

Here the website: http://os.js.org/ Here is the demo: http://osjsv2.0o.no/ Here is the source: https://github.com/andersevenrud/OS.js-v2

It's still in Beta, were still having some trouble with getting help but were moving along quite well.

This is a work-in-progress pull-request just so we can comment on it.

Finally I've managed to create a cross-toolchain and use it to compile a runnable NodeOS instance (i386-glibc -> i686-musl, I need to test x86_64 -> i386). After some tries, I got it to work using as basis Cross Linux From Scratch - Embedded, that uses musl as C lib instead of standard glibc. I wanted to use a glibc based system, but this is the only one I've managed to make it to work, since using the plain Linux From Scratch or also the standard Compressed Linux From Scratch (both based on glibc) was fairly overcomplicated and gave a lot of compilation problems.

This has some drawbacks that needs improvement (or not :-) ):

• it's a musl based system, so compiled modules that use non-standard extensions of GNU glibc will not compile. It's a fail of the developers, so this could help to improve their code to be C standard compliant (win-win for all :-) ).
• OpenSSL doesn't work well with musl (due to the use of that non-standard extensions...) and needs to be patched since nobody fix it :-( Luckily it's an easy one...
• GCC is not aware of musl so it needs to be patched, too. This leads us to use a fixed GCC version, but since it's somewhat new (April 2014) and probably we'll move to llvm when Linux could be compiled with it so we can use one of the llvm Javascript flavours on the userspace, then it's a fair trade by this moment.
• I was not be able to use a dynamically linked Node.js executable, so I'm using a fully-statically linked one. This should be fixed in the future for loading of compiled modules and specially to exec binaries, but if we don't allow binaries at all and since now require() of modules works because musl now include the required dl_ functions (at least native ones does while it was not working before, I need to test external ones), this could help to enforce a pure-Javascript environment :-) On the other hand, this also has the advantage that the memory foot-print is smaller since now the only required files on the initramfs are the console device and the Node.js executable (impossible to make it simpler!!! :-D )

It's still unstable and needs some more work and testing (please test it! :-D ), but when it's finished, NodeOS build system will be self-contained and will be easier to port it to other platforms just by updating the cross-compiler :-) Also I've been developing it as a NPM package, so when it's ready in the future we could be able to move it to be an independent project (I would love to see NodeOS self-hosted... :-D ).

Hi all!

Great work so far. I'm trying to run NodeOS using vagga within vagrant (because I'm on OSX). I downloaded both vagga RCs:

x86_64-vagga & i386-vagga

and after running vagga run I get:

thread '<main>' panicked at 'assertion failed: iter.next() == Some(RootDir)', src/path_util.rs:18

It's very possible that I'm doing something wrong. Any have any idea?

Thanks!

I really like the idea of this, it would make the OS less prone to errors and would make security a lot easier - there will be only the NPM packages as suspects. And updates will be a breeze for anyone.

Though i must admin i first thought it was a complete desktop experience ;-)

I've got that error with Arch Linux

Compiling init
make: x86_64-nodeos-linux-musl-gcc: Kommando nicht gefunden
<eingebaut>: die Regel für Ziel „init.o“ scheiterte
make: *** [init.o] Fehler 127
rmdir: konnte '/home/philipp/Dokumente/github/NodeOS/node_modules/nodeos-barebones/build/nocona' nicht entfernen: Datei oder Verzeichnis nicht gefunden

Hello! I'm from B2G OS Communications. As you all know Mozilla handed over smart phone code development to it's community. Since then, we are working hard to make the project come live again. In this process, we don't have people to handle gecko. B2G OS relies on standard web APIs. I recently came across this project & it's cool & you are also targeting SoC's like raspberry pi !. Can you please help our project from gecko side.

All our project discussions happen here: https://discourse.mozilla-community.org/c/b2g-os-participation

Thank you

Does NodeOS already have a utility to launch applications that need to begin on start up? If there is one, does it have an interface for apps to add or remove themselves from this list? I'm thinking of people who run servers for testing (like redis) or for GUI users, messengers and such.

Hey, i want to know if we can use es6 features like template strings and such things because nodejs.org (https://nodejs.org/en/docs/es6/) and kangax (https://kangax.github.io/compat-table/es6/#node4) shows that in node 4.4.3 we can use them.

And if we can make use of them, should we use it in strict mode?

Like in the other file (dockerBuild) we need to change the name to lowercase. And after this docker complains about absolute paths for this i put a slash infront of the userfs variable.

After this i get this error we already discussed #227:

λ philipp [~/Dokumente/NodeOS] at  master !?
→ npm run docker                                                                                          [e16936d]

> [email protected] docker /home/philipp/Dokumente/NodeOS
> scripts/docker

mount procfs: Operation not permitted
mount devtmpfs: Operation not permitted
fs.js:1048
  return binding.symlink(preprocessSymlinkDestination(target, type, path),
                 ^

Error: EEXIST: file already exists, symlink '/proc/mounts' -> '/etc/mtab'
    at Error (native)
    at Object.fs.symlinkSync (fs.js:1048:18)
    at /lib/node_modules/nodeos-mount-filesystems/server.js:381:6
    at /lib/node_modules/nodeos-mount-filesystems/node_modules/mkdirp/index.js:48:26
    at FSReqWrap.oncomplete (fs.js:117:15)
/proc/sched_debug: Operation not permitted
/proc/timer_stats: Operation not permitted
/proc/kcore: Operation not permitted
/proc/sysrq-trigger: Operation not permitted
/proc/sys: Operation not permitted
/proc/irq: Operation not permitted
/proc/fs: Operation not permitted
/proc/bus: Operation not permitted
/proc/asound: Operation not permitted
/dev/console: Operation not permitted
/dev/shm: Operation not permitted
/etc/hosts: Operation not permitted
/etc/hostname: Operation not permitted
/etc/resolv.conf: Operation not permitted
/dev/sda: Operation not permitted
/dev/mqueue: Operation not permitted
/sys/fs/cgroup/blkio: Operation not permitted
/sys/fs/cgroup/cpuset: Operation not permitted
/sys/fs/cgroup/pids: Operation not permitted
/sys/fs/cgroup/freezer: Operation not permitted
/sys/fs/cgroup/devices: Operation not permitted
/sys/fs/cgroup/memory: Operation not permitted
/sys/fs/cgroup/net_cls: Operation not permitted
/sys/fs/cgroup/cpu,cpuacct: Operation not permitted
/sys/fs/cgroup/systemd: Operation not permitted
/sys/fs/cgroup: Operation not permitted
/sys: Operation not permitted
/dev/pts: Operation not permitted
/dev: Operation not permitted
/proc: Operation not permitted
/: Operation not permitted
termination: Operation not permitted

npm ERR! Linux 4.6.2-1-ARCH
npm ERR! argv "/home/philipp/.nvm/versions/node/v5.12.0/bin/node" "/home/philipp/.nvm/versions/node/v5.12.0/bin/npm" "run" "docker"
npm ERR! node v5.12.0
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! [email protected] docker: `scripts/docker`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] docker script 'scripts/docker'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the NodeOS package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     scripts/docker
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs NodeOS
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls NodeOS
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/philipp/Dokumente/NodeOS/npm-debug.log

Framebuffer currently use the vanilla Tux logo on boot, we can cnange it to show NodeOS logo. Also, just today has been submitted a patch to Linux kernel to allow full-screen logos, that would be cool... :-)

whk@machine:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.4 LTS
Release:	20.04
Codename:	focal
whk@machine:~$ sudo docker run -t -i nodeos/nodeos
[sudo] contraseña para whk: 
Unable to find image 'nodeos/nodeos:latest' locally
latest: Pulling from nodeos/nodeos
94a50c750e92: Pull complete 
cc815e2e56f5: Pull complete 
b59c556bab11: Pull complete 
Digest: sha256:be4ab273faeb9dd296a3dd161d1a16faa7e9a1f15c948649070c4f4818bc708f
Status: Downloaded newer image for nodeos/nodeos:latest
mount procfs: Operation not permitted
mount devtmpfs: Operation not permitted
Trace: { Error: EPERM, Operation not permitted 'overlay'
    at Error (native) errno: 1, code: 'EPERM', path: 'overlay', syscall: 'mount' }
    at onerror (/lib/node_modules/nodeos-boot-multiUser/server.js:23:11)
    at /lib/node_modules/nodeos-boot-multiUser/server.js:46:26
    at /lib/node_modules/nodeos-boot-multiUser/lib/index.js:97:24
    at /lib/node_modules/nodeos-boot-multiUser/lib/jocker_root.js:198:24
Starting REPL session
NodeOS-boot-multiuser>

I have a plan + idea for starting a NodeOS windowing (GUI) kit, which being all js+html+css. I'd like to know how nodejs, when booted, how can it launch is UI process.

NodeOS is an operating system built entirely in Javascript.

Pardon me if I'm wrong but after browsing through the repository source's I just can not find anything in that regards.

The codebase is way too smal for this to be an operating system built in Javascript. Where's the kernel source in js? Where are the drivers in js? There's nothing?

The first operating system powered by node.js and npm.

This isn't really accurate either isn't it?

As far as I can tell this is a linux distribution that comes shipped with node.js/npm that with a sort of set-up node environment that boots into a node.js REPL.

This is FAR from being an operating system, let alone one built in JavaScript and let alone one that is powered by node.js/npm. It's a linux distribution, right?

This is the default start script file provided by NodeOS:

#!/usr/bin/env node

/**
 * NodeOS
 *
 * @copyright 2013-2017 Jacob Groundwater, Jesús Leganés-Combarro 'piranna'
 *  and other contributors
 *
 * @license MIT
 */

const spawn = require('child_process').spawn;

const prepareCommandLine = require('..')


const {command, argv, cwd} = prepareCommandLine(process.argv.slice(2))


// Exec NodeOS
spawn(command, argv, {stdio: 'inherit', cwd})
.on('error', console.trace.bind(console))
.on('exit', function(code, signal)
{
  process.exit(code || signal)
})

And when I run "npm start" in Ubuntu WSL it displays this error:

const {command, argv, cwd} = prepareCommandLine(process.argv.slice(2))
                             ^

TypeError: prepareCommandLine is not a function

I have also tried "bash npm start", but it just displays this error:

/home/stanlyhalo/.nvm/versions/node/v12.18.0/bin/npm: npm: line 2: syntax error near unexpected token `;'
/home/stanlyhalo/.nvm/versions/node/v12.18.0/bin/npm: npm: line 2: `;(function () { // wrapper in case we're in module_context mode'

What I'm trying to do in the end is run NodeOS in qemu.