@krnl386@lemmy.ca avatar

krnl386

@krnl386@lemmy.ca

I’m a computer and open source enthusiast from Toronto, Ontario, Canada.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

krnl386,
@krnl386@lemmy.ca avatar

Love how Rogers, Bell and Telus are pointing fingers at each other. AFAIK Rogers first stated that they didn’t commit to sharing the infrastructure with Bell and Telus at first, to the surprise and dismay of the TTC. Now Rogers is blaming Bell and Telus for dragging their feet… glad to see the Toronto telco market continues to be an absolute shit show. /s

Remote or hybrid workers, would you rather work a 4 day week on site, or WFH completely for 5 days a week, for the same pay?

I know this will vary a lot, so hypothetically let’s say you currently WFH/work remotely at least 3 days a week. Your commute to work takes an hour max (door to door) each way. If you were given the choice of a 4 day week working onsite, or a 5 day week WFH (or as many days as you’d like) for the same pay, which would you...

krnl386,
@krnl386@lemmy.ca avatar

5 days WFH hands down.

krnl386,
@krnl386@lemmy.ca avatar

Awww I hope she recovers.

krnl386,
@krnl386@lemmy.ca avatar

Interesting take. I’ll be making note of this author and reading more of his posts.

deleted_by_author

    •
    krnl386,
    @krnl386@lemmy.ca avatar

    Assuming you were using a Linux software RAID, you should be able to recover it.

    The first step would be to determine what kind of RAID you were using… btrfs, zfs, mdraid/dmraid/lvm… do you know what kind you set up?

    To start the process, try reconnecting your RAID disks to a working Linux machine, then try checking:

    1. The sudo lsblk command will help you get a list of all connected disks, sizes and partitions.
    2. The partition tables on the disks, eg: sudo fdisk -l /dev/sda (that’s a lowercase L and /dev/sda is your disk)
    3. Assuming you use a standard Linux software RAID, try sudo mdadm --examine /dev/sda1. If all goes well, the last command should give you an idea of what state the disk is in, what RAID level you had, etc.
    4. Next, I would try and see if mdadm can figure out how to reassemble the array, so try sudo mdadm --examine --scan. That should hopefully produce output with the name of the RAID array block device (eg, /dev/md0), RAID level and members of the RAID array (number of disks). Let me know what you discover…

    Note: if you used zfs of btrfs, do not do steps 3 and 4; they are MD RAID specific.

    krnl386,
    @krnl386@lemmy.ca avatar

    Good point! I assumed the worst; but it’s possible the array is rebuilding or even already rebuilt and just needs to be mounted.

    krnl386,
    @krnl386@lemmy.ca avatar

    According to LocalSend docs these are the ports that need to be opened: **Multicast (UDP)**Port: 53317 Address: 224.0.0.167 **HTTP (TCP)**Port: 53317 AFAIK macOS firewall is app-based, at least in the GUI. So depending on how you installed LocalSend, you may have to add it to the list of allowed apps: support.apple.com/en-ca/guide/mac-help/…/mac

    You may be able to add the ports above to /etc/pf.conf manually, but AFAIK messing with pf on macOS is not recommended.

    The other thing I wanted to ask is about Vallum. If you have it running on that Mac, would it not “take over” the macOS firewall?

    krnl386,
    @krnl386@lemmy.ca avatar

    I had a similar issue as you, and switching/reseating DP cables solved it for me. This is the switch I am using.

    Also note my monitors can only do 4K@60Hz.

    krnl386,
    @krnl386@lemmy.ca avatar

    Interactive (i.e. end-users) Clients should be using OAuth instead of app passwords. This will allow your users to use their own Office365 credentials for SMTP.

    For servers and non-interactive clients (e.g. copiers/printers/toasters/coffee makers) I would suggest something along the lines here: …microsoft.com/…/how-to-set-up-a-multifunction-de…

    krnl386,
    @krnl386@lemmy.ca avatar

    Ditto here. Either I’m not doing it properly, or this doesn’t affect my build/OS.

    krnl386,
    @krnl386@lemmy.ca avatar

    Thanks for sharing. Very nice writeup.

    krnl386,
    @krnl386@lemmy.ca avatar

    Congrats! I bet you learned a lot along the way…

    krnl386,
    @krnl386@lemmy.ca avatar

    I presume these are filesystem UUIDs. I also presume from your other post, that you used a live USB to fix nvidia drivers? Note that nvidia driver installers/packages trigger a initrd rebuild, and if you do that in a live environment, it’s possible that you will get the UUID of your live USB filesystem and not your actual boot drive… at least that’s my guess.

    If you booted into a live USB you need to make sure that you chroot into your install on your disk whenever doing any operations on the boot loader. That involves mounting your actual disk (eg, /dev/nvme0p1) somewhere on the live USB (eg, /mnt/example), then bind-mounting the proc, sys, dev, tempfs filesystems under /mnt/example/proc, /mnt/example/sys, etc. You may also need to mount /efi under /mnt/example/efi or boot/efi (wherever you have it in your system). Next, chroot to /mnt/example. You should now have a fully functional install you normally boot into, with the only difference being that the kernel booted off the USB drive. Now you can try reinstalling drivers, rebuilding initrd, reconfiguring the bootloader, etc. Since you’re chrooted, the system should see the proper UUIDs, in theory…

    If you want a more comprehensive tutorial on how to do this, look for bootloader fixing tutorials.

    krnl386,
    @krnl386@lemmy.ca avatar

    I think the key would be figuring out where this extra UUID is coming from. Maybe next time you try this, make a note of all the UUIDs on your system (including the bootable USB) and see which one ends up in the bootloader config.

    Knowing what’s happening can help guide your Googling to find out why it’s happening and how to fix it.

    krnl386,
    @krnl386@lemmy.ca avatar

    Weird… the only thing I can think of is that maybe the UUID changes on every boot with live USBs, since the root filesystem is ephemeral …

    krnl386,
    @krnl386@lemmy.ca avatar

    To be fair, average users would never (or should never) encounter such an issue. The person asking uses Arch (I think?) which is by far not an “average person” distribution.

    krnl386,
    @krnl386@lemmy.ca avatar

    Windows is difficult to repair mainly because of the registry, IMHO. Microsoft’s claims that it should never require cleanup doesn’t really make sense… it’s the most practical advice given how convoluted it is, but the fact that a database that keeps getting written to constantly doesn’t ever need any kind of maintenance just doesn’t make sense to me.

    krnl386,
    @krnl386@lemmy.ca avatar

    Ah, that would break things! Any idea how the incorrect UUID got into the kernel boot parameters?

    krnl386,
    @krnl386@lemmy.ca avatar

    That is how you learn! Actually one of the best ways to learn, IMHO.

    krnl386,
    @krnl386@lemmy.ca avatar

    Legacy API and app behaviour support. Ironically replacing the registry with something more straightforward would be relatively easy, unlike adding support for storing home directories on a drive other than C. Technically you can mount a different filesystem under c:/users to achieve this, but AFAIK that’s neither supported nor trivial to do.

    I tried doing it, and gave up. Sure, most software will respect the path changes in the user’s registry hive, however, every once in a while a program will just assume that your home dir lives under c:\documents and settings$username - and that’s when it all goes south. Really frustrating this lack of consistency.

    All in all, the OS is riddled with hacks and “supports” for legacy runtimes and behaviours. Heck, my username is poking fun at the fact that Windows 7 had support for the 386 (yes, Intel’s 80386 processor from the late 80’s) enhanced API. Windows 7…. My username is a “tribute” to a file called krnl386.exe that implemented a bunch of legacy API calls like how much RAM a system has or whether or not the OS is running in “386 enhanced mode” that were relevant back in Windows 3.x days… and still supported in Windows 7. That pretty much sums up why Windows is, and always will be, a hot mess.

    krnl386,
    @krnl386@lemmy.ca avatar

    Did you ask in !privacy?

    krnl386,
    @krnl386@lemmy.ca avatar

    I’m guessing this is a school and not a university? At a university students have more clout/rights, at least on paper.

    In any case, getting your own machine is the way to go. You can run whatever you want on it. You could still (cautiously) use the school network, as long as you use a VPN; basically treat the school network as a “hostile” environment. That’s assuming VPN use is not against the school rules. :)

    krnl386,
    @krnl386@lemmy.ca avatar

    Interesting; it’s consistently not working for me. I managed to change the app icon once, but subsequent attempts keep failing. The icon changes within the app’s settings screen, however, it does not change from the previous selection when I go into the app switcher or the launcher. Killing/restarting the app from the app switcher doesn’t help either.

    EDIT: the symptoms above are happening on app store version 1.10.1. I’m about to update to 1.11.0 to see if it helps.

    krnl386,
    @krnl386@lemmy.ca avatar

    Ok, just updated to 1.11.0 (latest app store release at the time of writing) and it behaves exactly the same. The icon changed after updating, however, subsequent attempts to change it are ineffective as before, even if the app is swiped up from the task selector to “kill” it. It seems like swiping up doesn’t really kill the app, however, installing/reinstalling/updating from the app store does.

    To test this, I’ll try offloading the app (delete app but not app data) and reinstalling to see if my hypothesis about updating/reinstalling is correct.

    Orion browser for macOS and iOS/iPadOS (browser.kagi.com)

    I’ve been testing the Orion browser for macOS and iOS/iPasOS for a few days. It’s WebKit-based, and Apple OS exclusive. First impressions are positive, although I haven’t put it through its paces (check multi-device iCloud settings sync, push tabs to its limits, dig into exactly how it protects privacy by syncing through...

    krnl386,
    @krnl386@lemmy.ca avatar

    It loads and UI seems to work, but it still doesn’t actually block ads or click them.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • anitta
  • everett
  • hgfsjryuu7
  • Youngstown
  • khanakhh
  • slotface
  • rosin
  • InstantRegret
  • ngwrru68w68
  • kavyap
  • vwfavf
  • thenastyranch
  • DreamBathrooms
  • PowerRangers
  • Leos
  • magazineikmin
  • Durango
  • tacticalgear
  • mdbf
  • cisconetworking
  • ethstaker
  • GTA5RPClips
  • osvaldo12
  • cubers
  • modclub
  • tester
  • normalnudes
  • provamag3
  • All magazines
    •