These are chat archives for TARDIX/Dev

19th
Apr 2015
Jared Allard
@jaredallard
Apr 19 2015 00:02
Back!
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 00:02
Welcome back.
Jared Allard
@jaredallard
Apr 19 2015 00:07
Thanks :3
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 00:07
So, usermode procfs-dealie.
Aptly-named procd.
I'm also making a program library.
So you'll have program.start(func1, ...), program.daemonize():addEvent(event, handler):addEvent():start() etc
Jared Allard
@jaredallard
Apr 19 2015 00:09
Mhm
OMFG
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 00:13
omfg
we can use that with Lambda.
Jared Allard
@jaredallard
Apr 19 2015 00:13
:OOO
SO
MUCH
YES
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 00:14
you know you've been doing too much JS when you go table.join
Jared Allard
@jaredallard
Apr 19 2015 00:14
Haha
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 00:15
agh wtf
Jared Allard
@jaredallard
Apr 19 2015 00:15
Now my mom is making me make dinner
ffs
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 00:15
I bricked my cc pda :/
OH, OF COURSE
THERE'S A LOOP.
hue
I was firing an event(that causes threads to update) when threads update
Jared Allard
@jaredallard
Apr 19 2015 00:32
Lel
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 00:36
Added basic /usr/proc
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 00:43
@RainbowDashDC, /usr/proc is populated everytime a process is exec'd (either l or v)
Each proc entry has a process_plist that details the properties
Proc entries are named after the last 4 characters of their random tuids
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 00:57
Added program.daemonize, @RainbowDashDC
Jared Allard
@jaredallard
Apr 19 2015 02:49
Hm
I like :P
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 12:59
I just have to change the way the cfg is parsed
if we have multiple events instead of one event per entry
or maybe multiple handlers?
Jared Allard
@jaredallard
Apr 19 2015 18:00
How long will it be until block devices are supported and whats the plan on how so
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 19:14
Well, there'll be /dev/hd0- root
/dev/mnt/img0, /dev/mnt/img1, up until 999
/dev/nfs0, /dev/nfs1, up until 9
and /dev/disk0, disk1, disk2, etc
@RainbowDashDC, I'm implementing a libdev to simplify adding custom devices
(and for fixing the devd)
I'm going to patch devd to use program.daemonize
I'm also going to add 2-way evented communication with the filesystem
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 19:26
Hello!
@RainbowDashDC, using gitter on Atom :D
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 20:03
Libdev is working.
Devd on the other hand
Matheus Magalhães de Alcantara
@demhydraz
Apr 19 2015 22:03
@RainbowDashDC, block devices will be base64-encoded inode tables
So when you cat myFile > /dev/blk0, you'll actually brick the block device :P
Instead you should do (cat /dev/blk0 | concat < myFile ) > /dev/blk0
That'll properly format the new inode table