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

help-circle
  • I came here to comment basically this. Except I did it last year and accidentally broke that system. Was trying to do the working directory and mistyped and did the root dir.

    For those that don’t know, so many elevated permissions commands fail if permissions are too open. And even ssh breaks because your certs and authorized_keys need to be only readable by you.

    I luckily was able to wipe and just restore an older image backup.



  • And it freaks the fuck out if that folder name exists. Like if you have a documents folder in a project’s sharedrive, you can’t add it to yours because documents exists.

    The “add shortcut to onedrive” option defaults to your root onedrive, and doesn’t differentiate what the original one drive name was.

    I didn’t see an option to change where the shortcut is made, it just defaults to root. You can manually move the shortcut after it is created though. But this was a pain last time I tried it.

    Same with mapping a teams group shared folder. We have a teams for each project, and a resources folder in that. It is a pain to open teams, so I tried mapping it to my one drive where I already have a folder for each project. So you go to teams, “add shortcut to onedrive”, go to your one drive folder and drag that shortcut to the appropriate folder, then repeat. Oh but project 3 is named differently and that folder name already exists in your one drive, here is some vague error. Ok, rename what I have in my onedrive, try to add the shortcut again, move shortcut, rename the file in my onedrive root back to what it was.

    That dialog should just ask for a export location.