#everythingisafile — Public Fediverse posts

I was able to port my #PLATOTERM terminal to #plan9 in an hour. It took only a fourth of the code of the #Linux version that uses #X11.

code: https://github.com/tschak909/platoterm-plan9/

#everythingisafile #distributedcomputing

I was able to port my #PLATOTERM terminal to #plan9 in an hour. It took only a fourth of the code of the #Linux version that uses #X11.

code: https://github.com/tschak909/platoterm-plan9/

#everythingisafile #distributedcomputing

I was able to port my #PLATOTERM terminal to #plan9 in an hour. It took only a fourth of the code of the #Linux version that uses #X11.

code: https://github.com/tschak909/platoterm-plan9/

#everythingisafile #distributedcomputing

I was able to port my #PLATOTERM terminal to #plan9 in an hour. It took only a fourth of the code of the #Linux version that uses #X11.

code: https://github.com/tschak909/platoterm-plan9/

#everythingisafile #distributedcomputing

I was able to port my #PLATOTERM terminal to #plan9 in an hour. It took only a fourth of the code of the #Linux version that uses #X11.

code: https://github.com/tschak909/platoterm-plan9/

#everythingisafile #distributedcomputing

I run a small #plan9 grid at home. This is my drawterm on my Linux PC connected to a Pi4 as a CPU server. It is viewing documents from my local PC, and I connected to a faster CPU in a window to play one of the NES games I wrote.

#distributedcomputing #9p #everythingisafile

I run a small #plan9 grid at home. This is my drawterm on my Linux PC connected to a Pi4 as a CPU server. It is viewing documents from my local PC, and I connected to a faster CPU in a window to play one of the NES games I wrote.

#distributedcomputing #9p #everythingisafile

I run a small #plan9 grid at home. This is my drawterm on my Linux PC connected to a Pi4 as a CPU server. It is viewing documents from my local PC, and I connected to a faster CPU in a window to play one of the NES games I wrote.

#distributedcomputing #9p #everythingisafile

I run a small #plan9 grid at home. This is my drawterm on my Linux PC connected to a Pi4 as a CPU server. It is viewing documents from my local PC, and I connected to a faster CPU in a window to play one of the NES games I wrote.

#distributedcomputing #9p #everythingisafile

I run a small #plan9 grid at home. This is my drawterm on my Linux PC connected to a Pi4 as a CPU server. It is viewing documents from my local PC, and I connected to a faster CPU in a window to play one of the NES games I wrote.

#distributedcomputing #9p #everythingisafile

Everything is a file https://www.both.org/?p=3191 #EverythingIsAFile, #Filesystems

Everything is a file https://www.both.org/?p=3191 #EverythingIsAFile, #Filesystems

Everything is a file https://www.both.org/?p=3191 #EverythingIsAFile, #Filesystems

@sean /tmp ;)
#everythingIsafile

@sean /tmp ;)
#everythingIsafile

@sean /tmp ;)
#everythingIsafile

@sean /tmp ;)
#everythingIsafile

@sean /tmp ;)
#everythingIsafile

Warum stehen File Descriptor Redirections eigentlich hinten wenn $shell sonst von links nach rechts liest?
ls -yz 2>&1 > foo
Warum nur stderr in foo landet, versteh ich ja aber warum bezieht sich:
ls -yz > foo 2>&1 auf die File Descriptors vom vorherige command (ls -yz)?

#everythingIsAfile

Warum stehen File Descriptor Redirections eigentlich hinten wenn $shell sonst von links nach rechts liest?
ls -yz 2>&1 > foo
Warum nur stderr in foo landet, versteh ich ja aber warum bezieht sich:
ls -yz > foo 2>&1 auf die File Descriptors vom vorherige command (ls -yz)?

#everythingIsAfile

Warum stehen File Descriptor Redirections eigentlich hinten wenn $shell sonst von links nach rechts liest?
ls -yz 2>&1 > foo
Warum nur stderr in foo landet, versteh ich ja aber warum bezieht sich:
ls -yz > foo 2>&1 auf die File Descriptors vom vorherige command (ls -yz)?

#everythingIsAfile

Warum stehen File Descriptor Redirections eigentlich hinten wenn $shell sonst von links nach rechts liest?
ls -yz 2>&1 > foo
Warum nur stderr in foo landet, versteh ich ja aber warum bezieht sich:
ls -yz > foo 2>&1 auf die File Descriptors vom vorherige command (ls -yz)?

#everythingIsAfile