| Deutsch English Français Italiano |
|
<101n06i$20jc$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: The Natural Philosopher <tnp@invalid.invalid> Newsgroups: comp.os.linux.misc Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them Date: Tue, 3 Jun 2025 15:17:54 +0100 Organization: A little, after lunch Lines: 92 Message-ID: <101n06i$20jc$1@dont-email.me> References: <pan$4068a$3910f4f1$8cbecede$9e42905e@linux.rocks> <slrn1013t50.1aev.rotflol2@geidiprime.bvh> <vAGdnR-Fj9qGS4_1nZ2dnZfqn_udnZ2d@giganews.com> <slrn1016uic.2qk.rotflol2@geidiprime.bvh> <vv24n5$rjdd$1@dont-email.me> <jlchelx0p6.ln2@Telcontar.valinor> <vv67ul$hbt1$14@dont-email.me> <101gt61$1s439$2@dont-email.me> <101j4nq$2udcb$2@dont-email.me> <101jq1q$36qt0$1@dont-email.me> <101jur7$386sv$1@dont-email.me> <101mfd2$3tnqt$2@dont-email.me> <101mk3m$3uskc$3@dont-email.me> <101mngj$3vdni$2@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Tue, 03 Jun 2025 16:17:54 +0200 (CEST) Injection-Info: dont-email.me; posting-host="9af0f27d64947adc1eb442b37e0ce959"; logging-data="66156"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19Y1WYeTrBFAmfaqOpVjAgM/04XcUM4pfw=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:s4L/bf/UMk3UMI0tUNYCxPGBzz8= In-Reply-To: <101mngj$3vdni$2@dont-email.me> Content-Language: en-GB On 03/06/2025 12:49, Rich wrote: > The Natural Philosopher <tnp@invalid.invalid> wrote: >> On 03/06/2025 10:31, Nuno Silva wrote: >>> For terminals (the hardware devices, it seems we may need to get another >>> word for terminals, as it might otherwise be seen as nitpicking...), >>> another issue is likely to be that, even if it somehow can support utf8, >>> it might be limited in how much glyphs it can support at once. (I mean, >>> not by an incomplete font, but because it has a limit in how much glyphs >>> any font can have.) >>> >> Are any terminals still being made? > > Actual commercial ones -- doubtful. Unless there is some esoteric > maker supplying all the banks running COBOL mainframes with 3250 > clones. > Wasnt the whole point of the IBM PC to be able to do a 3270 etc at lower cost ? >> I mean if I wanted to do the VT220 or wyse 50 thing I'd get a raspberry >> PI and a LCD monitor and run linux on it and build one out of software. > > And further blurring the line between what is a hardware terminal vs. a > virtual terminal. > ' Well exactly. 'Glass teletypes' versus 'smart terminals' become 'PCs'... Names of things are only metadata ponting to the 'thing in itself'. So many arguments arise from people confusing descriptions with the things they describe. Read your Kant >> And absolutely use the full amount of ROM space to fill it with fonts. > > Indeed, a R-PI terminal could have a glyph for every unicode code point > that was defined as of the last time you did a software update on the > OS. > Lord knows how many fonts I have on this desktop. Once upon a time they chewed RAM and slowed things down. To the extent you needed font managers to enable a subset only for specific jobs. Now just load em up is spare gigabyte somewhere... >> Last time I saw a dedicated terminal in a bank, hooked up to some remote >> mainframe, it was a PC running some custom code, anyway. > > This has been the way for a very long time. The actual single function > "terminal" hardware is not likely a very sellable item anymore. > Probly would be if someone made an LCD style Wyse 50 or VT220 >>> There'll be terminals with at least some graphical capability, but >>> that's only usable if it's fast enough. >>> >>> I think mine supports changing fonts, but unless the customization is >>> done with a cartridge(?) on the back side, I suspect loading the >>> customization will not be very fast. >> >> It really is simply too obsolete for me. >> >> I replaced serial terminals with a plasma screen laptop running DOS back >> in the 90s sometime... >> >> Or winodows3 equipped with a emulator or telnet client > > In my case, never had one. "Terminal" access to whatever needed to see > a "terminal" on my end was always via a general purpose computer > running a software terminal emulator. Originally Qmodem and a dialup > modem to access the college computers, later Linux and Minicom or > telnet or ssh. You don't go back far enough...:-) Many a job was sat in front of a VT200 or wyse 50 connected via a serial line to a PDP or VAX or even a SCO Unix box. The cost of a SCO UNIX on a 386 with a multiport serial card and 50 Wyse terminals was unbelievably low. -- “There are two ways to be fooled. One is to believe what isn’t true; the other is to refuse to believe what is true.” —Soren Kierkegaard