• 2 Posts
  • 182 Comments
Joined 3 years ago
cake
Cake day: January 23rd, 2022

help-circle
  • false dichotomy. Sometimes people justifiably dislike something for reasons beyond elitism (e.g. Canonical is a for-profit corporation that muddies the waters of FOSS), but it’s also not just playful bants.

    Also, as with every opinionated topic: do your own research and think critically. Don’t hate Ubuntu until you have tried it and have investigated those who maintain it. Don’t praise it until you do so either.

    I don’t care if you come to a different conclusion than me, as long as you didn’t just function on the “wisdom of the crowd”


  • When does Debian update a package? And how does it decide when to?

    These both can be answered in depth at Debian’s releases page, but the short answer is:

    Debian developers work in a repo called “unstable” or “sid,” and you can get those packages if you so desire. They will be the most up to date, but also the most likely to introduce breaking changes.

    When the devs decide these packages are “stable enough,” (breaking changes are highly unlikely) they get moved into “testing” (the release candidate repo) where users can do QA for the community. Testing is the repo for the next version of debian.

    When the release cycle hits the ~1.5 year mark, debian maintainers introduce a series of incremental “freezes,” whereby new versions of packages will slowly stop being accepted into the testing repo. You can see a table that explains each freeze milestone for Trixie (Debian 13) here.

    After all the freezes have gone into effect, Debian migrates the current Testing version (currently Trixie, Debian 13) into the new Stable, and downgrades the current stable version to old-stable. Then the cycle begins again

    As for upgrades to packages in the stable/old-stable repos: see the other comments here. The gist is that they will not accept any changes other than security patches and minor bug fixes, except for business critical software that cannot just be patched (e.g. firefox).


  • BaumGeist@lemmy.mltoPeople Twitter@sh.itjust.worksCory hot take.
    link
    fedilink
    arrow-up
    21
    arrow-down
    13
    ·
    25 days ago

    City people have fucked priorities. I moved to a large city from a small rural town, and it’s nothing but noise 24/7.

    People yelling, construction happening, people watching TV with the window open, babies crying, dogs barking, birds calling, cars constantly rumbling by and hitting potholes so loudly it sounds like an explosion, acs running, radio from businesses, crowd noises, hundreds of thousands of little bits of metal and plastic clinging and clanging and pinging and popping, shoes on concrete clicking and clacking, airplanes, conversations going on, gunshots and concerts and car alarms and sirens and parties and car radios all the way up and… Even in the dead of night when it’s all died down, there is this constant low hum coming from the city.

    But specifically fuck the people who play music on their phone i guess.




  • The point of security isn’t just protecting yourself from the threats you’re aware of. Maybe there’s a compromise in your distro’s password hashing, maybe your password sucks, maybe there’s a kernel compromise. Maybe the torrent client isn’t a direct route to root, but one step in a convoluted chain of attack. Maybe there are “zero days” that are only called such because the clear web hasn’t been made aware yet, but they’re floating around on the dark web already. Maybe your passwords get leaked by a flaw in Lemmy’s security.

    You don’t know how much you don’t know, so you should be implementing as much good security practices as you can. It’s called the “Swiss Cheese” model of security: you layer enough so that the holes in one layer are blocked by a different layer.

    Plus, keeping strong security measures in place for something that’s almost always internet connected is a good idea regardless of how cautious you think you’re being. It’s why modern web-browsers are basically their own VM inside your pc anymore, and it’s why torrent clients shouldn’t have access to anything besides the download/upload folders and whatever minimal set of network perms they need.








  • When I think of exquisite sound design, two of my favorite movies spring to mind: Stalker (1979) and The Good, The Bad, and The Ugly.

    The former has such a subtle soundtrack that it’s almost like it’s not there, but without it so much of the atmosphere of a movie that is heavily atmospheric would be lost.

    The latter is just a perfect western with a perfect western soundtrack. The theme is well known, but L’estasi Dell’oro gives me chills every time it starts playing.



  • BaumGeist@lemmy.mltoLinux@lemmy.mlLinux middle ground?
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    2 months ago

    Debian Testing has a lot more current packages, and is generally fairly stable. Debian Unstable is rolling release, and mostly a misnomer (but it is subject to massive changes at a moment’s notice).

    Fedora is like Debian Testing: a good middleground between current and stable.

    I hear lots of good things about Nix, but I still haven’t tried it. It seems to be the perfect blend of non-breaking and most up-to-date.

    I’ll just add to: don’t believe everything you hear. Distrowars result in rhetoric that’s way blown out of proportion. Arch isn’t breaking down more often than a cybertruck, and Debian isn’t so old that it yearns for the performance of Windows Vista.

    Arch breaks, so does anything that tries to push updates at the drop of a hat; it’s unlikely to brick your pc, and you’ll just need to reconfigure some settings.

    Debian is stable as its primary goal, this means the numbers don’t look as big on paper; for that you should be playing cookie clicker, instead of micromanaging the worlds’ most powerful web browser.

    Try things out for yourself and see what fits, anyone who says otherwise is just trying to program you into joining their culture war


  • It will cause a critical error during boot if the device isn’t given the nofail mount option, which is not included in the defaults option, and then fails to mount. For more details, look in the fstab(5) man page, and for even more detail, the mount(8) man page.

    Found that out for myself when not having my external harddrive enclosure turned on with a formatted drive in it caused the pc to boot into recovery mode (it was not the primary drive). I had just copy-pasted the options from my root partition, thinking I could take the shortcut instead of reading documentation.

    There’s probably other ways that a borked fstab can cause a fail to boot, but that’s just the one I know of from experience.


  • BaumGeist@lemmy.mltolinuxmemes@lemmy.worldAverage systemd debate
    link
    fedilink
    arrow-up
    24
    arrow-down
    4
    ·
    2 months ago

    To the feature creep: that’s kind of the point. Why have a million little configs, when I could have one big one? Don’t answer that, it’s rhetorical. I get that there are use cases, but the average user doesn’t like having to tweak every component of the OS separately before getting to doom-scrolling.

    And that feature creep and large-scale adoption inevitably has led to a wider attack surface with more targets, so ofc there will be more CVEs, which—by the way—is a terrible metric of relative security.

    You know what has 0 CVEs? DVWA.

    You know what has more CVEs and a higher level of privilege than systemd? The linux kernel.

    And don’tme get started on how bughunters can abuse CVEs for a quick buck. Seriously: these people’s job is seeing how they can abuse systems to get unintended outcomes that benefit them, why would we expect CVEs to be special?

    TL;DR: That point is akin to Trump’s argument that COVID testing was bad because it led to more active cases (implied: being discovered).


  • I’m gonna laugh if it’s something as simple as a botched fstab config.

    In the past, it’s usually been the case that the more ignorant I am about the computer system, the stronger my opinions are.

    When I first started trying out Linux, I was pissed at it and would regularly rant to anyone who would listen. All because my laptop wouldn’t properly sleep: it would turn off, then in a few minutes come back on; turns out the WiFi card had a power setting that was causing it to wake the computer up from sleep.

    After a year of avoiding the laptop, a friend who was visiting from out of town and uses Arch btw took one look at it, diagnosed and fixed it in minutes. I felt like a jackass for blaming the linux world for intel’s non-free WiFi driver being shit. (in my defense, I had never needed to toggle this setting when the laptop was originally running Windows).

    The worst part is that I’m a sysadmin, diagnosing and fixing computer problems should be my specialty. Instead I failed to put in the minimum amount of effort and just wrote the entire thing off as a lost cause. Easier then questioning my own infallibility, I suppose.