oso2k

21 ms·

211.
by oso2k 6y ago
Not to be snarky, but that's easy. Just disconnect your cluster from the internet. We have hundreds of customers that are running disconnected clusters.
212.
by oso2k 6y ago
FAT32 isn't often included these days in Linux FS benchmarks [0] but some older benchmarks [1] also show noticeable performance differences, especially when the workload is more meaningful than copy files. Lack of features does not im
213.
by oso2k 6y ago
FAT32 is not a very fast filesystem. Things like caching are necessary to make it performant. Also, the IO subsystems in Win98 sometimes chose slow paths or interfaces.
214.
by oso2k 6y ago
Early Pascals did. P-Code [0] it was called. I don't think it was really about easy of compilation. It was about ease of portability, at least early on. [0] https://en.wikipedia.org/wiki/P-code_machine
215.
by oso2k 6y ago
Not surprised [0]. Pascal was always very fast to compile, especially with Borland tools. [0] https://prog21.dadgum.com/47.html
216.
by oso2k 6y ago
Probably short for Electromagnetism or short for EMF which is short for Electro Magnetic Field.
217.
by oso2k 6y ago
I haven’t found this to be true. I’ve used 4 or more different chargers. A couple off-brand USB-C chargers, USB-C dock/charger, Apple USB-C chargers, USB-C to USB 2.0/3.0 cables with 1A, 2.4A, 2.5A chargers. All worked without
218.
by oso2k 6y ago
With HIMEM.SYS + EMM386.EXE [0][1], you could include or exclude certain memory segments. But, DOS Subsystem for Linux uses non-standard little documented Unreal Mode [2][3] instead of traditional DOS Memory Management. [0] http:/&#x
219.
by oso2k 6y ago
A couple comments....this is super interesting to me. It boots into Linux from an HDD image. It also requires and uses Unreal Memory Mode [0][1] (vs. Real Mode or Protected Mode). It makes me wonder how compatible & stable this is wi
220.
by oso2k 6y ago
LOL. I don't think it's that serious. Maybe it's the Berenstain Bears Effect, Mandela Effect, Glitch in the Matrix, or ... a slight lack of your favorite morning pick me up. :D In any case, looking forward to reading the
221.
by oso2k 6y ago
You read me correctly. I did intend the politer version of TFA of RTFA ("Read/The Fine Article"). IMO, Robert does a great job of setting up Pratt Parsing and his intent to write a Pratt Parser Generator. As such, it is a
222.
by oso2k 6y ago
Hopefully Robert Jacobson sees this, but, the TFA uses the word "donation" when Pratt used "denotation." Just a couple small typos.
223.
by oso2k 6y ago
I think of writing Operators more as writing your own Device Driver but I can see the correlation you're trying to make.
224.
by oso2k 6y ago
I am reminded of the movie Pi [0]. [0] - https://en.wikipedia.org/wiki/Pi_(film)
225.
by oso2k 6y ago
tpxl gets me. :D Even the "scale atomically" part. People seem to have inferred that I believe that Limits are used by the Scheduler. I don't. But if we set "Request = Limits", we're guaranteeing to the Sch
226.
by oso2k 6y ago
DISCLAIMER: I work for Red Hat Consulting as an OpenShift/k8s consultant. This is such a bad idea. And I get that they're point is to reduce latency. But the point of k8s is describe your workload accurately and allow it to make
227.
by oso2k 6y ago
`JL` and other conditional jumps/branches are a common type of instruction [0][1][2]. Depending on the ISA [3][4][5], there can be jumps, branches, and subroutine transfers (or even a subset of those). Some can be based (conditional)
228.
by oso2k 6y ago
This is the C Standard specifying its VM to match the assumptions of a *nix environment. `main` isn't so special, IMO. Conformance to the C Standard is always optional, see C++, golang, Rust. However, conformance to ABI is less opti
229.
by oso2k 6y ago
Not true. The kernel & shell makes the values available on the stack and the runtime can choose to link to them or not. The ABI also details how and where the values should be placed.
230.
by oso2k 6y ago
Locating argc, argv, and envp on the stack is done by the runtime [0]. [0] https://github.com/lpsantil/rt0/blob/master/src/lib/00_start...
231.
by oso2k 6y ago
I just got some wood cut for another project last night. They're usually pretty good about accuracy, in my experience. I think it all depends on the HD or Lowes employee you get. But I was very happy with the 48" and 66" c
232.
by oso2k 6y ago
I miss things like Slashdot Ultramode. That was from the times before RSS and other syndication methods.
233.
by oso2k 6y ago
Usually it's one or more of several common factors: cost to make, cost to buy, cost to integrate, slower/inefficient performance, loss of compatibility, some unintended design defect, poor or over-ambitious marketing, or some assu
234.
by oso2k 6y ago
That's not what I remember. Wikipedia backs up that recollection as well [0], marking systemd's initial release in 2010. Docker's initial release is listed as 2013 [1]. Maybe that was true of the dotCloud internal releases
235.
by oso2k 6y ago
DISCLAIMER: I work for Red Hat Consulting as an OpenShift/Kubernetes consultant. You might want to try minikube [0], minishift [1], CDK [2] or CRC [3]. You'll want to have a machine with a bit of resources available. 2 cores+, 8
236.
by oso2k 6y ago
I've used Mural.co quite successfully as well. I think we probably bought an enterprise license. Collaborative, full-featured, almost as good as a whiteboard/butcher paper and a tall stack of stickie notes.
237.
by oso2k 6y ago
Good job! I'm going to throw some cycles at this, this holiday weekend. https://github.com/lpsantil/GW-BASIC
238.
by oso2k 6y ago
Mentioned it in another reply, you'd probably want to start with the MASM and LINK from the MS-DOS 2.0 release. https://github.com/microsoft/MS-DOS/tree/master/v2.0/bin
239.
by oso2k 6y ago
You could probably use MASM from the the DOS 2.0 release [0], build each ASM file as an OBJ, and finally LINK it all together [1]. [0] https://github.com/microsoft/MS-DOS/blob/master/v2.0/bin/MA
240.
by oso2k 6y ago
When you say, "there is no standard way to list out the available commands", do you mean like a `make help`? https://gist.github.com/prwhite/8168133#gistcomment-3114855

More ›