• 9 Posts
  • 1.98K Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle






  • I think this might be getting overblown a bit. I think if this is a communication to an internal community, like in any job, you’d not want people sharing deeply personal information about their sexual orientation and whatnot.

    If I started a new corporate job and started just spouting “Hey, I’m [sexual orientation]” around the office or in chat rooms, I’d probably expect to be notified that it’s not going to be acceptable in a professional environment. I think the Furry thing would also probably be advised against because, regardless of the actual nature, it may make people uncomfortable.

    This person has every right to be announcing this as part of their identity in social settings, but it’s not shocking if it’s not allowed in a professional setting. The uncomfortable meter goes both ways, same as if someone else walks around the office spouting their cis-straight identity or religious bullshit. If it’s making people uncomfortable, they should also have to curb that speech to stop upsetting people in the larger group. I don’t think anyone has come up with a golden solution to solve for this that I’m aware of.

    There doesn’t seem to be any clarifying information on the nature of the list this was part of or anything, so it’s really hard to get the context. If this was a corporate and public communication, it’s not shocking if it was going against some corporate speak no-no bullshit. 🤷

    Edit: Christ, I’m not even saying controversial and I’m being brigaded ffs 🤣












  • Of course I don’t, you’re totally right. My contributions since 1998 mean I have zero idea of how to speak to common sense.

    Using antique hardware to run things is a fool’s errand, and always has been. It’s ridiculous to run outmoded, inefficient, and ineffective hardware for any general purpose.

    If there was a HUGE community out there who really needed something to work with Linux (a la Asahi), then I’d say go for it.

    This is a dumb waste of time with little payoffs except to say you did it. No community benefits.


  • You’re trying way too hard to make a very specific set of hardware work.

    1. The chip in there is going to have a 2GB memory limit, even if it you could expand it and found a module for sale.

    2. The CPU is an old style Intel N or C, both of which have just awful TDP at that age. You’d also have to have it plugged in constantly and draining more power because the battery is certainly dead.

    3. The addressable memory is almost certainly only going to be working for 32-bit without a BIOS hack. I say this because the majority of these produced were 32, but very few were 64. Telling the difference should be obvious by trying to install a microkernel.

    4. Even if you had the best set of circumstances - 64bit, 2GB memory - the rest of the hardwre5is likely to no longer be very compatible with modern kernels. Network, audio, power saving…etc. Almost all certainly will not work as expected.

    5. A $100 SoC board will have better outcomes and cost efficiency for running in general.

    I just don’t see the effort paying off here in taking what was already antiquated hardware when it was produced and making it work now just because it exists.

    To your questions:

    1. No. No modern GUI stack will work with it.
    2. Wayland won’t work with the available memory, at least not for long. Launching a browser would probably start OOMKilling things on any modern distro.