But for example ^T (letter transpose) do not work on macOS Firefox, which I'm quite accustomed to use also. But ^T works fine same macOS Safari and Chromium.

Firefox apparently has its own input method which do not implement all what macOS supports.

*) https://cs.wellesley.edu/~cs249/Resources/ed_is_the_standard...

Yes, 34 years and no plans to switch.

Emacs cursor movement keystrokes are quite widely supported elsewhere too which use GNU readline or implement at least subset themselves.

Those work well also besides shells with Chromium/Chrome/Safari etc. many browsers input fields (address bar and text area). Cisco IOS, Juniper Junos, Netscreen load balancers too etc. IMHO makes jumping around CLI much much convenient and faster than moving hand to reach cursor keys.

My only gripe is that Firefox and its derivatives it doesn't work any more. Long time ago it did work. And I have no idea why feature was dropped some rewrite.

e: s/deadline/readline/g

IBM Memo, Novel Netware etc. groupware and such X.400 and routing those required also odd email conventions. VAX VMS addresses did have % left side routing in too.

But if used as a senders source address there are even less limits.

For example you can use a null address <> when sending. That has been used bit less these days than earlier. It's been used ages SMTP delivery status notifications, mail loop prevention and so where intentionally not much sense to expect anyone to reply. And all well known MTA's forward it and email clients handle it very well by disabling reply to that message.

There is however a catch that anyone who thinks he would now start using it when he doesn't want any reply. Ever since IT Service Management (ITSM) and Service Desk software appeared, they have had issues with email coming from <> sender, because they like to always add received messages email addresses to database, where then someone handling would reply. I've been using only few, Service Now (SN) more lately and before Issue Tracker (IT), both didn't at least about year and half ago know how to handle null sender addresses. Both seemed to just discard or sort some trash bin those emails. With our SN sysadmin didn't find where those went in that system.

But otherwise <> as a sender works great. And sure it would be great if those ITSM making folks would get this fixed, because when your postmaster, postmaster, etc. and such role-aliases are the quite often handled by ITSM software, there is good chance you don't get some important notifications from systems that rely on that null address sender.

ps. Search Google: smtp and sender address as "<>" for more info incase needed.

Either because did not care or understand 32bit VFAT while it works for while, then when CF usage gets over VFAT16 supported 2GB fs gets corrupted, system fails after a while and then you got plenty of those FOUND.xxx files root of that CF drive after boot ran fsck. Those old ASA's did accept and work with 4GB CF's which were available much longer than 2GB versions, but you needed to make max 2GB VFAT16 primary partition and then format it with Linux mkfs.vfat with flags that made sure it's only 16bit version. Once that was done, you could copy files from old CF using something that copies also hidden files and directories too, which there were few there.

ASA used to be some Cisco proprietary OS and was just rebranded PIX firewall, then from 8 oddly hacked linux with grub boot.

Not much of my favourite box as a firewall, but Remote-access VPN features did work quite well quite long and when clustered it was easy to run upgrades each node at time without DTLS and IPsec clients even noticing it.

  "134 UNIX System Administration Handbook
  ...
  The lost+found directory is automatically created when you build a filesystem. It is 
  used by fsck in emergencies; do not delete it. The lost+found directory has some
  extra space prealocated so that fsck can store "unlinked" files there without having
  to allocate additional directory entries on an unstable filesystem. Some systems pro-
  vide mklost+found command that can recreate this special directory if it is aci- 
  dentally deleted.
  ...
  "

  "52 UNIX FOR SUPER-USERS
  ...
  The filestore consistency check is performed by the command fsck (usu-
  ally stored as /etc/fsck, but sometimes in /bin), which should be used to check
  all discs used as file-systems. It defaults to the list of filestore devices given
  in the file /etc/checklist. At this stage, most of the file-systems will not be
  mounted, so will be inactive; only the root file-system will be active. The
  fsck command goes through each one in turn, reports any inconsistencies in
  them, and offers to correct them. The reply to each query is either 'y' for yes
  (correct the inconsistency), or 'n' for no (leave the file-system inconsistent).
  A parameter '-y' to the command assumes 'yes' replies to all questions, so
  that no further interaction is necessary; a parameter '-n' similarly assumes
  all 'no' answers, and therefore needs no write permission to the device. Any
  'yes' reply may involve the loss of information, such as the complete removal
  of a suspect file. Suspect files on the file-system being checked are written to
  a directory lost + found on the device if such a directory exists; this directory
  must have been created, and be sufficiently large already to hold the names
  of all the files involved. This can be ensured by first creating the directory,
  then creating a number of files in the directory, and then removing them.
  The corrected systems will be consistent, and can later be mounted as and
  when required. It may be possible to recover information from deleted files
  by looking at the lost + found directory. There should be a lost + found direc-
  tory at the head of each mountable file-system.
  When checking the root file-system, there are complications, in that it
  will be active (even though, because it is root, it will not be formally mounted
  as such, but is implicitly mounted as root during the booting process). If
  modifications are necessary, they should be completed, and the machine
  rebooted without first performing a sync (see section 4.5 below for the nor-
  mal procedure for taking a system down). This is to ensure that the disc as
  modified by fsck is not overwritten by any in-core information, which may
  have been generated from information read from the original corrupt (incon-
  sistent) version.
  ...
  "

Old time UNIX systems directories were just another structured file, which a 'd' bit (like others you changed with chmod) on them, where each record was 16 bytes, which 2 first were the inode number followed by 14 bytes reserved for filename. IIRC linux also had first same limit first filesystems. You could read directory with any program, common feat was to check any odd stuff that "ls" would not show with could hexdump or "od" with some flags and print 16 bytes lines per row. That way you also could see any deleted or moved files from that directory, because directory entry was not quite long otherwise cleared but just clearing that inode reference two bytes.

A Quick look from other books that I have close me now Maurice J. Bach, The Design of Operating UNIX System (-86) contains much more about fsck and filesystem fixing issues scattered few pages in the book and what methods were used to mitigate loss of data. S.R Bourne The Unix System, no mention of fsck at all, at least by looking book automatically generated index.

It could have been some other quite old book I did read, but did not own or anything since BSD4.3-tahoe documentation I've read over the years. But sure it would be nice to read that exact reasoning again from credible sources.

edit: Oh, and you could preallocate also just by adding entries or copying some data to lost+found enough, and then remove entries. Unix traditionally have not compacted and resized directories. They only grow and can be if have been very large slow to traverse. The way to compact is creating another, moving existing data there and then swapping directories.

Gosh, but there are other ways to solve that issue like having bit more of fav clothes, so that you dont' have to wash same cloth every day but instead was a bunch of them end of week. Need white shirt every day at work, buy at least 10 of them, use one each day, wash & iron weekend, put on pile1 and use from pile2 next week rotating for even use and to have some redundancy, then pile1 week and so on. Get more trousers etc. whatever you need. This is what I did when had job where dress code told what to wear in office.

And kids, buy them more fav clothes too if it otherwise becomes fight what they want to wear daily.

But each to their own. Above is just my view and how I learned when I was kid looking my parents, and how I've done also.

All parts still available and when I bought new hose few years ago from service I asked if they still are willing to fix it if it went broke answer was. Sure absolutely, just bring it here and we make it work again. I've just bought once new floor nozzle that was worn out and that hose because it grew leaky from ends. Third party dust bags are available and very cheap.

But it's when you consider taking first full drive backup times. It still takes 'forever' when you'd rather like to get on with fixing single disk issues. Or like when you wait RAID rebuilds too.

We did plan our maintenance tasks so, that there was something else useful we could do while obligatory backup and Spinrite was running. Upgraded another devices EPROM's, PC BIOS or dot matrix printer EPROM, cleaned printer heads, chaff and dust from chassis, changed colour ribbon to it. Ran updates to software we had sold etc. And went lunch with the customer:)

And I've had both multiple accounts various servers both private and work. And dozens of work-related role aliases which Mail.app correctly always used when replying. No problems there. Neither I have had to rebuild sqlite mail folder db, but did have some quirks first when work emails were transferred to Office365 which wanted to rename folders etc. nuisance, 2FA worked also worked fine since IIRC Mojave. I've had some addons MacGPG, sorting and maintenance scripts too. MacGPG does need some attention when upgrading though besides paying for subscription it moved time ago.

I've used also Thunderbird, mostly with linux. And used and tested whole lot of various clients since Elm was a thing -80's, then Pine, mutt etc.

The macOS Mail.app is fast reliable in my opinion, but sure there are things in its UX it could be yet improved. But still it's been long time among best and never broken or let me down over 20 years, both work and private use.

I had AEG Lavamat 1055 about 35 years (from 1982), worked well without hitch. It was quite small, top loading model etc. Fast spin-dry w/ variomatic (shaking also while spinning). Laundry out of it was quite dry already.

Then 2017 building plumbing had to be redone and gave reason to remake bathroom completely and replacing old equipment. I would have bought Miele model but it didn't fit reserved place and I ended up buying Electrolux instead.

That's now month short of 9 years and I have no reason to believe it will not work well at least another 10 years to come. regardless advertised 10 years warranty.

This current one has more electronic parts, but now searching by its model found only fault codes all seem to be user errors, overfilling, water hose not open, draining filter clogged etc. All non issues whoever bothers knowing how to maintain and operate that thing over years. No complaints about issues with electronics problems.

These were first used by a couple and later single (me) needs which are usually once a week plus twice a month washing 4-5 uses single day. Which becomes bit over 100 washing in year.

That's just 1000 washings in 10 years and 3500 in 35 years. For a family washing every day once it would be 3563 uses in 10 years.

If washing machine isn't badly kept against instructions and it isn't cheapest knock off plastic rubish, why would be a surprise if it doesn't last at least that 10 years use washing family laundry. And last many decades with single or dink use?

Then even after std lowlevel it was worth using Spinrite to check if interleave value was proper. And if it wasn't it was worth letting it first before anything else. Same when changing a faster CPU as it could speed up IO so much that no interleave would not needed any more and get faster IO.

Spinrite was such a great tool and time saver fixing or making preventive periodic maintenance to customers disks, even though it chugged hours even 30M disks. And just because not to take absolutely any risk it was necessary to make full backup first, which that took quote long also. LapLink was a great tool for that, before LAN became more common.

Knowing you way around *BSD how check things, mount a USD drive, collect data & or evidence when need arises is well worth having beyond just surviving bare Linux skills. BSD's are alive and kicking on commercial appliances and devices.

You can build that way cheaper with 2-3 proper clustered load balancer units, 2-3 application servers behind those and those using persistent storage (databases,ldap, files) which allow writing multiple nodes simultaneously.

I used to work uni that we had few services from 2012 to 2025 my retirement with zero downtime. One time my manager with tech background tried to add PBR in hurry using WebUI and did not understand cli syntax and caused close to require reboot, but I was able to fix it from cli rolling back previous config and rebooting one unit at time. Upgrading software major version up to each unit supported level wasn't hard, upgrade node it joins back cluster, upgrade another node and it joins cluster, all done. Few times I had to fix manually config for some less important test backend servers that I had forgotten to change before upgrade. No big deal. No major outages during all that 13 years time happened. Some redirecting policy and action syntax was first hard to understand and learn like GeoIP, but I was very surprised how darn reliable and nice they to use and maintain.

The LB's were (Citrix) Netscalers in clustering mode (all nodes process traffic concurrently), which allowed live update one node at time without losing any connectivity through them. That wouldn't have been possible devices in just HA mode.

We had just 2 beefy units which worked very well for us, but you can have 2-32 of them in cluster and managing thousands of servers behind them if you need that. Netscalers are FreeBSD derived where quite a bit of the TCP/IP stack was rewritten adding support many some quite odd features std FreeBSD doesn't have. Much of that is IP/ethernet multicast features, PBR's, Traffic Domains (VRF's) and of many service and monitoring processes which sync cluster (or HA) and if node fails another can continue straight from there without any loss of traffic to clients being proxied.

Though I think most people in this forum are familiar with with haproxy, pound and web-server software provided reverse proxying.

A car analogy if previous were your fancy sport sedan Netscaler and F5 BigIP are formula F1 class cars ie. quite different beasts altogether.

e: And proper LB's are not just for HTTPS etc. but very nice proxying many other protocols were they TCP, UDP or something else. We did done VPN's and something like Cisco AP'S CAPWAP (DTLS ie SSL over UDP). e: typo.