I take my shitposts very seriously.

  • 0 Posts
  • 64 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle

  • There are use-cases where a computer should not be turned off by its user for the purpose of remote management. I’m dealing with one just as I’m writing this comment.

    There’s an exam in a classroom. In 20 minutes I’ll have to run an ansible script to remove this group’s work, clean up the project directory, and rollback two VMs to the prepared snapshot to get ready for the next group. I’ve put a big-ass banner on the wallpaper telling the students not to shut down the computer, and already half of them are off.


  • Mainly because our students are idiots and will complain if the computer doesn’t turn off. Or worse, take independent action and hold the power button, or actually yank the power cable. Maybe I should just lean into it and convince them that the monitor is the computer.

    Jokes aside, how could I implement such a policy? I’ve only found one that hides the power buttons from the start menu, but Windows still responds to ACPI.


  • As another IT guy at a university, having to manually turn on 30 computers in a classroom for updates or whatever is already a pain in the ass. Wake on LAN is not a reliable solution. Havin to manually flip over every box, then putting them down, and then fixing the cables that got yanked… I’d throw those fuckers in the trash.

    The Dell Optiplex 3080 Micro’s form factor is perfectly tiny without compromising user comfort.










  • I tried dual-booting Win10 and Arch for a few months. It was problematic.

    I had to set the clock every time I switched because one expected the hardware clock to use UTC time and the other expected local time.

    NTFS on Linux is not good. The driver works, but there are fundamental differences between NTFS and Unix-like filesystems that makes cooperation difficult (e.g. NTFS uses ACLs instead of the user/group ownership and user/group/others permissions of Unix). Windows also places additional restrictions on the filesystem (e.g. NTFS supports file names that contain :, Windows doesn’t) that can completely bork the volume if violated.

    But the worst offender, and what made me nuke Windows entirely, is Windows Update. It completely fucked up the boot partition, deleted the bootloader, then died and left Windows unusable.

    These are all issues that can be solved, if you know how to solve them. My advice is to go cold turkey and delete Windows from your life.





  • (edit) I assume you’re mounting the NTFS volume using fstab, which is how you should mount internal drives. If you’re trying to use the file manager to mount it dynamically, you really should look into how to use the fstab file.

    I’d like to see your mount options.

    As others have said, it’s best to explicitly mount it with the rw option.

    Second, because NTFS doesn’t understand the Unix-like file ownership of users and groups, you have to specify the UID and GID of the mounted filesystem using the uid= and gid= mount options. If you don’t specify these, all files within the NTFS volume will appear as being owned by root. Use the uid=1000,gid=1000 options to mount the volume as owned by your user.

    Third, use the windows_names option as well. Otherwise the filesystem will allow you to create files with illegal names, and that will completely fuck up the volume when mounted on Windows. For example, the : character is permitted by NTFS, but not by Windows.

    Although, in general, just avoid using NTFS on Linux if you can. The driver is good, but there are too many basic conceptual differences between NTFS and most Linux filesystems.