• 1 Post
  • 146 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle

  • I had a Pentium I 120 MHz Packard Hell machine. It came with Win95 OSR 1 and I loved that beast. I upgraded the disk (1.1 GB to 3.1GB!) and the RAM up to 40MB. The screen was a 13" fishbowl so I get a Sony Trinitron 15" screen eventually.

    The combo modem/fax/sound ISA card wasn’t worth keeping, but I got a PCI Sound blaster as well as a 3Com 3c905 fast 10/100 Ethernet card. I had one of the best machines in the dorm for a while. Warcraft II played so very good.

    The Linux support in RedHat 5.2, then through 6.2, and sometimes Mandrake, OpenBSD, and some other distros was great. As long as you set the IRQs in the bios right it worked like a dream.


  • They are file handles. All three are opened by default for all new processes.

    STDIN is number 0 STDOUT is number 1 STDERR is number 2

    By default STDIN is connected to a buffer which keyboard chars are put in by the OS.

    STDOUT is a buffer read by your terminal emulator to be drawn on the screen if it’s a GUI. A raw terminal does the same, but without the windows manager layer in the middle. Essentially, the virtual terminal is reading the STDIO buffer and rendering the characters to it’s GUI windows for you.

    STDERR is the same as STDIO, but is usually only used for error messages, but they’re displayed via a different file handles so they can be captured and redirected separately from STDIO.


  • I turned down a professorship position at a uni in part because they used windows for the whole curriculum. It would have driven me crazy having to use windows given how annoying it is for dev work. I put value on my sanity and it wasn’t worth the modest pay bump to be driven batty every day.

    I likely get to teach an IoT class next term. It’s going to be so much fun with SBC systems running Linux and Arduino sensor systems! That’s worth a ton to me.



  • Your perspective might be why I enjoy microcontroller work. I love getting to know everything about the system, reading hardware documentation, and getting the low level parts to work in a highly deterministic way.

    I use ATTiny85 cores when a ESP32 costs almost the same, but the 85 only has 256 bytes of SRAM and five I/O pins so I can track it all and ensure it will do exactly what I want.









  • They did that to my daughter. I’d setup a laptop for her. The windows boot partition was still there (my bad for scraping every last bit of Windows off - it was setup in haste) and she accidentally chose windows from grub one day. The Windows Bootloader decided to change boot options in the bios and then remove grub somehow, but there was no windows on disk to launch so it was bricked.

    The next time I could out hands on the computer I scoured that disk clean of Microsoft’s plague rats so they wouldn’t get a finger in edgewise again.







  • Yeah, those durn data size fields. At first you’re like “why would you do this? It’s specified in the spec, right?” Then you start consuming the data stream and go “oh, yeah need this”.

    I was doing some driver work for a real time location tracking board. The serial stream protocol was very well documented and designed. Plenty of byte length count fields, though.