The multipath daemon is for handling block devices (disks) with multiple connections and dynamically updating the geometry when errors occur. Not the sort of thing that you usually find in a workstation (or indeed most servers) and indeed it appears that I only have this installed because I started with the server install of Ubuntu.
It wasn’t causing any harm but it was annoying that it was spamming syslog log files, so I took a look at fixing it. Turns out it is rather easy. Just edit /etc/multipath.conf and add a “blacklist” section :-
blacklist {
devnode "^pktcdvd0"
}
The parameter to “devnode” is a regular expression but in this case we can get away with a “^” (meaning beginning of string) followed by the name of the device.
At this point, you could restart the daemon :-
systemctl restart multipathd.service
This shouldn’t cause any problems on most machines without multiple paths; and it probably won’t be a problem for servers which do have multiple paths. But in the later case, I’d test it or just go for a full reboot.
To be a nice person there are all sorts of things to avoid – racism, sexism, transphobism, ableism, and probably a whole lot more -isms. Which is really rather complicated but it can be boiled down to the very simple :-
Just don’t be an arsehole.
That’s it. No special magic, just treat everyone in the way you would like to be treated :-
Don’t stick your nose into other peoples’ private sex life; it’s none of your business.
If someone decides to transition their gender, don’t worry about it – just address them with their preferred pronoun and name, and job done. And whilst we’re about it (with particular reference to TERFs), don’t invent bullshit reasons to be an arsehole.
Colour is just skin-deep. It’s a spectacularly dumb reason to be labeled an arsehole.
Someone doesn’t share your religious belief? That’s their problem (or yours).
The list could go on and on.
But it can all be simplified – if someone isn’t directly causing harm to others, what they are up to is their business not yours. Just don’t be an arsehole.
Today if you are a Linux user and fire up a terminal window to “do something” at the command-line, you are using a gooey program to emulate an old terminal which was separate to the computer.
Today you are almost always using a keyboard and screen connected directly to the computer you are using and the gooey program you fire up as a terminal is in fact originally called a terminal emulator. That is, it pretends to be a real terminal.
So what were these real terminals?
The earliest “terminals” were actually teletypes for communicating text messages over long distances (over wires!). Not only was there no digital computer involved, but they predate computers by quite a way – the earliest ones were used in the late 19th century. And of course printed the text onto paper directly. The earliest digital computers used these teletypes as input and output devices, so you could type in commands and see the result immediately (or as quickly as the result could be produced). These early days still leave some traces today :-
✓ mike@Lime» tty
/dev/pts/5
The “tty” command commemorates those old printing terminals – the “tt” in “tty” is short for “teletype”.
The speed and wasted paper of those printing terminals was a bit tedious, so the 1970s saw them gradually replaced with glass teletypes – which were basically keyboards and CRT screens built into an enclosure that would attach to a central computer over a serial line.
binary comment
These terminals (and showing an ADM 3A here is a little unfair as it wasn’t quite this simple) were really simple – they had exactly the same capabilities as the printing terminals. No cursor control (meaning no full screen editing), plain text, no italics or bold, etc.
Over time, more and more features were added to the terminal allowing more usable software (in particular the learning curve was not quite as steep). These features grew to accommodate colour, graphics, the ability to load and save data locally, and even the ability to function as a microcomputer (the HP pictured below could run CP/M in certain configurations).
But where did they go?
The heyday of the terminal was in the 1980s when many office-based companies were busy trying to put something like a computer on every desk, and a terminal connected to a central computer was one way of doing that. But they compared rather poorly with microcomputers – typically very slow in comparison, less likely to offer any kind of graphics (graphics was an option but typically cost as much as a microcomputer), and just wasn’t very “cool”.
Despite several attempts at resurrecting them (they were popular amongst those who had to centrally support them), they never really returned.
But they do survive inside modern operating systems in terms of a terminal emulator (as mentioned previously) to access the operating system command line – all three main operating systems (Windows, macOS, and Linux) have a terminal emulator of sorts. And Microsoft is actually investing in re-engineering their terminal emulator.
This is related to the Scuntthorpe problem although it looks more at the meaning of a word rather than its appearance. This particular issue cropped up when a Facebook group I’m a member of briefly blew up (in a very English way) when Facebook prevented us mentioning that a particular shop was well known for its faggots.
But perhaps I should explain what I mean by faggots; the word itself has had plenty of meanings from bundles of wood (or any bundle) to a naughty child; in the case we’re talking about it is about a British meatball – the faggot.
Now this isn’t a “freedom of speech” thing – I’m not arguing those who denigrate homosexuals should get off scot free. But blindly banning the word “faggot” can have unintended consequences.
That posting on Facebook I mentioned? It went an interesting way – the blame wasn’t put on naïve censorship software but on political correctness itself. Whilst that was a mistake, there is now a few members of that group that will automatically respond badly whenever “political correctness” is mentioned and start talking about edible faggots.
When the blame is squarely with the censorship software that doesn’t take context into account – when you’re talking about “faggots and onions” or “a faggot shop”, you’re unlikely to be throwing rocks at homosexuals.
I use technologies like cookies to store and/or access device information. I do this to improve browsing experience and to show (non-) personalised ads. Consenting to these technologies will allow me to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.