• 3 Posts
  • 35 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle


  • The article you linked probably does not exactly say what you think it does. It’s just a professor in geography and linguistics reporting on an ukrainian neologism, adapting it to french audiences for phonetical convenience, it does not hint at any integration in the french language, quite the opposite, and that’s coming from a specialist in the field. While the neologism is interesting and very useful, this is definitely a very niche use among french people, as far as I’m aware. That being said, TIL thanks to you. The more you know.

    What I should have mentioned earlier, that leaves me scratching my head the most, is that the message makes very little sense. It won’t be legible for anyone who doesn’t speak french (barring a couple of words), so it’s not meant to be read by russian people. What’s more, “de Paris avec amour” is the literal translation of “from Paris with love”, which sounds very natural in english but not in french, at all, and sounds like something that what somebody who doesn’t speak french would get out of google translate or something. The only way I can make it make sense is that this would be entirely manufactured for social media, which tracks with the first impression I had that this image was manipulated and the text added in photoshop or something. This whole thing is very bizarre, hence my incredulous reaction at the premise of it being french at all.

    Hope that clarifies things a bit, and explains why I was instantly weirded out.

    Don’t get me wrong, the rascists (may as well adopt this nifty neologism now haha o/) can, indeed, go to hell and stay there, and french people massively support Ukraine, but it’s still useful to be mindful of what’s shared on social media, no matter how much it supports our positions or not. Probably now more than ever, with AI generative models becoming an increasingly scary problem.





  • Depends. That’s about what I paid for my previous phone second hand and it lasted me 7 years and I loved it to bits. But I was pretty broke and only could afford that. New phone, I decided to buy a brand new fairphone, because i think that the moment I get enough disposable income, I have a moral responsibility to use it in ways that encourage more ethical practices, for all the people who can’t. Doing that is bloody expensive, but if it somehow helps make this dystopian hellscape a little more bearable, I’ll invest.








  • You could switch all your repos to the core Arch ones. I did that by accident once, and it was fine (although, I did switch them back eventually). Maybe it’d add release stability? I’m not really clear how the EOS repos vary off the baseline, except by adding some custom packages.

    They don’t afaik. EOS uses Arch’s repos directly, unlike Manjaro. Just adds its own on top for all the fancy EOS stuff. Which is why EOS was immediately affected by the grub meltdown and not Manjaro. (which kinda digs a few holes in the stability hypothesis, though Manjaro is another kettle of fish tbf)

    Snapper sounds really interesting, and I didn’t expect “super easy” to be the feedback there. Sounds a bit overkill for my use case at home but I might look into it for work. Thanks for the info!

    Oh god a borked BIOS is my nightmare… I don’t even know how you’d go about fixing that on a modern PC mobo… Let’s not jinx it shall we?



  • Nisaea@lemmy.sdf.orgtoLinux@lemmy.mlI'm so frustrated rn.
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    2 years ago

    Mostly using eos-update by clicking on the notification, unless I’m on a terminal where I still have the yay reflex from arch. I should remember to use eos-update though, I do appreciate the extra housekeeping.

    Nop, I avoid nvidia as much as I can as well, I already can’t avoid it at work, too much driver drama. Ryzen and radeon it is, with (almost) no fuss.

    Also mostly using wayland, it works well even on KDE, but got Xorg around just in case, and I’ve had the occasional issue on both. That being said, it’s plymouth that blows up, long before the graphical session is opened, so that shouldn’t have an influence either.

    Maybe I’m just a black cat, and/or maybe it just comes with the territory when you stay long enough on a bleeding-edge-use-at-your-own-risk kinda distro and update almost every day. Something’s bound to go wrong eventually. Which, has also “been Arch with an easier install” for me, tbf.

    Gonna investigate a bit more today, couldn’t be asked yesterday. But if you’re curious I can keep you updated when I find a fix. :)

    Edit: Found the solution by essentially doing the same thing the folks on reddit did with nvidia by enabling early KMS start, and learning quite a bit along the way. Apparently it’s now required by Plymouth and my system didn’t get the memo? Or something? Eh it works.



  • Yeop, you can say that again. Can’t read the Arch wiki on a Nokia 3310 for sure lol

    Tbh I’m not too careful about updates, I have regular backups and grub exploding wasn’t enough to stop me, so eeeeh, if something really goes awfully wrong I have enough free time to deal with it and use it as a learning experience. I know I should be smarter about them like you are, but on my personal computer I just cannot be asked. ^^


  • Nisaea@lemmy.sdf.orgtoLinux@lemmy.mlI'm so frustrated rn.
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    2 years ago

    It’s exactly the opposite for me. Why? Because I’m just not used to Windows and nothing is where I expect it, or works as I would expect, and a lot of it makes no sense to me. On the other hand, I’ve been daily driving Linux since 2010 and I know what to do for most of the things I want to change in my system.

    It’s literally just a matter of what you’re used to. ¯\_(ツ)_/¯


  • https://endeavouros.com/news/full-transparency-on-the-grub-issue/

    A LOT of people’s PCs were bricked, including mine. No boot, just blank screen with blinking cursor. Thankfully Endeavour’s team was quick to react (quicker than Arch, as it happens) and published a full tutorial on how to chroot into your system and downgrade grub, but that already required a good level of knowledge and confidence in the Linux system as none of this was trivial, or intuitive for any stretch of the imagination. I woudl imagine most affected EndeavourOS users who were new-ish to Linux threw the towel that day. Wouldn’t blame them, it was jarring even for me, and it wasn’t my first chroot.