Search the Community
Showing results for tags 'rc'.
Found 2 results
TetraSource posted a topic in Libraries & API'sI just finished the first version of bundle - a rc application which virtually merges multiple filesystems into a bigger one. You can use it whenever a RAID full of tier 3 HDD isn't enough for your needs. On the picture above, for example, you can see 10 RAIDs with 30 tier 3 HDDs which yield a virtual HDD that can store over 200MB of data. You can also use filesystems of different size and create files bigger than any of the used filesystems since bundle is capable of storing a file on multiple HDDs. If you encounter any bug, please run it in the development enviroment first which is Open Computer 18.104.22.1686 on Minecraft 1.7.10 in Lua 5.2, although I also tested it in Lua 5.3. If the bug persists, please report it on my github repository. How to use it? First of all you can download it from pastebin (id: TmeSNidd) or my github repository and install the file in the directory for rc applications (/etc/rc.d/bundle.lua). Before using it you should configure the constants at the top of the script in accordance with their descriptions. Otherwise Bundle might work incorrectly. Then you need to add some filesystems by executing rc bundle add [address] in the shell. Please replace [address] by the address of the desired filesystem. Doing so wipes the added filesystem. However, Bundle never incorporates filesystems automatically. Next you should allow bundle to run in background by executing rc bundle enable Just reboot the computer and it should be listed by df Note that the label of the first added filesystem and the filesystem provided by Bundle are always equal since that's the way how bundle stores it. You can also view the added filesystems by executing rc bundle list You can also remove added filesystems by rc bundle remove [forcefully] Currently, this just removes the last added filesystem, however. If the removal causes the lose of data this fails except you set [forcefully] to true to remove the filesystem forcefully. Usage notes Please don't install the OS on a Bundle filesystem. Bundle requires some functions of OpenOS. Hence, installing the OS on a Bundle filesystem causes a dependency loop. Bundle uses a virtual copy of the file structure. So, when using complex file structure always provide a sufficient amont of RAM. On the other hand, this means that fs.exists(), fs.isDirectory() and fs.list() don't have to perform any "hardware" operation, thus being faster. Known bugs Seek operations that set the current position to a value that is bigger than the size of the file cause the file the become bigger than its actual physical size. This is also the case on filesystem components of Open Computers but with bundle it might cause internal errors. That is it for now, have fun using Bundle.
Ok!!! So I have been working my butt off to get this to work. It is a wirelessly controlled microcontroller! And if you have a look at the code you might notice that it DOES NOT HAVE SPACING! I RAN OUT OF EEPROM SPACE OK!!! DO NOT COMMENT ABOUT THAT!!! Ok... This took a long time to work all this out but I think its great! FEATURES: Network Cards (not sure about computronics spoofing card though) Wireless Network Cards (both tiers) Linked Cards (my personal favorite) Names Passwords Ports SUPER EASY!!! USES: Remote Door Control Remote Redstone Control Remote ANYTHING WITH A MICROCONTROLLER Control TUTORIAL: Step One - Set up a pc that can edit EEPROMs (I use the flash command) Step Two - Download the Pastebin file using this command: pastebin get BrhTgvET RCMICROBIOS Step There - Upload it to the EEPROM. I use this command: flash RCMICROBIOS Step Four - Make a Microcontroller: Must include these things 1. A Modem of any kind 2. A sign upgrade 3. The EEPROM that you just made Step Five - Place down the Microcontroller where you want then fill out a sign on ITS FACE like this: LINE1 = name of microcontroller LINE2 = password LINE3 = port (nothing if using a linked card) EXAMPLES SENDS: A. component.modem.broadcast(217,"DOOR A", "password123", "component.proxy(component.list(\"redstone\")()).setOutput(2,1)") --Yes you most call components this way on a EEPROM B. component.tunnel.send("DOOR A", "password123", "local R = component.proxy(component.list(\"redstone\")())") --But you can just save them as variables C. component.modem.broadcast(217,"DOOR A","password123","return R.getInput(2)") --it can even return data to you in a SERIALIZED packet! YAY! LINKS: https://pastebin.com/BrhTgvET And that's about it. If you have any suggestions just say so! I'll try to make this as great as possible!