Create accountLogin

Recent searches

No recent searches

Search options

Not available on lingo.lol.
lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Administered by:

Server stats:

70
active users

lingo.lol: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#patch

1 post1 participant0 posts today
Public
napierge

Did you see anytime different patch number when you run uname -a or freebsd-version?

It is not wrong because not all patches are applied to kernel or to userland. uname shows kernel patch.

check results of commands below:
$ freebsd-version -r (for kernel patch number)

$ freebsd-version -u (for userland patch number)

Honestly little bit confusing, but maybe because I do not understand details.

#freebsd#patch#versions
Public *
Dendrobatus Azureus

In this post Stephan teaches you why he moves many of his servers from Linux to freeBSD.

Here is some background History of Mine:

Because I have been using Linux ever since the pre-alpha days, I know many things about the operating system that most other users do not. There was no other way to install the operating system in the beginning, than to compile the kernel on another operating system, to hex edit a boot sector, then boot to see if your kernel would actually properly spawn on your machine. In the beginning the hex editing was done on the floppy disk you could not boot from the hard drive.

From that point, you had to go back to the foreign operating system, compile the rest that you needed for minimum functionality, then put them in a convoluted manner on the file system which was then Minix.
It was normal in that period where you first installed Linux to do not just everything yourself, but to know what to do otherwise you would never get the functioning operating system.
In the end you would also compile GCC in that foreign operating system, because there was no way for you to do it in Linux with a compiler you did not have yet {chicken egg dilemma}
Only after GCC was compiled, were you able to do Native compiling in Linux on the Minix file system.

It is exactly this manner of thinking, that is still bothering Linux distributions today. Somewhere there are people who still think, that there are many users who want to Tinker with the operating system, when they just want to go from one major version to the next.

This manner of thinking breaks things when you need to upgrade from minor to Major version.

One thing that has always bothered me, is that a simple major update from the operating system from one person to the next can **still*" literally break things in unexpected ways, because of the way that Upstream handles certain commands.
For no good reasons commands like ifconfig where depreciated, the other example's also like arp.

Ifconfig has been in Unix Forever.

Ifconfig is in muscle memory of hundreds of thousands of system operators. Ifconfig is a specialized command which does only one thing and it does it in a perfect manner and it has been doing it ever since UNIX existed.
It's still baffles me that I need to separately install the ifcommands, before I can work on a Linux system today, and that's with any any distribution

This is just one of the examples of why it is wrong to change commands on the fly, depreciating another set of commands, without giving the people the choice, at the beginning, to include it with the installation of the distribution

The IP Command is a good one, nice modern with colour output, ifconfig is still a very good command, nice, **stable** decades old, leave it be!

These are the major things, that often bring system operators to seek operating systems, where stability is first, where updates from minor to minor version go smoothly, and updates from minor to Major versions usually also go smoothly and where don't disappear 🫥 or are depreciated for trivial reasons.

/1

#bash #sh #zsh #ksh #csh #tsh #freeBSD #100DaysOfCode #1000DaysOfCode #POSIX #Programming #Patch #RetroComputing #UNIX #History

it-notes.dragas.net/2022/01/24

image is a webpage or blog post titled "IT Notes" with the heading "Why We're Migrating (Many Of) Our Servers From Linux to FreeBSD". It is written by Stefano Marinelli. Below the author's name are several tags including FreeBSD, Linux, Filesystems, Hosting, Jail, Lxc, Server, Snapshots, Zfs, Btrfs, Container, Alpine, Ownyourdata, and Series. The article was published on 24-01-2022 and updated on 17-10-2024. It is about 1900 words and a 9-minute read. The main image is of a chessboard with a white king being placed to capture the black king. Below the image is a button labeled "CONTENTS". Below that text that says "More about this in the article I wrote to accompany my talk at EuroBSDCon 2024".
Continued thread
Public *
Dendrobatus Azureus

This is the other end of the XLR cable pulled, out of the instrument mixer, where it's normally plugged into Channel two.
Of course since a bass guitar is a mono single channel instrument, I only use one channel if I had used a dual Channel effect somewhere in the effect chain, usually at the end, I would have two of these patch cables getting out of that effect, and getting into both ports of Channel two of the instrument mixer

A gold-colored 1/4 inch audio cable plug rests on a black box. The box is labeled "Eurorack Professional Multi-Purpose 16 Input Ultra-Low Noise Line Mixer".  The text is white and is partially visible.
#Soldering#XLR#patch
Public *
Dendrobatus Azureus

Today I decided to create another patch cable, within my long line of patch cables, important for sending signals from effects, whether they be discrete analog effects, or effects which process the signal digitally, then spit them back out in an analog wave.

It was important to make this cable because I was using an expensive higher grade cable which I need somewhere else. The cable that I used is a standard XLR cable which has ground signal 1 and signal 2. You can go read on Wikipedia why XLR needs that in detail, but it has to do with the length of an XLR cable which can go to 30 m if you need it.

The signal that I need to carry only needs an unstable connection which means a signal and a ground. My XLR cable is een overkill but I don't have any other cable.

Enthusiastically I warmed up my trusted Weller soldering iron, waited till it heated up, took my fantastic cable stripper stripped the cable on both ends, prepared the connectors beforehand and started soldering.

Everything went smoothly I've been soldering since I'm a 7 year old kid. Of course quality control is important so my multimeter was tuned on diode.

For the uninformed, a diode is a electrical component which only lets current on one side, and then blocks it from the other side. This setting is also used to check the connections & continuity in cables and on ports.

When I was done something strange occurred. I measured the cable and the mass, the common was open. Checking both sides of the soldering work showed it was perfect. Not believing that there could be disruption in the cable, I stripped one side then measured the cable and came to the same conclusion broken Mass. I caught and stripped another small section of the cable at the other side and still an open Mass.

So I've had a piece of XLR cable, that didn't ground and I had used that as a stable cable, which had given me all kinds of interesting artifacts, that I alleviated by just stripping out that one piece of cable, years ago.

Now a regular person would take that cable and chunk it on the side. I on the other hand I'm not a regular person, I started stripping / dismantling radios when I was two and when I was five I had such a skill that it looked like a trained electronic professional had stripped the radio. Are we talking about radios in the Tube era, where hundreds & hundreds of Volts and many Ampères were going through those circuits.

XLR cable has three conductors; signal one, signal two and ground. I used the white conductor as the new Mass, the new ground and used the red conductor as a signal two, thus making a balanced XLR cable unbalanced because the ground conductor was broken.

It was a wonderful trip, taking this piece of XLR cable and reusing it again even though only two conductors were usable effectively.

I may provide photographs later.

#Soldering#XLR#patch
Public
ken Tucky Swinson

For #patchTuesday I took my latest #owl patch and sewed it onto my hat!

This old hat has been my biggest challenge so far: curved, and rigid material.

Even with it's #sewing flaws, I love using #printmaking to give new life to an old hat-and the hand stitching is a cool way to show off my #art

These are a limited edition of 12-available on my website while they last!
Happy patch tuesday!

ken wearing a hat. he is pointing at a roughly stitched hand printed linocut patch which depicts an owl flying over a house.
#visibleMending#handmade#mastoArt
ExploreLive feeds
About