If you want to learn electronics without burning a capacitor or two, have a look at https://www.circuitlab.com/ . It allows one to draw circuit diagram and simulate it. Hope you'll find it useful.
Plan 9 is an Operating System (OS) from Bell Labs which is a successor to UNIX. It builds on the learnings from the previous Operating systems. Network computing and graphics is an integral part of the OS rather than an afterthought. It is modular and portable - it comes with a cross compiler . It is available, under MIT License , which anybody can use, learn and tweak. Features Everything is a file. Small Kernel: Around 5MB size which can be built in under 2 minutes. Singular Grid: All the computers running Plan 9 OS and connected together act like a singular grid. So there's no need for remote access solutions like VNC or RDP. This cool video shows a small glimpse of the possibilities. Process Isolation: Processes run within their own namespaces and are isolated from each other. So you can run rio (the window manager) within rio. Applications like Browsers don't need complicated sandboxing. And a crashing program is unlikely to bring down the OS. No DLL Hell : ...
UEFI ( Unified Extensible Firmware Interface) provides a quick way to set up a Plan 9 terminal on modern hardware . EFI System Partition (ESP) is a FAT32 partition. You should be able to modify it in most of the operating systems. Run mk in /sys/src/boot/efi . aux/aout2efi converts an a.out file to an EFI executable. For x86_64 hardware, copy over the files bootx64.efi (EFI application) , 9pc64 (kernel) , plan9.ini (configuration file) to \EFI\plan9\ directory in the ESP. If you want it be the default OS , you can create a symlink \EFI\boot to \EFI\plan9. Remember to include the full path to the kernel in plan9.ini. ( Note: ESP is a FAT32 partition. Hence you must use backward slashes.) bootfile=\EFI\plan9\9pc64 When bootx64.efi fails to find the bootfile (e.g. kernel is missing, plan9.ini is missing or path is incorrect), you can provide the arguments at > prompt followed by a boot command . Y...
Simple key visualizer for capturing keystrokes during a screencast using kbdfs, awk and statusmsg. Note : You need a Truetype font for arbitrary large display ( /n/ttf/mine/32/font in the example). Also, ensure truetypefs is running if you do use Truetype font. #!/bin/rc fn notify { scr=`{awk '{print $4, $5}' /dev/screen} w=200 h=60 ws=$scr(1) hs=$scr(2) minx=`{echo $ws - $w | bc} warg=`{echo -w $minx,0,$ws,$h} font=/n/ttf/mine/32/font aux/statusmsg $warg $1 } { tee /dev/kbdtap | tr '\000' '\034' | awk -v 'RS=\034' ' BEGIN { esc = sprintf("%c", 033) tab = sprintf("%c", 011) bksp = sprintf("%c", 010) del = sprintf("%c", 0177) ...
Comments
Post a Comment