Skip Navigation
agile is far left too. I will die on this hill
  • Honestly i wouldn't mind. Users on .world that don't want a butt load of defederations will probably (and hopefully) move to another instance, whilst the rest of lemmy will be free from all the liberals uncapable of discriminating between communists and tankies

  • How to create a bootable Linux USB drive
  • I don't remember where, but i read that this method only works because linux distributors "abuse" the ISO format to allow this. If I remember right, it's not possible to use this ISOs on regular disks

    Of course the command you provided is right and it's what I use, it's just a fun fact

  • Linux error starter pack
  • I'd like to add this one:

    Uhhuh. NMI received for unknown reason 31 on CPU 3.
    Dazed and confused, but trying to continue
    

    I get this one like once a week and it always makes me laugh. One day I'll investigate

  • Are you using passphrases? Is it worth it?
  • My cybersecurity prof at uni showed us this xkcd during class lol

  • Does ProtonVPN no longer offer the option to pay in crypto?
  • You can create a free account at first and then upgrade using bitcoin.

  • What is the /opt directory?
  • I think it refers to applications that do not respect the standard directories like /usr/bin, /usr/share/man, /etc

  • Is directory monitoring just cursed?
  • Just the other day I wrote something just like this, but I used inotify.

    I have to monitor a fairly small direcotry tho, so I didn't encounter any problem.

    both of which use the inotify interface and attempt to set watches on each individual subdirectory

    Is this really necessary? Inotify's man page says it can monitor a whole directory with only one watch, so that's what I did and it looks like it's working

    I didn't make a lot of tests tho, so I might be wrong

    Edit: from the inotify man page:

    Inotify monitoring of directories is not recursive: to monitor subdirectories under a directory, additional watches must be created. This can take a significant amount time for large directory trees.

    Yeah, it is necessary. That's what I get for not reading the whole thing.

  • got told to crosspost over here to reach more people:
  • Unfortunately i can't help you, but just to be sure, have you downloaded the -nvidia version of the ISO? In case, check it out

    Also try not to daily run with acpi=off, especially on a laptop, as it won't be very power efficient

  • Deleted
    acab rule
  • That's what a fed in your position would say.

  • Master Oogway knew what was up
  • The anguish of being stuck in the present

  • Do any of you program on non-US keyboard layouts?
  • Getting used to it is going to be a hell of a ride, but this is a wonderful thing.

    Also using other pc is going to be even harder lol

  • Do any of you program on non-US keyboard layouts?
  • Same. Forward slash always annoys me. It's in the middle of the keyboard, so you have to either 1. make a very uncomfortable move with your right hand, or 2. make an uncomfortable move with your right hand, or 3. use both your hands, which sucks.

    Luckily I'm using linux, so I have tilde and backtick (`) as AltGr+' and AltGr+ì, which are pretty easy to type.

  • is archive.ph/.is sad or is some content taken down?
  • I'm on mobile rn, it loads on mull (firefox fork) but not on vivaldi

  • People who can don't get mad and just go with the flow, how do you do it?
  • Happened to me too. Best thing is going to therapy.

    This might be caused by bigger problems with your family or work. Or it might just be accumulated stress unrelated to anything in particular.

    Therapy helps either way

  • Node.js segmentation fault does not happen on different envirnment
  • i think i'll submit a report with the exact info of the other environment, when i'll get back at it. for now i'll keep going.

    as another comment is saying, if it's not useful they'll just ignore it.

  • Node.js segmentation fault does not happen on different envirnment
  • yeah i'll probably do this, as soon as i get back to the other environment. thank you :)

  • Node.js segmentation fault does not happen on different envirnment

    Hi. I'm working on a project that compiles Rust code to WASM, and uses WASI in Node.js to execute it. After some development, I encountered a segmentation fault happening in the wasi.start() function. Considering that I'm kinda new to Node I was only able to understand that it was happening after the call to the exported WASM method returned.

    This happened almost two months ago, and while I thought about reporting this to the node devs (WASI's also experimental), I was going to move soon and a lot has gone on.

    Yesterday I tried to reproduce the bug on my laptop (that is not my usual development environment, which I don't have access to right now) but I wasn't able to.

    I had to start fresh and install all the necessary tools from zero, so my theory is that there was something wrong in the previous environment. I'm also on Gentoo now, while I was running Arch previously.

    Unfortunately I don't have the means to check on other environments. I tried to reproduce the old environment, installing the same versions of node and rust, with no luck. I also tested this with the latest versions and everything works fine.

    This situation is upsetting. I don't know what's changed that caused the problem to "disappear", so i feel uncomfortable considering this solved. What would be the best approach in this situation?

    EDIT: I also just tested it on Debian live, and I still wasn't able to reproduce the segfault

    4
    What is your Depression Anthem?
  • Mostly Leaf Ellis from Sorority Noise

  • Aint no Tolerance Paradox round here
  • Maybe a link to this article helps: Tolerance is not a moral precept

  • DNS Resolver Quad9 Wins Pirate Site Blocking Appeal Against Sony
  • Why do you say it's from the police?