Earlier quoted context omitted.
FYI: The site keeps crashing the tab in Firefox 115.7.0esr.
You should report it to Mozilla, nothing a site does should ever crash a browser. (Also, it could be an extension)
An IRC client in your motherboard
61–70 of 78 posts
Re: An IRC client in your motherboard
#62Earlier quoted context omitted.
Actually, all it takes on modern hardware for PXE boot to occur on hardware failure is the BIOS boot order setting. As PXE inherently trusts the LAN, and a LAN may have VLAN support, you can assign a default VLAN to the port which equates to the PXE server you want. The PXE server can further configure by client MAC prefix, DHCP-assigned IP mapped to physical port number or similar. Configured systems can report stat…
Well shit, glad I stumbled on this comment. Thanks for posting. Biggest gripe with my home lab setup is managing when something does or doesn’t PXE boot. Plug anything in and PXE boot it and it wipes the drive, does a scripted Debian install chained to an Ansible playbook that eventually installs k3s, discovers the rest of the cluster, and joins itself to it. So 0-click and 10 minutes from plug in to node in the clus…
Re: An IRC client in your motherboard
#63Re: An IRC client in your motherboard
#64Earlier quoted context omitted.
Actually, all it takes on modern hardware for PXE boot to occur on hardware failure is the BIOS boot order setting. As PXE inherently trusts the LAN, and a LAN may have VLAN support, you can assign a default VLAN to the port which equates to the PXE server you want. The PXE server can further configure by client MAC prefix, DHCP-assigned IP mapped to physical port number or similar. Configured systems can report stat…
Well shit, glad I stumbled on this comment. Thanks for posting. Biggest gripe with my home lab setup is managing when something does or doesn’t PXE boot. Plug anything in and PXE boot it and it wipes the drive, does a scripted Debian install chained to an Ansible playbook that eventually installs k3s, discovers the rest of the cluster, and joins itself to it. So 0-click and 10 minutes from plug in to node in the clus…
Every once in a while I look for a cheap remote KVM I can use as a crappy IPMI stand in, either with RJ45 or WiFi. I haven't looked in a year or so, but at the time the options I found all seemed far more costly than I would have hoped (the pi based ones seemed interesting but once you add the requirements together it wasn't cheap enough to be attractive to me for a home use). Server class equipment with built-in IPMI is quite a bit more expensive. I just want something affordable to put in front of a NUC to make dealing with it easier in some instances. You could stick some refurbished old KVM device in front of it to support multiple systems on that one KVM as long as they were in close proximity.
Seems like you could benefit from that as well (but in your case you might get a workable solution out of switch config though).
Re: An IRC client in your motherboard
#65bad ideas are bad. even if one can do them
Re: An IRC client in your motherboard
#66Maybe the most useless comment but: that non-linear mouse movement (aka acceleration) is the very first thing I turn off when I boot up a new OS. It literally hurts my hand somehow. For example linearmouse is free for Mac. For Windows you can just turn off acceleration. For Linux its easy, obviously.
Using mouse acceleration stops you from learning to map a distance traveled by the mouse to a distance on the screen. I do think its more efficient in the long run without it. Something I learned to do from gamers, and something I think all gamers still do for a good reason.
Re: An IRC client in your motherboard
#67> Each time we draw a bit of graphical content to a scroll view, we first allocate the tiles necessary to display the corresponding visual area. I get the intent here, to avoid the issue of not knowing how large a buffer to allocate for your scroll view in the first place. But doesn't this still use way too much memory? Especially for something like an irc client, the scroll view will only grow as the program is used…
Yes, you're absolutely correct! The design here totally suffers from unbounded memory use if you draw onto a large canvas. (Restating parts of your comment for confirmation that this is also how I think about it.) To resolve this while maintaining the spirit of the design, I think two representations need to be kept: one for the rendered pixel data, and one 'out of band' representation (such as the textual data - you…
But if it's fun, go ahead! Perhaps it's helpful for axle too. :)
Re: An IRC client in your motherboard
#68Hi everyone! As a bit of a gag, I’ve made a graphical IRC Client that runs entirely in the UEFI preboot environment. It features completely overdone features such as TrueType fonts, a cursor, and GUI decorations. I first started this project as I was getting a bit tired building a from-scratch GPS receiver, and wanted to make something relatively quick and lighthearted. As tends to happen, this took a fair bit longer…
Looking forward to ditching these bloated operating systems with all this cruft I I do not need for something smaller and simpler: UEFI. Not to mention faster startup. Easier "embedded" development. Of course I am joking. Sort of. As a minimalist I do not need a GUI or a mouse. It seems UEFI already has more than I need. Here is the Twitter client mentioned: https://github.com/arata-nvm/mitnal
Re: An IRC client in your motherboard
#69Earlier quoted context omitted.
You should report it to Mozilla, nothing a site does should ever crash a browser. (Also, it could be an extension)
With the possible exception of "consumes a lot of memory, leading to the OoM killer being invoked".
Re: An IRC client in your motherboard
#70Perfect for preboot botnets :)