Teknikal_Domain

Software developer, Linux sysadmin, amateur analog photographer.

(And pointy cheese monster)

I may write in English, German, or Russian, but make no mistake: my mother tongue is Sarcasm.

Public Key

npub1nray8pxrwrrpv5yljpyjj4r6cmp4pcqwqhrrc7kuw8dtvqdaekrsnezxf2

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsf37jrsnphp3sk2z0eqjff23avds6suq8qt33u0tw8rk4kqx7umpcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsus4hlk

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1nray8pxrwrrpv5yljpyjj4r6cmp4pcqwqhrrc7kuw8dtvqdaekrsnezxf2

Show more details

Last Notes

2024-08-02 06:53:13

Hey #linux people, weird question:
How much would I subtly break my system by having one Arch based distro and one Debian based distro both sharing a common /home partition? :taz_laugh:

2024-08-02 00:28:42

- reply

@npub1l3g…vu48 There is no "a" on the end of that word, so help me god do not let my eyesight fail.
(too late, it took me reading it 4 times)

2024-05-30 00:01:06

- reply

@npub1l3g…vu48 do I have one? No. Am I capable of setting up a VPS for you? Absolutely. 32 GB disk, two core, 4 GB RAM sound fine?

2024-03-02 23:08:30

- reply

@npub1l3g…vu48 TL;DR it's the exact branch path.
Your first commit is 1.1 then 1.2, then 1.3, the. 1.4. let's assume now you branch off a different line of changes. That branch is named 1.4.1, and the first commit is 1.4.1.1. the. 1.4.1.2. the. 1.4.1.3. if you made a second branch off 1.4, that's 1.4.2.1. if you branched off 1.4.1.3, that's 1.4.3.1.1.
An odd number of numbers is a branch name. An even number of numbers (x).y is commit number y on branch x.
I hate it.

2024-03-02 20:53:13

- reply

@npub1l3g…vu48 svn's revision ID is a monotonically increasing int. The first checkin is rev0. After that, rev1. rev2, rev3, and so on.
Unlike how Git used hashes (an idea taken from Monotone), or CVS does... 1.4.1.3.2.1.5.29.2

2024-03-02 17:52:45

- reply

@npub1l3g…vu48 subversion be like

2023-12-12 03:59:10

Okay, #AmateurRadio math time.
Anyone know roughly how far a UHF (440) signal can travel, 40W of power, end-fed half-wave vertical mounted above the metal roof of a 1-story house? We're on the city limits so there's not much obstruction.
I'm not looking for exact answers, I'm just trying to calculate if 40-50 watts of power is enough to reach the neighboring (30 miles) city.
For bonus points: assume I'm on a 5W HT. You think there's enough rx gain to even hear an HT 30 miles away? Or would I have to bounce through the 50W tx in my car as an amplifier to even try that.
#HamRadio

2023-08-07 05:31:33

- reply

@npub1l3g…vu48 It's a nice idea but it's good to have concrete values on something, like the original geek code, instead of you having to estimate percentages. I could say "g4 b0 u5 a4 s1 r2 n1" but that's also subjective enough as an opinion to not really convey the exact same meanings that I might intend.
#LinuxGeekCode, neat concept, just maybe a touch vague? I don't know, I'm just like, a single opinion here.

2023-08-07 03:51:15

- reply

@npub1trd…ussx @npub1l3g…vu48 Exactly.
BSD has had this concept for longer than Linux has. Take a process, or processes, and the isolate them from the rest of the processes on the system... That's it

2023-08-06 22:46:29

- reply

@npub1l3g…vu48
This is why stacks and docker-compose exist. You give it a YAML file detailing what containers, what images, what networking, what <everything> configuration, and tell it to start that, and it handles organizing the containers for you.. and if you set it up right, I think that even has some scalability too.
But this is why I say a Docker container is not a VM-lite, it's an app in a sandbox. Compared to what I'm normally using, LXC containers, which *are* meant to act as a full Linux system, Docker containers are meant to just draw boundaries around a single process in regards to it's filesystem access, environment, and maybe memory and CPU.
@npub1trd…ussx

2023-08-06 17:35:12

- reply

@npub1trd…ussx @npub1l3g…vu48 Personally I think FlatPak makes more sense, I don't think AppImage has the same sort of sandboxing which is the entire point of containers.
Unfortunately this comparison breaks down when you consider that Docker expects a sort of one-container-per-app topology, using stacks to link everything up. So a single application can be made of half a dozen containers, one for the app, one for the database, one for the frontend... All communicating on a loopback bridge network together. Updating these can be fun sometimes.
Also your understanding is good but misses some details, Docker (and the ContainerD runtime and system it uses) is doing basically all the work, the OS isn't doing anything besides cgroup separation. (And don't get me started on how Docker does storage and filesystems)

2023-08-06 09:08:40

- reply

@npub1l3g…vu48
To add, and address a separate point:
you're trusting them to not only update their app in the container image, but every underlying utility and library used.
Most projects that I can think of, building container images usually is part of the CI/CD pipeline, and those images usually start their build with a number of apt / dnf / yum / apk / pkg / etc. invocations to pull the libs, meaning that every application update is, within a day or two, an image update, and usually a library update since it's in effect firing up a very lightweight VM, running a bunch of package installations, and then copying its own files in.
Some places even build the app in the container with the libraries to make sure it's all set up correctly for the environment, and then have a second build stage, so you're not holding all the build-time dev dependencies that it needs, but that's getting a bit besides the point.
@npub1trd…ussx

2023-08-06 09:04:57

- reply

@npub1l3g…vu48
Like, okay, you *can* (and usually do) build a Docker image from some base OS, but that's really only just to give your program the support it needs to exist. A Docker container is not, fundamentally, supposed to be a VM. It's an application running in a sandbox. There is no real OS around it, besides the libraries and support files it would need to run. There are no processes besides whatever is in the CMD line when building the image + whatever else that starts up.
This removes like 90% of the OS from the OS, and not many OS updates are going to really have any effect besides major version changes or urgent fixes.
(And even for urgent fixes, you *can* modify and rebuild the image yourself just by changing the FROM line)
@npub1trd…ussx

2023-08-06 02:14:52

- reply

@npub1l3g…vu48
> Even then, how much behind regular OS updates will the software contained in the image be
Standard Docker, basically irrelevant most of the time
@npub1trd…ussx

2023-08-05 04:26:59

- reply

@npub1l3g…vu48 I mean it's not *that* bad if you have some experience. Then again, that's why VPS providers exist.
Most of my experience is in self-hostable though, I'm not one to trust data like my finances to some other company or provider that could go bankrupt overnight (ironic I know)

2023-08-05 04:09:42

- reply

@npub1l3g…vu48 I wonder if anything in the awesome selfhosted list works?
I assume you already checked though.

2023-08-05 04:00:02

- reply

@npub1l3g…vu48 Like 99% of that could be Firefly III (https://www.firefly-iii.org), self-hosted, web-based, complete with mobile app on F-Droid, just no auto reconcilliation and check printing.
Let me poke around.

2023-07-31 17:24:19

- reply

@npub1l3g…vu48 8 hours left. 6 of those are going to be sleep.
Let's see if I've retained everything

2023-07-31 02:58:00

- reply

@npub1l3g…vu48 I'm already routinely getting 47/50. Exam in 23 hours.

2023-07-30 13:29:02

- reply

@npub1l3g…vu48 No, I requested it literally the day I got my Tech license.
That's why I want to do this, because that means I'll have Extra within 18 days of getting Tech.

2023-07-30 07:03:26

- reply

@npub1l3g…vu48 I did/will do each one at a time, Tech two weeks ago, General a week ago, Extra next Monday... Meaning I've only had like a week of study time for each
Kinda hoping I'll get Extra before the FCC even officially activates my vanity call, hah.

2023-07-30 05:52:02

- reply

@npub1l3g…vu48 I mean you may be correct here. But my initial assertion of "it's digital lol" seems to be provable on paper the more I think about it.
I don't know if this conversation is proof that I need to get my extra or proof that I need to be barred from ever taking that exam 😆

2023-07-30 05:41:06

- reply

@npub1l3g…vu48 I was thinking you'd need either quaternary, or pairing up bits to symbols, but no.
The carrier is a binary on or off. We don't care about it's level. We care solely about it's timing. Therefore the only information you need is "was the carrier present at this time" because if you have enough timing samples you can decode the pattern. So no it could be a flat bitstream. You sample at a constant rate, outputting a 1 for carrier presence and 0 for carrier absence. As long as the sending WPM isn't too high for your sample rate, Morse is encodable as a binary stream.

2023-07-30 05:37:59

- reply

@npub1l3g…vu48 as a pure bitstream you'd... Wait.
As a pure bitstream you just represent carrier presence with the bits sampled at a constant rate.
0000001110000111000011110000000000011111111000111111111001111111110000000000111110000111100001111000000000000
With a little fuzzy logic you could decode that into a symbol stream.

2023-07-30 05:31:29

- reply

@npub1l3g…vu48 4 symbols can be represented with just one bit. If you count dit-spacw and dah-space as framing (which they basically are), you can use the timing of NO-CARRIER to differentiate one or the other, meaning they're bitless symbols that only exist in timing information.
It's not something you could serialize into a bitstream and write on paper because the timing is important here, whereas for most binary / digital encoding and transfer schemes it isn't besides knowing when to sample for a good read.

2023-07-30 05:12:07

Morse is just variable length digital using pulse width instead of pulse level to code for logic high or logic low
Here, I thought it, you suffer it.
CC: @npub1l3g…vu48