Shell Script Best Practices, from a decade of scripting things

Re:Shell Script Best Practices, from a decade of scripting t... by HyperSane on Thursday October 27, 2022 @11:11AM (#33358746)

"You have much less options when you are processing PowerShell objects."

There is simply no need for the kind of extensive text processing common in Linux because every command returns an object whose fields can be directly referenced. Combined with the ConvertTo-Json command this is incredibly powerful. Honestly it seems like you are attempting to do things in PowerShell the bash way instead of the PowerShell way.

" I think the first thing I tried to do in PowerShell was a script that scanned a directory recursively for files containing a CRC in their name, and then check it"

I wrote a PowerShell script that recursively scanned every filed and folder on our fileshares and wrote the permissions to a file for later indexing.

[ Parent | on HN ]

Re:Shell Script Best Practices, from a decade of scripting t... by ndsipa_pomu on Thursday October 27, 2022 @12:15PM (#33359804)

I tried to write a PowerShell script to recursively scan and find files/folders older than a certain date, but kept hitting problems with the length of the path/filenames. As a complete PowerShell noob, I'm sure I was trying to do it the wrong way, but after a few attempts, I gave up and install cygwin instead.

[ Parent | on HN ]

Re:Shell Script Best Practices, from a decade of scripting t... by Macha on Thursday October 27, 2022 @12:52PM (#33360452)

Your problem here is with win32 not powershell I suspect. Your script would probably have worked with powershell on Linux, but windows you need to use UNC paths to get a 2^16 - ~20 character path limit rather than the 256 character path limit of regular paths.

Or there's some registry hacks to remove the limit from regular paths.

[ Parent | on HN ]

Re:Shell Script Best Practices, from a decade of scripting t... by ndsipa_pomu on Thursday October 27, 2022 @01:25PM (#33360930)

You're probably right. It was a few years ago and after trying a couple of alternatives, just went with what I know.

[ Parent | on HN ]

Re:Shell Script Best Practices, from a decade of scripting t... by HyperSane on Thursday October 27, 2022 @02:14PM (#33361632)

You can enable long path support in Windows to have paths up to 32,767 characters long

https://learn.microsoft.com/en-us/windows/win32/fileio/maxim...

[ Parent | on HN ]

Re:Shell Script Best Practices, from a decade of scripting t... by ndsipa_pomu on Thursday October 27, 2022 @02:23PM (#33361778)

It was a few years back, so probably before Windows included that ability (Windows 10 onwards?)

[ Parent | on HN ]