JdeBP

161 ms·

1891.
by JdeBP 7y ago
One can learn a modicum about the differences among lbin, mbin, rbin, bin, 5bin, sbin, amdahl/bin, ucb, sun/bin, ccs/bin, local/bin, xpg4/bin, xpg6/bin, and some others at https://unix.stackexchange.
1892.
by JdeBP 7y ago
See https://utcc.utoronto.ca/~cks/space/blog/unix/DisklessUnixAn... and the comment by Greg A. Woods.
1893.
by JdeBP 7y ago
Did Apple marketing do that for the Escape key, too?
1894.
by JdeBP 7y ago
You saw it at https://news.ycombinator.com/item?id=21523873 , no doubt. (-:
1895.
by JdeBP 7y ago
Actually, I'm the one using the specific terminology (from Win32) here. A console is a specific I/O abstraction, widely known as such. Whereas "I'd claim that a terminal system plus ncurses is a console" is your o
1896.
by JdeBP 7y ago
You've got it backwards. This is the reality where UNIX (et al.) terminals were reinvented, throughout the 1980s as I said. This is the real problem, people going around talking of making a "better terminal", and when pre
1897.
by JdeBP 7y ago
If you actually read the whole discussion to this point, you'll see that the discussion started with being constrained to the models of teleprinters, not text processing.
1898.
by JdeBP 7y ago
It behooves one not to make egregious mistakes when talking about the mistakes supposedly made by Windows. cmd.exe is not a terminal emulator at all, and does not make DOS system calls (it being a Win32 program) at all. * http:/&#x2F
1899.
by JdeBP 7y ago
Enjoy some more manual pages in the same vein: * http://jdebp.uk./Softwares/nosh/guide/commands/monitored-fsc... * http://jdebp.uk./Softwares/nosh/guide/commands/monit
1900.
by JdeBP 7y ago
systemd-fsck, as the article outright told you, already starts it with -C .
1901.
by JdeBP 7y ago
Better to remember pgrep, instead of an incremental change that you'll find still has problem cases (such as matching usernames). * http://mywiki.wooledge.org/ProcessManagement#But_I.27m_on_so... M. Wooledge's des
1902.
by JdeBP 7y ago
There have been attempts to do so over the years. https://lkml.org/lkml/2019/6/5/174 was one. I haven't looked to see what became of them.
1903.
by JdeBP 7y ago
It doesn't really support all of the basics as exemplified in https://github.com/jdebp/terminal-tests/blob/master/PowerShe... and https://github.com/jdebp/terminal-tests/bl
1904.
by JdeBP 7y ago
Read https://news.ycombinator.com/item?id=17238350 and https://news.ycombinator.com/item?id=22603878 in this very discussion.
1905.
by JdeBP 7y ago
We do know why, now. The article has been updated. It was nothing to do with government sanctions, it turns out.
1906.
by JdeBP 7y ago
The other half is now in the updated article. It was nothing to do with Crimea, it transpires.
1907.
by JdeBP 7y ago
... and pretty much all of those were addressed, outwith Unix, by the evolution of the 1960s terminal I/O model into the console I/O model during the 1980s. You even forgot to mention one of the things that was addressed: input.
1908.
by JdeBP 7y ago
I suggest learning from history. The doing better has already happened. The 1960s terminal I/O model evolved into the console I/O model during the 1980s; from firmware-mediated access to CGA, through the VIO+KBD+MOU subsystems o
1909.
by JdeBP 7y ago
I didn't include it because in my experience people don't overlook seq, whereas they do overlook jot. I only included things where I've encountered people overlooking such tools and doing things the hard way.
1910.
by JdeBP 7y ago
There's also the likes of console-flat-table-viewer . One would have to convert the comma-separated stuff into one of the table types, but that's what Miller is for. (-: * http://jdebp.uk./Softwares/nosh&#x2
1911.
by JdeBP 7y ago
See https://unix.stackexchange.com/a/65819/5132 for some thinking on making every individual program have an escape sequence parser, and why that syntax is not specific nor original to the Bourne Again shell.
1912.
by JdeBP 7y ago
I would guess, from experience of people doing things the hard way, at: * John A. Kunze's jot and rs * John Kerl's mlr ("Miller") * jq * join and comm, as mentioned * fmt * ex And, given what you just wrote: * printf
1913.
by JdeBP 7y ago
MetaWare was producing a C/C++ compiler that did much the same thing, in the 1980s.
1914.
by JdeBP 7y ago
One thing not addressed in other comments: Please do not write logs to standard output, as implied by this article. Write them to standard error. In C++, one even has an explicit std::clog stream. Of the service management frameworks tha
1915.
by JdeBP 7y ago
You are not thinking about it clearly. Ask yourself this: Filesystem formats use blocking and deblocking. How would a filesystem know the file size without having metadata for it?
1916.
by JdeBP 7y ago
Xe is conflating compilers and calling conventions a bit. The way that structure types are returned varies by calling convention, as indeed do a lot of other things. Mismatched calling conventions leads to problems. But structure type r
1917.
by JdeBP 7y ago
You should stop reading this discussion here, for your own peace of mind. Because there's someone writing quotation marks and then immediately writing "quote-unquote" only a few bullet points ahead. (-:
1918.
by JdeBP 7y ago
Look at it another way: a centuries-old mistranslation is finally being fixed. (-:
1919.
by JdeBP 7y ago
Other interesting reading matter: * Ethical and Legal Considerations in Mitigating Pandemic Disease: Workshop Summary . National Academies Press. 2007. ISBN 9780309107693. https://www.ncbi.nlm.nih.gov/books/NBK54167&#x
1920.
Destroyer and Teacher: Managing the Masses During 1918–1919 Influenza Pandemic(ncbi.nlm.nih.gov)
3 points by JdeBP 7y ago|1 comments

More ›