I took an operating system class in college that involved basicly creating a baby OS. Lot of fun.
That’s me, who started using Linux 5 months ago. I’m like, “I use Linux btw” to everyone.
Who cares, be loud and proud about it.
Personally I’m just going to ramp up being annoying to my friends until they switch because they’ll thank me in a couple years and also because they deserve it
This is the way.
“It’s called a shovel,” said the Senior Wrangler. “I’ve seen the gardeners use them. You stick the sharp end in the ground. Then it gets a bit technical.”
—Terry Pratchett: Reaper ManIt’s a series of files (tubes)!
And files that can be deleted while even in use just because.
Why would a file not be deletable while in use?
Well. ACTUALLY, it’s very simple you see every time you spin up a new linux box a little piece of Linus Torvold’s soul get’s imprinted in the CPU registers and then that fragment handles everything from there.
I creating my Meshtastic network and was having trouble setting a node with the right settings and wanted to plug in the unit into my Lenovo laptop running Fedora installed from the factory.
I click serial connection. The web app recognized the connection. Click connect. Failed. Tried different plugs and ports. Failed. Searched online and I need to do a bunch of things in terminal to get it to work properly.
Normally I would spend a few hours figuring it out. Instead…
Pulled out my 15 year old PC running win10. Plugged in, instantly worked.
I reeeeally want this to be my primary laptop, but man. I am just struggling on some basic things.
it will never be your main mschine of you don’t use it as your main machine.
If it can’t do everything your main machine needs to do, it can’t possibly become your main machine.
But it CAN do it, it just needs a bit of work, be it by yourself oor by someone on the devs’ side
Counter argument. What is the goal of owning a computer in the first place? Needing to do “a bit of work” with the OS or actual work.
I don’t want to be a Linux developer. I want to do work. Sometimes I feel like I’m too much developer.
If you get Microsoft office to install and function, let me know how you did
Ah, permissions chicanery. Had to deal with that with connecting a Switch 2 controller with a WebUSB enabler. To be fair, once you add the right udev rules (it is a bit of a pain, yes), it should work for any other devices of the same type (I think it’s any with the same USB ID so like same manufacturer and model? Don’t quote me on that though). Still, I wish Chromium (since Firefox as far as I know still doesn’t support WebUSB) could sort it out by itself (like just have an “allow” button rather than writing udev config files yourself) or at least be a bit more helpful in pointing you the right way with a helpful error message.
You do have to get used to weird edge cases like these throwing a spanner in the works, just like you have weird stuff on Windows (trying to get some older Android devices to communicate in fastboot mode in Windows makes me feel like Odysseus).
Asking around and screwing around usually gets you places though. Eventually you find something.
My PC just programmed all the units in my mesh in around 5 minutes. It would have likely taken longer trying to fix the USB connector. I should figure out how to fix this edge case so I don’t have to take my old PC out again.
udev? WATCH -N 1 CHMOD A+RWX /DEV
deleted by creator
What they are talking about is an open source piece of software (Meshtastic) that’s using a well-known (if specific to Chromium) standard, WebUSB. It’s a genuine pain point, and stuff like this needs to work out of the box, no manually written udev rules required.
Whoa man. You ok?
Fresh knowledge is not to be underestimated.
On a client-server model turned single-user desktop, running on seven layers of abstraction. And the interface of choice is full of bugs and limitations. But we’ve got nothing better currently, that also works on the next computer, due to compatibility issues caused by misplaced secretivity of the vendors.
Compooter take symbol, compooter fuck symbol, symbol reincarnarnates as a stick, which is what is currently in my ass. Sideways, even. Symbols don’t fuck around here for longer than it takes to be forthsworn, but this just a warning to warm you up, and this is how we know these compooters work.
It’s just files, how hard could it be 🤷
“What’s a file anyways, more than a bunch of bytes in a specific order?”
I fucking wish
Check out dbus and notify.
And then unpack your dracut initrd.That killed a Plan9 (and 9front) fan.
There is a kernel of truth to this.
I understood that reference!
20 years this year and I still am not sure how it is supposed to be pronounced (in english)
it’s pronounced
gifguy over here trying to start a war
yiff*Now I just wanna know whether
GNUisGuh-nooorJuh-nooorGee-en-yooI haven’t used Linux regularly since 2006, which either means I’m out of the loop or an ancient bearer of lost knowledge:
I think it’s “G’noo” like “G’day” or “G’night.”
The GNU project has a page on it:
It seems he got it correct without knowing.
G’noo be my distro of choice, m’lady
lmao
Gnu like the animal
Wildebeest
the U is silent
a newt?
It’s
Gee-nyoo
linux
The linux is silent
not for linux users!
source: I use linux.
Line-yoox.
Gah Nuu plus Line-ucks
“As I’ve taken to calling it”
except it’s derived from Linus’s name, which in finnish is pronounced as Lee-noos, so technically it should be Lee-noox.
In reality tho? Nobody cares
I just say liinus. Or liinuksi.
It’s pronounced like Liminiux. Lominoliux is also acceptable.
actually, it’s lomi-lominux
Loon - icks
Loin-ughs
Lean-uggs
Lin-ix
So close the lunatic then.
That’s the thing, his pronounciation there is eerlie similar to what I’m used to spanish (where it is pronounced just as it is spelt) that my ol brain kind of does a short-circuit and can’t assimilate the fact that it’s just kind of the same thing in both languages and if it’s in the middle of a sentence I have to go back to speaking my crappy non-native english
Not sure if this helps, but in English (my native language), I would pronounce it with a short “i”, like in “sit”. You could also pronounce it with a Spanish “i” (same as Finnish “i” to my ears). I would not pronounce it with a long English “i” because the vowel length is too long and doesn’t sound right.
It always surprises me how much the pronunciation of Finnish and Dutch resemble each other.
LIH-nucks (rhymes with “tin bucks”).
It is pronounced like that but they don’t rhyme at all
/ˈlɪnuks/
I think it’s /ˈlɪn.əks/ It’s horritic tho, tbh
This gon be another gif or gif situation.
le necks
24 years exclusively running it.
Short answer: magic.
Long answer: a stressful full week trying to get everything right, followed by a long, blissful period forgetting how hard it was to get it up and running like magic.
Those weeks were a lot more stressful, and longer than a week, when I used Slackware and started installing stuff that wasn’t packaged for Slackware. I would dread new software. It was the Unifi controller that finally put me over the edge: I wasn’t even willing to give it a shot. I ran the controller on my Kubuntu desktop for a few weeks until I switched the server to Debian.
It felt like a house of cards. Nudge one of those cards by, say, updating a library, and you could easily break something else.
“If you want to know how Linux works, ask a Slackware user,” is the old saying. It’s true…we had to know, because we didn’t have a choice not to know.
After a dozen of those stressful weeks I decided to write down everything new I learn if I can.
my experiece is just stuff getting fixed and breaking rsndomly tbh.
So many factors at play.
The number of packages installed, the use of externally unsupported repos, the distro you use, reliability of their packaging system, how much you deviated from the baseline customization, and probably more.
Keeping track of everything off what and how much you changed may prove difficult. But it helps taking notes of how you solved the more complicated issues.
With time you learn to live with the inevitability of something breaking. You update less often, and only when you really have to. Repairing stuff becomes less overwhelmeming with time.
When Linux is working, one does not tempt fate by asking why.
One does not ask how the Linux is working, one only asks if.
The more you know, the more you know that you don’t know a damn thing.
